search

gizmo-platform / gizmo

https://gizmo-platform.github.io
ISC License
5 stars 3 forks source link

v0.0.11-rc2 command prompt does not finish command. #6

Closed Br1ck5t3r closed 4 months ago

Br1ck5t3r commented 6 months ago

Even after changing directories, When I try running the command

gizmo firmware configure

This results in nothing appearing an merely asking for a new command. Is this on my side or is this a bug?

2024-02-16

Br1ck5t3r commented 6 months ago

Further note, if I was to use the config file from v0.0.11-rc1, would it fail?

the-maldridge commented 6 months ago

That is a really weird bug. Here's what I think is happening:

The command prompt is rooted in 1980's computer arcana. This means that it handles modern concepts somewhat differently than we would expect it to. The firmware configure command makes use of a library to print pretty terminal prompts and allow you to click on things rather than having to do everything in a line oriented context. I think that what's happening is that the prompts are all getting written into NUL due to a windows stream processing choice that makes cmd.exe backwards compatible.

I know for sure this works in powershell, and I'm trying to replicate your screenshot here to see if I can work out what's going on.

As for the config file, we haven't changed any of the formats in the config files in a while, and in general we try to make sure we can continue to read old config files in newer versions, though this isn't always guaranteed. What is guaranteed is that we'll print an error if parsing the config file fails, so if you try it and don't get an error, we were able to read the file successfully.

the-maldridge commented 4 months ago

Closing this as obsolete, please re-verify on a current version.