barren lark
Open the network tab when you initiate a cache prune in the new UI and you'll see a failed GET request to https://api.dagger.cloud//magicache/prune?async=true .
I'm not sure of the impact, but the // doesn't look right.
After initiating the prune, waiting a few minutes, hard-killing my local dagger engine, and starting it back up, I'm still seeing about 30s engine start time spent on downloading cache volumes - so I'm not sure if it was actually pruned.
spark acorn
🙋♂️ @noble loom @weak jungle @maiden shoal
maiden shoal
checkng now @barren lark
yes, seems like something changed matt which broke the link somehow. Fixing that really quick 🙏
maiden shoal
@barren lark could you try again please? The fix should be already in production
barren lark
thanks! just tested - no more failed GET request. but, there isn't a toast after submission in the modal and the modal stays open.
maiden shoal
thanks! just tested - no more failed GET request. but, there isn't a toast after...
Strange. I wasn't seeing the same thing. Will check it out first time tomorrow
maiden shoal
@barren lark we've identified the issue and we're fixing the FE glitches 🙏
barren lark
Heads up, attempted to prune just now and I see:
Failed to load ‘https://api.dagger.cloudmagicache/prune?async=true’. A ServiceWorker passed a promise to FetchEvent.respondWith() that rejected with ‘TypeError: NetworkError when attempting to fetch resource.’. app-worker.js:47:9
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://api.dagger.cloudmagicache/prune?async=true. (Reason: CORS request did not succeed). Status code: (null).
fixed Matt. Sorry again for the trouble, we had a weekly merge train which undid the fix that I applied a few days ago 🙏