-
Notifications
You must be signed in to change notification settings - Fork 382
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
Infinite Loop Caused by Self-Referencing Struct in Map #2035
Comments
omarsy
added a commit
to TERITORI/gno
that referenced
this issue
May 4, 2024
7 tasks
omarsy
added a commit
to TERITORI/gno
that referenced
this issue
May 4, 2024
omarsy
added a commit
to TERITORI/gno
that referenced
this issue
May 4, 2024
omarsy
added a commit
to TERITORI/gno
that referenced
this issue
May 5, 2024
deelawn
pushed a commit
that referenced
this issue
May 6, 2024
…edValue (#2036) Closes #2035. <!-- please provide a detailed description of the changes made in this pull request. --> <details><summary>Contributors' checklist...</summary> - [ ] Added new tests, or not needed, or not feasible - [ ] Provided an example (e.g. screenshot) to aid review or the PR is self-explanatory - [ ] Updated the official documentation or not needed - [ ] No breaking changes were made, or a `BREAKING CHANGE: xxx` message was included in the description - [ ] Added references to related issues and PRs - [ ] Provided any useful hints for running manual tests - [ ] Added new benchmarks to [generated graphs](https://gnoland.github.io/benchmarks), if any. More info [here](https://github.com/gnolang/gno/blob/master/.benchmarks/README.md). </details>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Infinite Loop Caused by Self-Referencing Struct in Map
Description
During panic situations in our application realm, we've encountered an issue related to a self-referencing struct within a map. When attempting to print the state of the machine during a panic using
machine.String()
, the application enters an infinite loop.Steps to reproduce
Logs
Proposed solution
I will open a PR with a solution
The text was updated successfully, but these errors were encountered: