search

fission-codes / fission

Fission CLI & server
https://runfission.com/docs
119 stars 14 forks source link

CLI installation problem #602

Closed nichoth closed 2 years ago

nichoth commented 2 years ago

Summary

I followed the instructions here — https://guide.fission.codes/developers/installation — and here — https://guide.fission.codes/developers/getting-started .

I was prompted for a username, and I thought, "I don't know if I have a username, I will try my standard name here." Then the CLI program just seemed to freeze.

Problem

The CLI seems to just hang after asking for my username.

Impact

I can't use the CLI

Solution

?

To Reproduce Download fission CLI via brew as in the instructions, and enter a username.

Expected behavior CLI should continue the setup process.

Screenshots

image

Desktop (please complete the following information):

github-actions[bot] commented 2 years ago

Thank you for submitting an issue! It means a lot that you took the time -- it helps us be better 🙏

matheus23 commented 2 years ago

Thanks for submitting @nichoth!

Can you try re-running with the --verbose flag? There should be a lot more output, possibly something hinting on what's hanging.

nichoth commented 2 years ago

Sorry, I have kind of a long story now.

I recently started using a new computer, and wasn't sure how logging in with a fission account from an old computer would work.

Anyway, I set up a new username, nichoth1 on https://dashboard.fission.codes/, and when I tried the CLI again, everything seemed to work; meaning the program just exited after fission setup, and didn't prompt me for a username or anything.

image
nichoth commented 2 years ago

Sorry, i was able to get that scenario again by typing fission login

fission login --verbose
2022-06-07 14:33:44.626365: [debug] 👀📖 Reading global config.yaml
2022-06-07 14:33:44.626899: [debug] 👀📖 Reading YAML from "/Users/nick/.config/fission/config.yaml"
2022-06-07 14:33:44.626952: [debug] 🛑 Path does not exist
2022-06-07 14:33:44.626967: [warn] 🙋 Cannot find file
2022-06-07 14:33:44.627353: [debug] No cached server DID. Fetching from _did.runfission.com
2022-06-07 14:33:44.714129: [debug] DID retrieved did:key:z6MkgYGF3thn8k1Fv4p4dWXKtsXCnLH7q9yw4QgNPULDmDKB
2022-06-07 14:33:44.714210: [debug] User (Login (Options {optUsername = Nothing}))
2022-06-07 14:33:44.714242: [debug] 👀📖 Reading global config.yaml
2022-06-07 14:33:44.714268: [debug] 👀📖 Reading YAML from "/Users/nick/.config/fission/config.yaml"
2022-06-07 14:33:44.714314: [debug] 🛑 Path does not exist
2022-06-07 14:33:44.714334: [warn] 🙋 Cannot find file
2022-06-07 14:33:44.714354: [debug] Unable to parse config
2022-06-07 14:33:44.714374: [debug] App interpreter
2022-06-07 14:33:44.714475: [debug] 🧬🔬 Parsing signing key
2022-06-07 14:33:44.714509: [info] 🧬👍 Loaded signing key
2022-06-07 14:33:44.714534: [debug] 💪🛂 Getting root UCAN
2022-06-07 14:33:44.714552: [debug] 🛂🚚 Loading UCAN store
2022-06-07 14:33:44.714575: [debug] 👀📖 Reading JSON from "/Users/nick/.config/fission/ucan/store.json"
2022-06-07 14:33:44.714608: [debug] 🛑 File path does not exist
2022-06-07 14:33:44.714628: [warn] 🙋 Cannot find file
2022-06-07 14:33:44.714664: [debug] 👀📖 Reading global config.yaml
2022-06-07 14:33:44.714685: [debug] 👀📖 Reading YAML from "/Users/nick/.config/fission/config.yaml"
2022-06-07 14:33:44.714709: [debug] 🛑 Path does not exist
2022-06-07 14:33:44.714724: [warn] 🙋 Cannot find file
2022-06-07 14:33:44.714772: [debug] 🛂📥 Consuming log-in...
📛 Please enter your username: nichoth
2022-06-07 14:33:52.857289: [debug] Fetching DID for nichoth
2022-06-07 14:33:53.023333: [debug] Got raw DID response: ["000;did:key:z13V3Sog2YaUKhdGCmgx9UZuW1o1ShFJYc6DvGYe7NTt689NoL3A3d72c6jfNjZHVu4sfJAW2v5MV6m7TyQ87PNuCrTkgo2LETRJqRtLaQWJVwovdFuhGCVcRfQTSqgpfcSgXxaSHFcWpouSEt39n6m95iHFkR9NWGMKRqeSSXjpeXMGayxNU6169oJsjSpdf3H599NCtFwMfDoDS2ciUBW2gPjCiwh3bww3NkZTctTUgyW7zqn","001;b3fukerMaUxkJcNCjcTrjYCoLwkuM3ypTWxM8MHd3R8JKRbojYYaiTqSKuFCgoJnrszztz48WVDCQcqNiYvsbu7hyoejFK2gW4TwZZmb6awf2brguZQCiMJeCE8wJJQvBpJ9XqVREm6w4FL9gNPgzwAYSVy9nhhCyU6c"]
2022-06-07 14:33:53.025058: [debug] Raw DID: did:key:z13V3Sog2YaUKhdGCmgx9UZuW1o1ShFJYc6DvGYe7NTt689NoL3A3d72c6jfNjZHVu4sfJAW2v5MV6m7TyQ87PNuCrTkgo2LETRJqRtLaQWJVwovdFuhGCVcRfQTSqgpfcSgXxaSHFcWpouSEt39n6m95iHFkR9NWGMKRqeSSXjpeXMGayxNU6169oJsjSpdf3H599NCtFwMfDoDS2ciUBW2gPjCiwh3bww3NkZTctTUgyW7zqnb3fukerMaUxkJcNCjcTrjYCoLwkuM3ypTWxM8MHd3R8JKRbojYYaiTqSKuFCgoJnrszztz48WVDCQcqNiYvsbu7hyoejFK2gW4TwZZmb6awf2brguZQCiMJeCE8wJJQvBpJ9XqVREm6w4FL9gNPgzwAYSVy9nhhCyU6c
2022-06-07 14:33:53.026854: [debug] 📞🙏 Websocket connecting at: runfission.com:443/user/link/did:key:z13V3Sog2YaUKhdGCmgx9UZuW1o1ShFJYc6DvGYe7NTt689NoL3A3d72c6jfNjZHVu4sfJAW2v5MV6m7TyQ87PNuCrTkgo2LETRJqRtLaQWJVwovdFuhGCVcRfQTSqgpfcSgXxaSHFcWpouSEt39n6m95iHFkR9NWGMKRqeSSXjpeXMGayxNU6169oJsjSpdf3H599NCtFwMfDoDS2ciUBW2gPjCiwh3bww3NkZTctTUgyW7zqnb3fukerMaUxkJcNCjcTrjYCoLwkuM3ypTWxM8MHd3R8JKRbojYYaiTqSKuFCgoJnrszztz48WVDCQcqNiYvsbu7hyoejFK2gW4TwZZmb6awf2brguZQCiMJeCE8wJJQvBpJ9XqVREm6w4FL9gNPgzwAYSVy9nhhCyU6c
2022-06-07 14:33:53.571929: [debug] 📞🔗 Websocket pubsub connected
2022-06-07 14:33:53.572228: [debug] 🤝 Device linking handshake: Step 1
2022-06-07 14:33:53.684375: [debug] Opening secure channel over (PublicKey,PrivateKey)
2022-06-07 14:33:53.684544: [debug] 🤝 Device linking handshake: Step 2
2022-06-07 14:33:53.684563: [debug] 📞🗣️  Sending over pubsub:
2022-06-07 14:33:53.684576: [debug] did:key:z13V3Sog2YaUKhdGCmgx9UZuW1o1ShFJYc6DvGYe7NTt689NoL2Yd1CKcWuWdx1ujBbfVrRptg31J5gpVAoP5rEmFeQu7rW8Fz8kudh5j1WSj2c8yZjToK9Zxwq7KXFN9pXJgqpKQwq5GgBjBBxN6G4uubuJohDzVVjujpGYZ7QVLsVkaJA6ymt64hMUZwEL2PoTKXoexZFeJqG3pReDZDB3SeJTN25Bc6NVaKZPSEidAxtVbYTUAHH163A1m2mV5rB1Hv8oGNFCPp9ndjeqGuxjhEorQS7aABAbjPrD1KnoXfFvKEbcjHC2DAPVwq5Adc9sNwfrZ3Dhq358ugBcr3BWYr3n28KGoCAjvaBV829F1NrBYLxJRpr1RGCpVK8EPTow8oiSTp1XYkALQpCS3RJ
2022-06-07 14:33:53.685128: [debug] 🤝 Device linking handshake: Step 3
2022-06-07 14:33:53.685151: [debug] 📞👂 Listening for pubsub-over-websockets message...
nichoth commented 2 years ago

Can confirm it happens when using the new ID nichoth1 as well

blog develop % fission login --verbose
2022-06-07 14:37:26.784554: [debug] 👀📖 Reading global config.yaml
2022-06-07 14:37:26.784762: [debug] 👀📖 Reading YAML from "/Users/nick/.config/fission/config.yaml"
2022-06-07 14:37:26.784799: [debug] 🛑 Path does not exist
2022-06-07 14:37:26.784813: [warn] 🙋 Cannot find file
2022-06-07 14:37:26.785565: [debug] No cached server DID. Fetching from _did.runfission.com
2022-06-07 14:37:26.870874: [debug] DID retrieved did:key:z6MkgYGF3thn8k1Fv4p4dWXKtsXCnLH7q9yw4QgNPULDmDKB
2022-06-07 14:37:26.870957: [debug] User (Login (Options {optUsername = Nothing}))
2022-06-07 14:37:26.870991: [debug] 👀📖 Reading global config.yaml
2022-06-07 14:37:26.871016: [debug] 👀📖 Reading YAML from "/Users/nick/.config/fission/config.yaml"
2022-06-07 14:37:26.871049: [debug] 🛑 Path does not exist
2022-06-07 14:37:26.871068: [warn] 🙋 Cannot find file
2022-06-07 14:37:26.871087: [debug] Unable to parse config
2022-06-07 14:37:26.871107: [debug] App interpreter
2022-06-07 14:37:26.872230: [debug] 🧬🔬 Parsing signing key
2022-06-07 14:37:26.872269: [info] 🧬👍 Loaded signing key
2022-06-07 14:37:26.872294: [debug] 💪🛂 Getting root UCAN
2022-06-07 14:37:26.872315: [debug] 🛂🚚 Loading UCAN store
2022-06-07 14:37:26.872335: [debug] 👀📖 Reading JSON from "/Users/nick/.config/fission/ucan/store.json"
2022-06-07 14:37:26.872365: [debug] 🛑 File path does not exist
2022-06-07 14:37:26.872383: [warn] 🙋 Cannot find file
2022-06-07 14:37:26.872416: [debug] 👀📖 Reading global config.yaml
2022-06-07 14:37:26.872433: [debug] 👀📖 Reading YAML from "/Users/nick/.config/fission/config.yaml"
2022-06-07 14:37:26.872457: [debug] 🛑 Path does not exist
2022-06-07 14:37:26.872473: [warn] 🙋 Cannot find file
2022-06-07 14:37:26.872503: [debug] 🛂📥 Consuming log-in...
📛 Please enter your username: nichoth1
2022-06-07 14:37:30.493507: [debug] Fetching DID for nichoth1
2022-06-07 14:37:30.584512: [debug] Got raw DID response: ["001;eJAj5QFwaJzmcmDegv1tiXhxWuvM3zCe3frkMhvsKC9Qk9tAEp7YhNvQxE39u3Wbq4uvRYdpqPTM3dVDBCZchEdSujuRULNuZcPZCc33DdARRwrVygG1VeeByV2YGZxQ9Z1ogfrUoaAWMszJKoh56dZgW8PAfMzAzdg4","000;did:key:z13V3Sog2YaUKhdGCmgx9UZuW1o1ShFJYc6DvGYe7NTt689NoL2bcWjamjTPa4vtTV3NsQzN22iopeza2oief7exkii76ZV6orMdRQDJUiLCxPR2pjyLqnB9xwtHpvv7HMfFgEY4TtNuM1FYXmZwnbikfEaTrxkyuurtbFY7e8b2dLvkjrSUWjVmtHjVvcb9wLasdbAAjsBg5S2iE3UC6tGBqe4DrJqg4bqXLHQfjzfLoJiPHqi"]
2022-06-07 14:37:30.584857: [debug] Raw DID: did:key:z13V3Sog2YaUKhdGCmgx9UZuW1o1ShFJYc6DvGYe7NTt689NoL2bcWjamjTPa4vtTV3NsQzN22iopeza2oief7exkii76ZV6orMdRQDJUiLCxPR2pjyLqnB9xwtHpvv7HMfFgEY4TtNuM1FYXmZwnbikfEaTrxkyuurtbFY7e8b2dLvkjrSUWjVmtHjVvcb9wLasdbAAjsBg5S2iE3UC6tGBqe4DrJqg4bqXLHQfjzfLoJiPHqieJAj5QFwaJzmcmDegv1tiXhxWuvM3zCe3frkMhvsKC9Qk9tAEp7YhNvQxE39u3Wbq4uvRYdpqPTM3dVDBCZchEdSujuRULNuZcPZCc33DdARRwrVygG1VeeByV2YGZxQ9Z1ogfrUoaAWMszJKoh56dZgW8PAfMzAzdg4
2022-06-07 14:37:30.586244: [debug] 📞🙏 Websocket connecting at: runfission.com:443/user/link/did:key:z13V3Sog2YaUKhdGCmgx9UZuW1o1ShFJYc6DvGYe7NTt689NoL2bcWjamjTPa4vtTV3NsQzN22iopeza2oief7exkii76ZV6orMdRQDJUiLCxPR2pjyLqnB9xwtHpvv7HMfFgEY4TtNuM1FYXmZwnbikfEaTrxkyuurtbFY7e8b2dLvkjrSUWjVmtHjVvcb9wLasdbAAjsBg5S2iE3UC6tGBqe4DrJqg4bqXLHQfjzfLoJiPHqieJAj5QFwaJzmcmDegv1tiXhxWuvM3zCe3frkMhvsKC9Qk9tAEp7YhNvQxE39u3Wbq4uvRYdpqPTM3dVDBCZchEdSujuRULNuZcPZCc33DdARRwrVygG1VeeByV2YGZxQ9Z1ogfrUoaAWMszJKoh56dZgW8PAfMzAzdg4
2022-06-07 14:37:31.229176: [debug] 📞🔗 Websocket pubsub connected
2022-06-07 14:37:31.229280: [debug] 🤝 Device linking handshake: Step 1
2022-06-07 14:37:31.406343: [debug] Opening secure channel over (PublicKey,PrivateKey)
2022-06-07 14:37:31.406429: [debug] 🤝 Device linking handshake: Step 2
2022-06-07 14:37:31.406445: [debug] 📞🗣️  Sending over pubsub:
2022-06-07 14:37:31.406456: [debug] did:key:z13V3Sog2YaUKhdGCmgx9UZuW1o1ShFJYc6DvGYe7NTt689NoL2DTooQV2gh4hc2w21WxLFAGEKRHCmxAqY8Cr7aDTJXaWXEMHwchdmcJ2rUc2eYZMwTDKRUkqH66nGfTf1rpVHDb2sKZtSbh9tk85X8EeLPAUbX49VFSBYDBfK8UiUU1WPZisfn6SRQASDif4V8dM115HrYuMYFeEVAJSQj6GjG9CKLNSKtkjGE9uUZbZRfabz7y2T4QYvHZABST1MGSTpZd1D1npc3yDS2KhNJFG5oxaWk5qp9URxm6YjddbjEfJQtCV2dDKxKeNKfWDZVK3nyRmtpCaVMYEUQbKvPD5KmYbHtUA8kmovoTSPmoiw1GHD7FT66KXkeanK2sJqqQ7nXR8hxFTiMLZ7qBzG
2022-06-07 14:37:31.406986: [debug] 🤝 Device linking handshake: Step 3
2022-06-07 14:37:31.407013: [debug] 📞👂 Listening for pubsub-over-websockets message...

