Update callbacks documentation (errors and context)

[ying-w]

• Point out lack of logging on callback functions (errors are silent)
• Add more info about context

closes

• Errors in callback functions are hidden #31112
• Not easy to know what is in context passed to operators and call_backs #26830

[ying-w]

@potiuk i'm not sure how to check the rendering of RST

Also, do you have tips on what needs to be changed in config to show scheduler logs? I'm not sure this is the right term and it wasn't obvious from reading logging-tasks

[pankajkoti]

Should this level be a warning or note?

[ying-w]

i put it as warning because it wasn't obvious that there wouldn't be any errors shown in ui when callback function is broken (like function calls were incorrect syntax)

[potiuk]

warning is fine. There are some static checks/docs build errors to fix though (see the failed checks).

[ying-w]

There was a timeout waiting for docker image, can someone re-trigger the github action? it seems like there is quite the queue right now

[potiuk]

There was a timeout waiting for docker image, can someone re-trigger the github action? it seems like there is quite the queue right now

The queue was rather small. But It looks like there was some kind of event that happens once every few months that we have not diagnosed yet (and given that we we are likely to move to k8s infrastructure in a near future it makes little sense to spend time on) - resulting with our auto-scaling group goes down 0 and get stuck.

I pushed it a little to unstuck it (it usually helps) and restarting the job now.

[ying-w]

@potiuk a timeout occurred in gh actions when trying to get docker image, do you want to rerun or just merge?

[potiuk]

That's a quck test when re-run. (passed).