Closed mpass99 closed 2 months ago
Once we merged and deployed this issue, we should probably follow-up and sort / merge some of the Sentry issues, too. Can you please do so (since you know better which ones are related)?
I just deployed the latest version of Poseidon to production and staging, allowing us to take care of the Sentry issues (merging, ...).
I just resolved POSEIDON-3W and POSEIDON-3V. This allows us to notice when these high-level issues reoccur because of a different low-level error.
I hope to see another unexpected EOF
error soon creating its own Sentry issue so we can verify that the error check of this PR is working.
Thanks! As mentioned in the ticket #589, we need to make some further adjustments before resolving POSEIDON-3W again (since it was regressed).
by throwing the log warning at the common level of the Execute call and not at multiple places relying on it.
Related to #589