Aleksei Gagarin

It's still [one-time](https://github.com/reactphp/promise/blob/5f80055cc21ba7bcd3989e4902061fc12e2bcc1d/src/Internal/RejectedPromise.php#L38) handler

Regarding deprecations in the SDK, definitely create an issue 👍 . However, deprecations in dependencies should be tracked by the dependencies themselves.

Yes, it would be great to push the development of React/Promise. However, we still won't achieve the set goals, including those related to the [`@yield` annotation](https://github.com/orgs/reactphp/discussions/536). Therefore, the most promising...

Could you provide an example of the configuration before and after in the PR description? It seems that previously you could specify any PSR logger for database queries, but now...

The logs configuration behavior looks breaking changed there. I can't say that I like the new behavior but I think it's 2.0

> his needs calling out in the external docs Makes sense. > Is there any scope to change the type to be more explicit or restrictive? (though this would be...

Hi. We have similar issue in Trap: https://github.com/buggregator/trap/issues/43 Someday we will definitely do it.

The interface is in the public space, so changing it can be considered a breaking change (even though it's not intended to be implemented by the user). Overall, there is...

If we add parameters to the interface method, we will break all implementations that we do not control.

Hi. Sorry for the delay. Have you tried using `yield` to wait promises? ```php // Here: yield Workflow::asyncDetached( task: static function () { $options = ChildWorkflowOptions::new() ->withTaskQueue('task_name') ->withParentClosePolicy(ParentClosePolicy::Abandon); $workflow =...