Skip to content

Conversation

@amoghrajesh
Copy link
Contributor

@amoghrajesh amoghrajesh commented Jun 4, 2025

https://github.com/apache/airflow/pull/51379/files was done but that seems to have fixed it for google but seems that the core is pulling in with this dependency leading to conflicts!

Error:

  Using Python 3.9.22 environment at: /usr/local
    × Failed to build `sqlalchemy-spanner==1.12.0`
    ├─▶ The build backend returned an error
    ╰─▶ Call to `setuptools.build_meta:__legacy__.build_wheel` failed (exit
        status: 1)
  
        [stderr]
        Traceback (most recent call last):
          File "<string>", line 14, in <module>
          File
        "/root/.cache/uv/builds-v0/.tmpGXqNjn/lib/python3.9/site-packages/setuptools/build_meta.py",
        line 331, in get_requires_for_build_wheel
            return self._get_build_requires(config_settings, requirements=[])
          File
        "/root/.cache/uv/builds-v0/.tmpGXqNjn/lib/python3.9/site-packages/setuptools/build_meta.py",
        line 301, in _get_build_requires
            self.run_setup()
          File
        "/root/.cache/uv/builds-v0/.tmpGXqNjn/lib/python3.9/site-packages/setuptools/build_meta.py",
        line 512, in run_setup
            super().run_setup(setup_script=setup_script)
          File
        "/root/.cache/uv/builds-v0/.tmpGXqNjn/lib/python3.9/site-packages/setuptools/build_meta.py",
        line 317, in run_setup
            exec(code, locals())
          File "<string>", line 42, in <module>
        FileNotFoundError: [Errno 2] No such file or directory:
        '/root/.cache/uv/sdists-v9/pypi/sqlalchemy-spanner/1.12.0/ov5x7gb8PILJehef0Gf3j/src/version.py'
  
        hint: This usually indicates a problem with the package or the build
        environment.
    help: `sqlalchemy-spanner` (v1.12.0) was included
          because `apache-airflow[all]` (v3.1.0) depends on
          `apache-airflow-providers-google>=10.24.0` (v15.1.0) which depends on
          `sqlalchemy-spanner>=1.6.2`

Example: https://github.com/apache/airflow/actions/runs/15433020002/job/43434553777


^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

@eladkal
Copy link
Contributor

eladkal commented Jun 4, 2025

Wasn't this handled in #51379 ?

I don't think core dependencies should do this exclusion something may be missing in the CI to catch the fix of #51379

@Lee-W Lee-W self-requested a review June 4, 2025 07:52
@Lee-W
Copy link
Member

Lee-W commented Jun 4, 2025

is it also used in core 🤔 yep, looks like it's handled in #51379

@amoghrajesh
Copy link
Contributor Author

@eladkal that PR fixes it for google only

@eladkal
Copy link
Contributor

eladkal commented Jun 4, 2025

@eladkal that PR fixes it for google only

core doesn't need spanner. It makes no sense to exclude it in core.
core gets spanner version from google so if the issue is fixed in google provider it should automatically fixed for core.
I think we are missing something here.

@amoghrajesh
Copy link
Contributor Author

Looks like it hasnt been fixed properly in google

@eladkal
Copy link
Contributor

eladkal commented Jun 4, 2025

Should be closed in favor of #51393

@potiuk potiuk closed this Jun 4, 2025
@potiuk
Copy link
Member

potiuk commented Jun 4, 2025

#51393 has now more detailed error description explaining where and where to fix similar problem when it happens next time

image

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.

4 participants