Closed bhufmann closed 1 year ago
@sdirix the build fails. It seems unrelated but I'm not sure. Any suggestion?
Works for me with the packaged Electron AppImage! Just a minor comment regarding the automatic build/publish flow.
Do you know how this works in the packaged Electron build? Is the trace viewer extension smart enough to check the bundled resources?
Yes, the extension code is looking into the resources directory [1] of the AppImage for the executable of the server (until a user changes the preferences).
@bhufmann I added a commit how I would like to see the download of the trace viewer to be handled. if you agree with this approach I would squash my change into your commit and merge.
@bhufmann I added a commit how I would like to see the download of the trace viewer to be handled. if you agree with this approach I would squash my change into your commit and merge.
Thanks for providing the clarification. I'll update the PR and integrate your change.
What it does
How to test
yarn tracecompass-server:download
first and then package the application image on Linux. Start the application and use commandStart trace server
to start trace server. The server should start successfully.yarn browser
and connect with browser to localhost:3000 oryarn electron
. In the running application use commandStart trace server
to start trace server. The server should start successfully.Note, that this PR also includes a commit to Workaround rate limitation issues with open-vsx. It downloads the plug-ins sequentially instead of parallel. This should avoid the failure "Download:plugins fails with 429". See discussion: https://community.theia-ide.org/t/download-plugins-fails-with-429/2659