You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
➤ YN0085: │ + @types/glob@npm:8.1.0, @types/mocha@npm:10.0.6, @types/node@npm:20.11.30, @types/vscode@npm:1.95.0, @viperproject/locate-java-home@npm:1.1.15, @vscode/debugadapter-testsupport@npm:1.65.0, @vscode/debugadapter@npm:1.67.0, @vscode/test-electron@npm:2.3.8, @vscode/vsce@npm:2.22.0, @vscode/webview-ui-toolkit@npm:1.4.0, await-notify@npm:1.0.1, chai@npm:4.4.1, and more.
493
492
➤ YN0000: └ Completed in 9s 958ms
494
493
➤ YN0000: ┌ Post-resolution validation
495
494
➤ YN0002: │ apache-daffodil-vscode@workspace:. doesn't provide react (pa7c88), requested by @vscode/webview-ui-toolkit.
@@ -500,8 +499,6 @@ As of typing this document (Feb 2025), the latest version of yarn is 4.6.0. If y
500
499
➤ YN0000: └ Completed in 4m 47s
501
500
➤ YN0000: ┌ Link step
502
501
➤ YN0007: │ esbuild@npm:0.19.9 must be built because it never has been before or the last one failed
503
-
➤ YN0007: │ svelte-preprocess@npm:5.1.1 [5fe27] must be built because it never has been before or the last one failed
504
-
➤ YN0007: │ svelte-preprocess@npm:5.1.1 [ab741] must be built because it never has been before or the last one failed
505
502
➤ YN0007: │ keytar@npm:7.9.0 must be built because it never has been before or the last one failed
506
503
➤ YN0007: │ protobufjs@npm:7.4.0 must be built because it never has been before or the last one failed
507
504
➤ YN0000: └ Completed in 2m 40s
@@ -514,10 +511,6 @@ To remedy this, you need to change versions of Yarn. Use `yarn set version 1.22.
514
511
515
512
#### Yarn Test Issues
516
513
517
-
##### Data Editor Opens Test Case Failing
518
-
519
-
This means port 9000 is Occupied. See the current workarounds section in ["data editor opens" test fails if Port 9000 is Occupied · Issue #1175 · apache/daffodil-vscode](https://github.com/apache/daffodil-vscode/issues/1175).
520
-
521
514
##### TLS Certificate Issues
522
515
523
516
HTTPS TLS certificates are verified by default. When running the test suite in certain environments (e.g., company VPN that uses endpoint protection), TLS certificate verifications may fail with a self-signed certificate error. If this is the case, either have node trust the endpoint protection certificate, or use one of these workarounds to disable the certificate verification:
@@ -600,8 +593,6 @@ If issues persist, you may want to uninstall Node and reinstall it. If that does
600
593
601
594
For issues not mentioned in this section, the log files for the debugger are located in your OS temp directory (e.g. `/tmp` for Ubuntu 24.04.2). The log file for the debugger should be named `daffodil-debugger-<port>.log` when debugging the extension or `yarn-test-daffodil-debugger-<port>.log` when running yarn test.
602
595
603
-
The log files for the data editor are located in your OS app data path (e.g. `/home/<user>/.local/share/omega_edit`). The log files for the data editor should be named `serv-<port>.log` for the server logs and `dataEditor-<port>.log` for the data editor logs when using the data editor or `test-serv-<port>.log` and `test-dataEditor-<port>.log` when running yarn test.
Copy file name to clipboardExpand all lines: README.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -48,12 +48,12 @@ The Apache Daffodil™ Extension for Visual Studio provides a Daffodil parse deb
48
48
49
49

50
50
51
-
The Apache Daffodil™ Extension for Visual Studio Code provides an integrated data editor tuned specifically for challenging Daffodil use cases. It is designed to support large files, of any type, that are well beyond the limits of the standard text editor in VS Code. The Data Editor enables the editing of single or multiple bytes in various encodings. The Data Editor can seek to file offsets, search and replace byte sequences, profile data, and determine a file's content type. Features of the Data Editor will evolve to address the specific needs of the Daffodil community.
51
+
The Apache Daffodil™ Extension for Visual Studio Code integrates with the Ωedit™ Data Editor extension for challenging Daffodil use cases. The data editor is declared as a VS Code extension dependency and is designed to support large files, of any type, that are well beyond the limits of the standard text editor in VS Code. It enables editing single or multiple bytes in various encodings, seeking to file offsets, searching and replacing byte sequences, profiling data, and determining a file's content type.
The Data Editor component can be configured to run alongside and open the designated file specified by the data debugger. During this operation, whenever the debug session steps to a new byte position or stops at a breakpoint, the data content within the Data Editor will illustrate the byte location.
56
+
The Data Editor can be configured to open the designated data file when a Daffodil debug session starts. As the debug session steps to new byte positions, Daffodil sends byte-location highlights to the Ωedit™ Data Editor so the parse location is visible in the data content.
0 commit comments