consensus
Here are 392 public repositories matching this topic...
Improve error message when deliver service is asked for a block that doesn't yet exist on the node
Improve error message when deliver service is asked for a block that doesn't yet exist on the node.
This is all we get for now:
[common.deliver] deliverBlocks -> ERRO 18d59 [channel: channel1] Error reading from channel, cause was: NOT_FOUND
It is enough for Fabric developers to know what happened, but not for users or support personnel.
-
Updated
Apr 15, 2022 - Rust
-
Updated
Apr 15, 2022 - Java
-
Updated
Mar 28, 2022 - Go
-
Updated
Nov 27, 2021
-
Updated
Dec 20, 2021
-
Updated
Apr 8, 2022 - Go
A parametrized option to set the blocksize would be useful to experiment with. As quorum is used in a private setting I think this option should be available
大佬,你好,我是@abbykimi,我IDE运行您这个项目的时候,提示有几个漏洞,项目调用了org.apache.logging.log4j:log4j-core等172个开源组件,存在29个安全漏洞,建议你升级下。
漏洞标题:Apache Log4j2 < 2.15.0远程代码执行漏洞
漏洞编号:CVE-2021-44228
漏洞描述:
Apache log4j是java中常用的日志记录组件,攻击者发现在小于2.15.0的版本中存在远程代码执行漏洞。
漏洞原因:
由于log4j2默认支持JNDI在内的Lookup查找机制,当日志内容中包含${foo.bar}样式的内容时,会查找相应的值进行替换。因此当用户请求中的内容通过log4j作为日志内容记录时,攻击者可能通过恶意构造的内容,触发log4j的lookup方法,进而执行恶意代码。
影响范围:[2.0-beta9, 2.3.1)
-
Updated
Mar 29, 2022 - Java
-
Updated
Apr 15, 2022 - C++
-
Updated
Jul 17, 2020 - C++
-
Updated
Apr 15, 2022 - Go
-
Updated
Feb 11, 2022 - Rust
-
Updated
Apr 8, 2022
-
Updated
Feb 21, 2022
Here is a rough idea of what this test should do:
- It should be quite similar to the other tests which are currently in place.
- It should isolate a follower node, write a data to the cluster which will cause that node to fall behind into lagging state, but not into snapshotting state.
- It should then spawn a task which will continue to write data to the cluster.
- Just after it is spawne
-
Updated
Apr 1, 2022 - Go
-
Updated
Apr 15, 2022 - Java
-
Updated
Oct 7, 2020 - Go
-
Updated
Apr 14, 2022 - C++
-
Updated
Jul 12, 2017 - Java
Description
at the beginning of every epoch, there is a period of time when beacon is unavailable (until enough ballots are seen by the node and beacon value determined)
during this time, syncer will see that beacon is not available and will not request tortoise to verify a layer.
but the problem is: syncer uses two goro
-
Updated
Jan 4, 2020 - C++
-
Updated
Apr 14, 2022 - Python
-
Updated
Aug 13, 2018 - JavaScript
Improve this page
Add a description, image, and links to the consensus topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the consensus topic, visit your repo's landing page and select "manage topics."
What happened?
If you don't pass a
--name
argument to youretcd
processes, they will all have the namedefault
and the cluster will operate normally. However, when you add a member, the generatedETCD_INITIAL_CLUSTER
variable will have multiple entries with the name "default". When this environment variable is used,etcd
will parse these into a mapping under a single key ("defau