docs: show how to query a Job by id with a redis instance#525
Open
SAY-5 wants to merge 1 commit into
Open
Conversation
|
Codecov Report✅ All modified and coverable lines are covered by tests. @@ Coverage Diff @@
## main #525 +/- ##
==========================================
- Coverage 96.27% 95.85% -0.43%
==========================================
Files 11 11
Lines 1074 1085 +11
Branches 209 144 -65
==========================================
+ Hits 1034 1040 +6
- Misses 19 24 +5
Partials 21 21 see 1 file with indirect coverage changes Continue to review full report in Codecov by Sentry.
🚀 New features to boost your workflow:
|
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
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.
Per samuelcolvin's note on #240: "yes it's very simple, you also need to pass a redis instance ... PR welcome to add this to the docs." Adds a short paragraph and an
examples/job_by_id.pysnippet under the existing "Job Results" section so users can look up a job from its id and see what happens when no such job exists (JobStatus.not_found).Closes #240