Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Launch configurations are not available for running #8987

Open
Tracked by #19958
RomanNikitenko opened this issue Jan 26, 2021 · 1 comment
Open
Tracked by #19958

Launch configurations are not available for running #8987

RomanNikitenko opened this issue Jan 26, 2021 · 1 comment
Assignees
Labels
bug bugs found in the application debug issues that related to debug functionality Team: Che-Editors issues regarding the che-editors team
Milestone

Comments

@RomanNikitenko
Copy link
Contributor

Bug Description:

I faced with the issue that under certain conditions launch configurations are not available for running from Debug panel - they are not displayed in the list.

The first use case is: user has some debug configurations defined in

  • someProject/.theia/launch.json file
  • workspace config file, for example theia.theia-workspace file - so workspace launch configurations

The current behavior:

  • the configurations from someProject/.theia/launch.json file are available for running
  • the configurations from theia.theia-workspace file are NOT available for running

The second use case is: user has some debug configurations defined in

  • someProject/.theia/launch.json file
  • someProject/.vscode/launch.json file

The current behavior: configurations from someProject/.theia/launch.json file only are available for running.

About second use case I'm not sure - maybe it's expected behavior and user should keep launch configurations either .vscode/launch.json either .theia/launch.json file.
But workspace configurations should be available for running and don't depend on existence of configs in .theia/launch.json file

Steps to Reproduce:

  1. Start a multi-root workspace from config file with launch configurations (please see the example below )
  2. Add another launch configuration to yourProject/.theia/launch.json file
  3. Go to the Debug panel and check if the workspace level configs are available for running
  4. Remove yourProject/.theia/launch.json file
  5. Go to the Debug panel and check again if the workspace level configs are available for running

Example of workspace config file with launch configurations:

{
    "folders": [
        {
            "path": "theia"
        },
        {
            "path": "vscode"
        }
    ],
    "settings": {
        "launch": {
            "configurations": [
                {
                    "name": "Launch Chrome",
                    "request": "launch",
                    "type": "pwa-chrome",
                    "url": "http://localhost:8080",
                    "webRoot": "${workspaceFolder}"
                }
            ]
        }
    }
}

Additional Information

  • Operating System: Fedora 31
  • Theia Version: 4204297
@RomanNikitenko RomanNikitenko added bug bugs found in the application debug issues that related to debug functionality labels Jan 26, 2021
@RomanNikitenko
Copy link
Contributor Author

Theia has similar problem for Global launch configurations, please see #8830 (comment)

@RomanNikitenko RomanNikitenko self-assigned this Mar 30, 2021
@azatsarynnyy azatsarynnyy added che/current-sprint issues taken to the current sprint by Che teams Team: Che-Editors issues regarding the che-editors team labels Apr 1, 2021
@azatsarynnyy azatsarynnyy added this to the 1.13.0 milestone Apr 1, 2021
@azatsarynnyy azatsarynnyy added che/next-sprint issues are planned for the next sprint by Che teams and removed che/current-sprint issues taken to the current sprint by Che teams labels Apr 8, 2021
@azatsarynnyy azatsarynnyy modified the milestones: 1.13.0, 1.14.0 Apr 13, 2021
@azatsarynnyy azatsarynnyy added che/current-sprint issues taken to the current sprint by Che teams and removed che/next-sprint issues are planned for the next sprint by Che teams labels Apr 14, 2021
@azatsarynnyy azatsarynnyy added the che/next-sprint issues are planned for the next sprint by Che teams label Apr 27, 2021
@azatsarynnyy azatsarynnyy removed the che/next-sprint issues are planned for the next sprint by Che teams label May 26, 2021
@azatsarynnyy azatsarynnyy modified the milestones: 1.14.0, 1.15.0 May 26, 2021
@azatsarynnyy azatsarynnyy added the che/next-sprint issues are planned for the next sprint by Che teams label Jun 10, 2021
@azatsarynnyy azatsarynnyy modified the milestones: 1.15.0, 1.16.0 Jun 16, 2021
@azatsarynnyy azatsarynnyy removed the che/next-sprint issues are planned for the next sprint by Che teams label Jun 16, 2021
@azatsarynnyy azatsarynnyy added the che/next-sprint issues are planned for the next sprint by Che teams label Jun 30, 2021
@azatsarynnyy azatsarynnyy removed the che/next-sprint issues are planned for the next sprint by Che teams label Jul 2, 2021
@azatsarynnyy azatsarynnyy added che/next-sprint issues are planned for the next sprint by Che teams and removed che/current-sprint issues taken to the current sprint by Che teams che/next-sprint issues are planned for the next sprint by Che teams labels Jul 22, 2021
@azatsarynnyy azatsarynnyy modified the milestones: 1.16.0, Next Jul 28, 2021
@azatsarynnyy azatsarynnyy added the che/next-sprint issues are planned for the next sprint by Che teams label Sep 3, 2021
@azatsarynnyy azatsarynnyy removed the che/next-sprint issues are planned for the next sprint by Che teams label Sep 10, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug bugs found in the application debug issues that related to debug functionality Team: Che-Editors issues regarding the che-editors team
Projects
None yet
Development

No branches or pull requests

2 participants