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

client: don't send "web prefs" in scheduler requests. #5082

Merged
merged 1 commit into from
Feb 7, 2023

Conversation

davidpanderson
Copy link
Contributor

This was originally done to propagate prefs between projects.
When you edit prefs on project A, they propagate to project B and you can edit them there too.
But this doesn't make sense - and can lead to undesirable behavior - when projects
have different prefs-editing web code.
And it's not a particularly useful feature.
If you're using web prefs, the Manager tells you what project they came from.
You can go there to edit them.

Note: we still send working prefs,, which are used for scheduler decisions.

This was originally done to propagate prefs between projects.
When you edit prefs on project A,
they propagate to project B and you can edit them there too.
But this doesn't make sense - and can lead to undesirable behavior -
when projects have different prefs-editing web code.
And it's not a particularly useful feature.
If you're using web prefs, the Manager tells you what project they came from.
You can go there to edit them.

Note: we still send working prefs, which are used for scheduler decisions.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants