clojure.lang.LazySeq cannot be cast to clojure.lang.IFn

I'm new to Riemann and Clojure. All I want to do is to send email notifications to three email groups when some service's TTL is expired. I created some sort of config file where I store a list of emails: { :email_group_1 ( "fi...@example.com" "sec...@exampl

Re: JDK8

We've been running Oracle JDK8 on 30'ish servers (clj based web api, aggregation/streaming service, cassandra 2.1+, elastic search, etc) without any (noticeable) hiccups for a couple of weeks here. On Thursday, May 7, 2015 at 10:25:13 PM UTC+2, Pierre-Yves Ritschard wrote: > > Hi, > > There

Re: clojure.lang.LazySeq cannot be cast to clojure.lang.IFn

Dunno riemann but I would say that you need a closure here, not an immediate call to notify. The closure will be called when expiration is reached. So use #(notify ...) instead. In your current code notify gets called, return a lazy seq (for) and then the lazy seq is called as a function wh

Re: clojure.lang.LazySeq cannot be cast to clojure.lang.IFn

Looks like the exception is thrown during config parsing. You probably need to enclose the email addresses in a vector [] rather than a list (). Ray. On 8 May 2015 at 08:01, Alexey Astafyev wrote: > I'm new to Riemann and Clojure. All I want to do is to send email > notifications to three email

Re: Clojure needs a web framework with more momentum

I haven't used Luminus since before 2.0, so I guess it may have changed a lot since. At the time, I was disheartened by the amount of code generated. I will take another look when I get time. On Tue, 5 May 2015 at 14:06 Dmitri wrote: > Luminus uses a minimal amount of generated code. It complete

Clarity Keyboard by SwiftKey - Written in Clojure

Hi all, Just thought you might be interested to know that last week we (SwiftKey) released an Android app, written from the ground up in Clojure, which as of this morning has had 65k downloads. It's a keyboard we're using to test UI ideas which didn't fit well with the existing app. We also took t

Re: Clarity Keyboard by SwiftKey - Written in Clojure

Very good news for clojure-android. Keen to hear more. Dave On Friday, 8 May 2015 21:18:50 UTC+10, Adam Clements wrote: > > Hi all, > > Just thought you might be interested to know that last week we (SwiftKey) > released an Android app, written from the ground up in Clojure, which as of > th

Re: Why (defn- ...) but (def ^:private? ...)

Hi Herwig, On Thursday, 7 May 2015 15:36:44 UTC+1, Herwig Hochleitner wrote: > > 2015-05-07 16:12 GMT+02:00 Stig Brautaset >: > >> Is it because the def form can also be ^:dynamic? >> > Hm, cognitect turned it down, because basically "if you go down this road, > why stop with def- ? and before y

Re: Why (defn- ...) but (def ^:private? ...)

Do you have a link to the discussion? Is this really the reasoning? I find it insufficient, because there aren't many defs supporting private : def, defn, defmacro and definline if I am remembering correctly. I am kind of tired of writing def ^:private. def- would really be nice to have. defma

separation of concerns w/o encapsulation

Talk on the list about encapsulation usually comes back to some variation of "you don't need it when you have immutable data structures". But in the long term I'm finding the problem of working w/o encapsulation is not the danger of data being mutated under you. Rather, it's the danger of all th

Re: Why (defn- ...) but (def ^:private? ...)

I am not aware of any JIRA ticket for this, but there could be one lurking there somewhere. Here is a link to a previous discussion about it on this group: https://groups.google.com/d/msg/clojure/r_ym-h53f1E/y1S31QXNhcAJ Andy On Fri, May 8, 2015 at 9:26 AM, Leon Grapenthin wrote: > Do you have

[ANN] Shrubbery 0.2.0, a stubbing, spying, and mocking library for Clojure protocols

Clojure protocols are a great way to encapsulate operations with side effects, but suffer from a lack of general test tooling. Shrubbery provides a small set of basic building blocks for working with them: * stub, which accepts a protocol and a hashmap of functions and returns an implementation w

Re: separation of concerns w/o encapsulation

Avoiding encapsulation doesn't mean that every function needs to act on a huge global data structure. On the contrary, one of the core ideas of Clojure is that we should try to reduce incidental interconnections. What you describe in your example is essentially complexity creep. Ideally, functions

Re: separation of concerns w/o encapsulation

James, are you saying that with such a core.typed annotation for function available in that example, that it would give a warning if available or any of the functions it calls accesses any keys other than :stock and :reserved ? If so, that is quite impressive. Andy On Fri, May 8, 2015 at 10:36 A

Re: separation of concerns w/o encapsulation

On 8 May 2015 at 18:40, Andy Fingerhut wrote: > James, are you saying that with such a core.typed annotation for function > available in that example, that it would give a warning if available or any > of the functions it calls accesses any keys other than :stock and :reserved > ? > Yes and no.

Re: clojure.java.jdbc bug?

BTW, your tone comes across as rather snarky which isn’t going to make people want to assist you. If you have concrete, constructive suggestions to make, and you care enough to create a JIRA account and create a ticket for broader discussion, you’re likely to find your comments taken more serio

Re: Clarity Keyboard by SwiftKey - Written in Clojure

Just tried the keyboard on my old Galaxy Nexus and I have to say that it felt really responsive (prediction works great, too). This really validates Clojure (well Skummet) for Android development, IMO. Congrats on pushing the boundaries and for the writeup around what you've done. I'm curious if

CLJ-703 - 10x compilation time decrease after applying one-line patch, no downsides.

Hi all, This issue has been around for a while without much activity, although a very simple fix is already there: http://dev.clojure.org/jira/browse/CLJ-703 We have a pretty big Clojure project that we compile on machines with slow hard-drives, on CentOS 6. We noticed that compilation had beco

Re: Clojure needs a web framework with more momentum

Sven, I like this idea. Thanks. -Hari On Wednesday, May 6, 2015 at 11:46:35 AM UTC-7, Sven Richter wrote: > > Hi, > > I had a short chat with Dmitri (the owner of luminus) and we both agreed > that this is a good plan. I just don't have much time right now (family > things), but as soon as th

CLJ-703 - 10x compilation time decrease after applying one-line patch, no downsides.

I'm hoping to look at it for the next release. Alex -- 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

ANN: ClojureScript 0.0-3255 - pretty printer & latest Closure Compiler / Library

ClojureScript, the Clojure compiler that emits JavaScript source code. README and source code: https://github.com/clojure/clojurescript Leiningen dependency information: [org.clojure/clojurescript "0.0-3255"] A big thanks goes out to Jonathan Boston and Shaun Lebron for this release. Thanks

Re: ANN: ClojureScript 0.0-3255 - pretty printer & latest Closure Compiler / Library

I forgot to add that with this release there are now AOTed artifacts for ClojureScript and all of its Clojure dependencies. [org.clojure/clojurescript "0.0-3255" :classifier "aot" :exclusions [org.clojure/tools.reader org.clojure/data.json]] [org.clojure/tools.reader "0.9.2" :classifier "aot"] [or

Re: CLJ-703 - 10x compilation time decrease after applying one-line patch, no downsides.

Just to clarify, Alex, since your idea of "next release" might be different than those who aren't following Clojure 1.7 alphas/betas/etc. carefully. Do you mean "hoping to look at it for Clojure 1.8, since Clojure 1.7 is to the point of primarily fixing critical bugs and regressions" ? Andy On F

Re: What is "best practice" regarding transducers

I wouldn’t make any claims about “best practices” but I’ve been playing with transducers in my little project: https://github.com/miner/transmuters I have a blog post about how to “chain” transducers. (Not sure that’s the best term.) Basically, I wanted to use a transducer that might terminat

Re: CLJ-703 - 10x compilation time decrease after applying one-line patch, no downsides.

Yes. On Friday, May 8, 2015 at 3:09:06 PM UTC-5, Andy Fingerhut wrote: > > Just to clarify, Alex, since your idea of "next release" might be > different than those who aren't following Clojure 1.7 alphas/betas/etc. > carefully. > > Do you mean "hoping to look at it for Clojure 1.8, since Clojur

Re: CLJ-703 - 10x compilation time decrease after applying one-line patch, no downsides.

I'm glad to hear that. Thanks! Le vendredi 8 mai 2015 14:23:03 UTC-7, Alex Miller a écrit : > > Yes. > > > On Friday, May 8, 2015 at 3:09:06 PM UTC-5, Andy Fingerhut wrote: >> >> Just to clarify, Alex, since your idea of "next release" might be >> different than those who aren't following Clojure

Re: Clarity Keyboard by SwiftKey - Written in Clojure

Haven't played with j2objc, but have had a play with compiling the core in RoboVM using lein-fruit. The limitations are a bit different on iOS though, for example the 40mb hard limit on ram usage for a keyboard before it is forceably kicked out of memory, and that's around the low end of what we're

Re: ANN: ClojureScript 0.0-2496, cljs.test - a clojure.test port

Here's the commit I used when swapping cljs.test from clojurescript.test: https://github.com/testdouble/clojurescript.csv/commit/ad68052e311df423e245ec4d2a7ee5572b2a3a35 Note the runner.js file line 26 is calling the exported function to run all the tests. On Friday, May 8, 2015 at 12:49:07 AM

[ANN] kibit-helper.el 0.1.1 on melpa.org

If you are in the set of Clojure developers who use Emacs and the Kibit Leiningen plugin, you may be interested in kibit-helper . I started out by submitting a small pull request to Kibit to fix the sample Emacs lisp c

Re: how goeth the STM experiment?

This seems to be true: "I would have to say that the biggest surprise is how little they're needed in Clojure." Run this search on Google: agent send clojure site:github.com The first 5 pages point me to examples from several years ago, or error reports, or unit tests. Nothing substantial or

Re: [ANN] Bocko 0.2.0

Looks like fun. I would change `hlin` to `hline` and `vlin` to `vline`. It's only one more character to type, but much clearer to read. -- 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

Re: [ANN] Bocko 0.2.0

I guess HLIN and VLIN have a historical significance. Still kind of confusing, but I understand now how you arrived at those names. -- 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 t

Re: CLJ-703 - 10x compilation time decrease after applying one-line patch, no downsides.

I'd like to chime in here in support of this, our company has been running a modified clojure build because of this for over a year now. Alex On Friday, May 8, 2015 at 2:12:50 PM UTC-4, Martin Raison wrote: > > Hi all, > > This issue has been around for a while without much activity, although a

Re: CLJ-703 - 10x compilation time decrease after applying one-line patch, no downsides.

I'll just say one more time that the team should really consider doing bug-fix releases in the future. This problem sounds serious enough to be handled as quickly as possible. Clojure 1.6 was released over one year ago, so I'm guessing 1.8 is more than a year away from now. Waiting for major releas

Re: CLJ-703 - 10x compilation time decrease after applying one-line patch, no downsides.

There's a better 'fix'. Run your builds on SSDs or on a memory based file system. With the RAM available these days, any build can be done on a memory based file system. It speeds up every step by a huge factor. Not only compilation. You only need to copy your targets to a 'permanent' place.

Re: CLJ-703 - 10x compilation time decrease after applying one-line patch, no downsides.

Luc Prefontaine writes: > There's a better 'fix'. > Run your builds on SSDs or on a memory based file system. "Performance problems are solved best by throwing more hardware at them." Seriously?! No, I completely agree with Bozhidar in that regular bugfix releases would be a good thing. Cloj

[ANN] Shrubbery 0.2.0, a stubbing, spying, and mocking library for Clojure protocols

This looks neat Brian! People who find this useful may also like a similar lib I wrote that provides mocking tools at a single function level: https://github.com/glenjamin/q -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send