Skip to content
#

grpc

Here are 2,781 public repositories matching this topic...

jean-airoldie
jean-airoldie commented Jun 6, 2019

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.

  • Regarding the builder:
    • The fact that its kinda like an arena allocator used for serialization.
    • The concept of offsets, what do they repre
johanbrandhorst
johanbrandhorst commented Apr 30, 2020

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

thingsboard
dmolik
dmolik commented Apr 24, 2020

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

ganeshs
ganeshs commented Aug 12, 2019

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

chat
VictorV96
VictorV96 commented Jun 20, 2019

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
benny1611
benny1611 commented May 9, 2019

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!

Surging is a micro-service engine that provides a lightweight, high-performance, modular RPC request pipeline. The service engine supports http, TCP, WS,Grpc, Mqtt, UDP, and DNS protocols. It uses ZooKeeper and Consul as a registry, and integrates it. Hash, random, polling, Fair Polling as a load balancing algorithm, built-in service governance to ensure reliable RPC communication, the engine contains Diagnostic, link tracking for protocol and middleware calls, and integration SkyWalking Distributed APM

  • Updated May 31, 2020
  • C#
goddanao
goddanao commented Apr 16, 2020

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

armeria
ikhoon
ikhoon commented Mar 19, 2020

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

evk1986
evk1986 commented Feb 5, 2020

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

Improve this page

Add a description, image, and links to the grpc topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the grpc topic, visit your repo's landing page and select "manage topics."

Learn more

You can’t perform that action at this time.