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 Jan 13, 2021. It is now read-only.
Currently some things that aren't error are propagated as if they are within the code. For example, if an object, described in a bundle, exists but is marked for deletion that is reported as a terminal error in the resource's status. This is not an error, this should be reflected as "in progress" situation. There are more things like that. In general, more things should be propagated as just information about a resource, not as an error return value. Error return values should be used for true errors like unexpected failures, I/O failures, so on.
The text was updated successfully, but these errors were encountered:
Currently some things that aren't error are propagated as if they are within the code. For example, if an object, described in a bundle, exists but is marked for deletion that is reported as a terminal error in the resource's status. This is not an error, this should be reflected as "in progress" situation. There are more things like that. In general, more things should be propagated as just information about a resource, not as an error return value. Error return values should be used for true errors like unexpected failures, I/O failures, so on.
The text was updated successfully, but these errors were encountered: