You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 3, 2022. It is now read-only.
I was installing a bundle using duffle and got a stack trace that would have been much quicker to debug had it been obvious that the error was coming from the container and not the runtime itself.
I initially assumed that the panic was happening in duffle since it's written in go and vendors the yaml parsing library that throws this error. It turns out that it was actually my bundle's run tool panicking which was using the same library (and coincidentally failing because of cnabio/cnab-go#86).
I think duffle should print some helpful logging statements and tell users where it's output is coming from to avoid situations like this in the future.
I was installing a bundle using duffle and got a stack trace that would have been much quicker to debug had it been obvious that the error was coming from the container and not the runtime itself.
I initially assumed that the panic was happening in duffle since it's written in go and vendors the yaml parsing library that throws this error. It turns out that it was actually my bundle's run tool panicking which was using the same library (and coincidentally failing because of cnabio/cnab-go#86).
I think duffle should print some helpful logging statements and tell users where it's output is coming from to avoid situations like this in the future.
The text was updated successfully, but these errors were encountered: