So tweetdeck appears to be no more. Or rather, you have to pay for
what they now call XPro.
Should we still bother with this stuff? X/twitter is a lot less
relevant these days.
Personally, I think X/twitter is a big polluter of the media space and
kind of prefer to avoid it.
The Apache Daffodil community is pleased to announce the
release of version 3.8.0.
Notable changes in this release include a supported API for Daffodil layers.
Layers are a Daffodil extension to the DFDL language
which are small algorithmic code plugins for computing checksums/CRCs
on regions of
The VOTE to release Apache Daffodil 3.8.0-rc2 is now closed.
The vote passes with:
3 binding +1
The VOTE thread:
The Vote thread is here:
https://lists.apache.org/thread/fm7bfbcd01z9c38dos8h6dxhfjqg2rgw
The vote breakdown is:
+1 Michael Beckerle (binding)
+1 Stephen Lawrence(binding)
+1
On Tue, Jun 11, 2024 at 12:37 PM Mike Beckerle wrote:
>
> Hi all,
>
> I'd like to call a vote to release Apache Daffodil 3.8.0-rc2.
>
> Since RC1,
> * a Keys/Signing issue has been resolved
> * a schema-compilation performance issue was found to be non-reproducible
>
Hi all,
I'd like to call a vote to release Apache Daffodil 3.8.0-rc2.
Since RC1,
* a Keys/Signing issue has been resolved
* a schema-compilation performance issue was found to be non-reproducible
All distribution packages, including signatures, digests, etc. can be found at:
ur KEYS file, and this doesn't match D87AD4BD985035CD
> mentioned in the VOTE email. Is this the wrong key?
>
>
> On 2024-06-06 02:38 PM, Mike Beckerle wrote:
> > Hi all,
> >
> > I'd like to call a vote to release Apache Daffodil 3.8.0-rc1.
> >
> > All distribution
might help.
>
> On 2024-06-08 03:12 PM, Mike Beckerle wrote:
> > -1 binding
> >
> > [OK] Verified all signatures, md5, sha1, sha512, etc. Log of that is
> > at the bottom of this message:
> >
> > [OK] Regression tested 79 DFDL schemas that Owl has in a repos
mate]
PASSED GPG Signature Check
ALL ARCHIVES VALIDATED GPG SIGNATURES
sha512sum ./apache-daffodil-3.8.0-bin.zip
PASS SHA512 Comparison
sha512sum ./apache-daffodil-3.8.0-bin.msi
PASS SHA512 Comparison
sha512sum ./apache-daffodil-3.8.0-bin.tgz
PASS SHA512 Comparison
sha512sum ./apache-daffodil-3.8.0-src.zip
and source
> [OK] Successfully used apache-daffodil-3.8.0-bin.tgz
> [OK] JavaDoc and ScalaDoc are correct
>
>
>
> --
> Lola Kilo
>
> From: Mike Beckerle
> Sent: Thursday, June 6, 2024 2:38 PM
> To: dev@daffodil.apache.org
>
Should this wait for 3.8.0 daffodil so it can work with the latest?
Will not be much of a delay assuming 3.8.0 doesn't have lots of regressions.
On Tue, Jun 4, 2024 at 10:05 AM Shane Dell wrote:
>
> Hello all,
>
> The Apache Daffodil VS Code Extension development team believes we are
> ready to
Thank you for the discussion. I will submit the report with the
suggested additions.
-- Forwarded message -
From: Mike Beckerle
Date: Tue, Jun 4, 2024 at 11:31 AM
Subject: Re: [DISCUSS] Daffodil Board Report due by Wed Jun 12th -
Initial Reminder
To:
Our reports are one-month
Hi all,
I'd like to call a vote to release Apache Daffodil 3.8.0-rc1.
All distribution packages, including signatures, digests, etc. can be found at:
https://dist.apache.org/repos/dist/dev/daffodil/3.8.0-rc1/
Staging artifacts can be found at:
Strange issue.
I have found that using fedora 39 fixes this. So the rest of this may be
TL;DR.
This is more for posterity on our dev list in case someone else runs into
similar issues.
So I'm trying to build a release candidate, I'm using a computer,
running ubuntu 22.04, just an older laptop I
ould be quick for someone to give them
> all a +1
> > and merge.
> >
> >
> >
> > On 2024-05-31 03:03 PM, Mike Beckerle wrote:
> >> There is one major feature in 3.8.0, the revised "layers" API.
> >>
> >> I'd like to discuss releasing 3.
hat 3.8.0 will be release this month
> so 2Q2024
>
> On 2024-06-03 09:32 AM, Mike Beckerle wrote:
> > Our board report is due no later than next Wed.
> >
> > Here's a draft that I created as an evolution of our prior quarterly
> > report.
> >
> > Please com
ould be quick for someone to give them
> all a +1
> > and merge.
> >
> >
> >
> > On 2024-05-31 03:03 PM, Mike Beckerle wrote:
> >> There is one major feature in 3.8.0, the revised "layers" API.
> >>
> >> I'd like to discuss releasing 3.
Our board report is due no later than next Wed.
Here's a draft that I created as an evolution of our prior quarterly
report.
Please comment or suggest added points.
Specifically I'd like to update the status about the VSCode extension work,
which frankly I have been too busy to keep track of.
.0/javadoc/org/apache/daffodil/runtime1/layers/api/package-summary.html
If this discussion is positive I'll look into creating a release candidate
for evaluation.
Mike Beckerle
Apache Daffodil PMC | daffodil.apache.org
OGF DFDL Workgroup Co-Chair | www.ogf.org/ogf/doku.php/standards/dfdl/dfdl
I can't find tests that actually use these layers.
I have found only unit test of the underpinnings of these (ex:
TestByteSwapStreams), but not an actual TDML/DFDL-based test.
Am I missing something? Is there a test of this elsewhere someplace?
Mike Beckerle
Apache Daffodil PMC
There's some discussion of unmanagedSourceDirectories being a way of doing
this online.
Ultimately, I'd like all packages with "api" in their names, to get their
scaladoc and javadoc generated and included.
I have no idea if this is feasible.
On Mon, May 13, 2024 at 1:38 PM Mike Becke
Crickets on this.
If you want to see these tools in use, look at the gzip layer tests in
daffodil-core.
On Sat, Mar 23, 2024 at 11:34 PM Mike Beckerle wrote:
> I have some new fuzz testing stuff.
>
> It depends on TestUtils which is in daffodil-core, but lives in the
> src/te
+1
I verified hashes and signatures of source and binaries.
I discussed the usage tests I wanted to do with Steve L and he already did
those tests, so I did not repeat them.
On Fri, Apr 26, 2024 at 9:45 AM Steve Lawrence wrote:
> +1 (binding)
>
> I checked:
>
> [OK] hashes and signatures of
I'm looking for a machine readable specification i.e., not the spec
document, of the messages in this data format.
Like that could be used to generate a DFDL schema.
Any leads appreciated.
Need a release of this tool as soon as possible, so +1 on version 1.0.0
release of this tool.
On Mon, Apr 22, 2024 at 12:37 PM Steve Lawrence
wrote:
> I think the Daffodil SBT Plugin is in a good state where it is ready help
> manage, build, test, and release DFDL schema projects. All open pull
Just letting you all know I'll be away on mostly a vacation returning April
17.
be added to enhance the VS debugger extension?
> Larry
>
> -Original Message-
> From: Mike Beckerle
> Sent: Monday, March 18, 2024 11:22 AM
> To: dev@daffodil.apache.org
> Subject: Re: Discuss: Layer changes - 3.7.0 or 4.0.0 ?
>
> I think the compelling argumen
Nevermind. I learned that workflows don't run if your branch has conflicts
with the branch it will merge into.
On Sun, Mar 24, 2024 at 1:18 AM Mike Beckerle wrote:
> The push to this branch on my fork usually causes our workflows that test
> it on all those configurations, to run.
>
The push to this branch on my fork usually causes our workflows that test
it on all those configurations, to run.
Nothing running though. It says no workflows.
Anybody have a clue why?
On Sun, Mar 24, 2024 at 12:24 AM Mike Beckerle
wrote:
> *@mbeckerle* commented on this pull requ
that depend on this module have to move out of
daffodil-core because daffodil-test-tools will depend on core.
Yet a third possibility is to publish a daffodil-core test jar so that
others can depend on things in daffodil-core src/test.
Mike Beckerle
Apache Daffodil PMC | daffodil.apache.org
OGF DFDL
on a bare-metal Ubuntu Mate 22.04
install on a different laptop.
On Sat, Mar 16, 2024 at 3:11 PM Mike Beckerle wrote:
> Yeah, unfortunately I have had to back out of ubuntu 22.04 to ubuntu 20.04
> due to the system hangs problem. I'm now setting up the 20.04 system and
> that does not have lib
So Owl has a ZipLayer - for messages that contain the bytes of a zip file.
As part of exercising these new Daffodil Layer APIs, I have rewritten this
Zip Layer.
I have written a fuzz tester, the objective being to try to crash the
layers so they throw bad exceptions like NPE or other ill-behaved
If we can get 1065 (diagnostic file URLs fix) into the release that would
be great. It's worth waiting a day or two for this.
I think the layer changes should go into 3.8.0, which could follow fairly
closely behind 3.7.0 time-line wise, but I'd suggest it is the only change
in that release
; for that to be the next release. Maybe we can only focus on those changes
> for
> the next release and get 4.0.0 out relatively soon after 3.7.0.
>
>
>
>
> On 2024-03-16 07:40 PM, Mike Beckerle wrote:
> > Separate from the pull request review, I want to discuss whether these
>
the
two implementations, old and this new one, could co-exist for a release.
Another thought is to just punt on 3.7.0, and renumber so our next release
is 4.0.0, where we're allowed more to break things and not be backward
compatible.
Thoughts on this?
Mike Beckerle
Apache Daffodil PMC
-- Forwarded message -
From: Mike Beckerle
Date: Sat, Mar 16, 2024 at 4:23 PM
Subject: [apache/daffodil] 4th (and final) cut of New Layer API & Improved
Implementation (PR #1187)
To: apache/daffodil
Cc: Mike Beckerle , Your activity <
your_activ...@noreply.github.com>
t/setup.html#installation>
>
> If the first binary release you download doesn't work, downloading a
> sufficiently old binary release should work, or you can build the library
> from source. But as I said, you probably should not worry about
> libcriterion-dev at all.
>
> J
The build instructions call for a module libcriterion-dev which ubuntu
(20.04) seems to not know about.
Trying to install it piece by piece leads to
libcriterion-dev requires libcriterion3 which requires libc6(>=2.38)... at
that point I figured I better stop and ask, as I have libc6 2.31-1
I am creating negative tests. There are already a couple bugs that are
problematic.
A processing error during the read operation of a layer stream does not
propagate as a parse error and cause backtracking as it should.
On Wed, Mar 13, 2024 at 6:50 PM Mike Beckerle
wrote:
> @mbeckerle <
This is waiting for more tests for the various error conditions so that
there will be coverage of the error paths.
On Tue, Mar 12, 2024 at 11:33 PM Mike Beckerle
wrote:
> @mbeckerle <https://github.com/mbeckerle> pushed 1 commit.
>
>- 1e4f2b8
>
> <https://gi
Here is a draft of our Quarterly report to the ASF Board.
If you have things to add, edit away and send back to me. For the
most part the board's concerns are associated with the ASF theme
"Community Over Code", as in is our project healthy and moving
forward. They're less interested in
n 2024-03-09 02:59 PM, Mike Beckerle wrote:
> > Does anyone know why Daffodil searches for the files that advertise SPI
> > services for layers, charsets, and validators under resources/M.services
> > instead of the standard resources/META-INF/services directory, as is
searching for SPI info suggests "M.services" would have to be
configured somehow, but I cannot find any such configuration.
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
dded settings to launch.json for root element name and namespace to
> debug schema files from a jar
> * Upgrade to Daffodil 3.6.0
>
> Hope it helps!
>
>
> From: Mike Beckerle
> Date: Friday, March 8, 2024 at 1:12 PM
> To: dev@daffodil.apache.org
> Subject: Quiet on t
and a link to the mail thread is a
fine response. I've missed lots of emails over the last month or two.
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
/+/refs/tags/go1.22.0:src/go/token/token.go;l=233
>
> JavaScript allows it too but that is more of a preference thing (same
> thing with using semicolons or not).
>
> I can't say that I've seen common use of the comma preceding content on a
> line.
>
> // Mike
>
>
&g
> But with trailing commas the diff is this:
>
> Seq(
> 1,
> 2,
>+ 3,
> )
>
> IMO, the latter makes it much more clear that you're just adding "3" to
> the Seq and makes code review a little easier.
>
>
> On 2024-03-01 05:36 PM, Mik
as hell
.
Unless someone has a very very good reason why this should not change, I'm
very inclined to go back to scalafmt trailingCommas = never behavior.
Thoughts?
Mike Beckerle
Apache Daffodil PMC | daffodil.apache.org
OGF DFDL Workgroup Co-Chair | www.ogf.org/ogf/doku.php/standards/dfdl/dfdl
Owl
ame, e.g.
>
>@throws java.io.Exception ...
>
> Our UDF API is written in java and uses @throws with full package names
> that seems to work.
>
> On 2024-02-28 04:46 PM, Mike Beckerle wrote:
> > I am having trouble with scaladoc and javadoc.
I am having trouble with scaladoc and javadoc.
javadoc comments like this:
/**
* Wraps a layer encoder around the given OutputStream.
*
* @param jos The OutputStream to be wrapped.
* @param lr The LayerRuntime object containing runtime information
and stateful services.
* @return The
This looks very useful. Is the intention to use this as doc, or to generate
code or both?
I suggest we need this committed somewhere as a data structure. (Each sheet
as a CSV form is fine)
It is rather hard to review this in detail. Some of the same information
content should be derivable (via
check for forward progress on the problematic DFDL 1.0
> features seems worthwhile implementing. A schema compile time check would
> be even better if a way is found to formally prove the theoretical O(sn)
> constraint.
>
> -----Original Message-
> From: Mike Beckerle
> Se
ma compile time check would
> be even better if a way is found to formally prove the theoretical O(sn)
> constraint.
>
> -----Original Message-
> From: Mike Beckerle
> Sent: Wednesday, January 24, 2024 1:55 PM
> To: dev@daffodil.apache.org
> Subject: EXT: Theoretical Int
I don't know that we need automation for this.
I closed out and linked back from the associated JIRA tickets several of
these.
The remaining PRs all seem ok to me and are less than a year old.
On Tue, Feb 6, 2024 at 10:52 AM Steve Lawrence wrote:
> We have a relatively large number of stale
Workstation long term.
I'd run Linux natively, but my employer requires that we use managed
laptops, but we can use Virtual Machines on them for development.
Mike Beckerle
Apache Daffodil PMC | daffodil.apache.org
OGF DFDL Workgroup Co-Chair | www.ogf.org/ogf/doku.php/standards/dfdl/dfdl
Owl
someplace later.
If this is of interest, please take a look at this github pull request
below.
-- Forwarded message -----
From: Mike Beckerle
Date: Wed, Jan 24, 2024 at 3:50 PM
Subject: [mbeckerle/superexp] Example schema that illustrates pathological
DFDL behaviors (PR #1)
To: mbecker
it, their
trademark rules, etc.
At that point it will make sense to send this info to our users lists, make
a blog post, etc.
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
+1
I'd like to use this plugin as part of work I'm doing to integrate Daffodil
and Apache Drill.
Drill is distributed. Having a standard way to compile schemas makes it
easier to arrange to move them around the drill cluster (e.g., in a Jar
file)
On Thu, Jan 18, 2024 at 11:09 AM Steve Lawrence
ng a Rust backend makes sense, although we don’t think there is a
> > Rust to hardware path – at least none that we are aware of. What did you
> > mean by the phrase “basis for generating VHDL or System Verilog?”
> >
> > John
> >
> > From: Mike Beckerle
For status and searchability.
-- Forwarded message -
From: Rich Gillam (Unicode Jira)
Date: Thu, Jan 11, 2024 at 12:44 PM
Subject: [JIRA] (CLDR-17309) Pattern "#.##" fails to suppress leading 0
digit
To:
Rich Gillam *made 2 updates* and *added 1 new comment*. CLDR/CLDR-17309
affodil should have a Rust backend.
>
> -Original Message-
> From: Mike Beckerle
> Sent: Friday, January 12, 2024 5:50 AM
> To: dev@daffodil.apache.org
> Subject: EXT: Re: Rust vs. C backend
>
> what I meant by "What did you mean by the phrase “basis for generating
> VH
– at least none that we are aware of. What did you
> mean by the phrase “basis for generating VHDL or System Verilog?”
>
> John
>
> From: Mike Beckerle
> Sent: Thursday, January 11, 2024 5:13 AM
> To: John Interrante
> Cc: dev@daffodil.apache.org
> Subject: EXT:
language that would be acceptable
I believe ultimately, the goal is to generate a useful software
implementation that does not compromise on performance, and to be a basis
for generating VHDL or System Verilog.
I imagine you've given this some thought you can share.
Mike Beckerle
Apache Daffodil PMC
ance by changing to
> > copy-on-write. We may want to do some profiling on formats with lots of
> > PoUs to see if anything shows up.
> >
> >
> > On 2024-01-09 04:03 PM, Mike Beckerle wrote:
> >> Actually, I haven't measured it, but there are 4 built in variables, s
Original Message-----
> From: Mike Beckerle
> Sent: Tuesday, January 9, 2024 1:39 PM
> To: dev@daffodil.apache.org
> Subject: Thoughts on on demand copying of parser state
>
> Right now we copy the state of the parser as every point of uncertainty is
> reached.
>
&
Right now we copy the state of the parser as every point of uncertainty is
reached.
I am speculating that we could copy on demand. So, for example, if no
variable modifying operation occurs then there would be no overhead to
copy the variable state.
This comes at the cost of each variable doing
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, 2023 at 1:49 PM Shane Dell wrote:
>
>> He
b repository.
> The specific issue I am referring to,
> https://github.com/apache/daffodil-vscode/issues/653, was reported by Mike
> Beckerle and we are looking for 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
See Drill PR: https://github.com/apache/drill/pull/2836
When I say "mostly working" the metadata bridge, and data bridge work, but
Drill is a distributed system and nothing has been done yet about
distributing the DFDL schema (or compiled binary) out to the distributed
processing nodes.
Next:
-
I may have submitted this too late (I didn't get reminder emails about it)
so may have to resubmit in January.
Here's is what I submitted as our quarterly report:
## Description:
The mission of Apache Daffodil is the creation and maintenance of software
related to an implementation of the Data
Please add relevant status information or topics.
---
## Description: The mission of Apache Daffodil is the creation and
maintenance of software related to an implementation of the Data Format
Description Language (DFDL) used to convert between fixed format data and
more readily
daffodil with git hash d26a582b62c5e26b4bcac895b9cb8960c3ce8522
(2023-11-14) or newer supports the metadata and data bridges used by the
current drill integration work I have been doing.
I no longer have a special fork of the daffodil repo.
On Fri, Nov 10, 2023 at 7:00 PM Mike Beckerle wrote
, branch daffodil-2835.
My next step is to go back to daffodil, and get all the changes I have
needed there integrated in and pushed to the main branch.
That way at least others will have an easier time running this Drill
branch of mine to see what is going wrong.
Mike Beckerle
Apache Daffodil PMC
made Tue 31 Oct 2023 10:37:42 AM EDT
gpg:using RSA key B58C81142758101A43D5B17D36F3494B033AE661
gpg: Good signature from "Steve Lawrence " [full]
PASSED GPG Signature Check
ALL ARCHIVES VALIDATED GPG SIGNATURES
sha512sum ./apache-daffodil-3.6.0-bin.msi
PASS SHA512 Comparison
+1 (binding)
I'm trying to make a very big DFDL multi-part schema work,and all tests
(thousands) pass save just 2.
The 2 tests that fail I believe are pilot error in the test configurations.
My only small misgiving is that I haven't got it resolved to exactly why
yet. But it feels very unlikely
I'm getting this warning:
(yes I've set my build.sbt to 3.7.0-SNAPSHOT for now)
What would cause a dependency from daffodil-lib to an earlier version of
daffodil lib?
[warn] circular dependency found:
My vote -1
Too many regressions. Existing schemas need to keep working if at all
possible.
I think the issue of properties having whitespace e.g., dfdlx:repValues="0
" breaking due to the trailing space is a blocker. If that was tolerated
before, it needs to be tolerated forever.
I think the
I withdraw my prior statement. I'm convinced by John's reasoning that 3.6.0
is a better choice.
On Wed, Oct 18, 2023 at 10:00 AM Interrante, John A (GE Aerospace, US) <
john.interra...@ge.com> wrote:
> Yes, I have some C code generator changes that I haven't had time to
> collect into a PR yet.
I think 3.5.1 is the right number, as that is consistent with our odd-bug
fix, even-features convention on the 2nd component of the version number.
So 3.6.0 should be for the next addition of true new features.
On Wed, Oct 18, 2023 at 9:20 AM Steve Lawrence wrote:
> It's been a few months
.
The metadata bridge is here, and a stub of the data bridge - handles only
simple type "INT" right now, and of course doesn't compile yet.
https://github.com/apache/drill/pull/2836
-- Forwarded message -----
From: Mike Beckerle
Date: Fri, Oct 13, 2023 at 11:11 PM
Subjec
clined if the
> >> batch is full)
> >> * Write each field. For complex fields, such as records, recursively do
> the
> >> start/end record work.
> >> * Mark the record as complete.
> >>
> >> You should be able to map event handlers to EVF actions as a result
Daffodil parsing generates event callbacks to an InfosetOutputter, which is
analogous to a SAX event handler.
Drill is expecting an iterator style of calling next() to advance through
the input, i.e., Drill has the control thread and expects to do pull
parsing. At least from the code I studied in
ase 8 " warnings for Java and Scala compilation when
compiling with Java 21.
This is a more attractive alternative now.
On Tue, Oct 3, 2023 at 10:16 AM Mike Beckerle wrote:
>
> So Java 21 deprecates, but does not eliminate, Java 8 compatibility.
>
> You get an unavoidable warning.
"in effect" deprecate 3.5.0 and suggest people jump to 4.0.0
instead, and that means releasing 4.0.0 very soon. 3.5.0 should be our last
release which supports Java 8 JVMs.
Thoughts?
Mike Beckerle
Apache Daffodil PMC | daffodil.apache.org
OGF DFDL Workgroup Co-Chair | www.ogf.org/og
ulting URL can be
opened.
On Mon, Sep 25, 2023 at 1:55 PM Mike Beckerle wrote:
>
>> Instead of feeding the new resource path (e.g. /d1/quux.dfdl.xsd) into
>> getResource, can you strip off everything after the exclamation in the
>> original jar path, append
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.
>
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
ght 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, maybe that amount
> > precision error is fine?
&
ions 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 values in a few cases. Som
alternative 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
dd 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:
> > (Reviving this discussion threa
ta 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-safe cache data structure.
>
> On 2023-08-16 12:39 PM, Mi
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,
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:50 A
y 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
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
+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
ayer 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 NoCacheEvaluatable, so even if the schema does
> > dfd
1 - 100 of 541 matches
Mail list logo
