[Docs] Improve error 'NoneType' object has no attribute 'blob'

[brunomorampc]

Description

I get sometimes this error

AttributeError: Failed to convert inputs of task 
'path.to.some.funciton':
'NoneType' object has no attribute 'blob'

I was wondering if it is possible to improve the error message as it is not clear which input has a NoneType. Also I don't know if this comes from the fact that it cannot deserialize or if actually the input is None.

Are you sure this issue hasn't been raised already?

• Yes

Have you read the Code of Conduct?

• Yes

[welcome]

Thank you for opening your first issue here! 🛠

[runllm]

The error message you're encountering, 'NoneType' object has no attribute 'blob', suggests that Flyte is attempting to access an attribute on a None object, likely during the deserialization of task inputs. This can occur if an expected input is missing or if there is a mismatch in the expected data type.

To improve the error message, Flyte's error handling could be enhanced to include more context, such as the specific input name and the expected type. This would help users identify the source of the issue more easily. According to Flyte's GitHub issue #5439, Flyte relaunches a new task when it fails to deserialize the input, which might be related to your issue.

Would you like more details on how to handle this error or improve error messages in Flyte?

Sources:

• Flyte's GitHub issue #5439

---

This is an AI-generated response and your feedback is appreciated! Please leave a 👍 if this is helpful and 👎 if it is not.

Mention @RunLLM to ask follow-up questions. See runllm.com for more!

[0yukali0]

#take

[eapolinario]

@brunomorampc , can you give us a bit more detail? Maybe a small repro?

@0yukali0 , were you able to find out what's wrong?

[0yukali0]

No, i haven't.
I don't think that parameters in "pyflyte run " will be None type because **dict should not generate a None type for variable.
I will trace codes whether some cases trigger the None type in the process for blob type.

[github-actions]

"Hello 👋, this issue has been inactive for over 90 days. To help maintain a clean and focused backlog, we'll be marking this issue as stale and will close the issue if we detect no activity in the next 7 days. Thank you for your contribution and understanding! 🙏"

[github-actions]

Hello 👋, this issue has been inactive for over 90 days and hasn't received any updates since it was marked as stale. We'll be closing this issue for now, but if you believe this issue is still relevant, please feel free to reopen it. Thank you for your contribution and understanding! 🙏