-
Notifications
You must be signed in to change notification settings - Fork 132
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
Implement the List-returning GetFirstByLowestScoreFromSet #368
Comments
You cannot push to this repo directly while not being a collaborator/member. Please create a PR from a fork. |
shokanson-extensiv
pushed a commit
to shokanson-extensiv/Hangfire.PostgreSql
that referenced
this issue
May 25, 2024
shokanson-extensiv
added a commit
to shokanson-extensiv/Hangfire.PostgreSql
that referenced
this issue
May 25, 2024
shokanson-extensiv
added a commit
to shokanson-extensiv/Hangfire.PostgreSql
that referenced
this issue
May 30, 2024
support non-exception-based discovery of batching capability add HasFeature unit tests
azygis
added a commit
that referenced
this issue
Jun 27, 2024
…cheduler-parallelism #368 allow scheduler parallelism
Thank you! And sorry for the long wait. |
No problem. Thank you for accepting my contribution. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In a conversation with Sergey Odinokov regarding the new scheduler parallelism support in Hangfire.Core 1.8.12, he suggested this to allow Hangfire.PostgreSql to support it:
(I think the last part is incorrect because the
LIMIT
clause should remain, but instead of1
use the providedcount
.)I have made the changes in a local repo and would like to submit a PR for review. Should I fork this GitHub repo and submit a PR from my fork? Or should I push a feature branch to this repo and submit the PR from there?
The text was updated successfully, but these errors were encountered: