Repository navigation
Closed
Labels
high prioritymodule: ciIssues related to continuous integrationIssues related to continuous integrationtriagedThis issue has been looked at a team member, and triaged and prioritized into an appropriate moduleThis issue has been looked at a team member, and triaged and prioritized into an appropriate module
Description
I've followed the steps outlined https://pytorch.org/executorch/stable/getting-started-setup.html
But after running
python3 -m examples.portable.scripts.export --model_name="add"
I am getting the following error
mod_name, mod_spec, code = _get_module_details(mod_name, _Error)
File "/usr/lib/python3.8/runpy.py", line 111, in _get_module_details
__import__(pkg_name)
File "/home/azureuser/executorch/examples/portable/__init__.py", line 7, in <module>
from .utils import export_to_edge, export_to_exec_prog, save_pte_program
File "/home/azureuser/executorch/examples/portable/utils.py", line 11, in <module>
import executorch.exir as exir
File "/home/azureuser/executorch/.executorch/lib/python3.8/site-packages/executorch/exir/__init__.py", line 9, in <module>
from executorch.exir.capture import (
File "/home/azureuser/executorch/.executorch/lib/python3.8/site-packages/executorch/exir/capture/__init__.py", line 9, in <module>
from executorch.exir.capture._capture import (
File "/home/azureuser/executorch/.executorch/lib/python3.8/site-packages/executorch/exir/capture/_capture.py", line 14, in <module>
from executorch.exir.capture._config import CaptureConfig
File "/home/azureuser/executorch/.executorch/lib/python3.8/site-packages/executorch/exir/capture/_config.py", line 12, in <module>
from executorch.exir.passes import MemoryPlanningPass, ToOutVarPass
File "/home/azureuser/executorch/.executorch/lib/python3.8/site-packages/executorch/exir/passes/__init__.py", line 19, in <module>
from executorch.exir import control_flow, memory, memory_planning
File "/home/azureuser/executorch/.executorch/lib/python3.8/site-packages/executorch/exir/memory_planning.py", line 20, in <module>
from executorch.exir.delegate import executorch_call_delegate
File "/home/azureuser/executorch/.executorch/lib/python3.8/site-packages/executorch/exir/delegate.py", line 122, in <module>
@executorch_call_delegate.py_functionalize_impl
AttributeError: 'HigherOrderOperator' object has no attribute 'py_functionalize_impl'
Metadata
Metadata
Assignees
Labels
high prioritymodule: ciIssues related to continuous integrationIssues related to continuous integrationtriagedThis issue has been looked at a team member, and triaged and prioritized into an appropriate moduleThis issue has been looked at a team member, and triaged and prioritized into an appropriate module
Activity
mergennachin commentedon Jan 22, 2024
Hey @huydhn
It looks like it is the same issue as #1413
I tried installing
pip install --force-reinstall --pre torch=="dev20231010" -i https://download.pytorch.org/whl/nightly/cpubut it is not installing
ERROR: Could not find a version that satisfies the requirement torch==dev20231010 (from versions: 2.2.0.dev20231128+cpu, 2.2.0.dev20231129+cpu, 2.2.0.dev20231130+cpu, 2.2.0.dev20231201+cpu, 2.2.0.dev20231202+cpu, 2.2.0.dev20231203+cpu, 2.2.0.dev20231204+cpu, 2.2.0.dev20231205+cpu, 2.2.0.dev20231206+cpu, 2.2.0.dev20231207+cpu, 2.2.0.dev20231208+cpu, 2.2.0.dev20231209+cpu, 2.2.0.dev20231210+cpu, 2.2.0.dev20231211+cpu, 2.2.0.dev20231212+cpu, 2.2.0.dev20231213+cpu, 2.3.0.dev20231214+cpu, 2.3.0.dev20231215+cpu, 2.3.0.dev20231216+cpu, 2.3.0.dev20231217+cpu, 2.3.0.dev20231218+cpu, 2.3.0.dev20231219+cpu, 2.3.0.dev20231220+cpu, 2.3.0.dev20231221+cpu, 2.3.0.dev20231222+cpu, 2.3.0.dev20231223+cpu, 2.3.0.dev20231224+cpu, 2.3.0.dev20231225+cpu, 2.3.0.dev20231226+cpu, 2.3.0.dev20231227+cpu, 2.3.0.dev20231228+cpu, 2.3.0.dev20231229+cpu, 2.3.0.dev20231230+cpu, 2.3.0.dev20231231+cpu, 2.3.0.dev20240101+cpu, 2.3.0.dev20240102+cpu, 2.3.0.dev20240103+cpu, 2.3.0.dev20240104+cpu, 2.3.0.dev20240105+cpu, 2.3.0.dev20240106+cpu, 2.3.0.dev20240107+cpu, 2.3.0.dev20240108+cpu, 2.3.0.dev20240109+cpu, 2.3.0.dev20240110+cpu, 2.3.0.dev20240111+cpu, 2.3.0.dev20240113+cpu, 2.3.0.dev20240114+cpu, 2.3.0.dev20240115+cpu, 2.3.0.dev20240116+cpu, 2.3.0.dev20240117+cpu, 2.3.0.dev20240118+cpu, 2.3.0.dev20240119+cpu, 2.3.0.dev20240120+cpu, 2.3.0.dev20240121+cpu, 2.3.0.dev20240122+cpu) ERROR: No matching distribution found for torch==dev20231010huydhn commentedon Jan 22, 2024
Let me take a look, the files are still there on S3, but they are gone from the index. The code was moved around recently in pytorch/test-infra#4879, so may be it causes a regression
huydhn commentedon Jan 22, 2024
This should be fixed by pytorch/test-infra#4900
AlexRibard commentedon Jan 22, 2024
Duplicate of #1662 I'd say.
With conda all is good. It's really pip which messes up dependencies
Keep nightly 20231010 for ExecuTorch alpha 0.1 for now (#4900)
huydhn commentedon Jan 22, 2024
The files are back in the index now https://download.pytorch.org/whl/nightly/torch/ and
pip install --force-reinstall --pre torch=="2.2.0.dev20231010" -i https://download.pytorch.org/whl/nightly/cpuworks as expected.mergennachin commentedon Jan 22, 2024
Thanks @huydhn
I just went through the setup script in https://pytorch.org/executorch/stable/getting-started-setup.html from beginning to end.
Works for me now.
Thanks @AlexRibard for reporting. This was an actual bug on our side where torch=="2.2.0.dev20231010" (that stable branch, v0.1.0, uses) doesn't exist in the nightly index. Huy just updated it.