-
Notifications
You must be signed in to change notification settings - Fork 344
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
Fix backtraces feature #1613
Fix backtraces feature #1613
Conversation
#![cfg_attr(feature = "backtraces", feature(backtrace))] | ||
#![cfg_attr(feature = "backtraces", feature(error_generic_member_access))] | ||
#![cfg_attr(feature = "backtraces", feature(provide_any))] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see you are putting into life those changes from thiserror
: https://github.com/dtolnay/thiserror/pull/182/files
Thank you for bringing this up, @toml01. Happy to look into it. However, could you keep the PR minimal and specific to one thing? It seems like the whole lockfile is updated for no reason, including a bump of schemars and as a result newly generated JSON Schemas. This is cool, but should get its own PR. You can sue the dev scripts from the main README to only perform minimal lockfile updates: # Updates ./Cargo.lock
./devtools/check_workspace.sh
# Updates ./contracts/**/Cargo.lock
./devtools/check_contracts_fast.sh |
The schemars upgrade is now here: #1617 |
@webmaster128 yeah I was just trying to make the tests pass. |
4edc542
to
4eb3279
Compare
@webmaster128 I think it looks good now, lmk if I can do anything else :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, thanks a lot!
Published as part of 1.2.2 today |
The
backtraces
feature seems to be broken for a while now, this commit fixes it.