cabal --seed throws error

Question

cabal --seed throws error

okdistribute opened this issue 4 years ago · comments

On 11.2.0, after rm -rf ~/.cabal

$ npm install -g cabal
$ cabal cabal.chat --seed
Seeding cabal.chat

@: new peer
x: peer left
^: uploaded a chunk
.: downloaded a chunk


TypeError: Cannot read property 'ready' of undefined
    at trackAndPrintEvents (/home/okdistribute/.nvm/versions/node/v12.4.0/lib/node_modules/cabal/cli.js:332:9)
    at /home/okdistribute/.nvm/versions/node/v12.4.0/lib/node_modules/cabal/cli.js:322:9
    at Array.forEach (<anonymous>)
    at /home/okdistribute/.nvm/versions/node/v12.4.0/lib/node_modules/cabal/cli.js:314:12
    at processTicksAndRejections (internal/process/task_queues.js:89:5)

Are there automated tests for cabal for the --seed command?

Kira Oakley · Answer 1 · Sat Apr 25 2020 04:16:51 GMT+0800 (China Standard Time)

Is this on the latest version (11.2.0)?

J✪ΞY STANFORD · Answer 2 · Sat May 02 2020 06:19:54 GMT+0800 (China Standard Time)

I can get this to fail on multiple versions of nodejs but not in the manner reported. Still present in Cabal 11.2.0

Launch Cabal and join the public chat
Navigate to the status channel
Type "/add abcd"

J✪ΞY STANFORD · Answer 3 · Wed May 06 2020 12:24:19 GMT+0800 (China Standard Time)

So I don't hijack this thread, I'll open up a different bug report

Kira Oakley · Answer 4 · Sat Jun 20 2020 10:03:00 GMT+0800 (China Standard Time)

Confirmed still crashing on 13.1.6.

Kira Oakley · Answer 5 · Sat Jun 20 2020 10:16:24 GMT+0800 (China Standard Time)

Fixed on the main branch. It will be included in the next CLI release. The problem was trying to look up the cabal in cabal-client using the DNS name instead of the actual resolved key.