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

Bug recently introduced makes gno-js's provider.evaluateExpression timeout #2420

Open
RezaRahemtola opened this issue Jun 23, 2024 · 3 comments
Labels
🐞 bug Something isn't working

Comments

@RezaRahemtola
Copy link
Member

RezaRahemtola commented Jun 23, 2024

Bug recently introduced makes gno-js's provider.evaluateExpression timeout

Description

I'm trying to build a Medium-like app using Gno.
I started a bare-minimum contract and frontend (with gno-js and Adena), but when using provider.evaluateExpression it timeouts.
But the issue isn't with the websocket connexion, as calling provider.getFunctionSignatures or provider.getFileContent works fine.

I recently changed my computer (Fedora -> Mac) so my Gno installation is fresh, and I discovered that it was working correctly on my Fedora (that was installed on commit 93299802, which is at the time of writing 56 commits behind master).
It also works correctly on @agherasie's Mac, where he installed Gno at the same time as I did on my Fedora.
After doing a git checkout and make install on this commit, it works.

Looks like something broke in the meantime, I don't really know where, probably in gnodev ?
Or maybe in gno-js that doesn't support latest versions of gnodev ?
, exact commit in the comment below

Your environment

  • Mac M3
  • master, 31a5f2ea

Steps to reproduce

  • Use evaluateExpression from gno-js (my usage: provider.evaluateExpression("gno.land/r/demo/gnovox", "GetBlogs()")
  • Run gnodev locally to serve the realm called (my usage: gnodev ./contract/r/gnovox)
  • Notice that the evaluateExpression return an error: Request timed out while other methods work correctly

Expected behaviour

It should returns a result, in my case (nil []string)

Actual behaviour

Throws an error: Request timed out

Logs

Screenshot 2024-06-23 at 19 58 55
@RezaRahemtola
Copy link
Member Author

I'll dig this evening if I have some time to try to find the commit where this broke.

@RezaRahemtola
Copy link
Member Author

RezaRahemtola commented Jun 24, 2024

This is the commit where it broke: fix: (gnovm) star expr assign for

It was working fine in the commit just before: feat: refactor govdao structure and examples

PS: When testing locally these particular commits, you won't be able to launch gnodev because of the wrong package name introduced here: feat: add r/demo/bar20 example and fixed here fix(examples): update /r/demo/bar20/gno.mod
So either remove the bar20 or edit the gno.mod like the fix to be able to run gnodev

@zivkovicmilos
Copy link
Member

Hey @RezaRahemtola,

Thank you for opening up the issue 🙏

I'll look into it, and let you know what I find

@zivkovicmilos zivkovicmilos self-assigned this Jun 24, 2024
@zivkovicmilos zivkovicmilos added the investigating This behavior is still being tested out label Jun 24, 2024
@Kouteki Kouteki added the 🐞 bug Something isn't working label Jun 24, 2024
@Kouteki Kouteki moved this from Triage to In Progress in 🧙‍♂️gno.land core team Jun 24, 2024
@linear linear bot removed 🐞 bug Something isn't working investigating This behavior is still being tested out labels Sep 11, 2024
@zivkovicmilos zivkovicmilos removed their assignment Oct 4, 2024
@Kouteki Kouteki added the 🐞 bug Something isn't working label Nov 17, 2024
@Kouteki Kouteki moved this from In Progress to Backlog in 🧙‍♂️gno.land core team Nov 17, 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
Projects
Status: Backlog
Development

No branches or pull requests

3 participants