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

Debug configuration doesn't show up for second project in multi-root workspace #43079

Closed
DanTup opened this issue Feb 7, 2018 · 6 comments
Closed
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug config VS Code configuration, set up issues verified Verification succeeded
Milestone

Comments

@DanTup
Copy link
Contributor

DanTup commented Feb 7, 2018

I'm sure this has worked for me before, but today I added a second folder to my workspace then used the Add config (devicelab) option in the debug dropdown to add a new config. For some reason, the new launch config doesn't show up in that dropdown.

launch.json in the original folder (flutter_tools) has two configs that both appear (they're pretty much the same as this one, just with different args/program).

debug

@DanTup
Copy link
Contributor Author

DanTup commented Feb 7, 2018

Unsure if related, but dev console has a lot of warnings (284):

warnings

@DanTup
Copy link
Contributor Author

DanTup commented Feb 7, 2018

Note: after a "Reload Window" the config shows up, suggesting the config is fine but something went wrong earlier.

@weinand weinand assigned isidorn and unassigned weinand Feb 7, 2018
@weinand weinand added the debug Debug viewlet, configurations, breakpoints, adapter issues label Feb 7, 2018
@isidorn isidorn added the bug Issue identified by VS Code Team member as probable bug label Feb 7, 2018
@isidorn isidorn added this to the February 2018 milestone Feb 7, 2018
@isidorn
Copy link
Contributor

isidorn commented Feb 8, 2018

@DanTup the errors in consle are unrelated.

I am not getting an event from the configuration service. Forwarding this issue to @sandy081
Here are exact steps:

  1. Start with single folder vscode (no workspace)
  2. Add another folder to this workspace
  3. Add a configuration to the second folder's launch.json
  4. No configurationChange event gets fired

@isidorn isidorn added config VS Code configuration, set up issues and removed debug Debug viewlet, configurations, breakpoints, adapter issues labels Feb 8, 2018
@isidorn isidorn assigned sandy081 and unassigned isidorn Feb 8, 2018
@isidorn isidorn removed this from the February 2018 milestone Feb 8, 2018
@sandy081 sandy081 added this to the February 2018 milestone Feb 8, 2018
@sandy081
Copy link
Member

@isidorn I cannot reproduce this issue. I followed the steps as above and I could see the launches dropdown is getting updated. Not sure if I miss any steps here?

@sandy081 sandy081 added the info-needed Issue requires more information from poster label Feb 19, 2018
@isidorn
Copy link
Contributor

isidorn commented Feb 19, 2018

@sandy081 I can reproduce all the time exactly following the steps above, so please drop by my machine

@isidorn isidorn removed the info-needed Issue requires more information from poster label Feb 19, 2018
@isidorn
Copy link
Contributor

isidorn commented Feb 20, 2018

After investigating with @sandy081 I have created a new bug which captures the issue more correctly
#44034
@DanTup feel free to comment more there if I missed something

@isidorn isidorn closed this as completed Feb 20, 2018
@chrmarti chrmarti added the verified Verification succeeded label Mar 2, 2018
@vscodebot vscodebot bot locked and limited conversation to collaborators Apr 6, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug config VS Code configuration, set up issues verified Verification succeeded
Projects
None yet
Development

No branches or pull requests

5 participants