-
Notifications
You must be signed in to change notification settings - Fork 515
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AATH "acapy-main" build failing -- seems to be an issue with finding the right version of ConfigArgParse? #1842
Comments
@andrewwhitehead @dbluhm -- help! :-). Perhaps this is intermittent or something to do with downloading files. However, I'm not sure I've ever seen these messages If it is something in the changes -- I'm guessing it would be something to do with #1833, as perhaps that impacts ConfigArgParse since it is in that area. But that seems to be a stretch. Perhaps a change to the version of pip? Sigh... |
@nodlesh -- FYI -- none of the ACA-Py tests ran today because of this issue. |
Tried a few things that didn't impact.
So it appears to be something that changed in the environment. |
After some playing around, we determined that the error was not with ConfigArgParse, but rather with a recent merge done for this PR sicpa-dlab/acapy-resolver-universal#16 in the ACA-Py Resolver. That changed locked the ACA-Py version to 0.7.3, which conflicted with the requirement that ACA-Py be at whatever is current on the "main" branch. Temporary fix to lock https://github.com/sicpa-dlab/acapy-resolver-universal to the commit prior to the merge of the PR above. We'll sort out with those folks how to resolve this long term. |
When I try to build the acapy-main AATH Test Agent (commands
git clone https://github.com/hyperledger/aries-agent-test-harness; cd aries-agent-test-harness; ./manage rebuild -a acapy-main
, the process does not seem to complete.I get a the following errors:
The job continues, but seems to hang here:
The text was updated successfully, but these errors were encountered: