grpc
Here are 2,781 public repositories matching this topic...
Hello,
I found recently that grpc-go was working on an xds implementation for service discovery, which is great.
Using current HEAD, I tried to get both resolver and balancer working. I managed to get something more or less working for resolver by reversing code & tests code on Gist but as for balancer, I didn't.
I unders
Flaky Timeout test
As illustrated by https://app.circleci.com/pipelines/github/grpc-ecosystem/grpc-gateway/281/workflows/57fdb518-e3ee-4f16-9a55-0f417732ca80/jobs/7654/steps, one of the integration tests is sometimes failing with the wrong error. We should figure out why this is happening and fix it.
This should be a good issue to get introduced to the codebase. The test is here: https://github.com/grpc-ecosystem
I actually saw this in code review but then I noticed the old PNGs were also around 1-2 MB. Probably a little room for improvement if we pass these to online PNG optimizers. It seems like the main issue is that the resolution is simply too large.
The official Widgets Development Guide only contains the most basic widget types as example.
There is no functional example for a Flot chart in there right now. Or is it?
Since this is one of the most useful and probably used (at leat to me) widgets it would be very helpful to extend that docum
Bug report
General Information
- Cilium version: 1.7.2
- Kernel version: 5.6.6
- Orchestration system version: Kubernetes 1.18.2
I'm using terraform to spool and deploy kubeadm on AWS.
How to reproduce the issue
The issues is that if the Cloud Controller Manager is not brought up before Cilium the node is brought, and the operator starts running ENIs will be attached t
-
Updated
Jun 4, 2020 - Go
I have a module with two proto files in a directory. File1 is under directory dir1 and File2 is under dir2. Both dir1 and dir2 are under dir0.
I have the below configuration for the "doc" plugin.
- name: doc
flags: markdown,test.md
output: docs
when I invoke prototool by passing dir0 as input, I see it protoc command twice (once for each proto file). This cause
-
Updated
May 18, 2020 - TypeScript
Where's the instructions to convert interface type to protobuf and reverse it?
Can you put on the front page of this project? Where's the tutorial link?
Subject of the issue
Adding the function to delete / edit a message with a mini archive of this message.
Is this a bug report of a feature request?
- Bug report
- [+] Feature request
Your environment
Server-side
- [+] api.tinode.co
- [+] Your own setup:
Linux
Клиент: TinodeWeb/0.16.0-rc1 (tinodejs/0.16.0-rc1)
Сервер: 0.16 rethinkdb:v0.16.0-rc1; (api.tinode
Hi guys,
I'm a computer science student and I have to make a project in Go with Proto.Actor. Because of my lack of experience (this is my first project in Go, coming from Java) and the lack of documentation on the official website I find it very difficult to understand how one can use it. It would be nice if you could provide a better documentation. Thank you!
-
Updated
Jun 3, 2020
Raising this issue so we can merge #489. We need to ensure we don't regress on this functionality.
Quick Start Guide
I'm sure there are a lot of people, myself included, excited to use Rejoiner, but are rusty with their Java tooling knowledge.
Would love to see a very easy copy/paste how-to to get rejoiner up and running with vanilla Java. A quick start guide would help immensely.
-
Updated
May 31, 2020 - C#
- Instead of holding implementations for each logging, tracing, metrics providers, establish interfaces.
- Be clear about it in docs
- Store implementations in... nested go modules? Separate project? To agree.
Is your feature request related to a problem? Please describe.
I got few migrations each referring a different connection. migrate:fresh, migrate:refresh doesn't handle this scenario since they operate on the default connection or in the specific connection passed via --database param.
Describe the solution you'd like
The simplest solution can be to process only migrations that has th
In our codebase, we push RequestContext and immediately run some code with try-with-resources.
For example:
try (SafeCloseable ignored = ctx.push()) {
logger.trace(decorate(msg));
}If RequestContext provides run(Runnable) or call(Callable) we can reduce boilerplate code and simplify it.
ctx.run(() -> logger.trace(decorate(msg));This is inspired by g
We should expose something akin to warp::service that allows the Router type to turn into a Service implementation so that it can be combined with more custom implementations.
-
Updated
Jun 1, 2020 - Go
osctl cluster create works in two modes:
- configs might be supplied via
--input-dir= - configs might be generated with many options customizing the configs
We need to issue warning (or fail) if any flag is used which makes sense only for generated configs while --input-dir was specified.
-
Updated
Jun 4, 2020 - Go
-
Updated
May 25, 2020 - Go
When trying to register grpc server in consul recently was found that LogNet had not properly configured healthcheck. As a result we have service in consul, which doesn't have proper metadata and tags, health check route and so on. We use LogNet in prod, and we strongly need this functionality.
From my point of view, the right way is to use https://www.consul.io/docs/agent/checks.html gr
This is a usage question.
In the Sleuth docs for gRPC, they mention two variants. First one uses io.github.lognet:grpc-spring-boot-starter and io.zipkin.brave:brave-instrumentation-grpc and clients must use SpringAwareManagedChannelBuilder. In the second variant, nothing is said other than _"Grpc Spring Boot Sta
Improve this page
Add a description, image, and links to the grpc topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the grpc topic, visit your repo's landing page and select "manage topics."

Here is some general documentation improvement suggestion regarding flatbuffers. This is what I remember struggling with (from the top of my head). Also some point might be a little bit opinionated.
Some of the points were taken from #5387.