You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Opening an audio file from the terminal with a relative link breaks the audio player.
Steps to Reproduce:
Place an audio file in the root of the workspace (e.g. out.mp3)
Open the audio file through the file explorer => shows the audio player and you can listen to the file
In a terminal execute e.g. ls -dl ./out.mp3 and ctrl+click on the audio file (e.g. ./out.mp3) => shows error (see screenshot)
Opening the file from the file explorer and from the terminal also create two different tabs (even though it is the same file). This does not happen for any other file I tried.
Opening from the terminal shows this error:
Also note the leading . in the file path. This is not shown when opening the file from the file explorer. And it is also not shown for any other file type I tried.
In the browser I can see the following error when opening the audio file from the terminal:
GET https://XXXX:63712/webview/theia-resource/file///home/XXX/workspace/out.mp3?version%3D1709623218793 net::ERR_ABORTED 404 (Not Found)
When opening the audio file from the file explorer I can see the exact same request (except different version) in the network tab, but there it succeeds.
Opening the file with an absolute path from the terminal works and also jumps to the same tab opened by the file explorer.
Note that I'm not sure where the audio player comes from but it's not from a theia extension and I don't think it is from a third party VS Code plugin. So I think it is either provided by theia or maybe the VS Code builtin extension pack.
Additional Information
Operating System: Ubuntu 18.04 (running in docker)
Theia Version: 1.43.1 (also reproduced the issue in 1.47.0) running in the browser
The text was updated successfully, but these errors were encountered:
Bug Description:
Opening an audio file from the terminal with a relative link breaks the audio player.
Steps to Reproduce:
out.mp3
)ls -dl ./out.mp3
and ctrl+click on the audio file (e.g../out.mp3
) => shows error (see screenshot)Opening the file from the file explorer and from the terminal also create two different tabs (even though it is the same file). This does not happen for any other file I tried.
Opening from the terminal shows this error:
![image](https://private-user-images.githubusercontent.com/32217236/310019617-8c12eebb-4e57-49e9-8da4-358140a73a3f.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjA3MzE4NzAsIm5iZiI6MTcyMDczMTU3MCwicGF0aCI6Ii8zMjIxNzIzNi8zMTAwMTk2MTctOGMxMmVlYmItNGU1Ny00OWU5LThkYTQtMzU4MTQwYTczYTNmLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA3MTElMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNzExVDIwNTkzMFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTg2NjllYmY3MGI3ZDA4YTVhOTUzMTRjN2I0NTMzOWI3ZGQzODgzNTU5Y2JiNGZlZThlMzAwZGI0ZDliNTNiYjYmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.J3pkaOh_poSLtHCEgCbZQM5JECrotNOGVcBC0rELIa4)
Also note the leading
.
in the file path. This is not shown when opening the file from the file explorer. And it is also not shown for any other file type I tried.In the browser I can see the following error when opening the audio file from the terminal:
When opening the audio file from the file explorer I can see the exact same request (except different version) in the network tab, but there it succeeds.
Opening the file with an absolute path from the terminal works and also jumps to the same tab opened by the file explorer.
Note that I'm not sure where the audio player comes from but it's not from a theia extension and I don't think it is from a third party VS Code plugin. So I think it is either provided by theia or maybe the VS Code builtin extension pack.
Additional Information
The text was updated successfully, but these errors were encountered: