-
Notifications
You must be signed in to change notification settings - Fork 49
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: Not able to interpret any code in playground #127
Comments
I'm seeing the same issue with the online web browser demo version. |
Thanks for reporting! The issue with the online playground is different from that reported above. It was already fixed and you should be able to enjoy Aquascope online again. As for the local playground instance, there appears to be a misconfiguration in the repo. I'm currently traveling but will hopefully manage a fix in the next few days. |
Hey there @gavinleroy, were you able to find some bandwidth for looking into the local playground issue 😅 |
Yes, you need to make sure that the environment variable |
Hey @gavinleroy, thank you so much for this. But even after this it doesn't seem to work 😅 What I did was,
Am I missing something here? |
@Palanikannan1437 🤦 argh, my apologies. I inserted a typo into the Makefile, now that should be fixed and I've confirmed that others have been able to run the local playground as described. Please do let me know if that finally fixes the issue. |
Hi @gavinleroy |
Hey folks, thank you for building such a cool tool, this tool has greatly helped me in learning Rust, absolutely love it.
Description
I wanted to set it up locally and followed all the instructions as mentioned in "from source" section and was able to do it successfully without any errors.
Stderr
sectionI tried to run
cargo miri setup
and triedcargo make install-mdbook
andcargo make playground
post that but it doesn't seem to work even then, I'm getting the same output in theStderr
when trying to interpret any code. Could you please point me towards a potential fix? ThanksThe text was updated successfully, but these errors were encountered: