Add queue detail page, support for River Pro concurrency limits#326
Merged
Add queue detail page, support for River Pro concurrency limits#326
Conversation
Don't use Goose migration files, use plain SQL schema files for sqlc.
bgentry
force-pushed
the
bg-concurrency
branch
3 times, most recently
from
dd8e1ae to
f48340a
Compare
brandur
approved these changes
Apr 9, 2025
Collaborator
brandur
left a comment
brandur
left a comment
There was a problem hiding this comment.
Great stuff Blake! Some of the TS is a little beyond me, but seems to be generally good. Let's bias towards getting this out the door.
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.
Added a queue detail page with the ability to view queue stats. For River Pro customers, this page offers the ability to dynamically override concurrency limits and to view individual clients for each queue, along with how many jobs each is working.
I'm sure there will be lots of additional tweaks to make to this in the future but it's a solid start IMO.
@brandur I've organized the commits to hopefully make this easier for you to look at. Everything is small and granular with the exception of the giant JS commit 😆