Moul patch 1 #1159

moul · 2023-09-21T12:38:06Z

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.

This PR introduces a new `gno lint` subcommand, currently focused on checking for the presence of a `gno.mod` file in a package, and it's linked with the CI. In the future, we plan to expand `gno lint` to support additional checks, enhancing its utility for developers and CI integration. Addresses gnolang#850 Addresses gnolang#927 Related with gnolang#965 (comment) Signed-off-by: Manfred Touron <[email protected]> Co-authored-by: Miloš Živković <[email protected]>

Co-authored-by: Manfred Touron <[email protected]>

…1028) Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Implement `gno mod init` command. Usage: ```sh $ gno mod init <module-path> ``` If no `<module-path>` is given, tries to determine package name from existing `*.gno` files. <details><summary>Checklists...</summary> ## Contributors Checklist - [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 - [ ] Added references to related issues and PRs - [x] Provided any useful hints for running manual tests - [ ] Added new benchmarks to [generated graphs](https://gnoland.github.io/benchmarks), if any. More info [here](../.benchmarks/README.md). ## Maintainers Checklist - [x] Checked that the author followed the guidelines in `CONTRIBUTING.md` - [x] Checked the conventional-commit (especially PR title and verb, presence of `BREAKING CHANGE:` in the body) - [x] Ensured that this PR is not a significant change or confirmed that the review/consideration process was appropriate for the change </details>

…nolang#1034) Co-authored-by: Manfred Touron <[email protected]> Co-authored-by: Iuri Pereira <[email protected]>

Signed-off-by: Manfred Touron <[email protected]>

Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Co-authored-by: İlker G. Öztürk <[email protected]> Co-authored-by: İlker G. Öztürk <[email protected]>

…gnolang#1003) Bumps [github.com/mattn/go-runewidth](https://github.com/mattn/go-runewidth) from 0.0.14 to 0.0.15. <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/mattn/go-runewidth/commit/44b7c5b4d67df8ca22917b6800c158a6d3be3560"><code>44b7c5b</code></a> Merge pull request <a href="https://redirect.github.com/mattn/go-runewidth/issues/73">#73</a> from shogo82148/add-go1.20</li> <li><a href="https://github.com/mattn/go-runewidth/commit/fdb25172dac50a5bd73898f88e6e057635be9c26"><code>fdb2517</code></a> Merge pull request <a href="https://redirect.github.com/mattn/go-runewidth/issues/72">#72</a> from shogo82148/bump-github-actions</li> <li><a href="https://github.com/mattn/go-runewidth/commit/da7ce5baf2cc56998284df900192124a1c05390c"><code>da7ce5b</code></a> add Go 1.20, 1.19, 1.18 and 1.17 to the build matrix.</li> <li><a href="https://github.com/mattn/go-runewidth/commit/4874798c9a78e5e99d7872c19eaab85d833b5445"><code>4874798</code></a> bump GitHub Actions</li> <li>See full diff in <a href="https://github.com/mattn/go-runewidth/compare/v0.0.14...v0.0.15">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=github.com/mattn/go-runewidth&package-manager=go_modules&previous-version=0.0.14&new-version=0.0.15)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

…ng#945) Fix bug where `gno test` command doesn't recognize `_test.gno`/`_filetest.gno` file if directly passed as arg. Fixes another bug where `gno test` avoids absolute path in arguments. Note: This PR may contain some code that will be used to support future PR like gnolang#682 and PR that I will open after this to support patterns in arg.

`TestPackages` wasn't actually reporting test failures, due to a bug in the underlying function `machine.TestMemPackage()`. `TestMemPackage` was running the gno tests by just calling the test function with a new `testing.T`, but then it's not possible to detect if there's any failure, because `testing.T` has only private fields. The fix is to change that to a call to `testing.RunTest()` function, which is already used by `gno test`, and returns a `testing.Report` on which we can detect failures. A test has been added (see `TestMachineTestMemPackage()`) in gnovm/tests folder (because a `TestStore` is needed). On master, this test is failing. ``` go test ./gnovm/tests -v -run TestMachineTestMemPackage ``` The next step should be to merge the 2 ways that currently exists to run gno tests, i.e. `gno test` and `go test -run TestPackages`. Potentially this could fix gnolang#896. ## Contributors Checklist - [x] 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 - [x] Provided any useful hints for running manual tests - [ ] Added new benchmarks to [generated graphs](https://gnoland.github.io/benchmarks), if any. More info [here](../.benchmarks/README.md). ## Maintainers Checklist - [x] Checked that the author followed the guidelines in `CONTRIBUTING.md` - [x] Checked the conventional-commit (especially PR title and verb, presence of `BREAKING CHANGE:` in the body) - [x] Ensured that this PR is not a significant change or confirmed that the review/consideration process was appropriate for the change </details> --------- Co-authored-by: Manfred Touron <[email protected]>

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

@jaekwon

Asked by @jaekwon in gnolang#896 (comment) Add a long description for `gno test -h`, that explains the different files, `*_test.gno` and `*_filetest.gno`, and gives the list of instructions related to the latter. Thanks in advance for correcting my frenglish :) <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> --------- Co-authored-by: Manfred Touron <[email protected]> Co-authored-by: Morgan <[email protected]>

…nolang#1064) This PR fixes gnolang#1063. It downgrades `github.com/btcsuite/btcd/btcutil v1.1.1` to `v1.0.0` to resolve conflicts in the dependency graph for the `github.com/btcsuite/btcd` package and its dependencies. More information can be found in the issue above. <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: D4ryl00 <[email protected]>

simply add `path` package to stdlib, needed by `net/url` package (and probably some other packages) <details><summary>Contributors' checklist...</summary> - [X] 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 - [X] 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> Signed-off-by: gfanton <[email protected]>

@ekleiner

fixes gnolang#1060 (maybe). @ekleiner to verify :)

<details><summary>Original text from gnolang#825</summary> <p> # Description Part of gnolang#692 gnolang#585 BREAKING CHANGE: In GitHub Action Flow, the build script needs to be updated on moving tm2txsync from tm2/cmd to gno.land/cmd ## gno.land/ It provides information and tools necessary for running gno.land node. It includes - a node application for starting gnoland nodes to deliver an RPC endpoint - gnoweb for web access to the chain. - tools to interact with gno nodes. - a cosmos SDK gno VM module with keeper and handler. In the future, we plan to consolidate tools for node deployment and monitoring. The future plan also includes supporting both IBC and ICS. ## gnovm/ Gnovm is agnostic to any SDK or chain. It is intended for gno contract developers and gno VM developers. It includes - a gno development CLI - gnolang language - virtual machine implementation. - standard libraries for gno contracts, - examples and test cases. Future plans include making gnovm compatible with IBC ## tm2/ Tendermint2 is a BFT consensus engine and a set of tools for blockchain builders More details can be found at [https://github.com/tendermint/tendermint2#readme](https://github.com/tendermint/tendermint2#readme) In the future, tm2 plans to: - Remain synchronized with the tendermint2 repository. - Port issue fixes between Tendermint v0.23.4 and v0.34. - Ensure compatibility with IBC and ABCI2. # The dependences among tm2, gnovm and gno.land - gno.land depends on tm2 and gnovm - gnovm depends on tm2 - tm2 is independent to gnovm and gno.land ```mermaid flowchart LR A[gno.land]--> B[gnovm] --> C[tm2] A --> C ``` # Discussion ## client commands We aim to establish a clear dependency structure between these components as outlined earlier. Ideally we'd like to have clear dependency between these components as listed above At present, tm2/pkg/crypto/keys/client/root.go is dependent on gno.land/pkg/sdk/vm. We're considering moving the following commands to gno.land/cmd/gnokey/ and eliminating the newMakeTxCmd() from cmd.AddSubCommands() in tm2/pkg/crypto/client/root.go: - addpkg.go - call.go - send.go - maketx.go However, these files rely on the private config structure and private methods defined in tm2/pkg/crypto/keys/client/. Until we decide the next steps, these files will remain in tm2, which means that tm2/ continues to depend on gno.lang/ for now. ## genproto As for the genproto, we need to decide where misc/genproto/genproto.go should be placed. ## sample tendermint2 program Since we've moved out applications that depend on gno in tm2, we need to consider whether we should reintroduce the sample tendermint application or create a new one. [tendermint classic main.go](https://github.com/tendermint/classic/tree/master/cmd/tendermint) </p> </details> <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> --------- Co-authored-by: piux2 <> Co-authored-by: Manfred Touron <[email protected]>

Bumps [golang.org/x/term](https://github.com/golang/term) from 0.11.0 to 0.12.0. <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/golang/term/commit/f413282cd8dbb55102093d9f16ab3ba90f7b9b31"><code>f413282</code></a> go.mod: update golang.org/x dependencies</li> <li>See full diff in <a href="https://github.com/golang/term/compare/v0.11.0...v0.12.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=golang.org/x/term&package-manager=go_modules&previous-version=0.11.0&new-version=0.12.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

- simplify Less() and remove the unnecessary panic check - add comments - add tests

2 ways to reproduce : - Using a filetest: ``` go run ./gnovm/cmd/gno test -verbose ./examples/gno.land/p/demo/tests/ -run file/z0 ? ./examples/gno.land/p/demo/tests/subtests [no test files] === RUN file/z0_filetest.gno panic: expected JSON object but got "20" goroutine 1 [running]: github.com/gnolang/gno/tm2/pkg/amino.(*Codec).MustMarshalJSON(...) /home/tom/src/gno/tm2/pkg/amino/amino.go:818 github.com/gnolang/gno/tm2/pkg/amino.MustMarshalJSON({0xda1d40?, 0xc0001305a0?}) /home/tom/src/gno/tm2/pkg/amino/amino.go:140 +0x53 github.com/gnolang/gno/gnovm/pkg/gnolang.StoreOp.String({0x0, {0x1026bf0, 0xc0001305a0}, {0x0, 0x0}}) /home/tom/src/gno/gnovm/pkg/gnolang/store.go:654 +0xb2 github.com/gnolang/gno/gnovm/pkg/gnolang.(*defaultStore).SprintStoreOps(0xc0000166c0) /home/tom/src/gno/gnovm/pkg/gnolang/store.go:687 +0xff github.com/gnolang/gno/gnovm/tests.RunFileTest({0xc000357158, 0x11}, {0xc0003691a0, 0x2e}, {0xc0001499e8, 0x1, 0x1013280?}) /home/tom/src/gno/gnovm/tests/file.go:325 +0x44e main.gnoTestPkg({0xc000116500, 0x20}, {0x0?, 0x0, 0x1?}, {0xc00035b720, 0x1, 0xc000129af8?}, 0xc00034c8c0, 0xc0002948c0) /home/tom/src/gno/gnovm/cmd/gno/test.go:337 +0x876 main.execTest(0xc00034c8c0, {0xc00035b590, 0x1, 0x1}, 0xc000036220?) /home/tom/src/gno/gnovm/cmd/gno/test.go:208 +0xb67 main.newTestCmd.func1({0x0?, 0x0?}, {0xc00035b590?, 0xc00035f118?, 0x0?}) /home/tom/src/gno/gnovm/cmd/gno/test.go:51 +0x32 github.com/gnolang/gno/tm2/pkg/commands.(*Command).Run(0x5?, {0x1018768?, 0xc00003a130?}) /home/tom/src/gno/tm2/pkg/commands/command.go:233 +0x1ac github.com/gnolang/gno/tm2/pkg/commands.(*Command).Run(0xc00035ee70?, {0x1018768?, 0xc00003a130?}) /home/tom/src/gno/tm2/pkg/commands/command.go:237 +0x154 github.com/gnolang/gno/tm2/pkg/commands.(*Command).ParseAndRun(0x4059dc?, {0x1018768, 0xc00003a130}, {0xc0000361f0?, 0x401240?, 0x0?}) /home/tom/src/gno/tm2/pkg/commands/command.go:118 +0x4f main.main() /home/tom/src/gno/gnovm/cmd/gno/main.go:14 +0x75 exit status 2 ``` - using a go unit test: ``` $ go test ./gnovm/pkg/gnolang/ -v -run Amino === RUN TestAminoMustMarshalJSONPanics "20" --- FAIL: TestAminoMustMarshalJSONPanics (0.00s) panic: expected JSON object but got "20" [recovered] panic: expected JSON object but got "20" goroutine 6 [running]: testing.tRunner.func1.2({0xc15460, 0xc0002d2fc0}) /usr/lib/go/src/testing/testing.go:1526 +0x24e testing.tRunner.func1() /usr/lib/go/src/testing/testing.go:1529 +0x39f panic({0xc15460, 0xc0002d2fc0}) /usr/lib/go/src/runtime/panic.go:884 +0x213 github.com/gnolang/gno/tm2/pkg/amino.(*Codec).MustMarshalJSON(...) /home/tom/src/gno/tm2/pkg/amino/amino.go:818 github.com/gnolang/gno/tm2/pkg/amino.MustMarshalJSON({0xc59ec0?, 0xc0001c42d0?}) /home/tom/src/gno/tm2/pkg/amino/amino.go:140 +0x53 github.com/gnolang/gno/gnovm/pkg/gnolang.TestAminoMustMarshalJSONPanics(0x0?) /home/tom/src/gno/gnovm/pkg/gnolang/values_test.go:20 +0x134 testing.tRunner(0xc000300000, 0xcd8f40) /usr/lib/go/src/testing/testing.go:1576 +0x10b created by testing.(*T).Run /usr/lib/go/src/testing/testing.go:1629 +0x3ea FAIL github.com/gnolang/gno/gnovm/pkg/gnolang 0.008s FAIL ``` Additional notes: - when `// Realm:` instruction is present, it triggers a comparison between the store and the content of the instruction. - when the store content is serialized before the comparison, this panic happens in the amino code - this doesn't affect all `// Realm:` instruction, for instance `examples/gno.land/p/demo/avl/z_0_filetest.gno` is still working well  <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>

## Description This PR introduces several changes to the default JSON-RPC config of the Gno node: - allow all (`*`) origin requests by default. The reasoning behind this is that local development setups that require the RPC layer will have their requests rejected by the CORS policy, and will require a custom RPC config to be specified to the node. This is more of a convenience on the side of development, as production Gno RPC setups will have a concrete RPC configuration that is more limited - explicitly allow `OPTIONS` requests (preflight requests) in the default configuration - change the CORS library used in the project from [gnolang/cors](https://github.com/gnolang/cors) to [rs/cors](https://github.com/rs/cors). The [gnolang/cors](https://github.com/gnolang/cors) library is a fork of [rs/cors](https://github.com/rs/cors), with seemingly no functionality changes. Therefore, to stay up to date with the latest fixes and upstream changes, I've updated the library gno uses to the original one, which is actively maintained by the original authors ### How can I test this out? Essentially, you can run the local node with the default RPC params, and try to do an HTTP request from a frontend application: ```ts import { GnoJSONRPCProvider } from "@gnolang/gno-js-client"; const exampleMethod = async () => { // Local node as the endpoint const provider = new GnoJSONRPCProvider("http://127.0.0.1:26657"); const blockNumber: number = await provider.getBlockNumber(); console.log(blockNumber); }; exampleMethod() .then(() => { console.log("success"); }) .catch((e) => { console.error(e); }); ``` Example error: <img width="1192" alt="Screenshot 2023-09-13 at 12 27 22" src="https://github.com/gnolang/gno/assets/16712663/603b58c7-577d-4970-80eb-1c5984e0744b"> <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 - [ ] Added references to related issues and PRs - [x] 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>

See gnolang#1078 (review) Frankly, I'm always cautious when working with configuration files that can only be fully validated after merging and opening a new PR. I've consulted the documentation and also referenced popular codecov files from other repositories for guidance. Reference: https://docs.codecov.com/docs/codecovyml-reference

Based on tendermint/tendermint#3034

…1109) Bumps [golang.org/x/crypto](https://github.com/golang/crypto) from 0.12.0 to 0.13.0. <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/golang/crypto/commit/0d375be9b61cb69eb94173d0375a05e90875bbf6"><code>0d375be</code></a> go.mod: update golang.org/x dependencies</li> <li>See full diff in <a href="https://github.com/golang/crypto/compare/v0.12.0...v0.13.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=golang.org/x/crypto&package-manager=go_modules&previous-version=0.12.0&new-version=0.13.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Bumps [golang.org/x/net](https://github.com/golang/net) from 0.14.0 to 0.15.0. <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/golang/net/commit/2a0da8be5a758b33fa896384d689071e832b4aa2"><code>2a0da8b</code></a> go.mod: update golang.org/x dependencies</li> <li><a href="https://github.com/golang/net/commit/97384c11dd0db63357820b2cfcb44c40fbc3116a"><code>97384c1</code></a> quic: remove streams from the conn when done</li> <li><a href="https://github.com/golang/net/commit/03d5e623398478fa929c8ba4b8f15de74017d82a"><code>03d5e62</code></a> http2: remove unused ClientConn.tconnClosed</li> <li><a href="https://github.com/golang/net/commit/b82f062c4bc1abcfe993e3750d64c4bdd4a14f87"><code>b82f062</code></a> quic: include ignored frames in test log output</li> <li><a href="https://github.com/golang/net/commit/7374d342a2c3de79d7b96f3aacdb13498c3fc3b5"><code>7374d34</code></a> quic: don't block when closing read-only streams</li> <li><a href="https://github.com/golang/net/commit/b4d09be75101024ceed6b173b49a5630084174e6"><code>b4d09be</code></a> dns/dnsmessage: compress all names while appending to a buffer</li> <li><a href="https://github.com/golang/net/commit/8b010a5243b670aca8d2277a3c989d1b6a198a08"><code>8b010a5</code></a> quic: fix race condition in runAsync test helper</li> <li><a href="https://github.com/golang/net/commit/fe2abcb6e15f7a34d285220b437d421da4c76775"><code>fe2abcb</code></a> quic: validate stream limits in transport params</li> <li><a href="https://github.com/golang/net/commit/d1b0a97d84e0fa88851b5a065e23262afed10400"><code>d1b0a97</code></a> quic: avoid sending 1-RTT frames in initial/handshake packets</li> <li><a href="https://github.com/golang/net/commit/4332436fd1223b60e3127494d5ff771fba2c0adf"><code>4332436</code></a> quic: send more transport parameters</li> <li>Additional commits viewable in <a href="https://github.com/golang/net/compare/v0.14.0...v0.15.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=golang.org/x/net&package-manager=go_modules&previous-version=0.14.0&new-version=0.15.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

…#1126)" This reverts commit 6695e4e.

This eval realm is capable of evaluating 32-bit integer expressions as they would appear in Go. For example, you can use this package (and realm) to evaluate an expression like `"(32*32+4)-1"` when presented as a string. This could have several applications. This current "eval" realm is simply demonstrating it as a 32-bit integer calculator. I would like to also add floats, but it seems `strconv.ParseFloat` is not available yet. In the future I would like to use the int32 version of this package in the bytebeat realm (gnolang#840) which could then utilize this library to generate audio directly from string expressions, instead of programmed realms - which ultimately gets closer to an audio NFT platform where expressions are uploaded if they are parsed correctly. To test, you can just add the `eval` package and realm: ``` > gnokey maketx addpkg --pkgpath "gno.land/p/demo/math_eval_int32" \ --pkgdir "examples/gno.land/p/demo/math_eval/int32" \ --deposit 100000000ugnot --gas-fee 1000000ugnot \ --gas-wanted 2000000 --broadcast --chainid dev --remote localhost:26657 \ YOURKEY > gnokey maketx addpkg --pkgpath "gno.land/r/demo/math_eval" \ --pkgdir "examples/gno.land/r/demo/math_eval" \ --deposit 100000000ugnot --gas-fee 1000000ugnot \ --gas-wanted 2000000 --broadcast --chainid dev --remote localhost:26657 \ YOURKEY ``` Then open up to `localhost:8888/r/demo/math_eval` and try expressions in the URL query, like `localhost:8888/r/demo/math_eval:1+1`. ![image](https://github.com/gnolang/gno/assets/6550035/5b227a22-2ce5-4217-9b9b-99c967c9af86) <details><summary>Checklists...</summary> ## Contributors Checklist - [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 - [ ] Added new benchmarks to [generated graphs](https://gnoland.github.io/benchmarks), if any. More info [here](../.benchmarks/README.md). ## Maintainers Checklist - [ ] Checked that the author followed the guidelines in `CONTRIBUTING.md` - [ ] Checked the conventional-commit (especially PR title and verb, presence of `BREAKING CHANGE:` in the body) - [ ] Ensured that this PR is not a significant change or confirmed that the review/consideration process was appropriate for the change </details> --------- Co-authored-by: Manfred Touron <[email protected]>

See gnolang#1122 (comment) ```console ❯ cat codecov.yml | curl --data-binary @/dev/stdin https://codecov.io/validate Valid! { "codecov": { "require_ci_to_pass": false, ... ``` Signed-off-by: Manfred Touron <[email protected]>

This realm implements the `avl.Tree` as a user-addressable key-store. I wanted to have this realm to possibly use `gno.land` as a database where writes may cost gnots but reads are free because they can be performed through `Render` (related discussion: gnolang#947). As a nice additional feature it provides a UI for the database (through `gno.land`). Data can be set/removed if the caller is the same as the owner of the key-store (i.e. only owner's have write-access). For example: ```bash # Set key,value for user at YOURKEY (write-protected) gnokey maketx call --pkgpath "gno.land/r/demo/keystore" \ --func "Set" --args "hello" --args "world" \ --gas-fee "1000000ugnot" --gas-wanted "8000000" \ --broadcast --chainid dev --remote localhost:26657 YOURKEY ``` ```bash # Remove key for user at YOURKEY (write-protected) gnokey maketx call --pkgpath "gno.land/r/demo/keystore" \ --func "Remove" --args "hello" \ --gas-fee "1000000ugnot" --gas-wanted "8000000" \ --broadcast --chainid dev --remote localhost:26657 YOURKEY ``` ```bash # Get key gnokey maketx call --pkgpath "gno.land/r/demo/keystore" \ --func "Get" --args "hello" \ --gas-fee "1000000ugnot" --gas-wanted "8000000" \ --broadcast --chainid dev --remote localhost:26657 YOURKEY ``` All data is public and accessible as read-only from any user, as well as from gno.land. The main page lists all the available databases by owner (`/r/demo/keystore`): ![image](https://github.com/gnolang/gno/assets/6550035/3e21827c-0a22-47eb-bf42-53f6ee005a7e) Clicking on a user will show all the keys in their key-store (`/r/demo/keystore:USER`): ![image](https://github.com/gnolang/gno/assets/6550035/7d4b3d58-20ad-47fc-8e41-095e111f5f30) And the key values are accessible as well (`r/demo/keystore:USER:get:KEY`) ![image](https://github.com/gnolang/gno/assets/6550035/888a8ddf-6044-42d4-aed6-ffc3989def35) ## Contributors Checklist - [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](../.benchmarks/README.md). ## Maintainers Checklist - [ ] Checked that the author followed the guidelines in `CONTRIBUTING.md` - [ ] Checked the conventional-commit (especially PR title and verb, presence of `BREAKING CHANGE:` in the body) - [ ] Ensured that this PR is not a significant change or confirmed that the review/consideration process was appropriate for the change --------- Co-authored-by: Manfred Touron <[email protected]>

Proposed Fix for gnolang#1139. Given that we're only executing specific GitHub actions based on file changes, shared codecov flags might fluctuate between PRs due to variable testing targets. While this PR retains the recommended flag structure for monorepos, it aims to eliminate potential overlaps. However, overlap could still occur with Go versions like 1.19, 1.20, and so on. Personally, I suggest we retain this overlap for now to gauge its potential inconsistencies. If issues arise, appending the Go version as a suffix to the flag could be considered. Admittedly, I'm charting unfamiliar waters with this solution. Insights from those experienced with Codecov would be greatly appreciated. Signed-off-by: Manfred Touron <[email protected]>

Split coverages by component. Related to gnolang#1139 - [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). --------- Signed-off-by: Antonio Navarro Perez <[email protected]>

Split coverages by component. Check if it works better than prev iteration after doing some research: https://docs.codecov.com/docs/carryforward-flags Signed-off-by: Antonio Navarro Perez <[email protected]> - [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). Signed-off-by: Antonio Navarro Perez <[email protected]>

Fixing this: ![CleanShot 2023-09-18 at 16 29 59](https://github.com/gnolang/gno/assets/94029/f0139de3-f1d6-412d-9ba9-4f897bf4d2f3) Related with gnolang#1139 Signed-off-by: Manfred Touron <[email protected]>

moul · 2023-09-21T12:38:24Z

oops

moul and others added 30 commits July 30, 2023 15:36

chore: use self-hosted instance for benchmark (gnolang#1002)

59d9c53

chore(.github): fix broken link (gnolang#1005)

3a7c7aa

chore: more concise PR template (gnolang#998)

6c9a1c6

chore(cmd): print shortHelp if longHelp is empty (gnolang#1011)

1fc25f9

docs: fix outdated documentation in r/demo/boards (gnolang#1019)

ce2daf4

fix(gnovm): PrevRealm in _test files (gnolang#896)

e8016f3

Co-authored-by: Manfred Touron <[email protected]>

feat: add GNOROOT environment variables (gnolang#1014)

5d3be42

chore(deps): bump golang.org/x/crypto from 0.11.0 to 0.12.0 (gnolang#…

9045a8e

…1028) Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

docs: fix demo/boards/README, fix typos and change to a local node (g…

ffe18b0

…nolang#1034) Co-authored-by: Manfred Touron <[email protected]> Co-authored-by: Iuri Pereira <[email protected]>

feat(repl): support multi-line inputs and declarations (gnolang#978)

0beb958

feat: use PackageClauseOnly for parsing pkg name (gnolang#994)

b884a6e

docs: bootstrap a glossary, with p/ and r/ (gnolang#1043)

6e2a0a3

Signed-off-by: Manfred Touron <[email protected]>

chore(deps): bump golang.org/x/net from 0.11.0 to 0.14.0 (gnolang#1027)

0c3aca3

Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

feat: make gnovm wasm-friendly (gnolang#1012)

5a1d497

Co-authored-by: İlker G. Öztürk <[email protected]> Co-authored-by: İlker G. Öztürk <[email protected]>

test(gnovm): "*_filetest.gno" instructions (gnolang#1023)

902b7d9

feat(repl): Add support for new declarations. (gnolang#1044)

c6c601c

chore: use the Github version of the Boards realm (gnolang#1049)

7464b94

fix(pkg/commands): readPassword support for windows (gnolang#1089)

236c112

fixes gnolang#1060 (maybe). @ekleiner to verify :)

wolkykim and others added 21 commits September 6, 2023 13:34

test: refactor kvpair, add tests (gnolang#1057)

4586060

- simplify Less() and remove the unnecessary panic check - add comments - add tests

chore: update PHILOSOPHY.md (gnolang#1111)

3e6d139

Based on tendermint/tendermint#3034

Revert "chore(deps): Bump codecov/codecov-action from 3 to 4 (gnolang…

b0aebaa

…#1126)" This reverts commit 6695e4e.

chore: fix codecov config (h/t @the-howl) (gnolang#1137)

d5f14ff

See gnolang#1122 (comment) ```console ❯ cat codecov.yml | curl --data-binary @/dev/stdin https://codecov.io/validate Valid! { "codecov": { "require_ci_to_pass": false, ... ``` Signed-off-by: Manfred Touron <[email protected]>

chore: add empty test files for consistent coverage (gnolang#1147)

61f3ada

Fixing this: ![CleanShot 2023-09-18 at 16 29 59](https://github.com/gnolang/gno/assets/94029/f0139de3-f1d6-412d-9ba9-4f897bf4d2f3) Related with gnolang#1139 Signed-off-by: Manfred Touron <[email protected]>

Update codecov.yml

f438162

Update gh-pages.yml

8ed74e1

Update gh-pages.yml

0fccd20

Create test.gno

c7ac020

moul requested review from jaekwon and a team as code owners September 21, 2023 12:38

moul closed this Sep 21, 2023

github-actions bot assigned moul Sep 21, 2023

github-actions bot added 🧾 package/realm Tag used for new Realms or Packages. 📦 🤖 gnovm Issues or PRs gnovm related 📦 🌐 tendermint v2 Issues or PRs tm2 related 📦 ⛰️ gno.land Issues or PRs gno.land package related labels Sep 21, 2023

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Moul patch 1 #1159

Moul patch 1 #1159

moul commented Sep 21, 2023

moul commented Sep 21, 2023

Moul patch 1 #1159

Moul patch 1 #1159

Conversation

moul commented Sep 21, 2023

moul commented Sep 21, 2023