nimforum mirror - nimlsp using old nim package

derek-v-s (orginal) [2025-05-05T07:38:08+02:00] view original

Does nimble default to using a package like ~/.nimble/pkgs2/nim-2.0.8-46333e8f4bda41dd6d3852a3f5fa4975b96b66a2/bin/nim regardless of what I have installed with choosenim (2.2.4)? I had to delete that package for it to build with 2.2.4. Just wondering if this is intended behavior.

giaco (orginal) [2025-05-05T10:59:46+02:00] view original

nimble picks the version of a dependency following specific rules

if you're building something which has nim source as dependency, you can use "nimble --useSystemNim install nimlsp"

derek-v-s (orginal) [2025-05-05T22:33:56+02:00] view original

Glad to know about that flag, thanks!

I did check the nimble files for nimlsp and its dependencies and none of them seem to set an upper limit on the version of nim. I don't understand why nimble would choose to use that 2.0.8 nimble package.

khaledh-nim (orginal) [2025-05-07T06:20:14+02:00] view original

If you are running nimble from a directory that has a nimble.lock file, check if the file has nim locked to 2.0.8. Nimble will use the version from the lock file, even if a newer version is installed as a package.

derek-v-s (orginal) [2025-05-07T11:31:25+02:00] view original

You might be onto something! While I don't think whatever directory I was in had a lock file (or doesn't anymore) a search found one in ~/.nimble/pkgcache/githubcom_nimlanglangserver/ which indeed has


"nim": {
      "version": "2.0.8",

I'm not sure how this connects to nimlsp... but it seems like a very big coincidence otherwise.

jmgomez (orginal) [2025-05-07T11:37:14+02:00] view original

which would generate the lock file and pin nim to whatever version you had at that time

nimble setup does not imply lock

@derek-v- specify --useSystemNim

derek-v-s (orginal) [2025-05-07T11:57:04+02:00] view original

Yes I understood. I already solved the problem by deleting that 2.0.8 package, and possibly specifying the exact path to 2.2.4. I'm just curious to know what's going on, as this seems like either a bug, or something that defies the principle of least astonishment.

khaledh-nim (orginal) [2025-05-07T13:06:13+02:00] view original

nimble setup does not imply lock

You're right. My bad. For some reason I made that assumption as I don't recall explicitly creating the lock file.

khaledh-nim (orginal) [2025-05-07T13:30:26+02:00] view original

This may be relevant (from nimble --help):

--disableNimBinaries
Disable the use of nim precompiled binaries. Note in some platforms precompiled binaries are not available but the flag can still be used to avoid compile the Nim version once and reuse it.

It could mean that you had nim 2.0.8 compiled by nimble at some point, and it gets reused from that point on (until you manually uninstall it).

derek-v-s (orginal) [2025-05-07T23:26:56+02:00] view original

That seems to support my initial suspicion that nimble defaults to using these binaries. If that's true, I wonder what the benefits are, and if they outweigh the costs, which seem to be

the user needs to become aware of this behavior by reading all the flags and making an inference

the user needs to become aware of ~/.nimble/pkgs2/ and what is in it, or blindly use verbose flags like --useSystemNim or --disableNimBinaries

Am I missing something?

khaledh-nim (orginal) [2025-05-07T23:37:19+02:00] view original

That's obviously a question for nimble maintainers. But IMO, --useSystemNim should be the default (i.e. default to nim on the path), and then fallback to a built version in ~/.nimble/pkgs2 (subject to current version constraints, if any), and then finally fallback to downloading and compiling nim.

johnsonangela (orginal) [2025-05-16T23:19:02+02:00] view original

I lost $485,000.00 USDT to a fake cryptocurrency trading platform a few weeks back after I got lured into the trading platform with the intent of earning a 10% profit daily trading on the platform. It was a hell of a time for me as I could hardly pay my bills and got me ruined financially. I had to confide in a close friend of mine who then introduced me to this crypto recovery team with the best recovery software at CYBERSPACE HACK PRO. I contacted them and they were able to completely recover my stolen digital assets with ease. Their service was superb, and my problems were solved in swift action, It only took them 48 hours to investigate and track down those scammers and my funds were returned to me. I strongly recommend this team to anyone going through a similar situation with their investment or fund theft to look up this team for the best appropriate solution to avoid losing huge funds to these scammers. Send complaint to

Contact info:

Email: Cyberspacehackpro(@)rescueteam.com

WhatsApp: +1 (659) 217 9239

https://cyberspacehackpro0.wixsite.com/cyberspacehackpro

Mirror of forum.nim-lang.org

12860 :: nimlsp using old nim package