Conversation
thestumonkey
commented
Jan 28, 2026
thestumonkey
commented
- optimised pipeline page with less agressive polling
- fixed conversation display on pipeline page
- added support for omi-opus from mobile ushadow
- better logging
# Conflicts: # .env.example # backend/app/routes/api.chat.ts
|
This should now work with omi necklace and ushadow mobile streaming https://github.com/Ushadow-io/Ushadow |
| alias: "p", | ||
| type: "number", | ||
| describe: "Port to serve on.", | ||
| default: 5173, |
There was a problem hiding this comment.
are you sure that it's safe to change ports?
There was a problem hiding this comment.
Hmm, I didn't mean to change this here, however on my ushadow instance I have changed the backend port to 8888. In general AFAIK 5173 gtends to be used for the front end for hot reloads, not a backend that tends to be in the 8000's. 5173 ends up conflicting with lots of things, it's not a good default port to ship/
There was a problem hiding this comment.
so let's check if 5173 is used in the repo. I'm sure it is. so don't change port here in one place. and better to not change them in unrelated PR. let's make separate PR with ports migration and double check that all works
|
Thanks a lot for the contribution @thestumonkey! I wanted to flag a couple of implementation details. These are things I can fix on my side if you prefer, but I wanted to call them out so we’re aligned going forward. For Mongo access, we try to avoid using db.collection("audio_chunks").countDocuments({ vad: null })Instead, please go through the resource abstraction, like: await mongo({
action: "count",
collection: "audio_chunks",
query: {
vad: null,
},
})This gives us proper traceability and access logs, which is important for auditing and debugging. Direct Also, in Let me know whether you’d like to adjust these parts yourself, or if you’d rather I handle it. And, again, thanks for the contribution ❤️ |
|
@thestumonkey can you explain, how can I test it now? |
|
@Bakuutin I can change the getDBroot thing, however |
|
@skywinder I have been waiting for you on discord for some time to get you up and running? We were going to do this yesterday? |
Applied PR feedback from @Bakuutin on mycelia-tech#51: - Replaced getRootDB() with getMongoResource(auth) - Converted all direct database calls to use mongo resource abstraction - Ensures proper access logging and traceability - Maintains compatibility with future releases All database operations now go through the resource layer: - db.collection().countDocuments() → mongo({ action: "count", ... }) - db.collection().find().toArray() → mongo({ action: "find", ... }) This provides: - Access control and audit logging - Centralized permission enforcement - Consistent security checks Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
|
updated mongo db as requested. failing test is not due to this PR |
| alias: "p", | ||
| type: "number", | ||
| describe: "Port to serve on.", | ||
| default: 5173, |
There was a problem hiding this comment.
so let's check if 5173 is used in the repo. I'm sure it is. so don't change port here in one place. and better to not change them in unrelated PR. let's make separate PR with ports migration and double check that all works
|
the rest looks fine. But last thing that I want - is to break something with this PR. so better be safe. |
|
@thestumonkey ping on this. Would love to merge as soon as you revert the ports changes. |
|
Ok changed back to 5173 to reduce risk for now, although this should still get changed at some point imo |
3 participants
