-
Notifications
You must be signed in to change notification settings - Fork 138
fix the bug of thread block every request #59
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
Conversation
this sync function will block every request now I fix it
Update bots_orchestrator.py
|
@fengtality @cardosofede @tomasgaudino @rapcmia |
cardosofede
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pls test that works @rapcmia btw i think that we should evaluate doing it async by default
I have a look later this afternoon 🙏🏼 |
|
PR update:
Test when no container active
Steps to reproduce:
|
fix returns a coroutine for the active containers
MarsYoung
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
add await to sovle returns a coroutine for active containers
this result was caused by the missing of await keyword,fixed it @rapcmia |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Setup this PR with latest dashboard and deploy(broker) on source
- Build docker image for tests ✅
- Reported issues has been fixed by developer ✅
- Add credentials and observe diff from development branch
- Loads portfolio successfully
Test what happens when there are no containers?
- All ok, Launched 2 instances
- Relaunch backend-api and dashboard
- 1 instance paused and other is active ✅
- Start the instance and worked ok, 2 instance actively fetched from backend-api and dashboard/instance page
Testing with a mix of running and stopped containers
- Pause an instance while another is running then relaunch backend-api ✅
- Start an instance while another is paused observed behavior after backend api is launched ✅
- Paused all instance, relaunch backend-api then start all instance again ✅
- Archived all bots at the same time and observe behavior ✅
Run same tests cases with docker build ✅






get_active_containers is blocking every request, make a single request a long response time.