Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[Bug]: [CAP} Directory service does not detect other Directories in standalone mode. #2295

Open
rajan-chari opened this issue Apr 5, 2024 · 0 comments
Open

[Bug]: [CAP} Directory service does not detect other Directories in standalone mode. #2295

rajan-chari opened this issue Apr 5, 2024 · 0 comments
Labels
0.2 Issues which were filed before re-arch to 0.4 needs-triage

Comments

@rajan-chari
Copy link
Contributor

Describe the bug

When starting up two standalone AutoGen agents in two different processes, Directory Service first checks for existence of another directory service. This was feature is broken after the "remove sleeps" technical debt PR.

Steps to reproduce

  1. Start two AutoGen agents in CAP in two different processes.
  2. Request a connection to the AutoGen agent in one of the processes or from a third process

Actor resolution in the network will fail with "Actor not found."

Model Used

No response

Expected Behavior

No response

Screenshots and logs

No response

Additional Information

No response
@rajan-chari rajan-chari added the bug label Apr 5, 2024
@rajan-chari rajan-chari mentioned this issue Apr 5, 2024
Merged
3 tasks
@rysweet rysweet added 0.2 Issues which were filed before re-arch to 0.4 needs-triage labels Oct 2, 2024
@fniedtner fniedtner removed the bug label Oct 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
0.2 Issues which were filed before re-arch to 0.4 needs-triage
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@rysweet @rajan-chari @fniedtner