JetStream bucket put calls should support ctx

[elbek]

Proposed change

How can We set time outs to put and get jetstream calls,
We are running into context deadline exceeded issue.

It seems put/get calls do not support ctx.Context() go struct. How does one configure timeout for these calls? What is the default value, how can we check?

Thanks.

Use case

KeyValue.Get() and KeyValue.Put() should be able to accept ctx

Contribution

No response

[derekcollison]

This a Go client question?

[elbek]

This a Go client question?

probably, but client cannot do on its own if server doesn';t support.

[derekcollison]

The client can be updated to take a context regardless of server behavior, meaning you want to time out or cancel waiting for a response.

[jigarpatel1007]

Thanks for raising this — adding context support to KeyValue.Put() and KeyValue.Get() is a reasonable and important enhancement, especially for production systems that rely on timeout guarantees, retries, and cancellation logic.

---

✅ Recommended Solution Direction

This enhancement can likely be handled entirely within the Go client, as @derekcollison mentioned — since context timeouts affect client-side control flow, not server-side protocol changes.

I propose the following:

1. Extend KeyValue.Get() and KeyValue.Put() to accept context.Context

• Add KeyValue.PutWithContext(ctx context.Context, key string, value []byte) and similar for Get
• Wrap internal Request() calls using context-aware versions (e.g., js.nc.RequestWithContext())

2. Gracefully Handle Timeouts & Cancellation

• If context is canceled or exceeds deadline, return context.DeadlineExceeded or context.Canceled to the caller
• Document this clearly in the GoDoc to help developers understand integration behavior with context.WithTimeout

---

📄 Why This Matters

In distributed systems or high-throughput JetStream environments:

• Retry logic and circuit breakers depend on clear timeout signals
• Integrated services (e.g., CI/CD pipelines or provisioning workflows) often wrap KV interactions in context.WithTimeout
• This is a necessary step toward making JetStream key-value stores first-class citizens in resilient workflows

---

🔧 Optional Helper Layer

If we want to preserve backwards compatibility, we can add WithContext() variants rather than changing existing signatures. Later, deprecation can be considered if adoption grows.

---

Let me know if this approach aligns with the maintainers' direction.