IF YOU WOULD LIKE TO GET AN ACCOUNT, please write an
email to Administrator. User accounts are meant only to access repo
and report issues and/or generate pull requests.
This is a purpose-specific Git hosting for
BaseALT
projects. Thank you for your understanding!
Только зарегистрированные пользователи имеют доступ к сервису!
Для получения аккаунта, обратитесь к администратору.
psutil will fail to import on el6 due to not being able to access a
pseudo terminal. This issues a SIGKILL to the proot process in order to
force the stop
Previously we could just check for the absence of the stdout file to
know we didn't yet/wouldn't ever have any stdout content. Now that we
are creating the stdout file ahead of time and persisting it we need to
also check to see if the file contains any data. This is also
necessary for some unit tests.
The act of committing a PR that including part of these changes and then
reverting it meant that some of the changes from the original branch
didn't land in this new PR. This commit adds the missing bits.
Lesson learned: Create a new branch when submitting a PR on a
previously reverted PR
* Cleanup old code related to stdout download using temporary files
* Remove copy-into-database code
* Modify stdout download code to reference stdout file
psutil will fail to import on el6 due to not being able to access a
pseudo terminal. This issues a SIGKILL to the proot process in order to
force the stop
Previously we could just check for the absence of the stdout file to
know we didn't yet/wouldn't ever have any stdout content. Now that we
are creating the stdout file ahead of time and persisting it we need to
also check to see if the file contains any data. This is also
necessary for some unit tests.
The act of committing a PR that including part of these changes and then
reverting it meant that some of the changes from the original branch
didn't land in this new PR. This commit adds the missing bits.
Lesson learned: Create a new branch when submitting a PR on a
previously reverted PR
* Cleanup old code related to stdout download using temporary files
* Remove copy-into-database code
* Modify stdout download code to reference stdout file
Our old check used an extremely inefficient boolean logic AND and
generated a bad query. This does a simpler check by querying the
inventories that the user has access to and using that as a simple
condition when performing the job template permission query