Luke Steensen

We did attempt to implement Fibonacci backoffs as part of https://github.com/timberio/vector/pull/1006, but it's definitely worth investigating why we did not observe that behavior. It's possible that 429s don't follow that...

I don't think it's a replacement for us, unfortunately. From the readme [comparison with `glob`](https://github.com/BurntSushi/ripgrep/tree/master/crates/globset#comparison-with-the-glob-crate): > Doesn't provide a recursive directory iterator of matching file paths That's the exact function...

`globwalk` looks good! I think we could go ahead and swap that in.

Blocking on that `glob` issue seems like the right call to me. There doesn't seem to be one clear place we can easily contribute to, and I don't think that...

Yeah I think this is done. The initial conversation with @jszwedko had something to do with confusion around what happens when a stream of `Result` is sent, but I don't...

@njam I'm curious if wildcard inputs (just implemented in #6170) could accomplish the same thing? In the given example, instead of specifying `noop-ouput` you could specify `swimlane*`.

@jszwedko it was added but explicitly not registered, so it's not currently usable outside of internals. If we want to open it up for everyone we'll need to do both.

I spent some time on this as part of #139, and I think to do it right will require some rework of the util `HttpSink`. Right now, we don't have...

Thanks! I've updated the lib tests, so those should now be passing, but left the interop tests since I'm not sure of the best procedure for generating new fixtures. As...

I've added one more commit here to add a catch-all `additional_fields` property to ~~`TargetsMetadata`~~ all of the top level metadata structs. It turns out that [go-tuf](https://github.com/theupdateframework/go-tuf/blob/ac7b5d7bce18cca5a84a28b021bd6372f450b35b/data/types.go#L214) has a `custom` field...