-
Some background jobs might crash for some reason (e.g. synapse not being available). We need to test that they get actually rescheduled after some time
-
Triggering job generation via Comms Radio causes job generation to happen in parallel when multiple stations are listed. This happens for stations that are located close together, like Machine Factory…
-
### Environment
* Nautobot version (Docker tag too if applicable): 2.2.5
* Python version: 3.9.19
* Database platform, version: postgres, 13.15
* Middleware(s): nautobot_ssot
I am trying to…
-
### Describe the bug
I encountered the problem that my jobs are not properly killed when running on `localhost` using the `core.direct` scheduler. For example, when I kill a `PwCalculation`, the corr…
-
Hi everyone,
correct me please if I'm wrong, but out of the blue, I didn't find an acceptable way to run jobs inside a TransactionScope...
I mean, if you have a look at [CoreBackgroundJobPerfor…
-
I sent a job today, 7-19-24. However, when I look at the returned API response for **Jobs**, the created_at field shows 7-12-24. This bug is affecting all the returned items; the created_at timestamp …
-
**Description**
The issue arises when using the workspace_client.jobs.create() function to create a job with specific cluster settings. The function does not accept both node_type_id and instance_poo…
-
A user reported getting the big blue Dokku error page:
> We're sorry, but something went wrong
> If you are the application owner please check the logs for more information.
when trying to acces…
-
## Enhancement
Currently the context usage is a bit of messy. One problem is https://github.com/pingcap/tidb/issues/56017 and I think a better context usage and cancellation will solve it. After a …
-
Some Jobs APIs have a lot of required and optional parameters that might be better suited to be provided in an interface.
_Originally raised by @zFernand0 in https://github.com/zowe/zowe-cli/pull/2…