Thanks for the confirmation, Alex. Ticket
filedhttp://dev.clojure.org/jira/browse/CLJ-1260.
:)
Aaron, as shown in the test case attached to the ticket, I'm calling the
Clojure library from Java code, so I use the Agent.dispatch() method. The
project where this issue was found is attempting
Hi,
Am Donnerstag, 12. September 2013 11:11:36 UTC+2 schrieb Brandon Ibach:
Aaron, as shown in the test case attached to the ticket, I'm calling the
Clojure library from Java code, so I use the Agent.dispatch() method. The
project where this issue was found is attempting to use Clojure's
I have found what appears to be a bug in LockingTransaction, albeit one
that probably wouldn't occur often. But, I suppose that's a given for a
previously undiscovered problem in oft-used code that hasn't changed for
some while. :)
I'm using the Clojure 1.4 library strictly from Java code and
I have not gone to look at the code but the description certainly sounds
like a recipe for a bug.
If you can a) create a reproducible case and b) check that it happens on
1.5 as well we would greatly appreciate a ticket:
Create a jira account
-
On Wed, Sep 11, 2013 at 2:47 AM, Brandon Ibach brandon.l.ib...@gmail.comwrote:
I have found what appears to be a bug in LockingTransaction, albeit one
that probably wouldn't occur often. But, I suppose that's a given for a
previously undiscovered problem in oft-used code that hasn't changed
Hi,
without having a clear solution and without pinpointing to the exact issue,
I remember seeing this before. Also in unit tests from Java. The person
back then came up with the following solution.
He created a class from Clojure.
(ns your.app.CljApi
(:gen-class))
(defn -init [])
And
