Roo-Code: Failed to play sound effect inside Docker Container
App Version
3.16.5
API Provider
Not Applicable / Other
Model Used
N/A
π Steps to Reproduce
- Windows 11
- Connect to the Running Container using Dev Containers.
π₯ Outcome Summary (Optional)
Workaround: Use a webhook feature.
π Relevant Logs or Errors
workbench.desktop.main.js:2479 [Extension Host] rejected promise not handled within 1 second: Error: Failed to play sound effect
s_r @ workbench.desktop.main.js:2479
workbench.desktop.main.js:2479 [Extension Host] stack trace: Error: Failed to play sound effect
at /root/.cursor-server/extensions/rooveterinaryinc.roo-cline-3.16.0/dist/extension.js:1057:5823
s_r @ workbench.desktop.main.js:2479
workbench.desktop.main.js:2489 [RooVeterinaryInc.roo-cline]Failed to play sound effect
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 1
- Comments: 15
Commits related to this issue
- Remove explicit caching for gemini in OR / Cline provider (#3470) * remove explicit cache * changeset — committed to bgilbert6/Roo-Code by 0xToshii 2 years ago
@SmartManoj thanks, merged !
Using PR https://github.com/RooVetGit/Roo-Code/pull/3487, audio will come from the IDE and not from the Docker container.
I think this is probably becoming an off topic discussion, but to add $0.02: I think there should be a nightly build and the marketplace should publish it so people can easily test
mainand we can be immediately be notified of build problems.@mrubens what do you think about beta branch for advance user to test with new tool or new feature ? our evals donβt have too many usecase to test
@SmartManoj can you try this pr
https://github.com/RooVetGit/Roo-Code/pull/3487 ?