Re: [ANN] Clojure 1.10.0-alpha7
Would it be an idea to include something like
```
clj -Sdeps '{:deps {org.clojure/clojure {:mvn/version "1.10.0-alpha7"’
```
in such announcements so the lazy of us could just copy/paste it into our
shells to try it out?
Erik.
> On 5 Sep 2018, at 14:39, Stuart Halloway wrote:
>
> org.clojure/clojure {:mvn/version "1.10.0-alpha7"}
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
---
You received this message because you are subscribed to the Google Groups
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [ANN] spec.alpha 0.2.176 and core.specs.alpha 0.2.44
This is fantastic! Thank you Alex
-Gordon
On Wednesday, 5 September 2018 13:24:02 UTC+1, Alex Miller wrote:
>
> New releases of spec.alpha and core.specs.alpha are not available. These
> releases make several changes to spec error printing and to the definition
> of the existing clojure.core macro specs to improve readability and error
> reporting. Some additional changes are coming in 1.10.0-alpha7, but these
> libraries can be used now with Clojure 1.9.0.
>
> deps.edn:
>
> org.clojure/spec.alpha {:mvn "0.2.176"}
> org.clojure/core.specs.alpha {:mvn "0.2.44"}
>
>
> spec.alpha 0.2.176
>
>- CLJ-2373 Don't print
>ex-info into spec errors
>- CLJ-2391 Change spec
>problem line print order
>- CLJ-2392 Stop
>prepending :args to spec problem paths
>- CLJ-2393 Sort on
>descending "in" length before "at" length
>
>
> core.specs.alpha 0.2.44
>
>- CLJ-2395 improve path
>names and predicate names in core specs
>
>
>
>
>
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
---
You received this message because you are subscribed to the Google Groups
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [ANN] Clojure 1.10.0-alpha7
On Wednesday, 5 September 2018 13:39:36 UTC+1, stuart@gmail.com wrote: > > 1.10.0-alpha7 includes the following changes since 1.10.0-alpha6: > I was pleased to see that going from alpha 6 to 7 found an error in one of my tests. I had something like (is (= (x (func y and the new version reports > error: java.lang.Exception: = expects more than one argument > But (purely for my own interest) I tried to discover which change in clojure source made the difference and I couldn't. -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [ANN] Clojure 1.10.0-alpha7
Hi Erik,
That does seem like a good idea. Thanks!
Stu
On Thu, Sep 6, 2018 at 4:39 AM Erik Assum wrote:
> Would it be an idea to include something like
>
> ```
> clj -Sdeps '{:deps {org.clojure/clojure {:mvn/version "1.10.0-alpha7"’
> ```
>
> in such announcements so the lazy of us could just copy/paste it into our
> shells to try it out?
>
> Erik.
>
> On 5 Sep 2018, at 14:39, Stuart Halloway
> wrote:
>
> org.clojure/clojure {:mvn/version "1.10.0-alpha7"}
>
>
> --
> You received this message because you are subscribed to the Google
> Groups "Clojure" group.
> To post to this group, send email to clojure@googlegroups.com
> Note that posts from new members are moderated - please be patient with
> your first post.
> To unsubscribe from this group, send email to
> clojure+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/clojure?hl=en
> ---
> You received this message because you are subscribed to the Google Groups
> "Clojure" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to clojure+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
---
You received this message because you are subscribed to the Google Groups
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: Pipe shell output into REPL?
You can use tmux and run your REPL inside a pane. You can then use the tmux commands set-buffer and paste-buffer, wrapped in a little shell, to send text to the REPL. (This is actually how the Kakoune editor does REPLs.) On Wed, Sep 5, 2018 at 9:56 PM Didier wrote: > Hi all, > > I was wondering if there is an easy way I can pipe my shell output into a > REPL. Something like: > > cat /tmp/remus-lighthouse-apis-info.ion | lein repl > > When I try this, it starts a REPL, and then each line gets sent one by one > to the REPL and ran. > > I'd like it so that I'm at the REPL, and standard in is ready to be read > by me, from the REPL, so I can manipulate the input being piped how I see > fit within the repl session. > > Is there anyway to do this? > > -- > You received this message because you are subscribed to the Google > Groups "Clojure" group. > To post to this group, send email to clojure@googlegroups.com > Note that posts from new members are moderated - please be patient with > your first post. > To unsubscribe from this group, send email to > clojure+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/clojure?hl=en > --- > You received this message because you are subscribed to the Google Groups > "Clojure" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to clojure+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [ANN] Clojure 1.10.0-alpha7
Peter: I do not know why you are seeing this change in behavior. In order to see if I could determine why, I created my own unit test based on your description, but when I run my incorrectly unit test with Clojure 1.10.0-alpha6 or 1.10.0-alpha7, I get the same results -- no failures, and no "error: java.lang.Exception: = expects more than one argument" exception as you are seeing. I am probably doing something too different from your code. I created a tiny test repo on Github with what I tried, here: https://github.com/jafingerhut/catch-bad-unit-test Here is the unit test I tried: https://github.com/jafingerhut/catch-bad-unit-test where the definitions of functions x and y are simply these: https://github.com/jafingerhut/catch-bad-unit-test/blob/master/src/catchme/core.clj#L3-L7 If you have a few minutes to try out the tests in my repo to see if you get different results than I did, I'd be curious to hear if your results are different. I'd be more curious to learn of a way to write a unit test that gives the exception you see with Clojure 1.10.0-alpha7. Andy On Thu, Sep 6, 2018 at 4:34 AM Peter Hull wrote: > On Wednesday, 5 September 2018 13:39:36 UTC+1, stuart@gmail.com wrote: >> >> 1.10.0-alpha7 includes the following changes since 1.10.0-alpha6: >> > > I was pleased to see that going from alpha 6 to 7 found an error in one of > my tests. I had something like > (is (= (x (func y > and the new version reports > >> error: java.lang.Exception: = expects more than one argument >> > > But (purely for my own interest) I tried to discover which change in > clojure source made the difference and I couldn't. > > -- > You received this message because you are subscribed to the Google > Groups "Clojure" group. > To post to this group, send email to clojure@googlegroups.com > Note that posts from new members are moderated - please be patient with > your first post. > To unsubscribe from this group, send email to > clojure+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/clojure?hl=en > --- > You received this message because you are subscribed to the Google Groups > "Clojure" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to clojure+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [ANN] Clojure 1.10.0-alpha7
Sorry, wrong link to the unit test that I tried, which should have been: https://github.com/jafingerhut/catch-bad-unit-test/blob/master/test/catchme/core_test.clj#L5-L7 On Thu, Sep 6, 2018 at 7:08 AM Andy Fingerhut wrote: > Peter: > > I do not know why you are seeing this change in behavior. In order to see > if I could determine why, I created my own unit test based on your > description, but when I run my incorrectly unit test with Clojure > 1.10.0-alpha6 or 1.10.0-alpha7, I get the same results -- no failures, and > no "error: java.lang.Exception: = expects more than one argument" exception > as you are seeing. I am probably doing something too different from your > code. > > I created a tiny test repo on Github with what I tried, here: > https://github.com/jafingerhut/catch-bad-unit-test > > Here is the unit test I tried: > https://github.com/jafingerhut/catch-bad-unit-test > > where the definitions of functions x and y are simply these: > https://github.com/jafingerhut/catch-bad-unit-test/blob/master/src/catchme/core.clj#L3-L7 > > If you have a few minutes to try out the tests in my repo to see if you > get different results than I did, I'd be curious to hear if your results > are different. I'd be more curious to learn of a way to write a unit test > that gives the exception you see with Clojure 1.10.0-alpha7. > > Andy > > > On Thu, Sep 6, 2018 at 4:34 AM Peter Hull wrote: > >> On Wednesday, 5 September 2018 13:39:36 UTC+1, stuart@gmail.com >> wrote: >>> >>> 1.10.0-alpha7 includes the following changes since 1.10.0-alpha6: >>> >> >> I was pleased to see that going from alpha 6 to 7 found an error in one >> of my tests. I had something like >> (is (= (x (func y >> and the new version reports >> >>> error: java.lang.Exception: = expects more than one argument >>> >> >> But (purely for my own interest) I tried to discover which change in >> clojure source made the difference and I couldn't. >> >> -- >> You received this message because you are subscribed to the Google >> Groups "Clojure" group. >> To post to this group, send email to clojure@googlegroups.com >> Note that posts from new members are moderated - please be patient with >> your first post. >> To unsubscribe from this group, send email to >> clojure+unsubscr...@googlegroups.com >> For more options, visit this group at >> http://groups.google.com/group/clojure?hl=en >> --- >> You received this message because you are subscribed to the Google Groups >> "Clojure" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to clojure+unsubscr...@googlegroups.com. >> For more options, visit https://groups.google.com/d/optout. >> > -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [ANN] Clojure 1.10.0-alpha7
On Thursday, 6 September 2018 15:09:15 UTC+1, Andy Fingerhut wrote: > > > If you have a few minutes to try out the tests in my repo to see if you > get different results than I did, I'd be curious to hear if your results > are different. I'd be more curious to learn of a way to write a unit test > that gives the exception you see with Clojure 1.10.0-alpha7. > > Thanks for your help. I think I've made a mistake somewhere. I use emacs + CIDER and run the tests from there. With 'lein test' I don't see that error, but I do from emacs. So it may be something that's been updated in CIDER rather than clojure itself. I didn't realise they were different. The offending test was in a work project which has been put on hold/abandoned, but every time a new clojure comes out, I test it again to check it still works (ever hopeful it might be reinstated!). So, more had changed than just alpha6 to alpha7 when I tested this time. Does that make sense? Peter -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [ANN] Clojure 1.10.0-alpha7
Thanks for the response. Makes sense. I haven't used CIDER before, and don't plan to try it out just to learn if it has a feature that checks unit tests for problems. If anyone else knows whether CIDER has a feature to do that, I would be a little curious to learn more about it. Thanks, Andy On Thu, Sep 6, 2018 at 8:09 AM Peter Hull wrote: > > On Thursday, 6 September 2018 15:09:15 UTC+1, Andy Fingerhut wrote: >> >> >> If you have a few minutes to try out the tests in my repo to see if you >> get different results than I did, I'd be curious to hear if your results >> are different. I'd be more curious to learn of a way to write a unit test >> that gives the exception you see with Clojure 1.10.0-alpha7. >> >> Thanks for your help. I think I've made a mistake somewhere. I use emacs > + CIDER and run the tests from there. With 'lein test' I don't see that > error, but I do from emacs. So it may be something that's been updated in > CIDER rather than clojure itself. I didn't realise they were different. > The offending test was in a work project which has been put on > hold/abandoned, but every time a new clojure comes out, I test it again to > check it still works (ever hopeful it might be reinstated!). So, more had > changed than just alpha6 to alpha7 when I tested this time. > > Does that make sense? > > Peter > > -- > You received this message because you are subscribed to the Google > Groups "Clojure" group. > To post to this group, send email to clojure@googlegroups.com > Note that posts from new members are moderated - please be patient with > your first post. > To unsubscribe from this group, send email to > clojure+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/clojure?hl=en > --- > You received this message because you are subscribed to the Google Groups > "Clojure" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to clojure+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [ANN] Clojure 1.10.0-alpha7
Doing a little bit more digging, I just did a Google search for: clojure "expects more than one argument" and found this code hit that may be relevant for CIDER users: https://github.com/clojure-emacs/cider-nrepl/blob/master/src/cider/nrepl/middleware/test/extensions.clj#L28 Andy On Thu, Sep 6, 2018 at 8:57 AM Andy Fingerhut wrote: > Thanks for the response. Makes sense. I haven't used CIDER before, and > don't plan to try it out just to learn if it has a feature that checks unit > tests for problems. If anyone else knows whether CIDER has a feature to do > that, I would be a little curious to learn more about it. > > Thanks, > Andy > > On Thu, Sep 6, 2018 at 8:09 AM Peter Hull wrote: > >> >> On Thursday, 6 September 2018 15:09:15 UTC+1, Andy Fingerhut wrote: >>> >>> >>> If you have a few minutes to try out the tests in my repo to see if you >>> get different results than I did, I'd be curious to hear if your results >>> are different. I'd be more curious to learn of a way to write a unit test >>> that gives the exception you see with Clojure 1.10.0-alpha7. >>> >>> Thanks for your help. I think I've made a mistake somewhere. I use emacs >> + CIDER and run the tests from there. With 'lein test' I don't see that >> error, but I do from emacs. So it may be something that's been updated in >> CIDER rather than clojure itself. I didn't realise they were different. >> The offending test was in a work project which has been put on >> hold/abandoned, but every time a new clojure comes out, I test it again to >> check it still works (ever hopeful it might be reinstated!). So, more had >> changed than just alpha6 to alpha7 when I tested this time. >> >> Does that make sense? >> >> Peter >> >> -- >> You received this message because you are subscribed to the Google >> Groups "Clojure" group. >> To post to this group, send email to clojure@googlegroups.com >> Note that posts from new members are moderated - please be patient with >> your first post. >> To unsubscribe from this group, send email to >> clojure+unsubscr...@googlegroups.com >> For more options, visit this group at >> http://groups.google.com/group/clojure?hl=en >> --- >> You received this message because you are subscribed to the Google Groups >> "Clojure" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to clojure+unsubscr...@googlegroups.com. >> For more options, visit https://groups.google.com/d/optout. >> > -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [ANN] Clojure 1.10.0-alpha7
On Thursday, 6 September 2018 19:11:14 UTC+1, Andy Fingerhut wrote: > > Doing a little bit more digging, I just did a Google search for: > > clojure "expects more than one argument" > > Nice one, thanks. I did a similar search but didn't find that - instead a repo called "venantius/ultra" which has the same text in, which I assumed must be a dependency of cider somehow. -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [ANN] Clojure 1.10.0-alpha7
A linter is a good place for a warning that = is used with one apparent argument. Eastwood to the rescue! src/easter/core.clj:6:3: suspicious-expression: = called with 1 args. (= x) always returns true. Perhaps there are misplaced parentheses? Since = (and also < and > ) are handy in conjunction with *apply* to compute the consistency of a whole list of things, it's nice that they tolerate getting 1 argument. I suppose that is their degenerate case. -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
RE: [ANN] Clojure 1.10.0-alpha7
Thank you! We’ve been testing against master-SNAPSHOT all along but we’ve
decided we’ll try to take this to production (probably next week) to give the
new ASM stuff a good run.
(which is a bit slow for us – we normally take alphas to production pretty much
as they appear 😊 )
Sean Corfield -- (970) FOR-SEAN -- (904) 302-SEAN
An Architect's View -- http://corfield.org/
"If you're not annoying somebody, you're not really alive."
-- Margaret Atwood
From: clojure@googlegroups.com on behalf of Stuart
Halloway
Sent: Wednesday, September 5, 2018 5:39:16 AM
To: clojure@googlegroups.com
Subject: [ANN] Clojure 1.10.0-alpha7
deps.edn dependency:
org.clojure/clojure {:mvn/version "1.10.0-alpha7"}
1.10.0-alpha7 includes the following changes since 1.10.0-alpha6:
* Update deps to latest spec.alpha (0.2.176) and core.specs.alpha (0.2.44)
* CLJ-2373 - categorize and
overhaul printing of exception messages at REPL
* CLJ-1279 - report correct
arity count for function arity errors inside macros
* CLJ-2386 - omit ex-info
construction stack frames
* CLJ-2394 - warn in pst that
stack trace for syntax error failed before execution
* CLJ-2396 - omit :in clauses
when printing spec function errors if using default explain printer
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
---
You received this message because you are subscribed to the Google Groups
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
---
You received this message because you are subscribed to the Google Groups
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Just shoot me...: [ANN] Clojure 1.10.0-alpha5
Having posted about our success with testing Alpha 7, I need to ‘fess up about the end result of all this palaver from July: With a bit of instrumentation in our build pipeline it turned out that we were thrashing on heap space in a few places and, for whatever reason, that was causing all the ClassNotFoundException problems. Sigh. I bumped the heap size up in the JVM options for Boot and everything ran flawlessly… …the hint that pushed me in this direction was that, even on Clojure 1.9.0, we _occasionally_ saw problems loading instant18 (which I’d assumed was a weird edge case in Boot’s async pod setup/refresh)… and that started cropping up more often, and then we started seeing the same CFNE problems with 1.9.0 and that WebDriver test when run in a long Boot pipeline… …so clearly the issue WASN’T the new Alpha build: that just happened to push us nearer the heap/GC issue. Sean Corfield -- (970) FOR-SEAN -- (904) 302-SEAN An Architect's View -- http://corfield.org/ "If you're not annoying somebody, you're not really alive." -- Margaret Atwood From: Sean Corfield Sent: Saturday, July 21, 2018 8:22:21 PM To: clojure@googlegroups.com Subject: RE: [ANN] Clojure 1.10.0-alpha5 Things tried so far: * Update JDK to 1.8.0_144 (to match one of our other environments). No effect on the problem (well, I haven’t seem any JVM crashes since!). * Update Boot to 2.8.1. No effect. Ghadi wondered if Boot’s class loading might have changed since 2.7.2 and that might be a root cause. * Change our multi-version testing so we’re only loading Clojure 1.10.0-alpha6 (we were trying both alpha 4 and alpha 6 before). No effect. I wondered if loading Clojure based on two different versions of ASM (even isolated via pods) might cause issues. We can reliably run the Boot task on its own – clj-webdriver loads and all our tests pass as expected. All of our tasks combined up until this point run just fine. All tasks individually run just fine. The only time we see a failure is when we combine the WebDriver-based test task with all the other tasks – and it reliably fails to load some class (usually a clj-webdriver class but on one run it failed to load clojure.tools.logging.impl.Logger) originating from Boot’s pod refresh, preparing to load clj-webdriver, as far as I can tell. I haven’t been able to produce a smaller combination of tasks that exhibits the problem. I will observe that I have _occasionally_ seen CNFEs during pod refresh in the past, when Components are being stopped (and unloaded?) asynchronously, so it may be that this is an intermittent/non-deterministic bug in Boot pods that is exacerbated with Clojure 1.10.0-alpha5 and later? For now we’re staying on Clojure 1.9.0 (and running just our unit tests against both that and master-SNAPSHOT). As far as we can tell, all our apps run fine on Clojure 1.10.0-alpha6 so this seems to just impact our Boot-based build toolchain and we can probably work around that, so we’ll probably switch to 1.10 at some point (before release) so we can test it in production and provide feedback. Sean Corfield -- (970) FOR-SEAN -- (904) 302-SEAN An Architect's View -- http://corfield.org/ "If you're not annoying somebody, you're not really alive." -- Margaret Atwood From: Sean Corfield Sent: Thursday, July 19, 2018 4:55:47 PM To: clojure@googlegroups.com Subject: RE: [ANN] Clojure 1.10.0-alpha5 Progress so far… with Alpha 6. I’ve encountered a number of (random) JVM SEGV fatal errors running our Boot build pipeline and if I don’t hit any of those, I hit an exception like this fairly reliably: https://gist.github.com/seancorfield/f29bdb948a2a533c14a07ff6ffd6548a (the missing class seems to vary from run to run but the exception is always in the same place) It _seems_ to be an interaction between something new in Alpha 5 and Boot’s pod machinery since all of the failures I’m encountering seem to have when Boot is attempting to refresh pods in its pool of pods. We rely heavily on pods to isolate various parts of our build pipeline (since we load in different sets of dependencies for different sets of tests). Ghadi suggested I update my local JDK to a more recent version and try again so that’s next on my list. Narrowing this down is going to be hard: if I run the build pipeline in separate “chunks” – which means less interaction between pods – each chunk always passes. So, overall, no failures from our test suite itself for any of our application components (good). Just random failures within the build tool itself ☹ Sean Corfield -- (970) FOR-SEAN -- (904) 302-SEAN An Architect's View -- http://corfield.org/ "If you're not annoying somebody, you're not really alive." -- Margaret Atwood From: Sean Corfield Sent: Thursday, July 19, 2018 1:08:33 PM To: clojure@googlegroups.com Subject: RE: [ANN] Clojure 1.10.0-alpha5 Yes, which allowed us to actually _try_ to run our build pipeline – so the problems we’re seeing are fallou
