-
Notifications
You must be signed in to change notification settings - Fork 512
Document environment variables #4273
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
Conversation
configuration.yaml
Outdated
- Verbosity level for GRPC, e.g. INFO, ERROR, etc. | ||
type: string | ||
default_value: "ERROR" | ||
TPU_ML_PLATFORM: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lol I felt like we should not make this configurable
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder if we should include it here for the sake of documentation, and remark that it shouldn't be changed. My intention in including it was just to cover every environment variable that shows up in this repo.
Line 66 in f858155
_set_missing_env('TPU_ML_PLATFORM', 'PyTorch/XLA') |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mostly LGTM. Thanks for putting this together! Is it possible to group similar env var for better reading expericence?
For example we can split them into
- XRT related
- Build related
- Debug related
- Feature enablement
- Device configuration
- Distributed related
- ...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wow! Thanks for laying all of this out. LGTM at least for the variables I know about
I agree with Jack's comment that it would be clearer if you categorized the variables, especially separating the build-time variables from the run-time variables and separating the XRT configuration from the rest.
@JackCaoG Do we also want some designation of which variables are stable and which might get removed in the future? Or are we committed to actually supporting all of these?
fd335cc
to
77cfea1
Compare
yea I think in this or I am fine with only group them by cateratory. We can update it based on stable/to_be_removed in a follow up pr. |
77cfea1
to
e79223b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
Created a yaml file that captures all relevant environment variables with description, type, and default value.
Variables are grouped into the following: