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
if the first line return "error" it is more possiable always return "error" after sleep 2s
which will always yield status code 500 of response.
For example, some score of rnn decode may be inf.
This may occur when the downstream tag fitting process not stable (as normal training of
some neutral network)
Users should have a monitor of this incremental training process. If the network fitted bad should
Terminated before going wrong way too long.
Only return status 500 with frontend blocked seems not appropriate.
So i think should add a realtime validation interface by client.
The text was updated successfully, but these errors were encountered:
the code seems have many
if the first line return "error" it is more possiable always return "error" after sleep 2s
which will always yield status code 500 of response.
For example, some score of rnn decode may be inf.
This may occur when the downstream tag fitting process not stable (as normal training of
some neutral network)
Users should have a monitor of this incremental training process. If the network fitted bad should
Terminated before going wrong way too long.
Only return status 500 with frontend blocked seems not appropriate.
So i think should add a realtime validation interface by client.
The text was updated successfully, but these errors were encountered: