зеркало из https://github.com/mozilla/gecko-dev.git
73710e3148
After removing `optional` in Bug 1712804, we need to add a variant back here because there's fallible dependencies. However, I've tweaked the re-introduction of the feature to require a specific repercussion message as well. This seemed like a decent tradeoff - the developer becomes aware that the failure is bad, it has repercussions, but it's not a blocking issue. Additionally, since we're printing pip's output, the developer will be able to see the underlying error causing the warning. I also added comment functionality to requirements definitions to allow adjacent documentation of why some requirements are fallible. (Related: I'm looking forward to `mach_bootstrap` not needing to parse requirements definitions. Almost there!) Note that we'll temporarily lose the "pinned" nature of the three moved dependencies until dependency locking is implemented for Mach requirements definitions. Also note that the pinned `zstandard_requirements.txt` can't be removed like the other files because it still has a dangling usage. Finally, in preparation for review: I didn't make `PypiOptionalSpecifier` extend `PypiSpecifier` because I figured that the benefit of flexibility (easier to allow implementations to diverge without needing to untangle an inheritance relationship) was larger than the cost of needing to add properties to both specifiers. If we wanted re-use, I'd probably have `PypiOptionalSpecifier` _contain_ a `PypiSpecifier`, but then you have to reach deeper into the object to get data, so *shrug*. Differential Revision: https://phabricator.services.mozilla.com/D119835 |
||
|---|---|---|
| .. | ||
| docker-image | ||
| github-sync | ||
| liblowercase | ||
| mach | ||
| mozharness | ||
| perftest | ||
| profile-generate | ||
| push-to-try | ||
| sphinx-docs | ||
| taskgraph | ||
| toolchain-build | ||
| tps | ||
| update-verify | ||
| upload-generated-sources | ||
| upload-symbols | ||
| webrender | ||
| wgpu | ||