setuptools now depends on >=4.10 but our vendored package is preferred over its own vendored package. So this upgrades the existing one.
Differential Revision: https://phabricator.services.mozilla.com/D220865
Also instruct `mach` to use the vendored `glean_parser` instead of the one it
would otherwise pull down from `pip` as part of its `glean_sdk` dep.
This unfortunately ties updates of `mach`'s `glean_sdk` to any updates m-c gets
for its `glean_parser`. It's required to ensure `./mach build` always uses the
vendored `glean_parser` (see bug 1908020).
Differential Revision: https://phabricator.services.mozilla.com/D216717
Same rationale as vendoring of a recent version of `wheel`. We need it
in mozharness for `--no-use-pep517` so that we can use a recent `pip`,
so we'll update to a similar baseline to minimize issues.
Differential Revision: https://phabricator.services.mozilla.com/D211599
We need to use `wheel` in mozharness to use `--no-use-pep517` (so we can
use a modern `pip`). We don't explicitly need to upgrade `wheel`, but it
seems sensible to upgrade it to a similar baseline as both `pip` and
`setuptools` (which we also need are are upgrading with this stack).
Differential Revision: https://phabricator.services.mozilla.com/D211594
While nothing explicitly prompted updating this, letting `pip` and
`pip-tools` diverage too greatly in version release dates seems like
a bad idea, especially with the various deprecations in
`pip` and `python3.12`.
This also vendors the implicit dependencies `build`, `tomli`, and
`pyproject_hooks`.
Differential Revision: https://phabricator.services.mozilla.com/D210526
This is a bit of a hack to make it all work.
On every `submit` of a ping we call into `schedule_pings` to also
schedule ride-along pings.
Preferably we would like to have that in glean-core, but for builtin
pings that won't work because they are not code-generated and thus will
never see their `schedules_pings` array.
So instead we generate a function in m-c that does the mapping and call
that in the ping wrapper used inside m-c.
Another side effect: `testBeforeNextSubmit` callbacks from
JavaScript/C++ will _not_ be called, because they are only on the JS/C++
object and not reachable from the Rust parts where we actually submit the
ride-along pings.
Differential Revision: https://phabricator.services.mozilla.com/D209671
Update `aiohttp` to version 3.8.5 and `requests` to version 2.31.0,
and vendor their respective dependencies. Add all the new dependencies
to the various required site virtualenv requirements files.
Differential Revision: https://phabricator.services.mozilla.com/D188904
ManifestParser will read TOML files, if present, when use_toml=True
Added tomlkit as a third_party python package
Added poetry-core and tomlkit to pypi (separately as Bug 1845383, Bug 1844787)
Adds TOML test coverage
Adds tomlkit as a dependency of mozharness (in test_archive.py)
Added tomlkit to virtualenv_modules in testing/mozharness/configs/unittests
Removes dependency on six
testing/tools/mach_test_package_initialize.py
- Corrected SEARCH_PATHS
testing/mozharness/mozharness/mozilla/testing/per_test_base.py
- moved `from manifestparser import TestManifest` into function call
to avoid harness inability to locate the internal artifact
- Removed linter warnings
testing/mozbase/manifestparser/manifestparser/manifestparser.py
- Removed linter warnings
- Updated logger usage pattern
- Simplifed _read logic, refactored get_fp_filename()
- Improve context for `include:` logging message
- Defer `import mozlog` until the point of use
testing/mozbase/manifestparser/manifestparser/toml.py
- Removed linter warnings
- Removed unused logger
- Improved readability of read_toml()
testing/mozbase/manifestparser/manifestparser/ini.py
- Removed linter warnings
- Removed unused logger
testing/mozbase/manifestparser/manifestparser/filters.py
- Removed linter warnings
testing/mozbase/manifestparser/tests/test_chunking.py
- Removed linter warnings
Bumped manifestparser version to 2.2.31
Differential Revision: https://phabricator.services.mozilla.com/D184020