We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Some proposals pull their CoreEval submissions from the web. Some use a subdir on disk.
The subdir is good because it doesn't make CI dependent on network requests to wherever the CoreEval is stored.
But we need some way to validate that they match. It could be manual and also in CI as advisory.
The text was updated successfully, but these errors were encountered:
Note, to pull from a mainnet RPC node itself, the following should work:
agd query gov proposal $PROPOSAL_NUM -o json | jq -r '.content.evals'
Yields the following shape:
[ { "json_permits": "..." "js_code": "..." } ]
Sorry, something went wrong.
turadg
Successfully merging a pull request may close this issue.
Some proposals pull their CoreEval submissions from the web. Some use a subdir on disk.
The subdir is good because it doesn't make CI dependent on network requests to wherever the CoreEval is stored.
But we need some way to validate that they match. It could be manual and also in CI as advisory.
The text was updated successfully, but these errors were encountered: