[Environment Variable][7/N] Use thread-safe getenv functions

[cyyever]

Fixes #ISSUE_NUMBER

cc @H-Huang @awgu @kwen2501 @wanchaol @fegin @fduwjj @wz337 @wconstab @d4l3k @c-p-i-o @EikanWang @jgong5 @wenzhe-nrv @sanchitintel @malfet @zou3519 @xmfan

[pytorch-bot]

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/140211

• 📄 Preview Python docs built from this PR
• 📄 Preview C++ docs built from this PR
• ❓ Need help or want to give feedback on the CI? Visit the bot commands wiki or our office hours

Note: Links to docs will display an error until the docs builds have been completed.

❌ 3 New Failures

As of commit f79cec6 with merge base dcc32ff ():

NEW FAILURES - The following jobs have failed:

• pull / linux-docs / build-docs-cpp-false (gh)
  Process completed with exit code 9.
• pull / linux-docs / build-docs-functorch-false (gh)
  Process completed with exit code 9.
• pull / linux-docs / build-docs-python-false (gh)
  Process completed with exit code 9.

This comment was automatically generated by Dr. CI and updates every 15 minutes.

[ezyang]

@pytorchbot merge

[pytorchmergebot]

Merge started

Your change will be merged once all checks pass (ETA 0-4 Hours).

Learn more about merging in the wiki.

Questions? Feedback? Please reach out to the PyTorch DevX Team

Advanced Debugging

Check the merge workflow status
here

[malfet]

I think I left this comment in the past, but there are no such thing as thread safe getenv. If someone will modify environment variable using POSIX setenv call, all of those changes will not protect PyTorch from returning gargbage

[ezyang]

@pytorchbot revert -c nosignal -m "One of these diffs had incorrect downstream optional handling, we must reaudit all of these diffs"

[pytorchmergebot]

@pytorchbot successfully started a revert job. Check the current status here.
Questions? Feedback? Please reach out to the PyTorch DevX Team

[atalman]

Looks like following tests failing:
https://github.com/pytorch/executorch/blob/main/extension/aten_util/aten_bridge.cpp
https://github.com/pytorch/executorch/blob/main/extension/llm/sampler/sampler.cpp
https://github.com/pytorch/executorch/blob/main/extension/pytree/aten_util/test/ivalue_util_test.cpp

Error looks like:
libc++abi: terminating due to uncaught exception of type std::__1::system_error: mutex lock failed: Invalid argument

[cyyever]

@pytorchmergebot merge -f "Unrelated failures"

[pytorchmergebot]

Merge started

Your change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes). Please use -f as last resort and instead consider -i/--ignore-current to continue the merge ignoring current failures. This will allow currently pending tests to finish and report signal before the merge.

Learn more about merging in the wiki.

Questions? Feedback? Please reach out to the PyTorch DevX Team

Advanced Debugging

Check the merge workflow status
here