-
Notifications
You must be signed in to change notification settings - Fork 10
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
[duplicate] CI fails with "KeyError: development" #421
Labels
Comments
Looks like the change didn't fix the issue :( I just got the same error again https://github.com/oceanprotocol/df-py/actions/runs/3824465553/jobs/6506633126 and again Both in the CI for this PR : #404 |
trentmc
changed the title
CI sometimes fails because Barge isn't ready
CI sometimes fails. Because Barge isn't ready?
Jan 2, 2023
trentmc
changed the title
CI sometimes fails. Because Barge isn't ready?
CI fails with "KeyError: development". Barge issue?
Jan 3, 2023
Closed
trentmc
changed the title
CI fails with "KeyError: development". Barge issue?
CI fails with "KeyError: development"
May 9, 2023
trentmc
changed the title
CI fails with "KeyError: development"
[duplicate] CI fails with "KeyError: development"
May 10, 2023
Duplicate with #547 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Problem
I'm seeing failures in CI like this log. It fully fails.
Traceback:
ocean.py has a similar issue, reported in ocean.py#1259.
Candidate Solution (Failed)
Trent Q to Calina: I think it's trying to test before barge is ready, right? Can you point me to the similar issue we saw in ocean.py, and the similar fix, please?
Calina: https://github.com/oceanprotocol/df-py/actions/runs/3824009524/workflow#L38 you have to increase the 50 here
(This was tried, it didn't work)
The text was updated successfully, but these errors were encountered: