patchwork
patchwork copied to clipboard
The freedesktop.org edition of patchwork. Patchwork is a web patch tracking system for projects using a mailing list for contributions and reviews.
Bumps [django-debug-toolbar](https://github.com/jazzband/django-debug-toolbar) from 1.9 to 1.11.1. Changelog Sourced from django-debug-toolbar's changelog. 1.11.1 (2021-04-14) Fixed SQL Injection vulnerability, CVE-2021-30459. The toolbar now calculates a signature on all fields for the SQL...
Right now, nothing prevents two users to request a re-run on a series, which will likely lead to 2 runs being done instead of one. I think when a re-run...
Consider: https://lists.freedesktop.org/archives/xorg-devel/2016-July/050355.html https://cgit.freedesktop.org/xorg/app/edid-decode/commit/?id=c72db881557ba5d3546e9a4a0c85184ed3b4dbc1 patchwork only picked up the first 8 of that series.
I think it would be useful to have revision submitted date. It would be easy to match submitted date with test date to have an overall idea of CI response...
Sorry to bother, is there anything I should have initialized and forgot? Is this a fatal error? Traceback (most recent call last): File "./../../patchwork/bin/parsemail.py", line 890, in sys.exit(main(sys.argv)) File "./../../patchwork/bin/parsemail.py",...
Another trace back, trying to insert a revision that already exists! ``` Traceback (most recent call last): File "/srv/patchwork.freedesktop.org/patchwork/bin/parsemail.py", line 758, in main return parse_mail(mail) File "/srv/patchwork.freedesktop.org/patchwork/bin/parsemail.py", line 698, in...
That's the traceback I have on some of the patches on fdo: ``` Traceback (most recent call last): File "/srv/patchwork.freedesktop.org/patchwork/bin/parsemail.py", line 826, in main return parse_mail(mail) File "/srv/patchwork.freedesktop.org/patchwork/bin/parsemail.py", line 714,...
- there are too many states, which are sometimes not orthogonal (a patch can be both RFC and under review). This needs to be simplified, eg. new, under review, reviewed,...