feat: bundle mode with atomic deploys, seed assets, and version-gated caching#482
Open
divyanshub024 wants to merge 8 commits into
Open
feat: bundle mode with atomic deploys, seed assets, and version-gated caching#482divyanshub024 wants to merge 8 commits into
divyanshub024 wants to merge 8 commits into
Conversation
Contributor
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
📝 WalkthroughWalkthroughAdds opt-in bundle mode to ChangesStac package bundle mode
stac_cli atomic bundle deployment
Estimated code review effort: 4 (Complex) | ~60 minutes Sequence Diagram(s)sequenceDiagram
participant App
participant StacBundleService
participant StacBundleStore
participant BundlesAPI
App->>StacBundleService: request bundle synchronization
StacBundleService->>StacBundleStore: hydrate cached bundle
StacBundleService->>BundlesAPI: conditional GET /bundles
BundlesAPI-->>StacBundleService: bundle or not-modified response
StacBundleService->>StacBundleStore: persist updated bundle
StacBundleService-->>App: serve screen/theme JSON
sequenceDiagram
participant CLI
participant DeployService
participant BundlesAPI
participant SeedFilesystem
CLI->>DeployService: deploy bundle
DeployService->>BundlesAPI: POST /bundles
BundlesAPI-->>DeployService: versioned bundle response
DeployService->>SeedFilesystem: write assets/stac_bundle.json
Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
- StacBundle/StacBundleConfig models; SharedPreferences bundle store with schema-version guard - StacBundleService: conditional sync (ETag/since), seed-asset hydration (highest version wins), updates stream, offline fallback - StacBundleUpdater: sync on app-resume + optional foreground polling - StacCloud serves screens/themes from the bundle when enabled (opt-in; falls through to legacy per-artifact fetch) - CLI: single atomic POST /bundles with checksum + payload size log, seed asset emission with pubspec warning, --legacy fallback flag; build now cleans stale .build outputs
divyanshub024
force-pushed
the
feat/bundle-deploy
branch
from
July 3, 2026 12:19
11bd5a3 to
3b58309
Compare
divyanshub024
changed the title
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 2
🧹 Nitpick comments (2)
packages/stac/lib/src/services/stac_bundle_service.dart (2)
104-167: 🩺 Stability & Availability | 🔵 TrivialNo backoff on repeated sync failures.
On non-2xx/non-304/204 statuses or network errors,
sync()simply returns the stale bundle without recording failure state. Combined withStacBundleUpdater's fixed polling interval and resume-triggered checks, a persistently failing/rate-limiting server will be hit at the same fixed cadence indefinitely. Consider adding lightweight backoff (e.g., skip the next N scheduled checks after consecutive failures) for resilience during outages.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@packages/stac/lib/src/services/stac_bundle_service.dart` around lines 104 - 167, Add lightweight failure backoff to the bundle sync flow so repeated errors do not keep hitting the server at a fixed cadence. Update StacBundleService._syncInternal to record consecutive failures for non-2xx/304/204 responses and caught exceptions, then have StacBundleUpdater skip the next scheduled sync attempts for a short backoff window after repeated failures. Reset the failure state after a successful sync so normal polling resumes.
169-194: 🗄️ Data Integrity & Integration | 🔵 Trivial | ⚡ Quick winChecksum is stored but never verified.
_bundleFromResponsecaptureschecksumfrom the response into the persistedStacBundle, but nothing in this file (or the reviewed cohort) compares it against a locally computed hash ofscreens/themesbefore trusting and persisting the payload on a200. If the intent (per the CLI'scomputeBundleChecksum) is end-to-end integrity verification, a corrupted/incomplete-but-valid-JSON response would currently be accepted and cached without detection.If checksum verification is intentionally deferred to the model layer or CLI-only (deploy-time verification), this is fine — otherwise consider validating it here before swapping in the new bundle.
♻️ Possible verification step
final bundle = _bundleFromResponse( Map<String, dynamic>.from(data), projectId: projectId, etagHeader: response.headers.value('etag'), ); if (bundle == null) { Log.w('StacBundleService: Bundle response is missing a version'); return cached; } + if (bundle.checksum != null && + !_matchesChecksum(bundle)) { + Log.w('StacBundleService: Bundle checksum mismatch, discarding'); + return cached; + }Please confirm (or search) whether checksum verification against the bundle payload is implemented elsewhere in the
StacBundlemodel, or whether it's deploy-time-only by design.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@packages/stac/lib/src/services/stac_bundle_service.dart` around lines 169 - 194, The checksum captured in _bundleFromResponse is persisted but never validated against the bundle payload before accepting a 200 response. Check whether StacBundle or any related service already verifies the checksum; if not, add verification in StacBundleService._bundleFromResponse before constructing the StacBundle, comparing the response checksum to a locally computed hash of screens/themes and rejecting mismatches. If checksum validation is intentionally handled elsewhere, document that design clearly in this path.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@packages/stac_cli/lib/src/services/deploy_service.dart`:
- Around line 137-182: The deploy flow in deploy_service.dart currently writes
the seed asset even when the decoded 2xx response has no version, which can
overwrite a valid bundle with an invalid empty seed. Update the deploy handling
around the response body/version check in the deploy method to validate that
body['version'] is present before calling _writeSeedAsset, and either skip the
write or throw a StacException for malformed success responses; keep the
existing success/info logging and checksum handling in place.
In `@packages/stac/lib/src/framework/stac_service.dart`:
- Around line 202-207: The bundle initialization path in StacService should use
the caller’s dio and validate options up front: pass the same dio used by
StacNetworkService into the bundle sync flow so StacBundleService.sync honors
auth/interceptors/proxy settings, and guard the _bundleConfig.enabled branch so
StacBundleUpdater.start() and prefetch only run when options is present. If
bundle mode is enabled without options, fail fast during initialization with a
clear validation error instead of letting the later _projectId access in
StacBundleService or the updater throw asynchronously.
---
Nitpick comments:
In `@packages/stac/lib/src/services/stac_bundle_service.dart`:
- Around line 104-167: Add lightweight failure backoff to the bundle sync flow
so repeated errors do not keep hitting the server at a fixed cadence. Update
StacBundleService._syncInternal to record consecutive failures for
non-2xx/304/204 responses and caught exceptions, then have StacBundleUpdater
skip the next scheduled sync attempts for a short backoff window after repeated
failures. Reset the failure state after a successful sync so normal polling
resumes.
- Around line 169-194: The checksum captured in _bundleFromResponse is persisted
but never validated against the bundle payload before accepting a 200 response.
Check whether StacBundle or any related service already verifies the checksum;
if not, add verification in StacBundleService._bundleFromResponse before
constructing the StacBundle, comparing the response checksum to a locally
computed hash of screens/themes and rejecting mismatches. If checksum validation
is intentionally handled elsewhere, document that design clearly in this path.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 356aed86-6eb8-47f6-ae9f-429fd5ea4c48
⛔ Files ignored due to path filters (1)
packages/stac_cli/pubspec.lockis excluded by!**/*.lock
📒 Files selected for processing (19)
packages/stac/lib/src/framework/stac.dartpackages/stac/lib/src/framework/stac_service.dartpackages/stac/lib/src/models/models.dartpackages/stac/lib/src/models/stac_bundle.dartpackages/stac/lib/src/models/stac_bundle.g.dartpackages/stac/lib/src/models/stac_bundle_config.dartpackages/stac/lib/src/services/services.dartpackages/stac/lib/src/services/stac_bundle_service.dartpackages/stac/lib/src/services/stac_bundle_store.dartpackages/stac/lib/src/services/stac_bundle_updater.dartpackages/stac/lib/src/services/stac_cloud.dartpackages/stac/test/models/stac_bundle_test.dartpackages/stac/test/services/stac_bundle_service_test.dartpackages/stac_cli/CHANGELOG.mdpackages/stac_cli/lib/src/commands/deploy_command.dartpackages/stac_cli/lib/src/services/build_service.dartpackages/stac_cli/lib/src/services/deploy_service.dartpackages/stac_cli/pubspec.yamlpackages/stac_cli/test/services/deploy_service_test.dart
…dater Stac.initialize runs before runApp in most apps, so WidgetsBinding.instance may not exist when bundle mode registers its lifecycle observer. Create the binding defensively (idempotent) instead of requiring every app to add WidgetsFlutterBinding.ensureInitialized before Stac.initialize.
…rred migration prep)
- key in-memory bundle state by projectId; a re-initialize with a different project drops the old bundle (epoch-guarded, so in-flight syncs can't resurrect stale state) - clear() re-hydrates the seed and discards racing in-flight syncs - sync(force: true) queues behind an in-flight sync instead of being silently downgraded to its conditional result - back off ensureLoaded's auto-sync for 30s after a failure and stop falling through to legacy per-screen fetches when the bundles endpoint rejected the project (404/403); memoize missing-artifact warnings per bundle version - stop the updater when re-initialized with bundle mode disabled; re-arm the polling timer on config changes; sync without options returns null instead of throwing on resume/poll ticks - mark hydration complete only on success; surface store write failures and non-network sync errors at warn level - normalize trailing slash in baseUrl - CLI: skip the seed write (loudly) when the deploy response carries no version; fix bare `assets` pubspec false-negative; correct the 1.7.0 changelog wording Adds 16 tests covering each fixed behavior.
Bundle mode fetches a project's bundle and cannot function without a projectId. Validate at the top of initialize (before any state is mutated) instead of starting an updater whose resume and poll ticks can only warn. With the guarantee in place, the prefetch no longer needs its own null check. sync() keeps returning null for a missing-options call as defense in depth, since it is public API and reachable without a successful initialize.
Enable StacBundleConfig with a seed asset, add the generated stac_bundle.json, install agent skills into the example, migrate iOS Runner to the scene-delegate lifecycle, and bump stac to 1.5.0.
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.
What
Adds opt-in bundle mode: instead of fetching every screen/theme with its own request, apps download all artifacts as a single versioned bundle, cache it, and only re-download when the server has a newer version.
Client (
packages/stac)StacBundleConfigonStac.initialize(enabled: falseby default — zero behavior change unless opted in):seedAsset,baseUrl,checkOnResume,pollingInterval.StacBundleService: conditional sync (ETag/If-None-Match+?sincefallback) —304/204keep the cache,200swaps and persists; offline falls back to the cached bundle;updatesstream notifies hosts when a new version lands.StacBundleUpdater: re-checks on app-resume (default on) and on an optional foreground polling interval.CLI (
packages/stac_cli)stac deployis now atomic: one POST with all screens/themes + checksum; any failure exits non-zero with nothing partially applied. Logs artifact counts and payload size.--legacykeeps the old per-file behavior for one release.assets/stac_bundle.json) stamped with the server-authoritative version after every deploy, and warns if pubspec doesn't declare it.stac buildnow cleans stale outputs so deleted screens can't linger in.build.Tests
packages/stac), 8 deploy service tests (packages/stac_cli) — first tests in the CLI package (test: Write tests for stac_cli #459 start).dart analyzeclean in both packages.Notes
/bundlesendpoint (rolling out server-side).Summary by CodeRabbit
bundleConfigoption to initialize, sync, and serve screens/themes from a single versioned bundle (with resume checks and optional polling).--legacyto restore the previous upload flow.screens/themes, preventing redeploys with stale JSON.