* attempt upgrade over CI
update shadowbox build node version
wild guess
try other image, not holding my breath
switch image back, try no --upgrade? lol
whoops wrong SHA
trying this tip out of hand - will make platform a env var next
apparently buildx is supposed to detect the platform - lets see
find replace yarn w/ npm
fix git hook
cache npm deps
proper lock and enforce engine
licenses are... generated by yarn lmao
some weird leftovers
explode out test workflow jobs
Title Case and check for cache hit
upgrade NPM
check version...
eh, worth a try
reinstall deps for now so we can debug downstream issues
use root bin
fix npm workspace, merge lint w/ setup
HMMM
attempt cache load
fix keys
remove restore-keys
regular install
attempt more "correct" npm approach
annoyingly caching ~/.npm doesn't cache the global npm version
less correct node_module cache, will roll back if doesn't work
er... node 15 :/, restore keys
changing key...?
permission setting so cache can properly hit
separate dependecy permission task
verbose chmod
fix sentry webhook
consistency thing
* print architecture
* attempt amd64-explicit node image
* attempt nodev16 upgrade
* ah, okay, let's try picking this hash
* fix node version reference and npm run clean
* revert untouched files caught in squash
* remove yarn from travis.yml
* testing ci
* npmrc comment, revert one of cis
* Update src/server_manager/web_app/run_gallery_action.sh
Co-authored-by: Vinicius Fortuna <fortuna@users.noreply.github.com>
* Update src/server_manager/web_app/run_action.sh
Co-authored-by: Vinicius Fortuna <fortuna@users.noreply.github.com>
* licenses change
* fix package-lock regression
* fix webpack-dev-server properly
* set install to ci in Dockerfile
* forgot to include the README
* add ci where it makes sense
* delete this part of the README
* missed one
* testing sub-node_modules
* better chmod
* prefer glob
* reset .github/workflows/test.yml
* oops, yarn in ci
* rename everything (#1006)
* Update test.yml
* check_requirements (#1008)
* reqcheck draft
* finish drafting script - need to test and add to hooks
* attempt to roll our own setup...
* remove setup script and rename a couple things
* remove this nightmare lol
* Update release_manager.yml
* Update test.yml
* 'do' -> 'action'
* run -> start
* Update src/shadowbox/docker/build.action.sh
Co-authored-by: Vinicius Fortuna <fortuna@users.noreply.github.com>
* Update README.md
* Update README.md
Co-authored-by: Benjamin M. Schwartz <bemasc@google.com>
* rename 'action' to action
* add action list to run action itself
* Update src/shadowbox/README.md
Co-authored-by: Benjamin M. Schwartz <bemasc@google.com>
* Update README.md
Co-authored-by: Benjamin M. Schwartz <bemasc@google.com>
* Update scripts/run_action.sh
Co-authored-by: Benjamin M. Schwartz <bemasc@google.com>
* Update src/server_manager/scripts/fill_packaging_opts.sh
Co-authored-by: Benjamin M. Schwartz <bemasc@google.com>
* style guide fixes
* lower case fixes
* enforce major version
* Update scripts/run_action.sh
Co-authored-by: Benjamin M. Schwartz <bemasc@google.com>
* Update package.json
Co-authored-by: Benjamin M. Schwartz <bemasc@google.com>
Co-authored-by: Vinicius Fortuna <fortuna@users.noreply.github.com>
Co-authored-by: Benjamin M. Schwartz <bemasc@google.com>
Running "shellcheck", and attempting to comply with the shell script
style guide, required hundreds of trivial changes, and a small number of
nontrivial ones. For ease of review, this PR includes only the
nontrivial changes.
* 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
* Select newly added keys
* Add a comment about force rendering
* Use the newest types for express and remove a conflict between multiple
versions of express between the top level node modules and the
metrics_server node modules. Also fix node typing at major version 12
to avoid issues with typing in node 13.
