Skip to content

Conversation

@deivid-rodriguez
Copy link
Contributor

@deivid-rodriguez deivid-rodriguez commented Jan 27, 2025

What was the end-user or developer problem that led to this PR?

Ruby 3.5 moves irb to a bundled gem, so it may not always be available. If that happens, bundle console will try to load IRB again with the message

Couldn't load console irb, falling back to irb

which makes little sense to do and will always fail.

What is your fix for the problem, implemented in this PR?

Don't try to fallback to IRB if IRB was tried in the first place.

Fixes the little issue mentioned in #8396 (comment).

Make sure the following tasks are checked

These gems always define their main namespace and I don't think that
will ever change.
@deivid-rodriguez deivid-rodriguez force-pushed the deivid-rodriguez/remove-unnecessary-console-fallback branch from 7806b99 to f9bf585 Compare January 29, 2025 09:30
@deivid-rodriguez deivid-rodriguez merged commit 790a202 into master Jan 29, 2025
91 checks passed
@deivid-rodriguez deivid-rodriguez deleted the deivid-rodriguez/remove-unnecessary-console-fallback branch January 29, 2025 11:40
deivid-rodriguez added a commit that referenced this pull request Feb 17, 2025
…ssary-console-fallback

Fix `bundle console` unnecessarily trying to load IRB twice

(cherry picked from commit 790a202)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants