The update-extensions-repo-and-run-tests job has no top-level checkout,
so the default workspace is already <org>/<repo> =
work/IfcOpenShell/IfcOpenShell. Cloning the repo into a subdir also
named IfcOpenShell produced a third segment
(.../IfcOpenShell/IfcOpenShell/IfcOpenShell), and the BDD feature
fixtures template Path.cwd() into link_ifc file paths, yielding a
FileNotFoundError on ~8 link_ifc scenarios in project.feature.
Rename the manually-cloned directory to ifcopenshell_repo and update
its three dependent references. Pure rename, no behaviour change beyond
removing the path collision.
Traced by exact command reconstruction; final confirmation is the next
ci-bonsai-daily run (needs GitHub-hosted runners, not reproducible locally).
This change was made with the assistance of an AI tool.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
To avoid running in a situation when some builds are using one tag and some are using another and then unstable repo script fails to find builds for some platforms.
The problem is index.json is using urls pointing to zip files from the releases and it's possible that installation from unstable repo will be broken (user will get error message like '"Archive size mismatch "bonsai", expected 87417726, was 87418259"') in 2 cases:
1) during 5 minutes after commit while builds are still uploaded to the releases but index.json is not yet updated
2) if some builds were uploaded and some builds failed to upload, then for platforms that were uploaded successfully unstable installation will be broken until we fix the builds
When we add hours and minutes to the tag, that should be enough to make urls unique for each build avoiding this problem. If needed we can came up with some mechanism to clean up all builds besides the last one.
Petru Conduraru