Hey hi, with one specific custom tap, I am having the following error:

import singer
  File "/Users/rigerta/Library/Caches/pypoetry/virtualenvs/tap-xactly-OYJ0QBnr-py3.9/lib/python3.9/site-packages/singer/__init__.py", line 32, in <module>
    from singer.messages import (
  File "/Users/rigerta/Library/Caches/pypoetry/virtualenvs/tap-xactly-OYJ0QBnr-py3.9/lib/python3.9/site-packages/singer/messages.py", line 5, in <module>
    import ciso8601
ImportError: dlopen(/Users/rigerta/Library/Caches/pypoetry/virtualenvs/tap-xactly-OYJ0QBnr-py3.9/lib/python3.9/site-packages/ciso8601.cpython-39-darwin.so, 0x0002): tried: '/Users/rigerta/Library/Caches/pypoetry/virtualenvs/tap-xactly-OYJ0QBnr-py3.9/lib/python3.9/site-packages/ciso8601.cpython-39-darwin.so' (mach-o file, but is an incompatible architecture (have 'x86_64', need 'arm64e'))

Didn’t find anything on the internet on any arm version for singer - did someone encounter and solve this problem already maybe?

Hi @rigerta My first guess is that this problem should be taken up with the distributor of the

tap-xactly

extractor.

ciso8601

does not provide binary wheels on pypi.org , so it's really strange how the x86 version of the native library landed on your aarch64 macOS.

the

ciso8601

team can build the platform wheels but are not publishing them yet 🤷‍♂️ https://github.com/closeio/ciso8601/pull/109

Yup, that's exactly why I think it's not a Meltano problem. The mysterious part is how the x86_64 Mach-O version of ciso8601 ended up on Rigerta's M1 Mac. I somehow doubt that it was cross-compiled from source on her Mac.

I see, thanks for pointing this out @christoph thankyou

My suspicion is that the ciso8601 python wheel landed on your M1 Mac from somewhere other than pypi.org

I will try removing it entirely (from my system and the taps requirements file and any references) - fingers crossed 🤞