-
Notifications
You must be signed in to change notification settings - Fork 103
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
Logs reflect Failure when include from SQL is carried out during nosync_time_ranges #1429
Comments
Hi @qosobrin , The section "Steps to reproduce" should contain enough necessary and sufficient information to make the reader actually reproducing it. For example, please show us the lines you actually added to the configuration file. |
@qosobrin , if possible, could you please apply this patch and check if the problem will be solved? |
Sorry, @ikedas. I've been busy lately at work and had no time to check github. I will let you know as soon as I try your patch. Thank you very much. Best regards. |
I see. I'll merge my patch for now. If you notice any problems, please report them again. Thank you for reporting bug! |
Sorry for the delay, @ikedas I have just tested the patch and it worked as expected:
Thank you very much for your work. |
@qosobrin , thank you for confirming bug fix! |
Version
6.2.60
Installation method
Debian Bullseye Package
Expected behavior
We have plenty of lists with subscribers defined in a SQL external database; all these definitions contain nosync_time_ranges. In my understanding, inclusion of subscribers should not be even started during this periods and logs should not collect any entry related to this. But if the desing of sympa does not allow to prevent this inclusion from being started and logs to be collected, then logs should not reflect a Failure since this is not a failure in the process but an regular behaviour.
Actual behavior
Logging collects entries like this one:
Steps to reproduce
Define an include_sql_query with nosync_time_ranges.
The text was updated successfully, but these errors were encountered: