Skip to content

Conversation

@paracycle
Copy link
Member

Motivation

We have some internal gems that are meant to be used only during development. They have started enforcing that with a check at gem load time, and by calling exit to abort the process. This breaks Tapioca gem loading unnecessarily.

Implementation

We've already had the mechanism for running a block with disabled exits, so I just moved that to top level, and started using it around gem loading as well.

Tests

Added a test for the new expected behaviour.

@paracycle paracycle requested a review from a team as a code owner September 12, 2025 14:24
@paracycle paracycle added the enhancement New feature or request label Sep 12, 2025
@paracycle paracycle force-pushed the uk-abort-during-gem-load branch from d2046cd to 8aa00da Compare September 12, 2025 15:24
@paracycle paracycle enabled auto-merge September 12, 2025 15:33
@paracycle paracycle merged commit 68a6e09 into main Sep 12, 2025
17 checks passed
@paracycle paracycle deleted the uk-abort-during-gem-load branch September 12, 2025 15:52
) if @file_header

rbi.root = Runtime::Trackers::Autoload.with_disabled_exits do
rbi.root = Tapioca.with_disabled_exits do
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it could have stayed under Runtime with other runtime related helpers

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can move both of the runtime helper methods under runtime, no problem.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants