Downloaded latest boot.exe. Running boot dev and changing a file gives me this huge list of "Couldn't delete" exceptions I updated boot and deleted the ~/.boot/cache and properties files, still same issue. I have BOOT_HOME set in win7 variables. My boot -V

#
#Thu Nov 19 12:08:46 CET 2015
BOOT_CLOJURE_NAME=org.clojure/clojure
BOOT_VERSION=2.4.2
BOOT_CLOJURE_VERSION=1.7.0
#App version: 2.4.2

@xifi the output shows clojure 1.7.0

@martinklepsch: yeah the boot.properties file from the lein template has that set up. I'll try and change it to 1.8.0-RC2

#
#Thu Nov 19 12:37:15 CET 2015
BOOT_CLOJURE_NAME=org.clojure/clojure
BOOT_VERSION=2.4.2
BOOT_CLOJURE_VERSION=1.8.0-RC2
#App version: 2.4.2

@martinklepsch: ☝️

Can you paste a complete exception?

working on it, pc really slow

@martinklepsch: https://www.refheap.com/111857

@xifi: do you have a root dir “home”? is the project on the same disk as $BOOT_HOME?

@martinklepsch: I only have one disk, C:\. The first part I don't understand I do have an env variable HOME set to C:\home but some applications honor that and some don't. Here it decides to use my user's path C:\Users\IBM_ADMIN as the base

since the user path was the one used by default I added an env var for BOOT_HOME pointing to the same place, C:\Users\IBM_ADMIN

C:\Users\IBM_ADMIN\.boot\cache\tmp\home\code\cljs\address-book\5xw\11lgcg\index.html the bit behind tmp is from a root dir, that’s why I asked.

I see. My code lives in C:\home\code\cljs\address-book\

That said I don’t know what’s going on, there are some issues with cache dir and project dir not being on the same disk but that does not seem applicable in your case

I’d suggest creating a minimal case and opening an issue on Github

I used to have this issue before cljs had a file handle leak fix

after the fix it worked fine, now coming back after a month or two I have the same issue :O

The issue also occurs with files outside of cljs’ control like index.html so it seems more like a boot issue to me

have you tried with boot v2.3.0? maybe there’s a windows regression in 2.4.2?

will check

nope, happens on 2.3.0 as well

maybe try with 2.2.0 as well just to be sure

tracking down the change you made in your project that made this issue reappear would be most helpful

@martinklepsch: testing now. I didn't make any change to a project, I just started going through the hoplon tutorial as a refresher

same with 2.2.0, tried both clojure 1.7.0 and 1.8.0-RC2

Anyone have a working setup for using Expectations with Boot?

btw, ppl, have u read the "What Software is Made Of" article? http://siderea.livejournal.com/1241996.html?format=light im curious what do u think...

I'm confused about how to write a filter for the boot-test task

Am I supposed to be passing anonymous functions to the :filter flag, or just function names?

@bsima: seems you’re supposed to pass anon fns

¯\(ツ)/¯

the source is rather hard to decipher https://github.com/adzerk-oss/boot-test/blob/master/src/adzerk/boot_test.clj#L58-L61

I think that is inlining the filter functions you provide into (fn [%] (and ...), then wrapping that lambda in test-ns* with a partial, then mapping that over the collection of namespaces

(map (partial test-ns* (fn [%] (and my-filters))) namespaces) where my-filters are the filter functions you provide, and namespaces is the seq of namespaces that boot can find

Tried without the #?

@bsima: ^

yeah, didn't work

boot test -f '(println %) just hangs, I'm not sure why

with a single quote?

yeah

I guess your shell waits for end of string?

oh duh lol

try boot test -f (println %)

admittedly that API is strange and should probably be changed to something similar to this: https://github.com/hashobject/perun/blob/master/src/io/perun.clj#L262

I tried that too. See above snippet I posted, I just get back "unable to resolve symbol"

I mean, the current api is really lispy and (I think) lets you chain filters together, but I just need a few examples to figure out how to use it

@alqvist: just stumbled upon this by accident: https://github.com/upgradingdave/upgradingdave-boot/blob/cb3a0d59477ead3cab5f0e3bfd2b5153f0afd4bc/src/upgradingdave/boot_expect.clj

@martinklepsch, @alqvist I’ve been using that expect boot task on a side project and it’s a little rough but gets the job done for me at least if you have any trouble with it, please let me know

This is weird: taking a cue from the upgradingdave-boot readme, I tried boot test -f "(= \"test.profiler\" %)". That printed out the names of all my namespaces, but ran zero tests

I was trying to run just the test.profiler namespace

did you somehow still have the previous println filter function?

nope

this is my entire boot file:

i'm using it on top of lein

i'll file an issue and get back to this later. gotta do some real work ¯\(ツ)/¯

hold up

I think I got this to work boot test -f "(re-matcher #\".*test.*\" (str %))"

that should run the tests on any namespace with "test" in its name

the thing is, the test runner still prints the names of namespaces that it isn't testing

does anybody have a public project that uses tailrecursion/clojure-adapter-servlet or https://github.com/adzerk-oss/boot-beanstalk?

I'm having trouble configuring the war

@bensu: what are you deploying to?

Elastic beanstalk, "64bit Amazon Linux 2015.09 v2.0.4 running Tomcat 7 Java 7"

but I wouldn't have a problem changing the image

so i think what you want is a combination of the web, uber, and war tasks

that's what we tend to do now, and then use the aws cli to deploy it

yeah, I'm using all of them (comp (build) (web) (uber) (war))

with build being the frontend part

is there a reason not to use the beanstalk task?