Open matt2e opened 1 month ago
Repro'd by doing the following:
a20cc725
ftl dev --recreate --log-level=DEBUG
baa8449c
(this has a bumped version of ftl installed)So maybe this is to do with switching branches where FTL is on different versions, but that is also something people do, so maybe we should handle this in a more graceful way.
debug: changed "k": *.../modules/k/go.mod
So this is a 'go mod tidy' loop. PFI has a go.mod in backend/go.mod
. Because the other modules depend on this if they have been set to the older version by FTL running go mod tidy
will automatically upgrade them.
In the example above the exact sequence of events is:
backend/go.mod
as it is not a FTL module, so it remains at 0.309.go mod tidy
is run as part of the deployment process, and the version is synched back to 0.309
@jiyoontbd hit an endless build loop
logs (with module names changed):
It looks like
pm
module did have differences because it had to be deployed whereas other modules didn't detect any changes in the build artifacts