You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 14, 2019. It is now read-only.
Currently, the bot assumes that common fields will always be available for parsing, but that's not the case. Instead, the bot should ignore the field if it's null.
The text was updated successfully, but these errors were encountered:
Do you have any more info on this one? I'm not sure what it's referring to and can only find one place where null kind of misbehaves. I'm guessing this got fixed incidentally when you did all the work on the interview.
It might have been mostly fixed, but I did see this today. My previous standup was a simple "OOO" one, and the previous blocker was listed as null. That might be the sole remaining thing.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Currently, the bot assumes that common fields will always be available for parsing, but that's not the case. Instead, the bot should ignore the field if it's null.
The text was updated successfully, but these errors were encountered: