Alireza Ghasemi

Compose v2 build doesn't respect local git credential helpers

5

**Description** **Steps to reproduce the issue:** 1. Create a private git repository, e.g. at GitHub, with a valid Dockerfile in it. 2. Define a [git credential helper](https://git-scm.com/docs/gitcredentials) for accessing the...

Add warning about the old Helm charts

1

Related to #735; let's save people (like me) from wasting time debugging their deployment.

net/http/httptest: add comment to Server.Client() about Server.URL

6

Updates #30774.

Is the Chroma initial heartbeat necessary?

1

https://github.com/tmc/langchaingo/blob/e8498f5c2f097cd31c917d2e63b4f6f41c651bf2/vectorstores/chroma/chroma.go#L62-L64 Is this :point_up: necessary? wouldn't it be better to raise errors upon requests, rather than on client initialization? This would make developing a fault-tolerant application easier.

Add support for word-level audio transcription timestamp granularity

5

**Describe the change** Add support for word-level audio transcription timestamp granularity. **Provide OpenAI documentation link** - [timestamp_granularities[]](https://platform.openai.com/docs/api-reference/audio/createTranscription#audio-createtranscription-timestamp_granularities) - [words](https://platform.openai.com/docs/api-reference/audio/verbose-json-object#audio/verbose-json-object-words) **Describe your solution** Added `AudioRequest.TimestampGranularities` and `AudioResponse.Words` fields. **Tests** Filled `AudioRequest.TimestampGranularities`...

The Redis-lock methods do not receive a context argument; the merged PR #652 did a trick of passing the Redis client's context to its own methods' calls, which I strongly...

The go-redis v9 removed the `.Context()` method on its client; the `v1` package was updated accordingly in #793, but the `v2` package was left out which this PR fixes. Also,...

See [MaxAckPending | Configuration | Consumer | NATS Docs](https://docs.nats.io/nats-concepts/jetstream/consumers#maxackpending).

Fetch and misbehaving IMAP server

3

I encountered a misbehaving IMAP server in which a response has a bad impossible big number: ```text tag UID FETCH 63 BINARY.SIZE[1] * 1 FETCH (UID 63 BINARY.SIZE[1] 18446744073709551232) tag...