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
According to the documentation, the "bg_error" status is called with a non-OK status and the callback can set this to an "OK" value to suppress the error. By code inspection, it appears that it is always called with an OK status (s is not set to the new error) and that status is never checked or used as part of the return status (s is not checked for).
Expected behavior
Actual behavior
Steps to reproduce the behavior
The error_handler_fs_test shows calls to this handler passing in OK even when the underlyin Status is not OK.
The text was updated successfully, but these errors were encountered:
This was found by code inspection.
According to the documentation, the "bg_error" status is called with a non-OK status and the callback can set this to an "OK" value to suppress the error. By code inspection, it appears that it is always called with an OK status (s is not set to the new error) and that status is never checked or used as part of the return status (s is not checked for).
Expected behavior
Actual behavior
Steps to reproduce the behavior
The error_handler_fs_test shows calls to this handler passing in OK even when the underlyin Status is not OK.
The text was updated successfully, but these errors were encountered: