Yes, we can default to a location within a repo and use defaut configuration mechanism, but would need a way to point to some external config which will be version-controlled elsewhere. Suppose som...
We have it for all e2e tests for all package managers, so at least for consistency, I would add it. We can discuss it when we put all integration tests into a single repo. That should be a good sta...
> And how about the SBOM from e2e tests ?
Do we need it? The logic of SBOM generation is pretty static and well-tested with UTs (97+% coverage is no joke). The tests check that bundler can build...
I think we'll just use/enhance the existing [config-file functionality](https://github.com/containerbuildsystem/cachi2?tab=readme-ov-file#configuration), right?
# Maintainers will complete the following section
- [ ] Commit messages are descriptive enough
- [ ] Code coverage from testing does not decrease and new code is covered
- [ ] Docs updated (if...
> If I read the link correctly this is a different platform: not a platform a gem is compiled to, but a Ruby implementation. The given example explicitly mentions JRuby.
Okay. So we can probably...
What do you think about splitting the test in two: a positive and a negative test?
```python
@mark.parametrize("url",
["https://foo.com/bar.tgz", ...
],
)
def test__is_tarball_url_can_par...
> should be taken care of with an after model validator (as field validators must take attribute order validation into consideration and so are painful to deal with) OR maybe there's a callback for...
It would, but I know that these lockfiles won't be small and could go up to a couple thousand. I think that having a little more complicated code to achieve parallel download is worth it in this case.