-
Notifications
You must be signed in to change notification settings - Fork 824
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
Make runtime and trap errors well defined #1401
Merged
bors
merged 9 commits into
master
from
feature/runtime-errors-and-traps-are-well-defined
Apr 28, 2020
Merged
Make runtime and trap errors well defined #1401
bors
merged 9 commits into
master
from
feature/runtime-errors-and-traps-are-well-defined
Apr 28, 2020
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
MarkMcCaskey
added
📦 lib-compiler-cranelift
About wasmer-compiler-cranelift
📦 lib-deprecated
About the deprecated crates
labels
Apr 23, 2020
bors try |
tryBuild failed:
|
bors try |
bors try- |
MarkMcCaskey
force-pushed
the
feature/runtime-errors-and-traps-are-well-defined
branch
from
April 24, 2020 21:32
197f2f8
to
ae40d05
Compare
bors try |
MarkMcCaskey
force-pushed
the
feature/runtime-errors-and-traps-are-well-defined
branch
from
April 24, 2020 21:55
ae40d05
to
9723270
Compare
bors try- |
bors try |
tryBuild failed: |
bors try |
tryBuild failed: |
bors try |
bors try- |
MarkMcCaskey
force-pushed
the
feature/runtime-errors-and-traps-are-well-defined
branch
from
April 27, 2020 21:01
e1eac95
to
d0cd9d5
Compare
bors try- |
bors try |
MarkMcCaskey
force-pushed
the
feature/runtime-errors-and-traps-are-well-defined
branch
from
April 27, 2020 21:35
d0cd9d5
to
72196ee
Compare
bors try- |
bors try |
tryBuild failed: |
MarkMcCaskey
force-pushed
the
feature/runtime-errors-and-traps-are-well-defined
branch
from
April 27, 2020 21:59
72196ee
to
74ddc8e
Compare
bors try |
MarkMcCaskey
changed the title
Make runtime and trap errors well defined (WIP)
Make runtime and trap errors well defined
Apr 27, 2020
tryBuild succeeded: |
MarkMcCaskey
added
📦 lib-compiler-llvm
About wasmer-compiler-llvm
📦 lib-compiler-singlepass
About wasmer-compiler-singlepass
labels
Apr 27, 2020
syrusakbary
approved these changes
Apr 27, 2020
nlewycky
reviewed
Apr 27, 2020
nearprotocol-bulldozer bot
pushed a commit
to near/nearcore
that referenced
this pull request
Apr 28, 2020
Due to wasmerio/wasmer#1409 we need to rollback Wasmer to older version. I am replacing some of Wasmer generated error with Unknown to avoid undoing too much code from this PR: #2505 After the following PR lands wasmerio/wasmer#1401 we would need to revisit error handling from Wasmer anyway. CC @fckt ### Testing Ran near-evm test. CI passes.
bors r+ |
bors bot
added a commit
that referenced
this pull request
Apr 28, 2020
1401: Make runtime and trap errors well defined r=syrusakbary a=MarkMcCaskey Resolves #1328 This PR goes through and gives explicit types for all the errors instead of using `Box<dyn Any + Send>` where possible. This gives users better insight into what the specific errors are and should help with debugging in the case of mistakes in our code. The remaining uses of `Box<dyn Any>` are due to the structure of our dependency graph -- this is probably solvable but it seems fine as is as all error types are now explicit and the remaining `Box<dyn Any>`s are either fully user controlled or not for end-user consumption. # Review - [x] Add a short description of the the change to the CHANGELOG.md file Co-authored-by: Mark McCaskey <[email protected]>
Build failed:
|
bors r+ |
Build succeeded:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
📦 lib-compiler-cranelift
About wasmer-compiler-cranelift
📦 lib-compiler-llvm
About wasmer-compiler-llvm
📦 lib-compiler-singlepass
About wasmer-compiler-singlepass
📦 lib-deprecated
About the deprecated crates
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.
Resolves #1328
This PR goes through and gives explicit types for all the errors instead of using
Box<dyn Any + Send>
where possible. This gives users better insight into what the specific errors are and should help with debugging in the case of mistakes in our code.The remaining uses of
Box<dyn Any>
are due to the structure of our dependency graph -- this is probably solvable but it seems fine as is as all error types are now explicit and the remainingBox<dyn Any>
s are either fully user controlled or not for end-user consumption.Review