michael-hoke opened a new issue, #1421:
URL: https://github.com/apache/daffodil-vscode/issues/1421
## Description
Starting a debugging session from the command palette causes the infoset to
be opened after the debugging session is completed. However, starting a
debugging session from the launch config causes the infoset to not be opened.
I don't think it really matters how exactly this ticket is solved - either
always open the infoset after a debugging session is finished or don't.
## Steps to Reproduce
[
1. Create basic launch config, keeping as close to the default as possible
2. Start a debugging session. Note that when it finishes, the infoset
doesn't open
3. Run a debugging session via the command palette, using the same
schema/data files.
4. Note that the infoset automatically opens at the end of the debugging
session
]
## Expected Behavior
I expect both ways of starting a debugging session to work consistently
## Actual Behavior
They are not consistent
## Additional Notes and Screenshots (optional)
There is an `openInfosetView` field that opens the infoset in a split
editor. This is not related to this issue.
In activateDaffodilDebug.ts, in the createDebugRunFileConfigs function,
there is a block at the end that looks like this:
```
vscode.debug.onDidTerminateDebugSession(async () => {
if (!vscode.workspace.workspaceFolders) {
return
}
vscode.workspace
.openTextDocument(
`${vscode.workspace.workspaceFolders[0].uri.fsPath}/${infosetFile}`
)
.then((doc) => {
vscode.window.showTextDocument(doc)
})
})
```
This is probably why the infoset opens only when the debugging session is
started from the command palette.
## Environment
[
- Operating System(s): Rocky 9 and Windows 10
- Browser/VS Code version: 1.104.0
- Extension version: 1.4.2 development
]
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
