I'm curious if a non-source-generated solution would work, specifically
Scala Native and Graal? That is, there are non-JVM targets that can be
built from the Scala source, and they can be extremely performant. The
current hotness is the "billion row challenge" (
https://github.com/gunnarmorling/1br
We have some experience with jnr-ffi: daffodil-vscode uses omega-edit via
jnr-ffi bindings for the extension's data editor. See
https://github.com/ctc-oss/omega-edit/blob/4965d83ae40284ec8cf7af71d7c692060dbd21fb/server/scala/api/src/main/scala/com/ctc/omega_edit/FFI.scala#L262
for the binding of th
t:
https://gist.github.com/arosien/7383b5aba1f15aeba847b8db8b44cdad
On Tue, Aug 29, 2023 at 8:36 AM Adam Rosien wrote:
> Hi Mike, those sound like bugs that do need to be addressed: debug levels,
> json output, etc. I'll look into them to reproduce and handle issues, etc.
>
> .. Adam
> In the launch.json, changing the debug level to INFO didn't reduce the
huge
> debug output to the terminal.
This doesn't happen for me; the INFO and DEBUG levels are respected. Can
you share your launch.json configuration?
The relevant section from my launch.json looks like:
...
"configuration
parameter sets the format of the file, so if you change the format to
"json" you currently have to update the filename suffix.
I'll include this bug in my forthcoming "rework the launch and extension
configuration" issue.
.. Adam
On Tue, Aug 29, 2023 at 8:36 AM Adam Rosie
Hi Mike, those sound like bugs that do need to be addressed: debug levels,
json output, etc. I'll look into them to reproduce and handle issues, etc.
.. Adam
On Tue, Aug 29, 2023 at 7:59 AM Mike Beckerle wrote:
> My vote +1 (However, I see already there is a binding -1, so oh well)
>
> I want t
pointing to the 3.5.0 release notes page for more
> > details might be useful.
> >
> > Also, please create a release notes page for this release. Ideally this
> > would be be done prior to the vote, since we should be checking and
> > voting on the release notes as w
e create a release notes page for this release. Ideally this
> would be be done prior to the vote, since we should be checking and
> voting on the release notes as well.
>
>
> On 2023-08-25 01:09 PM, Adam Rosien wrote:
> > I suspect the dfdl-ethernetip-1.2.0.jar your laun
, the 1.3.1 VSCode Daffodil extension will load it
correctly.
Perhaps we can put something in the release notes about schemas needing to
be recompiled with Daffodil 3.5.0 (if holds).
.. Adam
On Fri, Aug 25, 2023 at 8:42 AM Adam Rosien wrote:
> I see the same problem and will file an issue. I do
I see the same problem and will file an issue. I don't have any quick ideas
why it is happening.
.. Adam
On Fri, Aug 25, 2023 at 7:45 AM 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 ethe
There's
```
// format: off
...
// format: on
```
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, Mike Becke
Yeah, sorry, I hit send faster than my brain. You're right.
On Wed, Mar 8, 2023 at 9:55 AM Mike Beckerle wrote:
> 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 - 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
Would it be possible to modify the email trigger script to ignore draft PR
updates?
On Tue, Mar 7, 2023 at 8:19 AM Mike Beckerle wrote:
> 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 revie
https://inside.java/2022/09/23/quality-heads-up/ ?
On Wed, 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 man
Re: scala native, wouldn't it *not* have the optimizing JIT when not on the
JVM, therefore making it potentially slower if the (compiler-based)
optimizer is inferior?
On Thu, Dec 15, 2022 at 11:44 AM Interrante, John A (GE Research, US) <
john.interra...@ge.com> wrote:
> The words "lots of integr
For "integrations", it means the enumerations library has support for use
in other libraries like cats, json libraries, HTTP libraries, testing, ORM,
etc., so the user doesn't have to bridge enum support themselves.
On Thu, Dec 15, 2022 at 11:03 AM Mike Beckerle wrote:
> I guess I don't understa
Yay!
On Mon, May 2, 2022 at 4:22 PM Shane Dell wrote:
> 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".
>
> T
In sbt you can run `show evicted` to print the dependencies and what has
been overridden, although usually the highest version is chosen by default,
so it is a bit confusing that a earlier version was chosen.
Then something like
https://stackoverflow.com/questions/63272822/can-sbt-override-a-trans
d when building outside of git. For
> reproducibility, we want to be able to have the exact same builds
> regardless of git vs no git.
>
> On 3/22/22 12:16 PM, Adam Rosien wrote:
> > I have successfully hit a breakpoint on an included file using the
> > 1.0.0-rc2 candidate exte
rsion: 3.2.1
scalaVersion: 2.12.13
sbtVersion: 1.5.1
**
```
On Tue, Mar 22, 2022 at 9:06 AM Adam Rosien wrote:
> Ah a necessary
>
> > "daffodilDebugClasspath": ""
>
> was missing from my launch conf
Ah a necessary
> "daffodilDebugClasspath": ""
was missing from my launch config. Confirmed backend launches... debugging
continues
On Tue, Mar 22, 2022 at 8:58 AM Adam Rosien wrote:
> I installed the vsix file from
> https://dist.apache.org/repos/dist/dev/d
I installed the vsix file from
https://dist.apache.org/repos/dist/dev/daffodil/daffodil-vscode/1.0.0-rc2/bin/
and set up a launch configuration (included below) based on the EDIFACT
schema at https://github.com/DFDLSchemas/EDIFACT. When running the session
I get a popup with the following error, wh
I think it's better to cut a release and iterate on that testing-wise.
On Wed, Feb 23, 2022 at 7:24 AM Mike Beckerle wrote:
> I have not had time to test the vscode debugger recently.
>
> We could hold off doing that, or I could do that as part of the rc1
> evaluation process if you prefer befor
My understanding is the Typescript code gets "compiled" into Javascript
when built and packaged.
On Wed, Oct 13, 2021 at 9:07 AM Mike Beckerle wrote:
> Does the typescript code get compiled to a binary form (e.g., analogous to
> a jar) or is it distributed as source (e.g., more like javascript)?
:clap:
On Wed, Oct 6, 2021 at 1:44 PM Mike Beckerle wrote:
> I just pushed the main branch per the agreed githash to the new repo.
>
>
>
> On Wed, Oct 6, 2021 at 4:21 PM John Wass wrote:
>
> > Steps 1-7 sound good to me. Some thoughts
> >
> > > 1) push to https://github.com/apache/daffodil-vsc
+1 GitHub for the VSCode DAP debugger.
On Thu, Sep 23, 2021 at 7:29 AM Beckerle, Mike <
mbecke...@owlcyberdefense.com> wrote:
> So, I inquired about whether we need to use JIRA, or can just use github
> issues.
>
> I got a reply basically saying we can do what we prefer. (reply is below.
> Apache
2021 at 4:45 PM Adam Rosien wrote:
> I said I'd do it, but completely forgot! I'll get this out this weekend.
>
> .. Adam
>
> On Fri, Sep 17, 2021 at 3:24 PM Beckerle, Mike <
> mbecke...@owlcyberdefense.com> wrote:
>
>> I recall someone verifying the
I said I'd do it, but completely forgot! I'll get this out this weekend.
.. Adam
On Fri, Sep 17, 2021 at 3:24 PM Beckerle, Mike <
mbecke...@owlcyberdefense.com> wrote:
> I recall someone verifying the licenses on dependencies. I can't find that
> message now.
>
> However, this must be a transiti
- how to package and identify the
> >>>> contribution - some git questions
> >>>>
> >>>> Correct. For more information about Apache license compatibility:
> >>>>
> >>>> https://www.apache.org/legal/resolved.html
> >
microsoft.java.debug.core" % "0.31.1" - EPL 1.0
"co.fs2" %% "fs2-io" % "3.0.4" - MIT
"com.monovore" %% "decline-effect" % "2.1.0" - APL 2.0
"org.typelevel" %% "log4cats-slf4j" % "2.1.0" - APL 2.0
I can relay the list of dependencies and their licenses.
On Thu, Sep 9, 2021 at 9:20 AM Steve Lawrence wrote:
> I personally don't care too much about having the existing git history
> once its part of ASF, especially if it makes thing any easier (as you
> mention, squash/rebase can be difficut
The only other technique I know of is library "shading", where the build
system aliases the packages of the classes to something unique and
"relinks" the build to use that custom namespace for the library, allowing
multiple versions to coexist on the same classpath. Daffodil could then
shade the mo
riable update.
>
> 3) I can imagine a feature where a user would want to select an infoset
> item and jump to the associated schema element, or query information
> about that infoset item (e.g.. what bit position did it start at, what
> was the length). We don't have this rig
I just created one. You can find it at
>
> https://github.com/apache/daffodil-vscode
>
> The DFDLSchemas is not directly analogous, as there are other DFDL
> implementations and numerous schemas there are created by others for use
> with those implementations. E.g., EDIFACT, iso8586,
tations and numerous schemas there are created by others for use
> with those implementations. E.g., EDIFACT, iso8586, etc. It also all
> significantly pre-dates Apache Daffodil.
>
>
>
>
>
> From: Adam Rosien
> Sent: Tuesday, May 4, 2021 5:36
I've been extending John's debugger prototype to support DAP, the debug
protocol supported by VS Code and other IDEs. There's an animated gif of
what the VS Code interaction looks like, where only the current schema
element and data position are relayed, at [1].
Now that we've made these first ste
On Mon, Apr 26, 2021 at 10:23 AM Adam Rosien wrote:
> I'm currently seeing what it takes to get a minimal VS Code extension
> talking DAP over stdin/stdout to an external Scala process.
>
> On Fri, Apr 23, 2021 at 11:01 AM Adam Rosien wrote:
>
>> I've looked at scal
I'm currently seeing what it takes to get a minimal VS Code extension
talking DAP over stdin/stdout to an external Scala process.
On Fri, Apr 23, 2021 at 11:01 AM Adam Rosien wrote:
> I've looked at scala-debug-adapter a bit now, and it doesn't do very much:
> there&#x
I've looked at scala-debug-adapter a bit now, and it doesn't do very much:
there's some socket stuff and state management, but otherwise it delegates
to the underflying java-debug library which manages the DAP protocol [1].
*That* library does assume use of JDI and supplies JVM-level stuff to DAP
(
Sorry for the threading madness, my default of markdown quoting doesn't
interact well with mailing lists like this...
On Thu, Apr 22, 2021 at 11:14 AM Adam Rosien wrote:
>
>
> On Thu, Apr 22, 2021 at 7:03 AM Steve Lawrence
> wrote:
>
>> Some thoughts related to sh
ssions rather
> than the JDI JVM sessions.
>
>
>
>
> On Wed, Apr 21, 2021 at 7:52 PM Adam Rosien wrote:
>
> > I've been reading up on DAP and wanted to share...
> >
> > > There are many areas though that are unique to Daffodil that have no
> > representat
ot;source", which the UI can display. In the case of
stacktrace-as-schema-processing, each frame would correspond to the
location of the schema element, and the UI could focus on that location.
>
> On 4/21/21 7:52 PM, Adam Rosien wrote:
> > I've been reading up on
I've been reading up on DAP and wanted to share...
> There are many areas though that are unique to Daffodil that have no
representation in the spec. These things (like InputStream, Infoset, PoU,
different variable types, backtracking, etc) will need an extension to
DAP. This really boils down t
There's a way to limit the incoming activity for various categories of
participants:
https://docs.github.com/en/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository
:
> Enabling an interaction limit for a repository restricts certain users
from commenting, ope
https://issues.apache.org/jira/browse/DAFFODIL-2133 for related issue.
>
> - Steve
>
> On 4/19/21 11:37 AM, Adam Rosien wrote:
> > As a Scala project, however, how about using Scalafmt? [1] It's become
> > standard in all the projects I've been involved with; it
As a Scala project, however, how about using Scalafmt? [1] It's become
standard in all the projects I've been involved with; it's supported by the
language creators and matches the previously mentioned features.
.. Adam
[1] https://scalameta.org/scalafmt/
On Mon, Apr 19, 2021 at 8:20 AM Interran
Hi everybody, I've recently started working on Daffodil with some other
folks and will be helping where I can with the debugger.
I've been writing Scala since ~2011 and recently wrote a book about Cats
Effect, which has a similar scope to ZIO (effects, concurrency, etc.). If
anybody has any questi
48 matches
Mail list logo
