Yes that's easy to do

Are you using lein or deps?

Lein

Ok, with lein it's a bit harder, but still doable

You can follow this answer: https://stackoverflow.com/a/41619046/172272

Or alternatively the one after it: https://stackoverflow.com/a/41620582/172272

Ahhh thanks!

With deps it's much easier though, because you can just define another folder as a dependency directly using: https://clojure.org/guides/deps_and_cli#_using_local_libraries Where you can just define the dependency as: {:deps {time-lib/time-lib {:local/root "../time-lib"}}}

you mean the same container? nginx + your application?

[docker-container [nginx [ jar-app]]]

so you want nginx to run your application?

yeah

nginx is a proxy server, not sure I ever saw it used as an application server

Yeah, that is not nginx’s task.

It depends more on your full deployment environment how you want to orchestrate/load balance/reverse proxy things.

We use nginx to serve some static content but other requests are just routed to a standalone jar running an embedded http server

(jetty is a solid choice for that)

Yeah, whatever your httpring server of choice uses will be fine. Jetty, Netty, Undertow, something's underneath, just lean on that.

Yeah I’m using aleph which I believe is built on netty

there is a version of nginx that can host clojure inside it, but outside of weird performance optimization (that you probably don't need) it's just a curiousity

i used nginx clojure in production to stream and cache files from a private s3 bucket with custom authorization checks and auditing implemented in clojure 😆

> debuggable You'd have to attach a debugger first and use a breakpoint - either at a specific location if you know it, or triggered by a specific exception. > clickable That depends on your development environment. E.g. in Cursive stack traces printed with .printStackTrace are clickable.

the stack trace printed by clojure.test.do-report doesn't seem to be clickable in cider

I think it would be if clojure.test would re-throw the error (depending on some configuration variable of course)

cider instruments clojure.test to make it "clickable"

what do I have to do to make it clickable in cider? I'm calling the test function simply from the cider repl

(ns integration.test-test
  (:require [clojure.test :refer [deftest]]))

(deftest something
  (throw (Exception. "test")))

I think that it just needs to get thrown back up to cider's test runner

how are you running the tests?

I'm calling it directly from the repl inside cider

I just found a menu item Cider Interactions -> Test -> Run Test

which will run 1 test, and let me navigate the failure.

yeah ... I tend to hit C-c C-t C-n to run all the tests in a namespace

but there are a bunch of shortcuts to get cider to run your tests, which will use cider's test reporting mechanism

Judging by the implementation, there are cases where msg is evaluated if the test passes.

😞

is there a clever way to evoke a side effect only if the test fails?

is returns a boolean and if-not only evaluates its branches when needed

you could create a macro wrapper around these replicating is but ensuring the msg arg isn't evaluated unless the test fails

if you only need one branch, I think or is clearer: (or (is ....) (some side effect))

I think the or above is pretty clean. If you need some more firepower you can make your own do-report that does something on failures. Since collecting these failures is a side effect of the actual testing suite

oh right, clojure.test has that tooling

what pprint does:

org.noisesmith.expecting=> (def bad-calculations {:a (future (/ 1 0)) :b (future (+ "hello" "world")) :c 42})
#'org.noisesmith.expecting/bad-calculations
org.noisesmith.expecting=> (pprint bad-calculations)
Execution error (ArithmeticException) at org.noisesmith.expecting/fn (a2ad38d8de6e530d571a2f0e206a3214c8d6fac1c305fe67d8ab4bf380e724df-init.clj:1).
Divide by zero
{:a

the raw value:

org.noisesmith.expecting=> bad-calculations
{:a #object[clojure.core$future_call$reify__8454 0x447aea69 {:status :failed, :val #error {
 :cause "Divide by zero"
 :via
 [{:type java.util.concurrent.ExecutionException
   :message "java.lang.ArithmeticException: Divide by zero"
   :at [java.util.concurrent.FutureTask report "FutureTask.java" 122]}
  {:type java.lang.ArithmeticException
   :message "Divide by zero"
   :at [clojure.lang.Numbers divide "Numbers.java" 188]}]
 :trace
 [[clojure.lang.Numbers divide "Numbers.java" 188]
  [clojure.lang.Numbers divide "Numbers.java" 3901]
  [org.noisesmith.expecting$fn__1769 invokeStatic "a2ad38d8de6e530d571a2f0e206a3214c8d6fac1c305fe67d8ab4bf380e724df-init.clj" 1]
  [org.noisesmith.expecting$fn__1769 invoke "a2ad38d8de6e530d571a2f0e206a3214c8d6fac1c305fe67d8ab4bf380e724df-init.clj" 1]
  [clojure.core$binding_conveyor_fn$fn__5754 invoke "core.clj" 2030]
  [clojure.lang.AFn call "AFn.java" 18]
  [java.util.concurrent.FutureTask run "FutureTask.java" 264]
  [java.util.concurrent.ThreadPoolExecutor runWorker "ThreadPoolExecutor.java" 1128]
  [java.util.concurrent.ThreadPoolExecutor$Worker run "ThreadPoolExecutor.java" 628]
  [java.lang.Thread run "Thread.java" 829]]}}], :b #object[clojure.core$future_call$reify__8454 0x43d12484 {:status :failed, :val #error {
 :cause "class java.lang.String cannot be cast to class java.lang.Number (java.lang.String and java.lang.Number are in module java.base of loader 'bootstrap')"
 :via
 [{:type java.util.concurrent.ExecutionException
   :message "java.lang.ClassCastException: class java.lang.String cannot be cast to class java.lang.Number (java.lang.String and java.lang.Number are in module java.base of loader 'bootstrap')"
   :at [java.util.concurrent.FutureTask report "FutureTask.java" 122]}
  {:type java.lang.ClassCastException
   :message "class java.lang.String cannot be cast to class java.lang.Number (java.lang.String and java.lang.Number are in module java.base of loader 'bootstrap')"
   :at [clojure.lang.Numbers add "Numbers.java" 153]}]
 :trace
 [[clojure.lang.Numbers add "Numbers.java" 153]
  [org.noisesmith.expecting$fn__1771 invokeStatic "a2ad38d8de6e530d571a2f0e206a3214c8d6fac1c305fe67d8ab4bf380e724df-init.clj" 1]
  [org.noisesmith.expecting$fn__1771 invoke "a2ad38d8de6e530d571a2f0e206a3214c8d6fac1c305fe67d8ab4bf380e724df-init.clj" 1]
  [clojure.core$binding_conveyor_fn$fn__5754 invoke "core.clj" 2030]
  [clojure.lang.AFn call "AFn.java" 18]
  [java.util.concurrent.FutureTask run "FutureTask.java" 264]
  [java.util.concurrent.ThreadPoolExecutor runWorker "ThreadPoolExecutor.java" 1128]
  [java.util.concurrent.ThreadPoolExecutor$Worker run "ThreadPoolExecutor.java" 628]
  [java.lang.Thread run "Thread.java" 829]]}}], :c 42}

note that it's all data, pprint is being "helpful" in a way that obscures data now that we have good exception printing in core

though the newlines in the exception printer act slightly odd when inline inside a map

About initImGui: https://clojuredocs.org/clojure.core/proxy-super

thanks!

@UGH9KH1DF, just curious why you're trying ImGui over some of the other options like seesaw, cljfx, skija, and quil. I've been working on my own desktop UI clojure lib and am interested in knowing what potential users are looking for.

Well, it looks very complete (e.g. I need to do lots of graphs & tables and it's all built in) and friends told me about it, but I haven't done lots of comparison with what's available I admit

isn't quil mostly for procedural art?

that's quil's most popular use case, but it can be used for other stuff. I wasn't sure what you were building

ImGui is pretty neat

it looks like it, and I hope I'll manage to write bindings for it, but I'm not off to a good start 😄

nb. this shouldn't be an issue for a GUI lib (they don't usually thread their UI code) but proxy-super is not thread safe

not ideal. There is another java bindings to imgui, maybe I'll have best luck with it

Hi, Chlorine author here. Indeed, there's no way. What you may be able to do is have a script to disconnect from one REPL, and connect to the other.

There's a little documentation on how to do this here: https://github.com/mauricioszabo/atom-chlorine/blob/master/docs/extending.md#extending-from-atoms-initcoffee-or-initjs

The only trouble I see is that you won't explicitly have a command to disconnect the REPL, but you also can handle something with:

// Disconnect if something exists
atom.commands.dispatch(atom.views.getView(atom.workspace.getActiveTextEditor()), 'chlorine:disconnect')
setTimeout(() => {
  //connect to a new REPL
}, 200) // a time to allow REPL disconnection

and what’s the best way to have a cljs + clj repl workflow on vscode?

@UFPEDL1LY Hiccup accepts any properties that HTML accepts. So you can do [:div {:id "cool-element, :class "bg-yellow-500"}] . The whole dot-separated, keyword class thing is just a shorthand.

@UFPEDL1LY you can also programmatically create collections (with optional nil values) and pass it to :class https://cljdoc.org/d/reagent/reagent/1.1.0/doc/tutorials/using-hiccup-to-describe-html#special-interpretation-of-class-attribute

@U05476190 is this particular to reagent? It doesn’t work for me with pure hiccup. I am not using clojurescript at all.

I didn't realize this was reagent specific. [0] I guess you'd have to write a helper function to do something similar:

[:div {:class (classes ["a-class" (when active? "active") "b-class"])}]