Closed AndreKfm closed 3 years ago
Additional information:
Seems to be related to our deployment, another fresh (nearly empty) Kubernetes deployment doesn't seem to have that issues
@build3GB, Thanks for sharing the update. Do you have any headless services deployed in the first instance and then they are removed in the second fresh deployment? From my investigation it seems that this issue is caused when there are headless services defined as part of your deployment.
FYI, we have fixed this issue and released it for VS Code. In the meantime until a release is done for VS, if possible you could work using VS Code.
@rakeshvanga, yes exactly we have a lot of headless services.
Thank you very much for the hint.
Though we didn't change anything, so it must be an issue introduced in the latest version.
VS Code, we can give it a try, though it's currently not a complete replacement for our developers, since they all use VStudio and are not customized with VSCode. Thx also for this hint.
Describe the bug We had a running environment with BrideToKubernetes (BTK) but out of the blue it doesn't operate anymore. It's always prompting "Collection was modified, enumeration operation may not execute" directly after start of debugging.
To Reproduce We simply (try to) start Visual Studio (Enterprise) - Bridge To Kubernetes - Local Config Konfiguration debugging of any project.
**Expected behavior** Project to start debugging without any issues. **Logs** 2021-05-03T11:24:07.1794456Z | MindaroCli | TRACE | Event: Command.Start