Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Allow knowing which jobs are running (and not just submitted/pending and paused)
See original GitHub issueIt seems like we can pretty easily know by looking at the job.next_run_time whether a job is paused or not but it is really hard to know if a job is running or not (as far as a I can tell) since there is no apparent job state that is connected to a job saying the job is actively running (the event notification system is not reliable enough to do this, as it can be fired out of order).
So this is more of a feature request to have such a capability…
If more details are needed (or I can suggest some ideas on how to do it or maybe even a PR).
Issue Analytics
- State:
- Created 5 years ago
- Reactions:11
- Comments:14 (6 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
+1
I’m trying to track state through event handlers, but so far keep running into problems with it (including #356). Whatever API changes are needed, I think they’ll be worth it. This is a capability that any application with a robust UI will need to have.
I can not agreen with you any more, I want to show users the state of current job …