This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-07-31
Channels
- # announcements (1)
- # beginners (171)
- # cider (51)
- # clj-kondo (40)
- # cljsrn (5)
- # clojure (68)
- # clojure-dev (42)
- # clojure-europe (2)
- # clojure-italy (20)
- # clojure-spec (2)
- # clojure-uk (141)
- # clojurescript (19)
- # community-development (4)
- # core-async (17)
- # core-logic (3)
- # cursive (11)
- # data-science (1)
- # datomic (7)
- # defnpodcast (2)
- # figwheel (9)
- # figwheel-main (2)
- # fulcro (15)
- # graphql (21)
- # jackdaw (3)
- # joker (11)
- # juxt (1)
- # luminus (12)
- # off-topic (2)
- # pathom (73)
- # pedestal (2)
- # re-frame (41)
- # reagent (14)
- # reitit (4)
- # shadow-cljs (39)
- # tools-deps (4)
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?
clj-kondo is tested with linux and Mac in CI, so it's likely an issue with your setup
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.
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
@robertfrederickwarner here you go: https://5148-176829714-gh.circle-artifacts.com/0/release/clj-kondo-2019.07.25-alpha-SNAPSHOT-linux-amd64.zip
i'll see if i can swap that into the spot that the existing binary is and run it that way
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)
This is my first foray into using snap so I'm not familiar with how it connects everything up
yes, that's related. snap binaries don't have access to anything other than the home dir
or maybe you can install it with classic or dev settings and then it would work, not sure
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
with each new release my code gets cleaner and my scripts & config get smaller, so happy camper here!
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