What kind of problem?
Cannot sign in
What you are seeing
Running freebuff login generates a login URL. Opening it on another device and signing in with GitHub returns the browser to the Freebuff homepage, where I appear signed in. The browser never shows the expected login confirmation, and the CLI keeps waiting until it reports: Login timed out. Please try again.
This used to work with the npm-installed CLI. I compared the preserved packaged CLI (0.0.189) with the source-built CLI (0.0.189-base2.1) on the same VM, and both now fail with the same behavior. This makes a current device-login confirmation or callback problem plausible, though I can’t determine its cause from the client side.
Could someone check whether the GitHub sign-in callback is confirming the CLI’s pending device-login code, and whether the status endpoint then reports that login as complete?
Model involved
Not applicable
What kind of problem?
Cannot sign in
What you are seeing
Running freebuff login generates a login URL. Opening it on another device and signing in with GitHub returns the browser to the Freebuff homepage, where I appear signed in. The browser never shows the expected login confirmation, and the CLI keeps waiting until it reports: Login timed out. Please try again.
This used to work with the npm-installed CLI. I compared the preserved packaged CLI (0.0.189) with the source-built CLI (0.0.189-base2.1) on the same VM, and both now fail with the same behavior. This makes a current device-login confirmation or callback problem plausible, though I can’t determine its cause from the client side.
Could someone check whether the GitHub sign-in callback is confirming the CLI’s pending device-login code, and whether the status endpoint then reports that login as complete?
Model involved
Not applicable