Patrik Dufresne comments

Results 183 comments of


                                            Patrik Dufresne

[16.0] Update fetchmail_server_folder

Here another tentative. Sorry for all the noise. I'm not used to OCA code policies. See my comments for #3017

[16.0] Update fetchmail_server_folder

Is there something blocking the merge ?

[16.0] Update fetchmail_server_folder

Hello All, I took some time to update this Pull Request with the changes recommended.

[16.0] Fetchmail_server_folder - fail with imaplib.IMAP4.abort: command: FETCH => System Error

Never mind, Suddently, I can't reproduce the problem. Sorry for the noise

[16.0] Fetchmail_server_folder - fail with imaplib.IMAP4.abort: command: FETCH => System Error

Finnaly the problem started again. I notice the issue arise when defining an "archive" folder option. Since the expunge is execute on every delete operation and not at the very...

[16.0] Fetchmail_server_folder - fail with imaplib.IMAP4.abort: command: FETCH => System Error

Thank you !

[16.0][FIX] fetch...folder: use message uid's not sequence

As highlighted in PR #3222, the reverse processing of emails aims to address a similar issue to the one you're working on here. But I fail to see the exact...

[16.0][FIX] fetch...folder: use message uid's not sequence

ok, I see `connection.uid("search", charset, criteria)` vs `connection.search(None, criteria)` I've missed that while looking at the changes. Thanks for pointing the changes.

Data tagging change breaks vars lookups with `default=`

> This change appears to be mentioned in the [changelog](https://github.com/ansible/ansible/blob/stable-2.19/changelogs/CHANGELOG-v2.19.rst#id10): > > > vars lookup - The default substitution only applies when trying to look up a variable which is...

Data tagging change breaks vars lookups with `default=`

> The problem occurs because in 2.18 the default for the vars lookup applies to any undefined that exists anywhere in the requested variable, no matter how deeply nested, but...