`turso db shell` starts in a weird state (not ready to use)

[jyrodrigues]

Steps to reproduce:

1. Start a new terminal session;
2. Run turso db shell db-name;
3. Once it's connected, typing .quit for example won't work, one have to press enter first and only then the prompt becomes available;
4. Quit and run turso db shell db-name again;
5. Now pressing enter simply shows ^M -- if you delete it and press ctrl-D it'll kill the process BUT if you leave the ^M there and press ctrl-D then the prompt becomes available.

After pressing enter for a subsequent connection on the same terminal session

And then after pressing ctrl-D right after that

MacOS 13.2.1 iTerm2 3.4.19 turso version v0.55.0

[CodingDoug]

I've never seen this behavior, and I always use the same general setup (macos/iterm).

• How did you install the CLI?
• Upgrade to CLI 0.55.1?
• Which shell are you using (bash, zsh)?
• Have you tried resetting all of your shell configuration temporarily to see if that might be triggering something?
• Is there anything in addition that might be going on here that you haven't mentioned?

[jyrodrigues]

Thank you @CodingDoug! It's fixed now that I upgraded the CLI to 0.56.0 :tada:

For the sake of curiosity: I use zsh and installed the CLI via homebrew.

[CodingDoug]

Now that I think about it, there was a brief period of time where shell was hanging consistently. I think it was fixed in 0.55.1. Glad you got unblocked!