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
A common pattern seems to be including progress information in a job's output, and checking that during a job's lifetime.
Having only an output field to store this in sometimes causes issues, e.g.:
output might be huge, and fetching large output repeatedly to check progress can be inefficient
more complex to handle in languages where JSON is mapped to structs/objects etc. (often either a compount type or tagged union is used to handle a progress data structure and a final output data structure)
Adding a new optional field might simplify this.
The text was updated successfully, but these errors were encountered:
A common pattern seems to be including progress information in a job's output, and checking that during a job's lifetime.
Having only an output field to store this in sometimes causes issues, e.g.:
Adding a new optional field might simplify this.
The text was updated successfully, but these errors were encountered: