Repository navigation
Two robustness fixes the Bazel pilot surfaced - #415
Conversation
require_relative resolves symlinks, so a stub registered under the path as given misses when the tree is reached through one (a symlinked checkout, Bazel's runfiles), and the real file loads instead. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A tarball checkout inside another git work tree made `git -C APP rev-parse` answer for the outer repository, and `git archive` exported that instead of the app: no Gemfile, and bundle install failed. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configuration
📒 Files selected for processing (3)
Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 9 remain after this review. 📝 WalkthroughWalkthroughPreparation now selects the tracked-file archive only when the app path matches the physical Git top level. Overlay tests now register loaded features with real paths derived from their requiring files. ChangesCheckout archive selection
Overlay loaded-feature paths
Priority: ➖ Normal Estimated code review effort: 2 (Simple) | ~10 minutes Change: Bug fix Suggested reviewers: Merge Risk: ⚪ Minimal · up to Preparation avoids using an enclosing repository’s archive for the app, and the overlay fixtures use paths that match the runtime’s relative requires. No actionable merge-blocking risk is established. Architecture SummaryArchitecture risk: 🔵 Low · up to The change affects 2 systems. Changed systems: Architecture concerns Review detailsSystems and components
Before / after behavior
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Two fixes the Bazel/BuildBuddy pilot (#309) surfaced. Both are correct without Bazel.
tests/overlay_cable_{identity,dispatch}.rb. They stubbedbroadcasts(andturbo_streams.rb's siblings) in$LOADED_FEATURESunder the path as given.require_relativeresolves symlinks, so from a symlinked tree (a symlinked checkout, Bazel's runfiles) the stub missed and the real file loaded. They now register the real path. To check, I ran both drivers from acp -ascopy ofruntime/: main's versions fail, and these printALL OK.scripts/campfire-oracle. It chosegit archiveafter a baregit -C APP rev-parse, which answers for any enclosing work tree. A tarball checkout inside another repository therefore exported the outer repository: no Gemfile, sobundle installfailed. It now uses git only when APP is its own repository's top level.Summary by CodeRabbit