Differences in dcc.Store storage_type performance with dash 2.17.1
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 24.4k
- Forks
- 2.3k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 13
Description
Background callback running correctly (loading animations appearing, print statements appearing too, etc) buut when it finishes it errors out (no output is returned) with this error in the console:
Failed to execute 'setItem' on 'Storage': Setting the value of 'flag_storage' exceeded the quota.
It was resolved by changing the storage_type to 'memory' as per: https://community.plotly.com/t/error-the-quota-has-been-exceeded/26944
Description by the user:
When tested with
storage_type = 'memory'instead of'session', we don’t get the issue, so I tried to understand more why the issue happened only in the past weeks while the storage assessionwas used for one year on server (Dash Enterprise) and still works in our local machine.
The only difference is that on the server we recently switched from the 2.16.1 version (that we still use on local machine) to the 2.17.1; if we specifydash==2.16.1even withstorage_type='session'we get no issue, but with 2.17.1 we have it.
I don't have additional information and haven't had the opportunity to try to replicate this.
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 issue with Dash 2.16.1 and 2.17.1, comparing dcc.Store with storage_type set to 'session' and 'memory'. The issue is done when the version-dependent storage behavior and the 'flag_storage' quota error are understood and a verified fix or documented limitation is provided.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100