launch.json configuration not loaded properly after refreshing the page with IDE

[lexiv0re]

Describe the bug

For a workspace with 2 projects it is not picking the existing launch configuration if launch.json is created in the second workspace.

Che version

7.50

Steps to reproduce

1. Create a workspace with two projects.
2. Create a file to be run in the second project.
3. Open the file and select Run -> Start Without Debugging.
4. It asks for the environment and debug configuration and creates .theia/launch.json in the second project.
5. The file can now be run successfully with Run -> Start Without Debugging without any prompts.
6. Refresh the page, close Getting Started tab so the same file is focused. Note, that launch.json is present.
7. Try Run -> Start Without Debugging again. Instead of executing the file it opens the existing launch.json and expects for more launch configurations to be added.

Expected behavior

On the step 7 it is expected to use the existing configuration and run without any additional prompts.

Runtime

other (please specify in additional context)

Screenshots

No response

Installation method

other (please specify in additional context)

Environment

Linux

Eclipse Che Logs

No response

Additional context

microK8s
chectl 7.50.0

Note: If I try to run all the same steps but for the first project in the workspace the problem doesn't reproduce.

[che-bot]

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

[lexiv0re]

/remove-lifecycle stale

[azatsarynnyy]

@lexiv0re I suggest checking the described use case in the upstream Eclipse Theia project. To me, it looks like an upstream issue.
Also, take into account #21771

[lexiv0re]

@azatsarynnyy thank you for the heads up.

I tested it on the upstream Theia with multi-root workspace and it's not reproducible there. That might be because

• It has been already fixed there by now
• It's specific to che-theia

[che-bot]

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.