Conversation
Advance external/go workspace submodule to v0.10.4 so dev (GOWORK on) and standalone (GOWORK=off) builds resolve the same core/go. Co-Authored-By: Virgil <virgil@lethean.io>
Wire the CoreGO side of the CoreGO <-> CoreDeno gRPC sidecar contract (code/core/go/api/RFC.grpc.md) into the gateway so it actually serves. - pkg/grpc: GoService (sandboxed I/O, KV state, exec, core:// scheme), DenoClient, and the GRPCServer (Unix socket / TCP loopback transport). - pkg/proto(+gen): core_sidecar.proto and generated bindings. - cmd/gateway: construct GoService against real subsystems (io.Local, a go-store KV database, the shared go-process Service) and serve it on a Unix domain socket (CORE_GATEWAY_GRPC_SOCKET, default under .core/run). kvStoreAdapter/procRunnerAdapter bridge go-store's error contract and go-process RunOptions to the GoService consumer interfaces. The process Service is now built once and shared by the HTTP provider and the gRPC bridge. Startup is additive: store/listen failures are logged and HTTP serving continues; the server stops gracefully on context cancel and via the cleanup stack. - go.mod/go.sum: add google.golang.org/grpc + dappco.re/go/store deps. Co-Authored-By: Virgil <virgil@lethean.io>
go-inference flipped TextModel/Backend to the core.Result idiom; the chat-completions handler's model.Err() probes now check !r.OK. Co-Authored-By: Virgil <virgil@lethean.io>
Co-Authored-By: Virgil <virgil@lethean.io>
…ers/ Verified each design's work is present in source before removal; the docs are redundant replication guides. Future superpowers output stays local (gitignored). Co-Authored-By: Virgil <virgil@lethean.io>
|
Warning Review limit reached
Next review available in: 26 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (3)
📒 Files selected for processing (18)
Warning Billing warning: we have not been able to collect payment for this subscription for more than 72 hours. Please update the payment method or pay any pending invoices in Billing to avoid service interruption. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
1 participant
This pull request removes the implementation plan document for OpenAPI describability of the inference surface. The deleted file detailed the steps, architecture, and tasks for surfacing remote/hybrid chat-completions endpoints and upstream router paths in the generated OpenAPI spec. No code changes are included—this is a documentation cleanup.