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
This project is for the Heroku CLI only. Use https://help.heroku.com for anything that is not specific to the CLI itself.
Do you want to request a feature or report a bug?
Bug
What is the current behavior?
I am using 'heroku-run' package to create a dyno and attach to it to run commands. After the command is run on the dyno, I display text on console in a loop. I am however not able to stop the display using sigint. It seems that console ignores any keyboard input to stop the process. This only happens when the options sent to the Dyno library has attach option set as true.
What is the expected behavior?
The console should exit the process when typing Ctrl + C
example:
let { Dyno } = require('heroku-run')
let opts = {
app: myApp,
command: migrationCmd,
release: currentRelease,
size: 'Private-M',
attach: true, // this bug does not happen on attach = false
'exit-code': true,
heroku: myClient
}
let dyno = new Dyno(opts)
await dyno.start()
while (!formationReady()) {
displayDynoFormation() . //cannot exit this loop with ctrl +c
cli.wait(1)
}
The text was updated successfully, but these errors were encountered:
This project is for the Heroku CLI only. Use https://help.heroku.com for anything that is not specific to the CLI itself.
Do you want to request a feature or report a bug?
Bug
What is the current behavior?
I am using 'heroku-run' package to create a dyno and attach to it to run commands. After the command is run on the dyno, I display text on console in a loop. I am however not able to stop the display using sigint. It seems that console ignores any keyboard input to stop the process. This only happens when the options sent to the Dyno library has attach option set as true.
What is the expected behavior?
The console should exit the process when typing Ctrl + C
example:
The text was updated successfully, but these errors were encountered: