-
Notifications
You must be signed in to change notification settings - Fork 11.2k
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
Move Trace Debugger Bug #20727
Comments
@Vadim-Kolchanov thanks for flagging this! |
@awelc would you have any idea what might be wrong? |
@Vadim-Kolchanov, thank you for the report indeed! I think I know what the problem is but it would be great if you could share your code so that I can confirm my suspicion, create a fix, and produce tests that will ensure that this will not happen in the future |
@awelc, I can't share the source code, because it's still in development. But I created a separate project (with the entire structure preserved), where the error is reproduced. I hope this will help you. |
Thank you! That helped a lot! The fix is in the works and hopefully a new version will soon land in the VSCode marketplace (will keep you posted) |
@awelc Thank you! I see you've done a great job |
The new version of the extension has been published, though admittedly support for dynamic fields is somewhat lacking. Will work on trying to improve it shortly, though! |
## Description This PR fixes trace ingestion for the case when global location is used in a write to address a problem reported in #20727 ## Test plan Added a new test (all new and old tests must pass)
I want to debug the code by running tests in VS code. I use
Move Trace Debugger
extension .sui move test --trace-execution
. Folder "traces" was created successfullyExpected Result
The debugger will start successfully
Actual Result
Get an error:
System Information
sui 1.39.3-5d4350d66d2b
sui-move 1.39.3-5d4350d66d2b
2024.beta
The text was updated successfully, but these errors were encountered: