- 23 Nov, 2022 7 commits
-
-
This makes it easy to store additional information that is meant for computers, not humans. For example, a CI system may store data such as the internal run ID associated to the test result. Signed-off-by:
Martin Roukala <martin.roukala@mupuf.org>
-
Without this, the only way to get the completion date is to manually filter the events list... Signed-off-by:
Martin Roukala <martin.roukala@mupuf.org>
-
This enables querying the list of test results belonging to a project, posted before/after a date, by a user, for a test name, which is in a list of states. This endpoint makes it easier to implement a bridge between patchwork and an existing CI system such as GitLab. Signed-off-by:
Martin Roukala <martin.roukala@mupuf.org>
-
The library removed some deprecated names recently, let's fix that up.
-
Not only will this release be supported until April 2024, it also brings features that will be of use in upcoming patches. Signed-off-by:
Martin Roukala <martin.roukala@mupuf.org>
-
Co-authored-by:
Martin Roukala <martin.roukala@mupuf.org> Signed-off-by:
Ryszard Knop <ryszard.knop@intel.com>
-
Django, django-filter and Celery are not updated, as they need extra changes. Co-authored-by:
Martin Roukala <martin.roukala@mupuf.org> Signed-off-by:
Ryszard Knop <ryszard.knop@intel.com>
-
- 11 Aug, 2022 3 commits
-
-
Dragoon Aethis authored
Until now, if anyone replied with a patch (as parsed by Patchwork) to the cover letter/first patch of a series, Patchwork would create a new revision within that series and have the sender "take over" a series. We now check if a given mail is in reply to any existing series before trying to parse its content, and if we have existing series AND the series' original author is not the current mail's author, we force the mail to be treated as a comment in reply to the cover letter/patch. Fixes #46.
-
Dragoon Aethis authored
Looking up existing Patches and Comments with msgids w/ whitespace fails as we try to get the first object whose msgid matches these values. They are always stripped before being saved to the database.
-
Dragoon Aethis authored
-
- 05 Aug, 2022 1 commit
-
-
Dragoon Aethis authored
Co-authored-by:
Martin Roukala <martin.roukala@mupuf.org> Signed-off-by:
Ryszard Knop <ryszard.knop@intel.com>
-
- 02 Aug, 2022 8 commits
-
-
Dragoon Aethis authored
Did not affect anything, but out it goes.
-
Dragoon Aethis authored
The target endpoints are mounted on a path where they require slashes - while Django can append these automatically, it cannot do so for POST requests, causing the tests to fail. Fix it.
-
Dragoon Aethis authored
This function can be replaced with os.makedirs(path, exist_ok=True).
-
Dragoon Aethis authored
Since Selenium version is not pinned and the current version removed some deprecated features tests used, it's time to bump these a little.
-
Dragoon Aethis authored
Yes, it's a little faster, but it also makes debugging failing tests less than fun. There's not a lot of logging in an average run anyways.
-
Dragoon Aethis authored
Functionally nothing changed, but pycodestyle complains about these.
-
Dragoon Aethis authored
This once again enables using the provided dev scripts to set up a fresh development environment with just Python installed - no extra config and tweaks needed. - Split dev configs into per-database files - Simplify scripts in "tools" and use per-database configs - Allow overriding DJANGO_SETTINGS_MODULE for dev scripts - Update .gitignore for more venv aliases and Django stuff - Update links for Django 2.2 - Misc comment cleanups
-
Dragoon Aethis authored
- Add last_updated fields to patchwork.patch objects - Remove version and n_patches fields from patchwork.series objects
-
- 26 Aug, 2021 1 commit
-
-
- 15 Jul, 2020 2 commits
-
-
Arkadiusz Hiler authored
Quoting RFC: "However, exploiting the case sensitivity of mailbox local-parts impedes interoperability and is discouraged." Most of the existing software is threating the local part (i.e. the thing before @) of emails as case insensitive. Some people use different capitalization at different times, e.g. arkadiusz.hiler@example.com with git-send-email and Arkadiusz.Hiler@example.com with their regular client. To mitigate this Person's email is now case insensitive for the sake of searching and normalized to lower case pre_save. It's not perfect by any means and still can be bypassed by doing .update() on the QuerySet, but will work in most of the usual cases. Tests and migration deduplicating existing entries are provided. Fixes: #32 Signed-off-by:
Arkadiusz Hiler <arkadiusz.hiler@intel.com>
-
Arkadiusz Hiler authored
class Series: submitter = models.ForeignKey(Person, ... Would result in Person having a field named series_set QuerySet that represents the other side of this one-to-many relation. related_name is used to overwrite that and it looks like it purpose was misunderstood as it had been set to "submitters" - Person.submitters doesn't make much sense. Let's remove related_name an use the default name. Signed-off-by:
Arkadiusz Hiler <arkadiusz.hiler@intel.com>
-
- 09 Jul, 2020 1 commit
-
-
Arkadiusz Hiler authored
Results send to Patchwork can now be marked as markdown (on a Test model level). Such results are then rendered into HTML and displayed on the web views. Emails that are sent to the mailing list / recipients for such results are going to be multipart/alternative containing both the text form (raw Markdown) and the rendered HTML. Fixes: #6 Signed-off-by:
Arkadiusz Hiler <arkadiusz.hiler@intel.com>
-
- 07 Jul, 2020 2 commits
-
-
Arkadiusz Hiler authored
Generated mboxes weren't representing newline (aka LF or \n) and carriage return (aka CR or \r) found in the original patch faithfully. This is mostly due to how email.Message is implemented - it tries to normalize newlines in plain text emails. This doesn't work for us as we want to provide the patches in an unchanged form. To do that we have to overwrite as_string() and as_bytes() methods on our Message class that will use modified Generator that doesn't mangle newlines. The difference in the checksums is due to slightly different header wrapping caused by the changes in generator. Additionally tests are provided to make sure that we ingest emails correctly (no mangling there) and that the generated mbox is also a-okay. Fixes: #33 Signed-off-by:
Arkadiusz Hiler <arkadiusz.hiler@intel.com>
-
Arkadiusz Hiler authored
This is done because Python's qp encoding can be a bit problematic with line endings. Also, bumping the line length limit to 200 makes the downloaded mboxes readable with any sensible patches and is well below the RFC 5322 limit of 998 characters. The changes in checksums are due to emails not being qp-encoded. Signed-off-by:
Arkadiusz Hiler <arkadiusz.hiler@intel.com>
-
- 06 Jul, 2020 1 commit
-
-
Arkadiusz Hiler authored
Turns out that clean_header() takes Header, so we were getting: AttributeError 'Header' object has no attribute 'startswith' Let's use Header in the test and fix the issue properly. Fix: a7046dca ("Add workaround for MUAs that don't handle UTF-8") Signed-off-by:
Arkadiusz Hiler <arkadiusz.hiler@intel.com>
-
- 01 Jul, 2020 4 commits
-
-
Arkadiusz Hiler authored
Noticed it while running tox with the recently added tests. Signed-off-by:
Arkadiusz Hiler <arkadiusz.hiler@intel.com>
-
Arkadiusz Hiler authored
Looks like it was added untested. Signed-off-by:
Arkadiusz Hiler <arkadiusz.hiler@intel.com>
-
Arkadiusz Hiler authored
We already have /patch/msgid/$MSGID to look up a single patch. This change adds /series/msgid/$MSGID so we can look up a whole series. This works with patch and cover letter message-ids. Fixes: #36 Signed-off-by:
Arkadiusz Hiler <arkadiusz.hiler@intel.com>
-
Arkadiusz Hiler authored
So people can use it both with and without <> Signed-off-by:
Arkadiusz Hiler <arkadiusz.hiler@intel.com>
-
- 25 Jun, 2020 1 commit
-
-
Arkadiusz Hiler authored
Some MUAs seem to send UTF-8 in headers (e.g.: Subject) as is instead of escaping it using RFC2047. Those usually get mangled somewhere on the way by the MTA/MDA and we end up with something escaped with 'unknown-8bit' encoding. Python raises an exception if we ever try to parse that, so it's better to at least try to decode it as UTF-8. Fixes: #43 Signed-off-by:
Arkadiusz Hiler <arkadiusz.hiler@intel.com>
-
- 23 Jun, 2020 2 commits
-
-
Arkadiusz Hiler authored
To be used with the recently added event 'until' filtering. Signed-off-by:
Arkadiusz Hiler <arkadiusz.hiler@intel.com>
-
Arkadiusz Hiler authored
We have 'since' filtering already and this can be used with some interesting CI workflows. Signed-off-by:
Arkadiusz Hiler <arkadiusz.hiler@intel.com>
-
- 16 Jun, 2020 1 commit
-
-
Arkadiusz Hiler authored
Signed-off-by:
Arkadiusz Hiler <arkadiusz.hiler@intel.com>
-
- 15 Jun, 2020 2 commits
-
-
Arkadiusz Hiler authored
Signed-off-by:
Arkadiusz Hiler <arkadiusz.hiler@intel.com>
-
Arkadiusz Hiler authored
and link to it from the messages about series being incomplete/strange. Signed-off-by:
Arkadiusz Hiler <arkadiusz.hiler@intel.com>
-
- 23 Apr, 2020 1 commit
-
-
Arkadiusz Hiler authored
RFC 5322 requires us to not have lines longer than 998 characters and strongly suggests that we should impose even stricter limitation of 78 characters. Let's follow that recommendation and use quoted-printable transfer encoding if any line of payload is longer than 78 characters. Reported-by:
Petri Latvala <petri.latvala@intel.com> Signed-off-by:
Arkadiusz Hiler <arkadiusz.hiler@intel.com>
-
- 25 Mar, 2020 3 commits
-
-
Arkadiusz Hiler authored
We were off by one as the patch's body counts as one comment. Signed-off-by:
Arkadiusz Hiler <arkadiusz.hiler@intel.com>
-
Arkadiusz Hiler authored
Use the first patch timestamp if available, otherwise use series completion date. Signed-off-by:
Arkadiusz Hiler <arkadiusz.hiler@intel.com>
-
Arkadiusz Hiler authored
Signed-off-by:
Arkadiusz Hiler <arkadiusz.hiler@intel.com>
-