Hi Nekia, As you may have seen that the stories in FAB-106 are only related to checkpointing. Archiving/Pruning will perhaps better be a separate Epic as it is orthogonal and sizable enough. Still,

Thanks Manish, I will do so.

https://jira.hyperledger.org/browse/FAB-17726 From: "Park, Jungil"<Jungil.Park@...> To: 'Yacov Manevich' <YACOVM@...> Cc: "'fabric@...'"<fabric@...> Date: 04/09/2020 03:24

Hi Yacov, I have tried to create Jira ticket but I can’t. My user account is no longer to log in to either linux foundation or hyperledger jira. jungil.park@... Can you create one for

Please open a JIRA so I can attach it tothe pull requests in https://github.com/hyperledger/fabric/pulls From: "Park, Jungil"<jungil.park@...> To: 'Yacov Manevich' <YACOVM@...> Cc:

Oh, okay, I understand you in wrong way. Sorry for this. I will wait for your response. Thanks again for the help. Met vriendelijke groet / Kind regards Jungil Park ABN AMRO | ABN AMRO

If it was a known issue, there was no suchissue. I'm currently trying to reproduce itlocally on 1.4 and 2.0, so far without success. It's unlikely that 2.0 fixes it, asthe communication code is the

Hi Yacov, Thanks a lot for the response. We are actually on the way to upgrade to 2.0. In the same way, this issue would be solved once we upgrade to 2.0? And it seems it is known issue

Yes I'll push a fix to all branches, giveme a few hours. Regardless, you should upgrade to thelatest Fabric version of 1.4.x branch and not use 1.4.0 From: "Park, Jungil"<jungil.park@...> To:

Hi Team, Can anyone help with this? Met vriendelijke groet / Kind regards Jungil Park ABN AMRO | ABN AMRO CLEARING Gustav Mahlerlaan 10 | 1082 PP Amsterdam | The Netherlands Mob +31

Hi Manish and Team, In "FAB-106 Ledger checkpoint and pruning/archiving" feature, can we add another story related to archiving? https://jira.hyperledger.org/browse/FAB-106 We got a chance to share

Reminder: Hyperledger Fabric Documentation Workgroup call - Eastern hemisphere When: Friday, 10 April 2020, 6:00am to 7:00am, (GMT+01:00) Europe/London Where:https://zoom.us/j/6223336701 View

It's likely a bug. The gossip code is sitting in a select where one case is receiving from an error channel and the other is receiving a message. [1] If, however, an error occurs when converting an

Hi Prasanth, The general idea was to be conservative in exposing APIs and configurations until a need is realized. If you are keen to propose and implement this change, I would encourage you to do so.

There are a lot of variables/unknowns to work through here. The mailing list probably isn't the ideal place for that. Can you join the Hyperledger RocketChat community at https://chat.hyperledger.org

I removed the init-required but still same error. queryInstalled and queryCommitted returned the correct values Installed chaincodes on peer: Package ID:

A few other questions: - I notice you have --init-required set for your chaincode. Are you invoking the init function first? - Which tutorial are you following from readthedocs? Thanks, Will

Yup here are the commands and the chaincode function. Something very simple async invokeTransaction(ctx, id, jsonPayload) { await ctx.stub.putState(id, JSON.stringify(jsonPayload));

Hi Nicholas, Can you share more information about the chaincode, such as the commands you used to install/approve/commit the chaincode and the invoke command you're submitting? We should be able to

Hey guys, I've been trying to get a chaincode to invoke with two basic functions. I'm able to package, install to the peer, approve and commit the chaincode. But when I invoke, I get the following