I was able to get past the inability to start the debugger, and try a few things by filling in the tdml-related entries in the launch.json (I had assumed they were optional).
My vote remains -1. Debugging seems to have regressed substantially in the basic debugging functionality (breakpoints and stepping) since the prior release. Here's a narration of the debugging I am attempting: I am debugging PCAP. This uses the ethernetIP schema, which jar file must be put on the daffodil debug classpath. The git hash I have for PCAP is 1f7d5610e97ec6914fa00478116154e440a7dfc8 The git has I have for EthernetIP is 3a0de0c4d452a8c1c5d8f77c8e1580991cbc27b0 I have verified that `sbt test` works. The schema is all working. When I try to do simple breakpoint debugging with the VSCode extension, I get nowhere. I set a breakpoint in the ethernetIP.dfdl.xsd line 68 (The MACDest element). I start a Daffodil Debug session, and hit the continue. It does not stop at the breakpoint. It just parses the entire file. So, I start again. I put a breakpoint in pcap.dfdl.xsd line 168 (The Ethernet element). I hit continue. It stops at the breakpoint in the pcap.dfdl.xsd line 168. Then I step-over until I am in the ethernetIP.dfdl.xsd file. That works. Then I attempt to set a breakpoint at line 70, the Ethertype element which is a couple of elements down from the current location. Except no breakpoint it set. Rather, execution resumes with a bunch of output going to the debug console, but this output is then quickly erased somehow. I'm not able to capture it before the panel gets cleared. Execution terminates, a dialog pops up saying the infoset.xml was written out, but that file is empty. That dialog also spontaneously goes away, not waiting to be dismissed. >From this I've concluded that the basics are not working sufficiently. -mikeb On Fri, Apr 28, 2023 at 11:52 AM Mike Beckerle <[email protected]> wrote: > > -1 binding. > > I can't get this to work at all. This is probably environmental, but still > has to get resolved so that this IDE works more reliably. > > I'm just trying to debug pcap, which is a public schema on the github DFDL > schemas web site. > > launch.json attached. > > > > On Thu, Apr 27, 2023 at 8:36 AM Steve Lawrence <[email protected]> > wrote: > >> I plan to take a look at this tomorrow, but can you created a release >> notes page with "released: false" for this release? I like to verify >> that at the same time everything else. >> >> On 2023-04-25 02:00 PM, Shane Dell wrote: >> > Hello all,I'd like to call a vote to release Apache Daffodil VS Code >> 1.3.0-rc1. >> > >> > All distribution packages, including signatures, digests, etc. can be >> > found at: >> > >> https://dist.apache.org/repos/dist/dev/daffodil/daffodil-vscode/1.2.0-rc3/ >> > >> > This release has been signed with PGP key >> > 86DDE7B41291E380237934F007570D3ADC76D51B, corresponding >> > to [email protected], which is included in the KEYS file here: >> > https://downloads.apache.org/daffodil/KEYS >> > >> > The release candidate has been tagged in git with 1.3.0-rc1. >> > >> > For reference, here is a list of all closed GitHub issues tagged with >> 1.3.0: >> > https://github.com/apache/daffodil-vscode/milestone/4?closed=1 >> > >> > Please review and vote. The vote will be open for at least 72 hours >> > (Friday, 28 April 2023, 2:00pm EST). >> > >> > [ ] +1 approve >> > [ ] +0 no opinion >> > [ ] -1 disapprove (and reason why) >> > Please note one of the large features that was focused on in 1.3.0 was >> > improving the data editor. To open the data editor you will need to >> open the >> > command palette using: >> > >> > - Ctrl + Shift + P (windows/linux) >> > - Command + Shift + P (mac) >> > >> > Then typing "data.edit", make sure "Daffodil Debug: Data Editor" is >> selected >> > and then hitting enter. By default the data editor will run on port >> 9000 of >> > your machine. However, if you want to use a different port you can add >> > "dataEditor.omegaEditPort": 9001 to your vscode/launch.json >> configuration. >> > Then once you run the command again the data editor should now use port >> 9001. >> > >> > Thank you, >> > >> > - Shane Dell >> > >> >>
