You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ignite.apache.org by "rpuch (via GitHub)" <gi...@apache.org> on 2025/01/14 10:05:58 UTC
[PR] IGNITE-22688 Make async continuation executor configurable in IgniteServer [ignite-3]
rpuch opened a new pull request, #5044:
URL: https://github.com/apache/ignite-3/pull/5044
https://issues.apache.org/jira/browse/IGNITE-22688
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@ignite.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] IGNITE-22688 Make async continuation executor configurable in IgniteServer [ignite-3]
Posted by "rpuch (via GitHub)" <gi...@apache.org>.
rpuch merged PR #5044:
URL: https://github.com/apache/ignite-3/pull/5044
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@ignite.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] IGNITE-22688 Make async continuation executor configurable in IgniteServer [ignite-3]
Posted by "rpuch (via GitHub)" <gi...@apache.org>.
rpuch commented on PR #5044:
URL: https://github.com/apache/ignite-3/pull/5044#issuecomment-2598250782
> Can we add tests for the new APIs?
I added tests demonstrating that all of `start()`, `startAsync()` and `builder()` (followed by `start()` and `startAsync()`) work.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@ignite.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org