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? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
@FiloSottile requested issue #24050 to be considered for backport to the next 1.9 minor release.
@gopherbot please open backport tracking issues. This might be a 1.10 regression, or also a 1.9 issue.
The text was updated successfully, but these errors were encountered:
-timeout
@ianlancetaylor which CLs would need to be cherry-picked for this to be fixed? Seems that the original issue isn't.
Sorry, something went wrong.
I don't actually know what's going on with that issue. As far as I know it isn't fixed so there is no CL to backport.
Closing this issue. The original issue is not fixed. There is no reason to have an issue opened for a backport of an issue that is not fixed.
No branches or pull requests
@FiloSottile requested issue #24050 to be considered for backport to the next 1.9 minor release.
The text was updated successfully, but these errors were encountered: