type mismatch @ createRealtimeThread --> install fails

[plushy-was-taken]

Hi, I was trying to install mash 0.1.3 on an x86 Linux Mint 22.2 (kernel 6.14). The nim package is 1.6 in apt, so I installed nim 2.2 with the shell script you pointed to in the readme and have amended $PATH. I also have jackd2 installed.

When trying to nimble install --verbose mash, I get this:

      Info: Package cache path /home/plushy/.nimble/pkgcache
     Info:  Nimble data file "/home/plushy/.nimble/nimbledata2.json" has been loaded.
    Reading official package list
     Info:  Dependency on nim@>= 1.6.0 already satisfied
     Info:  Dependency on nim@>= 2.0.0 already satisfied
     Info:  Dependency on jacket@any version already satisfied
     Info:  Dependency on nim@>= 2.0.0 already satisfied
     Info:  Dependency on nim@>= 2.0.0 already satisfied
     Info:  Dependency on jacket@any version already satisfied
     Info:  Dependency on jill@>= 0.2.1 already satisfied
     Info:  Dependency on rtthread@any version already satisfied
    Reading official package list
    Reading official package list
    Reading official package list
    Reading official package list
    Reading official package list
 Installing mash@0.1.3
   Building mash/mash using c backend
      Info: compiling nim package using /home/plushy/.nimble/bin/nim
  Executing /home/plushy/.nimble/bin/nim c --colors:on --noNimblePath -d:release -d:NimblePkgVersion=0.1.3 --path:/home/plushy/.nimble/pkgs2/rtthread-0.1.0-cd43fde8ef4b04e36e8a029f1d49cb12ed663462 --path:/home/plushy/.nimble/pkgs2/jacket-0.2.0-3f04b5bad16951abcaeb0d37771762b1ec5cba7c --path:/home/plushy/.nimble/pkgs2/jill-0.2.1-0052f616270676148635c3b61e95902a0b9a9d85 -o:/home/plushy/.nimble/pkgcache/githubcom_capocasamash/mash /home/plushy/.nimble/pkgcache/githubcom_capocasamash/mash.nim
 Nim Output Hint: used config file '/home/plushy/.choosenim/toolchains/nim-2.2.6/config/nim.cfg' [Conf]
        ... Hint: used config file '/home/plushy/.choosenim/toolchains/nim-2.2.6/config/config.nims' [Conf]
        ... ..........................................................................................................................
        ... /home/plushy/.nimble/pkgcache/githubcom_capocasamash/mash.nim(389, 21) Error: type mismatch
        ... Expression: createRealtimeThread(eventThread, eventHandler,
        ...                      priority = cint(eventThreadPriority))
        ...   [1] eventThread: Thread[system.void]
        ...   [2] eventHandler: proc (){.gcsafe.}
        ...   [3] priority = cint(eventThreadPriority): priority: cint
        ... Expected one of (first mismatch at [position]):
        ... [4] proc createRealtimeThread[TArg](t: var Thread[TArg];
        ...                                 tp: proc (arg: TArg) {.thread, nimcall.};
        ...                                 param: TArg; priority: cint = 80)
        ...   missing parameter: param
        ... 
    Reading official package list
  Verifying dependencies for mash@0.1.3
    Reading official package list
   Checking for jacket@any version
     Info:  Dependency on jacket@any version already satisfied
  Verifying dependencies for jacket@0.2.0
    Reading official package list
   Checking for jill@>= 0.2.1
     Info:  Dependency on jill@>= 0.2.1 already satisfied
  Verifying dependencies for jill@0.2.1
    Reading official package list
   Checking for jacket@any version
     Info:  Dependency on jacket@any version already satisfied
  Verifying dependencies for jacket@0.2.0
    Reading official package list
   Checking for rtthread@any version
     Info:  Dependency on rtthread@any version already satisfied
  Verifying dependencies for rtthread@0.1.0
 Installing mash@0.1.3
   Building mash/mash using c backend
      Info: compiling nim package using /home/plushy/.nimble/bin/nim
  Executing /home/plushy/.nimble/bin/nim c --colors:on --noNimblePath -d:release -d:NimblePkgVersion=0.1.3 --path:/home/plushy/.nimble/pkgs2/rtthread-0.1.0-cd43fde8ef4b04e36e8a029f1d49cb12ed663462 --path:/home/plushy/.nimble/pkgs2/jacket-0.2.0-3f04b5bad16951abcaeb0d37771762b1ec5cba7c --path:/home/plushy/.nimble/pkgs2/jill-0.2.1-0052f616270676148635c3b61e95902a0b9a9d85 -o:'/home/plushy/.nimble/pkgcache/githubcom_capocasamash_#head/mash' '/home/plushy/.nimble/pkgcache/githubcom_capocasamash_#head/mash.nim'
 Nim Output Hint: used config file '/home/plushy/.choosenim/toolchains/nim-2.2.6/config/nim.cfg' [Conf]
        ... Hint: used config file '/home/plushy/.choosenim/toolchains/nim-2.2.6/config/config.nims' [Conf]
        ... ..........................................................................................................................
        ... /home/plushy/.nimble/pkgcache/githubcom_capocasamash_#head/mash.nim(389, 21) Error: type mismatch
        ... Expression: createRealtimeThread(eventThread, eventHandler,
        ...                      priority = cint(eventThreadPriority))
        ...   [1] eventThread: Thread[system.void]
        ...   [2] eventHandler: proc (){.gcsafe.}
        ...   [3] priority = cint(eventThreadPriority): priority: cint
        ... Expected one of (first mismatch at [position]):
        ... [4] proc createRealtimeThread[TArg](t: var Thread[TArg];
        ...                                 tp: proc (arg: TArg) {.thread, nimcall.};
        ...                                 param: TArg; priority: cint = 80)
        ...   missing parameter: param
        ... 
nimble.nim(419)          buildFromDir

    Error:  Build failed for the package: mash
     Info:  Nimble data file "/home/plushy/.nimble/nimbledata2.json" has been saved.

Let me know if there's any more info I should provide.

Thank you!

[SpotlightKid]

You need to update rtthread.

A nimble uninstall rtthread and then nimble install in the mash checkout worked for me to get a mash binary in ~/.nimble/bin.

[plushy-was-taken]

Thank you @SpotlightKid , it seems like I got it to install by cloning https://github.com/capocasa/rtthread.git and after 4 or 5 attempts and while it still shows as "rtthread@0.1.0" in my nimble list --installed --ver, I now got it to install.

Still, I think this issue is reproducible, so I wouldn't close it until this is no longer the case :)