Clojurians Log v2

Hi, i'm trying to use atom and chlorine on Linux Mint. When I run the connect clojure socket repl I'm not getting the host and port popup. Do you have any ideas what I might be doing wrong?

I just updated to Chlorine 0.1.4 on my Windows machine and nothing works. The settings seem partly broken, and none of the commands load at all.

This is the only setting I see

Hmm, I downgraded to 0.1.3 but it still seems broken. Trying 0.1.2.

0.1.2 works just fine on Windows.

With 0.1.3 and 0.1.4, the package descriptor doesn't even have a Settings button.

With 0.1.2, the settings are back

oh, ill try 0.1.2 then

0.1.2 did the trick

:bananadance:

congrats :)

Thanks

my auto-complete and refresh were only working intermittently when I was using clj with socketrepl on Windows e.g.

{:ex #repl-tooling.editor-helpers.Error{:type java.io.FileNotFoundException, :message "Could not locate clojure/tools/namespace/repl__init.class, clojure/tools/namespace/repl.clj or clojure/tools/namespace/repl.cljc on classpath.", :add-data {}, :trace ... }

:aliases {
            :chlorine {:extra-deps {org.clojure/tools.deps.alpha {:mvn/version "0.6.496"}
                                    compliment {:mvn/version "0.3.8"}}}
            :socket {:jvm-opts ["-Dclojure.server.repl={:port,50505,:accept,clojure.core.server/repl}"]}}}

it might be more of a clj question than chlorine 🙂

ah ha! turns out the intermittent nature of my problem was caused by me trying out the nightcode lib, and it loaded tools.deps.alpha and compliment

Strange... I didn't change anything on it on v0.1.3

Maybe problems with the way Atom loads things?

Yeah, v0.1.4 is broken. I'm unpublishing it and will see what's wrong 😞

Interestingly, it all seems to work from source built locally, right? So it seems just the packaging of 0.1.3 / 0.1.4 that is an issue?

Maybe the submodule change broke something in the packaging?

Great, just found the problem... will fix it and see if things start to work again. To solve bugs I'm using a CI to make the release builds, but these last versions silently failed on the release build... but somehow the integration tests on the CI still build 😕

Ouch!

This happens on the release build before publishing the package, but isn't happening on the release build before testing... I'm checking for errors now, hope is something simple to fix

hey, some coworkers and I are trying to get chlorine to work

we are executing the leiningen command in the README, we see this output in the terminal:

$ JVM_OPTS='-Dclojure.server.repl={:port,5555,:accept,clojure.core.server/repl}' lein repl
nREPL server started on port 64114 on host 127.0.0.1 - <nrepl://127.0.0.1:64114>
REPL-y 0.4.3, nREPL 0.6.0
Clojure 1.10.0
OpenJDK 64-Bit Server VM 11.0.2+9
    Docs: (doc function-name-here)
          (find-doc "part-of-name-here")
  Source: (source function-name-here)
 Javadoc: (javadoc java-object-or-class-here)
    Exit: Control+D or (exit) or (quit)
 Results: Stored in vars *1, *2, *3, an exception in *e

chlorine-test.core=&gt;

however, running Connect Clojure Socket REPL seems to do nothing

@lilactown We just found a bug on the two last versions of Chlorine, I'll publish a newer version as soon as I find the error

ah OK! thanks 😄

apm install chlorine@0.1.2 will get you back to a working version @lilactown

sweet, thanks @seancorfield

(I run it from source locally on my Mac, so I didn't hit the problem until I upgraded my Windows laptop from 0.1.2 to 0.1.4 yesterday)

what should I see if it connects successfully?

I'm still not seeing it work with 0.1.2

Can you see the popup that asks for host and port?

Found the problem: different versions of node in different steps of build, and no check for errors before publishing the tag.

Just published version 0.1.5, should fix the issues on 0.1.3 and 0.1.4. Just installed here on a brand new ATOM_HOME and I'm seeing the configs again, and connecting to REPLs

(I just found out that Github is having issues with hooks, and the builds are not being called automatically but anyway. Now, it's working, tested with atom-stable and beta)

Thanks for the fast turnaround @mauricio.szabo! I'll try that on my Windows laptop later today.

@lilactown were you able to make it work?

not currently

I tried upgrading to 0.1.5, I still see the behavior where nothing happens after running Chlorine Connect

It doesn't even open a popup?

nope

I'm contemplating reinstalling Atom to ensure it's not some stale thing happening

I'll upgrade my atom version to the latest one. In the meantime, can you run atom with: ATOM_HOME=/tmp atom /tmp This way you get a "blank" atom without needing to reinstall... then see if it works that way

using the /tmp you pasted, I started Atom and reinstalled Ink and Chlorine. then executed the connect to clojure repl command. I still see no popup 😕

I'm currently using Atom 1.37.0 x64 on macOS

When you execute "connect to clojure REPL" and no popup appears, can you execute again or it disappears from the Atom command palette?

it disappears from the command palette. I have to close and reopen the project so it appears again.

Also, can you open the inspector (I think the keybinding for it is CMD+i or CMD-SHIFT-i) and see if it logs something on the console when you execute the command?

(I'm using Atom 1.37.0, but on Linux. Maybe this is the issue, but I'm not sure why it happens)

I don't see any logs in the chrome devtools inside Atom

only some warnings

[Violation] 'keydown' handler took 396ms
2[Violation] 'keydown' handler took 399ms

No, they aren't. Great, I'll try to figure out something. There are some friends that work with me that use Atom, I'll see if the problem happens on their machines too

OK 😬 thanks for the help!

yes, thanks

I'm very happy with Chlorine atm

Can I ask for something else? When you open Atom and search for Chlorine on plug-ins, can you see the Settings page?

Just an update, MacOSX version isn't working right now. I have no idea why - atom isn't logging anything on console nor on terminal. I'm trying to debug it (but it seems something that only happens with release builds)

Nevermind, just saw here that you can see the settings page, but it still don't connect

yeah 😞