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

VS-Code takes long time to hit breakpoint #1852

Closed
m-courtin opened this issue Feb 11, 2022 · 0 comments · Fixed by #1853
Closed

VS-Code takes long time to hit breakpoint #1852

m-courtin opened this issue Feb 11, 2022 · 0 comments · Fixed by #1853
Assignees
Labels
bug Something isn't working Developer_Experience enhancement New feature or request

Comments

@m-courtin
Copy link
Contributor

m-courtin commented Feb 11, 2022

Visual Studio Code >= V1.64 is takes minutes on Mac to hit a breakpoint even in a small and non-complex Unit Test. The suggested solution from Visual-Studio-Code is to configure the 'outFiles' property in the launch.json -> updating the template.launch.json to reflect the needed changes. Even on Windows machines the suggestion with the 'outfiles' is showing up with >= V1.64 but hitting the first breakpoint is not taking that immens amount of time as on Mac.

With the proper 'outfiles' configuration in place hitting then the first breakpoint is going even faster compared to V1.63 on Mac and on Windows

@m-courtin m-courtin added the bug Something isn't working label Feb 11, 2022
@m-courtin m-courtin self-assigned this Feb 11, 2022
m-courtin added a commit to m-courtin/cactus that referenced this issue Feb 11, 2022
Hitting breakpoints in debug mode is much slower with V1.64 and above
compared to V1.63. Visual Studio Code is suggesting to use the
'outFiles' property with a pattern to speed-up the process of hitting
the breakpoints. Integrating the suggestion into the
template.launch.json to provide a template solution to be taken into the
launch.json on demand.

Closes: hyperledger-cacti#1852
Signed-off-by: Michael Courtin <michael.courtin@accenture.com>
m-courtin added a commit to m-courtin/cactus that referenced this issue Feb 25, 2022
Hitting breakpoints in debug mode is much slower with V1.64 and above
compared to V1.63. Visual Studio Code is suggesting to use the
'outFiles' property with a pattern to speed-up the process of hitting
the breakpoints. Integrating the suggestion into the
template.launch.json to provide a template solution to be taken into the
launch.json on demand.

Closes: hyperledger-cacti#1852
Signed-off-by: Michael Courtin <michael.courtin@accenture.com>
m-courtin added a commit to m-courtin/cactus that referenced this issue Mar 1, 2022
Hitting breakpoints in debug mode is much slower with V1.64 and above
compared to V1.63. Visual Studio Code is suggesting to use the
'outFiles' property with a pattern to speed-up the process of hitting
the breakpoints. Integrating the suggestion into the
template.launch.json to provide a template solution to be taken into the
launch.json on demand.

Closes: hyperledger-cacti#1852
Signed-off-by: Michael Courtin <michael.courtin@accenture.com>
petermetz pushed a commit that referenced this issue Mar 1, 2022
Hitting breakpoints in debug mode is much slower with V1.64 and above
compared to V1.63. Visual Studio Code is suggesting to use the
'outFiles' property with a pattern to speed-up the process of hitting
the breakpoints. Integrating the suggestion into the
template.launch.json to provide a template solution to be taken into the
launch.json on demand.

Closes: #1852
Signed-off-by: Michael Courtin <michael.courtin@accenture.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Developer_Experience enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant