A modern programming language that makes developers happier.

kotlinlang

Hi all! *tl;dr:* Has anyone here ever needed to create *server-side deadlines*?

_Background_:
The `grpc-kotlin` wrapper to `grpc-java` already supports setting Deadlines on Client Stubs (using the <https://grpc.github.io/grpc-java/javadoc/io/grpc/stub/AbstractStub.html#withDeadline-io.grpc.Deadline-|withDeadline> function), however there is no "Kotlin coroutine" equivalent to the <https://grpc.github.io/grpc-java/javadoc/io/grpc/Context.html#withDeadline-io.grpc.Deadline-java.util.concurrent.ScheduledExecutorService-|io.grpc.Context#withDeadline> function that allows wrapping any operation into a Cancellable context with a deadline (a deadline that is then propagated to all gRPC client stubs within the operation!).

The problem is that the `io.grpc.Context#withDeadline` API requires using a `ScheduledExecutorService`, which as I understand it, would require bypassing Kotlin coroutine architecture. An alternative is to use `withTimeout`: however this results in 2 separate contextual timeouts (the `withTimeout` one and a potential propagated gRPC Deadline in the context)

Has anyone here had to set server-side deadlines/timeouts in the past (in the context of gRPC servers)? If so, what approach have you used?

in interceptors you can avoid messing with `ScheduledExecutorService`
```    override fun &lt;ReqT, RespT&gt; interceptCall(
        call: ServerCall&lt;ReqT, RespT&gt;,
        headers: Metadata,
        next: ServerCallHandler&lt;ReqT, RespT&gt;,
    ): ServerCall.Listener&lt;ReqT&gt; {
        return Contexts.interceptCall(Context.current().withDeadline(), call, headers, next)
    }```

Thanks <@U3GNZ6N1J> for the. suggestion! Won't `Context.current().withDeadline()` require passing the scheduler though? The signature of `withDeadline` API requires it. Or am I missing something? Looking at the `io.grpc.Context` code, the `deadline` attribute is only set on the `Context.CancellableContext` which is created thru `withDeadline`