fix(backend): del en_US.UTF-8 locale requirement #463
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rezib
force-pushed
the
pr/fix-432
branch
2 times, most recently
from
52e4f4a to
1ece17b
Compare
Remove abusive en_US.UTF-8 hardcoded locale requirement for agent and gateway uwsgi services. These services should work on all systems with correct systems locales that match loaded files encoding. There is no reason to require en_US.UTF-8 specifically. fix #432
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Remove abusive en_US.UTF-8 hardcoded locale requirement for agent and gateway uwsgi services. These services should work on all systems with correct systems locales that match loaded files encoding. There is no reason to require en_US.UTF-8 specifically.
fix #432