I'm using boot watch with my test runner to have it auto-rerun tests after files are saved, but it progressively gets slower with each run, about 1/3rd of a second each time. Is this expected or any kind of known issue?

@mattly there have been some issues with pods not being disposed properly resulting in a memory leak. What test runner are you using? I think @juhoteperi made boot-alt-test or so which does not use pods

ah, I'm using boot-test

Boot-alt-test uses a pod, but doesn't create a new pod each each test run like boot-test

So it is to be expected that boot-test can be slow with larger projects as it has to recompile even unchanged namespaces each time, but there shouldn't be reason why it gets slower each time

I'm trying to do some simple image resizing using this library, https://github.com/josephwilk/image-resizer.

(ns util.resize
  (:require
    [image-resizer.core :as core]
    [image-resizer.format :as format]
    [ :as io])

(defn myresize []
  (format/as-file
    (core/resize
      (io/file "sketch.png")
      100 100)
    "resized-sketch.png"))

(deftask resize []
  (r/myresize))

java.lang.Thread.run

java.util.concurrent.ThreadPoolExecutor$Worker.run

 java.util.concurrent.ThreadPoolExecutor.runWorker

               java.util.concurrent.FutureTask.run

                                               ...

               clojure.core/binding-conveyor-fn/fn                          core.clj: 1938
                                 boot.core/boot/fn                          core.clj: 1030
                                               ...

                         boot.core/construct-tasks                          core.clj:
  992
                                clojure.core/apply                          core.clj:
  646
                                               ...

                             boot.user/eval6228/fn  boot.user4743533291956162745.clj:
   15
                              util.resize/myresize                        resize.clj:
   15
                         image-resizer.core/resize                          core.clj:
   20
                 image-resizer.resize/resize-fn/fn                        resize.clj:
   35
                 image-resizer.util/buffered-image                          util.clj:
   12
                        javax.imageio.ImageIO.read

javax.imageio.IIOException: Can't read input file!
clojure.lang.ExceptionInfo: Can't read input file!
    file: "C:\\Users\\rigalo\\AppData\\Local\\Temp\\boot.user4743533291956162745.clj"

    line: 37

Hey. I have been looking through the boot docs.. but cannot find what I need. It (should) be pretty simple - so I thought I'd ask here. I would like to specify a dependency and give it an alias within my project. My use case, I have forked a library to fix a bug - and until that is merged back I have to stay with my fork. I do not want to update all of my code to "require" to forked version, id rather make my version accessible using the same name as the original.

@jamesmintram are you talking about the name of the clojure namespace you forked? or the library name? if you forked and have your own library (maven artifact name), there’s nothing to stop you from using the original namespace name

So I forked the repo and published it to clojars under my own account. Then updated the build.boot file to reference the new clojars dependency. So you are saying that should just work?

(Because I haven't made any changes to the code.. yet)

Ok thanks - that makes sense! I think I was confusing the artifact name with the namespaces it exports!

@jamesmintram np, and yup that’s the idea :thumbsup: