keybase / keybase/keybase-issues
siultaneous tracking requests fail, expecting outdated/changed hash
- Dominant language
- No language data
- Stars
- 899
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
I should have screen shotted the error, my apologies for not doing so.
Repro:
1. open multiple keybase.io/$userName tabs
2. attempt to track at least 2 different users at the same time (quickly switch browser tabs and send tracking request)
3. only one request will succeed - all others will output an error showing the key they were expecting and a different key to the one they recieved
Expected behaviour: all track requests should have succeeded given the correct passphrase
Actual behaviour: only one track request succeeded
Keep up the great work!
Contributor guide
No contributing guide indexed for this repository
Research direction
Reproduce by opening multiple keybase.io/$userName tabs and sending tracking requests for at least two users in quick succession. Compare the expected and received keys in the error; done means all tracking requests succeed with the correct passphrase.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100