Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deadline: Avoid submitting along OPENPYPE_LOG_NO_COLORS #3

Open
BigRoy opened this issue Sep 2, 2022 · 8 comments
Open

Deadline: Avoid submitting along OPENPYPE_LOG_NO_COLORS #3

BigRoy opened this issue Sep 2, 2022 · 8 comments
Assignees
Labels
type: maintenance Changes to the code that don't affect product functionality (Technical debt, refactors etc.))

Comments

@BigRoy
Copy link
Contributor

BigRoy commented Sep 2, 2022

Describe the issue

Currently Deadline submissions pass along OPENPYPE_LOG_NO_COLORS per host per job as EnvironmentKeyValue in the Job's info. However Deadline Job log viewer doesn't support custom coloring so all jobs running through Deadline should run with OPENPYPE_LOG_NO_COLORS=1

Proposal

I propose to remove submitting along OPENPYPE_LOG_NO_COLORS per job but instead set OPENPYPE_LOG_NO_COLORS=1 in the GlobalJobPreLoad.py of the Deadline module whenever it has detected that it's running a OpenPype job.

This would reduce the data send per jobs + reduce the logic required per submission.

Additional Info

Brought up on OpenPype Discord here

[cuID:OP-3897]

@BigRoy BigRoy transferred this issue from ynput/OpenPype Jul 8, 2024
@BigRoy
Copy link
Contributor Author

BigRoy commented Jul 8, 2024

This still seems relevant to ayon-deadline yet the variable is called AYON_LOG_NO_COLORS.

@jakubjezek001 jakubjezek001 added the type: maintenance Changes to the code that don't affect product functionality (Technical debt, refactors etc.)) label Sep 19, 2024
@BigRoy
Copy link
Contributor Author

BigRoy commented Sep 19, 2024

I propose to remove submitting along OPENPYPE_LOG_NO_COLORS per job but instead set OPENPYPE_LOG_NO_COLORS=1 in the GlobalJobPreLoad.py of the Deadline module whenever it has detected that it's running a OpenPype job.

This would reduce the data send per jobs + reduce the logic required per submission.

@iLLiCiTiT @antirotor what do you think of the proposal?

@iLLiCiTiT
Copy link
Member

I would say this should be defined by ayon-core, and not deadline. But until this is implemented, it should be set in deadline.

@BigRoy
Copy link
Contributor Author

BigRoy commented Sep 20, 2024

But - isn't basically anything running in Deadline AYON_LOG_NO_COLORS=1 - so instead of passing it from anywhere to the job, we could just handle this in globaljobpreload to always set it?

@iLLiCiTiT
Copy link
Member

And should deadline know about AYON_LOG_NO_COLORS? It is environment related to ayon-core, if ayon-core changes the terminal colors logic, then deadline is behind.

@BigRoy
Copy link
Contributor Author

BigRoy commented Sep 20, 2024

I see - so, we need some logic in core that is capable of disabling this automatically when needed?

@iLLiCiTiT
Copy link
Member

Maybe we should allow colored output only in AYON launcher process and don't use colors when headless mode is enabled?

@BigRoy
Copy link
Contributor Author

BigRoy commented Sep 20, 2024

I mean - a headless mode is exactly the type of mode that could benefit from colorization if the console supports it. So not sure if that's the best way to do that. Unless there are just very few consoles that actually support that. :')

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: maintenance Changes to the code that don't affect product functionality (Technical debt, refactors etc.))
Projects
None yet
Development

No branches or pull requests

3 participants