Automatically use Rails or a default timezone for the schedule#750
Merged
Conversation
Contributor
Author
|
Maybe I'm wrong, but the build failures don't feel anything to do with this change? |
Member
|
Hey @andyjeffries, thanks a lot for this, and sorry for the delay! I'm finally catching up with PRs. This makes sense, I'm going to tweak the code a bit and will be merging it shortly. |
Rather than have SolidQueue act on the server configured time, this change allows you to use either the Rails application's current timezone or a specified default.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Rather than have SolidQueue act on the server configured time, this change allows you to use either the Rails application's current timezone (by default if in a Rails app) or a specified default.