rjones (Tue, 15 Jan 2019 04:46:30 GMT):
Grid is a supply chain project

rjones (Tue, 15 Jan 2019 18:01:26 GMT):
User User_1 added by rjones.

rjones (Tue, 15 Jan 2019 18:02:11 GMT):
https://github.com/hyperledger/grid

amundson (Tue, 15 Jan 2019 18:40:07 GMT):
@rjones thanks!

agunde (Tue, 15 Jan 2019 18:44:04 GMT):
Has joined the channel.

arsulegai (Tue, 15 Jan 2019 18:45:37 GMT):
Has joined the channel.

rjones (Tue, 15 Jan 2019 18:46:16 GMT):
I'm working through: https://wiki2.hyperledger.org/display/~ryjones/Grid+New+Project+Checklist

amundson (Tue, 15 Jan 2019 18:47:30 GMT):
ah, cool

amundson (Tue, 15 Jan 2019 18:49:06 GMT):
first topic for this channel will be the github repos we need. I'm thinking 'grid' or 'grid-core', 'grid-contrib', 'grid-website', 'grid-rfcs'

amundson (Tue, 15 Jan 2019 18:49:16 GMT):
need to wait for everyone to join to have the discussion though :)

rjones (Tue, 15 Jan 2019 18:50:29 GMT):
I suspect there will be a lot of helpdesk tickets soon 🧐

amundson (Tue, 15 Jan 2019 18:53:18 GMT):
has there been any change in HL recommendations for build systems? re: jenkins vs. travis discussions?

amundson (Tue, 15 Jan 2019 18:53:37 GMT):
(I know this was a discussion w/Ursa but I didn't track the resolution.)

rjones (Tue, 15 Jan 2019 18:54:07 GMT):
not that I'm aware of. Each project is kind of doing its own thing.

TomBarnes (Tue, 15 Jan 2019 18:58:44 GMT):
Has joined the channel.

rjones (Tue, 15 Jan 2019 18:59:15 GMT):
I sent you invites to both of these: https://github.com/orgs/hyperledger/teams?utf8=✓&query=grid

rjones (Tue, 15 Jan 2019 18:59:25 GMT):
to help get bootstrapped

rjones (Tue, 15 Jan 2019 18:59:46 GMT):
once you accept, I'll make you a maintainer

rjones (Tue, 15 Jan 2019 19:00:03 GMT):
amundson

rjones (Tue, 15 Jan 2019 19:00:53 GMT):
One difficulty is GitHub only lets an org pin six repos. We have pinned all of the projects... until now

amundson (Tue, 15 Jan 2019 19:01:31 GMT):
what does it mean to pin a repo?

amundson (Tue, 15 Jan 2019 19:03:10 GMT):
I don't see the github team requests

pschwarz (Tue, 15 Jan 2019 19:03:44 GMT):
Has joined the channel.

amundson (Tue, 15 Jan 2019 19:08:52 GMT):
@rjones can we also create a 'Grid Admins' with the same folks from 'Sawtooth Admins'?

rjones (Tue, 15 Jan 2019 19:10:53 GMT):
what is your github ID?

amundson (Tue, 15 Jan 2019 19:11:19 GMT):
"vaporos"

rjones (Tue, 15 Jan 2019 19:11:54 GMT):
OK I deleted the old groups. I did send invites to that account for both of them.

amundson (Tue, 15 Jan 2019 19:12:07 GMT):
ok

rjones (Tue, 15 Jan 2019 19:14:17 GMT):
you're an maintainer for "grid admins", you should be able to add people etc

varinder (Tue, 15 Jan 2019 19:15:48 GMT):
Has joined the channel.

rjones (Tue, 15 Jan 2019 19:18:41 GMT):
@amundson https://github.com/orgs/hyperledger/teams/sawtooth-admins/members and https://github.com/orgs/hyperledger/teams/grid-admins/members are now the same membership. Fair winds and following seas

jsmitchell (Tue, 15 Jan 2019 19:23:48 GMT):
Has joined the channel.

jsmitchell (Tue, 15 Jan 2019 19:23:56 GMT):
hello

rjones (Tue, 15 Jan 2019 19:24:21 GMT):
salut!

amundson (Tue, 15 Jan 2019 19:29:16 GMT):
ok, I should have said the same as 'Sawtooth Core Admins', so I removed the extra folks from Grid Admins

jsmitchell (Tue, 15 Jan 2019 19:30:48 GMT):
User User_2 added by jsmitchell.

amundson (Tue, 15 Jan 2019 19:31:13 GMT):
@rjones so I can go ahead and create those teams now -- 'Grid Maintainers' and 'Grid Contributors'?

cecchi (Tue, 15 Jan 2019 19:46:26 GMT):
first!

amundson (Tue, 15 Jan 2019 19:46:35 GMT):
too late

jsmitchell (Tue, 15 Jan 2019 19:48:13 GMT):
https://www.gs1.org/sites/default/files/docs/barcodes/GS1_General_Specifications.pdf

jsmitchell (Tue, 15 Jan 2019 19:53:17 GMT):
gs1 controls some master data regarding the mapping of identifier prefix to organization/company and location identifiers

rbuysse (Tue, 15 Jan 2019 19:53:30 GMT):
Has joined the channel.

jsmitchell (Tue, 15 Jan 2019 19:55:30 GMT):
https://www.gs1us.org/tools/gs1-company-database-gepir

jsmitchell (Tue, 15 Jan 2019 20:19:15 GMT):
thoughts on how to map system org identities to ownership of company records within the gs1 dataset? Maybe some #indy style self-soverign identity approach with gs1 providing a proof?

jsmitchell (Tue, 15 Jan 2019 20:22:56 GMT):
relying on trusted CAs as root of trust?

ltseeley (Tue, 15 Jan 2019 21:59:32 GMT):
Has joined the channel.

tomislav (Tue, 15 Jan 2019 22:07:56 GMT):
Has joined the channel.

LinuxLearner1 (Tue, 15 Jan 2019 23:01:54 GMT):
Has joined the channel.

rjones (Tue, 15 Jan 2019 23:05:14 GMT):
@amundson do it to it

adamgering (Tue, 15 Jan 2019 23:50:40 GMT):
Has joined the channel.

MohitJuneja (Tue, 15 Jan 2019 23:51:59 GMT):
Has joined the channel.

RealDeanZhao (Wed, 16 Jan 2019 03:34:15 GMT):
Has joined the channel.

RealDeanZhao (Wed, 16 Jan 2019 07:28:22 GMT):
Hi, does grid use sawtooth?

amundson (Wed, 16 Jan 2019 15:38:58 GMT):
yes, the traceability code for grid uses sawtooth, and is derived from sawtooth supply chain

jsmitchell (Wed, 16 Jan 2019 16:19:29 GMT):
In the spirit of other top level projects like Explorer and Composer, we welcome contributions to support compatibility with the entire Hyperledger greenhouse

jsmitchell (Wed, 16 Jan 2019 16:27:02 GMT):
This is not a Sawtooth-only project. The vision is for a set of open source frameworks and libraries for businesses to collaborate on and use to build great apps on any distributed (or centralized) platform.

jsmitchell (Wed, 16 Jan 2019 16:27:52 GMT):
The more places that code can run the better.

amundson (Wed, 16 Jan 2019 16:28:50 GMT):
good point - even the traceability piece will evolve past it's sawtooth roots in the coming months

jsmitchell (Wed, 16 Jan 2019 16:48:34 GMT):
Touching on the gs1/corp identity thing, I think the way let's encrypt does it is interesting via "proof of domain control": https://letsencrypt.org/how-it-works/

jsmitchell (Wed, 16 Jan 2019 16:52:44 GMT):
@cecchi thoughts on what would be palatable to orgs as a lightweight way to prove who they are?

jsmitchell (Wed, 16 Jan 2019 16:53:53 GMT):
like does this lets encrypt process seem onerous for big companies, for example?

rranjan3 (Wed, 16 Jan 2019 17:15:25 GMT):
Has joined the channel.

danintel (Wed, 16 Jan 2019 19:43:14 GMT):
Has joined the channel.

amolk (Thu, 17 Jan 2019 16:20:43 GMT):
Has joined the channel.

danintel (Thu, 17 Jan 2019 17:52:27 GMT):
@varinder off-hand it looks like a proxy problem. It looks like it's redirecting. You can find out if it is going to a proxy by getting the headers. Use something like `wget --server-response http://localhost:8024/agents`

varinder (Thu, 17 Jan 2019 17:56:19 GMT):
@danintel yes, its under the intel proxy :sweat_smile:]

varinder (Thu, 17 Jan 2019 17:56:19 GMT):
@danintel yes, its under the intel proxy :sweat_smile:

varinder (Thu, 17 Jan 2019 17:56:19 GMT):
@danintel yes, its under the intel proxy :sweat_smile: DM'ed you

danintel (Thu, 17 Jan 2019 18:00:57 GMT):
@varinder Try setting NO_PROXY and no_proxy. I sent you a DM. I always download and run `setup_intel_proxy.sh` available internally at https://intelpedia.intel.com/Proxy_at_Intel

danintel (Thu, 17 Jan 2019 18:18:05 GMT):
Proxy support: I looked at the source repos and it appears that the Supply Chain Dockerfiles supports proxy environment variables (such as NO_PROXY). But I see no proxy support in the Education Supply Chain Dockerfiles. If anyone knows more, please correct me.

arsulegai (Thu, 17 Jan 2019 18:31:42 GMT):
Are you talking about "-environment" tag in sawtooth-supply-chain?

jsmitchell (Thu, 17 Jan 2019 18:32:23 GMT):
Let's keep sawtooth-supply-chain troubleshooting on #sawtooth-supply-chain

amundson (Thu, 17 Jan 2019 18:37:27 GMT):
Continuing w/git discussion. I heard a preference off-line to keep 'grid' and not switch to 'grid-core'. Sounds fine to me. The other repos proposed are 'grid-contrib', 'grid-website', 'grid-rfcs', which I will request shortly (barring discussion which would change this list).

agunde (Thu, 17 Jan 2019 18:38:55 GMT):
I agree with keeping grid and not grid-core fwiw

amundson (Thu, 17 Jan 2019 20:44:38 GMT):
the grid repo has been initialized with the contents from sawtooth-supply-chain. I'm going to start submitting PRs to it shortly to turn it into the starting point for grid

amundson (Thu, 17 Jan 2019 21:26:45 GMT):
I requested a DNS entry for the website and submitted the request for the repos above.

rbuysse (Thu, 17 Jan 2019 22:08:38 GMT):
are we gonna decom the supply-chain repo?

amundson (Thu, 17 Jan 2019 22:47:18 GMT):
not immediately

amundson (Thu, 17 Jan 2019 22:48:28 GMT):
it may continue to serve as a good application example, if we deviate significantly from it w/Grid (which seems very possible)

knagware9 (Fri, 18 Jan 2019 07:33:44 GMT):
Has joined the channel.

amiec (Sun, 20 Jan 2019 17:00:29 GMT):
Has joined the channel.

RahulToraskar (Mon, 21 Jan 2019 04:18:27 GMT):
Has joined the channel.

AvinashSingh2 (Mon, 21 Jan 2019 04:23:30 GMT):
Has joined the channel.

RahulToraskar (Mon, 21 Jan 2019 04:39:49 GMT):
what is the future roadmap for this project? Do we have any architecture that we can refer to?

vanditasaxena (Mon, 21 Jan 2019 11:02:25 GMT):
Has joined the channel.

jsmitchell (Mon, 21 Jan 2019 22:51:11 GMT):
@RahulToraskar it's just getting kicked off -- we are thinking of first focusing on product models including GS1/GTIN.

Tandeep23 (Tue, 22 Jan 2019 04:34:28 GMT):
Has joined the channel.

Chaim (Tue, 22 Jan 2019 17:06:17 GMT):
Has joined the channel.

kelly_ (Tue, 22 Jan 2019 17:49:18 GMT):
Has joined the channel.

rinor (Tue, 22 Jan 2019 17:51:49 GMT):
Has joined the channel.

bdjidi (Tue, 22 Jan 2019 18:02:16 GMT):
Has joined the channel.

mfford (Tue, 22 Jan 2019 19:34:21 GMT):
Has joined the channel.

amundson (Tue, 22 Jan 2019 22:20:56 GMT):
I was talking with @TelegramSam about Indy agents a few weeks ago and he gave some links, which I'm going to re-post here. It might be good reading for future discussions on patterns.

TelegramSam (Tue, 22 Jan 2019 22:20:56 GMT):
Has joined the channel.

amundson (Tue, 22 Jan 2019 22:21:23 GMT):
https://github.com/hyperledger/indy-hipe/tree/master/text/0021-message-types

amundson (Tue, 22 Jan 2019 22:22:06 GMT):
https://github.com/hyperledger/indy-hipe/tree/master/text/0022-cross-domain-messaging

amundson (Tue, 22 Jan 2019 22:22:17 GMT):
https://github.com/hyperledger/indy-hipe/blob/42fd315eed4a502f34a956abafd80a73700dbcb3/text/agent-message-routing/README.md

amundson (Tue, 22 Jan 2019 22:22:25 GMT):
https://github.com/hyperledger/indy-hipe/blob/ec6f2ac8355b625a987a68cf7a49ef1d3ea22c96/text/feature-discovery/README.md

amundson (Tue, 22 Jan 2019 22:22:35 GMT):
https://github.com/hyperledger/indy-hipe/blob/318f265d508a3ddf1da7d91c79ae4ae27ab9142b/text/localized-messages/README.md

amundson (Tue, 22 Jan 2019 22:22:52 GMT):
(the last three are in-progress)

anaswar (Wed, 23 Jan 2019 05:02:47 GMT):
Has joined the channel.

JonathanC (Wed, 23 Jan 2019 15:35:54 GMT):
Has joined the channel.

JPonna (Wed, 23 Jan 2019 15:59:24 GMT):
Has joined the channel.

JPonna (Wed, 23 Jan 2019 16:44:15 GMT):
@amundson @rjones This is a great project, one question though - will the network design be modular like fabric. Supply chain processes that we are working on currently desire for a modular architecture with plug and play components for scalability and sustenance.

jsmitchell (Wed, 23 Jan 2019 16:59:08 GMT):
@JPonna the grid components are unlikely to even take a position on what the 'network' is. That's probably a job for the lower layers of the stack (e.g. the underlying ledger that is processing the grid transactions and maintaining state).

jsmitchell (Wed, 23 Jan 2019 17:00:15 GMT):
Grid will help define the transaction formats, data types, storage formats, roles, permissions, etc. to allow applications to be built quickly

jsmitchell (Wed, 23 Jan 2019 17:01:36 GMT):
Product is a good example. Instead of getting together with a consortium and saying "ok, first we need to define what a product is, and how we represent it, and how products are created and owned, etc...", we can say "we all use GS1 GTIN identifiers for our products, here's a grid component which already lays all that out, let's use it and focus on higher value stuff"

jsmitchell (Wed, 23 Jan 2019 17:06:39 GMT):
and if we have other components like trading, or certification/audit, or shipping/BOL that all speak a common language (e.g. the trading rules operate on the exchange of Grid products as part of a trade), then it becomes possible to assemble a sophisticated set of business functionality very quickly

SMiskey (Wed, 23 Jan 2019 18:16:32 GMT):
Has joined the channel.

BretCarpenter (Wed, 23 Jan 2019 19:28:06 GMT):
Has joined the channel.

BretCarpenter (Wed, 23 Jan 2019 19:29:55 GMT):
How does Frabric or Sawtooth and Geospatial align with this project

MikeRichardson (Wed, 23 Jan 2019 19:45:03 GMT):
Has joined the channel.

varinder (Thu, 24 Jan 2019 00:49:12 GMT):
I am having issues transferring assets both using provided Sawtooth Fish Client Demo & Asset Track Demo. Also i am facing the same issue in my development environment.. These are the steps I am taking to transfer asset -> https://demo.bitwise.io/asset 1. create a new account via Login/Signup 2. create new asset from the newly created account 3. transfer the asset to another existing user 4. issue: owner does not change despite the asset transfer "Finalize". In my local development environment owner does not change despite the asset transfer and I see repeating error in shell "supply-server | Received GET request for /agents from ::ffff:172.26.0.10 supply-asset-client | 172.26.0.1 - - [19/Jan/2019:00:58:51 +0000] "GET /api/agents HTTP/1.1" 304 - supply-server | Received GET request for /agents from ::ffff:172.26.0.10 supply-asset-client | 172.26.0.1 - - [19/Jan/2019:00:58:54 +0000] "GET /api/agents HTTP/1.1" 304 - supply-server | Received GET request for /agents from ::ffff:172.26.0.10"

kelly_ (Thu, 24 Jan 2019 02:30:47 GMT):
@varinder the other user needs to 'accept' the asset

kelly_ (Thu, 24 Jan 2019 02:30:55 GMT):
assets are not 'push' in supply chain

kelly_ (Thu, 24 Jan 2019 02:31:02 GMT):
they require a request to transfer and an accept

kelly_ (Thu, 24 Jan 2019 02:31:25 GMT):
so you will need to log into the gui under the 2nd user, go to the asset, and accept the transfer

kelly_ (Thu, 24 Jan 2019 02:31:42 GMT):
the 'finalize' button is confusing, and it would probably be good to relabel it

kelly_ (Thu, 24 Jan 2019 02:31:57 GMT):
finalize - 'finalizes the assets life', this basically closes out the asset record

PaulaBanks (Thu, 24 Jan 2019 04:23:53 GMT):
Has joined the channel.

umamaheswarv (Thu, 24 Jan 2019 05:09:41 GMT):
Has joined the channel.

varinder (Thu, 24 Jan 2019 05:38:25 GMT):
Okay, I will try. I am unable to test on the demo, seeing extremely long loading times when creating/viewing assets

varinder (Thu, 24 Jan 2019 05:38:37 GMT):

Clipboard - January 23, 2019 9:38 PM

tejaswikhanna (Thu, 24 Jan 2019 05:47:49 GMT):
Has joined the channel.

YashDesai1 (Thu, 24 Jan 2019 07:05:30 GMT):
Has joined the channel.

PaulaBanks (Thu, 24 Jan 2019 07:53:39 GMT):
Hi everyone. I am going through the supply chain example and I can't seem to understand how data from the sensor is transferred to the blockchain. I would like to collect things like location data from an rfid tag and add it to the chain. Is there an illustration of this on the fishnet case? Thanks.

yinkokpheng (Thu, 24 Jan 2019 08:35:25 GMT):
Has joined the channel.

dyeghikoo (Thu, 24 Jan 2019 08:57:32 GMT):
Has joined the channel.

mrjdomingus (Thu, 24 Jan 2019 10:14:21 GMT):
Has joined the channel.

vkblue (Thu, 24 Jan 2019 14:31:56 GMT):
Has joined the channel.

Aswath8687 (Thu, 24 Jan 2019 15:38:36 GMT):
Has joined the channel.

danintel (Thu, 24 Jan 2019 16:52:09 GMT):
Has left the channel.

movee2005 (Thu, 24 Jan 2019 18:16:40 GMT):
Has joined the channel.

nage (Thu, 24 Jan 2019 21:38:32 GMT):
Has joined the channel.

varinder (Thu, 24 Jan 2019 21:41:39 GMT):
[ ](https://chat.hyperledger.org/channel/grid?msg=msGurBEoETtrB7HBd) @PaulaBanks I believe the UI in the supply chain example is for manual data insertion only. For collecting data via sensors, the sensors will probably need to submit rest api call (if running natively, browse something like localhost:8024/batches) as lightly mentioned here "For the adventurous, these actions can also be accomplished directly with the REST API running on the Supply Chain server, perfect for automated IoT sensors."

amundson (Thu, 24 Jan 2019 21:48:02 GMT):
@PaulaBanks @varinder That's right, we don't have code that runs on any particular sensor or device, we just submit transactions in the way we would do it on the device. The two apps (fish, assets) are examples of how you can use the underlying smart contract functionality. There is some automation/example of that in the JS code. Grid is going to switch all the npm-based stuff to Rust though, so that stuff will quickly be #sawtooth-supply-chain specific and not Grid-specific.

PaulaBanks (Fri, 25 Jan 2019 04:40:16 GMT):
Thanks @varinder @amundson

Ryan2 (Fri, 25 Jan 2019 06:45:20 GMT):
Has joined the channel.

IgorSim (Fri, 25 Jan 2019 08:18:30 GMT):
Has joined the channel.

bmsuite (Fri, 25 Jan 2019 15:47:39 GMT):
Has joined the channel.

DatNguyen (Fri, 25 Jan 2019 20:24:55 GMT):
Has joined the channel.

Its_Blockchain_Ira (Sat, 26 Jan 2019 17:34:02 GMT):
Has joined the channel.

KrishnaGundala (Mon, 28 Jan 2019 07:17:21 GMT):
Has joined the channel.

Tatse (Mon, 28 Jan 2019 07:44:23 GMT):
Has joined the channel.

peter.danko (Mon, 28 Jan 2019 11:45:46 GMT):
Has joined the channel.

deepakvparmar (Mon, 28 Jan 2019 15:26:13 GMT):
Has joined the channel.

deepakvparmar (Mon, 28 Jan 2019 15:29:47 GMT):
I would like to know whether Grid currently supporting Fabric?

jsmitchell (Mon, 28 Jan 2019 15:55:50 GMT):
@deepakvparmar grid is based on Sabre WASM smart contracts which currently are supported by Sawtooth. We welcome contributions/compatibility with other top level Hyperledger projects, including Fabric.

JonasM (Mon, 28 Jan 2019 16:21:03 GMT):
Has joined the channel.

tkuhrt (Mon, 28 Jan 2019 16:36:27 GMT):
Has joined the channel.

deepakvparmar (Mon, 28 Jan 2019 18:21:26 GMT):
[ ](https://chat.hyperledger.org/channel/grid?msg=6nVuhTikBbBVeNP34v) @jsmitchell Thank you. In summary, Currently only supporting Sawtooth, but may support other platforms if getting support from community, but not working actively right now to support Hyperledger Fabril.

jsmitchell (Mon, 28 Jan 2019 18:32:06 GMT):
it's an open project. PRs are welcome. We would love to see support for Fabric.

atcvince (Mon, 28 Jan 2019 21:39:29 GMT):
Has joined the channel.

robinrob (Tue, 29 Jan 2019 14:43:26 GMT):
Has joined the channel.

danintel (Tue, 29 Jan 2019 23:25:43 GMT):
Has joined the channel.

Logi (Wed, 30 Jan 2019 09:28:37 GMT):
Has joined the channel.

Logi (Wed, 30 Jan 2019 09:43:49 GMT):
Hello All, this is Lokesh.. I have been into Hyperledger fabric and Sawtooth. Excited to see how Grid can support and make the supply chain implementation simple.

cecchi (Wed, 30 Jan 2019 15:04:15 GMT):
thank you lokesh please stay excited

Silona (Wed, 30 Jan 2019 16:42:02 GMT):
Has joined the channel.

RohanMudaliar (Thu, 31 Jan 2019 05:29:37 GMT):
Has joined the channel.

MuthuT (Thu, 31 Jan 2019 05:36:14 GMT):
Has joined the channel.

DhruvKumar (Fri, 01 Feb 2019 08:51:46 GMT):
Has joined the channel.

ConnorChristie (Fri, 01 Feb 2019 19:06:42 GMT):
Has joined the channel.

pasimoes (Sat, 02 Feb 2019 00:59:33 GMT):
Has joined the channel.

RicardoGarcia (Sun, 03 Feb 2019 21:50:54 GMT):
Has joined the channel.

RicardoGarcia (Sun, 03 Feb 2019 21:52:04 GMT):
Hi all, this is Ricardo from ScanTrust. We are very active in the blockchain for supply chain vertical and would like to stay involved in this project.

cecchi (Mon, 04 Feb 2019 13:47:26 GMT):
that's great to hear thank you Ricardo

Claudius1 (Wed, 06 Feb 2019 16:11:03 GMT):
Has joined the channel.

jsmitchell (Wed, 06 Feb 2019 16:39:50 GMT):
We are thinking of setting up regular meetings to discuss grid collaboration and contribution. If you are interested in attending, please let me know your timezone (GMT +/-) so we can get a good sense of something that will work for most parties.

Claudius1 (Wed, 06 Feb 2019 16:43:30 GMT):
That would be great. I'm in Eastern Time zone (GMT -5). Thank you.

mfford (Wed, 06 Feb 2019 18:49:30 GMT):
A new meeting for Hyperledger Grid Contributors has been added to the Hyperledger Community Meetings Calendar. Here are the details:

mfford (Wed, 06 Feb 2019 18:50:23 GMT):
Hyperledger Grid Contributor Meeting Mon, February 11, 11am – 12pm Frequency: Weekly Day: Monday 2/11 to start (recurring on Mondays) Time: 11am CDT Duration: 1 Hour Facilitator: Mark Ford Zoom: Join Zoom Meeting https://zoom.us/j/815586463 One tap mobile +16468769923,,815586463# US (New York) +16699006833,,815586463# US (San Jose)

kaushikmehta (Thu, 07 Feb 2019 01:08:05 GMT):
Has joined the channel.

kaushikmehta (Thu, 07 Feb 2019 01:10:55 GMT):
[ ](https://chat.hyperledger.org/channel/grid?msg=SNmuuyBwt3niRCZRW) @mfford is this open for anyone to join? I'm not a contributor yet, but I would like to sit in if possible.

amundson (Thu, 07 Feb 2019 04:12:51 GMT):
@kaushikmehta yes, it is open to everyone. feel free to join.

amolk (Thu, 07 Feb 2019 04:16:43 GMT):
@mfford any chance the meeting could be scheduled a little earlier? It is currently from 10:30pm-11:30pm in India.

mfford (Thu, 07 Feb 2019 16:05:18 GMT):
@amolk My apologies, as I understand that is late for some folks interested in attending, but 11am is the time that seems to work best for the Grid maintainers, so we would like to make sure they can attend the initial meetings. As we go forward, we can determine if there are better options.

jsmitchell (Thu, 07 Feb 2019 16:14:10 GMT):
post the first monday meeting, we should definitely look for a time that works for better for all interested parties

jsmitchell (Thu, 07 Feb 2019 16:14:10 GMT):
post the first monday meeting, we should definitely look for a time that works better for all interested parties

amundson (Thu, 07 Feb 2019 16:22:13 GMT):
@mfford we should maybe send a note out to the mailing list with the meeting details for those not monitoring rocketchat

mfford (Thu, 07 Feb 2019 16:27:22 GMT):
posted to grid@lists.hyperledger.org

Claudius1 (Thu, 07 Feb 2019 16:32:04 GMT):
If there are contributors from asian time zones (i'm sure there are), we probably need to think about having an added call during a more friendly time for them.

Claudius1 (Thu, 07 Feb 2019 17:02:18 GMT):
Is there a list of current maintainers for Grid project? Not sure about the process for maintainers in projects in incubation status. Many thanks

amundson (Thu, 07 Feb 2019 17:05:41 GMT):
@Claudius1 https://github.com/hyperledger/grid/blob/master/MAINTAINERS.md

amundson (Thu, 07 Feb 2019 17:08:37 GMT):
this will evolve over time, but is basically going to be derived from participation. we plan to adopt an governance process similar to that of sawtooth https://github.com/hyperledger/sawtooth-rfcs/

Claudius1 (Thu, 07 Feb 2019 17:19:42 GMT):
@amundson Perfect. Thanks! I know it's somewhere on the Hyperledger wiki, but maybe you have it handy: is there a role description for a Maintainers, subteam members, subteam leads, etc?

amundson (Thu, 07 Feb 2019 17:20:15 GMT):
for sawtooth, it is this doc - https://github.com/hyperledger/sawtooth-rfcs/blob/master/text/0006-sawtooth-governance.md

amundson (Thu, 07 Feb 2019 17:21:48 GMT):
so, I'll submit a governance proposal for grid based on that after I have the RFCs repo setup

Claudius1 (Thu, 07 Feb 2019 18:19:42 GMT):
@amundson great, thanks!

amundson (Thu, 07 Feb 2019 19:55:20 GMT):
I just merged changes to the grid repo and the grid-contrib repo which splits the track and trace code into two pieces, the platform pieces (remaining in the grid repo) and the example pieces (which are now in the grid-contrib repo).

amundson (Thu, 07 Feb 2019 19:58:43 GMT):
if someone is looking for a way to contribute short-term, the docker compose files in the grid-contrib repo need to be repaired so the examples can be run with the platform code in the grid repo.

amundson (Thu, 07 Feb 2019 20:01:13 GMT):
remaining items for track and trace in the grid repo itself: 1) fix up the docs, 2) upgrade docker-compose files to sawtooth 1.1.

Claudius1 (Fri, 08 Feb 2019 16:37:53 GMT):
All, forgive the likely basic question, but since i'm a newbie: i saw somebody mentioning a supply chain example. Not sure where that is. Is that in Sawtooth? Not clear how to get started with Grid (understanding this is just the beginning).

amundson (Fri, 08 Feb 2019 18:57:21 GMT):
@Claudius1 there are two pieces currently. there is the code in the grid repo https://github.com/hyperledger/grid/, including the initial track an trace smart contract. we will be adding some more smart contracts shortly, like pike (org/identity), product catalog, etc. we will also add other platform code there like a grid CLI, state delta processors (database export), and reusable UI components. Then we also have the grid-contrib repo, https://github.com/hyperledger/grid-contrib/, which contains examples, prototypes, etc. that are not yet part of the platform. this is where the track and trace example code for the fishnet and asset track are, as well as a track and trace rest API and state delta export code.

amundson (Fri, 08 Feb 2019 18:59:43 GMT):
the platform code in can be run by cloning the repo and doing 'docker-compose up'. but, as it does not include a client, it is not super exciting unless you are developing with it. the track and trace code in contrib works but because I just split it off to contrib, it needs some work before it can be easily started up with docker-compose. (see my above TODO commentary).

amundson (Fri, 08 Feb 2019 19:02:02 GMT):
The track-and-trace code is currently substantially similar to sawtooth supply chain (currently only a few modifications since we forked it) -- https://github.com/hyperledger/sawtooth-supply-chain/ and there is a demo of that running at https://github.com/hyperledger/sawtooth-supply-chain/ and https://demo.bitwise.io/asset/#!/

Claudius1 (Fri, 08 Feb 2019 19:49:15 GMT):
@amundson Many thanks :thumbsup:

adeebahmed (Fri, 08 Feb 2019 21:24:40 GMT):
Has joined the channel.

colincmcc (Sun, 10 Feb 2019 20:38:07 GMT):
Has joined the channel.

singh_0 (Mon, 11 Feb 2019 09:58:52 GMT):
Has joined the channel.

slushpupie (Mon, 11 Feb 2019 14:29:16 GMT):
Has joined the channel.

mfford (Mon, 11 Feb 2019 15:04:14 GMT):
REMINDER: The first Weekly Hyperledger Grid Contributor Meeting is today! Here is the meeting information: Mon, February 11, 11am – 12pm Frequency: Weekly Day: Monday 2/11 to start (recurring on Mondays) Time: 11am CDT Duration: 1 Hour Facilitator: Mark Ford Zoom: Join Zoom Meeting https://zoom.us/j/815586463 One tap mobile +16468769923,,815586463# US (New York) +16699006833,,815586463# US (San Jose)

mfford (Mon, 11 Feb 2019 16:33:59 GMT):
Dial by your location +1 646 876 9923 US (New York) +1 669 900 6833 US (San Jose) +1 408 638 0968 US (San Jose) Meeting ID: 815 586 463 Find your local number: https://zoom.us/u/abPOgiNnD3

adamgering (Mon, 11 Feb 2019 17:29:44 GMT):
What are the instructions to subscribe to the mailing list? Is it just send a message with subject "subscribe" to "mailto:grid@lists.hyperledger.org" ?

Claudius1 (Mon, 11 Feb 2019 17:41:06 GMT):
you can join from here: https://lists.hyperledger.org/g/grid

adamgering (Mon, 11 Feb 2019 18:03:10 GMT):
thx

TBdori (Tue, 12 Feb 2019 01:49:00 GMT):
Has joined the channel.

Tatse (Tue, 12 Feb 2019 09:56:26 GMT):
I unfortunately missed the meeting yesterday. Are there any notes?

Claudius1 (Tue, 12 Feb 2019 16:44:38 GMT):
All, a couple of quick general questions. I know in next weekly meeting the RFC(Request For Comments) process will be presented, but to have an initial understanding: is RFC process common to all Hyperledger projects? I see that in Fabric documentation, a feature proposal can be made using Jira. https://hyperledger-fabric.readthedocs.io/en/latest/CONTRIBUTING.html#making-feature-enhancement-proposals

Claudius1 (Tue, 12 Feb 2019 16:46:38 GMT):
The RFC, as far as i see it, is for substantial changes. But not sure if RFC is used more in Sawtooth (found a clear description there https://github.com/hyperledger/sawtooth-rfcs#what-the-process-is) compared to other projects.

brockhager (Tue, 12 Feb 2019 16:56:24 GMT):
Has joined the channel.

amundson (Tue, 12 Feb 2019 18:59:48 GMT):
Indy and Ursa also use a similar RFC process

amundson (Tue, 12 Feb 2019 19:02:28 GMT):
I don't see a problem tracking features in JIRA, even if they are substantial enough to justify an RFC

Claudius1 (Tue, 12 Feb 2019 19:54:24 GMT):
Agree. I was just wondering if an RFC is always needed for a substantial feature, or adding an epic or story to Jira, properly documented, can be enough. Not that important, really. Just noticed the possible different approaches and wanted to make sure.

Lakshmipadmaja (Wed, 13 Feb 2019 04:21:13 GMT):
Has joined the channel.

achenette (Thu, 14 Feb 2019 22:04:23 GMT):
Has joined the channel.

mfford (Fri, 15 Feb 2019 14:59:34 GMT):
Reminder that our next Weekly Hyperledger Grid Contributor Meeting occurs this coming Monday (Feb 18th) at 11am CDT. This meeting is a forum for contributors to discuss Grid development. This is open to anyone interested in getting involved with Grid. Here are the details: Title: Weekly Hyperledger Grid Contributor Meeting Day/Time: Every Monday at 11am CDT Duration: 1 hour Facilitator: Mark Ford Call-in Information: Join Zoom Meeting https://zoom.us/j/815586463 One tap mobile +16468769923,,815586463# US (New York) +16699006833,,815586463# US (San Jose) Dial by your location +1 646 876 9923 US (New York) +1 669 900 6833 US (San Jose) +1 408 638 0968 US (San Jose) Meeting ID: 815 586 463 Find your local number: https://zoom.us/u/abPOgiNnD3

mfford (Mon, 18 Feb 2019 16:09:54 GMT):
Our HL Grid Contributor Meeting is today at 11am CDT. Hope to see everyone there that wants to discuss Grid development

mfford (Mon, 18 Feb 2019 16:09:59 GMT):
Title: Weekly Hyperledger Grid Contributor Meeting Day/Time: Every Monday at 11am CDT Duration: 1 hour Facilitator: Mark Ford Call-in Information: Join Zoom Meeting https://zoom.us/j/815586463 One tap mobile +16468769923,,815586463# US (New York) +16699006833,,815586463# US (San Jose) Dial by your location +1 646 876 9923 US (New York) +1 669 900 6833 US (San Jose) +1 408 638 0968 US (San Jose) Meeting ID: 815 586 463 Find your local number: https://zoom.us/u/abPOgiNnD3

onanta (Mon, 18 Feb 2019 17:55:07 GMT):
Has joined the channel.

cliveb (Mon, 18 Feb 2019 22:18:03 GMT):
Has joined the channel.

rranjan3 (Tue, 19 Feb 2019 02:11:16 GMT):
On an anticipatory note, is Grid going to be all DLT only or will it also include other popular technologies like BigData in the solution stack? There might be a requirement when storing things on a scaled up system. So organizations might want to store actual data in some BigData cluster with only urls(actual data location) on the chain. This is one aspect. There could be other such aspects where we might want to support these ubiquitous technologies out of the box.

rranjan3 (Tue, 19 Feb 2019 02:11:16 GMT):
On an anticipatory note, is Grid going to be all DLT only or will it also include other popular technologies like BigData in the solution stack? For example, there might be such a requirement when storing things on a scaled up system. So organizations might want to store actual data in some BigData cluster with only urls(actual data location) on the chain. This is one aspect. There could be other such aspects where we might want to support these ubiquitous technologies out of the box.

amundson (Tue, 19 Feb 2019 14:27:35 GMT):
@rranjan3 our expectation is to use DLT as a building block, but not the only build block. we feel the technology should solve the use case.

amundson (Tue, 19 Feb 2019 14:27:35 GMT):
@rranjan3 our expectation is to use DLT as a building block, but not the only building block. we feel the technology should solve the use case.

pbuendia (Thu, 21 Feb 2019 04:09:24 GMT):
Has joined the channel.

zac (Thu, 21 Feb 2019 16:12:45 GMT):
Has joined the channel.

srinivas (Fri, 22 Feb 2019 03:35:04 GMT):
Has joined the channel.

haggs (Fri, 22 Feb 2019 05:06:01 GMT):
Has joined the channel.

AliciaDominic (Fri, 22 Feb 2019 08:12:33 GMT):
Has joined the channel.

chadgates (Fri, 22 Feb 2019 08:51:17 GMT):
Has joined the channel.

koq 1 (Fri, 22 Feb 2019 10:25:27 GMT):
Has joined the channel.

varubasi77 (Fri, 22 Feb 2019 13:26:05 GMT):
Has joined the channel.

mfford (Fri, 22 Feb 2019 20:07:42 GMT):
Based on feedback from Grid maintainers, we will be changing the frequency of the "Weekly Hyperledger Grid Contributor Meeting" to better accommodate busy schedules. We will cancel the meeting on Monday, 2/25. A new scheduling will be announced shortly. Thanks to everyone that has attended our previous sessions!

pbuendia (Fri, 22 Feb 2019 20:07:48 GMT):
@rranjan3 We are also looking into a solution for Big Data in healthcare applications, such as genome sequence data, medical imaging, meta-genomics, and so on. For sequence data Nebula has an interesting solution that hashed the sequences into tiles (that's the short description) based on this paper doi:10.7287/peerj.preprints.1426v1.

danintel (Sat, 23 Feb 2019 00:05:24 GMT):
Has left the channel.

Pradeep_Pentakota (Mon, 25 Feb 2019 03:00:15 GMT):
Has joined the channel.

cliveb (Tue, 26 Feb 2019 18:27:23 GMT):
[ ](https://chat.hyperledger.org/channel/grid?msg=ukQmy3Ks4qwZvom5H) @mfford Looking forward to the new schedule and learning more about https://github.com/hyperledger/grid. Currently unsure about how grid will shape up into sample code. I'm stuck making contributions without knowing more, but do plan to contribute.

mfford (Tue, 26 Feb 2019 18:32:11 GMT):
@cliveb Great to hear that you're interested in contributing! Stay tuned for more on the HL Grid Contributor Meeting.

satelander (Tue, 26 Feb 2019 18:40:45 GMT):
Has joined the channel.

tuckerg (Thu, 28 Feb 2019 08:54:16 GMT):
Has joined the channel.

davidwboswell (Thu, 28 Feb 2019 16:59:59 GMT):
Has joined the channel.

davidwboswell (Thu, 28 Feb 2019 17:00:15 GMT):
The organizer of the Hyperledger Berlin meetup reached out to me and asked if there is someone near there who could speak at an event about Grid. Are there any Grid contributors based nearby? If not, are there any Grid contributors who would be interested in doing a remote presentation to that group? If we did that, we could record it and sharing it with a wider audience as well.

DirkKrueger (Fri, 01 Mar 2019 11:02:31 GMT):
Has joined the channel.

NavaneethanG 1 (Sun, 03 Mar 2019 06:01:16 GMT):
Has joined the channel.

cliveb (Tue, 05 Mar 2019 19:43:30 GMT):
@mfford Previously I ran the Hyperledger RequirementsWG. We collected multiple specs for supply chain use cases. Would it help Grid If I cleaned up a spec for a common supply use case such as contract manufacturing (i.e even Boeing has run into synchronization problems with new 737 MAX due to supply chain).

jsmitchell (Tue, 05 Mar 2019 20:46:20 GMT):
that would be fantastic @cliveb

mfford (Tue, 05 Mar 2019 20:49:51 GMT):
@cliveb Definately!

mfford (Wed, 06 Mar 2019 14:09:28 GMT):
The next "Hyperledger Grid Contributor Meeting" has been scheduled!

mfford (Wed, 06 Mar 2019 14:09:49 GMT):
Frequency: Monthly Day: Monday 3/18 to start (recurring monthly on 3rd Monday of the month) Time: 10am CDT Duration: 1 Hour Facilitator: Mark Ford Zoom Conference information: Join Zoom Meeting https://zoom.us/j/933448029

iamsteveng (Fri, 08 Mar 2019 02:28:42 GMT):
Has joined the channel.

bbehlendorf (Sun, 10 Mar 2019 04:17:47 GMT):
Has joined the channel.

abhilasharavind1979 (Tue, 12 Mar 2019 10:01:37 GMT):
Has joined the channel.

liutch (Tue, 12 Mar 2019 10:09:16 GMT):
Has joined the channel.

raccoonrat (Tue, 12 Mar 2019 10:14:02 GMT):
Has joined the channel.

NedSnark (Tue, 12 Mar 2019 19:01:14 GMT):
Has joined the channel.

NedSnark (Tue, 12 Mar 2019 19:01:39 GMT):
Whats up guys, new to the grid channel - is this still in beta, or ready to use/start building with?

NedSnark (Tue, 12 Mar 2019 19:46:37 GMT):
@mfford are there recordings of past Zoom webinars/calls we can listen/watch? Signed up for next Mondays but would love to hear the others as well.

mfford (Tue, 12 Mar 2019 19:48:33 GMT):
@NedSnark The previous meetings were not recorded. Looking forward to having you on the call on Monday!

NedSnark (Tue, 12 Mar 2019 19:48:50 GMT):
got it, thx

NedSnark (Tue, 12 Mar 2019 19:51:22 GMT):
So is Grid fully ready to be used, or still under dev?

amundson (Tue, 12 Mar 2019 20:05:47 GMT):
Under heavy development - current initiatives include primitives and product catalog

NedSnark (Tue, 12 Mar 2019 20:14:18 GMT):
Yep sorry just reading thre github

NedSnark (Tue, 12 Mar 2019 20:14:18 GMT):
Yep sorry just reading the github

NedSnark (Tue, 12 Mar 2019 20:15:11 GMT):
quick question, looks like sawtooth also good for supp-chains, so what are the key/basic differences that grid does/solves that Sawtooth doesn't have/do?

jsmitchell (Tue, 12 Mar 2019 20:18:04 GMT):
grid is the data models, business logic, etc. in consumable 'framework' form. sawtooth is a blockchain platform.

jsmitchell (Tue, 12 Mar 2019 20:18:50 GMT):
the idea is you'd build an app quickly using the grid frameworks and run the app on a platform that supports grid's execution semantics (like sawtooth).

NedSnark (Tue, 12 Mar 2019 20:46:26 GMT):
got it, makes perfect sense, thx

NedSnark (Tue, 12 Mar 2019 20:46:47 GMT):
any idea roughly speaking when Grid may be ready to actually start building with or using?

mfford (Wed, 13 Mar 2019 13:48:22 GMT):
Reminder that our next Hyperledger Grid Contributor Meeting is Monday, March 18th at 10am CDT. The meeting information can be found on the Hyperledger Community Meetings Calendar located here: https://wiki.hyperledger.org/display/HYP/Calendar+of+Public+Meetings We are in the process of creating the agenda for this meeting. If you have an appropriate topic you would like to discuss and facilitate, please add it to the agenda, located in the wiki here: https://wiki.hyperledger.org/pages/viewpage.action?pageId=6427269

iamsteveng (Thu, 14 Mar 2019 02:53:41 GMT):
Hi guys, I met several Indy contributors in the HK Hyperledger Bootcamp. Heard that Grid project may have plan on integrating Sawtooth and Indy together. It is really interesting to me. May I ask what role Indy will, or in general how would identity management looks like in Grid?

mfford (Fri, 15 Mar 2019 19:13:45 GMT):
Reminder that our next Hyperledger Grid Contributor Meeting is Monday, March 18th at 10am CDT. The meeting information can be found on the Hyperledger Community Meetings Calendar located here: https://wiki.hyperledger.org/display/HYP/Calendar+of+Public+Meetings You can still add agenda topics to the meeting. If you have an appropriate topic you would like to discuss and facilitate, please add it to the agenda, located in the wiki here: https://wiki.hyperledger.org/pages/viewpage.action?pageId=6427269 Looking forward to seeing everyone at our next meeting! -Mark

desktophero (Fri, 15 Mar 2019 19:27:20 GMT):
Has joined the channel.

walter211 (Sat, 16 Mar 2019 03:47:25 GMT):
Has joined the channel.

EvansChang (Mon, 18 Mar 2019 06:14:23 GMT):
Has joined the channel.

amundson (Mon, 18 Mar 2019 14:50:54 GMT):
Grid Primitives RFC draft is up - https://github.com/hyperledger/grid-rfcs/pull/4

anaswar (Tue, 19 Mar 2019 13:47:10 GMT):
hi all.. are the repos 'https://github.com/hyperledger/grid' and 'https://github.com/hyperledger/grid-contrib' ready for deploying the sample track and trace solution? or still under dev?

amundson (Tue, 19 Mar 2019 14:44:03 GMT):
@anaswar you should be able to use docker compose to start it up (the most recent PR for this work is https://github.com/hyperledger/grid-contrib/pull/4) you have to have 'grid' and 'grid-contrib' checked out next to each other (in the same directory. (I haven't personally tested this yet, and Ryan is on vacation.)

anaswar (Wed, 20 Mar 2019 04:34:31 GMT):
thank you @amundson, will definitely try it out !

cliveb (Thu, 21 Mar 2019 20:02:13 GMT):
@amundson @anaswar with 'grid' and 'grid-contrib' checked out next to each other. I tired using ... is this the right approach to try out? https://sawtooth.hyperledger.org/docs/core/releases/latest/app_developers_guide/docker.html

amundson (Thu, 21 Mar 2019 20:28:57 GMT):
@cliveb not exactly, though its related. basically you do "docker-compose up" in grid/ and in another window, "docker-compose up" in grid-contrib/track_and_trace/

amundson (Thu, 21 Mar 2019 20:29:10 GMT):
however, I think it has issues from some other activity today

amundson (Thu, 21 Mar 2019 20:29:14 GMT):
```grid-track-and-trace-tp | error: failed to load source for a dependency on `grid-sdk` grid-track-and-trace-tp | grid-track-and-trace-tp | Caused by: grid-track-and-trace-tp | Unable to update /grid/sdk grid-track-and-trace-tp | grid-track-and-trace-tp | Caused by: grid-track-and-trace-tp | failed to read `/grid/sdk/Cargo.toml` grid-track-and-trace-tp | grid-track-and-trace-tp | Caused by: grid-track-and-trace-tp | No such file or directory (os error 2)```

amundson (Thu, 21 Mar 2019 20:30:11 GMT):
@agunde ^

amundson (Thu, 21 Mar 2019 20:31:12 GMT):
I suspect we need to copy the sdk directory in that Dockerfile

agunde (Thu, 21 Mar 2019 20:35:23 GMT):
@amundson is that from docker-compose up in grid or grid contrib?

amundson (Thu, 21 Mar 2019 20:35:35 GMT):
grid

amundson (Thu, 21 Mar 2019 20:35:59 GMT):
a similar error in grid-contrib, but this is the contracts/track_and_trace/Dockerfile I think

agunde (Thu, 21 Mar 2019 20:36:44 GMT):
Let me rebuild my docker containers real quick because it worked for me. That dockerfile should copy the sdk over already

amundson (Thu, 21 Mar 2019 20:39:03 GMT):
yeah... it's probably my environment, I'll add some options to the docker-compose up and see if it resolves.

agunde (Thu, 21 Mar 2019 20:40:07 GMT):
Make sure you don't have an old Cargo.lock file around from before. Protos don't always get build correctly otherwise if they have been updated.

agunde (Thu, 21 Mar 2019 20:42:22 GMT):
@amundson contrib still fails. I think thats a location issue with where the dockerfile is trying to find the sdk.

agunde (Thu, 21 Mar 2019 20:42:22 GMT):
@amundson contrib fails. I think thats a location issue with where the Dockerfile is trying to find the sdk.

amundson (Thu, 21 Mar 2019 20:46:03 GMT):
'docker-compose up --force-recreate --build' seems to have works ok (in grid repo)

amundson (Thu, 21 Mar 2019 20:48:53 GMT):
oh, the grid-contrib one is standalone currently

agunde (Thu, 21 Mar 2019 20:50:47 GMT):
I think I got grid-contrib working. If it finishes building I make a PR.

agunde (Thu, 21 Mar 2019 20:50:47 GMT):
I think I got grid-contrib working. If it finishes building I'll make a PR.

amundson (Thu, 21 Mar 2019 20:52:19 GMT):
ok

Nish (Fri, 22 Mar 2019 06:14:49 GMT):
Has joined the channel.

Nish (Fri, 22 Mar 2019 07:55:36 GMT):

Clipboard - March 22, 2019 1:25 PM

agunde (Fri, 22 Mar 2019 13:39:57 GMT):
@Nish I am going to put up a PR to fix this shortly. We have recently added some changes that breaks grid-contrib docker file.

agunde (Fri, 22 Mar 2019 13:39:57 GMT):
@Nish I am going to put up a PR to fix this shortly. We have recently added some changes to grid that breaks grid-contrib docker file.

agunde (Fri, 22 Mar 2019 14:28:55 GMT):
@amundson Fix for grid-contrib/track_and_trace docker-compose file https://github.com/hyperledger/grid-contrib/pull/7

agunde (Fri, 22 Mar 2019 16:28:42 GMT):
That fix has been merged

cliveb (Fri, 22 Mar 2019 18:01:48 GMT):

Screen Shot 2019-03-22 at 10.54.59 AM.png

cliveb (Fri, 22 Mar 2019 18:02:25 GMT):
Any ideas? "ERROR: for validator Cannot start service validator: driver failed programming external connectivity on endpoint tnt-validator...." This error after pulling latest PR's for grid and grid-contrib into side-by side folder and "docker-compose up" in grid/ and in another window, "docker-compose up" in grid-contrib/track_and_trace/ (screen shot above)

agunde (Fri, 22 Mar 2019 18:04:33 GMT):
@cliveb you just need to start up grid-contrib docker-compose. It will pull in track and trace if the folder are next to each other.

cliveb (Fri, 22 Mar 2019 18:10:38 GMT):
@agunde Thanks, I did do that. I will try again in case its my local machine issue.

cliveb (Fri, 22 Mar 2019 18:10:38 GMT):
Pulled latest grid and grid-contrib/track-and-trace. Grid starts. Grid-contrib errors (on my machine)

rjones (Fri, 22 Mar 2019 22:59:53 GMT):
nage

rjones (Fri, 22 Mar 2019 23:00:20 GMT):
amundson

rjones (Fri, 22 Mar 2019 23:00:26 GMT):
Silona

rjones (Fri, 22 Mar 2019 23:00:34 GMT):
Has left the channel.

nitishbhardwaj19 (Mon, 25 Mar 2019 05:19:40 GMT):
Has joined the channel.

troyronda (Mon, 25 Mar 2019 20:26:17 GMT):
Has joined the channel.

amolk (Tue, 26 Mar 2019 05:19:42 GMT):
@amundson @pschwarz please review https://github.com/hyperledger/grid/pull/6

Psypher246 (Tue, 26 Mar 2019 09:36:30 GMT):
Has joined the channel.

anaswar (Tue, 26 Mar 2019 13:39:02 GMT):
I am getting a bit confused looking at the `grid` and `grid-contrib` repos.. 1. is the WebAssembly (WASM) Smart Contract interpreter implemented using the Rust programs in `grid/contracts/track_and_trace/src/` ? 2. actual smart contracts (chaincode) is wirtten in `grid-contrib` repo Please confirm if my understanding stated above are right

agunde (Tue, 26 Mar 2019 13:44:51 GMT):
The WASM Smart Contract interpreter is located here https://github.com/hyperledger/sawtooth-sabre. grid/contracts will house wasm smart contracts that can be used with Sabre. Track and Trace needs some small updates to be able to be run with Sabre but can currently run as a Sawtooth Transaction Processor. The changes should be submitted soon. There are a two rfc currently up for grid that explains 2 new smart contracts that will be written for grid https://github.com/hyperledger/grid-rfcs/pulls.

agunde (Tue, 26 Mar 2019 13:46:22 GMT):
Grid-contrib is a place for community submitted software that is not yet a part of grid. For example the Track and Trace example apps are house in grid.

agunde (Tue, 26 Mar 2019 13:46:22 GMT):
Grid-contrib is a place for community submitted software that is not yet a part of grid. For example the Track and Trace example apps are housed in grid-contrib.

anaswar (Tue, 26 Mar 2019 13:47:46 GMT):
ok. i did not know that chaincode could be written in Rust, hence the confusion.

anaswar (Tue, 26 Mar 2019 13:49:45 GMT):
and this "This repository (_grid-repo_) is intended for community-contributed software, including example libraries, data models, and reference implementations for *smart contracts* (also called "transaction families") "

anaswar (Tue, 26 Mar 2019 13:49:45 GMT):
and this "This repository _(grid-repo)_ is intended for community-contributed software, including example libraries, data models, and reference implementations for *smart contracts* (also called "transaction families") "

agunde (Tue, 26 Mar 2019 13:53:01 GMT):
Chaincode is for Fabric. Grid is based on Sabre WASM smart contracts which currently are supported by Sawtooth. We welcome contributions/compatibility with other top level Hyperledger projects, including Fabric.

anaswar (Tue, 26 Mar 2019 13:57:20 GMT):
thank you @agunde

pschwarz (Tue, 26 Mar 2019 14:39:05 GMT):
@amolk Still missing some stuff, I left some comments.

amolk (Tue, 26 Mar 2019 15:25:27 GMT):
@pschwarz updated again, Pls check.

cliveb (Tue, 26 Mar 2019 15:32:02 GMT):

Screen Shot 2019-03-26 at 8.28.37 AM.png

cliveb (Tue, 26 Mar 2019 15:32:18 GMT):

Screen Shot 2019-03-26 at 8.28.51 AM.png

cliveb (Tue, 26 Mar 2019 15:34:26 GMT):
I pulled latest grid and grid-contrib. Grid starts. Grid-contrib/track-and-trace/ does not start (screen shots from my machine).

cliveb (Wed, 27 Mar 2019 16:38:01 GMT):
Hangs after pulling latest grid do "docker-compose up" in grid, with 'grid' and 'grid-contrib' checked out next to each other... "sawtooth-devmode-engine-rust-default | WARN | devmode_engine_rust: | Block not ready to summarize"

amundson (Wed, 27 Mar 2019 16:52:45 GMT):
@cliveb I accidentally introduced that error from you first screenshot in a recent PR and should have it fixed tomorrow

amundson (Wed, 27 Mar 2019 16:54:57 GMT):
I am not quite sure why this didn’t show up when running cargo test.

daijianw (Fri, 29 Mar 2019 08:27:26 GMT):
Has joined the channel.

cliveb (Fri, 29 Mar 2019 18:09:23 GMT):

Screen Shot 2019-03-29 at 11.05.48 AM.png

cliveb (Fri, 29 Mar 2019 18:09:26 GMT):
@amundson I pull latest. grid starts ok. grid-compose/track_and_trace encountered errors

cliveb (Fri, 29 Mar 2019 18:09:26 GMT):
@amundson I pulled latest CL. grid starts ok. grid-compose/track_and_trace encountered errors

cliveb (Fri, 29 Mar 2019 18:09:26 GMT):
@amundson I pulled latest CL. grid starts ok. grid-compose/track_and_trace encountered errors (screen shot above)

rbuysse (Mon, 01 Apr 2019 14:41:19 GMT):
@cliveb do you have other containers already using that port?

kumble (Tue, 02 Apr 2019 01:05:16 GMT):
Has joined the channel.

cliveb (Tue, 02 Apr 2019 01:50:15 GMT):
@rbuysse NAFIK. To make sure, I did a clean boot on Macbook after pulling down latest CL. Grid starts fine. docker-compose up in grid-contributor/track-and-trace errors while bringing up the project. Screen shots follow.

cliveb (Tue, 02 Apr 2019 01:50:15 GMT):
@rbuysse NAFIK. To make sure, I did a clean boot on Macbook after pulling down latest CL. Grid starts fine. 'docker-compose up' in $ grid-contributor/track-and-trace errors while bringing up the project. Screen shots follow.

cliveb (Tue, 02 Apr 2019 01:50:15 GMT):
@rbuysse NAFIK. To make sure, I did a clean boot on Macbook after pulling down latest CL. Grid starts fine. 'docker-compose up' in $ grid-contributor/track_and_trace errors while bringing up the project. Screen shots follow.

cliveb (Tue, 02 Apr 2019 01:52:30 GMT):

Screen Shot 2019-04-01 at 6.51.29 PM.png

cliveb (Tue, 02 Apr 2019 01:53:17 GMT):

Screen Shot 2019-04-01 at 6.51.10 PM.png

cliveb (Tue, 02 Apr 2019 17:23:50 GMT):

Screen Shot 2019-04-02 at 10.21.08 AM.png

krishna_r (Tue, 02 Apr 2019 18:57:01 GMT):
Has joined the channel.

pdxjohnnyintel (Tue, 02 Apr 2019 19:32:10 GMT):
Has joined the channel.

pdxjohnnyintel (Tue, 02 Apr 2019 19:48:29 GMT):
Hi All, I just cloned and ran grid-contrib (899036d26f330223bdf17ced275833445ea33b53) and grid (244ff4e6f6edb4debb49ecca6bc69c8ec09b7c0d) and got the error "Record Type does not exist asset" when I try to add a new record to the asset tracker app localhost:8021/#!/create Also, tnt-shell is saying "Server unavailable, retrying in 5 seconds..." forever.

pdxjohnnyintel (Tue, 02 Apr 2019 19:50:05 GMT):

logs.txt

pdxjohnnyintel (Tue, 02 Apr 2019 19:50:26 GMT):
Also, Why is the issue tracker on github not in use? Is there another place to track issues?

amundson (Tue, 02 Apr 2019 19:57:49 GMT):
@pdxjohnnyintel we have a JIRA project setup - https://jira.hyperledger.org/projects/GRID/issues

amundson (Tue, 02 Apr 2019 21:18:08 GMT):
@cliveb @rbuysse I think we need to move to a slightly different model between these repos. maybe one where we give docker-compose multiple -f options instead of duplicating the content over to contrib.

cliveb (Wed, 03 Apr 2019 15:26:51 GMT):
[ ](https://chat.hyperledger.org/channel/grid?msg=RuY97TNvdHLanfYS5) @amundson Yes please, after pulling latest CL, I have still have port clash over on contrib. com. docke 515 seebe 18u IPv4 0x3aec15b0464bcc97 0t0 TCP *:4020 (LISTEN) com.docke 515 seebe 20u IPv6 0x3aec15b0499b81d7 0t0 TCP [::1]:4020 (LISTEN)

cliveb (Wed, 03 Apr 2019 15:26:51 GMT):
[ ](https://chat.hyperledger.org/channel/grid?msg=RuY97TNvdHLanfYS5) @amundson Yes please, after pulling latest CL, I have still have port clash over on contrib. com. docke 515 cliveb 18u IPv4 0x3aec15b0464bcc97 0t0 TCP *:4020 (LISTEN) com.docke 515 cliveb 20u IPv6 0x3aec15b0499b81d7 0t0 TCP [::1]:4020 (LISTEN)

cliveb (Fri, 05 Apr 2019 18:18:25 GMT):

Screen Shot 2019-04-05 at 11.15.26 AM.png

rbuysse (Fri, 05 Apr 2019 21:30:37 GMT):
@cliveb that looks like you're out of space in docker as well

rbuysse (Fri, 05 Apr 2019 21:30:53 GMT):
I'm working on getting the track and trace stuff fixed up. I'll have a PR soon.

rbuysse (Fri, 05 Apr 2019 21:43:08 GMT):
@cliveb I've got a draft PR here: https://github.com/hyperledger/grid-contrib/pull/8

DuanLu-Lin (Mon, 08 Apr 2019 07:35:45 GMT):
Has joined the channel.

Dan (Mon, 08 Apr 2019 14:44:31 GMT):
Has joined the channel.

cliveb (Mon, 08 Apr 2019 18:25:51 GMT):
I found this post useful for cleaning up unused space by docker https://alexpnt.github.io/2017/08/15/docker-cleanup/

cliveb (Mon, 08 Apr 2019 18:25:51 GMT):
I found this post useful for cleaning up space by docker https://alexpnt.github.io/2017/08/15/docker-cleanup/

JulianGordonHK (Tue, 09 Apr 2019 06:48:58 GMT):
Has joined the channel.

ruairih (Wed, 10 Apr 2019 18:00:25 GMT):
Has joined the channel.

mfford (Thu, 11 Apr 2019 12:48:16 GMT):
Reminder that our next Hyperledger Grid Contributor Meeting is Monday, April 15th at 10am CDT. The meeting information can be found on the Hyperledger Community Meetings Calendar located here: https://wiki.hyperledger.org/display/HYP/Calendar+of+Public+Meetings We are in the process of creating the agenda for this meeting. If you have an appropriate topic you would like to discuss and facilitate, please add it to the agenda, located in the wiki here: https://wiki.hyperledger.org/pages/viewpage.action?pageId=6429346

cliveb (Thu, 11 Apr 2019 18:00:30 GMT):
[ ](https://chat.hyperledger.org/channel/grid?msg=JXGGMQ4hA4CLgw5pj) @mfford Done. Like to clarify my understanding on Monday.

viossat (Thu, 11 Apr 2019 19:23:00 GMT):
Has joined the channel.

mfford (Thu, 11 Apr 2019 20:17:38 GMT):
@cliveb Thanks for the agenda comments. See you on the call on Monday

JulianMoeller (Fri, 12 Apr 2019 11:58:41 GMT):
Has joined the channel.

rjones (Sat, 13 Apr 2019 00:11:06 GMT):
Has joined the channel.

rjones (Sat, 13 Apr 2019 00:11:13 GMT):
Could I ask Grid maintainers to please join https://lists.hyperledger.org/g/maintainers ? I'd appreciate it.

mfford (Mon, 15 Apr 2019 13:17:48 GMT):
Reminder that the Hyperledger Grid Contributor Meeting is today at 10am CDT. The meeting information can be found on the Hyperledger Community Meetings Calendar located here: https://wiki.hyperledger.org/display/HYP/Calendar+of+Public+Meetings

amundson (Mon, 15 Apr 2019 14:16:17 GMT):
We are working on a HL project proposal for a new transation execution library (tentatively called Transact). Sawtooth and Grid will use this library. Anyone interested, please review - https://docs.google.com/document/d/13d0cMReGOhK13BbdgMOFZy_prUzqWBXWc4nlI7mehpY/edit

Dan (Mon, 15 Apr 2019 14:21:01 GMT):
Is there an agenda maintained for the contrib meeting?

agunde (Mon, 15 Apr 2019 14:22:50 GMT):
@Dan https://wiki.hyperledger.org/pages/viewpage.action?pageId=6429346

Dan (Mon, 15 Apr 2019 14:25:12 GMT):
gracias

amundson (Mon, 15 Apr 2019 16:01:46 GMT):
thanks for the great discussion guys, and especially thank @cliveb for the discussion topics

jadhavajay (Mon, 15 Apr 2019 18:37:41 GMT):
Has joined the channel.

cliveb (Tue, 16 Apr 2019 19:03:54 GMT):
[ ](https://chat.hyperledger.org/channel/grid?msg=mmQRBHNxYKSSDd9Zr) @amundson Thanks for all contextual answers and team grid team member and contributor updates.

cliveb (Tue, 16 Apr 2019 19:05:15 GMT):
@amundson Is anyone working on refactoring into Rust using the Rocket web framework? https://jira.hyperledger.org/browse/GRID-4

amundson (Tue, 16 Apr 2019 19:21:45 GMT):
@cliveb I don't think anyone is actively taken that on yet.

amundson (Tue, 16 Apr 2019 19:22:39 GMT):
I updated the JIRA issue - really, we need these to go into the grid daemon (gridd in the repo) and we are using actix instead of rocket (because rocket requires nightly rust, and we want grid daemon to use stable rust).

austbot (Wed, 17 Apr 2019 02:25:15 GMT):
Has joined the channel.

ajayjadhav (Wed, 24 Apr 2019 09:15:25 GMT):
Has joined the channel.

lepar (Wed, 24 Apr 2019 14:23:06 GMT):
Has joined the channel.

Dan (Wed, 24 Apr 2019 15:45:57 GMT):
There's some minor bugs in the docker-compose for sawtooth-supply-chain. is this code more actively maintained in grid-contrib? Happy to get it fixed either way, but more curious where the longer term home is for that code.

amundson (Wed, 24 Apr 2019 15:50:25 GMT):
@Dan my thought is this. we should move sawtooth-supply-chain and other things to sawtooth-contrib. the track and trace stuff in Grid is currently derived from it, but will quickly deviate and not provide the same type of example on how to do a sawtooth app. (it will start to, for example, depend heavily on the grid sdk). so there is probably room for both.

amundson (Wed, 24 Apr 2019 15:52:10 GMT):
FWIW, it's already been integrated into grid. so it's really a sawtooth discussion on whether the maintaining it as an example is worthwhile.

cliveb (Wed, 24 Apr 2019 16:45:09 GMT):
If there's a decision made to move sawtooth-supply-chain code to sawtooth-contrib. That sounds like a contribution a remote dev could make and test w/o too much guidance. I will start by make a design doc on targets that need to move. Get that approved before moving the code. If so feel free to please assign to @cliveb.

cliveb (Wed, 24 Apr 2019 16:45:09 GMT):
If there's a decision made to move sawtooth-supply-chain code to sawtooth-contrib. That sounds like a contribution a remote dev could make and test w/o too much guidance. I could start by making a design doc on targets that need to move. Get that approved before moving the code. If so feel free to please assign to @cliveb.

cliveb (Wed, 24 Apr 2019 18:18:19 GMT):

Screen Shot 2019-04-09 at 11.51.46 AM.png

cliveb (Wed, 24 Apr 2019 18:19:45 GMT):

Screen Shot 2019-04-24 at 11.14.43 AM.png

amundson (Wed, 24 Apr 2019 18:48:08 GMT):
@cliveb we probably need to do a sawtooth rfc to make sure we have agreement before doing the contrib repo in sawtooth. it's a relatively large change for sawtooth if we go down that path.

amundson (Wed, 24 Apr 2019 18:49:59 GMT):
@cliveb I've been running grid a lot and I don't think I've seen that. can you do "docker-compose down" and then "docker-compose up --build" to make sure you have recently built images.

phoniks (Wed, 24 Apr 2019 19:54:53 GMT):
Has joined the channel.

rossth (Wed, 24 Apr 2019 20:31:35 GMT):
Has joined the channel.

cliveb (Wed, 24 Apr 2019 23:50:12 GMT):

Screen Shot 2019-04-05 at 11.15.26 AM.png

mc (Thu, 25 Apr 2019 12:04:13 GMT):
Has joined the channel.

cliveb (Thu, 25 Apr 2019 21:08:47 GMT):
@amundson any ideas on why grid-contrib path is incorrect in screen shot above?

cliveb (Thu, 25 Apr 2019 21:08:47 GMT):
@amundson Still getting 3 warnings and error on build path. My folder tree is github/hyperledger/grid and github/hyperledger/grid-contrib/track_and_trace. Terminal tabs for docker-compose up are side-by-side?

amundson (Thu, 25 Apr 2019 21:36:17 GMT):
@cliveb can you post the command line you are using?

amundson (Thu, 25 Apr 2019 21:36:27 GMT):
and what directory you are running it from?

amundson (Thu, 25 Apr 2019 21:36:55 GMT):
I think the "no space left on device" is probably relevant

amundson (Thu, 25 Apr 2019 21:37:37 GMT):
nevermind, I see the prompt is there

amundson (Thu, 25 Apr 2019 21:37:55 GMT):
I think it's just a disk space issue

cliveb (Fri, 26 Apr 2019 05:35:41 GMT):

Screen Shot 2019-04-25 at 10.33.19 PM.png

cliveb (Fri, 26 Apr 2019 05:43:35 GMT):

Screen Shot 2019-04-25 at 10.41.40 PM.png

cliveb (Fri, 26 Apr 2019 05:49:33 GMT):
@amundson Still getting 3 warnings and build path error with /hyperledger/grid-contrib/track_and_trace $ docker-compose up. Grid is side-by-side in folder tree /hyperledger/grid and terminal prompts. Any other ideas?

eloafran (Fri, 26 Apr 2019 15:17:01 GMT):
Has joined the channel.

amundson (Fri, 26 Apr 2019 15:38:09 GMT):
@cliveb you need to run docker-compose from the grid directory. make sure you have both the grid and grid-contrib repos next to each other, then: cd grid/; docker-compose up -f docker-compose.yaml -f ../grid-contrib/track_and_trace/docker-compose.yaml

amundson (Fri, 26 Apr 2019 15:38:28 GMT):
think of this as "starting up grid and adding the track and trace components to it"

amundson (Fri, 26 Apr 2019 15:38:57 GMT):
@rbuysse ^ is this documented somewhere?

amundson (Fri, 26 Apr 2019 15:39:36 GMT):
FWIW - I didn't just test this, it is from-memory.

rbuysse (Fri, 26 Apr 2019 15:39:58 GMT):
it was in the PR. I'm not sure where to document it officially

MelanieNuce (Fri, 26 Apr 2019 15:40:19 GMT):
Has joined the channel.

agunde (Fri, 26 Apr 2019 15:40:30 GMT):
@amundson Ryan Banks has a story to add the Readme to the grid-contrib/track_and_trace repor to explain how to do this.

agunde (Fri, 26 Apr 2019 15:40:30 GMT):
@amundson Ryan Banks has a story to add the Readme to the grid-contrib/track_and_trace repo to explain how to do this.

agunde (Fri, 26 Apr 2019 15:40:30 GMT):
@amundson Ryan Banks has a story to add the Readme to the grid-contrib/track_and_trace repo to explain how to do this. @RobinBanks

MelanieNuce (Fri, 26 Apr 2019 15:41:04 GMT):
Check out this link for an example of an EPCIS implementation for product traceability: https://github.com/JaewookByun/epcis

amundson (Fri, 26 Apr 2019 15:44:46 GMT):
I think it would be useful for us to maintain a curated list of additional reading material.

MelanieNuce (Fri, 26 Apr 2019 15:44:55 GMT):
For more detail about the Oliot project (by Jaewook Byun), here is another link: http://gs1oliot.github.io/oliot/

amundson (Fri, 26 Apr 2019 15:44:55 GMT):
(for everything related to Grid)

MelanieNuce (Fri, 26 Apr 2019 15:45:34 GMT):
If you let me know how to best contribute, I would be happy to send more info

MelanieNuce (Fri, 26 Apr 2019 15:48:02 GMT):
Sorry - first-timer. Here are the FOUR helpful links about open-source EPCIS coming out of KAIST in South Korea: Oliot Project: http://gs1oliot.github.io/oliot/ Github for JaewookByun / EPCIS https://github.com/JaewookByun/epcis Oliot EPCIS v1.2.10 http://14.63.168.75:8080/epcis/ Tutorial: http://14.63.168.75:8080/epcis/tutorialPage.jsp

cecchi (Fri, 26 Apr 2019 15:48:09 GMT):
a ghe markdown doc full of good links

amundson (Fri, 26 Apr 2019 15:48:10 GMT):
will this work as a way to collect it (and then we can move it somewhere more official later)? https://docs.google.com/document/d/1iAbGkgQHJomk3q8ZJLlKDWU8MOJuJPjb3aG2wBLObB8/edit?usp=sharing

cecchi (Fri, 26 Apr 2019 15:48:24 GMT):
let's not start it in google docs

amundson (Fri, 26 Apr 2019 15:48:31 GMT):
no?

jsmitchell (Fri, 26 Apr 2019 15:50:31 GMT):
@cecchi you have to remember, @amundson comes from a world where only code is stored in source repositories

mattp (Fri, 26 Apr 2019 15:51:31 GMT):
Has joined the channel.

rjones (Fri, 26 Apr 2019 15:53:33 GMT):
please use the wiki @amundson

rjones (Fri, 26 Apr 2019 15:54:02 GMT):
google docs effectively excludes our Chinese members

rjones (Fri, 26 Apr 2019 15:54:02 GMT):
google docs effectively excludes our Chinese contributors

cecchi (Fri, 26 Apr 2019 15:54:08 GMT):
and tons of corporate members

cecchi (Fri, 26 Apr 2019 15:54:19 GMT):
should have said contributors, not members

amundson (Fri, 26 Apr 2019 15:55:08 GMT):
ok, removed that doc.

amundson (Fri, 26 Apr 2019 15:57:04 GMT):
if we want to use the wiki, everyone needs to create LF accounts and sign-in

jsmitchell (Fri, 26 Apr 2019 15:57:53 GMT):
@mattp https://lists.hyperledger.org/g/grid

amundson (Fri, 26 Apr 2019 15:57:59 GMT):
I personally would prefer we not store things long-term in the wiki but if we go back and clean it up and integrate it into a git repo (docs or contrib) I guess that would be fine

amundson (Fri, 26 Apr 2019 15:58:20 GMT):
I think @pschwarz has had issues accessing the wiki

cecchi (Fri, 26 Apr 2019 16:01:16 GMT):
how about helpful links go in RFC's

cecchi (Fri, 26 Apr 2019 16:01:55 GMT):
@amundson doesn't get a vote because he only thinks code should be there even tho he reviews RFCs which are not code

Silona (Fri, 26 Apr 2019 16:03:07 GMT):
Get an LFID here's @rjones video https://www.youtube.com/watch?v=EEc4JRyaAoA you will also need it for JIRA

amundson (Fri, 26 Apr 2019 16:03:23 GMT):
@jsmitchell @cecchi I feel like you are misrepresenting me. I'd argue the RFCs are code.

cecchi (Fri, 26 Apr 2019 16:04:51 GMT):
so the EPCIS stuff could go in an EPCIS RFC as "references" or something

amundson (Fri, 26 Apr 2019 16:05:21 GMT):
sure, chicken-and-egg. need to collect links so we can have the conversations about the RFC :)

jsmitchell (Fri, 26 Apr 2019 16:05:35 GMT):
@amundson how do you feel about powerpoint docs?

amundson (Fri, 26 Apr 2019 16:06:05 GMT):
no comment

cecchi (Fri, 26 Apr 2019 16:10:44 GMT):
can we get amundson some more badges at some point?

cecchi (Fri, 26 Apr 2019 16:11:13 GMT):
not intimidating enough

Gena (Fri, 26 Apr 2019 16:16:45 GMT):
Has joined the channel.

amundson (Fri, 26 Apr 2019 16:22:23 GMT):
a "Maintainer" one maybe?

jamesmlynch (Fri, 26 Apr 2019 16:23:52 GMT):
Has joined the channel.

rjones (Fri, 26 Apr 2019 16:26:17 GMT):
amundson

amundson (Fri, 26 Apr 2019 16:26:35 GMT):
ouch

rjones (Fri, 26 Apr 2019 16:26:35 GMT):
if you're an owner don't need moderator powers

rjones (Fri, 26 Apr 2019 16:31:29 GMT):
there, @cecchi, a badge for you :)

amundson (Fri, 26 Apr 2019 16:38:49 GMT):
@rjones is crazy with power

MelanieNuce (Fri, 26 Apr 2019 16:45:15 GMT):
Quick reference overview for all GS1 keys (identifiers): https://www.gs1.org/sites/default/files/docs/idkeys/gs1_id_keys_reference_card.pdf.pdf

amundson (Fri, 26 Apr 2019 16:47:08 GMT):
@MelanieNuce is there a doc that lists product attributes?

Dan (Fri, 26 Apr 2019 16:49:24 GMT):
@rjones got any best practices how to post PDFs? Like can we upload them onto the wiki?

Silona (Fri, 26 Apr 2019 16:58:59 GMT):
yes you can. there are many options on how to display the PDFs

Silona (Fri, 26 Apr 2019 16:59:49 GMT):
Remember in Confluence - there's a macro for that. And also we get most addons for free since OSS

Silona (Fri, 26 Apr 2019 17:00:25 GMT):
and if you click on <> in the upper right hand corner - there's a version of HTML to play with

MelanieNuce (Fri, 26 Apr 2019 17:06:19 GMT):
@amundson I have that on my list to ask - There is an online tool, but the UX is terrible. Will get back on that item

amundson (Fri, 26 Apr 2019 17:07:10 GMT):
if you want to try uploading files to the wiki, here is a page - https://wiki.hyperledger.org/display/GRID/Uploaded+Files?flashId=1521546842

Dan (Fri, 26 Apr 2019 17:11:51 GMT):
event terms section 7.1.3 of https://www.gs1.org/sites/default/files/docs/epc/CBV-Standard-1-2-2-r-2017-10-12.pdf

cliveb (Fri, 26 Apr 2019 17:18:12 GMT):
[ ](https://chat.hyperledger.org/channel/grid?msg=irba5ciELSu4NfZcy) @agunde For the grid Readme. From @amundson's helper. I tuned and tested and this bash command works correctly. Is there a PR that I can remark? cd grid/; docker-compose up --force-recreate ;cd ../grid-contrib/track_and_trace/ docker-compose up --force-recreate

cliveb (Fri, 26 Apr 2019 17:18:12 GMT):
[ ](https://chat.hyperledger.org/channel/grid?msg=irba5ciELSu4NfZcy) @agunde For the grid Readme. From @amundson's helper. I tuned and tested this bash command works correctly. Is there a PR that I can remark? cd grid/; docker-compose up --force-recreate ;cd ../grid-contrib/track_and_trace/ docker-compose up --force-recreate

cliveb (Fri, 26 Apr 2019 17:26:26 GMT):

Screen Shot 2019-04-26 at 10.11.01 AM.png

agunde (Fri, 26 Apr 2019 17:42:54 GMT):
@cliveb not yet, I'll let you know when it gets put up.

Gena (Fri, 26 Apr 2019 18:44:45 GMT):

2018_11_19 EPCIS.pdf

rjones (Mon, 29 Apr 2019 07:57:13 GMT):
@Dan :beers:

adeebahmed (Mon, 29 Apr 2019 14:04:28 GMT):

grid.jpg

adeebahmed (Mon, 29 Apr 2019 14:37:13 GMT):
Hi all, any word on that follow-up design discussion we seemingly need to have per our friday meeting? For product at least. I'm hesitant to move forward. I am free this afternoon/tomorrow. Matt and I will be out of town wed-fri.

pschwarz (Mon, 29 Apr 2019 16:12:19 GMT):
With respect to Date primitives,there are a couple of ways we could store these: ISO 8601 strings or a int64 of millis since the unix epoch (akin to Java Date values), plus a timezone adjustment. E.g.: ``` message Date { int64 milliseconds = 1; int16 timezone_offset = 2; // offset in minutes } ``` The default timezone offset would be `0`, and therefore be `Z`

amundson (Mon, 29 Apr 2019 18:33:30 GMT):
Another option would be ISO 8601

pschwarz (Mon, 29 Apr 2019 22:13:13 GMT):
Yeah, that was my first option

pschwarz (Mon, 29 Apr 2019 22:13:34 GMT):
Seems kind of storage intensive

Silona (Tue, 30 Apr 2019 19:16:44 GMT):
[ ](https://chat.hyperledger.org/channel/grid?msg=yceQnfC9hhAYtFb5v) @MelanieNuce @MelanieNuce May I suggest the Gliffy plugin and you can have editable diagrams.

cliveb (Tue, 30 Apr 2019 21:02:03 GMT):
[ ](https://chat.hyperledger.org/channel/grid?msg=jg5skuS5LMJRBRLg6) @pschwarz Discussed at LinxFest was inconsistencies in how Linux, MacOS and Windows operating systems handle date created, date modified. Seems eay to step on a landmine. https://www.linuxfestnorthwest.org/conferences/2019/program/proposals/328

cliveb (Tue, 30 Apr 2019 21:02:03 GMT):
[ ](https://chat.hyperledger.org/channel/grid?msg=jg5skuS5LMJRBRLg6) @pschwarz Discussed at LinxFest was inconsistencies in how Linux, MacOS and Windows operating systems handle date created, date modified. Seems easy to step on a landmine. https://www.linuxfestnorthwest.org/conferences/2019/program/proposals/328

cecchi (Wed, 01 May 2019 13:56:09 GMT):
should TSC update include community outreach/events/etc?

cecchi (Wed, 01 May 2019 13:56:31 GMT):
STILL LOVE MY BADGE

cliveb (Wed, 01 May 2019 18:57:20 GMT):
[ ](https://chat.hyperledger.org/channel/grid?msg=4Nuf5FqYLsiGBiBD4) @cecchi I saw this grid talk posted on twitter https://twitter.com/mvpworkshop/status/1109213275680636928

cecchi (Wed, 01 May 2019 21:17:47 GMT):
[ ](https://chat.hyperledger.org/channel/grid?msg=eCSS2yFHS29WnxNxa) THIS IS AWESOME!!!!

amundson (Wed, 01 May 2019 21:29:28 GMT):
@rjones @Silona can JIRA be used for labs projects? we might have a project coming to labs, and zenhub looks better than jira if we can get a consolidated board across all the projects. we know we can do this inside JIRA but that presumes we are using jira for everything.

Silona (Wed, 01 May 2019 23:03:27 GMT):
Yes

Silona (Wed, 01 May 2019 23:03:56 GMT):
Send an email to community-architects@hyperledger.org

Silona (Wed, 01 May 2019 23:05:15 GMT):
We are working on integrations with jira and Confluence. Also for security reasons we are centralizing on jira @dhuseby

dhuseby (Wed, 01 May 2019 23:05:21 GMT):
Has joined the channel.

amundson (Thu, 02 May 2019 15:04:34 GMT):
@Silona thanks. is the same true for the wiki (that we can get a space there for a lab project)?

Silona (Thu, 02 May 2019 15:10:55 GMT):
Currently there are pages in the lab space

Gena (Thu, 02 May 2019 18:38:03 GMT):
Hi all

Gena (Thu, 02 May 2019 18:38:03 GMT):
Hi all. I am gathering all of our Business Message standards to send over. I think we agreed I would post to the Wiki - but want to confirm.

Gena (Thu, 02 May 2019 18:38:03 GMT):
Hi all. I am gathering all of our Business Message standards to send over. I think we agreed I would post to the Wiki - but want to confirm. @agunde

jsmitchell (Thu, 02 May 2019 18:46:36 GMT):
Thanks @Gena - the wiki seems to be where things are headed. Let us know how it goes

Gena (Thu, 02 May 2019 19:34:29 GMT):
getting to the the complete needs - is not as easy as one would expect. So - We have a consolidated list of the product attributes and those of GLN

Gena (Thu, 02 May 2019 19:35:26 GMT):
(it is in a spreadsheet) :upside_down: I will also link you all to the the BMS itself if you want to see the uml diagrams, etc, etc,

jsmitchell (Thu, 02 May 2019 20:10:52 GMT):
yes, that would be great

vikas.kundz (Fri, 03 May 2019 05:57:50 GMT):
Has joined the channel.

Gena (Fri, 03 May 2019 14:37:35 GMT):
Just dropped a load of documentation on the WIKI. Apologies in advance. Happy to follow up with the right folks to walk through this.

agunde (Fri, 03 May 2019 14:54:29 GMT):
Thanks @Gena!

jsmitchell (Fri, 03 May 2019 15:14:47 GMT):
Here's a link if folks want to take a look: https://wiki.hyperledger.org/display/GRID/Uploaded+Files

cecchi (Fri, 03 May 2019 15:45:40 GMT):
i'm such a huge fan of wikis

Gena (Tue, 07 May 2019 18:33:43 GMT):
Hi guys!

Gena (Tue, 07 May 2019 18:38:42 GMT):
So I am in the Product RFC, and I am just curious if we nailed down the minimum set of required attributes? That will be very helpful for comments/input. Also - an understanding of the expected use of "product" (which should help inform the former)? I think there was a discussion about having a design session, but not sure where things landed? Thank you! @adeebahmed - wondering if we should/could have a follow up call as we look toward location?

amundson (Tue, 07 May 2019 19:33:42 GMT):
note - there is now a #transact channel for the new HL project that Sawtooth, Grid, and potentially others will eventually use for transaction processing

mc (Wed, 08 May 2019 18:32:00 GMT):
hey all

mc (Wed, 08 May 2019 18:35:09 GMT):
i'm interested in getting involved. Are there any upcoming meetings?

mfford (Wed, 08 May 2019 19:09:30 GMT):
@mc Our next HL Grid Contributor Meeting will be on May 20th. Hope to see you there! https://wiki.hyperledger.org/display/HYP/Calendar+of+Public+Meetings

mc (Wed, 08 May 2019 23:34:47 GMT):
thank you!

rahul_prasad (Thu, 09 May 2019 12:39:31 GMT):
Has joined the channel.

adeebahmed (Thu, 09 May 2019 15:07:45 GMT):
Yes @Gena, we had a post design meeting the following week after our 2-day. We arrived at keeping product as generic as possible. it will include a GTIN and a repeated field for additional property values. Apologies for the late response.

adeebahmed (Thu, 09 May 2019 16:59:52 GMT):
The current product RFC will be refactored to reflect our decision. Think of this as sort of a "base" implementation of product that can be extended on for what ever use case

Gena (Fri, 10 May 2019 18:36:42 GMT):
Ok. I am surmising that location (or is it party) would be the same? GLN would be use as the party or location identifier, with repeated fields for property values?

adeebahmed (Mon, 13 May 2019 16:10:06 GMT):
Are you asking in relation to product?

jsmitchell (Mon, 13 May 2019 16:17:47 GMT):
I think the question was 'is this general pattern also going to apply to Location and other concepts?' and my answer would be 'yes'.

viossat (Mon, 13 May 2019 19:34:39 GMT):
In Grid, are data visible to everyone?

jsmitchell (Mon, 13 May 2019 19:52:46 GMT):
@viossat the visibility of data is a question of who runs distributed ledger nodes and what data flows between parties. Grid is meant to be a set of reusable components defining data models and smart contracts which can be run on those distributed ledgers. The specific implementation may choose to make data broadly visible to a set of consortium members, or constrain it to specific parties, based on its capabilities. In other words, Grid doesn't take a position on this. It's a concern of the ledger on which the Grid code runs.

viossat (Mon, 13 May 2019 19:56:34 GMT):
Thanks. Is there an on-chain way to allow someone to read one of my data while keeping it encrypted to the others people?

adeebahmed (Mon, 13 May 2019 20:38:49 GMT):
Updated the product RFC per our post design discussion. Overall changes have narrowed the scope of this RFC down to a "base" product, such that complex product types can be be derived from this (i.e. food product, clothing, furniture, services, etc.) https://github.com/hyperledger/grid-rfcs/pull/5 @Gena @MelanieNuce

jsmitchell (Mon, 13 May 2019 20:56:52 GMT):
@viossat that is not a Grid question, but my advice would be not to share information with parties that shouldn't have access to it.

amundson (Tue, 14 May 2019 14:22:39 GMT):
@agunde @mfford @mattp @adeebahmed and I were chatting yesterday about how to handle issue tracking yesterday, and I'd like to summarize here.

amundson (Tue, 14 May 2019 14:24:47 GMT):
There are reservations about Zenhub because it requires all-or-nothing permissions and would force us to expose permissions to private repos to Zenhub. A secondary concern is lack of support for multiple dashboards per repo (you can do multiple repo per dashboard, but not the inverse).

amundson (Tue, 14 May 2019 14:25:36 GMT):
There are reservations about using HL JIRA because HL doesn't have enough resources to help configure it.

amundson (Tue, 14 May 2019 14:28:06 GMT):
The current thinking is that we proceed with a kanban board in JIRA for Grid, assuming we can get enough support from HL to create a workflow with the appropriate states. Kanban because cross-company sprint boundaries don't really make sense and we want to be friendly to all contributors. But we would add columns to enable sprint planning for those of us that are doing sprints. (Kind of like the teams have been using waffle.)

amundson (Tue, 14 May 2019 14:30:16 GMT):
We would create a label in JIRA that could be added to issues that we want to discuss during the montly contributor meeting.

amundson (Tue, 14 May 2019 14:33:46 GMT):
It looked possible yesterday to do cross-project boards based on saved filters, so @mfford is planning to look into that to see if it's a viable approach. Lack of a cross-project board solution will make it difficult to manage planning using HL JIRA, since many of the maintainers work on 3+ HL projects.

amundson (Tue, 14 May 2019 14:34:29 GMT):
[ end summary ]

rjones (Wed, 15 May 2019 15:17:06 GMT):
this is a thread about JIRA

rjones (Wed, 15 May 2019 15:17:36 GMT):
@amundson @mfford what is the goal with the JIRA mods

rjones (Wed, 15 May 2019 15:19:21 GMT):
looking at the configuration for sawtooth and grid, they have the same workflows

rjones (Wed, 15 May 2019 15:21:39 GMT):
I've added you two as "administrators" of the project, but I don't know if that is all that you need

rjones (Wed, 15 May 2019 15:24:08 GMT):
@amundson you've been an admin of the project since I created it in JIRA. Are you still blocked?

amundson (Wed, 15 May 2019 15:35:28 GMT):
@rjones ok, I didn't see it in the administration list before, but I do now

rjones (Wed, 15 May 2019 15:36:00 GMT):
I'm trying to figure out how to do cross project dashboards

amundson (Wed, 15 May 2019 15:37:24 GMT):
from what @mfford was showing me this morning, he might have that piece figured out via creating a dashboard off of a filter (I think that's the approach).

rjones (Wed, 15 May 2019 15:38:30 GMT):
OK. are you blocked on the import issue?

amundson (Wed, 15 May 2019 15:39:19 GMT):
we can see if we have enough perms now and report back. if it's not enough perms, we could get together to do it.

rjones (Wed, 15 May 2019 15:39:49 GMT):
my concern is I'm on the road a lot.

rjones (Wed, 15 May 2019 15:40:03 GMT):
but let me know.

amundson (Wed, 15 May 2019 15:40:27 GMT):
we have a meeting finishing up right now and will look at this immediately after.

amundson (Wed, 15 May 2019 15:41:19 GMT):
re:import - once we can get the board configured, we will not be hung up.

mfford (Wed, 15 May 2019 15:41:49 GMT):
@rjones Looks like I have admin now. Will check on the other capabilities in an hour and get back to you.

mattp (Wed, 15 May 2019 17:30:40 GMT):
Hey @mfford , if you get stuck configuring the project, board, or integration, let me know and will see if I or others here at TGT can help.

amundson (Wed, 15 May 2019 17:32:18 GMT):
Currently trying to do these columns on the kanban board:

amundson (Wed, 15 May 2019 17:32:22 GMT):
Backlog Planning To Do (Prioritized) In Progress In Review Done

rjones (Wed, 15 May 2019 17:46:35 GMT):
if you're blocked I'm here for the next 1:15 or so

amundson (Wed, 15 May 2019 17:50:13 GMT):
@rjones we don't think we have any blockers - we've been able to edit workflow and create a multi-project board that looks pretty nice. so we are going to start working toward using it and see if things pop up (over the next few days).

amundson (Wed, 15 May 2019 18:00:04 GMT):
apparently epics can have issues from other projects, which is cool

mfford (Wed, 15 May 2019 18:22:55 GMT):
Thanks @mattp we were able to get the board up and configured. Let me know if you would like to see what we did, and I'll ping you with a zoom when you are available.

mattp (Wed, 15 May 2019 18:42:23 GMT):
Ready when you are!

mattp (Wed, 15 May 2019 18:42:23 GMT):
@mfford Ready when you are!

mfford (Wed, 15 May 2019 18:50:33 GMT):
@mattp Sent you a zoom link

mattp (Wed, 15 May 2019 18:51:24 GMT):
Thanks. connecting now

johnfranklin (Fri, 17 May 2019 05:33:23 GMT):
Has joined the channel.

Dan (Sun, 19 May 2019 23:58:23 GMT):
Sounds like Jira issues have been resolved. There was an earlier comment about HL resources to support Jira. If there is still a perceived resourcing gap I would like to know. We are constantly evaluating where we have resource gaps across HL and whether/how to address them.

Dan (Mon, 20 May 2019 00:01:02 GMT):
Please be aware that HL has recently started a Logistics and Supply Chain SIG. [HL facilitates SIGs as well as projects and Working Groups. We deemed that SIGs were out of scope for TSC and are instead facilitated by HL staff. My perception is they tend to be business people more than developers. ] https://wiki.hyperledger.org/display/SCSIG

mfford (Mon, 20 May 2019 13:56:45 GMT):
Our next Hyperledger Grid Contributor Meeting is today at 10am CDT. The meeting information can be found on the Hyperledger Community Meetings Calendar located here: https://wiki.hyperledger.org/display/HYP/Calendar+of+Public+Meetings The agenda for today's meeting is located in the wiki here: https://wiki.hyperledger.org/pages/viewpage.action?pageId=13861020

pschwarz (Mon, 20 May 2019 15:32:01 GMT):
@cecchi Perhaps some videos for CLI/curling REST API's could be made using this: https://asciinema.org/

phoniks (Mon, 20 May 2019 17:35:31 GMT):
Hey there I'm interested in exploring how the Overlay Data Capture Architecture from the Indy Semantics WG might be able to be integrated into Grid. Here's an intro to overlays: https://medium.com/@paul.knowles_52509/overlays-data-capture-architecture-odca-providing-a-standardized-global-solution-for-data-caeb1679137a

phoniks (Mon, 20 May 2019 17:44:35 GMT):
Overlay Data Capture Architecture in Hyperledger Grid?

Dan (Tue, 21 May 2019 14:56:26 GMT):
I was unable to attend the Contrib mtg yesterday. Will there be minutes posted?

mfford (Tue, 21 May 2019 14:59:43 GMT):
There will be shortly

amundson (Tue, 21 May 2019 15:16:09 GMT):
@Dan TLDR; @Dan assigned a bunch of stuff to accomplish.

Dan (Tue, 21 May 2019 15:17:13 GMT):
thanks @mfford Not thanks @amundson

amundson (Tue, 21 May 2019 15:17:52 GMT):
thanks @Dan for the not thanks

mfford (Tue, 21 May 2019 15:20:48 GMT):
Thanks @Dan for the thanks

mfford (Wed, 22 May 2019 16:15:05 GMT):
Meeting notes from the 5/20/2019 Hyperledger Grid Contributor Meeting is here: https://wiki.hyperledger.org/pages/viewpage.action?pageId=13861678

Dan (Wed, 22 May 2019 17:58:53 GMT):
wow, that's a full on transcript :)

adeebahmed (Wed, 22 May 2019 18:37:34 GMT):
impressive

mfford (Wed, 22 May 2019 18:44:34 GMT):
Nothing gets past @agunde taking notes

adeebahmed (Thu, 23 May 2019 21:11:18 GMT):
https://github.com/hyperledger/grid-rfcs/pull/5 -- Reviews? :smiley: @jsmitchell @pschwarz @cecchi @amundson Apologies for the force pushes. Won't be doing that on future RFC's to cleanly retain the history of conversation.

brockhager (Fri, 24 May 2019 04:00:38 GMT):
Hello. I am looking at using Grid as a POC to demo to my blockchain committee at work. Is there somewhere to view the requirements for standing up a solo setup?

Dan (Fri, 24 May 2019 13:34:55 GMT):
That's a good question. You can run this right from your laptop (it will probably take 30 min or so the first time you run it so it can download and compile everything). https://github.com/hyperledger/grid-contrib/tree/master/track_and_trace If you are more interested in HW requirements that model production, it will probably depend most on your disk throughput. So on a physical machine, just make sure it has an SSD, and on a cloud instance make sure it's configured for something akin to SSD (high iops). Of course a real deployed solution is going to use several nodes for the blockchain component and whatever sort of clients you need.

Dan (Fri, 24 May 2019 13:34:55 GMT):
That's a good question @brockhager . You can run this right from your laptop (it will probably take 30 min or so the first time you run it so it can download and compile everything). https://github.com/hyperledger/grid-contrib/tree/master/track_and_trace If you are more interested in HW requirements that model production, it will probably depend most on your disk throughput. So on a physical machine, just make sure it has an SSD, and on a cloud instance make sure it's configured for something akin to SSD (high iops). Of course a real deployed solution is going to use several nodes for the blockchain component and whatever sort of clients you need.

pikvik (Fri, 24 May 2019 15:30:16 GMT):
Has joined the channel.

TelegramSam (Mon, 27 May 2019 16:35:47 GMT):
Has left the channel.

amundson (Tue, 28 May 2019 14:52:54 GMT):
@mfford this filter bar on jira looks pretty nice so far

mfford (Tue, 28 May 2019 15:12:14 GMT):
That's thanks to @rjones

mfford (Tue, 28 May 2019 15:13:03 GMT):
Certainly will help with reviews and planning

amundson (Tue, 28 May 2019 15:32:34 GMT):
it's almost like that should just be part of jria

amundson (Tue, 28 May 2019 15:32:34 GMT):
it's almost like that should just be part of jira

mfford (Tue, 28 May 2019 15:36:04 GMT):
It should be the new normal

jsmitchell (Tue, 28 May 2019 15:41:18 GMT):
oh, is that thing good?

mfford (Tue, 28 May 2019 15:59:20 GMT):
It's an improvement OOTB. It also provides tools for further search customizations

jsmitchell (Tue, 28 May 2019 16:05:15 GMT):
you missed my obvious fishing for praise

mfford (Tue, 28 May 2019 16:09:09 GMT):
I was merely reinforcing how wonderful this thing is that your humble self inspired

brockhager (Tue, 28 May 2019 19:09:14 GMT):
Thanks @Dan. I tried to build it and I got an error.

brockhager (Tue, 28 May 2019 19:09:54 GMT):
Grid

brockhager (Tue, 28 May 2019 19:10:08 GMT):

Capture.PNG

Dan (Wed, 29 May 2019 16:22:40 GMT):
I haven't seen that error before. 90% of errors we run into are network related. Are you behind a proxy?

eloafran (Wed, 29 May 2019 18:22:40 GMT):
Grid PR# 78 was merged this morning. It updates the Track and Trace Transaction Processor in Grid to use Pike Agents and Grid Schema. These changes cause transactions submited via the track-and-trace clients in grid-contrib to fail. Bellow are examples of the messages you might see. The team is currently working on updating the track and trace clients in grid-contrib, to submit transactions in the format required by the current Track and Trace Transaction Processor. Please, let me know if you have any questions. ``` grid-track-and-trace-tp | INFO | sawtooth_sdk::proces | Message: aed6271227ef4b2eab56f90443075e35 grid-track-and-trace-tp | INFO | sawtooth_sdk::proces | TP_PROCESS_REQUEST sending TpProcessResponse: Cannot build track and trace payload: InvalidTypeError: Cannot convert TrackAndTracePayload_Action with type unset. grid-track-and-trace-tp | INFO | sawtooth_sdk::proces | Message: df8a13f4160e47eeaead87275b790392 grid-track-and-trace-tp | INFO | sawtooth_sdk::proces | TP_PROCESS_REQUEST sending TpProcessResponse: Cannot build track and trace payload: InvalidTypeError: Cannot convert TrackAndTracePayload_Action with type unset. grid-track-and-trace-tp | INFO | sawtooth_sdk::proces | Message: 896fb16097e947b6a278339d075b6290 grid-track-and-trace-tp | INFO | sawtooth_sdk::proces | TP_PROCESS_REQUEST sending TpProcessResponse: Cannot build track and trace payload: InvalidTypeError: Cannot convert TrackAndTracePayload_Action with type unset. ```

eloafran (Wed, 29 May 2019 18:22:54 GMT):
Link for the PR https://github.com/hyperledger/grid/pull/78

cliveb (Thu, 30 May 2019 13:44:42 GMT):
Did I miss the Grid Q2 TSC update or is it upcoming?

agunde (Thu, 30 May 2019 13:47:24 GMT):
@cliveb it has already happened. Here is the link to the update https://wiki.hyperledger.org/display/HYP/2019+Q2+Hyperledger+Grid

adeebahmed (Thu, 30 May 2019 16:12:44 GMT):
kill running containers, and try allocating more space to your docker containers?

amundson (Thu, 30 May 2019 16:17:26 GMT):
@cliveb have you seen the new jira board? https://jira.hyperledger.org/secure/RapidBoard.jspa?rapidView=232&quickFilter=619

adeebahmed (Thu, 30 May 2019 18:03:32 GMT):
lost track of time, i'll be over in 15

cliveb (Thu, 30 May 2019 18:06:16 GMT):
Awesome: ... I'm gonna grok this board

pschwarz (Fri, 31 May 2019 15:01:01 GMT):
Added an entry to the Primitives RFC with a Datetime data type, implemented with ISO 8601 datetime strings: https://github.com/hyperledger/grid-rfcs/pull/4

dplumb (Tue, 04 Jun 2019 18:20:30 GMT):
Has joined the channel.

dplumb (Tue, 04 Jun 2019 18:23:44 GMT):
https://github.com/hyperledger/grid/pull/83 `GET /record` endpoint for Track and Trace

desktophero (Wed, 05 Jun 2019 03:21:44 GMT):
I've been contemplating a Grid concept around distributed/decentralized permissions. But it includes packaging of the applications as a desired outcome. I want to drive through some use cases and see how this fits into some overall Grid directions. @amundson - we've chatted and I'd like to see who to pull in on further convos. Would a Grid-RFC make sense?

Dan (Wed, 05 Jun 2019 15:34:23 GMT):
RFCs can be a hefty process. Nothing wrong with mailing the list an idea. If that looks to people like it should be an RFC you've already got the seed of the text.

jsmitchell (Wed, 05 Jun 2019 15:47:00 GMT):
this is also a place that conversations can happen

dexhunter (Thu, 06 Jun 2019 03:31:42 GMT):
Has joined the channel.

nhrishi (Thu, 06 Jun 2019 17:01:28 GMT):
Has joined the channel.

AmimKnabben (Tue, 11 Jun 2019 17:19:07 GMT):
Has joined the channel.

AmimKnabben (Tue, 11 Jun 2019 18:38:05 GMT):
hi, just come from Supply Chain SIG, I would like to contribute in the development side of the GRID project. Could someone point to a "help wanted" or "good first issue" list?

mfford (Tue, 11 Jun 2019 18:55:42 GMT):
@AmimKnabben Welcome to Grid! Two items that you could look into are https://jira.hyperledger.org/browse/GRID-60 and https://jira.hyperledger.org/browse/GRID-78. Also, the HL Grid Contributor Meeting is next week Monday (6/17) at 10am, where these discussions happen. Hope you can join us then! https://wiki.hyperledger.org/display/GRID/2019-06-17+Grid+Contributor+Meeting+Agenda

AmimKnabben (Tue, 11 Jun 2019 19:10:29 GMT):
@mfford awesome!

desktophero (Thu, 13 Jun 2019 04:52:35 GMT):
A use case: One of the constraints I'm attempting to address is that new Docker images would be generated (in some fashion) as part of a new version of an artifact on chain, specifically smart contracts. I'm not yet comfortable with the idea of using Docker images in a Kubernetes environment where auto-scale (at an app level) or k8s cluster events (node rolling) would mean relying on mutating a defined Docker image defined as a replica in a deployment. That mutation coming from on-chain applications. My preference would be to say that the on-chain change of a new version of the smart contract generates a new Docker image (tested via a pipeline) and updated into a manifest (Helm, vanilla YAML, whatever), and then through a CI/CD pipeline "approved" to get deployed. I realize there are some other gates in those steps but I've seen some automated deployments in a controlled pipeline k8s implementation get into a roll back loop and not be able to run any pods because everything is sideways.

bryangross (Fri, 14 Jun 2019 13:34:54 GMT):
Has joined the channel.

raph (Fri, 14 Jun 2019 15:24:59 GMT):
Has joined the channel.

mfford (Fri, 14 Jun 2019 15:45:40 GMT):
Reminder that the next Hyperledger Grid Contributor Meeting is Monday, June 17th at 10am CDT. The meeting information can be found on the Hyperledger Community Meetings Calendar: https://wiki.hyperledger.org/display/HYP/Calendar+of+Public+Meetings There is still an opportunity to add topics to the meeting. If you have an appropriate topic you would like to facilitate, please add it to the agenda: https://wiki.hyperledger.org/display/GRID/2019-06-17+Grid+Contributor+Meeting+Agenda Looking forward to seeing everyone at our next meeting!

DjCillers (Sun, 16 Jun 2019 10:50:16 GMT):
Has joined the channel.

mfford (Mon, 17 Jun 2019 13:59:38 GMT):
The Hyperledger Grid Contributor Meeting is today at 10am CDT https://wiki.hyperledger.org/display/GRID/2019-06-17+Grid+Contributor+Meeting+Agenda

Dan (Mon, 17 Jun 2019 15:19:13 GMT):
Grid smart contract specifications: https://grid.hyperledger.org/docs/grid/nightly/master/transaction_family_specifications.html

ZakiAlam (Mon, 17 Jun 2019 22:50:40 GMT):
Has joined the channel.

AmimKnabben (Wed, 19 Jun 2019 21:41:51 GMT):
is there some draft for the track and trace RFC or this will be a separated part of grid?

AmimKnabben (Wed, 19 Jun 2019 21:41:51 GMT):
is there some draft for the track and trace RFC/ideas to bring this to Grid or this will be a separated system?

AmimKnabben (Wed, 19 Jun 2019 21:58:31 GMT):
i nvm found out the task

AmimKnabben (Wed, 19 Jun 2019 21:58:31 GMT):
nvm found out the task

mattp (Thu, 20 Jun 2019 16:19:04 GMT):
Does anyone here have anyone guidance or concerns with getting Grid stickers printed up? I think I have a good image from one of the Grid project sites. Thoughts?

mattp (Thu, 20 Jun 2019 16:19:04 GMT):
Does anyone here have guidance or concerns with getting Grid stickers printed up? I think I have a good image from one of the Grid project sites. Thoughts?

wgraham (Thu, 20 Jun 2019 16:22:57 GMT):
Has joined the channel.

wgraham (Thu, 20 Jun 2019 16:22:57 GMT):
Hey everyone, are there any sample Grid track and trace apps someone can point me to? Been playing around with the contracts but would appreciate a UI :)

amundson (Thu, 20 Jun 2019 16:25:42 GMT):
@mattp we used sticker mule in the past for some of them (the ones without 'Hyperledger' on them - those were done by HL directly). do you have the grid svg?

mattp (Thu, 20 Jun 2019 16:26:48 GMT):
Sounds good. We've used them before and just grabbed the svg from the top of the page here: https://wiki.hyperledger.org/display/GRID/Hyperledger+Grid

jsmitchell (Thu, 20 Jun 2019 16:27:19 GMT):
@mattp can you order enough of them so that we could have a stack to handout?

mattp (Thu, 20 Jun 2019 16:27:47 GMT):
Absolutely. I'll order as much as possible.

amundson (Thu, 20 Jun 2019 16:28:06 GMT):
I'd like the variant with only the square logo, same size as the others we have for other projects, so we can plaster them on notebooks etc. If you are taking requests. :)

jsmitchell (Thu, 20 Jun 2019 16:28:06 GMT):
I'm sure @cecchi would want some too

mattp (Thu, 20 Jun 2019 16:28:45 GMT):
Sounds good. Maybe I can two variants printed. One with and one without the text.

mattp (Thu, 20 Jun 2019 16:28:45 GMT):
Sounds good. Maybe I can get two variants printed. One with and one without the text.

jsmitchell (Thu, 20 Jun 2019 16:29:23 GMT):
@wgraham there is a PR up with an asset tracking UI and associated contracts <- @dplumb

wgraham (Thu, 20 Jun 2019 16:29:51 GMT):
@jsmitchell amazing will take a look, thanks for the heads up

jsmitchell (Thu, 20 Jun 2019 16:30:30 GMT):
https://github.com/hyperledger/grid-contrib/pull/20

jsmitchell (Thu, 20 Jun 2019 16:33:07 GMT):
@mattp hyperledger already had a bunch of stickers printed up with the logo and the text. I assume they ordered a large amount. We haven't been sent any. @cecchi was able to grab a couple from the booth at Consensus, but it would be nice if HL could ship us a couple of hundred. cc @ry

amundson (Thu, 20 Jun 2019 16:33:49 GMT):
I'd like to call for final-comment-period (which lasts a week) on two RFCs - core team and GS1 subteam - https://github.com/hyperledger/grid-rfcs/pull/12 and https://github.com/hyperledger/grid-rfcs/pull/11 - at the end of the FCP, the root team will take a vote. any concerns? if not, I'll call for FCP on the PRs themselves.

cecchi (Thu, 20 Jun 2019 17:14:37 GMT):
HL already printed up a bunch - we can prob just order more and/or get their template if we want

mattp (Thu, 20 Jun 2019 17:40:38 GMT):
When you say a bunch, are we talking like a couple hundred, or thousands? I'm pretty sure if I ordered 1k, I'd be able to get rid of them before the summer is over. :smiley:

chlsc (Fri, 21 Jun 2019 05:39:54 GMT):
Has joined the channel.

davidwboswell (Mon, 24 Jun 2019 15:12:32 GMT):
We're planning on doing a Hyperledger meetup in Portland in July during OSCON. The Portland meetup group is particularly interested in having a talk on Grid, so I wanted to see if anyone here is planning on attending OSCON and would like to speak at a Hyperledger meetup there. If so, please feel free to reach out here or at dboswell@linuxfoundation.org. Thanks.

amundson (Mon, 24 Jun 2019 15:32:59 GMT):
Portland is great, highly recommended. (I can't make it unfortunately.)

raph (Mon, 24 Jun 2019 16:31:26 GMT):
Looking to contribute to the grid cli. For clarification, if I wanted to write the cli to manage product, here https://github.com/hyperledger/grid/tree/master/cli would be the place to do that?

cecchi (Mon, 24 Jun 2019 16:34:55 GMT):
https://github.com/hyperledger/grid-rfcs/pull/5 is a good place to review current thinking for Product, in particular a GS1 specific variant

amundson (Mon, 24 Jun 2019 21:26:55 GMT):
The core team RFC has entered FCP - https://github.com/hyperledger/grid-rfcs/pull/11

cecchi (Mon, 24 Jun 2019 21:54:50 GMT):
Fantastic to see merge for Product smart contracts -@adeebahmed++

cecchi (Mon, 24 Jun 2019 21:54:50 GMT):
Fantastic to see merge for Product smart contracts -@adeebahmed ++

cecchi (Mon, 24 Jun 2019 21:54:50 GMT):
Fantastic to see merge for Product smart contracts - @adeebahmed ++

cecchi (Mon, 24 Jun 2019 21:55:27 GMT):
karmabot--

pschwarz (Tue, 25 Jun 2019 00:55:56 GMT):
@cecchi I think I've addressed your primitives comment

mattp (Tue, 25 Jun 2019 21:00:49 GMT):

UcS0dG96HmWBaPcL6Vsp.jpeg

adeebahmed (Tue, 25 Jun 2019 21:05:15 GMT):
if you want a good lol as to why rocket 0.3 is broken - https://github.com/briansmith/ring/issues/774

adeebahmed (Tue, 25 Jun 2019 21:06:21 GMT):
yanked with good intentions

amundson (Tue, 25 Jun 2019 21:18:24 GMT):
basically "stay away from ring" is the take away

pschwarz (Tue, 25 Jun 2019 21:36:55 GMT):
I wouldn't call those good intentions

pschwarz (Tue, 25 Jun 2019 21:37:27 GMT):
That maintainer seems to have a fundamental misunderstanding of how versions are supported

amundson (Tue, 25 Jun 2019 21:50:43 GMT):
grid-daemon depends on ring indirectly because actix-web uses cookie

amundson (Tue, 25 Jun 2019 21:51:38 GMT):
this is a very cool tool - https://github.com/sfackler/cargo-tree

amundson (Tue, 25 Jun 2019 21:53:11 GMT):
```ring v0.13.5 └── cookie v0.11.0 └── actix-web v0.7.19 └── grid-daemon v0.1.0```

pschwarz (Tue, 25 Jun 2019 21:55:33 GMT):
Yeah, I've been using that - helped me diagnose a build issue with Sawtooth recently

amundson (Tue, 25 Jun 2019 21:55:53 GMT):
it's really very good

pschwarz (Tue, 25 Jun 2019 21:57:32 GMT):
Using that plus cargo-outdated are two nice tools for dependency upkeep: https://crates.io/crates/cargo-outdated

raph (Wed, 26 Jun 2019 18:33:56 GMT):
I have a PR opened with a failing Jenkins build: https://github.com/hyperledger/grid/pull/104 Looking at the error, seems like I'm not on a builders whitelist ``` + ./bin/whitelist pa3ng /etc/jenkins-authorized-builders FAILED: User 'pa3ng' not whitelisted. ``` How would one get on this whitelist?

agunde (Wed, 26 Jun 2019 19:10:54 GMT):
@raph @rberg2 will add you __

agunde (Wed, 26 Jun 2019 19:10:54 GMT):
@raph @rberg2 will add you

rberg2 (Wed, 26 Jun 2019 19:10:54 GMT):
Has joined the channel.

rberg2 (Wed, 26 Jun 2019 19:25:58 GMT):
@raph You have been added and I restarted your build.

raph (Wed, 26 Jun 2019 20:02:20 GMT):
thanks!

eloafran (Mon, 01 Jul 2019 17:03:50 GMT):
PR #90 was merged this morning. If you rebase on master you will have to rebuild the grid daemon image, otherwise `docker-compose up` will fail

raph (Mon, 01 Jul 2019 19:52:55 GMT):
Hi, looking for some feedback on [PR 104](https://github.com/hyperledger/grid/pull/104). Thx!

amundson (Tue, 02 Jul 2019 18:42:17 GMT):
The core subteam RFC has been merged - https://github.com/hyperledger/grid-rfcs/pull/11

amundson (Tue, 02 Jul 2019 19:19:27 GMT):
The GS1 subteam RFC has been merged - https://github.com/hyperledger/grid-rfcs/pull/12

HLFPOC (Sat, 06 Jul 2019 10:17:31 GMT):
Has joined the channel.

HLFPOC (Mon, 08 Jul 2019 08:38:34 GMT):
Hello Team, I am a complete beginner in terms of Hyperledger Grid and want to develop a supply chain solution on Blockchain. I have got hands-on experience of Hyperledger Fabric and now want to build a supply chain solution using Hyperledger Grid. So I would like to understand the correct approach to go through the basics and other necessary material to start my development. Also I would like to understand if it is mandatory to understand Hyperledger Sawtooth in order to start with GRID ?

mfford (Mon, 08 Jul 2019 18:03:20 GMT):
Our next Hyperledger Grid Contributor Meeting is Monday, July 15th at 10am CDT. The meeting information can be found on the Hyperledger Community Meetings Calendar: https://wiki.hyperledger.org/display/HYP/Calendar+of+Public+Meetings We are in the process of creating the agenda for this meeting. If you have an appropriate topic you would like to facilitate, please add it to the agenda: https://wiki.hyperledger.org/display/GRID/2019-07-15+Grid+Contributor+Meeting+Agenda Hope everyone can attend!

rjones (Mon, 08 Jul 2019 18:08:33 GMT):
Has left the channel.

amundson (Mon, 08 Jul 2019 20:56:56 GMT):
@HLFPOC The track_and_trace example apps (fish_client and asset_client) in grid-contrib are good examples of applications which uses several of Grid's components. There is a dependency on Sawtooth.

HLFPOC (Tue, 09 Jul 2019 04:11:11 GMT):
Thanks for the reply! I assume I will have to start with Sawtooth first before jumping directly into the GRID samples

pschwarz (Tue, 09 Jul 2019 14:51:46 GMT):
The Grid Primitives RFC should be re-reviewed, and probably moved towards final comment period soon: https://github.com/hyperledger/grid-rfcs/pull/4

amundson (Tue, 09 Jul 2019 15:46:29 GMT):
@pschwarz I read through the RFC and it looks fine to me. Once everyone on the core subteam has had a chance to do a final read through, I agree we should move to FCP.

amundson (Tue, 09 Jul 2019 15:47:52 GMT):
@cecchi was advocating for renaming 'schema'. I don't have a solid alternative suggestion that is better though.

adeebahmed (Tue, 09 Jul 2019 15:49:09 GMT):
back from vacation -- final review? https://github.com/hyperledger/grid-rfcs/pull/5 :)

adeebahmed (Tue, 09 Jul 2019 16:11:31 GMT):
This should also be good to merge, once jenkins is done: https://github.com/hyperledger/grid/pull/100

amundson (Tue, 09 Jul 2019 16:34:54 GMT):
@adeebahmed I'll read through the current version of product next - can we fix the word wrapping first? I attempted to create a PR for you against your branch (never done this before, but I think it will work) - https://github.com/target/grid-rfcs/pull/2

adeebahmed (Tue, 09 Jul 2019 17:55:05 GMT):
Thanks @amundson just merged it. Looks like it propagate back to the hyperledger/grid-rfcs as intended :)

adeebahmed (Tue, 09 Jul 2019 17:55:05 GMT):
Thanks @amundson just merged it. Looks like it propagated back to the hyperledger/grid-rfcs as intended :)

adeebahmed (Tue, 09 Jul 2019 17:55:05 GMT):
Thanks @amundson just merged it. Looks like it propagated back to the hyperledger/grid-rfcs repo as intended :)

cliveb (Tue, 09 Jul 2019 19:30:06 GMT):
Substrate or Membrane ....

Imoh (Thu, 11 Jul 2019 06:36:34 GMT):
Has joined the channel.

adeebahmed (Thu, 11 Jul 2019 21:08:59 GMT):
should be a quick review: https://github.com/hyperledger/grid/pull/100

adeebahmed (Thu, 11 Jul 2019 21:12:39 GMT):
I'm thinking about starting up the catalog rfc -- we should meet and briefly discuss the scope it. Perhaps before sprint planning on Tuesday? Thoughts? @amundson @cecchi @mfford

raph (Fri, 12 Jul 2019 15:11:54 GMT):
fyi this open issue may cause your PR's Jenkins build fail: https://github.com/rust-lang/rust/issues/62562 *TL;DR:* `serde` does not build with the latest version of nightly

raph (Fri, 12 Jul 2019 15:11:54 GMT):
FYI this open issue may cause your PR's Jenkins build fail: https://github.com/rust-lang/rust/issues/62562 *TL;DR:* `serde` does not build with the latest version of nightly

raph (Fri, 12 Jul 2019 15:11:54 GMT):
FYI this open issue may cause your PR's Jenkins build to fail: https://github.com/rust-lang/rust/issues/62562 *TL;DR:* `serde` does not build with the latest version of nightly

adeebahmed (Fri, 12 Jul 2019 15:16:51 GMT):
Why is Jenkins building with nightly?

agunde (Fri, 12 Jul 2019 15:17:29 GMT):
@adeebahmed wasm smart contracts need nightly to build

agunde (Fri, 12 Jul 2019 15:18:17 GMT):
the rest uses stable

adeebahmed (Fri, 12 Jul 2019 15:18:42 GMT):
gotcha

adeebahmed (Fri, 12 Jul 2019 15:19:04 GMT):
https://github.com/hyperledger/grid/pull/100 :smiley:

mfford (Fri, 12 Jul 2019 15:21:49 GMT):
Reminder that our next Hyperledger Grid Contributor Meeting is Monday, July 15th at 10am CDT. The meeting information can be found on the Hyperledger Community Meetings Calendar: https://wiki.hyperledger.org/display/HYP/Calendar+of+Public+Meetings We are finalizing the agenda for this meeting. If you have an appropriate topic you would like to facilitate, please add it to the agenda: https://wiki.hyperledger.org/display/GRID/2019-07-15+Grid+Contributor+Meeting+Agenda Looking forward to seeing everyone at our next meeting!

raph (Fri, 12 Jul 2019 19:58:47 GMT):
@eloafran thanks for the build restart!

raph (Fri, 12 Jul 2019 20:00:23 GMT):
issue seems resolved with the newest nightly

eloafran (Fri, 12 Jul 2019 20:02:58 GMT):
np!

mfford (Mon, 15 Jul 2019 12:28:18 GMT):
Reminder that the Hyperledger Grid Contributor Meeting is today at 10am CDT. The meeting information can be found on the Hyperledger Community Meetings Calendar: https://wiki.hyperledger.org/display/HYP/Calendar+of+Public+Meetings If you have an appropriate topic you would like to facilitate, you can still add it to the agenda: https://wiki.hyperledger.org/display/GRID/2019-07-15+Grid+Contributor+Meeting+Agenda Looking forward to seeing everyone at our next meeting!

raph (Mon, 15 Jul 2019 15:34:42 GMT):
Hi, fishing for one last review/approval on this PR https://github.com/hyperledger/grid/pull/104 Thanks! :smile:

raph (Mon, 15 Jul 2019 15:39:11 GMT):
This is also ready for review: https://github.com/hyperledger/grid/pull/99 :raised_hands:

mfford (Mon, 15 Jul 2019 15:55:51 GMT):
Meeting notes from today's Hyperledger Grid Contributor Meeting: https://wiki.hyperledger.org/pages/viewpage.action?pageId=16321690

adeebahmed (Wed, 17 Jul 2019 15:38:08 GMT):
should members of the core subteam have the ability to review pr's?

agunde (Wed, 17 Jul 2019 16:55:27 GMT):
The members of the subteams need to be added as maintainers and codeowners in the RFC repo. Once that is done you will be able to review PRs in the Grid RFC repo. Note you can still add comments before this is complete.

ViaSky (Wed, 17 Jul 2019 17:27:34 GMT):
Has joined the channel.

cheeky (Wed, 17 Jul 2019 18:49:06 GMT):
Has joined the channel.

raph (Thu, 18 Jul 2019 15:42:30 GMT):
Looking for a merge on this approved PR https://github.com/hyperledger/grid/pull/104

jsmitchell (Thu, 18 Jul 2019 15:44:41 GMT):
merged

adeebahmed (Thu, 18 Jul 2019 15:46:30 GMT):
if we could get a review on this: https://github.com/hyperledger/grid/pull/99 -- this not being merged is blocking product cli

adeebahmed (Thu, 18 Jul 2019 15:46:30 GMT):
if we could get 2 reviews on this: https://github.com/hyperledger/grid/pull/99 -- this not being merged is blocking product cli

jsmitchell (Thu, 18 Jul 2019 16:14:21 GMT):
looks like @agunde and @pschwarz should re-review

agunde (Thu, 18 Jul 2019 16:14:31 GMT):
working on it now

adeebahmed (Thu, 18 Jul 2019 16:18:40 GMT):
thanks :smiley:

pschwarz (Thu, 18 Jul 2019 16:23:57 GMT):
Looks like the existing comments haven't been addressed, @add

pschwarz (Thu, 18 Jul 2019 16:23:57 GMT):
Looks like the existing comments haven't been addressed, @adeebahmed

add (Thu, 18 Jul 2019 16:23:57 GMT):
Has joined the channel.

pschwarz (Thu, 18 Jul 2019 16:24:26 GMT):
and @raph

raph (Thu, 18 Jul 2019 16:24:52 GMT):
thanks!

agunde (Thu, 18 Jul 2019 16:32:46 GMT):
I also added some more comments

cheeky (Thu, 18 Jul 2019 20:44:16 GMT):
Hi all, we've been working on building a supply chain tracking solution with Sawtooth, and have just recently become aware of this project. How close is Grid to exiting incubation? We are thinking about whether to continue investing our effort with Sawtooth or begin exploring Grid.

Dan (Fri, 19 Jul 2019 14:07:47 GMT):
Hi @cheeky the two should be pretty well aligned. Sawtooth will be your deployment layer and Grid offers libraries, data types, etc. to facilitate the App Layer development. The original work for Grid spun out from the supply chain example in Sawtooth.

adeebahmed (Fri, 19 Jul 2019 22:05:57 GMT):
Incorporated your comments @cecchi https://github.com/hyperledger/grid-rfcs/pull/5

adeebahmed (Mon, 22 Jul 2019 14:53:32 GMT):
Goodmorning, https://github.com/hyperledger/grid/pull/100 - 2 approvals ready to be merged

raph (Tue, 23 Jul 2019 15:31:01 GMT):
@agunde @pschwarz Applied change requests for https://github.com/hyperledger/grid/pull/99 ready again for review

raph (Tue, 23 Jul 2019 15:31:01 GMT):
@agunde @pschwarz Applied change requests to https://github.com/hyperledger/grid/pull/99 ready again for review

raph (Tue, 23 Jul 2019 19:20:59 GMT):
thanks for the reveiw @agunde applied the new change requests

mattp (Wed, 24 Jul 2019 18:19:00 GMT):
gina

raph (Wed, 24 Jul 2019 19:02:42 GMT):
^ Looking for 1 more approval!

adeebahmed (Wed, 24 Jul 2019 20:11:48 GMT):
https://github.com/hyperledger/grid-rfcs/pull/5 - Ready for reviews, lets get this into final comment period :smiley:

adeebahmed (Wed, 24 Jul 2019 20:33:55 GMT):
It would be good to have a discussion about the intersection of Grid Catalog and GS1 standards -- I'm reading into the Catalogue Item Sync document and want to be clear about actors and their roles when it comes different catalog actions

adeebahmed (Wed, 24 Jul 2019 20:34:22 GMT):
The document for reference: https://www.gs1.org/docs/gdsn/3.1/BMS_GDSN_Catalogue_Item_Sync_r3p1p0_i1_p0_p6_25Aug2015.pdf

MelanieNuce (Wed, 24 Jul 2019 22:18:19 GMT):
Yes, agreed. I apologize for not getting back to you on the DM about this. I was confusing your ask with an attribute association (grouping items together that have like characteristics). @Gena clarified for me that this is about actual exchange of item data for multiple items, and in that case, Catalogue Item Sync and of course the actual schema for the payload - Catalogue Item Notification, would both be in play. Should we schedule a call to discuss?

raph (Thu, 25 Jul 2019 15:11:15 GMT):
'

adeebahmed (Thu, 25 Jul 2019 15:37:05 GMT):
How does tomorrow 2pm-3pm CST sound? @MelanieNuce

MelanieNuce (Thu, 25 Jul 2019 16:17:10 GMT):
@adeebahmed Unfortunately, I am traveling tomorrow - I have Mon 11 am-Noon or 3:30 on, or Tue 10-11 am or 1-3:30 pm - any of those windows work on your side?

adeebahmed (Thu, 25 Jul 2019 16:28:27 GMT):
Monday 11am-noon works for me. Would others like to be included in this conversation? @cecchi @amundson @jsmitchell

jsmitchell (Thu, 25 Jul 2019 16:33:50 GMT):
yeah, I'd like to attend -- that time works for me

adeebahmed (Thu, 25 Jul 2019 16:37:58 GMT):

Clipboard - July 25, 2019 11:37 AM

adeebahmed (Thu, 25 Jul 2019 16:38:02 GMT):
There are some limitation with the free version of zoom... do we all have skype, or lync?

mfford (Thu, 25 Jul 2019 16:39:36 GMT):
I could set-up a zoom for that time, if that helps

adeebahmed (Thu, 25 Jul 2019 16:40:01 GMT):
that'd be great @mfford i'll forward you the agenda

MelanieNuce (Thu, 25 Jul 2019 17:25:38 GMT):
thanks @mfford, I also have a conference line/WebEx (I know, we are so last century) if needed

mfford (Thu, 25 Jul 2019 17:35:17 GMT):
No worries. I can provide the zoom

jsmitchell (Thu, 25 Jul 2019 18:20:38 GMT):
@mfford go ahead and add @cecchi to the invite

mattp (Thu, 25 Jul 2019 19:10:03 GMT):
@mfford Please add me to the invite on Monday as well. Thank you!

PatrickErichsen (Fri, 26 Jul 2019 14:02:44 GMT):
Has joined the channel.

raph (Fri, 26 Jul 2019 15:56:42 GMT):
1 more review plz https://github.com/hyperledger/grid/pull/99 :eyes:

adeebahmed (Fri, 26 Jul 2019 17:02:01 GMT):
small annoyance https://github.com/hyperledger/grid/pull/109

adeebahmed (Fri, 26 Jul 2019 19:26:37 GMT):
^ 2 approvals should bea quick merge

adeebahmed (Fri, 26 Jul 2019 19:26:37 GMT):
^ 2 approvals should be a quick merge

cecchi (Mon, 29 Jul 2019 15:02:07 GMT):
i can only make first half of the catalog meeting today

MelanieNuce (Mon, 29 Jul 2019 16:34:24 GMT):
Current GS1 price synchronization standard: https://www.gs1.org/sites/default/files/docs/gdsn/guidelines/GDSN-Price-Sync-ImpGuide.pdf

MelanieNuce (Mon, 29 Jul 2019 16:38:50 GMT):
Earlier post is the implementation guide, here is the actual Business Message Standard: https://www.gs1.org/docs/gdsn/3.1/BMS_Price_Sync_r3p1p3_i1p3p5_23May2017.pdf

Patrick-Erichsen (Tue, 30 Jul 2019 19:58:10 GMT):
Has joined the channel.

pschwarz (Tue, 30 Jul 2019 21:03:38 GMT):
Have folks on the reviewer list read the Primitives RFC? https://github.com/hyperledger/grid-rfcs/pull/4 Specifically, @RobinBanks @jsmitchell @amundson

RobinBanks (Tue, 30 Jul 2019 21:03:39 GMT):
Has joined the channel.

pschwarz (Tue, 30 Jul 2019 21:04:14 GMT):
:point_up: @Dan @eloafran @ltseeley

amundson (Tue, 30 Jul 2019 21:08:22 GMT):
@pschwarz yes

pschwarz (Tue, 30 Jul 2019 21:25:39 GMT):
And @desktophero

raph (Wed, 31 Jul 2019 15:06:02 GMT):
Looking for a merge on this approved PR https://github.com/hyperledger/grid/pull/99

adeebahmed (Wed, 31 Jul 2019 15:12:08 GMT):
https://github.com/hyperledger/grid-rfcs/pull/5 - review this pls @cecchi @pschwarz

adeebahmed (Wed, 31 Jul 2019 15:12:08 GMT):
https://github.com/hyperledger/grid-rfcs/pull/5 - review this pls @cecchi @pschwarz @amundson @jsmitchell @agunde

raph (Wed, 31 Jul 2019 19:29:06 GMT):
PR to add unit tests for Product smart contract https://github.com/hyperledger/grid/pull/111

cecchi (Thu, 01 Aug 2019 18:05:36 GMT):
thoughts on the name 'product type' as an attribute of Product schema, but meaning the more specific "type" (GS1, etc) of Product. I have some concerns about this being a heavily used term within the product domain generally, so avoiding overloading it here may make sense. I also think this will set precedent for other Schemas with similar patterns

cecchi (Thu, 01 Aug 2019 18:05:59 GMT):
options could be (others welcome):

cecchi (Thu, 01 Aug 2019 18:06:08 GMT):
product_spec

cecchi (Thu, 01 Aug 2019 18:06:18 GMT):
product_format

cecchi (Thu, 01 Aug 2019 18:07:00 GMT):
product_schema_type

cecchi (Thu, 01 Aug 2019 18:07:08 GMT):
product_schema[_spec | _format | _etc]

jsmitchell (Thu, 01 Aug 2019 18:08:21 GMT):
we should keep schema out of it, as that already has a meaning in the design

jsmitchell (Thu, 01 Aug 2019 18:08:49 GMT):
I like both spec and format

jsmitchell (Thu, 01 Aug 2019 18:09:28 GMT):
format probably has a more formal connotation

jsmitchell (Thu, 01 Aug 2019 18:13:17 GMT):
so, of those, my vote would be for product_spec

adeebahmed (Thu, 01 Aug 2019 18:15:38 GMT):
I had responded on the github thread with the suggestion "product_standard" -- I was considering product_spec, but i feel specifications associated with products may be another concept within supply chains that we may overload with using it here

jsmitchell (Thu, 01 Aug 2019 18:24:42 GMT):
standard is good too, although not all product thingies might be standards

cecchi (Thu, 01 Aug 2019 18:35:07 GMT):
spec for sure has deeper meaning

cecchi (Thu, 01 Aug 2019 18:40:24 GMT):
i can't get super psyched about any of these really

cecchi (Thu, 01 Aug 2019 18:44:34 GMT):
the intent is to capture the industry standard / spec that the ID and the Properties will conform to

cecchi (Thu, 01 Aug 2019 18:44:59 GMT):
GS1 is a standard and a spec

cecchi (Thu, 01 Aug 2019 18:45:45 GMT):
maybe taking product_ out of the name is good, that way when we use the same concept on Location or whatever it'd be the same field

adeebahmed (Thu, 01 Aug 2019 18:48:30 GMT):
i would opt for "standard" for reuse -- we are using the GS1 standard, but may not be following the exact spec to every detail. In fact it's often the case where we meld the GS1 spec with custom attributes of our own

cecchi (Thu, 01 Aug 2019 18:51:27 GMT):
good take

cecchi (Thu, 01 Aug 2019 18:55:25 GMT):
ok product_standard

cecchi (Thu, 01 Aug 2019 18:55:49 GMT):
i still don't like it as much as i want to but i can't come up with anything i like better

mattp (Thu, 01 Aug 2019 19:06:55 GMT):
Just a couple more to toss in there:

mattp (Thu, 01 Aug 2019 19:07:39 GMT):
Product_Conformance Product_Adherence Product_Alignment Product_Segment

amundson (Thu, 01 Aug 2019 19:13:52 GMT):
It should probably be product_namespace given it's meaning in the RFC.

jsmitchell (Thu, 01 Aug 2019 19:17:09 GMT):
yeah, that's good

amundson (Thu, 01 Aug 2019 19:17:15 GMT):
specifically, it is there for this purpose: "All Grid addresses are prefixed by the 6-hex-character namespace prefix “621dee”, Products are further prefixed under the Grid namespace with reserved enumerations of “02” (“00” and “01” being reserved for other purposes) indicating “Products” and an additional “01” indicating “GS1 Products”."

amundson (Thu, 01 Aug 2019 19:17:41 GMT):
so you need to know GS1 so you can build the address

amundson (Thu, 01 Aug 2019 19:18:47 GMT):
and everything in that product namespace follows rules associated with that style of product storage (such as it's use of schema, addressing, etc.)

trevormcdonald (Thu, 01 Aug 2019 19:19:09 GMT):
Has joined the channel.

cecchi (Thu, 01 Aug 2019 20:28:27 GMT):
v good

cecchi (Thu, 01 Aug 2019 20:28:37 GMT):
will update rfc w/ comments as such

adeebahmed (Fri, 02 Aug 2019 15:11:03 GMT):
updated: https://github.com/hyperledger/grid-rfcs/pull/5

raph (Fri, 02 Aug 2019 22:15:47 GMT):
Looking for 1 more approval and a merge: https://github.com/hyperledger/grid/pull/111

amundson (Fri, 02 Aug 2019 22:23:10 GMT):
@raph done

adeebahmed (Mon, 05 Aug 2019 15:29:55 GMT):
Does pike store its data in the same state as grid? In the code I see the namespace for pike is 'cad11d', is that it's own state root hash? I don't see it prepended by '621dee' so it doesn't seem to be a part of grid state. Is that intentional?

jsmitchell (Mon, 05 Aug 2019 15:49:15 GMT):
they are all part of the same state, those are both address prefixes

cecchi (Mon, 05 Aug 2019 18:02:14 GMT):
gs1 session today will do a group review of Product RFC, Catalog RFC and talk about attribute schemas for Product

raph (Tue, 06 Aug 2019 01:54:37 GMT):
Small PR, should be a quick review https://github.com/hyperledger/grid/pull/112

raph (Tue, 06 Aug 2019 17:54:19 GMT):
Have a PR out for story grid-21, adding grid product to state delta export https://github.com/hyperledger/grid/pull/113 Looking for feedback/reviews :slight_smile:

adeebahmed (Tue, 06 Aug 2019 20:41:40 GMT):
https://github.com/hyperledger/grid-rfcs/pull/14#discussion_r311103450

Gena (Thu, 08 Aug 2019 16:58:06 GMT):
I would like to understand this more - is there a perceived gap in the GS1 standard for what we are doing here? if so - what is that and can we accommodate somehow in GS1 standards?

cecchi (Fri, 09 Aug 2019 14:21:48 GMT):
i think this is about addressing "custom" or specific fields that a trading partner may require

cecchi (Fri, 09 Aug 2019 14:23:11 GMT):
like a company may - and often does - ask for GS1 compliant product data + additional attributes

Gena (Fri, 09 Aug 2019 15:12:22 GMT):
ok - great

Gena (Fri, 09 Aug 2019 15:12:46 GMT):
so that impacts greatly the design of catalog

cecchi (Fri, 09 Aug 2019 16:21:48 GMT):
it may or may not impact the design of catalog - catalog is a collection of products

cecchi (Fri, 09 Aug 2019 16:23:13 GMT):
and it's super unlikely that the product attributes would impact the ability of a catalog to 'store' it

raph (Fri, 09 Aug 2019 18:17:52 GMT):
Looking for 1 more review/approval https://github.com/hyperledger/grid/pull/113 thanks!

adeebahmed (Fri, 09 Aug 2019 19:15:43 GMT):
lot of good discussion on the product and catalog RFCs

Patrick-Erichsen (Fri, 09 Aug 2019 21:03:56 GMT):
Hello all,

Patrick-Erichsen (Fri, 09 Aug 2019 21:03:56 GMT):
Hello all, I just opened a PR to Grid but my Jenkins build failed with the following error: `FAILED: User ‘Patrick-Erichsen’ not whitelisted.` Is this the right forum to request addition to the whitelist?

pschwarz (Sat, 10 Aug 2019 21:43:14 GMT):
I can kick the build off for you

raph (Mon, 12 Aug 2019 16:20:12 GMT):
[ ](https://chat.hyperledger.org/channel/grid?msg=sdnwwEmYPneTqwKmX) :pray:

mfford (Tue, 13 Aug 2019 13:35:33 GMT):
The next Hyperledger Grid Contributor Meeting is Monday, August 19th at 10am CDT. The meeting information can be found on the Hyperledger Community Meetings Calendar: https://wiki.hyperledger.org/display/HYP/Calendar+of+Public+Meetings Here is the direct link to the meeting: https://zoom.us/j/933448029 We are creating the agenda for this meeting. If you have an appropriate topic you would like to facilitate, please add it to the agenda: https://wiki.hyperledger.org/display/GRID/2019-08-19+Grid+Contributor+Meeting+Agenda

adeebahmed (Tue, 13 Aug 2019 14:04:22 GMT):
We have 3 "Changes requested" on the product rfc, @agunde @cecchi @jsmitchell If you are satisfied with the outcome please accept the changes. https://github.com/hyperledger/grid-rfcs/pull/5

adeebahmed (Tue, 13 Aug 2019 14:13:51 GMT):
I have started the process to enter FCP: https://github.com/hyperledger/grid-rfcs/pull/5#issuecomment-520851888 please review/approve accordingly, thanks

pschwarz (Tue, 13 Aug 2019 14:23:40 GMT):
I will be making the move with RFC 4 (https://github.com/hyperledger/grid-rfcs/pull/4), but would like to make sure that @amundson @agunde @desktophero @dplumb @jsmitchell have read it

raph (Tue, 13 Aug 2019 15:26:31 GMT):
Morning! Can I get a merge for this PR - https://github.com/hyperledger/grid/pull/113 thanks!

agunde (Tue, 13 Aug 2019 15:53:51 GMT):
@adeebahmed there are still formatting issues in the Grid Product RFC that need to be fixed.

adeebahmed (Tue, 13 Aug 2019 17:05:14 GMT):
better? https://github.com/hyperledger/grid-rfcs/pull/5

agunde (Tue, 13 Aug 2019 17:17:48 GMT):
There are still lines longer then 80 characters in some of the bullets @adeebahmed

adeebahmed (Tue, 13 Aug 2019 18:01:06 GMT):
:cry:

adeebahmed (Tue, 13 Aug 2019 18:15:48 GMT):
fixed

Dan (Tue, 13 Aug 2019 18:17:32 GMT):
Someone gave me an interesting idea the other day. An RFC linter. Save as many headaches as possible on RFC process and help focus reviewer feedback on the substance of the idea rather than formatting/spelling/etc. A few things like line length would be easy to flag. Other things I've seen people get caught up on like grammar probably aren't as addressable.

amundson (Tue, 13 Aug 2019 18:18:53 GMT):
@Dan yeah, that would be great

jsmitchell (Tue, 13 Aug 2019 18:24:35 GMT):
@Dan code it up

Dan (Tue, 13 Aug 2019 18:25:12 GMT):
I did. I just wrote all that text up there.

jsmitchell (Tue, 13 Aug 2019 18:25:30 GMT):
https://github.com/markdownlint/markdownlint

Dan (Tue, 13 Aug 2019 18:26:19 GMT):
nice ^

adeebahmed (Tue, 13 Aug 2019 18:28:36 GMT):
Yes, a RFC linter that ignores code within backticks would be very nice. Also wrapping sentences from the start of a line, rather than combining them (in the case of bullet points). These are some RFC linting pain points i've experienced

Dan (Tue, 13 Aug 2019 20:20:22 GMT):
I'd write it but it seems really hard. I bet no one on this channel could even create an MVP version.

agunde (Tue, 13 Aug 2019 20:47:00 GMT):
@raph merged

raph (Tue, 13 Aug 2019 20:47:18 GMT):
thanks!

desktophero (Wed, 14 Aug 2019 13:38:02 GMT):
Commented, @pschwarz

desktophero (Wed, 14 Aug 2019 13:53:33 GMT):
I figured I'd raise my comment on the grid primitive (https://github.com/hyperledger/grid-rfcs/pull/4#issuecomment-521243522) RFC here ... the primitive RFC calls out two specific permissions (`can_create_schema` and `can_update_schema`). I'm not clear on the RBAC enforcement model within Grid - either the conceptual thinking around the direction it will go or if there are concrete examples. From an "enterprise" view, these roles would typically be delegated by a separate role that doesn't have permissions to modify schema but does have permissions to apply/remove/enforce those permissions to other roles as well as add agents (people, systems, etc.) to the roles. Any docs/rfcs that folks can point me at around this?

achenette (Wed, 14 Aug 2019 18:10:07 GMT):
:eyes:

adeebahmed (Thu, 15 Aug 2019 14:36:45 GMT):
reverse psychology eh? :smiley:

Dan (Thu, 15 Aug 2019 15:07:23 GMT):
I have no idea what you are talking about. I'm too busy white washing this fence.. it's like the funnest thing I've ever done. :D

desktophero (Thu, 15 Aug 2019 15:27:05 GMT):
Write what?

Dan (Thu, 15 Aug 2019 17:15:28 GMT):
An RFC linter. James also linked to a markdown linter above that would handle some portion of the concept.

desktophero (Thu, 15 Aug 2019 18:40:54 GMT):
gotcha

Patrick-Erichsen (Thu, 15 Aug 2019 20:55:00 GMT):
Hello all, I'm getting the following error when trying to perform a `Product Create` action: ``` sawtooth-sabre-tp | 2019-08-15 20:53:03,276 INFO [sawtooth_sabre::handler] Action: Execute Contract ["00ec01d391987f1d0b5e8e2c7dde388fa110c9d1c6f14a6a7c03d2e85fb3a6379c79ae", "00ec02d15330c9f52aa67a4fee0efdc00f7f55b5116f0365d294af7ffcc951e8974de7", "00ec00d4eb478d386d0d216048a54575feda3450f2fcc42b3d15f80e258c16010da412", "00ec00ebfd680ea8abffc272049e01409cda9efec943f4ddca0263897e715913a04705", "cad11d", "621dee01"] ["00ec01d391987f1d0b5e8e2c7dde388fa110c9d1c6f14a6a7c03d2e85fb3a6379c79ae", "00ec02d15330c9f52aa67a4fee0efdc00f7f55b5116f0365d294af7ffcc951e8974de7", "00ec00ebfd680ea8abffc272049e01409cda9efec943f4ddca0263897e715913a04705", "621dee02"] sawtooth-sabre-tp | 2019-08-15 20:53:03,279 INFO [sawtooth_sdk::processor] TP_PROCESS_REQUEST sending TpProcessResponse: Contract does not exist: grid_product, 1.0 ``` It seems like Sabre isn't able to find the contract even though the executable appears to be building just fine. Here is the relevant piece of the docker-compose: https://github.com/target/grid/blob/master/docker-compose.yaml#L80

Patrick-Erichsen (Thu, 15 Aug 2019 20:55:00 GMT):
Hello all, I'm getting a `Contract does not exist` error when trying to perform a `Product Create` action: ``` sawtooth-sabre-tp | 2019-08-15 20:53:03,276 INFO [sawtooth_sabre::handler] Action: Execute Contract ["00ec01d391987f1d0b5e8e2c7dde388fa110c9d1c6f14a6a7c03d2e85fb3a6379c79ae", "00ec02d15330c9f52aa67a4fee0efdc00f7f55b5116f0365d294af7ffcc951e8974de7", "00ec00d4eb478d386d0d216048a54575feda3450f2fcc42b3d15f80e258c16010da412", "00ec00ebfd680ea8abffc272049e01409cda9efec943f4ddca0263897e715913a04705", "cad11d", "621dee01"] ["00ec01d391987f1d0b5e8e2c7dde388fa110c9d1c6f14a6a7c03d2e85fb3a6379c79ae", "00ec02d15330c9f52aa67a4fee0efdc00f7f55b5116f0365d294af7ffcc951e8974de7", "00ec00ebfd680ea8abffc272049e01409cda9efec943f4ddca0263897e715913a04705", "621dee02"] sawtooth-sabre-tp | 2019-08-15 20:53:03,279 INFO [sawtooth_sdk::processor] TP_PROCESS_REQUEST sending TpProcessResponse: Contract does not exist: grid_product, 1.0 ``` It seems like Sabre isn't able to find the contract even though the executable appears to be building just fine. Here is the relevant piece of the docker-compose: https://github.com/target/grid/blob/master/docker-compose.yaml#L80

RedKnight13 (Fri, 16 Aug 2019 10:00:33 GMT):
Has joined the channel.

agunde (Fri, 16 Aug 2019 14:21:54 GMT):
@Patrick-Erichsen can you look for InvalidTransactions My first guess would be that one of the steps for uploading the contract failed.

adeebahmed (Fri, 16 Aug 2019 15:51:27 GMT):
https://github.com/hyperledger/grid-rfcs/pull/5 @dplumb @desktophero @cecchi @MelanieNuce :)

Patrick-Erichsen (Fri, 16 Aug 2019 16:18:25 GMT):
For anyone curious, the problem was that I had a mismatch between the contract registry and the name of the contract - one was 'product' and the other was 'grid_product'.

desktophero (Fri, 16 Aug 2019 16:21:25 GMT):
[ ](https://chat.hyperledger.org/channel/grid?msg=bpXAXqAkHrXgGEFjz) @ I'm traveling today and will try to take a look this weekend. Thanks for the poke.

mfford (Fri, 16 Aug 2019 18:29:19 GMT):
REMINDER: The next Hyperledger Grid Contributor Meeting is Monday, August 19th at 10am CDT. The meeting information can be found on the Hyperledger Community Meetings Calendar: https://wiki.hyperledger.org/display/HYP/Calendar+of+Public+Meetings Here is the direct link to the meeting: https://zoom.us/j/933448029 We are still collecting agenda items for this meeting. If you have an appropriate topic you would like to facilitate, please add it to the agenda: https://wiki.hyperledger.org/display/GRID/2019-08-19+Grid+Contributor+Meeting+Agenda

adityasingh177 (Mon, 19 Aug 2019 09:56:49 GMT):
Has joined the channel.

adeebahmed (Mon, 19 Aug 2019 14:21:49 GMT):
REMINDER: We are very close to the merging of the Product RFC, 3 more approvals https://github.com/hyperledger/grid-rfcs/pull/5#issuecomment-520851888 @desktophero @cecchi @MelanieNuce

adeebahmed (Mon, 19 Aug 2019 14:21:49 GMT):
REMINDER: We are very close to the FCP of the Product RFC, 3 more approvals https://github.com/hyperledger/grid-rfcs/pull/5#issuecomment-520851888 @desktophero @cecchi @MelanieNuce

Patrick-Erichsen (Mon, 19 Aug 2019 15:27:13 GMT):
Need one more approval for a quick build fix on some `dyn` errors: https://github.com/hyperledger/grid/pull/117

adeebahmed (Tue, 20 Aug 2019 14:19:46 GMT):
last 2 before we can enter FCP: https://github.com/hyperledger/grid-rfcs/pull/5#issuecomment-520851888 @desktophero @cecchi

desktophero (Tue, 20 Aug 2019 15:33:01 GMT):
commented and approved. LGTM

adeebahmed (Mon, 26 Aug 2019 15:05:52 GMT):
Friendly reminder, we have entered FCP for the Product RFC. It will end on Friday, Aug 30th 2019 EOD.

adeebahmed (Mon, 26 Aug 2019 18:42:20 GMT):
Catalog RFC update: https://github.com/hyperledger/grid-rfcs/pull/14/files

desktophero (Tue, 27 Aug 2019 13:17:41 GMT):
I've looked for existing docs (here in chat, Grid mailing list, internal backlogs) and the closest I've come is finding some callouts on getting a smart permission/identity RFC started. If this isn't already in another person's workload, I'd like to get an RFC started (following the steps in the grid-rfc README). If this is part of an existing work stream, I've love to help contribute.

Dan (Tue, 27 Aug 2019 14:09:45 GMT):
Not sure if this is helpful or not but here's some Pike docs if you haven't already seen those. https://sawtooth.hyperledger.org/docs/sabre/releases/latest/smart_permissions.html https://github.com/hyperledger/sawtooth-sabre/blob/master/contracts/sawtooth-pike/docs/source/pike_transaction_family.rst

desktophero (Tue, 27 Aug 2019 20:37:54 GMT):
Thanks for the link. I have read through that. I'll circle back on that and see if I can unwrap that a little more. An example of what I'm wondering tied back to [this comment](https://github.com/hyperledger/grid-rfcs/pull/4#issuecomment-521243522) on the Primitives RFC

desktophero (Tue, 27 Aug 2019 20:40:01 GMT):
`can_create_schema` is the example permission but not the only sample. This entity needs to have some actions associated with it for the permission to mean anything, right?

Patrick-Erichsen (Tue, 27 Aug 2019 20:56:53 GMT):
Couple of small PRs to review: https://github.com/hyperledger/grid/pull/116 https://github.com/hyperledger/grid/pull/120 And one meatier one:

Patrick-Erichsen (Tue, 27 Aug 2019 20:56:53 GMT):
Couple of small PRs to review: https://github.com/hyperledger/grid/pull/116 https://github.com/hyperledger/grid/pull/120 And one meatier one: https://github.com/hyperledger/grid/pull/114

trevormcdonald (Tue, 27 Aug 2019 20:57:51 GMT):
Related PR ready for review: https://github.com/hyperledger/grid/pull/115

pschwarz (Thu, 29 Aug 2019 16:01:15 GMT):
The Grid Primitives RFC has entered final comment period. It will be merged on 05 Sep 2019.

cecchi (Thu, 29 Aug 2019 16:11:51 GMT):
hi all - i'll be unavailable for the Design session this afternoon

adeebahmed (Fri, 30 Aug 2019 20:16:35 GMT):
Do all catalogs have an expiry date? In the context of Grid as an SDK, i'm debating whether "expiry_date" is a field that should be a "catalog primitive". A Grid catalog (the function of grouping products together) does not _need_ an "expiry_date". A field like that could be enforced by a catalog related schema that requires it in its additional fields, along with say an "effective_date" and whatever else an organization would like to see.

adeebahmed (Fri, 30 Aug 2019 20:18:04 GMT):
I'm thinking of pulling that out of being primitive field -- and providing a schema for catalog that enforces it (as an example). Similar to what i did with catalog_product.

adeebahmed (Fri, 30 Aug 2019 20:18:39 GMT):
Just throwing the thought out into the ether, can definitely discuss this in detail in the next design discussion

Dan (Sun, 01 Sep 2019 14:20:55 GMT):
FYI, if you were not already aware we are planning a maintainers summit across HL for the beginning of October in Minneapolis. https://wiki.hyperledger.org/display/events/Maintainer+Summit+October+8-10%2C+2019 For MSP locals, if you have ideas for extracurricular activities please contact @mfford.

Dan (Sun, 01 Sep 2019 14:21:29 GMT):
Also maintainers please register at the link ^ so we have an accurate count.

trevormcdonald (Tue, 03 Sep 2019 14:27:32 GMT):
Looking for a review on this: https://github.com/hyperledger/grid/pull/115

VipinB (Tue, 03 Sep 2019 14:45:23 GMT):
Has joined the channel.

adeebahmed (Tue, 03 Sep 2019 15:21:45 GMT):
Good to merge the product-rfc? https://github.com/hyperledger/grid-rfcs/pull/5 -- or are the open conversations on this a preventing factor? I've addressed all the comments.

adeebahmed (Tue, 03 Sep 2019 15:31:18 GMT):
@amundson @Dan @cecchi

VipinB (Tue, 03 Sep 2019 16:13:15 GMT):
#performance-and-scale-wg is in the process of creating a provenance use case to be the driver for objective metrics across dlts. The data model uses GS1 concepts. The preliminary writeup is in https://docs.google.com/document/d/1pARtxESnOqQViJabErC5hxFupyfZWCWtOnxsLVtHP4Y/edit?usp=sharing - Would like to find out what the level of GS1 support in Grid. I have been poking around the repo, any tips about layout or documentation of the repo will also be appreciated.

cecchi (Tue, 03 Sep 2019 19:07:11 GMT):
good from my end

amundson (Tue, 03 Sep 2019 19:23:16 GMT):
@adeebahmed add another comment with the checklist of people that must approve accepting the RFC (you can copy it from your "enter FCP" comment), then we just need everyone to put in their vote.

amundson (Tue, 03 Sep 2019 19:25:31 GMT):
"FCP has ended without substantial new feedback. Propose this RFC be approved and merged. Both GS1 and core subteams must approve." or similar

adeebahmed (Tue, 03 Sep 2019 19:30:25 GMT):
:thumbsup:

adeebahmed (Tue, 03 Sep 2019 19:49:35 GMT):
FCP on the Product RFC has ended! No substantial feedback during FCP. Please review/approve or request for me to do so on your behalf. Thanks! https://github.com/hyperledger/grid-rfcs/pull/5#issuecomment-527610405 @agunde @dplumb @jsmitchell @desktophero @pschwarz @amundson @Gena @mattp @MelanieNuce

adeebahmed (Tue, 03 Sep 2019 20:37:20 GMT):
pls review: https://github.com/hyperledger/grid/pull/115

adeebahmed (Tue, 03 Sep 2019 20:37:43 GMT):
@pschwarz @agunde :smiley:

adeebahmed (Wed, 04 Sep 2019 14:25:20 GMT):
Goodmorning all, FCP on the Product RFC has ended! No substantial feedback during FCP. Please review/approve or request for me to do so on your behalf. Thanks! https://github.com/hyperledger/grid-rfcs/pull/5#issuecomment-527610405 @dplumb @jsmitchell @desktophero @pschwarz @Gena

trevormcdonald (Wed, 04 Sep 2019 20:00:08 GMT):
https://github.com/hyperledger/grid/pull/115 @pschwarz @agunde

Patrick-Erichsen (Wed, 04 Sep 2019 20:00:13 GMT):
This one could also use a review https://github.com/hyperledger/grid/pull/114 :smile:

adeebahmed (Wed, 04 Sep 2019 20:00:23 GMT):
^^

adeebahmed (Thu, 05 Sep 2019 14:11:56 GMT):
Goodmorning people of Grid, FCP on the Product RFC has ended! No substantial feedback during FCP. Please review/approve or request for me to do so on your behalf. Thanks! https://github.com/hyperledger/grid-rfcs/pull/5#issuecomment-527610405 @Patrick-Erichsen jsmitchell @desktophero @Gena

VipinB (Thu, 05 Sep 2019 22:00:28 GMT):
[ ](https://chat.hyperledger.org/channel/grid?msg=DEv5Mw7r5gQmgu4bt) Hi guys, any word on the GS1 support in Grid would be appreciated, especially pointers to documents or code... This is for #performance-and-scale-wg use-case and solution

jsmitchell (Thu, 05 Sep 2019 23:37:23 GMT):
@VipinB Grid is based on GS1 data concepts read the properties and product PRs which are in final comment period in the grid-rfcs repo

jsmitchell (Thu, 05 Sep 2019 23:37:23 GMT):
@VipinB Grid is based on GS1 data concepts. Read the properties and product PRs which are in final comment period in the grid-rfcs repo.

VipinB (Fri, 06 Sep 2019 13:01:26 GMT):
Thanks @jsmitchell will look at this. Any plans to bring in or liaison with GS1 open source work. https://github.com/gs1

VipinB (Fri, 06 Sep 2019 13:04:25 GMT):
This is still in the initial stages of construction. What did the Oracle team do to build their demo (Grid on Fabric)? since they seemed to have some code for GS1 types. Have they contributed the code back?

cecchi (Fri, 06 Sep 2019 14:29:01 GMT):
they have not contributed the code back - based on the review we saw they implemented a grid inspired set of smart contracts that mimic'd grid/GS1 design

cecchi (Fri, 06 Sep 2019 14:29:46 GMT):
GS1 has day to day involvement in Grid and their resources are probably better positioned to respond to the github/gs1 question

pschwarz (Fri, 06 Sep 2019 15:01:34 GMT):
Final comment period has ended on the Grid Primitives RFC. Please review/approve or request for me to do so on your behalf: https://github.com/hyperledger/grid-rfcs/pull/4 @adeebahmed @agunde @dplumb @desktophero @jsmitchell @amundson

adeebahmed (Fri, 06 Sep 2019 15:28:12 GMT):
EVERYONE HAS APPROVED https://github.com/hyperledger/grid-rfcs/pull/5#issuecomment-527610405

adeebahmed (Fri, 06 Sep 2019 15:28:18 GMT):
good to merge?

mfford (Fri, 06 Sep 2019 15:45:56 GMT):
@adeebahmed Since the approvals are present, proceed with merging

adeebahmed (Fri, 06 Sep 2019 16:18:42 GMT):
merged

VipinB (Fri, 06 Sep 2019 19:19:53 GMT):
I will take a look at Pike as well since the two sets of Identities being modeled are a. Enterprises (maybe GLN or GLEIF based) (this may be in Pike) b.Products (GTIN) there might be additional types and events we want to model along with EPIC and other GS1 concepts. Still feeling my way around

Patrick-Erichsen (Mon, 09 Sep 2019 13:45:25 GMT):
would anyone mind merging this PR? https://github.com/hyperledger/grid/pull/120

pschwarz (Mon, 09 Sep 2019 13:56:00 GMT):
@Patrick-Erichsen done

Patrick-Erichsen (Mon, 09 Sep 2019 13:56:18 GMT):
appreciated :thumbsup:

trevormcdonald (Mon, 09 Sep 2019 16:18:06 GMT):
Could this PR also get merged? https://github.com/hyperledger/grid/pull/115

agunde (Mon, 09 Sep 2019 16:20:46 GMT):
@trevormcdonald merged

pschwarz (Mon, 09 Sep 2019 20:10:16 GMT):
Grid primitives RFC has been merged

desktophero (Mon, 09 Sep 2019 21:45:47 GMT):
:fireworks:

cecchi (Tue, 10 Sep 2019 12:42:06 GMT):
i will unfortunately be unable to make planning in person today, will be on the phone

mattp (Tue, 10 Sep 2019 18:12:26 GMT):
Target is not planning to be on the phone today due to our annual events (today and this week). We'll update our Jira tickets with up to date info.

mfford (Tue, 10 Sep 2019 20:19:37 GMT):
We can move the planning portions of today's meeting to the Thursday design session. I'll update the calendar accordingly

mfford (Tue, 10 Sep 2019 20:19:37 GMT):
We can move the planning portions of today's meeting to the Thursday design session. I'll update the calendar accordingly, and cancel today's meeting.

mfford (Wed, 11 Sep 2019 14:50:04 GMT):
The next Hyperledger Grid Contributor Meeting is Monday, September 16th at 10am CDT. The meeting information can be found on the Hyperledger Community Meetings Calendar: https://wiki.hyperledger.org/display/HYP/Calendar+of+Public+Meetings Here is the direct link to the meeting: https://zoom.us/j/933448029 We are collecting agenda items for this meeting. If you have an appropriate topic you would like to facilitate, please add it to the agenda: https://wiki.hyperledger.org/display/GRID/2019-09-16+Grid+Contributor+Meeting+Agenda

mfford (Fri, 13 Sep 2019 17:46:13 GMT):
REMINDER: The next Hyperledger Grid Contributor Meeting is Monday, September 16th at 10am CDT. The meeting information can be found on the Hyperledger Community Meetings Calendar: https://wiki.hyperledger.org/display/HYP/Calendar+of+Public+Meetings Here is the direct link to the meeting: https://zoom.us/j/933448029 We are still collecting agenda items for this meeting. If you have an appropriate topic you would like to facilitate, please add it to the agenda: https://wiki.hyperledger.org/display/GRID/2019-09-16+Grid+Contributor+Meeting+Agenda

mfford (Mon, 16 Sep 2019 15:58:10 GMT):
Meeting notes from today's Hyperledger Grid Contributor Meeting: https://wiki.hyperledger.org/pages/viewpage.action?pageId=20022554

Levilk (Fri, 20 Sep 2019 12:09:04 GMT):
Has joined the channel.

Levilk (Fri, 20 Sep 2019 12:09:05 GMT):
Hello! Are there any roadmap about the development of this project? I am curious, when will the tool support Fabric?

amundson (Fri, 20 Sep 2019 14:40:28 GMT):
@Levilk there is not a timeline for Fabric support. many of us are using Sawtooth with PBFT because it is a better fit for our use cases. but from a Grid project perspective, we do want wider DLT support. so, we do have an informal medium/long term plan. the general approach will be to integrate support for Transact (which can run Grid's Sabre contracts) into Fabric. that is a deep platform engineering task (really, between Fabric and Transact). once that is done, then it should be relatively easy to figure out the tasks we need to do as part of Grid. In the short term, as a Grid community we are committed to only include smart contracts that can be run in Transact so we are in-line with this plan.

MelanieNuce (Sun, 22 Sep 2019 22:51:18 GMT):
Team, I uploaded some additional files pertaining to GS1 Location to the Grid Wiki: https://wiki.hyperledger.org/display/GRID/Uploaded+Files

MelanieNuce (Sun, 22 Sep 2019 22:55:20 GMT):
These include the GS1 Web Vocabulary standard (designed to support web search based on structured data) and the GS1 US Data Hub Location user guide. GS1 US Data Hub is a local tool based on the GS1 Global Location Number standard, with local implementation needs included. The user guide covers the complete experience in the tool, but there is a location data model starting on page 21 - which includes all attributes supported in the tool. As @Gena had previously shared, the EPCIS event visibility data sharing standard also has location (site and sub-site) master data attributes, which are detailed in the Core Business Vocabulary (CBV) standard. Both of those were already uploaded to the Wiki by Gena some months ago. We have a new team member that just started two weeks ago, he is going to begin working on pulling together the GS1 Location overview for the RFC immediately. We will keep the team apprised of his progress. He should be on the HL project page and Rocketchat sometime next week. Thanks!

st (Mon, 23 Sep 2019 08:10:57 GMT):
Has joined the channel.

mattp (Mon, 23 Sep 2019 17:17:37 GMT):
I will be unavailable today for the design session due to a conflicting Dr appt. :head_bandage:

agunde (Mon, 23 Sep 2019 18:42:36 GMT):
@raph @Patrick-Erichsen does https://github.com/hyperledger/grid/pull/120 close https://jira.hyperledger.org/browse/GRID-99

Patrick-Erichsen (Mon, 23 Sep 2019 19:17:11 GMT):
I don't believe so - https://github.com/hyperledger/grid/pull/120 is to allow for the deletion of a Product, but https://jira.hyperledger.org/browse/GRID-99 is to allow for the creation of an empty product list.

agunde (Mon, 23 Sep 2019 19:27:27 GMT):
I was thinking this bug was created because there was not a way to remove a Product from a ProductList (and reset in state) if ProductList only contained the one product. 120 however implements the correct solution of just deleting the entire product list if it only contains the product being deleted. What are the remaining uses for creating an empty ProductList?

Patrick-Erichsen (Mon, 23 Sep 2019 19:31:02 GMT):
Ah I see what you mean - I don't know to be honest. I just assumed that there was use case for it based on this sentence ``` Theoretically, we should be able to instantiate an empty ProductList. ```

Patrick-Erichsen (Mon, 23 Sep 2019 19:31:54 GMT):
@raph

Patrick-Erichsen (Mon, 23 Sep 2019 19:42:47 GMT):
Sounds like Raph created this ticket because while testing it was sort of a pain to need to first create a Product and then add it to a ProductList in order to test the ProductList. So I don't think we have any real-world use case for having an empty ProductList

Patrick-Erichsen (Mon, 23 Sep 2019 19:42:54 GMT):
I think we can close the ticket.

nussharif123 (Mon, 23 Sep 2019 20:09:40 GMT):
Has joined the channel.

nussharif123 (Mon, 23 Sep 2019 20:09:41 GMT):
Hello all, I'm new to this group - Joining from the GS1 US side, on Melanie's team. Just getting setup and will work on the GS1 Location overview for the RFC. Looking forward to contributing and collaborating with you all:hand_splayed:

jsmitchell (Mon, 23 Sep 2019 20:12:18 GMT):
hi @nussharif123 !

mattp (Mon, 23 Sep 2019 20:19:05 GMT):
Looking forward to working with you @nussharif123 ! Welcome!

nussharif123 (Mon, 23 Sep 2019 20:22:59 GMT):
thanks @mattp @jsmitchell , likewise

adeebahmed (Tue, 24 Sep 2019 15:13:49 GMT):
https://github.com/hyperledger/grid-rfcs/pull/16 @amundson @jsmitchell when you get a chance :)

Levilk (Thu, 26 Sep 2019 12:01:12 GMT):
Thank you for the answer!

Patrick-Erichsen (Thu, 26 Sep 2019 16:04:16 GMT):
Looking for one more review on the Product CLI PR - https://github.com/hyperledger/grid/pull/114

KellyCooper (Sun, 29 Sep 2019 18:11:02 GMT):
Has joined the channel.

trevormcdonald (Mon, 30 Sep 2019 13:07:59 GMT):
https://github.com/hyperledger/grid/pull/121 is ready for a merge

agunde (Mon, 30 Sep 2019 17:08:19 GMT):
@trevormcdonald merged

NickWest (Wed, 02 Oct 2019 09:13:51 GMT):
Has joined the channel.

NickWest (Wed, 02 Oct 2019 09:13:52 GMT):
Hiya everyone

NickWest (Wed, 02 Oct 2019 09:16:15 GMT):
I am an Eth dev looking to get my feet wet with Hyper Ledger to see if it is suitable for a supply chain project I am undertaking

NickWest (Wed, 02 Oct 2019 09:19:20 GMT):
any recommendations re: getting started with HyperLedger services with the goal of eventually playing with/developing Grid?

NickWest (Wed, 02 Oct 2019 10:30:27 GMT):
hmm, it appears that Sawtooth is the way to go?

Dan (Wed, 02 Oct 2019 11:50:55 GMT):
You can get started with Grid directly.

Dan (Wed, 02 Oct 2019 11:52:54 GMT):
There's a docker-compose file in the root of the repo that will launch a bunch of stuff for you. You can poke into those different components to see what they do or check out the docs: https://grid.hyperledger.org/

Dan (Wed, 02 Oct 2019 11:54:05 GMT):
With your Eth background you might also be interested to dig into the WASM smart contract aspect of grid. You'll see references to `sabre` - that's analogous to the EVM.

pschwarz (Thu, 03 Oct 2019 15:30:16 GMT):
@Patrick-Erichsen left some feedback on PR 114

pschwarz (Thu, 03 Oct 2019 15:30:29 GMT):
(sorry for the late feedback; was on vacation)

adeebahmed (Mon, 07 Oct 2019 14:48:06 GMT):
2 approvals, can this be merged? @Patrick-Erichsen https://github.com/hyperledger/grid/pull/114

Patrick-Erichsen (Mon, 07 Oct 2019 14:48:59 GMT):
Yes - Peter had some feedback on Friday that I have finished and the builds are passing.

pschwarz (Mon, 07 Oct 2019 15:56:45 GMT):
Merged!

silasdavis (Tue, 08 Oct 2019 17:54:49 GMT):
Has joined the channel.

silasdavis (Tue, 08 Oct 2019 17:54:51 GMT):
Behold this majesty: https://github.com/hyperledger/grid/pull/125

silasdavis (Wed, 09 Oct 2019 21:55:32 GMT):
So... I compiled grid's pike contract with: ``` rustup update rustup target add wasm32-unknown-unknown cargo build --target wasm32-unknown-unknown ```

silasdavis (Wed, 09 Oct 2019 21:55:39 GMT):
the contract I get is 42MB

silasdavis (Wed, 09 Oct 2019 21:55:48 GMT):
gzipped its still 7MB

silasdavis (Wed, 09 Oct 2019 21:55:52 GMT):
am I doing something wrong?

silasdavis (Wed, 09 Oct 2019 21:56:06 GMT):
because this will blow the default 4 MiB limit of GRPC

silasdavis (Wed, 09 Oct 2019 22:00:59 GMT):
Actually I see that I am pulling this from the target/wasm.../debug directory

pschwarz (Wed, 09 Oct 2019 22:31:59 GMT):
After that, did you compile it with `--release`?

agunde (Thu, 10 Oct 2019 12:47:43 GMT):
@silasdavis From locally testing debug gives me 41M and release is 2.6M.

pschwarz (Thu, 10 Oct 2019 13:56:36 GMT):
Here is a guide (draft at the moment) for optimizations of the resulting wasm: https://rustwasm.github.io/book/reference/code-size.html

silasdavis (Thu, 10 Oct 2019 14:16:19 GMT):
ah thanks... where is the WASM artefact written with --release?

RobinBanks (Thu, 10 Oct 2019 14:18:38 GMT):
target/wasm.../release

RobinBanks (Thu, 10 Oct 2019 14:18:38 GMT):
target/release

silasdavis (Thu, 10 Oct 2019 14:19:49 GMT):
yeah sorry just answered my own question, I was in the wrong bit

silasdavis (Thu, 10 Oct 2019 14:19:54 GMT):
target/wasm32-unknown-unknown/release/grid-pike-tp.wasm

silasdavis (Thu, 10 Oct 2019 15:48:45 GMT):
cool... so I can now run these contracts

silasdavis (Thu, 10 Oct 2019 15:48:52 GMT):
I mean they break

silasdavis (Thu, 10 Oct 2019 15:49:07 GMT):
Where in sabre can I find the storage function resolvers for WASM?

pschwarz (Thu, 10 Oct 2019 15:53:22 GMT):
I think they are implemented here: https://github.com/hyperledger/sawtooth-sabre/blob/master/tp/src/wasm_executor/wasm_externals.rs @RobinBanks can probably provide more details

jsmitchell (Thu, 10 Oct 2019 15:53:56 GMT):
they are wrapped by the sdk as externs https://github.com/hyperledger/sawtooth-sabre/blob/master/sdk/src/externs.rs

MelanieNuce (Thu, 10 Oct 2019 19:45:08 GMT):
@nussharif123 will you please add the GLN doc discussed on today's design call to the project wiki?

nussharif123 (Thu, 10 Oct 2019 19:45:39 GMT):
will do. thanks @MelanieNuce

nussharif123 (Thu, 10 Oct 2019 19:54:53 GMT):
done.

newhall (Thu, 17 Oct 2019 14:29:14 GMT):
Has joined the channel.

mfford (Thu, 17 Oct 2019 15:32:04 GMT):
The next Hyperledger Grid Contributor Meeting is Monday, October 21st at 10am CDT. The meeting information can be found on the Hyperledger Community Meetings Calendar. Here is the direct link to the meeting: https://zoom.us/j/933448029 We are collecting agenda items for this meeting. If you have an appropriate topic you would like to facilitate, please add it to the agenda: https://wiki.hyperledger.org/display/GRID/2019-10-21+Grid+Contributor+Meeting+Agenda Looking forward to seeing everyone at our next meeting!

adeebahmed (Thu, 17 Oct 2019 18:29:15 GMT):
https://github.com/hyperledger/grid-rfcs/pull/14

amundson (Mon, 21 Oct 2019 15:22:12 GMT):
Can we set a goal date for everyone reading this RFC? Maybe Friday?

mattp (Mon, 21 Oct 2019 15:39:24 GMT):
Great idea. +1

sanket1211 (Fri, 08 Nov 2019 12:25:22 GMT):
Has joined the channel.

adeebahmed (Mon, 11 Nov 2019 19:58:14 GMT):
Hey all, I've incorporated a good amount of feedback in the last week or two. Please read through it and add any questions/concerns at your earliest convenience :smiley: https://github.com/hyperledger/grid-rfcs/pull/14/files?short_path=5de5fb3#diff-5de5fb32f294f10e0dad597fbc967bd2

adeebahmed (Mon, 11 Nov 2019 19:58:14 GMT):
Hey all, I've incorporated a good amount of feedback for the Catalog RFC in the last week or two. Please read through it and add any questions/concerns at your earliest convenience :smiley: https://github.com/hyperledger/grid-rfcs/pull/14/files?short_path=5de5fb3#diff-5de5fb32f294f10e0dad597fbc967bd2

AmimKnabben (Wed, 13 Nov 2019 16:09:05 GMT):
https://courses.edx.org/courses/course-v1:MITx+CTL.SC4x+3T2019/course/

AmimKnabben (Wed, 13 Nov 2019 16:09:39 GMT):
s/rdbms/grid/g

adeebahmed (Thu, 14 Nov 2019 21:29:54 GMT):
Hi all, please read through it and add any questions/concerns at your earliest convenience 😃 https://github.com/hyperledger/grid-rfcs/pull/14/files?short_path=5de5fb3#diff-5de5fb32f294f10e0dad597fbc967bd2

Deepakbyrappa (Sun, 17 Nov 2019 04:38:43 GMT):
Has joined the channel.

trevormcdonald (Wed, 20 Nov 2019 13:53:19 GMT):
Looking for reviews on this PR: https://github.com/hyperledger/grid/pull/122

SatheeshNehru (Wed, 20 Nov 2019 14:55:47 GMT):
Has joined the channel.

SatheeshNehru (Wed, 20 Nov 2019 14:56:41 GMT):
how to get start with grid is there any way by which i can try out grid?

mfford (Wed, 20 Nov 2019 15:54:11 GMT):
Hi @SatheeshNehru you can get started with Grid by looking at the links contained here: https://grid.hyperledger.org/

adeebahmed (Tue, 26 Nov 2019 16:24:00 GMT):
Please resolve open conversations if my response is satisfactory: https://github.com/hyperledger/grid-rfcs/pull/14#pullrequestreview-323109975 @agunde @amundson @jsmitchell @Gena

adeebahmed (Tue, 26 Nov 2019 16:24:00 GMT):
Please resolve open conversations if my response is satisfactory: https://github.com/hyperledger/grid-rfcs/pull/14 @agunde @amundson @jsmitchell @Gena

adeebahmed (Wed, 27 Nov 2019 15:44:28 GMT):
Updated to resolved feedback, please resolve open conversations https://github.com/hyperledger/grid-rfcs/pull/14

adeebahmed (Tue, 03 Dec 2019 20:07:45 GMT):
Updated to resolved feedback, please resolve open conversations https://github.com/hyperledger/grid-rfcs/pull/14

adeebahmed (Tue, 03 Dec 2019 20:07:45 GMT):
Updated to resolve feedback, please resolve open conversations https://github.com/hyperledger/grid-rfcs/pull/14

adeebahmed (Fri, 06 Dec 2019 15:42:41 GMT):
Updated to resolve feedback, please resolve open conversations https://github.com/hyperledger/grid-rfcs/pull/14

adeebahmed (Mon, 09 Dec 2019 16:18:07 GMT):
pls https://github.com/hyperledger/grid-rfcs/pull/14#pullrequestreview-323109975

trevormcdonald (Tue, 10 Dec 2019 16:09:16 GMT):
Looking for a review: https://github.com/hyperledger/grid/pull/122

amundson (Tue, 10 Dec 2019 16:37:39 GMT):
@trevormcdonald I added some comments.

adeebahmed (Tue, 10 Dec 2019 17:41:06 GMT):
Please resolve or respond to the open conversations https://github.com/hyperledger/grid-rfcs/pull/14 @dplumb

trevormcdonald (Fri, 13 Dec 2019 14:28:10 GMT):
Looking for re-reviews: https://github.com/hyperledger/grid/pull/122

pschwarz (Mon, 16 Dec 2019 15:47:14 GMT):
@amundson :point_up:

harrywright (Wed, 18 Dec 2019 18:11:49 GMT):
Has joined the channel.

ikingqu (Thu, 19 Dec 2019 13:43:47 GMT):
Has joined the channel.

RunaStaph (Tue, 24 Dec 2019 20:23:25 GMT):
Has joined the channel.

RunaStaph (Wed, 25 Dec 2019 18:24:14 GMT):
Hello all and Merry Christmas. In the spirit of Christmas, I want to share that the current `grid-contrib` and possibly the 'grid' code needs further testing

RunaStaph (Wed, 25 Dec 2019 18:24:14 GMT):
Hello all and Merry Christmas. Can someone confirm that they have successful built the current grid / grid-contrib code and the demos run smoothly.

RunaStaph (Wed, 25 Dec 2019 18:29:14 GMT):
I have been debugging (and getting to know) the code since last night in an attempt to `1` run the demo, `2` run sample data + seed core types scripts located in the Server folder, Fish Client folder, and Asset Client folder. I haven't succeed yet. Suffice to say either I suck (99% chance) or there are errors within the code

RunaStaph (Wed, 25 Dec 2019 18:32:49 GMT):
I will post error messages later if needed. However, the errors that I have seen so far are simple errors eg https://github.com/hyperledger/grid-contrib/blob/08c2061ccb5be7fb4e138ada614a4875c9ee98d8/track_and_trace/server/api/agents.js#L26

RunaStaph (Wed, 25 Dec 2019 18:34:22 GMT):
The code: ```javascript ```

RunaStaph (Wed, 25 Dec 2019 18:34:22 GMT):
The code: ```javascript const fetch = ({ publicKey }) => db.fetch(publicKey, publicKey === authedKey) ```

RunaStaph (Wed, 25 Dec 2019 18:36:39 GMT):
`function is missing the `authedKey` parameter or definition somewhere

RunaStaph (Wed, 25 Dec 2019 18:36:39 GMT):
function is missing the `authedKey` parameter or definition somewhere

RunaStaph (Wed, 25 Dec 2019 18:40:26 GMT):
That one is simple. My ask for now is that someone confirm that they have successful built the current grid / grid-contrib code and the demos run smoothly

RunaStaph (Wed, 25 Dec 2019 18:41:10 GMT):
Thanks all and tty tomorrow after the Christmas break

LedgerXYZ (Tue, 31 Dec 2019 16:09:29 GMT):
Has joined the channel.

adeebahmed (Tue, 07 Jan 2020 19:34:16 GMT):
Was able to get back to your comments @desktophero https://github.com/hyperledger/grid-rfcs/pull/14 Pending review from @jsmitchell and @amundson

adeebahmed (Tue, 07 Jan 2020 19:34:16 GMT):
Was able to get back to your comments @desktophero https://github.com/hyperledger/grid-rfcs/pull/14#issuecomment-571734240 Pending review from @jsmitchell and @amundson

amundson (Tue, 07 Jan 2020 20:29:23 GMT):
LGTM

amundson (Tue, 07 Jan 2020 20:32:06 GMT):
@adeebahmed reminder, after you get the final approval, don't merge it right away - it moves to FCP and we vote again in a week. that final vote should go quick unless there is something new that comes to light. then we merge after that vote.

trevormcdonald (Wed, 08 Jan 2020 14:53:49 GMT):
I'm having trouble submitting any transactions and was wondering if anyone was noticing similar behavior. After spinning up Grid and execing into the `grid-cli` service, this is the behavior I'm seeing: ``` root@091115dce6e3:/# grid keygen root@091115dce6e3:/# grid --url http://gridd:8080 -vv organization create 314156 target "target hq" 2020-01-07 20:54:49,968 DEBUG [hyper::client::connect::dns] resolving host="gridd" 2020-01-07 20:54:49,970 DEBUG [hyper::client::connect::http] connecting to 172.26.0.5:8080 2020-01-07 20:54:49,970 DEBUG [tokio_reactor] adding I/O source: 0 2020-01-07 20:54:49,970 DEBUG [tokio_reactor::registration] scheduling Write for: 0 2020-01-07 20:54:49,970 DEBUG [hyper::client::connect::http] connected to Some(V4(172.26.0.5:8080)) 2020-01-07 20:54:49,971 DEBUG [tokio_reactor::registration] scheduling Read for: 0 2020-01-07 20:54:49,971 DEBUG [tokio_reactor::registration] scheduling Read for: 0 2020-01-07 20:54:49,971 DEBUG [hyper::proto::h1::io] flushed 130 bytes 2020-01-07 20:54:49,971 DEBUG [hyper::proto::h1::io] flushed 1280 bytes 2020-01-07 20:54:49,974 DEBUG [hyper::proto::h1::io] read 154 bytes 2020-01-07 20:54:49,975 DEBUG [hyper::proto::h1::io] parsed 3 headers 2020-01-07 20:54:49,975 DEBUG [hyper::proto::h1::conn] incoming body is content-length (18 bytes) 2020-01-07 20:54:49,975 DEBUG [hyper::proto::h1::conn] incoming body completed 2020-01-07 20:54:49,975 DEBUG [tokio_reactor::registration] scheduling Read for: 0 2020-01-07 20:54:49,975 DEBUG [tokio_reactor::registration] scheduling Read for: 0 2020-01-07 20:54:49,975 DEBUG [tokio_reactor::registration] scheduling Read for: 0 2020-01-07 20:54:49,976 DEBUG [hyper::client::pool] pooling idle connection for "http://gridd:8080" 2020-01-07 20:54:49,976 DEBUG [reqwest::async_impl::response] Response: '500 Internal Server Error' for http://gridd:8080/batches 2020-01-07 20:54:49,976 DEBUG [tokio_reactor::registration] scheduling Read for: 0 2020-01-07 20:54:49,978 DEBUG [tokio_reactor::registration] scheduling Read for: 0 2020-01-07 20:54:49,979 DEBUG [tokio_reactor] dropping I/O source: 0 2020-01-07 20:54:49,981 ERROR [grid] Reqwest Error: expected value at line 1 column 1 ```

RobinBanks (Wed, 08 Jan 2020 15:04:06 GMT):
Taking a look

RobinBanks (Wed, 08 Jan 2020 16:24:53 GMT):
My bad this should fix the issue you're having @trevormcdonald

RobinBanks (Wed, 08 Jan 2020 16:24:55 GMT):
https://github.com/hyperledger/grid/pull/150

adeebahmed (Mon, 13 Jan 2020 20:06:34 GMT):
```https://github.com/hyperledger/grid-rfcs/pull/14#issuecomment-573845963 ```

adeebahmed (Mon, 13 Jan 2020 20:06:34 GMT):
``` Per the unanimous approval of the Core and GS1 Subteams, this RFC has entered final comment period (FCP). Please get in your final round of comments within the next 7 days. Also please resolve any open conversations, or request me to resolve them for you. Final comment period will end on Tuesday, January 21st 2020, by EOD. ``` https://github.com/hyperledger/grid-rfcs/pull/14#issuecomment-573845963

saanvijay (Tue, 14 Jan 2020 09:45:21 GMT):
Has joined the channel.

Silona (Tue, 14 Jan 2020 16:49:58 GMT):
Help Us Help you! Attend the Developer Relationship Meeting with Myself and our Marketing Dept. tomorrow at 9:00am Pacific Time. For the agenda and Dial in info https://wiki.hyperledger.org/display/Marketing/2020-01-15+Meeting+notes

Silona (Tue, 14 Jan 2020 17:01:21 GMT):
Calling all Projects! We will have a special Kiosk setup at Hyperledger Global Forum for Projects. We are asking that all projects sign up to do 10 minute presentations. https://wiki.hyperledger.org/display/HGF/Projects+Kiosk We will close this page on Feb 28 for printing reasons.

Silona (Tue, 14 Jan 2020 17:04:40 GMT):
Calling all Projects, SIG, and WG!!! We will have a Video recording Studio setup at HGF (Hyperledger Global Forum). We are asking that all projects and groups help us create a 5 minute video about your group so that we can promote it afterward. Sign up Here! https://wiki.hyperledger.org/display/HGF/Video+Recording+Schedule

trevormcdonald (Wed, 15 Jan 2020 17:51:16 GMT):
Looking for some reviews on https://github.com/hyperledger/grid/pull/122

amundson (Thu, 16 Jan 2020 19:10:21 GMT):
@agunde ^ needs you re-review

amundson (Thu, 16 Jan 2020 19:10:21 GMT):
@agunde ^ needs your re-review

arsulegai (Sat, 25 Jan 2020 06:59:31 GMT):
Helio team, we need help. Is multi-party circuit supported in the underlying Splinter framework? If so how would the circuit proposal look like if we're using the experimental CLI build?

amundson (Mon, 27 Jan 2020 15:23:29 GMT):
@arsulegai you mean 3 node circuit, for example? if so, yes, but there is a known bug in the latest release that @agunde is working on related to it, should be fixed soon

arsulegai (Mon, 27 Jan 2020 15:31:48 GMT):
Thanks @amundson

adeebahmed (Mon, 27 Jan 2020 16:18:42 GMT):
FCP on the grid catalog RFC has come to an end. Final comments have been addressed and feedback has been incorporated. I've opened final vote: https://github.com/hyperledger/grid-rfcs/pull/14#issuecomment-578825790

amundson (Mon, 27 Jan 2020 16:31:43 GMT):
Here are the changes since FCP started:

amundson (Mon, 27 Jan 2020 16:31:46 GMT):
https://github.com/hyperledger/grid-rfcs/pull/14/commits/d8b1960f2087c97a9f57d829b2ad494bfc0f7043

amundson (Mon, 27 Jan 2020 16:31:59 GMT):
https://github.com/hyperledger/grid-rfcs/pull/14/commits/55d322965cab5c39e930e7ef1828492856090f01

amundson (Mon, 27 Jan 2020 16:32:12 GMT):
https://github.com/hyperledger/grid-rfcs/pull/14/commits/9d61daa95cf1f1bc31e3593292cbe510e999b479

amundson (Mon, 27 Jan 2020 16:34:51 GMT):
@dplumb for your alternatives comment, is that a suggestion that we move that direction in the future, or a statement that it was considered and we agreed we were not going to do it? If it i still up for consideration, that should be made clear in the text, maybe in the unresolved questions section

dplumb (Mon, 27 Jan 2020 16:54:46 GMT):
It is an alternative that I am in favor of moving forward with. However, I'm not requesting that it is changed in the RFC, since I am fairly sure that the implementation described in the RFC is technically correct.

dplumb (Mon, 27 Jan 2020 16:55:54 GMT):
No one else took a position on that issue during FCP, so I am fine with it remaining in the alternative and it can be referred back to if during implementation it seems like it could be a better alternative

Silona (Mon, 27 Jan 2020 22:26:33 GMT):
The Linux Foundation’s CommunityBridge engineers are working on a tool to measure the health of critical open source projects and one of the key areas identified is QA Testing. They request that our communities provide honest and detailed information on testing tools and methodologies you use in your projects for us to come up with a detailed analysis, which they will share with all respondents and projects. https://www.surveymonkey.com/r/9H5G2GV. It’s only 5 questions long.

Koja78 (Wed, 29 Jan 2020 12:32:20 GMT):
Has joined the channel.

lucianosilva44 (Fri, 31 Jan 2020 01:40:07 GMT):
Has joined the channel.

lucianosilva44 (Fri, 31 Jan 2020 01:40:09 GMT):
Hello! Is there any tutorial of how to use Hyperledger Grid? I do not find anything in the documentations at the website.

Patrick-Erichsen (Fri, 31 Jan 2020 16:58:15 GMT):
The Track and Trace Transaction Family Specification (https://grid.hyperledger.org/docs/grid/nightly/master/transaction_family_specifications/grid_track_and_trace_family_specification.html) would be a good place to see an example.

lucianosilva44 (Sat, 01 Feb 2020 03:16:03 GMT):
Thanks, Patrick!!

lucianosilva44 (Sat, 01 Feb 2020 03:26:51 GMT):
Other doubt here: trying to build Grid here, but get an error

lucianosilva44 (Sat, 01 Feb 2020 03:27:37 GMT):
error: failed to run custom build command for `grid-sdk v0.1.0

Patrick-Erichsen (Sat, 01 Feb 2020 04:19:31 GMT):
This was the instructions you were following? https://github.com/hyperledger/grid#building-grid What was the command that you ran that gave you that error?

lucianosilva44 (Mon, 03 Feb 2020 13:57:36 GMT):
Yes, those were the instructions. I ran cargo build and then the error appeared.

lucianosilva44 (Mon, 03 Feb 2020 14:05:57 GMT):
I had success when building in docker containers. However, don't know how to make them work (which sequence do I have to launch the containers, etc?)

Patrick-Erichsen (Mon, 03 Feb 2020 14:48:18 GMT):
Have you tried `docker compose up` ?

lucianosilva44 (Mon, 03 Feb 2020 15:26:39 GMT):
Uh, is there a docker-compose.yaml file in the repo?

Patrick-Erichsen (Mon, 03 Feb 2020 15:29:14 GMT):
https://github.com/hyperledger/grid/blob/master/docker-compose.yaml

Patrick-Erichsen (Mon, 03 Feb 2020 15:30:11 GMT):
There is logic in some of the entrypoints that should bring the network up properly, e.g. https://github.com/hyperledger/grid/blob/master/docker-compose.yaml#L186-L198

lucianosilva44 (Mon, 03 Feb 2020 17:23:23 GMT):
Understood

lucianosilva44 (Mon, 03 Feb 2020 17:37:36 GMT):
@Patrick-Erichsen , I executed the containers here. However, it only makes a pre-programmed small demonstration of the contracts execution?

lucianosilva44 (Mon, 03 Feb 2020 17:38:01 GMT):
Isn't there anything that can be made step-by-step, for better understanding?

Patrick-Erichsen (Tue, 04 Feb 2020 15:06:51 GMT):
At the current stage there isn't really much in the sense of tutorials. A lot of the concepts/work on Grid is still evolving, but there are some project examples in https://github.com/hyperledger/grid-contrib

Patrick-Erichsen (Tue, 04 Feb 2020 15:06:51 GMT):
At the current stage there isn't really much in the sense of tutorials. A lot of the concepts/work on Grid is still evolving, but there are some good project examples in https://github.com/hyperledger/grid-contrib

yarrkov (Thu, 06 Feb 2020 14:17:14 GMT):
Has joined the channel.

yarrkov (Fri, 07 Feb 2020 10:06:02 GMT):
I use docker-compose.yaml from the repo. I use `grid` in grid-cli to add a test organization. But gridd:8080/organization returns an empty array. It's in the `organization` psql table, but filtered out like . service_id in the db is not null but an empty string. This seems to fix the issue:

yarrkov (Fri, 07 Feb 2020 10:07:41 GMT):
Does that seem right? Should I submit a pull request or something?

pschwarz (Fri, 07 Feb 2020 15:49:28 GMT):
@yarrkov Yeah, that seems right. A PR would be welcome

adeebahmed (Fri, 07 Feb 2020 16:00:19 GMT):
Opened a pr to rename and move catalog.md to the correct location: https://github.com/hyperledger/grid-rfcs/pull/19

Silona (Thu, 13 Feb 2020 18:24:18 GMT):
Howdy Contributors and Maintainers! Are you wondering about tapping into Developer marketing for your group or project? Do you have a blog post idea? An awesome announcement? Please attend our Contributor/marketing meeting! https://wiki.hyperledger.org/display/Marketing/2020-02-19+Meeting+notes

Silona (Mon, 17 Feb 2020 22:18:18 GMT):
Are you wondering about tapping into Developer marketing for your group or project? Do you have a blog post idea? An awesome announcement? Please attend TOMORROW! https://wiki.hyperledger.org/display/Marketing/2020-02-19+Meeting+notes

yeiyei (Tue, 03 Mar 2020 15:28:00 GMT):
Has joined the channel.

tomislav (Mon, 09 Mar 2020 12:40:57 GMT):
Has left the channel.

arsulegai (Wed, 01 Apr 2020 11:16:07 GMT):
Can we move pike contract, helper utility code that can be imported into the smart contract for permission checks to #sawtooth-sabre ? There's potential for it to be used as a common permissioning mechanism in sabre.

georges (Tue, 07 Apr 2020 14:41:06 GMT):
Has joined the channel.

georges (Tue, 07 Apr 2020 14:41:07 GMT):
hey

georges (Tue, 07 Apr 2020 14:41:11 GMT):
why are you using sawtooth sawbre

georges (Tue, 07 Apr 2020 14:41:11 GMT):
why are you using sawtooth sabre

georges (Tue, 07 Apr 2020 14:41:26 GMT):
and grid instead of sawtooth perharps

arsulegai (Thu, 09 Apr 2020 17:37:49 GMT):
@georges Is this question for me? or are you asking in general why do we need sawtooth-sabre?

georges (Thu, 09 Apr 2020 19:10:55 GMT):
do you

georges (Thu, 09 Apr 2020 19:11:03 GMT):
and in general if someone would want to reply

arsulegai (Fri, 10 Apr 2020 18:23:00 GMT):
sawtooth-sabre is a transaction processor that allows you to run WASM contracts on HL Sawtooth

PedroMangini (Mon, 13 Apr 2020 13:54:18 GMT):
Has joined the channel.

ascii1011 (Fri, 24 Apr 2020 07:57:58 GMT):
Has joined the channel.

desktophero (Fri, 24 Apr 2020 16:29:57 GMT):
Are Grid Docker images pre-built and published anywhere? I didn't see anything in Docker Hub and the Jenkins setup doesn't appear to publish. Perhaps some other location?

dineshthemacho1 (Mon, 27 Apr 2020 06:14:00 GMT):
Has joined the channel.

kenty (Wed, 20 May 2020 08:13:48 GMT):
Has joined the channel.

kenty (Wed, 20 May 2020 08:13:49 GMT):
hi everyone! hyperledger study circle is looking for example code and tutorials for learning Grid: http://meetu.ps/e/HX9KH/f2rrM/d

AlexanderZhovnuvaty (Fri, 22 May 2020 08:22:46 GMT):
Has joined the channel.

rajesh_kumar_p (Thu, 04 Jun 2020 14:31:09 GMT):
Has joined the channel.

hidura (Fri, 05 Jun 2020 16:14:23 GMT):
Has joined the channel.

amundson (Fri, 05 Jun 2020 21:47:47 GMT):
Grid now supports the new Splinter 0.4

shadab14meb346 (Fri, 26 Jun 2020 08:55:56 GMT):
Has joined the channel.

shadab14meb346 (Fri, 26 Jun 2020 08:55:57 GMT):
does grid support contracts in NodeJS currently?

amundson (Fri, 26 Jun 2020 14:24:41 GMT):
smart contracts in grid run inside Sawtooth Sabre; the closest thing would be Sabre's AssemblyScript SDK

shadab14meb346 (Wed, 01 Jul 2020 13:53:28 GMT):
I have few questions. It will be very helpful if I can get these answers or some resources to read from. 1. Why sawtooth was used in place of fabric with grid? 2. Does the use of sawtooth provides some more features or value over fabric when used in supply chain solutions. If yes what are those? 3. Is NodeJS SDK support is planned for future? 4. Why RUST was preferred over other more famous languages like GO or Node which is supported in fabric.?

shadab14meb346 (Wed, 01 Jul 2020 13:53:28 GMT):
I have a few questions. It will be very helpful if I can get these answers or some resources to read from. 1. Why sawtooth was used in place of fabric with the GRID? 2. Does the use of sawtooth provide some more features or value over the fabric when used in supply chain solutions? If yes what are those? 3. Is NodeJS SDK support is planned for the future? 4. Why RUST was preferred over other more famous languages like GO or Node which is supported in fabric?

amundson (Wed, 01 Jul 2020 15:04:00 GMT):
@shadab14meb346 1) Grid supports both Sawtooth and Splinter (https://www.splinter.dev/), both of which are committed to running smart contracts with Hyperledger Transact, which is how we run WASM contracts in Sabre. These platforms are distributed, which make them suitable for the types of patterns we need in supply chain. Where they are deficient, we are actively changing them to be more suitable for Grid. 2) Architecture primarily. I don't want to get into all Fabric's disadvantages here, but lack of support for Transact and its centralized architecture; 3) Not NodeJS specifically, but Javascript smart contracts are definitely something we are interested in adding (thus why we explored AssemblyScript), either within Sabre or as another smart contract engine that runs in Transact. We will keep with on-chain smart contracts, because any other model has administration issues. 4) From a platform perspective, we are using Rust because its the perfect programming language for what we are doing. Besides the language being great, the ecosystem and libraries are excellent. Platforms written in Go are kind of legacy, like COBOL. And Node is Javascript, which is maybe the worst of everything for systems programming problems. However, if you mean for smart contracts specifically -- we are really focused on WASM, not Rust. Rust has the best support for compiling into WASM with relatively small resulting binaries. Adding Go smart contract SDK to Sabre is certainly possible, but the resulting WASM binaries would be relatively large due to Go's runtime. Javascript is actually very interesting for smart contracts though (as long as it is on-chain).

amundson (Wed, 01 Jul 2020 15:07:26 GMT):
@shadab14meb346 this might also be of interest - https://www.hyperledger.org/blog/2019/02/08/assembling-the-future-of-smart-contracts-with-sawtooth-sabre

nivant9091 (Sun, 12 Jul 2020 07:54:52 GMT):
Has joined the channel.

z3100 (Fri, 17 Jul 2020 03:50:26 GMT):
Has joined the channel.

prem-baranwal (Mon, 20 Jul 2020 07:25:00 GMT):
Has joined the channel.

prem-baranwal (Mon, 20 Jul 2020 07:25:00 GMT):
Hi, Is anyone recently been able to setup the grid/grid-contrib and run the asset-client successfully? Does it require any changes in the docker-compose.yaml? I tried to run the asset-client and run into the following error- tnt-asset-client | 219.91.250.236 - - [20/Jul/2020:07:05:10 +0000] "GET /dist/bundle.js HTTP/1.1" 200 16619083 tnt-server | Received POST request for /users from ::ffff:172.24.0.2 tnt-asset-client | 219.91.250.236 - - [20/Jul/2020:07:05:52 +0000] "POST /api/users HTTP/1.1" 200 478 tnt-asset-client | [Mon Jul 20 07:06:52.666939 2020] [proxy_http:error] [pid 7:tid 140667812566784] (70007)The timeout specified has expired: [client 219.91.250.236:29677] AH01102: error reading status line from remote server gridd:8080, referer: http://34.239.164.246:8021/ tnt-asset-client | [Mon Jul 20 07:06:52.667004 2020] [proxy:error] [pid 7:tid 140667812566784] [client 219.91.250.236:29677] AH00898: Error reading from remote server returned by /grid/batches, referer: http://34.239.164.246:8021/ tnt-asset-client | 219.91.250.236 - - [20/Jul/2020:07:05:52 +0000] "POST /grid/batches HTTP/1.1" 502 341 sawtooth-devmode-engine-rust-default | thread 'main' panicked at 'Failed to summarize block: ReceiveError("TimeoutError")', src/libcore/result.rs:997:5 sawtooth-devmode-engine-rust-default | note: Run with `RUST_BACKTRACE=1` environment variable to display a backtrace. sawtooth-devmode-engine-rust-default exited with code 101 gridd | ERROR [actix_http::response] Internal Server Error: RequestHandlerError("TimeoutError") FYI, at this point there were already 12 blocks created. Later, i tried couple of things like changing the hyperledger/sawtooth images to chime (1.2.5) and adding dependency of sabre-tp to *-contract-builder services. But that led to some validator connection error "Failed to receive events; aborting: connection received invalid message: Received unexpected message: PING_REQUEST".

prem-baranwal (Mon, 20 Jul 2020 07:25:00 GMT):
Hi, Is anyone recently been able to setup the grid/grid-contrib and run the asset-client successfully? Does it require any changes in the docker-compose.yaml? I tried to run the asset-client and run into the following error- tnt-asset-client | 219.91.250.236 - - [20/Jul/2020:07:05:10 +0000] "GET /dist/bundle.js HTTP/1.1" 200 16619083 tnt-server | Received POST request for /users from ::ffff:172.24.0.2 tnt-asset-client | 219.91.250.236 - - [20/Jul/2020:07:05:52 +0000] "POST /api/users HTTP/1.1" 200 478 tnt-asset-client | [Mon Jul 20 07:06:52.666939 2020] [proxy_http:error] [pid 7:tid 140667812566784] (70007)The timeout specified has expired: [client 219.91.250.236:29677] AH01102: error reading status line from remote server gridd:8080, referer: http://:8021/ tnt-asset-client | [Mon Jul 20 07:06:52.667004 2020] [proxy:error] [pid 7:tid 140667812566784] [client 219.91.250.236:29677] AH00898: Error reading from remote server returned by /grid/batches, referer: http://:8021/ tnt-asset-client | 219.91.250.236 - - [20/Jul/2020:07:05:52 +0000] "POST /grid/batches HTTP/1.1" 502 341 sawtooth-devmode-engine-rust-default | thread 'main' panicked at 'Failed to summarize block: ReceiveError("TimeoutError")', src/libcore/result.rs:997:5 sawtooth-devmode-engine-rust-default | note: Run with `RUST_BACKTRACE=1` environment variable to display a backtrace. sawtooth-devmode-engine-rust-default exited with code 101 gridd | ERROR [actix_http::response] Internal Server Error: RequestHandlerError("TimeoutError") FYI, at this point there were already 12 blocks created. Later, i tried couple of things like changing the hyperledger/sawtooth images to chime (1.2.5) and adding dependency of sabre-tp to *-contract-builder services. But that led to some validator connection error "Failed to receive events; aborting: connection received invalid message: Received unexpected message: PING_REQUEST".

pschwarz (Mon, 20 Jul 2020 16:47:00 GMT):
Did you update both the sawtooth validator image to 1.2 as well as the devmode consensus image?

prem-baranwal (Tue, 21 Jul 2020 12:00:05 GMT):
yes. in fact i did it for settings-tp and shell images as well.

pschwarz (Tue, 21 Jul 2020 13:36:53 GMT):
Based on your followup email, the Sawtooth REST API needs an update, as well.

pschwarz (Tue, 21 Jul 2020 14:02:52 GMT):
There are a couple of minor updates that are needed to the grid daemon to work with sawtooth 1.2. I will (hopefully) get a PR up shortly.

prem-baranwal (Thu, 23 Jul 2020 05:40:42 GMT):
That would be really helpful. I looked at the code and it looks like the PING_REQUEST from validator need to be handled. Instead of throwing error and exiting, it should respond with PING_RESPONSE. Let me know if there is more to it.

pschwarz (Thu, 23 Jul 2020 14:10:09 GMT):
Fixed in this PR: https://github.com/hyperledger/grid/pull/259

prem-baranwal (Thu, 23 Jul 2020 15:31:24 GMT):
Thanks a lot Peter.

prem-baranwal (Thu, 23 Jul 2020 15:31:45 GMT):
Now i am getting "sawtooth-devmode-engine-rust-default | thread 'main' panicked at 'Failed to summarize block: ReceiveError("TimeoutError")', src/engine.rs:87:23 sawtooth-devmode-engine-rust-default | note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace sawtooth-devmode-engine-rust-default exited with code 101 "

pschwarz (Thu, 23 Jul 2020 15:32:17 GMT):
I'm trying to track that issue down now, too

prem-baranwal (Thu, 23 Jul 2020 15:33:12 GMT):
i am using tag 1.2 for validator/devmode-engine/settings-tp/rest-api/sawtooth-shell and tag 0.5 for sawtooth-sabre-tp.

prem-baranwal (Thu, 23 Jul 2020 15:42:14 GMT):
it seems to be failing in ZmqService::summarize_block

prem-baranwal (Mon, 27 Jul 2020 11:50:20 GMT):
Hi Peter, is there any update on the consensus issue arising after the issue fix 259?

prem-baranwal (Mon, 27 Jul 2020 11:50:20 GMT):
Hi @pschwarz , is there any update on the consensus issue arising after the issue fix 259?

cecchi (Fri, 31 Jul 2020 17:00:26 GMT):
New RFC for a Grid Location based on GS1/GLN standards has been published for comment. https://github.com/hyperledger/grid-rfcs/pull/20

amundson (Fri, 31 Jul 2020 17:59:11 GMT):
I reviewed it -- very straight-forward given how nicely it matches up with product.

amundson (Fri, 31 Jul 2020 17:59:56 GMT):
very much appreciate that it was submitted line-wrapped :)

ajeenckya (Sat, 01 Aug 2020 14:29:40 GMT):
Has joined the channel.

ajeenckya (Sat, 01 Aug 2020 16:13:49 GMT):
@prem-baranwal is it working for you now? Even after all the mentioned changes, it is not working for me and getting timeout error.

prem-baranwal (Mon, 03 Aug 2020 07:03:50 GMT):
I was able to finally make it work. The issue was with the versioning of transaction families.

prem-baranwal (Mon, 03 Aug 2020 07:05:21 GMT):
AssetClient/FishClient mention pike version as 0.4 while creating transactions where as the latest sabre-tp is processing 0.5 only.

prem-baranwal (Mon, 03 Aug 2020 07:05:48 GMT):
Once i updated the frontend to 0.5 it worked.

pschwarz (Mon, 03 Aug 2020 14:22:32 GMT):
Can you submit a PR for that front-end fix?

ajeenckya (Tue, 04 Aug 2020 04:37:15 GMT):
Okay.

ajeenckya (Tue, 04 Aug 2020 05:19:11 GMT):
@prem-baranwal it works. I did multiple changes for versioning across grid and grid-contrib repo to make it work.

calvin.heo (Mon, 10 Aug 2020 06:08:36 GMT):
Has joined the channel.

amundson (Tue, 11 Aug 2020 15:37:09 GMT):
I'd like to see Grid's issue management move to git issues on the grid repo. Thoughts?

amundson (Tue, 11 Aug 2020 17:30:28 GMT):
looks like besu, avalon, others already use github issues

amundson (Tue, 11 Aug 2020 17:32:06 GMT):
enabled - https://github.com/hyperledger/grid/issues - if there are any concerns, we can still discuss

RyanBanks (Tue, 11 Aug 2020 17:38:24 GMT):
Has joined the channel.

RyanBanks (Tue, 11 Aug 2020 17:38:24 GMT):
I will be adding some stories shortly for the location RFC implementation

hidura (Tue, 11 Aug 2020 20:52:18 GMT):
I want to participate in the grid development, one of my projects is focus on that area and grid basically could be the base

hidura (Tue, 11 Aug 2020 20:52:26 GMT):
How can I join?

hidura (Tue, 11 Aug 2020 23:48:47 GMT):
I've read all the documentation of grid, is amazing what you've done! I want to know, do you recommend me use grid to make traceability for products on a production system?

amundson (Wed, 12 Aug 2020 18:45:36 GMT):
@hidura welcome! we are going to do a community meeting soon, just working on a date for that. we will post that information here.

amundson (Wed, 12 Aug 2020 18:48:27 GMT):
the "Product" capability in grid is for sharing GS1-based product definitions between companies. There is a location RFC that is being worked on (https://github.com/hyperledger/grid-rfcs/blob/69e84bdc4bee7a75455557221b207055b0c25e81/text/0000-location.md) that will provide very similar capability for sharing GS1-based locations between companies.

amundson (Wed, 12 Aug 2020 18:54:16 GMT):
the track-and-trace functionality built into Grid pre-dates our focus on GS1 standards, so one of the TODO items there is to modify it to integrate nicely with both Product and Location. some of the track-and-trace code is in grid proper, and some of it is in grid-contrib. the pieces in grid-contrib are there because they need to be update and/or rewritten in order to make it in the grid codebase. for example, we need to update the state-delta-export feature to a Rust implementation so it can run inside gridd. That is open to anyone that wants to work on it. Another TODO there is to take a careful look at GS1 standards and see how we should modify track-and-trace to be more in-line with how it works in those standards.

JessieZamzow (Wed, 12 Aug 2020 19:03:12 GMT):
Has joined the channel.

amundson (Wed, 12 Aug 2020 19:06:41 GMT):
hi @JessieZamzow

amundson (Wed, 12 Aug 2020 19:08:24 GMT):
do we have a date we would like to set as a goal for calling FCP (final comment period) for the location RFC?

JessieZamzow (Wed, 12 Aug 2020 19:13:28 GMT):
Would it be fair to set a goal of Friday (8/14) to begin the final calling period? How long does that calling period last? My thought process is I could push a commit with updates tonight, folks can resolve comments tomorrow (and into FCP), and then allow final comments off the cleaner version. Thoughts?

hidura (Wed, 12 Aug 2020 21:50:45 GMT):
Thanks @amundson I am looking to use grid on my market due to the grid adaptation to that area, then only thing is I can't find a way to start, because there's some areas that I don't understand

hidura (Wed, 12 Aug 2020 21:52:23 GMT):
Like how I can interact to create agents, products, schemas on grid is via CLI or is there any library?

amundson (Thu, 13 Aug 2020 13:34:45 GMT):
@JessieZamzow FCP lasts a week. We will want votes from two subteams, the core subteam and the gs1 subteam. Prior to the vote, we need both subteam members to provide their input. The subteams members are here: https://github.com/hyperledger/grid-rfcs/tree/master/subteams

amundson (Thu, 13 Aug 2020 13:39:01 GMT):
core subteam - @adeebahmed @agunde @dplumb @jsmitchell @desktophero @pschwarz and gs1 subteam @adeebahmed @cecchi @Gena @jsmitchell @mattp @MelanieNuce - please finish your review of the location RFC - https://github.com/hyperledger/grid-rfcs/pull/20

amundson (Thu, 13 Aug 2020 13:39:50 GMT):
others that are not on subteams - please also get your reviews and comments in on the RFC

MelanieNuce (Thu, 13 Aug 2020 16:28:52 GMT):
@mattp based on your question on the Location RFC, API access to GS1 US Data Hub is $6500/year in addition to the $500/year subscription to Company data. Location and Product data are each an additional $500/yr, but the API subscription is good across all three levels.

MelanieNuce (Thu, 13 Aug 2020 16:30:53 GMT):
@amundson and @JessieZamzow I think the GS1 contributions are completed, unless there are open questions from others that require more changes to the RFC. If you can tag us or let me know what still requires GS1 support, I will make sure we complete those items. Thanks!

mattp (Thu, 13 Aug 2020 17:17:59 GMT):
Thanks @MelanieNuce, this is helpful. @cecchi Do you think the design is in line with each developing party requiring us to get access here? Said differently, 1) Is API access to the GS1 US data hub required? 2) Assuming so, is each developing and contributing party required to get access? 3) If access to the GS1 US data hub is not required, how else do we intend to validate company data as suggested in the RFC?

amundson (Thu, 13 Aug 2020 19:32:54 GMT):
@mattp The RFC does not cover integration with any existing system. Is your question more about whether GLNs are the right identifiers to use for locations? If so, there is identifier space "reserved" in the RFC for additional identification schemes (this is what LocationNamespace is about). This is the identical approach we took with GS1 product support, where there is namespace reserved if GTIN is not the desired product identifier.

amundson (Thu, 13 Aug 2020 19:33:39 GMT):
@MelanieNuce thanks!

mattp (Thu, 13 Aug 2020 20:21:19 GMT):
Hi Shawn, thanks for your reply. My question is not about GLN being the right identifier to use for location. Given the broader use and standards already existing about them, I think it makes sense. My question is more about identity management and ensuring those inputting and asserting product data are correct. After reading James' response in the thread, it seemed to indicate linking a GS1 prefix to pike orgs with a transaction signed by the appropriate GS1 identity for this purpose, but maybe that serves a different purpose. My original question was this: Is the intent to validate the GLN input with GS1? Wondering if there is a need to validate the input is coming from the correct GS1 company prefix and those who are associated with it, from a GS1 perspective. I think stated differently, is how do we ensure bad actors are ruled out and not allowed to input false or misleading data if they simply use a valid GS1 company prefix and the check digit format is correct as part of the GLN?

mattp (Thu, 13 Aug 2020 20:25:10 GMT):
It seemed like the what was being suggested and natural way to do this would be to validate the GLN and related organizational identity via the GS1 US data hub API, but maybe thats not possible or desired here?

mattp (Thu, 13 Aug 2020 20:25:10 GMT):
It seemed like what was being suggested and natural way to do this would be to validate the GLN and related organizational identity via the GS1 US data hub API, but maybe thats not possible or desired here?

hidura (Fri, 14 Aug 2020 02:31:21 GMT):
Hello when I've try to start the grid-sawtooth-rest-api, always give me this mistake: `schema-contract-builder exited with code 0 tnt-contract-builder exited with code 0 product-contract-builder exited with code 0 `

hidura (Fri, 14 Aug 2020 02:32:58 GMT):
Hello when I've try to start the grid-sawtooth-rest-api, always give me this mistake: ``` schema-contract-builder exited with code 0 tnt-contract-builder exited with code 0 product-contract-builder exited with code 0 ```

agunde (Fri, 14 Aug 2020 14:10:08 GMT):
@hidura If you are using the grid docker-compose.yaml file to start all of grid, that is not an error. Those containers compile the smart contracts into wasm and then submit the required transactions to Sabre to make the smart contracts available. You should see a log that looks like `---------========= track and trace contract is loaded =========---------` and then the container exists.

hidura (Fri, 14 Aug 2020 14:11:28 GMT):
Ok, thanks, with this up I can start using the grid-cli?

hidura (Fri, 14 Aug 2020 14:11:48 GMT):
Because my main goal is to use the cli directly

agunde (Fri, 14 Aug 2020 14:15:21 GMT):
Yes, you should be able to

hidura (Fri, 14 Aug 2020 14:20:08 GMT):
Excellent! Thanks!

amundson (Fri, 14 Aug 2020 18:22:14 GMT):
I suggest we put together a Grid community call for Aug 21st at 10am US/Central. Will that work for most people?

hidura (Fri, 14 Aug 2020 18:48:20 GMT):
Agree

hidura (Fri, 14 Aug 2020 22:33:12 GMT):
I wish to add Python support to the gid-cli, I'll be starting doing it, because due the small span of time, is impossible to learn rust and add do all the system on grid.

amundson (Fri, 14 Aug 2020 22:53:51 GMT):
@hidura I assume you mean calling into a python interpreter from the Rust code. That isn't desirable as it would substantially raise the effort to maintain the code. we have a mixed python/rust codebase in Sawtooth and our #1 goal is to finish the python->rust transition and purge all the Python code. While most of us like both Rust and Python, there are some very big negatives to combining them.

amundson (Fri, 14 Aug 2020 22:54:40 GMT):
Python tools are welcome in grid-contrib though

hidura (Fri, 14 Aug 2020 22:55:14 GMT):
So, to interact with the grid-cli, what you recommend me?

amundson (Fri, 14 Aug 2020 22:57:07 GMT):
If you are adding a subcommand to the grid cli, it should be implemented in Rust.

hidura (Fri, 14 Aug 2020 22:58:02 GMT):
Ok, I'll not add any subcommand, my goal is to interact with the grid

hidura (Fri, 14 Aug 2020 22:58:32 GMT):
I'll be creating my code in Python, to interact via command line with grid-cli

amundson (Fri, 14 Aug 2020 22:58:50 GMT):
Can you elaborate?

hidura (Fri, 14 Aug 2020 23:01:58 GMT):
I'll have my python flask webapp that will interact with the grid-cli, as for example a organization register, I'll be calling from python the grid cli command on bash(this is how I understand the grid-cli works): ``` grid organization create

```

amundson (Fri, 14 Aug 2020 23:04:29 GMT):
ah, ok. you could make calls directly to the REST API as well if you wanted (this is what the grid CLI does)

hidura (Fri, 14 Aug 2020 23:06:08 GMT):
Ok, I can use that and send the same protos message as the cli does.

amundson (Fri, 14 Aug 2020 23:06:12 GMT):
is this a javascript app calling into python flask webapp?

hidura (Fri, 14 Aug 2020 23:07:04 GMT):
Will be a Python/Flask mainly because we'll be allowing companies to connect to the API

hidura (Fri, 14 Aug 2020 23:07:37 GMT):
As probably will be added some goverment organizations and regular people with an Javascript App that will be provide for the end user

amundson (Fri, 14 Aug 2020 23:07:57 GMT):
if you are doing any javascript, you may find this interesting - https://github.com/hyperledger/grid/tree/master/grid-ui

amundson (Fri, 14 Aug 2020 23:09:00 GMT):
what authentication/authorization are you planning to implement?

hidura (Fri, 14 Aug 2020 23:09:06 GMT):
I was trying to using it, but it always give me an error

hidura (Fri, 14 Aug 2020 23:10:35 GMT):
A descentralized market, that will allow the producers(mostly farmers), to have their information on a Blockchain and will give the goverment the capacity to give them the permissions that they need so they can export easly

amundson (Fri, 14 Aug 2020 23:10:38 GMT):
there are folks on this channel that will definitely help you get past that error

hidura (Fri, 14 Aug 2020 23:10:48 GMT):
Excellent!

hidura (Fri, 14 Aug 2020 23:11:46 GMT):
Also I am planning to use sawtooth for traceability of the drugs that are sold in my country

hidura (Fri, 14 Aug 2020 23:11:46 GMT):
Also I am planning to use grid for traceability of the drugs that are sold in my country

amundson (Fri, 14 Aug 2020 23:12:56 GMT):
were you starting up grid-ui with splinter or with sawtooth?

hidura (Fri, 14 Aug 2020 23:13:57 GMT):
grid directly without the ui

hidura (Fri, 14 Aug 2020 23:14:40 GMT):
I am reading the code of the grid-ui so I can understand

hidura (Fri, 14 Aug 2020 23:14:45 GMT):
better the work

amundson (Fri, 14 Aug 2020 23:15:22 GMT):
most developers are probably out for the weekend, but any errors post them here with steps to repeat (or what instructions you are going through) and we can work through it

hidura (Fri, 14 Aug 2020 23:16:13 GMT):
Thanks!

hidura (Fri, 14 Aug 2020 23:16:24 GMT):
I'll be doing that

hidura (Fri, 14 Aug 2020 23:18:38 GMT):
``` grid organization create 1 BMSUITE 365656565 Reqwest Error: http://localhost:8000/batches: error trying to connect: Cannot assign requested address (os error 99) ``` When I run the grid organization command tell me this.

RyanBanks (Mon, 17 Aug 2020 14:54:08 GMT):
@hidura it looks like the port is wrong. Assuming you're using the docker-compose in the grid repo the grid daemon is bound to port 8080.

RyanBanks (Mon, 17 Aug 2020 14:54:56 GMT):
``` grid --url http://location:8080 organization create 1 BMSUITE 365656565 ```

cecchi (Mon, 17 Aug 2020 15:39:35 GMT):
API access to the GS1 US Data Hub is not required by this RFC, no.

cecchi (Mon, 17 Aug 2020 15:43:31 GMT):
the owner of the GPC will submit their GLN data to Grid. There can be structural validation of the data, obvs, but there are no plans for additional "calls to GS1" to validate that it matches what is in DataHub or anything. This would be true for other GS1 data objects as well.

cecchi (Mon, 17 Aug 2020 15:43:50 GMT):
that could be done as part of SDE processing locally

amundson (Mon, 17 Aug 2020 15:46:41 GMT):
Ok, scheduled grid community meeting for Friday at 10am US/Central -- zoom link is https://us02web.zoom.us/j/86725415937

amundson (Mon, 17 Aug 2020 15:53:56 GMT):
Here is a working doc for the agenda - https://docs.google.com/document/d/1CQGW101MVGnOCuI2K-UkwgwMqSfVtxpec8wrE-HsgOY/edit#

mattp (Mon, 17 Aug 2020 16:00:30 GMT):
Ok, thanks for the follow up and clarification.

hidura (Mon, 17 Aug 2020 20:03:27 GMT):
I agree

hidura (Mon, 17 Aug 2020 20:04:58 GMT):
It was the name of the container that was impossible to be accessed, I put it a name and it was done.

itomb (Thu, 20 Aug 2020 13:15:21 GMT):
Has joined the channel.

hidura (Fri, 21 Aug 2020 04:22:00 GMT):
Hello, tomorrow I won't be able to stay with you in the conference if you can recorded so I can know what was talked I'll be glad of that

amundson (Fri, 21 Aug 2020 14:59:06 GMT):
Reminder, the zoom URL for the call is https://us02web.zoom.us/j/86725415937

amundson (Fri, 21 Aug 2020 14:59:35 GMT):
The agenda is at: https://docs.google.com/document/d/1CQGW101MVGnOCuI2K-UkwgwMqSfVtxpec8wrE-HsgOY/edit#

jcldnatv (Sat, 22 Aug 2020 17:24:24 GMT):
Has joined the channel.

amundson (Mon, 24 Aug 2020 17:51:41 GMT):
I've proposed the Grid Location RFC be merged -- subteams please vote to start final comment period -- https://github.com/hyperledger/grid-rfcs/pull/20

Nandhitharamalingam (Wed, 26 Aug 2020 11:07:15 GMT):
Has joined the channel.

Nandhitharamalingam (Wed, 26 Aug 2020 11:07:15 GMT):
How to perform track and trace ability in grid ,enabled ui but unable to initiate or record a product? can some one tell me how to perform ?

Nandhitharamalingam (Thu, 27 Aug 2020 07:49:06 GMT):
Unable to perform operations inside grid-cli ,docker exec -it grid-cli bash root@12d895802bb3:/# grid \ > organization create 314156 myorg '123 main street' \ > --metadata gs1_company_prefixes=314156 Reqwest Error: http://localhost:8000/batches: error trying to connect: Cannot assign requested address (os error 99). I can do the same operation inside splinter node. Please help me out

Nandhitharamalingam (Thu, 27 Aug 2020 12:01:43 GMT):
Hi ,so the previous error is resolved by applying this --url http://gridd:8080 to the command, Now , let me know why i cannot list the product that is created grid --url http://gridd:8080 product list

Nandhitharamalingam (Thu, 27 Aug 2020 12:02:27 GMT):
Hi ,so the previous error is resolved by applying this --url http://gridd:8080 to the command, Now , let me know why i cannot list the product that is created This command ->grid --url http://gridd:8080 product list gives me no result

Nandhitharamalingam (Thu, 27 Aug 2020 13:07:42 GMT):
How can i create schema inside grid cli? any example?

Radhai (Fri, 28 Aug 2020 04:35:16 GMT):
Has joined the channel.

Radhai (Fri, 28 Aug 2020 04:35:16 GMT):
Hi, I read that grid includes distributed ledger. By default, it uses sawtooth as distributed ledger when we run the grid repo. Is my understanding correct ?

Radhai (Fri, 28 Aug 2020 04:39:54 GMT):
I am trying to run the grid-contrib. When i try to create product, cannot able to see the product in the product list tab ?

amundson (Fri, 28 Aug 2020 14:16:57 GMT):
@Nandhitharamalingam can you provide the sequence you are going through up to that point? you mentioned track and trace but that's not related to product (they are separate smart contracts, etc.)

amundson (Fri, 28 Aug 2020 14:20:45 GMT):
@Radhai Grid works on top of either Sawtooth or Splinter. The docs are lacking for running it on top of Sawtooth, but yes, some of the docker compose files are setup that way (you can look at the compose file and determine this by whether its running a sawtooth validator). Here are some Splinter-specific instructions - https://grid.hyperledger.org/docs/0.1/grid_on_splinter.html. (Having a doc like this for Sawtooth would be great too, just hasn't been written in the same way yet.)

N8Shrader (Fri, 28 Aug 2020 19:37:28 GMT):
Has joined the channel.

Radhai (Sat, 29 Aug 2020 14:50:09 GMT):
Ok. Thanks.

Radhai (Sat, 29 Aug 2020 14:51:46 GMT):
How can i use Track and Trace smart contract ? I don't see record command in CLI ?

Radhai (Sat, 29 Aug 2020 14:52:14 GMT):
can i get any example for creating record and proposal ?

Radhai (Sat, 29 Aug 2020 14:52:59 GMT):
On Splinter Instructions also , there is no sample for record.

Radhai (Sat, 29 Aug 2020 14:55:16 GMT):
And how to change the owner for a product ? I tried to change the owner, but only the properties changing.

andremayer (Sun, 30 Aug 2020 15:13:21 GMT):
Has joined the channel.

Radhai (Tue, 01 Sep 2020 07:54:13 GMT):
Hi, I need to use Track & Trace contract. But I dont see any option to create record in grid cli. How can i use that ? any sample example example for creating record ?

Nandhitharamalingam (Fri, 04 Sep 2020 06:30:13 GMT):
Hi @amundson , Is there any option in the grid cli to create record ,proposal for grid's track and trace contract as per https://grid.hyperledger.org/docs/0.1/grid_track_and_trace_family_specification.html .

Nandhitharamalingam (Fri, 04 Sep 2020 06:30:13 GMT):
Hi @amundson , Is there any option in the grid cli to create record ,proposal using grid's track and trace contract as per https://grid.hyperledger.org/docs/0.1/grid_track_and_trace_family_specification.html .

dplumb (Fri, 04 Sep 2020 21:29:48 GMT):
Hmm looks like there isn't currently CLI functionality in Grid for Track and Trace. The implementation would be very similar to the existing CLI functionality. Theres an example of creating transactions for it in the track and trace examples in Grid Contrib repo. This is for Sawtooth however, I don't believe those apps have been updated to be used with Splinter yet.

dplumb (Fri, 04 Sep 2020 21:30:28 GMT):
https://github.com/hyperledger/grid-contrib/tree/master/track_and_trace/asset_client/src/services

amundson (Mon, 14 Sep 2020 17:01:12 GMT):
FCP has begun for the Grid Location RFC - https://github.com/hyperledger/grid-rfcs/pull/20 -- ends Sept 21

amundson (Tue, 15 Sep 2020 22:06:13 GMT):
The next Grid community meeting will be this Friday, September 18th at 10am US/Central via zoom - https://us02web.zoom.us/j/86725415937

amundson (Tue, 15 Sep 2020 22:06:54 GMT):
Tentative agenda is here - https://docs.google.com/document/d/1CQGW101MVGnOCuI2K-UkwgwMqSfVtxpec8wrE-HsgOY/edit#

arsulegai (Sun, 27 Sep 2020 12:06:33 GMT):
Hello Grid community from the Hyperledger India Chapter, we are calling for speakers to engage with the community in Asia Pacific, Europe and Africa. Please see our event details here https://www.linkedin.com/feed/update/urn:li:activity:6715897303481372672 Calling the tech enthusiasts, maintainers to be part of it.

amundson (Wed, 30 Sep 2020 21:09:05 GMT):
The Grid Location RFC has been merged! - https://github.com/hyperledger/grid-rfcs/blob/master/text/0020-location.md

MelanieNuce (Thu, 01 Oct 2020 16:52:55 GMT):
@amundson I am having trouble finding what requires my sign off/review on github. Will you please point me to the link where I can complete that? Thank you!

amundson (Thu, 01 Oct 2020 19:13:45 GMT):
@MelanieNuce your name was already checked off on the list, and its all merged now so nothing to do -- here is the PR for reference - https://github.com/hyperledger/grid-rfcs/pull/20

MelanieNuce (Thu, 01 Oct 2020 19:17:52 GMT):
@amundson Thank you! I had reviewed it and checked my name, so it was probably just email catch up happening. I appreciate the confirmation!

Freydal (Mon, 05 Oct 2020 13:47:56 GMT):
Has joined the channel.

hidura (Mon, 05 Oct 2020 19:11:29 GMT):
Is anyway to fast up the load of the gridd-cli

hidura (Mon, 05 Oct 2020 19:11:32 GMT):
?

Sandeepk40 (Wed, 07 Oct 2020 04:30:06 GMT):
Has joined the channel.

hidura (Thu, 08 Oct 2020 15:47:03 GMT):
Hello I am having an issue when I start the grid, this is an error that appear and is impossible to reach the rest-api ``` product-contract-builder | thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Error("missing field `link`", line: 7, column: 1)', src/libcore/result.rs:1188:5 product-contract-builder | note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace. tnt-contract-builder | thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Error("missing field `link`", line: 7, column: 1)', src/libcore/result.rs:1188:5 tnt-contract-builder | note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace. ```

aditya520 (Mon, 12 Oct 2020 18:47:28 GMT):
Has joined the channel.

granticusmaximus (Tue, 13 Oct 2020 02:00:22 GMT):
Has joined the channel.

amundson (Tue, 13 Oct 2020 15:02:04 GMT):
@newhall is now a grid maintainer

amundson (Wed, 14 Oct 2020 15:01:46 GMT):
Reminder, there is a Grid Community meeting this Friday at 10am US/Central. The zoom URL is https://us02web.zoom.us/j/86725415937?pwd=NHN2WFRieGtYbFV1SnNiT3pxUEdZZz09

amundson (Fri, 16 Oct 2020 15:02:59 GMT):
^ community meeting happening now

aditya520 (Fri, 16 Oct 2020 16:31:49 GMT):
How can I execute a transaction in xo constract from `scabbard` in the basic read the docs tutorial?

amundson (Fri, 16 Oct 2020 16:40:28 GMT):
which tutorial?

aditya520 (Fri, 16 Oct 2020 16:41:05 GMT):
https://grid.hyperledger.org/docs/0.1/uploading_smart_contracts.html

aditya520 (Fri, 16 Oct 2020 16:41:27 GMT):
After completing this, I want to execute a transaction, how can I do that?

aditya520 (Fri, 16 Oct 2020 16:41:58 GMT):
`scabbard exec --contract sawtooth_xo:1.0 --inputs 5b7349 --outputs 5b7349 --payload "xo create" --service-id $CIRCUIT_ID::gsBB --key 036c875f611922d94281b0132203ef38d376b5ac3ba14394a995f69d803c3f3562` This is not working!

amundson (Fri, 16 Oct 2020 16:58:14 GMT):
you are on the right track but you have to generate a payload file (--payload takes a filename) -- https://www.splinter.dev/docs/0.4/references/cli/scabbard-exec.1.html

aditya520 (Fri, 16 Oct 2020 16:59:18 GMT):
And how do I do that?

ltseeley (Fri, 16 Oct 2020 17:18:12 GMT):
@aditya520 as @amundson mentioned, you'll need to write the payload to a file. This payload file will look different for each smart contract. For the `sawtooth_xo` smart contract, it's pretty simple. You can see the description of the different payload options here: https://sawtooth.hyperledger.org/docs/core/releases/latest/transaction_family_specifications/xo_transaction_family.html#transaction-payload

ltseeley (Fri, 16 Oct 2020 17:19:22 GMT):
So to create a new xo game called "my_game", you'd write the string `my_game,create` to a file, then use that file like `scabbard exec ... --payload /path/to/payload/file`

ltseeley (Fri, 16 Oct 2020 17:19:22 GMT):
So to create a new xo game called "my_game", you'd write the string `my_game,create,` to a file, then use that file like `scabbard exec ... --payload /path/to/payload/file`

hidura (Fri, 16 Oct 2020 17:31:34 GMT):
Hello when I try to create an organization give me an error like this ``` [2020-10-16 12:32:59.787 ERROR web_protocol] Error handling request grid-sawtooth-rest-api | Traceback (most recent call last): grid-sawtooth-rest-api | File "/usr/lib/python3/dist-packages/aiohttp/web_protocol.py", line 416, in start grid-sawtooth-rest-api | resp = yield from self._request_handler(request) grid-sawtooth-rest-api | File "/usr/lib/python3/dist-packages/aiohttp/web.py", line 323, in _handle grid-sawtooth-rest-api | resp = yield from handler(request) grid-sawtooth-rest-api | File "/usr/lib/python3/dist-packages/sawtooth_rest_api/route_handlers.py", line 139, in submit_batches grid-sawtooth-rest-api | if request.headers['Content-Type'] != 'application/octet-stream': grid-sawtooth-rest-api | File "multidict/_multidict.pyx", line 124, in multidict._multidict._Base.__getitem__ (multidict/_multidict.c:3486) grid-sawtooth-rest-api | File "multidict/_multidict.pyx", line 119, in multidict._multidict._Base._getone (multidict/_multidict.c:3421) grid-sawtooth-rest-api | KeyError: "Key not found: 'Content-Type'" grid-sawtooth-rest-api | [2020-10-16 12:32:59.787 INFO helpers] POST /batches HTTP/1.1: 500 status, 330 size, in 0.000762 s ``` I am checking the cli/src/organization.rs, but i would like to know if that's the file that handle the call

hidura (Fri, 16 Oct 2020 18:19:01 GMT):
I fixed the code of the Http, how can I contribute with that?

hidura (Fri, 16 Oct 2020 18:19:21 GMT):
There's a mistake that will trigger that error.

troyronda (Wed, 28 Oct 2020 17:44:46 GMT):
Has left the channel.

hidura (Sun, 01 Nov 2020 19:45:02 GMT):
In which state is the project?

hidura (Sun, 01 Nov 2020 19:45:02 GMT):
Hello, in which state is the project?

amundson (Mon, 02 Nov 2020 17:18:09 GMT):
@hidura yes, please submit a PR against the repository - https://grid.hyperledger.org/community/contributing.html

amundson (Mon, 02 Nov 2020 17:20:59 GMT):
many of us are using splinter a lot, but we are adding some grid-on-sawtooth docs too, so I'm curious if this would actually occur with that flow. that work is here - https://github.com/hyperledger/grid-docs/pull/158

hidura (Mon, 02 Nov 2020 19:29:33 GMT):
Hello @amundson I'd took the protos message and doing it with Python to adapt it to my company needs, probably I'll be porting all the code from rust to python due that I was unable to use splinter or the core.

amundson (Mon, 02 Nov 2020 20:50:24 GMT):
I'm not following

hidura (Mon, 02 Nov 2020 22:59:48 GMT):
I'd have to many problems to make grid work, specially the grid-cli and the validator. So at the end I took the protos file, and start writing the grid-cli using python and is working right now. I want to know the state of grid because I'd ask some question recently and nobody answer so I tought it was over.

amundson (Wed, 04 Nov 2020 14:35:44 GMT):
no, quite the opposite, gearing up for the 0.1 release

amundson (Wed, 04 Nov 2020 14:39:51 GMT):
answers can be hard to provide without enough context to recreate the issue (traceback is great, but its not enough unless someone has already run into it), and everyone is busy coding as well. you can view the project board if you want to know on what -- https://github.com/orgs/hyperledger/projects/1

dplumb (Thu, 05 Nov 2020 19:46:15 GMT):
Sorry for the lack of response @hidura , as @amundson mentioned we have been super busy with the 0.1 release. Btw, there is some updated documentation and an example for running Grid on Sawtooth coming soon that is currently in PR form. You can check it out on the Grid repo if you're interested in reviewing it or getting a preview: https://github.com/hyperledger/grid/pull/397

hidura (Wed, 11 Nov 2020 12:39:37 GMT):
Thanks @dplumb I'll be checking it!

dplumb (Thu, 12 Nov 2020 15:50:17 GMT):
Hi folks, the next Grid community meeting is this Friday, November 13th at 10am US Central time. Zoom link: https://us02web.zoom.us/j/86725415937?pwd=NHN2WFRieGtYbFV1SnNiT3pxUEdZZz09 Agenda: https://docs.google.com/document/d/1CQGW101MVGnOCuI2K-UkwgwMqSfVtxpec8wrE-HsgOY/edit# Please let me know if there are any items you would like to add to the agenda. Thanks and I hope to see you there!

knu1p (Sun, 15 Nov 2020 07:35:16 GMT):
Has joined the channel.

knu1p (Sun, 15 Nov 2020 07:35:16 GMT):
Hi everybody...is possible run *Hyperledger Grid* on IBM Blockchain Platform (BaaS)??

knu1p (Sun, 15 Nov 2020 09:14:18 GMT):
Has sense use Hyperledger Grid for government ?, using GRID smart contracts for administrative purposes

piyushmaheshwari65 (Wed, 25 Nov 2020 04:20:23 GMT):
Has joined the channel.

dplumb (Thu, 10 Dec 2020 20:18:55 GMT):
Hi all, here is a reminder that the next Grid community meeting is tomorrow, Friday November 13th at 10am US Central time. Zoom link: https://us02web.zoom.us/j/86725415937?pwd=NHN2WFRieGtYbFV1SnNiT3pxUEdZZz09 Agenda: https://docs.google.com/document/d/1CQGW101MVGnOCuI2K-UkwgwMqSfVtxpec8wrE-HsgOY/edit# Please let me know if there are any discussion topics or other Grid related information you would like to include on the agenda (either for this time or a future community meeting). Thanks and I hope to see you there!

dplumb (Thu, 10 Dec 2020 20:18:55 GMT):
Hi all, here is a reminder that the next Grid community meeting is tomorrow, Friday, December 11th at 10am US Central time. Zoom link: https://us02web.zoom.us/j/86725415937?pwd=NHN2WFRieGtYbFV1SnNiT3pxUEdZZz09 Agenda: https://docs.google.com/document/d/1CQGW101MVGnOCuI2K-UkwgwMqSfVtxpec8wrE-HsgOY/edit# Please let me know if there are any discussion topics or other Grid related information you would like to include on the agenda (either for this time or a future community meeting). Thanks and I hope to see you there!

joker_cc (Fri, 18 Dec 2020 03:47:19 GMT):
Has joined the channel.

joker_cc (Fri, 18 Dec 2020 03:47:20 GMT):
hi everybody, When I try to create location following the documentation steps, the log prints the following indefinitely.I use the same YAML file as the document, I don't know why this is so, can someone help me, thanks!`sawtooth-sabre-tp | 2020-12-18 03:43:51,005 INFO [sawtooth_sabre::wasm_executor::wasm_externals] Attempting to get state, addresses: ["621dee01b5c39e5da5a7db911c4d85e3458928417618469e936409ac0a8551b218e562"] sawtooth-sabre-tp | 2020-12-18 03:43:51,009 INFO [sawtooth_sdk::processor] TP_PROCESS_REQUEST sending TpProcessResponse: ExternalsError { message: "Trap(Trap { kind: Host(ExternalsError { message: \"AuthorizationError(\\\"Tried to get unauthorized addresses: [\\\\\\\"621dee01b5c39e5da5a7db911c4d85e3458928417618469e936409ac0a8551b218e562\\\\\\\"]\\\")\" }) })" }`

joker_cc (Fri, 18 Dec 2020 03:48:27 GMT):
d

joker_cc (Fri, 18 Dec 2020 04:07:11 GMT):
hi everybody, When I try to create location following the documentation steps, the log prints the following indefinitely.I use the same YAML file as the document. Then, execute "grid location list" without any display. Can someone help me, thanks! like this, sawtooth-sabre-tp | 2020-12-18 04:00:49,867 INFO [sawtooth_sabre::wasm_executor::wasm_externals] Attempting to get state, addresses: ["621dee01b5c39e5da5a7db911c4d85e3458928417618469e936409ac0a8551b218e562"] sawtooth-sabre-tp | 2020-12-18 04:00:49,871 INFO [sawtooth_sdk::processor] TP_PROCESS_REQUEST sending TpProcessResponse: ExternalsError { message: "Trap(Trap { kind: Host(ExternalsError { message: \"AuthorizationError(\\\"Tried to get unauthorized addresses: [\\\\\\\"621dee01b5c39e5da5a7db911c4d85e3458928417618469e936409ac0a8551b218e562\\\\\\\"]\\\")\" }) })" }

lcvalves (Tue, 22 Dec 2020 08:19:58 GMT):
Has joined the channel.

lcvalves (Tue, 22 Dec 2020 08:25:58 GMT):
Hey everyone, ran into this issue a couple of days ago, does anyone have a solution for it? Thanks in advance! https://github.com/hyperledger/grid/issues/465

inf_Barry (Wed, 30 Dec 2020 20:18:35 GMT):
Has joined the channel.

inf_Barry (Wed, 30 Dec 2020 20:18:36 GMT):
Hi there, as a senior procurement consultant, I'm interested by joining the community and to contribute in the development of this project.

dplumb (Thu, 07 Jan 2021 17:46:14 GMT):
Hey @lcvalves , I believe that issue was fixed by this PR: https://github.com/hyperledger/grid/pull/470

dplumb (Thu, 07 Jan 2021 17:46:22 GMT):
Let me know if you still run into it

dplumb (Thu, 07 Jan 2021 17:46:36 GMT):
@inf_Barry Welcome to the community!

dplumb (Thu, 07 Jan 2021 17:50:51 GMT):
Hi all, here is a reminder that the next Grid community meeting is tomorrow, Friday, January 8th at 10am CT. Zoom link: https://us02web.zoom.us/j/86725415937?pwd=NHN2WFRieGtYbFV1SnNiT3pxUEdZZz09 Agenda: https://docs.google.com/document/d/1CQGW101MVGnOCuI2K-UkwgwMqSfVtxpec8wrE-HsgOY/edit# The major topic here will be the Grid Identity RFC, but there will likely be some open time left in the agenda. Please let me know if there are any discussion topics or other Grid related information you would like to include on the agenda (either for tomorrow or a future community meeting). Thanks and I hope to see you there!

ajayjadhav (Thu, 21 Jan 2021 12:11:09 GMT):
Has left the channel.

rjones (Mon, 25 Jan 2021 18:29:34 GMT):
Has joined the channel.

rjones (Mon, 25 Jan 2021 18:29:34 GMT):
Hi, the following repos still use `master` as the default branch: `grid, grid-contrib, grid-docs, grid-rfcs`. `main` [is the current guidance for naming](https://github.com/github/renaming).

amundson (Wed, 27 Jan 2021 14:53:27 GMT):
@rjones thanks, we are putting together a plan to roll out that change for Grid

TomKlein (Sun, 31 Jan 2021 00:22:24 GMT):
Has joined the channel.

TomKlein (Sun, 31 Jan 2021 00:22:24 GMT):
Hi, Tom Klein here. I co-chair the https://wiki.hyperledger.org/display/SCSIG/Supply+Chain+SIG . We have an opening this coming Thursday, Feb 4, on our regular call and I'd like to give Grid the hour if somebody would like to present. Usually 20-30 minutes of pres at a mostly business level and then the rest questions. Definitely would like to help start some cross-pollination. You can contact me at tkklein100@gmail.com if this could work.

amundson (Mon, 01 Feb 2021 14:58:31 GMT):

pike2schema

amundson (Mon, 01 Feb 2021 14:59:39 GMT):
CFK = conceptual foreign key. Because we are using slowly-changing dimensions, it can't technically be implemented with database constraints

amundson (Tue, 02 Feb 2021 19:37:15 GMT):

Clipboard - February 2, 2021 1:36 PM

fishnexj (Tue, 02 Feb 2021 22:50:36 GMT):
Has joined the channel.

fishnexj (Tue, 02 Feb 2021 22:50:36 GMT):
Hey @TomKlein

fishnexj (Tue, 02 Feb 2021 22:50:36 GMT):
Hey @TomKlein, we'd love to do something at a later meeting - the Feb 4th one doesn't work for us but sometime soon would be great!

TomKlein (Wed, 03 Feb 2021 15:59:12 GMT):
@fishnexj and group. Thanks for getting back to me. Our next openings are either 4/1 or 4/15. Let me know which one to put you down for and then we can coordinate beforehand.

dplumb (Wed, 03 Feb 2021 21:38:54 GMT):
Hi all, here is a reminder that the next Grid community meeting is two days from now, Friday, Feb 5th at 10am CT. Zoom link: https://us02web.zoom.us/j/86725415937?pwd=NHN2WFRieGtYbFV1SnNiT3pxUEdZZz09 Agenda: https://docs.google.com/document/d/1CQGW101MVGnOCuI2K-UkwgwMqSfVtxpec8wrE-HsgOY/edit# Please let me know if there are any more discussion topics you'd like to include on the agenda (either for this time or a future community meeting). Thanks and I hope to see you there!

dplumb (Wed, 03 Feb 2021 21:39:43 GMT):
I believe I had the wrong date on the agenda from last time. The correct date is Feb 5th. Sorry for any confusion there.

amundson (Thu, 04 Feb 2021 15:08:50 GMT):

Clipboard - February 4, 2021 9:08 AM

rjones (Fri, 05 Feb 2021 16:20:25 GMT):
Here is [the link to the deck](https://docs.google.com/presentation/d/1PRianIgWGNYsDeZ45yTi0cQVjY9deQu6DakFf_0wcZM/edit?usp=sharing) which we presented to the TSC a few weeks ago.

rjones (Fri, 05 Feb 2021 16:40:24 GMT):
[Here is the link to Insights](https://insights.lfx.linuxfoundation.org/projects/hyperledger-f)

rjones (Fri, 05 Feb 2021 17:01:16 GMT):
I have another call now - thanks for having me!

dplumb (Fri, 05 Feb 2021 17:02:12 GMT):
https://grid.hyperledger.org/community/roadmap.html

amundson (Fri, 05 Feb 2021 17:26:11 GMT):
This is the AFN article that mentions Grid - https://agfundernews.com/splinter-cargill-open-sources-software-to-build-a-better-agrifood-supply-chain.html

knagware9 (Sun, 07 Feb 2021 08:52:03 GMT):
Has left the channel.

carlo.burgos (Wed, 17 Feb 2021 17:00:35 GMT):
Has joined the channel.

carlo.burgos (Wed, 17 Feb 2021 17:00:35 GMT):
hi all - apologies if im posting this question on the wrong channel, but I'm running into an issue while running the grid/splinter example using the docker-compose command. I'm using the docker-compose command specified on the docs to deploy the test network with all Splinter artifacts, but its failing when trying to build the Pike's image. Error says that it was caused by... "Error parsing major identifier for key `package.version`. I checked the Cargo.toml file on Pike's folder and I see the version as "0.2.1". I did a "Git Pull" before running the docker compose build command as well as the docker-compose command to make sure I'm using up-to-date images. Any guidance to get this fix?

RobinBanks (Wed, 17 Feb 2021 18:43:34 GMT):
Could you paste the full error you're seeing and the command you're running?

carlo.burgos (Wed, 17 Feb 2021 19:33:21 GMT):

Clipboard - February 17, 2021 2:33 PM

carlo.burgos (Wed, 17 Feb 2021 19:33:23 GMT):
Hey, this is the error output (also attaching image): error: failed to parse manifest at `/build/contracts/pike/Cargo.toml` Caused by: Error parsing major identifier for key `package.version` The command '/bin/sh -c cargo build --target wasm32-unknown-unknown --release' returned a non-zero code: 101 ERROR: Service 'pike-contract-builder' failed to build

carlo.burgos (Wed, 17 Feb 2021 19:33:23 GMT):
Hey, this is the error output (also attaching image): `error: failed to parse manifest at /build/contracts/pike/Cargo.toml Caused by: Error parsing major identifier for key package.version The command '/bin/sh -c cargo build --target wasm32-unknown-unknown --release' returned a non-zero code: 101 ERROR: Service 'pike-contract-builder' failed to build`

carlo.burgos (Wed, 17 Feb 2021 19:33:23 GMT):
Hey, this is the error output (also attaching image): *error: failed to parse manifest at /build/contracts/pike/Cargo.toml Caused by: Error parsing major identifier for key package.version The command '/bin/sh -c cargo build --target wasm32-unknown-unknown --release' returned a non-zero code: 101 ERROR: Service 'pike-contract-builder' failed to build*

carlo.burgos (Wed, 17 Feb 2021 19:33:51 GMT):
The command I'm running is: `docker-compose -f examples/splinter/docker-compose.yaml build --pull`

carlo.burgos (Wed, 17 Feb 2021 19:34:37 GMT):
Let me know if you need any other info

RobinBanks (Wed, 17 Feb 2021 20:02:48 GMT):
Thanks! The issue is that the `REPO_VERSION` environment variable is not set. It should build if you run ``` $ docker-compose -f examples/splinter/docker-compose.yaml up --build ``` This should build the images and set that value correctly

carlo.burgos (Wed, 17 Feb 2021 20:55:14 GMT):
ok well i can see that the docker-compose file `example/splinter/docker-compose.yaml` defines the REPO_VERSION as part of the "args" section within the build block, shouldn't that set it as an environment variable?

RobinBanks (Wed, 17 Feb 2021 21:13:37 GMT):
Right, so running `docker-compose up --build` flag should work

carlo.burgos (Wed, 17 Feb 2021 21:19:35 GMT):
i think the variable substitution is not working when running that docker-compose command from the root directory, but referencing a docker-compose file on a sub-directory. I checked the docker-compose file using the "config" option and the ${REPO_VERSION} is coming up blank. I think is because the .env file on the root directory is not getting properly scoped. It does get set if the .env file is stored on the examples/splinter sub-directory.

carlo.burgos (Wed, 17 Feb 2021 21:23:03 GMT):
i've had this issue before and ended up mitigating it via a central shell script at root that first loads the env variables from a targeted .env, then proceeds with docker commands

carlo.burgos (Wed, 17 Feb 2021 21:31:51 GMT):
anyway... Thank you so much for the help and the quick responses! Please let me know if you need me to document this anywhere.

RobinBanks (Wed, 17 Feb 2021 21:53:08 GMT):
No problem! Unfortunately I wasn’t able to reproduce you’re issue locally, and I managed to build everything with the default .env at root. If you’d like, could you create an issue in the grid repo detailing the bug with the version of docker and the OS you’re using?

rjones (Thu, 18 Feb 2021 17:34:54 GMT):
@amundson I don't know if you've seen this: https://www.zenhub.com/ it plugs into GitHub issues directly. Cactus is using it.

amundson (Thu, 18 Feb 2021 19:03:44 GMT):
last time we looked at zenhub for public projects, it required giving fully permissions for all repos (public and private) to zenhub, which is a complete show-stopper

amundson (Thu, 18 Feb 2021 19:03:58 GMT):
it is otherwise quite nice

amundson (Thu, 18 Feb 2021 19:05:20 GMT):
its like 90% the same as github projects

rjones (Thu, 18 Feb 2021 21:54:25 GMT):
oh, yikes. That's a limitation of GitHub - which I have complained about as often as I can

rjones (Thu, 18 Feb 2021 21:55:47 GMT):
https://news.ycombinator.com/item?id=26087582

dplumb (Fri, 26 Feb 2021 21:39:00 GMT):
Hey all, I am planning to motion for final comment period for the Grid Pike v.2 RFC early next week. If you are interested and haven't had a chance to review it yet, now would be a great time. https://github.com/hyperledger/grid-rfcs/pull/23

AdityaDeepak (Sun, 28 Feb 2021 22:44:55 GMT):
Has joined the channel.

AdityaDeepak (Sun, 28 Feb 2021 22:54:13 GMT):
Hi everyone! I'm new to Grid and I've been trying to get the asset transfer example in grid-contrib to work. I just cloned both grid and grid-contrib and I was able to get everything up and running but when I go to the web client and create a new user, I get the following error in the logs. `tnt-server | Received POST request for /users from ::ffff:192.168.96.9 tnt-asset-client | 192.168.96.1 - - [28/Feb/2021:22:50:00 +0000] "POST /api/users HTTP/1.1" 200 478 tnt-shell | (node:117) UnhandledPromiseRejectionWarning: 408 - "" tnt-shell | (node:117) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2) tnt-shell | (node:117) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code. tnt-asset-client | [Sun Feb 28 22:51:00.356070 2021] [proxy_http:error] [pid 11:tid 140133701510912] (70007)The timeout specified has expired: [client 192.168.96.1:57378] AH01102: error reading status line from remote server gridd:8080, referer: http://localhost:8021/ tnt-asset-client | [Sun Feb 28 22:51:00.356384 2021] [proxy:error] [pid 11:tid 140133701510912] [client 192.168.96.1:57378] AH00898: Error reading from remote server returned by /grid/batches, referer: http://localhost:8021/ tnt-asset-client | 192.168.96.1 - - [28/Feb/2021:22:50:00 +0000] "POST /grid/batches HTTP/1.1" 502 341` What could be causing this? Thank you!

AdityaDeepak (Sun, 28 Feb 2021 22:54:13 GMT):
Hi everyone! I'm new to Grid and I've been trying to get the asset transfer example in grid-contrib to work. I just cloned both grid and grid-contrib and I was able to get everything up and running but when I go to the web client and create a new user, I get the following error in the logs. ` tnt-server | Received POST request for /users from ::ffff:192.168.96.9 tnt-asset-client | 192.168.96.1 - - [28/Feb/2021:22:50:00 +0000] "POST /api/users HTTP/1.1" 200 478 tnt-shell | (node:117) UnhandledPromiseRejectionWarning: 408 - "" tnt-shell | (node:117) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2) tnt-shell | (node:117) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code. tnt-asset-client | [Sun Feb 28 22:51:00.356070 2021] [proxy_http:error] [pid 11:tid 140133701510912] (70007)The timeout specified has expired: [client 192.168.96.1:57378] AH01102: error reading status line from remote server gridd:8080, referer: http://localhost:8021/ tnt-asset-client | [Sun Feb 28 22:51:00.356384 2021] [proxy:error] [pid 11:tid 140133701510912] [client 192.168.96.1:57378] AH00898: Error reading from remote server returned by /grid/batches, referer: http://localhost:8021/ tnt-asset-client | 192.168.96.1 - - [28/Feb/2021:22:50:00 +0000] "POST /grid/batches HTTP/1.1" 502 341 ` What could be causing this? Thank you!

AdityaDeepak (Sun, 28 Feb 2021 22:54:13 GMT):
Hi everyone! I'm new to Grid and I've been trying to get the asset transfer example in grid-contrib to work. I just cloned both grid and grid-contrib and I was able to get everything up and running but when I go to the web client and create a new user, I get the following error in the logs. ``` tnt-server | Received POST request for /users from ::ffff:192.168.96.9 tnt-asset-client | 192.168.96.1 - - [28/Feb/2021:22:50:00 +0000] "POST /api/users HTTP/1.1" 200 478 tnt-shell | (node:117) UnhandledPromiseRejectionWarning: 408 - "" tnt-shell | (node:117) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2) tnt-shell | (node:117) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code. tnt-asset-client | [Sun Feb 28 22:51:00.356070 2021] [proxy_http:error] [pid 11:tid 140133701510912] (70007)The timeout specified has expired: [client 192.168.96.1:57378] AH01102: error reading status line from remote server gridd:8080, referer: http://localhost:8021/ tnt-asset-client | [Sun Feb 28 22:51:00.356384 2021] [proxy:error] [pid 11:tid 140133701510912] [client 192.168.96.1:57378] AH00898: Error reading from remote server returned by /grid/batches, referer: http://localhost:8021/ tnt-asset-client | 192.168.96.1 - - [28/Feb/2021:22:50:00 +0000] "POST /grid/batches HTTP/1.1" 502 341 ``` What could be causing this? Thank you!

AdityaDeepak (Tue, 02 Mar 2021 16:36:23 GMT):
make

dplumb (Tue, 02 Mar 2021 17:52:33 GMT):
Hey Aditya. Hmm that is interesting.. looks like some improper error handling. By nature, the examples in grid-contrib aren't necessarily being actively maintained. Though I can't think of a reason why this would be happening. Ill try to reproduce that later on today.

dplumb (Tue, 02 Mar 2021 17:52:33 GMT):
Hey Aditya. Hmm that is interesting.. looks like some improper error handling. By nature, the examples in grid-contrib aren't necessarily being actively maintained. Though I can't think of a reason why this would have broken. Ill try to reproduce that later on today.

AdityaDeepak (Tue, 02 Mar 2021 17:54:30 GMT):
Thank you!

amundson (Tue, 02 Mar 2021 18:19:32 GMT):
it might be good to explicitly lock that contrib code to grid 0.1

dplumb (Wed, 03 Mar 2021 22:18:19 GMT):
Hmm I was able to repro that error. Not entirely sure what the issue is with some minimal debugging but I will log a bug for it in the development board. We should definitely get that locked to a released version (I think we will have to release an experimental Grid 0.1 artifact for it since track and trace is experimental)

dplumb (Wed, 03 Mar 2021 22:20:52 GMT):
@AdityaDeepak In the meantime I would recommend looking at the Creating Locations and Creating Agents examples in the Grid documentation under the "For Administrators" section https://grid.hyperledger.org/docs/0.1/

dplumb (Thu, 04 Mar 2021 17:41:17 GMT):
Hi all, here is a reminder that the next Grid community meeting is tomorrow, March 5th at 10am CT. Zoom link: https://us02web.zoom.us/j/86725415937?pwd=NHN2WFRieGtYbFV1SnNiT3pxUEdZZz09 Agenda: https://docs.google.com/document/d/1CQGW101MVGnOCuI2K-UkwgwMqSfVtxpec8wrE-HsgOY/edit# We will be primarily doing Q&A on the open RFCs for Grid. Please check them out at https://github.com/hyperledger/grid-rfcs/pulls if you are interested in reading them ahead of time. Other topics are welcome as well. Thanks and I hope to see you there!

T.ian (Thu, 04 Mar 2021 23:18:51 GMT):
Has joined the channel.

AdityaDeepak (Thu, 04 Mar 2021 23:35:26 GMT):
Thanks! @dplumb

zoup (Sat, 06 Mar 2021 19:32:21 GMT):
Has joined the channel.

zoup (Sat, 06 Mar 2021 19:32:22 GMT):
Hello All! Thank you for your efforts! Any ideas where i can find docs on REST API 0.2.1 ?

dplumb (Mon, 08 Mar 2021 18:21:03 GMT):
Hey zoup, you can find the REST API docs for 0.2.0 at https://grid.hyperledger.org/docs/0.2/api/ (to find this, go to the docs site, switch the version in the sidebar to 0.2, and find Grid REST API at the bottom). There are no docs for 0.2.1 at the moment since 0.2 is the main development branch and hasnt been released yet.

dplumb (Mon, 08 Mar 2021 18:35:09 GMT):
Hi all, I am motioning for the Pike 2 RFC to enter final comment period. Core team, please submit your reviews and approvals. Other reviews also remain welcome at this time. Thanks! https://github.com/hyperledger/grid-rfcs/pull/23#issuecomment-792976805

TomKlein (Thu, 11 Mar 2021 19:43:27 GMT):
@fishnexj @dplumb Are you able to present to our Supply Chain SIG on either 4/1 or 4/15? noon EDT is when we meet. Be great to have you if it will work.

fishnexj (Mon, 15 Mar 2021 12:31:32 GMT):
Hi @TomKlein we are not available to present at April 1st or 15th. We may be ready for a future session in June+

adineshreddy1 (Tue, 16 Mar 2021 09:37:22 GMT):
Has joined the channel.

rdeshmukh73 (Thu, 18 Mar 2021 14:29:51 GMT):
Has joined the channel.

rdeshmukh73 (Thu, 18 Mar 2021 14:29:51 GMT):
Hello All, I am very new to Hyperledger Grid. Pardon my naive question: Does Grid work on Hyperledger Fabric or is it at the moment restricted to Sawtooth and Splinter? Any plans to make it work on Fabric soon? Thanks for your time.

amundson (Thu, 18 Mar 2021 15:21:44 GMT):
@rdeshmukh73 no current plans; Grid supports platforms using Hyperledger Transact, so it is really a question of Fabric support for Transact which AFAIK is not currently being worked on.

TomKlein (Fri, 19 Mar 2021 16:55:54 GMT):
ok, let's look to a later date.

sumit0042 (Sun, 11 Apr 2021 10:29:54 GMT):
Has joined the channel.

T.ian (Thu, 22 Apr 2021 18:50:45 GMT):
Hi all, is there a suggested way to add an action (like CreateProduct, UpdateProduct) to the existing SDK?

squarfed (Tue, 27 Apr 2021 17:48:52 GMT):
Has joined the channel.

dplumb (Thu, 29 Apr 2021 16:11:20 GMT):
@T.ian Can you elaborate on that a bit? Are you talking about new smart contract functionality?

dplumb (Thu, 29 Apr 2021 19:31:10 GMT):
Hi all, due to a lack of any urgent agenda items and a few of the typical contributors being unavailable tomorrow, the Grid Community Meeting is cancelled for this month. Meetings will resume as normal next month.

dplumb (Fri, 30 Apr 2021 14:51:30 GMT):
Final vote for Pike 2 RFC: https://github.com/hyperledger/grid-rfcs/pull/23

gusBar (Thu, 06 May 2021 05:14:33 GMT):
Has joined the channel.

zoup (Thu, 13 May 2021 12:09:17 GMT):
Hi All! My name is Armin, i'm working with Blockcorp and a number of hospital in europe to create a mask tracking logistics management software on top of Grid

zoup (Thu, 13 May 2021 12:09:35 GMT):
Thank you all for the effort you put in the project!

zoup (Thu, 13 May 2021 12:10:15 GMT):
few days ago we experienced this issue (https://github.com/hyperledger/grid/issues/687) and we are kinda stuck, would be great if you can advise on this

zoup (Thu, 13 May 2021 12:10:18 GMT):
thanks again!

zoup (Thu, 13 May 2021 12:10:40 GMT):
btw our project info is at http://blockchainlab.lu/medlogistics/

amundson (Fri, 14 May 2021 13:47:19 GMT):
@zoup can you explain a little bit about what you were doing that led up to this? i.e. what transactions, etc.

zoup (Fri, 14 May 2021 14:44:35 GMT):
With pleasure, thank you for getting back to me! Basically, we do this over a CI/CD test system where we create an organization, a role with all permissions, allocating that role to the user, creating a custom location schema (based on grid test yamls) generating GLN based on companies prefix + checkdigit and then try to create that location via CLI with the permission of the user we just created

zoup (Fri, 14 May 2021 14:44:41 GMT):
basically, we run cli all over

zoup (Fri, 14 May 2021 14:45:01 GMT):
above is of course for grid 0.2, but same exact end-result (trap exception) happened with 0.1

zoup (Fri, 14 May 2021 14:46:31 GMT):
at the moment i can share anything that you need, if it's db dumps, yaml files, even source codes, that's certainly shareable as we are planning to opensource it anyway

dplumb (Fri, 14 May 2021 14:58:40 GMT):
Hmm interesting! If you have the yaml files you are using to define the custom location schema and the command you are using to create the location, I can try to reproduce it

zoup (Fri, 14 May 2021 16:29:03 GMT):
Will definitely dig them up and share with you!

zoup (Fri, 14 May 2021 21:31:21 GMT):
Hi Again! updated the issue with a list of all commands, parameters, stdout and stderr, as well as yaml files

zoup (Fri, 14 May 2021 21:31:23 GMT):
https://github.com/hyperledger/grid/issues/687

zoup (Fri, 14 May 2021 21:31:58 GMT):
this installation is also accessible to you if you want to see status on batches etc : http://172.255.253.162:8080

charith1994 (Sat, 15 May 2021 17:04:42 GMT):
Has joined the channel.

slim-patchy (Wed, 19 May 2021 11:25:20 GMT):
Has joined the channel.

slim-patchy (Wed, 19 May 2021 11:25:20 GMT):
Hi everyone! My name is Kris and I am working for a FinTech startup that is exploring using Hyperledger Grid for banking applications. Nice to meet you here!

rjones (Wed, 19 May 2021 13:08:26 GMT):
Has left the channel.

dplumb (Wed, 19 May 2021 16:42:42 GMT):
@zoup I responded to you in your issue

dplumb (Wed, 19 May 2021 16:43:04 GMT):
Welcome @slim-patchy !

zoup (Wed, 19 May 2021 18:03:46 GMT):
@dplumb Thank you very much! will try them out and get back to you!

dplumb (Wed, 19 May 2021 18:32:42 GMT):
You're welcome! The example I provided is for the dev branch, so if you are using 0.1 you will need slightly different commands. Not sure which version you're targeting

zoup (Wed, 19 May 2021 18:36:17 GMT):
actually running this on 0.2

zoup (Wed, 19 May 2021 18:39:37 GMT):
hmm, excluding --metadata on organization create, i can't find any difference between my commands and 0.2 docs...

zoup (Wed, 19 May 2021 18:39:57 GMT):
either case, removed --metadata, still getting the same exception..

zoup (Wed, 19 May 2021 18:51:58 GMT):
can you please share your schema and location yamls?

zoup (Wed, 19 May 2021 18:52:49 GMT):
maybe there is something wrong with those? because the one in the cli/tests/locations/ are not working as well (missing owner field)

dplumb (Wed, 19 May 2021 21:07:52 GMT):
That is odd. I downloaded the schema and location yaml that you had linked in the issue

zoup (Wed, 19 May 2021 23:46:39 GMT):
ah, note that create location cli actually returns 0, whatever's the input grid cli is happy with it

zoup (Wed, 19 May 2021 23:46:53 GMT):
the exception thing happens at the sawtooth level

zoup (Wed, 19 May 2021 23:50:51 GMT):
on your test, did the location actually got created?

dplumb (Thu, 20 May 2021 19:14:04 GMT):
Yes, in my testing they did get created. How recently did you set up your containers? There were some changes on main to Pike addressing that may have impacted this, but that was quite a few weeks ago.

dplumb (Thu, 20 May 2021 19:14:09 GMT):
Ill take another look at it tomorrow

zoup (Thu, 20 May 2021 19:16:41 GMT):
Thanks! i'm actually running this via docker-compose -f examples/sawtooth/docker-compose.yaml build --pull and up

zoup (Thu, 20 May 2021 19:16:48 GMT):
not sure if that's the best approach...

zoup (Thu, 20 May 2021 19:17:06 GMT):
and on master

dplumb (Thu, 20 May 2021 19:21:56 GMT):
Oh you are using sawtooth. Ok I was using splinter when I tried to reproduce it

zoup (Thu, 20 May 2021 19:22:53 GMT):
Yes it's sawtooth, but which is more stable in term of using for production between sawtooth and splinter?

zoup (Thu, 20 May 2021 19:23:24 GMT):
i think you guys mainly use splinter for development right? judging by docs and comments here and there...

amundson (Thu, 20 May 2021 19:37:01 GMT):
which one to use really comes down to your use case; splinter's scabbard ledger currently supports 2-3 nodes using 2-phase-commit and isn't technically a blockchain

amundson (Thu, 20 May 2021 19:37:36 GMT):
sawtooth w/pbft is 5+ nodes all with a shared state

amundson (Thu, 20 May 2021 19:38:49 GMT):
long-term roadmap, splinter will be the underlying network layer for sawtooth 2

amundson (Thu, 20 May 2021 19:39:09 GMT):
so a lot of our energy goes there

zoup (Thu, 20 May 2021 19:39:15 GMT):
Hi @amundson, my first concern is stability in terms of how well grid works with either of them

zoup (Thu, 20 May 2021 19:41:51 GMT):
Splinter's longer term plan works for us as well, hopefully we can help with that process

amundson (Thu, 20 May 2021 19:42:00 GMT):
most of the developers use splinter daily and we test out sawtooth when we do releases, so I guess to some extent splinter?

zoup (Thu, 20 May 2021 19:42:36 GMT):
Understood

amundson (Thu, 20 May 2021 19:42:54 GMT):
but we do intend it to work on both, so I'm just speaking from a practical perspective not a goal perspective

amundson (Thu, 20 May 2021 19:48:46 GMT):
as we are approaching the 0.2 release, it is on the todo to run through all the docs and re-test for regressions -- I think maybe you are a couple weeks ahead of us, so this is definitely something we are currently interested in understanding and fixing

zoup (Thu, 20 May 2021 19:50:41 GMT):
that's perfectly fine, we are planning to help with splinter/grid development as well

zoup (Thu, 20 May 2021 19:50:59 GMT):
i actually explained what we are trying to achieve with grid a while ago

amundson (Thu, 20 May 2021 19:51:16 GMT):
it might be useful to create a bug issue for this to help track it

zoup (Thu, 20 May 2021 19:51:30 GMT):
we are basically a luxembourg based company, partnered up with a number of hospitals around the Europe

amundson (Thu, 20 May 2021 19:51:38 GMT):
that would be great!

zoup (Thu, 20 May 2021 19:51:53 GMT):
our product, VeriBlok is basically a logistics management system specialized for medical devices

zoup (Thu, 20 May 2021 19:52:17 GMT):
we started just 3 months ago, so, relatively new

amundson (Thu, 20 May 2021 19:55:35 GMT):
there is a medical device company here in minneapolis called medtronic

amundson (Thu, 20 May 2021 19:56:32 GMT):
I heard some stories about devices they make being delivered as-needed quickly in trunks of cars and it being a hard problem to keep track of everything accurately

zoup (Thu, 20 May 2021 19:57:00 GMT):
Yes, Masks, Vaccines, those stuff are critical at this point

zoup (Thu, 20 May 2021 19:57:40 GMT):
long story short, turns out the entire EU has no real way to verify the authenticity of a product

zoup (Thu, 20 May 2021 19:58:19 GMT):
and the whole COVID crisis just made that worst, a hospital which purchased 3000 masks per "year" had to suddenly buy 6000 per day

amundson (Thu, 20 May 2021 19:59:35 GMT):
presumably some of that specific example has started to be worked out at this point?

zoup (Thu, 20 May 2021 20:00:35 GMT):
They really couldn't fix the problem but find a way around it

amundson (Thu, 20 May 2021 20:01:59 GMT):
what's your vision of a solution?

zoup (Thu, 20 May 2021 20:03:02 GMT):
basically a platform that contain both labs (who certify the product as well as raw material) as well as purchaser/manufacturers

zoup (Thu, 20 May 2021 20:03:21 GMT):
sending the deck to your PM (Sorry can't share publicly at this point)

dplumb (Tue, 25 May 2021 15:30:13 GMT):
@zoup I was able to repro your error on Sawtooth, so likely a regression. We will look into that

zoup (Tue, 25 May 2021 15:42:00 GMT):
@dplumb Thanks, node that it happens on 0.1 as well

zoup (Tue, 25 May 2021 15:42:00 GMT):
@dplumb Thanks, note that it happens on 0.1 as well

fishnexj (Tue, 25 May 2021 20:49:29 GMT):
Hey all here's a brief update on the Grid Community: https://lists.hyperledger.org/g/grid/message/100

lcvalves (Fri, 28 May 2021 14:52:19 GMT):
Is v0.1.2 the lastest stable version?

lcvalves (Fri, 28 May 2021 14:52:19 GMT):
Is v0.1.2 the latest stable version?

arsulegai (Fri, 28 May 2021 15:03:07 GMT):
Hi, do we have Grid community meeting today?

arsulegai (Fri, 28 May 2021 15:03:26 GMT):
I am held up from 2 months, did not get a chance to attend any of the meetings

agunde (Fri, 28 May 2021 15:07:22 GMT):
@arsulegai There is not a meeting today. You can see an more about how grid meetings are going to work going forward in an update that was sent to the mailing list https://lists.hyperledger.org/g/grid/message/100

arsulegai (Fri, 28 May 2021 15:08:15 GMT):
Thanks :)

ardeshir (Mon, 07 Jun 2021 17:23:00 GMT):
Has joined the channel.

ardeshir (Mon, 07 Jun 2021 17:23:01 GMT):
Hi team

fishnexj (Mon, 07 Jun 2021 17:23:21 GMT):
Hi @ardeshir welcome!

ardeshir (Mon, 07 Jun 2021 17:24:32 GMT):
I want to rust on grid / splinter my days away :D

wakasupi (Mon, 07 Jun 2021 17:31:53 GMT):
Has joined the channel.

wakasupi (Mon, 07 Jun 2021 17:31:53 GMT):
Hi, I work with Ardeshir and Kevin Johnson. I am also interested in contributing.

fishnexj (Mon, 07 Jun 2021 17:32:18 GMT):
Super great welcome @wakasupi

ardeshir (Mon, 07 Jun 2021 17:32:50 GMT):
hello Paul

wakasupi (Mon, 07 Jun 2021 17:33:09 GMT):
@fishnexj is giving us an overview of the application

VikrantKumbhar (Thu, 10 Jun 2021 14:15:51 GMT):
Has joined the channel.

VikrantKumbhar (Thu, 10 Jun 2021 14:15:51 GMT):
Hi, I am getting below error after execution grid product create --file product.yaml Subcommand encountered an error: No signing key found in /root/.cylinder/keys. Either specify the --key argument or generate the default key via splinter keygen Please advice

VikrantKumbhar (Thu, 10 Jun 2021 14:16:45 GMT):
I am learning Grid

ksanjayk (Thu, 10 Jun 2021 17:41:40 GMT):
Has joined the channel.

zoup (Fri, 11 Jun 2021 08:50:31 GMT):
[ ](https://chat.hyperledger.org/channel/grid?msg=gZeEgmcSdjWBAxyQ9) by the looks of it you either haven't generated keys at all, lack env variables, or stored somewhere grid can't find

zoup (Fri, 11 Jun 2021 08:50:48 GMT):
easiest to just generate key and pass --key to grid so it can find them out :)

VikrantKumbhar (Fri, 11 Jun 2021 12:39:47 GMT):
[ ](https://chat.hyperledger.org/channel/grid?msg=sXKwKtsZCba7nzc3o) Hi zoup, Thank you for reply. I have used echo "{PublicKey}" > gridd.pub command. Is there any other command I need to use to generate Key. Please suggest, still stuck on same point .

dplumb (Fri, 11 Jun 2021 16:39:36 GMT):
We had a change on the development branch (main) which may not be reflected in the docs yet

dplumb (Fri, 11 Jun 2021 16:57:22 GMT):
For now you should be able to pass --key as @zoup said, or set `CYLINDER_PATH` env var to the location of your key

VikrantKumbhar (Sat, 12 Jun 2021 05:49:41 GMT):
[ ](https://chat.hyperledger.org/channel/grid?msg=3hSp4hHNoeh5GrPqo) Hi dplump, Thank you for reply. Please provide the command, as you mentioned it is not available in docs.

zoup (Sat, 12 Jun 2021 07:35:31 GMT):
[ ](https://chat.hyperledger.org/channel/grid?msg=vmbQBhsyuPGaHZvvX) it really isn't a command, it's just a parameter, --key as @dplumb said

coreycollins (Tue, 15 Jun 2021 14:23:23 GMT):
Has joined the channel.

nage (Mon, 21 Jun 2021 17:29:40 GMT):
Has left the channel.

AjinkyaBhamre (Wed, 23 Jun 2021 10:22:54 GMT):
Has joined the channel.

AjinkyaBhamre (Wed, 23 Jun 2021 10:22:54 GMT):
hi I am new to this grid framework, I was referring from "https://grid.hyperledger.org/docs/0.1/grid_on_splinter.html" building and running docker containers, I noticed all of my containers are not running. whenever I use this command "docker exec gridd-alpha cat /etc/grid/keys/gridd.pub " on my ubuntu machine I get "Error response from daemon: Container f6195c23172dfb309f8d5208ab30dfcd8dd0c132c12fca7a4f8aee000b5650cb is not running" this error 🐞

AjinkyaBhamre (Wed, 23 Jun 2021 10:25:06 GMT):
my docker containers in terminal showing exit code(0) and exit code(1)

AjinkyaBhamre (Wed, 23 Jun 2021 10:26:42 GMT):

Screenshot 2021-06-23 at 3.56.33 PM.png

dplumb (Wed, 23 Jun 2021 17:20:06 GMT):
Is there anything earlier in the logs for the gridd-alpha container to indicate why it exited?

AjinkyaBhamre (Thu, 24 Jun 2021 11:35:04 GMT):
no

AjinkyaBhamre (Thu, 24 Jun 2021 11:35:37 GMT):
no

AjinkyaBhamre (Thu, 24 Jun 2021 11:38:57 GMT):

Screenshot 2021-06-24 at 5.08.44 PM.png

AjinkyaBhamre (Thu, 24 Jun 2021 11:39:02 GMT):
hi, I am getting this InvalidYamlError while creating schemas from product_schema.yaml file as per in the documentation (https://grid.hyperledger.org/docs/0.1/creating_schemas.html )

AjinkyaBhamre (Thu, 24 Jun 2021 11:42:00 GMT):
I'm new to learning grid. please advice. thank you .

dplumb (Thu, 01 Jul 2021 17:15:33 GMT):
Hey @AjinkyaBhamre sorry for the delay on reply. Are you using Grid 0.1 or the main branch (0.2 dev)?

sharkrit (Mon, 05 Jul 2021 18:23:15 GMT):
Has joined the channel.

sharkrit (Mon, 05 Jul 2021 18:23:16 GMT):
Hi There, I'm newbie here. Can someone please guide me to the high-level architect diagram of Hyperledger Grid communication with Hyperledger Sawtooth?

amundson (Fri, 09 Jul 2021 15:36:04 GMT):

Clipboard - July 9, 2021 10:35 AM

amundson (Fri, 09 Jul 2021 15:36:23 GMT):
@sharkrit ^

tim-trutech (Tue, 20 Jul 2021 03:25:26 GMT):

Clipboard - July 19, 2021 8:25 PM

tim-trutech (Tue, 20 Jul 2021 03:25:30 GMT):
Has joined the channel.

tim-trutech (Tue, 20 Jul 2021 03:25:30 GMT):
Hello. New to Grid and Hyperledger in general. I'm not sure if this is a bug or not. Running the following, I was thinking that roles would be "reset" to whatever `--role` args were passed in. Instead, they are appended: `grid agent update a1 023a706934e3be6eb624f74a687e4bb2687238ab84440d1e2197d8a81a65b3ad63 --active --role "admin" --role "product-admin"`

septcinquante (Thu, 22 Jul 2021 19:58:03 GMT):
Has joined the channel.

septcinquante (Thu, 22 Jul 2021 19:58:03 GMT):
Hello New to Grid , i'm trying the sample for sawtooth but when i try to create an organisation `grid organization create 000000001 sept_cinquante --metadata gs1_company_prefixes=SC_01` in alpha container i have an error : http://gridd-alpha:8080/batches: error trying to connect: Connection refused (os error 111) all containers are running, version of docker : v20.10.7 thanks for help

tim-trutech (Fri, 23 Jul 2021 04:18:03 GMT):
Hi @septcinquante. Where are you running the command from? Can you resolve the name gridd-alpha via DNS? If you're in the gridd-alpha container itself, can you access http://localhost:8080?

septcinquante (Fri, 23 Jul 2021 15:38:12 GMT):
Hi from the container alpha himself

septcinquante (Fri, 23 Jul 2021 15:38:12 GMT):
Hi from the container alpha itself

tim-trutech (Fri, 23 Jul 2021 18:58:34 GMT):
@septcinquante I'm guessing it's a DNS/resolution issue. Can you access http://localhost:8080/batches from within the container?

septcinquante (Mon, 26 Jul 2021 12:34:44 GMT):
your right , when i use wget inside the container , i have ``` `root@gridd-alpha:/# wget http://gridd-alpha:8080 --2021-07-26 12:33:22-- http://gridd-alpha:8080/ Resolving gridd-alpha (gridd-alpha)... 172.21.0.9 Connecting to gridd-alpha (gridd-alpha)|172.21.0.9|:8080... failed: Connection refused.` ```

septcinquante (Mon, 26 Jul 2021 12:34:44 GMT):
your are right , when i use wget inside the container , i have ``` `root@gridd-alpha:/# wget http://gridd-alpha:8080 --2021-07-26 12:33:22-- http://gridd-alpha:8080/ Resolving gridd-alpha (gridd-alpha)... 172.21.0.9 Connecting to gridd-alpha (gridd-alpha)|172.21.0.9|:8080... failed: Connection refused.` ```

septcinquante (Mon, 26 Jul 2021 20:58:12 GMT):
I have migrate to real ubuntu server and it's working, maybe an issue when running on OSX

septcinquante (Mon, 26 Jul 2021 21:01:27 GMT):
hello there is a grid ui with sawtooth ? i understand that it's only for Splinter

dplumb (Tue, 27 Jul 2021 13:31:06 GMT):
Yes it only supports Splinter at the moment

septcinquante (Tue, 27 Jul 2021 19:28:14 GMT):
Hi in sawtooth , who is responsable to write in the ledger ? validator or processor or ...? thanks

septcinquante (Wed, 28 Jul 2021 20:00:08 GMT):
Hello , i don't understand how it's possible to delete a product in grid ? I have learned that blockChain is immutable , so how grid do it ?

septcinquante (Wed, 28 Jul 2021 20:00:08 GMT):
Hello , i don't understand how it's possible to delete a product in grid ? I have learned that blockChain is immutable , so how grid do it ? thanks

LeslytH (Thu, 29 Jul 2021 08:10:20 GMT):

Clipboard - July 29, 2021 10:10 AM

LeslytH (Thu, 29 Jul 2021 08:10:23 GMT):
Has joined the channel.

LeslytH (Thu, 29 Jul 2021 08:10:24 GMT):
Hello everyone, I am a student in my last few months and I am trying to make a POC of a Hyperledger Grid solution. I am following the following tutorial: https://grid.hyperledger.org/docs/0.1/grid_on_splinter.html However... I get the following issue when trying to run the following docker command: docker-compose -f examples/splinter/docker-compose.yaml build --pull

LeslytH (Thu, 29 Jul 2021 08:11:19 GMT):
I tried it with Splinter and with Sawtooth. I am on Windows 10 Enterprise, WSL 2 with Ubuntu 20.04.

tim-trutech (Mon, 02 Aug 2021 04:55:00 GMT):
I received this error if I used the downloadable zip file. If I did a git clone, the error went away.

LeslytH (Mon, 02 Aug 2021 10:15:45 GMT):
Hi! I also did that. And now I have a new error

LeslytH (Mon, 02 Aug 2021 10:16:16 GMT):
Yes you are right Tim. Now I have the following issue when trying to install

LeslytH (Mon, 02 Aug 2021 10:16:18 GMT):

Clipboard - August 2, 2021 12:16 PM

LeslytH (Mon, 02 Aug 2021 10:16:56 GMT):

Clipboard - August 2, 2021 12:16 PM

LeslytH (Mon, 02 Aug 2021 10:53:29 GMT):
It keeps alternating between splinterd-beta splinterd-alpha splinterd-beta spliterd-gamma

LeslytH (Tue, 03 Aug 2021 13:47:37 GMT):
Thansk for the response!

LeslytH (Tue, 03 Aug 2021 13:47:47 GMT):
Now I have a new Issue which is bothering me greatly...

LeslytH (Tue, 03 Aug 2021 13:47:49 GMT):

Clipboard - August 3, 2021 3:47 PM

LeslytH (Tue, 03 Aug 2021 13:48:34 GMT):
This is something which was noteworthy while starting the docker compose file up

LeslytH (Tue, 03 Aug 2021 13:48:51 GMT):

Clipboard - August 3, 2021 3:48 PM

LeslytH (Tue, 03 Aug 2021 13:48:54 GMT):
And I get the following loop now everytime.

LeslytH (Tue, 03 Aug 2021 13:53:32 GMT):
I guess it is something within the docker compose file with registry:registry

LeslytH (Tue, 03 Aug 2021 13:53:36 GMT):

Clipboard - August 3, 2021 3:53 PM

LeslytH (Tue, 03 Aug 2021 13:54:34 GMT):
I am running this command: docker-compose -f examples/splinter/docker-compose.yaml up And it does not matter if I try it with sudo in front of the command or without.

LeslytH (Tue, 03 Aug 2021 14:00:35 GMT):

Clipboard - August 3, 2021 4:00 PM

LeslytH (Tue, 03 Aug 2021 14:04:18 GMT):
Also multiple docker containers are running and in a new windows I can acces gridd-alpha and such. But when I tryto use the Schema builder or something it does not work because it is not up

LeslytH (Tue, 03 Aug 2021 14:04:23 GMT):

Clipboard - August 3, 2021 4:04 PM

LeslytH (Tue, 03 Aug 2021 14:04:36 GMT):
I am sorry for the spam. But I am trying multiple days already to no availl

LeslytH (Tue, 03 Aug 2021 14:08:49 GMT):
So I am getting kinda frustrated haha

agunde (Tue, 03 Aug 2021 19:43:47 GMT):
@LeslytH Some of the containers are excepted to shutdown when they are done. For example the builder and generate-registry shutdown once they are done.

dplumb (Tue, 03 Aug 2021 20:07:42 GMT):
which version of Grid are you using @LeslytH ?

dplumb (Tue, 03 Aug 2021 20:08:33 GMT):
If you are trying to just execute the example commands, you can exec into the gridd-alpha container and run the CLI commands from there. Before you go through the example make sure you select the version of grid that you're using from the sidebar of the docs

LeslytH (Tue, 03 Aug 2021 20:38:52 GMT):
[ ](https://chat.hyperledger.org/channel/grid?msg=LnjaeZrxHnxjK25zT) But then shouldn't it be said in the CLI of the WSL?

LeslytH (Tue, 03 Aug 2021 20:39:36 GMT):
[ ](https://chat.hyperledger.org/channel/grid?msg=Sz788GqZDNSixigam) I am following https://grid.hyperledger.org/docs/0.2/grid_on_splinter.html But I also had it at V 0.1

LeslytH (Tue, 03 Aug 2021 20:41:44 GMT):
[ ](https://chat.hyperledger.org/channel/grid?msg=Sz788GqZDNSixigam) I can do this eventually untill the point I want to create a Schema. At that point after I copy the example schema to the node it says that the batch is succesfully submitted with a long code. But when using the command to show the Schema nothing is there. When I look at my Docker setup the Schema builder Node is offline

LeslytH (Tue, 03 Aug 2021 20:43:01 GMT):
But I am curious. What are other people using as a base os? Is anyone having succes with WSL and ubuntu 20.04? Or are people using Ubuntu 20.04 (VM)?

LeslytH (Tue, 03 Aug 2021 20:44:39 GMT):
Nonethless, THank you for your time and patience haha.

dplumb (Fri, 06 Aug 2021 15:54:58 GMT):
When you submit the transaction you'll either see that the transaction was successful and the grid daemon added it to the database, or youll see an invalid transaction log with the reason why the transaction may have failed

dplumb (Fri, 06 Aug 2021 15:55:21 GMT):
that doesnt get reported back to the CLI at the moment

LeslytH (Wed, 11 Aug 2021 11:05:00 GMT):
Hmm okay

LeslytH (Wed, 11 Aug 2021 11:05:23 GMT):
I see there is also a newer version of Grid. I will give it another chance and I will share my findings with you

LeslytH (Wed, 11 Aug 2021 11:21:58 GMT):
The product catalog specification as mentioned in V0.3 will be my lifesaver for my PoC! (If I can get it to work ofcourse :P)

LeslytH (Wed, 11 Aug 2021 11:22:50 GMT):
https://grid.hyperledger.org/releases/0.2/download.html I see that V0.3 is not mentioned here? Will it be?

LeslytH (Wed, 11 Aug 2021 15:23:06 GMT):
Okay... I tried again. Still get stuck on this screen

LeslytH (Wed, 11 Aug 2021 15:23:19 GMT):

Splinterd-alpha stuck on this.JPG

LeslytH (Wed, 11 Aug 2021 15:23:34 GMT):
When i look into that docker container I see this

LeslytH (Wed, 11 Aug 2021 15:23:40 GMT):

Splinterd-alpha container.JPG

LeslytH (Wed, 11 Aug 2021 15:23:56 GMT):
The databases are running

LeslytH (Wed, 11 Aug 2021 15:24:02 GMT):

Splinterd-alpha fault.JPG

LeslytH (Wed, 11 Aug 2021 15:24:56 GMT):
I still get this error when using the following line docker-compose -f examples/splinter/docker-compose.yaml up

LeslytH (Wed, 11 Aug 2021 15:26:03 GMT):
I am really getting frustrated that I keep failing at this point. Has anyone an idea what to do? I have WSL2 Latest docker version within WSL2 Ubuntu 20.04 I am also using the v0.3 docs

LeslytH (Wed, 11 Aug 2021 15:26:14 GMT):
0.3 from Grid

LeslytH (Wed, 11 Aug 2021 15:27:12 GMT):
Do people recommend I try a full linux environment? But in WSL it should also work right?

LeslytH (Thu, 12 Aug 2021 12:52:31 GMT):
Okay, I think it just needs to keep running like that. I opened a new WSL instance and continued through the tutorial and it seems everything is going smoother than expected!

LeslytH (Thu, 12 Aug 2021 14:46:03 GMT):
I have added my first product!

LeslytH (Thu, 12 Aug 2021 14:46:28 GMT):
However when I try to add a second product with a different GTIN I get an error

LeslytH (Thu, 12 Aug 2021 14:46:30 GMT):

Clipboard - August 12, 2021 4:46 PM

LeslytH (Thu, 12 Aug 2021 14:47:07 GMT):

LeslytH - Thu Aug 12 2021 16:46:53 GMT+0200 (Central European Summer Time).txt

LeslytH (Thu, 12 Aug 2021 14:47:57 GMT):

Clipboard - August 12, 2021 4:47 PM

LeslytH (Thu, 12 Aug 2021 14:48:45 GMT):
I have one visible. But if I change the GTIN to ...930 for example. it gives these errors

LeslytH (Fri, 13 Aug 2021 11:23:52 GMT):
okay it works again

LeslytH (Fri, 13 Aug 2021 13:04:39 GMT):
Okay, I finally have a decent grasp of hyperledger Grid. However to make my PoC a succes I have to implement the following things in my PoC is it *now* possible to change product data from other organizations? Is it possible to have a kind of versioning of changing productdata? For example Product A with owner OrgA has description A. But orgB changes the description to description B. Is it possible to have an overview of version 1 (Original product) and version 2 (changed product)? Something similar like https://prod.etim-international.com/Class/Compare?classIdLeft=EC000001&classVersionLeft=5&classIdRight=EC000001&classVersionRight=4 I see something in the REST API about batches. What are they? Is it possible to look at the history of products? As in version 1 like in my example? Also lastly, How do i export the products to the postgres database?

LeslytH (Fri, 13 Aug 2021 13:05:12 GMT):
I know, a lot of questions but this might help me immensely when answered.

LeslytH (Mon, 16 Aug 2021 13:08:02 GMT):

Clipboard - August 16, 2021 3:07 PM

LeslytH (Mon, 16 Aug 2021 13:08:40 GMT):
How are the inputs and outputs determined? I would like to make/update a Smart Contract but I am not sure how to start/update it.

LeslytH (Mon, 16 Aug 2021 13:30:28 GMT):
How do you use the delegation of roles in an organization? How to make a smart contract is really difficult for me. There is not a lot of information how to effectively add funcitons to a smart cotnract.

LeslytH (Mon, 16 Aug 2021 14:30:37 GMT):
Or how to make a whole new smart contract for that matter.

dplumb (Mon, 16 Aug 2021 18:38:36 GMT):
> is it now possible to change product data from other organizations? Yes this is possible. Org A will make a new role with the `product::can-update-product` role and add Org B to the `allowed_organizations` field. Then org B can create a new role with the role name of the role that Org A created in the `inherits_from` field. Example of that here: https://grid.hyperledger.org/docs/0.3/using_pike.html > Is it possible to have a kind of versioning of changing productdata? Currently theres no versioning of product data in Grid Product.

LeslytH (Mon, 16 Aug 2021 21:43:27 GMT):
Ah thanks for the reply!

LeslytH (Mon, 16 Aug 2021 21:44:52 GMT):
Where do I put the inherits-from line in??

LeslytH (Mon, 16 Aug 2021 21:45:30 GMT):
And about the versioning... Is IT possible to het tidbits out of the tnt

LeslytH (Mon, 16 Aug 2021 21:46:44 GMT):
Tnt smart contract and work with timestamping new properties instead of ownership of the product? That way it is somewhat similar to versioning

LeslytH (Tue, 17 Aug 2021 06:38:27 GMT):

Clipboard - August 17, 2021 8:38 AM

LeslytH (Tue, 17 Aug 2021 06:39:52 GMT):
This part seems similar to what I want. Updated properties which are timestamped with the organization/agent who changed the the properties of that product.

LeslytH (Tue, 17 Aug 2021 07:45:17 GMT):
I would like to try to add additional attributes to my products besides GDSN 3.1 attributes. But it is not working... I am following https://grid.hyperledger.org/docs/0.3/creating_products_with_nonstandard_attrs.html word for word. I do not get an error. The product gets added successfully but when I am opening the .xml file of the product in the UI it is only the GDSN 3.1 xml attributes

LeslytH (Tue, 17 Aug 2021 07:48:08 GMT):

Clipboard - August 17, 2021 9:48 AM

LeslytH (Tue, 17 Aug 2021 09:54:14 GMT):

Clipboard - August 17, 2021 11:54 AM

LeslytH (Tue, 17 Aug 2021 09:55:42 GMT):
This is the error i get. But I already have the following permissions set

LeslytH (Tue, 17 Aug 2021 09:55:43 GMT):

Clipboard - August 17, 2021 11:55 AM

LeslytH (Tue, 17 Aug 2021 11:11:11 GMT):
@dplumb , You are one of the most active people on here. Is it possible you might help me with my questions when both of us are online? I am myself in UTC +2 at the moment. Which one are you? Or other active people who would like to help me? That way I can come online when you are active so that I can properly ask questions and troubleshooting will not take multiple days.

LeslytH (Tue, 17 Aug 2021 12:18:00 GMT):
If I can finish my PoC I have to document every detail for my assignment so it might be a good additional tutorial which I can add to the Hyperledger Grid documentation or something

dplumb (Tue, 17 Aug 2021 13:53:58 GMT):
Sounds good I'll DM you

septcinquante (Tue, 24 Aug 2021 16:02:16 GMT):
hello can someone explain the relation beetween the schema.yaml and the product.xml , where i can find a very simple file for product ? i'm testing grid with this schema ` name: gs1_product3 description: GS1 product schema owner: septCinquante properties: - name: GDSN_3_1 data_type: STRING description: str containing GDSN 3.1 Trade Item product definition in XML required: true` Now how to write a product file, there is directly the posibility to add product in CLI without file ? thanks for your help

LeslytH (Wed, 25 Aug 2021 06:31:38 GMT):
Well the example file is downlaodable ro mthe documentation

LeslytH (Wed, 25 Aug 2021 06:31:40 GMT):

Clipboard - August 25, 2021 8:31 AM

LeslytH (Wed, 25 Aug 2021 06:31:47 GMT):
https://grid.hyperledger.org/docs/0.2/creating_products.html

LeslytH (Wed, 25 Aug 2021 06:32:26 GMT):
Here you can download an example .xml

LeslytH (Wed, 25 Aug 2021 06:34:10 GMT):
And about adding a product directly without using a file. i think you want to make a new file instead of import a file from outside the gridd nodes right?

LeslytH (Wed, 25 Aug 2021 06:37:46 GMT):
IIRC you can not make a new files in those docker machines. But if you want to make a new file in Linux/ubuntu you could use the following command: sudo nano new_Product_Name.xml This makes a new file in Linux wherein you can add the properties. But I would use the product.xml as a template and continue with that. Or make your own custom schema wherein the most important GDSN product data is also in there.

LeslytH (Wed, 25 Aug 2021 06:41:20 GMT):
And make a .YAML product

LeslytH (Wed, 25 Aug 2021 06:41:36 GMT):
https://grid.hyperledger.org/docs/0.2/creating_products_with_nonstandard_attrs.html

septcinquante (Wed, 25 Aug 2021 07:55:40 GMT):
Hello , thanks for your help I will study this. Just a confirmation, the schema is the template for a product so my product.xml must match exactly my schema isn't it ? From my shema (see prev post ) how to create products ? Sorry i'm a newbies , i'm not yet ready with grid Many thanks

septcinquante (Wed, 25 Aug 2021 07:55:40 GMT):
Hello , thanks for your help I will study this. Just a confirmation, the schema is the template for a product so my product.xml must match exactly my schema isn't it ? From my shema (see prev post ) how to create product.xml and add products to grid ? Sorry i'm a newbies , i'm not yet ready with grid Many thanks

LeslytH (Wed, 25 Aug 2021 07:56:35 GMT):
Hi! I am also new to Grid so my information might be of a little bit

LeslytH (Wed, 25 Aug 2021 07:56:48 GMT):
off*

septcinquante (Wed, 25 Aug 2021 07:57:10 GMT):
:slight_smile:

septcinquante (Wed, 25 Aug 2021 07:57:35 GMT):
have you succes with add a new product ?

LeslytH (Wed, 25 Aug 2021 07:58:05 GMT):
Yeah. In your schema you define certain things like which properties you want to use. In this case the GDSN 3.1 properties. And within the product.xml you are able to change things a little bit for testing purposes

LeslytH (Wed, 25 Aug 2021 07:58:20 GMT):
However. The GTIN number is very strict

LeslytH (Wed, 25 Aug 2021 07:58:25 GMT):
You need to be aware of that

septcinquante (Wed, 25 Aug 2021 07:58:42 GMT):
ok , so the schema is not the product template like i mean ?

LeslytH (Wed, 25 Aug 2021 07:58:46 GMT):
And I have had some successes with adding products

LeslytH (Wed, 25 Aug 2021 07:58:54 GMT):
The schema is the template

LeslytH (Wed, 25 Aug 2021 07:59:05 GMT):
I meant hte product.xml example

LeslytH (Wed, 25 Aug 2021 07:59:24 GMT):
I am goign in a meeting now. I will continue talking later ok?

septcinquante (Wed, 25 Aug 2021 07:59:46 GMT):
ok thanks i will explore more , stay in touch

LeslytH (Wed, 25 Aug 2021 08:00:15 GMT):
:thumbsup:

LeslytH (Wed, 25 Aug 2021 08:32:22 GMT):
I am back

LeslytH (Wed, 25 Aug 2021 08:32:25 GMT):
How is it going?

LeslytH (Wed, 25 Aug 2021 08:42:28 GMT):
And copy the product file to the gridd node and create/update the product

septcinquante (Wed, 25 Aug 2021 13:51:31 GMT):
sorry i was on another dev , i wiil check it tommorow I keep you posted

LeslytH (Wed, 25 Aug 2021 13:52:00 GMT):
:thumbsup:

LeslytH (Thu, 26 Aug 2021 16:32:56 GMT):
Hi! I got some issues/ questions about Hyperledger grid. I hope someone might answer them for me :) I have put it in a Word Document to keep it a little bit clean and added screenshots.

LeslytH (Thu, 26 Aug 2021 16:33:18 GMT):

Questions Hyperledger Grid.docx

satelander (Thu, 26 Aug 2021 21:06:35 GMT):
Hey @LeslytH! I've taken a look at your questions so I'll answer them in the order from your document

satelander (Thu, 26 Aug 2021 21:06:49 GMT):
1. You should be able to see a “submitter” field on the transaction, which would enable you to search the agent that submitted the transaction. Therefore, you’d be able to find the organization that made which update.

satelander (Thu, 26 Aug 2021 21:06:58 GMT):
2. If the product you originally made did not have a “properties” defined, this error might be returned.

satelander (Thu, 26 Aug 2021 21:07:07 GMT):
3. Yes, once again each transaction should have a “submitter” or “public_key" field within the transaction header, which would give you the submitting agent’s public key. You’d be able to find the transaction header within logs or within the database. For example, you can also find this value in the “transactions” table in the Grid DB, the “signer_public_key” column is semantically equivalent to the submitter of the transaction.

satelander (Thu, 26 Aug 2021 21:08:02 GMT):
4. Need to think and ask some questions for this one, will report back.

satelander (Thu, 26 Aug 2021 21:08:16 GMT):
5. You can look at the “Using Pike” doc on the Grid website, located here: https://grid.hyperledger.org/docs/0.2/using_pike.html, in the “Delegation of Roles Between Organizations” section. Pike does support role permissions across organizations. Therefore, as long as you give each agent the correct permissions (with the correct “allowed_organizations”)

satelander (Thu, 26 Aug 2021 21:09:26 GMT):
Let me know if you have any more questions from this

dplumb (Thu, 26 Aug 2021 21:54:28 GMT):
```TnT & product catalog properties How can I implement these properties? If not yet? When Is it possible? Especially the mention of historical data under header Properties (link) is very interesting.``` Track and Trace was a sort of example app that predated Grid and was later incorporated into it. It doesnt follow all of the same design principles of modern Grid features like Product, Pike, Location (Not standards based, has a slightly larger scope, not fully built in Rust, etc). Due to that it is currently considered an experimental feature and may not be compatible with the current version of Grid. But it could definitely be updated to work with Grid if someone had a usecase for it. The API and some other functionality is in the grid-contrib repo: https://github.com/hyperledger/grid-contrib/tree/main/track_and_trace

dplumb (Thu, 26 Aug 2021 22:00:27 GMT):
I believe the historical data views were implemented via queries against the slowly changing dimensions fields in the database (tracking which data was relevant at a specific commit/block ID). The Grid REST API doesnt currently support that but it could probably be added.

LeslytH (Fri, 27 Aug 2021 12:29:01 GMT):
[ ](https://chat.hyperledger.org/channel/grid?msg=KrKJxNH2Pn2uCpnZb) Thank you for your response!

LeslytH (Fri, 27 Aug 2021 12:29:12 GMT):
[ ](https://chat.hyperledger.org/channel/grid?msg=PAoeqHhnC8SNgeHMQ) Also thank you for your response

LeslytH (Fri, 27 Aug 2021 12:29:13 GMT):
!

LeslytH (Fri, 27 Aug 2021 12:29:19 GMT):
Really appreciate your time and help!

LeslytH (Fri, 27 Aug 2021 12:31:59 GMT):
I now have a greater understanding of it all. Also that track and trace contrib POC is very interesting! You should have added a reference to it in the documentation of hyperledger grid so that people get a proper idea of how it works.

LeslytH (Fri, 27 Aug 2021 12:34:56 GMT):
I am now installing hyperledger grid on Azure in ubuntu 20.04 and will now work to a showable POC/demo for my company where i am doing my assignment for. Later this day I will probably have some more questions which i anticipate that I get when showing my POC. So I will ask them here in advance so that I am armed with the right knowledge haha!

LeslytH (Fri, 27 Aug 2021 17:24:07 GMT):
Okay, first questions haha! When trying to make multiple Schemas. It was not possible to have multiple schemas active in one circuit right? So I have to make multiple circuits for multiple schemas? It is not possible to delete a circuit when i messed that one up right? Also, when i want to connect new nodes besides alpha, gamma and beta. How do I do that? I saw something at the SPlinter documentation. Is that applicable also for hyperledger Grid (splinter)?

LeslytH (Fri, 27 Aug 2021 17:25:33 GMT):
https://www.splinter.dev/docs/0.4/concepts/splinter_registry.html

LeslytH (Fri, 27 Aug 2021 17:26:08 GMT):
I want to try to connect a new node from my laptop to the azure environment

LeslytH (Fri, 27 Aug 2021 18:18:22 GMT):
Is there an ETA when Hyperledger Grid is ready for production?

LeslytH (Fri, 27 Aug 2021 18:19:37 GMT):

Clipboard - August 27, 2021 8:19 PM

LeslytH (Fri, 27 Aug 2021 18:19:38 GMT):
Okay, when i am making my own schema with my own products. I still get this error:

LeslytH (Fri, 27 Aug 2021 18:19:59 GMT):

Clipboard - August 27, 2021 8:19 PM

LeslytH (Fri, 27 Aug 2021 18:20:08 GMT):
This is the yaml file of the product

LeslytH (Fri, 27 Aug 2021 18:20:31 GMT):

Clipboard - August 27, 2021 8:20 PM

LeslytH (Fri, 27 Aug 2021 18:20:35 GMT):
This is the schema

LeslytH (Fri, 27 Aug 2021 19:03:08 GMT):
[ ](https://chat.hyperledger.org/channel/grid?msg=dnQmb3E2rcqJqx587) This is now not applicable because this is a new Grid installation with a new schema and a new product

LeslytH (Fri, 27 Aug 2021 19:21:11 GMT):
Okay never mind.

LeslytH (Fri, 27 Aug 2021 19:21:14 GMT):

Clipboard - August 27, 2021 9:21 PM

LeslytH (Fri, 27 Aug 2021 19:21:24 GMT):
When i put it like this it works fine :)

LeslytH (Fri, 27 Aug 2021 19:24:26 GMT):
i used a YAML lint to "tidy"it up. But that is not something you should do

LeslytH (Fri, 27 Aug 2021 20:04:48 GMT):
Okay.. now when I updated my schema. it is properly shown. And it works. But when I want to update the product with the new property called: Beschrijving product2" I get an error

LeslytH (Fri, 27 Aug 2021 20:04:52 GMT):

Clipboard - August 27, 2021 10:04 PM

LeslytH (Fri, 27 Aug 2021 20:05:04 GMT):
This is the product with the added porperty

LeslytH (Fri, 27 Aug 2021 20:05:47 GMT):
WHen I update it

LeslytH (Fri, 27 Aug 2021 20:05:52 GMT):

Clipboard - August 27, 2021 10:05 PM

satelander (Fri, 27 Aug 2021 20:57:49 GMT):
[ ](https://chat.hyperledger.org/channel/grid?msg=n2TXFdJv8iuBDdNPk) Alright, I'll try to answer a few of these questions. 1. Schemas must have unique names, but you are able to make multiple schemas on a single circuit. You do not need to make multiple circuits for multiple schemas. 2. Yeah, Grid running on Splinter v0.4 does not support circuit deletion. 3. You can find documentation for how to connect external nodes to a Splinter network on the Splinter site, specifically here: https://splinter.dev/docs/0.4/tutorials/configuring_splinter_nodes.html. If you are running the Splinter example, then the documentation would be useful.

LeslytH (Mon, 30 Aug 2021 06:23:15 GMT):
OKay thank you for explaining!

LeslytH (Mon, 30 Aug 2021 06:23:44 GMT):
And what about the: Erro: Field GTIN not found. Even when it is there

satelander (Mon, 30 Aug 2021 17:05:28 GMT):
@LeslytH No problem! As for the GTIN field error, I'll have to take a look around a little bit to find a solution there

LeslytH (Mon, 30 Aug 2021 18:14:00 GMT):
OKay thanks!

LeslytH (Mon, 30 Aug 2021 21:12:58 GMT):
@satelander , Do you already have an idea?

LeslytH (Mon, 30 Aug 2021 21:13:49 GMT):
Or maybe @dplumb ?

LeslytH (Mon, 30 Aug 2021 21:43:09 GMT):
Also some questions I am guaranteed that I get when demoing my PoC, Are there any use cases or examples of companies who are using Hyperledger Grid/Splinter as a demo or PoC? Is/will there be any support by a hyperledger team or Splinter team in Europe? So that when I/we need some help or support I/we don't need to wait till night (Our time) before someone is online at your company. What is the release cycle of Hyperledger grid/Splinter? Every 2 months a new release or something? Also for which company is the (core) Grid team working for? Splinter is developed by Cargill. But what about Grid?

LeslytH (Mon, 30 Aug 2021 23:13:05 GMT):
Also, whenever a new stable version of Splinter is released. How long does it take before the new splinter version is also available/utilised by the grid team?

dplumb (Tue, 31 Aug 2021 11:51:11 GMT):
In this case the `product_id` should be the GTIN instead of that coming from your schema (see the example product for example). That may have caused the issue

dplumb (Tue, 31 Aug 2021 11:53:28 GMT):
There are folks who are using it in a PoC sense but not everyone is publicly contributing yet. You can check the maintainers to see that there are folks from quite a few orgs contributing.

dplumb (Tue, 31 Aug 2021 11:53:52 GMT):
Currently there is no official support team. It is still a very early project. No plans for that at the moment

dplumb (Tue, 31 Aug 2021 11:55:07 GMT):
Splinter releases weekly. Right now Grid releases when we have something to release, but we are trying to get that to be more stable.

dplumb (Tue, 31 Aug 2021 11:55:38 GMT):
Most of the active Grid devs are also at Cargill but there are also significant contributions from Target and a few others

dplumb (Tue, 31 Aug 2021 11:57:54 GMT):
Grid tries to use the stable version of splinter (so not necessarily the weekly release). One of our efforts right now is on compatibility with the dev version of Splinter so we can switch to 0.6 when it comes out.

LeslytH (Tue, 31 Aug 2021 14:29:14 GMT):
With that product ID. That is dumb on my part haha

LeslytH (Tue, 31 Aug 2021 14:29:22 GMT):
Thanks for the rest of the info

LeslytH (Tue, 31 Aug 2021 14:30:22 GMT):
Now i noticed after i gracefully stop hyperledger grid in my azure vm. It does not remember my settings... So I have to start again...

LeslytH (Tue, 31 Aug 2021 14:30:51 GMT):
Are there any ports that I have to have open so that data between the docker containers go okay?

LeslytH (Tue, 31 Aug 2021 14:33:30 GMT):
On my local machine everything went well after ctrl + C ing the application.

LeslytH (Tue, 31 Aug 2021 14:41:57 GMT):
In about an hour I can properly look into it again and share some screenshots

LeslytH (Tue, 31 Aug 2021 18:36:45 GMT):
I am trying to make a schema. But I get the following erro splinterd-alpha | [2021-08-31 18:30:39.848] T["StaticExecutionAdapter"] DEBUG [transact::execution::adapter::static_adapter] Executing TransactionPair { transaction: Transaction {header_signature: "30835d00b6eb76a8c0d05a41f5c4ea5802d5c969a6ade0fce7d96f6b4a89d2da3f1aae864d4d057ef133e431976cb926de2c5d5f77ee64cc1cb232410e287d5b", header: <819 bytes>, payload: <761 bytes> }, header: TransactionHeader{ family_name: "sabre", family_version: "0.5", inputs: ["00ec01f350b88222eee9efe5ba3ab4499872ba1c0d9985ab89b75f7bb42409b6c64566", "00ec02fdac2d44097bf0849ee666c2da09707df9a1b7d558f12cd9c257998ffa6d5e84", "00ec00ebfd680ea8abffc272049e01409cda9efec943f4ddca0263897e715913a04705", "00ec00ebfd680ea8abffc272049e01409cda9efec943f4ddca0263897e715913a04705", "621dee05", "621dee01"]outputs: ["00ec01f350b88222eee9efe5ba3ab4499872ba1c0d9985ab89b75f7bb42409b6c64566", "00ec02fdac2d44097bf0849ee666c2da09707df9a1b7d558f12cd9c257998ffa6d5e84", "00ec00ebfd680ea8abffc272049e01409cda9efec943f4ddca0263897e715913a04705", "621dee01"]signer_public_key: "036186fec44a09d123691df6ca1f8b841968b823d5014fd75ea38e1049225d6d8a", payload_hash: "a6326c8c43e8d614dddb76d7f51765239bfb4fc08b7c4ccc0aec61a09764eafd954df8ba1b1ac34164c7b91d7a264ead3ac653dfc912041c8212f4d7c4a32841", payload_hash_method: SHA512, nonce: "30313030" } } in context [77, 237, 45, 59, 5, 206, 69, 50, 172, 169, 230, 18, 2, 114, 191, 66] splinterd-alpha | [2021-08-31 18:30:39.848] T["StaticExecutionAdapter"] INFO [sawtooth_sabre::handler] Action: Execute Contract ["00ec01f350b88222eee9efe5ba3ab4499872ba1c0d9985ab89b75f7bb42409b6c64566", "00ec02fdac2d44097bf0849ee666c2da09707df9a1b7d558f12cd9c257998ffa6d5e84", "00ec00ebfd680ea8abffc272049e01409cda9efec943f4ddca0263897e715913a04705", "00ec00ebfd680ea8abffc272049e01409cda9efec943f4ddca0263897e715913a04705", "621dee05", "621dee01"] ["00ec01f350b88222eee9efe5ba3ab4499872ba1c0d9985ab89b75f7bb42409b6c64566", "00ec02fdac2d44097bf0849ee666c2da09707df9a1b7d558f12cd9c257998ffa6d5e84", "00ec00ebfd680ea8abffc272049e01409cda9efec943f4ddca0263897e715913a04705", "621dee01"] splinterd-alpha | [2021-08-31 18:30:39.849] T["consensus-gsAA"] ERROR [splinter::consensus::two_phase] Error while creating proposal: proposal manager error occurred: scabbard state error: transaction failed: "Contract does not exist: grid_schema, 2" gridd-alpha | WARN [grid_sdk::rest_api::actix_web_3::routes::schemas] No Protocol version specified, defaulting to version 1

LeslytH (Tue, 31 Aug 2021 18:37:19 GMT):

Clipboard - August 31, 2021 8:37 PM

LeslytH (Tue, 31 Aug 2021 18:37:44 GMT):

Clipboard - August 31, 2021 8:37 PM

LeslytH (Tue, 31 Aug 2021 18:38:53 GMT):
Also when trying to create an organization I get the same issue it seems

LeslytH (Tue, 31 Aug 2021 18:42:05 GMT):
I have two circuits

LeslytH (Tue, 31 Aug 2021 18:42:10 GMT):
SHould that make the difference?

LeslytH (Tue, 31 Aug 2021 19:48:32 GMT):
That was the difference. I started over and probably miscopied something

LeslytH (Tue, 31 Aug 2021 19:48:42 GMT):
Started over and now have 1 circuit and it works

LeslytH (Wed, 01 Sep 2021 06:58:31 GMT):
Whenever I try to make it work on a second splinter circuit. I get the following error:

LeslytH (Wed, 01 Sep 2021 06:58:33 GMT):

Clipboard - September 1, 2021 8:58 AM

LeslytH (Wed, 01 Sep 2021 06:58:45 GMT):
A second organization I mean

LeslytH (Wed, 01 Sep 2021 10:22:07 GMT):
I have one circuit with Alpha node and beta node And one with Alpha node and Gamma node

LeslytH (Wed, 01 Sep 2021 13:23:31 GMT):
splinter circuit list ID MANAGEMENT MEMBERS nvtTw-ikPRl grid2 alpha-node-000;gamma-node-000 vyBzC-AB28q grid alpha-node-000;beta-node-000

LeslytH (Wed, 01 Sep 2021 14:10:15 GMT):
OKay, I shut down the Grid application with CTRL + C But got the following error

LeslytH (Wed, 01 Sep 2021 14:10:17 GMT):

Clipboard - September 1, 2021 4:10 PM

LeslytH (Wed, 01 Sep 2021 14:11:10 GMT):
Tried agian and yet again. so I just restarted the Vm to make sure if I have everything and yet again. Everything gone..... What does that error mean and how can I fix it the next time?

septcinquante (Wed, 01 Sep 2021 15:56:21 GMT):
Hello with GRID on docker , if i don't wante use the GS1 schema , does i need to write a news smarts contracts for shema and product, for my POC the products are very particulary and i need to glue with the work rules. What is it the way to follow for get a custom product rule thanks

LeslytH (Wed, 01 Sep 2021 17:22:20 GMT):
[ ](https://chat.hyperledger.org/channel/grid?msg=zhAbLkkH23o58ttyk) https://grid.hyperledger.org/docs/0.2/creating_products_with_nonstandard_attrs.html

LeslytH (Wed, 01 Sep 2021 17:25:28 GMT):

Clipboard - September 1, 2021 7:25 PM

LeslytH (Wed, 01 Sep 2021 17:26:21 GMT):
THis is the schema

LeslytH (Wed, 01 Sep 2021 17:26:30 GMT):
Owner needs to be you as owner ofcourse

LeslytH (Wed, 01 Sep 2021 17:26:39 GMT):
Or a schema to be precise

LeslytH (Wed, 01 Sep 2021 17:26:42 GMT):

Clipboard - September 1, 2021 7:26 PM

LeslytH (Wed, 01 Sep 2021 17:26:55 GMT):
And this might be a product

LeslytH (Wed, 01 Sep 2021 17:27:11 GMT):
Keep in mind that the owner is the same

LeslytH (Wed, 01 Sep 2021 17:27:16 GMT):
as yours

LeslytH (Wed, 01 Sep 2021 17:27:44 GMT):
@septcinquante

LeslytH (Thu, 02 Sep 2021 07:49:09 GMT):
[ ](https://chat.hyperledger.org/channel/grid?msg=uw5xFSxXkuZfgo7zz) Now even with only one splinter circuit

LeslytH (Thu, 02 Sep 2021 07:55:06 GMT):
Now I am not even able to create a schema or organization on a new installation..

LeslytH (Thu, 02 Sep 2021 08:01:02 GMT):
Is it maybe an idea to have a troubleshooting page with per category (creating circuits, products, schemas, locations et.) the possible errors? So that people like the developers can keep developing instead of answering questions again and again they probably have see n10 times?

LeslytH (Thu, 02 Sep 2021 08:01:53 GMT):
Users are also quicker back on track and they don't get demotivated by the errors and having to wait untill developers are answerting our questions

septcinquante (Thu, 02 Sep 2021 08:32:41 GMT):
Hello @LeslytH thank for your help. This way is over the standard GS1 shema, but all required fields in GS1 must be fill, right ?

LeslytH (Thu, 02 Sep 2021 09:31:30 GMT):
If you do not want to use the GS1 properties you leave out the GS properties

LeslytH (Thu, 02 Sep 2021 09:31:33 GMT):
As in m,y example

LeslytH (Thu, 02 Sep 2021 09:32:17 GMT):
Do you want to add GS1 properties with additional properties?

septcinquante (Thu, 02 Sep 2021 09:39:07 GMT):
It's strange when create a product with no standard shema , i have an error with the GTIN number. I think that the CS1 shema is the base and we need to fill all required fields or my shema is not taken into consideration. i'm working sawtooth , i understand that you're working on splinter ...

LeslytH (Thu, 02 Sep 2021 10:15:16 GMT):
Could you send a screenshot how your schema looks?

LeslytH (Thu, 02 Sep 2021 10:15:19 GMT):
ANd your product?

LeslytH (Thu, 02 Sep 2021 13:51:07 GMT):
@septcinquante ?

satelander (Thu, 02 Sep 2021 14:06:21 GMT):
[ ](https://chat.hyperledger.org/channel/grid?msg=3XnwtLtL3WamwyZtG) Hi! Sorry for not getting back sooner, had some other tasks to finish up, but this specific issue is with Docker. I believe this happens when containers get stuck in an odd set-up. I would suggest running `docker system prune -a --volumes` and rebuilding (if attempting with Splinter) using the directions as they are explained here: https://grid.hyperledger.org/docs/0.2/grid_on_splinter.html, including pulling the images to ensure you are using the most up-to-date containers. This will hopefully help with funky docker setups that seem to happen when working with the same containers for awhile.

satelander (Thu, 02 Sep 2021 14:08:23 GMT):
New installation @LeslytH, did you remove all containers and rebuild as I suggested above?

satelander (Thu, 02 Sep 2021 14:08:36 GMT):
[ ](https://chat.hyperledger.org/channel/grid?msg=v8Z4rvKKAyrNrSx5D) In reference to this issue

LeslytH (Thu, 02 Sep 2021 14:19:02 GMT):
Yes, I am now installing everything again. So I will get bakc to you on it

LeslytH (Thu, 02 Sep 2021 14:20:01 GMT):
Did you have a look at my other issues? Those are at this point more pressing because I had to postpone my Demo because of the issue..

satelander (Thu, 02 Sep 2021 14:20:40 GMT):
Can you clarify which questions you're referring to?

LeslytH (Thu, 02 Sep 2021 14:31:20 GMT):
I also made a docker compose file for the splinter setup with persistent database volumes. I am not sure if people are interested in having their data persist after shutdown so that they can continue after a while

LeslytH (Thu, 02 Sep 2021 14:31:36 GMT):
[ ](https://chat.hyperledger.org/channel/grid?msg=v8Z4rvKKAyrNrSx5D) @satelander

LeslytH (Thu, 02 Sep 2021 14:32:02 GMT):
[ ](https://chat.hyperledger.org/channel/grid?msg=uw5xFSxXkuZfgo7zz) @satelander

LeslytH (Thu, 02 Sep 2021 14:34:43 GMT):
My workday is done for now. So I will be offline for an hour or two or so

LeslytH (Thu, 02 Sep 2021 14:35:03 GMT):
After that I will be online because I really want to have this fixed haha!

LeslytH (Thu, 02 Sep 2021 14:35:57 GMT):
Some additional information. I get the contract error when I try to create a location or schema

LeslytH (Thu, 02 Sep 2021 14:36:18 GMT):
Creating an agent went okay if I recall correctly

LeslytH (Thu, 02 Sep 2021 14:38:40 GMT):
I had this issue once when I had 3 circuits, 2 circuits and 1 circuit. So how that happened I am not sure. Maybe after docker compose up and down(ing) everything 20 times is killing my HG haha!

LeslytH (Thu, 02 Sep 2021 14:40:30 GMT):
IDEA: maybe make a docker-compose file available without the UI. They take a long time building and most of the time people (will) use the API I think

LeslytH (Thu, 02 Sep 2021 14:41:12 GMT):
I know it is easy to do yourself by deleting it out the current docker compose file. But maybe giving everyone the choice to have it included or excluded might be an idea?

satelander (Thu, 02 Sep 2021 14:47:03 GMT):
[ ](https://chat.hyperledger.org/channel/grid?msg=qwqiTbtZnZchkoENK) Yeah, a lot of the times running things up/down across a period of time (longer than a day), especially with Docker and its persistent state, can make you run into issues with Docker containers getting wonky.

satelander (Thu, 02 Sep 2021 14:49:58 GMT):
[ ](https://chat.hyperledger.org/channel/grid?msg=962PzF3EhnjPcXpAf) The UI is an integral part to our system, especially when attempting to demonstrate the current functionality of Grid, especially for non-technical Grid users that may not be comfortable using an API with Grid yet.

satelander (Thu, 02 Sep 2021 14:49:58 GMT):
[ ](https://chat.hyperledger.org/channel/grid?msg=962PzF3EhnjPcXpAf) The UI is an integral part to our system when attempting to demonstrate the current functionality of Grid, especially for non-technical Grid users that may not be comfortable using an API with Grid yet.

satelander (Thu, 02 Sep 2021 14:51:01 GMT):
You may remove the UI from the docker-compose file, or write your own docker-compose file without the UI which should be pretty simple based on our example.

LeslytH (Thu, 02 Sep 2021 16:07:03 GMT):
Okay thanks!

LeslytH (Thu, 02 Sep 2021 16:07:12 GMT):
Just tried again with a fresh installation

LeslytH (Thu, 02 Sep 2021 16:07:14 GMT):

Clipboard - September 2, 2021 6:07 PM

LeslytH (Thu, 02 Sep 2021 16:07:38 GMT):
Tried to create a organization

LeslytH (Thu, 02 Sep 2021 16:07:46 GMT):
@satelander

satelander (Thu, 02 Sep 2021 16:09:52 GMT):
@LeslytH Can I see more of the logs surrrounding this error? Just the error message doesn't give me quite enough info

LeslytH (Thu, 02 Sep 2021 16:10:55 GMT):
Ofcourse

LeslytH (Thu, 02 Sep 2021 16:11:04 GMT):

troubleshooting.txt

LeslytH (Thu, 02 Sep 2021 16:11:38 GMT):

Clipboard - September 2, 2021 6:11 PM

LeslytH (Thu, 02 Sep 2021 16:11:46 GMT):
And this is from in the gridd-alpha

satelander (Thu, 02 Sep 2021 16:15:17 GMT):
Which version of Grid are you running?

LeslytH (Thu, 02 Sep 2021 16:16:05 GMT):
I Am not sure. I do https git clone

LeslytH (Thu, 02 Sep 2021 16:16:08 GMT):

Clipboard - September 2, 2021 6:16 PM

LeslytH (Thu, 02 Sep 2021 16:16:20 GMT):
Does it automatically take the 0.3 version?

satelander (Thu, 02 Sep 2021 16:16:48 GMT):
Ok, you're using the development version of Grid, v0.3. Yes, cloning the repository from the "main" branch will give you that most up-to-date code from our repo

LeslytH (Thu, 02 Sep 2021 16:16:48 GMT):
How do I downlaod and build 0.2?

satelander (Thu, 02 Sep 2021 16:19:22 GMT):
Yes, 0.2 is our stable release (and maybe a better foundation for your PoC, as we are actively developing Grid 0.3) and I believe you can download the crate here: https://crates.io/crates/grid-sdk, otherwise if you are using GitHub, the 0-2 branch in our main repository is Grid v0.2. I believe you could fetch that remote branch (0-2) if you have already cloned the repo.

satelander (Thu, 02 Sep 2021 16:19:22 GMT):
Yes, 0.2 is our stable release (and maybe a better foundation for your PoC, as we are actively developing Grid 0.3) and I believe you can download the crate here: https://crates.io/crates/grid-sdk, otherwise if you are using GitHub, the 0-2 branch in our main repository is Grid v0.2. You could also fetch that remote branch (0-2) if you have already cloned the repo.

LeslytH (Thu, 02 Sep 2021 16:21:32 GMT):

Clipboard - September 2, 2021 6:21 PM

LeslytH (Thu, 02 Sep 2021 16:21:36 GMT):
This you mean?

satelander (Thu, 02 Sep 2021 16:22:40 GMT):
Yes!

satelander (Thu, 02 Sep 2021 16:22:48 GMT):
The clone link doesn't change

satelander (Thu, 02 Sep 2021 16:24:02 GMT):
But if you look here: https://www.atlassian.com/git/tutorials/syncing/git-fetch, you should be able to find out how to pull down that remote branch. Probably something like this: `git fetch `

LeslytH (Thu, 02 Sep 2021 16:26:09 GMT):
okay!

LeslytH (Thu, 02 Sep 2021 16:26:19 GMT):
Maybe add taht to the documentation or tutorial

LeslytH (Thu, 02 Sep 2021 16:26:40 GMT):
Because in the whole tutorial there is no mention how to go to a stable version.

LeslytH (Thu, 02 Sep 2021 16:26:51 GMT):
Or how to know when you are in a stable version

satelander (Thu, 02 Sep 2021 16:27:13 GMT):

Screen Shot 2021-09-02 at 11.27.08 AM.png

satelander (Thu, 02 Sep 2021 16:27:32 GMT):
The documentation tutorials are based on the stable release, and you can change which version of Grid's documentation you are viewing directly on the site

LeslytH (Thu, 02 Sep 2021 16:28:21 GMT):
Yes I know. I did that.

LeslytH (Thu, 02 Sep 2021 16:28:23 GMT):

Clipboard - September 2, 2021 6:28 PM

LeslytH (Thu, 02 Sep 2021 16:28:36 GMT):
But it says nothing about how to choose the 0.2 branch

LeslytH (Thu, 02 Sep 2021 16:28:55 GMT):
Just clone the github repository. And that is standard the dev one

satelander (Thu, 02 Sep 2021 16:29:34 GMT):
If you look at the "releases" section of the Grid website, you can see all of our stable releases, how to download those, and how to upgrade between stable versions: https://grid.hyperledger.org/releases/0.2/

LeslytH (Thu, 02 Sep 2021 16:32:27 GMT):
yes i went by that page a few times. However. It does not mention exactly how to get the 0.2 repository on my machine. Via github that is.

LeslytH (Thu, 02 Sep 2021 16:33:19 GMT):
I'll try the cargo.toml way

satelander (Thu, 02 Sep 2021 16:33:21 GMT):
Yep, I see that the link to the repo doesn't go to the release branches, which it should on the release page. We'll update those release documentation pages

satelander (Thu, 02 Sep 2021 16:34:16 GMT):
As the versions exist on Github, is individual branches within the Grid repository. If you want to run Grid 0.2, you need to pull down the 0-2 branch from Grid using the steps I mentioned earlier using git.

satelander (Thu, 02 Sep 2021 16:34:46 GMT):
At that point, your local version of Grid, at least on that branch, would be Grid 0.2

LeslytH (Thu, 02 Sep 2021 16:34:53 GMT):
ok ok

satelander (Thu, 02 Sep 2021 16:35:54 GMT):
I would also suggest pulling the images between removing them and rebuilding. Using this line from the walkthrough: `docker-compose -f examples/splinter/docker-compose.yaml pull generate-registry db-alpha scabbard-cli-alpha splinterd-alpha`

satelander (Thu, 02 Sep 2021 16:36:46 GMT):
Docker can get into weird states when left running for a long time and without rebuilding in between those long periods of time which may be the cause of some of your issues.

LeslytH (Thu, 02 Sep 2021 16:46:36 GMT):
Okay I will

LeslytH (Thu, 02 Sep 2021 16:46:38 GMT):
git clone -b 0-2 --single-branch https://github.com/hyperledger/grid.git

LeslytH (Thu, 02 Sep 2021 16:46:46 GMT):
I did this one

LeslytH (Thu, 02 Sep 2021 16:47:19 GMT):
Should also work right? (I am not a developer, just trying something for the PoC, So please bear with me)

LeslytH (Thu, 02 Sep 2021 16:47:43 GMT):
[ ](https://chat.hyperledger.org/channel/grid?msg=WGhBACi47NcmSy2Ze) I do not undertsand this one

LeslytH (Thu, 02 Sep 2021 16:49:08 GMT):
git fetch https://github.com/hyperledger/grid.git 0-2

LeslytH (Thu, 02 Sep 2021 16:49:20 GMT):
This will be it right?

LeslytH (Thu, 02 Sep 2021 16:50:39 GMT):
Nope it was not

LeslytH (Thu, 02 Sep 2021 16:51:31 GMT):
git clone -b 0-2 --single-branch https://github.com/hyperledger/grid.git I did this one. How can I verify if I succesfully downlaoded the 0.2 branch?

LeslytH (Thu, 02 Sep 2021 16:56:09 GMT):

Clipboard - September 2, 2021 6:56 PM

LeslytH (Thu, 02 Sep 2021 16:56:13 GMT):
I already know the answer

LeslytH (Thu, 02 Sep 2021 16:56:24 GMT):
Thanks @satelander for your time and patience!

LeslytH (Fri, 03 Sep 2021 07:14:20 GMT):
@satelander @dplumb okay, Now I am losing my mind... I deleted the whole grid map. Cloned the 0-2 branch. Started over. Have 1 circuit. trying to add an organization I get the same error again..

LeslytH (Fri, 03 Sep 2021 07:14:23 GMT):

Clipboard - September 3, 2021 9:14 AM

LeslytH (Fri, 03 Sep 2021 07:15:10 GMT):

troubleshooting.txt

septcinquante (Fri, 03 Sep 2021 07:21:26 GMT):
Hello @LeslytH Sorry for the delay i'm working intermittently on this project I prepare you a feedback

LeslytH (Fri, 03 Sep 2021 07:40:50 GMT):
I really need some help with this whenever someone who is able to help me is online:sweat_smile: .

LeslytH (Fri, 03 Sep 2021 10:07:59 GMT):
ok

LeslytH (Fri, 03 Sep 2021 11:19:30 GMT):
Tried again. Deleted everything. New build , pulled with the normal 0-2 docker-compose file. 1 Circuit

LeslytH (Fri, 03 Sep 2021 11:19:34 GMT):

Clipboard - September 3, 2021 1:19 PM

LeslytH (Fri, 03 Sep 2021 11:36:46 GMT):

Clipboard - September 3, 2021 1:36 PM

LeslytH (Fri, 03 Sep 2021 11:36:55 GMT):
From within the container

LeslytH (Fri, 03 Sep 2021 11:37:04 GMT):
splinterd-alpha container

dplumb (Fri, 03 Sep 2021 13:42:06 GMT):
Did you try `docker system prune --volumes` before rebuilding everything?

dplumb (Fri, 03 Sep 2021 13:42:23 GMT):
Not sure if you should have to but you may have something cached

dplumb (Fri, 03 Sep 2021 13:43:50 GMT):
If you want to just use the published images from 0-2, you can use `docker-compose -f examples/splinter/docker-compose-dockerhub.yaml up`

LeslytH (Fri, 03 Sep 2021 13:46:48 GMT):
I did the follwoing within Docker desktop

LeslytH (Fri, 03 Sep 2021 13:46:50 GMT):

Clipboard - September 3, 2021 3:46 PM

amundson (Fri, 03 Sep 2021 13:47:32 GMT):
you need to look further back in the output and see why pike didn't get loaded

LeslytH (Fri, 03 Sep 2021 13:50:56 GMT):
Only thing in the red what I can see is tha terror while creating proposal proposal error occured ..... Contract does not exist

LeslytH (Fri, 03 Sep 2021 13:51:24 GMT):
[ ](https://chat.hyperledger.org/channel/grid?msg=tvEsPLNrkJbQ92dtq) Here I had the whole bootup till the error documented

LeslytH (Fri, 03 Sep 2021 13:52:01 GMT):
[ ](https://chat.hyperledger.org/channel/grid?msg=MdSA6ErYozPXe4g3K) What is the difference between this one and the original one from the documentation?

LeslytH (Fri, 03 Sep 2021 13:52:05 GMT):
The version number?

LeslytH (Fri, 03 Sep 2021 13:57:56 GMT):
I will try the docker system prune command

LeslytH (Fri, 03 Sep 2021 13:58:02 GMT):
Then this

LeslytH (Fri, 03 Sep 2021 13:58:07 GMT):
And we will see again haha

satelander (Fri, 03 Sep 2021 14:00:21 GMT):
The `dockerhub` compose file utilizes pre-built images that you can find in the Grid 0.2 release page that I linked yesterday, here: https://grid.hyperledger.org/releases/0.2/download.html in the `Docker images` section

LeslytH (Fri, 03 Sep 2021 14:10:34 GMT):
Ok

LeslytH (Fri, 03 Sep 2021 14:10:42 GMT):
I did the dockerhub.yaml

LeslytH (Fri, 03 Sep 2021 14:10:51 GMT):
Now I get the follwoing error..

LeslytH (Fri, 03 Sep 2021 14:10:53 GMT):

Clipboard - September 3, 2021 4:10 PM

LeslytH (Fri, 03 Sep 2021 14:27:37 GMT):
??

LeslytH (Fri, 03 Sep 2021 14:36:44 GMT):
Deleted everything again. With docker prune

dplumb (Fri, 03 Sep 2021 14:36:49 GMT):
Ok

LeslytH (Fri, 03 Sep 2021 14:37:03 GMT):
I can get back to the dockerhub one

LeslytH (Fri, 03 Sep 2021 14:37:22 GMT):
Tell me what you want me to do for further troubleshooting

agunde (Fri, 03 Sep 2021 14:37:41 GMT):
looks like the docker hub file is still using 0.1 images

dplumb (Fri, 03 Sep 2021 14:37:52 GMT):
It looks like the dockerhub images on 0-2 are pointing to 0-1 images for some reason, we will get that updated. If you use the dockerhub images from main that will get you the right build

dplumb (Fri, 03 Sep 2021 14:38:06 GMT):
Even so, im not sure why your pike contract isnt loaded

LeslytH (Fri, 03 Sep 2021 14:38:20 GMT):
[ ](https://chat.hyperledger.org/channel/grid?msg=sahGQKRXnxEwGrseJ) Yes. this is really the issue

LeslytH (Fri, 03 Sep 2021 14:38:28 GMT):
I als odon't get it why/how

dplumb (Fri, 03 Sep 2021 14:38:46 GMT):
You were able to get past that before without issue right?

LeslytH (Fri, 03 Sep 2021 14:38:47 GMT):
i also went back to my wsl2 machine where it did work

LeslytH (Fri, 03 Sep 2021 14:38:50 GMT):
Yes

dplumb (Fri, 03 Sep 2021 14:38:52 GMT):
ah

dplumb (Fri, 03 Sep 2021 14:39:00 GMT):
Is your docker up to date?

LeslytH (Fri, 03 Sep 2021 14:39:01 GMT):
I had organizations, schemas

LeslytH (Fri, 03 Sep 2021 14:39:10 GMT):
Now nothing is working

LeslytH (Fri, 03 Sep 2021 14:39:19 GMT):
My docker desktop is up to date

LeslytH (Fri, 03 Sep 2021 14:39:39 GMT):
Am updating ubuntu now

LeslytH (Fri, 03 Sep 2021 14:40:15 GMT):
For my ubuntu there are no new updates related to my docker

LeslytH (Fri, 03 Sep 2021 14:41:41 GMT):
i don't know what your policy is about talking via teams? that way I can share my screen and quickly talk about what I should do next.

LeslytH (Fri, 03 Sep 2021 14:41:56 GMT):
[ ](https://chat.hyperledger.org/channel/grid?msg=mfFnWvHuSemmAmAEN) I can try this?

LeslytH (Fri, 03 Sep 2021 14:42:01 GMT):
should*

dplumb (Fri, 03 Sep 2021 15:09:23 GMT):
Yes I would recommend that

dplumb (Fri, 03 Sep 2021 15:10:37 GMT):
Im not sure what could cause that pike contract issue

dplumb (Fri, 03 Sep 2021 15:10:58 GMT):
But that should eliminate any issues with your build

LeslytH (Fri, 03 Sep 2021 15:10:59 GMT):
So clone the main repository and then use the dockerhub compose file intead of the normol compose file right?

LeslytH (Fri, 03 Sep 2021 15:11:02 GMT):
Just to be clear?

dplumb (Fri, 03 Sep 2021 15:11:22 GMT):
Yes

LeslytH (Fri, 03 Sep 2021 15:11:35 GMT):
Ok

LeslytH (Fri, 03 Sep 2021 15:12:01 GMT):
I am docker pruning everything, deleting everything from the Grid map and goign to clone main branch

dplumb (Fri, 03 Sep 2021 15:12:20 GMT):
Sounds good

LeslytH (Fri, 03 Sep 2021 15:12:53 GMT):
With this command I am cloning the repo

LeslytH (Fri, 03 Sep 2021 15:12:54 GMT):
git clone https://github.com/hyperledger/grid.git

LeslytH (Fri, 03 Sep 2021 15:13:46 GMT):
Sorry for being so thorough with explaining. Just want to be sure I dam not screwing sometthing up

LeslytH (Fri, 03 Sep 2021 15:14:22 GMT):
Just askin, but what are these for?

LeslytH (Fri, 03 Sep 2021 15:14:24 GMT):

Clipboard - September 3, 2021 5:14 PM

LeslytH (Fri, 03 Sep 2021 15:14:54 GMT):
In the mean time i will build and docker compose up the dockerhub one in the examples/splinter folder

LeslytH (Fri, 03 Sep 2021 15:16:17 GMT):

Clipboard - September 3, 2021 5:16 PM

LeslytH (Fri, 03 Sep 2021 15:16:18 GMT):
This stays the same right?

satelander (Fri, 03 Sep 2021 15:22:53 GMT):
[ ](https://chat.hyperledger.org/channel/grid?msg=KMNWYLfqoFrAkCT5p) I think the dockerhub images on main are also outdated, and will need to be updated

leebradley (Fri, 03 Sep 2021 15:47:28 GMT):
Has joined the channel.

LeslytH (Fri, 03 Sep 2021 16:07:45 GMT):
Is the main correct?

LeslytH (Fri, 03 Sep 2021 16:08:01 GMT):
Just relocated from location so I still have to build things

dplumb (Fri, 03 Sep 2021 16:25:14 GMT):
It looks like the update to those files did not get into main somehow

dplumb (Fri, 03 Sep 2021 16:25:16 GMT):
Sorry about that

dplumb (Fri, 03 Sep 2021 16:27:41 GMT):
Which one were you using before?

LeslytH (Fri, 03 Sep 2021 16:28:37 GMT):
first on the 0-2 branch both docker compose and dockerhub one

dplumb (Fri, 03 Sep 2021 16:28:49 GMT):
Which is the one that worked for you?

LeslytH (Fri, 03 Sep 2021 16:29:06 GMT):
Main branch and docker-compose worked for a while

LeslytH (Fri, 03 Sep 2021 16:29:11 GMT):
But now it does not

LeslytH (Fri, 03 Sep 2021 16:29:19 GMT):
IIRC

dplumb (Fri, 03 Sep 2021 16:29:21 GMT):
If you were using main, nothing should have changed to cause that issue with pike

dplumb (Fri, 03 Sep 2021 16:29:34 GMT):
so it may have been an intermittent issue

LeslytH (Fri, 03 Sep 2021 16:30:17 GMT):
ok ok? And what do you mean with that?

dplumb (Fri, 03 Sep 2021 16:32:00 GMT):
Something like your docker partition running out of space could cause an issue

LeslytH (Fri, 03 Sep 2021 16:33:21 GMT):
Ok

LeslytH (Fri, 03 Sep 2021 16:33:28 GMT):
So reinstall docker on Ubuntu?

LeslytH (Fri, 03 Sep 2021 16:39:06 GMT):
I just reinstall my whole ubuntu

LeslytH (Fri, 03 Sep 2021 16:39:40 GMT):
And try again with the main branch and normal docker compose

LeslytH (Fri, 03 Sep 2021 16:42:51 GMT):
[ ](https://chat.hyperledger.org/channel/grid?msg=5XkppFiB9PPvoygZQ) But I had this happen on my azure vm and also back on my WSL vm... So I am not sure what is happening then

LeslytH (Fri, 03 Sep 2021 16:48:51 GMT):

Clipboard - September 3, 2021 6:48 PM

LeslytH (Fri, 03 Sep 2021 16:49:18 GMT):
Building should also be done from the dockerhub file right?

LeslytH (Fri, 03 Sep 2021 16:49:39 GMT):
Not the regular compose, because I will up the containers from the dockerhub right?

LeslytH (Fri, 03 Sep 2021 16:52:15 GMT):

Clipboard - September 3, 2021 6:52 PM

LeslytH (Fri, 03 Sep 2021 16:52:18 GMT):
Nope doesn't work

LeslytH (Fri, 03 Sep 2021 16:52:25 GMT):
I will just do the regular build

satelander (Fri, 03 Sep 2021 16:54:57 GMT):
Yeah, the docker images that are pre-built won't get pulled down. The `--pull` command pulls down the most up-to-date image for that service, so since you are already using pre-built images with the `dockerhub` compose file, it won't affect anything

LeslytH (Fri, 03 Sep 2021 16:56:03 GMT):
ok ok

LeslytH (Fri, 03 Sep 2021 16:56:20 GMT):
Just a quick question in between. Am I the only one with this issue?

LeslytH (Fri, 03 Sep 2021 16:56:29 GMT):
I dont hear anyone else about it

satelander (Fri, 03 Sep 2021 17:02:29 GMT):
We do see this error every once in awhile, as it points out that the smart contracts Grid is trying to use have not been correctly loaded which may be due to a Docker issue, network issue, etc., but we do not encounter this error regularly in Grid.

LeslytH (Tue, 07 Sep 2021 07:05:51 GMT):
Ah okay! Well I also did a docker prune and tried everything again. But to no availl...

LeslytH (Tue, 07 Sep 2021 14:34:53 GMT):
How can I get something similar as Splinter Circuits working on Hyperledger Sawtooth? The idea of working with smaller groups within a bigger group really made running Grid on Splinter more preferable. But at the moment because I cannot get Grid working on Splinter I am going to try it on Sawtooth

rbuysse (Tue, 07 Sep 2021 16:36:40 GMT):
I have some PRs open that should address what's going on here. looks like the compose file is loading the v1 version of the contract. https://github.com/hyperledger/grid/pull/919

satelander (Tue, 07 Sep 2021 16:42:53 GMT):
As for the issue @LeslytH was encountering with Grid on Splinter and the "grid_pike, 2 contract not found" error, we realized the `circuit_management_type` needed to be set to `grid`, as it had been set to something else which wasn't allowing Grid to trigger loading the smart contracts to the created circuit. Going to clarify this point in the documentation for creating a Grid circuit on Splinter.

LeslytH (Tue, 07 Sep 2021 16:58:04 GMT):
Yes, starting up my laptop to confirm your assumptions @satelander

LeslytH (Tue, 07 Sep 2021 17:08:29 GMT):
WOOHOO!

LeslytH (Tue, 07 Sep 2021 17:08:31 GMT):

Clipboard - September 7, 2021 7:08 PM

LeslytH (Tue, 07 Sep 2021 17:11:16 GMT):
[ ](https://chat.hyperledger.org/channel/grid?msg=fDcE5Lhyb2Sdfucb6) This was indeed the issue! I thought that the text: "grid" was a placeholdername for the circuits. Earlier I only made one circuit and just days before my demo I made multiple changes and added circuits and some other things. But I was pretty sure that management type Grid was okay If I renamed it so I did not bother

LeslytH (Tue, 07 Sep 2021 17:38:36 GMT):
Now the normal questions are back haha

LeslytH (Tue, 07 Sep 2021 17:38:39 GMT):

Clipboard - September 7, 2021 7:38 PM

LeslytH (Tue, 07 Sep 2021 17:39:06 GMT):
How can I properly use this API command?

LeslytH (Tue, 07 Sep 2021 17:40:06 GMT):
When I copy the following and paste it into my Postman

LeslytH (Tue, 07 Sep 2021 17:40:08 GMT):

Clipboard - September 7, 2021 7:40 PM

LeslytH (Tue, 07 Sep 2021 17:40:12 GMT):
The ID part

LeslytH (Tue, 07 Sep 2021 17:40:53 GMT):

Clipboard - September 7, 2021 7:40 PM

LeslytH (Wed, 08 Sep 2021 12:51:15 GMT):
Okay, whenever I have multiple circuits. the error about Contrct does not exist. I want to have a circuit with node alpha, beta and gamma. Alpha and beta Alpha and gamma. However I get the mentioned error. Started over with only one circuit (and management on grid :P) and it works properly

LeslytH (Wed, 08 Sep 2021 12:52:20 GMT):
I use the following splinter circuit proposes per circuit: Creating splinter circuits Circuit Alpha and Beta splinter circuit propose \ --key /registry/alpha.priv \ --url http://splinterd-alpha:8085 \ --node alpha-node-000::tcps://splinterd-alpha:8044 \ --node beta-node-000::tcps://splinterd-beta:8044 \ --service gsAA::alpha-node-000 \ --service gsBB::beta-node-000 \ --service-type *::scabbard \ --management grid \ --service-arg *::admin_keys=$(cat gridd.pub) \ --service-peer-group gsAA,gsBB Circuit Alpha and Gamma splinter circuit propose \ --key /registry/alpha.priv \ --url http://splinterd-alpha:8085 \ --node alpha-node-000::tcps://splinterd-alpha:8044 \ --node gamma-node-000::tcps://splinterd-gamma:8044 \ --service gsAA::alpha-node-000 \ --service gsCC::gamma-node-000 \ --service-type *::scabbard \ --management grid \ --service-arg *::admin_keys=$(cat gridd.pub) \ --service-peer-group gsAA,gsCC Circuit Alpha. Beta and Gamma splinter circuit propose \ --key /registry/alpha.priv \ --url http://splinterd-alpha:8085 \ --node alpha-node-000::tcps://splinterd-alpha:8044 \ --node beta-node-000::tcps://splinterd-beta:8044 \ --node gamma-node-000::tcps://splinterd-gamma:8044 \ --service gsAA::alpha-node-000 \ --service gsBB::beta-node-000 \ --service gsCC::gamma-node-000 \ --service-type *::scabbard \ --management grid \ --service-arg *::admin_keys=$(cat gridd.pub) \ --service-peer-group gsAA,gsBB,gsCC

satelander (Thu, 09 Sep 2021 15:55:46 GMT):
Hey @LeslytH, testing out with a 3-party circuit locally, we're able to make an organization. Is this specifically happening on a 3-party circuit, or when you have multiple circuits running?

LeslytH (Thu, 16 Sep 2021 06:18:53 GMT):
@satelander Sorry for the late reply! I just returned from my vacation!

LeslytH (Thu, 16 Sep 2021 06:19:31 GMT):
Happens both ways. When I have Alpha & Beta, Alpha & Gamma and/or Alpha, Beta & Gamma

igorkrupczynski (Thu, 16 Sep 2021 10:13:13 GMT):
Has joined the channel.

LeslytH (Tue, 21 Sep 2021 06:41:13 GMT):
Is everyone on a vacation or something?

fishnexj (Wed, 22 Sep 2021 01:39:17 GMT):
@amundson ^^

satelander (Wed, 22 Sep 2021 18:55:06 GMT):
@LeslytH (repeating this from a dm sent earlier) Since we were able to use a 3-party circuit to create an organization when we tested this scenario locally, I may need a little more info on what error you're running into, that is coming up in the logs when you attempt to create an organization

satelander (Wed, 22 Sep 2021 18:55:06 GMT):
@LeslytH (repeating this from a dm sent yesterday) Since we were able to use a 3-party circuit to create an organization when we tested this scenario locally, I may need a little more info on what error you're running into, that is coming up in the logs when you attempt to create an organization

LeslytH (Mon, 27 Sep 2021 07:45:52 GMT):
@satelander Yes, sorry yet again! Have not been very active on here since my showcase of the functionalities to my coworkers. I have been busy with other things surrounding Hyperledger Grid.

LeslytH (Mon, 27 Sep 2021 07:46:19 GMT):
I think in a week or two I will retry everything again and return here.

LeslytH (Mon, 27 Sep 2021 09:05:09 GMT):
But I do have a quick question about Grid/Splinter. The data is immutable and there can not be tampered with it. However we can delete products and schemas. But it should still be possible to find out which agent/organization deleted the product/schema right? In the logs of Splinter it should be seen. Also, how does HG comply with the GDPR rules in Europe? Especially the right to be forgotten? Could someone explain that to me with an example?

amundson (Mon, 27 Sep 2021 15:33:03 GMT):
@LeslytH how does GDPR apply?

LeslytH (Wed, 29 Sep 2021 15:18:31 GMT):
[ ](https://chat.hyperledger.org/channel/grid?msg=T2wtKHSfZ5JF64DbB) How do you mean? What is GDPR?

LeslytH (Wed, 29 Sep 2021 15:18:32 GMT):

Clipboard - September 29, 2021 5:18 PM

Daniela_Barbosa (Thu, 30 Sep 2021 14:34:19 GMT):
Has joined the channel.

Daniela_Barbosa (Thu, 30 Sep 2021 14:39:22 GMT):
@amundson can you share the Grid meeting URL?

Daniela_Barbosa (Thu, 30 Sep 2021 14:42:36 GMT):
For anyone else looking, this is using Microsoft Team instead of our standard zoom, but here it is lick here to join the meeting

Daniela_Barbosa (Thu, 30 Sep 2021 14:42:36 GMT):
For anyone else looking, this is using Microsoft Team instead of our standard zoom, but here it is link here to join the meeting

gusBar (Thu, 30 Sep 2021 15:47:34 GMT):
Hi... Can you share the presentation from Teams meeting just now?

amundson (Thu, 30 Sep 2021 22:18:01 GMT):
The video of the event should be up soon

LeslytH (Fri, 01 Oct 2021 12:39:46 GMT):
[ ](https://chat.hyperledger.org/channel/grid?msg=Dtfz2kpGG6W2KAZHu) Could someone else from the team answer my questions? For clarification: There is a rule in the GDPR which needs to be adhered to by businesses. And that is the right to be forgotten. So when an user requests to be deleted from the system. It should be possible to delete that person. But blockchain solutions like Splinter are immutable and blockchains are known for showing proof of every transaction

LeslytH (Fri, 01 Oct 2021 12:40:25 GMT):
So how does HG comply to the GDPR rule of the right to be forgotten?

amundson (Fri, 01 Oct 2021 13:27:02 GMT):
A few things: 1) the ledger we are currently using with splinter is scabbard; scabbard is a digital ledger but not a blockchain and doesn't have the immutability properties you are describing (the Sawtooth backend for Grid does have those properties though, so its still a relevant topic); 2) Grid currently doesn't directly store any personal data; 3) In Pike, Agents have permissions on behalf of organizations; Agents are identified by a public key which could be used by a person, a group of people (more than one person could have the key), or a system process (such as an integration component with another backend system); it is not necessarily possibly to determine who might be using the key without an additional mapping; likely that mapping would be local to the organization and not distributed

amundson (Fri, 01 Oct 2021 13:31:16 GMT):
In Splinter, there is a concept of a "user"; any of the user concepts there are local to an organization and do not intersect with the distributed ledger. For example, there is a feature which allows the REST API to store a key (such as the agent key) on behalf of a user (so if you login to a browser, you can retrieve an encrypted version of the key that you then use when interacting with the ledger). Since the user concept is not distributed, its just stored in the database and is very much a standard web app pattern (no immutability, etc.)

amundson (Fri, 01 Oct 2021 13:41:00 GMT):
That said, this is just a description of the pieces of grid that I think might be related to GDPR, but please understand I don't know much about GDPR

LeslytH (Fri, 01 Oct 2021 21:44:36 GMT):
Ah thanks! Yes that helps a lot!

fishnexj (Tue, 19 Oct 2021 03:21:20 GMT):
@gusBar sorry for the delay in updating you - here is the video for the September 30 Grid 0.2 Release Party: https://www.youtube.com/watch?v=wgVvkeKe8AM

david.liu (Thu, 21 Oct 2021 23:26:24 GMT):
Has joined the channel.

david.liu (Thu, 21 Oct 2021 23:26:25 GMT):
Hello, I am a ETH full stack developer and am currently looking into building Enterprise Supply Chain Blockchain software. I have a couple of questions for using Grid. 1. What development tools should be used? 2. How do I write a smart contract? Do I use Sawtooth or Splinter? or Both? What's the difference? 3. Is Grid production ready? When 0.3 releases, will it be backwards compatible?

david.liu (Thu, 21 Oct 2021 23:35:09 GMT):
also, I would like to create an tutorial article explaining how to use Grid for devs coming from ETH

JorgeLuisAcosta (Mon, 25 Oct 2021 07:01:23 GMT):
Has joined the channel.

leebradley (Tue, 26 Oct 2021 14:33:55 GMT):
@david.liu Hey! So here are some answers to your questions 1. You should be able to use any development tool that is compatible with Rust, but if I had to recommend something, maybe VS Code. Or if you're familiar with VIM, that works quite well!

leebradley (Tue, 26 Oct 2021 14:34:14 GMT):
2. You can write a smart contract in any language that compiles to WASM. To see how to write a smart contract, check out the Sabre guide here: https://sawtooth.hyperledger.org/docs/sabre/releases/latest/application_developer_guide.html and the Grid guide for uploading the smart contract https://grid.hyperledger.org/docs/0.2/uploading_smart_contracts.html

leebradley (Tue, 26 Oct 2021 14:34:27 GMT):
Splinter and Sawtooth have different use cases, with Splinter having the ability to manage splinter circuits where data is contained only to that circuit. Sawtooth is much more analogous to Ethereum's global visibility.

satelander (Tue, 26 Oct 2021 15:22:01 GMT):
Ok, I'll answer question 3: We are currently in the process of getting Grid ready for a production environment. When 0.3 releases, it will be backwards compatible with Grid 0.2.

satelander (Tue, 26 Oct 2021 15:22:01 GMT):
Ok, I'll answer question 3 @david.liu: We are currently in the process of getting Grid ready for a production environment. When 0.3 releases, it will be backwards compatible with Grid 0.2.

satelander (Wed, 17 Nov 2021 21:30:27 GMT):
Hi all, the Workflow RFC has entered final comment period after the motion to enter FCP passed earlier this year. Core team, please submit your reviews and approvals. Other reviews also remain welcome at this time. Thanks! https://github.com/hyperledger/grid-rfcs/pull/24#issuecomment-971813949

satelander (Mon, 29 Nov 2021 15:55:31 GMT):
Hi all, the Workflow RFC's final comment period has ended. Therefore, I propose a final vote for the Workflow RFC to be merged. Core team, please submit your reviews. https://github.com/hyperledger/grid-rfcs/pull/24

satelander (Wed, 08 Dec 2021 16:22:34 GMT):
Hi all, the Workflow RFC has been merged! https://github.com/hyperledger/grid-rfcs/blob/main/text/0024-workflows.md

peter_somogyvari (Mon, 13 Dec 2021 18:30:22 GMT):
Has joined the channel.

peter_somogyvari (Mon, 13 Dec 2021 18:30:22 GMT):
Hi All, quick question: would anyone from the Grid community be willing to help me by filling out a survey[1] for the TSC chat platform task force? I'm happy to do the typing if anyone would prefer to get on a call and just explain themselves instead of filling it out themselves. [1]: https://wiki.hyperledger.org/display/TF/Grid

amundson (Tue, 14 Dec 2021 15:05:03 GMT):
@peter_somogyvari I updated the survey with answers; these answers would generally apply to Sawtooth and Transact as well with the exception that those projects do not interact with non-engineer users as often.

peter_somogyvari (Tue, 14 Dec 2021 15:23:27 GMT):
@amundson Understood, thank you very much for taking the time to fill it out!

SeanBohan (Fri, 17 Dec 2021 20:03:06 GMT):
Has joined the channel.

LeslytH (Fri, 24 Dec 2021 11:50:49 GMT):
Hi everyone, SInce the attack of log4j a lot of things are banned at my qorganization until further notice. How did the log4j impact the docker images of Hyperledger (Grid)

amundson (Thu, 30 Dec 2021 17:03:07 GMT):
@LeslytH Grid doesn't use java, thus no log4j.

satelander (Tue, 18 Jan 2022 22:09:43 GMT):
Hi all, I propose the Purchase Order smart contract enter final comment period. Core subteam, please provide your vote: https://github.com/hyperledger/grid-rfcs/pull/25#issuecomment-1015876895

sbohanlf (Tue, 25 Jan 2022 15:21:00 GMT):
Has joined the channel.

satelander (Fri, 28 Jan 2022 15:51:40 GMT):
Hi all, the Purchase Order RFC has entered final comment period. Core team, please submit any final reviews. Other reviews also remain welcome at this time. Thanks! https://github.com/hyperledger/grid-rfcs/pull/25

cxk934 (Mon, 31 Jan 2022 16:21:41 GMT):
Has joined the channel.

cxk934 (Mon, 31 Jan 2022 16:21:42 GMT):
Greetings TeamGrid! We are evaluating Grid + Sawtooth, and are having issues with a "docker-compose build" in the grid repo. The build never seems to finish. "cargo build" natively on a new Apple M1 Mac works fine. We're interested in pushing this out to a test k8s environment. Anyone experience something similar?

cxk934 (Tue, 01 Feb 2022 14:49:54 GMT):
Took me a bit (and an Intel mac) to realize the obvious. This just won't work on an M1 because of the Sawtooth dependency on Intel chipsets.

rjones (Wed, 23 Mar 2022 17:35:31 GMT):