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
as joannis.swiftonserver-site has 17 dependencies, it’s possible we are hitting some hard-coded resource limit in UnidocDB. although from reading Unidoc.DB.Snapshots.swift 16 is only the stride limit and it ought to support up to 32 dependencies already.
another, more-remote possibility is something weird is happening with the duplicated 1.1 and 1.1.0 tags in the swift-http-types repository…
The text was updated successfully, but these errors were encountered:
the 17 dependency count was a red herring, the problem was in fact caused by the maintainer of swift-http-types creating two semver tags (1.1, 1.1.0) that both point to the same commit. the maintainer evidently realized her/his mistake and deleted the tag on GitHub but it remains in Swiftinit’s tag database.
even though the two tags point to the same commit, Swiftinit considers them distinct versions, and it evidently pinned swiftonserver-site to the version that had no symbol graph, making swift-http-types unavailable for linking. Swiftinit pinned the dependency to the wrong version because SwiftPM ignores the git ref string and therefore considers 1.1 and 1.1.0 to belong to an equivalence class. there is no way to disambiguate on Swiftinit’s end because both tags point to the same commit.
for some reason, https://swiftinit.org/docs/joannis.swiftonserver-site is failing to link against
swift-http-types
at 1.1.0as
joannis.swiftonserver-site
has 17 dependencies, it’s possible we are hitting some hard-coded resource limit inUnidocDB
. although from readingUnidoc.DB.Snapshots.swift
16 is only the stride limit and it ought to support up to 32 dependencies already.another, more-remote possibility is something weird is happening with the duplicated
1.1
and1.1.0
tags in the swift-http-types repository…The text was updated successfully, but these errors were encountered: