Skip to content

Conversation

@gsmolk
Copy link
Contributor

@gsmolk gsmolk commented Jan 22, 2021

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.

…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))
Copy link
Contributor

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?

Copy link
Contributor Author

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;
Copy link
Contributor

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?

Copy link
Contributor Author

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.

@gsmolk
Copy link
Contributor Author

gsmolk commented Jan 26, 2021

Merged

@gsmolk gsmolk closed this Jan 26, 2021
@gsmolk gsmolk deleted the issue_240 branch January 26, 2021 13:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants