Skip to content

Warn when --only-bootsnap-rbs-cache runs without TAPIOCA_RBS_CACHE=1#2624

Open
KaanOzkan wants to merge 1 commit into
mainfrom
kaan/warn-missing-rbs-cache-env
Open

Warn when --only-bootsnap-rbs-cache runs without TAPIOCA_RBS_CACHE=1#2624
KaanOzkan wants to merge 1 commit into
mainfrom
kaan/warn-missing-rbs-cache-env

Conversation

@KaanOzkan
Copy link
Copy Markdown
Contributor

@KaanOzkan KaanOzkan commented May 13, 2026

Summary

  • Addresses PR #2617 review comment from @Morriar.
  • Without TAPIOCA_RBS_CACHE=1 set, bootsnap/setup isn't required at boot and no RBS cache gets populated. Previously tapioca dsl --only-bootsnap-rbs-cache would still print "Bootsnap RBS cache populated", misleading users into thinking it had done useful work.
  • Now emits a warning to stderr in that case so the misuse is visible.

Test plan

  • New spec: warns when --only-bootsnap-rbs-cache is set without TAPIOCA_RBS_CACHE=1
  • Existing happy-path spec updated to set TAPIOCA_RBS_CACHE=1 and assert bootsnap stats appear on stderr (confirming bootsnap actually ran)

Without the env var set, `bootsnap/setup` isn't required at boot and no
RBS cache gets populated. Previously the command would still print
"Bootsnap RBS cache populated", misleading users into thinking it had
done useful work.

Addresses #2617 (comment)
@KaanOzkan KaanOzkan requested a review from a team as a code owner May 13, 2026 17:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant