posting really long string prevents future access to chat
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
Keybase GUI Version: 4.3.0-20190809172319+f8de90a10f
Using small teams chat:
Posted a 4,822,012 character string, no spaces, into the chat text field, hit return.
App hangs.
30 min later, quit and restarted app - it appears to have 'refreshed' on its own during that period (have noticed that for the past couple of days)
Can access other components, user profiles, etc via system tray icon menu, but chat interface will no longer load.
( Yes, I know... but I figured it would cut me off at a specific character count if it were an issue. )
Short of reinstall, any solutions?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source files or tests are named. Start by reproducing the long no-space string in the small-team chat text field, then inspect the chat interface path used after the app restarts. Done means the client remains usable and the affected chat can load after the oversized message is submitted.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- electron, react
- Domain
- desktop, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100