Skip to content

Fix et_replay install in the Python Linting workflow - #225

Closed
sunguobao wants to merge 1 commit into
facebookresearch:mainfrom
sunguobao:export-D127034812
Closed

sunguobao wants to merge 1 commit into
facebookresearch:mainfrom
sunguobao:export-D127034812

Conversation

@sunguobao

Copy link
Copy Markdown
Contributor

Summary:
The Python Linting workflow has failed on every pull request since et_replay/pyproject.toml changed its package-dir from . to et_replay (#210). That value is right for meta-pytorch/chakra_replay, where pyproject.toml sits at the repository root above the et_replay/ package. In this repository pyproject.toml lives inside the package directory, so pip install et_replay/ fails with error: package directory 'et_replay' does not exist.

  • Install et_replay from a copy staged in the chakra_replay layout, rather than changing pyproject.toml, which chakra_replay also uses.
  • Import ExecutionTrace from et_replay.execution_trace. The same change emptied the package __init__.py, so from et_replay import ExecutionTrace no longer works.

Differential Revision: D127034812

Summary:
The `Python Linting` workflow has failed on every pull request since `et_replay/pyproject.toml` changed its `package-dir` from `.` to `et_replay` (facebookresearch#210). That value is right for meta-pytorch/chakra_replay, where `pyproject.toml` sits at the repository root above the `et_replay/` package. In this repository `pyproject.toml` lives inside the package directory, so `pip install et_replay/` fails with `error: package directory 'et_replay' does not exist`.

- Install et_replay from a copy staged in the chakra_replay layout, rather than changing `pyproject.toml`, which chakra_replay also uses.
- Import `ExecutionTrace` from `et_replay.execution_trace`. The same change emptied the package `__init__.py`, so `from et_replay import ExecutionTrace` no longer works.

Differential Revision: D127034812
@meta-cla meta-cla Bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Oct 22, 2026
@meta-codesync

meta-codesync Bot commented Oct 22, 2026

Copy link
Copy Markdown

@sunguobao has exported this pull request. If you are a Meta employee, you can view the originating Diff in D127034812.

@meta-codesync

meta-codesync Bot commented Oct 23, 2026

Copy link
Copy Markdown

This pull request has been merged in 985ae34.

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. Merged meta-exported

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant