shailshouryya commented on issue #32849:
URL: https://github.com/apache/airflow/issues/32849#issuecomment-1650942707

   The [original 
error](https://github.com/apache/airflow/issues/32849#issue-1821453305) you ran 
into seems different, but your most [recent 
error](https://github.com/apache/airflow/issues/32849#issuecomment-1650914972) 
seems similar to https://github.com/google/re2/issues/437, specifically 
https://github.com/google/re2/issues/437#issuecomment-1649512300 and 
https://github.com/google/re2/issues/437#issuecomment-1649654172.
   
   It's not clear why this started failing now, since the `google-re2` has the 
following in the `setup.py` file:
   ```
   Known issues with regard to building the C++ extension:
   
     * Building requires RE2 to be installed on your system.
       On Debian, for example, install the libre2-dev package.
     * Building requires pybind11 to be installed on your system OR venv.
       On Debian, for example, install the pybind11-dev package.
       For a venv, install the pybind11 package from PyPI.
     * Building on macOS is known to work, but has been known to fail.
       For example, the system Python may not know which compiler flags
       to set when building bindings for software installed by Homebrew;
       see https://docs.brew.sh/Homebrew-and-Python#brewed-python-modules.
     * Building on Windows has not been tested yet and will probably fail.
   ```
   (see 
https://github.com/google/re2/blob/e66463312e1d30d427bbde6c40e7fd627dcfb82e/python/setup.py#L30-L42)
   
   There also don't seem to be many changes in [release 
2023-07-01](https://github.com/google/re2/compare/2023-06-02...2023-07-01) of 
`google-re2`, and [release 
2.11.1](https://github.com/pybind/pybind11/compare/v2.11.0...v2.11.1) of 
`pybind11` also does not change much. Something else in the dependency chain 
may have changed, or perhaps there **is some change** in one of these recent 
releases that caused the break.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to