Fix job.created_at time if necessary #1284
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
terrazoon
requested review from
A-Shumway42,
heyitsmebev and
xlorepdarkhelm
and removed request for
heyitsmebev
This was referenced Aug 20, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
We have some anomaly where the created_at field for jobs is set 3 days in the past (intermittently). It seems like there is only one place where this happens (dao_create_job()), so add some debugging and a repair attempt and get this up to staging and see what happens.
We have a couple dozen tests using "freeze time" which all break if we try to do the repair, so do a check on what environment we are running in before doing it.
Security Considerations
N/A