Test added. But branch was reverted to 7.3, because the problem was introduced in 7.3 (here#59711) Is it ok?

because the problem was introduced in 7.3

Oh, my bad - so the problem doesn't exist < 7.3?

Yes, it did not exist in <7.3

Not sure either. Before test fails there is logInstalling symfony/scheduler (7.4.x-dev ac9f564): Extracting archive.

I suppose that the reason is that thehigh-deps is runned against7.4.x-dev in which it is not fixed yet? Could that be the reason?

Could that be the reason?

Yeah, that's what I'm thinkingbut I would have expected this issue with "low-deps" (oh, I forgot this wasn't an issue in 6.4 so that makes sense).

It should be fixed once merged though.

Suggestion applied, thank you.

Thank you@jan-pintr.

Hello,

thanks,

Idk if this is a real problem or something supported, but as there is no nullsafe check on $tagAttributes['arguments']here, this is breaking a tag on my use case, which is a "scheduler.task" tag added in a LoadExtension bundle I'm currently developping.

I'm notifying because every others attributes seems optionnals :

$myService->tag('scheduler.task', ['frequency' =>15,'schedule' =>$config['schedule'],'trigger' =>'every','arguments' =>null,// <- had to add this line to avoid a Warning: Undefined array key "arguments"]);

@johndodev Please look at#61307.

Even at leasttrigger and thenfrequency (fortrigger: every) orexpression (fortrigger: cron) parameters are also mandatory then requiring specifyarguments => null seems not intended.