Matthew Suozzo
Matthew Suozzo
> > Done > > Where? oops! it never got pushed. Regardless, I'm fine abandoning this given it's no longer relevant for our use-case.
So I actually like the behavior of silently moving the conversation to the bundle since my categorization workflow is sequential through the inbox. Pulling focus to a bundle would be...
Thanks so much! Testing the fix, I think I stumbled on a variant of this but when _removing_ from a bundle: When selecting a message inside an expanded bundle and...
Interesting. In my case, I was unlabelling a message that had other labels so, I'd assume, it would also be present in a collapsed bundle after the unlabelling action. Not...
The aforementioned change is still not submitted so the proto version is effectively unusable. Can we merge the fix for this issue in the meantime? https://github.com/in-toto/in-toto-golang/pull/328
Is this worth a patch-release? This is technically a bug fix but I can pin to the commit hash if necessary.
Nah the issue is that we'd be walking from inside the container so the symlink will be broken.
> The symlink _is_ valid. It's just not visible to the binary running in the container. I don't think this distinction is valuable. We're running this action in a container...
Oh yeah this is definitely the case. I'll fix that.
Ugh. So while I didn't implement symlink resolution when walking a directory provided as the artifact path, the example workflow here provides a file so that shouldn't be the issue....