Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Serlib warning #800

Closed
MRandl opened this issue Jul 2, 2024 · 4 comments · Fixed by #723
Closed

Serlib warning #800

MRandl opened this issue Jul 2, 2024 · 4 comments · Fixed by #723
Labels
kind: bug Something isn't working
Milestone

Comments

@MRandl
Copy link

MRandl commented Jul 2, 2024

Describe the bug
On my machine, coq-lsp gives the following warning:

Serlib plugin: coq-serapi.serlib.btauto is not available.
Incremental checking for commands in this plugin will be impacted.

It happens when attempting to browse files from github.com/MRandl/verith
It does not seem to have an impact on my workflow

To Reproduce
Steps to reproduce the behavior:
This warning was not emitted on my other machine, so it must be environment-dependent

  1. clone verith as above
  2. make
  3. browse Cmod.v
    The first import displays the warning

Expected behavior
No warning, as on the other machine

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

  • Arch on linux kernel 6.9.7
  • coq-lsp 0.1.9+8.18
  • coq-lsp extension 0.1.10
  • Codium 1.90.2
@MRandl MRandl added the kind: bug Something isn't working label Jul 2, 2024
@MRandl
Copy link
Author

MRandl commented Jul 2, 2024

I'll gladly add more info on my environment if you need it !

@ejgallego
Copy link
Owner

ejgallego commented Jul 2, 2024

Thanks @MRandl for tying out LSP and taking the time to submit this issue!

This is mostly a developer warning, and for this plugin totally harmless.

I think time has come to disable it in the 0.2.x. series , tho this particular one is already fixed in master (merging serlib into coq-lsp fixed this , cc #698 )

@ejgallego ejgallego added this to the 0.2.0 milestone Jul 2, 2024
@MRandl
Copy link
Author

MRandl commented Jul 2, 2024

All good then ! Thanks

@ejgallego
Copy link
Owner

Solved by #723

@ejgallego ejgallego linked a pull request Jul 18, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind: bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants