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

Detect bad gno.mod configuration from CI #927

Closed
moul opened this issue Jun 22, 2023 · 2 comments
Closed

Detect bad gno.mod configuration from CI #927

moul opened this issue Jun 22, 2023 · 2 comments
Labels
🐞 bug Something isn't working 🗺️good first issue🗺️ Ideal for newcomer contributors help wanted Want to contribute? We recommend these issues.

Comments

@moul
Copy link
Member

moul commented Jun 22, 2023

PR #882 introduced a bug (#882) that went unnoticed until after it was merged. It was fixed with PR #921.

The issue arises from the current cycle detection tool, which is only tested with ./gno.land, when relevant go files are updated, not when the ./examples folder is modified in a pull request.

To address this, we should update the examples.yml workflow to include cycle checks. In the long term, it would be ideal to develop a gno lint tool (#850) to thoroughly check for cycles in the entire example folder.

@moul moul added 🗺️good first issue🗺️ Ideal for newcomer contributors help wanted 🐞 bug Something isn't working labels Jun 22, 2023
@moul
Copy link
Member Author

moul commented Jun 22, 2023

cc @harry-hov, @thehowl

@moul moul mentioned this issue Jul 20, 2023
15 tasks
moul added a commit that referenced this issue Jul 31, 2023
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 #850
Addresses #927
Related with
#965 (comment)

Signed-off-by: Manfred Touron <94029+moul@users.noreply.github.com>
Co-authored-by: Miloš Živković <milos@zmilos.com>
Doozers pushed a commit to Doozers/gno that referenced this issue Aug 31, 2023
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 <94029+moul@users.noreply.github.com>
Co-authored-by: Miloš Živković <milos@zmilos.com>
@moul moul moved this to 🏆 Needed for Launch in 🚀 The Launch [DEPRECATED] Sep 5, 2023
@moul moul modified the milestone: 🚀 main.gno.land Sep 6, 2023
@harry-hov harry-hov self-assigned this Dec 14, 2023
@moul moul moved this to Todo in 💪 Bounties & Worx Dec 22, 2023
@Kouteki Kouteki added help wanted Want to contribute? We recommend these issues. and removed help wanted labels Oct 2, 2024
@thehowl
Copy link
Member

thehowl commented Oct 4, 2024

Cycles are now detected, because we test gno.land also for simple changes to examples/. gno mod tidy is performed in general, and that should detect bad imports. So, done.

@thehowl thehowl closed this as completed Oct 4, 2024
@github-project-automation github-project-automation bot moved this from Todo to Done in 💪 Bounties & Worx Oct 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐞 bug Something isn't working 🗺️good first issue🗺️ Ideal for newcomer contributors help wanted Want to contribute? We recommend these issues.
Projects
Status: Done
Status: 🚀 Needed for Launch
Development

No branches or pull requests

4 participants