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.

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

Bug: Multiple instances of the orchestrator with default classifier #68

Closed
cornelcroi opened this issue Oct 15, 2024 · 1 comment
Closed
Assignees
Labels
bug Something isn't working

Comments

@cornelcroi
Copy link
Contributor

Expected Behaviour

To have a new instance of the orchestrator when used with default value for classifier

Current Behaviour

The orchestrator becomes static

Code snippet

orchestrator = MultiAgentOrchestrator(options=OrchestratorConfig(
        LOG_AGENT_CHAT=True,
        LOG_CLASSIFIER_CHAT=True,
        LOG_CLASSIFIER_RAW_OUTPUT=True,
        LOG_CLASSIFIER_OUTPUT=True,
        LOG_EXECUTION_TIMES=True,
        MAX_RETRIES=3,
        USE_DEFAULT_AGENT_IF_NONE_IDENTIFIED=True,

        MAX_MESSAGE_PAIRS_PER_AGENT=10       
    ))

Possible Solution

Better handle the default values initialization in the init of the orchestrator

Steps to Reproduce

Instantiate the orchestrator several times. Issue easy to test with FastAPI.

@cornelcroi cornelcroi added the bug Something isn't working label Oct 15, 2024
@cornelcroi cornelcroi removed the triage label Oct 15, 2024
@brnaba-aws brnaba-aws self-assigned this Oct 16, 2024
@brnaba-aws
Copy link
Contributor

Fixed in python 0.0.18

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants