This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-03-08
Channels
- # bangalore-clj (5)
- # beginners (6)
- # boot (66)
- # cider (48)
- # cljsrn (14)
- # clojure (699)
- # clojure-austin (2)
- # clojure-berlin (1)
- # clojure-boston (5)
- # clojure-dev (3)
- # clojure-india (7)
- # clojure-italy (24)
- # clojure-nl (5)
- # clojure-russia (33)
- # clojure-spec (30)
- # clojure-uk (64)
- # clojure-ukraine (22)
- # clojurescript (123)
- # clojurewest (1)
- # cursive (18)
- # datascript (44)
- # datomic (12)
- # dirac (46)
- # figwheel (1)
- # gsoc (5)
- # hoplon (6)
- # immutant (29)
- # instaparse (1)
- # juxt (26)
- # lein-figwheel (5)
- # leiningen (4)
- # luminus (8)
- # mount (56)
- # off-topic (60)
- # om (67)
- # om-next (1)
- # onyx (8)
- # proton (28)
- # re-frame (125)
- # ring (3)
- # ring-swagger (3)
- # specter (22)
- # testing (2)
- # unrepl (1)
- # untangled (91)
@chancerussell can you try with 2.7.1 please?
hey all, wondering if anyone happens to be using protocol buffers in a boot project, and if so how do you depend on the auto-generated .java code?
is there an equivalent to lein mixed projects? https://github.com/technomancy/leiningen/blob/master/doc/MIXED_PROJECTS.md
@micha will give it a try in the morning and let you know. Thanks!
is there a way to solve a transitive dependency conflict in a boot project with two different system
tasks? currently I'm loading each of the systems at the top level in boot, wasn't able to find a better way
@skynet Not quite sure what you're asking but it sounds like something pods can help address, since you can manage the dependencies separately inside each pod...?
is there an equivalent for https://github.com/tobyhede/lein-git-deps in boot?
@seancorfield I think that's right, do you have an example of using pods to manage dependencies like that?
more details on what I'm doing, right now my build.boot
looks like:
(require '[my.ns1 :refer [my-sys1] '[my.ns2 :refer [my-sys2])
(deftask sys1 [] (comp (watch) (system :sys #'my-sys1)))
(deftask sys2 [] (comp (watch) (system :sys #'my-sys2)))
but now I need them to have different dependencies. It seems like I need to wrap them in pods, but I'm not sure how@skynet I don’t think you can do that “just like that"
What you can do is create multiple pods that run those systems. If you want to use the system
task however you’d need to run two boot pipelines in parallel to get the isolation you want.
I just want boot sys1
and boot sys2
to work in different terminals for example, but they have to have different dependency sets
ah! @skynet in that case: you probably now have a set-env! call with all your dependencies top-level right now — you’ll need to move that into a task, say env1
and env2
and then you can define sys1
like this (deftask sys1 [] (comp (env1) (watch) (system :sys #‘my-sys1)))
here’s some documentation on how to set dependencies from inside a task: https://github.com/boot-clj/boot/wiki/Boot-for-Leiningen-Users#profiles-middleware
a word of warning: multiple subsequent tasks to set-env!
might result in a different combination of versions than as if you call set-env!
only once. To keep things predictable you should try to only have one set-env! :dependencies
call
I've created a boot issue on Microsoft / Bash on Windows: https://github.com/Microsoft/BashOnWindows/issues/1760
@micha bumping version to 2.7.1 solved my symlink issue. Will try that first next time! Thanks 🙂
@chancerussell awesome
Awesome you folks have merged some PR. I know that you don't like it, but are changes in 2.7.2-SNAPSHOT
by any chance?
or -alpha1
? 🙂
@laforge49 That’s an old build of Windows 10. I think you’ll find it’s been fixed in the latest version. I run Boot on Windows 10 15046 with no problems.
Never mind I see there are more PRs left to merge 😀
@laforge49 Yeah, the error you reported is one I reported in August 2016 and that’s definitely been fixed. They also fixed a subsequent error (about processes not spawning due to memory allocation issues). You’ll need to consider joining the Insider program and get Fast Ring builds if you want the fix “sooner” rather than later.
Thanks @seancorfield. I've closed that issue and joined insider. Having only one machine, I think I'll wait for the creator release... next month?
Not sure when the public release of that will be. I got the creator release a while back. Lots of good updates since the anniversary release (which introduced WSL / Bash on Windows).
I can run my entire Mac/Linux DEV stack on WSL* now, after a bit of a shaky start with JVM-powered stuff. *Technically, on a combination of Windows 10 native and WSL.
That's good to hear, Sean! I'm looking forward to using wsl, but don't have a pressing need. 🙂
I’m writing a packaging task that needs to operate on the whole output fileset, and it needs to present the current output files to an external (`dosh`) call as a directory. Anyone know of a clean pattern for doing this?
Obviously there isn’t one directory within the cache dirs that underly the file set that I could point the external program to
Wondering if I have a better option than creating a tmp directory and copying all of the files from a call to output-files
into it
Ahhh, perfect
So simple but I wouldn’t have thought of it
@micha you are a helpful person 🙂
Have people tested the latest Boot-cljs 2.0.0-SNAPSHOT? After the latest changes it finally works with all my work projects so I'll be releasing it soon if no one reports new problems
juhoteperi: is the changelog up to date? support for :output-to, :output-dir, and :modules?
output-to and output-dir changes are not included
Is there something wrong with :modules
I don't recall any open issue with that
sorry, not yet sure. tried using this morning and had problems, but that may be due to my output-x patch. should :modules work?
Will give it a shot tomorrow and report back
@U0LGCREMU Yes, modules should be supported since 1.7.228-0: https://github.com/boot-clj/boot-cljs/pull/114
@U0LGCREMU Also, make a PR from your output-to patch, else I will re-implement it 🙂
ok, I need a little help with git here. I cleaned up my patch, added, commited, and pushed, thinking I was pushing to my fork. but i see my changes in the main repo: https://github.com/boot-clj/boot-cljs/compare/master…mobileink:outputs-fix - is that supposed to happen?
I’m not sure about the etiquette - in my fork it looks like i should click on “Compare & pull request” . but I see kinda sorta the same thing in the boot-cljs repo. confused.
also, just created an issue ticket, just for the record. some way to link the PR to the issue?
using boot-cljs 2.0.0-SNAPSHOT since two weeks and haven’t run into any issues. that said, the project just migrated from lein to boot, so we never used boot-cljs 1.x
I know there are many open issues but I'd like to get this version out before starting fixing those
(So I'm mostly asking about regressions related to new changes)
has anyone ever used boot.util/sh
or boot.util/dosh
on windows (with or without WSL)?
boot.user=> (sh "ls")
java.io.IOException: Cannot run program "ls": error=12, Cannot allocate memory
java.io.IOException: error=12, Cannot allocate memory
get the above when I try in WSL
boot.user=> (sh "ls")
IOException CreateProcess error=2, The system cannot find the file specified java.lang.ProcessImpl.create (:-2)
get that one when I try in vanilla boot for Windows