Anything that can be done to avoid this issue in the interim? Need to make
a call soon if we’re going to use Glitch this semester & this might be a
dealbreaker if we can’t reliably work around it.
I ran rm .glitch-assets; refresh from terminal, still getting the “No Assets Yet” message. Am I missing something?
I’m also getting a blank editor view when clicking the assets folder on occasion. Clicking back out to another file and back in seems to solve it. Is this bug on your radar?
@creativecomputing,
we’re working on debugging the root of what caused this issue in the first place. Can you give us more information about what you uploaded to the assets? Is it possible that you uploaded over 100mb or so of files?
I don’t think .gitignore is related to this issue. I do have .gitignore’s in my projects and they work fine. To be honest we still didn’t figure out why you had the issue In general using git to checkout a working version of .glitch-assets and then running refresh should get you back to a working state, but if it happens again to you, please let us know!
Strange - I’m able to reliably reproduce it here by adding a gitignore back in. Is there something specific to this project that’s broken? If you have a look now, you can see it’s having the same issue…
I guess I’m still confused - the issue is related to gitignore or something else?
Again, would be helpful to know so that we can avoid confusion here – rolling things back via a git checkout is going to be non-optimal w/ beginning students.
Sorry, it was me being silly; yes, there is a bug in our code that is triggered by .gitignore, but I’ve identified it. I’ll let you know when the fix is released so you can check if the behavior is now correct
Just to confirm - these assets will persist on your CDN indefinitely? Or are they wiped periodically? In other words - can I reference those URLs & expect them to be valid through June?
We don’t currently remove or expire any of the assets you upload. Of course for the future we can only guarantee that the assets listed in the assets file won’t be deleted
This happened because you added .glitch-assets to your .gitignore today. It’s a bug that this makes them disappear, but you really don’t want to ignore that file. The bug should be fixed in a few minutes.
Hi Tim - We didn’t make any edits to .gitignore until the files disappeared (.glitch-assets has been in there for some time… at least since the bug was fixed the last time around). I did remove .glitch-assets once the bug reappeared.
I can just keep the .glitch-assets in my repo - no problem - but is it going to be possible to restore the existing assets to the project?
Ah, I see. I was looking at it backwards. I restored the assets. I also added a .env file to your project for now - we have an editor bug that doesn’t like projects without that file. I should have that fixed this morning, so you can delete the file tomorrow if you like.
You should be fine using .gitignore. I wouldn’t add .glitch-assets to it, because that’s a file you would like to keep the history of. I just misunderstood what caused your problem yesterday - I thought it was adding .glitch-assets to .gitignore that had messed things up. .lesshst is exactly the kind of thing you want in .gitignore. I fixed the .env issue too, so you can delete that now.
We’re running into this bug with this project (https://glitch.com/~ultra-rutabaga) two of the earlier uploaded assets aren’t listed, but are served up just fine when showing the webpage.