Skip to content
New issue

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

[CI] CircleCI failing in tests due to Numpy unsupported version for Python 3.12 #2978

Closed
flavienSindou opened this issue Nov 18, 2024 · 0 comments · Fixed by #2981
Closed
Assignees
Labels
bug use for describing something not working as expected filigran team use to identify PR from the Filigran team solved use to identify issue that has been solved (must be linked to the solving PR)
Milestone

Comments

@flavienSindou
Copy link
Contributor

flavienSindou commented Nov 18, 2024

Description

Numpy is a dependency of stix-shifter

The primary cause of this issue is the deprecated dependencies in setuptools and the incomplete migration to meson.

introduced in d629de0

Environment

  1. OS (where OpenCTI server runs): N/A
  2. OpenCTI client: N/A
  3. Other environment details:

Reproducible Steps

Steps to create the smallest reproducible scenario:

  1. Go to https://app.circleci.com/pipelines/github/OpenCTI-Platform/connectors/7062/workflows/c588f5d3-37f9-4af7-9fa1-92732f1f6ba9/jobs/23884

Expected Output

Numpy installed correctly or error raised

Actual Output

Success message whereas failure

Additional information

N/A

Screenshots (optional)

@flavienSindou flavienSindou added bug use for describing something not working as expected filigran team use to identify PR from the Filigran team labels Nov 18, 2024
@flavienSindou flavienSindou linked a pull request Nov 18, 2024 that will close this issue
4 tasks
@flavienSindou flavienSindou self-assigned this Nov 18, 2024
@flavienSindou flavienSindou removed a link to a pull request Nov 18, 2024
4 tasks
@flavienSindou flavienSindou linked a pull request Nov 18, 2024 that will close this issue
4 tasks
@helene-nguyen helene-nguyen added the solved use to identify issue that has been solved (must be linked to the solving PR) label Nov 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug use for describing something not working as expected filigran team use to identify PR from the Filigran team solved use to identify issue that has been solved (must be linked to the solving PR)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants