8cabe37818
Some checks failed
build-and-release / build (cron) (push) Successful in 4m47s
build-and-release / build (developers) (push) Successful in 8m43s
build-and-release / build (companies) (push) Successful in 9m9s
build-and-release / build (catering-services) (push) Successful in 9m11s
build-and-release / build (customers) (push) Successful in 9m16s
build-and-release / build (employees) (push) Successful in 9m32s
build-and-release / build (gateway) (push) Successful in 3m3s
build-and-release / build (fitness-trainers) (push) Successful in 8m35s
build-and-release / build (jobs) (push) Successful in 4m33s
build-and-release / build (graphic-designers) (push) Successful in 8m21s
build-and-release / build (leads) (push) Successful in 8m29s
build-and-release / build (job-seekers) (push) Successful in 9m47s
build-and-release / build (makeup-artists) (push) Successful in 8m5s
build-and-release / build (payments) (push) Successful in 8m33s
build-and-release / build (photographers) (push) Successful in 8m44s
build-and-release / build (social-media-managers) (push) Successful in 8m11s
build-and-release / build (ugc-content-creators) (push) Successful in 7m1s
build-and-release / build (tutors) (push) Successful in 8m37s
build-and-release / build (video-editors) (push) Has been cancelled
build-and-release / build (users) (push) Has been cancelled
tracing::error!("...: {}", e) on an anyhow::Error only prints the outermost
.context() message ("B2 upload failed") — the actual root cause (auth
failure, DNS, timeout, bad bucket, etc.) from the AWS SDK is swallowed.
Switching to {:?} prints the full chain so the real failure is visible in
logs instead of a message that just repeats itself.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
|
||
|---|---|---|
| .. | ||
| src | ||
| Cargo.toml | ||