-
Notifications
You must be signed in to change notification settings - Fork 137
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
Consider redirect the test stack trace into the debug console #903
Comments
There is a scroll bar at the bottom of the view. |
@jdneo I knew this is a up-down scroll bar, while I couldn't see the right part which show the exact line of file. the stack trace show the whole information of exceptions or omit some part. |
@jdneo Is there any settings I could configure redirect the exception into DEBUG CONSOLE. or Output. I could view the whole stack trace info. |
Sorry there is no such setting for now. Will consider to add the ability to redirect it into debug console. |
@jdneo Would the feature release in next version? Be eager to see the feature in next release. Because there is no other way to help me out within the VSCode. |
|
@jdneo Could it be released in 0.22.0? |
I cannot say a definite time or version of when this feature get released for now. But it's on our radar. Meanwhile, if you want to contribute for this feature, you can just send out the PR. Thanks. |
@jdneo I got it. If time available. I will. |
Thanks @jkryanchou, IMO, I prefer to support navigate from the stacktrace instead of redirect the output into the debug console, since it will ruin the program's own output. If you want to implement navigating from the stacktrace, here is a reference of the debugger's Java implementation: https://github.com/microsoft/java-debug/blob/ac7d26bcfd5736f2cabd93f2bc065aa8ff302088/com.microsoft.java.debug.core/src/main/java/com/microsoft/java/debug/core/adapter/handler/LaunchRequestHandler.java#L256-L280 Meanwhile, I'll ask the team if it is possible to let either Debugger or Language Server to expose the related API for navigating from the stacktrace. If we have this API, things would be much easier. |
Related issue in language server eclipse-jdtls/eclipse.jdt.ls#1202 If we have this API in language server, both Debugger and Test Runner can leverage it. |
@jdneo Got it. Thanks. If I could navigate the traceback in DEBUG Console. it could be link to the proper file location easily. |
@jkryanchou I still not prefer redirecting the stacktrace to debug console. This will ruin the program's output. We should enable the feature in the test report. |
@jdneo OK. |
Now it's supported to navigate from stracktrace to source location in Is this solved your problem @jkryanchou? |
This issue has been closed automatically because it needs more information and has not had recent activity. Please reach out if you have or find the answers we need so that we can investigate further. |
@jdne OK I will try it later. |
Close since being inactive for a long time. Please let me know if you have any concerns. |
I run a test case raise a exception on stack trace in the test report while I could not see the whole filename on it. While in the IDEA, I could see the whole stack trace. in de debug console.
Could author redirect the stack trace into the debug console? it also could navigate the stack trace file through the debug console panel.
The text was updated successfully, but these errors were encountered: