Recently it seems that when a PR linked to a bpo issue is merged, no note of this event is made in the bpo issue. Look at https://bugs.python.org/issue43933 for example. There are notes for the first two merged PRs (25717 and 25719), at https://bugs.python.org/issue43933#msg392343 and the next message. But I cannot find a similar note for the third PR, 26054, which is also merged.
I recall seeing this for other recent issues as well. Did some piece of automation recently break? (Could it have to do with the master->main move?)
I've noticed this too. I'm pretty sure it predates the master -> main change.
Eric
On 5/12/2021 10:22 AM, Guido van Rossum wrote:
Recently it seems that when a PR linked to a bpo issue is merged, no note of this event is made in the bpo issue. Look at https://bugs.python.org/issue43933 https://bugs.python.org/issue43933 for example. There are notes for the first two merged PRs (25717 and 25719), at https://bugs.python.org/issue43933#msg392343 https://bugs.python.org/issue43933#msg392343 and the next message. But I cannot find a similar note for the third PR, 26054, which is also merged.
I recall seeing this for other recent issues as well. Did some piece of automation recently break? (Could it have to do with the master->main move?) -- --Guido (mobile)
python-committers mailing list -- python-committers@python.org To unsubscribe send an email to python-committers-leave@python.org https://mail.python.org/mailman3/lists/python-committers.python.org/ Message archived at https://mail.python.org/archives/list/python-committers@python.org/message/M... Code of Conduct: https://www.python.org/psf/codeofconduct/
On Wed, May 12, 2021 at 07:22:52AM -0700, Guido van Rossum wrote:
I recall seeing this for other recent issues as well. Did some piece of automation recently break? (Could it have to do with the master->main move?)
Looks like the link is broken only for "main" branch. It works for 3.10 (and possibly) other branches.
-- Senthil
On Wed, May 12, 2021 at 9:23 AM Guido van Rossum guido@python.org wrote:
(Could it have to do with the master->main move?)
I think this is likely; we do still get messages from backport PRs. I'm not sure what service is actually creating the messages, though.
Is the bpo message posted by the CPython emailer webhook service? If so, I might be able to see logs on Heroku.
On Wed., May 12, 2021, 8:15 a.m. Zachary Ware, zachary.ware+pydev@gmail.com wrote:
On Wed, May 12, 2021 at 9:23 AM Guido van Rossum guido@python.org wrote:
(Could it have to do with the master->main move?)
I think this is likely; we do still get messages from backport PRs. I'm not sure what service is actually creating the messages, though.
-- Zach _______________________________________________ python-committers mailing list -- python-committers@python.org To unsubscribe send an email to python-committers-leave@python.org https://mail.python.org/mailman3/lists/python-committers.python.org/ Message archived at https://mail.python.org/archives/list/python-committers@python.org/message/2... Code of Conduct: https://www.python.org/psf/codeofconduct/
Any update on this issue? Nobody recalls what code and service sends a comment to bugs.python.org when a commit is merged?
Victor
On Wed, May 12, 2021 at 4:23 PM Guido van Rossum guido@python.org wrote:
Recently it seems that when a PR linked to a bpo issue is merged, no note of this event is made in the bpo issue. Look at https://bugs.python.org/issue43933 for example. There are notes for the first two merged PRs (25717 and 25719), at https://bugs.python.org/issue43933#msg392343 and the next message. But I cannot find a similar note for the third PR, 26054, which is also merged.
I recall seeing this for other recent issues as well. Did some piece of automation recently break? (Could it have to do with the master->main move?)
--Guido (mobile) _______________________________________________ python-committers mailing list -- python-committers@python.org To unsubscribe send an email to python-committers-leave@python.org https://mail.python.org/mailman3/lists/python-committers.python.org/ Message archived at https://mail.python.org/archives/list/python-committers@python.org/message/M... Code of Conduct: https://www.python.org/psf/codeofconduct/
I'm guessing we have to escalate this to Ee.
On Mon, May 17, 2021 at 2:58 PM Victor Stinner vstinner@python.org wrote:
Any update on this issue? Nobody recalls what code and service sends a comment to bugs.python.org when a commit is merged?
Victor
On Wed, May 12, 2021 at 4:23 PM Guido van Rossum guido@python.org wrote:
Recently it seems that when a PR linked to a bpo issue is merged, no
note of this event is made in the bpo issue. Look at https://bugs.python.org/issue43933 for example. There are notes for the first two merged PRs (25717 and 25719), at
https://bugs.python.org/issue43933#msg392343 and the next message. But
I cannot find a similar note for the third PR, 26054, which is also merged.
I recall seeing this for other recent issues as well. Did some piece of
automation recently break? (Could it have to do with the master->main move?)
-- --Guido (mobile) _______________________________________________ python-committers mailing list -- python-committers@python.org To unsubscribe send an email to python-committers-leave@python.org https://mail.python.org/mailman3/lists/python-committers.python.org/ Message archived at
https://mail.python.org/archives/list/python-committers@python.org/message/M...
Code of Conduct: https://www.python.org/psf/codeofconduct/
-- Night gathers, and now my watch begins. It shall not end until my death.
On Mon, May 17, 2021 at 4:58 PM Victor Stinner vstinner@python.org wrote:
Any update on this issue? Nobody recalls what code and service sends a comment to bugs.python.org when a commit is merged?
I might have found it; I at least opened https://github.com/psf/bpo-roundup/pull/1 against what I found :)
I'm not getting emails about updates to bpo issues I'm nosying anymore.
On Mon, May 17, 2021 at 11:33 PM Zachary Ware zach@python.org wrote:
On Mon, May 17, 2021 at 4:58 PM Victor Stinner vstinner@python.org wrote:
Any update on this issue? Nobody recalls what code and service sends a comment to bugs.python.org when a commit is merged?
I might have found it; I at least opened https://github.com/psf/bpo-roundup/pull/1 against what I found :) _______________________________________________ python-committers mailing list -- python-committers@python.org To unsubscribe send an email to python-committers-leave@python.org https://mail.python.org/mailman3/lists/python-committers.python.org/ Message archived at https://mail.python.org/archives/list/python-committers@python.org/message/2... Code of Conduct: https://www.python.org/psf/codeofconduct/
On Tue, May 18, 2021 at 12:33 AM Zachary Ware zach@python.org wrote:
I might have found it; I at least opened https://github.com/psf/bpo-roundup/pull/1 against what I found :)
Sadly, commits in the main branch are still not logged to bugs.python.org, see: https://github.com/psf/bpo-roundup/pull/1#issuecomment-847754199
Victor
Night gathers, and now my watch begins. It shall not end until my death.
I think this seems fixed now? At least I've been getting emails about commits in main for bpo issues I'm following.
On Tue, May 25, 2021 at 3:33 AM Victor Stinner vstinner@python.org wrote:
On Tue, May 18, 2021 at 12:33 AM Zachary Ware zach@python.org wrote:
I might have found it; I at least opened https://github.com/psf/bpo-roundup/pull/1 against what I found :)
Sadly, commits in the main branch are still not logged to bugs.python.org, see: https://github.com/psf/bpo-roundup/pull/1#issuecomment-847754199
Victor
Night gathers, and now my watch begins. It shall not end until my death. _______________________________________________ python-committers mailing list -- python-committers@python.org To unsubscribe send an email to python-committers-leave@python.org https://mail.python.org/mailman3/lists/python-committers.python.org/ Message archived at https://mail.python.org/archives/list/python-committers@python.org/message/F... Code of Conduct: https://www.python.org/psf/codeofconduct/
I confirm that commits merged in 3.9, 3.10 and main branches are logged again in bugs.python.org. Thanks to everyone who helped to solve this issue!
Victor
Night gathers, and now my watch begins. It shall not end until my death.
I'm not getting anything at all from bpo for about a week now. Maybe it had enough of me.
On Thu, May 27, 2021 at 6:01 PM Victor Stinner vstinner@python.org wrote:
I confirm that commits merged in 3.9, 3.10 and main branches are logged again in bugs.python.org. Thanks to everyone who helped to solve this issue!
On Thu, May 27, 2021 at 8:46 PM Irit Katriel via python-committers python-committers@python.org wrote:
I'm not getting anything at all from bpo for about a week now. Maybe it had enough of me.
That has nothing to do with the BPO issue we have been talking about. The infra team is the best place to report email delivery problems.
--Berker
Did you check your junk or spam mail folders? The email address from which bpo is sending email is not super trusted by the spam filters used by large email providers like GMail and Outlook.
On Thu, May 27, 2021 at 10:46 AM Irit Katriel iritkatriel@googlemail.com wrote:
I'm not getting anything at all from bpo for about a week now. Maybe it had enough of me.
On Thu, May 27, 2021 at 6:01 PM Victor Stinner vstinner@python.org wrote:
I confirm that commits merged in 3.9, 3.10 and main branches are logged again in bugs.python.org. Thanks to everyone who helped to solve this issue!
On Thu, May 27, 2021 at 9:50 PM Guido van Rossum guido@python.org wrote:
Did you check your junk or spam mail folders? The email address from which bpo is sending email is not super trusted by the spam filters used by large email providers like GMail and Outlook.
Unfortunately, this is not just the case for BPO emails. I've even found emails sent by core developers and PSF staff in my spam folder. Perhaps email providers don't like the high traffic created from @python.org emails :)
--Berker
My spam folder contains solutions to most of life's problems, but nothing about python. I'll check with the infra team, thanks.
On Thu, May 27, 2021 at 8:11 PM Berker Peksağ berker.peksag@gmail.com wrote:
On Thu, May 27, 2021 at 9:50 PM Guido van Rossum guido@python.org wrote:
Did you check your junk or spam mail folders? The email address from
which bpo is sending email is not super trusted by the spam filters used by large email providers like GMail and Outlook.
Unfortunately, this is not just the case for BPO emails. I've even found emails sent by core developers and PSF staff in my spam folder. Perhaps email providers don't like the high traffic created from @python.org emails :)
--Berker _______________________________________________ python-committers mailing list -- python-committers@python.org To unsubscribe send an email to python-committers-leave@python.org https://mail.python.org/mailman3/lists/python-committers.python.org/ Message archived at https://mail.python.org/archives/list/python-committers@python.org/message/W... Code of Conduct: https://www.python.org/psf/codeofconduct/
Not a solution, but I just wanted to point out the hilarity of the "bro issues" instead of "bpo issues" typo. I've been having a difficult evening and seeing the title in my inbox made me chuckle. Might as well stop and love life's happy little accidents when one has the chance to. :)
On Wed, May 12, 2021 at 10:23 AM Guido van Rossum guido@python.org wrote:
Recently it seems that when a PR linked to a bpo issue is merged, no note of this event is made in the bpo issue. Look at https://bugs.python.org/issue43933 for example. There are notes for the first two merged PRs (25717 and 25719), at https://bugs.python.org/issue43933#msg392343 and the next message. But I cannot find a similar note for the third PR, 26054, which is also merged.
I recall seeing this for other recent issues as well. Did some piece of automation recently break? (Could it have to do with the master->main move?) -- --Guido (mobile) _______________________________________________ python-committers mailing list -- python-committers@python.org To unsubscribe send an email to python-committers-leave@python.org https://mail.python.org/mailman3/lists/python-committers.python.org/ Message archived at https://mail.python.org/archives/list/python-committers@python.org/message/M... Code of Conduct: https://www.python.org/psf/codeofconduct/
-
Berker Peksağ -
Eric V. Smith -
Guido van Rossum -
Irit Katriel -
Kyle Stanley -
Mariatta -
Senthil Kumaran -
Victor Stinner -
Zachary Ware -
Zachary Ware