Skip to content
This repository has been archived by the owner on Sep 20, 2024. It is now read-only.

Deadline: better logging for DL webservice failures #3694

Merged
merged 4 commits into from
Aug 22, 2022

Conversation

kalisp
Copy link
Member

@kalisp kalisp commented Aug 18, 2022

Brief description

It seems that DL webservice can return broken json payload even if response.ok. Safer and saner report.

Additional info

Without it error message is a bit vague:
Screenshot 2022-08-18 171733

Not sure how to test it properly. I would just try to send regular DL submission from AE (or Harmony).

In some specific cases DL sends broken json payload even if response.ok. Handle parsing of broken json better.
In some specific cases DL sends broken json payload even if response.ok. Handle parsing of broken json better.
@kalisp kalisp added the sponsored Client endorsed or requested label Aug 18, 2022
@kalisp kalisp self-assigned this Aug 18, 2022
@BigRoy
Copy link
Collaborator

BigRoy commented Aug 18, 2022

It's a tricky one. It's hard to tell what the culprit of the issue originally was and whether this PR will actually avoid the same confusion.

The fact that this now also raises its own replacement error I wonder whether it might make it harder to debug in the future than just re-raising the error with raise or alike. (Or at least having something that will follow that traceback?)

Warning should print exception.
JSONDecoder is not in Pype2
Co-authored-by: Jakub Trllo <43494761+iLLiCiTiT@users.noreply.github.com>
@kalisp kalisp requested a review from iLLiCiTiT August 19, 2022 12:03
@kalisp kalisp merged commit 370c7f8 into develop Aug 22, 2022
@kalisp kalisp deleted the chore/better_logging_in_DL branch August 22, 2022 07:44
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
sponsored Client endorsed or requested
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants