Skip to content

Improvement: more orchestrator asynchronism #295

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed

Conversation

gsegatti
Copy link
Contributor

@gsegatti gsegatti commented Apr 27, 2025

@gsegatti gsegatti force-pushed the improv/orchestrator branch 3 times, most recently from 6ae5ada to 539f803 Compare April 30, 2025 23:08
@gsegatti gsegatti force-pushed the improv/orchestrator branch 2 times, most recently from f423424 to 9c99189 Compare May 24, 2025 15:14
- Much like PrimeIntellect-ai#294, but also applied to discovery and node.
@gsegatti gsegatti force-pushed the improv/orchestrator branch from 9c99189 to 3bf67ba Compare May 24, 2025 15:15
@gsegatti gsegatti marked this pull request as ready for review May 24, 2025 15:30
gsegatti added a commit to gsegatti/protocol that referenced this pull request May 24, 2025
@JannikSt JannikSt closed this Jul 8, 2025
@JannikSt
Copy link
Member

JannikSt commented Jul 8, 2025

Cheers @gsegatti - thank you for your contribution! Unfortunately we are moving the project in a different direction in terms of how we handle nodes via an orchestrator, thus your current PR does not match anymore.
We'll update our issues soon to be up-to-date with our plans.
Thank you again!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants