* Remove now-404ing link to a webinar from the H2 2021 Transparency Report page
* Revert "Remove now-404ing link to a webinar from the H2 2021 Transparency Report page"
This reverts commit dd6d053884.
* Fix 404ing link to a webinar from the H2 2021 Transparency Report page
Django 3.0 fixes:
* Remove six
* Convert LANGUAGES to a list
* Update redirects
* Django's `re_path` no longer sends they key for matched group name if the value is `None`. This caused some errors as we were depending on the old behavior.
* Add `private` for cache-control headers
* Remove context argument to `from_db_value`
* Re-arrange check due to `re_path` change.
* Tweak contentful query
* The change to using bitwise operations on the `Q` object here are due to this adding an empty `(AND: )` to the query. While this doesn't change anything about the underlying query, I made this change to clean up the query and match Django documented usage.
* Fix failing contentful test
* `is_ajax` is deprecated
* The `HttpRequest.is_ajax()` method is deprecated as it relied on a jQuery-specific way of signifying AJAX calls, while current usage tends to use the JavaScript Fetch API. Depending on your use case, you can either write your own AJAX detection method, or use the new HttpRequest.accepts() method if your code depends on the client Accept HTTP header.
* Update docs to follow Django upgrades and syntax
Django 3.2 fixes:
* Set value for the new `DEFAULT_AUTO_FIELD` setting
* Updates for new app config discovery
* Update to new response headers interface.
* Remove regex from URL `path`s
* Change quoting to match black in docs
* Fix hyperlink to security@mozilla.com to be a mailto:
* Fix broken link in MPL2.0 FAQs back to MPL itself
* Fix link to National Security Requests info
This fixes a bad link on https://www.mozilla.org/en-US/about/policy/transparency/
in the section How does Mozilla handle Government Demands for User Data?
* Fix broken links on Safari page
* Fix broken link to Norwegian locale from the /locales/ page
* Fix broken link in VPN 'What is an IP address' page - variable no longer available
Added a new FTL string and used the original (semi broken) one as a fallback for now
* Make outdated string obvious
Co-authored-by: Alex Gibson <alexgibson@users.noreply.github.com>
Co-authored-by: Alex Gibson <alexgibson@users.noreply.github.com>
* access policy: Improve the rendering
* access policy: Comment the old content until it is addressed
* Minor fix around HTML comment
Co-authored-by: Steve Jalim <steve@stevejalim.net>
* Adding cdn tests
Using a cdn mark to allow skipping or only running the cdn tests
uses ssllabs to get the tls/cipher information
That can be fairly slow, so trying to ensure it only happens once per run - so caching to a json file
* migrating existing tests into the functional area
* formatting failed in circle
* Move Bedrock to pip-compile-multi for easier Python dependency management
This changeset adds tooling to ease dependency management and also rationalises
our requirements files.
Before, we were just using hashin to manually hash pinned deps straight into a requirements file
Now we're using pip-compile-multi, which sits on top of pip-tools to do this.
We now get:
* Simpler syntax for adding and pinning dependencies via *.in files
* Automatic hash generation when the *.txt requirements files are produced
The dependency compilation/update tooling runs in a Docker container, so will be compatible
with the deployed service's containers.
We're also rationalising the existing split of dependency files:
* base -> being retired and used as the basis for prod requirements
* migration -> being retired and the two deps still useful to us (for moz-l10n-lint)
added to dev deps
* dev -> now extends from the prod requirements. We're not too concerned about image
size for dev and test builds
* prod -> still exists, but includes the base deps
* docs -> still exists as a standalone file, but also follows the "*.in"-file pattern
* Regenerate dependency files using pip-compile-multi
Note that to avoid clashes, the following balances were made:
* Keep meinheld at the lower version used in prod.txt, not the dev.txt one -- for now at least
* Downgrade Markdown to 3.3 to avoid a clash over importlib-metadata version
* Remove importlib-metadata==4.10.1 altogether as a hard pin and let pip-compile-multi work out the best fit
* Update docs to reference pip-compile-multi, replacing now-redundant notes on hashin
* Update Dockerfile to copy over and use freshly recut dependency files
* Attempting to tune deps to allow local builds to work, not just Docker ones
* Update pip-compile-multi config to inject a custom header that explains how to rebuild reqs
* Update Bedrock to use Python 3.9
* Update base images
* Update CI
* Update dependencies to make install run -- this involved manually using hashin to upgrade two hashed deps (greenlet and meinheld) then re-running make compile-requirements to update the top-level hash in prod.txt. It's a bit of a chicken-and-egg situation when the deps are built/re-locked in a container but you can't build the container itself unless the deps are viable, but it worked
* Upgrade everett in order to remove configobj, which is redundant and causing local install issues on MacOS M1
* Drop backports.cached-property and typed-ast from dev reqs because we don't need them on 3.9
* Update docs with local-installation guidance for pyenv and pyenv-virtualenv
* Remove 'upgrade requirements' option
Given that the --upgrade flag is implicitly / by-default true with
pip-compile-multi anyway, plus the fact we're hard-pininng everything,
there's no point having an explicit 'upgrade' path - so let's remove it
* Docs tweak to suggest simpler virtualenv name
* Update help option in Makefile
* Pin version of pip in the compile-requirements script
When unpinned, the build suddenly broke, so we're keeping it under strict
limits for now
* Upgrade Django to 2.2.27
* Upgrade newrelic package to latest, incl py3.9 support
* Switch to Python 3.9 Debian bullseye image, from buster
* Rationalise dependency input files to remove over-pinned subdeps
When we moved from hand-managed requirements.txt files, we were taking on files
that had literally every dependency and thier sub-deps in them. We don't want
the input (*.in) files to reference those subdeps, so this changeset tries to
thin things out and remove them
Note that the diff shows this was successful - there are very few changes to
the dependencies being mentioned in the output *.txt files, and the ones that
are there are all deliberate changes (eg removing 'pbr')
* Drop unused tenacity dep, bump APScheduler and link to a Python 3.9-patched version of mdx-outline
* Add --require-hashes option to pip usage in Dockerfile
It's implicitly set because the reqs files feature --hash=XXX
but better to be explicit
* Drop what appear to be redundant top-level dev dependencies
regex, pep8 and wcwidth appear to be subdeps that don't need pinning.
The others appear to not be in used, based on a search of the codebase.
Tests till pass
* Thin out some unnecessary top-level deps in prod.in
- funcsigs - old backport, redundant
- lxml - over-pinned subdep of BeautifulSoup?
- typing_extensions - over-pinned subdep
- zipp - over-pinned subdep
* Cap pip version to 21 for pip-compile-multi for now
* Reinstate lxml as a first-class dep: BeautifulSoup needs it as a user-specified parser
* Fix typo in pip-compile-multi header
* Hard-pin latest working combo of pip + pip-tools in compile-requirements.sh
* Update docs explaining why we're using 3.9.10 locally
maureenlholland
Alex Gibson
Rob Hudson
Steve Jalim
Craig Cook
Reem H
Paul McLanahan
Moises Sanchez
Alan Alexander
Steve Jalim
dependabot[bot]
Sylvestre Ledru
Ayushsunny
Benjamin Beurdouche
Ed Lee