Skip to content

fix: log actual interval for materialized views refresh schedule - #452

Open
erensh27 wants to merge 1 commit into
chaoss:mainfrom
erensh27:fix/mat-views-log-message
Open

fix: log actual interval for materialized views refresh schedule#452
erensh27 wants to merge 1 commit into
chaoss:mainfrom
erensh27:fix/mat-views-log-message

Conversation

@erensh27

@erensh27 erensh27 commented Aug 9, 2026

Copy link
Copy Markdown

Description

  • The materialized-views periodic-task log claimed the refresh runs "every night at 1am CDT", but the schedule uses the configurable refresh_materialized_views_interval_in_days relative to process start. The log now reports the actual configured interval days instead of the misleading hardcoded time/timezone.

This PR fixes #126

Notes for Reviewers

  • No behavior change; log message only.

Signed commits

  • Yes, I signed my commits.

Generative AI disclosure
Please select one option:

  • This contribution was NOT assisted or created by Generative AI tools.
  • This contribution was assisted or created by Generative AI tools.

If AI tools were used, please provide details below:

  • What tools were used? AI coding assistant (opencode / Claude-class model)
  • How were these tools used? Wrote and reviewed the one-line log message change
  • Did you review these outputs before submitting this PR? Yes and I made these fixes: reviewed the diff against the issue; the change only alters the log string and references the configured interval variable.

… views schedule

Signed-off-by: abhinav <244986440+erensh27@users.noreply.github.com>
@erensh27
erensh27 requested a review from MoralCode as a code owner August 9, 2026 07:10

@MoralCode MoralCode left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the contribution!

Small amount of feedback, but overall I like that this is a small, very focused PR!

mat_views_interval = int(config.get_value('Celery', 'refresh_materialized_views_interval_in_days'))
if mat_views_interval > 0:
logger.info(f"Scheduling refresh materialized view every night at 1am CDT")
logger.info(f"Scheduling refresh materialized view every {mat_views_interval} days (interval starts relative to Augur process start, not a fixed time)")

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Augur is the name of an older predecessor to this project, CollectOSS is the current name.

That said, I would suggest removing the name entirely as way to resolve this - potentially by reducing the verbosity of the language to just say "N days relative to program start"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Log message incorrectly referenced a set schedule

2 participants