Closed bdraco closed 3 months ago
This is likely something to do with arm7 specifically. I removed arm7 as a wheel because it wouldn't pass CI. Why, though? The Rust target is "guaranteed to build", not "guaranteed to work". And this is running nightly, so I don't know. And then the build and test are both emulated in QEMU in an environment I can't reproduce and that take ~15 minutes per iteration. You could imagine doing an entirely separate arm7 stable rust nightly build.
That commit itself is just doing a memcpy instead of check for escapes etc on strings the library constructs itself and are known to not need escaping. There's nothing interesting on 64/32-bit or aarch64/amd64 around then either.
I thought it was armv7 as well but the linked issue is aarch64 as well
Edit https://github.com/home-assistant/core/issues/118909
And
https://github.com/home-assistant/core/issues/118507#issuecomment-2144756742
I asked for explicit verification in in linked issue that wasn't explicit and it's now confirmed in both of the linked issues that they are on aarch64
Is your provided setup musl libc and 3.12? orjson-3.10.3-cp312-cp312-musllinux_1_2_aarch64.whl
was installed?
Yes
Musl (alpine 3.19), cpython 3.12, Installed from wheel
3.10.6 has arm7 wheels and should be appropriate to try. It possibly was an issue with the u64 write.
Thanks for the heads up. I’ll give it a shot when I get home later tonight
Initial testing looks good.
Will have a better idea if everything is OK in early August when HA core 2024.8.x ships
So far so good with the HA beta. Will followup again after the stable release.
Thanks
Home Assistant stable release shipped yesterday and everything seems to be ok. Thanks for the fix!
Thanks for letting me know.
https://github.com/home-assistant/core/issues/118507#issuecomment-2151033933