On start, update git_pillar on second loop#56316
Conversation
554902a to
e7fb270
Compare
|
can we get an associated issue open alongside this PR, so its clear what issue we are fixing and in case anyone else is running into the issue its easily discoverable? |
Ch3LL
left a comment
There was a problem hiding this comment.
any chance we can get a test case here to ensure it does not regress in the future?
e7fb270 to
e8fa960
Compare
|
@Ch3LL I have no idea of how to test this. |
|
I would suggest a unit test here |
|
Hey @sathieu any follow up on this? I can help you write a test if you need for this PR. 😄 |
22f7ba0 to
5c70ccd
Compare
|
@xeacott Yes, please help me with a test. |
5c70ccd to
3fbe7eb
Compare
@Ch3LL OK but how to escape the |
|
I would suggest something like this to get you started... |
289c55c to
7a93f6d
Compare
|
@Ch3LL Please review again. There are (passing 😄) tests now! |
|
Also @xeacott please review ... |
|
Oh yes will do, thanks for writing those tests! |
7a93f6d to
654e2c7
Compare
|
@xeacott You've marked this PR Merge Ready. I've now rebased and fixed |
9b01805 to
81c0e5d
Compare
What does this PR do?
Before this patch, the master would wait
git_pillar_update_intervalbefore doing the first update. When this setting is big (we set it to one week at work), this can lead to unfetched repositories.What issues does this PR fix or reference?
PR #53621
Fixes #56356.
Previous Behavior
The first
git_pillarupdate would run at start time +git_pillar_update_interval.New Behavior
The first git_pillar update would run at start time.
Tests written?
No
Commits signed with GPG?
No