fix: consistently use ErrorDetail in StackTrace #2
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Fix parse error when error happens in library * Test dev message * fix a test * split out dev reason test --------- Co-authored-by: Charles Cooper <[email protected]>
* feat: added vvm related methods * test: vvm compilation with old version * chore: pre-commit run for ci * test: fix import path for CI execution * test: corrected path * merge vvm deployer into regular loads entry point * refactor VVMDeployer --------- Co-authored-by: Charles Cooper <[email protected]>
regressions introduced in vyper-0.4.0 upgrade and zksync plugin refactor (2a0065d)
- refactor _hook_trace_computation architecture to deal with lack of support in coverage.py for multiple dynamic_source_filenames per (python) function call - refactor the reporter to only depend on ast, not compilation. this is because imported modules may not be valid compilation targets, so we can't depend on compiling them. luckily, parsing to ast may be a much faster method for generating the necessary data.
* Jupyter plugin simplify and test * Run jupyter tests separately with proper dependencies * Outline imports * Cleanup memory on error * Jupyter tests back to unitary, dependencies in dev-requirements.txt * Cleanup dependencies file
the mock wrapper for internal functions would report a file of `"VyperContract"`. we can ignore these (as soon as they enter into the actual module, the pc traces should be correct anyway).
- fix exit_counts - fix lineno for for loop variables (skip it)
multiple paths in coverage for the same file can blow up the coverage report
fix: coverage paths
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes vyperlang#225
Moved from vyperlang#239
What I did
Converted the stack traces for ABI and unknown contracts to a list of
ErrorDetailinstead ofstr.How I did it
How to verify it
Description for the changelog
Cute Animal Picture