Skip to content

Conversation

@hussein-awala
Copy link
Member

closes: #31799

I searched in the history about the reason to use 100 as log level, but it seems that it was just for debugging, where there is no logical need to log an error here, sine we need to stop the trigger after each run.

This line was added by #29482 which restored #27758


^ Add meaningful description above

Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in newsfragments.

@boring-cyborg boring-cyborg bot added the area:Scheduler including HA (high availability) scheduler label Jun 8, 2023
@hussein-awala hussein-awala added this to the Airflow 2.6.2 milestone Jun 8, 2023
@potiuk potiuk requested a review from dstandish June 8, 2023 18:36
@potiuk
Copy link
Member

potiuk commented Jun 8, 2023

I think @dstandish should have a say on this one.

@hussein-awala
Copy link
Member Author

I think @dstandish should have a say on this one.

Indeed, I was going to mention him.

@eladkal eladkal modified the milestones: Airflow 2.6.2, Airlfow 2.6.3 Jun 8, 2023
Copy link
Contributor

@dstandish dstandish left a comment

Choose a reason for hiding this comment

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

nope can't do this.

this is a special log message that signals to the wrapper "this handler can be closed" so we need it.

it's filtered out so user should never see it.

perhaps we should add a clarifying comment instead?

if you are seeing it then something is probably not working right let me review the issue

@potiuk
Copy link
Member

potiuk commented Jun 9, 2023

perhaps we should add a clarifying comment instead?

Clearly we need it as none of us had a clue about it :)

@ephraimbuddy ephraimbuddy removed this from the Airflow 2.6.3 milestone Jul 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:Scheduler including HA (high availability) scheduler

Projects

None yet

Development

Successfully merging this pull request may close these issues.

"trigger end" being spuriously logged from triggerer_job_runner at level 100

5 participants