Welcome to the public Flycheck channel. Ask questions and discuss development. Please follow our Code of Conduct.
Anyone have any insight on this error in ruby-mode
:
Suspicious state from syntax checker ruby: Flycheck checker ruby returned 1, but its output contained no errors: ruby: /usr/lib/x86_64-linux-gnu/libcrypt.so.1: version `XCRYPT_2.0' not found (required by /home/sfernandez/.rbenv/versions/2.7.1/lib/libruby.so.2.7)
Try installing a more recent version of ruby, and please open a bug report if the issue persists in the latest release. Thanks!
Not sure if it's a Flycheck checker error, but I came across this on the trouble shooting page as a common error. As suggested I ran flycheck-verify-setup
and everything looks right:
First checker to run:
ruby
- may enable: yes
- executable: Found at /home/sfernandez/.rbenv/shims/ruby
- next checkers: ruby-rubylint
I also have a stack overflow post running here: https://stackoverflow.com/questions/62623392/ruby-usr-lib-x86-64-linux-gnu-libcrypt-so-1-version-xcrypt-2-0-not-found-r
But i'm losing hope, thanks all
M-x flycheck-compile
and see the command. Then try to run that same command in your terminal and see if you get the same error.
@codygman I came across another post that was talking about LD_INCLUDE_PATH
? I tried exporting it on command line with export LD_LIBRARY_PATH=/usr/lib:$LD_LIBRARY_PATH
but that didn't work, apparently there are many locations for libcrypt.so.1
or something? I'm not sure though
ok thanks for the advice will try flycheck-compile and see
Tried what you suggested. Not sure what this means, but there seems to be a disconnect here?
I ran flycheck-compile
and here's the result i got in compilation buffer:
-*- mode: compilation; default-directory: "~/the-odin-project/ruby/baby_ruby/" -*-
Compilation started at Sun Jun 28 14:49:41
/home/sfernandez/.rbenv/shims/ruby -w -c < /home/sfernandez/the-odin-project/ruby/baby_ruby/hello.rb
ruby: /usr/lib/x86_64-linux-gnu/libcrypt.so.1: version `XCRYPT_2.0' not found (required by /home/sfernandez/.rbenv/versions/2.7.1/lib/libruby.so.2.7)
Compilation exited abnormally with code 1 at Sun Jun 28 14:49:41
I ran the command /home/sfernandez/.rbenv/shims/ruby -w -c < /home/sfernandez/the-odin-project/ruby/baby_ruby/hello.rb
on command line and got: Syntax OK
Hello, my javascript-eslint checker returns a missing/incorrect config file. The executable IS found, and it points to the project's node-modules eslint package.
There is a .eslintrc.js file in the root of the project.
Running 'eslint --print-config path/to/file.ts' returns the correct json without any errors.
I have installed exec-path-from-shell-initialize, but it has no effect.
Any ideas?
javascript-eslint
checker and it works great. The only quibble I have is that it uses the same severity levels as eslint, so an eslint error is an error and an eslint warning is a warning. This is logical, but I find it a bit awkward to deal with. Is there a way I can locally configure the checker to change the levels to warning and info, respectively?
flycheck-parse-eslint
, so it’s not an insurmountable problem. I was just wondering whether there’s an official or cleaner way.
I'm wondering if the following might be considered a bug. Using emacs to write sphinx documention, flycheck automatically detects the source directory of the sphinx project. However the sphinx project is part of another bigger project that is contained within a virtual environment, as python projects tends to. As such, any special extensions required by the sphinx documentation will fail to load because flycheck doesn't take care of loading the proper environment before finding sphinx-build
.
Even if I manually activate the pipenv, the environment in which flycheck execute doesn't change.
python-pylint
checker: syl20bnr/spacemacs#13975 It seems to be a flycheck issue but I'm not sure where to look to find out what's going on. Could anyone take a look?
python3
? I'm working in an environment where I don't have / can't have a suitable python3 env variable. I think this is the reason I'm seeing "Missing; sys.path is nil" in the 'module' lines of my flycheck verification window
(error line-start (file-name) ":" line ": " (message) line-end)
. However the path to the file file-name
isn't correct since its relative to the docker container not my host os. So all I need to do is manipulate file-name
. I've tried to search the documentation but couldn't find an example on how to do this.