Issue 176745 in chromium: Increase chrome.storage.sync quota for unpacked extensions in development

[chro...@googlecode.com]

Status: Unconfirmed
Owner: ----
Labels: Feature-Extensions Pri-2 Via-Wizard Type-Bug OS-Mac

New issue 176745 by 4braham: Increase chrome.storage.sync quota for
unpacked extensions in development
http://code.google.com/p/chromium/issues/detail?id=176745

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_5)
AppleWebKit/537.31 (KHTML, like Gecko) Chrome/26.0.1410.5 Safari/537.31

Steps to reproduce the problem:
1. Load a new unpacked extension you are developing
2. Start writing some code that uses chrome.storage.sync
3. Hit quota limits forcing you to wait a period of time before continuing
to development

What is the expected behavior?
Development generally results in atypically high usage patterns that don't
normally surface under general use. It would be nice if the quota for
extensions in unpacked dev mode had higher quotas so that developers don't
have to take so many coffee breaks while writing sync code.

What went wrong?
Normal usage quotas are too restrictive for development usage and
repeatedly having to take a break or change to different features is
disruptive to developers.

WebStore page:

Did this work before? No

Chrome version: 26.0.1410.5 Channel: dev
OS Version: OS X 10.7.5

Apologies to Randall Munroe

Attachments:
compiling.png 57.3 KB

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[chro...@googlecode.com]

Updates:
Status: WontFix
Cc: kal...@chromium.org
Labels: -OS-Mac OS-All Area-Internals

Comment #2 on issue 176745 by tap...@chromium.org: Increase

chrome.storage.sync quota for unpacked extensions in development
http://code.google.com/p/chromium/issues/detail?id=176745

Not sure we can distinguish between sync being used in development, and
sync being used "live" without opening a hole for abuse. I would try
something like

myStorage = chrome.storage.local; // for development
// myStorage = chrome.storage.sync;

Apart from throttles, I think the APIs are mostly interchangeable w.r.t.
development.

[chro...@googlecode.com]

Comment #3 on issue 176745 by kal...@chromium.org: Increase

chrome.storage.sync quota for unpacked extensions in development
http://code.google.com/p/chromium/issues/detail?id=176745

We can check to see if the extension is unpacked and give is more quota -
but I don't think we should. Throttles and quotas in sync are there to
prevent the logged in user from being throttled at the server level, which
as Trent says, isn't something we can distinguish. Either use chrome.local
or restart Chrome (disabling or uninstalling extension might also work).