Skip to content


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

yanglbme commented Apr 15, 2019


成为 Doocs 项目维护者

本项目 advanced-java,包括 Doocs 开源组织下的所有项目,都欢迎各位朋友参与完善。

如果你提交的内容有价值,且具备规范性,将有机会提升为项目的维护者,直接参与项目的 review、merge 等维护工作,提交内容时也可以直接 pushdoocs/advanced-java 主分支 master 下,无须提交 PR 等待 review。

目前 advanced-java 只有 [yanglbme](http

rkd-msw commented Apr 18, 2019

I'm using TLS on etcd 3.3.12 and have a mix of etcd proxies and masters. The proxies don't seem to honour the --cipher-suites setting, as it ends up with ECDHE-RSA-AES256-GCM-SHA384 despite --cipher-suites=TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 being set.

$ pgrep -laf /usr/bin/etcd
21968 /usr/bin/etcd --listen-client-urls --adv
heat commented Aug 21, 2018

Hi folks, sory about my bad english.
I'm trying get up nsq services at containerum, at containerum the public port to services and container are random. With nsqlookupd and nsqadmin it's easy not a big trouble.
But when we try to run nsqd it's registrer ther right broadcast url but the follow ports that nsqd register is that expose in container and not the service port random assigned with the

GiladShoham commented Apr 14, 2020

Currently, if look at the windows_e2e tests on circle under the write e2e files step, you will see this warning:

Error autodetecting timing type, falling back to weighting by name. Autodetect no matching filename or classname.  If file names are used, double check paths for absolute vs relative.
Example input file: "e2e\\api\\add-many.e2e.1.ts"
Example file from timings: "C:\\Users\\****
adriancole commented Aug 29, 2018

Let's support at least reading "b3" header from a single string, most commonly traceid-spanid-1
It would also be nice to support optionally writing this, especially in message providers or others with constrained environments.

Expected behavior

As discussed on openzipkin/b3-propagation#21 and first implemented here:

JeanGolang commented Feb 7, 2017

Hello Philip!
I think there is an issue with this part of the code of rqlite (store/store.go).

func (s *Store) Database(leader bool) ([]byte, error) {
	if leader && s.raft.State() != raft.Leader {
		return nil, ErrNotLeader
	// Ensure only one snapshot can take place at once, and block all queries.

	f, err := ioutil.TempFile("", "rqlilte-snap-
brson commented Jun 18, 2019

The beginning of the course is pretty boring, and there's not a lot of interesting background reading before project 1. I'm thinking a great way to start it off would be to make the first reading a link to a powerfully inspiring experience report. Something that makes people psyched to learn how to write systems programs in this unique language.

Here are two I've been suggested but haven't eval

candlerb commented Apr 3, 2018

Trying to build under ubuntu 16.04 with go 1.10.1, and following the building instructions:

root@builder:~# go get
package no Go files in /root/go/src/
root@builder:~# cd go/src/
brapse commented Feb 27, 2020

The blockchain v2 reactor utilizes concurrency to saturate the bottleneck of writing blocks to disk. This concurrency is internal to the reactor where the reactor itself will launch and manage internal state machines running as go-routines. This configuration makes testing difficult as we don't know when messages processed by internal state machines will be processed and when we can assert that th

tastyeggs commented Jan 27, 2020

In a cluster configured with Windows Authentication, where a FileShare doesn't require a username and a password, the creation of a new backup policy using Service Fabric Explorer UI fails with an Internal Server Error (500).

Expected Behavior

A new backup policy should be created. At the very least a proper error message should be returned.

Current Behavior

I see an Internal Server

gluster-ant commented Mar 12, 2020

Creator: ndevos at redhat
Time: 20160928T10:44:57

Description of problem: adds new public functions for gfapi applications that want to receive upcall events. These functions are sparsely documented, which need to improve.

Version-Release number of selected component (if applicable):
mainline (+backports)

Improve this page

Add a description, image, and links to the distributed-systems 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 distributed-systems topic, visit your repo's landing page and select "manage topics."

Learn more

You can’t perform that action at this time.