Is your feature request related to a problem? Please describe.
As the options for local CV data sources expand, we're finding the limiting factor is now using the CT talker with the API emulator Fakevine and the hard limit programmatically of 200 calls, which CT has no way of knowing these limits don't exist, why would it? The real deal doesn't even bother responding when the limit is reached.
Describe the solution you'd like
Just an argument (definitely good and warning like maybe even with a one time typed out 'yes' indicating understanding of responsibility for the action) to ignore pyrate for the kicked off run
Describe alternatives you've considered
None come to mind we need this limit for normal operations and it shouldn't be just a flag to turn off the first time ideally
Additional context
As always love this tool and modernization of it
Is your feature request related to a problem? Please describe.
As the options for local CV data sources expand, we're finding the limiting factor is now using the CT talker with the API emulator Fakevine and the hard limit programmatically of 200 calls, which CT has no way of knowing these limits don't exist, why would it? The real deal doesn't even bother responding when the limit is reached.
Describe the solution you'd like
Just an argument (definitely good and warning like maybe even with a one time typed out 'yes' indicating understanding of responsibility for the action) to ignore pyrate for the kicked off run
Describe alternatives you've considered
None come to mind we need this limit for normal operations and it shouldn't be just a flag to turn off the first time ideally
Additional context
As always love this tool and modernization of it