| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
Use python location in cache key used by Breeze (#29947) Pipx installation is cached between runs and it should use python location in order to not reuse cache between different python versions, otherwise pipx installation might fail. | 3 年前 | |
| 3 年前 | ||
| 3 年前 | ||
Remove stderr redirection for get-workflow-info (#29381) The #28514 change added capability of getting trace errors for the command by swapping redirection of stderr and stdout, but debug output for github_output file remoined in stderr. This was no problem in most cases as rich did not produce color codes for stderr redirection and github_output was able to parse it properly - and each line in the GITHHUB_OUTPUT was simply duplicated. However, when number of labels was big, rich split the message and it caused Invalid format message. | 3 年前 | |
| 3 年前 | ||
Fix integration with codecov (#29145) | 3 年前 | |
Proper Python Host output from composite tasks in CI (#28254) When we separated actions into composite workflows in #27369 and the #27371 we missed the fact that there was a step passing the host python version to static checks - to make sure we start with a fresh cache every time new python version is changed (this caused problems in the past) The "host-python-version" was therefore empty and not really used in the cache key determining. This has no bad effect when Python version does not change but when there is an upgrade of Python, the symbolic links in stored cache get broken, and next time new Python version is used in the AMIs, we might get them broken, so better to fix it now. | 3 年前 | |
SagemakerProcessingOperator stopped honoring existing_jobs_found (#27456) | 3 年前 | |
Run "third party" github actions from submodules instead (#13514) Rather than having to mirror all the repos we can instead use git submodules to pull in the third party actions we want to use - with recent(ish) changes in review for submodules on GitHub we still get the same "review/audit" visibility for changes, but this way we don't have to either "pollute" our repo with the actions code, nor do we have to maintain a fork of the third party action. | 5 年前 |
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
| 3 年前 | ||
| 3 年前 | ||
| 3 年前 | ||
| 3 年前 | ||
| 3 年前 | ||
| 3 年前 | ||
| 3 年前 | ||
| 3 年前 | ||
| 5 年前 |