That code block above ^ is where the command fission login stops and hangs.

the web browser, however, seems to be ok

image
bgins commented 2 years ago

Do you still have your old computer on hand? One thing you could do is copy over your private key and use it to setup your new machine.

The private key should be at ~/.config/fission/key/machine_id.ed25519. Copy that onto a USB drive or something and then on your new machine. Make sure that ~./config/fission doesn't exist on your new machine, then run:

fission setup --with-key machine_id.ed25519

That should set up everything with your nichoth account.

One detail, this assumes you originally registered your account at the CLI on your old computer. If you have a ~/.config/fission/ucan directory, the account was linked from another device. In theory, you should be able to copy over the ucan directory after setup -- though I haven't actually tried this, so I may be overlooking something.

bgins commented 2 years ago

Oh you might also need to copy over ~/.config/fission/wnfs as well. That has the read key for WNFS, which doesn't matter so much at the CLI, but you want it around for linking your CLI to browsers.

nichoth commented 2 years ago

Some more information, inspired by discord discussion… I deleted the directory ./config/fission. Then it was the same, I did fission setup and fission login, with nichoth1 and it got stuck at the same place:

[debug] 📞👂 Listening for pubsub-over-websockets message...

So, I tried copying the existing keypair from the old machine. It looks like it didn't have a directory ~/.config/fission, so first I installed fission-cli on the old machine. I logged in with the username nichoth this time, not nichoth1. It got stuck at the same place

[debug] 📞👂 Listening for pubsub-over-websockets message...

so, on the old computer, i opened up the browser while that terminal process was waiting, and didn't get very far though. It displayed this message:

your filesystem is outdated message

[message saying "your filesystem is outdated"]

bgins commented 2 years ago

Ah ok, your filesystem for nichoth is from before there were some breaking changes to WNFS. You can try the filesystem migration instructions here: https://guide.fission.codes/accounts/account-signup/account-migration.

Not sure why the linking hangs. Are you able to create a new account at the CLI and link it in the browser?

nichoth commented 2 years ago

I was able to create a new account via CLI, following instructions here: https://guide.fission.codes/developers/cli/managing-your-account#setup-a-new-user

image
nichoth commented 2 years ago

... and linking the browser worked too

following these instructions

image
bgins commented 2 years ago

Alright great! It might be possible to recover your nichoth account by migrating the filesystem, and installing it on your new machine using fission setup and the --with-key argument.

What do you think? Are you attached to your original username? Have data in the filesystem that you want recover? We can keep working on getting it working if you want.

nichoth commented 2 years ago

Thank you for the help @bgins . No there's no need to keep the original name. Honestly the only thing stopping me is just me being too preoccupied to read and follow the instructions for migrating the filesystem.

bgins commented 2 years ago

Sounds good. 👌

I'll close this issue for now, but if you change your mind we can re-open it and see if we can get nichoth back and working for you. 🙂