Skip to content
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

Jira does not load up, error "http: read on closed response body" #1070

Closed
orthdron opened this issue Mar 25, 2021 · 5 comments · Fixed by #1071
Closed

Jira does not load up, error "http: read on closed response body" #1070

orthdron opened this issue Mar 25, 2021 · 5 comments · Fixed by #1071
Labels
🐛 bug "Houston, we've had a problem."

Comments

@orthdron
Copy link

Version: 0.36.0 (2021-03-23T12:48:25+00:00)
OS: macOS

Jira does not load up, with the error http: read on closed response body

Config for JIRA:

jira:
   apiKey: "<REDACTED>"
   colors:
     rows:
       even: "lightblue"
       odd: "white"
   domain: "https://<REDACTED>.atlassian.net"
   email: "<REDACTED>"
   enabled: true
   position:
     top: 3
     left: 2
     height: 3
     width: 2
   refreshInterval: 900
   project: ["<REDACTED>"]
   username: "<REDACTED>"
   verifyServerCertificate: true
@senorprogrammer senorprogrammer added the 🐛 bug "Houston, we've had a problem." label Mar 26, 2021
@senorprogrammer
Copy link
Collaborator

Sounds like a similar issue that's affected a few other modules. Solution should be the same. I'll try and patch this this weekend.

@orthdron
Copy link
Author

orthdron commented Mar 26, 2021 via email

@senorprogrammer
Copy link
Collaborator

Fixed. Will go out with the next release.

@superlevure
Copy link

Could we have a release to benefit from this fix now?

Thanks for the great tool

@senorprogrammer
Copy link
Collaborator

For sure, that's a good idea! Done: https://github.com/wtfutil/wtf/releases/tag/v0.37.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛 bug "Houston, we've had a problem."
Development

Successfully merging a pull request may close this issue.

3 participants