JeremyYao commented on issue #974: URL: https://github.com/apache/daffodil-vscode/issues/974#issuecomment-2698479017
## More Test Cases Follow instructions as outlined in https://github.com/apache/daffodil-vscode/issues/974#issuecomment-2698420246, but copy the corresponding DFDL schemas and input files. The corresponding DFDL schemas and input files are contained in the following zip file. Note that you will need to include all of the files in the .zip as the specified DFDL files depend on the other files in there. [extra_test_cases.zip](https://github.com/user-attachments/files/19075471/extra_test_cases.zip) ### Parse error Powershell Output ```PowerShell PS C:\Users\jeremy.yao\repos\daffodilWorkspace\PPT Examples\974Test> daffodil parse --schema .\test.dfdl_parse_err.dfdl.xsd .\test_parse_err.txt [error] Parse Error: Unable to parse xs:integer from text: According to all known laws of aviation, there is no way a bee should be able to fly Schema context: label Location line 16 column 18 in test.dfdl_parse_err.dfdl.xsd Data location was preceding byte 84 ``` - DFDL Schema: test.dfdl_parse_err.dfdl.xsd - Test file: test_parse_err.txt ### Schema Definition Error ```PowerShell PS C:\Users\jeremy.yao\repos\daffodilWorkspace\PPT Examples\974Test> daffodil parse --schema .\test.dfdl_parse_err.dfdl.xsd .\test_parse_err.txt [error] Parse Error: Unable to parse xs:integer from text: According to all known laws of aviation, there is no way a bee should be able to fly Schema context: label Location line 16 column 18 in test.dfdl_parse_err.dfdl.xsd Data location was preceding byte 84 PS C:\Users\jeremy.yao\repos\daffodilWorkspace\PPT Examples\974Test> daffodil parse --schema .\bad_dfdl.dfdl.xsd .\test_parse_err.txt [error] Schema Definition Error: Type integer cannot have lengthKind='implicit' when representation='text' Schema context: label Location line 16 column 18 in bad_dfdl.dfdl.xsd ``` - DFDL Schema: test.dfdl_parse_err.dfdl.xsd - Test file: test_parse_err.txt -- 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]
