Fulton Byrne

Alright so I've got two PRs now: 1. https://github.com/hashicorp/vault/pull/17919 refactoring to make changes to the sleep calculation easier. 2. https://github.com/hashicorp/vault/pull/17921 introducing a "backwards compatible" change to introduce "Age" to secrets...

@hsimon-hashicorp is there a better way to approach this problem? Get some hashicorp engineers involved? It really causes havoc, mayhem, and prevents us from adopting Vault for credential management.

Hey! I'll take a look. So glad to see you all picking this up!

@peteski22 we dropped the ticket a while back. Our test case would look something like https://github.com/hashicorp/vault/issues/16439#issuecomment-1234734726. We won't work on it further. We found that it was _very_ difficult to...

Makes sense! I think the thread _is_ really complicated and it may be better to start with the _root_ of the issue and then work up. Or just summarize all...

I know very little about the type system and wanted to learn some more. Here's all the extra context I've collected: 1. This most recent work was to implement _nominal_...

Specifically for llama.cpp I think https://github.com/hwchase17/langchain/issues/2404#issuecomment-1497521897 points to the issue being in the Callback Manager. It's likely that due to the async nature of callback manager the "main" program exits...

Yeah, this is a bummer. You would think that you would get a Vector store you could use as a `retriever` when using `VectoreStoreIndexCreator`. The way I work around this...

This seems like an interesting thing to look into, but first what are we looking into? We can see every time `run_command_and_read_response` is called we are generally executing _another_ parsing...

`imap-proto` makes heavy use of `nom` and `streaming` parsing to handle parsing the streams. It's likely that we can get rid of `readline` by building on `nom` as well: https://github.com/jonhoo/rust-imap/blob/5d0d2f9723b626770ffeab7e334ded67ae94fd7e/src/client.rs#L1606-L1621...