Seems like most of the pip bugmail I get now is lockbot messages telling me that a bug that hasn't received any discussion for a long time now can't have any more discussion. Is that really needed? The github UI shows the lock status of bugs itself... -Rob
The bot has just been enabled, and it's catching up on historical bugs (which can't be done all in one go, as rate limits would hit us). Hopefully it should die down in a few days. Whether there's a way to tell github not to send such notifications, or whether it's possible for us to configure the bot to lock the thread but not add a comment, I don't know. Paul On Sun, 2 Jun 2019 at 09:12, Robert Collins <robertc@robertcollins.net> wrote:
Seems like most of the pip bugmail I get now is lockbot messages telling me that a bug that hasn't received any discussion for a long time now can't have any more discussion. Is that really needed? The github UI shows the lock status of bugs itself...
-Rob -- Distutils-SIG mailing list -- distutils-sig@python.org To unsubscribe send an email to distutils-sig-leave@python.org https://mail.python.org/mailman3/lists/distutils-sig.python.org/ Message archived at https://mail.python.org/archives/list/distutils-sig@python.org/message/2Z4TH...
One thought - is it possible in github to subscribe to "everything that isn't closed"? I couldn't see such an issue but that would (a) let me ignore the lockbot messages, and (b) let me ignore close threads so I wouldn't even need lockbot. Paul On Sun, 2 Jun 2019 at 12:26, Paul Moore <p.f.moore@gmail.com> wrote:
The bot has just been enabled, and it's catching up on historical bugs (which can't be done all in one go, as rate limits would hit us). Hopefully it should die down in a few days.
Whether there's a way to tell github not to send such notifications, or whether it's possible for us to configure the bot to lock the thread but not add a comment, I don't know. Paul
On Sun, 2 Jun 2019 at 09:12, Robert Collins <robertc@robertcollins.net> wrote:
Seems like most of the pip bugmail I get now is lockbot messages telling me that a bug that hasn't received any discussion for a long time now can't have any more discussion. Is that really needed? The github UI shows the lock status of bugs itself...
-Rob -- Distutils-SIG mailing list -- distutils-sig@python.org To unsubscribe send an email to distutils-sig-leave@python.org https://mail.python.org/mailman3/lists/distutils-sig.python.org/ Message archived at https://mail.python.org/archives/list/distutils-sig@python.org/message/2Z4TH...
So the API endpoint to lock an issue absolutely does not require comments on each thing. I think the idea is probably that it's easier to understand that this was an automated process doing this rather than being used in the vein of GitHub's moderation (which doesn't account for anything other than abuse). For those who are interested, the lock API is https://developer.github.com/v3/issues/#lock-an-issue On Sun, Jun 2, 2019 at 6:40 AM Paul Moore <p.f.moore@gmail.com> wrote:
One thought - is it possible in github to subscribe to "everything that isn't closed"? I couldn't see such an issue but that would (a) let me ignore the lockbot messages, and (b) let me ignore close threads so I wouldn't even need lockbot.
Paul
On Sun, 2 Jun 2019 at 12:26, Paul Moore <p.f.moore@gmail.com> wrote:
The bot has just been enabled, and it's catching up on historical bugs (which can't be done all in one go, as rate limits would hit us). Hopefully it should die down in a few days.
Whether there's a way to tell github not to send such notifications, or whether it's possible for us to configure the bot to lock the thread but not add a comment, I don't know. Paul
On Sun, 2 Jun 2019 at 09:12, Robert Collins <robertc@robertcollins.net> wrote:
Seems like most of the pip bugmail I get now is lockbot messages telling me that a bug that hasn't received any discussion for a long time now can't have any more discussion. Is that really needed? The github UI shows the lock status of bugs itself...
-Rob -- Distutils-SIG mailing list -- distutils-sig@python.org To unsubscribe send an email to distutils-sig-leave@python.org https://mail.python.org/mailman3/lists/distutils-sig.python.org/ Message archived at https://mail.python.org/archives/list/distutils-sig@python.org/message/2Z4TH...
-- Distutils-SIG mailing list -- distutils-sig@python.org To unsubscribe send an email to distutils-sig-leave@python.org https://mail.python.org/mailman3/lists/distutils-sig.python.org/ Message archived at https://mail.python.org/archives/list/distutils-sig@python.org/message/ROZ4Z...
In the lock.yml you can specify to not leave a comment upon locking. See https://github.com/microsoft/vscode-python/blob/master/.github/lock.yml as an example. On Sun, Jun 2, 2019 at 5:20 AM Ian Stapleton Cordasco < graffatcolmingov@gmail.com> wrote:
So the API endpoint to lock an issue absolutely does not require comments on each thing. I think the idea is probably that it's easier to understand that this was an automated process doing this rather than being used in the vein of GitHub's moderation (which doesn't account for anything other than abuse).
For those who are interested, the lock API is https://developer.github.com/v3/issues/#lock-an-issue
On Sun, Jun 2, 2019 at 6:40 AM Paul Moore <p.f.moore@gmail.com> wrote:
One thought - is it possible in github to subscribe to "everything that isn't closed"? I couldn't see such an issue but that would (a) let me ignore the lockbot messages, and (b) let me ignore close threads so I wouldn't even need lockbot.
Paul
On Sun, 2 Jun 2019 at 12:26, Paul Moore <p.f.moore@gmail.com> wrote:
The bot has just been enabled, and it's catching up on historical bugs (which can't be done all in one go, as rate limits would hit us). Hopefully it should die down in a few days.
Whether there's a way to tell github not to send such notifications, or whether it's possible for us to configure the bot to lock the thread but not add a comment, I don't know. Paul
On Sun, 2 Jun 2019 at 09:12, Robert Collins <robertc@robertcollins.net>
wrote:
Seems like most of the pip bugmail I get now is lockbot messages telling me that a bug that hasn't received any discussion for a long time now can't have any more discussion. Is that really needed? The github UI shows the lock status of bugs itself...
-Rob -- Distutils-SIG mailing list -- distutils-sig@python.org To unsubscribe send an email to distutils-sig-leave@python.org https://mail.python.org/mailman3/lists/distutils-sig.python.org/ Message archived at
https://mail.python.org/archives/list/distutils-sig@python.org/message/2Z4TH... -- Distutils-SIG mailing list -- distutils-sig@python.org To unsubscribe send an email to distutils-sig-leave@python.org https://mail.python.org/mailman3/lists/distutils-sig.python.org/ Message archived at https://mail.python.org/archives/list/distutils-sig@python.org/message/ROZ4Z... -- Distutils-SIG mailing list -- distutils-sig@python.org To unsubscribe send an email to distutils-sig-leave@python.org https://mail.python.org/mailman3/lists/distutils-sig.python.org/ Message archived at https://mail.python.org/archives/list/distutils-sig@python.org/message/KXWKP...
On Tue, 4 Jun 2019 at 1:00 AM, Brett Cannon <brett@python.org> wrote:
In the lock.yml you can specify to not leave a comment upon locking. See https://github.com/microsoft/vscode-python/blob/master/.github/lock.yml as an example.
We did this yesterday. Sorry for the email spam folks! I completely misjudged how long the bot would take to catch up to the ridiculous amount of closed old issues on the tracker, due to rate limits. If it's any comfort, I had to face the same spam. 🙂 If there are any concerns other than email spam, please comment on https://github.com/pypa/pip/issues/6563 and not here. Thanks, Pradyun
Another issue with the lockbot: I was watching specific issues and PRs because they're important to me (as a packager and a maintainer of numpy.distutils. The locking has made it very hard to now follow any updates. Even if someone opens a new issue or PR to continue where a locked one, there's no way for anyone but maintainers to comment on the original issue (which isn't likely to happen consistently) to alert me of that. And I really don't want to watch the whole repo, that's many times more noisy. Ralf On Sun, Jun 2, 2019 at 1:40 PM Paul Moore <p.f.moore@gmail.com> wrote:
One thought - is it possible in github to subscribe to "everything that isn't closed"? I couldn't see such an issue but that would (a) let me ignore the lockbot messages, and (b) let me ignore close threads so I wouldn't even need lockbot.
Paul
On Sun, 2 Jun 2019 at 12:26, Paul Moore <p.f.moore@gmail.com> wrote:
The bot has just been enabled, and it's catching up on historical bugs (which can't be done all in one go, as rate limits would hit us). Hopefully it should die down in a few days.
Whether there's a way to tell github not to send such notifications, or whether it's possible for us to configure the bot to lock the thread but not add a comment, I don't know. Paul
On Sun, 2 Jun 2019 at 09:12, Robert Collins <robertc@robertcollins.net>
wrote:
Seems like most of the pip bugmail I get now is lockbot messages telling me that a bug that hasn't received any discussion for a long time now can't have any more discussion. Is that really needed? The github UI shows the lock status of bugs itself...
-Rob -- Distutils-SIG mailing list -- distutils-sig@python.org To unsubscribe send an email to distutils-sig-leave@python.org https://mail.python.org/mailman3/lists/distutils-sig.python.org/ Message archived at
https://mail.python.org/archives/list/distutils-sig@python.org/message/2Z4TH... -- Distutils-SIG mailing list -- distutils-sig@python.org To unsubscribe send an email to distutils-sig-leave@python.org https://mail.python.org/mailman3/lists/distutils-sig.python.org/ Message archived at https://mail.python.org/archives/list/distutils-sig@python.org/message/ROZ4Z...
participants (6)
-
Brett Cannon -
Ian Stapleton Cordasco -
Paul Moore -
Pradyun Gedam -
Ralf Gommers -
Robert Collins