#Dagger cloud issues?
1 messages · Page 1 of 1 (latest)
Hey there! Can you share which cli/sdk version you're using?
Maybe related to today's engine release? 🤔
That's my guess as well
@tired brook are you still around to check if cloud cache works with v0.8.8? 🙏
I'm AFK currently
Yes I'll test
Apologies, it was due to the release. We were pinning 0.8.1 in our repo, updating to 0.8.8 appears to fix the issue.
Glad to hear it! I wasn't aware of any breaking change, so we'll make sure to follow up on that
Yes, same here. We didn't deploy any changes to the caching service today. We'll look into this tomorrow
Hmmm, ok. Spoke too soon. Seems to work with caches turned off (in dagger cloud), but fail with them turned on.
Not an urgent issue for us, we can just switch off the caches for now.
Ah ok. I'm trying to reproduce this on my end
RE: Volumes are automatically created when they are declared in your code. You can manage them by disabling or deleting them. I don't seem to be able (i.e. there is no button) to delete the cache volumes via the web UI
(could just be a corrupted cache volume?)
Will try giving them new names and see if it fixes it
I have reproduced the issue!
Yeah, renaming the caches didn't fix it for me :(. Looks like a real issue.
Thanks for trying 🙂 Now that I have a repro I'm digging in on my end!
@gilded torrent can you try pinning your SDK and CLI v 0.8.7 please?
to check if that fixes it?
Pinning the CLI to 0.8.7 and the code to 0.8.7 works with the cloud cache enabled.
(side question: there is no "delete" button in the UI to remove caches? I now have several unused ones - due to the testing here!). How do you delete them?
that's coming next week 🙏