Closed schollz closed 9 months ago
Yes, expected behaviour. https://github.com/gnolang/gno/pull/763 (tl;dr: everything with a gno.mod in examples gets automatically loaded)
Because realm/pkg upgrades are still up for discussion (#694), current behaviour is to reject any addpkg to an existing path. Suggestion is to change the name to something else. (For my own pet-project, I configured an auto-deployer that watches for fs changes, and publishes the realm with a random numerical suffix, ie gno.land/r/demo/chess_1234
)
Thanks, changing the name works! Also love the auto-deployer, I have something similar in a makefile but yours is much more clever.
Description
I've been out for a few weeks and coming back there is a new change that I wasn't expecting. When I am working on a realm (currently working on
/r/demo/art/haiku
), I am finding thatgnoland
is automatically creating a realm before making a transaction.Reproduce
Create a realm folder (I'm using https://github.com/schollz/gno/tree/realm/haiku with the haiku realm added) and start gnoland. I use the following script to spin-up a fresh gnoland locally:
Now I can query the realm before creating a transaction to add it:
Expected behaviour
Previously, the behavior was that it would produce a response correctly saying it could not find realm:
Actual behaviour
Now it actually prints out some HTML from a different realm:
Problem
The problem is that I can't seem to add a realm anymore because it "already exists" though it has not actually been added:
Perhaps this is all expected behavior now? If so, I'm not sure how to add my realm in when starting gnoland.