keybase / keybase/client

Warning about a "reverse scan" error during log sending

Open
#5,882 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
9.2k
Forks
1.3k
Avg merge
12h 58m
Merged PRs (30d)
56

Description

Steps
  • run keybase log send
Expected:
  • no Warnings in the output
Actual:
  • The console gets output(please refer to the output bellow)
Additional:
  • Windows 10
  • Installed per user in the AppData directory

This command will send recent keybase log entries to keybase.io
for debugging purposes only.

These logs don’t include your private keys or encrypted data,
but they will include filenames and other metadata keybase normally
can’t read, for debugging purposes.

Continue sending logs to keybase.io? (type 'YES' to confirm): yes
- WARNING error occurred during reverse scan: token too long


Success! Your log ID is:

5c7b87f66d6bc44b99dfda1c

Here's a URL to submit new bug reports containing this ID:

https://github.com/keybase/client/issues/new?body=[write%20something%20useful%20and%20descriptive%20here]%0A%0Amy%20log%20id:%205c7b87f66d6bc44b99dfda1c

Thanks!

my log id: 5c7b87f66d6bc44b99dfda1c

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the keybase log send command and the reverse-scan warning that appears during log upload on Windows 10. Reproduce the command with the provided output and log ID, then verify that successful log sending no longer emits the token too long warning.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
cli
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.