Web: bump fula_client to 0.6.12 (large-upload v7-migration fix)#54
Merged
Conversation
…ync web/pkg fula_client 0.6.12 (fula-api #44) fixes large-file uploads failing on GC-damaged buckets: the v1->v7 forest migration now tolerates a 410/Gone on its backup copy_object (the gc'd v1 index blob) and rebuilds v7 from the in-memory forest, instead of aborting and failing the upload. All other copy errors still defer. No FxFiles code change -- the SDK API is unchanged. Just the version pin + the matching wasm bundle. - pubspec.yaml / pubspec.lock: fula_client ^0.6.12. - web/pkg/: re-synced via tools/sync-wasm-pkg.ps1 to the v0.6.12 flutter-wasm-pkg.zip (VERSION 0.6.12) so the deploy gate passes. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps
fula_clientto 0.6.12 (functionland/fula-api#44) + re-syncsweb/pkg.What 0.6.12 fixes
Large-file uploads were failing on GC-damaged buckets. A large file pushes the forest past the v7 sharding threshold, triggering the one-time v1→v7 migration, whose first step is a server-side
copy_objectof the v1 index — which 410s because that index blob's backing CID was garbage-collected. 0.6.12 treats a410/Gonebackup-copy as "source already gone, nothing to back up", skips the backup, and rebuilds v7 from the in-memory forest (every other copy error still defers). Once migrated, the bucket is healthy v7 and never hits this path again.Changes
pubspec.yaml/pubspec.lock:fula_client ^0.6.12.web/pkg/: re-synced viatools/sync-wasm-pkg.ps1to the v0.6.12flutter-wasm-pkg.zip(VERSION 0.6.12) so the committed wasm matches the pin and the deploy gate passes.Validation
flutter build web -t lib/main_web.dartgreen against 0.6.12.After deploy
Retry the previously-failing large upload on
videos-v8at files.fx.land/app/. It should now (a) succeed (the v1→v7 migration completes past the gc'd backup) and (b) show the advancing upload % (the 0.6.11 progress feature, which couldn't be seen before because the upload died at finalize). That single retry is the real-server E2E for both the migration fix and the progress feature.🤖 Generated with Claude Code