Error handling in post publication script #135
Merged
Conversation
This file contains 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
karenc
changed the title
karenc
force-pushed
the
post-publication-error-handling
branch
from
12e765e
to
83cbb5e
Compare
karenc
force-pushed
the
post-publication-error-handling
branch
3 times, most recently
from
d3c0b55
to
0cbdffb
Compare
Some errors were not getting caught causing some collections to be in the "processing" state.
Used to log the state of books processed by the post publication worker.
Used to log the state of books processed by the post publication worker.
Admins can go to `/a/post-publications` to view the status of books that are being processed and were processed by the post publication worker.
|
Screenshot of the admin interface:
|
karenc
force-pushed
the
post-publication-error-handling
branch
from
0cbdffb
to
be78ee8
Compare
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.
Some errors were not getting caught causing some collections to be in
the "processing" state.