Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: Only reuse cached detections if the cached run completed #348

Conversation

spdawson
Copy link
Contributor

@spdawson spdawson commented Jan 9, 2023

Description

If an invocation is killed or otherwise interrupted, then it should not result in a cached detection set that can be re-used by a subsequent invocation.

Related

Closes #335

Checklist

  • I've added test coverage that shows my fix or feature works as expected.
  • I've updated or added documentation if required.
  • I've included usage information in the description if CLI behavior was updated or added.
  • PR title follows Conventional Commits format

If an invocation is killed or otherwise interrupted, then it should
not result in a cached detection set that can be re-used by a
subsequent invocation.

Closes #335
@spdawson spdawson force-pushed the 335-cached-detections-shouldnt-be-reused-if-the-binary-has-been-killed branch from 400fb49 to f7c3df1 Compare January 9, 2023 09:36
@spdawson spdawson merged commit 554a73e into main Jan 9, 2023
@spdawson spdawson deleted the 335-cached-detections-shouldnt-be-reused-if-the-binary-has-been-killed branch January 9, 2023 10:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Cached detections shouldn't be reused if the binary has been killed
2 participants