Fork me on GitHub
#clj-kondo
<
2019-07-31
>
robertfrederickwarner18:07:34

So up until now I've been using clj-kondo via spacemacs integration, and that's been working great. I just tried running from the command line, so that I could get a full-project check, and I'm running into issues running on the VM that my project lives on. It runs fine locally (i.e., directly on my mac host), but when I run in the vm I get lots of "file does not exist" warnings, and it doesn't seem to see my .clj-kondo directory with config/cache. Are there any known quirks of running in a VM, or have I just run into some peculiarity of our setup?

borkdude18:07:01

clj-kondo is tested with linux and Mac in CI, so it's likely an issue with your setup

borkdude18:07:25

maybe a permission issue

borkdude18:07:38

although "not exists" usually means it really doesn't exist

borkdude18:07:50

what OS is your VM running, linux?

borkdude18:07:01

^ @robertfrederickwarner

robertfrederickwarner18:07:41

Yup, ubuntu 18.04.02

robertfrederickwarner18:07:31

Thanks, I just wanted to check if there was anything known before I started my dig. I had taken a look through the open issues but hadn't spotted anything seemingly related.

borkdude18:07:58

I'm just working on a feature that does this: $ clj -A:clj-kondo --lint foo foo:0:0: error: file does not exist linting took 11ms, errors: 1, warnings: 0 $ clj -A:clj-kondo --lint foo --config '{:output {:canonical-paths true}}' /Users/borkdude/Dropbox/dev/clojure/clj-kondo/foo:0:0: error: file does not exist linting took 9ms, errors: 1, warnings: 0

borkdude18:07:06

maybe that would be helpful to find your error?

borkdude18:07:04

ok, linux binary coming up

robertfrederickwarner18:07:40

excellent, thanks 🙂

borkdude18:07:09

I was just about to push this release out, but now I've got a tester, how wonderful

robertfrederickwarner18:07:48

using that directly, everything works normally

robertfrederickwarner18:07:06

i'll see if i can swap that into the spot that the existing binary is and run it that way

robertfrederickwarner18:07:45

I'm wondering if it's related to this command actually: sudo snap connect clj-kondo:home - we don't have our code in the home directory (it lives in /vagrant, which is mounted from the host)

robertfrederickwarner18:07:03

This is my first foray into using snap so I'm not familiar with how it connects everything up

borkdude18:07:08

yes, that's related. snap binaries don't have access to anything other than the home dir

borkdude18:07:42

the alternative is to use brew for linux

borkdude18:07:20

nothing I can change there

borkdude18:07:55

or maybe you can install it with classic or dev settings and then it would work, not sure

robertfrederickwarner18:07:37

I'll have a browse through the snap docs and see what I can find

borkdude18:07:10

I'll push out the current release then

borkdude19:07:33

clj-kondo v2019.07.31-alpha This version includes the ability to output analysis data which allows building custom linters and tools. Happy hacking! https://github.com/borkdude/clj-kondo/releases/tag/v2019.07.31-alpha

borkdude19:07:49

(@sogaiu: it also includes printing full paths)

sogaiu21:07:40

@borkdude sounds great! hope to try it soon :)

dharrigan21:07:36

arch updated.

borkdude21:07:25

thanks, I hope you're not getting tired of updating

lee22:07:05

with each new release my code gets cleaner and my scripts & config get smaller, so happy camper here!

robertfrederickwarner22:07:38

Is there a delay for new releases to hit snapcraft? I tried refreshing my snap to get the latest but am not seeing the new version. The snapcraft page is still showing the July 24th release https://snapcraft.io/clj-kondo

borkdude22:07:17

oh, I have to release it manually after a push I think

borkdude22:07:58

can you try again?

robertfrederickwarner22:07:48

still seeing the earlier version

borkdude22:07:24

should be good now

robertfrederickwarner22:07:50

yup! seeing the new version now