Updates dependencies for possible 1.1 release #847
No reviewers
Labels
No labels
action
check-aws
action
discussion-needed
action
for-external-contributors
action
for-newcomers
action
more-info-needed
action
need-funding
action
triage-required
kind
correctness
kind
ideas
kind
improvement
kind
performance
kind
testing
kind
usability
kind
wrong-behavior
prio
critical
prio
low
scope
admin-api
scope
background-healing
scope
build
scope
documentation
scope
k8s
scope
layout
scope
metadata
scope
ops
scope
rpc
scope
s3-api
scope
security
scope
telemetry
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Deuxfleurs/garage#847
Loading…
Reference in a new issue
No description provided.
Delete branch "update-dependencies-1.1"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Just a simple dependency file updates, with a warning fix.
efa755a79f
to4d8df6856f
@ -397,3 +398,1 @@
.date()
.succ_opt()
.expect("no next day")
.date_naive()
By removing
.succ_opt()
, you are changing the meaning of this function! It is supposed to return the date of the day following the day of the given timestamp, not just the day of the timestamp.Ok, so this escalated quickly. We are deadlocked, because:
The updated
aws-sdk-config
crate requires rustc >= 1.77.0 and we are building with 1.73.0The updates to the flake.nix file that import a newer version of cargo2nix and a new compiler cause a build error of the kind
error: executing shell '/bin/bash': Argument list too long
. I'm not sure where this comes from, but until we are able to fix it, we cannot update the compiler version to 1.80 as I tried doing.I think trying to update the Nix dependencies (and the Rust toolchain) at the same time we updated Cargo dependencies was a bad move. Updating the toolchain is always hard, but we don't need to do it for the moment.
My suggestion is to:
aws-sdk-config
if it prevents building with the current 1.73 toolchain, it is not a critical dependency, it's not even part of Garage itself, it's only used for testing7abf1f5833
tof3589fee77
Should fix #849
We are leaving the following for future PRs:
move back to cargo2nix upstream (this might break stuff)
update nixpkgs in flake.nix
update rust-overlay in flake.nix and update rust to 1.80 in nix/compile.nix (this might break stuff)
maybe: remove the obsolete clippy driver (it doesn't work)
eventually, allow upgrading the aws-* depenencies
Each of these things should be done independently in different PRs to avoid breaking stuff, we can probably do these steps one after another and keep a working CI build at every step.
5432818ad1
tof3589fee77
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.