There is a new "CodeCov" thing on Python pull requests which adds a
giant comment with many numbers and statistics and then mark my pull
request as "failed" (red).
I know the concept of code coverage, ok. But who uses this service?
Does it *have to* send emails to say:
"Merging #18743 into master will increase coverage by 0.00%. The diff
coverage is n/a."
My PR changes distutils, but the comment also says "Lib/ftplib.py
63.85% <0.00%> (-6.06%)". The service doesn't seem reliable. A
distutils change should have no impact on ftplib coverage. Or someone
should explain me how it's supposed to work.
https://devguide.python.org/coverage/ says nothing about CodeCov.
Would it be possible to disable this service?
Or can I opt-out somehow to no longer get emails from it nor see such
comments on my PRs?
Night gathers, and now my watch begins. It shall not end until my death.
the release managers noticed Stefan adding a new compile flag and backporting it to (soon to be) 3.7.7 and (eventually to be) 3.8.3.
Should this go in? It does look like a new feature to us.
- Ł and Ned
In the end of 2019 I've reported an issue where all b.p.o notifications
would get into my spam folder (apparently because my ISP's mail server
marks them as suspicious in the e-mail headers):
Then since the beginning of 2020 I haven't been receiving b.p.o
notifications anymore. Not even in my spam folder:
I've never had a single response on those two issues. This means that I
miss all messages that are being posted on issues for which I am in the
nosy list, except in extremely rare cases when I visit an issue for
unrelated reasons (I rarely find myself casually browsing the bug
tracker these days).
I realize that e-mail delivery issues are not necessarily trivial. But
at least I would hope that problems like this don't get completely
ignored. Is there a way to get this sorted out?