You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@daffodil.apache.org by "JeremyYao (via GitHub)" <gi...@apache.org> on 2025/05/06 16:55:34 UTC
[I] Debugger Unable to Start: Error parsing infoset output path if path in tdmlConfig is specified [daffodil-vscode]
JeremyYao opened a new issue, #1246:
URL: https://github.com/apache/daffodil-vscode/issues/1246
### Description
- Windows 10
- 1.4.1 Snapshot
Snippet of configuration JSON item
```JSON
{
"request": "launch",
"type": "dfdl",
"name": "Cat_DFDL",
"schema": {
"path": "${workspaceFolder}/src/main/resources/com/mitre/jpeg/xsd/jpeg.dfdl.xsd",
"rootName": null,
"rootNamespace": null
},
"data": "${workspaceFolder}/test_images/curious-cat-thumb.jpg",
"debugServer": 4712,
"infosetFormat": "xml",
"infosetOutput": {
"type": "file",
"path": "${workspaceFolder}/target/infoset.xml"
},
"tdmlConfig": {
"action": "generate",
"name": "a",
"description": "a",
"path": "C:/repos/test"
},
"trace": true,
"stopOnEntry": true,
"useExistingServer": false,
"openDataEditor": true,
"openInfosetView": true,
"openInfosetDiffView": true,
"daffodilDebugClasspath": [],
"dataEditor": {
"port": 9000,
"logging": {
"file": "${workspaceFolder}/dataEditor-${omegaEditPort}.log",
"level": "info"
}
},
"dfdlDebugger": {
"logging": {
"file": "${workspaceFolder}/daffodil-debugger.log",
"level": "INFO"
}
}
}
```
When launching a DFDL debugging session, if there's a path specified in the `tdmlConfig` portion of the configuration, it causes the debugging session to not run and the following error message to pop up:

What seems to be happening is that the `path` value under `tdmlConfig` is being substituted in for the infoset output path.
### How to replicate
Some sample files one could use:
- https://github.com/DFDLSchemas/GIF/blob/master/src/main/resources/com/mitre/gif/xsd/gif.dfdl.xsd
- https://tenor.com/bw7gZ.gif
Steps
1. Open up the command pallete w/ `Ctrl` + `Shift` + `P` and start typing in Daffodil until you see the option to configure launch.json

2. Configure the launch.json as needed. Be sure to specify a TDML file path

3. Save the launch.json
4. Start debugging

5. The error message pictured above should pop up
--
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
Re: [I] Debugger Unable to Start: Error parsing infoset output path if path in tdmlConfig is specified [daffodil-vscode]
Posted by "scholarsmate (via GitHub)" <gi...@apache.org>.
scholarsmate closed issue #1246: Debugger Unable to Start: Error parsing infoset output path if path in tdmlConfig is specified
URL: https://github.com/apache/daffodil-vscode/issues/1246
--
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
Re: [I] Debugger Unable to Start: Error parsing infoset output path if path in tdmlConfig is specified [daffodil-vscode]
Posted by "JeremyYao (via GitHub)" <gi...@apache.org>.
JeremyYao commented on issue #1246:
URL: https://github.com/apache/daffodil-vscode/issues/1246#issuecomment-3057669359
@CoverRyan, this ticket is worded a bit ambiguously. Another way to look at it is that if you specify an invalid file path for generated TDML file (tdmlConfig -> path), the error message that pops up says `... can't write to infoset output...`. This is misleading as the infoset output path the user may have specified in launch.json may be valid.
A potential resolution to this could be to display a more accurate error message-- something along the lines of `The path specified for the generated TDML file is invalid` or something like that. This could be addressed in the frontend typescript code (displayed as a VSCode error message) or done in the Scala code. The error message that is in the screenshot is from the scala code.
--
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