-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
replicator http usage logger crashes when canceling transient (_replicate) jobs #4760
Labels
Comments
nickva
added a commit
that referenced
this issue
Sep 14, 2023
Previously when transient replication jobs were canceled their `#rep` record's source and target fields would be `undefined`. That was accounted for in the http usage logger when it's enabled and resulted in a badrecord 500 error. Fix: #4760
Example of how it fails:
|
nickva
added a commit
that referenced
this issue
Sep 14, 2023
Previously when transient replication jobs were canceled their `#rep` record's source and target fields would be `undefined`. That was accounted for in the http usage logger when it's enabled and resulted in a badrecord 500 error. Fix: #4760
nickva
added a commit
that referenced
this issue
Sep 14, 2023
Previously when transient replication jobs were canceled their `#rep` record's source and target fields would be `undefined`. That was accounted for in the http usage logger when it's enabled and resulted in a badrecord 500 error. Fix: #4760
nickva
added a commit
that referenced
this issue
Sep 14, 2023
Previously when transient replication jobs were canceled their `#rep` record's source and target fields would be `undefined`. That was accounted for in the http usage logger when it's enabled and resulted in a badrecord 500 error. Fix: #4760
nickva
added a commit
that referenced
this issue
Sep 14, 2023
Previously when transient replication jobs were canceled their `#rep` record's source and target fields would be `undefined`. That was accounted for in the http usage logger when it's enabled and resulted in a badrecord 500 error. Fix: #4760
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The text was updated successfully, but these errors were encountered: