-
-
Notifications
You must be signed in to change notification settings - Fork 210
fix: improve unresolved task deletion job #594
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
base: master
Are you sure you want to change the base?
Conversation
Seems weird that the build failed on
|
Yeah, probably a test-issue |
Anything I can do with this? |
schedulerTaskRepository.getScheduledExecutions( | ||
ScheduledExecutionsFilter.all(), | ||
execution -> | ||
taskToNewestExecutionTime.merge( | ||
execution.taskInstance.getTaskName(), | ||
execution.executionTime, | ||
(oldValue, newValue) -> oldValue.isAfter(newValue) ? oldValue : newValue)); | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would rather avoid this...
Is there perhaps a way to have the TaskResolver also get information on how long the task-name has been unresolved 🤔 (and use that, rather than fetching all executions into mem and checking)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I.e. do something here
For example, sending in the execution-time for the execution that is unresolved
Brief, plain english overview of your changes here
Calculates age of unresolved execution based on it's execution time instead of first scheduler run.
More in issue: #515 (comment)
Fixes
#515
Reminders
mvn spotless:apply
- also added.gitattributes
because spotless went mad with CRLF on Windowscc @kagkarlsson