stocky-tiger-66593
05/11/2024, 7:53 PMpants package path/to/my/helm-chart-dir::
hanging indefinitely when performing operations on helm charts? It seems to be the case where there are dependencies on 3rd party charts:
helm_artifact(
name="cert-manager-chart",
artifact="cert-manager",
version="1.12.2",
repository="<https://charts.jetstack.io>",
)
helm_chart(
name="cert-manager",
dependencies=[
":cert-manager-chart",
]
)
such as the above. However, it does not hang when packaging this one, which also has a dependency on 3rd party:
helm_artifact(
name="argocd-chart",
artifact="argo-cd",
version="5.36.3",
repository="<https://argoproj.github.io/argo-helm>",
)
helm_chart(
name="argocd",
dependencies=[
":argocd-chart",
]
)
what might be the best way to debug?
output:
✗ pants package apps/argocd::
15:53:28.23 [INFO] Wrote dist/apps.argocd/argocd/argocd-0.5.0.tgz
Built Helm chart artifact: apps.argocd/argocd/argocd-0.5.0.tgz
✗ pants package apps/cert-manager
⠒
⠖
.... indefinitely hangs
broad-processor-92400
05/11/2024, 10:15 PM__run.sh
script there, to see if you can reproduce it outside of pants. If so, you can edit the run script and sandbox contents to add more logging, to get to a minimal reproducer or whatever else required to understand what’s going on.
https://www.pantsbuild.org/2.20/docs/using-pants/troubleshooting-common-issues#debug-tip-inspect-the-sandbox-with---keep-sandboxesstocky-tiger-66593
05/12/2024, 2:53 PMstocky-tiger-66593
05/13/2024, 1:03 AMbroad-processor-92400
05/13/2024, 1:44 AM--keep-sandboxes=always
will print out the sandbox path in advance?
And/or maybe finding the command that's hanging and killing that (via the normal operating system means e.g. pkill ...
) which will look like a failure to Pants? You can use --level=debug
I think to have pants print out the command that it's running if you need help finding which command is hangingstocky-tiger-66593
05/13/2024, 4:35 AMbroad-processor-92400
05/13/2024, 5:24 AMstocky-tiger-66593
05/13/2024, 1:40 PM