-
Notifications
You must be signed in to change notification settings - Fork 11
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
Comments
This still seems relevant to |
@iLLiCiTiT @antirotor what do you think of the proposal? |
I would say this should be defined by ayon-core, and not deadline. But until this is implemented, it should be set in deadline. |
But - isn't basically anything running in Deadline |
And should deadline know about |
I see - so, we need some logic in core that is capable of disabling this automatically when needed? |
Maybe we should allow colored output only in AYON launcher process and don't use colors when headless mode is enabled? |
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. :') |
Describe the issue
Currently Deadline submissions pass along
OPENPYPE_LOG_NO_COLORS
per host per job asEnvironmentKeyValue
in the Job's info. However Deadline Job log viewer doesn't support custom coloring so all jobs running through Deadline should run withOPENPYPE_LOG_NO_COLORS=1
Proposal
I propose to remove submitting along
OPENPYPE_LOG_NO_COLORS
per job but instead setOPENPYPE_LOG_NO_COLORS=1
in theGlobalJobPreLoad.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]
The text was updated successfully, but these errors were encountered: