Skip to content

Conversation

@brandur
Copy link
Contributor

@brandur brandur commented Jan 25, 2025

This one follows up [1] in the main repository, in which we fix what
could be considered a bug in that by period uniqueness was always based
off the current time, even though a job may have been given a custom
value for scheduled_at, which really should take precedence.

[1] riverqueue/river#734

@brandur brandur requested a review from bgentry January 25, 2025 21:28
Copy link
Contributor

@bgentry bgentry left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:shipit:

This one follows up [1] in the main repository, in which we fix what
could be considered a bug in that by period uniqueness was always based
off the current time, even though a job may have been given a custom
value for `scheduled_at`, which really should take precedence.

[1] riverqueue/river#734
@brandur brandur force-pushed the brandur-scheduled-at-period branch from 0bd8d8f to 0451fce Compare January 25, 2025 21:36
@brandur
Copy link
Contributor Author

brandur commented Jan 25, 2025

Thx. Added changelog too.

@brandur brandur merged commit 560c6b4 into master Jan 25, 2025
7 checks passed
@brandur brandur deleted the brandur-scheduled-at-period branch January 25, 2025 21:40
brandur added a commit that referenced this pull request Apr 12, 2025
I just noticed that we've had an unreleased change sitting in `master`
since December since changes in this gem are pretty rare unfortunately.
Let's cut a release just so we can get that change (#39) finally shipped
out.
@brandur brandur mentioned this pull request Apr 12, 2025
brandur added a commit that referenced this pull request Apr 12, 2025
I just noticed that we've had an unreleased change sitting in `master`
since December since changes in this gem are pretty rare unfortunately.
Let's cut a release just so we can get that change (#39) finally shipped
out.
brandur added a commit that referenced this pull request Apr 12, 2025
I just noticed that we've had an unreleased change sitting in `master`
since December since changes in this gem are pretty rare unfortunately.
Let's cut a release just so we can get that change (#39) finally shipped
out.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants