build process packages up old versions of MistServer somehow about catalyst

[hjpotter92]

My initial thought was that it might be timing issue, where the mist builds had not yet succeeded and catalyst build was triggered. However, we push the updated manifest only after the binaries have been successfully compressed and uploaded to bucket; which in-turn created the auto-commit.

The other alternative "could" be that github action fetched the old copy of manifest (is there cloudflare caching on build.livepeer.live domain?)

The 3rd possibility i can think of is that the staging branch was merged pretty quick which led to the builder (which uses github URL for context) wasn't able to fetch information about it? This, however, shouldn't affect the make build pipeline at all.

Creating a PR with more logging context. I'll be observing the builds from auto-commits and their merges closely.

[hjpotter92]

This seems to have been a caching issue. A fix was deployed to cloudflare yesterday; and the worker will be moved to wrangler with this open PR: livepeer/livepeer-worker#6

[leszko]

@hjpotter92 If the related PR is merged, can we close this issue?