We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We got this error when using the client:
unexpected EOF: file already closed
We don't expect to see file already closed errors.
file already closed
This is sporadic and can happen when reading from the http response body after a valid response status was received.
The root cause here it's possible that an error is returned while reading the response body, like here:
go-jira/cloud/jira.go
Lines 249 to 250 in 50d59fe
So while decoding there is a network error and the read fails, not the body is closed on defer.
Than the error is passed to:
go-jira/cloud/issue.go
Line 1084 in 50d59fe
And there, it is expected that the body was not closed/read already, so it tries to read again from the body:
go-jira/cloud/error.go
Lines 25 to 26 in 50d59fe
As a result we get a confusing error.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
What happened?
We got this error when using the client:
What did you expect to happen?
We don't expect to see
file already closed
errors.How can we reproduce it (as minimally and precisely as possible)?
This is sporadic and can happen when reading from the http response body after a valid response status was received.
The root cause here it's possible that an error is returned while reading the response body, like here:
go-jira/cloud/jira.go
Lines 249 to 250 in 50d59fe
So while decoding there is a network error and the read fails, not the body is closed on defer.
Than the error is passed to:
go-jira/cloud/issue.go
Line 1084 in 50d59fe
And there, it is expected that the body was not closed/read already, so it tries to read again from the body:
go-jira/cloud/error.go
Lines 25 to 26 in 50d59fe
As a result we get a confusing error.
The text was updated successfully, but these errors were encountered: