Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

automatic process does not sync owner and editor #1918

Open
simonelbaz opened this issue Dec 24, 2024 · 2 comments · May be fixed by #1919
Open

automatic process does not sync owner and editor #1918

simonelbaz opened this issue Dec 24, 2024 · 2 comments · May be fixed by #1919
Labels

Comments

@simonelbaz
Copy link

Hi,

Version

Reproduced in 6.2.70
The code is still the same in main branch

Installation method

deb, bullseye distribution

Expected behavior

owner and editor should be synced if defined in the config.tt2

Actual behavior

only members are synced by automatic process

Steps to reproduce

TT2 attached

sympa-families-groupes-config.tt2.j2.txt

Additional information

Logs:

root@ppr1-sympa02-r1:/opt/docker/compose/sympa-docker# docker compose logs sympa-web-11-automatic | grep role
sympa-web-11-automatic-1  | notice Sympa::Spindle::ProcessRequest::_twist() Processing Sympa::Request [<action=include;context=xxxxxx;role=member>](mailto:action=include;context=xxxxxxxx;role=member)
sympa-web-11-automatic-1  | info Sympa::Request::Handler::include::_twist() Sympa::DataSource::LDAP [<context=xxxxxxx;id=0a62f42a;role=member;name=ldap>](mailto:context=xxxxxx;id=0a62f42a;role=member;name=ldap): 4 included, 0 deleted, 0 updated, 0 kept
sympa-web-11-automatic-1  | info Sympa::Request::Handler::include::_twist() Sympa::Request [<action=include;context=xxxxxxx;role=member>](mailto:action=include;context=xxxxxxxx;role=member): Success, 4 added, 0 deleted, 0 updated
sympa-web-11-automatic-1  | notice Sympa::Spindle::ProcessRequest::_twist() Processing Sympa::Request [<action=include;context=xxxxxx;role=member>](mailto:action=include;context=xxxxxxx;role=member)
sympa-web-11-automatic-1  | info Sympa::Request::Handler::include::_twist() Sympa::DataSource::LDAP [<context=xxxxxx;id=0a62f42a;role=member;name=ldap>](mailto:context=xxxxx;id=0a62f42a;role=member;name=ldap): 0 included, 0 deleted, 0 updated, 4 kept
sympa-web-11-automatic-1  | info Sympa::Request::Handler::include::_twist() Sympa::Request [<action=include;context=xxxxxxxx;role=member>](mailto:action=include;context=xxxxxx;role=member): Success, 0 added, 0 deleted, 0 updated
sympa-web-11-automatic-1  | notice Sympa::Spindle::ProcessRequest::_twist() Processing Sympa::Request [<action=include;context=xxxxxxx;role=member>](mailto:action=include;context=xxxxx;role=member)
sympa-web-11-automatic-1  | info Sympa::Request::Handler::include::_twist() Sympa::DataSource::LDAP [<context=xxxxx;id=0a62f42a;role=member;name=ldap>](mailto:context=xxxxx;id=0a62f42a;role=member;name=ldap): 0 included, 0 deleted, 0 updated, 4 kept
sympa-web-11-automatic-1  | info Sympa::Request::Handler::include::_twist() Sympa::Request [<action=include;context=xxxxx;role=member>](mailto:action=include;context=xxxxxxr;role=member): Success, 0 added, 0 deleted, 0 updated

Code:

unless (defined $list->sync_include('member')) {

@simonelbaz simonelbaz added the bug label Dec 24, 2024
@simonelbaz simonelbaz linked a pull request Dec 30, 2024 that will close this issue
@ikedas ikedas linked a pull request Jan 4, 2025 that will close this issue
@ikedas
Copy link
Member

ikedas commented Jan 11, 2025

Hi @simonelbaz ,

Could you please wait for a while (one hour or so) after a new automatic-list was created? Periodical task may sync owner/editor
.

@simonelbaz
Copy link
Author

Hi @ikedas ,

Thanks for your feedback.

This is the behaviour I have noticed: waiting for the task mgr to sync the owners and editors solves the issue.

However, in the interval, the send sees his mails rejected due to insufficient privileges.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants