search

brownplt / code.pyret.org

Website for serving Pyret to folks.
Other
24 stars 44 forks source link

shared-grive caching issue #227

Open sorawee opened 7 years ago

sorawee commented 7 years ago

Say, I have two Pyret code open: a.arr and b.arr where a.arr imports b.arr. I run a.arr and find that b.arr is wrong, so I edit and republish b.arr. When I run a.arr again, it still runs the old b.arr. I need to refresh the page (start Pyret again) of a.arr to update to the latest version of b.arr.

This will really affect students who have implementations and tests on two tabs.

I understand the need of caching, but can it be less aggressive. I.e., look at the timestamp of shared code. If it's newer than what gets run before, then clear the cache and reload the file.

jpolitz commented 7 years ago

Can't students use "my-gdrive" for this use case? It should do the right file-based caching for this.

sorawee commented 7 years ago

Yup, they can, and this would solve their problem indeed :)

But I think this is still a valid issue that would be nice to be fixed.