You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 14, 2021. It is now read-only.
bin/bundle should trap SIGINT all the time, rather than just surrounding Bundler::CLI.start.
Currently, if the user hits <ctrl>+c generating a SIGINT while bundler is in the middle of require 'bundler'or require 'bundler/cli', the error will be unhandled. Bundler should trap this SIGINT too by wrapping the whole binary in an exception-handling block which handles Interrupt. If Bundler did so, then there would be much less chance (essentially just the binstub or any -r flags) for a SIGINT to go unhandled.
The text was updated successfully, but these errors were encountered:
bin/bundle
should trapSIGINT
all the time, rather than just surroundingBundler::CLI.start
.Currently, if the user hits
<ctrl>+c
generating aSIGINT
while bundler is in the middle ofrequire 'bundler'
orrequire 'bundler/cli'
, the error will be unhandled. Bundler should trap thisSIGINT
too by wrapping the whole binary in an exception-handling block which handlesInterrupt
. If Bundler did so, then there would be much less chance (essentially just the binstub or any-r
flags) for aSIGINT
to go unhandled.The text was updated successfully, but these errors were encountered: