|
Hyperledger Fabric Documentation Workgroup call - Eastern hemisphere - Fri, 02/28/2020
#cal-notice
Hyperledger Fabric Documentation Workgroup call - Eastern hemisphere
When:
Friday, 28 February 2020
6:00am to 7:00am
(GMT+00:00)
Hyperledger Fabric Documentation Workgroup call - Eastern hemisphere
When:
Friday, 28 February 2020
6:00am to 7:00am
(GMT+00:00)
|
By
fabric@lists.hyperledger.org Calendar <noreply@...>
·
#7795
·
|
|
Documentation Workgroup: Agenda for Friday, 28 Feb
Hello!
We will hold thedocumentation workgroup call this Friday as usual -- with both an Easternhemisphere and Western hemisphere call.
You can read allabout last week's call at
Hello!
We will hold thedocumentation workgroup call this Friday as usual -- with both an Easternhemisphere and Western hemisphere call.
You can read allabout last week's call at
|
By
Anthony O'Dowd <a_o-dowd@...>
·
#7794
·
|
|
Upcoming Event: Hyperledger Fabric Documentation Workgroup call - Eastern hemisphere - Fri, 02/28/2020 6:00am-7:00am
#cal-reminder
Reminder: Hyperledger Fabric Documentation Workgroup call - Eastern hemisphere
When: Friday, 28 February 2020, 6:00am to 7:00am, (GMT+00:00)
Reminder: Hyperledger Fabric Documentation Workgroup call - Eastern hemisphere
When: Friday, 28 February 2020, 6:00am to 7:00am, (GMT+00:00)
|
By
fabric@lists.hyperledger.org Calendar <fabric@...>
·
#7792
·
|
|
ANNOUNCEMENT: Hyperledger Fabric v2.0.1 is now available!
The first set of fixes on v2.0 is now available. See release notes for details:
https://github.com/hyperledger/fabric/releases/tag/v2.0.1
We expect the next quarterly release v2.1 to be available by
The first set of fixes on v2.0 is now available. See release notes for details:
https://github.com/hyperledger/fabric/releases/tag/v2.0.1
We expect the next quarterly release v2.1 to be available by
|
By
David Enyeart
·
#7791
·
|
|
Re: Doubt in defining an Asset
Hi - the world state is a set of key-value pairs - the value can be whatever data format you wish. Marshalling these is part of the job of the client applications.
Regards, Matthew.
Matthew B
Hi - the world state is a set of key-value pairs - the value can be whatever data format you wish. Marshalling these is part of the job of the client applications.
Regards, Matthew.
Matthew B
|
By
Matthew White
·
#7790
·
|
|
Doubt in defining an Asset
Hi,
I had two questions.
I wanted to know if it would be possible to define an asset which is self-referential. Also when defining assets such as these, do they work in the traditional way of
Hi,
I had two questions.
I wanted to know if it would be possible to define an asset which is self-referential. Also when defining assets such as these, do they work in the traditional way of
|
By
t-amsi@...
·
#7789
·
|
|
回复: [Hyperledger Fabric] Hashing of World State.
in what aspect you mean hashing the world state?
发件人: fabric@... <fabric@...> 代表 qwert limframe <qwertlimframe@...>
发送时间: 2020年2月27日 0:00
收件人: hyperledger-fabric@...
in what aspect you mean hashing the world state?
发件人: fabric@... <fabric@...> 代表 qwert limframe <qwertlimframe@...>
发送时间: 2020年2月27日 0:00
收件人: hyperledger-fabric@...
|
By
david liu <david-khala@...>
·
#7788
·
|
|
Hashing of World State.
Is the World State Hashed?
If yes, though world state is a constantly changing database. why is it hashed?
Is the World State Hashed?
If yes, though world state is a constantly changing database. why is it hashed?
|
By
qwert limframe
·
#7787
·
|
|
Re: ANNOUNCEMENT: Hyperledger Fabric v1.4.6 is now available!
A few more fixes got merged in the last week, so we went ahead and released Fabric and Fabric CA v1.4.6
A few more fixes got merged in the last week, so we went ahead and released Fabric and Fabric CA v1.4.6
|
By
David Enyeart
·
#7786
·
|
|
回复: [Hyperledger Fabric]
#fabric
#fabric-questions
#fabric-ca
#fabric-ca-client
Before you blame it to fabric-ca-client, please help to re-test it again with `fabric-ca-client` command tool.
发件人: fabric@... <fabric@...> 代表 chauhan.kartik25@...
Before you blame it to fabric-ca-client, please help to re-test it again with `fabric-ca-client` command tool.
发件人: fabric@... <fabric@...> 代表 chauhan.kartik25@...
|
By
david liu <david-khala@...>
·
#7785
·
|
|
Re: [External] RE: [Hyperledger Fabric] Reverting from incorrect capability version
I see.
Then maybe orderer should accept a version it doesn’t recognizeonly when
It’s higher than orderer’s binary version
some–force flag or similar used
This way, at least you can
I see.
Then maybe orderer should accept a version it doesn’t recognizeonly when
It’s higher than orderer’s binary version
some–force flag or similar used
This way, at least you can
|
By
Eryargi, Hakan
·
#7784
·
|
|
Re: Reverting from incorrect capability version
Unfortunately, this is "working as designed". We could revisit the validation that ordering does, but the original capabilities concept was to allow independent management of the orderers and peers.
Unfortunately, this is "working as designed". We could revisit the validation that ordering does, but the original capabilities concept was to allow independent management of the orderers and peers.
|
By
Jason Yellick <jyellick@...>
·
#7783
·
|
|
Re: Reverting from incorrect capability version
Hakan,
I understand your concern. However, the only way for the ordering service to know about the newest application capability levels is to keep it at the latest binary version. A 1.3 ordering
Hakan,
I understand your concern. However, the only way for the ordering service to know about the newest application capability levels is to keep it at the latest binary version. A 1.3 ordering
|
By
Joe Alewine <joe.alewine@...>
·
#7782
·
|
|
Re: Reverting from incorrect capability version
Hi Joe,
Thanks for the clarification. So, there is no way of reverting back from that state except restoring from a backup.
I guess it’s a good idea to guard against this at orderer as
Hi Joe,
Thanks for the clarification. So, there is no way of reverting back from that state except restoring from a backup.
I guess it’s a good idea to guard against this at orderer as
|
By
Eryargi, Hakan
·
#7781
·
|
|
Re: Reverting from incorrect capability version
As it says in our conceptual documentation on capabilities:
Take caution when specifying or modifying an application capability. Because the ordering service does not validate that the capability
As it says in our conceptual documentation on capabilities:
Take caution when specifying or modifying an application capability. Because the ordering service does not validate that the capability
|
By
Joe Alewine <joe.alewine@...>
·
#7780
·
|
|
Re: Reverting from incorrect capability version
Sure, they are attached.
From: Yacov Manevich <YACOVM@...>
Sent: Monday, 24 February 2020 12:56
To: Eryargi, Hakan <hakan.eryargi@...>
Cc: fabric@...
Subject: [External] RE: [Hyperledger Fabric]
Sure, they are attached.
From: Yacov Manevich <YACOVM@...>
Sent: Monday, 24 February 2020 12:56
To: Eryargi, Hakan <hakan.eryargi@...>
Cc: fabric@...
Subject: [External] RE: [Hyperledger Fabric]
|
By
Eryargi, Hakan
·
#7779
·
|
|
Re: Reverting from incorrect capability version
Can you attach logs?
From: "Eryargi, Hakanvia Lists.Hyperledger.Org" <hakan.eryargi=accenture.com@...>
To: Yacov Manevich <YACOVM@...>
Cc: fabric@...
Date: 02/24/2020 01:51
Can you attach logs?
From: "Eryargi, Hakanvia Lists.Hyperledger.Org" <hakan.eryargi=accenture.com@...>
To: Yacov Manevich <YACOVM@...>
Cc: fabric@...
Date: 02/24/2020 01:51
|
By
Yacov
·
#7778
·
|
|
Re: [External] Re: [Hyperledger Fabric] Reverting from incorrect capability version
Yup exactly that happened.
I made a config update for application capability for version V1_4_3, orderers accepted the block and peers crashed.
Below json path to be more
Yup exactly that happened.
I made a config update for application capability for version V1_4_3, orderers accepted the block and peers crashed.
Below json path to be more
|
By
Eryargi, Hakan
·
#7777
·
|
|
Re: Reverting from incorrect capability version
Did you manage to reach a situation wherethe orderers accepted the block but the peers didn't? Were the orderersat a higher software version than the peers?
From: "Eryargi, Hakanvia
Did you manage to reach a situation wherethe orderers accepted the block but the peers didn't? Were the orderersat a higher software version than the peers?
From: "Eryargi, Hakanvia
|
By
Yacov
·
#7776
·
|
|
Reverting from incorrect capability version
Hi,
Is there a way of reverting from an incorrect capability version? (except restoring the whole Fabric network from a backup)
For example Application capability V1_4_3 does not exist, and
Hi,
Is there a way of reverting from an incorrect capability version? (except restoring the whole Fabric network from a backup)
For example Application capability V1_4_3 does not exist, and
|
By
Eryargi, Hakan
·
#7775
·
|