Hi, any suggestion of open source project for a beginner with some entry level Clojure learner to start?

what is the closest to "`condlet` " ? I'm looking for a mix of cond and when-let . Like

(condlet
 [thing (re-find ...)] (do-stuff1 thing)
 [other-thing (re-find ...)] (other ...)
 default)

how i can compare the value of vector with its previous values for example if I have vector [5 6 4 8] how can I compare the 6 with 5 , 7 with 6 I wanted something like this if value is greater than previous value return red otherwise green like [green green red green] ?

Maybe this will help you?

(partition 2 1 [5 6 4 8])
=> ((5 6) (6 4) (4 8))

Hi, lets say that i get a max values like this

(map 
  (fn [lst] (apply max-key :price lst)) 
  (partition 5  
    [{:name 1 :price 10} 
     {:name 2 :price 10} 
     {:name 3 :price 20} 
     {:name 4 :price 50} 
     {:name 5 :price 40} 
     {:name 6 :price 70} 
     {:name 7 :price 15} 
     {:name 8 :price 20} 
     {:name 9 :price 14} 
     {:name 10 :price 24}])))

({:name 4, :price 50} {:name 6, :price 70})

({:name 1 :price 10 :max 50} {:name 2 :price 10 :max 50} {:name 3 :price 20 :max 50} {:name 4 :price 50 :max 50} {:name 5 :price 40 :max 50}
{:name 6 :price 50 :max 70}  {:name 7 :price 15 :max 70} {:name 8 :price 20 :max 70} {:name 9 :price 14 :max 70} {:name 10 :price 24 :max 70}

My first thought is something like this @zikajk

dev=> (into [] 
 #_=>       (comp (partition-all 5)
 #_=>             (mapcat #(let [max-price (:price (apply max-key :price %))]
 #_=>                        (map merge % (repeat {:max max-price}))))) 
 #_=>       data)
[{:name 1, :price 10, :max 50} {:name 2, :price 10, :max 50} {:name 3, :price 20, :max 50} {:name 4, :price 50, :max 50} {:name 5, :price 40, :max 50} {:name 6, :price 70, :max 70} {:name 7, :price 15, :max 70} {:name 8, :price 20, :max 70} {:name 9, :price 14, :max 70} {:name 10, :price 24, :max 70}]

But I hope someone will suggest something nicer for that nested max/map expression...

How often would you say with-precision is really the answer to Non-terminating decimal expansion; no exact representable decimal result. ? I'm wondering whether the exception is just a symptom of bad design sometimes. Edit: "bad design" as in mixing bigdecimals and doubles when you only need doubles, or something. Sorry if the question doesn't make a lot of sense, I don't understand the issue very well but I've started seeing it more often lately (in code that didn't use to need the with-precision workaround) and that made me wonder.

is there a way to tell if a swap! changed the atom?

use swap-vals! instead - compare the old/new that are returned

forgot about that one, thanks!

or compare-and-set!

A little specific, but something weird happened and I don't understand.. I've been working with https://github.com/clj-jgit/clj-jgit for a few days, interacting with it from my REPL and such. All good. Suddenly I've started getting very heavy log output like this when making calls to it:

2021-11-19T20:14:05.103Z x DEBUG [org.eclipse.jgit.internal.storage.file.FileSnapshot:239] - file=/home/sheluchin/repos/foo/.git/config, create new FileSnapshot: lastRead=2021-11-19 15:14:05.099201000, lastModified=2021-11-18 14:52:20.617262000, size=92, fileKey=(dev=3c,ino=3903529)
2021-11-19T20:14:05.120Z x DEBUG [org.eclipse.jgit.internal.storage.file.FileSnapshot:548] - file=null, size changed from -1 to 124 bytes
2021-11-19T20:14:05.125Z x DEBUG [org.eclipse.jgit.util.SystemReader:389] - loading config FileBasedConfig[/home/sheluchin/.config/jgit/config]

Very likely you don't have any logging setup in your project, so the log output you get is at the whims of whatever logging setup your dependencies bring in

Which can be a tangle, likely you added a new dependency (not logging related) that did this

If you don't proactively setup logging then things like the order of different dependencies in the classpath can alter logging behavior

I don't think so. I didn't add any new deps lately and my project is based on the fulcro-rad-demo, so it has this: https://github.com/fulcrologic/fulcro-rad-demo/blob/develop/src/shared/com/example/lib/logging.cljc Do I need some specific subkeys here maybe? https://github.com/fulcrologic/fulcro-rad-demo/blob/develop/src/shared/config/defaults.edn#L71 Still not sure why it suddenly started happening though :thinking_face:

It isn't going to be any of that

What your are seeing is the default output from an unconfigured java.util.logging

And timbre is a whole other thing

Oh, so I should look at how to set up config for java.util.logging?

That would be one way

My preference for complex projects these days is to setup up log4j2 and redirect all the other java logging to it

If you haven't encountered the complexities of java logging before, you can sort of split logging into a top half and bottom half. The top half is the API that programs call with log messages, the bottom half actually outputs the log messages somewhere.

A lot of logging libraries provide both a top and bottom half, and some libraries, like the clojure specific tools.logging is just the top half

And most logging libraries provide shims that act like the top half of other libraries, but direct messages to their own bottom half

https://github.com/fulcrologic/fulcro-rad-demo/blob/28a925f24a2b9237726f0e1f2b0bb936394a8e63/deps.edn I'm wondering if those logging deps impact what you're saying.

Timbre is this weird kind of attempt to paper over the complexities of logging, while also doing some clojure specific stuff, and I don't really care for it, and avoid using it, so I can't speak too much to how it is effecting all of that

The logging stuff there appears to be trying to pipe the top half of a lot of java logging libraries to the log4j bottom half

My mistake, it is piping it to slf4j bottom half

Mmm, that output may not actually be from java.util.logging, but from slf4j, so configuring slf4j, possibly through timbre may be the thing

Heh, this sounds like a job I shouldn't be doing last thing on a Friday 🙂

Thanks @hiredman, that gives me a lot to look into. I'll leave it to the next morning to tackle this. A little odd that is just randomly started happening, but there must have been some event in my workflow that triggered the change and I just don't remember.

Ah, figured it out. Totally my fault. The function which starts the HTTP server and populates the DB also inits the config, and I wrongly assumed since I was only interacting with git/local filesystem, I didn't need any of that... on this particular run. I attribute it to fatigue 😛 But I appreciate your explanation very much nonetheless. I'm not that familiar with java logging complexities, so this top/bottom split gives me something to look into before I inevitably do encounter it.