Ok, got it. It was an oversight on my part. From a config file, I was
pulling in *myns/myfn*. But this is just a symbol. I needed to resolve it,
and deref the var that it pointed to. So now the below works. Tricky, but I
should have caught it earlier.
(apply @(resolve *afn*) params)
Thanks guy
;> Thanks
>>>>>
>>>>> Tim Washington
>>>>> Interruptsoftware.com <http://interruptsoftware.com>
>>>>>
>>>>>
>>>>> On Fri, Jan 3, 2014 at 2:39 PM, Jason Wolfe wrote:
>>
t;>>>
>>>>
>>>> On Fri, Jan 3, 2014 at 2:39 PM, Jason Wolfe wrote:
>>>>
>>>>> Thanks for the report.
>>>>>
>>>>> Schema fns inside of go blocks seem to work fine for me. It seems
>>>>> likely that you
blocks seem to work fine for me. It seems
>>>> likely that you're seeing an exception inside the go block, which is
>>>> swallowed by default:
>>>>
>>>> user> (clojure.core.async/go (println "A"))
>>>> #>>
ide of go blocks seem to work fine for me. It seems
>>>> likely that you're seeing an exception inside the go block, which is
>>>> swallowed by default:
>>>>
>>>> user> (clojure.core.async/go (println "A"))
>>>> #>&
ntln "A"))
>>> #>> 46ae10a6>
>>> A
>>>
>>> user> (clojure.core.async/go (throw (RuntimeException.)) (println "A"))
>>> #>> 427c78c1>
>>>
>>> Would you mind wrapping the body of your go block in a tr
eException.)) (println "A"))
>>> #>> 427c78c1>
>>>
>>> Would you mind wrapping the body of your go block in a try/catch and
>>> printing the exception stack trace, or posting a gist that demonstrates the
>>> issue so I can look into it f
; clojure.core.async.impl.channels.ManyToManyChannel@427c78c1>
>>
>> Would you mind wrapping the body of your go block in a try/catch and
>> printing the exception stack trace, or posting a gist that demonstrates the
>> issue so I can look into it further?
>>
>>
eption.)) (println "A"))
>>> #>> clojure.core.async.impl.channels.ManyToManyChannel@427c78c1>
>>>
>>> Would you mind wrapping the body of your go block in a try/catch and
>>> printing the exception stack trace, or posting a gist that demonst
go (throw (RuntimeException.)) (println "A"))
>> #> clojure.core.async.impl.channels.ManyToManyChannel@427c78c1>
>>
>> Would you mind wrapping the body of your go block in a try/catch and
>> printing the exception stack trace, or posting a gist that demonstrate
ould you mind wrapping the body of your go block in a try/catch and
> printing the exception stack trace, or posting a gist that demonstrates the
> issue so I can look into it further?
>
> Thanks!
>
>
> On Friday, January 3, 2014 10:21:16 AM UTC-8, frye wrote:
>
>> Forw
C-8, frye wrote:
>
> Forwarding...
>
> -- Forwarded message --
> From: Timothy Washington >
> Date: Fri, Jan 3, 2014 at 1:17 PM
> Subject: Re: Core.async, Rules for passing clojure vals to go block
> To: Shaun Gilchrist >
>
>
> I'm using Prismatic's Sche
Forwarding...
-- Forwarded message --
From: Timothy Washington
Date: Fri, Jan 3, 2014 at 1:17 PM
Subject: Re: Core.async, Rules for passing clojure vals to go block
To: Shaun Gilchrist
I'm using Prismatic's Schema in my code base. Now, it looks like defining
some
Hi there,
For core.async, what are the rules for, *i)* having vals from a function
closure, *ii)* passed into a go block. In the example below, I cannot pass
in the system-atom to the handle function. The call will just die silently,
without throwing any exception. Instead, I have to pass in a nil
14 matches
Mail list logo
