Repository navigation
Rework SUPERVISOR_COMMS.send_request class/method to have log stored as a attribute #44615
Description
This reminds me: we should rework this class/method to have `log` stored as a attribute so we don't need to pass log in to this class.
(Future work; doing this will make it easier to use this from within XCom or Variable class.)
Originally posted by @ashb in #44590 (comment)
Activity
[-]This reminds me: we should rework this class/method to have `log` stored as a attribute so we don't need to pass log in to this class.[/-][+]Rework `SUPERVISOR_COMMS.send_request` class/method to have `log` stored as a attribute so we don't need to pass log in to this class.[/+][-]Rework `SUPERVISOR_COMMS.send_request` class/method to have `log` stored as a attribute so we don't need to pass log in to this class.[/-][+]Rework `SUPERVISOR_COMMS.send_request` class/method to have `log` stored as a attribute[/+]task-sdkdependency fromairflow-core#62061Prab-27 commentedon Feb 18, 2026
@amoghrajesh I'd like to participate to understand how this dependency separation is done.
If it’s okay, can I work on this issue?
amoghrajesh commentedon Feb 20, 2026
Feel free, right now we have to init a
logand pass it around functions intask_runneretc, it would be better if we could have simpler API / functions without need to pass them around.Assigning it to you, let us know if you have qns.
potiuk commentedon Mar 2, 2026
@Prab-27 We are unassigning you from this issue as part of our updated assignment policy.
This is not meant to discourage your contribution — quite the opposite! You are still very welcome to work on this issue and submit a PR for it. Simply comment that you are working on it and open a PR when ready.
We found that formal assignments were not working well, as they often prevented others from contributing when the assignee was not actively working on the issue.
Prab-27 commentedon Mar 3, 2026
Working on this
Prab-27 commentedon Mar 12, 2026
As we discussed in dev calls - @amoghrajesh Do we need to include this in next release version - 3.2.ob2 ?
amoghrajesh commentedon Mar 25, 2026
Since this has not yet been picked up and we are approaching the 3.2 release, I am moving it to the 3.3 milestone.
Prab-27 commentedon Mar 25, 2026
Thanks !! have started working on this !!
wjddn279 commentedon May 2, 2026
@Prab-27 Hi, still working on this?
Prab-27 commentedon May 2, 2026
@wjddn279 yes I'll raise a PR soon
amoghrajesh commentedon Jun 15, 2026
Wasn't committed for Airflow 3.3, moving to Airflow 3.4 as best effort work.
eladkal commentedon Jun 15, 2026
@amoghrajesh we try to avoid setting milestones on issues. we can tag the PR with the proper milestone
amoghrajesh commentedon Jun 15, 2026
Cool thanks for notifying me.