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/06/05 13:59:22 UTC
[GitHub] [daffodil-vscode] mbeckerle opened a new issue, #648: No error information is displayed after parse error from assert
mbeckerle opened a new issue, #648:
URL: https://github.com/apache/daffodil-vscode/issues/648
Trying to test the vscode extension with the PCAP DFDL schema.
I clobbered the magic number in the first bytes of an icmp1.cap file. This fails an assert at line 97 of pcap.dfdl.xsd, which is the first element of simple type in the schema.
I step through with the debugger, and nothing displays *anything* about the assert failure. Execution ends. A little pop-up dialog says it wrote my infoset out, which it didn't. There's nothing showing that anything went wrong. All panels on the left are blank.
I was testing 1.3.0-RC2 version of the vscode extension.
--
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] mbeckerle closed issue #648: No error information is displayed after parse error from assert
Posted by "mbeckerle (via GitHub)" <gi...@apache.org>.
mbeckerle closed issue #648: No error information is displayed after parse error from assert
URL: https://github.com/apache/daffodil-vscode/issues/648
--
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] shanedell commented on issue #648: No error information is displayed after parse error from assert
Posted by "shanedell (via GitHub)" <gi...@apache.org>.
shanedell commented on issue #648:
URL: https://github.com/apache/daffodil-vscode/issues/648#issuecomment-1587841307
@mbeckerle Would a good fix this to be to output the error message from the assert to the debugger console? Also not displaying that dialog about the infoset if it didn't actually get made.
--
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 #648: No error information is displayed after parse error from assert
Posted by "arosien (via GitHub)" <gi...@apache.org>.
arosien commented on issue #648:
URL: https://github.com/apache/daffodil-vscode/issues/648#issuecomment-1629865925
I also saw the comments in #666 about feedback mechanisms. Instead of ending the debug session, we could raise an exception which would pause the debugger and the UI would show the assertion failure. Any subsequent "next" action would end the parse.
In contrast the current mechanism sends the error info, which we then log or show a dialog, but the debug session ends concurrently.
--
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 #648: No error information is displayed after parse error from assert
Posted by "mbeckerle (via GitHub)" <gi...@apache.org>.
mbeckerle commented on issue #648:
URL: https://github.com/apache/daffodil-vscode/issues/648#issuecomment-1601753157
Testing 1.3.0-RC3
You got this output, which would be great:
```java.lang.Error: Parse Error: Assertion failed: Magic number was not 0xA1B2C3D4 (for bigEndian) or 0xD4C3B2A1 (for littleEndian).
Schema context: MagicNumber Location line 87 column 14 in file:/Users/sdell/apache/sampleWorkspace/dfdl-pcap/src/main/resources/com/tresys/pcap/xsd/pcap.dfdl.xsd
Data location was preceding byte 4
```
Alas, my debug console window is empty, and the terminal window does not contain the characters "assert" (case insensitive). So I am simply not getting anything to indicate an error occurred.
--
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] shanedell commented on issue #648: No error information is displayed after parse error from assert
Posted by "shanedell (via GitHub)" <gi...@apache.org>.
shanedell commented on issue #648:
URL: https://github.com/apache/daffodil-vscode/issues/648#issuecomment-1602819404
@mbeckerle If the above comment fixes the issue, we have another GitHub issue about making testing local changes to the debugger easier. If this is the issue you see I think it would be in the best interest to figure out another way of extracting the debugger or bundling the debugger so that you always use the latest and won't hit this issue anymore
--
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] shanedell commented on issue #648: No error information is displayed after parse error from assert
Posted by "shanedell (via GitHub)" <gi...@apache.org>.
shanedell commented on issue #648:
URL: https://github.com/apache/daffodil-vscode/issues/648#issuecomment-1601805603
@mbeckerle can you try removing this folder: /home/mbeckerle/.local/share/daffodil-dap/ and run the debug again? I believe you are using an old version of the debugger and that is why you are not seeing the output you should.
--
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 #648: No error information is displayed after parse error from assert
Posted by "arosien (via GitHub)" <gi...@apache.org>.
arosien commented on issue #648:
URL: https://github.com/apache/daffodil-vscode/issues/648#issuecomment-1629732560
While this fix adds the error to the (terminal) console, we could also handle it by writing it to the "debug console":
<img width="1432" alt="Screen Shot 2023-07-10 at 2 05 21 PM" src="https://github.com/apache/daffodil-vscode/assets/31163/c91eab8b-0359-4736-8e3a-c427c4262b49">
or we could create a special event that causes a dialog/popup, like the current behavior when there is a compilation error in the schema.
What do you think @mbeckerle @shanedell?
--
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 #648: No error information is displayed after parse error from assert
Posted by "mbeckerle (via GitHub)" <gi...@apache.org>.
mbeckerle commented on issue #648:
URL: https://github.com/apache/daffodil-vscode/issues/648#issuecomment-1589573154
I created an icmp1.bad.cap where I hammered the first byte to be 0x00. Using that as the data file causes the failure.
--
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] shanedell commented on issue #648: No error information is displayed after parse error from assert
Posted by "shanedell (via GitHub)" <gi...@apache.org>.
shanedell commented on issue #648:
URL: https://github.com/apache/daffodil-vscode/issues/648#issuecomment-1591977031
@mbeckerle Does this output from the terminal looks acceptable?
```bash
2023-06-14 16:58:58,763 [io-compute-5] INFO o.a.d.d.d.DAPodil -
******************************************************
A DAP server for debugging Daffodil schema processors.
Build info:
version: 1.3.0
daffodilVersion: 3.4.0
scalaVersion: 2.12.15
sbtVersion: 1.8.2
******************************************************
2023-06-14 16:58:58,765 [io-compute-5] INFO o.a.d.d.d.DAPodil - launched with options listenPort: 4711, listenTimeout: 10 seconds
2023-06-14 16:58:58,773 [io-compute-5] INFO o.a.d.d.d.DAPodil - waiting at tcp://0.0.0.0:4711
2023-06-14 16:59:02,337 [io-compute-blocker-5] INFO o.a.d.d.d.DAPodil - connected at tcp://0.0.0.0:4711
2023-06-14 16:59:02,465 [io-compute-2] INFO o.a.d.d.d.DAPSession - R> #1 initialize {"clientID":"vscode","clientName":"Visual Studio Code","adapterID":"dfdl","pathFormat":"path","linesStartAt1":true,"columnsStartAt1":true,"supportsVariableType":true,"supportsVariablePaging":true,"supportsRunInTerminalRequest":true,"locale":"en","supportsProgressReporting":true,"supportsInvalidatedEvent":true,"supportsMemoryReferences":true,"supportsArgsCanBeInterpretedByShell":true,"supportsMemoryEvent":true,"supportsStartDebuggingRequest":true}
2023-06-14 16:59:02,486 [io-compute-11] INFO o.a.d.d.d.DAPSession - <R #1 initialize success {"supportsConfigurationDoneRequest":true,"supportsHitConditionalBreakpoints":false,"supportsConditionalBreakpoints":false,"supportsEvaluateForHovers":false,"supportsCompletionsRequest":false,"supportsRestartFrame":false,"supportsSetVariable":false,"supportsRestartRequest":false,"supportTerminateDebuggee":false,"supportsDelayedStackTraceLoading":false,"supportsLogPoints":false,"supportsExceptionInfoRequest":false,"supportsDataBreakpoints":false,"supportsClipboardContext":false,"supportsLoadedSourcesRequest":false}
2023-06-14 16:59:02,487 [io-compute-blocker-11] INFO o.a.d.d.d.DAPSession - <E initialized
2023-06-14 16:59:02,489 [io-compute-4] INFO o.a.d.d.d.DAPSession - R> #2 launch {"type":"dfdl","request":"launch","name":"pcap on icmp1.cap classpath with ethernetIP directory","program":"/Users/sdell/apache/sampleWorkspace/dfdl-pcap/src/main/resources/com/tresys/pcap/xsd/pcap.dfdl.xsd","stopOnEntry":true,"data":"/Users/sdell/apache/sampleWorkspace/dfdl-pcap/src/test/resources/com/tresys/pcap/data/icmp1.bad.cap","infosetOutput":{"type":"file","path":"/tmp/pcap-icmp1.infoset.xml"},"debugServer":4711,"openHexView":false,"openInfosetView":false,"openInfosetDiffView":false,"useExistingServer":false,"daffodilDebugClasspath":"/Users/sdell/apache/sampleWorkspace/dfdl-ethernet/src/main/resources:/Users/sdell/apache/sampleWorkspace/dfdl-ethernet/target/classes","__configurationTarget":6,"__sessionId":"93f0320e-82f5-419c-902b-e16a25054602"}
2023-06-14 16:59:02,490 [io-compute-2] INFO o.a.d.d.d.DAPSession - R> #3 setBreakpoints {"source":{"name":"pcap.dfdl.xsd","path":"/Users/sdell/apache/sampleWorkspace/dfdl-pcap/src/main/resources/com/tresys/pcap/xsd/pcap.dfdl.xsd"},"lines":[87,97],"breakpoints":[{"line":87},{"line":97}],"sourceModified":false}
ERROR StatusLogger Log4j2 could not find a logging implementation. Please add log4j-core to the classpath. Using SimpleLogger to log to the console...
2023-06-14 16:59:04,332 [io-compute-10] DEBUG o.a.d.d.d.DAPodil - awaiting first stack frame
2023-06-14 16:59:04,392 [io-compute-0] DEBUG o.a.d.d.d.P.DaffodilDebugger - pre-control await
2023-06-14 16:59:04,395 [io-compute-0] DEBUG o.a.d.d.d.P.DaffodilDebugger - post-control await
2023-06-14 16:59:04,395 [io-compute-0] DEBUG o.a.d.d.d.P.DaffodilDebugger - pre-checkBreakpoints
2023-06-14 16:59:04,395 [io-compute-10] DEBUG o.a.d.d.d.P.DaffodilDebugger - pre-control await
2023-06-14 16:59:04,410 [io-compute-10] DEBUG o.a.d.d.d.DAPodil - awaiting first stack frame: got it
2023-06-14 16:59:04,415 [io-compute-12] DEBUG o.a.d.d.d.DAPodil - started Launched
2023-06-14 16:59:04,415 [io-compute-12] INFO o.a.d.d.d.DAPSession - <E thread started
2023-06-14 16:59:04,418 [io-compute-blocker-12] INFO o.a.d.d.d.DAPSession - <R #2 launch success null
2023-06-14 16:59:04,420 [io-compute-4] DEBUG o.a.d.d.d.DAPodil - sourceEventsDelivery: Succeeded
2023-06-14 16:59:04,421 [io-compute-8] INFO o.a.d.d.d.DAPSession - <E stopped entry
2023-06-14 16:59:04,422 [io-compute-15] INFO o.a.d.d.d.DAPSession - <E daffodil.config
2023-06-14 16:59:04,424 [io-compute-7] INFO o.a.d.d.d.DAPSession - <E daffodil.data
2023-06-14 16:59:04,424 [io-compute-blocker-12] INFO o.a.d.d.d.DAPSession - <R #3 setBreakpoints success {"breakpoints":[{"id":0,"verified":true,"line":87,"message":""},{"id":1,"verified":true,"line":97,"message":""}]}
2023-06-14 16:59:04,434 [io-compute-13] INFO o.a.d.d.d.DAPSession - R> #4 threads null
2023-06-14 16:59:04,435 [io-compute-8] INFO o.a.d.d.d.DAPSession - <R #4 threads success {"threads":[{"id":1,"name":"daffodil"}]}
2023-06-14 16:59:04,439 [io-compute-2] INFO o.a.d.d.d.DAPSession - R> #5 configurationDone null
2023-06-14 16:59:04,439 [io-compute-2] INFO o.a.d.d.d.DAPSession - <R #5 configurationDone success null
2023-06-14 16:59:04,440 [io-compute-0] INFO o.a.d.d.d.DAPSession - R> #6 stackTrace {"threadId":1,"startFrame":0,"levels":20}
2023-06-14 16:59:04,442 [io-compute-blocker-2] INFO o.a.d.d.d.DAPSession - <R #6 stackTrace success {"stackFrames":[{"id":1,"source":{"name":"pcap.dfdl.xsd","path":"/Users/sdell/apache/sampleWorkspace/dfdl-pcap/src/main/resources/com/tresys/pcap/xsd/pcap.dfdl.xsd","sourceReference":0},"line":36,"column":0,"name":"PCAP"}],"totalFrames":1}
2023-06-14 16:59:04,446 [io-compute-3] INFO o.a.d.d.d.DAPSession - R> #7 threads null
2023-06-14 16:59:04,447 [io-compute-4] INFO o.a.d.d.d.DAPSession - <R #7 threads success {"threads":[{"id":1,"name":"daffodil"}]}
2023-06-14 16:59:04,521 [io-compute-0] INFO o.a.d.d.d.DAPSession - R> #8 threads null
2023-06-14 16:59:04,521 [io-compute-3] INFO o.a.d.d.d.DAPSession - <R #8 threads success {"threads":[{"id":1,"name":"daffodil"}]}
2023-06-14 16:59:04,855 [io-compute-3] INFO o.a.d.d.d.DAPSession - R> #9 scopes {"frameId":1}
2023-06-14 16:59:04,861 [io-compute-13] INFO o.a.d.d.d.DAPSession - <R #9 scopes success {"scopes":[{"name":"Parse","variablesReference":1,"expensive":false},{"name":"Schema","variablesReference":2,"expensive":false},{"name":"Data","variablesReference":3,"expensive":false}]}
2023-06-14 16:59:04,863 [io-compute-1] INFO o.a.d.d.d.DAPSession - R> #10 variables {"variablesReference":1}
2023-06-14 16:59:04,867 [io-compute-14] INFO o.a.d.d.d.DAPSession - <R #10 variables success {"variables":[{"name":"Delimiters","value":"","variablesReference":9,"namedVariables":0,"indexedVariables":0},{"name":"Diagnostics","value":"","variablesReference":10,"namedVariables":0,"indexedVariables":0},{"name":"Points of uncertainty","value":"","variablesReference":8,"namedVariables":0,"indexedVariables":0},{"name":"childIndex","value":"1","variablesReference":0,"namedVariables":0,"indexedVariables":0},{"name":"groupIndex","value":"1","variablesReference":0,"namedVariables":0,"indexedVariables":0},{"name":"hidden","value":"false","type":"bool","variablesReference":0,"namedVariables":0,"indexedVariables":0},{"name":"occursIndex","value":"1","variablesReference":0,"namedVariables":0,"indexedVariables":0}]}
2023-06-14 16:59:08,540 [io-compute-7] INFO o.a.d.d.d.DAPSession - R> #11 continue {"threadId":1}
2023-06-14 16:59:08,542 [io-compute-1] INFO o.a.d.d.d.DAPSession - <R #11 continue success null
2023-06-14 16:59:08,543 [io-compute-3] DEBUG o.a.d.d.d.P.DaffodilDebugger - post-control await
2023-06-14 16:59:08,543 [io-compute-3] DEBUG o.a.d.d.d.P.DaffodilDebugger - pre-checkBreakpoints
2023-06-14 16:59:08,544 [io-compute-1] INFO o.a.d.d.d.DAPSession - <E daffodil.data
2023-06-14 16:59:08,545 [io-compute-1] DEBUG o.a.d.d.d.P.DaffodilDebugger - pre-control await
2023-06-14 16:59:08,545 [io-compute-0] INFO o.a.d.d.d.DAPSession - <E daffodil.infoset
2023-06-14 16:59:08,545 [io-compute-1] DEBUG o.a.d.d.d.P.DaffodilDebugger - post-control await
2023-06-14 16:59:08,545 [io-compute-1] DEBUG o.a.d.d.d.P.DaffodilDebugger - pre-checkBreakpoints
2023-06-14 16:59:08,546 [io-compute-3] DEBUG o.a.d.d.d.P.DaffodilDebugger - pre-control await
2023-06-14 16:59:08,546 [io-compute-3] DEBUG o.a.d.d.d.P.DaffodilDebugger - post-control await
2023-06-14 16:59:08,546 [io-compute-3] DEBUG o.a.d.d.d.P.DaffodilDebugger - pre-checkBreakpoints
2023-06-14 16:59:08,548 [io-compute-3] INFO o.a.d.d.d.DAPSession - <E stopped breakpoint
2023-06-14 16:59:08,554 [io-compute-10] INFO o.a.d.d.d.DAPSession - R> #12 threads null
2023-06-14 16:59:08,554 [io-compute-5] INFO o.a.d.d.d.DAPSession - <R #12 threads success {"threads":[{"id":1,"name":"daffodil"}]}
2023-06-14 16:59:08,558 [io-compute-2] INFO o.a.d.d.d.DAPSession - R> #13 stackTrace {"threadId":1,"startFrame":0,"levels":20}
2023-06-14 16:59:08,559 [io-compute-3] INFO o.a.d.d.d.DAPSession - <R #13 stackTrace success {"stackFrames":[{"id":4,"source":{"name":"pcap.dfdl.xsd","path":"/Users/sdell/apache/sampleWorkspace/dfdl-pcap/src/main/resources/com/tresys/pcap/xsd/pcap.dfdl.xsd","sourceReference":0},"line":87,"column":0,"name":"MagicNumber"},{"id":3,"source":{"name":"pcap.dfdl.xsd","path":"/Users/sdell/apache/sampleWorkspace/dfdl-pcap/src/main/resources/com/tresys/pcap/xsd/pcap.dfdl.xsd","sourceReference":0},"line":76,"column":0,"name":"PCAPHeader"},{"id":2,"source":{"name":"pcap.dfdl.xsd","path":"/Users/sdell/apache/sampleWorkspace/dfdl-pcap/src/main/resources/com/tresys/pcap/xsd/pcap.dfdl.xsd","sourceReference":0},"line":36,"column":0,"name":"PCAP"},{"id":1,"source":{"name":"pcap.dfdl.xsd","path":"/Users/sdell/apache/sampleWorkspace/dfdl-pcap/src/main/resources/com/tresys/pcap/xsd/pcap.dfdl.xsd","sourceReference":0},"line":36,"column":0,"name":"PCAP"}],"totalFrames":4}
2023-06-14 16:59:08,965 [io-compute-7] INFO o.a.d.d.d.DAPSession - R> #14 scopes {"frameId":4}
2023-06-14 16:59:08,967 [io-compute-8] INFO o.a.d.d.d.DAPSession - <R #14 scopes success {"scopes":[{"name":"Parse","variablesReference":37,"expensive":false},{"name":"Schema","variablesReference":38,"expensive":false},{"name":"Data","variablesReference":39,"expensive":false}]}
2023-06-14 16:59:08,972 [io-compute-2] INFO o.a.d.d.d.DAPSession - R> #15 variables {"variablesReference":37}
2023-06-14 16:59:08,973 [io-compute-7] INFO o.a.d.d.d.DAPSession - <R #15 variables success {"variables":[{"name":"Delimiters","value":"","variablesReference":45,"namedVariables":0,"indexedVariables":0},{"name":"Diagnostics","value":"","variablesReference":46,"namedVariables":0,"indexedVariables":0},{"name":"Points of uncertainty","value":"","variablesReference":44,"namedVariables":0,"indexedVariables":0},{"name":"childIndex","value":"1","variablesReference":0,"namedVariables":0,"indexedVariables":0},{"name":"groupIndex","value":"1","variablesReference":0,"namedVariables":0,"indexedVariables":0},{"name":"hidden","value":"false","type":"bool","variablesReference":0,"namedVariables":0,"indexedVariables":0},{"name":"occursIndex","value":"1","variablesReference":0,"namedVariables":0,"indexedVariables":0}]}
2023-06-14 16:59:09,787 [io-compute-1] INFO o.a.d.d.d.DAPSession - R> #16 continue {"threadId":1}
2023-06-14 16:59:09,789 [io-compute-0] INFO o.a.d.d.d.DAPSession - <R #16 continue success null
2023-06-14 16:59:09,794 [io-compute-5] DEBUG o.a.d.d.d.P.DaffodilDebugger - infoset queue completed
2023-06-14 16:59:09,794 [io-compute-6] DEBUG o.a.d.d.d.Parse - infosetChanges (orig): Succeeded
2023-06-14 16:59:09,794 [io-compute-2] DEBUG o.a.d.d.d.DAPodil - deliverStoppedEvents: Succeeded
2023-06-14 16:59:09,795 [io-compute-3] DEBUG o.a.d.d.d.Parse - deliverParseData: Succeeded
2023-06-14 16:59:09,795 [io-compute-3] DEBUG o.a.d.d.d.DAPodil - dapEvents: Succeeded
2023-06-14 16:59:09,803 [io-compute-0] INFO o.a.d.d.d.DAPSession - <E thread exited
java.lang.Error: Parse Error: Assertion failed: Magic number was not 0xA1B2C3D4 (for bigEndian) or 0xD4C3B2A1 (for littleEndian).
Schema context: MagicNumber Location line 87 column 14 in file:/Users/sdell/apache/sampleWorkspace/dfdl-pcap/src/main/resources/com/tresys/pcap/xsd/pcap.dfdl.xsd
Data location was preceding byte 4
at org.apache.daffodil.debugger.dap.Parse$$anon$1.$anonfun$run$2(Parse.scala:111)
at as @ com.monovore.decline.effect.CommandIOApp$.addVersionFlag(CommandIOApp.scala:67)
2023-06-14 16:59:09,803 [io-compute-blocker-14] INFO o.a.d.d.d.DAPSession - <E terminated
2023-06-14 16:59:09,804 [io-compute-blocker-1] DEBUG o.a.d.d.d.Parse - parsing: Errored(java.lang.Error: Parse Error: Assertion failed: Magic number was not 0xA1B2C3D4 (for bigEndian) or 0xD4C3B2A1 (for littleEndian).
Schema context: MagicNumber Location line 87 column 14 in file:/Users/sdell/apache/sampleWorkspace/dfdl-pcap/src/main/resources/com/tresys/pcap/xsd/pcap.dfdl.xsd
Data location was preceding byte 4)
java.lang.Error: Parse Error: Assertion failed: Magic number was not 0xA1B2C3D4 (for bigEndian) or 0xD4C3B2A1 (for littleEndian).
Schema context: MagicNumber Location line 87 column 14 in file:/Users/sdell/apache/sampleWorkspace/dfdl-pcap/src/main/resources/com/tresys/pcap/xsd/pcap.dfdl.xsd
Data location was preceding byte 4
at org.apache.daffodil.debugger.dap.Parse$$anon$1.$anonfun$run$2(Parse.scala:111)
at as @ com.monovore.decline.effect.CommandIOApp$.addVersionFlag(CommandIOApp.scala:67)
2023-06-14 16:59:09,812 [io-compute-10] INFO o.a.d.d.d.DAPSession - R> #17 disconnect {"restart":false}
2023-06-14 16:59:09,813 [io-compute-3] INFO o.a.d.d.d.DAPSession - <R #17 disconnect success null
2023-06-14 16:59:09,813 [io-compute-blocker-12] DEBUG o.a.d.d.d.DAPodil - launched: Succeeded
2023-06-14 16:59:09,813 [io-compute-blocker-12] DEBUG o.a.d.d.d.Parse - signalling a stop
2023-06-14 16:59:09,814 [io-compute-blocker-12] DEBUG o.a.d.d.d.Parse - parse done, no interruption
2023-06-14 16:59:09,818 [io-compute-6] DEBUG o.a.d.d.d.DAPodil - debugee: Succeeded
2023-06-14 16:59:09,820 [io-compute-6] ERROR o.a.d.d.d.DAPodil - unhandled error
java.lang.Error: Parse Error: Assertion failed: Magic number was not 0xA1B2C3D4 (for bigEndian) or 0xD4C3B2A1 (for littleEndian).
Schema context: MagicNumber Location line 87 column 14 in file:/Users/sdell/apache/sampleWorkspace/dfdl-pcap/src/main/resources/com/tresys/pcap/xsd/pcap.dfdl.xsd
Data location was preceding byte 4
at org.apache.daffodil.debugger.dap.Parse$$anon$1.$anonfun$run$2(Parse.scala:111)
at as @ com.monovore.decline.effect.CommandIOApp$.addVersionFlag(CommandIOApp.scala:67)
java.lang.Error: Parse Error: Assertion failed: Magic number was not 0xA1B2C3D4 (for bigEndian) or 0xD4C3B2A1 (for littleEndian).
Schema context: MagicNumber Location line 87 column 14 in file:/Users/sdell/apache/sampleWorkspace/dfdl-pcap/src/main/resources/com/tresys/pcap/xsd/pcap.dfdl.xsd
Data location was preceding byte 4
at org.apache.daffodil.debugger.dap.Parse$$anon$1.$anonfun$run$2(Parse.scala:111)
at as @ com.monovore.decline.effect.CommandIOApp$.addVersionFlag(CommandIOApp.scala:67)
2023-06-14 16:59:09,820 [io-compute-10] DEBUG o.a.d.d.d.DAPodil - whenDone: completed
2023-06-14 16:59:09,820 [io-compute-10] DEBUG o.a.d.d.d.DAPodil - hotswap: Succeeded
2023-06-14 16:59:09,820 [io-compute-10] INFO o.a.d.d.d.DAPodil - disconnected at tcp://0.0.0.0:4711
```
--
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 #648: No error information is displayed after parse error from assert
Posted by "mbeckerle (via GitHub)" <gi...@apache.org>.
mbeckerle commented on issue #648:
URL: https://github.com/apache/daffodil-vscode/issues/648#issuecomment-1603324708
The back trace is a Java 17 issue. If I use Java 11 I do not get this backtrace.
--
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] shanedell commented on issue #648: No error information is displayed after parse error from assert
Posted by "shanedell (via GitHub)" <gi...@apache.org>.
shanedell commented on issue #648:
URL: https://github.com/apache/daffodil-vscode/issues/648#issuecomment-1629931415
@arosien I like displaying it in the "Debug Console". I wouldn't do the pop up or dialog because we had that before and it was removed as @mbeckerle said it didn't need to be a blocking dialog
--
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 #648: No error information is displayed after parse error from assert
Posted by "mbeckerle (via GitHub)" <gi...@apache.org>.
mbeckerle commented on issue #648:
URL: https://github.com/apache/daffodil-vscode/issues/648#issuecomment-1601800500
I am testing 1.3.0-RC3.
Complete output from terminal is attached in a file. Note there is a backtrace.
[terminal-output.zip](https://github.com/apache/daffodil-vscode/files/11826857/terminal-output.zip)
--
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 #648: No error information is displayed after parse error from assert
Posted by "mbeckerle (via GitHub)" <gi...@apache.org>.
mbeckerle commented on issue #648:
URL: https://github.com/apache/daffodil-vscode/issues/648#issuecomment-1603311093
Uninstalling the debugger should delete ~/.local/share/daffodil-dap if it installs it there.
I do indeed get an assert-related error to the terminal now. But then a big noisy backtrace due to exception in initializer error.
Can we turn down the Logging level from INFO to remove some of the noise from the terminal?
```
java.lang.Error: Parse Error: Assertion failed: Magic number was not 0xA1B2C3D4 (for bigEndian) or 0xD4C3B2A1 (for littleEndian).
Schema context: MagicNumber Location line 87 column 14 in file:/home/mbeckerle/dataiti/opensource/DFDLSchemas/PCAP/src/main/resources/com/tresys/pcap/xsd/pcap.dfdl.xsd
Data location was preceding byte 4
at org.apache.daffodil.debugger.dap.Parse$$anon$1.$anonfun$run$2(Parse.scala:113)
at as @ com.monovore.decline.effect.CommandIOApp$.addVersionFlag(CommandIOApp.scala:67)
2023-06-22 16:54:18,313 [io-compute-3] INFO o.a.d.d.d.DAPSession - R> #16 disconnect {"restart":false}
2023-06-22 16:54:18,315 [io-compute-7] INFO o.a.d.d.d.DAPSession - <R #16 disconnect success null
2023-06-22 16:54:18,316 [io-compute-blocker-5] DEBUG o.a.d.d.d.DAPodil - launched: Succeeded
2023-06-22 16:54:18,316 [io-compute-blocker-5] DEBUG o.a.d.d.d.Parse - signalling a stop
2023-06-22 16:54:18,317 [io-compute-blocker-5] DEBUG o.a.d.d.d.Parse - parse done, no interruption
Exception in thread "io-compute-6" java.lang.ExceptionInInitializerError
at com.sun.xml.bind.v2.runtime.reflect.opt.AccessorInjector.prepare(AccessorInjector.java:81)
at com.sun.xml.bind.v2.runtime.reflect.opt.OptimizedAccessorFactory.get(OptimizedAccessorFactory.java:179)
at com.sun.xml.bind.v2.runtime.reflect.Accessor$FieldReflection.optimize(Accessor.java:285)
at com.sun.xml.bind.v2.runtime.property.ArrayProperty.<init>(ArrayProperty.java:68)
at com.sun.xml.bind.v2.runtime.property.ArrayERProperty.<init>(ArrayERProperty.java:88)
at com.sun.xml.bind.v2.runtime.property.ArrayElementProperty.<init>(ArrayElementProperty.java:100)
at com.sun.xml.bind.v2.runtime.property.ArrayElementNodeProperty.<init>(ArrayElementNodeProperty.java:62)
at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:77)
at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.base/java.lang.reflect.Constructor.newInstanceWithCaller(Constructor.java:499)
at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:480)
at com.sun.xml.bind.v2.runtime.property.PropertyFactory.create(PropertyFactory.java:128)
at com.sun.xml.bind.v2.runtime.ClassBeanInfoImpl.<init>(ClassBeanInfoImpl.java:181)
at com.sun.xml.bind.v2.runtime.JAXBContextImpl.getOrCreate(JAXBContextImpl.java:503)
...
```
--
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] shanedell commented on issue #648: No error information is displayed after parse error from assert
Posted by "shanedell (via GitHub)" <gi...@apache.org>.
shanedell commented on issue #648:
URL: https://github.com/apache/daffodil-vscode/issues/648#issuecomment-1589604606
@mbeckerle Thank you for this information this helped me reproduce the issue! I will get working on a fix, thank you again
--
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 #648: No error information is displayed after parse error from assert
Posted by "mbeckerle (via GitHub)" <gi...@apache.org>.
mbeckerle commented on issue #648:
URL: https://github.com/apache/daffodil-vscode/issues/648#issuecomment-1589590424
As an interim, outputting the error info to the debug console makes sense, and perhaps it should always go there, but there are all those information displays on the left of the VSCode window that seem like they should be populated with the state of the failed (or running) parse/unparse, and ending the parse/unparse shouldn't clear them.
--
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] shanedell closed issue #648: No error information is displayed after parse error from assert
Posted by "shanedell (via GitHub)" <gi...@apache.org>.
shanedell closed issue #648: No error information is displayed after parse error from assert
URL: https://github.com/apache/daffodil-vscode/issues/648
--
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 #648: No error information is displayed after parse error from assert
Posted by "mbeckerle (via GitHub)" <gi...@apache.org>.
mbeckerle commented on issue #648:
URL: https://github.com/apache/daffodil-vscode/issues/648#issuecomment-1603325354
With a caveat that 1.3.0-RC3 still doesn't work with Java 17 (release note), this issue can be closed.
--
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] shanedell commented on issue #648: No error information is displayed after parse error from assert
Posted by "shanedell (via GitHub)" <gi...@apache.org>.
shanedell commented on issue #648:
URL: https://github.com/apache/daffodil-vscode/issues/648#issuecomment-1601759935
@mbeckerle are you on the terminal tab? By default I think it ends and goes to console or debug console but those won't have the output. There should a tab called Terminal that you can click on and see all the information from the debugger
--
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