https://linen.dev logo
Upgrade to Shuttle 0.11
# help
b
Hi guys, Upgraded the first of my projects to Shuttle 0.11. I followed the instructions in today's release notes. Local run works without errors, the site does seem to be live without errors, https://apodviewer.shuttleapp.rs/ but the messages output after a cargo shuttle deploy lead one to believe it hasn't worked. I'm going to try another of my sites.
o
If it helps, I have the same issue with slightly different symptoms
Copy code
bash
❯ cargo shuttle deploy

2023-02-27T21:10:39.038945958Z  INFO Entering queued state
2023-02-27T21:10:39.038975762Z TRACE shuttle_deployer::deployment::queue: getting a build slot
2023-02-27T21:10:39.039605156Z TRACE {uri="http://gateway:8001/stats/load"} shuttle_deployer::deployment::gateway_client: calling gateway
2023-02-27T21:10:39.040216364Z DEBUG hyper::client::connect::http: connecting to 10.99.48.65:8001
2023-02-27T21:10:39.043909864Z DEBUG hyper::client::connect::http: connected to 10.99.48.65:8001
2023-02-27T21:10:39.044457399Z DEBUG hyper::client::pool: pooling idle connection for ("http", gateway:8001)
2023-02-27T21:10:39.044485353Z TRACE {response="Response { status: 200, version: HTTP/1.1, headers: {\"content-type\": \"application/json\", \"content-length\": \"38\", \"date\": \"Tue, 28 Feb 2023 05:10:38 GMT\"}, body: Body(Streaming) }"} shuttle_deployer::deployment::gateway_client: Load response

2023-02-27T21:10:39.044853079Z  INFO Entering building state
2023-02-27T21:10:39.513589884Z  INFO     Updating `shuttle-crates-io-mirror` index
2023-02-27T21:11:47.620426838Z  INFO warning: Patch `shuttle-aws-rds v0.11.0 (/usr/src/shuttle/resources/aws-rds)` was not used in the crate graph.
2023-02-27T21:11:47.620449020Z  INFO Patch `shuttle-persist v0.11.0 (/usr/src/shuttle/resources/persist)` was not used in the crate graph.
2023-02-27T21:11:47.620684131Z  INFO Patch `shuttle-shared-db v0.11.0 (/usr/src/shuttle/resources/shared-db)` was not used in the crate graph.
2023-02-27T21:11:47.620849733Z  INFO Patch `shuttle-static-folder v0.11.0 (/usr/src/shuttle/resources/static-folder)` was not used in the crate graph.
2023-02-27T21:11:47.621063976Z  INFO Check that the patched package version and available features are compatible
2023-02-27T21:11:47.621237853Z  INFO with the dependency requirements. If the patch has a different version from
2023-02-27T21:11:47.621409531Z  INFO what is locked in the Cargo.lock file, run `cargo update` to use the new
2023-02-27T21:11:47.621586160Z  INFO version. This may also occur with an optional dependency that is not enabled.
Deployment has not entered the running state
I guess I spoke too soon, I just kept hammering the command a few times and it went through
b
Just did another of my sites, same issue as initially reported, but the site is live. https://crusty-rustacean-dev.shuttleapp.rs. Noticed a typo in the footer that I'll correct later 🙂
Same thing as me...messages lead you to believe it's not running, but it seems to be running.
k
Thanks! Yeah, we're working on this, there is an issue with the deployment logs currently.
b
I’ve updated all my sites now, everything seems to be up and running. The very last site I updated gave more normal log messages.
One thing I've noticed with an API project I updated, instead of a 200 OK when I hit the health_check route, it gives me back a 301 Moved Permanently. I find this a little confusing. As nothing has changed in my route. Code is here: https://github.com/sentinel1909/crusty-rustacean-api
k
That is weird... Do you have a URL to that endpoint (if it's live)?
b
Before the 0.11 upgrade it returned a 200 OK
k
Ah, you're curling http, it should be https
b
OMG
😦
Le sigh...carry on everyone, nothing to see here. Everything is working great 🙂