[Kineto][Profiler] Guard event metadata python thread via verbose flag

[aaronenyeshi]

Summary: For Python Tracing enabled trace files, this field "python thread": 0 is repeated for every python_function event. This bloats the trace json size for large number of events or deep call stacks. Instead make this metadata guarded by the verbose flag.

Test Plan: CI

Reviewed By: robieta, slgong-fb

Differential Revision: D40325815

Pulled By: aaronenyeshi

[pytorch-bot]

🔗 Helpful Links

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

• 📄 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

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

❗ 2 Active SEVs

There are 2 currently active SEVs. If your PR is affected, please view them below:

• Conda ChecksumMismatchError error blocking CI jobs
• Run Simulator Tests fails with Segmentation Fault #87207

❌ 1 Failures

As of commit df9918a:

The following jobs have failed:

• macos-12-py3-arm64 / build

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

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: aaronenyeshi / name: Aaron Shi (d2fd306)

[facebook-github-bot]

This pull request was exported from Phabricator. Differential Revision: D40325815

[facebook-github-bot]

This pull request was exported from Phabricator. Differential Revision: D40325815

[aaronenyeshi]

@pytorchbot rebase -b viable/strict

[pytorchmergebot]

@pytorchbot successfully started a rebase job. Check the current status here

[pytorchmergebot]

Tried to rebase and push PR #87096, but it was already up to date

[facebook-github-bot]

This pull request was exported from Phabricator. Differential Revision: D40325815

[facebook-github-bot]

This pull request was exported from Phabricator. Differential Revision: D40325815

[aaronenyeshi]

@pytorchmergebot merge -f

[pytorch-bot]

❌ 🤖 pytorchbot command failed:

@pytorchbot merge: error: argument -f/--force: expected one argument

usage: @pytorchbot merge [-g | -f MESSAGE | -l] [-r [{viable/strict,master}]]

Try @pytorchbot --help for more info.

[aaronenyeshi]

@pytorchmergebot merge -f The 1 failing check is unrelated to this diff, it looks like some timeout on MacOS downloading a file.

[pytorch-bot]

❌ 🤖 pytorchbot command failed:

@pytorchbot: error: unrecognized arguments: 1 failing check is unrelated to this diff, it looks like some timeout on MacOS downloading a file.

usage: @pytorchbot [-h] {merge,revert,rebase,label} ...

Try @pytorchbot --help for more info.

[aaronenyeshi]

@pytorchmergebot merge -f "The 1 failing check is unrelated to this diff, it looks like a timeout on MacOS downloading a file."

[pytorchmergebot]

Merge started

Your change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes).

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

[github-actions]

Hey @aaronenyeshi.
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.