Hey Thomas, Thomas Bracht Laumann Jespersen, Aug 28, 2026 at 11:47: > Hello Robin, > > I'm not a regular patchwork user, but I always found the project > interesting. I work mostly in Gentoo Linux and have been wondering if > it'd make sense for Gentoo to use Patchwork. Gentoo sees a modest stream > of patches on https://public-inbox.gentoo.org/gentoo-dev/ (and some > other MLs as well). Some form of changes are required to be posted on > gentoo-dev@ ML, but many smaller patches are received via pull requests > on Codeberg and GitHub. > > So I figured I'd give patchwork-next a spin! I cloned patchwork-next and > followed instructions to set up a database (sqlite), created a > gentoo-dev project and started the services (pw http and pw ingress). I > must say the setup is *very* easy.
Glad you had no issue ;) > Next I wanted to import some patches, and found the --mbox argument for > "pw ingress" in the "Manual Import" section of the installation docs. I > downloaded an mbox archive from the gentoo-dev public-inbox, unpacked it > and ran: > > --- [snip] --- > $ ./pw ingress --mbox < > patches/gentoo-dev-PATCH-prefix.eclass-support-EAPI-9.mbox [snip] > panic: runtime error: invalid memory address or nil pointer dereference > [signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0xca8a28] [snip] > > Although it crashes, the first message is actually imported and I can > see it in the UI. Re-running the command imports the next message: [snip] > If I keep running the command, all messages are eventually imported and > the crash stops happening (all messages are skipped, I think). > > In case you're interested in trying it out for yourself, here's the mail > thread that I started from to get the above logs (downloaded with the > mbox.gz link at the bottom of the page and unpacked locally): > > https://public-inbox.gentoo.org/gentoo-dev/[email protected]/T/#t > > I figured that running "ingress --mbox" with an mbox file containing > multiple messages that all messages would be processed. > > I hope this helps :) Thanks a lot for the detailed bug report. I have fixed the issue and pushed the commit to: https://github.com/getpatchwork/patchwork-next/commit/469071b06d8df Let me know if the latest tag (v4.0.0-rc9) works for you. Cheers. -- Robin # Monitor not included. _______________________________________________ Patchwork mailing list [email protected] https://lists.ozlabs.org/listinfo/patchwork
