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
core: BareosDb::FindLastJobStartTimeForJobAndClient: take into account Running job #1265
core: BareosDb::FindLastJobStartTimeForJobAndClient: take into account Running job #1265
Conversation
08b95b8
to
08f1b94
Compare
08f1b94
to
2f6001f
Compare
2f6001f
to
60492e1
Compare
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 have changed the PR title, as it is not BareosDb::SqlFindResult
, but
BareosDb::FindLastJobStartTimeForJobAndClient
where the changes werde made. BareosDb::SqlFindResult
is the return type.
This is also wrong in the commit comment.
I also changed the comment a bit, I hope that my changes make sense. They are in a separate commit.
Thanks for the good work!
250fa8f
to
6e6a185
Compare
I've rebased on master, plus fixed the commit comment, and also have prepared the CHANGELOG.md line. |
…t Running job - Adding Created and Running jobs to the query will avoid the start of a second backup job for the same client while starttime is overdue. As we need to return a time_t and jobstatus = C doesn't have starttime set, now() is used with casting forced to expected timestamp without DST Fix [BUG bareos#1466] Signed-off-by: Bruno Friedmann <bruno.friedmann@bareos.com>
Signed-off-by: Bruno Friedmann <bruno.friedmann@bareos.com>
6e6a185
to
b8865d4
Compare
Fix [BUG #1466]
[OP #5251]
Please check
If you have any questions or problems, please give a comment in the PR.
Helpful documentation and best practices
Checklist for the reviewer of the PR (will be processed by the Bareos team)
General
Source code quality
bareos-check-sources --since-merge
does not report any problems