commit message variable missing after update

[sgoggins]

Please help us help you by filling out the following sections as thoroughly as you can.

Description:
The new variable for commit messages is not getting set or defaulted correctly. It could be added to augur_operations.config, or defaulted in some other way. Right now its causing issues when the latest test build from main is run.

How to reproduce:

[2025-12-17 19:54:48,494: INFO/ForkPoolWorker-2] Generating facade sequence
[2025-12-17 19:54:48,496: INFO/ForkPoolWorker-32] Task augur.tasks.git.facade_tasks.clone_repos[2d6a6ef1-dbe3-4e65-82a5-d5ce7cf98400] retry: Retry in 1s: KeyError('commit_messages')
[2025-12-17 19:54:48,534: ERROR/ForkPoolWorker-2] Task augur.tasks.start_tasks.augur_collection_monitor[ba7f3da0-6b9d-40d4-8dd4-f04115f622e0] raised unexpected: KeyError('commit_messages')
Traceback (most recent call last):
  File "/home/sean/github/ai.chaoss/.venv/lib/python3.11/site-packages/celery/app/trace.py", line 453, in trace_task
    R = retval = fun(*args, **kwargs)
                 ^^^^^^^^^^^^^^^^^^^^
  File "/home/sean/github/ai.chaoss/.venv/lib/python3.11/site-packages/celery/app/trace.py", line 736, in __protected_call__
    return self.run(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/sean/github/ai.chaoss/augur/tasks/start_tasks.py", line 282, in augur_collection_monitor
    main_routine.start_data_collection()
  File "/home/sean/github/ai.chaoss/augur/tasks/util/collection_util.py", line 503, in start_data_collection
    for repo_git, task_id, hook_name in self.send_messages():
  File "/home/sean/github/ai.chaoss/augur/tasks/util/collection_util.py", line 534, in send_messages
    augur_collection_sequence.append(job(repo_git, full_collection))
                                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/sean/github/ai.chaoss/augur/tasks/git/facade_tasks.py", line 464, in facade_phase
    facade_helper = FacadeHelper(logger)
                    ^^^^^^^^^^^^^^^^^^^^
  File "/home/sean/github/ai.chaoss/augur/tasks/git/util/facade_worker/facade_worker/config.py", line 135, in __init__
    self.commit_messages = worker_options["commit_messages"]
                           ~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^
KeyError: 'commit_messages'
[2025-12-17 19:54:49,540: INFO/MainProcess] Task augur.tasks.git.facade_tasks.clone_repos[2d6a6ef1-dbe3-4e65-82a5-d5ce7cf98400] received
[2025-12-17 19:54:49,544: INFO/ForkPoolWorker-32] Task augur.tasks.git.facade_tasks.clone_repos[2d6a6ef1-dbe3-4e65-82a5-d5ce7cf98400] retry: Retry in 0s: KeyError('commit_messages')
[2025-12-17 19:54:49,734: INFO/MainProcess] Task augur.tasks.git.facade_tasks.clone_repos[2d6a6ef1-dbe3-4e65-82a5-d5ce7cf98400] received
[2025-12-17 19:54:49,734: INFO/ForkPoolWorker-32] Task augur.tasks.git.facade_tasks.clone_repos[2d6a6ef1-dbe3-4e65-82a5-d5ce7cf98400] retry: Retry in 4s: KeyError('commit_messages')
2025-12-17 19:54:50 kate process_contributors[242968] INFO Retrieved 74 github api keys for use
2025-12-17 19:54:50 kate process_contributors[242968] INFO No contributors to enrich...returning...
[2025-12-17 19:54:50,112: INFO/ForkPoolWorker-32] Task augur.tasks.github.contributors.process_contributors[63b9cd92-db38-47c8-9607-29cd5496a773] succeeded in 7.1303588819992s: None
[2025-12-17 19:54:53,793: INFO/MainProcess] Task augur.tasks.git.facade_tasks.clone_repos[2d6a6ef1-dbe3-4e65-82a5-d5ce7cf98400] received
[2025-12-17 19:54:53,794: INFO/ForkPoolWorker-32] Task augur.tasks.git.facade_tasks.clone_repos[2d6a6ef1-dbe3-4e65-82a5-d5ce7cf98400] retry: Retry in 6s: KeyError('commit_messages')
2025-12-17 19:54:55 kate process_contributors[242971] INFO Retrieved 74 github api keys for use
2025-12-17 19:54:55 kate process_contributors[242971] INFO No contributors to enrich...returning...
[2025-12-17 19:54:55,226: INFO/ForkPoolWorker-33] Task augur.tasks.github.contributors.process_contributors[79c33903-1fbe-4b76-bbb3-599303315d0f] succeeded in 6.8613529989997915s: None
2025-12-17 19:54:55 kate contributor_breadth_model[242973] INFO Retrieved 74 github api keys for use
[2025-12-17 19:54:59,838: INFO/MainProcess] Task augur.tasks.git.facade_tasks.clone_repos[2d6a6ef1-dbe3-4e65-82a5-d5ce7cf98400] received
[2025-12-17 19:54:59,840: INFO/ForkPoolWorker-32] Task augur.tasks.git.facade_tasks.clone_repos[2d6a6ef1-dbe3-4e65-82a5-d5ce7cf98400] retry: Retry in 1s: KeyError('commit_messages')
[2025-12-17 19:55:00,882: INFO/MainProcess] Task augur.tasks.git.facade_tasks.clone_repos[2d6a6ef1-dbe3-4e65-82a5-d5ce7cf98400] received
[2025-12-17 19:55:00,883: INFO/ForkPoolWorker-32] Task augur.tasks.git.facade_tasks.clone_repos[2d6a6ef1-dbe3-4e65-82a5-d5ce7cf98400] retry: Retry in 24s: KeyError('commit_messages')

[sgoggins]

testing if this fixes it, which I expect it to: INSERT INTO "augur_operations"."config" ("id", "section_name", "setting_name", "value", "type") VALUES (10062, 'Facade', 'commit_messages', '0', 'int');

[MoralCode]

Based on a quick skim of the stack trace I want to see where worker_options is created/what its data structure is.

I dont think this is an issue with config defaults

[sgoggins]

@MoralCode : I verified that adding that row in the config table fixes the issue.

[sgoggins]

on the plus side, with collection of messages turned off and the contributor table scanning fix implemented the commit counting is smokin' fast again!

[MoralCode]

The process I added to the config classes that keeps the automatic database population working only works because docker automatically calls a function to Initialize the config at startup.

This issue isnt new (has existed probably since we added two different install modes), but it is probably worth figuring out how to modify the process for manual install users so that their databases get automatically updated with new values too

[sgoggins]

@MoralCode : Knowing Docker requires these config parameters, when we inject them into core Augur code we just need to bootstrap some kind of functionality to ensure the variables are set. For this issue and #3475 the issues are similar. One's an environment variable Augur needs, and that could be set when we bootstrap Augur instead of purely in Docker. In this case, we just need to generate the config.json file with new parameters or populate the DB.

If there's no good way to universally initialize key variables we'll just need to have defaults or checking code.

I see this exercise as making Augur more robust in general. :)

[MoralCode]

retesting due to timing questions with regard to the merge of #3353, which should resolve this