This repository was archived by the owner on Dec 28, 2025. It is now read-only.
This repository was archived by the owner on Dec 28, 2025. It is now read-only.
[Improvement] Message Hub Error Caught #1
Description
What is the feature?
The message hub receives critical Tensor input and displays them. In it's procedure, the item method is called when handling values (can be lr, loss, metrics, time, epoch, etc...) When there exists some invalid values, the message simply crashes the process as there is an assertion.
Considering the user is easy to print something bad to the message hub at ANY code line, a more robust way is to should a warning and returns the value and see if the directly returned value can be successfully processed by outer functions.
Any other context?
No response