I think the answer is currently "no", but want to double check.
It appears that anytime there is a failure and there is a configuration found for reporting, scope will prompt the user (assuming auto-report isn't set).
https://github.com/oscope-dev/scope/blob/53ec4cf3a9c3fcf077093c29ce9029abe55dbe6e/scope/src/doctor/commands/run.rs#L78
Is this correct? There is currently no way to bypass the prompt?
Additional context:
Now, you're going to tell me "don't do that" and you'd be right, but we're currently in the process of migrating from a script based solution to scope doctor.
We have a script that was using scope-intercept as the shebang.
In order to start migrating over to scope, we started calling scope doctor near the beginning of that script.
#!/usr/bin/env scope-intercept -- bash
# some env variable stuff and some argument translation shenanigans
scope doctor run # passing some translated flags here too
ruby path/to/ruby/script
I was recently making a change to make this script stop if scope doctor run fails and noticed that this caused users to get prompted twice, in quick succession, to report the error.
#!/usr/bin/env scope-intercept -- bash
scope doctor run || exit 1
ruby path/to/ruby/script
I worked around this by returning a success code if scope doctor run fails, but that is obviously less than idea.
#!/usr/bin/env scope-intercept -- bash
scope doctor run || exit 0
ruby path/to/ruby/script
At some point, we should be able to stop using scope-intercept and just delegate directly to scope doctor run, but until we've completely migrated and removed ruby path/to/ruby/script it would be nice if we could disable reporting from one of these.
Hopefully that provides some context on why I would like to be able to disable the reporting prompt.
I think the answer is currently "no", but want to double check.
It appears that anytime there is a failure and there is a configuration found for reporting,
scopewill prompt the user (assuming auto-report isn't set).https://github.com/oscope-dev/scope/blob/53ec4cf3a9c3fcf077093c29ce9029abe55dbe6e/scope/src/doctor/commands/run.rs#L78
Is this correct? There is currently no way to bypass the prompt?
Additional context:
Now, you're going to tell me "don't do that" and you'd be right, but we're currently in the process of migrating from a script based solution to
scope doctor.We have a script that was using
scope-interceptas the shebang.In order to start migrating over to scope, we started calling
scope doctornear the beginning of that script.I was recently making a change to make this script stop if
scope doctor runfails and noticed that this caused users to get prompted twice, in quick succession, to report the error.I worked around this by returning a success code if
scope doctor runfails, but that is obviously less than idea.At some point, we should be able to stop using
scope-interceptand just delegate directly toscope doctor run, but until we've completely migrated and removedruby path/to/ruby/scriptit would be nice if we could disable reporting from one of these.Hopefully that provides some context on why I would like to be able to disable the reporting prompt.