-
Notifications
You must be signed in to change notification settings - Fork 51
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
Sub-task's state is to do, but task is done #262
Labels
bug
Something isn't working
Comments
SteveMcGrath
added a commit
that referenced
this issue
May 22, 2024
The SubTask upsert method was failing do to the mapping change from 2.0.4, however was masked because this was occuring within a worker thread. Corrected the issue, Added logic to only use threading when the max_workers is above 1 (for testing), and also added a failsafe to stop execution after processing findings if the number of observed exceptions from the worker jobs is above 0.
SteveMcGrath
added a commit
that referenced
this issue
May 22, 2024
The SubTask upsert method was failing do to the mapping change from 2.0.4, however was masked because this was occuring within a worker thread. Corrected the issue, Added logic to only use threading when the max_workers is above 1 (for testing), and also added a failsafe to stop execution after processing findings if the number of observed exceptions from the worker jobs is above 0.
Can run an automation task to re-open those closed tasks && test with 2.0.5? If you are still seeing issues, I'd like you to set the max_workers to |
yes, set max_workers to 1 and verison 2.0.5, The issue was fix . And the task in "done" state will be reopen to "to do". I think this issue was fixed |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Sub-task's state is to do, but task is done
The text was updated successfully, but these errors were encountered: