Move TorchDispatchModeTLS to c10/core

[ezyang]

Stack from ghstack (oldest at bottom):

• Convert SymInt tracing to mode based tracing #83380
• Respect TorchDispatchMode for shallow_copy_and_detach #83372
• -> Move TorchDispatchModeTLS to c10/core #83370

I need to access it directly from TensorImpl to route directly
TensorImpl induced operations to modes (upcoming PR).

Signed-off-by: Edward Z. Yang ezyang@fb.com

[facebook-github-bot]

🔗 Helpful links

• 🧪  See artifacts and rendered test results at hud.pytorch.org/pr/83370
• 📄  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 our office hours
• ↩️  [fb-only] Re-run with SSH instructions

❌ 3 New Failures

As of commit ee2767c (more details on the Dr. CI page):

Expand to see more

---

• 3/3 failures introduced in this PR

---

🕵️ 2 new failures recognized by patterns

The following CI failures do not appear to be due to upstream breakages

pull / win-vs2019-cpu-py3 / test (default, 2, 2, windows.4xlarge) (1/2)

Step: "Test" (full log | diagnosis details)

2022-08-15T15:10:15.1506768Z RuntimeError: test_ops_jit failed!

2022-08-15T15:10:14.7776676Z   File "C:\actions-runner\_work\pytorch\pytorch\build\win_tmp\build\torch\testing\_internal\common_utils.py", line 634, in run_tests
2022-08-15T15:10:14.7777054Z     os.environ['DISABLED_TESTS_DICT'] = fp.read()
2022-08-15T15:10:14.7777364Z   File "C:\Jenkins\Miniconda3\lib\os.py", line 685, in __setitem__
2022-08-15T15:10:14.7869995Z     putenv(key, value)
2022-08-15T15:10:14.7870297Z ValueError: the environment variable is longer than 32767 characters
2022-08-15T15:10:15.1499700Z Traceback (most recent call last):
2022-08-15T15:10:15.1500159Z   File "C:\actions-runner\_work\pytorch\pytorch\test\run_test.py", line 990, in <module>
2022-08-15T15:10:15.1503367Z     main()
2022-08-15T15:10:15.1503782Z   File "C:\actions-runner\_work\pytorch\pytorch\test\run_test.py", line 968, in main
2022-08-15T15:10:15.1506505Z     raise RuntimeError(err_message)
2022-08-15T15:10:15.1506768Z RuntimeError: test_ops_jit failed!
2022-08-15T15:10:15.3671601Z 
2022-08-15T15:10:15.3672124Z (base) C:\actions-runner\_work\pytorch\pytorch\test>if ERRORLEVEL 1 goto fail 
2022-08-15T15:10:15.3674374Z 
2022-08-15T15:10:15.3674604Z (base) C:\actions-runner\_work\pytorch\pytorch\test>exit /b 1 
2022-08-15T15:10:15.3726391Z ##[error]Process completed with exit code 1.
2022-08-15T15:10:15.3852844Z Prepare all required actions
2022-08-15T15:10:15.3853318Z Getting action download info
2022-08-15T15:10:15.5862488Z Download action repository 'nick-fields/retry@71062288b76e2b6214ebde0e673ce0de1755740a' (SHA:71062288b76e2b6214ebde0e673ce0de1755740a)
2022-08-15T15:10:15.8636291Z ##[group]Run ./.github/actions/get-workflow-job-id
2022-08-15T15:10:15.8636520Z with:

pull / win-vs2019-cpu-py3 / test (default, 1, 2, windows.4xlarge) (2/2)

Step: "Test" (full log | diagnosis details)

2022-08-15T15:10:36.5758773Z RuntimeError: test_ops failed!

2022-08-15T15:10:35.7702354Z   File "C:\actions-runner\_work\pytorch\pytorch\build\win_tmp\build\torch\testing\_internal\common_utils.py", line 634, in run_tests
2022-08-15T15:10:35.7702744Z     os.environ['DISABLED_TESTS_DICT'] = fp.read()
2022-08-15T15:10:35.7703093Z   File "C:\Jenkins\Miniconda3\lib\os.py", line 685, in __setitem__
2022-08-15T15:10:35.7801021Z     putenv(key, value)
2022-08-15T15:10:35.7801293Z ValueError: the environment variable is longer than 32767 characters
2022-08-15T15:10:36.5751627Z Traceback (most recent call last):
2022-08-15T15:10:36.5752134Z   File "C:\actions-runner\_work\pytorch\pytorch\test\run_test.py", line 990, in <module>
2022-08-15T15:10:36.5755207Z     main()
2022-08-15T15:10:36.5755505Z   File "C:\actions-runner\_work\pytorch\pytorch\test\run_test.py", line 968, in main
2022-08-15T15:10:36.5758530Z     raise RuntimeError(err_message)
2022-08-15T15:10:36.5758773Z RuntimeError: test_ops failed!
2022-08-15T15:10:36.8454453Z 
2022-08-15T15:10:36.8455201Z (base) C:\actions-runner\_work\pytorch\pytorch\test>if ERRORLEVEL 1 goto fail 
2022-08-15T15:10:36.8456687Z 
2022-08-15T15:10:36.8457098Z (base) C:\actions-runner\_work\pytorch\pytorch\test>exit /b 1 
2022-08-15T15:10:36.8513018Z ##[error]Process completed with exit code 1.
2022-08-15T15:10:36.8652283Z Prepare all required actions
2022-08-15T15:10:36.8652822Z Getting action download info
2022-08-15T15:10:37.0277050Z Download action repository 'nick-fields/retry@71062288b76e2b6214ebde0e673ce0de1755740a' (SHA:71062288b76e2b6214ebde0e673ce0de1755740a)
2022-08-15T15:10:37.2317740Z ##[group]Run ./.github/actions/get-workflow-job-id
2022-08-15T15:10:37.2317985Z with:

---

🕵️‍♀️ 1 failure not recognized by patterns:

The following CI failures may be due to changes from the PR

Job	Step
win-vs2019-cpu-py3 / test (functorch, 1, 1, windows.4xlarge)	Unknown

---

This comment was automatically generated by Dr. CI (expand for details).

Please report bugs/suggestions to the (internal) Dr. CI Users group.

Click here to manually regenerate this comment.

[ezyang]

@pytorchbot merge

[pytorchmergebot]

@pytorchbot successfully started a merge job. Check the current status here.
The merge job was triggered without a flag. This means that your change will be merged once all checks on your PR have passed (ETA: 0-4 Hours). If this is not the intended behavior, feel free to use some of the other merge options in the wiki.
Please reach out to the PyTorch DevX Team with feedback or questions!

[pytorchmergebot]

Merge failed due to Refusing to merge as mandatory check(s) pull failed for rule superuser
Raised by https://github.com/pytorch/pytorch/actions/runs/2861338744

[ezyang]

@pytorchbot merge -f "known windows outage"

[pytorchmergebot]

@pytorchbot successfully started a merge job. Check the current status here.
The merge job was triggered with the force (-f) flag. This means your change will be merged immediately, bypassing any CI checks (ETA: 1-5 minutes). If this is not the intended behavior, feel free to use some of the other merge options in the wiki.
Please reach out to the PyTorch DevX Team with feedback or questions!

[github-actions]

Hey @ezyang.
You've committed this PR, but it does not have both a 'release notes: ...' and 'topics: ...' label. Please add one of each to the PR. The 'release notes: ...' label should represent the part of PyTorch that this PR changes (fx, autograd, distributed, etc) and the 'topics: ...' label should represent the kind of PR it is (not user facing, new feature, bug fix, perf improvement, etc). The list of valid labels can be found here for the 'release notes: ...' and here for the 'topics: ...'.
For changes that are 'topic: not user facing' there is no need for a release notes label.