You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
mAke standalone dag file processor works in DB isolation mode
There were a few missing DB operations in DAGFileProcessor that
prevented it to run in DB isolation mode. Those have been refactored
and exposed as internal API calls.
A bug was fixed in scheduler_job_runner that caused using of next_event
before it has been declared (which occured when standalone dag processor
is used and db isolation mode.
The DB retry will now correctly use logger when it is used as decorator
on class method.
The "main" code that removes DB connection from configuration (mostly in
case of Breeze) when untrusted components are used has been improved
to handle the case where DAGFile Processor forks parsing subprocesses.
Tmux configuration got improved so that both non-isolation and isolation
mode distribute panels better.
Simplified InternalApiConfig - "main" directly sets db/internal use
in db_isolation mode depending on the component.
0 commit comments