Cristian Le
Cristian Le
This is the first example case of how the sphinx tmt domain is utilized. Depends on: https://github.com/teemtee/tmt/pull/4287
When working on `Lmod`, I've found the need to source `/etc/profile.d/modules.sh` which is not sourced by default because the scripts are not run as interactive mode. The proposal here would...
Could we track why we need a custom `Path` object? Reading the docstring, isn't `pathlib.Path.relative_to(walk_up=True)` what is needed there?
Let's start looking in how we can start using `uv.lock` files. We probably cannot use it in pre-commit and such, but let's see how we can make use of it...
This is mostly to cleanup some interfaces that we would not use. In retrospect this is important to cleanup because the user should not be allowed to use `provide: koji:xyz`
This sphinx domain has a few major components: - [x] Directives to define the tmt objects we document - [x] Index of all tmt objects we have documented - [x]...
This is quite a nasty hidden issue. Because both sphinx and tmt are using annotations, if sphinx imports tmt first, it will affect the code when we actually want to...
I haven't checked that it works, but my understanding is that this is one way to check the plugin type of a particular step: ```python # Check that there is...
Seeing `requre` in action, I think it would a very good asset for our test suite to guarantee we are using some realistic requests. It basically does one real request...
Some relevant places where it clashes: https://github.com/teemtee/tmt/blob/ba13b63bec89fd40155fde8c14cb226f639dae55/tmt/base.py#L1937-L1942 Caught this when working on some refactoring