Skip to content
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

Closed
trentmc opened this issue Jan 2, 2023 · 3 comments · Fixed by #422
Closed

[duplicate] CI fails with "KeyError: development" #421

trentmc opened this issue Jan 2, 2023 · 3 comments · Fixed by #422
Assignees
Labels
Status: Duplicate This issue or pull request already exists Type: Bug Something isn't working

Comments

@trentmc
Copy link
Member

trentmc commented Jan 2, 2023

Problem

I'm seeing failures in CI like this log. It fully fails.

Traceback:

INTERNALERROR>     return func(*args, **kwargs)
INTERNALERROR>   File "/home/runner/work/df-py/df-py/util/oceanutil.py", line 40, in recordDeployedContracts
INTERNALERROR>     a = json.load(json_file)[network]  # dict of contract_name: address
INTERNALERROR> KeyError: 'development'

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)

trentmc pushed a commit that referenced this issue Jan 2, 2023
@trentmc trentmc reopened this Jan 2, 2023
@trentmc
Copy link
Member Author

trentmc commented Jan 2, 2023

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
https://github.com/oceanprotocol/df-py/actions/runs/3824462271/jobs/6506627108

Both in the CI for this PR : #404

@trentmc trentmc changed the title CI sometimes fails because Barge isn't ready CI sometimes fails. Because Barge isn't ready? Jan 2, 2023
@trentmc trentmc changed the title CI sometimes fails. Because Barge isn't ready? CI fails with "KeyError: development". Barge issue? Jan 3, 2023
@trentmc trentmc added the Type: Bug Something isn't working label May 4, 2023
@trentmc
Copy link
Member Author

trentmc commented May 5, 2023

Maybe this is related to #438 "switch to new barge"? Handing this to @calina-c too. Thanks! :)

@trentmc trentmc changed the title CI fails with "KeyError: development". Barge issue? CI fails with "KeyError: development" May 9, 2023
@trentmc trentmc added the Status: Duplicate This issue or pull request already exists label May 10, 2023
@trentmc trentmc changed the title CI fails with "KeyError: development" [duplicate] CI fails with "KeyError: development" May 10, 2023
@trentmc
Copy link
Member Author

trentmc commented May 10, 2023

Duplicate with #547

@trentmc trentmc closed this as completed May 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Duplicate This issue or pull request already exists Type: Bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants