* s/AccessKeyDataLimit/DefaultDataLimit/g for shadowbox
* Implement per-key custom data limits in shadowbox
* Shadowbox integration test
* Fix the manager service test to maintain backwards compatibility with
the GET /server response
* Fix integration test for Travis
* Fix lint errors
* Implement removal of access key data limits
* Persist custom data limits
* Bump Shadowbox version number
* Add a per key dat alimit count to the feature metrics endpoint
This also involved modifying the schema of
uproxysite:uproxy_metrics_dev.feature_metrics to include the new field.
See https://cloud.google.com/bigquery/docs/managing-table-schemas#bq_1
for how this was accomplished
Tested:
yarn do metrics_server/test && yarn do metrics_server/test_integration
* Collect usage metrics for per-key data limits
* API documentation and cleanup
* Respond to review comments
* Respond to review comments
* Don't encode the data limit in the access key url
This should have been caught in the integration test, but the
integration test was miswritten with "echo" instead of "fail", cause the
test to mistakenly pass.
Fixing this exposed other errors in the test, which were fixed. The
test has been confirmed to both pass and fail successfully.
* Fix the manager service unit test
* Remove stray files
* Split integration test into individual functions
* Clarify comment in the AccessKey interface
* Be more explicit about behavior when no data limits are set
* Remove spuriosu import added by vscode
* DOn't bump shadowbox version number yet
* Rename to accessKeyToApiJson
* Don't export AccessKeyJson and use "StorageJson"
* Don't await data limit enforcement
* Rename the defaultDataLimit getter
* Make dataLimit in the accesskey model readonly
* Use nullish coalescing operator
* Update Outline and Jigsaw logos
* Update launcher icon to not use transparency.
* Make the Jigsaw logo in the About view a reasonable size.
* Remove the background from the TOS view icon
* Generate all updates files
* TEST
* Allow staged releases and beta channels for all Electron platforms
* Clarify manager_release_channel.sh
* Install jq in the CI build
* Use a common script for common packaging options
* Fix comment in get_packaging_opts
* Use a version of `jq` managed by Yarn
* Make staged rollouts affect the beta channel for mainline builds
Also remove the alpha info chanel files since we aren't using them.
* Fix packaging scripts when no args are passed
* Don't install jq in Travis anymore
* Fix trailing newlines
* Fill packaging options by `source`-ing the options parsing script
* Rename to get_manager_release_channel.sh
From conversations with @alalamav, at one point the main window needed
connect to the Internet and so we would display a loading page if it
took more than 3 seconds to load. The main window no longer accesses
the internet, so there's no real reason for us to keep a loading page
around which won't be displayed.
