Skip to content

Conversation

d4l3k
Copy link
Member

@d4l3k d4l3k commented May 5, 2021

Summary: This adds the standard python .gitignore file from https://github.com/github/gitignore/blob/master/Python.gitignore.

Differential Revision: D28231530

Summary: This adds the standard python .gitignore file from https://github.com/github/gitignore/blob/master/Python.gitignore.

Differential Revision: D28231530

fbshipit-source-id: 4630ff5787e311073d6b2323476d958e989d0fab
@facebook-github-bot facebook-github-bot added CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. fb-exported labels May 5, 2021
@facebook-github-bot
Copy link
Contributor

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

@d4l3k d4l3k assigned d4l3k and kiukchung and unassigned d4l3k May 5, 2021
@d4l3k d4l3k requested a review from kiukchung May 5, 2021 19:45
@d4l3k d4l3k closed this May 5, 2021
facebook-github-bot pushed a commit that referenced this pull request Oct 5, 2021
…inding penv.par, add a CWD/penv.par search fallback to handle unittest @mode/opt (#216)

Summary:
Pull Request resolved: #216

Fixes the following two scenarios:

#1
```
~/bin
    - python
    - penv.par

$ cd ~/bin
$ ./python -m mo.du.le
```
Does not pick up `~/bin/penv.par` (as expected) because `sys.argv[0] = ./python`. Fix is to return `(Path(sys.argv[0])/"penv.par").absolute() `

#2
Using this interpreter as a unittest resource + torchx local_cwd scheduler does not resolve penv.par from the test source dir since the symlink is resolved by unix and `sys.argv[0]` is set to the actual interpreter (not the symlinked one)
```
python_unittest(
   name="foo_test",
   resource={
       "//torchx/fb:python": "python",
       "//torchx/apps:penv": "penv.par",
   }
   ...
)

# buck run mode/opt //foo_test
# outputs in build dir

~/fbcode/buck-out/opt/gen/foo_test#link-tree/
    - python -> buck-out/opt/gen/torchx/fb/python.par
    - penv.par
```
Hence with the current penv par lookup logic we end up looking for a penv.par in `buck-out/opt/gen/torchx/fb/penv.par` which does not exist and we just simply fall back to system python.

Reviewed By: aivanou

Differential Revision: D31402466

fbshipit-source-id: 257d9aa53033a306f3e8fa2653ccc6ba7089d90d
facebook-github-bot pushed a commit that referenced this pull request Mar 28, 2025
Summary:
I fixed doc-build in #1033 by:

1. pinning `protobuf-3.20.x` in torchx's `dev-requirements.txt` since `apache-airflow` (defined in `docs/requirements.txt`) was upgrading to `protobuf>=5.x` which is incompatible with `kfp-1.8.x`.
2. installing `doc/requirements.txt` FIRST, then installing `torchx` so that the pinned version of `protobuf` is honored.

The above fixes `doc-build` but not `doc-push` because `doc-push` runs `scripts/doc-push.sh` which needed the same change as #2.

Differential Revision: D72059926
@kiukchung kiukchung mentioned this pull request Mar 28, 2025
kiukchung added a commit that referenced this pull request Mar 28, 2025
Summary:

I fixed doc-build in #1033 by:

1. pinning `protobuf-3.20.x` in torchx's `dev-requirements.txt` since `apache-airflow` (defined in `docs/requirements.txt`) was upgrading to `protobuf>=5.x` which is incompatible with `kfp-1.8.x`.
2. installing `doc/requirements.txt` FIRST, then installing `torchx` so that the pinned version of `protobuf` is honored.

The above fixes `doc-build` but not `doc-push` because `doc-push` runs `scripts/doc-push.sh` which needed the same change as #2.

NOTE: this wasn't caught in #1033 because we don't run `doc-push` for PRs (doc-push only runs for releases and commits in trunk since it literally pushes the built docs to https://pytorch.org/torchx)

Differential Revision: D72059926
kiukchung added a commit that referenced this pull request Mar 28, 2025
Summary:
Pull Request resolved: #1034

I fixed doc-build in #1033 by:

1. pinning `protobuf-3.20.x` in torchx's `dev-requirements.txt` since `apache-airflow` (defined in `docs/requirements.txt`) was upgrading to `protobuf>=5.x` which is incompatible with `kfp-1.8.x`.
2. installing `doc/requirements.txt` FIRST, then installing `torchx` so that the pinned version of `protobuf` is honored.

The above fixes `doc-build` but not `doc-push` because `doc-push` runs `scripts/doc-push.sh` which needed the same change as #2.

NOTE: this wasn't caught in #1033 because we don't run `doc-push` for PRs (doc-push only runs for releases and commits in trunk since it literally pushes the built docs to https://pytorch.org/torchx)

Differential Revision: D72059926
kiukchung added a commit that referenced this pull request Mar 28, 2025
Summary:
Pull Request resolved: #1034

I fixed doc-build in #1033 by:

1. pinning `protobuf-3.20.x` in torchx's `dev-requirements.txt` since `apache-airflow` (defined in `docs/requirements.txt`) was upgrading to `protobuf>=5.x` which is incompatible with `kfp-1.8.x`.
2. installing `doc/requirements.txt` FIRST, then installing `torchx` so that the pinned version of `protobuf` is honored.

The above fixes `doc-build` but not `doc-push` because `doc-push` runs `scripts/doc-push.sh` which needed the same change as #2.

NOTE: this wasn't caught in #1033 because we don't run `doc-push` for PRs (doc-push only runs for releases and commits in trunk since it literally pushes the built docs to https://pytorch.org/torchx)

Differential Revision: D72059926
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. fb-exported
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants