Dave Bort

This PR seems to have picked up a release-cut commit, pulling in some yaml changes. @manuelcandales please rebase your dequantize-schema-compatibility branch on top of the latest `release/0.2` branch and re-push.

@guangy10 doh, the `torch==2.3` is breaking assumptions in the CI environment. This is the requirement that we need when we release, but right now it can't be fulfilled. I updated...

I'm not sure why the lint job is failing. Some of the suggestions it's giving look wrong, and I don't see those same suggestions when running locally. I'm re-running the...

Trying to reinstate the `torch==2.3` dependency in https://github.com/pytorch/executorch/pull/3277

Thanks for reporting this @bryangarza. Could you also let us know which `executorch` git commit hash you checked out when running this?

Yes, the problem here seems to be that python is executing the .py files under your `executorch` directory instead of using the files installed by the `pip` package. The old...

@adonnini That is the correct way to install the pip package. But the problems you're seeing are probably related to how you're running the failing program. Earlier you said >...

Thanks for that, @adonnini. When you run this command, what is your current directory? Does that directory contain a directory named `executorch`, which contains the ExecuTorch repo?

Link to landed trunk PR: * https://github.com/pytorch/executorch/pull/3507 Link to release branch PR: * https://github.com/pytorch/executorch/pull/3512 Criteria category and reasons: * Fix #3502 ----- @mcr229 merged

Sorry yeah I broke this while hardening up the pip build process to support `flatc` and pybindings. https://github.com/pytorch/executorch/blob/cc2d3b57420c9dd73abf458c8cc45e099d9e8a7b/setup.py#L411-L413 has some notes about what needs to change here: I think we...