quarto-hub: some users still experiencing IndexedDB storage bugs
Open
Nobody has claimed this yet.
bug
- Dominant language
- Rust
- Stars
- 255
- Forks
- 17
- Avg merge
- 6h 20m
- Merged PRs (30d)
- 109
Description
Unfortunately, they appear to be locked out of quarto-hub.com until they clear their caches, which is not really a thing we should feel good about asking users to do.
Sam said:
I should amend that: clearing site data & cookies, not just the cache
"Site data" here probably includes IndexedDB storage.
Contributor guide
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
Start by reproducing the storage failure on quarto-hub.com and examine the site's IndexedDB and other site data behavior. Done means users are no longer locked out or required to clear site data and cookies to access the site.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- databases, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100