-
Notifications
You must be signed in to change notification settings - Fork 87
[Issue #240] bugfix #299
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Issue #240] bugfix #299
Conversation
…xectuion of async task, save the error message and return it when requested. Also handle the SIGPIPE signal.
int | ||
fio_check_error_fd_gz(gzFile f, char **errmsg) | ||
{ | ||
if (f && ((size_t)f & FIO_GZ_REMOTE_MARKER)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you please add a comment to FIO_GZ_REMOTE_MARKER definition?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure
|
||
//TODO: should we reset the tainted state ? | ||
// pg_free(async_errormsg); | ||
// async_errormsg = NULL; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't see, where we reset async_errormsg.
How would we handle several consecutive errors?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We don`t. Currently it is assumed, that a first error is the last error.
Merged |
When remote agent encounters an error condition during exectuion of async task, save the error message and return it when requested. Also handle the SIGPIPE signal.