with
unexpected consequences.
>
> On 2023-09-25 12:13 PM, Mike Beckerle wrote:
> > As of Java 20, the constructors for Java.net.URL have all been
> deprecated.
> >
> > This has some implications for us. The matter is rather subtle, so bear
> > with me.
> >
cise web search on, and
ChatGPT4 has been useless regarding this also (Java 20 is too new for it)
in terms of finding anything useful online that addresses this.
Mike Beckerle
Apache Daffodil PMC | daffodil.apache.org
OGF DFDL Workgroup Co-Chair | www.ogf.org/ogf/doku.php/standards/dfdl/dfdl
Owl Cyber Defense | www.owlcyberdefense.com
>
> > Although epsilon comparison is the right way to compare floats, my
> > concern is that we might add some bug in Daffodil where we do math
> > wrong and end up with a very very very slightly wrong answer and it
> > would be hidden. But if our epsilon is small enough,
19 and newer. Older versions would expect exact
> values and so would catch any off by very very small amount bugs. That
> might be adding unnecessary complication though.
>
>
> On 2023-09-24 12:09 PM, Mike Beckerle wrote:
> > So Java 21 produces different floating point v
ative I can think of is some sort of conditional infoset
construction, so that the expected values can vary for different JVMs.
On Sat, Sep 23, 2023 at 2:13 PM Mike Beckerle wrote:
>
> JVM 21 LTS is now out.
>
> So I decided to try to building Daffodil using it. My WIP PR is
> h
JVM 21 LTS is now out.
So I decided to try to building Daffodil using it. My WIP PR is
https://github.com/apache/daffodil/pull/1090
It looks pretty close.
The --release 8 option for javac is now deprecated. So I conditionalized
that.
Fixed some deprecated calls.
Remaining issues:
2 more deprec
ce--it's very easy to add new mutable state and forget to
> also add a corresponding change to a reset function. New instances avoid
> this issue.
>
> I would suggest avoid the reset() thing. One more thing to be buggy.
>
> On 2023-09-13 09:48 AM, Mike Beckerle wrote:
> > (
ey need
> to use ThreadLocals or some thread-safe data structure for that state.
>
> And actually this is what the Daffodil NiFi processor does. It has a
> mutable cache compiled parsers so it doesn't need to recompile them all
> the time, and this cache is stored in a thread-saf
Congrats to the VSCode Extension contributors!
This just made it "under the wire" into this month's Daffodil Quarterly
Board report !
On Tue, Sep 12, 2023 at 1:41 PM Shane Dell wrote:
> The Apache Daffodil community is pleased to announce the
> release of version 1.3.1 of the Apache Daffodil VS
I just got back from PTO and won't have time to evaluate rc2 today.
I vote 0, which means I'm fine if you go ahead if you have enough other
votes.
On Tue, Sep 12, 2023 at 9:02 AM Davin Shearer
wrote:
> +1 (binding)
>
> v1.3.1 is solid and is a big improvement over v1.3.0. Mike B. gave RC1
> a
My vote +1 (However, I see already there is a binding -1, so oh well)
I want to try some even harder schemas, but already this is more robust and
usable than 1.3.0 because it makes the error outputs more visible.
A few notes:
I like the Debug Console tab. The error messages that mention files, t
This is the issue. I have created PCAP and EthernetIP for Daffodil 3.5.0
and it is working now.
On Fri, Aug 25, 2023 at 2:17 PM Mike Beckerle wrote:
> Ah. 1.3.1 is Daffodil 3.5.0. That's quite possibly the explanation. I
> will report back.
>
> On Fri, Aug 25, 2023 at 11
e only thing I could think of that breaks
> the schemas. I cloned a
> fresh instance of the PCP schema and I am getting errors trying to run a
> `sbt clean install`,
> so I don't know if I am also doing something wrong there.
>
> On 2023/08/25 14:45:41 Mike Beckerle wrote:
>
Not voting yet, because I am perhaps doing something simple wrong.
I am getting nowhere fast:
I am debugging PCAP with the ethernetIP dependency. From a terminal,'sbt
clean test' works and all tests pass. This also populates lib_managed which
is where the ethernetIP jar is found for the debug cl
+1 also
On Thu, Aug 17, 2023 at 7:44 AM Steve Lawrence wrote:
> +1, these settings look like a big improvement. I suggest we don't do
> anything and use the defaults come October 1
>
> On 2023-08-17 04:27 AM, Christofer Dutz wrote:
> > TL;DR: We’re updating how auto-generated email from Github w
;
> That said, I'm curious what optimizations the CRC32 layer is trying to
> do with a constant layer length?
>
> On 2023-08-15 05:49 PM, Mike Beckerle wrote:
> > Lola Kilo and I were debugging a layer for CRC32 and found that the
> > LayerLengthEv is a NoC
Lola Kilo and I were debugging a layer for CRC32 and found that the
LayerLengthEv is a NoCacheEvaluatable, so even if the schema does
dfdlx:layerLength="1240" a constant, the the layerLengthEv.optConstant is
None, which is because it is a NoCacheEvaluatable, which insists
optConstant is false to pr
> · Refine snippet suggestions for specific element tags
>
> · Refine the handling of auto-complete closing tags for multi-line
> attributes (attribute split on multiple lines)
>
> · Add semantic highlighting for XPath expressions
>
> TDML
>
> · Resolved
+1 from me. I looked at the changes/fixes, and there is quite a lot in
1.3.1. Definitely worth a point release.
On Tue, Aug 15, 2023 at 10:27 AM Shane Dell wrote:
> Hello all,
>
> The Apache Daffodil VS Code Extension development team believes we are
> ready to create a release candidate for 1.3
Well that's unfortunate, but I still want to do the integration.
...mike beckerle
-- Forwarded message -
From:
Date: Thu, Aug 3, 2023 at 2:18 PM
Subject: Talk not accepted for Community over Code 2023
To:
Mike Beckerle
Unfortunately, your talk
Direct Query of Arbi
I have a few opinions to offer.
First, what is this data profile for? I know of only a few things one would
use that sort of profile for, and those could all be handled by looking at
the first Kbyte of the data.
(Guessing natural language, guessing charset, LF vs. CRLF, and guessing
text vs. binar
d
in the schema, and force load the jars directly rather than letting
ordinary class loader classpath stuff do it.
Taken together, these would let people add Daffodil to a product without
having to add features for tuning, for specifying plug-ins, etc. The schema
could specify all these things.
Thanks. I made it up myself. Didn't even use ChatGPT :-)
On Thu, Jul 6, 2023 at 12:46 PM Ted Dunning wrote:
> That's a cool abstract.
>
>
>
> On Thu, Jul 6, 2023 at 8:29 AM Mike Beckerle wrote:
>
> > I decided the only way to force getting this Drill + Da
This looks like a fairly long list for a 1.3.1
Getting rid of the excess debug/info output to the terminal, so that you
can find errors in it more easily is my priority 1 feature need, and feels
like a 1.3.1 kind of change.
Next would be avoiding the jumping back and forth between enclosing
eleme
I decided the only way to force getting this Drill + Daffodil integration
done, or at least started, is to have a deadline.
So I submitted this abstract below for the upcoming "Community over Code"
(formerly known as ApacheCon) conference this fall (Oct 7-10)
I'm hoping this forces some of the re
g a new visx shouldn't it?
Maybe this is fixed already? (I deleted it anyway, because I got tripped up
by this evaluating an earlier 1.3.0-RCx.)
-mike beckerle
On Tue, Jun 27, 2023 at 3:27 PM Shane Dell wrote:
> Hello all,I'd like to call a vote to release Apache Daffodil VS Code
gt;
> https://scalameta.org/scalafmt/docs/configuration.html#-format-off
>
> On Fri, Jun 23, 2023 at 9:20 AM Steve Lawrence
> wrote:
>
> > scalafmt as a lot of configurability. Maybe there are some options we
> > could tweak?
> >
> > On 2023-06-23 12:13 PM, Mi
We added scalafmt, and I have not done much coding since that time. Now
that I have, I hate it.
It turns this:
val optURI =
Misc.getResourceRelativeOption(sysId, baseURI) orElse
Misc.getResourceRelativeOption(removeInitialUpwardPathSteps(sysId), baseURI)
into:
val optURI =
Misc
.get
manager activities. That
> *should* be enough if we start a new vote, but it doesn't leave a lot of
> time, considering there's a 72 hour voting period followed by approx 24
> hours for release artifacts to reach mirrors.
>
> On 2023-06-22 01:43 PM, Mike Beckerle wrote:
>
h for Daffodil parse/unparse,
but also as XML schemas with a variety of separate validators including
those written in C/C++ so which cannot use Daffodil's schemaLocation
resolver.
On Wed, Jun 21, 2023 at 5:16 PM Mike Beckerle wrote:
> +1
>
> I verified all checksums/hashes via th
My vote -1
See https://github.com/apache/daffodil-vscode/issues/648. I'm still not
getting any output from a basic assert failure.
See also: https://github.com/apache/daffodil-vscode/issues/672
The fact that it now checks that files/dirs in the DaffodilDebugClasspath
exist is wonderful. Without
+1
I verified all checksums/hashes via the script which is a comment on the
release workflow page.
I re-tested all the schemas Owl has (public and private source) using the
3.5.0-rc1 with Java 17.
This is 84 total. Only those expected to fail (still in development)
failed. All others succeeded.
Shane,
648 I added info to the ticket. Basically make icmp1.bad.cmp where byte 1
is clobbered to be 0x00.
649, just modify the pcap.dfdl.xsd to make it not compile. E.g., put a
typographical error in some DFDL property name.
I agree with your assessment that the above 2 make sense for 1.3.0, but
I am a huge fan of the lihaoyi SourceCode library.
One can get rid of all the redundancy in Junit tests for TDML for example
and have
@Test test_my_tdml_test_name(): Unit = runTest()
and that runTest() can use the SourceCode library to reliably get the
method name which can then be converted int
le this.
>
> * The setDistinguishedRootNode function was removed from the Compiler
> class. Instead the root node should be passed as a parameter to the
> compileSource/File function, or withDistinguishedRootNode should be used
> on the ProcessorFactory.
>
> * The ParseResult.isA
ing layers, for example as we never hardened the API for
layers, so as it has evolved, schemas have broken.
On Mon, Jun 5, 2023 at 6:07 PM Mike Beckerle wrote:
>
> All critical and blocker type bugs have been fixed including a couple
> quite challenging ones in the last few weeks.
>
&
mikeb
Mike Beckerle
Apache Daffodil PMC | daffodil.apache.org
OGF DFDL Workgroup Co-Chair | www.ogf.org/ogf/doku.php/standards/dfdl/dfdl
Owl Cyber Defense | www.owlcyberdefense.com
;t
working, and seemed at the time like it might have been a Java 11 vs. 17
incompatibility. Clearly it ended up NOT being that.
-mikeb
On Mon, Jun 5, 2023 at 4:53 PM Mike Beckerle wrote:
> Well I had sufficient problems with it that I should re-verify if it works
> with Java 17. It may be
However, when it comes to Java I think if
> there is an issue with Java
> 17 we should figure that out first. Then maybe put it out for a vote or
> something about bundling
> a Java version with the extension and then letting the user specify a
> different path to Java or
> someth
the review phase to make sure that each issue is being properly and
> fully addressed.
>
> Shane is out, but I'm sure he'll have some additional follow up and things
> to try before making new pull requests.
>
>
> On Wed, May 31, 2023 at 7:02 PM Mike Beckerle
> wr
So it seems it went round full circle by telling you yes, you could bundle
the JVM, and this redhat java language thing does so, but then they tell
you it doesn't bundle the JVM anyway, it just uses the system one.
So was this answer useful, or just misleading?
might still be with that shell env variable you have
> for
> DAFFODIL_CLASSPATH, but this might only be an issue with a terminal that
> is already opened
> with the name "daffodil-debugger". If you close that terminal, the next
> you time you run it should
> create a new te
t; 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 Mike Beckerle wrote:
> > I have been able to continue evaluati
I wanted to revive this thread from a while back.
If Josh's analysis is right, and I think it is, we may have more
incompatibilities in 3.5.0 than we think.
Lots of internal API things changed package due to the fix allowing the
jars to be OGSI-ified. Many schemas may be depending on internal API
I think some of the techniques described here might smooth issues with the
VSCode extension e..g, it depending on Java 11, when the rest of all my
work now uses Java 17.
On Thu, Mar 2, 2023 at 10:46 AM Interrante, John A (GE Research, US) <
john.interra...@ge.com> wrote:
> Interesting article
t flatMap @ fs2.Compiler$Target.flatMap(Compiler.scala:163)
On Tue, May 23, 2023 at 5:19 PM Mike Beckerle wrote:
> I really am trying to eval the RC2.
>
> Right now my VMWare Linux system has been broken by recent updates to the
> MS Windows host environment.
>
> I don
A unix-domain socket would definitely be preferable.
On Tue, May 23, 2023 at 5:24 PM Shearer, Davin wrote:
> Is it possible that the daffodil debugger server could connect to a domain
> socket instead of a TCP socket? I think that could solve a lot of these
> issues.
>
> From
I really am trying to eval the RC2.
Right now my VMWare Linux system has been broken by recent updates to the
MS Windows host environment.
I don't exactly understand this, but the VSCode front end can no longer
connect to the server at localhost:4711. I get ECONNREFUSED. This started
when a bunc
I need more time. I won't be able to get to this before Monday.
On Tue, May 16, 2023 at 1:24 PM Shane Dell wrote:
> Hello all,I'd like to call a vote to release Apache Daffodil VS Code
> 1.3.0-rc2.
>
> All distribution packages, including signatures, digests, etc. can be
> found at:
> https://di
've concluded that the basics are not working sufficiently.
-mikeb
On Fri, Apr 28, 2023 at 11:52 AM Mike Beckerle 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
o.tdml"
}
Now I get to the first stop on the schema root.
On Fri, Apr 28, 2023 at 12:23 PM Mike Beckerle wrote:
> Operating system is Ubuntu 20.04.
>
> I have changed that to 4712, and that also fails same way.
>
>
> On Fri, Apr 28, 2023 at 12:11 PM Davin Shearer wrote:
&
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:
> > > >
-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 S
ke 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?
> &g
u svn checkout the entire repo
though)
Mike Beckerle
Apache Daffodil PMC | daffodil.apache.org
OGF DFDL Workgroup Co-Chair | www.ogf.org/ogf/doku.php/standards/dfdl/dfdl
Owl Cyber Defense | www.owlcyberdefense.com
I am not getting off the ground. I set out to evaluate this rc1.
I uninstalled the existing 1.2.0 visx. I installed the 1.3.0-rc1 visx. I
restarted VSCode.
I am trying to debug into PCAP. PCAP uses, via a jar file, the ethernetIP
DFDL schema as a component.
I deleted the old and created a new la
So I got a free trial of google "bard", which is google's
large language-model AI thing.
It recently was updated and supports writing code now.
It supports Scala.
This is amazingly better than just web search. Consider this session, which
starts from my query which is completely useless as a reg
uot;really close" to finished and you would
like to complete them in time for 3.5.0 please respond to this email.
Otherwise I would plan to move them to 3.5.1.
Or just discuss any of the tickets by responding to this thread.
Our plan for release 3.5.1 is to continue to focus on fixing bugs.
Another alternative is to leave the doc where it is, but have a page on the
main apache daffodil site linking to these various versions of the doc. Not
that different from the releases page here:
https://daffodil.apache.org/vscode/ . In fact one might have the releases
page serve mulitple purposes:
https://issues.apache.org/jira/browse/DAFFODIL-2803
I'd swear I saw work on this, but the ticket is open. Can you comment on
this?
-- Forwarded message -
From: Chris Lambertus
Date: Thu, Apr 6, 2023 at 7:41 PM
Subject: [ANNOUNCE] LDAP anonymous access removal
To:
Hi folks,
On April 14th 1600 UTC Infra will be removing the ability to query the ASF
LDAP service
anonymously. The directory will now require au
Access requires CAC or ECA Cert and authorization. They are on intelink.gov
(a sharepoint document library) at:
https://intelshare.intelink.gov/sites/ncdsmo/Shared
Documents/Forms/AllItems.aspx?RootFolder=%2Fsites%2Fncdsmo%2FShared
Documents%2FCDS Development Guidance and Software%2FFilters and Ot
@Steve Lawrence makes a good point that if a JIRA
user is added, that this doesn't generate any specific email (I don't
think), so that should be announced to this list.
On Wed, Mar 22, 2023 at 12:41 PM Steve Lawrence
wrote:
> Since this only grants access to GitHub issues and wiki (is that tru
I suggest add/remove collaborators is always done as a distinct PR that
ONLY adds/removes collaborators.
That eliminates a need for redundant emails to this list that are no
different than the PR itself.
On Wed, Mar 22, 2023 at 12:41 PM Steve Lawrence
wrote:
> Since this only grants access to G
I think the only thing that works is create PRs when you are requesting
review, not before.
On Wed, Mar 8, 2023 at 12:51 PM Adam Rosien wrote:
> Got it. Make drafts on your own forks then?
>
> On Tue, Mar 7, 2023 at 9:04 AM Mike Beckerle wrote:
>
> > Draft PRs - intenti
Draft PRs - intentionally created for review, are important. We don't want
those ignored.
On Tue, Mar 7, 2023 at 11:34 AM Adam Rosien wrote:
> Would it be possible to modify the email trigger script to ignore draft PR
> updates?
>
> On Tue, Mar 7, 2023 at 8:19 AM Mik
I'd like to request that people change the way they work slightly.
Please do NOT create a pull request until you are actually requesting
people to review your work. There's some things in github that seem to
suggest creating a PR then doing one's work there. This is problematic due
to the high tr
Please let me know if there is more you'd like to see added to this report
draft.
(It will be due probably Wed March 8)
-
## Description:
The mission of Apache Daffodil is the creation and maintenance of an
implementation of, and relat
Well for DFDL annotations not on the group definition. We should warn that
that will be ignored and the annotation placed on the sequence or choice
itself inside the group definition.
You can annotate a group reference however, and there's an annotation
element `` for that purpose.
For other anno
numbers the first digit is
changed when users can expect to have to adapt their code to changes.
What are people's thoughts on whether we should change 3.5.0-SNAPSHOT to
4.0.0-SNAPSHOT because we've made breaking changes?
Mike Beckerle
Apache Daffodil PMC | daffodil.apache.org
OGF DFDL Wo
he compiled executable and get a parse result from it, they can simply
> call the TDMLDFDLProcessor implementation. The semantics are pretty
> equivalent, only with TDML prefixed to the names. That's my rationale for
> the simplification.
>
> John
>
> -Origina
What you are suggesting sounds reasonable to me.
So the point of the base TDMLDFDProcessor was to enable us to create a TDML
processor from IBM DFDL (or other DFDL processors) for the IBM Cross Tester
rig. It's supposed to be the minimal interface that will let our TDML
runner drive a DFDL impleme
I suggest "codegen-c" as the name and convention.
I don't think the daffodil- prefix helps really and just makes all the
names long.
(Somewhere we had a discussion of eliminating all the daffodil- prefixes.
Can't recall why we didn't. )
On Fri, Feb 3, 2023 at 5:31 PM Interrante, John A (GE Rese
Has anyone tried running DAFFODIL
Mike Beckerle
Apache Daffodil PMC | daffodil.apache.org
OGF DFDL Workgroup Co-Chair | www.ogf.org/ogf/doku.php/standards/dfdl/dfdl
Owl Cyber Defense | www.owlcyberdefense.com
, Jan 11, 2023 at 5:45 PM Mike Beckerle
> wrote:
>
> > Just a warning. I installed java 19.0.1 and saw odd behaviors where tests
> > failed due to floating point number behavior changing. E.g., another
> digit
> > at the end of a long double float mantissa, etc
Just a warning. I installed java 19.0.1 and saw odd behaviors where tests
failed due to floating point number behavior changing. E.g., another digit
at the end of a long double float mantissa, etc.
I also saw some seemingly timing/non-deterministic behaviors. Ex where
a test fails sometimes, but n
libraries that don't
> >> already ship with Daffodil, then they should be marked as a dependency
> >> of the transformer and their jars downloaded and included in the
> >> classpath along with the transformer.
> >>
> >> You could maybe get around h
along with the transformer.
>
> You could maybe get around his by making your transformer a fat jar, but
> it might include all the Daffodil jars as well, which might cause some
> problems.
>
>
> On 2023-01-10 03:24 PM, Mike Beckerle wrote:
> > So I wrote a layer transforme
commons compress jar to the daffodil
classpath.
Is this expected behavior?
Mike Beckerle
Apache Daffodil PMC | daffodil.apache.org
OGF DFDL Workgroup Co-Chair | www.ogf.org/ogf/doku.php/standards/dfdl/dfdl
Owl Cyber Defense | www.owlcyberdefense.com
Ah, I reread this. I think I understand now.
The coroutine is set up, started, but control is on the main thread, which
hits an exception and the coroutine thread is left blocked.
On Fri, Jan 6, 2023, 12:56 PM Mike Beckerle wrote:
> So when using coroutines, the main code should be passed
So when using coroutines, the main code should be passed all exceptions. A
top level catch-throwable should surround all resumes on the peer coroutine
which should pass the object back to the waiting (always) main coroutine
which should rethrow it.
Since the two coroutines never run simultaneously
400 tickets) it is necessary
to revisit their priority sometimes.
If you feel this reassignment is incorrect for any particular ticket, be
sure to raise it as a discussion on our dev list.
Mike Beckerle
Apache Daffodil PMC | daffodil.apache.org
OGF DFDL Workgroup Co-Chair | www.ogf.org/ogf/doku.php
I'd also like to upvote DAFFODIL-2596, because we're simply running into it
a great deal now, and it is quite confusing especially to new DFDL schema
writers.
On Wed, Dec 14, 2022 at 6:07 PM Mike Beckerle wrote:
> I'd vote to increase priority of
> https://issues.apache.org
izing hot pieces of frequently run loops
> > like micro-benchmarks. If you really need native machine execution speed
> > along with good things like low energy consumption, memory/stack
> > protection, and functional computing, Rust is famous for providing all
> > th
; for consideration.
>
> -Davin
>
> On 12/14/22, 9:31 AM, "Mike Beckerle" wrote:
>
> It seems at this point we need an Apache Daffodil examples/misc repo
> that
> is recognized as part of the project, though like daffodil-site is not
> something wh
I guess I don't understand what it means for an enumerations library to
have "lots of integrations".
By this do you mean the versions of scala it supports, and the scala native
and scala js?
I think these things are pretty easy to support for a small library with no
dependencies at all.
re: Scala
container (reading from a TCP socket, writing to another TCP
> socket), so it would be good to update the streaming documentation too (
> https://issues.apache.org/jira/browse/DAFFODIL-2718).
>
> That's all I found within the first 200 "major" issues.
>
this should be named? I ask because daffodil-examples
seems too narrow. Utilities, test rigs, and such might want to live here.
Mike Beckerle
Apache Daffodil PMC | daffodil.apache.org
OGF DFDL Workgroup Co-Chair | www.ogf.org/ogf/doku.php/standards/dfdl/dfdl
Owl Cyber Defense | www.owlcyberdefense.com
gt; A teammate wants to know how to run Daffodil in streaming mode within a
> Docker container (reading from a TCP socket, writing to another TCP
> socket), so it would be good to update the streaming documentation too (
> https://issues.apache.org/jira/browse/DAFFODIL-2718).
>
> That
I approached Xerces about making the validator serializable. Got some
pushback that "this is hard".
On Fri, Dec 9, 2022 at 10:00 AM Steve Lawrence wrote:
> I believe the issue is that we don't serialize the XercesValidator used
> for full validation, I think maybe because it's not serializable?
hat
userid is a good choice.
Note that bugs can include performance problems as well as things not
working as they should. Some kinds of missing features can even be
considered to be "bugs" even if our JIRA classifies them as
improvements or new features.
Thanks
Mike Beckerle
that I do it?
>
> -Davin
>
> On 12/2/22, 1:19 PM, "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 page which
> is
>
d.
This was inserted by intellisense. I'm not sure what caused this, but I'm
not able to get back to the behavior where it inserts properties with the
dfdl: prefix on them any longer. Even if remove the default xmlns="..."
binding, put all the xs: back on everything, save, restart VSCode, it still
inserts properties like byteOrder without the required dfdl: prefix.
That's it for now.
Mike Beckerle
Apache Daffodil PMC | daffodil.apache.org
OGF DFDL Workgroup Co-Chair | www.ogf.org/ogf/doku.php/standards/dfdl/dfdl
Owl Cyber Defense | www.owlcyberdefense.com
My vote: +1
I verified all PCP sigs and sha512 hashes.
Debugging still works across files/jars of multiple schemas. So no
regressions there. I tested this by debugging the PCAP schema, which uses
the ethernetIP schema as a component schema.
The above are sufficient for a +1 from me.
I did atte
main one? As for the Vote should it be left open or should I close it and
> do an rc3 since this bug you found is a pretty important item that should
> be working when debugging?
>
> On 2022/11/29 22:51:20 Mike Beckerle wrote:
> > Verified the GPG signatures
> > Verified the s
tories, reduce burden on schema authors, and institute best
> practices.
>
> On Wed, Nov 30, 2022 at 9:48 AM Mike Beckerle
> wrote:
>
> > I never got any feedback on this idea. Thoughts? Observations?
> >
> > On Tue, Nov 1, 2022 at 11:17 AM Mike Beckerle
> >
I never got any feedback on this idea. Thoughts? Observations?
On Tue, Nov 1, 2022 at 11:17 AM Mike Beckerle wrote:
> I am having trouble regression testing schemas in bulk against the
> 3.4.0-RC1.
>
> The challenge is that there are 70+ such schemas. All of them have
> build.sb
Verified the GPG signatures
Verified the sha512 checksums
Alas, -1 because I couldn't get my standard (since 1.1.0) "check out
vscode" DFDL application to work.
This could be pilot error, but I'm just trying to get PCAP+EthernetIP DFDL
schemas to work and debug, which worked with 1.1.0, but I can
hat would need fixed before I
> close this vote and make a another release canidate.
>
>
> On 2022/11/17 16:28:12 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:
>
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 distribution packages, including signatures, digests, etc. can be
> found at:
> https://dis
101 - 200 of 621 matches
Mail list logo