You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@daffodil.apache.org by "arosien (via GitHub)" <gi...@apache.org> on 2023/01/26 23:55:35 UTC
[GitHub] [daffodil-vscode] arosien opened a new pull request, #436: Relay diagnostics in the "Parse" section of variables.
arosien opened a new pull request, #436:
URL: https://github.com/apache/daffodil-vscode/pull/436
Limited validation is enabled and diagnostics are separated into validations and errors.
Fixes #269.
--
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] arosien commented on pull request #436: Relay diagnostics in the "Parse" section of variables.
Posted by "arosien (via GitHub)" <gi...@apache.org>.
arosien commented on PR #436:
URL: https://github.com/apache/daffodil-vscode/pull/436#issuecomment-1410736145
> +1
>
> For the future... new tickets maybe,.... The thought struck me that we have the parse output, the various state of the parse including variables, and now the diagnostics. The only other things daffodil does are (a) log4J log output (b) crash dumps (when an assertion fails - i.e., it's a daffodil bug).
>
> We should probably have a way for the log to be inspected by the GUI/IDE, and if daffodil hits one of its crashes, that should be brought to the attention of the user without them losing their state or having the GUI stop responding, etc. Ideally if they crash daffodil we'd like a bug report, so the IDE has to not crash just because Daffodil did.
The log is printed to a terminal console, where it can be viewed during debugging. Do you mean have the log persisted to a file somewhere? We can do that.
I'm interested in hearing more about the crashing situation. Currently the Daffodil session runs within the same process as the DAP debug session; if it became a requirement to detect a crash we could potentially fork the parsing process.
--
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] arosien merged pull request #436: Relay diagnostics in the "Parse" section of variables.
Posted by "arosien (via GitHub)" <gi...@apache.org>.
arosien merged PR #436:
URL: https://github.com/apache/daffodil-vscode/pull/436
--
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