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:53:15 UTC
[GitHub] [daffodil-vscode] mbeckerle opened a new issue, #615: Need a way to use pre-compiled DFDL schemas
mbeckerle opened a new issue, #615:
URL: https://github.com/apache/daffodil-vscode/issues/615
Large DFDL schemas can take upwards of a minute to compile.
We must have a way to specify a pre-compiled DFDL schema rather than being required to compile the schema "on the fly" at startup every time you click to debug a test.
A parameter specifying a pre-compiled schema location is the minimum thing needed.
--
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] lrbarber commented on issue #615: Need a way to use pre-compiled DFDL schemas
Posted by "lrbarber (via GitHub)" <gi...@apache.org>.
lrbarber commented on issue #615:
URL: https://github.com/apache/daffodil-vscode/issues/615#issuecomment-1536446329
Does the precompiled schema have any information in it that would relate it to the .xsd file?
How can the source schema be displayed in the debugger if we don't have the original code that was compiled?
What if there is a link, but the .xsd file has been changed since the compiled version was saved?
--
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] stevedlawrence commented on issue #615: Need a way to use pre-compiled DFDL schemas
Posted by "stevedlawrence (via GitHub)" <gi...@apache.org>.
stevedlawrence commented on issue #615:
URL: https://github.com/apache/daffodil-vscode/issues/615#issuecomment-1536233169
Yeah, that's usually what we mean by a pre-compiled schema.
Note that a pre-compiled schema using that command is basically just a serialized `DataProcessor`. Maybe an alternatively is to have the extension cache DataProcessor it builds for reuse, and only rebuild it when the schema changes?
--
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 issue #615: Need a way to use pre-compiled DFDL schemas
Posted by "arosien (via GitHub)" <gi...@apache.org>.
arosien commented on issue #615:
URL: https://github.com/apache/daffodil-vscode/issues/615#issuecomment-1721638554
> I see the basic feature as a caching problem, but I'm worried detecting transitively-included schema updates is too difficult to solve. Is there perhaps a variation of compiling a schema that only validates the syntactical structure (which handles includes)?
Another issue mentioned a way: https://github.com/apache/daffodil-vscode/issues/76#issuecomment-1029178015
--
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 #615: Need a way to use pre-compiled DFDL schemas
Posted by "mbeckerle (via GitHub)" <gi...@apache.org>.
mbeckerle commented on issue #615:
URL: https://github.com/apache/daffodil-vscode/issues/615#issuecomment-1536379931
Yeah, in the long run, having an IDE that eliminates all this schema compilation noise and just manages properly a cache of them would be great.
Of course just making compilation of schemas way faster would be better, but that's fairly hard to do, and runtime performance is more critical than schema compilation time, IF that is, one can avoid the schema compilation time as much as possible.
The TDML runner tries to cache compiled schemas for tests. Maybe that functionality should be exposed differently so that it can be reused from the IDE?
--
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 #615: Need a way to use pre-compiled DFDL schemas
Posted by "scholarsmate (via GitHub)" <gi...@apache.org>.
scholarsmate commented on issue #615:
URL: https://github.com/apache/daffodil-vscode/issues/615#issuecomment-1536223417
Pre-compiled schema meaning the output of the save-parser subcommand (ref: https://daffodil.apache.org/cli/#save-parser-subcommand)?
--
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] stevedlawrence commented on issue #615: Need a way to use pre-compiled DFDL schemas
Posted by "stevedlawrence (via GitHub)" <gi...@apache.org>.
stevedlawrence commented on issue #615:
URL: https://github.com/apache/daffodil-vscode/issues/615#issuecomment-1536456316
The precompiled schema has all the same information in it that a normal DataProcessor has. As long as the pre-compiled parser was built using the same files that VS Code is looking at, I think it should work the same?
> What if there is a link, but the .xsd file has been changed since the compiled version was saved?
Could you detect if the schema files are newer than the pre-compiled file and output a warning.
--
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 issue #615: Need a way to use pre-compiled DFDL schemas
Posted by "arosien (via GitHub)" <gi...@apache.org>.
arosien commented on issue #615:
URL: https://github.com/apache/daffodil-vscode/issues/615#issuecomment-1719907019
I see the basic feature as a caching problem, but I'm worried detecting transitively-included schema updates is too difficult to solve. Is there perhaps a variation of compiling a schema that only validates the syntactical structure (which handles includes)?
--
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