You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Issue Description:
When building the Patchwork project from source using Poetry, the build fails with the following error:
Patchflow AutoFix not found in deque (['patchwork patchflows'])
Steps to Reproduce:
1. Clone the Patchwork repository.
2. Install Poetry (tested with Poetry 1.8.4).
3. Use Python 3.9 or Python 3.12 (tested with both versions).
4. Run the build steps:
poetry shell
poetry install —all-extras
Environment Details:
• Operating Systems Tested: macOS, Linux (Ubuntu).
• Python Versions Tested: 3.9, 3.12.
• Poetry Version: 1.8.4.
Additional Context:
The issue occurs consistently on both tested operating systems and Python versions. Let me know if you need any debug logs, configurations, or further details.
Please provide a link to a minimal reproduction of the bug
No response
Please provide the exception or error you saw
Patchflow AutoFix not found in deque (['patchwork patchflows'])
Anything else?
No response
The text was updated successfully, but these errors were encountered:
Is this a regression?
Yes
Description
Issue Description:
When building the Patchwork project from source using Poetry, the build fails with the following error:
Patchflow AutoFix not found in deque (['patchwork patchflows'])
Steps to Reproduce:
1. Clone the Patchwork repository.
2. Install Poetry (tested with Poetry 1.8.4).
3. Use Python 3.9 or Python 3.12 (tested with both versions).
4. Run the build steps:
Environment Details:
• Operating Systems Tested: macOS, Linux (Ubuntu).
• Python Versions Tested: 3.9, 3.12.
• Poetry Version: 1.8.4.
Additional Context:
The issue occurs consistently on both tested operating systems and Python versions. Let me know if you need any debug logs, configurations, or further details.
Please provide a link to a minimal reproduction of the bug
No response
Please provide the exception or error you saw
Anything else?
No response
The text was updated successfully, but these errors were encountered: