Skip to content
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: correct panic message for ParseMemPackage() #1052

Merged
merged 2 commits into from
Aug 17, 2023

Conversation

harry-hov
Copy link
Contributor

@harry-hov harry-hov commented Aug 16, 2023

The ParseMemPackage() function panics when encountering a
package name mismatch. The panic message stated,
"expected package name [%s] or [%s_test], but got [%s]". However,
since we are skipping the _test.gno files, we should never expect
[%s_test] as a package name. This commit fixes the error message
to accurately reflect this condition.

Signed-off-by: Hariom Verma hariom.verma@tendermint.com

Contributors' checklist...
  • 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, if any. More info here.

The ParseMemPackage() function panics when encountering a
package name mismatch. The panic message stated,
"expected package name [%s] or [%s_test], but got [%s]". However,
since we are skipping the _test.gno files, we should never expect
`[%s_test]` as a package name. This commit fixes the error message
to accurately reflect this condition.

Signed-off-by: Hariom Verma <hariom.verma@tendermint.com>
@github-actions github-actions bot added the 📦 🤖 gnovm Issues or PRs gnovm related label Aug 16, 2023
@harry-hov harry-hov marked this pull request as ready for review August 16, 2023 09:56
Copy link
Member

@zivkovicmilos zivkovicmilos left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good 💯

@moul moul merged commit c0aea10 into gnolang:master Aug 17, 2023
49 checks passed
Doozers pushed a commit to Doozers/gno that referenced this pull request Aug 31, 2023
The ParseMemPackage() function panics when encountering a
package name mismatch. The panic message stated,
"expected package name [%s] or [%s_test], but got [%s]". However,
since we are skipping the _test.gno files, we should never expect
`[%s_test]` as a package name. This commit fixes the error message
to accurately reflect this condition.

Signed-off-by: Hariom Verma <hariom.verma@tendermint.com>

<details><summary>Contributors' checklist...</summary>

- [x] Added new tests, or not needed, or not feasible
- [x] Provided an example (e.g. screenshot) to aid review or the PR is
self-explanatory
- [x] Updated the official documentation or not needed
- [x] No breaking changes were made, or a `BREAKING CHANGE: xxx` message
was included in the description
- [x] Added references to related issues and PRs
- [x] Provided any useful hints for running manual tests
- [x] 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>

Signed-off-by: Hariom Verma <hariom.verma@tendermint.com>
@moul moul added this to the 🚀 main.gno.land (required) milestone Sep 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
📦 🤖 gnovm Issues or PRs gnovm related
Projects
Archived in project
Archived in project
Development

Successfully merging this pull request may close these issues.

3 participants