-
Notifications
You must be signed in to change notification settings - Fork 113
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
Request: close outdated issues #197
Comments
Thanks! You're absolutely right, I would need to do a major cleanup of the open issues/PRs, but I've unfortunately been a bit to busy to track that well (and it doesn't seem to get better). The three issues you linked were indeed all solved; thanks for pointing that out, and I appreciate that you took the time to help dig these up and close them! |
No problem! FYI those came from just a cursory search through the issues -- I'd be happy to go through the rest and see if anything else looks ready to close. |
Here's the first batch: Appears to be already solved by a PR:Super old/probably no longer relevant:Long time with no response from originator:#117 Solved by originatorMisc#135: I think this one was solved by PR #191 #143 is possibly done? not sure, please take a look |
Thank you so much @thomasjm! I was able to close most of these and added comments to others. I'm currently vacationing in Mexico but will try to do another pass soon. |
This can be closed now. |
Thanks for the great library!
I was wondering if it would be possible to close some of the outstanding issues on this library if they're believed to have been solved. There are a number of scary-looking outstanding issues, such as
#72
#124
#194
but when I look at these it seems like PRs have already been merged to fix them.
There are also some random bug and feature requests going all the way back to 2011. All together, these issues make it hard to look at the issue tracker and see what is actually a real issue/priority that I should worry about when using this library.
The text was updated successfully, but these errors were encountered: