Scary... do users of these platforms know that there have been two LTS releases since v1.2, and therefore those platforms don't have and won't receive any of the fixes that have been applied since

On 9/1/20 9:03 PM, Joe Alewine wrote: There's a thread long ago I could dig up, where I noted that we don't currently have any sort of run-time usage analytics (that I know of

I guess there will be never an accurate answer. But 1.2 is a milestone, GCP still provide 1.2 in marketplace

Is there any data available about people actually running production networks on these unsupported versions? I would be interested to see that. Nobody wants to pull the rug out from people who have

Just because people are still referencing older versions of docs doesn’t necessarily mean there’s an issue. They may still be using the older version. Now, I know we don’t *support* older

I just had a discussion with Pam and I proposed a solution that I thought might solve both of these problems. When we retire doc, we can use GitHub Pages to post their final form. We then add a

The performance epic that serves as an umbrella for v2.x performance items is: https://jira.hyperledger.org/browse/FAB-14513 It is accurate in that the only significant v2.x performance improvement

Hello, I know that there were performance improvements between 1.x and 2.x and changes to the validation process that improved Fabric latency and throughput. However, going through Jira, many of the

dear Fabric ApplicationDeveloper, the next FabricApplication Developer community call is: Thursday3rd Sept: 3pm UTC, 4pm UK time (+1), 11am ET (-5 hrs), 8amPT (-8 hrs) - othertime zoneshere. It

I do not think it is ever wise to remove old documentation, even with automated redirection. There are valid use cases for examining old docs, from understanding how a feature evolved

I am also facing the same issue. @Nicholas Leonardi, did you get any solution of it?

As Joe mentioned on the last Contributor's call, we’ve noticed from Google Analytics of the Fabric documentation that there are still readers viewing older versions of the documentation and we'd

>>Is there a requirement that the CouchDB cannot be used for anything other than the state database? Yes. You don't want any other application to have write privilege to the state database, and

A little bit more context: If there is already a database in CouchDB and if I try to start the peer node, this is the relevant error message: 2020-08-31 11:18:31.083 UTC [couchdb] handleRequest ->

Hi, I intend to use Couchdb as a simple database that handles some other functions other than just behaving as a state database. However, when I create any other databases in Couchdb, the peer node

Hey, I am not sure if I sent this to you privately or not so I am sending it again here. Here are the logs from peer. https://del.dog/logs_fabric.go I am using a simple endorsement

Just to avoid duplication of effort: https://stackoverflow.com/questions/63628826/error-cannot-find-module-fabric-client-in-fabric-1-2

Hyperledger Fabric Documentation Workgroup call - Western hemisphere When: Friday, 28 August 2020 4:00pm to 5:00pm (GMT+01:00)

Reminder: Hyperledger Fabric Documentation Workgroup call - Western hemisphere When: Friday, 28 August 2020, 4:00pm to 5:00pm, (GMT+01:00)

Hello Abhay, Are you using Amazon managed blockchain by chance? If so, they may be multiple versions behind where you would be if you were using native Fabric deployment on AWS. If you are using a