We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TypeScript xlang Tests fail with the error ValueError: numpy.dtype size changed, may indicate binary incompatibility. Expected 96 from C header, got 88 from PyObject. See https://github.com/apache/beam/actions/runs/12248355502/job/34167812294#step:9:65
ValueError: numpy.dtype size changed, may indicate binary incompatibility. Expected 96 from C header, got 88 from PyObject
Priority: 2 (default / most bugs should be filed as P2)
The text was updated successfully, but these errors were encountered:
No branches or pull requests
What happened?
TypeScript xlang Tests fail with the error
ValueError: numpy.dtype size changed, may indicate binary incompatibility. Expected 96 from C header, got 88 from PyObject
. See https://github.com/apache/beam/actions/runs/12248355502/job/34167812294#step:9:65Issue Priority
Priority: 2 (default / most bugs should be filed as P2)
Issue Components
The text was updated successfully, but these errors were encountered: