* WIP
* Add endpoint to cancel jobs
* Fix endpoints and add modal to cancel jobs
* Add useful tooltips and warnings
* Fix openapi.yml
* Prepare sqlx
* Prepare sqlx
* Select jobs to cancel
* Prepare sqlx
* Remove unused variable
* Make small fixes
- gap between buttons
- dropdown in one button with chevron instead of two buttons
- filters shown on the cancel filtered modal
* Store jobs that waited for too long
* Add warnings as badges for long waited jobs
* Separate into self_wait_time and aggregate
Change the UI accordingly
* Prepare sqlx
* Update backend/windmill-queue/src/jobs.rs
Co-authored-by: ellipsis-dev[bot] <65095814+ellipsis-dev[bot]@users.noreply.github.com>
* Fix incorrect query
* Prepare sqlx
* Move insert to pull + UI fixes
Insert as soon as the job is pulled and therefore started.
Add a badge on the lfow timeline to show the self wait time
* Move to after the pull in the worker
Move the logic to after the pull in the worker in the case its not a
noop
* Remove weird line
* Remove unnecessary async
---------
Co-authored-by: ellipsis-dev[bot] <65095814+ellipsis-dev[bot]@users.noreply.github.com>
Co-authored-by: Ruben Fiszel <ruben@windmill.dev>
* fix missing filtering on ommision of obscured jobs
Also allow cron and scheduled jobs for the filtering security
* Revert incorrect change
* Revert frontend change
* Resize badge and add filter by key button
* Make status filters icononly with tooltip
* nit: replace current job None with empty
* tooltip should be on the same row with flex
* Expand selected on ToggleButtonMore
* Make a common definition of UnifiedJob fields
* fix: mismatch when filtering on concurrency key
Fix a mismatch between to endpoints when filtering by concurrency key
* Add ObscuredJob type on openapi spec
* Correct unit for graph
* Finish frontend changes
* Add field indicating if obscured jobs were omitted
* impl from for ListQueueQuery and factor logic
---------
Co-authored-by: Ruben Fiszel <ruben@windmill.dev>
* Add concurrency_key table and field to payload
Add a new table custom_concurrency_key for storing concurrency keys on a
per job basis. Add the field to the job payload to populate the table on
creation of a new job.
* Rename to custom_concurrency_key
Be more explicit about the nature of the option variable by calling it
a more appropriate name.
* Delete concurrency_keys on delete_expire_items
* Propagate db errors up
* Add ref to EE changes
* update sqlx
* Add concurrency_key to tests
* Revert renaming of FlowValue field
FlowValue field concurrency_key must be named concurrency_key for
serialization purposes.
* Remove debug print statement
* Get concurrency_key from Job
Whether it is a Completed job or a queued one, add a ways to get the
associated concurrency key
* Add endpoint to get concurrency_key
* Add endpoint and button to get job concurrency_key
Add a line with a link on the FlowMetadata that goes to the
concurrency_groups page. add endpoint to get the concurrency_key of a
job
* Merge concurrency_key tables into one
migration + change all related querrys
* Add concurrency plot to the runs page
* Prepare sqlx
* Add concurrency Key filter on UI
* Prepare sqlx
* Prepare sqlx
* Fix filter and order query
The limit makes more sense if we cut the older rows, so order by
started_at
* Factor interpolation to reuse on concurrency key
Factor the arg interpolation logic into a function and finish the
processing of concurrency key before insertion
* Remove old concurrency key processing logic
* Second transaction with userdb
To send all concurrency intervals but revealing only uuids of accessible
jobs, make a second transaction with the userdb.
* Remove old second endpoint
the intervals endpoint now also gets the concurrencyt key information
for all jobs
* Show external jobs
* Put filters into a dropdown
Create a ToggleButtonMore and put elements into a dropdown
* Add toggle between two graphs
* Add filter functionality to concurrency graph
* Improve concurrency graph front
* Fix concurrency groups page
* Prepare sqlx
* Add ref to ee
* Change migration to create new table instead
Instead of renaming the custom_concurrency_key_ended atble, we create a
new table and we will delete custom_concurrency_key_ended in the future
when it is no longer linked to any jobs
* Do small UI improvements
* Fix range fusion by not filtering past jobs
Instead of filtering jobs in the backend on a startedAfter value, limit
the query to 1000 and query all possible towards the past to get a good
context for the graph in most sane situations
* Improve frontend UI
