You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This has been already reported in Discord over here and here.
After the introduction of cargo-shuttle 0.11.2, with the idle-to-sleep changes, I've seen that all my projects that have a dependency of shuttle-static-folder will crash when they try to recover from sleep.
The error I'm getting is this one: 2023-03-06T16:48:13.792356279Z ERROR {error="Run error: Custom error: failed to provision shuttle_static_folder :: StaticFolder"} shuttle_deployer::deployment::run: service startup encountered an error.
For now, the only alternative is to redeploy everything with --idle-minutes 0 flag.
Version
v0.11.2
Which operating systems are you seeing the problem on?
Linux
Which CPU architectures are you seeing the problem on?
x86_64
Relevant log output
No response
Duplicate declaration
I have searched the issues and there are none like this.
The text was updated successfully, but these errors were encountered:
This was fixed in #692 and the fix has been released. An announcement will also be posted in Discord soon.
For your deployer to use the fixed version you'll need to first run cargo shuttle project new and then cargo shuttle project rm. Then you need to bump your dependency on shuttle-static-folder to 0.11.3, before re-deploying. You do not need to upgrade your cargo-shuttle cli or other dependencies.
What happened?
This has been already reported in Discord over here and here.
After the introduction of cargo-shuttle 0.11.2, with the idle-to-sleep changes, I've seen that all my projects that have a dependency of
shuttle-static-folder
will crash when they try to recover from sleep.The error I'm getting is this one:
2023-03-06T16:48:13.792356279Z ERROR {error="Run error: Custom error: failed to provision shuttle_static_folder :: StaticFolder"} shuttle_deployer::deployment::run: service startup encountered an error
.For now, the only alternative is to redeploy everything with
--idle-minutes 0
flag.Version
v0.11.2
Which operating systems are you seeing the problem on?
Linux
Which CPU architectures are you seeing the problem on?
x86_64
Relevant log output
No response
Duplicate declaration
The text was updated successfully, but these errors were encountered: