-
Notifications
You must be signed in to change notification settings - Fork 369
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Full build machine paths in panic messages #1918
Labels
dev-experience
improvements to DevX
Comments
the |
This seems more like something that should be fixed in the Rust compiler.
|
Yeah, my 2 cents:
|
Looks like we cannot build the panic message ourselves, since access to |
Merged
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
When a Wasm contract panicks, the full file path and line number is visible in the panic message. If a user does not use workspace-optimizer/rust-optimizer, this exposes personal file system infomation
The contents of the Aborted error is coming from Wasm:
The source of this is https://github.com/CosmWasm/cosmwasm/blob/v1.4.1/packages/std/src/panic.rs#L10-L12. If I recall correctly, this used to be a relative path.
It seems like more recent versions of Rust use a line break between location and message.

So to me there are two open questions:
let full_message = info.to_string();
?The text was updated successfully, but these errors were encountered: