You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@daffodil.apache.org by "mbeckerle (via GitHub)" <gi...@apache.org> on 2023/05/02 20:50:33 UTC
[GitHub] [daffodil-vscode] mbeckerle opened a new issue, #614: 1.3.0-rc1 error erased from terminal window before it can be read
mbeckerle opened a new issue, #614:
URL: https://github.com/apache/daffodil-vscode/issues/614
I am trying to configure the vscode extension to allow me to single step through a DFDL schema.
I am unable to debug what is wrong with the launch.json because it fails, and a backtrace or something like one is displayed on the terminal window, but it is erased a split second later before it can be read or captured.
I'm attaching a little video of this I created by doing a MS-Teams screen share in a meeting that was just me and recording it.
https://user-images.githubusercontent.com/1524099/235781974-3e8b06a2-e4d2-4a78-8504-2e45c53053bf.mp4
The action occurs between 8 and 10 seconds into the video.
The VSCode environment is then stuck for a minute perhaps (I didn't time it) with a run indicator at the top still moving until it times out and leaves me with a dialog to dismiss.
Github, in its infinite wisdom, won't let me attach the launch.json file here. And even renaming it to launch_json.txt it still won't let me attach it. So I'm inlining it here. I already know there are things that need to be added to the daffodilDebugClasspath that are not listed. The complaint on the terminal is quite likely just telling me something is missing.
```json
{
// Use IntelliSense to learn about possible attributes.
// Hover to view descriptions of existing attributes.
// For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
"version": "0.2.0",
"configurations": [
{
"type": "dfdl",
"request": "launch",
"name": "vmf-pmmc-dfdl run",
"program": "${workspaceFolder}/src/main/resources/com/owlcyberdefense/vmf-multi/xsd/vmf-noc.dfdl.xsd",
"stopOnEntry": true,
"data": "${workspaceFolder}/src/test/resources/data/owl/binary-file-zip-message.dat",
"infosetFormat": "xml",
"infosetOutput": {
"type": "file",
"path": "/tmp/vmf-pmmc-dfdl-infoset.xml"
},
"debugServer": 4711,
"openHexView": false,
"openInfosetView": false,
"openInfosetDiffView": false,
"daffodilDebugClasspath": "${workspaceFolder}/src/main/resources:${workspaceFolder}/src/test/resources:${workspaceFolder}/../../zipLayerTransformer/src/main/resources:${workspaceFolder}/../noc-header/src/main/resources:${workspaceFolder}/../../../../../../opensource/DFDLSchemas/mil-std-2045/src/main/resources:${workspaceFolder}/lib_managed/jars/com.owlcyberdefense/zip-layer-transformer/zip-layer-transformer-1.0.0.jar",
"variables": {},
"tunables": {},
"dataEditor.omegaEditPort": 9001,
"dataEditor.logFile": "${workspaceFolder}/dataEditor-${omegaEditPort}.log",
"dataEditor.logLevel": "info"
}
]
}
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@daffodil.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [daffodil-vscode] mbeckerle commented on issue #614: 1.3.0-rc1 error erased from terminal window before it can be read
Posted by "mbeckerle (via GitHub)" <gi...@apache.org>.
mbeckerle commented on issue #614:
URL: https://github.com/apache/daffodil-vscode/issues/614#issuecomment-1536382982
That sounds like it would solve the problem.
But do you know why the terminal window is clearing at all? Why wouldn't that stack-trace output just output to the terminal window and remain visible there so that I can scroll back through it?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@daffodil.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [daffodil-vscode] Shanedell closed issue #614: 1.3.0-rc1 error erased from terminal window before it can be read
Posted by "Shanedell (via GitHub)" <gi...@apache.org>.
Shanedell closed issue #614: 1.3.0-rc1 error erased from terminal window before it can be read
URL: https://github.com/apache/daffodil-vscode/issues/614
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@daffodil.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [daffodil-vscode] mbeckerle commented on issue #614: 1.3.0-rc1 error erased from terminal window before it can be read
Posted by "mbeckerle (via GitHub)" <gi...@apache.org>.
mbeckerle commented on issue #614:
URL: https://github.com/apache/daffodil-vscode/issues/614#issuecomment-1532170159
I constructed a complete daffodilDebugClasspath by way of `sbt export runtime:fullClasspath` which outputs a ":" separated list of everything on the classpath.
I pasted this into the launch.json as the value for daffodilDebugClasspath, but ... still I get the failure as per the video above. So it's not that something is missing from the classpath.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@daffodil.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [daffodil-vscode] scholarsmate commented on issue #614: 1.3.0-rc1 error erased from terminal window before it can be read
Posted by "scholarsmate (via GitHub)" <gi...@apache.org>.
scholarsmate commented on issue #614:
URL: https://github.com/apache/daffodil-vscode/issues/614#issuecomment-1536250161
Looks like there is 1 frame in that video with the stack trace, but it's insufficient to determine the cause of the problem. I think what we need to do is configure a logger for the server and have that stuff "tee'd" into an error log in addition to being emitted to stdout/stderr. In the event that an error does happen, ideally we can detect it in the client and pop up message that contains the log file location to make it easier to do a post-mortem analysis.
For reference, a logger is configured in the DataEditor (https://github.com/apache/daffodil-vscode/blob/main/src/dataEdit/client.ts#L157) which also happens to use a Scala server. Perhaps we can do something similar for the debugger server.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@daffodil.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [daffodil-vscode] mbeckerle commented on issue #614: 1.3.0-rc1 error erased from terminal window before it can be read
Posted by "mbeckerle (via GitHub)" <gi...@apache.org>.
mbeckerle commented on issue #614:
URL: https://github.com/apache/daffodil-vscode/issues/614#issuecomment-1536388944
Let me rephrase.
There are two problems here:
(1) I couldn't debug my problem - providing another way I can get the backtrace/error info would help with that
(2) the terminal window is clearing, erasing valuable output info.
Fixing (2) solves (1), but fixing (1) only solves my immediate debug problem.
So the best fix here is just not clear the terminal window.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@daffodil.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org