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

  1. Windows 11
  2. 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

Most upvoted comments

@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.

Would you create a GitHub action to build a .vsix in PR automatically?

@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

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 main and we can be immediately be notified of build problems.

Would you create a GitHub action to build a .vsix in PR automatically?

@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