parsemail.sh hanging with large mails

[Stephen Finucane]

On Thu, 2017-09-21 at 15:32 +0200, David Demelier wrote:
> On Thu, 2017-09-21 at 14:05 +0100, Stephen Finucane wrote:
> > The easiest thing to do here is probably read the main directly with
> > the
> > 'manage.py parsemail --debug <file>' command. There's not a whole of
> > info
> > output by this so you will probably need to add your own additional
> > logging
> > (printf debugging ftw) or start that with PDB.
> > 
> 
> Hmm, do I miss something? it looks like --debug is not a valid option
> both before and after parsemail command:
> 
> # ./manage.py --debug parsemail
> 1505922744.M947824P28474Q0Rfbc0bb3c1be6df02.patchwork
> Unknown command: '--debug'
> Type 'manage.py help' for usage.
> # ./manage.py parsemail --debug
> /tmp/m/new/1505922744.M947824P28474Q0Rfbc0bb3c1be6df02.patchwork
> usage: manage.py parsemail [-h] [--version] [-v {0,1,2,3}]
>                            [--settings SETTINGS] [--pythonpath
> PYTHONPATH]
>                            [--traceback] [--no-color] [--list-id
> LIST_ID]
>                            [infile]
> manage.py parsemail: error: unrecognized arguments: --debug

Ah, sorry - my mistake. We changed this in 2.0. What you should do instead is
modify the following lines in 'patchwork/settings/base.py':

    LOGGING = {
        ...
        'loggers': {
            ...
            'patchwork.management.commands': {
                ...
                'level': 'INFO',  # <-- change this to 'DEBUG'

As Andy has said another mail, there could be merit in simply dropping these
patches. However, I would curious to know how we could have something so big.

Stephen