Current capture behavior for targeting mirrors the API StartTracking contract--capture only functions when the target is available, validating and failing early with clear error reason when otherwise.
Request was received for a behavior where, in the --target-name matching mode, the app would arm and wait for a matching process if one does not already exist when the command is first executed. This could be implemented with a loop that repeats on failure (with suitable holdoff, creating an effective polling loop), or with explicit polling for availability before actual execution. Prefer 2nd approach since first will generate log spam without annoying modifications to error handling and reporting.
Current capture behavior for targeting mirrors the API StartTracking contract--capture only functions when the target is available, validating and failing early with clear error reason when otherwise.
Request was received for a behavior where, in the --target-name matching mode, the app would arm and wait for a matching process if one does not already exist when the command is first executed. This could be implemented with a loop that repeats on failure (with suitable holdoff, creating an effective polling loop), or with explicit polling for availability before actual execution. Prefer 2nd approach since first will generate log spam without annoying modifications to error handling and reporting.