jonaro00

We have continued investigating this, and we made some improvements in 0.39.0 that we hope help reduce the frequency of this bug.

The probability of getting this error seems to be reduced since 0.39.0

Improvements in recent releases has made this error very rare now. We are continuing work on getting rid of it completely.

shuttle-opendal (#1617) and other libraries allow you to use your own S3 etc, but keeping this issue open since it tracks Shuttle-native blob storage.

S3 buckets etc that we provision, like we do for AWS RDS currently.

The Shuttle team will work on this in due time after upcoming changes to the proxy.

I think the main challenge/blocker is that the Shuttle runtime wraps the app with a `tonic` server, and using that without tokio looks cumbersome at best. Based on this, I...

Since 0.12, you can simply do `cargo watch -x 'shuttle run'`.

@jmwill86 Do you envision encapsulating `cargo watch` or implementing file watching "from scratch"? I would not consider it worth putting effort into mimicking/wrapping `cargo watch` since it is already a...

To clarify my stance on this: IMO if a user wants hot reloads they can install `cargo-watch` (or `watchexec`) separately, so that it can be used as the general purpose...