Skip to content

Fix PyTorch stack helpers with NumPy backend#3449

Open
FlorianPfaff wants to merge 2 commits into
mainfrom
chatgpt-backend-stack-contract
Open

Fix PyTorch stack helpers with NumPy backend#3449
FlorianPfaff wants to merge 2 commits into
mainfrom
chatgpt-backend-stack-contract

Conversation

@FlorianPfaff

Copy link
Copy Markdown
Owner

Summary

  • Patch the low-level PyTorch stack helper entry points from the backend support compatibility hook.
  • Preserve NumPy-style array-like sequence support even when the selected public backend is NumPy.
  • Add a subprocess regression for hstack, vstack, column_stack, and dstack with PYRECEST_BACKEND=numpy.

Bug fixed

When the process selected the NumPy public backend, the PyTorch-specific stack-helper normalization path did not run. Direct PyTorch backend helper calls could therefore still reach Torch-native stack functions, which reject Python list elements such as ([1, 2], [3, 4]).

Testing

  • Added tests/backend_support/test_pytorch_stack_helpers_raw_backend_contract.py.
  • Not run locally in this connector-only session; CI should execute the focused backend-portable regression.

@FlorianPfaff FlorianPfaff enabled auto-merge (squash) June 29, 2026 15:51
@github-actions

Copy link
Copy Markdown
Contributor

MegaLinter analysis: Success

Descriptor Linter Files Fixed Errors Warnings Elapsed time
✅ COPYPASTE jscpd yes no no 74.59s
✅ JSON prettier 7 0 0 0 0.75s
✅ JSON v8r 7 0 0 4.04s
✅ MARKDOWN markdownlint 68 0 0 0 1.93s
✅ MARKDOWN markdown-table-formatter 68 0 0 0 0.8s
✅ PYTHON black 1132 4 0 0 63.88s
✅ PYTHON isort 1132 4 0 0 4.48s
✅ REPOSITORY checkov yes no no 49.64s
✅ REPOSITORY gitleaks yes no no 8.93s
✅ REPOSITORY git_diff yes no no 0.1s
✅ REPOSITORY secretlint yes no no 32.83s
✅ REPOSITORY syft yes no no 4.0s
✅ REPOSITORY trivy-sbom yes no no 11.65s
✅ REPOSITORY trufflehog yes no no 21.72s
✅ YAML prettier 11 0 0 0 0.75s
✅ YAML v8r 11 0 0 12.45s
✅ YAML yamllint 11 0 0 0.64s

Notices

📣 MegaLinter 9.5.0 is out! Discover the new features and security recommendations in the release announcement. (Skip this info by defining SECURITY_SUGGESTIONS: false)

See detailed reports in MegaLinter artifacts

Your project could benefit from a custom flavor, which would allow you to run only the linters you need, and thus improve runtime performances. (Skip this info by defining FLAVOR_SUGGESTIONS: false)

  • Documentation: Custom Flavors
  • Command: npx mega-linter-runner@9.5.0 --custom-flavor-setup --custom-flavor-linters PYTHON_BLACK,PYTHON_ISORT,COPYPASTE_JSCPD,JSON_V8R,JSON_PRETTIER,MARKDOWN_MARKDOWNLINT,MARKDOWN_MARKDOWN_TABLE_FORMATTER,REPOSITORY_CHECKOV,REPOSITORY_GIT_DIFF,REPOSITORY_GITLEAKS,REPOSITORY_SECRETLINT,REPOSITORY_SYFT,REPOSITORY_TRIVY_SBOM,REPOSITORY_TRUFFLEHOG,YAML_PRETTIER,YAML_YAMLLINT,YAML_V8R

MegaLinter is graciously provided by OX Security
Show us your support by starring ⭐ the repository

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant