keybase / keybase/client

"user" on twitter/github failed: context canceled (code=170)

Open
#6,985 4 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

Affects all attempts to verify Twitter/GitHub proofs. Prior to this issue, all Twitter proofs were failing with 404 Not Found (code=240)

OS: macOS Sierra 10.12.4 (16E195)
Keybase Client: 1.0.22-20170502110012+a3c4856
Keybase Service: 1.0.22-20170502110012+a3c4856

Command: keybase -d id zenexer
Relevant output:

1b3 + API GET https://twitter.com/Zenexer/status/752620356578533376 [tags:ID2=kFScbP58hd9N,API=vQNpo2hpHViW]
1b4 - API GET https://twitter.com/Zenexer/status/752620356578533376: err=ok, status="200 OK", jsonBytes=0 [tags:ID2=kFScbP58hd9N,API=vQNpo2hpHViW]
1b5 PVL @(service:twitter script:0 pc:2) Error code=INTERNAL_ERROR: context canceled [tags:ID2=kFScbP58hd9N]
1b6 PVL CheckProof failed: context canceled (code=170) [tags:ID2=kFScbP58hd9N]
✔ "zenexer" on twitter failed: context canceled (code=170)

Command: keybase track [redacted]
Output:

▶ INFO Identifying [redacted]
✔ <tracked> public key fingerprint: [redacted]
You last followed [redacted] on 2017-05-13 01:25:36 EDT
฿  bitcoin [redacted]
✔ <tracked> "[redacted]" on reddit: https://www.reddit.com/r/KeybaseProofs/comments/[redacted]/ [cached 2017-05-13 01:24:46 EDT]
✔ <tracked> admin of DNS zone [redacted]: found TXT entry keybase-site-verification=[redacted] [cached 2017-05-13 01:24:47 EDT]
✔ <tracked> "[redacted]" on github failed: context canceled (code=170)
✔ <tracked> "[redacted]" on twitter failed: context canceled (code=170)
▶ INFO Your view is up-to-date

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 reproducing the failure with keybase -d id zenexer and keybase track [redacted], then trace the Twitter and GitHub proof verification flow associated with the logged context canceled error. Done means both proof checks complete successfully instead of returning code 170.

Written by the indexing model from the issue text.

Assessment

Tech stack
github, go
Domain
authentication, security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.