Flow observes `suspend` setting and will wait for resume messages sent for the job before continuing to the next step in a flow.
Adds endpoints under workspaces at `/jobs/<cancel|resume>/<job-uuid>` to either cancel or resume the job with a payload. For POST requests to the endpoint, payload is a JSON document. For GET requests to the endpoints, the payload is a base64url encoded JSON document as the value of the payload query parameter.
* add jobs_duration to /api/w/*/users/list
A few improvements on this might be considered.
- Adding the duration to /whoami and /whois
- Optionally fetching duration conditional on a query parameter.
- Using the query parameter value to select how far back to look,
`created_at > now() - $2 * '1 day'::interval`.
Subquery might not be optimal, but performance is a bit weird to test
right now as I haven't done much with my development database to get it
to resemble a typical (production) database. And there aren't many
indexes currently either.
And I think my rust rustfmt doesn't run because unstable options in the
rustfmt.toml or something so the formatting might be a bit wonky.
* duration -> duration_ms for completed_job
sqlx reordered keys in sqlx-data.json so the diff is quite noisy. I'm
not sure if I did it wrong or if this tool is obnoxious that way.
* don't double count job duration in flows
* job_duration_ms to Usage duration_ms jobs flows
rustfmt got carried away sorry
* typescript support
* frontend
* type inference
* type inference
* v0 works
* v0 typescript
* v0 typescript
* deno-client v0
* deno-client v0
* build_deno
* rm autogenerated files
* test workflow
* test workflow
* test workflow
* test workflow
* test workflow
* test workflow
* test workflow
* test workflow
* test workflow
* test workflow
* test workflow
* test workflow
* test workflow
* test workflow
* test workflow
* test workflow
* test workflow
* test workflow
* on tags
* createResource
* createResource
* createResource2
* typescript support
* templates
* include version
