Florian Boucault

in `summarizeValues` commenting out this piece fixes the issue: ``` // MT specific bit: if !s.alignToFrom we want the output to be canonical // only thing needed is strip out...

very linked to previously fixed issue https://github.com/grafana/metrictank/issues/1811

Popular libraries that implement anomaly detection in Python: https://pycaret.org/anomaly-detection/ https://github.com/salesforce/Merlion https://github.com/arundo/adtk https://github.com/selimfirat/pysad https://github.com/SeldonIO/alibi-detect Hope it helps

I will try to workaround it pushing manually and using `disable_push=True`.

Actually I cannot do a manual push since I don't know what the expected image reference will be. It is `$EXPECTED_REF` only in the local docker registry. In the end...

Yeah it was surprising to me too but then `internal/build/custom_builder.go` seems pretty clear about it: ``` dig := digest.Digest(inspect.ID) tag, err := digestAsTag(dig) ``` thus discarding `expectedTag` passed to `ExecCustomBuilder.Build()`

And yep I'm using `kind`. Tilt does `kind load` fine indeed but with the incorrect tag.

I'm going to checkout kubernetes/kubernetes#51017 though, it seems it could be related.

Thanks @nicks for taking the time. So actually I don't care that much about the tag that Tilt used to deploy the image. However what I care about is that...

> (for example, would it help if you could query Tilt to get the tag of the image it ended up deploying?) That would not unfortunately. I need to know...