Clojurians Log v2

@hlolli also I just fixed the EOF issue

not related to buffer / string

it’s my fault when doing a refactoring a while ago

oh I know

planck - <<< 1 doesn’t produce output

Lumo does

Ok nice, something at least broke it since i initially made the pr. Want to use lumo ad preprocessor in csound so i wanted to use this functionality.

I’ll fix it

Ok noted, sounds like a learningfull task. I look at it, and close my PR if you fixed the EOF error, that was in the end main reason for the PR.

No i mean the only reason

@hlolli yeah just fixed it in https://github.com/anmonteiro/lumo/commit/261b93a2c9e1d1d3f7d2b20482bdf5ba29f4d0d1

Prima

so if I do boot dev, can I then call node target/bundle.js with all the normal parameters in order to emulate a call to lumo binary?

@richiardiandrea yarn dev will set the right options

or npm run dev

ok I see, I was missing target in the classpath let me try that

uhm, no...probably something else, I would like to launch:

node ~/git/lumo/target/bundle.js -c ~/git/lumo/target:$(cat cp):~/git/serverless-cljs-plugin/serverless-cljs-plugin -m serverless-lumo.build --zip-path /home/arichiardi/git/cqrs-cloud/.serverless/cqrs-cloud-event-store.zip --functions '[{:name "cqrs-cloud-event-store-dev-append-event" :invoke cqrs-cloud.event-store/append-event}]' --index true

inside my project dir in order to compile

I get:

(node:20366) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): TypeError: Cannot set property 'user' of undefined
(node:20366) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

@richiardiandrea do you have boot dev running?

yup

maybe it is not finding stuff in node_modules

no that’s not it

can you run that with the built binary?

yep I can

oh

https://github.com/anmonteiro/lumo/blob/master/src/js/cljs.js#L122

^ that main.js is the compiled CLJS bundle

it probably needs to be in the target folder from where you’re running lumo

it is there, but the fact that I am running from another folder messes things up...cwd is not target maybe

yes, that’s what I’m saying

k cool

I’ll fix it

1 sec

@richiardiandrea try master

kk

https://github.com/anmonteiro/lumo/commit/1d5c5e84498648ec7b75cafcfb757aca46e7a041

also you may wanna set a cache path

or it’ll take a little while

works for me now

k trying, yes I set the cache after checking what yarn dev does

the answer is prolly not, but is clojure.tools.trace working for lumo? if not, alternatives?

so, https://github.com/philoskim/debux claims to work with cljs, no idea lumo though

@dominicm thanks will try that!