Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Tags: TERITORI/gno

Tags

v0.0.1-dev.2024.06.01

Toggle v0.0.1-dev.2024.06.01's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
feat(docs/home): Add Faucet Hub & `gno.land/faucet` mentions (gnolang…

…#2124)

<!-- please provide a detailed description of the changes made in this
pull request. -->

## Description

Closes [gnolang#2121](gnolang#2121)

<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
- [ ] 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>

v0.0.1-dev.2024.05.01

Toggle v0.0.1-dev.2024.05.01's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
fix(cmd/gnoland): fixup startup ascii art (gnolang#1942)

This is _very_ important

v0.0.1-dev.2024.04.01

Toggle v0.0.1-dev.2024.04.01's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
fix: hardcode max vm cycles in keeper (gnolang#1807)

<!-- please provide a detailed description of the changes made in this
pull request. -->
This hardcodes the maximum VM cycles in the keeper to ten million, the
same that is currently being used from genesis. It doesn't seem like
there is a reason why we should want people to be able to adjust this.
<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>

v0.0.1-dev.2024.03.01

Toggle v0.0.1-dev.2024.03.01's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
fix(gnovm): don't treat `[]byte("xxx")` as a constant expression (gno…

…lang#1597)

this is a fix to gnolang#1570 .

The underlying issue in gnolang#1570 stems from how []byte("xxx") is handled:
it's treated as a constant, yet its value can still be altered. This
mutability leads to unintended persistence of its state across loop
iterations.

The proposed resolution involves modifying the preprocessing stage to
avoid converting an untyped string directly into a []byte type.