This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-09-25
Channels
- # bangalore-clj (1)
- # beginners (13)
- # boot (163)
- # cljsrn (23)
- # clojure (70)
- # clojure-czech (1)
- # clojure-russia (6)
- # clojure-spec (8)
- # clojurescript (47)
- # cloverage (16)
- # cursive (2)
- # editors (1)
- # garden (2)
- # lein-figwheel (1)
- # om (30)
- # om-next (2)
- # perun (2)
- # planck (23)
- # rdf (4)
- # reagent (1)
- # specter (2)
- # untangled (8)
- # vim (7)
@juhoteperi regarding https://github.com/clojure-vim/async-clj-omni/issues/7 do you know how to trigger it (a particular project or command is more important than accessibility to me). Adding print()s would really help. I'll try figure out how you'd end up with a string there.
No idea. Happens during work and I don't usually have time to start debugging it.
I'll try put together a diff for catching the error, should give you a little snippet to easily share with me.
@juhoteperi try this patch on bencode.py. You probably want to pair it with either https://github.com/SevereOverfl0w/.files/blob/layers/nvim/layer/completion/config.vim#L7 or a version not under a command to enable debugging.
It might be a little heavy.
You should be able to do something like grep /tmp/deopletelog 'intstr' | tail -n 50
to get the logging. Hopefully it will shed some light on it.