kaxil edited a comment on pull request #19637:
URL: https://github.com/apache/airflow/pull/19637#issuecomment-972723105


   > Deserialization problems seems to be a well known and often occuring 
situation. Seeing a cryptic error - rather than reassuring message and helpful 
instuctions - creates the impression that Airlfow is not an enterprise-grade 
software. Those kind of errors are very bad - because there are only two 
options when you see it: either "I screwed up" or "they screwed up". Both 
thoughts have bad consequences.
   
   Can you give some examples of this please except for the 2.2.0 issue where 
just reserializing would have helped
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to