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

Some Bugfixes #2357

Merged
merged 16 commits into from
May 16, 2023
Merged

Some Bugfixes #2357

merged 16 commits into from
May 16, 2023

Conversation

wagner-intevation
Copy link
Contributor

  • doc: lib/pipeline: move arch docs to module docstring
  • cache mixin: remove unused operation
  • bugfix: domain suffix: fix parameter error message
  • lib/bot: use *args, **kwargs for derived classes' constructors
    avoids errors when parameters of Bot change
    now all derived classes are always compatible
  • lib/bot: load logging defaults from constants

@wagner-intevation
Copy link
Contributor Author

Added:

  • jinja and remove_affix expert bots: fix bot class
  • small documentation fix in remove affix bot
  • typing additions in Bot.__check_bot_id

@wagner-intevation
Copy link
Contributor Author

wagner-intevation commented May 3, 2023

Added:
fix bug in lib/bot: use exit code 0 at normal shutdown

the job name 'build' does not fit here and is not unique
ubuntu 20.04 is old, try 22.04
In Python 3.7, the logging of the previous bot run can end up in the logging of the next run, resulting in line 0 being:
"Processed 1 messages since last logging." (written at shutdown of that bot)
prevents undefined variable errors in stop() if the logger is not yet
initialized
these are accesses in stop(), so if the initialization fails before e.g.
__message_counter["since"] was set, stop() will fail to
to prevent this, create the variable beforehand
same for the other variables
strip nullbytes from first line of bot log
truncate log_stream before initializing bot instance
ignore rare errors when the logs of the previous bot run appears in the logs of the current bot run
@sebix
Copy link
Member

sebix commented May 16, 2023

I removed two commits which are not suitable for a bugfix release:
0c443d0 and c3314f8

@kamil-certat could you please have a look?

@sebix sebix merged commit 60b657a into certtools:develop May 16, 2023
24 checks passed
@sebix sebix self-assigned this May 16, 2023
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.

None yet

3 participants