Personas memories fix#1917
Conversation
|
1/ from my experience, this code block is the cause of websocket connection drop (/listen API). do you experience the same ? https://github.com/BasedHardware/omi/pull/1917/files#diff-e518096e8d0948a411d3035bacafc371d1a8600659b7b7f6ea667f73b2231dc4L195-R203 |
|
1/ I did not had issues when I was testing locally (with 30s timeout). I'll test it a bit more and maybe will move it to make it independent so no other function should be dependent on it |
|
1/ please do a small research. how does the thread impact to the python application ? |
|
@nquang29 babe, could you help Mohsin a bit with researching, why this code of block drop the WS connection sometime ? |
|
1/ sure will do, just occupied with somewhat more support tickets haha. And Quang has already been a lot helpful to me, and some more insights from him will only help me more |
|
i think this issue come from |
|
nice. can you verify it ? i mean reproducing the issue and solving it. @nquang29 @mdmohsin7 |
|
The old code that was there initially indeed blocks the main thread. But the code introduced in this PR does not. Because we are starting the personas updation in a separate thread without joining it to main thread This won't block the main thread. This separate thread will be blocked until all the sub threads in it are complete |
|
ok cool. lgtm @mdmohsin7 🚀 |
- [x] 30s timeout for X api calls - [x] add try catch for sync_update_persona_prompt - [x] update the persona prompts async in a separate thread without disturbing the process_memory


Uh oh!
There was an error while loading. Please reload this page.