Fork me on GitHub
#calva
<
2019-06-18
>
minhnhat10bk04:06:33

I think repl window is limited, so my workflow is using external terminal to run nrepl, and connect repl window to nrepl instead of jack-in

pez06:06:44

@minhnhat10bk: You can also jack-in and then connect an internal or external terminal with something like lein repl :connect. That way you won't need to keep track of the Calva dependencies.

linkerfelix12:06:13

@pez I found that Ctrl+Alt+C, Enter works well. In my scenario, I had the user ns in dev resources use another ns dev-data in dev resources which wasn't reloaded when I did (use 'user :reload) in the REPL window but doing Ctrl+Alt+C, Enter in dev_data.clj does reload that ns

linkerfelix12:06:06

Well... just tried to reproduce this... (use 'user :reload) seems to work just fine now. No idea what was going on...

linkerfelix12:06:37

:man-shrugging:

pez14:06:26

¯\(ツ)

hoppy18:06:49

@pez, I'm getting a bit of a regression on 2.0.14. I'm not sure I can describe the symptoms adequatly. The web-app part of it is suddenly unable to find resources that are plainly there. When I revert to 2.0.13, the problem disappears.

pez18:06:19

What resources? What is the web app, in this context?

hoppy18:06:50

stuff it's trying to pull through the clj server

hoppy18:06:23

plain http stuff

pez18:06:41

Interesting. Can you see which commits are between 13 and 14?

hoppy19:06:04

I can dig in and maybe even bisect it later. Right now, a bit in the fray, and just wanted to alert/jog because .14 for me is being toxic

pez19:06:44

There is a risk it is the bundling. But I need much more detailed and exact descriptions of what is going wrong.

hoppy19:06:38

understood

pez20:06:46

Can you try this one, @hoppy? I am hoping it will not fix the problem, but also realising that it might…

hoppy20:06:47

stand by for 4 min recompile (make clean build)

pez20:06:25

I really would like to be able to keep bundling the extension. But I can’t see what else could be causing it to get toxic.

hoppy20:06:05

that one works

pez20:06:22

Damn it.

hoppy20:06:46

I'll load .14 and get you some chrome babble

pez20:06:28

Thanks. Maybe that can throw some light on this.

hoppy20:06:41

you won't like this. I reverted to .14 and it's working now

hoppy20:06:07

I'll run with it for a while, and see if it reappears.

hoppy20:06:48

I'm pretty sure I'm not completely nutz, but the evidence contradicts that.

pez20:06:52

It was .15 that was problematic, right?

hoppy20:06:07

it was .14, I just took the update from vscode

hoppy20:06:23

not seeing a 15 in there

pez20:06:28

I see. Then I just skipped a version. 😃

hoppy20:06:12

trying to sandbag those agile velocity numbers....

pez20:06:05

So, .14 works sometimes… I really would like that it was some crazy fluke, but I have never seen such hopes being delivered by the software gods.

hoppy21:06:07

only when you depend on it, and It's revoked when you need it most.