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

chore: deprecate upgrade standards implementation #856

Merged
merged 3 commits into from
Jul 1, 2022

Conversation

austinabell
Copy link
Contributor

Not quite sure why this was added, somewhat broken as per #855 and the interface doesn't make much sense and is inefficient.

Deprecating for now and can optimize/update if there are real use cases or the standard is actually added to NEPs

Copy link
Contributor

@itegulov itegulov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This might make more sense as an example. WDYT?

@austinabell
Copy link
Contributor Author

austinabell commented Jun 28, 2022

@ChaoticTempest noting that the CI had a failure with the same error as before, just to note the non-deterministic failures are still happening after the patch update pulled in (maybe less frequent, unclear yet)

@ChaoticTempest
Copy link
Member

@austinabell hmm, weird. Yeah keep updating me about these. Might need to up it via the env var to 100 secs, or maybe its not even a timeout issue happening, but that the sandbox node wasn't able to start up. If its the latter that's the issue, the error should have been reported earlier on... It could be that GH has a shared CPU behind its task scheduling, so you get bursty workloads that leads to this non-determinism

@austinabell austinabell merged commit 41eb838 into master Jul 1, 2022
@austinabell austinabell deleted the austin/deprecate_upgrade branch July 1, 2022 16:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants