[DISCUSS] Apache Daffodil™ Extension for Visual Studio Code Launch Wizard Enhancement

additional ideas to add? Note: This would most likely be targeted to be a part of 1.4.1 or 1.5.0 and not the 1.4.0 milestone. Thank you, Shane Dell

[CLOSED][VOTE] Apache Daffodil™ Extension for Visual Studio Code 1.4.0-rc1

The VOTE to release Apache Daffodil™ Extension for Visual Studio Code 1.4.0-rc1 is now closed. The vote fails with: 1 binding -1 The VOTE thread: https://lists.apache.org/thread/3s1jo2dogym1sg3vstky7p97z3sb9r9z The vote breakdown is: -1 Mike Beckerle (binding) Alongside the issues Mike menti

[VOTE] Apache Daffodil™ Extension for Visual Studio Code 1.4.0-rc1

https://github.com/apache/daffodil-vscode/wiki/Apache-Daffodil%E2%84%A2-Extension-for-Visual-Studio-Code:-v1.4.0. Thank you, - Shane Dell

[DISCUSS] Apache Daffodil VS Code Extension 1.4.0 Release

for 1.4.0 can be found at https://github.com/apache/daffodil-vscode/milestone/5?closed=1. Are there any problems, complaints or concerns? This discussion thread will be opened for at least 72 hours before moving forward. This will be Friday June 7th at 10:30 AM. Thank you, Shane Dell

Re: Apache Daffodil VSCode Extension Issue Input

: > Please see PR: https://github.com/DFDLSchemas/envelope-payload/pull/1 > > > On Tue, Jan 2, 2024 at 12:32 PM Mike Beckerle wrote: > > > I'm creating an envelope-payload example schema under DFDLSchemas on > > github. > > > > > > On Wed, Dec 27,

Apache Daffodil VSCode Extension Issue Input

some help/input on a schema we can use to test what Mike is describing so that we are able to update the extensions debugger in the appropriate way. Any information would be greatly appreciated either through this email thread or by posting a comment to the linked GitHub Issue. Thank you, Shane

[ANNOUNCE] Apache Daffodil VS Code Extension 1.3.1 Released

The Apache Daffodil community is pleased to announce the release of version 1.3.1 of the Apache Daffodil VS Code Extension. Notable changes in this release include improved Debugging, Data Editor, Bug Fixes, Package Update and other enhancements. Detailed release notes and downloads are available

[RESULT][VOTE] Apache Daffodil VS Code Extension 1.3.1-rc2

The VOTE to release Apache Daffodil VS Code Extension 1.3.1-rc2 is now closed. The vote passes with: 3 binding +1 The VOTE thread: https://lists.apache.org/thread/wst7zo1x74sqhcng154nqyyxk3h2tdcj The vote breakdown is: +1 Steve Lawrence (binding) +1 Davin Shearer (binding) +1 Robert Stricklan

[VOTE] Apache Daffodil VS Code Extension 1.3.1-rc2

pache/daffodil-vscode/wiki/Apache-Daffodil%E2%84%A2-Extension-for-Visual-Studio-Code:-v1.3.1. Thank you, - Shane Dell

[RESULT][VOTE] Apache Daffodil VS Code Extension 1.3.1-rc1

thoughts? - Shane Dell

Re: [VOTE] Apache Daffodil VS Code Extension 1.3.1-rc1

/xsd/ethernetIP.dfdl.xsd > >>> at > >>> org.apache.daffodil.debugger.dap.Compiler$$anon$1.$anonfun$compile$2(Compiler.scala:38) > >>> at cats.MonadError.$anonfun$ensureOr$1(MonadError.scala:41) > >>> at println @ > >>> c

Re: [VOTE] Apache Daffodil VS Code Extension 1.3.1-rc1

Parse$.apply(Parse.scala:81) > at println @ > com.monovore.decline.effect.CommandIOApp$.addVersionFlag(CommandIOApp.scala:67) > at map @ > org.apache.daffodil.debugger.dap.Parse$Debugee$LaunchArgs$Manual.data(Parse.scala:213) > at flatMap @ > org.apache.daffodil.debu

[VOTE] Apache Daffodil VS Code Extension 1.3.1-rc1

pache/daffodil-vscode/wiki/Apache-Daffodil%E2%84%A2-Extension-for-Visual-Studio-Code:-v1.3.1. Thank you, - Shane Dell

[DISCUSS] Apache Daffodil VS Code Extension 1.3.1 Release

for 1.3.1 can be found at https://github.com/apache/daffodil-vscode/milestone/10?closed=1. Are there any problems, complaints or concerns? This discussion thread will be opened for at least 72 hours before moving forward. This will be Friday August 18th at 10:30 AM. Thank you, Shane Dell

[ANNOUNCE] Apache Daffodil VS Code Extension 1.3.0 Released

I apologize for the second email but I messed up a link in the first one. The Apache Daffodil community is pleased to announce the release of version 1.3.0 of the Apache Daffodil VS Code Extension. Notable changes in this release include improved Data Editor, Bug Fixes, Package Update and enhance

Fwd: [ANNOUNCE] Apache Daffodil VS Code Extension 1.3.0 Released

I apologize for the second email but I messed up a link in the first one. The Apache Daffodil community is pleased to announce the release of version 1.3.0 of the Apache Daffodil VS Code Extension. Notable changes in this release include improved Data Editor, Bug Fixes, Package Update and enhance

[ANNOUNCE] Apache Daffodil VS Code Extension 1.3.0 Released

The Apache Daffodil community is pleased to announce the release of version 1.3.0 of the Apache Daffodil VS Code Extension. Notable changes in this release include improved Data Editor, Bug Fixes, Package Update and enhancements. Detailed release notes and downloads are available at: https://daf

[RESULT][VOTE] Apache Daffodil VS Code Extension 1.3.0-rc4

The VOTE to release Apache Daffodil VS Code Extension 1.3.0-rc4 is now closed. The vote passes with: 4 binding +1 The VOTE thread: https://lists.apache.org/thread/5rcpms2lk19mpbbhhpplgnpltzhd6cyp The vote breakdown is: +1 Mike Beckerle (binding) +1 Shane Dell (binding) +1 Davin Shearer

Re: [VOTE] Apache Daffodil VS Code Extension 1.3.0-rc4

eing: - @omega-edit/client - quick-format-unescaped However, this also shouldn't stop the vote from passing and these can added in 1.3.1. All scala dependencies were listed, these were the only one's missing between both node and scala. On 2023/06/27 19:26:48 Shane Dell wrote: >

Re: [VOTE] Apache Daffodil VS Code Extension 1.3.0-rc4

ebugger to extract. This would probably be mostly always extracting the debugger bundled with the extension instead of only do it when the folder doesn't exist like it does currently. I believe that is planned for 1.4.0 but could possibly be done in 1.3.1. Thank you, Shane Dell On 2023/06/2

[VOTE] Apache Daffodil VS Code Extension 1.3.0-rc4

if you want to use a different port follow steps here Data Editor Launch Settings <https://github.com/apache/daffodil-vscode/wiki/Apache-Daffodil%E2%84%A2-Extension-for-Visual-Studio-Code:-v1.3.0#data-editor-launch-settings> Thank you, - Shane Dell

[CLOSED][VOTE] Apache Daffodil VS Code Extension 1.3.0-rc3

The VOTE to release Apache Daffodil 1.3.0-rc2 is now closed. The vote fails with: 1 binding -1 The VOTE thread: https://lists.apache.org/thread/x1jljr4l6h5stwox8zxszn8sf0tn9pnh The vote breakdown is: -1 Mike Beckerle (binding) Multiple GitHub issues were made to look at the issues found by M

Re: [VOTE] Apache Daffodil VS Code Extension 1.3.0-rc3

extraction of the debugger's zip package so that if this is your issue it will no longer happen. Thank you, Shane Dell On 2023/06/21 22:23:06 Mike Beckerle wrote: > My vote -1 > > See https://github.com/apache/daffodil-vscode/issues/648. I'm still not > getting any output from

[VOTE] Apache Daffodil VS Code Extension 1.3.0-rc3

if you want to use a different port follow steps here Data Editor Launch Settings <https://github.com/apache/daffodil-vscode/wiki/Apache-Daffodil%E2%84%A2-Extension-for-Visual-Studio-Code:-v1.3.0#data-editor-launch-settings> Thank you, - Shane Dell

Re: Daffodil-vscode Issues

; in the CLI debugger to cause it to pause > whenever a parser error occurs. > > > On 2023-06-14 01:31 PM, Shane Dell wrote: > > Hey Mike, > > > > Does the CLI version of the debugger handle asserts failing? If so could > > you point in the > > d

Re: Daffodil-vscode Issues

d and the vscode debugger seems to end debugging as if everything was fine even though it fails that assert. Thank you, Shane Dell On 2023/06/13 15:54:07 Mike Beckerle wrote: > Shane, > > 648 I added info to the ticket. Basically make icmp1.bad.cmp where byte 1 > is clobbered to

Re: Daffodil-vscode Issues

ger thing. I also believe issue > > https://github.com/apache/daffodil-vscode/issues/651 should be closed as > > we already have a similar issue ( > > https://github.com/apache/daffodil-vscode/issues/76) to support adding > > breakpoints to schemas in JARs that is planned fo

[CLOSED][VOTE] Apache Daffodil VS Code Extension 1.3.0-rc2

The VOTE to release Apache Daffodil 1.3.0-rc2 is now closed. The vote fails with: 1 binding -1 The VOTE thread: https://lists.apache.org/thread/nh8t4c32ov0c0hrvrp2qo3q84179ngvv The vote breakdown is: -1 Mike Beckerle (binding) Multiple GitHub issues were made to look at the issues found by M

Re: [VOTE] Apache Daffodil VS Code Extension 1.3.0-rc2

gt; with Java 17. It may be that the java version thing was a non-issue that > > other things were interacting with it. > > > > > > On Mon, Jun 5, 2023 at 4:45 PM Shane Dell wrote: > > > >> The extension does not depend on Java 11 it should work fine with Ja

Re: [VOTE] Apache Daffodil VS Code Extension 1.3.0-rc2

1-openjdk-amd64/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin > ORIGINAL_XDG_CURRENT_DESKTOP=undefined > DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus > TERM_PROGRAM=vscode > _=/usr/bin/env > > If I run daffodil, then c-C in the terminal it creates,

Re: [VOTE] Apache Daffodil VS Code Extension 1.3.0-rc2

". If you close that terminal, the next you time you run it should create a new terminal with the env set properly. If you could try this and see if it works how you expect, that would help us single out this issue out to an already active terminal. Thank you, Shane Dell On 2023/05/2

Re: [VOTE] Apache Daffodil VS Code Extension 1.3.0-rc2

debugger that may not be present on rc2. But if the folder daffodil-dap/daffodil-debugger-3.4.0-1.3.0/ already exists from rc1 then rc2 will not remake it. So in order to remake it you have to manually remove this folder. Let me know if this helps. Thank you, Shane Dell On 2023/05/24 15:15:33

[VOTE] Apache Daffodil VS Code Extension 1.3.0-rc2

if you want to use a different port follow steps here Data Editor Launch Settings <https://github.com/apache/daffodil-vscode/wiki/Apache-Daffodil%E2%84%A2-Extension-for-Visual-Studio-Code:-v1.3.0#data-editor-launch-settings> Thank you, - Shane Dell

[CLOSED][VOTE] Apache Daffodil VS Code Extension 1.3.0-rc1

Sorry for being late to release this email. The vote to release Apache Daffodil VS Code Extension 1.3.0-rc1 fails. The votes were as follows: +1 Davin Shearer (binding) -1 Mike Beckerle (binding) -1 Steve Lawrence (binding) Thank you, Shane Dell

[RESULT][VOTE] Apache Daffodil VS Code Extension 1.3.0-rc1

The VOTE to release Apache Daffodil 1.3.0-rc1 is now closed. The vote fails with: 1 binding +1 2 binding -1 The VOTE thread: https://lists.apache.org/thread/r2grf2lm3ox6m33g8n6s2gf65wn2lcrq The vote breakdown is: +1 Davin Shearer (binding) -1 Mike Beckerle (binding) -1 Steve Lawrence (binding

Re: Having trouble with Apache Daffodil VS Code Extension 1.3.0-rc1

port 9001. FYI, You don't have to make it 9001 it can be whatever open port you would like. Thank you, Shane Dell On 2023/04/25 21:11:44 "Shearer, Davin" wrote: > Hi Mike, > > Are you running something already that binding to port 9000, like Portainer? > > -Davin &

Re: [VOTE] Apache Daffodil VS Code Extension 1.3.0-rc1

My apologies I linked to the wrong packages, below is the correct link: https://dist.apache.org/repos/dist/dev/daffodil/daffodil-vscode/1.3.0-rc1/ On 2023/04/25 18:00:15 Shane Dell wrote: > Hello all,I'd like to call a vote to release Apache Daffodil VS Code > 1.3.0-rc1. > >

[VOTE] Apache Daffodil VS Code Extension 1.3.0-rc1

e 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

[DISCUSS] Apache Daffodil VS Code Extension 1.3.0 Release

This will be Friday April 21st at 12:00 PM. Thank you, Shane Dell

[ANNOUNCE] Apache Daffodil VS Code 1.2.0 Released

The Apache Daffodil community is pleased to announce the release of version 1.2.0 of the Daffodil VS Code Extension. This is the third official release of the Apache Daffodil VS Code Extension. Detailed release notes and downloads are available at: https://daffodil.apache.org/vscode/1.2.0/ The

[RESULT][VOTE] Release Apache Daffodil VS Code 1.2.0-rc3

The VOTE to release Apache Daffodil VS Code 1.2.0-rc3 is now closed. The vote passes with: 3 binding +1 The VOTE thread: https://lists.apache.org/thread/swwf3v0xwn8g559qqf1krczvr94z31bb The vote breakdown is: +1 Mike Beckerle (binding) +1 Shane Dell (binding) +1 Steve Lawrence (binding

Re: [VOTE] Apache Daffodil VS Code Extension 1.2.0-rc3

make sure they are marked for the 1.3.0 milestone, does this work for you? Thank you, Shane Dell On 2022/12/06 19:03:00 Steve Lawrence wrote: > +1 (binding) > > Four checks I marked as MINOR and I'm fine with them being fixed prior > to the release (website link update & iss

Re: Experience with Apache Daffodil VSCode Ext 1.2.0-RC3

that these are good items for us to fixed for the next release of the extension! - Shane Dell On 2022/12/02 18:18:08 Mike Beckerle wrote: > These items below do not block the release, but were things I observed: > > SITE: > - I did notice a bug on the VSCode Extension 1.2.0 release p

Re: [VOTE] Apache Daffodil VS Code Extension 1.2.0-rc3

also able to use the omega-edit commands and saw no issues with the different editing items. On 2022/12/01 13:40:33 Shane Dell wrote: > Hello all,I'd like to call a vote to release Apache Daffodil VS Code > 1.2.0-rc3. > > All distribution packages, including signatures, dig

[VOTE] Apache Daffodil VS Code Extension 1.2.0-rc3

https://github.com/apache/daffodil-vscode/milestone/3?closed=1 Please review and vote. The vote will be open for at least 72 hours (Tuesday, 6 December 2022, 9:00am EST). [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Thank you, - Shane Dell

[CANCELED][VOTE] Release Apache Daffodil VS Code Extension 1.2.0-rc2

hread/mnovtl32vvwchv7hrw6m3zhbns29glpy Thanks, - Shane Dell

Re: [VOTE] Apache Daffodil VS Code Extension 1.2.0-rc2

tests. > > Now, open VSCode and nstall the 1.2.0 vsix. > > Now open the PCAP folder in vscode. > > Use the attached launch.json. > > Either of the two launch configs should work. Both give the same problem: > > [image: image.png] > > > > >

Re: [VOTE] Apache Daffodil VS Code Extension 1.2.0-rc2

sts. > > Now, open VSCode and nstall the 1.2.0 vsix. > > Now open the PCAP folder in vscode. > > Use the attached launch.json. > > Either of the two launch configs should work. Both give the same problem: > > [image: image.png] > > > > >

[VOTE] Apache Daffodil VS Code Extension 1.2.0-rc2

https://github.com/apache/daffodil-vscode/milestone/3?closed=1 Please review and vote. The vote will be open for at least 72 hours (Thursday, 1 December 2022, 3:00pm EST). [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Thank you, - Shane Dell

[RESULT][VOTE] Release Apache Daffodil VS Code 1.2.0-rc1

the thread: - Intellisense < Issue <https://github.com/apache/daffodil-vscode/issues/350> - Note: This is already fixed and a new VOTE will be sent out soon. Thanks to everyone who voted! - Shane Dell

Re: [VOTE] Apache Daffodil VS Code Extension 1.2.0-rc1

Mike Beckerle wrote: > Apologies. i won't be able to evaluate this until next week. > > On Mon, Nov 14, 2022 at 4:23 PM Shane Dell wrote: > > > > Hello all,I'd like to call a vote to release Apache Daffodil VS Code > > 1.2.0-rc1. > > > > All dis

[VOTE] Apache Daffodil VS Code Extension 1.2.0-rc1

https://github.com/apache/daffodil-vscode/milestone/3?closed=1 Please review and vote. The vote will be open for at least 72 hours (Thursday, 17 November 2022, 4:30pm EST). [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Thank you, - Shane Dell

Re: [DISCUSS] Release Apache Daffodil VS Code 1.2.0

4.0 once it's released: > >#336 Update the extension to use Apache Daffodil 3.4.0 > > On 11/7/22 2:19 PM, Shane Dell wrote: > > It has been over 3 months since the last Daffodil VS Code release. We've > > had a > > number of bug fixes and features added

Re: [VOTE] Release Apache Daffodil 3.4.0-rc2

+1 (binding) [OK] Able to build and publish locally. [OK] Unit and Integration tests passed. [OK] I was able to successfully build the daffodil-vscode Scala debugger using a locally published version of daffodil (3.4.0). [OK] I was also able to take said debugger to debug and run schemas in vscod

[DISCUSS] Release Apache Daffodil VS Code 1.2.0

propose that we start the 1.2.0 release process. - Shane Dell

[ANNOUNCE] Apache Daffodil VS Code 1.1.0 Released

The Apache Daffodil community is pleased to announce the release of version 1.1.0 of the Daffodil VS Code Extension. This is the second official release of the Apache Daffodil VS Code Extension. Detailed release notes and downloads are available at: https://daffodil.apache.org/vscode/1.1.0/ The

Re: [RESULT][VOTE] Release Apache Daffodil VS Code 1.1.0-rc2

Okay that was added would there be anything else you would suggest doing? I assume I can't update my initial message other than adding here: "Another +1 was added to the vote: +1 Shane Dell (binding)" On 2022/08/23 17:14:26 Steve Lawrence wrote: > Yeah, I'd suggest just

Re: [VOTE] Release Apache Daffodil VS Code 1.1.0-rc2

hout a milestone > - There's a handful of issues that have been closed but have not been >assigned a milestone. Were they all closed as part of 1.1.0? Can >they be added to this milestone? > > > https://github.com/apache/daffodil-vscode/issues?q=is%3Aissue+is

RE: Re: [RESULT][VOTE] Release Apache Daffodil VS Code 1.1.0-rc2

ne is a PMC, so he can vote and count as the third. Should have > added an explicit +1 and added his name to the pass vote though. > > - Steve > > > On 8/22/22 11:22 AM, Mike Beckerle wrote: > > I think you need a third PMC member vote. Releases should have 3 votes. >

[RESULT][VOTE] Release Apache Daffodil VS Code 1.1.0-rc2

The VOTE to release Apache Daffodil VS Code 1.1.0-rc2 is now closed. The vote passes with: 2 binding +1 The VOTE thread: https://lists.apache.org/thread/m4tc565t84fo2mwpxvgyr4qqmg9tgv37 The vote breakdown is: +1 Mike Beckerle (binding) +1 Steve Lawrence (binding) Thanks to everyone who voted

[VOTE] Release Apache Daffodil VS Code 1.1.0-rc2

https://github.com/apache/daffodil-vscode/milestone/2?closed=1 Please review and vote. The vote will be open for at least 72 hours (Thursday, 18 August 2022, 5:30pm EST). [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Thank you, - Shane Dell

[RESULT][VOTE] Release Apache Daffodil VS Code 1.1.0-rc1

The VOTE to release Apache Daffodil VS Code 1.1.0-rc1 is now closed. The vote fails with: 2 binding -1 The VOTE thread: https://lists.apache.org/thread/4bmxpmb0bj9j3pl7v9qq02b1rnxo635m The vote brea

Re: [VOTE] Release Apache Daffodil VS Code 1.1.0-rc1

ies, so I'm not sure if those are > transitive dependencies, build dependencies, or something else and maybe > they're aren't actually included in the .vsix file where this matters. > I'm not sure how we originally generated the list of things that need to > go in

Re: [VOTE] Release Apache Daffodil VS Code 1.1.0-rc1

t; If I choose Daffodil Debug File from the command palette, I'm immediately > > getting "ENOENT: no such file or directory, lstat". > > > > I tried also to select Daffodil Debugger, configure launch.json but I get: > > > > image.png > > (btw: w

[VOTE] Release Apache Daffodil VS Code 1.1.0-rc1

https://github.com/apache/daffodil-vscode/milestone/2?closed=1 Please review and vote. The vote will be open for at least 72 hours (Saturday, 30 July 2022, 3 Noon EST). [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Thank you, - Shane Dell

[DISCUSS] Apache Daffodil VS Code Extension 1.1.0 Release

All, This thread will be to discuss the topic of creating a 1.1.0 release of the Apache Daffodil VS Code Extension. This release would include all issues listed here 1.1.0 Milestone Close Items . In summary the main changes in this re

Daffodil Debugger Scala Source Code

the extension. My personal vote is for creating a new repo called something like either apache/daffodil-debugger or apache/daffodil-debugger-scala. Sincerely, Shane Dell

Re: DISCUSS - test automation for vscode - to what extent possible?

>From what I am seeing it is common to use mock data to test out extensions. I >can create an issue in apache/daffodil-vscode to start work on a new test >suite for better testing UI aspects and other things that rely on the VS Code >API. On 2022/05/24 13:48:46 Shane Dell wrote: &g

Re: DISCUSS - test automation for vscode - to what extent possible?

I think to a certain extent we can create more unit tests that test out UI components. I have not done much of this but I believe that it is relatively common to do so for frontend heavy projects. However, in some cases in may be more involved some cases I have seen they write python selenium co

Apache Daffodil VS Code Extension

All, I am excited to announce that the Apache Daffodil VS Code Extension is now available via the VS Code Extension Marketplace. The quickest way to search for it is to go to the marketplace and search for "asf" or "daffodil". Thank you, Shane Dell

[ANNOUNCE] Apache Daffodil VS Code 1.0.0 Released

The Apache Daffodil community is pleased to announce the release of version 1.0.0 of the Daffodil VS Code Extension. This is the first official release of the Apache Daffodil VS Code Extension. Detailed release notes and downloads are available at: https://daffodil.apache.org/vscode/1.0.0/ The

[RESULT][VOTE] Release Apache Daffodil VS Code 1.0.0-rc3

The VOTE to release Apache Daffodil VS Code 1.0.0-rc3 is now closed. The vote passes with: 4 binding +1 The VOTE thread: https://lists.apache.org/thread/9csq1t0f3dcnpgh9cx8km2r51dkmofs8 The vote breakdown is: +1 Mike Beckerle (binding) +1 John Interrante (binding) +1 Shane Dell (binding) +1

Re: [VOTE] Release Apache Daffodil VS Code 1.0.0-rc3

ror > [OK] No open CVE's found using sbt-dependency-check plugin > > > On 3/31/22 12:41 PM, Shane Dell wrote: > > Hello all, > > I'd like to call a vote to release Apache Daffodil VS Code 1.0.0-rc3. > > > > All distribution packages, including sign

Re: [VOTE] Release Apache Daffodil VS Code 1.0.0-rc3

+1 I was able to successfully download the extension and install it into VS Code. Once done I was able to debug the EDIFACT schema and put breakpoints into the different files without issue. On 2022/03/31 16:41:04 Shane Dell wrote: > Hello all, > I'd like to call a vote to rel

[VOTE] Release Apache Daffodil VS Code 1.0.0-rc3

hours (Sunday, 3 April 2022, 12 Noon EST). [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Thank you, - Shane Dell

[CANCELED][VOTE] Release Apache Daffodil VS Code 1.0.0-rc2

Hello all, I am cancelling the rc2 vote as there were some needed changes for the release candidate. Keep an eye out for rc3 release. Thank you, Shane Dell

Re: [VOTE] Release Apache Daffodil VS Code 1.0.0-rc2

k the log4cats findings can be ignored, and should be > considered a bug in the CVE checker. > > > On 3/24/22 9:27 PM, Shane Dell wrote: > > Ah okay that makes we will still want dependabot for the node/typescript > > extension side. But > > what do you think is be

Re: [VOTE] Release Apache Daffodil VS Code 1.0.0-rc2

ncy > PRs to approve. > > Also, now that I think about it, dependabot doesn't do sbt dependencies. > We need scala-steward for that. Daffodil uses enables dependabot for > github-actions and container updates, and scala steward for sbt updated. > > On 3/24/22 9:18 PM,

Re: [VOTE] Release Apache Daffodil VS Code 1.0.0-rc2

e latest. Eventually we'll want dependabot to help us > with that and automate it, but the sbt-updates plugin can be used to > manually check for updates: > > https://github.com/rtimush/sbt-updates > > On 3/24/22 9:02 PM, Shane Dell wrote: > > So its an issue com.microsoft

Re: [VOTE] Release Apache Daffodil VS Code 1.0.0-rc2

2022/03/25 00:37:40 Steve Lawrence wrote: > The sbt dependency graph plugin might help to show where transitive > dependencies are coming from: > > https://github.com/sbt/sbt-dependency-graph > > > On 3/24/22 8:34 PM, Shane Dell wrote: > > I would say it is correct

Re: [VOTE] Release Apache Daffodil VS Code 1.0.0-rc2

in log4j-core, which vscode does not > include? > > So maybe this 4.0.0 list is correct, assuming log4j-api doesn't have the > vulnerability? > > On 3/24/22 11:11 AM, Shane Dell wrote: > > I get the vulnerabilities for: > > > > - commons-lang3-3.6.jar &

Re: [VOTE] Release Apache Daffodil VS Code 1.0.0-rc2

yours picking up cached dependencies or ones from other projects not just the vscode repo? On 2022/03/24 15:05:27 Shane Dell wrote: > So I think the log4j errors you are seeing are coming from a library > dependency the Scala debugger user, this being `log4cats-slf4j` which only > goe

Re: [VOTE] Release Apache Daffodil VS Code 1.0.0-rc2

would recommend adding CVE checking to CI because > downloading the CVE database takes a long time, especially the first > time. I might recommend instead just enabling dependabot, that's been > good about keeping Daffodil dependencies up to date. > > > On 3/24/22 9:45 AM,

Re: [VOTE] Release Apache Daffodil VS Code 1.0.0-rc2

gt; > >but this should be fixed for the next release. > > > [MINOR] The README shows up in VS Code, but is focused on how to build > > >the extension. This makes sense for the main github README, but I > > >wonder if the README displayed in VS Code want

Re: [VOTE] Release Apache Daffodil VS Code 1.0.0-rc2

n in it again. > > > > So I am definitely installing and running the vsix from the > > dist.apache.org site for rc2. Something must be wrong with it. > > > > My next step would be to build my own vsix from source, but I don't have > > time before the Sunda

Re: [VOTE] Release Apache Daffodil VS Code 1.0.0-rc2

"type": "console", > >>>>> "path": "${workspaceFolder}/infoset.xml" > >>>>> }, > >>>>> "trace": true, > >>>>>

Re: [VOTE] Release Apache Daffodil VS Code 1.0.0-rc2

I believe a lot of the issue that Mike has been having is because of the artifacts both using 1.0.0 without the rc. Since Mike installed the rc1 extension which created a folder called something like "daffodil-dap/daffodil-debugger-${DAFFODIL_VERSION}-${DAFFODIL_VSCODE_VERSION" in this instance

Re: [VOTE] Release Apache Daffodil VS Code 1.0.0-rc2

way we do Daffodil releases pages, but > that's mostly just a template with a .md page for each release so > copying that and making adjustments shouldn't be too bad. > > On 3/17/22 3:06 PM, Shane Dell wrote: > > Hello all, > > Ignore the last vote as I did not change

[VOTE] Release Apache Daffodil VS Code 1.0.0-rc2

+0 no opinion [ ] -1 disapprove (and reason why) Thank you, - Shane Dell

[VOTE] Release Apache Daffodil VS Code 1.0.0-rc2

https://github.com/apache/daffodil-vscode/issues?q=is%3Aissue+is%3Aclosed+is%3A1.0.0 Please review and vote. The vote will be open for at least 72 hours (Sunday, 17 March 2022, 12 Noon EST). [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Thank you, - Shane Dell

[CANCELED][VOTE] Release Apache Daffodil VS Code 1.0.0-rc1

Officially cancelling the VOTE for 1.0.0-rc1. I'll create a 1.0.0-rc2 and start a new VOTE once the issue is resolved. VOTE thread: https://lists.apache.org/thread/f5qopxc7opv4z1jql8f1rq4qj5gjys32 Thank you, Shane Dell

Re: [VOTE] Release Apache Daffodil VS Code 1.0.0-rc1

you made yourself or just debugging it via vscode. On 2022/03/03 19:41:25 Shane Dell wrote: > Mike, > > That folder path only gets created from debugging/running the extension > locally. When installed onto a machine it will be in a different location. > With this release VSI

Re: [VOTE] Release Apache Daffodil VS Code 1.0.0-rc1

local/share/daffodil-dap/daffodil-debugger-3.1.0-1.0.0-SNAPSHOT > Should be daffodil 3.2.1 version and "SNAPSHOT" shouldn't be in the name. > > > > > On Wed, Mar 2, 2022 at 7:26 PM Shane Dell wrote: > > > Hello all, > > > > I'd like to

[VOTE] Release Apache Daffodil VS Code 1.0.0-rc1

https://github.com/apache/daffodil-vscode/issues?q=is%3Aissue+is%3Aclosed+is%3A1.0.0 Please review and vote. The vote will be open for at least 72 hours (Sunday, 6 March 2022, 12 Noon EST). [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Thank you, - Shane Dell