You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems that UV doesn't support version identifiers great than 18446744073709551615. I don't believe https://peps.python.org/pep-0440/ has this restriction and assume it is a function of using Int64 to parse the build number.
To reproduce simply add a dependency with a dev version identifier > 18446744073709551615.
Internally we are using a concatenation of the hash of a branch name and the git commit to version development packages. We don't use the local identifier syntax because google won't let us install those in the cloud-composer (even though we use a private artifactory) :(
error: Failed to build: `vi-composer @ file:///Users/dschneider/bombora/repos/vi-composer`
Caused by: Failed to parse metadata from built wheel
Caused by: expected number less than or equal to 18446744073709551615, but number found in "768230559194918072045" exceeds it
bombora-composer3-airflow2 ==0.2.1.dev768230559194918072045
uv 0.4.13 (b8f9ee3b4 2024-09-19)
on macos
The text was updated successfully, but these errors were encountered:
It's hard to say if we should support larger integers. I assume it will come with more complexity and performance degradation. Curious to see what @BurntSushi thinks though, as he's the expert on this.
It seems that UV doesn't support version identifiers great than 18446744073709551615. I don't believe https://peps.python.org/pep-0440/ has this restriction and assume it is a function of using Int64 to parse the build number.
To reproduce simply add a dependency with a dev version identifier > 18446744073709551615.
Internally we are using a concatenation of the hash of a branch name and the git commit to version development packages. We don't use the local identifier syntax because google won't let us install those in the cloud-composer (even though we use a private artifactory) :(
on macos
The text was updated successfully, but these errors were encountered: