Code Monkey home page Code Monkey logo

Comments (9)

 avatar commented on September 26, 2024 1

Thanks!! Unregistering has actually helped. Now extload works and for i=0 to 50:draw random*500,random*500:next works correctly, which means that atto is in the latest version now.

from atto.

James-Livesey avatar James-Livesey commented on September 26, 2024

Happy to help! Seems like you're having some strange issues... Using the broadcasting extension is working for me, though.

From what I hear with the specific issue you're facing, you might want to try emptying your browser cache and hard reloading. The way to do this varies between browsers — on Chrome, open DevTools (press Ctrl + Shift + I) and then go back to atto and right-click the refresh button in Chrome, before selecting empty cache and hard reload.

If you're able to upload any screenshots of the issues you're facing, that might help so I can see what's going on. If you could provide me with your OS and browser versions and any JavaScript error logs that are shown in DevTools, that would also be appreciated!

You might also want to refer to the example programs in the atto documentation for the broadcasting extension as they are known to be working fine.

Just to note that the atto broadcasting services are provided by a web server that currently goes to sleep after a while and spins up on-demand, and so an initial call to broadcasting.host may take up to a minute to finish in some cases — though I don't think this relates to the issues that you're having.

from atto.

 avatar commented on September 26, 2024

Thanks! The hard reset actually fixed it. I don't know why it broke though, but maybe it won't occure anymore - I don't remember extload working before.

You might also want to refer to the example programs in the atto documentation for the broadcasting extension as they are known to be working fine.

The examples were also breaking immidetaly after seeing "extload", "broadcast" or etc.

from atto.

James-Livesey avatar James-Livesey commented on September 26, 2024

No worries — glad it's working for you now! The browser cache can be a bit of a pain sometimes... If you come across this problem again, please do feel free to let me know!

from atto.

 avatar commented on September 26, 2024

Yep, for some reason it keeps breaking and I should do a reset everytime. This is the only thing I know right now.

from atto.

 avatar commented on September 26, 2024

I tried testing it multiple times, this is how DevTools outputs differ:

After a normal reset (extload doesn't work in that case):
atto devtools 1
Cache reset and hard reset (the red error message seems to be the main thing):
atto devtools 2
Should I reopen the issue?

from atto.

James-Livesey avatar James-Livesey commented on September 26, 2024

The errors and warnings I can see in DevTools are what I get too, so they shouldn't be related to the issue you're having. If you can take any screenshots of your atto code/syntax highlighting problems that you've seen and send them over, then I can reopen the issue and might be able to try and work out a solution to things that are going wrong (along with what version of Chrome you have/the OS you're running)!

from atto.

 avatar commented on September 26, 2024

Version: latest, 112.0.5615.121 (Official build), (64 bit)
Computer:

  • Intel(R) Core(TM) i5-8400 CPU @ 2.80GHz 2.81 GHz
  • 16,0 GB RAM (15,9 GB free)
  • 64 bit

After a normal refresh:
atto devtools 5
After clearing cache and hard reset:
atto devtools 6

from atto.

James-Livesey avatar James-Livesey commented on September 26, 2024

Okay, I reckon that it might be something to do with the service worker that's preferring an old version of atto from when attoX didn't exist. Any invalid command is errored with Unexpected end of line as atto expects a variable assignment expression here (eg. in this case extload=5), as can be seen in the example below:

image

I've invalidated the service worker's version so it should hopefully be forced to redownload everything. If you do a hard refresh at your end, it should now hopefully be fine from here on! If not, then in DevTools, go to the Application tab at the top, then Service Workers section, then press Unregister — that should do the trick (service workers can be weird sometimes).

I might at some point try and investigate that Failed to execute 'addAll' on 'Cache': Request failed issue and maybe also make it clearer when a command doesn't exist in atto...

from atto.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.