cbf (Wed, 01 Feb 2017 20:52:38 GMT):
Discussion of Hyperledger Fabric top level project
cbf (Wed, 01 Feb 2017 20:58:33 GMT):
Hyperledger Fabric discussion
rjones (Thu, 02 Feb 2017 08:35:46 GMT):
Has joined the channel.
cbf (Thu, 02 Feb 2017 16:59:22 GMT):
User User_1 added by cbf.
VipinB (Thu, 02 Feb 2017 17:19:42 GMT):
Has joined the channel.
vvnick (Thu, 02 Feb 2017 17:20:48 GMT):
Has joined the channel.
jimthematrix (Thu, 02 Feb 2017 17:25:08 GMT):
Has joined the channel.
C0rWin (Thu, 02 Feb 2017 17:29:01 GMT):
Has joined the channel.
markparz (Thu, 02 Feb 2017 17:32:57 GMT):
Has joined the channel.
nnao (Thu, 02 Feb 2017 17:33:04 GMT):
Has joined the channel.
yacovm (Thu, 02 Feb 2017 17:36:46 GMT):
Has joined the channel.
silliman (Thu, 02 Feb 2017 17:55:55 GMT):
Has joined the channel.
sstone1 (Thu, 02 Feb 2017 18:24:30 GMT):
Has joined the channel.
muralisr (Thu, 02 Feb 2017 18:33:40 GMT):
Has joined the channel.
jsmitchell (Thu, 02 Feb 2017 18:49:12 GMT):
Has joined the channel.
jyellick (Thu, 02 Feb 2017 19:14:29 GMT):
Has joined the channel.
markparz (Thu, 02 Feb 2017 19:58:43 GMT):
Here is the deck that Simon Stone @sstone1 presented today
sstone1 (Thu, 02 Feb 2017 20:01:02 GMT):
http://www.slideshare.net/SimonStone8/fabric-composer-construct-2017
sstone1 (Thu, 02 Feb 2017 20:01:20 GMT):
can't seem to upload pptx files
Ratnakar (Thu, 02 Feb 2017 20:08:00 GMT):
Has joined the channel.
kostas (Thu, 02 Feb 2017 20:47:13 GMT):
Has joined the channel.
lehors (Thu, 02 Feb 2017 21:00:25 GMT):
Has joined the channel.
sbrakev (Thu, 02 Feb 2017 22:16:13 GMT):
Has joined the channel.
timblankers (Thu, 02 Feb 2017 23:27:51 GMT):
Has joined the channel.
donjohnny (Thu, 02 Feb 2017 23:39:06 GMT):
Has joined the channel.
nickgaski (Thu, 02 Feb 2017 23:46:15 GMT):
Has joined the channel.
ashutosh_kumar (Fri, 03 Feb 2017 00:22:34 GMT):
Has joined the channel.
dave.enyeart (Fri, 03 Feb 2017 00:26:52 GMT):
Has joined the channel.
mastersingh24 (Fri, 03 Feb 2017 00:49:29 GMT):
Has joined the channel.
grapebaba (Fri, 03 Feb 2017 01:18:04 GMT):
Has joined the channel.
salmanbaset (Fri, 03 Feb 2017 01:18:34 GMT):
Has joined the channel.
JonathanTan (Fri, 03 Feb 2017 01:53:59 GMT):
Has joined the channel.
tuand (Fri, 03 Feb 2017 02:08:33 GMT):
Has joined the channel.
Donald Liu (Fri, 03 Feb 2017 02:16:01 GMT):
Has joined the channel.
didnotgetagoodname (Fri, 03 Feb 2017 03:55:35 GMT):
Has joined the channel.
rock_martin (Fri, 03 Feb 2017 05:21:16 GMT):
Has joined the channel.
harsha (Fri, 03 Feb 2017 05:27:38 GMT):
Has joined the channel.
dinesh.rivankar (Fri, 03 Feb 2017 06:50:34 GMT):
Has joined the channel.
frbrkoala (Fri, 03 Feb 2017 06:53:05 GMT):
Has joined the channel.
SriramaSharma (Fri, 03 Feb 2017 07:04:37 GMT):
Has joined the channel.
nvlasov (Fri, 03 Feb 2017 07:12:48 GMT):
Has joined the channel.
ryokawajp (Fri, 03 Feb 2017 07:49:14 GMT):
Has joined the channel.
cca88 (Fri, 03 Feb 2017 08:17:22 GMT):
Has joined the channel.
danacr (Fri, 03 Feb 2017 09:38:55 GMT):
Has joined the channel.
cdutra (Fri, 03 Feb 2017 11:20:53 GMT):
Has joined the channel.
mqmatt (Fri, 03 Feb 2017 11:35:01 GMT):
Has joined the channel.
jdockter (Fri, 03 Feb 2017 11:37:23 GMT):
Has joined the channel.
dante (Fri, 03 Feb 2017 13:10:07 GMT):
Has joined the channel.
wlahti (Fri, 03 Feb 2017 13:38:02 GMT):
Has joined the channel.
greg.haskins (Fri, 03 Feb 2017 14:18:34 GMT):
@rjones at earliest convenience, could you add "fabric-chaintool" tag to JIRA?
gormand (Fri, 03 Feb 2017 14:24:42 GMT):
Has joined the channel.
jeffgarratt (Fri, 03 Feb 2017 14:39:58 GMT):
Has joined the channel.
kletkeman (Fri, 03 Feb 2017 15:18:36 GMT):
Has joined the channel.
suryalanka (Fri, 03 Feb 2017 15:31:03 GMT):
Has joined the channel.
bbehlendorf (Fri, 03 Feb 2017 15:37:03 GMT):
Has joined the channel.
ssaddem (Fri, 03 Feb 2017 15:51:02 GMT):
Has joined the channel.
cdaughtr (Fri, 03 Feb 2017 16:25:39 GMT):
Has joined the channel.
mhagelstrom (Fri, 03 Feb 2017 16:55:14 GMT):
Has joined the channel.
rickr (Fri, 03 Feb 2017 17:31:56 GMT):
Has joined the channel.
rjones (Fri, 03 Feb 2017 17:46:35 GMT):
@greg.haskins a component or a tag?
rjones (Fri, 03 Feb 2017 17:58:19 GMT):
@greg.haskins I added it as a component
oiakovlev (Fri, 03 Feb 2017 19:25:07 GMT):
Has joined the channel.
fz (Fri, 03 Feb 2017 19:26:44 GMT):
Has joined the channel.
karkal (Fri, 03 Feb 2017 19:50:48 GMT):
Has joined the channel.
rocket.chat (Fri, 03 Feb 2017 20:10:15 GMT):
Has joined the channel.
rjones (Fri, 03 Feb 2017 20:10:56 GMT):
ping
clessor (Fri, 03 Feb 2017 20:11:17 GMT):
Has joined the channel.
rickr (Fri, 03 Feb 2017 20:11:33 GMT):
[ ](https://chat.hyperledger.org/channel/fabric?msg=slack-C0Y4PEU22-1486152663-003400) @conroydave linux foundation id
rjones (Fri, 03 Feb 2017 20:11:34 GMT):
https://identity.linuxfoundation.org/ sign up with your email address first, don't use a social login the first time
charlesbrandontheis (Fri, 03 Feb 2017 20:11:44 GMT):
Has joined the channel.
mwklein (Fri, 03 Feb 2017 20:20:44 GMT):
Has joined the channel.
dividovi2 (Fri, 03 Feb 2017 20:23:58 GMT):
Has joined the channel.
dwkrypto (Fri, 03 Feb 2017 20:30:06 GMT):
Has joined the channel.
conroydave (Fri, 03 Feb 2017 20:33:40 GMT):
Has joined the channel.
ecb (Fri, 03 Feb 2017 20:36:46 GMT):
Has joined the channel.
TonyT (Fri, 03 Feb 2017 20:41:45 GMT):
Has joined the channel.
arner (Fri, 03 Feb 2017 20:43:08 GMT):
Has joined the channel.
stanliberman (Fri, 03 Feb 2017 20:44:31 GMT):
Has joined the channel.
matanyahu (Fri, 03 Feb 2017 20:56:02 GMT):
I am trying to obtain information about an average transaction size for Fabric. I want to use it for comparison against Bitcoin and Ethereum. Does anyone know how big is a “clean” transaction?
mcoblenz (Fri, 03 Feb 2017 21:08:17 GMT):
Has joined the channel.
shannoncode (Fri, 03 Feb 2017 21:24:36 GMT):
I used to grab my history from slack and store it in airtable
rjones (Fri, 03 Feb 2017 21:35:52 GMT):
@shannoncode http://hyperledgerproject.slackarchive.io/ exists but it's a recent addition so a bunch of stuff is lost
shannoncode (Fri, 03 Feb 2017 21:35:52 GMT):
Has joined the channel.
Liqui (Fri, 03 Feb 2017 22:01:00 GMT):
Has joined the channel.
ericmvaughn (Fri, 03 Feb 2017 22:03:39 GMT):
Has joined the channel.
mdavid (Fri, 03 Feb 2017 22:07:28 GMT):
Has joined the channel.
greg.haskins (Fri, 03 Feb 2017 22:49:41 GMT):
@matanyahu at least on v0.6, they can be quite large
matanyahu (Fri, 03 Feb 2017 22:49:41 GMT):
Has joined the channel.
greg.haskins (Fri, 03 Feb 2017 22:50:24 GMT):
I dont have data in front of me, I but I think I have put transactions through that were over 130k each
greg.haskins (Fri, 03 Feb 2017 22:50:42 GMT):
not that I would advise this in all circumstances, but I have seen that
eddie.allen (Fri, 03 Feb 2017 22:54:02 GMT):
Has joined the channel.
matanyahu (Fri, 03 Feb 2017 23:01:21 GMT):
ok, thanks
dourada (Fri, 03 Feb 2017 23:24:22 GMT):
Has joined the channel.
changyu (Fri, 03 Feb 2017 23:43:32 GMT):
why not use irc like normal people
sachikoy (Fri, 03 Feb 2017 23:54:12 GMT):
Has joined the channel.
sachikoy (Fri, 03 Feb 2017 23:56:49 GMT):
Hi, I am looking for information about endorsement policy. How can I change the endorsement policy? How policy is specified, and what are the type of policy supported? (e.g., unanimous, x out of N, etc.)
dayubian (Sat, 04 Feb 2017 00:39:10 GMT):
Has joined the channel.
jiangyaoguo (Sat, 04 Feb 2017 01:30:43 GMT):
Has joined the channel.
sheehan (Sat, 04 Feb 2017 02:33:20 GMT):
Has joined the channel.
shimron (Sat, 04 Feb 2017 02:44:09 GMT):
Has joined the channel.
meraki (Sat, 04 Feb 2017 03:32:05 GMT):
Hello, What should the function `stub.GetCallerCertificate()` from the shim package supposed to return?How should it be used?
genggjh (Sat, 04 Feb 2017 03:34:26 GMT):
Has joined the channel.
sachikoy (Sat, 04 Feb 2017 03:38:04 GMT):
@meraki GetCallerCertificate() returns the certificate (i.e., Tcert) which is used to sign the transaction. Typically chaincode use this function to get security context of the transaction, and do access control.
meraki (Sat, 04 Feb 2017 03:38:04 GMT):
Has joined the channel.
guruprasath (Sat, 04 Feb 2017 06:11:26 GMT):
Has joined the channel.
bfuentes@fr.ibm.com (Sat, 04 Feb 2017 09:19:26 GMT):
Has joined the channel.
ruslan.kryukov (Sat, 04 Feb 2017 10:10:57 GMT):
Has joined the channel.
chungbd (Sat, 04 Feb 2017 11:27:04 GMT):
Has joined the channel.
sword_linux (Sat, 04 Feb 2017 11:28:40 GMT):
Has joined the channel.
yury (Sat, 04 Feb 2017 11:45:08 GMT):
Has joined the channel.
mastersingh24 (Sat, 04 Feb 2017 12:52:21 GMT):
@meraki - should return the certificate used to sign the transaction which was submitted to the peer
alacambra (Sat, 04 Feb 2017 15:53:11 GMT):
It is possible to fetch the state of a key on a given transaction? Or to get track of the values that a variable has had?
matanyahu (Sat, 04 Feb 2017 16:17:40 GMT):
I am currently testing tx performance on Fabric 0.6 with Example02 chaincode. I created a bash script that executes a loop chaincode invoke command for 1000 times. I copied that script on 4 nodes, deployed in a PBFT-compliant mode (4 VPs + 1 membership service node). Here are my results: *Avg. Txn Latency 45ms Transaction Rate 15 /sec Mining Rate 8blocks/sec* . Has anyone got anything better than that?
spiro (Sat, 04 Feb 2017 20:06:23 GMT):
Hello everyone, I've been trying to run a hyperledger setup in windows & linux. In windows using Docker-compose, my question is what are the commands/settings to register my chaincode? Ref https://hyperledger-fabric.readthedocs.io/en/latest/Setup/Chaincode-setup/#starting-and-registering-the-chaincode .
spiro (Sat, 04 Feb 2017 20:08:10 GMT):
In the linux environment, I'm able to start the chaincode, but I get an error about a Go package "context" that is missing, which causes failure?!
spiro (Sat, 04 Feb 2017 20:12:05 GMT):
Question what is missing from these set of instructions, its mean for UNIX/Linux, but using Windows Docker presents new problems when using a powershell/cmd prompt: https://hyperledger-fabric.readthedocs.io/en/latest/Setup/Chaincode-setup/#writing-building-and-running-chaincode-in-a-development-environment
matanyahu (Sat, 04 Feb 2017 20:17:17 GMT):
@spiro : the best way is to deploy a clean docker environment just by pulling stable images from docker hub
spiro (Sat, 04 Feb 2017 20:17:18 GMT):
Has joined the channel.
matanyahu (Sat, 04 Feb 2017 20:17:35 GMT):
then, execute docker-compose with a selected topology
matanyahu (Sat, 04 Feb 2017 20:18:05 GMT):
and then, log in to one of VPs and deploy chaincode either as REST API or with peer chaincode deploy command
matanyahu (Sat, 04 Feb 2017 20:18:22 GMT):
that's what I do and I do not use the newest master
matanyahu (Sat, 04 Feb 2017 20:19:12 GMT):
images from docker hub dating back from 3 months ago are fair enough for me, especially that I want to have an environment identical to the one used on IBM Bluemix (0.6.1)
matanyahu (Sat, 04 Feb 2017 20:19:35 GMT):
take a look at this
matanyahu (Sat, 04 Feb 2017 20:19:38 GMT):
https://github.com/yeasy/docker-compose-files/tree/master/hyperledger/0.6
spiro (Sat, 04 Feb 2017 20:22:44 GMT):
Okay , thank you - I forgot the virtual login part, very new to me.
spiro (Sat, 04 Feb 2017 20:24:47 GMT):
matanyahu: ok so I have to send the cmd: docker run vp0_1 for example
spiro (Sat, 04 Feb 2017 20:25:17 GMT):
Thanks for the links!
morgenhund (Sat, 04 Feb 2017 20:26:13 GMT):
matanyahu (Sat, 04 Feb 2017 20:27:13 GMT):
after you select your docker-compose topology and run your network
spiro (Sat, 04 Feb 2017 20:27:27 GMT):
I now assume "docker exec -it vp0_1 bash
matanyahu (Sat, 04 Feb 2017 20:27:29 GMT):
log in to one of your containers representing one of peers deployed by docker-compose sscript
matanyahu (Sat, 04 Feb 2017 20:28:11 GMT):
and then you can start sending commands locally (peer cmdlets or REST API curl cmdlets against 0.0.0.0:7050)
matanyahu (Sat, 04 Feb 2017 20:28:55 GMT):
or from your workstation you can send commands remotely if you know your containers ip addresses
spiro (Sat, 04 Feb 2017 20:29:05 GMT):
Cool
spiro (Sat, 04 Feb 2017 20:30:25 GMT):
Is their an English version?
spiro (Sat, 04 Feb 2017 20:42:36 GMT):
I was referring to the text
spiro (Sat, 04 Feb 2017 21:07:26 GMT):
It logged in finally-had to re-id the image, thank you
cbf (Sat, 04 Feb 2017 21:34:03 GMT):
@matanyahu pretty sure that we've seen better numbers than 45tps. @bmos299 leads a team that has been doing some of the performance and scale testing and some of these tests are being added into the master branch (they will work with current implementation, but not v0.6 unfortunately).
bmos299 (Sat, 04 Feb 2017 21:34:03 GMT):
Has joined the channel.
spiro (Sat, 04 Feb 2017 23:08:21 GMT):
So that means all go code editing/building will need to occur within the VM image...in progress. Any other ways (from Windows files)?
mastersingh24 (Sun, 05 Feb 2017 00:21:38 GMT):
@spiro - sorry for joining the conversation late here. Looks like you are trying to do everything with Windows? Which version of Windows? Also - are you solely interested in being able to "use" fabric (i.e. build and run chaincode, etc versus actually working on fabric code)?
mastersingh24 (Sun, 05 Feb 2017 00:22:10 GMT):
I primarily use OSX these days, but I do run the Docker images on Windows 10
sword_linux (Sun, 05 Feb 2017 01:13:39 GMT):
Hi everyone, I've been trying to run a hyperledger setup in GNU/Linux (Ubuntu). I see we have 2 options:
1) Use Vagrant.
2) Use Docker (docker-compose).
So i have some questions:
- Can i use only 1 peer node without membersrvc?
- Can i setup environment on normal VM, eg: AWS EC2? I used this tutorial https://github.com/hyperledger/fabric/blob/master/docs/dev-setup/devenv.md but it does not work.
- Can i use Rancher for setup environment?
jeffgarratt (Sun, 05 Feb 2017 02:56:41 GMT):
@spiro you can edit from your favorite Windows editor and build in linux
jeffgarratt (Sun, 05 Feb 2017 02:57:41 GMT):
when you use the vagrant environment, your git project is synced with the vagrant VM
jeffgarratt (Sun, 05 Feb 2017 02:57:58 GMT):
so you can edit from your host (Windows) and then build/run in vagrant VM
ray (Sun, 05 Feb 2017 08:41:52 GMT):
Has joined the channel.
patchpon (Sun, 05 Feb 2017 10:06:59 GMT):
Has joined the channel.
mandler (Sun, 05 Feb 2017 10:46:42 GMT):
Has joined the channel.
cbf (Sun, 05 Feb 2017 12:34:57 GMT):
@sword_linux trying to understand more about what you want to do. We have two versions of the Fabric, but the one currently under development is still lagging in the documentation department;-) That should be remedied by end of week.
cbf (Sun, 05 Feb 2017 12:36:00 GMT):
in the interim, you can use the published release: v0.6 and yes, it can be deployed to Amazon, though most people that have done this have not fully shared their config information.
cbf (Sun, 05 Feb 2017 12:36:34 GMT):
I would recommend that you visit the v0.6 starter kit and from there, transpose to AWS.
cbf (Sun, 05 Feb 2017 12:36:57 GMT):
http://hyperledger-fabric.readthedocs.io/en/v0.6/starter/fabric-starter-kit/
cbf (Sun, 05 Feb 2017 12:37:49 GMT):
note that you do not need to build anything, you simply need to deploy the published docker images.
jamescarlyle (Sun, 05 Feb 2017 12:45:09 GMT):
Has joined the channel.
rascal-3 (Sun, 05 Feb 2017 14:44:42 GMT):
Has joined the channel.
raj.nair (Sun, 05 Feb 2017 14:59:19 GMT):
Has joined the channel.
sword_linux (Sun, 05 Feb 2017 15:28:05 GMT):
@cbf thanks for your answer, let me try to deploy v0.6 to Amazon
schwentker2 (Sun, 05 Feb 2017 15:45:48 GMT):
Has joined the channel.
kkpatel (Sun, 05 Feb 2017 18:02:23 GMT):
Has joined the channel.
rjones (Sun, 05 Feb 2017 18:21:31 GMT):
@cbf: @greg.haskins: who are the maintainers (who has +2) for fabric-chaintool? fabric maintainers (which already contains greg.haskins and @muralisr) + Eric Baur?
rjones (Sun, 05 Feb 2017 18:36:40 GMT):
I've used the 2+2 rules for chaintool and added a layer of permissions: https://gerrit.hyperledger.org/r/#/admin/projects/fabric-chaintool,access it's easy to roll back if required (please note: github mirroring is not yet defined)
alacambra (Sun, 05 Feb 2017 19:22:57 GMT):
it is possible to get the actions and/or state of a key for some transaction on the ledger?
sibelius (Sun, 05 Feb 2017 20:08:15 GMT):
@aliblackwell our graphql + fabric boilerplate is open sourced: check it out here: https://github.com/entria/hyperledger-fabric-graphql-boilerplate
xixuejia (Mon, 06 Feb 2017 00:57:36 GMT):
Has joined the channel.
hanhzf (Mon, 06 Feb 2017 03:34:58 GMT):
Has joined the channel.
passkit (Mon, 06 Feb 2017 03:56:34 GMT):
Has joined the channel.
bryanhuang (Mon, 06 Feb 2017 04:29:14 GMT):
Has joined the channel.
kansi (Mon, 06 Feb 2017 05:10:23 GMT):
Has joined the channel.
baohua (Mon, 06 Feb 2017 06:12:17 GMT):
Has joined the channel.
Vadim (Mon, 06 Feb 2017 06:38:12 GMT):
Has joined the channel.
TakekiyoKubo (Mon, 06 Feb 2017 07:20:53 GMT):
Has joined the channel.
season7 (Mon, 06 Feb 2017 07:28:44 GMT):
Has joined the channel.
jojocheung (Mon, 06 Feb 2017 07:31:45 GMT):
Has joined the channel.
ibmamnt (Mon, 06 Feb 2017 07:49:42 GMT):
Has joined the channel.
kiewza (Mon, 06 Feb 2017 08:33:15 GMT):
Has joined the channel.
kiewza (Mon, 06 Feb 2017 08:33:26 GMT):
Hi, I'm using v0.6 with TLS enabled. after I enabled TLS, it seems I cannot access to PEER node via REST anymore although I installed the certificate on the browser. Is this the normal behavior? Could anyone suggest on this? Thanks
pd93 (Mon, 06 Feb 2017 08:51:25 GMT):
Has joined the channel.
david.peyronnin (Mon, 06 Feb 2017 09:47:34 GMT):
Has joined the channel.
meraki (Mon, 06 Feb 2017 09:52:17 GMT):
Hello, How to set StateDB to COuchDB while starting the peer?
rafael.turk (Mon, 06 Feb 2017 10:57:04 GMT):
Has joined the channel.
sibelius (Mon, 06 Feb 2017 10:57:04 GMT):
Has joined the channel.
rafael.turk (Mon, 06 Feb 2017 10:57:46 GMT):
@aliblackwell tks! Plan is to migrate this to V1 as soon as possible
naddison (Mon, 06 Feb 2017 11:22:59 GMT):
Has joined the channel.
mastersingh24 (Mon, 06 Feb 2017 11:40:01 GMT):
[ What error are you seeing?](https://chat.hyperledger.org/channel/fabric?msg=STzWw3KrADeW3HABo) @kiewza
maximus rus (Mon, 06 Feb 2017 11:59:40 GMT):
Has joined the channel.
ruslan.kryukov (Mon, 06 Feb 2017 12:04:08 GMT):
Who can help me with understanding envelop and transaction-id in blocks? Block contains header with a TxID field and also contains field Data which is represented as array of arrays of bytes. The array of bytes is envelop for the block. My Question sounds like that: Does TxID from the block relate to all envelops in the block or every single envelop has own txID which is already put in this envelop?
karnn (Mon, 06 Feb 2017 12:11:39 GMT):
I'm trying to get the hyper ledger boilerplate up and running but i'm getting the following error from the docker running the blockchain:
sibelius (Mon, 06 Feb 2017 12:16:55 GMT):
which boilerplate?
karnn (Mon, 06 Feb 2017 12:18:44 GMT):
https://github.com/IBM-Blockchain/fabric-boilerplate
sibelius (Mon, 06 Feb 2017 12:39:22 GMT):
try this one: https://github.com/entria/hyperledger-fabric-graphql-boilerplate
sibelius (Mon, 06 Feb 2017 12:39:30 GMT):
it is based on fabric-boilerplate
sibelius (Mon, 06 Feb 2017 12:39:35 GMT):
but it uses es6/7
karnn (Mon, 06 Feb 2017 12:46:05 GMT):
@mastersingh24 hey, could you please check out the errors i've been getting with running the boilerplate?
marcusvcs (Mon, 06 Feb 2017 12:58:30 GMT):
Has joined the channel.
denisglotov (Mon, 06 Feb 2017 13:25:12 GMT):
hi! Do the `membersrvc` need to be the only instance for the whole network (like in `dour-peer-ca.yaml` example)? Or may each node has its own copy of `membersrvc` provided they all have the same config?
mastersingh24 (Mon, 06 Feb 2017 13:43:01 GMT):
@denisglotov - assuming you are working with v0.6 then you can only really use a single instance of `membersrvc`. In v1.0, you can use multiple `fabric-ca` instances (fabric-ca replaces membersrvc)
denisglotov (Mon, 06 Feb 2017 13:43:01 GMT):
Has joined the channel.
karnn (Mon, 06 Feb 2017 13:48:34 GMT):
@sibelius i'll check it out once i figure out whats up with my setup. thanks.
ercw (Mon, 06 Feb 2017 14:15:05 GMT):
Has joined the channel.
ercw (Mon, 06 Feb 2017 14:17:04 GMT):
I'm trying to get a clear overview of how the consensus process works in Fabric but I'm not finding the answer to my question in the documentation. I am assuming nodes verify and sign blocks in a round-robin fashion? And that these signatures are counted by each nodes before adding a block to their own chain? Where can I get a detailed description of that process? Sorry if my assuming is completely off
mastersingh24 (Mon, 06 Feb 2017 14:22:42 GMT):
@ercw - I'd start with https://github.com/hyperledger/fabric/blob/master/proposals/r1/Next-Consensus-Architecture-Proposal.md
mastersingh24 (Mon, 06 Feb 2017 14:23:01 GMT):
(that's the basics for the V1.0 release - the stuff currently in master)
mastersingh24 (Mon, 06 Feb 2017 14:23:10 GMT):
v0.6 used a different design based on PBFT
ercw (Mon, 06 Feb 2017 14:26:31 GMT):
Thanks alot!
ercw (Mon, 06 Feb 2017 14:26:41 GMT):
I found the segment: "A peer collects CHECKPOINT messages until it obtains enough correctly signed messages with matching blockno, blocknohash and stateHash to establish a valid checkpoint (see Section 4.2.2.)." sound about right
mayerwa (Mon, 06 Feb 2017 14:30:43 GMT):
Has joined the channel.
tuand (Mon, 06 Feb 2017 14:44:04 GMT):
@ercw , re-ask over in https://chat.hyperledger.org
tuand (Mon, 06 Feb 2017 14:44:47 GMT):
oops... i see you did already nvm
ercw (Mon, 06 Feb 2017 14:44:57 GMT):
I am in both places :D will follow your advice in the future
cbf (Mon, 06 Feb 2017 14:47:40 GMT):
we have mirroring from slack->rocketchat
skarim (Mon, 06 Feb 2017 14:53:34 GMT):
Has joined the channel.
Jonas.Hedin (Mon, 06 Feb 2017 14:53:44 GMT):
Has joined the channel.
sukrit.handa@gmail.com (Mon, 06 Feb 2017 15:02:02 GMT):
Has joined the channel.
nhrishi (Mon, 06 Feb 2017 15:12:43 GMT):
Has joined the channel.
harrijk (Mon, 06 Feb 2017 15:13:03 GMT):
Has joined the channel.
john.d.sheehan (Mon, 06 Feb 2017 15:22:01 GMT):
Has joined the channel.
pd93 (Mon, 06 Feb 2017 15:34:42 GMT):
My docker logs are full of errors like this: `15:17:09.987 [peer] handleChat -> ERRO 036 Error handling message: Peer FSM cannot handle message (DISC_GET_PEERS) with payload size (0) while in state: created`. any ideas why?
DennisM330 (Mon, 06 Feb 2017 15:38:05 GMT):
Has joined the channel.
mastersingh24 (Mon, 06 Feb 2017 15:42:15 GMT):
@pd93 - there's an odd race condition that is really hard to reproduce which can cause this error to happen. You can cut down on the number of these messages by changing the following settings:
https://github.com/hyperledger/fabric/blob/v0.6/peer/core.yaml#L190
https://github.com/hyperledger/fabric/blob/v0.6/peer/core.yaml#L208
(just increase them to a higher value and make sure the second value is at least 1 larger than the first)
pd93 (Mon, 06 Feb 2017 15:42:52 GMT):
So nothing to actually worry about?
pd93 (Mon, 06 Feb 2017 15:42:52 GMT):
@mastersingh24 So nothing to actually worry about? or will this cause other issues?
klorenz (Mon, 06 Feb 2017 16:05:19 GMT):
Has joined the channel.
tzipih0 (Mon, 06 Feb 2017 16:38:15 GMT):
Has joined the channel.
yuki-kon (Mon, 06 Feb 2017 16:51:19 GMT):
Has joined the channel.
bravera (Mon, 06 Feb 2017 17:00:08 GMT):
Has joined the channel.
StevenLanders (Mon, 06 Feb 2017 17:25:15 GMT):
Has joined the channel.
Dsummers91 (Mon, 06 Feb 2017 17:33:55 GMT):
Has joined the channel.
deon (Mon, 06 Feb 2017 17:49:18 GMT):
Has joined the channel.
karan-bharadwaj (Mon, 06 Feb 2017 17:57:49 GMT):
Has joined the channel.
karan-bharadwaj (Mon, 06 Feb 2017 18:00:48 GMT):
i keep getting these errors when trying to get the fabric-boilerplate up '''
vp0_1 | 2017/02/06 12:07:46 transport: http2Server.HandleStreams failed to receive the preface from client: EOF
vp0_1 | 2017/02/06 12:07:46 grpc: Server.Serve failed to create ServerTransport: connection error: desc = "transport: write tcp 172.17.0.3:7051->172.17.0.1:49102: write: broken pipe"'''
karan-bharadwaj (Mon, 06 Feb 2017 18:00:48 GMT):
i keep getting these errors when trying to get the fabric-boilerplate up ```
vp0_1 | 2017/02/06 12:07:46 transport: http2Server.HandleStreams failed to receive the preface from client: EOF
vp0_1 | 2017/02/06 12:07:46 grpc: Server.Serve failed to create ServerTransport: connection error: desc = "transport: write tcp 172.17.0.3:7051->172.17.0.1:49102: write: broken pipe" ```
karan-bharadwaj (Mon, 06 Feb 2017 18:00:48 GMT):
i keep getting these errors when trying to get the fabric-boilerplate up ```
vp0_1 | 2017/02/06 12:07:46 transport: http2Server.HandleStreams failed to receive the preface from client: EOF
vp0_1 | 2017/02/06 12:07:46 grpc: Server.Serve failed to create ServerTransport: connection error: desc = "transport: write tcp 172.17.0.3:7051->172.17.0.1:49102: write: broken pipe" ```
karan-bharadwaj (Mon, 06 Feb 2017 18:00:48 GMT):
i keep getting these errors when trying to get the fabric-boilerplate up ```
vp0_1 | 2017/02/06 12:07:46 transport: http2Server.HandleStreams failed to receive the preface from client: EOF
vp0_1 | 2017/02/06 12:07:46 grpc: Server.Serve failed to create ServerTransport: connection error: desc = "transport: write tcp 172.17.0.3:7051->172.17.0.1:49102: write: broken pipe"
```
karan-bharadwaj (Mon, 06 Feb 2017 18:03:26 GMT):
any ideas why?
conroydave (Mon, 06 Feb 2017 18:24:28 GMT):
what os are you running
arner (Mon, 06 Feb 2017 18:24:40 GMT):
Hi @karan-bharadwaj I always get that as last message when the client SDK finished a message to the peer, don't know why.
arner (Mon, 06 Feb 2017 18:24:54 GMT):
Or doesn't it run at all?
arner (Mon, 06 Feb 2017 18:26:09 GMT):
Anyway I recommend to checkout the branch v2-typescript, it has many improvements like using typescript, having containerized the full stack and consequently almost no dependencies or troubles setting up :)
karan-bharadwaj (Mon, 06 Feb 2017 18:26:32 GMT):
@arner the node app tells me that the chaincode deployed successfully but every action throws up that error
arner (Mon, 06 Feb 2017 18:27:14 GMT):
Yeah that's 'normal', maybe one of the developers knows more about it but I also see it all the time with no problems...
karan-bharadwaj (Mon, 06 Feb 2017 18:27:48 GMT):
i'll check out the branch now and get back to you
arner (Mon, 06 Feb 2017 18:28:17 GMT):
You will see the same error, but apart from that I think you'll like it ;)
OlufAndrews (Mon, 06 Feb 2017 18:35:25 GMT):
Has joined the channel.
rjones (Mon, 06 Feb 2017 18:35:45 GMT):
jtrayfield are you clicking the "login" button above the username/password?
rjones (Mon, 06 Feb 2017 18:37:14 GMT):
one second
rjones (Mon, 06 Feb 2017 18:37:40 GMT):
try now
jtrayfield (Mon, 06 Feb 2017 18:38:57 GMT):
@rjones works, thanks!
rjones (Mon, 06 Feb 2017 18:39:12 GMT):
User User_2 added by rjones.
pschnap (Mon, 06 Feb 2017 18:50:15 GMT):
Has joined the channel.
Asara (Mon, 06 Feb 2017 18:57:23 GMT):
Has joined the channel.
vpaprots (Mon, 06 Feb 2017 18:59:44 GMT):
Has joined the channel.
afarhan (Mon, 06 Feb 2017 19:11:16 GMT):
Has joined the channel.
arner (Mon, 06 Feb 2017 19:51:37 GMT):
Great job with the graphql boilerplate @sibelius and @rafael.turk, very exciting to see more choices coming up and it looks great! The IBM CIC Benelux also released a new version of our boilerplate, using TypeScript, Angular 2 and with everything running in containers. We welcome everyone to use it, only asking for a pull request if you make any improvements. Let's accelerate innovation together! https://github.com/IBM-Blockchain/fabric-boilerplate/tree/v2-typescript
Ratnakar (Mon, 06 Feb 2017 20:00:25 GMT):
`make native` fails with below error on latest code, after make clean and make docker-clean
```
docker tag hyperledger/fabric-javaenv hyperledger/fabric-javaenv:x86_64-0.7.0-snapshot-2f801c7
make: *** No rule to make target 'build/bin/orderer', needed by 'orderer'. Stop.
```
Ratnakar (Mon, 06 Feb 2017 20:02:05 GMT):
@greg.haskins can you help please ^^
greg.haskins (Mon, 06 Feb 2017 20:03:21 GMT):
otp, give me a bit
greg.haskins (Mon, 06 Feb 2017 20:03:45 GMT):
this is usually caused by you adding/removing files though
greg.haskins (Mon, 06 Feb 2017 20:04:30 GMT):
its because make is using "git ls-files" to determine dependencies
greg.haskins (Mon, 06 Feb 2017 20:04:43 GMT):
so, for instance, if you remove a file but havent committed, you may see this
bsmita (Mon, 06 Feb 2017 20:14:35 GMT):
Has joined the channel.
weeds (Mon, 06 Feb 2017 20:23:15 GMT):
Has joined the channel.
greg.haskins (Mon, 06 Feb 2017 20:30:04 GMT):
@Ratnakar back
greg.haskins (Mon, 06 Feb 2017 20:31:43 GMT):
gossip sure is chatty on HEAD
forgeRW (Mon, 06 Feb 2017 20:33:54 GMT):
Has joined the channel.
Ratnakar (Mon, 06 Feb 2017 20:35:01 GMT):
I cleaned my local files and hoping it is going though now .. Thanks @greg.haskins :)
bretharrison (Mon, 06 Feb 2017 20:35:47 GMT):
Has joined the channel.
Ratnakar (Mon, 06 Feb 2017 20:35:55 GMT):
Yes it worked
nickgaski (Mon, 06 Feb 2017 21:05:53 GMT):
while the getting started demo seems to be working almost across the board, there is still a recurring issue with the peers and client unable to resolve the orderer localhost:7050. The channel can be created and joined manually through the CLI, but the deploy ends up failing because the SDK/application cannot forward the proposal responses (endorsements) to the ordering service. Any ideas why this is occurring? DNS error? Docker error? @tuand - any thoughts
nickgaski (Mon, 06 Feb 2017 21:06:22 GMT):
I should note that the manual create and join only works if the IP Addresses are hardcoded
nickgaski (Mon, 06 Feb 2017 21:06:58 GMT):
I should also note that this exact problem happened to me and then it just went away. A somewhat ephemeral error!
nickgaski (Mon, 06 Feb 2017 21:07:23 GMT):
@greg.haskins - any ideas on the above?
greg.haskins (Mon, 06 Feb 2017 21:08:02 GMT):
@nickgaski there was a bug a few weeks ago that was fixed of this nature
greg.haskins (Mon, 06 Feb 2017 21:08:10 GMT):
i assume you are running on HEAD though?
greg.haskins (Mon, 06 Feb 2017 21:08:16 GMT):
or is this an older snapshot?
greg.haskins (Mon, 06 Feb 2017 21:09:08 GMT):
@nickgaski for reference: https://gerrit.hyperledger.org/r/#/c/4901/
greg.haskins (Mon, 06 Feb 2017 21:09:25 GMT):
I would expect code prior to 4901 to have problems like you mention
greg.haskins (Mon, 06 Feb 2017 21:09:29 GMT):
but after it, it should be fixed
nickgaski (Mon, 06 Feb 2017 21:09:53 GMT):
it's the docker-compose-gettingstarted.yml. @rameshthoomu - are those images frozen commits or does it pull the most recent snapshot. I know ccenv pulls the latest snapshot and then retags as hyperledger latest
rameshthoomu (Mon, 06 Feb 2017 21:09:53 GMT):
Has joined the channel.
nickgaski (Mon, 06 Feb 2017 21:10:11 GMT):
we are literally seeing this on only one remaining machine
nickgaski (Mon, 06 Feb 2017 21:10:42 GMT):
I've had her strip all older images, stop restart docker, etc... I'm out of ideas. Let me look at that patch set
greg.haskins (Mon, 06 Feb 2017 21:11:28 GMT):
ok, let me know
greg.haskins (Mon, 06 Feb 2017 21:11:43 GMT):
it def smells like its a pre CR4901 image
greg.haskins (Mon, 06 Feb 2017 21:12:12 GMT):
that was the exact behavior, basically docker links (like "peer -> orderer" could not resolve "orderer:7050" but it would work fine if you used the IP
rameshthoomu (Mon, 06 Feb 2017 21:36:19 GMT):
@nickgaski yes those images are frozen and tied to commit "c7b3fe0" which is after CR4901
greg.haskins (Mon, 06 Feb 2017 21:37:07 GMT):
i just realized he said "localhost:7050" not "orderer:7050"
greg.haskins (Mon, 06 Feb 2017 21:37:22 GMT):
CR4901 would have been related to DNS lookup of "orderer"
greg.haskins (Mon, 06 Feb 2017 21:37:26 GMT):
this sounds like something different
greg.haskins (Mon, 06 Feb 2017 21:37:50 GMT):
its probably in the configuration/setup of the composition
mgutala (Mon, 06 Feb 2017 21:38:01 GMT):
Has joined the channel.
hartm (Tue, 07 Feb 2017 01:04:57 GMT):
Has joined the channel.
tarima (Tue, 07 Feb 2017 01:08:45 GMT):
Has joined the channel.
crmiles (Tue, 07 Feb 2017 01:37:47 GMT):
Has joined the channel.
grapebaba (Tue, 07 Feb 2017 01:49:10 GMT):
@greg.haskins @mastersingh24 Does it still allow run 'make unit-test' with specific package?
greg.haskins (Tue, 07 Feb 2017 01:49:43 GMT):
@grapebaba what what allow it?
greg.haskins (Tue, 07 Feb 2017 01:49:43 GMT):
@grapebaba does what allow it?
grapebaba (Tue, 07 Feb 2017 01:51:15 GMT):
I remember @mastersingh24 said it can run like 'make unit-test chaincode/' format
grapebaba (Tue, 07 Feb 2017 01:51:42 GMT):
but i forget the correct syntax
grapebaba (Tue, 07 Feb 2017 01:52:31 GMT):
i want to test all tests in one package
grapebaba (Tue, 07 Feb 2017 01:54:05 GMT):
If I run 'go test' directly, it show error like below
grapebaba (Tue, 07 Feb 2017 01:54:08 GMT):
```
greg.haskins (Tue, 07 Feb 2017 01:55:27 GMT):
you are talking about the TEST_PKGS feature
greg.haskins (Tue, 07 Feb 2017 01:55:46 GMT):
`TEST_PKGS=github.com/hyperledger/fabric/core/chaincode/platforms make unit-test`
grapebaba (Tue, 07 Feb 2017 01:55:54 GMT):
yep
grapebaba (Tue, 07 Feb 2017 01:55:59 GMT):
thanks
greg.haskins (Tue, 07 Feb 2017 01:56:04 GMT):
np
grapebaba (Tue, 07 Feb 2017 01:56:08 GMT):
:grinning:
BharatChaturvedi (Tue, 07 Feb 2017 02:43:20 GMT):
Has joined the channel.
niteshsolanki (Tue, 07 Feb 2017 02:53:45 GMT):
Has joined the channel.
crazybit (Tue, 07 Feb 2017 05:32:50 GMT):
Has joined the channel.
Hangyu (Tue, 07 Feb 2017 06:12:53 GMT):
Has joined the channel.
baohua (Tue, 07 Feb 2017 06:21:15 GMT):
hi, i noticed that the peer is using `/etc/hyperledger/fabric`, while orderer uses `/etc/hyperledger/fabric/orderer` as the config path. IMHO, peer stays the same role level with orderer. Should we change the peer's default config path to `/etc/hyperledger/fabric/peer`?
chadgates (Tue, 07 Feb 2017 06:58:39 GMT):
Has joined the channel.
rjones (Tue, 07 Feb 2017 07:24:49 GMT):
@raghavsood try now
raghavsood (Tue, 07 Feb 2017 07:25:18 GMT):
Works :slightly_smiling_face:
raghavsood (Tue, 07 Feb 2017 07:26:01 GMT):
Has joined the channel.
bur (Tue, 07 Feb 2017 07:32:07 GMT):
Has joined the channel.
hrishikeshio (Tue, 07 Feb 2017 07:32:26 GMT):
Has joined the channel.
hrishikeshio (Tue, 07 Feb 2017 07:32:36 GMT):
Hi Guys getting this error when following tutorial
mbaizan (Tue, 07 Feb 2017 07:42:23 GMT):
Has joined the channel.
rjones (Tue, 07 Feb 2017 07:44:17 GMT):
@hrishikeshio please join us on https://chat.hyperledger.org/
ibmamnt (Tue, 07 Feb 2017 08:06:52 GMT):
Hi, I'm testing compondkey() solution here (sample is here ->
> https://github.com/denyeart/table_to_json/blob/master/chaincode/table_to_json_chaincode.go
ibmamnt (Tue, 07 Feb 2017 08:10:35 GMT):
I noticed I can not query by "Owner" only ( I haved added Owner as compound key already). I can only query "Color". I think this is because key is created like "Marbles7blue4A1bob3", so rangeQuery does not work for key "Marbles7bob". Is there any work around ? Looks like I can use just two keys, the first one "Color". The example code status like N position though.
zlliu (Tue, 07 Feb 2017 08:13:59 GMT):
Has joined the channel.
o.o. (Tue, 07 Feb 2017 08:31:01 GMT):
Has joined the channel.
vitaly.ilinykh (Tue, 07 Feb 2017 08:40:24 GMT):
Has joined the channel.
hrishikeshio (Tue, 07 Feb 2017 08:57:57 GMT):
ok
hrishikeshio (Tue, 07 Feb 2017 08:58:21 GMT):
new suer registration is disabled :neutral_face:
hrishikeshio (Tue, 07 Feb 2017 08:58:25 GMT):
user
abhinav.garg (Tue, 07 Feb 2017 09:01:21 GMT):
can I get any POC working with hyperledger
any demo excluding IBM marbles,car lease
gatakka (Tue, 07 Feb 2017 09:28:11 GMT):
Has joined the channel.
Rymd (Tue, 07 Feb 2017 09:29:08 GMT):
Has joined the channel.
brianeno (Tue, 07 Feb 2017 10:49:35 GMT):
Has joined the channel.
absingh0 (Tue, 07 Feb 2017 11:06:56 GMT):
Has joined the channel.
mhagelstrom (Tue, 07 Feb 2017 11:32:56 GMT):
@abhinav.garg you can find a few demos (the ones you excluded + commercial paper) on the bluemix platform if you follow the link: https://console.ng.bluemix.net/docs/services/blockchain/ibmblockchain_tutorials.html
abhinav.garg (Tue, 07 Feb 2017 11:32:56 GMT):
Has joined the channel.
mhagelstrom (Tue, 07 Feb 2017 11:34:17 GMT):
Try repeating the question on the new chat platform. You might get other replies over there.
gvlax (Tue, 07 Feb 2017 12:02:55 GMT):
Has joined the channel.
bart.cant@gmail.com (Tue, 07 Feb 2017 12:13:24 GMT):
Has joined the channel.
toddb (Tue, 07 Feb 2017 12:51:30 GMT):
Has joined the channel.
nickmelis (Tue, 07 Feb 2017 12:58:54 GMT):
Has joined the channel.
gatakka (Tue, 07 Feb 2017 13:10:58 GMT):
Hello, I am playing with HL from master branch and when I try to make a invocation request to peer i receive gRPC error:
code = 2 desc = Failed to deserialize creator identity, err MSP admin is unknown
User admin is enrolled from CI and has proper cert
I am using docker images and docker-compose from https://github.com/hyperledger/fabric/blob/master/docs/gettingstarted.md
Any idea what may cause MSP not to find user admin (or any other user)
gatakka (Tue, 07 Feb 2017 13:10:58 GMT):
Hello, I am playing with HL from master branch and when I try to make a invocation request to peer i receive gRPC error:
code = 2 desc = Failed to deserialize creator identity, err MSP admin is unknown
User admin is enrolled from CA and has proper cert
I am using docker images and docker-compose from https://github.com/hyperledger/fabric/blob/master/docs/gettingstarted.md
Any idea what may cause MSP not to find user admin (or any other user)
gatakka (Tue, 07 Feb 2017 13:12:03 GMT):
When i do invocation from CLI everything is working properly.
gatakka (Tue, 07 Feb 2017 13:12:30 GMT):
Hello, I am playing with HL from master branch and when I try to make a invocation request to peer i receive gRPC error:
code = 2 desc = Failed to deserialize creator identity, err MSP admin is unknown
User admin is enrolled from CA and has proper cert
I am using docker images and docker-compose from https://github.com/hyperledger/fabric/blob/master/docs/gettingstarted.md
Any idea what may cause MSP not to find user admin (or any other user)
When i do invocation from CLI everything is working properly.
thojest (Tue, 07 Feb 2017 13:44:40 GMT):
hi everyone, following question considering Hyperledger v 0.6
When I create a webapp and I want to handle user login, how would i do that? afaik there are several security layers
thojest (Tue, 07 Feb 2017 13:44:55 GMT):
1)webapp
2) membersrvc
3) blockchain
thojest (Tue, 07 Feb 2017 13:47:28 GMT):
So if the user wants to login is this the best way of doing this???
- take username and password
- encrypt passwords and sends details to chaincode
- chaincode checks that encrypted passwords match
- If correct send, success message back to node
- node then enrols the user so that the app can send transactions as the user with the returned cert
- It also creates a session so that it knows it is allowed to use the cert.
thojest (Tue, 07 Feb 2017 13:47:39 GMT):
what confuses me is the following point
thojest (Tue, 07 Feb 2017 13:48:09 GMT):
I thought membesrvc manages all this user authentification stuff?
thojest (Tue, 07 Feb 2017 13:49:25 GMT):
do i have to write user + hash(password) to the blockchain?
cbf (Tue, 07 Feb 2017 13:58:44 GMT):
https://hyperledgerproject.slack.com/archives/general/p1486475686004850
barinjato (Tue, 07 Feb 2017 14:11:36 GMT):
Has joined the channel.
reachk.raj (Tue, 07 Feb 2017 14:11:49 GMT):
Has joined the channel.
DrTES (Tue, 07 Feb 2017 14:14:23 GMT):
Has joined the channel.
coolsvap (Tue, 07 Feb 2017 14:17:57 GMT):
Has joined the channel.
kenzhang (Tue, 07 Feb 2017 14:34:23 GMT):
Has joined the channel.
b9lab-damien (Tue, 07 Feb 2017 14:41:01 GMT):
Has joined the channel.
ardashev120101 (Tue, 07 Feb 2017 14:41:21 GMT):
Has joined the channel.
nickgaski (Tue, 07 Feb 2017 14:41:38 GMT):
@gatakka - do you have any additional images on your machine? Also are you succeeding at the `GOPATH=$PWD node deploy.js` step? If you share your logs we should be able to resolve
skbodwell (Tue, 07 Feb 2017 14:42:59 GMT):
Has joined the channel.
gatakka (Tue, 07 Feb 2017 14:46:24 GMT):
@nickgaski i removed all images before that, I'm 100% sure that proper images are running. I do not use nodejs SDK because for me it gives me errors in key/value store implementation. I create gRPC requests and send them peer using protocol buffers. Interesting is while I play if i do NOT provide ChainID in ChainHeader proto request is accepted, but later i got "chainID not provided for chaincode myc1".
If i provide any sting in protobuf.ChainHeader.ChainID i got MSP error, if i do not provide it it loads default MSP but tell me that ChainID is not provided
gatakka (Tue, 07 Feb 2017 14:46:24 GMT):
@nickgaski i removed all images before that, I'm 100% sure that proper images are running. I do not use nodejs SDK because for me it gives me errors in key/value store implementation. I create gRPC requests and send them to peer using protocol buffers. Interesting is while I play if i do NOT provide ChainID in ChainHeader proto request is accepted, but later i got "chainID not provided for chaincode myc1".
If i provide any sting in protobuf.ChainHeader.ChainID i got MSP error, if i do not provide it it loads default MSP but tell me that ChainID is not provided
gatakka (Tue, 07 Feb 2017 14:46:24 GMT):
@nickgaski i removed all images before that, I'm 100% sure that proper images are running. I do not use nodejs SDK because for me it gives me errors in key/value store implementation. I create gRPC requests and send them to peer using protocol buffers. Interesting is while I play if i do NOT provide ChainID in ChainHeader proto request is accepted, but later i got "chainID not provided for chaincode myc1".
If i provide any string in protobuf.ChainHeader.ChainID i got MSP error, if i do not provide it it loads default MSP but tell me that ChainID is not provided
gatakka (Tue, 07 Feb 2017 14:50:26 GMT):
Here is the log when chainID is not provided:
peer0 | 2017-02-07 14:49:19.199 UTC [protoutils] ValidateProposalMessage -> INFO d4a ValidateProposalMessage starts for signed proposal 0xc4217df830
peer0 | 2017-02-07 14:49:19.199 UTC [protoutils] validateChainHeader -> INFO d4b validateChainHeader info: header type 3
peer0 | 2017-02-07 14:49:19.199 UTC [protoutils] checkSignatureFromCreator -> INFO d4c checkSignatureFromCreator starts
peer0 | 2017-02-07 14:49:19.199 UTC [peer] GetLocalMSP -> INFO d4d Returning existing local MSP
peer0 | 2017-02-07 14:49:19.199 UTC [msp] DeserializeIdentity -> INFO d4e Obtaining identity
peer0 | 2017-02-07 14:49:19.199 UTC [msp] newIdentity -> INFO d4f Creating identity instance for ID &{DEFAULT DEFAULT}
peer0 | 2017-02-07 14:49:19.199 UTC [protoutils] checkSignatureFromCreator -> INFO d50 checkSignatureFromCreator info: creator is &{DEFAULT DEFAULT}
peer0 | 2017-02-07 14:49:19.199 UTC [msp] Validate -> INFO d51 MSP DEFAULT validating identity
peer0 | 2017-02-07 14:49:19.199 UTC [protoutils] checkSignatureFromCreator -> INFO d52 checkSignatureFromCreator info: creator is valid
peer0 | 2017-02-07 14:49:19.199 UTC [msp] Verify -> DEBU d53 Verify: digest = 00000000 37 97 25 ac 61 39 7c 35 9c fc 6b dd 59 80 26 4e |7.%.a9|5..k.Y.&N|
peer0 | 00000010 cc 94 cf c2 33 fd 54 37 55 68 25 3c de 61 11 a7 |....3.T7Uh%<.a..|
peer0 | 2017-02-07 14:49:19.199 UTC [msp] Verify -> DEBU d54 Verify: sig = 00000000 30 45 02 21 00 86 e9 b0 15 0a 2d 10 02 06 45 cb |0E.!......-...E.|
peer0 | 00000010 c5 59 7e b8 40 1e 06 e8 10 fb 2b 3d 4e 08 0e 10 |.Y~.@.....+=N...|
peer0 | 00000020 89 5b d7 ad b3 02 20 26 b6 e8 ed ae 5f ae 89 62 |.[.... &...._..b|
peer0 | 00000030 6b e4 95 93 08 08 1c 63 be 19 b3 47 4a 7a cd 84 |k......c...GJz..|
peer0 | 00000040 5d 42 a9 64 cf 94 ee |]B.d...|
peer0 | 2017-02-07 14:49:19.199 UTC [protoutils] checkSignatureFromCreator -> INFO d55 checkSignatureFromCreator exists successfully
peer0 | 2017-02-07 14:49:19.199 UTC [protoutils] validateChaincodeProposalMessage -> INFO d56 validateChaincodeProposalMessage starts for proposal 0xc4213c1f40, header 0xc4213c2a70
peer0 | 2017-02-07 14:49:19.199 UTC [protoutils] validateChaincodeProposalMessage -> INFO d57 validateChaincodeProposalMessage info: header extension references chaincode name:"myc1"
gatakka (Tue, 07 Feb 2017 14:50:54 GMT):
and here is when chainID is provided:
peer0 | 2017-02-07 14:50:37.725 UTC [protoutils] ValidateProposalMessage -> INFO d73 ValidateProposalMessage starts for signed proposal 0xc422eeb770
peer0 | 2017-02-07 14:50:37.725 UTC [protoutils] validateChainHeader -> INFO d74 validateChainHeader info: header type 3
peer0 | 2017-02-07 14:50:37.725 UTC [protoutils] checkSignatureFromCreator -> INFO d75 checkSignatureFromCreator starts
peer0 | 2017-02-07 14:50:37.725 UTC [peer] GetManagerForChain -> INFO d76 Returinging existing manager for chain myc1
gatakka (Tue, 07 Feb 2017 14:56:02 GMT):
and if i do not provide any value for protos.ChaincodeSpec.ChaincodeID it panics like:
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0x737a59]
goroutine 15825 [running]:
panic(0xb91020, 0xc420012050)
/opt/go/src/runtime/panic.go:500 +0x1a1
github.com/hyperledger/fabric/core/endorser.(*Endorser).ProcessProposal(0x12552a0, 0x7f1b1c062800, 0xc423238f30, 0xc423238f90, 0x0, 0x0, 0x0)
/opt/gopath/src/github.com/hyperledger/fabric/core/endorser/endorser.go:319 +0x119
github.com/hyperledger/fabric/protos/peer._Endorser_ProcessProposal_Handler(0xc09820, 0x12552a0, 0x7f1b1c062800, 0xc423238f30, 0xc4217f7480, 0x0, 0x0, 0x44152b, 0x8000, 0xb4ce40)
/opt/gopath/src/github.com/hyperledger/fabric/protos/peer/peer.pb.go:113 +0x27d
github.com/hyperledger/fabric/vendor/google.golang.org/grpc.(*Server).processUnaryRPC(0xc42013eab0, 0x12181e0, 0xc423ba55f0, 0xc4232680f0, 0xc420172f60, 0x11f8890, 0xc423238f00, 0x0, 0x0)
/opt/gopath/src/github.com/hyperledger/fabric/vendor/google.golang.org/grpc/server.go:580 +0xa2d
github.com/hyperledger/fabric/vendor/google.golang.org/grpc.(*Server).handleStream(0xc42013eab0, 0x12181e0, 0xc423ba55f0, 0xc4232680f0, 0xc423238f00)
/opt/gopath/src/github.com/hyperledger/fabric/vendor/google.golang.org/grpc/server.go:737 +0x6ad
github.com/hyperledger/fabric/vendor/google.golang.org/grpc.(*Server).serveStreams.func1.1(0xc4213d4160, 0xc42013eab0, 0x12181e0, 0xc423ba55f0, 0xc4232680f0)
/opt/gopath/src/github.com/hyperledger/fabric/vendor/google.golang.org/grpc/server.go:402 +0xab
created by github.com/hyperledger/fabric/vendor/google.golang.org/grpc.(*Server).serveStreams.func1
/opt/gopath/src/github.com/hyperledger/fabric/vendor/google.golang.org/grpc/server.go:403 +0xa3
nickgaski (Tue, 07 Feb 2017 14:57:41 GMT):
I am curious why the SDK does not work for you? Can you share your node and npm versions?
nickgaski (Tue, 07 Feb 2017 14:58:04 GMT):
we've seen some funky behavior if node is outdated
gatakka (Tue, 07 Feb 2017 14:58:58 GMT):
i am not using nodejs. I create requests using proto bufers using golang and communicating directly to peer and CA
gatakka (Tue, 07 Feb 2017 14:59:58 GMT):
think of it like I am creating SDK for HL in golang - just to learn how HL is working :)
nickgaski (Tue, 07 Feb 2017 15:01:02 GMT):
I think your question may be better suited for the SDK channel then to diagnose the errant piece in your proto buf
gatakka (Tue, 07 Feb 2017 15:03:54 GMT):
OK, Thank you for the help. I will ask there
jworthington (Tue, 07 Feb 2017 15:14:54 GMT):
Has joined the channel.
mihaig (Tue, 07 Feb 2017 15:23:49 GMT):
Has joined the channel.
mpage (Tue, 07 Feb 2017 15:25:35 GMT):
Has joined the channel.
magg (Tue, 07 Feb 2017 15:52:04 GMT):
Has joined the channel.
magg (Tue, 07 Feb 2017 15:52:09 GMT):
hello
magg (Tue, 07 Feb 2017 15:52:35 GMT):
i was reading about 3 types of nodes... consenter, etc. could you give me more background information. How do I know what type of node my peers are, or how can I configure that? I also heard about an orderer node
dolanort (Tue, 07 Feb 2017 15:56:54 GMT):
Has joined the channel.
magg (Tue, 07 Feb 2017 15:58:42 GMT):
hello
magg (Tue, 07 Feb 2017 15:58:44 GMT):
i was reading about 3 types of nodes... consenter, etc. could you give me more background information. How do I know what type of node my peers are, or how can I configure that? I also heard about an orderer node
umasuthan (Tue, 07 Feb 2017 16:03:00 GMT):
Has joined the channel.
jansony1 (Tue, 07 Feb 2017 16:06:05 GMT):
Has joined the channel.
jansony1 (Tue, 07 Feb 2017 16:07:18 GMT):
@magg this may help https://github.com/hyperledger/fabric/blob/master/proposals/r1/Next-Consensus-Architecture-Proposal.md
magg (Tue, 07 Feb 2017 16:07:44 GMT):
thanks @jansony1
jansony1 (Tue, 07 Feb 2017 16:08:14 GMT):
@magg np~
troyronda (Tue, 07 Feb 2017 16:31:40 GMT):
Has joined the channel.
randomnerd (Tue, 07 Feb 2017 17:06:59 GMT):
Has joined the channel.
mohamoud.egal (Tue, 07 Feb 2017 17:12:12 GMT):
Has joined the channel.
mohamoud.egal (Tue, 07 Feb 2017 17:13:15 GMT):
HI, I am working to on running Chaincode for V1.0 and I’m currently stuck. Below is a screen shot of the error message, my file directory for the example Chain code go file I made per instructions and the command I was supposed to use
mohamoud.egal (Tue, 07 Feb 2017 17:14:06 GMT):
I ran a file named chaincode_example02.go
cedoor (Tue, 07 Feb 2017 17:14:13 GMT):
hello,
mohamoud.egal (Tue, 07 Feb 2017 17:14:29 GMT):
Message Attachments
mohamoud.egal (Tue, 07 Feb 2017 17:15:42 GMT):
Message Attachments
cedoor (Tue, 07 Feb 2017 17:15:53 GMT):
Hello,
is it possible to get the data of an old state of smart conctract ( after overwrite invoke functions ) in Fabric?
mohamoud.egal (Tue, 07 Feb 2017 17:17:08 GMT):
Message Attachments
randomnerd (Tue, 07 Feb 2017 17:21:20 GMT):
@mohamoud.egal you forgot to run `go build`
mohamoud.egal (Tue, 07 Feb 2017 17:23:02 GMT):
Message Attachments
mohamoud.egal (Tue, 07 Feb 2017 17:23:08 GMT):
@randomnerd
randomnerd (Tue, 07 Feb 2017 17:23:45 GMT):
this log reports that you don't have fabric codebase checked out
mohamoud.egal (Tue, 07 Feb 2017 17:24:08 GMT):
as in?
randomnerd (Tue, 07 Feb 2017 17:24:21 GMT):
as in .../src/github.com/hyperledger/fabric/...
randomnerd (Tue, 07 Feb 2017 17:24:21 GMT):
as in ...`/src/github.com/hyperledger/fabric/`...
randomnerd (Tue, 07 Feb 2017 17:24:21 GMT):
as in `.../src/github.com/hyperledger/fabric/...`
mohamoud.egal (Tue, 07 Feb 2017 17:25:40 GMT):
@randomnerd I followed the directions on this page https://hyperledger-fabric.readthedocs.io/en/latest/Setup/Chaincode-setup/#running-the-chaincode
randomnerd (Tue, 07 Feb 2017 17:26:32 GMT):
didnt you miss this step? ```mkdir -p $GOPATH/src/github.com/hyperledger
cd $GOPATH/src/github.com/hyperledger
git clone http://gerrit.hyperledger.org/r/fabric```
randomnerd (Tue, 07 Feb 2017 17:26:32 GMT):
didnt you miss this step?
```mkdir -p $GOPATH/src/github.com/hyperledger
cd $GOPATH/src/github.com/hyperledger
git clone http://gerrit.hyperledger.org/r/fabric```
mohamoud.egal (Tue, 07 Feb 2017 17:28:40 GMT):
I saw that but in an earlier step I already created a hyperledger folder under github.com
mohamoud.egal (Tue, 07 Feb 2017 17:29:14 GMT):
Message Attachments
randomnerd (Tue, 07 Feb 2017 17:30:03 GMT):
you should do that, it downloads the actual fabric code
randomnerd (Tue, 07 Feb 2017 17:30:23 GMT):
@mohamoud.egal in previous step you just created an empty folder
mohamoud.egal (Tue, 07 Feb 2017 17:30:31 GMT):
Message Attachments
mohamoud.egal (Tue, 07 Feb 2017 17:30:36 GMT):
@randomnerd
randomnerd (Tue, 07 Feb 2017 17:31:00 GMT):
what does `echo $GOPATH` return?
mohamoud.egal (Tue, 07 Feb 2017 17:31:55 GMT):
Message Attachments
randomnerd (Tue, 07 Feb 2017 17:32:01 GMT):
@mohamoud.egal also `ls fabric`
mohamoud.egal (Tue, 07 Feb 2017 17:32:52 GMT):
Message Attachments
randomnerd (Tue, 07 Feb 2017 17:33:08 GMT):
weird, looks like everything is in place
randomnerd (Tue, 07 Feb 2017 17:34:18 GMT):
try `cd fabric/examples/chaincode/go/chaincode_example02`
randomnerd (Tue, 07 Feb 2017 17:34:25 GMT):
and do `go build` in there
randomnerd (Tue, 07 Feb 2017 17:35:25 GMT):
@mohamoud.egal
randomnerd (Tue, 07 Feb 2017 17:35:56 GMT):
also make sure you're at the 0.6 branch `git checkout v0.6`
mohamoud.egal (Tue, 07 Feb 2017 17:37:00 GMT):
@randomnerd I thought I was in the V1.0
mohamoud.egal (Tue, 07 Feb 2017 17:37:15 GMT):
Message Attachments
randomnerd (Tue, 07 Feb 2017 17:37:37 GMT):
@mohamoud.egal now try `go build` here
randomnerd (Tue, 07 Feb 2017 17:38:27 GMT):
not sure if those examples are up to date with v1.0 so its better to use 0.6 with those i guess
mohamoud.egal (Tue, 07 Feb 2017 17:38:45 GMT):
Message Attachments
randomnerd (Tue, 07 Feb 2017 17:39:20 GMT):
did you `git checkout v0.6`?
mohamoud.egal (Tue, 07 Feb 2017 17:39:56 GMT):
Message Attachments
mohamoud.egal (Tue, 07 Feb 2017 17:40:22 GMT):
@randomnerd the directions point to another chancode_example02.go than the one I'm currently in
randomnerd (Tue, 07 Feb 2017 17:40:48 GMT):
should be the same one
randomnerd (Tue, 07 Feb 2017 17:41:20 GMT):
at that step you just checked out that exact file instead of the whole repository
mohamoud.egal (Tue, 07 Feb 2017 17:41:55 GMT):
yes.
mohamoud.egal (Tue, 07 Feb 2017 17:42:06 GMT):
then I ran the command "CORE_CHAINCODE_ID_NAME=mycc CORE_PEER_ADDRESS=0.0.0.0:7051 ./chaincode_example02"
mohamoud.egal (Tue, 07 Feb 2017 17:42:22 GMT):
to start & register the chaincode
randomnerd (Tue, 07 Feb 2017 17:42:24 GMT):
you have to build the file before running it :)
randomnerd (Tue, 07 Feb 2017 17:42:50 GMT):
as for now, you only have chaincode_example02.go which is the source code that should be compiled
mohamoud.egal (Tue, 07 Feb 2017 17:43:44 GMT):
so run "go build" in this directory?
randomnerd (Tue, 07 Feb 2017 17:43:52 GMT):
yep
randomnerd (Tue, 07 Feb 2017 17:44:31 GMT):
not sure what went wrong, try going to `$GOPATH/src/github.com/hyperledger` , `rm -rf fabric` and then `git clone https://github.com/hyperledger/fabric` and `cd fabric && git checkout v0.6`
randomnerd (Tue, 07 Feb 2017 17:45:28 GMT):
if that doesnt help, we're stuck and need someone with better knowledge to help you :(
gennadyl (Tue, 07 Feb 2017 17:47:41 GMT):
Has joined the channel.
mohamoud.egal (Tue, 07 Feb 2017 17:48:34 GMT):
Message Attachments
randomnerd (Tue, 07 Feb 2017 17:49:34 GMT):
now go try building the chaincode again
mohamoud.egal (Tue, 07 Feb 2017 17:51:05 GMT):
I still don't know if I should be in the "/Desktop/gocode/src/github.com/hyperledger/fabric/examples/chaincode/go/chaincode_example02" or the "Desktop/gocode/src/github.com//chaincode_example02"
randomnerd (Tue, 07 Feb 2017 17:51:15 GMT):
either should work
randomnerd (Tue, 07 Feb 2017 17:51:31 GMT):
but the better choice is the short path
mohamoud.egal (Tue, 07 Feb 2017 17:52:38 GMT):
Message Attachments
randomnerd (Tue, 07 Feb 2017 17:53:07 GMT):
you have to be at the chaincode_example02 folder
mohamoud.egal (Tue, 07 Feb 2017 17:55:51 GMT):
Message Attachments
Tetiana (Tue, 07 Feb 2017 17:58:12 GMT):
Has joined the channel.
randomnerd (Tue, 07 Feb 2017 17:58:52 GMT):
:thumbsup: have fun
kell (Tue, 07 Feb 2017 18:00:36 GMT):
Has joined the channel.
rjones (Tue, 07 Feb 2017 18:02:53 GMT):
please migrate to https://chat.hyperledger.org
randomnerd (Tue, 07 Feb 2017 18:04:16 GMT):
we're actually here :)
niechen (Tue, 07 Feb 2017 18:19:30 GMT):
Has joined the channel.
rjones (Tue, 07 Feb 2017 18:33:59 GMT):
@randomnerd that is the feed from slack to here for channels that happen to have the same name :)
binhn (Tue, 07 Feb 2017 18:38:48 GMT):
Has joined the channel.
binhn (Tue, 07 Feb 2017 18:49:25 GMT):
@channel I'd like to pick up the discussion of alpha release content documented here https://wiki.hyperledger.org/projects/proposedv1alphacontent, which I mentioned at the hackfest during my update. Basically this is what we have on the master branch now: Stable API for chaincode development, default configuration to start up a simple network to run chaincodes on multiple channels using docker image http://hyperledger-fabric.readthedocs.io/en/latest/gettingstarted.
binhn (Tue, 07 Feb 2017 18:50:57 GMT):
Or we wait 3 more weeks to get the configuration items listed by Gari on the fabric-maintainers channel, which I copied below
```
1) Channels - we've spent a lot of time and effort on this feature and we need to show how it really works. This means we need to be able to have the "proper" config items as part of channel creation - e.g. member organizations (each comprised of an MSP and anchor peers)
We need to be able to create multiple channels and have different membership for each channel (at least from a configuration perspective)
2) We need to be able to create channels *properly* from at least one of the SDKs (e.g. Node) and the CLI (although the CLI needs a real overhaul in this aspect as it should be a real client of the orderer)
3) Need to show that we can have peers from multiple organizations "join" a channel. This means that we need to properly parse and leverage the genesis / config block (with proper config items as specified in 1) above) - i.e. use this information in the peer to have per channel MSP list which can be used by both the endorser (to verify proposals from clients) and by gossip (gossip also needs the per channel list of anchor peers as well). We could decide that we should not show gossip across orgs but I think at this point that would be a mistake
4) Endorsement / validation policies - we need to demonstrate how to author a basic policy which requires multiple signatures. Should be able to do this from at least one SDK and from the CLI when deploying chaincode
5) There is a load of crypto material needed for 1) - 4) above so we need to document how to use fabric-ca to generate / obtain this material
6) We need to have published Docker images for the peer, orderer and fabric-ca plus NodeSDK published to NPM and if we are going to put out the Java SDK need to have a downloadable JAR and/or install via maven or gradle
```
binhn (Tue, 07 Feb 2017 18:53:39 GMT):
Keep in mind that alpha is normally not complete and subject to change based on feedback from alpha users, and we definitely want to have feedback on APIs and chaincode development and running on multichannel architecture
binhn (Tue, 07 Feb 2017 18:55:13 GMT):
Are configurations pertaining to bootstrap, channel set up, endorsement important for folks at this point or those can be included in an upcoming beta (end of Feb)?
seand20tech (Tue, 07 Feb 2017 19:40:25 GMT):
Has joined the channel.
cbf (Tue, 07 Feb 2017 19:45:35 GMT):
@binhn an alpha release that then incorporates feedback from users is not the same as deferring feature/function post alpha that was already on the docket.
randomnerd (Tue, 07 Feb 2017 20:29:20 GMT):
do we finally get v1 docker images?
randomnerd (Tue, 07 Feb 2017 20:29:42 GMT):
afaik there are none at docker hub right now
JonathanLevi (Tue, 07 Feb 2017 20:31:25 GMT):
Has joined the channel.
mastersingh24 (Tue, 07 Feb 2017 20:31:35 GMT):
@randomnerd - yes - when we tag a release, we publish Docker images for that release. We have yet cut a V1.0 release, so we are talking about cutting an alpha release
randomnerd (Tue, 07 Feb 2017 20:32:34 GMT):
thats what im talking about, its much easier to participate in alpha while not having to build all the stuff by yourself :)
JonathanLevi (Tue, 07 Feb 2017 20:34:17 GMT):
Oh, of course. Not just that - we should set the exact same baseline for reporting issues, testing performance, reproduce numbers - etc.
JonathanLevi (Tue, 07 Feb 2017 20:34:46 GMT):
(that's why we are not yet *formalizing* a cut yet) - thanks for checking @randomnerd!
randomnerd (Tue, 07 Feb 2017 20:35:43 GMT):
so any idea when we get those? ;)
Asara (Tue, 07 Feb 2017 20:39:06 GMT):
yeah, a pre-release of 1.0 would be awesome to play around with
randomnerd (Tue, 07 Feb 2017 20:40:25 GMT):
with some good docs, yep
not sure which one i want more, v1 or better docs :D
cbf (Tue, 07 Feb 2017 20:46:08 GMT):
@randomnerd you can pull some interim ones we used for the hackfest last week... see http://fabric-rtd.readthedocs.io/en/latest/gettingstarted/
cbf (Tue, 07 Feb 2017 20:46:23 GMT):
docs changes are in flight
cbf (Tue, 07 Feb 2017 20:46:43 GMT):
I have a batch here: https://gerrit.hyperledger.org/r/#/c/5615/
Asara (Tue, 07 Feb 2017 20:48:00 GMT):
When is the preview release slated for anyways? I know 1.0 is slated for march
randomnerd (Tue, 07 Feb 2017 20:48:12 GMT):
@cbf will check that out, thanks!
randomnerd (Tue, 07 Feb 2017 20:50:02 GMT):
@cbf do those doc changes get built and published anywhere?
cbf (Tue, 07 Feb 2017 20:51:42 GMT):
http://fabric-rtd.readthedocs.io/en/latest/ as a byproduct of the merge build
randomnerd (Tue, 07 Feb 2017 20:52:20 GMT):
awesome, thanks again!
randomnerd (Tue, 07 Feb 2017 20:53:22 GMT):
an offtopic: anyone knows how to hide the channel panel without narrowing the whole chat window?
cbf (Tue, 07 Feb 2017 20:53:55 GMT):
@randomnerd not that I have found
randomnerd (Tue, 07 Feb 2017 20:54:25 GMT):
@cbf i'll put a note to submit a feature request then
cbf (Tue, 07 Feb 2017 20:54:40 GMT):
SGTM thanks
beauson45 (Tue, 07 Feb 2017 20:55:13 GMT):
Has joined the channel.
SivaKannan (Tue, 07 Feb 2017 21:05:37 GMT):
Has joined the channel.
binhn (Tue, 07 Feb 2017 21:06:35 GMT):
@cbf definition of alpha is not feature complete, but a good subset of functions to collect feedback
mwall (Tue, 07 Feb 2017 21:15:57 GMT):
Has joined the channel.
JonathanLevi (Tue, 07 Feb 2017 21:42:50 GMT):
A related question: What do we envision as a realistic window of time between the cut of (say, a first or a final) `v1-alpha` and a `v1` release?
JonathanLevi (Tue, 07 Feb 2017 21:44:28 GMT):
Maybe this will help us in assessing our definition of alpha-ready.
JonathanLevi (Tue, 07 Feb 2017 21:45:03 GMT):
I feel like we really need to both collect feedback and have a lot of the core stuff working (which does not contradict what you say about @binhn)
JonathanLevi (Tue, 07 Feb 2017 21:46:20 GMT):
I know for myself, that I usually form a stronger opinion over something (say a feature) after "playing with it"... at the same time, I also want (for example) fabric-ca (again, without loss of generality) to get heavily tested.
rjones (Tue, 07 Feb 2017 21:47:43 GMT):
is there any discussion of a bug bar or bug budget for releases?
Asara (Tue, 07 Feb 2017 21:48:41 GMT):
Only way to get it heavily tested is by letting us play with it ;)
Asara (Tue, 07 Feb 2017 21:48:54 GMT):
I for one want a alpha release ASAP
Asara (Tue, 07 Feb 2017 21:49:15 GMT):
Mostly so I can start moving towards targeting 1.0 instead of building on 0.6 going forward
thomasmarckx (Tue, 07 Feb 2017 21:52:50 GMT):
Has joined the channel.
JonathanLevi (Tue, 07 Feb 2017 21:53:17 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-maintainers?msg=fXAXZWEiWQiL3ZQE9) @rjones
cbf (Tue, 07 Feb 2017 21:53:57 GMT):
@Asara exactly
JonathanLevi (Tue, 07 Feb 2017 21:54:22 GMT):
@Asara, yes, buy you can really already build it yourself. Don't not have to be "tagged", really.
JonathanLevi (Tue, 07 Feb 2017 21:54:22 GMT):
@Asara, yes, but you can really already build it yourself. Don't not have to be "tagged", really.
cbf (Tue, 07 Feb 2017 21:54:29 GMT):
but do you want to have to rework a bunch of stuff if we have breaking changes because of things in flight?
cbf (Tue, 07 Feb 2017 21:54:50 GMT):
@JonathanLevi but the docs aren't there
JonathanLevi (Tue, 07 Feb 2017 21:54:54 GMT):
Exactly. We are trying to "lock/freeze APIs"
JonathanLevi (Tue, 07 Feb 2017 21:55:10 GMT):
We want people to use the features the way they are intended/designed
JonathanLevi (Tue, 07 Feb 2017 21:56:02 GMT):
We need to make sure that even the basic stuff works (e.g., even the basic NPEs, error messages, integration... that we should really check/test/try on our own, before we ask the world to "do it for us")
JonathanLevi (Tue, 07 Feb 2017 21:56:19 GMT):
I feel that there is a lot to do.
JonathanLevi (Tue, 07 Feb 2017 21:56:19 GMT):
I feel like/that there is a lot to do.
Asara (Tue, 07 Feb 2017 21:58:53 GMT):
@cbf its better I refactor stuff slowly than all at once when 1.0's api is finalized/comes out completely
randomnerd (Tue, 07 Feb 2017 21:59:17 GMT):
@Asara +1
magg (Tue, 07 Feb 2017 22:00:56 GMT):
i'm trying to setup a network with multiple peers to test the consensus mechanisms.. using docker-compose... somehow my demo is not working.. your docker-compose files use links instead of a network. is there a reason to this? if vp0 goes down the network goes down
mastersingh24 (Tue, 07 Feb 2017 22:02:25 GMT):
@magg - are you using the v0.6 Docker images? not sure what you mean by the "network" goes down?
magg (Tue, 07 Feb 2017 22:03:13 GMT):
yes i'm using those... i meant to say that the demo app will not work anymore
magg (Tue, 07 Feb 2017 22:03:13 GMT):
yes i'm using those... i meant to say that the demo app will not work anymore @mastersingh24
mgk (Tue, 07 Feb 2017 22:03:25 GMT):
Has joined the channel.
magg (Tue, 07 Feb 2017 22:06:28 GMT):
https://github.com/IBM-Blockchain/fabric-images these ones...
magg (Tue, 07 Feb 2017 22:06:54 GMT):
and the car lease demo / marbles demo
mastersingh24 (Tue, 07 Feb 2017 22:07:04 GMT):
ah - yeah - not sure which demo app you are using, but the issue with most of the NodeJS demo apps we originally did is that they only invoke/query vp0
mastersingh24 (Tue, 07 Feb 2017 22:07:55 GMT):
the blockchain network can tolerate one faulty peer, but I don't think we coded "failover" to alternate peer in the apps
magg (Tue, 07 Feb 2017 22:09:18 GMT):
yeah i tested shutting one of other nodes.. and everything is OK... if shutdown 2... i can't save transactions in the ledger
Adil.B (Tue, 07 Feb 2017 22:09:23 GMT):
Has joined the channel.
magg (Tue, 07 Feb 2017 22:10:15 GMT):
oh... how can the failover be implemented? the nodejs apps need to handle that then?
mastersingh24 (Tue, 07 Feb 2017 22:11:05 GMT):
correct - consensus in those setups is PBFT and with 4 (3f+1) peers it can tolerate 1 faulty node (f=1)
mastersingh24 (Tue, 07 Feb 2017 22:11:37 GMT):
yeah - you should be able to modify the app to try a second endpoint on failure
mastersingh24 (Tue, 07 Feb 2017 22:11:50 GMT):
I've done it before a while back
magg (Tue, 07 Feb 2017 22:12:34 GMT):
Also - do yo have any guides on how to setup a network with the new types of peers (orderer/endorser) in v1.0... and a sample app?
markgrand (Tue, 07 Feb 2017 22:29:58 GMT):
Has joined the channel.
nickgaski (Tue, 07 Feb 2017 22:31:14 GMT):
@magg see here - http://fabric-rtd.readthedocs.io/en/latest/gettingstarted
nickgaski (Tue, 07 Feb 2017 22:31:54 GMT):
please make sure you have node 6.9.5 and docker 1.13
nickgaski (Tue, 07 Feb 2017 22:32:13 GMT):
need to add a tweak to the docs for those prereqs
rahulhegde (Tue, 07 Feb 2017 22:59:28 GMT):
Has joined the channel.
seand20tech (Tue, 07 Feb 2017 23:45:58 GMT):
i'm trying to set up a 1.0 network based on the getting started guide mentioned above -- when i run the docker compose file, everything comes up and the cli node logs that the channel was created successfully, and that all peers have joined
seand20tech (Tue, 07 Feb 2017 23:46:54 GMT):
however, the peers are continuously writing error messages like Failed obtaining connection for peer0:7051, PKIid:[ ... ] but got [ ... ]
seand20tech (Tue, 07 Feb 2017 23:47:10 GMT):
where the contents between the brackets are long lists of numbers
seand20tech (Tue, 07 Feb 2017 23:47:59 GMT):
question: is this expected (and ignorable?) or did i make a mistake in my setup somewhere?
seand20tech (Tue, 07 Feb 2017 23:49:34 GMT):
i notice that the cli logs messages like proto: textWriter unindented too far, followed by Received block: Header:<6:71 0:"\x00" } 0:4 8:4889 12:/* unknown wire type 7 */ } 1684:/* unexpected EOF */ } ...
seand20tech (Tue, 07 Feb 2017 23:49:51 GMT):
after creating the the channel
mrkiouak (Tue, 07 Feb 2017 23:52:17 GMT):
Has joined the channel.
danielwatsonpro (Tue, 07 Feb 2017 23:59:05 GMT):
Has joined the channel.
yacovm (Tue, 07 Feb 2017 23:59:32 GMT):
@seand20tech regarding the "but got [...]" - can you please write here the numbers? :)
yacovm (Wed, 08 Feb 2017 00:01:59 GMT):
are you doing the guide from https://github.com/hyperledger/fabric/blob/master/docs/gettingstarted.md ?
yacovm (Wed, 08 Feb 2017 00:04:32 GMT):
Also if you can put here https://cryptii.com/decimal/text the numbers you get and convert them to a string and tell me what the string value is?
seand20tech (Wed, 08 Feb 2017 00:18:31 GMT):
@yacovm the contents of the PKIid array is: DEFAULT°-----BEGIN CERTIFICATE-----
MIICjDCCAjKgAwIBAgIUBEVwsSx0TmqdbzNwleNBBzoIT0wwCgYIKoZIzj0EAwIw
fzELMAkGA1UEBhMCVVMxEzARBgNVBAgTCkNhbGlmb3JuaWExFjAUBgNVBAcTDVNh
biBGcmFuY2lzY28xHzAdBgNVBAoTFkludGVybmV0IFdpZGdldHMsIEluYy4xDDAK
BgNVBAsTA1dXVzEUMBIGA1UEAxMLZXhhbXBsZS5jb20wHhcNMTYxMTExMTcwNzAw
WhcNMTcxMTExMTcwNzAwWjBjMQswCQYDVQQGEwJVUzEXMBUGA1UECBMOTm9ydGgg
Q2Fyb2xpbmExEDAOBgNVBAcTB1JhbGVpZ2gxGzAZBgNVBAoTEkh5cGVybGVkZ2Vy
IEZhYnJpYzEMMAoGA1UECxMDQ09QMFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAE
HBuKsAO43hs4JGpFfiGMkB/xsILTsOvmN2WmwpsPHZNL6w8HWe3xCPQtdG/XJJvZ
+C756KEsUBM3yw5PTfku8qOBpzCBpDAOBgNVHQ8BAf8EBAMCBaAwHQYDVR0lBBYw
FAYIKwYBBQUHAwEGCCsGAQUFBwMCMAwGA1UdEwEB/wQCMAAwHQYDVR0OBBYEFOFC
dcUZ4es3ltiCgAVDoyLfVpPIMB8GA1UdIwQYMBaAFBdnQj2qnoI/xMUdn1vDmdG1
nEgQMCUGA1UdEQQeMByCCm15aG9zdC5jb22CDnd3dy5teWhvc3QuY29tMAoGCCqG
SM49BAMCA0gAMEUCIDf9Hbl4xn3z4EwNKmilM9lX2Fq4jWpAaRVB97OmVEeyAiEA
25aDPQHGGq2AvhKT0wvt08cX1GTGCIbfmuLpMwKQj38=
-----END CERTIFICATE-----
seand20tech (Wed, 08 Feb 2017 00:19:33 GMT):
and the "but got" is 172.19.0.3:7051
seand20tech (Wed, 08 Feb 2017 00:20:48 GMT):
172.19.0.3 happens to be the IP address of the peer0 container
yacovm (Wed, 08 Feb 2017 00:22:10 GMT):
aha I know what's your problem
yacovm (Wed, 08 Feb 2017 00:22:37 GMT):
are you using https://github.com/hyperledger/fabric/blob/master/docs/gettingstarted.md ?
seand20tech (Wed, 08 Feb 2017 00:23:45 GMT):
yes
yacovm (Wed, 08 Feb 2017 00:24:58 GMT):
ok can you edit something in the `/docker-compose-gettingstarted.yml` and re-try please?
seand20tech (Wed, 08 Feb 2017 00:25:02 GMT):
sure
yacovm (Wed, 08 Feb 2017 00:25:24 GMT):
https://github.com/hyperledger/fabric/blob/master/examples/sfhackfest/channel_test.sh#L5
Prefix the entire line with `CORE_PEER_GOSSIP_IGNORESECURITY=true`
yacovm (Wed, 08 Feb 2017 00:25:43 GMT):
`CORE_PEER_GOSSIP_IGNORESECURITY=true
CORE_PEER_MSPCONFIGPATH=/etc/hyperledger/fabric/msp/sampleconfig CORE_PEER_COMMITTER_LEDGER_ORDERER=orderer:7050 peer channel create -c myc1 >>log.txt 2>&1`
yacovm (Wed, 08 Feb 2017 00:25:43 GMT):
`CORE_PEER_GOSSIP_IGNORESECURITY=true CORE_PEER_MSPCONFIGPATH=/etc/hyperledger/fabric/msp/sampleconfig CORE_PEER_COMMITTER_LEDGER_ORDERER=orderer:7050 peer channel create -c myc1 >>log.txt 2>&1`
yacovm (Wed, 08 Feb 2017 00:26:15 GMT):
and re-try everything
seand20tech (Wed, 08 Feb 2017 00:29:51 GMT):
this is better -- now i'm seeing these errors Failed obtaining connection for peer0:7051, PKIid:[112 101 101 114 48 58 55 48 53 49] reason: Authentication failure
seand20tech (Wed, 08 Feb 2017 00:29:52 GMT):
and
seand20tech (Wed, 08 Feb 2017 00:30:11 GMT):
Remote endpoint claims to be a different peer, expected [112 101 101 114 48 58 55 48 53 49] but got [49 55 50 46 49 57 46 48 46 51 58 55 48 53 49]
yacovm (Wed, 08 Feb 2017 00:30:40 GMT):
put them into that link i posted
seand20tech (Wed, 08 Feb 2017 00:30:44 GMT):
the 112 ... string is peer0:7051 and the but go string is 172.19.0.3:7051
yacovm (Wed, 08 Feb 2017 00:31:02 GMT):
aha! bingo
yacovm (Wed, 08 Feb 2017 00:31:08 GMT):
just as i thought
seand20tech (Wed, 08 Feb 2017 00:32:16 GMT):
should i put the CORE_PEER_GOSSIP_IGNORESECURITY=true bit on the channel join command in channel_test.sh as well?
yacovm (Wed, 08 Feb 2017 00:33:19 GMT):
no, it won't help
yacovm (Wed, 08 Feb 2017 00:33:34 GMT):
long story short- more is needed to be done if you want to have more than 1 peer
yacovm (Wed, 08 Feb 2017 00:33:50 GMT):
so:
yacovm (Wed, 08 Feb 2017 00:34:37 GMT):
1) we need to update the script, @bmos299 I believe this is yours right? Please contact me tomorrow and I can explain what needs to be fixed there.
2) seanand20tech- want me to walk you through in PMs?
seand20tech (Wed, 08 Feb 2017 00:34:53 GMT):
sure, if you don't mind
yacovm (Wed, 08 Feb 2017 00:37:14 GMT):
actually, try something before that-
https://github.com/hyperledger/fabric/blob/master/examples/sfhackfest/docker-compose-gettingstarted.yml#L60-L70
add there CORE_PEER_GOSSIP_ENDPOINT=peer0
yacovm (Wed, 08 Feb 2017 00:37:14 GMT):
actually, try something before that-
https://github.com/hyperledger/fabric/blob/master/examples/sfhackfest/docker-compose-gettingstarted.yml#L60-L70
add there `CORE_PEER_GOSSIP_ENDPOINT=peer0`
yacovm (Wed, 08 Feb 2017 00:37:17 GMT):
and see if that works ok?
kongakong (Wed, 08 Feb 2017 01:05:49 GMT):
Has joined the channel.
seand20tech (Wed, 08 Feb 2017 01:15:18 GMT):
to recap on this thread -- @yacovm and i debugged the issue and came up with two modifications to the channel_test.sh script from the examples
seand20tech (Wed, 08 Feb 2017 01:15:46 GMT):
1. run the peer channel create command with CORE_PEER_GOSSIP_IGNORESECURITY=true
seand20tech (Wed, 08 Feb 2017 01:16:32 GMT):
2. generate an anchor file containing the IP address of peer0 and the cert referenced above
yacovm (Wed, 08 Feb 2017 01:17:31 GMT):
the cert is actually not that important in this case.
BREWTAN (Wed, 08 Feb 2017 01:31:50 GMT):
Has joined the channel.
BREWTAN (Wed, 08 Feb 2017 01:32:11 GMT):
how to change block size without rebooting peer
mdevilliers (Wed, 08 Feb 2017 01:35:22 GMT):
Has joined the channel.
johnm (Wed, 08 Feb 2017 02:09:06 GMT):
Has joined the channel.
lafenicecc (Wed, 08 Feb 2017 02:10:22 GMT):
Has joined the channel.
ckeyer (Wed, 08 Feb 2017 02:12:50 GMT):
Has joined the channel.
warong (Wed, 08 Feb 2017 02:49:53 GMT):
Has joined the channel.
yp (Wed, 08 Feb 2017 02:57:40 GMT):
Has joined the channel.
Rokkinchic (Wed, 08 Feb 2017 03:18:23 GMT):
Has joined the channel.
py (Wed, 08 Feb 2017 03:24:55 GMT):
Has joined the channel.
rjkuro (Wed, 08 Feb 2017 03:31:04 GMT):
Has joined the channel.
hshimo (Wed, 08 Feb 2017 03:40:13 GMT):
Has joined the channel.
rnsastry (Wed, 08 Feb 2017 04:10:52 GMT):
Has joined the channel.
sachinsurvase (Wed, 08 Feb 2017 04:21:03 GMT):
Has joined the channel.
vigneswaran.r (Wed, 08 Feb 2017 04:24:31 GMT):
Has joined the channel.
raghavsood (Wed, 08 Feb 2017 05:18:45 GMT):
Anyone ever tried to do any network simulations (packet loss, throttled bandwidth) etc. on a set of docker nodes?
TimskiiTim (Wed, 08 Feb 2017 06:02:00 GMT):
Has joined the channel.
jansony1 (Wed, 08 Feb 2017 06:45:36 GMT):
2017-02-08 06:44:36.689 UTC [msp] GetDefaultSigningIdentity -> INFO 026 Obtaining default signing identity
Error: Error getting broadcast client: Error connecting to orderer:7050 due to grpc: timed out when dialing
Usage:
peer channel create [flags]
jansony1 (Wed, 08 Feb 2017 06:46:12 GMT):
http://hyperledger-fabric.readthedocs.io/en/latest/gettingstarted/2017-02-08 06:44:36.689 UTC [msp] GetDefaultSigningIdentity -> INFO 026 Obtaining default signing identity
Error: Error getting broadcast client: Error connecting to orderer:7050 due to grpc: timed out when dialing
Usage:
peer channel create [flags]
jansony1 (Wed, 08 Feb 2017 06:47:48 GMT):
hi ALL: when following this doc http://hyperledger-fabric.readthedocs.io/en/latest/gettingstarted/ and during the channel set-up phase, I got this error:2017-02-08 06:44:36.689 UTC [msp] GetDefaultSigningIdentity -> INFO 026 Obtaining default signing identity
Error: Error getting broadcast client: Error connecting to orderer:7050 due to grpc: timed out when dialing
Usage:
peer channel create [flags]
jansony1 (Wed, 08 Feb 2017 06:48:06 GMT):
hi ALL: when following this doc http://hyperledger-fabric.readthedocs.io/en/latest/gettingstarted and during the channel set-up phase, I got this error:2017-02-08 06:44:36.689 UTC [msp] GetDefaultSigningIdentity -> INFO 026 Obtaining default signing identity
Error: Error getting broadcast client: Error connecting to orderer:7050 due to grpc: timed out when dialing
Usage:
peer channel create [flags] Any advice?
jansony1 (Wed, 08 Feb 2017 06:49:09 GMT):
hi ALL: when following this doc http://hyperledger-fabric.readthedocs.io/en/latest/gettingstarted
and during the channel set-up phase, I got this error:
2017-02-08 06:44:36.689 UTC [msp] GetDefaultSigningIdentity -> INFO 026 Obtaining default signing identity
Error: Error getting broadcast client: Error connecting to orderer:7050 due to grpc: timed out when dialing
Usage:
peer channel create [flags]
Any advice?
padmaja (Wed, 08 Feb 2017 07:03:03 GMT):
Has joined the channel.
arvindupadhyaya (Wed, 08 Feb 2017 07:23:17 GMT):
Has joined the channel.
Sandeep.Kanaparthi (Wed, 08 Feb 2017 07:30:00 GMT):
Has joined the channel.
arvindupadhyaya (Wed, 08 Feb 2017 07:32:37 GMT):
Hi.. in the previous version of the fabric I was able to do REST api calls like {
"jsonrpc": "2.0",
"method": "deploy",
"params": {
"type": 1,
"chaincodeID":{
"name": "viato"
},
"ctorMsg": {
"function":"init",
"args":["lead", "initial value"]
},
"secureContext": "jim"
},
"id": 1
}
arvindupadhyaya (Wed, 08 Feb 2017 07:33:30 GMT):
to say localhost:7050/chaincode, but now this doesn't work anymore..
arvindupadhyaya (Wed, 08 Feb 2017 07:33:30 GMT):
to say localhost:7050/chaincode, but now this doesn't work anymore.. This used to work on v0.6..
arvindupadhyaya (Wed, 08 Feb 2017 07:33:30 GMT):
is the REST Api for chaincode supported in the latest version? Say localhost:7050/chaincode, but now this doesn't work anymore.. This used to work on v0.6..
arvindupadhyaya (Wed, 08 Feb 2017 07:33:30 GMT):
is the REST Api for chaincode supported in the latest version? Say localhost:7050/chaincode, but now this doesn't work anymore.. This used to work on v0.6.. if the REST Api is not available are there any other options to use chaincode from a client?
arvindupadhyaya (Wed, 08 Feb 2017 07:33:39 GMT):
any ideas on this?
arvindupadhyaya (Wed, 08 Feb 2017 07:34:31 GMT):
{
"jsonrpc": "2.0",
"method": "deploy",
"params": {
"type": 1,
"chaincodeID":{
"name": “test”
},
"ctorMsg": {
"function":"init",
"args”:[“a”, "initial value"]
},
"secureContext": "jim"
},
"id": 1
}
arvindupadhyaya (Wed, 08 Feb 2017 07:41:42 GMT):
I get back 锟斤拷
AStepanov (Wed, 08 Feb 2017 07:49:42 GMT):
Has joined the channel.
Ratnakar (Wed, 08 Feb 2017 08:01:36 GMT):
@arvindupadhyaya Yes REST API is deprecated from V1.0 , you can NodeSDK client to do the same
Please refer doc `http://hyperledger-fabric.readthedocs.io/en/latest/gettingstarted`
Ratnakar (Wed, 08 Feb 2017 08:03:55 GMT):
@jansony1 Isn't the Troubleshoot section http://hyperledger-fabric.readthedocs.io/en/latest/gettingstarted/#troubleshooting-optional not solved the issue ?
Sandeep.Kanaparthi (Wed, 08 Feb 2017 08:06:03 GMT):
[ ](https://chat.hyperledger.org/channel/fabric?msg=Cfe8XD6E2j2wjHCgB) @Ratnakar
Sandeep.Kanaparthi (Wed, 08 Feb 2017 08:08:01 GMT):
I ran into the same REST API issue. I used to connect to REST API directly from my client-side Javascript. I don't want to add another nodeJS middle tier just to use NodeSDK. Are there any alternatives to connect to a blockchain node directly from the browser?
jansony1 (Wed, 08 Feb 2017 08:09:04 GMT):
@Ratnakar Hi, this section does not work..And i have repeated the
docker-compose -f docker-compose-gettingstarted.yml up -d
and down section for many times. The channel just does not work with the same error
vu3mmg (Wed, 08 Feb 2017 08:54:35 GMT):
Has joined the channel.
Vadim (Wed, 08 Feb 2017 08:57:44 GMT):
@jansony1 seems that the ordering service is not running
vu3mmg (Wed, 08 Feb 2017 09:03:38 GMT):
A naive query , since the REST API is deprecated , could you please let me know the over all programming model from a app developer perspective . Is it some thing like the following ? developer will use chain code and will use node SDK to access the services provided by chain code ?
jansony1 (Wed, 08 Feb 2017 09:04:59 GMT):
@Vadim the container is running here:
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
956a27cb5fcf sfhackfest22017/fabric-peer:x86_64-0.7.0-snapshot-c7b3fe0 "sh -c './channel_tes" 43 minutes ago Up 43 minutes cli
5624ba5d9099 sfhackfest22017/fabric-peer:x86_64-0.7.0-snapshot-c7b3fe0 "peer node start --pe" 43 minutes ago Up 43 minutes 0.0.0.0:8056->7051/tcp peer2
954c8c8dd125 sfhackfest22017/fabric-peer:x86_64-0.7.0-snapshot-c7b3fe0 "peer node start --pe" 43 minutes ago Up 43 minutes 0.0.0.0:8055->7051/tcp peer1
35af00759ee6 sfhackfest22017/fabric-peer:x86_64-0.7.0-snapshot-c7b3fe0 "/bin/sh -c 'peer nod" 43 minutes ago Up 43 minutes 0.0.0.0:8051->7051/tcp, 0.0.0.0:8053->7053/tcp peer0
d4d831b76c0a sfhackfest22017/fabric-ca:x86_64-0.7.0-snapshot-6294c57 "sh -c 'sleep 10; fab" 43 minutes ago Up 43 minutes 0.0.0.0:8054->7054/tcp ca
d0faf11af98d sfhackfest22017/fabric-orderer:x86_64-0.7.0-snapshot-c7b3fe0 "orderer" 43 minutes ago Up 43 minutes 0.0.0.0:8050->7050/tcp orderer]
Vadim (Wed, 08 Feb 2017 09:05:02 GMT):
as far as I know, rest api is deprecated in favour of grpc
jansony1 (Wed, 08 Feb 2017 09:06:21 GMT):
@Vadim sorry， the message format is kind of clumsy
Vadim (Wed, 08 Feb 2017 09:09:01 GMT):
@jansony1 do you see any error on peers? If they are connected to the orderer?
Vadim (Wed, 08 Feb 2017 09:09:22 GMT):
e.g. do "docker logs 5624ba5d9099"
jansony1 (Wed, 08 Feb 2017 09:13:08 GMT):
@Vadim hi Vadim. Peer works fine itself, and i have not seen any log related to connect to orderers:
It ends up with creating system chaincode success:
2017-02-08 08:20:46.672 UTC [sysccapi] deploySysCC -> INFO 0b6 system chaincode qscc/(github.com/hyperledger/fabric/core/chaincode/qscc) deployed
2017-02-08 08:20:46.672 UTC [nodeCmd] initChainless -> INFO 0b7 Deployed chainless system chaincodess
2017-02-08 08:20:46.672 UTC [nodeCmd] serve -> INFO 0b8 Starting peer with ID=name:"peer2" , network ID=peer0, address=172.22.0.5:7051
2017-02-08 08:20:46.713 UTC [logging] SetModuleLevel -> DEBU 0b9 Module 'error' logger enabled for log level: WARNING
2017-02-08 08:20:46.714 UTC [nodeCmd] func4 -> INFO 0ba Starting profiling server with listenAddress = 0.0.0.0:6060
Vadim (Wed, 08 Feb 2017 09:13:44 GMT):
so when do you get the error message?
jansony1 (Wed, 08 Feb 2017 09:14:24 GMT):
@Vadim if there is a connection to orderers shown in your peers log? I think the error is coming from build the channel, and before peer send message to the orderers.
jansony1 (Wed, 08 Feb 2017 09:15:49 GMT):
@Vadim if there is a connection to orderers shown in your peers log? I think the error is coming from build the channel, and before peer send message to the orderers.
the error coming from this step docker-compose -f docker-compose-gettingstarted.yml up -d in this doc http://hyperledger-fabric.readthedocs.io/en/latest/gettingstarted/#troubleshooting-optional
which basically set up the container for channel, orderer, and peers.
jansony1 (Wed, 08 Feb 2017 09:16:39 GMT):
@Vadim if there is a connection to orderers shown in your peers log? I think the error is coming from build the channel, and before peer send message to the orderers.
the error coming from this step docker-compose -f docker-compose-gettingstarted.yml up -d in this doc http://hyperledger-fabric.readthedocs.io/en/latest/gettingstarted/#troubleshooting-optional
which basically set up the container for cli, channel, orderer, and peers.
and I see this error from cli shell.
jansony1 (Wed, 08 Feb 2017 09:17:20 GMT):
@Vadim and after set up all container, it will link them all
C0rWin (Wed, 08 Feb 2017 09:23:25 GMT):
@jansony1 are you trying to run this command? `CORE_PEER_COMMITTER_LEDGER_ORDERER=orderer:7050 peer channel create -c myc2`?
C0rWin (Wed, 08 Feb 2017 09:32:23 GMT):
>d0faf11af98d sfhackfest22017/fabric-orderer:x86_64-0.7.0-snapshot-c7b3fe0 "orderer" 43 minutes ago Up 43 minutes 0.0.0.0:8050->7050/tcp orderer]
^^^ According to this, you probably need `CORE_PEER_COMMITTER_LEDGER_ORDERER=orderer:8050`
arvindupadhyaya (Wed, 08 Feb 2017 09:43:35 GMT):
Hi I tried to do npm install as instructed here.. https://hyperledger-fabric.readthedocs.io/en/latest/gettingstarted/#curl-the-application-source-code-and-sdk-modules but the install failed.. i'm using a mac.. does the install require xcode libraries to be present?
jansony1 (Wed, 08 Feb 2017 09:46:35 GMT):
@C0rWin Hi C0rWin, CORE_PEER_COMMITTER_LEDGER_ORDERER=orderer:7050 peer channel create -c myc2，
this command is for mananuly build up the channel., its also not work. What i mentioned is step one build the network from docker-compose
TonyT (Wed, 08 Feb 2017 09:49:06 GMT):
@arvindupadhyaya what's the error message?
arvindupadhyaya (Wed, 08 Feb 2017 09:49:43 GMT):
something like this
gyp WARN download NVM_NODEJS_ORG_MIRROR is deprecated and will be removed in node-gyp v4, please use NODEJS_ORG_MIRROR
gyp WARN download NVM_NODEJS_ORG_MIRROR is deprecated and will be removed in node-gyp v4, please use NODEJS_ORG_MIRROR
xcode-select: error: tool 'xcodebuild' requires Xcode, but active developer directory '/Library/Developer/CommandLineTools' is a command line tools instance
xcode-select: error: tool 'xcodebuild' requires Xcode, but active developer directory '/Library/Developer/CommandLineTools' is a command line tools instance
No receipt for 'com.apple.pkg.CLTools_Executables' found at '/'.
No receipt for 'com.apple.pkg.DeveloperToolsCLILeo' found at '/'.
No receipt for 'com.apple.pkg.DeveloperToolsCLI' found at '/'.
gyp: No Xcode or CLT version detected!
gyp ERR! configure error
gyp ERR! stack Error: `gyp` failed with exit code: 1
gyp ERR! stack at ChildProcess.onCpExit (/Users/arvind/.nvm/versions/node/v6.9.5/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:305:16)
gyp ERR! stack at emitTwo (events.js:106:13)
gyp ERR! stack at ChildProcess.emit (events.js:191:7)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:215:12)
gyp ERR! System Darwin 16.4.0
gyp ERR! command "/Users/arvind/.nvm/versions/node/v6.9.5/bin/node" "/Users/arvind/.nvm/versions/node/v6.9.5/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "configure" "build"
gyp ERR! cwd /Users/arvind/hyperledger-fabric/node_modules/hashtable
gyp ERR! node -v v6.9.5
gyp ERR! node-gyp -v v3.4.0
gyp ERR! not ok
jansony1 (Wed, 08 Feb 2017 09:50:32 GMT):
@C0rWin Hi C0rWin, CORE_PEER_COMMITTER_LEDGER_ORDERER=orderer:7050 peer channel create -c myc2，
this command is for mananuly build up the channel., its also not work. What i mentioned is step one build the network from docker-compose
And from cli node, the doc said we should use 7050, which i think also should be 8050(the host port).
Have you go through the guidance?
TonyT (Wed, 08 Feb 2017 09:52:08 GMT):
Looks like you need XCode. I hate that node package.
Vadim (Wed, 08 Feb 2017 09:52:46 GMT):
@arvindupadhyaya have you tried to install and run xcode?
arvindupadhyaya (Wed, 08 Feb 2017 09:53:24 GMT):
Installing it now.. will update once its done
jansony1 (Wed, 08 Feb 2017 09:54:12 GMT):
@C0rWin both build-up from compose or manaully, all not works. So I think the error comes from channel or order not build up. But when i use docker ps, the ordered service is there..
Vadim (Wed, 08 Feb 2017 09:55:56 GMT):
@jansony1 can you change the port in the channel_test.sh and check whether that would work?
14gracel (Wed, 08 Feb 2017 09:58:10 GMT):
Has joined the channel.
jansony1 (Wed, 08 Feb 2017 10:02:01 GMT):
@Vadim it cames back with same error. Error getting broadcast client: Error connecting to orderer:8050 due to grpc: timed out when dialing
Vadim (Wed, 08 Feb 2017 10:02:32 GMT):
and if you try to create a channel manually?
jansony1 (Wed, 08 Feb 2017 10:10:59 GMT):
@Vadim yep，came the same error, so i think it came from channel or orderer service. While i do not where to find out~~
Vadim (Wed, 08 Feb 2017 10:11:25 GMT):
and if you specify IP address of the orderer instead of "orderer"?
jansony1 (Wed, 08 Feb 2017 10:11:39 GMT):
@Vadim try that also~~
Vadim (Wed, 08 Feb 2017 10:11:59 GMT):
so you tried it and it did not work?
jansony1 (Wed, 08 Feb 2017 10:13:55 GMT):
yes @Vadim
jansony1 (Wed, 08 Feb 2017 10:14:23 GMT):
@Vadim yep, it does not work neither.
Vadim (Wed, 08 Feb 2017 10:16:58 GMT):
well this is strange
Vadim (Wed, 08 Feb 2017 10:17:17 GMT):
from which container did you try that?
dolanort (Wed, 08 Feb 2017 10:45:35 GMT):
Hi, how do we connect 2 peers that are in their own containers but in 2 different host computers ?
dolanort (Wed, 08 Feb 2017 10:46:06 GMT):
is there an ENV var to set to tell a peer where to connect to another peer ?
jvsteiner (Wed, 08 Feb 2017 10:54:22 GMT):
Has joined the channel.
randomnerd (Wed, 08 Feb 2017 11:01:09 GMT):
@dolanort CORE_PEER_DISCOVERY_ROOTNODE
TonyT (Wed, 08 Feb 2017 11:14:23 GMT):
I'd be interested in seeing fabric deployed on GKE
TonyT (Wed, 08 Feb 2017 11:19:07 GMT):
will give it a try unless someone has a link
Eagel (Wed, 08 Feb 2017 11:38:10 GMT):
Has joined the channel.
patsToms (Wed, 08 Feb 2017 11:48:39 GMT):
Has joined the channel.
vu3mmg (Wed, 08 Feb 2017 11:52:05 GMT):
Dear Experts, when i delploy chain code , using cli , i am getting following error
vu3mmg (Wed, 08 Feb 2017 11:52:06 GMT):
root@877fd5a6fb70:/opt/gopath/src/github.com/hyperledger/fabric# peer chaincode deploy -n mycc -c '{Args": ["init", "a","100", "b", "200"]}'
11:48:15.700 [logging] LoggingInit -> DEBU 001 Setting default logging level to DEBUG for command 'chaincode'
Error: Chaincode argument error: invalid character 'A' looking for beginning of object key string
vu3mmg (Wed, 08 Feb 2017 11:52:11 GMT):
any pointers
vu3mmg (Wed, 08 Feb 2017 11:52:12 GMT):
?
vu3mmg (Wed, 08 Feb 2017 11:52:25 GMT):
i have spawned docker container
vu3mmg (Wed, 08 Feb 2017 11:52:38 GMT):
deployed chain code from mac to docker
vu3mmg (Wed, 08 Feb 2017 11:52:59 GMT):
then entered into the shell of the docker node and tried to deploy chain code
vu3mmg (Wed, 08 Feb 2017 11:53:09 GMT):
is the above procedure correct ?
randomnerd (Wed, 08 Feb 2017 11:59:54 GMT):
[ ](https://chat.hyperledger.org/channel/fabric?msg=a6E2iSbEm7XqcaXbL) @vu3mmg you forgot a quote before the capital A
vu3mmg (Wed, 08 Feb 2017 12:00:48 GMT):
Thank you
vu3mmg (Wed, 08 Feb 2017 12:01:11 GMT):
i blindly copied
vu3mmg (Wed, 08 Feb 2017 12:01:11 GMT):
http://hyperledger-fabric.readthedocs.io/en/v0.6/Setup/Chaincode-setup/#chaincode-deploy-via-cli-and-rest
randomnerd (Wed, 08 Feb 2017 12:04:46 GMT):
yikes, you should report it then
vu3mmg (Wed, 08 Feb 2017 12:18:16 GMT):
sure
vu3mmg (Wed, 08 Feb 2017 12:18:27 GMT):
will do that
vu3mmg (Wed, 08 Feb 2017 12:18:31 GMT):
one more help
vu3mmg (Wed, 08 Feb 2017 12:18:39 GMT):
could you please help to get this over
vu3mmg (Wed, 08 Feb 2017 12:18:40 GMT):
Error: Error building chaincode: rpc error: code = 2 desc = Error getting chaincode package bytes: Cannot generate hashcode from empty chaincode path
randomnerd (Wed, 08 Feb 2017 12:19:53 GMT):
obviously you didnt set chaincode path
vu3mmg (Wed, 08 Feb 2017 12:41:25 GMT):
I have a confusion related to chaincode path
vu3mmg (Wed, 08 Feb 2017 12:41:36 GMT):
my setup is like the following
vu3mmg (Wed, 08 Feb 2017 12:41:40 GMT):
mac host
vu3mmg (Wed, 08 Feb 2017 12:42:00 GMT):
docker based single node
vu3mmg (Wed, 08 Feb 2017 12:47:52 GMT):
so chain code we need to compile from docker image and run ?
jadhavajay (Wed, 08 Feb 2017 12:56:17 GMT):
Has joined the channel.
ayoub (Wed, 08 Feb 2017 13:12:43 GMT):
Has joined the channel.
ayoub (Wed, 08 Feb 2017 13:14:38 GMT):
Hi all, I am trying to setup a chain (the sfhackfest example in the documentation) . able to see 3 peers, orderer, ca, and cl running but when I run the node-sdk deploy.js I am getting this error:
ayoub (Wed, 08 Feb 2017 13:14:41 GMT):
error: [Peer.js]: GRPC client got an error response from the peer. Error: Failed to deserialize creator identity, err MSP DEFAULT is unknown
ayoub (Wed, 08 Feb 2017 13:15:19 GMT):
any suggestions on what might be causing this error?
ercw (Wed, 08 Feb 2017 13:17:03 GMT):
Hi. I read that Chain are working to include Greg Maxwell-style confidential transactions (https://blog.chain.com/hidden-in-plain-sight-transacting-privately-on-a-blockchain-835ab75c01cb#.k9x9plhc3). Is there something on the horizon for Fabric to incorporate similar tech?
arvindupadhyaya (Wed, 08 Feb 2017 13:22:11 GMT):
Hi @Vadim , @TonyT Xcode installation helped.. it will be useful for others if this step gets documented
randomnerd (Wed, 08 Feb 2017 13:22:42 GMT):
@ercw hyperledger v1 is promised to include private transactions as well
arvindupadhyaya (Wed, 08 Feb 2017 13:22:46 GMT):
But now if try GOPATH=$PWD node deploy.js its giving me an error
arvindupadhyaya (Wed, 08 Feb 2017 13:22:57 GMT):
Error: Cannot find module '/Users/arvind/hyperledger-fabric/node_modules/grpc/src/node/extension_binary/grpc_node.node'
at Function.Module._resolveFilename (module.js:469:15)
at Function.Module._load (module.js:417:25)
at Module.require (module.js:497:17)
at require (internal/module.js:20:19)
at Object.
arvindupadhyaya (Wed, 08 Feb 2017 13:22:57 GMT):
Error: Cannot find module '/Users/arvind/hyperledger-fabric/node_modules/grpc/src/node/extension_binary/grpc_node.node'
at Function.Module._resolveFilename (module.js:469:15)
at Function.Module._load (module.js:417:25)
at Module.require (module.js:497:17)
at require (internal/module.js:20:19)
at Object.
arvindupadhyaya (Wed, 08 Feb 2017 13:23:40 GMT):
where hyperledger-fabric is my local src folder
randomnerd (Wed, 08 Feb 2017 13:26:54 GMT):
@arvindupadhyaya try `rm -rf node_modules && npm i`
randomnerd (Wed, 08 Feb 2017 13:26:54 GMT):
@arvindupadhyaya try `rm -rf node_modules && npm i`
arvindupadhyaya (Wed, 08 Feb 2017 13:30:00 GMT):
@randomnerd it worked! but now its giving a different error
arvindupadhyaya (Wed, 08 Feb 2017 13:30:01 GMT):
info: Returning a new winston logger with default configurations
info: [Chain.js]: Constructed Chain instance: name - fabric-client1, securityEnabled: true, TCert download batch size: 10, network mode: true
info: [Peer.js]: Peer.const - url: grpc://localhost:8051 options grpc.ssl_target_name_override=tlsca, grpc.default_authority=tlsca
info: [Peer.js]: Peer.const - url: grpc://localhost:8055 options grpc.ssl_target_name_override=tlsca, grpc.default_authority=tlsca
info: [Peer.js]: Peer.const - url: grpc://localhost:8056 options grpc.ssl_target_name_override=tlsca, grpc.default_authority=tlsca
info: [Client.js]: Failed to load user "admin" from local key value store
info: [FabricCAClientImpl.js]: Successfully constructed Fabric CA service client: endpoint - {"protocol":"http","hostname":"localhost","port":8054}
info: [crypto_ecdsa_aes]: This class requires a KeyValueStore to save keys, no store was passed in, using the default store /Users/arvind/.hfc-key-store
events.js:160
throw er; // Unhandled 'error' event
^
Error: Connect Failed
at ClientDuplexStream._emitStatusIfDone (/Users/arvind/hyperledger-fabric/node_modules/grpc/src/node/src/client.js:201:19)
at ClientDuplexStream._readsDone (/Users/arvind/hyperledger-fabric/node_modules/grpc/src/node/src/client.js:169:8)
at readCallback (/Users/arvind/hyperledger-fabric/node_modules/grpc/src/node/src/client.js:229:12)
randomnerd (Wed, 08 Feb 2017 13:33:35 GMT):
as it says, you didnt specify keyvaluestore
arvindupadhyaya (Wed, 08 Feb 2017 13:34:16 GMT):
*no store was passed in, using the default store* so it should work right?
randomnerd (Wed, 08 Feb 2017 13:35:03 GMT):
oh
randomnerd (Wed, 08 Feb 2017 13:35:12 GMT):
missed that
randomnerd (Wed, 08 Feb 2017 13:35:35 GMT):
check if peer node is running, it says connect failed
arvindupadhyaya (Wed, 08 Feb 2017 13:39:20 GMT):
@randomnerd yes i didn't bring up the containers.. my bad
arvindupadhyaya (Wed, 08 Feb 2017 13:39:26 GMT):
info: Returning a new winston logger with default configurations
info: [Chain.js]: Constructed Chain instance: name - fabric-client1, securityEnabled: true, TCert download batch size: 10, network mode: true
info: [Peer.js]: Peer.const - url: grpc://localhost:8051 options grpc.ssl_target_name_override=tlsca, grpc.default_authority=tlsca
info: [Peer.js]: Peer.const - url: grpc://localhost:8055 options grpc.ssl_target_name_override=tlsca, grpc.default_authority=tlsca
info: [Peer.js]: Peer.const - url: grpc://localhost:8056 options grpc.ssl_target_name_override=tlsca, grpc.default_authority=tlsca
info: [Client.js]: Failed to load user "admin" from local key value store
info: [FabricCAClientImpl.js]: Successfully constructed Fabric CA service client: endpoint - {"protocol":"http","hostname":"localhost","port":8054}
info: [crypto_ecdsa_aes]: This class requires a KeyValueStore to save keys, no store was passed in, using the default store /Users/arvind/.hfc-key-store
[2017-02-08 19:08:04.173] [ERROR] Helper - Error: Calling enrollment endpoint failed with error [Error: socket hang up]
at ClientRequest.
randomnerd (Wed, 08 Feb 2017 13:40:19 GMT):
if you enrolled once, you cant do it again. you'll have to `rm -rf /Users/arvind/.hfc-key-store` and recreate containers
arvindupadhyaya (Wed, 08 Feb 2017 13:42:37 GMT):
info: Returning a new winston logger with default configurations
info: [Chain.js]: Constructed Chain instance: name - fabric-client1, securityEnabled: true, TCert download batch size: 10, network mode: true
info: [Peer.js]: Peer.const - url: grpc://localhost:8051 options grpc.ssl_target_name_override=tlsca, grpc.default_authority=tlsca
info: [Peer.js]: Peer.const - url: grpc://localhost:8055 options grpc.ssl_target_name_override=tlsca, grpc.default_authority=tlsca
info: [Peer.js]: Peer.const - url: grpc://localhost:8056 options grpc.ssl_target_name_override=tlsca, grpc.default_authority=tlsca
info: [Client.js]: Failed to load user "admin" from local key value store
info: [FabricCAClientImpl.js]: Successfully constructed Fabric CA service client: endpoint - {"protocol":"http","hostname":"localhost","port":8054}
info: [crypto_ecdsa_aes]: This class requires a KeyValueStore to save keys, no store was passed in, using the default store /Users/arvind/.hfc-key-store
[2017-02-08 19:11:17.482] [INFO] Helper - Successfully enrolled user 'admin'
info: [crypto_ecdsa_aes]: This class requires a KeyValueStore to save keys, no store was passed in, using the default store /Users/arvind/.hfc-key-store
[2017-02-08 19:11:17.501] [INFO] DEPLOY - Successfully obtained enrolled user to deploy the chaincode
[2017-02-08 19:11:17.501] [INFO] DEPLOY - Executing Deploy
error: [Peer.js]: GRPC client got an error response from the peer. Error: Chaincode exists mycc
arvindupadhyaya (Wed, 08 Feb 2017 13:42:47 GMT):
how do i delete an existing chaincode?
randomnerd (Wed, 08 Feb 2017 13:44:35 GMT):
no idea, just use a different name for it
randomnerd (Wed, 08 Feb 2017 13:44:48 GMT):
afaik you cant delete from blockchain :)
Technoprenerd (Wed, 08 Feb 2017 13:45:31 GMT):
Has joined the channel.
arvindupadhyaya (Wed, 08 Feb 2017 13:45:50 GMT):
sure..
pipor (Wed, 08 Feb 2017 13:46:13 GMT):
Has joined the channel.
googlielmo (Wed, 08 Feb 2017 13:48:19 GMT):
Has joined the channel.
arvindupadhyaya (Wed, 08 Feb 2017 13:48:39 GMT):
thanks a lot @randomnerd :)
kushnir.grigoriy (Wed, 08 Feb 2017 13:48:53 GMT):
Has joined the channel.
randomnerd (Wed, 08 Feb 2017 13:48:53 GMT):
no problem :)
jsalvachua (Wed, 08 Feb 2017 13:49:15 GMT):
Has joined the channel.
arvindupadhyaya (Wed, 08 Feb 2017 13:50:26 GMT):
@randomnerd , such steps should be documented for other noobs like me..
randomnerd (Wed, 08 Feb 2017 13:57:14 GMT):
yep the docs are pretty much incomplete at the moment, i had to learn this stuff the hard way :
randomnerd (Wed, 08 Feb 2017 13:57:14 GMT):
yep the docs are pretty much incomplete at the moment, i had to learn this stuff the hard way :S
arvindupadhyaya (Wed, 08 Feb 2017 13:59:07 GMT):
thanks for sharing :)
sk.karl (Wed, 08 Feb 2017 14:15:05 GMT):
Has joined the channel.
benjamin.matten (Wed, 08 Feb 2017 14:16:11 GMT):
Has joined the channel.
Basug (Wed, 08 Feb 2017 14:17:34 GMT):
Has joined the channel.
niteshthakrar (Wed, 08 Feb 2017 14:27:11 GMT):
Has joined the channel.
frank.felhoffer (Wed, 08 Feb 2017 14:33:24 GMT):
Has joined the channel.
cbf (Wed, 08 Feb 2017 14:39:56 GMT):
@randomnerd @arvindupadhyaya yes, and the docs are definitely a focus. It would really help if we could understand gaps or inconsistencies or incorrect statements in the docs... please feel free to add JIRAs to the fabric-docs board https://jira.hyperledger.org/secure/RapidBoard.jspa?rapidView=119&view=planning&selectedIssue=FAB-2114
cbf (Wed, 08 Feb 2017 14:40:16 GMT):
or post in #fabric-documentation
cbf (Wed, 08 Feb 2017 14:40:33 GMT):
suggestions for what could be improved
arvindupadhyaya (Wed, 08 Feb 2017 15:09:17 GMT):
@cbf I will post in #fabric-documentation
cbf (Wed, 08 Feb 2017 15:13:45 GMT):
@arvindupadhyaya awesome
cbf (Wed, 08 Feb 2017 15:13:50 GMT):
thanks
VladimirStarostenkov (Wed, 08 Feb 2017 15:38:22 GMT):
Has joined the channel.
vbortnik (Wed, 08 Feb 2017 15:56:21 GMT):
Has joined the channel.
marcusvcs (Wed, 08 Feb 2017 16:00:12 GMT):
Hi, i am getting this error on my chaincode while executing a query method, anyone knows what might be?ERRO 5be�[0m Got error: [c3ad1ffb-fc95-422d-811f-1f7c2c9750c1]Chaincode handler FSM cannot handle message (RANGE_QUERY_STATE) with payload size (18) while in state: ready
ERRO 5bf�[0m [c3ad1ffb]Error handling message, ending stream: [c3ad1ffb-fc95-422d-811f-1f7c2c9750c1]Chaincode handler validator FSM cannot handle message (ERROR) with payload size (146) while in state: ready
marcusvcs (Wed, 08 Feb 2017 16:00:12 GMT):
Hi, i am getting this error on my chaincode while executing a query method, anyone knows what might be?
ERRO 5be�[0m Got error: [c3ad1ffb-fc95-422d-811f-1f7c2c9750c1]Chaincode handler FSM cannot handle message (RANGE_QUERY_STATE) with payload size (18) while in state: ready
ERRO 5bf�[0m [c3ad1ffb]Error handling message, ending stream: [c3ad1ffb-fc95-422d-811f-1f7c2c9750c1]Chaincode handler validator FSM cannot handle message (ERROR) with payload size (146) while in state: ready
sword_linux (Wed, 08 Feb 2017 16:10:48 GMT):
Hi everyone, i got a problem when i try to use REST to test the _example 02_ chaincode on my local environment. The *deploy* and *invoke* are working. But i got a problem with *query* command. Here is my request:
```
{
"jsonrpc": "2.0",
"method": "query",
"params": {
"type": 1,
"chaincodeID":{
"name":"mycc"
},
"ctorMsg": {
"args":["query", "a"]
},
"secureContext": "jim"
},
"id": 3
}
```
And my error result:
```
{
"jsonrpc": "2.0",
"error": {
"code": -32003,
"message": "Query failure",
"data": "Error when querying chaincode: Error:Failed to launch chaincode spec(Could not get deployment transaction for mycc - LedgerError - ResourceNotFound: ledger: resource not found)"
},
"id": 3
}
```
Pls give any idea. Thanks!
sword_linux (Wed, 08 Feb 2017 16:10:48 GMT):
Hi everyone, i got a problem when i try to use REST to test the _example 02_ chaincode on my local environment. The *deploy* and *invoke* are working. But i got a problem with *query* command. Here is my request:
```
{
"jsonrpc": "2.0",
"method": "query",
"params": {
"type": 1,
"chaincodeID":{
"name":"mycc"
},
"ctorMsg": {
"args":["query", "a"]
},
"secureContext": "jim"
},
"id": 3
}
```
And my error result:
```
{
"jsonrpc": "2.0",
"error": {
"code": -32003,
"message": "Query failure",
"data": "Error when querying chaincode: Error:Failed to launch chaincode spec(Could not get deployment transaction for mycc - LedgerError - ResourceNotFound: ledger: resource not found)"
},
"id": 3
}
```
Pls give me any idea. Thanks!
sword_linux (Wed, 08 Feb 2017 16:11:56 GMT):
More a bit, here is request and request of *invoke* command:
```
{
"jsonrpc": "2.0",
"method": "invoke",
"params": {
"type": 1,
"chaincodeID":{
"name":"mycc"
},
"ctorMsg": {
"args":["invoke", "a", "b", "10"]
},
"secureContext": "jim"
},
"id": 3
}
```
```
{
"jsonrpc": "2.0",
"result": {
"status": "OK",
"message": "44235d89-1e07-464e-9a7b-069b3b60d960"
},
"id": 3
}
```
marcusvcs (Wed, 08 Feb 2017 16:16:15 GMT):
@sword_linux afaik ResourceNotFound means that your chaincode cannot be found, probably because of a deployment error. I would check the peer logs to see if there are any error in the chaincode compilation
jkirke (Wed, 08 Feb 2017 16:32:50 GMT):
Has joined the channel.
sword_linux (Wed, 08 Feb 2017 16:34:20 GMT):
@marcusvcs thanks. Now i try to run *deploy* REST again, but it gets error, here is my REST:
```
{
"jsonrpc": "2.0",
"method": "deploy",
"params": {
"type": 1,
"chaincodeID":{
"name": "mycc"
},
"input": {
"args":["init", "a", "100", "b", "200"]
}
},
"id": 1
}
```
And my result:
```
{
"jsonrpc": "2.0",
"error": {
"code": -32602,
"message": "Invalid params",
"data": "Payload must contain a CtorMsg with a Chaincode function name."
},
"id": 1
}
```
I don't know *CtorMsg*, i google it but i don't understand the meaning. Now i stuck
rjones (Wed, 08 Feb 2017 16:36:32 GMT):
Has left the channel.
angel-ibm (Wed, 08 Feb 2017 16:44:32 GMT):
Has joined the channel.
sword_linux (Wed, 08 Feb 2017 16:44:59 GMT):
@all i got this log when i run *deploy* command `vp0_1 | 16:42:25.333 [chaincode] Launch -> ERRO ee85 sending init failed(handler not found for chaincode mycc)`. Please help me explain it
muralisr (Wed, 08 Feb 2017 16:46:09 GMT):
@sword_linux are you using latest master ?
sword_linux (Wed, 08 Feb 2017 16:47:08 GMT):
@muralisr i'm using latest Docker image `hyperledger/fabric-peer:latest`
bfuentes@fr.ibm.com (Wed, 08 Feb 2017 16:47:51 GMT):
@sword_linux : do you have an init function like this ? func (t *SimpleChaincode) Init(stub shim.ChaincodeStubInterface, function string, args []string) ([]byte, error) {
fmt.Println("Init firing. Function will be ignored: " + function)
return nil, nil
}
bfuentes@fr.ibm.com (Wed, 08 Feb 2017 16:48:03 GMT):
or the main ?
sword_linux (Wed, 08 Feb 2017 16:51:10 GMT):
@bfuentes@fr.ibm.com i used https://github.com/hyperledger/fabric/blob/master/examples/chaincode/go/chaincode_example02/chaincode_example02.go code to test. As i see, this file doesn't have above function
arvindupadhyaya (Wed, 08 Feb 2017 16:53:20 GMT):
@sword_linux did you deploy the chaincode? after the docker images were up.. I used to do something like CORE_CHAINCODE_ID_NAME=mycc CORE_PEER_ADDRESS=0.0.0.0:7051 ./mycc where mycc is the compiled go code
sword_linux (Wed, 08 Feb 2017 16:56:28 GMT):
@arvindupadhyaya thank you so much. Now everything is work fine
sword_linux (Wed, 08 Feb 2017 16:57:15 GMT):
i forgot run this command on my container
arvindupadhyaya (Wed, 08 Feb 2017 16:58:12 GMT):
@sword_linux welcome! I wrote this piece of code in my notes because I used to run into this issue all the time
sword_linux (Wed, 08 Feb 2017 16:59:49 GMT):
so i have a question: In this case, we have to run a command on container, could i package this command in Docker image?
arvindupadhyaya (Wed, 08 Feb 2017 17:00:55 GMT):
I don't know.. i'm new to docker :)
sword_linux (Wed, 08 Feb 2017 17:02:30 GMT):
:)
Basug (Wed, 08 Feb 2017 17:06:24 GMT):
All - looking to build docker image for use with java sdk. any pointers ?
Basug (Wed, 08 Feb 2017 17:06:44 GMT):
I have it all working with 0.6, but wanted to get it running with 1.0
paulw (Wed, 08 Feb 2017 17:21:43 GMT):
Has joined the channel.
mikezaccardo (Wed, 08 Feb 2017 21:00:09 GMT):
Has joined the channel.
rjones (Wed, 08 Feb 2017 22:05:02 GMT):
Has joined the channel.
ongkhaiwei (Thu, 09 Feb 2017 01:43:47 GMT):
Has joined the channel.
cbf (Thu, 09 Feb 2017 02:22:55 GMT):
@Basug try fabric-test image on hub.docker.com/u/hyperledger org
Basug (Thu, 09 Feb 2017 02:25:57 GMT):
@cbf - don't see that image (fabric-test) @ https://hub.docker.com/u/hyperledger/
cbf (Thu, 09 Feb 2017 02:27:13 GMT):
hmmm maybe fabric-testenv - you might need to build it
Honglei (Thu, 09 Feb 2017 02:27:48 GMT):
Has joined the channel.
Basug (Thu, 09 Feb 2017 02:27:51 GMT):
was about to ask - I could build it, where could I find the docker file ?
cbf (Thu, 09 Feb 2017 02:27:59 GMT):
basically this is image we use for testing
Basug (Thu, 09 Feb 2017 02:28:13 GMT):
neat !
sword_linux (Thu, 09 Feb 2017 02:28:30 GMT):
@cbf i have a question: after i update my code, what should i do with old container? Because the old container is running previous my code. If i run new container with updated code, everything is change
sword_linux (Thu, 09 Feb 2017 02:28:30 GMT):
@cbf i have a question: after i update my code, what should i do with old container? Because the old container is running my previous code. If i run a new container with updated code, everything is change
cbf (Thu, 09 Feb 2017 02:28:43 GMT):
@greg.haskins could tell you but chase the unit-tests target in fabric/Makefile
Basug (Thu, 09 Feb 2017 02:29:07 GMT):
ok.
cbf (Thu, 09 Feb 2017 02:29:43 GMT):
@sword_linux if you started with docker-compose up -d then docker-compose down will clean up
cbf (Thu, 09 Feb 2017 02:30:21 GMT):
@Basug sorry am on my cell phone at MIA so can't dig
Basug (Thu, 09 Feb 2017 02:30:52 GMT):
no worries - i will figure it out, thanks for pointing out..
Basug (Thu, 09 Feb 2017 02:30:56 GMT):
safe travels
sword_linux (Thu, 09 Feb 2017 02:40:07 GMT):
@cbf sorry, i mean how to package my chaincode code to Docker image and run it?
greg.haskins (Thu, 09 Feb 2017 02:40:22 GMT):
@Basug I am not clear on what you are trying to do, but within fabric.git "make docker" should build all hyperledger/fabric-* images
greg.haskins (Thu, 09 Feb 2017 02:40:57 GMT):
which would include fabric-javaenv
greg.haskins (Thu, 09 Feb 2017 02:41:45 GMT):
@sword_linux i assume you are using a netmode deployment and you are asking how do you update it?
rahulhegde (Thu, 09 Feb 2017 02:41:53 GMT):
For v1.0 - return status code >=0 to <500 is considered as endorsement success and anything >500 as endorsement failure by the Fabric SDK?
rahulhegde (Thu, 09 Feb 2017 02:41:53 GMT):
For v1.0 Architecture - return status code by the user-chain code >=0 to <500 is considered as endorsement success and anything >500 as endorsement failure by the Fabric SDK?
greg.haskins (Thu, 09 Feb 2017 02:42:22 GMT):
@rahulhegde technically >= 500 ;)
rahulhegde (Thu, 09 Feb 2017 02:43:33 GMT):
yes >= 500 and will be checked in the Fabric SDK?
sword_linux (Thu, 09 Feb 2017 02:45:53 GMT):
@greg.haskins no, i'm learning how to deployment my code and how to update it. So pls give me more about `netmode deployment`
zhoupeiwen (Thu, 09 Feb 2017 03:20:36 GMT):
Has joined the channel.
xiejunxi (Thu, 09 Feb 2017 03:24:16 GMT):
Has joined the channel.
chenxl (Thu, 09 Feb 2017 03:29:43 GMT):
Has joined the channel.
zhangmenghang (Thu, 09 Feb 2017 03:34:20 GMT):
Has joined the channel.
AndyJi (Thu, 09 Feb 2017 03:39:30 GMT):
Has joined the channel.
t-watana (Thu, 09 Feb 2017 06:36:56 GMT):
Has joined the channel.
shibo.lin (Thu, 09 Feb 2017 06:52:33 GMT):
Has joined the channel.
siddhid (Thu, 09 Feb 2017 08:11:24 GMT):
Has joined the channel.
mjkong (Thu, 09 Feb 2017 08:33:36 GMT):
Has joined the channel.
mjkong (Thu, 09 Feb 2017 08:33:42 GMT):
tls
raanaaray (Thu, 09 Feb 2017 08:35:17 GMT):
Has joined the channel.
snehas (Thu, 09 Feb 2017 08:37:57 GMT):
Has joined the channel.
ashnur (Thu, 09 Feb 2017 09:04:33 GMT):
Has joined the channel.
zemtsov (Thu, 09 Feb 2017 09:10:41 GMT):
Has joined the channel.
BlockchainSource (Thu, 09 Feb 2017 09:34:20 GMT):
Has joined the channel.
BlockchainSource (Thu, 09 Feb 2017 09:43:50 GMT):
i'm interested in setting up fabric on ubuntu so i can start developing chaincode in go. i looked at "getting started" https://hyperledger-fabric.readthedocs.io/en/latest/gettingstarted/ but ran into some issues with the peers and `sendToEndpoint -> WARN 1ec Failed obtaining connection for peer0:7051` and `reason: Authentication failure`. the containers are running but just lots of these errors...is this the best place to get started?
yacovm (Thu, 09 Feb 2017 09:44:33 GMT):
yes @BlockchainSource
yacovm (Thu, 09 Feb 2017 09:45:02 GMT):
how did you set up the system? are you using a `docker-compose.yml` file?
yacovm (Thu, 09 Feb 2017 09:45:04 GMT):
can you share it?
BlockchainSource (Thu, 09 Feb 2017 09:45:18 GMT):
i followed the instructions in that link
BlockchainSource (Thu, 09 Feb 2017 09:45:20 GMT):
so yes
BlockchainSource (Thu, 09 Feb 2017 09:45:45 GMT):
so i downloaded the hackfest which download all images and start them
yacovm (Thu, 09 Feb 2017 09:46:32 GMT):
aha so you're using https://github.com/hyperledger/fabric/blob/master/examples/sfhackfest/docker-compose-gettingstarted.yml ?
BlockchainSource (Thu, 09 Feb 2017 09:46:43 GMT):
yes
yacovm (Thu, 09 Feb 2017 09:46:47 GMT):
I see.
yacovm (Thu, 09 Feb 2017 09:47:05 GMT):
and you're running: https://github.com/hyperledger/fabric/blob/master/examples/sfhackfest/channel_test.sh ?
BlockchainSource (Thu, 09 Feb 2017 09:47:22 GMT):
i have a clean machine with ubuntu 16.04, docker, docker compose etc
BlockchainSource (Thu, 09 Feb 2017 09:47:27 GMT):
didn't yet
BlockchainSource (Thu, 09 Feb 2017 09:47:36 GMT):
i just started the containers and look in the logs
Jonas.Hedin (Thu, 09 Feb 2017 09:48:31 GMT):
Doesn't channel_test.sh run automatically in the orderer?
yacovm (Thu, 09 Feb 2017 09:48:52 GMT):
in the CLI
Jonas.Hedin (Thu, 09 Feb 2017 09:49:05 GMT):
Yeah I meant CLI
yacovm (Thu, 09 Feb 2017 09:49:07 GMT):
so you did "docker-compose up" and after a while you saw these errors, right?
yacovm (Thu, 09 Feb 2017 09:49:17 GMT):
well that's because there is a "bug" in the script
BlockchainSource (Thu, 09 Feb 2017 09:49:21 GMT):
i am all new to the setup so i don't know. however my expectation is that the docker-compose file sets up all what is needed
yacovm (Thu, 09 Feb 2017 09:49:24 GMT):
want to patch it?
yacovm (Thu, 09 Feb 2017 09:49:28 GMT):
I mean I can give you a patch set
BlockchainSource (Thu, 09 Feb 2017 09:49:29 GMT):
yes
yacovm (Thu, 09 Feb 2017 09:49:31 GMT):
you can apply it
BlockchainSource (Thu, 09 Feb 2017 09:49:45 GMT):
sure
yacovm (Thu, 09 Feb 2017 09:49:50 GMT):
https://gerrit.hyperledger.org/r/#/c/5691/
BlockchainSource (Thu, 09 Feb 2017 09:50:22 GMT):
btw does the linux foundation id work as login in gerrit?
yacovm (Thu, 09 Feb 2017 09:50:37 GMT):
should work
BlockchainSource (Thu, 09 Feb 2017 09:57:20 GMT):
@yacovm i patched `channel_test.sh`, do i need to rebuild?
yacovm (Thu, 09 Feb 2017 09:57:29 GMT):
no
yacovm (Thu, 09 Feb 2017 09:57:38 GMT):
the script doesn't effect the build
BlockchainSource (Thu, 09 Feb 2017 09:58:03 GMT):
so do i run this manually?
BlockchainSource (Thu, 09 Feb 2017 09:58:08 GMT):
the script
yacovm (Thu, 09 Feb 2017 09:58:11 GMT):
hmmm
yacovm (Thu, 09 Feb 2017 09:58:17 GMT):
oh
yacovm (Thu, 09 Feb 2017 09:58:19 GMT):
actually
BlockchainSource (Thu, 09 Feb 2017 09:58:30 GMT):
what i did: down, patch script, build, up
BlockchainSource (Thu, 09 Feb 2017 09:58:33 GMT):
see errors
yacovm (Thu, 09 Feb 2017 09:58:35 GMT):
you know what
yacovm (Thu, 09 Feb 2017 09:58:38 GMT):
re-build
yacovm (Thu, 09 Feb 2017 09:58:59 GMT):
oh damn
yacovm (Thu, 09 Feb 2017 09:59:07 GMT):
` image: sfhackfest22017/fabric-peer:x86_64-0.7.0-snapshot-c7b3fe0`
BlockchainSource (Thu, 09 Feb 2017 09:59:18 GMT):
`handleMessage -> WARN 232 No such channel`
BlockchainSource (Thu, 09 Feb 2017 09:59:54 GMT):
the previous errors i don't see atm
yacovm (Thu, 09 Feb 2017 09:59:59 GMT):
I think that patching the script won't cut it, and the docker image needs to be updated because probably the channel_test.sh is taken from the file system of the docker image
BlockchainSource (Thu, 09 Feb 2017 10:01:07 GMT):
the image you list i use
yacovm (Thu, 09 Feb 2017 10:01:14 GMT):
hmm on 2nd thought:
https://github.com/hyperledger/fabric/blob/master/examples/sfhackfest/docker-compose-gettingstarted.yml#L170
yacovm (Thu, 09 Feb 2017 10:01:17 GMT):
maybe it will
yacovm (Thu, 09 Feb 2017 10:01:51 GMT):
so you don't see anymore that `Authentication failure` error?
BlockchainSource (Thu, 09 Feb 2017 10:02:01 GMT):
no
BlockchainSource (Thu, 09 Feb 2017 10:02:20 GMT):
the line you wrote kind of indicates the script comes from github
BlockchainSource (Thu, 09 Feb 2017 10:02:31 GMT):
not local
yacovm (Thu, 09 Feb 2017 10:03:10 GMT):
no, it comes from local IMO
BlockchainSource (Thu, 09 Feb 2017 10:06:06 GMT):
@yacovm do you have a link to the Dockerfile that produces the peer image?
BlockchainSource (Thu, 09 Feb 2017 10:06:32 GMT):
interested to see if there's a copy or add of files from my host's local
yacovm (Thu, 09 Feb 2017 10:07:17 GMT):
No. Maybe @bmos299
BlockchainSource (Thu, 09 Feb 2017 10:10:11 GMT):
see this without Dockerfile https://hub.docker.com/r/sfhackfest22017/fabric-peer/tags/
BlockchainSource (Thu, 09 Feb 2017 10:14:26 GMT):
so i looked at the `cli` container's `channel_test.sh` and it's the one i patched.
BlockchainSource (Thu, 09 Feb 2017 10:14:51 GMT):
`docker exec -it cli bash` and then cat the script
yacovm (Thu, 09 Feb 2017 10:14:59 GMT):
yeah but in https://github.com/hyperledger/fabric/blob/master/examples/sfhackfest/docker-compose-gettingstarted.yml#L170 it says (I think) that the CLI takes the script from the local file system, doesn't it?
yacovm (Thu, 09 Feb 2017 10:15:11 GMT):
I mean- if you managed to patch the script, it was on your local directory, wasn't it?
BlockchainSource (Thu, 09 Feb 2017 10:15:18 GMT):
local to the container yes
yacovm (Thu, 09 Feb 2017 10:15:28 GMT):
now, I think it's outside of the container
BlockchainSource (Thu, 09 Feb 2017 10:15:30 GMT):
the volume maps the script
yacovm (Thu, 09 Feb 2017 10:15:30 GMT):
isn't it?
BlockchainSource (Thu, 09 Feb 2017 10:15:33 GMT):
no
yacovm (Thu, 09 Feb 2017 10:15:34 GMT):
yeah
yacovm (Thu, 09 Feb 2017 10:15:53 GMT):
but- if the volume maps the script to the container, doesn't it mean- the source of the script is outside of the container?
BlockchainSource (Thu, 09 Feb 2017 10:16:10 GMT):
ah yes it takes local
BlockchainSource (Thu, 09 Feb 2017 10:16:20 GMT):
still errors...will continue to look at that
JonathanTan (Thu, 09 Feb 2017 10:16:26 GMT):
Hi everyone, has anyone used the x86_64-0.3.0 tagged docker image? is it v0.6?
yacovm (Thu, 09 Feb 2017 10:16:29 GMT):
what errors do you see now?
BlockchainSource (Thu, 09 Feb 2017 10:16:49 GMT):
[ ](https://chat.hyperledger.org/channel/fabric?msg=KZhdtHHPeeQPcuuqA) this
yacovm (Thu, 09 Feb 2017 10:17:03 GMT):
can you write here the entire line?
yacovm (Thu, 09 Feb 2017 10:17:08 GMT):
it prints the message too
BlockchainSource (Thu, 09 Feb 2017 10:18:16 GMT):
`peer2 | 2017-02-09 10:13:16.026 UTC [gossip-172.19.0.5:7051] handleMessage -> WARN 1ed No such channel [116 101 115 116 99 104 97 105 110 105 100] discarding message channel:"testchainid" tag:CHAN_OR_ORG stateInfoPullReq:<>`
yacovm (Thu, 09 Feb 2017 10:19:11 GMT):
aha
yacovm (Thu, 09 Feb 2017 10:19:13 GMT):
I have an idea
yacovm (Thu, 09 Feb 2017 10:19:19 GMT):
do `docker ps`
yacovm (Thu, 09 Feb 2017 10:19:23 GMT):
and then grab the container id of `peer0`
yacovm (Thu, 09 Feb 2017 10:19:39 GMT):
and then do `docker exec -it CONTAINER_ID /bin/bash`
yacovm (Thu, 09 Feb 2017 10:19:49 GMT):
when the CONTAINER_ID is the ID you grabbed from `docker ps`
yacovm (Thu, 09 Feb 2017 10:19:58 GMT):
this logs you into the container
yacovm (Thu, 09 Feb 2017 10:20:04 GMT):
there, do `ps -ef | grep peer`
yacovm (Thu, 09 Feb 2017 10:20:08 GMT):
and tell me what you see
BlockchainSource (Thu, 09 Feb 2017 10:20:39 GMT):
root@50c0df2165ee:/opt/gopath/src/github.com/hyperledger/fabric/peer# ps -ef | grep peer
root 1 0 0 10:12 ? 00:00:00 /bin/sh -c peer node start
root 5 1 0 10:12 ? 00:00:04 peer node start
root 22 13 0 10:20 ? 00:00:00 grep --color=auto peer
yacovm (Thu, 09 Feb 2017 10:20:58 GMT):
great
yacovm (Thu, 09 Feb 2017 10:21:00 GMT):
that's the problem
yacovm (Thu, 09 Feb 2017 10:21:09 GMT):
go to the docker-compose file
yacovm (Thu, 09 Feb 2017 10:21:18 GMT):
https://github.com/hyperledger/fabric/blob/master/examples/sfhackfest/docker-compose-gettingstarted.yml#L102 this line
yacovm (Thu, 09 Feb 2017 10:21:21 GMT):
needs to be also in peer0
ThiruVijayan (Thu, 09 Feb 2017 10:21:50 GMT):
Has joined the channel.
BlockchainSource (Thu, 09 Feb 2017 10:23:09 GMT):
fixed and now up...
danieldewar (Thu, 09 Feb 2017 10:25:04 GMT):
Has joined the channel.
BlockchainSource (Thu, 09 Feb 2017 10:26:07 GMT):
root@ac75ea0f8958:/opt/gopath/src/github.com/hyperledger/fabric/peer# ps -ef | grep peer
root 1 0 0 10:22 ? 00:00:01 peer node start --peer-defaultchain=false
root 20 11 0 10:25 ? 00:00:00 grep --color=auto peer
BlockchainSource (Thu, 09 Feb 2017 10:26:41 GMT):
no errors in the logs afaics
BlockchainSource (Thu, 09 Feb 2017 10:26:58 GMT):
is there something to check to know it works or what is suggested to run to test all good?
BlockchainSource (Thu, 09 Feb 2017 10:28:34 GMT):
oh now i see some errors in peer1
BlockchainSource (Thu, 09 Feb 2017 10:28:52 GMT):
`peer1 | 2017-02-09 10:23:50.186 UTC [gossip-172.19.0.4:7051] ValidateAliveMsg -> WARN 1eb Don't have certificate for membership:
BlockchainSource (Thu, 09 Feb 2017 10:29:04 GMT):
and `peer1 | 2017-02-09 10:23:53.815 UTC [gossip-172.19.0.4:7051] getOrgOfPeer -> ERRO 1f1 Failed getting certificate by PKIid: [49 55 50 46 49 57 46 48 46 53 58 55 48 53 49] : PkiID wasn't found`
BlockchainSource (Thu, 09 Feb 2017 10:29:19 GMT):
same with `peer2`
BlockchainSource (Thu, 09 Feb 2017 10:29:51 GMT):
nothing in `peer0`
yacovm (Thu, 09 Feb 2017 10:29:58 GMT):
this is expected
yacovm (Thu, 09 Feb 2017 10:30:07 GMT):
and as long as it doesn't log this for ever
yacovm (Thu, 09 Feb 2017 10:30:08 GMT):
it's ok
yacovm (Thu, 09 Feb 2017 10:30:29 GMT):
if it logs it continuously we have a problem, but at startup it's ok
BlockchainSource (Thu, 09 Feb 2017 10:33:12 GMT):
ok, thanks so far for helping out with the missing patches.
yacovm (Thu, 09 Feb 2017 10:33:18 GMT):
sure, np
yacovm (Thu, 09 Feb 2017 10:33:31 GMT):
by the way- the --defaultChain thing is critical
yacovm (Thu, 09 Feb 2017 10:33:54 GMT):
the other errors you see in the log file are not critical as long as you have `CORE_PEER_GOSSIP_ORGLEADER=true` in all peers in the yaml file
yacovm (Thu, 09 Feb 2017 10:33:54 GMT):
the other errors you saw in the log file are not critical as long as you have `CORE_PEER_GOSSIP_ORGLEADER=true` in all peers in the yaml file
dangma (Thu, 09 Feb 2017 10:35:08 GMT):
Has joined the channel.
kiewza (Thu, 09 Feb 2017 10:43:27 GMT):
Hi, I'm using v.0.6. after I tried to deploy chaincode via HFC. I got the error below on the PEER node and it seems I cannot query the transaction that deploy though that chaincode. I tried to look in to folder $GOPATH/src as well but there was no "build-chaincode" folder there. Could anyone suggest on this?. Thanks so much
vp0_1 | 09:07:01.110 [dockercontroller] deployImage -> ERRO 1952 Error building images: The command '/bin/sh -c go install build-chaincode && cp src/build-chaincode/vendor/github.com/hyperledger/fabric/peer/core.yaml $GOPATH/bin && mv $GOPATH/bin/build-chaincode $GOPATH/bin/cb6162bf509a454a0102eedadae9d40d53cf57eeb2ab9e27dfb7858e54a88743' returned a non-zero code: 1
vp0_1 | 09:07:01.110 [dockercontroller] deployImage -> ERRO 1953 Image Output:
vp0_1 | ********************
vp0_1 | Step 1 : FROM hyperledger/fabric-baseimage
vp0_1 | ---> 4ac07a26ca7a
vp0_1 | Step 2 : COPY . $GOPATH/src/build-chaincode/
vp0_1 | ---> Using cache
vp0_1 | ---> 4ef69ad891aa
vp0_1 | Step 3 : WORKDIR $GOPATH
vp0_1 | ---> Using cache
vp0_1 | ---> 3dda085985b2
vp0_1 | Step 4 : RUN go install build-chaincode && cp src/build-chaincode/vendor/github.com/hyperledger/fabric/peer/core.yaml $GOPATH/bin && mv $GOPATH/bin/build-chaincode $GOPATH/bin/cb6162bf509a454a0102eedadae9d40d53cf57eeb2ab9e27dfb7858e54a88743
vp0_1 | ---> Running in f2afbcfffec4
vp0_1 | can't load package: package build-chaincode: no buildable Go source files in /opt/gopath/src/build-chaincode
vp0_1 |
vp0_1 | ********************
vp0_1 | 09:07:01.110 [container] unlockContainer -> DEBU 1954 container lock deleted(dev-vp0-cb6162bf509a454a0102eedadae9d40d53cf57eeb2ab9e27dfb7858e54a88743)
mastersingh24 (Thu, 09 Feb 2017 11:25:57 GMT):
@kiewza - how did you deploy the chaincode? can you post the command you tried?
jonreid (Thu, 09 Feb 2017 11:41:08 GMT):
Has joined the channel.
debkhoo (Thu, 09 Feb 2017 12:04:21 GMT):
Has joined the channel.
arvindupadhyaya (Thu, 09 Feb 2017 12:11:36 GMT):
Hi.. has anyone tried to `browserify` the code used here https://hyperledger-fabric.readthedocs.io/en/latest/gettingstarted/#use-node-sdk-to-registerenroll-user-and-deployinvokequery ? I am a getting a weird error which is to do with `grpc`
mastersingh24 (Thu, 09 Feb 2017 12:33:27 GMT):
hi @arvindupadhyaya - I assume you are trying to run all the that code within a browser (hence browserify)? Unfortunately GRPC (the protocol we use for communication with the peer and ordering nodes) is not supported directly from within a browser
arvindupadhyaya (Thu, 09 Feb 2017 12:34:56 GMT):
@mastersingh24 yes.. I am trying to embed it into an angularjs app.. any ideas or suggestions?
Vadim (Thu, 09 Feb 2017 12:37:59 GMT):
@arvindupadhyaya use nodejs for backend and install sdk there
arvindupadhyaya (Thu, 09 Feb 2017 12:39:01 GMT):
yes @Vadim that's a good solution.. thank you
rahulhegde (Thu, 09 Feb 2017 14:11:25 GMT):
@mastersingh24 @snehas @bmos299
Few question on v1.0 architecture
1. Multiple endorsement proposal request call to the same peer, will result in peer serializing the endorsement proposal call to the user chain-code.
This mean user-chain code can define global variables to cache data across?
2. Which logging library needs to be used by the user-chain code. We found https://github.com/op/go-logging in example but had to do go install package.
Would this package be part of the Chaincode environment package, else my understand we would end up with compilation failure during chaincode deployment?
rahulhegde (Thu, 09 Feb 2017 14:11:25 GMT):
@mastersingh24 @snehas @bmos299
Few question on v1.0 architecture
1. Multiple endorsement proposal request call to the same peer, will result in peer serializing the endorsement proposal call to the user chain-code. Is this correct?
If yes - this mean user-chain code can define global variables to cache data across multiple endorsement simulation call?
2. Which logging library needs to be used by the user-chain code. We found https://github.com/op/go-logging in example but had to do go install package.
Would this package be part of the Chaincode environment package, else my understand we would end up with compilation failure during chaincode deployment?
rahulhegde (Thu, 09 Feb 2017 14:22:11 GMT):
3. We are planning to adopt the same unit-testing methodology for our user-chain code as done for examples (https://github.com/hyperledger/fabric/blob/master/examples/chaincode/go/chaincode_example02/chaincode_example02_test.go) present in the fabric repository. This uses go test and provides a shim stub to verify the chain code functionality. We consider this as recommended way to verify the user chain-code functionally in silo, please confirm?
Now going forward – we are considering Fabric architecture will support a Query Interface between two different chain-codes. Like A-B channel deployed chain-code (requester) will query A-B-C deployed chain-code (responder) (on same peer only?). This will cause the requester chaincode to perform certain actions depending upon the query response.
We consider the same unit test methodology will support to control the responder chain-code query response (may be by first performing a invoke via test case step) so that the requester chaincode gets the test-case expected query response to perform expected-action. Could you please confirm.
juslee (Thu, 09 Feb 2017 14:32:13 GMT):
Has joined the channel.
anuragvijayvergia (Thu, 09 Feb 2017 14:45:37 GMT):
Has joined the channel.
crow15 (Thu, 09 Feb 2017 15:12:42 GMT):
Has joined the channel.
AdnanC (Thu, 09 Feb 2017 15:32:18 GMT):
Has joined the channel.
latitiah (Thu, 09 Feb 2017 15:33:14 GMT):
Has joined the channel.
bfuentes@fr.ibm.com (Thu, 09 Feb 2017 15:36:36 GMT):
Does anyone know how chaincode upgrades will be implemented for V1 ?
bfuentes@fr.ibm.com (Thu, 09 Feb 2017 15:40:06 GMT):
I saw this : https://jira.hyperledger.org/browse/FAB-183
bfuentes@fr.ibm.com (Thu, 09 Feb 2017 15:44:33 GMT):
maybe is enough for my knowledge :)
muralisr (Thu, 09 Feb 2017 16:08:46 GMT):
@bfuentes@fr.ibm.com that's definitely a start
muralisr (Thu, 09 Feb 2017 16:11:11 GMT):
essentially upgrade is very simlar to `deploy` except that the chaincode referenced by the name needs to have been deployed earlier
ayoub (Thu, 09 Feb 2017 17:16:47 GMT):
hi all, anybody knows if there is a fabric-composer channel?
mastersingh24 (Thu, 09 Feb 2017 17:23:39 GMT):
there is now
subbu165 (Thu, 09 Feb 2017 17:39:16 GMT):
Has joined the channel.
bmos299 (Thu, 09 Feb 2017 21:02:46 GMT):
@rahulhedge do you want take the questions to the fabric-quality channel and we will work closely with you?
sstone1 (Thu, 09 Feb 2017 21:06:02 GMT):
Related to chaincode upgrade, is chaincode list (from the SDKs) to discover deployed chaincodes part of the plan for V1 at all
sstone1 (Thu, 09 Feb 2017 21:06:02 GMT):
Related to chaincode upgrade, is chaincode list (from the SDKs) to discover deployed chaincodes part of the plan for V1 at all?
rahulhegde (Thu, 09 Feb 2017 21:06:06 GMT):
Thanks @bmos299, I will post to the channel.
bmos299 (Thu, 09 Feb 2017 21:06:44 GMT):
i can cut and paste the three questions if you want. We want to work close with you o your use cases.
bmos299 (Thu, 09 Feb 2017 21:14:35 GMT):
@rahulhegde thanks.
theathibm (Thu, 09 Feb 2017 21:38:42 GMT):
Has joined the channel.
gregnotso (Thu, 09 Feb 2017 21:46:48 GMT):
Has joined the channel.
maanas (Fri, 10 Feb 2017 03:44:39 GMT):
Has joined the channel.
siddhid (Fri, 10 Feb 2017 03:56:20 GMT):
Hi All,
we can specify a relaxed endorsement policy for a chaincode. so from the below mentioned link I got how to specify endorsement policy for a chaincode from command prompt at the time of deploy. I want to know how to specify the endorsement policy from node js application.
Link
https://github.com/hyperledger/fabric/blob/master/docs/endorsement-policies.md
Thanks
subbu165 (Fri, 10 Feb 2017 04:17:23 GMT):
Hello,using hyperledger v0.6 i have written and running a chaincode in golang, in the go code I want to refer some properties/configuration files from anywhere. any idea how can I achieve this, as of now I try to use os.readfile and even with absolute path it gives the below error:
ERROR : %!(EXTRA *os.PathError=open /Users/spalani1/work/src/github.com/anonyms.txt: no such file or directory)
Any suggestions please
greg.haskins (Fri, 10 Feb 2017 04:18:35 GMT):
@subbu165 i assume you are using standard netmode deployment?
siddhid (Fri, 10 Feb 2017 04:20:31 GMT):
Hi Guys
In fabric 1.0 we can create multiple channels. But wanted to know if there is a way where we create a dedicated channel between 2 peers, such that the third peer is prevented from joining the channel?
Thanks
subbu165 (Fri, 10 Feb 2017 04:21:06 GMT):
hmm..not sure about that, but I use docker-compose up command
greg.haskins (Fri, 10 Feb 2017 04:21:27 GMT):
what I mean is: how are you deploying the code?
greg.haskins (Fri, 10 Feb 2017 04:21:54 GMT):
are you using things like the SDK/CLI to deploy, or are you following the devmode guides and launching the chaincode by hand?
greg.haskins (Fri, 10 Feb 2017 04:22:11 GMT):
the former would be "standard netmode"
subbu165 (Fri, 10 Feb 2017 04:25:00 GMT):
ohh ok then we are using node SDK to deploy the chaincode which I suppose then its standard netmode
greg.haskins (Fri, 10 Feb 2017 04:27:33 GMT):
ok, thats what I figured
greg.haskins (Fri, 10 Feb 2017 04:28:05 GMT):
so, what you are observing is: when you deploy, just the .go code is uploaded to the peer, injected into a container, and compiled into a binary
greg.haskins (Fri, 10 Feb 2017 04:28:27 GMT):
and then executed as a docker container colocated with the peer
greg.haskins (Fri, 10 Feb 2017 04:28:54 GMT):
there is no "/User/spalani1/..." path that is valid in that context
greg.haskins (Fri, 10 Feb 2017 04:29:20 GMT):
in fact, the .txt file is never even uploaded
subbu165 (Fri, 10 Feb 2017 04:30:04 GMT):
ok
greg.haskins (Fri, 10 Feb 2017 04:30:06 GMT):
so, the ENOENT is what I would expect to see in those cirucmstances
greg.haskins (Fri, 10 Feb 2017 04:31:24 GMT):
today, there isnt a notion of the java jar equivalent of a resources/ folder you can include with the chaincode
greg.haskins (Fri, 10 Feb 2017 04:31:54 GMT):
we could possibly add it (after considering security implications) but it wouldnt be available in the v0.6 release
greg.haskins (Fri, 10 Feb 2017 04:32:34 GMT):
one thing you could do is work within the constraints of "only .go code" and embed resource files in the source
greg.haskins (Fri, 10 Feb 2017 04:33:04 GMT):
e.g. anonyms.txt -> bzip2 -> []byte{}
greg.haskins (Fri, 10 Feb 2017 04:33:20 GMT):
that would work, though awkward
greg.haskins (Fri, 10 Feb 2017 04:33:50 GMT):
i actually pack files into .go code within chaintool, if you'd like to see an example
subbu165 (Fri, 10 Feb 2017 04:35:01 GMT):
yes please let me know if there is a example that would help
greg.haskins (Fri, 10 Feb 2017 04:35:08 GMT):
ok, hold on
greg.haskins (Fri, 10 Feb 2017 04:37:06 GMT):
this is a bit indirect, but this template generates embedded files in golang: https://github.com/hyperledger/fabric-chaintool/blob/62f24c2c905cd45a481929c5f5f9959c176c423b/resources/generators/golang.stg#L214
greg.haskins (Fri, 10 Feb 2017 04:37:13 GMT):
and example of its output would be
greg.haskins (Fri, 10 Feb 2017 04:39:11 GMT):
```var interfaces = map[string][]byte{
"appinit": []byte("\x1f\x8b\x08\x00\x00\x00\x00\x00\x02\xff\xe3\xca\x4d\x2d\x2e\x4e\x4c\x4f\x55\x08\x48\x2c\x2a\xa9\x54\xa8\xe6\x52\x80\x82\xe2\x92\xa2\xcc\xbc\x74\x85\xd4\xbc\x92\x4c\xa0\xb8\xad\x82\xa1\x35\x5c\x2a\x33\xaf\xc4\xd8\x48\x41\xa1\x2c\x31\xa7\x34\x55\x01\x28\x65\x64\xcd\x55\xcb\xc5\x05\x33\xc8\x33\x2f\xb3\x04\xc9\x1c\x88\xb9\x05\x20\xd2\x11\xd5\x18\x24\x19\x27\x98\x29\x00\x21\x47\xc5\xe1\x8f\x00\x00\x00"),
"org.hyperledger.chaincode.example02": []byte("\x1f\x8b\x08\x00\x00\x00\x00\x00\x02\xff\x6d\x8f\xc1\x0e\x82\x30\x10\x44\xef\xfd\x8a\x3d\xc2\x51\x38\x12\x0e\x2a\x1e\x4d\x88\x7e\xc1\x5a\x57\x6c\xa0\xc5\xb4\x8b\x09\x31\xfe\xbb\x68\x51\xdb\xe8\xde\xba\x33\xdb\x99\x27\x34\x39\x87\x0d\x41\x8d\xa3\x26\xc3\x35\x5a\xd4\x0e\x6e\x02\xe6\x71\x6c\x95\x69\xe0\x82\x96\xc7\xbd\x95\x50\xc2\xa2\xf8\x2b\x56\x8e\x27\x31\xfb\x8a\xca\x70\x9e\x01\xa0\xee\x07\xc3\xd3\xbb\x84\xbc\x10\x77\x21\xde\x89\x1b\xc3\x8a\xc7\xdf\x28\x75\xf4\x21\x81\x75\x85\x1d\x1a\x49\x3b\x72\x43\xc7\xc1\x85\x8f\x38\x78\xf5\x73\x75\x1a\x8c\x64\xd5\x9b\x10\xe3\xda\x4f\xdf\x6e\xb1\xa5\x99\x33\x89\x78\xd3\x18\xeb\x65\xae\xa8\x23\xa6\xa5\x94\xcf\xfa\x89\x2f\x9b\xc6\x84\x71\xad\xf5\x99\x64\x3b\xaf\x02\xbf\x87\x7e\x00\x7e\xd2\x4e\xd8\x68\x01\x00\x00"),
}```
greg.haskins (Fri, 10 Feb 2017 04:39:34 GMT):
I think in my case, those are gzip encoded text files
greg.haskins (Fri, 10 Feb 2017 04:40:17 GMT):
it would be trivial to use gzip.NewReader(entry) to spit those back out to a file at start up or something
subbu165 (Fri, 10 Feb 2017 04:40:41 GMT):
ohh ok. I will surely try out that Greg. for me its just plain text files
greg.haskins (Fri, 10 Feb 2017 04:41:18 GMT):
right, mine too actually, I just gzipped them prior to emitting the file
greg.haskins (Fri, 10 Feb 2017 04:41:23 GMT):
to save space
subbu165 (Fri, 10 Feb 2017 04:41:28 GMT):
ahh ok
greg.haskins (Fri, 10 Feb 2017 04:41:56 GMT):
you dont have to though
subbu165 (Fri, 10 Feb 2017 04:42:16 GMT):
ok
greg.haskins (Fri, 10 Feb 2017 04:42:18 GMT):
actually, what am I saying: you dont need to spit them out to a file
greg.haskins (Fri, 10 Feb 2017 04:42:28 GMT):
you could just open them as an input stream as if they were a file
subbu165 (Fri, 10 Feb 2017 04:42:35 GMT):
ya got it
greg.haskins (Fri, 10 Feb 2017 04:42:35 GMT):
using a byte reader
subbu165 (Fri, 10 Feb 2017 04:42:43 GMT):
ok
greg.haskins (Fri, 10 Feb 2017 04:42:55 GMT):
good luck
subbu165 (Fri, 10 Feb 2017 04:43:08 GMT):
Thank you for the help Greg.
greg.haskins (Fri, 10 Feb 2017 04:43:23 GMT):
any time
coolsvap (Fri, 10 Feb 2017 05:33:39 GMT):
howdy
coolsvap (Fri, 10 Feb 2017 05:37:59 GMT):
guys I am new to fabric and I am doing the containerized deployment using http://hyperledger-fabric.readthedocs.io/en/latest/gettingstarted/
coolsvap (Fri, 10 Feb 2017 05:38:26 GMT):
I got the yml for couchdb in the slack history
coolsvap (Fri, 10 Feb 2017 05:38:40 GMT):
but when I deploy it the channel creation fails
coolsvap (Fri, 10 Feb 2017 05:38:46 GMT):
anyone facing similar issue?
ylsGit (Fri, 10 Feb 2017 06:51:31 GMT):
Has joined the channel.
NIKESHGOGIA (Fri, 10 Feb 2017 07:13:48 GMT):
Has joined the channel.
Jonas.Hedin (Fri, 10 Feb 2017 08:34:20 GMT):
Hi. What files do you need to transfer to the CLI to run java chaincode? I wan't to try to get one of the examples working but I have no idea what the CLI needs.
gatakka (Fri, 10 Feb 2017 08:47:56 GMT):
Hello, what will be expected performance in final/production ready version? For now in v1 using nodejs sdk and images provided in getting-started it takes about 5-6 seconds for a single transaction. In documentations is mentioned something like 100 000 request per seconds on 15 nodes. This is impressive. Is there any "setting" or configuration that has to be changed in current version, or performance optimizations are not ready?
gatakka (Fri, 10 Feb 2017 08:47:56 GMT):
Hello, what will be expected performance in final/production ready version? For now in v1 using nodejs sdk and images provided in getting-started it takes about 5-6 seconds for a single transaction. In documentations is mentioned something like 100 000 request per second on 15 nodes. This is impressive. Is there any "setting" or configuration that has to be changed in current version, or performance optimizations are not ready?
levinkwong (Fri, 10 Feb 2017 08:48:43 GMT):
Has joined the channel.
tarima (Fri, 10 Feb 2017 08:51:06 GMT):
Hi I have a small question.
Now, Is git branch for master (Version 0.7) is the same as V1.0-alpha right?
Vadim (Fri, 10 Feb 2017 08:51:39 GMT):
@gatakka have you tried sending multiple transactions at once? Is the transaction processing time increasing?
Vadim (Fri, 10 Feb 2017 08:52:49 GMT):
what I'm saying here that latency might be 5-6 seconds, but you still can have a performance of several transactions per second
gatakka (Fri, 10 Feb 2017 08:55:37 GMT):
Yes, I understand that, but then I have another problem
gatakka (Fri, 10 Feb 2017 08:56:07 GMT):
while transanction is executed (this 5-6 seconds) if i make another request I dot success, but ledger is not updated
gatakka (Fri, 10 Feb 2017 08:56:14 GMT):
for second execution
Vadim (Fri, 10 Feb 2017 08:56:33 GMT):
are you sending it to the orderer?
gatakka (Fri, 10 Feb 2017 08:56:58 GMT):
I am using nodejs examples from getting started, invoke.js
Vadim (Fri, 10 Feb 2017 08:57:17 GMT):
can you send me a link to it?
gatakka (Fri, 10 Feb 2017 08:57:27 GMT):
that transfer tokens from party A to party B. As far As I can see invocation is endorsed and then send to orderer
gatakka (Fri, 10 Feb 2017 08:57:46 GMT):
https://github.com/hyperledger/fabric/blob/master/docs/gettingstarted.md
gatakka (Fri, 10 Feb 2017 08:58:19 GMT):
nothing from this example is modified, only deployment of chaincode is manual because this verson cannot deploy.
gatakka (Fri, 10 Feb 2017 08:58:19 GMT):
nothing from this example is modified, only deployment of chaincode is manual because this version of nodejs cannot deploy.
gatakka (Fri, 10 Feb 2017 08:58:31 GMT):
i can give you logs and all other information if you need it
Vadim (Fri, 10 Feb 2017 08:59:19 GMT):
and what is the second request that you do?
gatakka (Fri, 10 Feb 2017 09:00:28 GMT):
I execute nodejs invoke.js in 2 terminals on same machine. They are same request. Same enrolment ID and cert. I try with different amounts it is the same.
gatakka (Fri, 10 Feb 2017 09:00:28 GMT):
I execute nodejs invoke.js in 2 terminals on same machine. They are same request. Same enrolment ID and cert. I try with different amounts in the request (2 request different amount), result it is the same.
Vadim (Fri, 10 Feb 2017 09:01:18 GMT):
I can only guess that both transactions you are trying are concurrently modifying the same state, so the second one is discarded because of that
gatakka (Fri, 10 Feb 2017 09:01:50 GMT):
probably, but i got Success from orderer
gatakka (Fri, 10 Feb 2017 09:02:01 GMT):
on both of them
gatakka (Fri, 10 Feb 2017 09:02:20 GMT):
but the ledger is updated only wit values from first request. Like second never happend
gatakka (Fri, 10 Feb 2017 09:02:20 GMT):
but the ledger is updated only with values from first request. Like second never happend
Vadim (Fri, 10 Feb 2017 09:02:59 GMT):
so you move lets say 10 tokens from A and the balance should be 90 tokens, then you move 10 tokens again and the balance should be 80 tokens, you get success for both transactions, but when you query, the result is 90 tokens and not 80?
gatakka (Fri, 10 Feb 2017 09:03:56 GMT):
yes, it is 90, not 80. It is like second invocation is not executed at all, but i got success for both of them
Vadim (Fri, 10 Feb 2017 09:04:13 GMT):
interesting
Vadim (Fri, 10 Feb 2017 09:04:19 GMT):
let me try myself :)
gatakka (Fri, 10 Feb 2017 09:04:55 GMT):
ok, If I can help you somehow I will be here :)
coolsvap (Fri, 10 Feb 2017 09:12:11 GMT):
guys is the fabric deployment working with containers?
subbu165 (Fri, 10 Feb 2017 09:23:21 GMT):
@greg.haskins, One more doubt I have is:
Earlier I used to deploy using REST API. That time, I used to extend volume in my docker-compose.yaml file e.g. /Users/spalani1/work/src/github.com/myWork:/opt/gopath/src/work_folder and then used to give the .txt files paths like `src/work_folder/anonyms.txt` and it used to read files properly because the whole content of `myWork` folder was mapped to container.
Why does this not work in case of NodeSDK?
subbu165 (Fri, 10 Feb 2017 09:23:21 GMT):
@greg.haskins, One more doubt I have is:
Earlier I used to deploy using REST API. That time, I used to extend volume in my docker-compose.yaml file e.g. `/Users/spalani1/work/src/github.com/myWork:/opt/gopath/src/work_folder` and then used to give the .txt files paths like `src/work_folder/anonyms.txt` and it used to read files properly because the whole content of `myWork` folder was mapped to container.
Why does this not work in case of NodeSDK?
mastersingh24 (Fri, 10 Feb 2017 10:59:47 GMT):
@subbu165 - see https://github.com/hyperledger/fabric/blob/v0.6/sdk/node/src/sdk_util.ts#L147 - you'll notice the extensions of files which are included. `*.txt* is not one of them but you can use `*.yaml` or `*.json`
mastersingh24 (Fri, 10 Feb 2017 10:59:47 GMT):
@subbu165 - see https://github.com/hyperledger/fabric/blob/v0.6/sdk/node/src/sdk_util.ts#L147 - you'll notice the extensions of files which are included. `*.txt*` is not one of them but you can use `*.yaml` or `*.json`
subbu165 (Fri, 10 Feb 2017 11:04:00 GMT):
so volume extension in docker compose yml should work even if we deploy the chain code through nodesdk?
subbu165 (Fri, 10 Feb 2017 11:05:08 GMT):
its only because of the file extension unsupported? If I change it to lets say .json it will start working? as of now I get the error like below:
ERROR : %!(EXTRA *os.PathError=open /Users/spalani1/work/src/github.com/anonyms.txt: no such file or directory)
mastersingh24 (Fri, 10 Feb 2017 11:05:40 GMT):
maybe I am missing what you are trying to do?
mastersingh24 (Fri, 10 Feb 2017 11:07:29 GMT):
I assume you want your chaincode to read in some config files?
subbu165 (Fri, 10 Feb 2017 11:08:45 GMT):
Yes and the chain code are deployed using nodesdk. The config file can be anywhere in the system which the customer will provide. The chain code I have written in golang should be able to access it
mastersingh24 (Fri, 10 Feb 2017 11:27:49 GMT):
`The config file can be anywhere in the system which the customer will provide` - I don't understand how you expect this to work? Were you modifying the Dockerfile used for chaincode containers?
mastersingh24 (Fri, 10 Feb 2017 11:28:19 GMT):
or you mean the customer can choose a config file when they deploy?
subbu165 (Fri, 10 Feb 2017 11:41:09 GMT):
yes customer can choose a config file when they deploy, probably not anywhere, but at least in a specific path, but we are not sure as of now where it should be.
mastersingh24 (Fri, 10 Feb 2017 11:42:18 GMT):
well even in the case of using REST, it still needs to be in your chaincode folder.
mastersingh24 (Fri, 10 Feb 2017 11:42:48 GMT):
but as I mentioned, the Node SDK does not include `*.txt` files
mastersingh24 (Fri, 10 Feb 2017 11:43:22 GMT):
so they will not be packaged up. so you'll need to use either `*.json` or `*.yaml`
mastersingh24 (Fri, 10 Feb 2017 11:44:05 GMT):
and the files should be in your chaincode source folder (BTW - I don't really recommend using config files, but that's beside the point here)
daijianw (Fri, 10 Feb 2017 11:45:36 GMT):
Has joined the channel.
AbhishekSeth (Fri, 10 Feb 2017 11:56:33 GMT):
Has joined the channel.
seanbarclay (Fri, 10 Feb 2017 11:57:05 GMT):
Has joined the channel.
subbu165 (Fri, 10 Feb 2017 12:00:11 GMT):
ok Gari, we are trying this now, we had modified it to .yaml
mastersingh24 (Fri, 10 Feb 2017 12:07:24 GMT):
if I understand everything you were doing before, I think this should resolve the issues you were seeing
mastersingh24 (Fri, 10 Feb 2017 12:08:00 GMT):
(well at least the files will be present in the chaincode container(s) as previously they were definitely not included in deploying via the NodeSDK)
sb2407 (Fri, 10 Feb 2017 12:10:55 GMT):
Has joined the channel.
Basug (Fri, 10 Feb 2017 12:45:23 GMT):
Is there a way to query transaction history ?
ssaddem (Fri, 10 Feb 2017 13:19:58 GMT):
hi there is any way to debug my chaincode with visual studio code ?
anuragvijayvergia (Fri, 10 Feb 2017 13:32:28 GMT):
hey I am getting following error while executing demo sdk chaincode ,
`{"created":"@1486733195.147972000","description":"Handshake read failed","file":"../src/core/lib/security/transport/handshake.c","file_line":237,"referenced_errors":[{"created":"@1486733195.147961000","description":"FD shutdown","file":"../src/core/lib/iomgr/ev_poll_posix.c","file_line":427}]}`
*note*, my vp0 is shut, i was able to execute everything when all 4 vp were running , I want to execute this by keeping vp0 shut, incase thats not possible , i would really appreciate the explanation . Thanks in advance :)
nickgaski (Fri, 10 Feb 2017 14:10:12 GMT):
@coolsvap - can you share the yaml you are using and the logs on channel creation failure.
greg.haskins (Fri, 10 Feb 2017 14:13:03 GMT):
[ ](https://chat.hyperledger.org/channel/fabric?msg=AN4hhcnZGwm958G87) @tarima yes, the master branch represents the development stream for what will become v1.0 when its released. Ignore the current version number of v0.7.0-snapshot...that is just because its bumped v0.6+1 after v0.6 was finished
tarima (Fri, 10 Feb 2017 14:15:41 GMT):
[ ](https://chat.hyperledger.org/channel/fabric?msg=qF27T4AoEbBt8JC66) @greg.haskins Thank you my question. I get it. :blush:
tarima (Fri, 10 Feb 2017 14:16:05 GMT):
@greg.haskins +1
greg.haskins (Fri, 10 Feb 2017 14:26:10 GMT):
[ ](https://chat.hyperledger.org/channel/fabric?msg=DCkgB8RuFzbuM3c62) @subbu165 I suspect what you were seeing was you were working with a local peer and its CLI?
coolsvap (Fri, 10 Feb 2017 14:26:34 GMT):
@nickgaski hi
coolsvap (Fri, 10 Feb 2017 14:26:49 GMT):
@nickgaski I am using https://jira.hyperledger.org/secure/attachment/10418/10418_docker-couchdb.yml
greg.haskins (Fri, 10 Feb 2017 14:26:49 GMT):
if so, note that was not going to really work...it might have looked like it was working with your one node but if you had tried to run a network of nodes, the other nodes would not have seen your .txt file
coolsvap (Fri, 10 Feb 2017 14:26:56 GMT):
with current master
coolsvap (Fri, 10 Feb 2017 14:27:50 GMT):
@nickgaski I have that setup on my office setup I am recreating it, will be up in 10-15 mins I can share teh logs once its started
greg.haskins (Fri, 10 Feb 2017 14:27:50 GMT):
I also dont think you should rely on the .json/.yaml filter, that was a function of a situation that is no longer present
greg.haskins (Fri, 10 Feb 2017 14:28:13 GMT):
future versions are likely to scrub those as well (in fact I have a patch as part of FAB-2122 that does this)
nickgaski (Fri, 10 Feb 2017 14:28:30 GMT):
let me look. we have a configuration with frozen images that will work. Note: couchDB will not be supported for first v1 release. That will still be levelDB running as a peer process. But we can hack it together so that you can see the couch containers in action
greg.haskins (Fri, 10 Feb 2017 14:28:33 GMT):
but what we could think about is creating the notion of a formal "resources/' ala .jar spec
coolsvap (Fri, 10 Feb 2017 14:29:56 GMT):
alright let me get the containers built and start the services with the compose
markparz (Fri, 10 Feb 2017 14:37:30 GMT):
Thanks @muralisr for the new video on install & instantiate chaincode. For all, this is replacing 'deploy' of CC. Check out Murali's demo/video here https://www.youtube.com/watch?v=NKb4XqJUXD0&feature=youtu.be
ruslan.kryukov (Fri, 10 Feb 2017 14:41:51 GMT):
[ ](https://chat.hyperledger.org/channel/fabric?msg=Nzsrh8bvtTzzEkpJc) @markparz How can I watch all his video about hyperledger? Because for example this video seems cool and I wanna more :)
markparz (Fri, 10 Feb 2017 14:43:12 GMT):
Hi @ruslan.kryukov you can see all the videos off the Hypledger Fabric youtube channel at https://www.youtube.com/channel/UCCFdgCWH_1vCndMPVqQlwZw
markparz (Fri, 10 Feb 2017 14:43:31 GMT):
I suggest subscribing and then you can be auto-notified of all new videos that are posted
markparz (Fri, 10 Feb 2017 14:44:31 GMT):
check out all the videos posted, as well as the playlist. Those are videos that I have linked to the channel as they were posted directly by the contributor.
greg.haskins (Fri, 10 Feb 2017 14:46:19 GMT):
[ ](https://chat.hyperledger.org/channel/fabric?msg=kcNucAgdqngxBjbtk) @mastersingh24 Note that even these were a leftover from when the system was auto-packaging the entire GOPATH (including the shim, which required core.yaml IIRC)
nickmelis (Fri, 10 Feb 2017 14:46:46 GMT):
any idea why when querying the keyvaluestore by range, the number of results returned is always capped to 100 maximum?
nickmelis (Fri, 10 Feb 2017 14:46:58 GMT):
is there a way to bypass it or configure this limit?
greg.haskins (Fri, 10 Feb 2017 14:47:16 GMT):
they are likely no longer needed, and in any case the source for the chaincode is not likely to be retained in the container after compilation
greg.haskins (Fri, 10 Feb 2017 14:47:22 GMT):
(FAB-2122)
nickmelis (Fri, 10 Feb 2017 14:47:24 GMT):
and also do results get returned in any specific order?
mastersingh24 (Fri, 10 Feb 2017 14:47:57 GMT):
@greg.haskins - good point and what I am saying above is actually only really applicable to v0.6 moving forward given the recent packaging change
greg.haskins (Fri, 10 Feb 2017 14:48:07 GMT):
yes, you do have a point there
nickmelis (Fri, 10 Feb 2017 14:48:11 GMT):
I'm using v0.6 atm
greg.haskins (Fri, 10 Feb 2017 14:48:14 GMT):
v0.6 that trick will likely still work
greg.haskins (Fri, 10 Feb 2017 14:49:06 GMT):
ive been thinking of adding some kind of resources/ feature to car, similar to .jar...im sure we could come up with a solution for non car as well...the bigger concern is security / "should we"?
greg.haskins (Fri, 10 Feb 2017 14:50:07 GMT):
at some level, giving a user the opportunity to put whatever they want (./fabrichacker.a) seems risky
greg.haskins (Fri, 10 Feb 2017 14:50:32 GMT):
on the other hand, the user could attack the system any number of ways so the container really just needs to be robust
greg.haskins (Fri, 10 Feb 2017 14:52:02 GMT):
but anyway, the point still stands: a) you can't really refer to client relative paths in your chaincode...it will run in a different content (though earlier releases running in a certain way may have inadvertently still had access
greg.haskins (Fri, 10 Feb 2017 14:52:21 GMT):
and b) any notion of "resources/" needs to be designed and formally supported
coolsvap (Fri, 10 Feb 2017 14:53:23 GMT):
@nickgaski this is result.txt >> https://paste.fedoraproject.org/552499/73835614/
coolsvap (Fri, 10 Feb 2017 14:53:48 GMT):
sorry log.txt
coolsvap (Fri, 10 Feb 2017 14:53:58 GMT):
result.txt shows there is error in joining channel
ruslan.kryukov (Fri, 10 Feb 2017 14:54:22 GMT):
[ ](https://chat.hyperledger.org/channel/fabric?msg=Zzc8d7pYbcohtCSRx) already, thanks :)
nickgaski (Fri, 10 Feb 2017 14:56:05 GMT):
ah @coolsvap - I see. you're producing a genesis block where anchor peers are not specified. I suspect you are using current images from master code?
nickgaski (Fri, 10 Feb 2017 14:56:22 GMT):
As a result your joinChannel is failing
coolsvap (Fri, 10 Feb 2017 14:57:06 GMT):
@nickgaski I think yes
coolsvap (Fri, 10 Feb 2017 14:57:17 GMT):
I am using master
nickgaski (Fri, 10 Feb 2017 14:57:44 GMT):
yea there are some configuration things that you'd need to do when issuing the createChannel
nickgaski (Fri, 10 Feb 2017 14:58:07 GMT):
do you want a docker-compose with older images ?
coolsvap (Fri, 10 Feb 2017 14:58:27 GMT):
@nickgaski sure I want to see the fabric in action
nickgaski (Fri, 10 Feb 2017 14:58:45 GMT):
the flow will be the same, but the granularity with anchor peers, gossip, all that good stuff isn't quite baked yet
nickgaski (Fri, 10 Feb 2017 14:59:02 GMT):
try this guy
nickgaski (Fri, 10 Feb 2017 15:03:35 GMT):
https://jira.hyperledger.org/secure/attachment/10418/10418_docker-couchdb.yml
Basug (Fri, 10 Feb 2017 15:09:03 GMT):
@nickgaski - thank you , I was about to make changes to the existing one based on https://github.com/hyperledger/fabric-sdk-node/blob/master/test/fixtures/docker-compose-marbles.yml
Basug (Fri, 10 Feb 2017 15:09:09 GMT):
to add couchdb
nickgaski (Fri, 10 Feb 2017 15:10:46 GMT):
you can deploy marbles too with the one I pasted. Just change the go code in your /src directory to - https://github.com/hyperledger/fabric/tree/master/examples/chaincode/go/marbles02
Basug (Fri, 10 Feb 2017 15:11:51 GMT):
yeah - have chaincode based on assetmanagement example, that i deployed..
Basug (Fri, 10 Feb 2017 15:12:13 GMT):
wanted to try queries - so wanted to try couchdb
coolsvap (Fri, 10 Feb 2017 15:12:37 GMT):
@nickgaski I was able to get the things working :)
coolsvap (Fri, 10 Feb 2017 15:12:55 GMT):
that should be perfect start of weekend for me
Basug (Fri, 10 Feb 2017 15:14:37 GMT):
@nickgaski - thank you my chaincode seems to work fine with couchdb.
Basug (Fri, 10 Feb 2017 15:14:57 GMT):
I see these eouchdb errors though
Basug (Fri, 10 Feb 2017 15:15:21 GMT):
couchdb2 | [notice] 2017-02-10T15:13:55.867605Z nonode@nohost <0.326.0> -------- chttpd_auth_cache changes listener died database_does_not_exist at mem3_shards:load_shards_from_db/6(line:327) <= mem3_shards:load_shards_from_disk/1(line:315) <= mem3_shards:load_shards_from_disk/2(line:331) <= mem3_shards:for_docid/3(line:87) <= fabric_doc_open:go/3(line:38) <= chttpd_auth_cache:ensure_auth_ddoc_exists/2(line:187) <= chttpd_auth_cache:listen_for_changes/1(line:134)
couchdb2 | [error] 2017-02-10T15:13:55.867654Z nonode@nohost emulator -------- Error in process <0.4061.0> with exit value: {database_does_not_exist,[{mem3_shards,load_shards_from_db,"_users",[{file,"src/mem3_shards.erl"},{line,327}]},{mem3_shards,load_shards_from_disk,1,[{file,"src/mem3_shards.erl"},{line,315}]},{mem3_shards,load_shards_from_disk...
couchdb0 | [error] 2017-02-10T15:13:57.634533Z nonode@nohost emulator -------- Error in process <0.4057.0> with exit value: {database_does_not_exist,[{mem3_shards,load_shards_from_db,"_users",[{file,"src/mem3_shards.erl"},{line,327}]},{mem3_shards,load_shards_from_disk,1,[{file,"src/mem3_shards.erl"},{line,315}]},{mem3_shards,load_shards_from_disk...
couchdb0 | [notice] 2017-02-10T15:13:57.634561Z nonode@nohost <0.326.0> -------- chttpd_auth_cache changes listener died database_does_not_exist at mem3_shards:load_shards_from_db/6(line:327) <= mem3_shards:load_shards_from_disk/1(line:315) <= mem3_shards:load_shards_from_disk/2(line:331) <= mem3_shards:for_docid/3(line:87) <= fabric_doc_open:go/3(line:38) <= chttpd_auth_cache:ensure_auth_ddoc_exists/2(line:187) <= chttpd_auth_cache:listen_for_changes/1(line:134)
couchdb1 | [error] 2017-02-10T15:13:57.700588Z nonode@nohost emulator -------- Error in process <0.4055.0> with exit value: {database_does_not_exist,[{mem3_shards,load_shards_from_db,"_users",[{file,"src/mem3_shards.erl"},{line,327}]},{mem3_shards,load_shards_from_disk,1,[{file,"src/mem3_shards.erl"},{line,315}]},{mem3_shards,load_shards_from_disk...
couchdb1 | [notice] 2017-02-10T15:13:57.700711Z nonode@nohost <0.326.0> -------- chttpd_auth_cache changes listener died database_does_not_exist at mem3_shards:load_shards_from_db/6(line:327) <= mem3_shards:load_shards_from_disk/1(line:315) <= mem3_shards:load_shards_from_disk/2(line:331) <= mem3_shards:for_docid/3(line:87) <= fabric_doc_open:go/3(line:38) <= chttpd_auth_cache:ensure_auth_ddoc_exists/2(line:187) <= chttpd_auth_cache:listen_for_changes/1(line:134)
couchdb2 | [notice] 2017-02-10T15:14:00.868614Z nonode@nohost <0.326.0> -------- chttpd_auth_cache changes listener died database_does_not_exist at mem3_shards:load_shards_from_db/6(line:327) <= mem3_shards:load_shards_from_disk/1(line:315) <= mem3_shards:load_shards_from_disk/2(line:331) <= mem3_shards:for_docid/3(line:87) <= fabric_doc_open:go/3(line:38) <= chttpd_auth_cache:ensure_auth_ddoc_exists/2(line:187) <= chttpd_auth_cache:listen_for_changes/1(line:134)
couchdb2 | [error] 2017-02-10T15:14:00.868865Z nonode@nohost emulator -------- Error in process <0.4126.0> with exit value: {database_does_not_exist,[{mem3_shards,load_shards_from_db,"_users",[{file,"src/mem3_shards.erl"},{line,327}]},{mem3_shards,load_shards_from_disk,1,[{file,"src/mem3_shards.erl"},{line,315}]},{mem3_shards,load_shards_from_disk...
couchdb0 | [error] 2017-02-10T15:14:02.635525Z nonode@nohost emulator -------- Error in process <0.4138.0> with exit value: {database_does_not_exist,[{mem3_shards,load_shards_from_db,"_users",[{file,"src/mem3_shards.erl"},{line,327}]},{mem3_shards,load_shards_from_disk,1,[{file,"src/mem3_shards.erl"},{line,315}]},{mem3_shards,load_shards_from_disk...
couchdb0 | [notice] 2017-02-10T15:14:02.635553Z nonode@nohost <0.326.0> -------- chttpd_auth_cache changes listener died database_does_not_exist at mem3_shards:load_shards_from_db/6(line:327) <= mem3_shards:load_shards_from_disk/1(line:315) <= mem3_shards:load_shards_from_disk/2(line:331) <= mem3_shards:for_docid/3(line:87) <= fabric_doc_open:go/3(line:38) <= chttpd_auth_cache:ensure_auth_ddoc_exists/2(line:187) <= chttpd_auth_cache:listen_for_changes/1(line:134)
couchdb1 | [error] 2017-02-10T15:14:02.701511Z nonode@nohost emulator -------- Error in process <0.4136.0> with exit value: {database_does_not_exist,[{mem3_shards,
Basug (Fri, 10 Feb 2017 15:17:07 GMT):
Message Attachments
arvindupadhyaya (Fri, 10 Feb 2017 15:58:16 GMT):
Hi.. I need help regarding a use case.. say a = 200, b = 100 the code for invoke is `"functionName":"invoke",
"args":[
"move",
"a",
"b",
"100"
]`
The above code makes a = 100 and b = 200. I want to use invoke to update a's value to say 300. How can this be done? I understand I can use init, but I have a use case in which I need to constantly update a single value
Basug (Fri, 10 Feb 2017 16:06:03 GMT):
@arvindupadhyaya - you probably have to modify the chaincode - write another function that will set value of individual key
Basug (Fri, 10 Feb 2017 16:09:30 GMT):
right now in the example move expects 4 arguments.. you could just copy the same function, call it something else and make it work with 2 arguments. Also don't forget to call the new function based on arg[0] in Invoke
arvindupadhyaya (Fri, 10 Feb 2017 16:13:04 GMT):
so I change the go file (say example_cc.go).. what should I do next? Previously I used to compile it and deploy it using the command `CORE_CHAINCODE_ID_NAME=mycc CORE_PEER_ADDRESS=0.0.0.0:7051 ./mycc` is this still valid or has the process changed?
Basug (Fri, 10 Feb 2017 16:13:46 GMT):
are you using 1.0 ?
arvindupadhyaya (Fri, 10 Feb 2017 16:13:51 GMT):
yes
Basug (Fri, 10 Feb 2017 16:14:01 GMT):
the file on your local drive is already mapped to docker image
Basug (Fri, 10 Feb 2017 16:14:10 GMT):
you can modify it and use nodejs deploy to deploy it
Basug (Fri, 10 Feb 2017 16:14:21 GMT):
or you could do the way you were deploying
arvindupadhyaya (Fri, 10 Feb 2017 16:15:27 GMT):
i'm not sure about the way I am deploying.. what is the recommended way?
Basug (Fri, 10 Feb 2017 16:15:30 GMT):
I have modified the file locally multiple times and deployed and the changes take effect when you deploy
arvindupadhyaya (Fri, 10 Feb 2017 16:16:15 GMT):
ok.. I'll try and modify the local file and let you know
Basug (Fri, 10 Feb 2017 16:16:15 GMT):
I prefer the node way, I could have it as a service and call deploy service in the future (like the way it used to be 0.6)
Basug (Fri, 10 Feb 2017 16:16:18 GMT):
- ./src/github.com/example_cc/example_cc.go:/opt/gopath/src/github.com/hyperledger/fabric/examples/example_cc.go
Basug (Fri, 10 Feb 2017 16:16:25 GMT):
this is the mapping you see in docker file
Basug (Fri, 10 Feb 2017 16:16:54 GMT):
similarly i added my own one, based on smart contract
Basug (Fri, 10 Feb 2017 16:16:56 GMT):
- ./src/smartcontracts/sc1/sc1.go:/opt/gopath/src/github.com/hyperledger/fabric/smartcontracts/sc1/sc1.go
Basug (Fri, 10 Feb 2017 16:17:09 GMT):
and modified node config file to deploy this one as well.. and it works without issues
arvindupadhyaya (Fri, 10 Feb 2017 16:17:14 GMT):
ya.. i noticed that.. but was not sure what was going on :P
arvindupadhyaya (Fri, 10 Feb 2017 16:17:40 GMT):
I will try it out and let you know @Basug
Basug (Fri, 10 Feb 2017 16:19:55 GMT):
All - Is there a way to query history for a given key ?
Basug (Fri, 10 Feb 2017 16:20:11 GMT):
asked this in the morning - may be it was too early :)
nickmelis (Fri, 10 Feb 2017 16:20:54 GMT):
@Basug I would be interest in this feature too
Basug (Fri, 10 Feb 2017 16:21:16 GMT):
@nickmelis I see there is GetQueryResult in chaincode stub
Basug (Fri, 10 Feb 2017 16:21:52 GMT):
but looks like it is to get multiple records that match the query, not sure if it returns history for a given key
Basug (Fri, 10 Feb 2017 16:24:08 GMT):
for 0.6 I was able to do it, not sure what the corresponding api is for 1.0
nickmelis (Fri, 10 Feb 2017 16:31:13 GMT):
@Basug > for 0.6 I was able to do it
nickmelis (Fri, 10 Feb 2017 16:31:16 GMT):
how?
Basug (Fri, 10 Feb 2017 16:31:59 GMT):
localhost:7050/chain
Basug (Fri, 10 Feb 2017 16:32:07 GMT):
it would give all the changes
Basug (Fri, 10 Feb 2017 16:32:29 GMT):
then individual block by localhost:7050/chain/blocks/0
nickmelis (Fri, 10 Feb 2017 16:33:12 GMT):
ah well it wouldn't work with encrypted content though
Basug (Fri, 10 Feb 2017 16:33:37 GMT):
agreed..
nickmelis (Fri, 10 Feb 2017 16:33:37 GMT):
you browse every single transaction in every single block then right?
Basug (Fri, 10 Feb 2017 16:33:44 GMT):
yes.
Basug (Fri, 10 Feb 2017 16:34:08 GMT):
I am trying to get this working for a POC, it doesn't need security and stuff for the moment..
arvindupadhyaya (Fri, 10 Feb 2017 16:34:35 GMT):
I'm getting this error
Basug (Fri, 10 Feb 2017 16:34:46 GMT):
running 1.0 with couchdb, i can see the records, trying to see if couchdb does store all the history
arvindupadhyaya (Fri, 10 Feb 2017 16:35:02 GMT):
I'm getting this error `[Peer.js]: GRPC client got an error response from the peer. Error: Failed to deploy chaincode spec
(Error creating image: %!s(
arvindupadhyaya (Fri, 10 Feb 2017 16:35:33 GMT):
this is when I am trying to deploy
Basug (Fri, 10 Feb 2017 16:36:03 GMT):
if you do in cli like the way you used to do before does it work?
Basug (Fri, 10 Feb 2017 16:38:17 GMT):
the only time I got that was when i messed around with docker file and try to reduce the number of peers to 2 instead of 3. There was an additional peer in config.json. After removing that, it was alright
Basug (Fri, 10 Feb 2017 16:38:29 GMT):
tried*
arvindupadhyaya (Fri, 10 Feb 2017 16:39:14 GMT):
I just added the code which we were discussing.. i will try to deploy without it..
Basug (Fri, 10 Feb 2017 16:42:52 GMT):
also if you are running in detached mode (docker-compose -f ... up -d), it might be worth to see the logs
Basug (Fri, 10 Feb 2017 16:43:01 GMT):
I while developing run it without -d
arvindupadhyaya (Fri, 10 Feb 2017 16:46:54 GMT):
it is definitely due to the code I've written.. because it works fine without it.. i'm not sure what the problem is.. the function i wrote is quite simple
Basug (Fri, 10 Feb 2017 17:29:52 GMT):
```Basanths-MacBook-Pro:hackfest basu$ curl -X PUT http://127.0.0.1:5984/_users
{"ok":true}
Basanths-MacBook-Pro:hackfest basu$ curl -X PUT http://127.0.0.1:5984/_replicator
{"ok":true}
Basanths-MacBook-Pro:hackfest basu$ curl -X PUT http://127.0.0.1:5984/_global_changes
{"ok":true}```
Basug (Fri, 10 Feb 2017 17:30:18 GMT):
if any one is using couch DB, these 3 commands will get rid of the errors that you might see
idiaz5 (Fri, 10 Feb 2017 17:31:57 GMT):
Has joined the channel.
rameshthoomu (Fri, 10 Feb 2017 17:59:22 GMT):
@arvindupadhyaya : deploy is not working with the recent changes in sdk node.. Please try this command `curl -OOOOOO https://raw.githubusercontent.com/hyperledger/fabric-sdk-node/v1.0-alpha/examples/balance-transfer/{config.json,deploy.js,helper.js,invoke.js,query.js,package.json}` and follow the deploy steps mentioned in getting started
jeaha (Fri, 10 Feb 2017 18:39:23 GMT):
Has joined the channel.
jvergeldedios (Fri, 10 Feb 2017 18:39:37 GMT):
Has joined the channel.
jyg (Fri, 10 Feb 2017 18:53:11 GMT):
Has joined the channel.
marcusvcs (Fri, 10 Feb 2017 19:31:23 GMT):
I am running the 1.0 example (http://hyperledger-fabric.readthedocs.io/en/latest/gettingstarted/). Anyone knows how can I change one of the nodes to not be a endorser? Is that CORE_PEER_ENDORSER_ENABLED property on docker-compose?
marcusvcs (Fri, 10 Feb 2017 19:37:01 GMT):
I am asking because I changed of all peers to false, recreate the containers, and the example is working the same way
rjones (Fri, 10 Feb 2017 19:42:04 GMT):
I tagged all of the github/fabric* repos using the new `topics` feature from github. LMK if you want more/different tags. for instance if you look here: https://github.com/hyperledger/fabric you'll see the topics under the description.
rrrodrig (Fri, 10 Feb 2017 20:52:08 GMT):
Has joined the channel.
rrrodrig (Fri, 10 Feb 2017 20:52:50 GMT):
For version 0.6 of the fabric, is there a way to dynamically create a new user that has an auditor role??
Harvey-Specter (Fri, 10 Feb 2017 23:05:02 GMT):
Has joined the channel.
trentonknight (Sat, 11 Feb 2017 00:50:41 GMT):
Has joined the channel.
sha256cn (Sat, 11 Feb 2017 07:38:40 GMT):
Has joined the channel.
cbf (Sat, 11 Feb 2017 09:47:11 GMT):
@rjones thanks, you beat me to it
rjones (Sat, 11 Feb 2017 09:47:58 GMT):
you're very welcome.
LordGoodman (Sat, 11 Feb 2017 11:00:08 GMT):
Has joined the channel.
LordGoodman (Sat, 11 Feb 2017 12:16:25 GMT):
hello everyone, how could I find more detials of hyperledger v1.0
gregnotso (Sat, 11 Feb 2017 12:31:34 GMT):
@LordGoodman i would think this would be as good a starting point as any other: https://jira.hyperledger.org/projects/FAB/issues/FAB-2184?filter=allopenissues
LordGoodman (Sat, 11 Feb 2017 12:37:53 GMT):
@gregnotso Thanks, mate
daijianw (Sat, 11 Feb 2017 13:46:18 GMT):
I'm setting up development environment on my Mac, but the "make all" failed while building ccenv-image. Anyone can provide any hint? I tried to use Vagrant environment, still got the same error.
daijianw (Sat, 11 Feb 2017 13:46:49 GMT):
Building docker ccenv-image
docker build --build-arg https_proxy=https://9.37.132.138:3128 -t hyperledger/fabric-ccenv build/image/ccenv
Sending build context to Docker daemon 29.37 MB
Step 1/3 : FROM hyperledger/fabric-baseimage:x86_64-0.3.0
---> f4751a503f02
Step 2/3 : COPY payload/chaintool payload/protoc-gen-go /usr/local/bin/
---> Using cache
---> 56caa6fcb6ab
Step 3/3 : ADD payload/goshim.tar.bz2 $GOPATH/src/
Error processing tar file(exit status 1): link /github.com/hyperledger/fabric/core/chaincode/shim/java/build/classes/main/org/hyperledger/java/shim/ChaincodeBase.class /github.com/hyperledger/fabric/core/chaincode/shim/java/build/classes/main/org/hyperledger/java/shim/ChaincodeBase.class: no such file or directory
make: *** [build/image/ccenv/.dummy-x86_64-0.7.0-snapshot-9011c66] Error 1
yacovm (Sat, 11 Feb 2017 13:47:48 GMT):
@adc You had something similar didn't you?
yacovm (Sat, 11 Feb 2017 13:47:48 GMT):
@adc You had something similar didn't you? See @daijianw 's case
adc (Sat, 11 Feb 2017 13:47:48 GMT):
Has joined the channel.
greg.haskins (Sat, 11 Feb 2017 14:20:22 GMT):
I think you don't have a GOPATH set
greg.haskins (Sat, 11 Feb 2017 14:20:22 GMT):
@daijianw: I think you don't have a GOPATH set
surabhi (Sat, 11 Feb 2017 17:58:35 GMT):
Has joined the channel.
arvindupadhyaya (Sat, 11 Feb 2017 19:11:00 GMT):
@rameshthoomu : thanks for the reply :) I solved the issue
mqshen (Sun, 12 Feb 2017 02:28:51 GMT):
Has joined the channel.
mqshen (Sun, 12 Feb 2017 02:31:37 GMT):
I want use GetCallerCertificate to get caller's certificate when deploy chaincode, but it return nil. my command: build/bin/peer chaincode deploy -p path -n name -c args . what is the correct way to get caller's certificate. thx!
LordGoodman (Sun, 12 Feb 2017 03:43:41 GMT):
@mqshen use argument 'u'
mqshen (Sun, 12 Feb 2017 03:51:17 GMT):
ok, thx.
hanhzf (Sun, 12 Feb 2017 05:28:44 GMT):
Hi，according to the design of ”Gossip based data Dissemination”, “Each organization will select a peer which will connect to the ordering service on its behalf and will disseminate the batches among the rest of the peers belonging to the same organization”.
Then I started a solo environment with 3 peers with only *vp0* connecting to the orderer service, *vp1* and *vp2* set *vp0* as the *CORE_PEER_DISCOVERY_ROOTNODE*, configuration as in solo.yml below.
Then I deployed with “peer chaincode deploy -p github.com/hyperledger/fabric/examples/chaincode/go/chaincode_example02 -c '{"Function":"init", "Args": ["a","100", "b", "200"]}' -n mycc”, but then found that only *vp0* has the ledger synced, *vp1* and *vp2* are not, so this is not the same as the design of ”Gossip based data Dissemination” has said.
Is this a defect or this part is not done yet in alpha? Thanks all
hanhzf (Sun, 12 Feb 2017 05:31:38 GMT):
Message Attachments
hanhzf (Sun, 12 Feb 2017 05:33:29 GMT):
> Simply check the ledger space:
```
$ du -sh /data/hyperledger/*
45M vp0
112K vp1
112K vp2
```
LordGoodman (Sun, 12 Feb 2017 06:30:08 GMT):
@hanhzf I think you missing the "expose" command
LordGoodman (Sun, 12 Feb 2017 06:31:34 GMT):
@hanhzf I think your "expose" command is missing
hanhzf (Sun, 12 Feb 2017 09:01:54 GMT):
@LordGoodman what do you mean by expose ?
daijianw (Sun, 12 Feb 2017 10:42:03 GMT):
@greg.haskins Greg, I have set GOPATH. For the vagrant environment, the fabric build succeeded last time in this Jan, but it failed after I pull new changes from repository last Thursday.
C0rWin (Sun, 12 Feb 2017 12:35:49 GMT):
@hanhzf Can you please explain your full flow? In you compose file I cannot find `CORE_PEER_GOSSIP_ORGLEADER` environmental variable flags which instructs peer to get connected to the ordering service?
C0rWin (Sun, 12 Feb 2017 12:36:41 GMT):
How do you create a channel? Are you listing others `vp1` and `vp2` as anchor peers?
C0rWin (Sun, 12 Feb 2017 12:37:23 GMT):
in your `docker-compose` file not one instructs `vp0` to get connected to the ordering service, how did you checked the ledger is in sync?
greg.haskins (Sun, 12 Feb 2017 14:54:40 GMT):
@daijianw All I know is I have seen an error similar to that when I fail to set the GOPATH appropriately
greg.haskins (Sun, 12 Feb 2017 14:55:03 GMT):
I can help you debug when at my desk probably tomorrow
debkhoo (Sun, 12 Feb 2017 22:19:41 GMT):
Can someone please help me... what do i do with this? :/ hfc [MemberServicesImpl.enroll] [Contact ECA] {"ts":{"seconds":{"low":1486937820,"high":0,"unsigned":false},"nanos":0},"id":{"id":"WebAppAdmin"},"tok":{"tok":{"buffer":{"type":"Buffer","data":[68,74,89,50,55,112,69,110,108,49,54,100]},"offset":0,"markedOffset":-1,"limit":12,"littleEndian":false,"noAssert":false}},"sign":{"type":0,"key":{"buffer":{"type":"Buffer","data":[48,89,48,19,6,7,42,134,72,206,61,2,1,6,8,42,134,72,206,61,3,1,7,3,66,0,4,16,201,34,167,62,9,190,2,127,25,231,247,250,87,87,134,78,44,187,74,226,186,102,58,161,135,254,90,179,255,247,203,74,255,143,102,148,91,172,84,88,79,170,42,246,207,3,73,68,73,235,53,178,58,8,50,153,204,250,106,227,59,68,47]},"offset":0,"markedOffset":-1,"limit":91,"littleEndian":false,"noAssert":false}},"enc":{"type":0,"key":{"buffer":{"type":"Buffer","data":[48,89,48,19,6,7,42,134,72,206,61,2,1,6,8,42,134,72,206,61,3,1,7,3,66,0,4,53,80,189,25,243,49,31,147,58,41,194,209,252,171,233,187,80,130,53,109,135,187,150,55,132,43,130,77,122,87,236,118,74,18,133,251,198,12,54,243,39,67,97,240,83,111,0,207,241,197,7,164,119,240,118,85,222,38,56,107,94,13,255,54]},"offset":0,"markedOffset":-1,"limit":91,"littleEndian":false,"noAssert":false}},"sig":null} +1ms
hfc [MemberServicesImpl.enroll] failed to create cert pair: err={"code":14,"metadata":{"_internal_repr":{}}} +23ms
hfc [memberServices.enroll] err=Error: {"created":"@1486937820.235588000","description":"EOF","file":"../src/core/lib/iomgr/tcp_posix.c","file_line":235,"grpc_status":14}, enrollment=undefined +0ms
subaru365 (Mon, 13 Feb 2017 01:36:39 GMT):
Has joined the channel.
salmanbaset (Mon, 13 Feb 2017 02:01:55 GMT):
I am running v1.0 following the getting started instructions. It seems that deploying a new chain code creates a new docker container, e.g.,
salmanbaset (Mon, 13 Feb 2017 02:01:55 GMT):
I am running v1.0 preview following the getting started instructions. It seems that deploying a new chain code creates a new docker container, e.g.,
salmanbaset (Mon, 13 Feb 2017 02:02:11 GMT):
`docker ps | grep mycc | awk '{print $1, $2}'
bf5ab2d68f51 peer0-peer0-mycc1-0-8befbaf7e7ab7f7fcbbacb338bb6034287b9be540f5bad2e3c8a335311db17b48c5843ce0b2251317c6ba028d9cd8b719a820ab9f14b2754eef23af58dd8e2ce
6fc87f4c193d peer0-peer0-mycc-0-8befbaf7e7ab7f7fcbbacb338bb6034287b9be540f5bad2e3c8a335311db17b48c5843ce0b2251317c6ba028d9cd8b719a820ab9f14b2754eef23af58dd8e2ce
57192a098bab peer0-peer2-mycc-0-c659a47dce16ded8af86b9f91dfc411edac0416e43dff2ced2faac39f7633bbbde2fcc9a65a5d07adaeca3513c970f7b8b9f4125848bea488e5e1cfc85db5ac0
97205880a980 peer0-peer0-mycc-0-c659a47dce16ded8af86b9f91dfc411edac0416e43dff2ced2faac39f7633bbbde2fcc9a65a5d07adaeca3513c970f7b8b9f4125848bea488e5e1cfc85db5ac0
ea1974675d21 peer0-peer1-mycc-0-c659a47dce16ded8af86b9f91dfc411edac0416e43dff2ced2faac39f7633bbbde2fcc9a65a5d07adaeca3513c970f7b8b9f4125848bea488e5e1cfc85db5ac0`
salmanbaset (Mon, 13 Feb 2017 02:02:39 GMT):
`docker ps | grep mycc | awk '{print $1, $2}'
bf5ab2d68f51 peer0-peer0-mycc1-0-8befbaf7e7ab7f7fcbbacb338bb6034287b9be540f5bad2e3c8a335311db17b48c5843ce0b2251317c6ba028d9cd8b719a820ab9f14b2754eef23af58dd8e2ce
6fc87f4c193d peer0-peer0-mycc-0-8befbaf7e7ab7f7fcbbacb338bb6034287b9be540f5bad2e3c8a335311db17b48c5843ce0b2251317c6ba028d9cd8b719a820ab9f14b2754eef23af58dd8e2ce
57192a098bab peer0-peer2-mycc-0-c659a47dce16ded8af86b9f91dfc411edac0416e43dff2ced2faac39f7633bbbde2fcc9a65a5d07adaeca3513c970f7b8b9f4125848bea488e5e1cfc85db5ac0
97205880a980 peer0-peer0-mycc-0-c659a47dce16ded8af86b9f91dfc411edac0416e43dff2ced2faac39f7633bbbde2fcc9a65a5d07adaeca3513c970f7b8b9f4125848bea488e5e1cfc85db5ac0
ea1974675d21 peer0-peer1-mycc-0-c659a47dce16ded8af86b9f91dfc411edac0416e43dff2ced2faac39f7633bbbde2fcc9a65a5d07adaeca3513c970f7b8b9f4125848bea488e5e1cfc85db5ac0`
salmanbaset (Mon, 13 Feb 2017 02:03:28 GMT):
```docker ps | grep mycc | awk '{print $1, $2}'
bf5ab2d68f51 peer0-peer0-mycc1-0-8befbaf7e7ab7f7fcbbacb338bb6034287b9be540f5bad2e3c8a335311db17b48c5843ce0b2251317c6ba028d9cd8b719a820ab9f14b2754eef23af58dd8e2ce
6fc87f4c193d peer0-peer0-mycc-0-8befbaf7e7ab7f7fcbbacb338bb6034287b9be540f5bad2e3c8a335311db17b48c5843ce0b2251317c6ba028d9cd8b719a820ab9f14b2754eef23af58dd8e2ce
57192a098bab peer0-peer2-mycc-0-c659a47dce16ded8af86b9f91dfc411edac0416e43dff2ced2faac39f7633bbbde2fcc9a65a5d07adaeca3513c970f7b8b9f4125848bea488e5e1cfc85db5ac0
97205880a980 peer0-peer0-mycc-0-c659a47dce16ded8af86b9f91dfc411edac0416e43dff2ced2faac39f7633bbbde2fcc9a65a5d07adaeca3513c970f7b8b9f4125848bea488e5e1cfc85db5ac0
ea1974675d21 peer0-peer1-mycc-0-c659a47dce16ded8af86b9f91dfc411edac0416e43dff2ced2faac39f7633bbbde2fcc9a65a5d07adaeca3513c970f7b8b9f4125848bea488e5e1cfc85db5ac0```
salmanbaset (Mon, 13 Feb 2017 02:05:45 GMT):
where i deployed chain code mycc and mycc1.
salmanbaset (Mon, 13 Feb 2017 02:06:28 GMT):
what is the relationship between number of docker containers started AND peers, chain code deployed on peers, channels?
norinos (Mon, 13 Feb 2017 02:26:36 GMT):
Has joined the channel.
Ashish (Mon, 13 Feb 2017 02:59:18 GMT):
Has joined the channel.
eheads (Mon, 13 Feb 2017 05:50:24 GMT):
Has joined the channel.
gdinhof (Mon, 13 Feb 2017 06:25:54 GMT):
Has joined the channel.
NIKESHGOGIA (Mon, 13 Feb 2017 07:03:18 GMT):
what is the best hadrware requirement to execute 4 peer on VM's or bare metal ?
NIKESHGOGIA (Mon, 13 Feb 2017 07:03:24 GMT):
I mean how much ram and other stuffs
ynamiki (Mon, 13 Feb 2017 07:05:35 GMT):
Has joined the channel.
ilasica (Mon, 13 Feb 2017 07:23:12 GMT):
Has joined the channel.
zhengjun (Mon, 13 Feb 2017 07:43:37 GMT):
Has joined the channel.
hanhzf (Mon, 13 Feb 2017 08:15:29 GMT):
@C0rWin I connected *vp0* with orderer with environment *CORE_PEER_COMMITTER_LEDGER_ORDERER=orderer:7050*. Yes I didn't configure *CORE_PEER_GOSSIP_ORGLEADER* for the peer node. For simplicity, I did not create any customized channel, just used the default "testchain" channel. With *CORE_PEER_COMMITTER_LEDGER_ORDERER=orderer:7050* set in vp0's docker environment, ledger can be synced with vp0 once I have delivered chaincode on vp0.
hanhzf (Mon, 13 Feb 2017 08:19:47 GMT):
My understanding is that: in an organization, one of the peer will be selected as the leader which will communicate with the orderer service, other peer nodes in the organization will sync ledger by help of the leader peer node rather than connecting directly with the orderer service. Am I right? @C0rWin
C0rWin (Mon, 13 Feb 2017 08:37:21 GMT):
@hanhzf yes your understanding is correct, but currently leader is not selected automatically, therefore you need explicitly specify `CORE_PEER_GOSSIP_ORGLEADER=true` for peer you want to be be connected to the ordering service.
C0rWin (Mon, 13 Feb 2017 08:38:25 GMT):
and if you need other peers to get connected to first one rather than ordering service you need to specify a bootstrap set
C0rWin (Mon, 13 Feb 2017 08:38:56 GMT):
this way gossip will be able to establish a membership and leader will be able to distributed blocks pulled out from ordering service.
hanhzf (Mon, 13 Feb 2017 08:39:26 GMT):
@C0rWin thanks, will try this environment. Also, how to specify the bootstrap set?
coolsvap (Mon, 13 Feb 2017 08:39:50 GMT):
@C0rWin hi
C0rWin (Mon, 13 Feb 2017 08:40:00 GMT):
@coolsvap hi
coolsvap (Mon, 13 Feb 2017 08:40:43 GMT):
@C0rWin I am trying to deploy latest fabric code with couch db, but I am facing some issues related to connectivity to orderer
C0rWin (Mon, 13 Feb 2017 08:40:45 GMT):
@hanhzf `CORE_PEER_GOSSIP_BOOTSTRAP=host:port`
hanhzf (Mon, 13 Feb 2017 08:41:20 GMT):
@C0rWin cool, will try it now :grin:
coolsvap (Mon, 13 Feb 2017 08:42:22 GMT):
@C0rWin Error: Error getting broadcast client: Error connecting to orderer:7050 due to grpc: timed out when dialing
coolsvap (Mon, 13 Feb 2017 08:42:33 GMT):
any pointers on this issue?
C0rWin (Mon, 13 Feb 2017 08:43:16 GMT):
well, could you explain what exactly did you do? share your `docker-compose.yml`?
coolsvap (Mon, 13 Feb 2017 08:43:42 GMT):
@C0rWin I am using the compose file https://jira.hyperledger.org/secure/attachment/10418/10418_docker-couchdb.yml
coolsvap (Mon, 13 Feb 2017 08:44:09 GMT):
built the images and deployed
coolsvap (Mon, 13 Feb 2017 08:44:25 GMT):
I am following the http://hyperledger-fabric.readthedocs.io/en/latest/gettingstarted/ manual
coolsvap (Mon, 13 Feb 2017 08:44:47 GMT):
just using the above compose file to use couchdb
C0rWin (Mon, 13 Feb 2017 08:49:57 GMT):
can you please try to replace `channel_test.sh` with following content? ```#!/bin/sh
# find address of peer0 in your network
PEER0_IP_ADDRESS=`perl -e 'use Socket; $a = inet_ntoa(inet_aton("peer0")); print "$a\n";'`
# create an anchor file
cat<
C0rWin (Mon, 13 Feb 2017 08:49:57 GMT):
can you please try to replace `channel_test.sh` with following content?
C0rWin (Mon, 13 Feb 2017 08:50:19 GMT):
```#!/bin/sh
# find address of peer0 in your network
PEER0_IP_ADDRESS=`perl -e 'use Socket; $a = inet_ntoa(inet_aton("peer0")); print "$a\n";'`
# create an anchor file
cat<
C0rWin (Mon, 13 Feb 2017 08:50:32 GMT):
see: https://gerrit.hyperledger.org/r/#/c/5691/1/examples/sfhackfest/channel_test.sh
yacovm (Mon, 13 Feb 2017 09:01:44 GMT):
https://chat.hyperledger.org/channel/fabric-gossip?msg=p8QcxgwMJB8u5n3j5
coolsvap (Mon, 13 Feb 2017 09:03:58 GMT):
@C0rWin does not work for me, i think there is dependency on perl in the finding the PEER0_IP_ADDRESS
yacovm (Mon, 13 Feb 2017 09:04:33 GMT):
what? the docker container doesn't have perl?!
coolsvap (Mon, 13 Feb 2017 09:05:50 GMT):
@yacovm no
coolsvap (Mon, 13 Feb 2017 09:05:57 GMT):
following is the error ./channel_test.sh: line 4: iperl: command not found
C0rWin (Mon, 13 Feb 2017 09:05:57 GMT):
just checked, there is perl avail on image
C0rWin (Mon, 13 Feb 2017 09:06:22 GMT):
what is `iperl`?
yacovm (Mon, 13 Feb 2017 09:06:23 GMT):
yep I also checked
coolsvap (Mon, 13 Feb 2017 09:06:57 GMT):
wait
coolsvap (Mon, 13 Feb 2017 09:09:59 GMT):
I am still getting timed out while connectng to orderer
yacovm (Mon, 13 Feb 2017 09:10:19 GMT):
try running a peer and telneting to the orderer host on port 7050
yacovm (Mon, 13 Feb 2017 09:10:19 GMT):
or alternatively connect to an already running peer and telnet from it
yacovm (Mon, 13 Feb 2017 09:10:19 GMT):
try to "connect" to an already running peer and telnet from it
coolsvap (Mon, 13 Feb 2017 09:13:31 GMT):
connected to orderer from peer0
C0rWin (Mon, 13 Feb 2017 09:13:35 GMT):
just completed to run through steps in tutorial, with `channel_test.sh` updated, was able to get
C0rWin (Mon, 13 Feb 2017 09:13:38 GMT):
```SUCCESSFUL CHANNEL CREATION
SUCCESSFUL JOIN CHANNEL on PEER0
SUCCESSFUL JOIN CHANNEL on PEER1
SUCCESSFUL JOIN CHANNEL on PEER2
```
C0rWin (Mon, 13 Feb 2017 09:13:44 GMT):
:/
coolsvap (Mon, 13 Feb 2017 09:24:27 GMT):
@C0rWin not workingfor me :-/
C0rWin (Mon, 13 Feb 2017 09:25:06 GMT):
can you `docker exec -it cli bash`?
C0rWin (Mon, 13 Feb 2017 09:25:18 GMT):
what do you see in `result.txt`?
coolsvap (Mon, 13 Feb 2017 09:25:19 GMT):
@C0rWin yes
coolsvap (Mon, 13 Feb 2017 09:25:19 GMT):
@C0rWin yes
coolsvap (Mon, 13 Feb 2017 09:25:43 GMT):
ERROR on CHANNEL CREATION
C0rWin (Mon, 13 Feb 2017 09:26:25 GMT):
can you run `./channel_test.sh`? and post the output?
coolsvap (Mon, 13 Feb 2017 09:27:34 GMT):
I get the 172.19.0.6 in output
C0rWin (Mon, 13 Feb 2017 09:28:45 GMT):
wait, you run `channel_test.sh` and as output it bring you back the IP address?
C0rWin (Mon, 13 Feb 2017 09:28:56 GMT):
can you post the content of this file?
coolsvap (Mon, 13 Feb 2017 09:30:58 GMT):
```#!/bin/sh
# find address of peer0 in your network
PEER0_IP_ADDRESS=`perl -e 'use Socket; $a = inet_ntoa(inet_aton("peer0")); print "$a\n";'`
# create an anchor file
cat<
C0rWin (Mon, 13 Feb 2017 09:31:54 GMT):
ok, there is nothing here which could do such output.
C0rWin (Mon, 13 Feb 2017 09:32:50 GMT):
are you 100% sure logged into docker cli? and executing script from there?
1. `docker exec -it cli bash`
2. `./channel_test.sh`
C0rWin (Mon, 13 Feb 2017 09:33:31 GMT):
Can you run this: `CORE_PEER_GOSSIP_IGNORESECURITY=true CORE_PEER_MSPCONFIGPATH=/etc/hyperledger/fabric/msp/sampleconfig CORE_PEER_COMMITTER_LEDGER_ORDERER=orderer:7050 peer channel create -c myc1`?
C0rWin (Mon, 13 Feb 2017 09:33:45 GMT):
inside `cli`?
coolsvap (Mon, 13 Feb 2017 09:34:03 GMT):
[root@hyperledger hackfest]# docker ps | grep cli
da42c89971f7 sfhackfest22017/fabric-peer:x86_64-0.7.0-snapshot-c7b3fe0 "sh -c './channel_..." 9 minutes ago Up 9 minutes cli
[root@hyperledger hackfest]# docker exec -it cli bash
root@da42c89971f7:/opt/gopath/src/github.com/hyperledger/fabric/peer# ./channel_test.sh
172.19.0.6
root@da42c89971f7:/opt/gopath/src/github.com/hyperledger/fabric/peer#
C0rWin (Mon, 13 Feb 2017 09:35:26 GMT):
@coolsvap can you try: https://chat.hyperledger.org/channel/fabric?msg=DxqJ2mARS9TxmbNCs?
C0rWin (Mon, 13 Feb 2017 09:35:52 GMT):
are you running on windows, linux, mac?
coolsvap (Mon, 13 Feb 2017 09:36:15 GMT):
@C0rWin I have a centos vm on virtualbox
coolsvap (Mon, 13 Feb 2017 09:36:42 GMT):
@C0rWin https://chat.hyperledger.org/channel/fabric?msg=DxqJ2mARS9TxmbNCs did not work
C0rWin (Mon, 13 Feb 2017 09:36:52 GMT):
what was the error?
coolsvap (Mon, 13 Feb 2017 09:39:29 GMT):
Message Attachments
C0rWin (Mon, 13 Feb 2017 09:40:11 GMT):
do you have orderer container running?
coolsvap (Mon, 13 Feb 2017 09:40:21 GMT):
yes
C0rWin (Mon, 13 Feb 2017 09:40:37 GMT):
can you telnet to orderer?
coolsvap (Mon, 13 Feb 2017 09:40:46 GMT):
# docker ps | grep orderer
223a443f8384 sfhackfest22017/fabric-orderer:x86_64-0.7.0-snapshot-c7b3fe0 "orderer" 17 minutes ago Up 16 minutes 0.0.0.0:8050->7050/tcp
C0rWin (Mon, 13 Feb 2017 09:40:47 GMT):
`telnet orderer 7050`?
coolsvap (Mon, 13 Feb 2017 09:42:45 GMT):
I am getting connection refused when I use IP
yacovm (Mon, 13 Feb 2017 09:43:08 GMT):
do `docker inspect 223a443f8384 `
yacovm (Mon, 13 Feb 2017 09:43:13 GMT):
and tell us the ip address
coolsvap (Mon, 13 Feb 2017 09:43:42 GMT):
connected with ip
coolsvap (Mon, 13 Feb 2017 09:44:28 GMT):
# docker inspect 223a443f8384 | grep IPAddress
"SecondaryIPAddresses": null,
"IPAddress": "",
"IPAddress": "172.19.0.2",
[root@hyperledger hackfest]# telnet 172.19.0.2 7050
Trying 172.19.0.2...
Connected to 172.19.0.2.
Escape character is '^]'.
coolsvap (Mon, 13 Feb 2017 09:45:37 GMT):
also able to connect to peer on 7051
C0rWin (Mon, 13 Feb 2017 09:47:00 GMT):
ok
C0rWin (Mon, 13 Feb 2017 09:47:24 GMT):
try `CORE_PEER_GOSSIP_IGNORESECURITY=true CORE_PEER_MSPCONFIGPATH=/etc/hyperledger/fabric/msp/sampleconfig CORE_PEER_COMMITTER_LEDGER_ORDERER=172.19.0.2:7050 peer channel create -c myc1`
coolsvap (Mon, 13 Feb 2017 09:52:00 GMT):
done!
thojest (Mon, 13 Feb 2017 09:54:01 GMT):
Has joined the channel.
coolsvap (Mon, 13 Feb 2017 10:19:07 GMT):
@C0rWin so its working for me without CORE_PEER_GOSSIP_IGNORESECURITY=true and using IP instead of hostname
C0rWin (Mon, 13 Feb 2017 10:37:17 GMT):
@coolsvap great
coolsvap (Mon, 13 Feb 2017 10:38:31 GMT):
@C0rWin i think its OS specific issue
C0rWin (Mon, 13 Feb 2017 10:38:59 GMT):
could be, but I'm not 100% sure... need to be checked.
dolanort (Mon, 13 Feb 2017 11:09:08 GMT):
Hi, is there an example of a go app (not chaincode) calling a chaincode ?
dolanort (Mon, 13 Feb 2017 11:09:48 GMT):
I'd rather not use node
dolanort (Mon, 13 Feb 2017 11:12:13 GMT):
Actually, I can't use node :p
Thomas_Domingos (Mon, 13 Feb 2017 11:32:05 GMT):
Has joined the channel.
kathrynharrison (Mon, 13 Feb 2017 11:35:16 GMT):
Has joined the channel.
radbrawler (Mon, 13 Feb 2017 11:36:04 GMT):
Has joined the channel.
Basug (Mon, 13 Feb 2017 11:45:35 GMT):
may be worth looking at cli code ?
thojest (Mon, 13 Feb 2017 11:53:40 GMT):
@dolanort have a look here https://github.com/IBM-Blockchain/SDK-Demo/blob/master/helloblockchain.js#L144
thojest (Mon, 13 Feb 2017 11:54:05 GMT):
ahh you mean not nodejs :D
thojest (Mon, 13 Feb 2017 11:54:12 GMT):
then i have no idea
Vadim (Mon, 13 Feb 2017 11:54:50 GMT):
@dolanort check this example: https://github.com/hyperledger/fabric/tree/master/examples/chaincode/go/asset_management_interactive
thojest (Mon, 13 Feb 2017 12:02:35 GMT):
lets assume i want to build a very simple web-app, where users can send money around. I want to make it possible that the users can create an account and afterwards log in /off
thojest (Mon, 13 Feb 2017 12:03:09 GMT):
at the moment im doing it the following way.
thojest (Mon, 13 Feb 2017 12:04:48 GMT):
1) when user registers, admin registers the user and enrolls him. the password of the user he specifies while creating his account i write as a key-value pair to the blockchain, meaning {username, hash(password)}
thojest (Mon, 13 Feb 2017 12:05:51 GMT):
2) user tries to login: check if passwords he provides is the right one, comparing it with PW hash in blockchain. If correct, create a session based cookie for that users and log him in
thojest (Mon, 13 Feb 2017 12:07:06 GMT):
my question is: is this best practice? this writing username + hash of pw as a key value pair to the blockchain, for me seems a bit like a work around
thojest (Mon, 13 Feb 2017 12:07:57 GMT):
what i mean is, how can you reconcile the fact that you can enroll users only once, but users have to be able to log in/ off several times
gatakka (Mon, 13 Feb 2017 12:14:28 GMT):
Why you want to store user password in blockchain? How you will verify it later, you need endoled user certificate to get data from blockchain? I think better approach is:
When you register user in fabric you provide a enrollment id and got back password. You store this password in your database. Also in database you have a "normal" password for user. So when user try to login in the app you check this "normal" password as any other conventional app, get fabric password and enroll user and get certificate.
With this scenario you can use any normal user authentication system, just you store fabric password as user attribute (or whatever is called in the app/framework)
Basug (Mon, 13 Feb 2017 12:14:42 GMT):
Is there a way to get data that was submitted by invoke as events ?
thojest (Mon, 13 Feb 2017 12:16:12 GMT):
@gatakka thanks, im very new to this whole thing, thats why my question might seem a bit dumb ^^
gatakka (Mon, 13 Feb 2017 12:17:26 GMT):
@thojest no worries, it is not a dumb question, fabric is not conventional CRUD app :)
thojest (Mon, 13 Feb 2017 12:18:50 GMT):
@gatakka so if I understand you correct, you say I should store the normal PW together with the enrollment PW in a database, and when users then enters his normal pw i can look up the enrollment pw for him in a table outside the blockchain
thojest (Mon, 13 Feb 2017 12:18:59 GMT):
of course hashed :D
gatakka (Mon, 13 Feb 2017 12:25:42 GMT):
@thojest Yes, password that is generated during Register call to CA cannot be changed (for now). So you have a normal auth module with username/email/password/change password/forgot password etc. It is working as you want, but you keep fabric password in users table, just another column, and when you need it just take it and use it. This will allow you to use existing auth system of any kind (hardware modules, 2 ways confirmation etc) and just plug fabric to work with them.
In general when you register user then you enroll it, this will give you a certificate. It is a very good idea to store this certificate and use it later insted of enrolling user again.
From point of view of fabric one enrollment = one valid certificate and later all invocations to fabric MUST be with this certificate. So password is used only once, to get this Ecert (Enrollment certificate)
thojest (Mon, 13 Feb 2017 12:27:27 GMT):
ahh ok, and when user wants to log in later and provides the correct normal pw for his account you just have to look if there exists an ECert for this user?
gatakka (Mon, 13 Feb 2017 12:29:14 GMT):
exactly!
thojest (Mon, 13 Feb 2017 12:29:33 GMT):
@gattaka thx a lot!
thojest (Mon, 13 Feb 2017 12:29:46 GMT):
so i understood that with ECerts.
thojest (Mon, 13 Feb 2017 12:29:54 GMT):
now i have to make familiar with TCerts :D
Vadim (Mon, 13 Feb 2017 12:31:56 GMT):
@Basug in v1?
gatakka (Mon, 13 Feb 2017 12:31:58 GMT):
TCerts in v 0.6 are easy but will change in v1. For now TCerts are not ready v1, so we have to wait :) In general Tcerts (transaction certificate) is generated for every transaction, and hide user identity from Ecert, but details are tricky and very smart people now are tring to make them work :)
Basug (Mon, 13 Feb 2017 12:32:14 GMT):
@vadim - Yes
Vadim (Mon, 13 Feb 2017 12:32:41 GMT):
the master branch for fabric and node-sdk support events
Vadim (Mon, 13 Feb 2017 12:32:41 GMT):
the master branches for fabric and node-sdk support events
Basug (Mon, 13 Feb 2017 12:32:56 GMT):
I am able to get events
Basug (Mon, 13 Feb 2017 12:33:13 GMT):
but Block contains only responses status of 200 and not the data that was submitted
Vadim (Mon, 13 Feb 2017 12:33:19 GMT):
well the data is passed as an argument to callback
Vadim (Mon, 13 Feb 2017 12:33:27 GMT):
which event type do you use?
thojest (Mon, 13 Feb 2017 12:33:42 GMT):
@gatakka thx again, one more question :) what are these TLS Certs?
Vadim (Mon, 13 Feb 2017 12:34:00 GMT):
there are chaincode events, there you can get the data which has been sent by the chaincode
thojest (Mon, 13 Feb 2017 12:34:01 GMT):
can you compare this to https, like securing the communication channel?
Basug (Mon, 13 Feb 2017 12:34:31 GMT):
@Vadim does eventhub get those events as well ?
Vadim (Mon, 13 Feb 2017 12:34:53 GMT):
if you referring to node-sdk, then yes
Vadim (Mon, 13 Feb 2017 12:35:06 GMT):
but it's in the master branch, the support was added quite recently
thojest (Mon, 13 Feb 2017 12:35:48 GMT):
@Vadim @Basug if i remember correctly, i think there was a problem in v0.6 to get events on invoke?
Vadim (Mon, 13 Feb 2017 12:36:04 GMT):
@Basug eventHub.registerChaincodeEvent(ccname, evtName, cb);
Vadim (Mon, 13 Feb 2017 12:36:17 GMT):
@thojest it's v1
Basug (Mon, 13 Feb 2017 12:38:39 GMT):
thanks @Vadim I see it in EventHub.js . As far as eventName - doc says ` @param {string} eventname string The regex string used to filter events` is there a list of what valid event names are ?
Vadim (Mon, 13 Feb 2017 12:38:56 GMT):
it's the event that you generate in your chaincode
Vadim (Mon, 13 Feb 2017 12:39:20 GMT):
i.e. stub.SetEvent("EventName", participantJSON)
Vadim (Mon, 13 Feb 2017 12:39:20 GMT):
i.e. stub.SetEvent("EventName", data)
Basug (Mon, 13 Feb 2017 12:39:30 GMT):
Ah I missed that.. Is there an example, which does this ?
Basug (Mon, 13 Feb 2017 12:39:49 GMT):
I mean the one that does SetEvent ?
murrekatt (Mon, 13 Feb 2017 12:39:51 GMT):
Has joined the channel.
Vadim (Mon, 13 Feb 2017 12:39:51 GMT):
well I don't know, but his is quite straightforward
Basug (Mon, 13 Feb 2017 12:40:09 GMT):
Thank you. I will try it out
Vadim (Mon, 13 Feb 2017 12:40:12 GMT):
just one line at the end of your chaincode func before you send shim.Success(nil)
Vadim (Mon, 13 Feb 2017 12:40:12 GMT):
just one line at the end of your chaincode func before you return shim.Success(nil)
Basug (Mon, 13 Feb 2017 12:40:56 GMT):
ok, we don't need to do any encoding and all that.. Thanks much.. This would be good for me to take it further
Vadim (Mon, 13 Feb 2017 12:41:28 GMT):
you don't, but you can return JSON and then it will be easier to handle it in node
Basug (Mon, 13 Feb 2017 12:44:13 GMT):
sure. thanks !
Vadim (Mon, 13 Feb 2017 12:45:31 GMT):
no problem
thojest (Mon, 13 Feb 2017 13:41:04 GMT):
the following question hast nothing to do with hyperledger or fabric, but is related somehow because i want to build an app based on fabric, so i would be very thankful if someone has an idea
thojest (Mon, 13 Feb 2017 13:41:43 GMT):
im setting up a node-js server. Then I want to visit my app from a different computer entering the ip6 address and the correct port on which the app listens
thojest (Mon, 13 Feb 2017 13:41:50 GMT):
the good message is it works...
thojest (Mon, 13 Feb 2017 13:42:36 GMT):
the problem is, that every initial connection attempt needs +10 seconds, sometimes I even get a timeout, and when you then click try again it works.
thojest (Mon, 13 Feb 2017 13:43:42 GMT):
Afterwards every other connection attempt like querying chaincode or making transactions through the webinterface happens in the blink of an eye.. but if you wait to long i.e. a few minutes and try again to do somthing it again takes very long to get a response
thojest (Mon, 13 Feb 2017 13:44:08 GMT):
i tried to google that for hours but couldnt find a good idea how to solve this or what might be the reason
Clayton Sims (Mon, 13 Feb 2017 14:11:36 GMT):
Has joined the channel.
ssaddem (Mon, 13 Feb 2017 14:45:00 GMT):
Failed to init chaincode(handler not found for chaincode )
ssaddem (Mon, 13 Feb 2017 14:45:21 GMT):
i got this error in --peer-chaincodedev
ssaddem (Mon, 13 Feb 2017 14:45:27 GMT):
can you help me plz
thojest (Mon, 13 Feb 2017 14:49:24 GMT):
@ssaddem which version of hyperledger u use
thojest (Mon, 13 Feb 2017 14:49:33 GMT):
do you deploy chaincode via CLI ?
ssaddem (Mon, 13 Feb 2017 14:49:47 GMT):
v0.6
thojest (Mon, 13 Feb 2017 14:50:06 GMT):
have you registered chaincode before deployment?
ssaddem (Mon, 13 Feb 2017 14:50:31 GMT):
in nop
thojest (Mon, 13 Feb 2017 14:50:42 GMT):
what?
ssaddem (Mon, 13 Feb 2017 14:51:29 GMT):
nope
ssaddem (Mon, 13 Feb 2017 14:51:43 GMT):
i have delete /var/hyperledger contenent
ssaddem (Mon, 13 Feb 2017 14:52:08 GMT):
but it work without --peer-chaincodedev
thojest (Mon, 13 Feb 2017 14:54:11 GMT):
so when you try to deploy a chaincode in dev mode
thojest (Mon, 13 Feb 2017 14:54:24 GMT):
afaik you have to register the chaincode before deploying it
thojest (Mon, 13 Feb 2017 14:54:55 GMT):
something like this
thojest (Mon, 13 Feb 2017 14:54:58 GMT):
`CORE_CHAINCODE_ID_NAME=mycc CORE_PEER_ADDRESS=0.0.0.0:7051 ./chaincode_example02`
thojest (Mon, 13 Feb 2017 14:55:21 GMT):
`peer chaincode deploy -n mycc -c '{"Args": ["init", "a","100", "b", "200"]}'`
thojest (Mon, 13 Feb 2017 14:55:31 GMT):
then deploy it
ssaddem (Mon, 13 Feb 2017 14:55:44 GMT):
ok thanks a lot :)
thojest (Mon, 13 Feb 2017 14:56:13 GMT):
np, hope it works
ssaddem (Mon, 13 Feb 2017 14:57:06 GMT):
yes it's work
ssaddem (Mon, 13 Feb 2017 14:57:30 GMT):
thx :)
murrekatt (Mon, 13 Feb 2017 15:10:09 GMT):
is the release date for 1.0 set and where is the place to find an overview of the work?
s.narayanan (Mon, 13 Feb 2017 15:52:51 GMT):
Has joined the channel.
dhwang (Mon, 13 Feb 2017 15:53:47 GMT):
Has joined the channel.
conroydave (Mon, 13 Feb 2017 16:00:20 GMT):
I am running the v2 branch of boilerplate in docker on my macbook.
conroydave (Mon, 13 Feb 2017 16:00:27 GMT):
already have had success with the main branch v1
conroydave (Mon, 13 Feb 2017 16:00:42 GMT):
now that i am using the TS version, everythign seems to build and launch fine
conroydave (Mon, 13 Feb 2017 16:00:52 GMT):
but when I try to login - i get nothing. it just sits on this page
conroydave (Mon, 13 Feb 2017 16:01:23 GMT):
Message Attachments
conroydave (Mon, 13 Feb 2017 16:02:06 GMT):
the server see's the get , the logs: server_1 | debug: ::ffff:192.168.99.1 - - [Mon, 13 Feb 2017 15:54:51 GMT] "GET / HTTP/1.1" 404 13 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_4) AppleWebKit/537.36 (KHTML, like Gecko) Kitematic/0.10.4 Chrome/45.0.2454.85 Electron/0.35.4 Safari/537.36"
conroydave (Mon, 13 Feb 2017 16:08:10 GMT):
trying to debug, looking in the logs i find this: fabricboilerplate_utils_1 exited with code 0
conroydave (Mon, 13 Feb 2017 16:20:52 GMT):
is that container supposed to stay up?
Dsummers91 (Mon, 13 Feb 2017 17:05:04 GMT):
W) 2
Dsummers91 (Mon, 13 Feb 2017 17:05:49 GMT):
Try running ./clean.sh - and that should fix it, usually works for me
Dsummers91 (Mon, 13 Feb 2017 17:07:08 GMT):
I have a question, may be a dumb question.. Is it possible to update a members attributes after he's been registered? If so how would I go about doing that
tennenjl (Mon, 13 Feb 2017 17:32:23 GMT):
Has joined the channel.
KouichiUme (Mon, 13 Feb 2017 17:42:51 GMT):
Has joined the channel.
WebKruncher (Mon, 13 Feb 2017 18:56:24 GMT):
Has joined the channel.
mrkiouak (Mon, 13 Feb 2017 20:09:34 GMT):
on the fabric v1 getting started.... i'm trying to troubleshoot grpc connection issues with the node client (deploy fails with events.js:141
throw er; // Unhandled 'error' event
^
Error: Connect Failed)
mrkiouak (Mon, 13 Feb 2017 20:09:50 GMT):
neither stopping & starting peers nor hardcoding ip has resolved the connect issue
mrkiouak (Mon, 13 Feb 2017 20:09:56 GMT):
any other suggestions to troubleshoot?
mrkiouak (Mon, 13 Feb 2017 20:10:24 GMT):
ports match up from config.json to docker ps results, etc.
mrkiouak (Mon, 13 Feb 2017 20:19:34 GMT):
would appreciate help from anyone who may have time and is familiar with this sf hackfest/v1 image setup-- feel free to direct message me. Again, any time is greatly appreciated :).
greg.haskins (Mon, 13 Feb 2017 21:16:12 GMT):
did you get resolution on this @mrkiouak
greg.haskins (Mon, 13 Feb 2017 21:16:15 GMT):
?
rjones (Mon, 13 Feb 2017 23:59:18 GMT):
Has left the channel.
dsanchezseco (Tue, 14 Feb 2017 11:16:37 GMT):
Has joined the channel.
Jonas.Hedin (Tue, 14 Feb 2017 11:52:42 GMT):
What is the best way to test you chaincode? Is there a better way than deploying it every time you have made a change to the code?
Vadim (Tue, 14 Feb 2017 11:55:52 GMT):
@Jonas.Hedin check out how the example chaincode is being tested: https://github.com/hyperledger/fabric/blob/master/examples/chaincode/go/chaincode_example02/chaincode_example02_test.go
Jonas.Hedin (Tue, 14 Feb 2017 12:00:58 GMT):
aah, thanks @Vadim
Missed those files completely
Vadim (Tue, 14 Feb 2017 12:01:12 GMT):
you're welcome
oiakovlev (Tue, 14 Feb 2017 12:35:57 GMT):
Hi here, have a question about Bluemix but have not found separate channel, so hope this one would be fine :)
If we want to restrict access to the peer url some how would it be possible with Bluemix via VPN setup for example? If so, I have not found such option in Bluemix dashboard - should it be separate request to Bluemix support?
murrekatt (Tue, 14 Feb 2017 12:44:48 GMT):
did the REST API move away from the peer in v1.0? don't see any config for the endpoint in `core.yml` anymore.
oiakovlev (Tue, 14 Feb 2017 12:46:35 GMT):
yes, REST API has been deprecated - only gRPC is available via one of the SDKs..
oiakovlev (Tue, 14 Feb 2017 12:46:35 GMT):
yes, REST API has been deprecated - only gRPC will be available via one of the SDKs..
murrekatt (Tue, 14 Feb 2017 12:48:30 GMT):
I assume the CLI too is deprecated then
murrekatt (Tue, 14 Feb 2017 12:49:02 GMT):
which endpoint is the gRPC then for the peer?
murrekatt (Tue, 14 Feb 2017 12:51:04 GMT):
i'm reading both the code and the docs in various places but it seems all is not up the date with the v1.0 so i just ask for clarification
murrekatt (Tue, 14 Feb 2017 12:52:17 GMT):
i.e. i see the peer has two endpoint defaulting to `:7053` for events and `:7051` for the peer itself
murrekatt (Tue, 14 Feb 2017 12:52:50 GMT):
is it correct that both these use gRPC and protobuf?
rickr (Tue, 14 Feb 2017 14:02:44 GMT):
while building locally I'm seeing ...
make[1]: Leaving directory '/opt/gopath/src/github.com/hyperledger/fabric/gotools
cp /opt/gotools/obj/gopath/bin/golint /opt/gotools/obj/gopath/bin/govendor /opt/gotools/obj/gopath/bin/goimports /opt/gotools/obj/gopath/bin/protoc-gen-go /opt/gotools/obj/gopath/bin/ginkgo /opt/gotools/obj/gopath/bin/gocov /opt/gotools/obj/gopath/bin/gocov-xml /opt/gotools/bin
env | grep GO
GOROOT=/usr/local/lib/go
GOPATH=/home/rineholt/gitws/bc/fabric-0210
why is it copying it to `/opt/gotools` and cd to `/opt/gopath/`
I'm building locally and expect all my build artifacts to be in `/home/rineholt/gitws/bc/fabric-0210`
``
rickr (Tue, 14 Feb 2017 14:02:44 GMT):
while building locally I'm seeing ...
make[1]: Leaving directory '/opt/gopath/src/github.com/hyperledger/fabric/gotools
cp /opt/gotools/obj/gopath/bin/golint /opt/gotools/obj/gopath/bin/govendor /opt/gotools/obj/gopath/bin/goimports /opt/gotools/obj/gopath/bin/protoc-gen-go /opt/gotools/obj/gopath/bin/ginkgo /opt/gotools/obj/gopath/bin/gocov /opt/gotools/obj/gopath/bin/gocov-xml /opt/gotools/bin
env | grep GO
GOROOT=/usr/local/lib/go
GOPATH=/home/rineholt/gitws/bc/fabric-0210
why is it copying it to `/opt/gotools` and cd to `/opt/gopath/`
I'm building locally and expect all my build artifacts to be in `/home/rineholt/gitws/bc/fabric-0210`
rickr (Tue, 14 Feb 2017 14:05:07 GMT):
``perledger/fabric/protos/orderer github.com/hyperledger/fabric/protos/peer github.com/hyperledger/fabric/protos/testutils github.com/hyperledger/fabric/protos/utils -p 1 -timeout=20m
unit-tests_1 | ./unit-test/run.sh: line 32: gocov-xml: command not found
unit-tests_1 | ./unit-test/run.sh: line 32: gocov: command not found
unittest_unit-tests_1 exited with code 127
Aborting on container exit...
``
rickr (Tue, 14 Feb 2017 14:05:07 GMT):
```perledger/fabric/protos/orderer github.com/hyperledger/fabric/protos/peer github.com/hyperledger/fabric/protos/testutils github.com/hyperledger/fabric/protos/utils -p 1 -timeout=20m
unit-tests_1 | ./unit-test/run.sh: line 32: gocov-xml: command not found
unit-tests_1 | ./unit-test/run.sh: line 32: gocov: command not found
unittest_unit-tests_1 exited with code 127
Aborting on container exit...
```
rickr (Tue, 14 Feb 2017 14:07:07 GMT):
Can someone familiar with the build look into this ? Try building somewhere outside of /opt ? I think this has be recently introduced as I've do this in the past and not see this
jamessheen (Tue, 14 Feb 2017 15:00:30 GMT):
Has joined the channel.
dolanort (Tue, 14 Feb 2017 15:14:55 GMT):
[ ](https://chat.hyperledger.org/channel/fabric?msg=cAyRNqkoPxJFtRcNh) @Vadim Hi
I tried to follow it, but I don't think the code is still good. There is nothing in the core/crypto dir, and it seems it needs the crypto.Client.
Should i checkout some older version (0.6 ?)
bmos299 (Tue, 14 Feb 2017 15:51:11 GMT):
Please ensure when opening bugs to include:
Fix Version/s:
v1.0.0
fmarino (Tue, 14 Feb 2017 17:00:14 GMT):
Has joined the channel.
fmarino (Tue, 14 Feb 2017 17:36:18 GMT):
Hello everyone! I need to validate a transaction in such a way that one user starts the transaction with his token and another user finishes it (using his token, different from the one used to start the transaction).
Actually I need a multiple-signatures validation. Is this feature present in hyperledger 0.6.1 (that's my current version)?
kamo (Tue, 14 Feb 2017 18:07:16 GMT):
Has joined the channel.
marcusvcs (Tue, 14 Feb 2017 19:42:06 GMT):
i am trying to run https://github.com/hyperledger/fabric/tree/master/examples/chaincode/go/marbles02 in 1.0 using the hackfest version (http://hyperledger-fabric.readthedocs.io/en/latest/gettingstarted/) and I am getting an error on deploy:
src/build-chaincode/marbles.go:317: stub.GetStateByPartialCompositeKey undefined
Any ideas?
kostas (Tue, 14 Feb 2017 20:52:12 GMT):
https://chat.hyperledger.org/channel/fabric-maintainers?msg=yqcb9Pan4o3og2YRY
kostas (Tue, 14 Feb 2017 20:52:27 GMT):
@dshuffma:
dshuffma (Tue, 14 Feb 2017 20:52:27 GMT):
Has joined the channel.
kostas (Tue, 14 Feb 2017 20:53:14 GMT):
`Data` is where you would expect to find, say, a least of all the transactions included in the block.
kostas (Tue, 14 Feb 2017 20:53:44 GMT):
`Metadata` is a slice where you expect to find this kind of metadata:
kostas (Tue, 14 Feb 2017 20:53:45 GMT):
https://github.com/hyperledger/fabric/blob/master/protos/common/common.proto#L47
kostas (Tue, 14 Feb 2017 20:54:05 GMT):
i.e. in the first slot, you expect to find signatures over the block
kostas (Tue, 14 Feb 2017 20:54:31 GMT):
In the second block, the sequence number of the block that carried the most recent configuration.
kostas (Tue, 14 Feb 2017 20:54:31 GMT):
In the second slot, the sequence number of the block that carried the most recent configuration.
kostas (Tue, 14 Feb 2017 20:54:54 GMT):
etc.
kostas (Tue, 14 Feb 2017 20:54:58 GMT):
Let me know if that covers you.
dshuffma (Tue, 14 Feb 2017 20:56:17 GMT):
ok that make sense, but doesn't really align with what i'm seeing. everything i see in data is also in metadata (identical).
kostas (Tue, 14 Feb 2017 20:56:41 GMT):
Interesting. Who produces these blocks?
dshuffma (Tue, 14 Feb 2017 20:57:02 GMT):
but forget that for now, i don't see transaction payload details at all, is that on purpose? i do see what looks like the outcome of the transaction
dshuffma (Tue, 14 Feb 2017 20:57:29 GMT):
there are chaincode transactions from an application
dshuffma (Tue, 14 Feb 2017 20:57:29 GMT):
there are chaincode transactions from an application (successful ones)
dshuffma (Tue, 14 Feb 2017 20:57:29 GMT):
these are chaincode transactions from an application (successful ones)
kostas (Tue, 14 Feb 2017 20:58:39 GMT):
Are you unmarshalling the block `Data` (type `BlockData`) properly before inspecting it?
dshuffma (Tue, 14 Feb 2017 20:59:33 GMT):
the marshaling isn't done by me really, its done by "qscc" https://github.com/hyperledger/fabric/blob/a4646a9ede1d7594c77c3daaa18b3dcb0c8e4260/core/scc/qscc/querier.go
kostas (Tue, 14 Feb 2017 21:00:55 GMT):
Interesting. I haven't played around with this at all.
dshuffma (Tue, 14 Feb 2017 21:01:03 GMT):
ok
kostas (Tue, 14 Feb 2017 21:01:05 GMT):
Can you screenshare?
kostas (Tue, 14 Feb 2017 21:02:05 GMT):
Also, on what kind of orderer do you run this? Solo, Kafka?
dshuffma (Tue, 14 Feb 2017 21:03:19 GMT):
no screenshare lol, not important enough. its solo, (hackfest docker images). I can continue as is, just wanted to know if someone could enlighten me
rickr (Tue, 14 Feb 2017 21:22:56 GMT):
```
$docker-compose up --abort-on-container-exit --force-recreate
WARNING: The TEST_PKGS variable is not set. Defaulting to a blank string.
Pulling unit-tests (hyperledger/fabric-testenv:latest)...
Trying to pull repository docker.io/hyperledger/fabric-testenv ...
ERROR: unauthorized: authentication required
```
rickr (Tue, 14 Feb 2017 21:22:56 GMT):
```
$docker-compose up --abort-on-container-exit --force-recreate
WARNING: The TEST_PKGS variable is not set. Defaulting to a blank string.
Pulling unit-tests (hyperledger/fabric-testenv:latest)...
Trying to pull repository docker.io/hyperledger/fabric-testenv ...
ERROR: unauthorized: authentication required
```
rickr (Tue, 14 Feb 2017 21:22:56 GMT):
cd unit-tests
```
$docker-compose up --abort-on-container-exit --force-recreate
WARNING: The TEST_PKGS variable is not set. Defaulting to a blank string.
Pulling unit-tests (hyperledger/fabric-testenv:latest)...
Trying to pull repository docker.io/hyperledger/fabric-testenv ...
ERROR: unauthorized: authentication required
```
rickr (Tue, 14 Feb 2017 21:23:09 GMT):
Any ideas ?
yacovm (Tue, 14 Feb 2017 21:28:22 GMT):
@rickr ask in #fabric-dev-env too
rickr (Tue, 14 Feb 2017 21:28:49 GMT):
k
boliang (Wed, 15 Feb 2017 01:22:27 GMT):
Has joined the channel.
siddhid (Wed, 15 Feb 2017 04:28:56 GMT):
what is the command promt command for specifying the certificates to be included/avoided while creating the channel
binhn (Wed, 15 Feb 2017 05:00:47 GMT):
@bmos299 created a nice jira filter https://jira.hyperledger.org/issues/?filter=10500
zhangchao (Wed, 15 Feb 2017 05:46:19 GMT):
Has joined the channel.
daudahmad (Wed, 15 Feb 2017 09:24:51 GMT):
Has joined the channel.
pospi (Wed, 15 Feb 2017 09:50:30 GMT):
Has joined the channel.
murrekatt (Wed, 15 Feb 2017 12:20:35 GMT):
in vagrant dev end with latest master and have a docker compose with orderer and single peer and see in log at start `[peer] Initialize -> WARN 195^[[0m Failed to load ledger testchainid(Ledger already opened)`. not sure what might trigger this?
o.o. (Wed, 15 Feb 2017 13:31:35 GMT):
In the architecture deep dive of the fabric documentation (http://hyperledger-fabric.readthedocs.io/en/latest/arch-deep-dive/) it seems that the node ledgers may also store invalid transactions (for example not fulfilling the version dependencies in a readset). There is also something called a _validated ledger (or vLedger)_, which has filtered out the invalid transactions.
It also seems that it would be possible to simply not have the orderers deliver them.
Does anyone know why they are kept; or where I can read up more on the motivation behind the inclusion of invalid transactions?
o.o. (Wed, 15 Feb 2017 13:31:35 GMT):
In the architecture deep dive of the fabric documentation (http://hyperledger-fabric.readthedocs.io/en/latest/arch-deep-dive/) it seems that the node ledgers may also store invalid transactions (for example not fulfilling the version dependencies in a readset). There is also something called a _validated ledger (or vLedger)_, which has filtered out the invalid transactions.
It also seems that it would be possible to simply not have the orderers deliver them.
Does anyone know why they are kept; or where I can read up more on the motivation behind the inclusion of invalid transactions in the ledgers?
jwolpert (Wed, 15 Feb 2017 13:34:08 GMT):
Has joined the channel.
nickmelis (Wed, 15 Feb 2017 13:35:59 GMT):
how would you implement a unique id generator (possibly for an incrementing sequence number) within the chaincode? I was thinking about using a variable in the state to keep track of the latest sequence number but how would you ensure it is read/written in an atomic way across nodes?
Vadim (Wed, 15 Feb 2017 13:36:58 GMT):
is it not what consensus algorithm is for?
henriquecd (Wed, 15 Feb 2017 13:38:35 GMT):
Has joined the channel.
yacovm (Wed, 15 Feb 2017 13:39:59 GMT):
@o.o. - Think of the following- you're a peer and you want to fetch blocks from another peer. These blocks, are signed by the ordering service.
If that peer gives you just the transactions he considered valid, there is no way of him to prove that these transactions really came from the block that ordering service created, other then sending you also the block itself.
yacovm (Wed, 15 Feb 2017 13:40:15 GMT):
So, in short- peers replicate blocks between themselves and want to validate the authenticity of these blocks
yacovm (Wed, 15 Feb 2017 13:40:24 GMT):
so that's why they keep the raw blocks from the ordering service
yacovm (Wed, 15 Feb 2017 13:40:33 GMT):
and only commit the transactions they consider valid
o.o. (Wed, 15 Feb 2017 13:44:03 GMT):
Thanks for the answer, and sorry if I am slow;
but why would the ordering service include the invalid transactions in the raw blocks in the first place?
It is not the ordering services place to mess with questions of validity?
o.o. (Wed, 15 Feb 2017 13:44:03 GMT):
Thanks yacovm for the answer, and sorry if I am slow;
but why would the ordering service include the invalid transactions in the raw blocks in the first place?
It is not the ordering services place to mess with questions of validity?
murrekatt (Wed, 15 Feb 2017 13:44:09 GMT):
thanks @yacovm this is an important distinction from bitcoin where the transactions in a block in fact are all valid
murrekatt (Wed, 15 Feb 2017 13:44:56 GMT):
@o.o. three steps, endorsement, order, commit...i.e. can fail at each step
murrekatt (Wed, 15 Feb 2017 13:45:05 GMT):
at least in v1.0
yacovm (Wed, 15 Feb 2017 13:48:22 GMT):
@o.o. the ordering service isn't supposed to interfere with business logic. It doesn't know whether you move money from bank A to bank B or count a number of cows in your farm.
Its sole job is to - well, order transactions in order for all peers to receive the same order, and this way to prevent double spending, and data divergence.
In order for it to not include invalid transactions, it'd need to have the logic of the peers inside and it would make it more complex and slow.
murrekatt (Wed, 15 Feb 2017 13:50:21 GMT):
maybe there would be a better term than block here...batch maybe
yacovm (Wed, 15 Feb 2017 13:50:48 GMT):
batch is a set of transactions, that a block is made of
murrekatt (Wed, 15 Feb 2017 13:52:49 GMT):
so what does the block encapsulate?
yacovm (Wed, 15 Feb 2017 13:55:02 GMT):
you can take a look in https://github.com/hyperledger/fabric/tree/master/protos/orderer
yacovm (Wed, 15 Feb 2017 13:55:17 GMT):
Sorry I can't give anymore detailed information, in the middle of something :)
murrekatt (Wed, 15 Feb 2017 13:56:29 GMT):
would be curious to hear the rationale behind batch and block to understand what is sought to model.
murrekatt (Wed, 15 Feb 2017 13:58:00 GMT):
block and blockchain are clear in bitcoin but here it becomes slightly confusing with also batch and blocks with invalid txs. maybe we could make it clearer?
murrekatt (Wed, 15 Feb 2017 13:58:57 GMT):
something like transaction -> block -> blockchain and transaction proposal -> endorsed transaction -> ordered transactions (batch?) -> ledger
o.o. (Wed, 15 Feb 2017 14:15:54 GMT):
Thanks again yacovm!
bobbiejc (Wed, 15 Feb 2017 14:19:27 GMT):
Has joined the channel.
sk.karl (Wed, 15 Feb 2017 14:36:22 GMT):
Hi, I'm trying to find out if there is a way for a (system) chaincode to differentiate between invokers, peers vs. client. I am looking at shim.GetCallerCertificate(), shim.GetCallerMetadata() and authshim.go but it seems like it's WIP and I'm not clear on were it's going. Can someone explain the general concept or point me to the right piece of documentation? Thanks.
dolanor (Wed, 15 Feb 2017 14:55:44 GMT):
Has joined the channel.
nickgaski (Wed, 15 Feb 2017 15:07:45 GMT):
[ ](https://chat.hyperledger.org/channel/fabric?msg=mevHLdkPLp6axtsiQ) @o.o. take this to the ledger channel. I suppose you could make the argument that a record of invalid txs might be desired for auditing and quality control purposes or to ascertain whether a certain party on your channel repeatedly tries to double spend. It's a good question though.
hwg (Wed, 15 Feb 2017 15:18:13 GMT):
Has joined the channel.
kidinamoto (Wed, 15 Feb 2017 16:02:14 GMT):
Has joined the channel.
jtrayfield (Wed, 15 Feb 2017 16:29:31 GMT):
I'm having trouble with deployment in network mode:
12:45:40.388 [consensus/statetransfer] blockThread -> INFO 017 Validated blockchain to the genesis block
12:45:40.388 [rest] StartOpenchainRESTServer -> INFO 018 Initializing the REST service on 0.0.0.0:7050, TLS is disabled.
2017/02/09 12:46:42 transport: http2Server.HandleStreams received bogus greeting from client: "POST /registrar HTTP/1.1"
2017/02/09 12:47:21 transport: http2Server.HandleStreams received bogus greeting from client: "GET /network/peers HTTP/"
2017/02/09 12:47:27 transport: http2Server.HandleStreams received bogus greeting from client: "GET /network/peers HTTP/"
14:49:43.652 [chaincode] processStream -> ERRO 019 Error handling chaincode support stream: stream error: code = 1 desc = "context canceled"
jtrayfield (Wed, 15 Feb 2017 16:30:35 GMT):
the code works fine in development mode. this is on v0.6
jtrayfield (Wed, 15 Feb 2017 17:22:34 GMT):
nevermind I found the problem
kostas (Wed, 15 Feb 2017 19:48:05 GMT):
@muralisr Looking at [this changeset](https://github.com/hyperledger/fabric/commit/3b6c70d4576b0c2356dea9f89d320170f0aca7e7#diff-78365d16127d04b2316d974959ae57deR62) and the description of the `epoch` field in `ChannelHeader` in `common.proto` is giving me pause. Why do we mention "reponses" and "proposal responses" here? Is the `epoch` field only used for those? That's the impression I get, but I'm not sure that should be the case.
kostas (Wed, 15 Feb 2017 19:48:05 GMT):
@muralisr Looking at [this changeset](https://github.com/hyperledger/fabric/commit/3b6c70d4576b0c2356dea9f89d320170f0aca7e7#diff-78365d16127d04b2316d974959ae57deR62) and the description of the `epoch` field in `ChannelHeader` in `common.proto` is giving me pause. Why do we mention "reponses" and "proposal responses" here? Is the `epoch` field only used for those? That's the impression I get, but I'm not sure that should be the case.
kostas (Wed, 15 Feb 2017 19:48:05 GMT):
@muralisr Looking at [this changeset](https://github.com/hyperledger/fabric/commit/3b6c70d4576b0c2356dea9f89d320170f0aca7e7#diff-78365d16127d04b2316d974959ae57deR62) and the description of the `epoch` field in `ChannelHeader` in `common.proto` is giving me pause. Why do we mention "reponses" and "proposal responses" here? Is the `epoch` field only used for those? That's the impression I get, but I'm not sure that should be the case.
kostas (Wed, 15 Feb 2017 19:48:05 GMT):
@muralisr Looking at [this changeset](https://github.com/hyperledger/fabric/commit/3b6c70d4576b0c2356dea9f89d320170f0aca7e7#diff-78365d16127d04b2316d974959ae57deR62) and the description of the `epoch` field in `ChannelHeader` in `common.proto` is giving me pause. Why do we mention "reponses" and "proposal responses" here? Is the `epoch` field only used for those? That's the impression I get, but I'm not sure that should be the case.
UshKrish (Wed, 15 Feb 2017 20:27:02 GMT):
Has joined the channel.
UshKrish (Wed, 15 Feb 2017 20:27:21 GMT):
To make life easy (?) we use the docker version (which is currently on Ubuntu) and documentation for docker for the build says IBMHyperledger supported. Is docker based option the correct way to go for Hyperledger if enterprise application is the target? If docker what are other supported docker platforms. If it is supported to be on VMs directly - what are the options? As a mini question - I see new dockers are spinned everytime I deploy a new chaincode. If not a docker version, how will this work?
raj (Wed, 15 Feb 2017 20:29:51 GMT):
Has joined the channel.
shabs (Wed, 15 Feb 2017 20:44:52 GMT):
Has joined the channel.
shabs (Wed, 15 Feb 2017 20:53:02 GMT):
hi , i tried to re-deploy my HyperLedger project on bluemix after a small change and it gives this error :
shabs (Wed, 15 Feb 2017 20:53:19 GMT):
"Identity or token does not match.There was an error starting the demo. Please try again. Ensure you delete both the demo and the blockchain service"
munapower (Wed, 15 Feb 2017 21:05:19 GMT):
Has joined the channel.
david_dornseifer (Wed, 15 Feb 2017 21:11:39 GMT):
Has joined the channel.
david_dornseifer (Wed, 15 Feb 2017 21:18:08 GMT):
Hi, get this when i try to deploy some chaincode via the cli / using the latest yeasy build `Error endorsing chaincode: rpc error: code = 2 desc = Failed to deserialize creator identity, err MSP DEFAULT is unknown`
david_dornseifer (Wed, 15 Feb 2017 21:18:29 GMT):
is there a doc describing the MSP setup>
david_dornseifer (Wed, 15 Feb 2017 21:18:29 GMT):
is there a doc describing the MSP setup?
ThomasB (Wed, 15 Feb 2017 23:18:15 GMT):
Has joined the channel.
UshKrish (Thu, 16 Feb 2017 02:29:18 GMT):
What is the difference between setting up Hyperledger.org docker (based on Ubuntu?) and IBMBlockchain docker (based on linux ... ?). Is there a difference between the two, if so what and as a typical user (for production purposes), how should one decide?
MadhavaReddy (Thu, 16 Feb 2017 06:03:06 GMT):
Has joined the channel.
baohua (Thu, 16 Feb 2017 06:51:58 GMT):
the msp problem has been fixed already.
baohua (Thu, 16 Feb 2017 06:52:26 GMT):
the `peer deploy` command is changing, need to update the getting-started-doc.
baohua (Thu, 16 Feb 2017 06:52:26 GMT):
the `peer deploy` command is changed, need to update the getting-started-doc.
saifulislamsaaif (Thu, 16 Feb 2017 07:54:47 GMT):
Has joined the channel.
Vadim (Thu, 16 Feb 2017 08:40:33 GMT):
@all does anybody else have an orderer process crash on channel creation? I have just checked out the latest fabric and it does not work anymore. More details here: https://lists.hyperledger.org/pipermail/hyperledger-fabric/2017-February/000638.html. Thanks for the help!
SriramaSharma (Thu, 16 Feb 2017 08:52:18 GMT):
@ushapriya.krishnan@gmail.com docker images that you see on docker hub under hyperledger org (https://hub.docker.com/u/hyperledger/) are the one's published by the Hyperledger community through the community CI pipeline. The docker images in dockerhub under IBMBlockchain org (https://hub.docker.com/u/ibmblockchain/) are in sync with v0.6 community released docker images and also comes with an support option from IBM.
murrekatt (Thu, 16 Feb 2017 08:54:38 GMT):
@Vadim what commit hash are you on?
Vadim (Thu, 16 Feb 2017 08:55:09 GMT):
7559dd9d727669cc95eb0334848c7196fe4fb161
Vadim (Thu, 16 Feb 2017 08:55:29 GMT):
I've also checked out 02322a1ff68b0238ae6a575372235835155b66a8 and there it works
Vadim (Thu, 16 Feb 2017 08:55:51 GMT):
that one is just before FAB-2225 commit
murrekatt (Thu, 16 Feb 2017 08:58:53 GMT):
will test too. do you have e.g. a docker compose file you use for the setup? maybe you could share it?
Vadim (Thu, 16 Feb 2017 08:59:51 GMT):
I'm building in vagrant
murrekatt (Thu, 16 Feb 2017 09:22:14 GMT):
same here, but how do you run things?
murrekatt (Thu, 16 Feb 2017 09:22:25 GMT):
after building
Vadim (Thu, 16 Feb 2017 09:24:10 GMT):
orderer: `ORDERER_GENERAL_LOGLEVEL=debug ./orderer`
peer: `peer node start --peer-defaultchain=false --logging-level=DEBUG`
create channel: `peer channel create -c mych -a anchor`
anchor:
`
127.0.0.1
7051
-----BEGIN CERTIFICATE-----
MIICjDCCAjKgAwIBAgIUBEVwsSx0TmqdbzNwleNBBzoIT0wwCgYIKoZIzj0EAwIw
fzELMAkGA1UEBhMCVVMxEzARBgNVBAgTCkNhbGlmb3JuaWExFjAUBgNVBAcTDVNh
biBGcmFuY2lzY28xHzAdBgNVBAoTFkludGVybmV0IFdpZGdldHMsIEluYy4xDDAK
BgNVBAsTA1dXVzEUMBIGA1UEAxMLZXhhbXBsZS5jb20wHhcNMTYxMTExMTcwNzAw
WhcNMTcxMTExMTcwNzAwWjBjMQswCQYDVQQGEwJVUzEXMBUGA1UECBMOTm9ydGgg
Q2Fyb2xpbmExEDAOBgNVBAcTB1JhbGVpZ2gxGzAZBgNVBAoTEkh5cGVybGVkZ2Vy
IEZhYnJpYzEMMAoGA1UECxMDQ09QMFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAE
HBuKsAO43hs4JGpFfiGMkB/xsILTsOvmN2WmwpsPHZNL6w8HWe3xCPQtdG/XJJvZ
+C756KEsUBM3yw5PTfku8qOBpzCBpDAOBgNVHQ8BAf8EBAMCBaAwHQYDVR0lBBYw
FAYIKwYBBQUHAwEGCCsGAQUFBwMCMAwGA1UdEwEB/wQCMAAwHQYDVR0OBBYEFOFC
dcUZ4es3ltiCgAVDoyLfVpPIMB8GA1UdIwQYMBaAFBdnQj2qnoI/xMUdn1vDmdG1
nEgQMCUGA1UdEQQeMByCCm15aG9zdC5jb22CDnd3dy5teWhvc3QuY29tMAoGCCqG
SM49BAMCA0gAMEUCIDf9Hbl4xn3z4EwNKmilM9lX2Fq4jWpAaRVB97OmVEeyAiEA
25aDPQHGGq2AvhKT0wvt08cX1GTGCIbfmuLpMwKQj38=
-----END CERTIFICATE-----
`
Vadim (Thu, 16 Feb 2017 09:24:10 GMT):
orderer: `ORDERER_GENERAL_LOGLEVEL=debug ./orderer`
peer: `peer node start --peer-defaultchain=false --logging-level=DEBUG`
create channel: `peer channel create -c mych -a anchor`
anchor:
```
127.0.0.1
7051
-----BEGIN CERTIFICATE-----
MIICjDCCAjKgAwIBAgIUBEVwsSx0TmqdbzNwleNBBzoIT0wwCgYIKoZIzj0EAwIw
fzELMAkGA1UEBhMCVVMxEzARBgNVBAgTCkNhbGlmb3JuaWExFjAUBgNVBAcTDVNh
biBGcmFuY2lzY28xHzAdBgNVBAoTFkludGVybmV0IFdpZGdldHMsIEluYy4xDDAK
BgNVBAsTA1dXVzEUMBIGA1UEAxMLZXhhbXBsZS5jb20wHhcNMTYxMTExMTcwNzAw
WhcNMTcxMTExMTcwNzAwWjBjMQswCQYDVQQGEwJVUzEXMBUGA1UECBMOTm9ydGgg
Q2Fyb2xpbmExEDAOBgNVBAcTB1JhbGVpZ2gxGzAZBgNVBAoTEkh5cGVybGVkZ2Vy
IEZhYnJpYzEMMAoGA1UECxMDQ09QMFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAE
HBuKsAO43hs4JGpFfiGMkB/xsILTsOvmN2WmwpsPHZNL6w8HWe3xCPQtdG/XJJvZ
+C756KEsUBM3yw5PTfku8qOBpzCBpDAOBgNVHQ8BAf8EBAMCBaAwHQYDVR0lBBYw
FAYIKwYBBQUHAwEGCCsGAQUFBwMCMAwGA1UdEwEB/wQCMAAwHQYDVR0OBBYEFOFC
dcUZ4es3ltiCgAVDoyLfVpPIMB8GA1UdIwQYMBaAFBdnQj2qnoI/xMUdn1vDmdG1
nEgQMCUGA1UdEQQeMByCCm15aG9zdC5jb22CDnd3dy5teWhvc3QuY29tMAoGCCqG
SM49BAMCA0gAMEUCIDf9Hbl4xn3z4EwNKmilM9lX2Fq4jWpAaRVB97OmVEeyAiEA
25aDPQHGGq2AvhKT0wvt08cX1GTGCIbfmuLpMwKQj38=
-----END CERTIFICATE-----
```
knagware9 (Thu, 16 Feb 2017 09:28:53 GMT):
Has joined the channel.
murrekatt (Thu, 16 Feb 2017 09:30:14 GMT):
i'll rebuild and test
Vadim (Thu, 16 Feb 2017 09:32:26 GMT):
which was the last working commit for you? I'm trying now 02322a1ff68b0238ae6a575372235835155b66a8, but there it crashes with "cannot deserialize creator identity" each time I try to query/invoke
Vadim (Thu, 16 Feb 2017 09:33:09 GMT):
actually it's more precisely "checkSignatureFromCreator -> INFO 603 checkSignatureFromCreator starts" and then it panics
murrekatt (Thu, 16 Feb 2017 09:34:12 GMT):
i have been on `2203c24ae4b0e88c35653bf0f5f1236348878051`
Vadim (Thu, 16 Feb 2017 09:42:25 GMT):
which node-sdk are you using? It seems that it does not provide the version, so proposal gets rejected
wutongtree (Thu, 16 Feb 2017 09:44:09 GMT):
Has joined the channel.
pd93 (Thu, 16 Feb 2017 10:13:36 GMT):
Anyone familiar with this error during chaincode deployment?
```
vp0 | 10:10:50.269 [dockercontroller] Start -> ERRO 036 start-could not start container API error (404): {"message":"network fabric_ not found"}
vp0 | 10:10:50.269 [chaincode] Launch -> ERRO 037 launchAndWaitForRegister failed Error starting container: API error (404): {"message":"network fabric_ not found"}
```
nickmelis (Thu, 16 Feb 2017 10:41:29 GMT):
is Hyperledger fabric considering any other DB alternative than simply key-value stores?
nickmelis (Thu, 16 Feb 2017 10:41:29 GMT):
is Hyperledger fabric considering any other DB alternative than simple key-value stores?
nickmelis (Thu, 16 Feb 2017 10:41:55 GMT):
i.e. a document oriented database?
nickmelis (Thu, 16 Feb 2017 10:45:06 GMT):
@Basug
> running 1.0 with couchdb, i can see the records, trying to see if couchdb does store all the history
Did you find an answer to that?
nickmelis (Thu, 16 Feb 2017 10:54:36 GMT):
as a general discussion, how do you bypass the limitations of a pure key-value store, especially when dealing with structured data and the need to query by range over composite keys?
murrekatt (Thu, 16 Feb 2017 10:55:50 GMT):
@nickmelis looking in the `peer/core.yml` you see mentions of both leveldb and couchdb...maybe someone can shed some light on these and the rocksdb key value store?
murrekatt (Thu, 16 Feb 2017 10:56:16 GMT):
@nickmelis current master which is v1.0
Vadim (Thu, 16 Feb 2017 10:58:12 GMT):
@murrekatt have you managed to create a channel by any chance?
nickmelis (Thu, 16 Feb 2017 10:58:45 GMT):
@murrekatt couchdb would be interesting, but does it mean we should go into the db straight for non trivial key-value query operations?
arvindupadhyaya (Thu, 16 Feb 2017 10:58:46 GMT):
Hi, i'm getting this error when I try to modify and deploy the example_cc.go file `error: [Peer.js]: GRPC client got an error response from the peer. Error: Failed to deploy chaincode spec(Error creating image: %!s(
nickmelis (Thu, 16 Feb 2017 10:59:07 GMT):
yes it would be definitely good for someone to shed some light on the matter
Vadim (Thu, 16 Feb 2017 11:00:00 GMT):
@arvindupadhyaya you have build errors in your chaincode, try to build it manually by gunning `go build`. You need to have chaincode and fabric in your GOPATH
Vadim (Thu, 16 Feb 2017 11:00:00 GMT):
@arvindupadhyaya you have build errors in your chaincode, try to build it manually by gunning `go build`. You need to have chaincode and fabric in your GOPATH for that.
murrekatt (Thu, 16 Feb 2017 11:00:09 GMT):
@Vadim building took long and ran into some issues as i usually use docker and not run directly in the vagrant dev env
murrekatt (Thu, 16 Feb 2017 11:00:12 GMT):
looking into it
Vadim (Thu, 16 Feb 2017 11:00:28 GMT):
ok, thanks for the update
murrekatt (Thu, 16 Feb 2017 11:00:49 GMT):
@Vadim will get back to you
Vadim (Thu, 16 Feb 2017 11:00:59 GMT):
thx
arvindupadhyaya (Thu, 16 Feb 2017 11:04:15 GMT):
@Vadim : I'll try that.. thanks
fabianpo (Thu, 16 Feb 2017 12:43:54 GMT):
Has joined the channel.
dave.enyeart (Thu, 16 Feb 2017 12:46:03 GMT):
@murrekatt @nickmelis To understand the leveldb/couchdb positioning, please review the ledger charts at : https://jira.hyperledger.org/browse/FAB-758
dave.enyeart (Thu, 16 Feb 2017 12:46:28 GMT):
Bring any questions to #fabric-ledger
dave.enyeart (Thu, 16 Feb 2017 12:47:35 GMT):
And see /fabric/examples/chaincode/go/marbles02 for various chaincode data patterns
murrekatt (Thu, 16 Feb 2017 12:48:26 GMT):
thanks @dave.enyeart
MadhavaReddy (Thu, 16 Feb 2017 13:16:32 GMT):
Hi All, did the v1.0 installation as per the instruction however when i try to deploy chaincode getting below error please help me to fix the issue
MadhavaReddy (Thu, 16 Feb 2017 13:16:33 GMT):
ubuntu@ip-20-0-4-192:~/work/hackfest$ GOPATH=$PWD node deploy.js
info: Returning a new winston logger with default configurations
info: [Chain.js]: Constructed Chain instance: name - fabric-client1, securityEnabled: true, TCert download batch size: 10, network mode: true
info: [Peer.js]: Peer.const - url: grpc://localhost:7051 options grpc.ssl_target_name_override=tlsca, grpc.default_authority=tlsca
info: [Peer.js]: Peer.const - url: grpc://localhost:8051 options grpc.ssl_target_name_override=tlsca, grpc.default_authority=tlsca
info: [Peer.js]: Peer.const - url: grpc://localhost:9051 options grpc.ssl_target_name_override=tlsca, grpc.default_authority=tlsca
events.js:160
throw er; // Unhandled 'error' event
^
Error: Connect Failed
at ClientDuplexStream._emitStatusIfDone (/home/ubuntu/work/hackfest/node_modules/grpc/src/node/src/client.js:201:19)
at ClientDuplexStream._readsDone (/home/ubuntu/work/hackfest/node_modules/grpc/src/node/src/client.js:169:8)
at readCallback (/home/ubuntu/work/hackfest/node_modules/grpc/src/node/src/client.js:242:12)
vigneswaran.r (Thu, 16 Feb 2017 14:08:58 GMT):
Hello.. In Fabric v0.6.1-preview, is there any way to execute some function inside the chaincode, at a specific date/time automatically? eg., in a share market usecase, can we do calculation and transfer of dividend at a specific day, time of every month/quarter etc? or should we need an external application to make this happen (by invoking some transaction)?
ecn (Thu, 16 Feb 2017 14:22:37 GMT):
Has joined the channel.
rrader (Thu, 16 Feb 2017 15:08:37 GMT):
Has joined the channel.
jansony1 (Thu, 16 Feb 2017 15:18:30 GMT):
hi fellows:
when i Fellow this doc(http://hyperledger-fabric.readthedocs.io/en/latest/dev-setup/build/) to build fabric v1. It return fellowing errors.
fabric git:(master) ✗ make dist-clean all
docker images -q hyperledger/fabric-peer | xargs -I '{}' docker rmi -f '{}'
docker images -q hyperledger/fabric-orderer | xargs -I '{}' docker rmi -f '{}'
docker images -q hyperledger/fabric-ccenv | xargs -I '{}' docker rmi -f '{}'
docker images -q hyperledger/fabric-javaenv | xargs -I '{}' docker rmi -f '{}'
docker images -q hyperledger/fabric-testenv | xargs -I '{}' docker rmi -f '{}'
docker images -q hyperledger/fabric-zookeeper | xargs -I '{}' docker rmi -f '{}'
docker images -q hyperledger/fabric-kafka | xargs -I '{}' docker rmi -f '{}'
cd gotools && /Applications/Xcode.app/Contents/Developer/usr/bin/make clean
make[1]: Entering directory '/opt/gopath/src/github.com/hyperledger/fabric/gotools'
Building github.com/golang/lint/golint -> golint
package golang.org/x/tools/go/gcexportdata: unrecognized import path "golang.org/x/tools/go/gcexportdata" (https fetch: Get https://golang.org/x/tools/go/gcexportdata?go-get=1: dial tcp 216.239.37.1:443: i/o timeout)
make[1]: *** [gotool.golint] Error 1
Makefile:47: recipe for target 'gotool.golint' failed
make[1]: Leaving directory '/opt/gopath/src/github.com/hyperledger/fabric/gotools'
make: *** [/opt/gotools/obj/gopath/bin/golint] Error 2
Makefile:52: recipe for target '/opt/gotools/obj/gopath/bin/golint' failed
make: *** [build/docker/gotools] Error 2
any idea?
rickr (Thu, 16 Feb 2017 15:37:11 GMT):
Hi
I was able in older builds just start the orderer with rm -rf /var/hyperledger/production;ORDERER_GENERAL_LOGLEVEL=debug build/bin/orderer
rickr (Thu, 16 Feb 2017 15:37:26 GMT):
from fabric directory
rickr (Thu, 16 Feb 2017 15:38:17 GMT):
```2017-02-16 10:37:37.706 EST [msp] getPemMaterialFromDir -> DEBU 005 Reading directory ../msp/cacerts
panic: Failed initializing crypto [Could not load a valid ca certificate from directory ../msp/cacerts, err Could not read directory open ../msp/cacerts: no such file or directory, err ../msp/cacerts]``
rickr (Thu, 16 Feb 2017 15:39:10 GMT):
```
$ find -name cacerts
./examples/sfhackfest/tmp/peer2/cacerts
./examples/sfhackfest/tmp/peer3/cacerts
./examples/sfhackfest/tmp/peer1/cacerts
./examples/sfhackfest/tmp/peer0/cacerts
./msp/sampleconfig/cacerts```
rickr (Thu, 16 Feb 2017 15:40:07 GMT):
so can someone recommend where I need to start this now ? I want to start up native running on linux
rickr (Thu, 16 Feb 2017 15:40:56 GMT):
is there a paramete to point to the cacerts ? is ./msp/sampleconfig/cacerts whats recommended ?
greg.haskins (Thu, 16 Feb 2017 15:43:00 GMT):
@rickr being burned by this: https://gerrit.hyperledger.org/r/#/c/6033/?
d8bhatta (Thu, 16 Feb 2017 15:46:21 GMT):
Has joined the channel.
jorgedr (Thu, 16 Feb 2017 15:48:40 GMT):
Has joined the channel.
rickr (Thu, 16 Feb 2017 15:51:12 GMT):
did that fix it or break it ?
rickr (Thu, 16 Feb 2017 15:51:31 GMT):
```[ fabric(master)]$ git log | grep 2239
Merge "[FAB-2239] Fix broken orderer image"
[FAB-2239] Fix broken orderer image
https://jira.hyperledger.org/browse/FAB-2239```
rickr (Thu, 16 Feb 2017 15:51:46 GMT):
I think I have that
jorgedr (Thu, 16 Feb 2017 15:52:17 GMT):
Hello there, new to Hyperledger and Fabric and I would like to take a look at how fabric 1.0 works. Are the examples listed under https://github.com/hyperledger/fabric/tree/master/examples current? Meaning are they updated to work with 1.0?
kostas (Thu, 16 Feb 2017 15:53:01 GMT):
@rickr This will help: https://gerrit.hyperledger.org/r/#/c/6075/
rickr (Thu, 16 Feb 2017 15:58:05 GMT):
@kostas Thx ! worked like a charm!
kostas (Thu, 16 Feb 2017 16:07:07 GMT):
[ ](https://chat.hyperledger.org/channel/fabric?msg=EeP8ZjHPeKdZkL79u) @rickr You're welcome. Credit goes to @jyellick for pushing the fix.
jyellick (Thu, 16 Feb 2017 16:08:59 GMT):
@rickr Yes, sorry for the regression, 6033 fixed the orderer docker image, but in turn broke the local execution, 6075 fixed the local execution, but note, `orderer` must now be executed from the `fabric/` root
tiennv (Thu, 16 Feb 2017 16:16:34 GMT):
Has joined the channel.
TinStribor (Thu, 16 Feb 2017 16:16:42 GMT):
Has joined the channel.
MadhavaReddy (Thu, 16 Feb 2017 16:17:33 GMT):
Hi, what would happen when application sdk submit a proposal and if two peers send different response to sdk? consider chain code on one of the peer has been changed, please clarify
alviontaran (Thu, 16 Feb 2017 16:17:52 GMT):
Has joined the channel.
rickr (Thu, 16 Feb 2017 16:23:45 GMT):
I've always run it from fabric root .. thx Jason
farhan3 (Thu, 16 Feb 2017 16:40:20 GMT):
Has joined the channel.
farhan3 (Thu, 16 Feb 2017 16:41:21 GMT):
Hi - in v1.0, does chaincode need to run in a container or can it run as a process?
farhan3 (Thu, 16 Feb 2017 16:44:37 GMT):
More specifically in "production". What is expected, container or process?
oiakovlev (Thu, 16 Feb 2017 16:52:35 GMT):
Hi, re-asking question about Bluemix:
If we want to restrict access to the peer url some how would it be possible with Bluemix via VPN setup for example? If so, I have not found such option in Bluemix dashboard - should it be separate request to Bluemix support?
greg.haskins (Thu, 16 Feb 2017 17:19:29 GMT):
@jyellick @kostas we should chat about the config stuff
greg.haskins (Thu, 16 Feb 2017 17:19:44 GMT):
not sure you saw the comments I made in 6033(??)
greg.haskins (Thu, 16 Feb 2017 17:19:50 GMT):
not sure which it was, actually
kostas (Thu, 16 Feb 2017 17:19:51 GMT):
Yes please, I'd love to hear what you have in mind.
kostas (Thu, 16 Feb 2017 17:19:57 GMT):
I did, and commented on that.
greg.haskins (Thu, 16 Feb 2017 17:20:00 GMT):
but anyway, we have to get away from assuming fabric
greg.haskins (Thu, 16 Feb 2017 17:20:07 GMT):
ok, ill look
greg.haskins (Thu, 16 Feb 2017 18:06:52 GMT):
@kostas @jyellick @muralisr added more comments: https://jira.hyperledger.org/browse/FAB-2037
greg.haskins (Thu, 16 Feb 2017 18:07:07 GMT):
please add to the thread as you see fit
kostas (Thu, 16 Feb 2017 18:20:37 GMT):
@greg.haskins: (Left a comment.)
kelly_ (Thu, 16 Feb 2017 18:44:38 GMT):
Has joined the channel.
marcusvcs (Thu, 16 Feb 2017 18:46:01 GMT):
can someone explain to me what is the meaning of CORE_SECURITY_ENABLED and CORE_SECURITY_PRIVACY in 0.6? Is it about the use of TCerts from the membership service?
kostas (Thu, 16 Feb 2017 19:44:36 GMT):
@jyellick: Still on catch-up mode, working my way through the `configtx` package. This comment here gives me pause: https://github.com/hyperledger/fabric/blob/master/common/configtx/template.go#L156
Here are two claims:
1. I can have a `CompositeTemplate` without a `CreationPolicy` defined.
2. Then, I can use the result of `ChainCreationTemplate` and combine with the result of 1, and come up with a new `CompositeTemplate` that does not have its CreationPolicy invalidated (because it doesn't have one).
jyellick (Thu, 16 Feb 2017 19:45:27 GMT):
That comment used to be true, but is no longer
jyellick (Thu, 16 Feb 2017 19:45:39 GMT):
The CreationPolicy used to include a computed digest over the rest of the config
jyellick (Thu, 16 Feb 2017 19:45:53 GMT):
So, modifying the set of config would invalidate the digest computation
jyellick (Thu, 16 Feb 2017 19:46:01 GMT):
It should be removed
greg.haskins (Thu, 16 Feb 2017 20:01:08 GMT):
@chrism28 so you are having an issue where your chaincode isnt compiling but you cant see the errors?
chrism28 (Thu, 16 Feb 2017 20:01:08 GMT):
Has joined the channel.
kostas (Thu, 16 Feb 2017 20:01:49 GMT):
[ ](https://chat.hyperledger.org/channel/fabric?msg=NZPJgJCEM5kpuwCZG) @jyellick https://gerrit.hyperledger.org/r/#/c/6107/1
chrism28 (Thu, 16 Feb 2017 20:21:35 GMT):
@greg.haskins That's correct. I've tried deploying via both node-sdk and the CLI and all I see are the following errors (repeated 3 times - presumably once for each endorser)
```
error: [Peer.js]: GRPC client got an error response from the peer. Error: Failed to deploy chaincode spec(Error creating image: %!s(
greg.haskins (Thu, 16 Feb 2017 20:22:21 GMT):
@chrism28 can you show the peer log?
kostas (Thu, 16 Feb 2017 20:22:42 GMT):
Am I correct to assume that the code that generates the `./genesisblock` referenced [here](https://github.com/hyperledger/fabric/blob/master/orderer/orderer.yaml#L53), is located in `fabric/peer/channel/create.go`?
kostas (Thu, 16 Feb 2017 20:24:17 GMT):
Also, as a follow up to [the above](https://chat.hyperledger.org/channel/fabric?msg=gqGxhMKggN2GHPehZ), and to make sure I'm not inventing extra steps, how would one go about generating the `genesisblock` file in the least amount of steps possible?
chrism28 (Thu, 16 Feb 2017 20:24:21 GMT):
@greg.haskins Sorry but I don't know where the peer log is. I presume it's inside the peer docker container - but I don't really know where to look...
greg.haskins (Thu, 16 Feb 2017 20:24:42 GMT):
@chrism28 how are you launching it?
greg.haskins (Thu, 16 Feb 2017 20:24:48 GMT):
(the peer, I mean)
chrism28 (Thu, 16 Feb 2017 20:27:30 GMT):
@greg.haskins I'm following the Getting Started guide here: `https://hyperledger-fabric.readthedocs.io/en/latest/gettingstarted/` which uses docker-compose - up.
greg.haskins (Thu, 16 Feb 2017 20:37:25 GMT):
@chrism28 ok, i hadnt used the getting started before, so I had to pull it down to get my bearings
greg.haskins (Thu, 16 Feb 2017 20:37:35 GMT):
but I think the command you generally want is "docker-compose logs"
greg.haskins (Thu, 16 Feb 2017 20:37:37 GMT):
docker-compose -f docker-compose-gettingstarted.yml logs peer0
greg.haskins (Thu, 16 Feb 2017 20:37:45 GMT):
for example, that shows me the log running on peer0
greg.haskins (Thu, 16 Feb 2017 20:38:02 GMT):
note that the getting started environment has three peers (peer[012]
greg.haskins (Thu, 16 Feb 2017 20:38:20 GMT):
so you might need to poke around if you dont see the log
greg.haskins (Thu, 16 Feb 2017 20:38:40 GMT):
(in theory all three should have it, but since something is failing and its unreleased software, you never know)
greg.haskins (Thu, 16 Feb 2017 20:41:01 GMT):
anyway, I believe the docker-build output should end up in the peer log
nickgaski (Thu, 16 Feb 2017 20:45:22 GMT):
hi @chrism28 can you make sure that your channel was successfully created and that your peers have joined
nickgaski (Thu, 16 Feb 2017 20:45:30 GMT):
`docker exec -it cli bash`
nickgaski (Thu, 16 Feb 2017 20:45:40 GMT):
`more results.txt`
chrism28 (Thu, 16 Feb 2017 20:45:52 GMT):
@greg.haskins Excellent. Thank you so much for your help. The compile errors are indeed sitting there in the log. This is exactly what I was looking for. Many thanks.
chrism28 (Thu, 16 Feb 2017 20:47:46 GMT):
@nickgaski Thanks for the input. Yes everything else is up and running I was just trying to figure out how to view compilation errors and chaincode debug print statements
nickgaski (Thu, 16 Feb 2017 20:48:37 GMT):
sweet. does the CLI deploy still fail?
greg.haskins (Thu, 16 Feb 2017 20:52:52 GMT):
@chrism28 vw
chrism28 (Thu, 16 Feb 2017 20:53:59 GMT):
@nickgaski Well... that's another story... It seems my docker containers degrade slowly to the point that I have to completely rebuild them. So, I start fresh by deleting all my docker images and rebuilding them all. At that point I can deploy using both CLI and node-sdk. After some time (and probably because of my multiple failed deployment attempts) I start to receive "MSP DEFAULT is unknown" errors from the peers when I try to deploy via CLI and/or the node-sdk. When this happens I need to delete and rebuild the images.
nickgaski (Thu, 16 Feb 2017 20:55:51 GMT):
well that's a first. @greg.haskins @rameshthoomu - have you come across this behavior before. Are the containers overburdened somehow?
greg.haskins (Thu, 16 Feb 2017 20:56:56 GMT):
@nickgaski no, but if I had to guess its something to do with /var/hyperledger persistence
greg.haskins (Thu, 16 Feb 2017 20:57:45 GMT):
one thing that could be done is volume mount /var/hyperledger and then experiment
chrism28 (Thu, 16 Feb 2017 21:00:24 GMT):
@nickgaski Oh the other thing I had to do to make the CLI deploy work was to use ip addresses instead of the node names. eg. Instead of `CORE_PEER_ADDRESS=peer0:7051` I have to use `CORE_PEER_ADDRESS=172.19.0.3:7051`. Probably my network issues though?
nickgaski (Thu, 16 Feb 2017 21:01:30 GMT):
ugh. yea we've seen some repeated behavior of the peer and client being unable to resolve with orderer
nickgaski (Thu, 16 Feb 2017 21:01:44 GMT):
you hard coded the orderer as well, I presume?
chrism28 (Thu, 16 Feb 2017 21:02:07 GMT):
@nickgaski Yep
nickgaski (Thu, 16 Feb 2017 21:02:38 GMT):
this thing should stabilize in the next few days. still a lot of moving pieces with the code base
chrism28 (Thu, 16 Feb 2017 21:04:16 GMT):
I can work around these little issues - the main thing was to be able to view the peer log. Now I can happily move forward. Thanks for all your help...
vu3mmg (Fri, 17 Feb 2017 00:53:29 GMT):
DO we need to give chain code path when we depoly the chain code , (http://hyperledger-fabric.readthedocs.io/en/v0.6/Setup/Chaincode-setup/ )
vu3mmg (Fri, 17 Feb 2017 00:53:34 GMT):
i am getting an error
vu3mmg (Fri, 17 Feb 2017 00:53:41 GMT):
Invalid params","data":"Chaincode path may not be blank."},"id":1}
vu3mmg (Fri, 17 Feb 2017 00:53:46 GMT):
any hints
vu3mmg (Fri, 17 Feb 2017 00:54:01 GMT):
i think earlier i was able to run the examples successfully
vu3mmg (Fri, 17 Feb 2017 01:53:57 GMT):
I am getting following error when i tried to query the deployed chain code
vu3mmg (Fri, 17 Feb 2017 01:53:58 GMT):
"Error when querying chaincode: Error:Failed to launch chaincode spec
vu3mmg (Fri, 17 Feb 2017 01:54:21 GMT):
the deploy rest api and invoke rest api returns success
vu3mmg (Fri, 17 Feb 2017 01:54:27 GMT):
any hits
vu3mmg (Fri, 17 Feb 2017 01:54:29 GMT):
hints
vu3mmg (Fri, 17 Feb 2017 01:54:31 GMT):
?
baohua (Fri, 17 Feb 2017 02:02:15 GMT):
Welcome to help give comments on this jira task (update those cfg variables): https://jira.hyperledger.org/browse/FAB-2118, thanks!
yong (Fri, 17 Feb 2017 02:03:40 GMT):
Has joined the channel.
zhangzhen (Fri, 17 Feb 2017 02:34:16 GMT):
Has joined the channel.
yong (Fri, 17 Feb 2017 03:35:36 GMT):
Hi, I build Fabric.## License
The Hyperledger Project uses the [Apache License Version 2.0](LICENSE) software
license.
[root@bogon fabric]# make dist-clean all
docker images -q hyperledger/fabric-peer | xargs -I '{}' docker rmi -f '{}'
docker images -q hyperledger/fabric-orderer | xargs -I '{}' docker rmi -f '{}'
docker images -q hyperledger/fabric-ccenv | xargs -I '{}' docker rmi -f '{}'
docker images -q hyperledger/fabric-javaenv | xargs -I '{}' docker rmi -f '{}'
docker images -q hyperledger/fabric-buildenv | xargs -I '{}' docker rmi -f '{}'
docker images -q hyperledger/fabric-testenv | xargs -I '{}' docker rmi -f '{}'
docker images -q hyperledger/fabric-zookeeper | xargs -I '{}' docker rmi -f '{}'
docker images -q hyperledger/fabric-kafka | xargs -I '{}' docker rmi -f '{}'
cd gotools && make clean
make[1]: Entering directory '/home/yong/go/src/github.com/hyperledger/fabric/gotools'
make[1]: Leaving directory '/home/yong/go/src/github.com/hyperledger/fabric/gotools'
make: stat: Makefile: Permission denied
make: *** No rule to make target 'install'. Stop.
Makefile:153: recipe for target 'build/docker/gotools' failed
make: *** [build/docker/gotools] Error 2
## License
The Hyperledger Project uses the [Apache License Version 2.0](LICENSE) software
license.
[root@bogon fabric]# make dist-clean all
docker images -q hyperledger/fabric-peer | xargs -I '{}' docker rmi -f '{}'
docker images -q hyperledger/fabric-orderer | xargs -I '{}' docker rmi -f '{}'
docker images -q hyperledger/fabric-ccenv | xargs -I '{}' docker rmi -f '{}'
docker images -q hyperledger/fabric-javaenv | xargs -I '{}' docker rmi -f '{}'
docker images -q hyperledger/fabric-buildenv | xargs -I '{}' docker rmi -f '{}'
docker images -q hyperledger/fabric-testenv | xargs -I '{}' docker rmi -f '{}'
docker images -q hyperledger/fabric-zookeeper | xargs -I '{}' docker rmi -f '{}'
docker images -q hyperledger/fabric-kafka | xargs -I '{}' docker rmi -f '{}'
cd gotools && make clean
make[1]: Entering directory '/home/yong/go/src/github.com/hyperledger/fabric/gotools'
make[1]: Leaving directory '/home/yong/go/src/github.com/hyperledger/fabric/gotools'
make: stat: Makefile: Permission denied
make: *** No rule to make target 'install'. Stop.
Makefile:153: recipe for target 'build/docker/gotools' failed
make: *** [build/docker/gotools] Error 2
## License
The Hyperledger Project uses the [Apache License Version 2.0](LICENSE) software
license.
[root@bogon fabric]# make dist-clean all
docker images -q hyperledger/fabric-peer | xargs -I '{}' docker rmi -f '{}'
docker images -q hyperledger/fabric-orderer | xargs -I '{}' docker rmi -f '{}'
docker images -q hyperledger/fabric-ccenv | xargs -I '{}' docker rmi -f '{}'
docker images -q hyperledger/fabric-javaenv | xargs -I '{}' docker rmi -f '{}'
docker images -q hyperledger/fabric-buildenv | xargs -I '{}' docker rmi -f '{}'
docker images -q hyperledger/fabric-testenv | xargs -I '{}' docker rmi -f '{}'
docker images -q hyperledger/fabric-zookeeper | xargs -I '{}' docker rmi -f '{}'
docker images -q hyperledger/fabric-kafka | xargs -I '{}' docker rmi -f '{}'
cd gotools && make clean
make[1]: Entering directory '/home/yong/go/src/github.com/hyperledger/fabric/gotools'
make[1]: Leaving directory '/home/yong/go/src/github.com/hyperledger/fabric/gotools'
make: stat: Makefile: Permission denied
make: *** No rule to make target 'install'. Stop.
Makefile:153: recipe for target 'build/docker/gotools' failed
make: *** [build/docker/gotools] Error 2
yong (Fri, 17 Feb 2017 03:36:28 GMT):
how to resolve?
RajkumarNatarajan (Fri, 17 Feb 2017 03:54:51 GMT):
Has joined the channel.
matanyahu (Fri, 17 Feb 2017 08:44:36 GMT):
hi, I would like to know how to query ledger history at a given point of time
matanyahu (Fri, 17 Feb 2017 08:45:31 GMT):
let's say, we are at block 3
matanyahu (Fri, 17 Feb 2017 08:45:40 GMT):
and a transaction took place in block 1 and 2
matanyahu (Fri, 17 Feb 2017 08:45:54 GMT):
I would like to know what the balance of a given account was in block 1
matanyahu (Fri, 17 Feb 2017 08:46:00 GMT):
instead of querying world state
o.o. (Fri, 17 Feb 2017 09:08:20 GMT):
I could not find any information in the latest (v1,0 current) documentation about the CAs. I remember there being a description of them in v0.6. Has this documentation been moved, or has the approach changed, or have the docs simply not been updated yet?
levinkwong (Fri, 17 Feb 2017 09:10:09 GMT):
https://docs.google.com/document/d/1Qg7ZEccOIsrShSHSNl4kBHOFvLYRhQ3903srJ6c_AZE/edit
fabric-ca, is this what you want?
o.o. (Fri, 17 Feb 2017 09:17:18 GMT):
Had completely missed that document! Thanks levinkwong!
levinkwong (Fri, 17 Feb 2017 09:19:13 GMT):
@o.o. You may want this too : https://wiki.hyperledger.org/community/fabric-design-docs
ecn (Fri, 17 Feb 2017 09:43:53 GMT):
Hello,
ecn (Fri, 17 Feb 2017 09:46:57 GMT):
Hello, does someone knows how to invoke a chaincode with attributes using HFC ? (I can do it with the command peer chaincode invoke -a ["role"] ...).
I would like to do something like this;
var invokeRequest = {
chaincodeID: chaincodeName,
fcn: "invoke",
args: ["arg1","arg2"],
attributes: ["role"]
};
// Invoke request
var tx = user.invoke(invokeRequest);
nickmelis (Fri, 17 Feb 2017 10:10:20 GMT):
do we have a date for v1.0 release?
wwendy (Fri, 17 Feb 2017 10:35:00 GMT):
Has joined the channel.
waterhole (Fri, 17 Feb 2017 10:45:45 GMT):
Has joined the channel.
waterhole (Fri, 17 Feb 2017 10:47:25 GMT):
are there anybody successfully build v 1.0 and explorer?
Vadim (Fri, 17 Feb 2017 10:49:18 GMT):
I can build v1 on Vagrant
waterhole (Fri, 17 Feb 2017 10:51:29 GMT):
@Vadim can you deploy multiple nodes? or only single node, is the blockchain explorer working?
Vadim (Fri, 17 Feb 2017 10:51:51 GMT):
I did not try blockchain explorer
Vadim (Fri, 17 Feb 2017 10:52:23 GMT):
I am working with one node (developing something), but I don't see why I could not use several nodes
waterhole (Fri, 17 Feb 2017 10:53:45 GMT):
I am also having no issues with single node, but multiple nodes not working. 0.6 is fully working though
Vadim (Fri, 17 Feb 2017 10:54:16 GMT):
what error do you get?
ucwong (Fri, 17 Feb 2017 10:57:39 GMT):
Has joined the channel.
ucwong (Fri, 17 Feb 2017 11:01:53 GMT):
sending init failed(handler not found for chaincode mycc)
ucwong (Fri, 17 Feb 2017 11:04:57 GMT):
one node is ok, query failed when running more nodes
Oleksbor (Fri, 17 Feb 2017 11:41:01 GMT):
Has joined the channel.
Jonas.Hedin (Fri, 17 Feb 2017 12:13:59 GMT):
Is there some guide or example on how to use MSPs?
yacovm (Fri, 17 Feb 2017 14:13:43 GMT):
Ask in #fabric-crypto but what di you mean by use them? They are infrastructure
Jonas.Hedin (Fri, 17 Feb 2017 14:25:19 GMT):
I would like to restrict usage of the my chaincode to certain users, for example only the user that added an entry should be able to change it. I am kind of lost in the documentation on how to achieve this.
Vadim (Fri, 17 Feb 2017 14:25:58 GMT):
I think this should be a part of a chaincode logic
Jonas.Hedin (Fri, 17 Feb 2017 14:27:32 GMT):
aah, I thought you could use certificates for this
Vadim (Fri, 17 Feb 2017 14:27:59 GMT):
you do
Vadim (Fri, 17 Feb 2017 14:28:24 GMT):
I'm talking about "only the user that added an entry should be able to change it"
Vadim (Fri, 17 Feb 2017 14:29:41 GMT):
so for example, somebody adds entry, you get his certificate and store it along with the entry, then when somebody wants to change it, so you compare the stored certificate with the caller certificate
Jonas.Hedin (Fri, 17 Feb 2017 14:32:59 GMT):
ok thanks. Follow-up question: Is there some way to simulate multiple users from a single CLI? Could you say " I would like to use this certificate for this invoke but another for that invoke"?
Vadim (Fri, 17 Feb 2017 14:33:32 GMT):
I'm not using cli, so don't know.
Vadim (Fri, 17 Feb 2017 14:33:32 GMT):
I'm not using cli, so I don't know.
Jonas.Hedin (Fri, 17 Feb 2017 14:33:59 GMT):
Thanks anyway :)
Honglei (Fri, 17 Feb 2017 15:36:04 GMT):
Hi, we're implementing fabric supporting on javascript-chaincode. I created FAB-2331. 2 questions: Should jira be reviewed firstly? During implementation, we used otto as js-interpreter (https://github.com/robertkrimen/otto). Adding otto to fabric github.com/vendor is OK?
Vadim (Fri, 17 Feb 2017 15:37:18 GMT):
I think you should check https://fabric-composer.github.io/ , they used the same principle
Honglei (Fri, 17 Feb 2017 15:39:05 GMT):
But I didn't seem code changes on fabric/master. They will commit their changes?
Vadim (Fri, 17 Feb 2017 15:39:38 GMT):
it's a project on top of fabric, hosted on different repository
Vadim (Fri, 17 Feb 2017 15:39:57 GMT):
https://github.com/fabric-composer
farhan3 (Fri, 17 Feb 2017 15:40:44 GMT):
Hi - quick question. For the peer yaml file, I can see that the state is stored in a database, e.g. CouchDB. Is the ledger also stored in the same database?
farhan3 (Fri, 17 Feb 2017 15:40:44 GMT):
Hi - quick question. From the peer yaml file, I can see that the state is stored in a database, e.g. CouchDB. Is the ledger also stored in the same database?
Honglei (Fri, 17 Feb 2017 15:43:31 GMT):
@Vadim It seems a node application. I'd like to know how farbic execute the javascript chaincode created by composer.
Vadim (Fri, 17 Feb 2017 15:44:51 GMT):
it's not just a node application, it has a chaincode which is a javascript runtime which gets deployed onto fabric and your javascript business logic are executed within it
Vadim (Fri, 17 Feb 2017 15:45:46 GMT):
I recommend you to read the overview: https://fabric-composer.github.io/overview/overview.html
Honglei (Fri, 17 Feb 2017 15:45:50 GMT):
OK. So farbic will deploy a docker with node, to execute the chaincode .
Vadim (Fri, 17 Feb 2017 15:46:38 GMT):
node is just to provide interface
Vadim (Fri, 17 Feb 2017 15:46:48 GMT):
chaincode runtime is written in golang
Vadim (Fri, 17 Feb 2017 15:48:21 GMT):
here is the runtime itself: https://github.com/fabric-composer/fabric-composer/tree/master/packages/composer-runtime-hlf
Honglei (Fri, 17 Feb 2017 15:49:24 GMT):
Thanks. It seems otto too.
rcampos@altus.cr (Fri, 17 Feb 2017 15:55:33 GMT):
Has joined the channel.
mwall (Fri, 17 Feb 2017 16:54:05 GMT):
Hello! How can I handle this `panic: Own checkpoint for seqNo 30 (CAsSQIpPFvKebFWy+m2TAdP7aTd81EC3AJo6sSU5TgG4xq3+bH74yJxkYDZzHQmQEpyl9hTrtl6Uqa004oFNTZtFG0AaQMcwvg2v92PjvmzVXH3KoPBNvGnPJAeBbivC6EKWSWQIVfTcJUAf1v+AkBxX77MQetWpLWTvx7riohEPPuhOOHk=) different from weak checkpoint certificate (CAsSQAlFXxAlQbHSQicJBptYJQTa2pgfTRuP5cPMbPY8hmNAlIMDj9kRgouWRddx7AAryuf92OD4QoC/gAxnlsxnx+MaQOYL4z+XcjXGbTCxcmAcd2XPFOK1sQHDTm1FJinLjmIeWEt+xlTspwUXhUGrG5AhzmXBsW39rDBqmouHoYfg84o=)`?
kostas (Fri, 17 Feb 2017 16:55:51 GMT):
@mwall: Sounds like something that has gone wrong. Running on your own chaincode, or one of the standard ones?
mwall (Fri, 17 Feb 2017 16:56:07 GMT):
@kostas Running my own
kostas (Fri, 17 Feb 2017 16:56:26 GMT):
You are running non-deterministic chaincode.
kostas (Fri, 17 Feb 2017 16:56:41 GMT):
Your chaincode generates results that are not identical across all peers.
kostas (Fri, 17 Feb 2017 16:56:47 GMT):
So the state divergences.
kostas (Fri, 17 Feb 2017 16:56:47 GMT):
So the state diverges.
kostas (Fri, 17 Feb 2017 16:56:56 GMT):
This is what this error message tells you.
aparwatkar (Fri, 17 Feb 2017 16:59:07 GMT):
Has joined the channel.
mwall (Fri, 17 Feb 2017 17:03:19 GMT):
Message Attachments
mwall (Fri, 17 Feb 2017 17:03:50 GMT):
Can you help me, is var id a mistake?
mwall (Fri, 17 Feb 2017 17:05:32 GMT):
I'm sending messages with 500ms delay to all 4 peers concurrently
kostas (Fri, 17 Feb 2017 17:16:11 GMT):
Interesting, I had a quick look and nothing jumps out at me.
nandinirao (Fri, 17 Feb 2017 17:34:18 GMT):
Has joined the channel.
mcoblenz (Fri, 17 Feb 2017 18:04:41 GMT):
I see there's no planned support in 1.0 for cross-chaincode transactions. Is there someone I can chat with about that? I'm interested in learning more about the context there.
kostas (Fri, 17 Feb 2017 18:23:28 GMT):
@greg.haskins: Can you think of a good reason as to why we create both a `$PEER_CFG_PATH$ and a `$ORDERER_CFG_PATH$` directory here? https://github.com/hyperledger/fabric/blob/master/images/testenv/Dockerfile.in#L10
kostas (Fri, 17 Feb 2017 18:23:28 GMT):
@greg.haskins: Can you think of a good reason as to why we create both a `$PEER_CFG_PATH$` and a `$ORDERER_CFG_PATH$` directory here? https://github.com/hyperledger/fabric/blob/master/images/testenv/Dockerfile.in#L10
kostas (Fri, 17 Feb 2017 18:23:51 GMT):
They're identical, right?
greg.haskins (Fri, 17 Feb 2017 18:24:20 GMT):
well, each program is included in that image, and each program has its own namespace, so thats the basic reason
greg.haskins (Fri, 17 Feb 2017 18:24:35 GMT):
but I assume you knew that and are asking whether we can combine them somehow?
kostas (Fri, 17 Feb 2017 18:26:55 GMT):
You are saying that a program may overwrite, say, the $ORDERER_CFG_PATH$ ENV var, and this is why `mkdir` command needs to reference both PATHs even though they are identical? (https://github.com/hyperledger/fabric/blob/master/images/testenv/Dockerfile.in#L4)
kostas (Fri, 17 Feb 2017 18:26:55 GMT):
You are saying that a program may overwrite, say, the $ORDERER_CFG_PATH$ ENV var, and this is why the `mkdir` command needs to reference both PATHs even though they are identical? (https://github.com/hyperledger/fabric/blob/master/images/testenv/Dockerfile.in#L4)
kostas (Fri, 17 Feb 2017 18:28:45 GMT):
I am still not sure what's the use of `mkdir -p $PEER_CFG_PATH $ORDERER_CFG_PATH` when that file sets them to the same value. That's what I'm commenting on I guess.
greg.haskins (Fri, 17 Feb 2017 18:52:43 GMT):
ah, i understand what you are saying now
greg.haskins (Fri, 17 Feb 2017 18:52:53 GMT):
i think at one point they were different and thus the mkdir
greg.haskins (Fri, 17 Feb 2017 18:52:59 GMT):
that can be cleaned up, sure
greg.haskins (Fri, 17 Feb 2017 18:53:34 GMT):
I thought you were asking why we define both variables
greg.haskins (Fri, 17 Feb 2017 18:53:40 GMT):
but yes, I agree, the mkdir is redundant
kostas (Fri, 17 Feb 2017 18:53:48 GMT):
Right.
gregnotso (Fri, 17 Feb 2017 18:54:00 GMT):
is chaincode 'roughly' an equivalent of Bitcoin Core? i know they are not the same, but they should have something in common, shouldn't they?
kostas (Fri, 17 Feb 2017 18:54:02 GMT):
I guess for the `mkdir` call I can go with either.
kostas (Fri, 17 Feb 2017 18:54:21 GMT):
Thanks @greg.haskins, I'll push a quick fix now.
kostas (Fri, 17 Feb 2017 18:59:24 GMT):
https://gerrit.hyperledger.org/r/#/c/6175/
firas.qutishat (Fri, 17 Feb 2017 19:37:06 GMT):
Has joined the channel.
muralisr (Fri, 17 Feb 2017 20:16:33 GMT):
with https://gerrit.hyperledger.org/r/#/c/6161 end-to-end tests work (channel create/join, chaincode install/instantiate/invoke/query)
muralisr (Fri, 17 Feb 2017 20:17:28 GMT):
@kostas reviewed and +2ed
conroydave (Sat, 18 Feb 2017 07:19:37 GMT):
hello everyone
conroydave (Sat, 18 Feb 2017 07:20:05 GMT):
have not dug into the logs yet, but ive noticed that v2-typescript of the boilerplate runs fine on linux
conroydave (Sat, 18 Feb 2017 07:20:16 GMT):
but on Mac the demo fails
conroydave (Sat, 18 Feb 2017 07:20:41 GMT):
im guessing it is because docker on mac is really a VM where on linux it is more on local host
conroydave (Sat, 18 Feb 2017 07:21:39 GMT):
anyone available to help me dig through the v2-typescript and find where it could be broken?
conroydave (Sat, 18 Feb 2017 07:33:07 GMT):
in v1 it took a change to chaincodeconfig.js
conroydave (Sat, 18 Feb 2017 07:33:26 GMT):
theres gotta be other fan boy idlers in this channel
xbee (Sat, 18 Feb 2017 10:42:39 GMT):
Has joined the channel.
rrader (Sat, 18 Feb 2017 10:56:33 GMT):
I want to build a mobile application, as I understand blockchain is saved in hyperledger, but how integrity of blockchain is achieved?
rrader (Sat, 18 Feb 2017 10:56:46 GMT):
I need to copy the blockchain into every mobile application, and when someone create new ledger to compare wil all the mobile applications blockchains?
conroydave (Sat, 18 Feb 2017 10:59:37 GMT):
with hyperledger you will have private blockchains
conroydave (Sat, 18 Feb 2017 11:00:13 GMT):
itll run in the cloud or on your servers
conroydave (Sat, 18 Feb 2017 11:00:35 GMT):
but , if written well bringing new nodes or participants online will be trivial
rrader (Sat, 18 Feb 2017 11:03:36 GMT):
can you please provide some articles/sources how to make public blockchain?
conroydave (Sat, 18 Feb 2017 11:05:00 GMT):
are you more interested in building your own network or do you have a business need for a blockchain backend
rrader (Sat, 18 Feb 2017 11:07:15 GMT):
I am trying to build a voting app
andyz (Sat, 18 Feb 2017 11:29:38 GMT):
Has joined the channel.
conroydave (Sat, 18 Feb 2017 12:06:56 GMT):
check out the boiler plate app
conroydave (Sat, 18 Feb 2017 12:07:41 GMT):
https://github.com/IBM-Blockchain/fabric-boilerplate
jsong1230 (Sat, 18 Feb 2017 12:44:23 GMT):
Has joined the channel.
cdaughtr (Sat, 18 Feb 2017 16:58:09 GMT):
@jyellick With today's fabric at commit 'Removing security section from core.yaml', the orderer will not run. I tried adding the env variables it mentioned with no luck:
2017-02-18 15:21:57.597 UTC [configtx/tool/localconfig] Load -> INFO 012 Checking for genesis.yaml at: /etc/hyperledger/fabric
2017-02-18 15:21:57.597 UTC [configtx/tool/localconfig] Load -> INFO 013 Checking for genesis.yaml at: /etc/hyperledger/fabric
2017-02-18 15:21:57.597 UTC [configtx/tool/localconfig] Load -> INFO 014 Checking for genesis.yaml at: /opt/gopath/src/github.com/hyperledger/fabric/common/configtx/tool
2017-02-18 15:21:57.597 UTC [configtx/tool/localconfig] Load -> CRIT 015 Could not find genesis.yaml in paths of [/etc/hyperledger/fabric /etc/hyperledger/fabric /opt/gopath/src/github.com/hyperledger/fabric/common/configtx/tool]. Try setting ORDERER_CFG_PATH, PEER_CFG_PATH, or GOPATH correctly
jyellick (Sat, 18 Feb 2017 16:58:41 GMT):
How are you starting the orderer?
jyellick (Sat, 18 Feb 2017 16:59:29 GMT):
(And can you verify that `genesis.yaml` is at one of those locations?
jyellick (Sat, 18 Feb 2017 16:59:29 GMT):
(And can you verify that `genesis.yaml` is at one of those locations?) @cdaughtr
jyellick (Sat, 18 Feb 2017 17:16:01 GMT):
@cdaughtr
Looks like commit 60ecaf1caf5b8e13170c0c95c2ab41d8a87a3d26 reverted the fix that went in with cef0aa3283d9aeb3ec188ae32e185da9f344a289 for some reason.
```
[yellickj@jmobile fabric]$ git diff cef0aa3283d9aeb3ec188ae32e185da9f344a289..60ecaf1caf5b8e13170c0c95c2ab41d8a87a3d26 -- ./images/orderer/Dockerfile.in
diff --git a/images/orderer/Dockerfile.in b/images/orderer/Dockerfile.in
index 5e539e01..60c4b9bf 100644
--- a/images/orderer/Dockerfile.in
+++ b/images/orderer/Dockerfile.in
@@ -3,7 +3,6 @@ ENV ORDERER_CFG_PATH /etc/hyperledger/fabric
ENV ORDERER_GENERAL_LOCALMSPDIR $ORDERER_CFG_PATH/msp/sampleconfig
RUN mkdir -p /var/hyperledger/production $ORDERER_CFG_PATH
COPY payload/orderer /usr/local/bin
-COPY payload/genesis.yaml $ORDERER_CFG_PATH/
COPY payload/orderer.yaml $ORDERER_CFG_PATH/
ADD payload/msp-sampleconfig.tar.bz2 $ORDERER_CFG_PATH/
EXPOSE 7050
[yellickj@jmobile fabric]$
```
jyellick (Sat, 18 Feb 2017 17:20:11 GMT):
https://gerrit.hyperledger.org/r/#/c/6077/ <- looks like it was accidentally caught up in a rebase
jyellick (Sat, 18 Feb 2017 17:20:59 GMT):
I already have a pending CR which fixes this https://gerrit.hyperledger.org/r/#/c/6171/
jyellick (Sat, 18 Feb 2017 17:21:14 GMT):
I thought I had fixed a regression from my own rebase, but looks like it was already in master
jyellick (Sat, 18 Feb 2017 17:22:03 GMT):
We really need to get the bdd tests enabled in the build, as they exercise these images and would have caught this regression
pmullaney (Sat, 18 Feb 2017 17:51:01 GMT):
Has joined the channel.
AkshayVish (Sat, 18 Feb 2017 18:26:02 GMT):
Has joined the channel.
AkshayVish (Sat, 18 Feb 2017 18:26:37 GMT):
Hi, I'm using the v2-typescript branch of fabric-boilerplate and deploying it to Bluemix. I ran npm run cf to get into the CF repository. Now, that I'm in the CF repository when I execute cd server && npm run deploy, it gives me the following error:
AkshayVish (Sat, 18 Feb 2017 18:26:51 GMT):
Error: Cannot find module '../../resources/testData.json'
AkshayVish (Sat, 18 Feb 2017 18:27:14 GMT):
anything that im doing wrong/
AkshayVish (Sat, 18 Feb 2017 18:27:18 GMT):
*?
cdaughtr (Sat, 18 Feb 2017 19:22:43 GMT):
@jyellick I pulled and rebuilt fabric and it includes 6171, but orderer is failing with a different error:
Error loading MSP configuration for org SampleOrg: Could not load a valid ca certificate from directory msp/sampleconfig/cacerts, err Could not read directory open msp/sampleconfig/cacerts: no such file or directory, err msp/sampleconfig/cacerts
jyellick (Sat, 18 Feb 2017 19:23:18 GMT):
How are you executing the orderer?
cdaughtr (Sat, 18 Feb 2017 19:23:56 GMT):
docker-compose
cdaughtr (Sat, 18 Feb 2017 19:24:55 GMT):
do I need to add some env variables?
jyellick (Sat, 18 Feb 2017 19:31:01 GMT):
Which compose configuration?
jyellick (Sat, 18 Feb 2017 19:39:26 GMT):
@cdaughtr Ah, I see, as a workaround for the moment you may specify: `ORDERER_GENERAL_GENESISPROFILE=SampleInsecureSolo`
cdaughtr (Sat, 18 Feb 2017 19:41:51 GMT):
Thanks. I'm going to leave you alone for now, since your change came in after a change that breaks us. I'm going back to a level from yesterday.
jyellick (Sat, 18 Feb 2017 19:44:05 GMT):
Sorry for all the churn @cdaughtr
jhulten (Sat, 18 Feb 2017 20:38:26 GMT):
Has joined the channel.
jyellick (Sat, 18 Feb 2017 20:59:25 GMT):
FYI all
A merge has introduced a failure in master, and all CI is failing
jyellick (Sat, 18 Feb 2017 20:59:27 GMT):
https://gerrit.hyperledger.org/r/#/c/6225/
craigwilliams (Sat, 18 Feb 2017 22:08:23 GMT):
Has joined the channel.
craigwilliams (Sat, 18 Feb 2017 22:09:41 GMT):
Hi all, I've got a quick question. When deploying chaincode via the node SDK (hfc), is it possible to set the chaincode path to be a github url? It seems to want to deploy a local version
muralisr (Sat, 18 Feb 2017 22:40:31 GMT):
https://gerrit.hyperledger.org/r/#/c/6219/ has been rebased to use https://gerrit.hyperledger.org/r/#/c/6225.. once it succeeds hopefully master will be back on track
dselman (Sat, 18 Feb 2017 22:48:54 GMT):
Has joined the channel.
dselman (Sat, 18 Feb 2017 22:50:25 GMT):
We've created an Open Source application development framework for Hyperledger Fabric: https://fabric-composer.github.io/
dselman (Sat, 18 Feb 2017 22:51:02 GMT):
Please give it a try! We welcome contributions and collaboration.
dselman (Sat, 18 Feb 2017 22:51:43 GMT):
Please post detailed questions to StackOverflow (using the fabric-composer tag), or join the #fabric-composer channel.
dselman (Sat, 18 Feb 2017 22:52:52 GMT):
Intro blog article: https://blog.selman.org/2017/02/02/fabric-composer-open-source-framework-for-the-hyperledger-fabric-blockchain/
rascal-3 (Sun, 19 Feb 2017 07:01:10 GMT):
@dselman Looks nice!
vu3mmg (Sun, 19 Feb 2017 08:06:56 GMT):
A query about fabric-starter-kit
vu3mmg (Sun, 19 Feb 2017 08:07:29 GMT):
based on my understanding when we add our own code we need to rebuild the docker image for fabric-starter-kit ?
vu3mmg (Sun, 19 Feb 2017 08:08:02 GMT):
but I am facing an issue of mounting the local directory in my host mac system to the directory in side docker image
vu3mmg (Sun, 19 Feb 2017 08:08:20 GMT):
the mapped directory does not have files , the directory is empty
vu3mmg (Sun, 19 Feb 2017 08:08:34 GMT):
any one faced similiar issue ?
johnwolpert (Sun, 19 Feb 2017 16:05:43 GMT):
Has joined the channel.
HenryZhang (Sun, 19 Feb 2017 16:17:27 GMT):
Has joined the channel.
binhn (Sun, 19 Feb 2017 16:31:21 GMT): tothfn (Sun, 19 Feb 2017 18:56:56 GMT): scottz (Sun, 19 Feb 2017 19:21:20 GMT): GoodFaith (Sun, 19 Feb 2017 21:41:59 GMT): GoodFaith (Sun, 19 Feb 2017 21:42:31 GMT): UshKrish (Sun, 19 Feb 2017 22:00:01 GMT): rahulhegde (Sun, 19 Feb 2017 22:56:08 GMT): vdods (Mon, 20 Feb 2017 00:18:10 GMT): tarima (Mon, 20 Feb 2017 01:55:14 GMT): tarima (Mon, 20 Feb 2017 01:56:07 GMT): tarima (Mon, 20 Feb 2017 02:22:34 GMT): tarima (Mon, 20 Feb 2017 02:30:21 GMT): vu3mmg (Mon, 20 Feb 2017 06:27:55 GMT): vu3mmg (Mon, 20 Feb 2017 06:27:56 GMT): vu3mmg (Mon, 20 Feb 2017 06:28:18 GMT): vu3mmg (Mon, 20 Feb 2017 06:28:28 GMT): vu3mmg (Mon, 20 Feb 2017 06:28:36 GMT): raghavsood (Mon, 20 Feb 2017 07:01:11 GMT): raghavsood (Mon, 20 Feb 2017 07:01:17 GMT): raghavsood (Mon, 20 Feb 2017 07:01:24 GMT): raghavsood (Mon, 20 Feb 2017 07:01:53 GMT): raghavsood (Mon, 20 Feb 2017 07:02:02 GMT): raghavsood (Mon, 20 Feb 2017 07:02:14 GMT): dazzaji (Mon, 20 Feb 2017 07:07:06 GMT): redpanda (Mon, 20 Feb 2017 08:39:36 GMT): YanLi (Mon, 20 Feb 2017 08:43:12 GMT): redpanda (Mon, 20 Feb 2017 09:10:37 GMT): mastersingh24 (Mon, 20 Feb 2017 09:21:05 GMT): TrevorOakley (Mon, 20 Feb 2017 09:22:53 GMT): TrevorOakley (Mon, 20 Feb 2017 09:22:59 GMT): TrevorOakley (Mon, 20 Feb 2017 09:23:28 GMT): Vadim (Mon, 20 Feb 2017 09:23:56 GMT): TrevorOakley (Mon, 20 Feb 2017 09:24:02 GMT): TrevorOakley (Mon, 20 Feb 2017 09:24:23 GMT): ascatox (Mon, 20 Feb 2017 09:24:30 GMT): Vadim (Mon, 20 Feb 2017 09:24:32 GMT): TrevorOakley (Mon, 20 Feb 2017 09:24:39 GMT): alisonb (Mon, 20 Feb 2017 09:24:40 GMT): TrevorOakley (Mon, 20 Feb 2017 09:24:47 GMT): Vadim (Mon, 20 Feb 2017 09:24:59 GMT): alisonb (Mon, 20 Feb 2017 09:25:03 GMT): ascatox (Mon, 20 Feb 2017 09:25:10 GMT): TrevorOakley (Mon, 20 Feb 2017 09:25:18 GMT): Vadim (Mon, 20 Feb 2017 09:25:45 GMT): TrevorOakley (Mon, 20 Feb 2017 09:26:11 GMT): Vadim (Mon, 20 Feb 2017 09:26:25 GMT): Vadim (Mon, 20 Feb 2017 09:26:38 GMT): TrevorOakley (Mon, 20 Feb 2017 09:27:02 GMT): Vadim (Mon, 20 Feb 2017 09:27:07 GMT): Vadim (Mon, 20 Feb 2017 09:27:07 GMT): redpanda (Mon, 20 Feb 2017 09:27:37 GMT): TrevorOakley (Mon, 20 Feb 2017 09:29:19 GMT): Vadim (Mon, 20 Feb 2017 09:29:42 GMT): TrevorOakley (Mon, 20 Feb 2017 09:30:05 GMT): TrevorOakley (Mon, 20 Feb 2017 09:30:26 GMT): Vadim (Mon, 20 Feb 2017 09:30:32 GMT): ascatox (Mon, 20 Feb 2017 09:47:51 GMT): ascatox (Mon, 20 Feb 2017 09:48:08 GMT): ascatox (Mon, 20 Feb 2017 09:48:08 GMT): ascatox (Mon, 20 Feb 2017 09:48:16 GMT): levinkwong (Mon, 20 Feb 2017 11:10:36 GMT): TrevorOakley (Mon, 20 Feb 2017 11:13:53 GMT): TrevorOakley (Mon, 20 Feb 2017 11:14:25 GMT): TrevorOakley (Mon, 20 Feb 2017 11:14:48 GMT): TrevorOakley (Mon, 20 Feb 2017 11:15:55 GMT): TrevorOakley (Mon, 20 Feb 2017 11:16:47 GMT): Vadim (Mon, 20 Feb 2017 11:31:43 GMT): Vadim (Mon, 20 Feb 2017 11:32:25 GMT): TrevorOakley (Mon, 20 Feb 2017 11:43:21 GMT): TrevorOakley (Mon, 20 Feb 2017 11:44:21 GMT): Vadim (Mon, 20 Feb 2017 11:44:22 GMT): Vadim (Mon, 20 Feb 2017 11:44:40 GMT): TrevorOakley (Mon, 20 Feb 2017 11:45:24 GMT): dolanort (Mon, 20 Feb 2017 11:45:30 GMT): Vadim (Mon, 20 Feb 2017 11:46:16 GMT): Vadim (Mon, 20 Feb 2017 11:46:27 GMT): Vadim (Mon, 20 Feb 2017 11:46:27 GMT): dolanort (Mon, 20 Feb 2017 11:48:26 GMT): dolanort (Mon, 20 Feb 2017 11:48:38 GMT): Vadim (Mon, 20 Feb 2017 11:51:36 GMT): dolanort (Mon, 20 Feb 2017 11:52:38 GMT): dolanort (Mon, 20 Feb 2017 11:52:49 GMT): dolanort (Mon, 20 Feb 2017 11:53:54 GMT): dolanort (Mon, 20 Feb 2017 11:53:54 GMT): yacovm (Mon, 20 Feb 2017 11:53:57 GMT): yacovm (Mon, 20 Feb 2017 11:54:08 GMT): dolanort (Mon, 20 Feb 2017 11:55:17 GMT): dolanort (Mon, 20 Feb 2017 11:55:44 GMT): dolanort (Mon, 20 Feb 2017 11:55:44 GMT): dolanort (Mon, 20 Feb 2017 11:57:23 GMT): dolanort (Mon, 20 Feb 2017 11:57:23 GMT): yacovm (Mon, 20 Feb 2017 12:00:23 GMT): yacovm (Mon, 20 Feb 2017 12:00:45 GMT): yacovm (Mon, 20 Feb 2017 12:00:49 GMT): thojest (Mon, 20 Feb 2017 12:09:57 GMT): thojest (Mon, 20 Feb 2017 12:10:01 GMT): thojest (Mon, 20 Feb 2017 12:10:08 GMT): thojest (Mon, 20 Feb 2017 12:10:18 GMT): dolanort (Mon, 20 Feb 2017 12:11:46 GMT): dolanort (Mon, 20 Feb 2017 12:12:04 GMT): dolanort (Mon, 20 Feb 2017 12:23:24 GMT): dolanort (Mon, 20 Feb 2017 12:23:44 GMT): yacovm (Mon, 20 Feb 2017 12:26:52 GMT): yacovm (Mon, 20 Feb 2017 12:26:52 GMT): dolanort (Mon, 20 Feb 2017 12:27:32 GMT): yacovm (Mon, 20 Feb 2017 12:29:15 GMT): dolanort (Mon, 20 Feb 2017 12:30:01 GMT): yacovm (Mon, 20 Feb 2017 12:30:14 GMT): yacovm (Mon, 20 Feb 2017 12:30:25 GMT): yacovm (Mon, 20 Feb 2017 12:30:32 GMT): dolanort (Mon, 20 Feb 2017 12:31:01 GMT): thojest (Mon, 20 Feb 2017 12:32:20 GMT): rickr (Mon, 20 Feb 2017 12:35:08 GMT): rickr (Mon, 20 Feb 2017 12:35:08 GMT): mastersingh24 (Mon, 20 Feb 2017 12:39:33 GMT): thojest (Mon, 20 Feb 2017 12:40:39 GMT): mastersingh24 (Mon, 20 Feb 2017 12:51:11 GMT): manish-sethi (Mon, 20 Feb 2017 12:51:11 GMT): AnupamVijayvergia (Mon, 20 Feb 2017 13:00:27 GMT): kleman (Mon, 20 Feb 2017 13:36:30 GMT): MadhavaReddy (Mon, 20 Feb 2017 13:53:23 GMT): ztluo (Mon, 20 Feb 2017 14:41:24 GMT): jyellick (Mon, 20 Feb 2017 15:14:56 GMT): muralisr (Mon, 20 Feb 2017 15:16:37 GMT): ashutosh_kumar (Mon, 20 Feb 2017 15:24:35 GMT): ashutosh_kumar (Mon, 20 Feb 2017 15:24:35 GMT): mastersingh24 (Mon, 20 Feb 2017 18:10:19 GMT): ashutosh_kumar (Mon, 20 Feb 2017 18:40:09 GMT): wisam.mohammed (Mon, 20 Feb 2017 19:13:28 GMT): binhn (Mon, 20 Feb 2017 19:21:10 GMT): rkiouak (Mon, 20 Feb 2017 21:15:15 GMT): altharp (Mon, 20 Feb 2017 21:18:42 GMT): vukolic (Mon, 20 Feb 2017 23:02:02 GMT): LordChaos (Mon, 20 Feb 2017 23:58:33 GMT): baohua (Tue, 21 Feb 2017 00:42:46 GMT): Ying (Tue, 21 Feb 2017 02:10:39 GMT): ibmamnt (Tue, 21 Feb 2017 02:40:41 GMT): ibmamnt (Tue, 21 Feb 2017 02:43:59 GMT): huxiangdong (Tue, 21 Feb 2017 02:59:03 GMT): weeds (Tue, 21 Feb 2017 03:24:36 GMT): elli-androulaki (Tue, 21 Feb 2017 03:24:36 GMT): raghavsood (Tue, 21 Feb 2017 04:46:05 GMT): raghavsood (Tue, 21 Feb 2017 04:47:34 GMT): chenshuijin (Tue, 21 Feb 2017 05:16:20 GMT): warm3snow (Tue, 21 Feb 2017 05:19:10 GMT): elli-androulaki (Tue, 21 Feb 2017 07:36:52 GMT): mastersingh24 (Tue, 21 Feb 2017 07:38:20 GMT): elli-androulaki (Tue, 21 Feb 2017 07:41:43 GMT): elli-androulaki (Tue, 21 Feb 2017 07:41:43 GMT): raghavsood (Tue, 21 Feb 2017 07:45:11 GMT): raghavsood (Tue, 21 Feb 2017 07:45:32 GMT): mastersingh24 (Tue, 21 Feb 2017 08:12:05 GMT): mastersingh24 (Tue, 21 Feb 2017 08:12:20 GMT): ibmamnt (Tue, 21 Feb 2017 08:13:47 GMT): raghavsood (Tue, 21 Feb 2017 08:15:37 GMT): elli-androulaki (Tue, 21 Feb 2017 08:18:46 GMT): mastersingh24 (Tue, 21 Feb 2017 08:20:20 GMT): mastersingh24 (Tue, 21 Feb 2017 08:20:41 GMT): raghavsood (Tue, 21 Feb 2017 08:20:58 GMT): mastersingh24 (Tue, 21 Feb 2017 08:21:33 GMT): raghavsood (Tue, 21 Feb 2017 08:21:39 GMT): raghavsood (Tue, 21 Feb 2017 08:21:43 GMT): raghavsood (Tue, 21 Feb 2017 08:21:47 GMT): mastersingh24 (Tue, 21 Feb 2017 08:21:57 GMT): mastersingh24 (Tue, 21 Feb 2017 08:21:57 GMT): raghavsood (Tue, 21 Feb 2017 08:22:05 GMT): mastersingh24 (Tue, 21 Feb 2017 08:22:18 GMT): raghavsood (Tue, 21 Feb 2017 08:22:48 GMT): raghavsood (Tue, 21 Feb 2017 08:23:05 GMT): raghavsood (Tue, 21 Feb 2017 08:23:14 GMT): raghavsood (Tue, 21 Feb 2017 08:23:51 GMT): mastersingh24 (Tue, 21 Feb 2017 08:24:05 GMT): mastersingh24 (Tue, 21 Feb 2017 08:24:20 GMT): allwelder (Tue, 21 Feb 2017 08:31:25 GMT): conroydave (Tue, 21 Feb 2017 09:19:51 GMT): conroydave (Tue, 21 Feb 2017 09:19:58 GMT): conroydave (Tue, 21 Feb 2017 09:20:06 GMT): conroydave (Tue, 21 Feb 2017 09:20:15 GMT): dselman (Tue, 21 Feb 2017 09:46:21 GMT): conroydave (Tue, 21 Feb 2017 09:47:08 GMT): conroydave (Tue, 21 Feb 2017 09:47:26 GMT): dselman (Tue, 21 Feb 2017 09:47:36 GMT): dselman (Tue, 21 Feb 2017 09:48:04 GMT): conroydave (Tue, 21 Feb 2017 09:48:25 GMT): conroydave (Tue, 21 Feb 2017 09:49:19 GMT): conroydave (Tue, 21 Feb 2017 09:50:03 GMT): dselman (Tue, 21 Feb 2017 09:50:18 GMT): conroydave (Tue, 21 Feb 2017 09:50:20 GMT): conroydave (Tue, 21 Feb 2017 09:50:26 GMT): conroydave (Tue, 21 Feb 2017 09:50:34 GMT): dselman (Tue, 21 Feb 2017 09:50:50 GMT): conroydave (Tue, 21 Feb 2017 09:51:10 GMT): conroydave (Tue, 21 Feb 2017 09:51:24 GMT): dselman (Tue, 21 Feb 2017 09:51:25 GMT): dselman (Tue, 21 Feb 2017 09:51:54 GMT): conroydave (Tue, 21 Feb 2017 09:52:13 GMT): dselman (Tue, 21 Feb 2017 09:52:23 GMT): conroydave (Tue, 21 Feb 2017 09:52:32 GMT): dselman (Tue, 21 Feb 2017 09:52:33 GMT): conroydave (Tue, 21 Feb 2017 09:52:34 GMT): conroydave (Tue, 21 Feb 2017 09:52:44 GMT): conroydave (Tue, 21 Feb 2017 09:53:20 GMT): conroydave (Tue, 21 Feb 2017 09:55:23 GMT): sword_linux (Tue, 21 Feb 2017 10:11:18 GMT): oiakovlev (Tue, 21 Feb 2017 10:12:59 GMT): pd93 (Tue, 21 Feb 2017 10:13:11 GMT): pd93 (Tue, 21 Feb 2017 10:13:11 GMT): sword_linux (Tue, 21 Feb 2017 10:14:07 GMT): cbf (Tue, 21 Feb 2017 10:14:14 GMT): cbf (Tue, 21 Feb 2017 10:15:16 GMT): sword_linux (Tue, 21 Feb 2017 10:15:30 GMT): kleman (Tue, 21 Feb 2017 10:19:41 GMT): sword_linux (Tue, 21 Feb 2017 10:22:20 GMT): kleman (Tue, 21 Feb 2017 10:24:59 GMT): mastersingh24 (Tue, 21 Feb 2017 10:33:42 GMT): mastersingh24 (Tue, 21 Feb 2017 10:34:41 GMT): mastersingh24 (Tue, 21 Feb 2017 10:36:07 GMT): conroydave (Tue, 21 Feb 2017 10:52:18 GMT): realhuyi (Tue, 21 Feb 2017 11:30:17 GMT): jessilb (Tue, 21 Feb 2017 11:38:37 GMT): mrkiouak (Tue, 21 Feb 2017 12:58:57 GMT): mrkiouak (Tue, 21 Feb 2017 13:00:30 GMT): mrkiouak (Tue, 21 Feb 2017 13:01:41 GMT): mastersingh24 (Tue, 21 Feb 2017 13:04:49 GMT): mrkiouak (Tue, 21 Feb 2017 13:09:21 GMT): mrkiouak (Tue, 21 Feb 2017 13:09:48 GMT): greg.haskins (Tue, 21 Feb 2017 13:23:32 GMT): greg.haskins (Tue, 21 Feb 2017 13:24:26 GMT): greg.haskins (Tue, 21 Feb 2017 13:24:34 GMT): magg (Tue, 21 Feb 2017 14:49:35 GMT): magg (Tue, 21 Feb 2017 14:50:17 GMT): magg (Tue, 21 Feb 2017 14:50:17 GMT): magg (Tue, 21 Feb 2017 14:52:17 GMT): mastersingh24 (Tue, 21 Feb 2017 14:52:41 GMT): mastersingh24 (Tue, 21 Feb 2017 14:53:14 GMT): magg (Tue, 21 Feb 2017 14:55:43 GMT): magg (Tue, 21 Feb 2017 15:02:15 GMT): tuand (Tue, 21 Feb 2017 15:09:31 GMT): kostas (Tue, 21 Feb 2017 15:13:11 GMT): kostas (Tue, 21 Feb 2017 15:13:11 GMT): kostas (Tue, 21 Feb 2017 15:13:11 GMT): kostas (Tue, 21 Feb 2017 15:13:11 GMT): kostas (Tue, 21 Feb 2017 15:13:23 GMT): eragnoli (Tue, 21 Feb 2017 15:16:04 GMT): magg (Tue, 21 Feb 2017 15:17:07 GMT): smfaizalkhan (Tue, 21 Feb 2017 15:51:41 GMT): smfaizalkhan (Tue, 21 Feb 2017 15:52:22 GMT): rrader (Tue, 21 Feb 2017 15:53:02 GMT): smfaizalkhan (Tue, 21 Feb 2017 16:06:28 GMT): smfaizalkhan (Tue, 21 Feb 2017 16:07:07 GMT): bjornwgnr (Tue, 21 Feb 2017 16:07:58 GMT): greg.haskins (Tue, 21 Feb 2017 16:33:50 GMT): jtrayfield (Tue, 21 Feb 2017 16:33:53 GMT): greg.haskins (Tue, 21 Feb 2017 16:34:38 GMT): jtrayfield (Tue, 21 Feb 2017 16:36:05 GMT): mikias (Tue, 21 Feb 2017 17:53:39 GMT): weeds (Tue, 21 Feb 2017 18:05:28 GMT): weeds (Tue, 21 Feb 2017 18:05:51 GMT): RezwanKabir (Tue, 21 Feb 2017 18:51:46 GMT): agaragiola (Tue, 21 Feb 2017 20:53:21 GMT): scottz (Tue, 21 Feb 2017 22:29:13 GMT): zmanian (Wed, 22 Feb 2017 00:27:06 GMT): greg.haskins (Wed, 22 Feb 2017 00:53:44 GMT): jtrayfield (Wed, 22 Feb 2017 00:54:41 GMT): greg.haskins (Wed, 22 Feb 2017 00:55:00 GMT): greg.haskins (Wed, 22 Feb 2017 00:57:57 GMT): greg.haskins (Wed, 22 Feb 2017 00:58:47 GMT): jtrayfield (Wed, 22 Feb 2017 01:00:11 GMT): levinkwong (Wed, 22 Feb 2017 06:42:54 GMT): levinkwong (Wed, 22 Feb 2017 08:04:49 GMT): ibmamnt (Wed, 22 Feb 2017 08:35:53 GMT): ibmamnt (Wed, 22 Feb 2017 08:36:34 GMT): levinkwong (Wed, 22 Feb 2017 08:38:45 GMT): levinkwong (Wed, 22 Feb 2017 08:40:30 GMT): ibmamnt (Wed, 22 Feb 2017 08:40:52 GMT): levinkwong (Wed, 22 Feb 2017 08:41:29 GMT): ibmamnt (Wed, 22 Feb 2017 08:42:27 GMT): gatakka (Wed, 22 Feb 2017 09:13:12 GMT): gatakka (Wed, 22 Feb 2017 09:14:06 GMT): yacovm (Wed, 22 Feb 2017 09:14:06 GMT): aso (Wed, 22 Feb 2017 09:14:06 GMT): RezwanKabir (Wed, 22 Feb 2017 09:17:29 GMT): TrevorOakley (Wed, 22 Feb 2017 09:42:57 GMT): TrevorOakley (Wed, 22 Feb 2017 09:43:41 GMT): TrevorOakley (Wed, 22 Feb 2017 09:43:43 GMT): TrevorOakley (Wed, 22 Feb 2017 09:44:06 GMT): TrevorOakley (Wed, 22 Feb 2017 09:46:06 GMT): TrevorOakley (Wed, 22 Feb 2017 10:56:14 GMT): dolanor (Wed, 22 Feb 2017 11:34:22 GMT): dolanor (Wed, 22 Feb 2017 11:35:21 GMT): adc (Wed, 22 Feb 2017 12:14:07 GMT): TrevorOakley (Wed, 22 Feb 2017 12:16:34 GMT): TrevorOakley (Wed, 22 Feb 2017 12:16:45 GMT): dolanor (Wed, 22 Feb 2017 12:22:49 GMT): dolanor (Wed, 22 Feb 2017 12:22:49 GMT): vu3mmg (Wed, 22 Feb 2017 12:55:17 GMT): vu3mmg (Wed, 22 Feb 2017 12:55:23 GMT): vu3mmg (Wed, 22 Feb 2017 12:56:01 GMT): psa (Wed, 22 Feb 2017 13:05:10 GMT): ruslan.kryukov (Wed, 22 Feb 2017 13:18:08 GMT): ruslan.kryukov (Wed, 22 Feb 2017 13:18:08 GMT): weeds (Wed, 22 Feb 2017 13:26:29 GMT): jtrayfield (Wed, 22 Feb 2017 13:41:41 GMT): jtrayfield (Wed, 22 Feb 2017 13:45:45 GMT): lohitkrishnan (Wed, 22 Feb 2017 13:48:09 GMT): vu3mmg (Wed, 22 Feb 2017 14:00:33 GMT): gatakka (Wed, 22 Feb 2017 14:04:57 GMT): vu3mmg (Wed, 22 Feb 2017 14:05:14 GMT): gatakka (Wed, 22 Feb 2017 14:05:28 GMT): gatakka (Wed, 22 Feb 2017 14:05:28 GMT): vu3mmg (Wed, 22 Feb 2017 14:05:56 GMT): aso (Wed, 22 Feb 2017 14:06:02 GMT): gatakka (Wed, 22 Feb 2017 14:06:51 GMT): gatakka (Wed, 22 Feb 2017 14:07:25 GMT): vu3mmg (Wed, 22 Feb 2017 14:08:01 GMT): gatakka (Wed, 22 Feb 2017 14:08:53 GMT): uber.twin (Wed, 22 Feb 2017 14:11:12 GMT): uber.twin (Wed, 22 Feb 2017 14:14:20 GMT): uber.twin (Wed, 22 Feb 2017 14:14:49 GMT): uber.twin (Wed, 22 Feb 2017 14:15:15 GMT): vu3mmg (Wed, 22 Feb 2017 14:16:50 GMT): uber.twin (Wed, 22 Feb 2017 14:17:42 GMT): dolanor (Wed, 22 Feb 2017 14:42:59 GMT): git123456 (Wed, 22 Feb 2017 16:42:19 GMT): davidkel (Wed, 22 Feb 2017 17:01:32 GMT): stanacton (Wed, 22 Feb 2017 17:40:33 GMT): stanacton (Wed, 22 Feb 2017 17:40:36 GMT): stanacton (Wed, 22 Feb 2017 17:41:54 GMT): davidkel (Wed, 22 Feb 2017 17:48:10 GMT): GoodFaith (Wed, 22 Feb 2017 18:55:41 GMT): GoodFaith (Wed, 22 Feb 2017 19:05:50 GMT): GoodFaith (Wed, 22 Feb 2017 19:15:00 GMT): techalchemist (Wed, 22 Feb 2017 19:32:00 GMT): techalchemist (Wed, 22 Feb 2017 19:36:30 GMT): techalchemist (Wed, 22 Feb 2017 19:36:38 GMT): techalchemist (Wed, 22 Feb 2017 19:36:38 GMT): techalchemist (Wed, 22 Feb 2017 19:36:50 GMT): techalchemist (Wed, 22 Feb 2017 19:41:26 GMT): dragosh (Wed, 22 Feb 2017 19:46:55 GMT): pascallouis (Wed, 22 Feb 2017 20:02:49 GMT): weeds (Wed, 22 Feb 2017 20:22:33 GMT): elli-androulaki (Wed, 22 Feb 2017 20:23:51 GMT): elli-androulaki (Wed, 22 Feb 2017 20:23:51 GMT): stanacton (Wed, 22 Feb 2017 20:24:00 GMT): elli-androulaki (Wed, 22 Feb 2017 20:27:03 GMT): ktekavec@us.ibm.com (Wed, 22 Feb 2017 20:28:32 GMT): elli-androulaki (Wed, 22 Feb 2017 20:28:56 GMT): elli-androulaki (Wed, 22 Feb 2017 20:29:44 GMT): stanacton (Wed, 22 Feb 2017 20:29:59 GMT): elli-androulaki (Wed, 22 Feb 2017 20:31:14 GMT): elli-androulaki (Wed, 22 Feb 2017 20:31:14 GMT): stanacton (Wed, 22 Feb 2017 20:32:24 GMT): elli-androulaki (Wed, 22 Feb 2017 20:33:19 GMT): elli-androulaki (Wed, 22 Feb 2017 20:33:56 GMT): elli-androulaki (Wed, 22 Feb 2017 20:33:56 GMT): stanacton (Wed, 22 Feb 2017 20:38:50 GMT): stanacton (Wed, 22 Feb 2017 20:41:49 GMT): elli-androulaki (Wed, 22 Feb 2017 20:42:27 GMT): elli-androulaki (Wed, 22 Feb 2017 20:42:27 GMT): gbh (Wed, 22 Feb 2017 22:35:07 GMT): zerppen (Thu, 23 Feb 2017 01:48:06 GMT): Hangyu (Thu, 23 Feb 2017 02:11:16 GMT): bartcant (Thu, 23 Feb 2017 02:12:20 GMT): ashutosh_kumar (Thu, 23 Feb 2017 02:21:34 GMT): ashutosh_kumar (Thu, 23 Feb 2017 02:21:34 GMT): YichenWang (Thu, 23 Feb 2017 03:16:39 GMT): YichenWang (Thu, 23 Feb 2017 03:17:13 GMT): YichenWang (Thu, 23 Feb 2017 03:17:18 GMT): saridsa1 (Thu, 23 Feb 2017 06:55:45 GMT): saridsa1 (Thu, 23 Feb 2017 08:17:44 GMT): saridsa1 (Thu, 23 Feb 2017 08:19:10 GMT): vinayakkumar (Thu, 23 Feb 2017 08:22:25 GMT): Ying (Thu, 23 Feb 2017 08:31:53 GMT): elli-androulaki (Thu, 23 Feb 2017 08:39:48 GMT): elli-androulaki (Thu, 23 Feb 2017 08:39:48 GMT): elli-androulaki (Thu, 23 Feb 2017 08:39:48 GMT): elli-androulaki (Thu, 23 Feb 2017 08:39:48 GMT): gatakka (Thu, 23 Feb 2017 08:50:49 GMT): CarlXK (Thu, 23 Feb 2017 09:02:51 GMT): pd93 (Thu, 23 Feb 2017 09:12:58 GMT): warm3snow (Thu, 23 Feb 2017 09:18:49 GMT): aratic (Thu, 23 Feb 2017 09:28:01 GMT): Ying (Thu, 23 Feb 2017 09:31:07 GMT): aratic (Thu, 23 Feb 2017 09:31:08 GMT): pd93 (Thu, 23 Feb 2017 09:32:19 GMT): pd93 (Thu, 23 Feb 2017 09:32:43 GMT): aratic (Thu, 23 Feb 2017 09:33:31 GMT): Ying (Thu, 23 Feb 2017 09:34:56 GMT): Ying (Thu, 23 Feb 2017 09:35:23 GMT): pd93 (Thu, 23 Feb 2017 09:36:08 GMT): Ying (Thu, 23 Feb 2017 09:37:17 GMT): MartinC (Thu, 23 Feb 2017 09:46:19 GMT): fuego917 (Thu, 23 Feb 2017 11:08:15 GMT): ianj_mitchell@uk.ibm.com (Thu, 23 Feb 2017 11:14:43 GMT): rickr (Thu, 23 Feb 2017 11:51:41 GMT): gatakka (Thu, 23 Feb 2017 11:52:50 GMT): gatakka (Thu, 23 Feb 2017 12:00:13 GMT): gatakka (Thu, 23 Feb 2017 12:06:59 GMT): rrader (Thu, 23 Feb 2017 12:14:51 GMT): gatakka (Thu, 23 Feb 2017 12:20:23 GMT): gatakka (Thu, 23 Feb 2017 12:20:23 GMT): rrader (Thu, 23 Feb 2017 12:22:24 GMT): rrader (Thu, 23 Feb 2017 12:22:24 GMT): gatakka (Thu, 23 Feb 2017 12:28:24 GMT): srm (Thu, 23 Feb 2017 13:30:31 GMT): greg.haskins (Thu, 23 Feb 2017 13:51:19 GMT): rameshthoomu (Thu, 23 Feb 2017 13:56:07 GMT): rrader (Thu, 23 Feb 2017 13:58:38 GMT): jyellick (Thu, 23 Feb 2017 13:59:14 GMT): gatakka (Thu, 23 Feb 2017 13:59:45 GMT): rameshthoomu (Thu, 23 Feb 2017 13:59:49 GMT): rrader (Thu, 23 Feb 2017 14:13:38 GMT): rrader (Thu, 23 Feb 2017 14:18:49 GMT): muralisr (Thu, 23 Feb 2017 14:54:51 GMT): greg.haskins (Thu, 23 Feb 2017 14:55:12 GMT): muralisr (Thu, 23 Feb 2017 14:55:38 GMT): greg.haskins (Thu, 23 Feb 2017 14:56:00 GMT): greg.haskins (Thu, 23 Feb 2017 14:56:09 GMT): greg.haskins (Thu, 23 Feb 2017 14:56:11 GMT): greg.haskins (Thu, 23 Feb 2017 14:56:49 GMT): muralisr (Thu, 23 Feb 2017 15:57:50 GMT): greg.haskins (Thu, 23 Feb 2017 16:00:12 GMT): muralisr (Thu, 23 Feb 2017 16:00:44 GMT): muralisr (Thu, 23 Feb 2017 16:02:13 GMT): greg.haskins (Thu, 23 Feb 2017 16:07:02 GMT): greg.haskins (Thu, 23 Feb 2017 16:07:22 GMT): muralisr (Thu, 23 Feb 2017 16:08:42 GMT): muralisr (Thu, 23 Feb 2017 16:08:42 GMT): greg.haskins (Thu, 23 Feb 2017 16:10:50 GMT): greg.haskins (Thu, 23 Feb 2017 16:11:04 GMT): greg.haskins (Thu, 23 Feb 2017 16:12:49 GMT): greg.haskins (Thu, 23 Feb 2017 16:13:33 GMT): greg.haskins (Thu, 23 Feb 2017 16:13:45 GMT): greg.haskins (Thu, 23 Feb 2017 16:14:20 GMT): greg.haskins (Thu, 23 Feb 2017 16:14:43 GMT): greg.haskins (Thu, 23 Feb 2017 16:15:07 GMT): kdj (Thu, 23 Feb 2017 16:48:46 GMT): aaron.benningfield (Thu, 23 Feb 2017 16:50:01 GMT): aaron.benningfield (Thu, 23 Feb 2017 16:57:04 GMT): stanacton (Thu, 23 Feb 2017 17:21:06 GMT): elli-androulaki (Thu, 23 Feb 2017 17:30:50 GMT): stanacton (Thu, 23 Feb 2017 17:33:34 GMT): elli-androulaki (Thu, 23 Feb 2017 17:33:54 GMT): pd93 (Thu, 23 Feb 2017 18:09:58 GMT): sbrakev (Thu, 23 Feb 2017 18:10:37 GMT): pd93 (Thu, 23 Feb 2017 18:10:52 GMT): pd93 (Thu, 23 Feb 2017 18:10:55 GMT): sbrakev (Thu, 23 Feb 2017 18:11:59 GMT): sbrakev (Thu, 23 Feb 2017 18:12:19 GMT): pd93 (Thu, 23 Feb 2017 18:13:28 GMT): pd93 (Thu, 23 Feb 2017 18:13:37 GMT): sbrakev (Thu, 23 Feb 2017 18:13:52 GMT): sbrakev (Thu, 23 Feb 2017 18:14:37 GMT): sbrakev (Thu, 23 Feb 2017 18:14:40 GMT): tulioribeiro (Thu, 23 Feb 2017 18:15:57 GMT): pd93 (Thu, 23 Feb 2017 18:15:59 GMT): pd93 (Thu, 23 Feb 2017 18:16:01 GMT): tulioribeiro (Thu, 23 Feb 2017 18:17:48 GMT): cdaughtr (Thu, 23 Feb 2017 18:49:55 GMT): beckmann (Thu, 23 Feb 2017 19:03:59 GMT): beckmann (Thu, 23 Feb 2017 19:05:51 GMT): weeds (Thu, 23 Feb 2017 19:07:32 GMT): weeds (Thu, 23 Feb 2017 19:07:41 GMT): weeds (Thu, 23 Feb 2017 19:08:17 GMT): weeds (Thu, 23 Feb 2017 19:08:30 GMT): weeds (Thu, 23 Feb 2017 19:08:57 GMT): pd93 (Thu, 23 Feb 2017 19:09:13 GMT): pd93 (Thu, 23 Feb 2017 19:10:30 GMT): pd93 (Thu, 23 Feb 2017 19:10:34 GMT): weeds (Thu, 23 Feb 2017 19:11:11 GMT): nickgaski (Thu, 23 Feb 2017 19:11:42 GMT): weeds (Thu, 23 Feb 2017 19:11:56 GMT): pd93 (Thu, 23 Feb 2017 19:12:32 GMT): nickgaski (Thu, 23 Feb 2017 19:15:08 GMT): pd93 (Thu, 23 Feb 2017 19:16:15 GMT): tuand (Thu, 23 Feb 2017 19:17:45 GMT): cdaughtr (Thu, 23 Feb 2017 19:24:07 GMT): RyanElliott (Thu, 23 Feb 2017 19:26:09 GMT): pd93 (Thu, 23 Feb 2017 19:37:56 GMT): jyellick (Thu, 23 Feb 2017 19:41:12 GMT): cdaughtr (Thu, 23 Feb 2017 19:41:43 GMT): jyellick (Thu, 23 Feb 2017 19:42:53 GMT): cdaughtr (Thu, 23 Feb 2017 19:43:56 GMT): jyellick (Thu, 23 Feb 2017 20:08:20 GMT): cdaughtr (Thu, 23 Feb 2017 20:09:32 GMT): Regena (Thu, 23 Feb 2017 20:10:42 GMT): nickgaski (Thu, 23 Feb 2017 20:31:32 GMT): jimthematrix (Thu, 23 Feb 2017 20:46:56 GMT): jimthematrix (Thu, 23 Feb 2017 20:47:23 GMT): jyellick (Thu, 23 Feb 2017 20:47:26 GMT): jimthematrix (Thu, 23 Feb 2017 20:48:13 GMT): jimthematrix (Thu, 23 Feb 2017 20:49:25 GMT): rickr (Thu, 23 Feb 2017 20:51:55 GMT): jimthematrix (Thu, 23 Feb 2017 20:52:18 GMT): jyellick (Thu, 23 Feb 2017 20:53:46 GMT): jyellick (Thu, 23 Feb 2017 20:54:57 GMT): jyellick (Thu, 23 Feb 2017 20:56:11 GMT): jyellick (Thu, 23 Feb 2017 20:59:04 GMT): jyellick (Thu, 23 Feb 2017 20:59:04 GMT): jimthematrix (Thu, 23 Feb 2017 21:02:26 GMT): jyellick (Thu, 23 Feb 2017 21:02:58 GMT): jimthematrix (Thu, 23 Feb 2017 21:05:51 GMT): jyellick (Thu, 23 Feb 2017 21:07:16 GMT): jyellick (Thu, 23 Feb 2017 21:07:26 GMT): jyellick (Thu, 23 Feb 2017 21:07:37 GMT): jimthematrix (Thu, 23 Feb 2017 21:08:28 GMT): jyellick (Thu, 23 Feb 2017 21:08:34 GMT): jimthematrix (Thu, 23 Feb 2017 21:08:41 GMT): jimthematrix (Thu, 23 Feb 2017 21:08:59 GMT): jyellick (Thu, 23 Feb 2017 21:08:59 GMT): jyellick (Thu, 23 Feb 2017 21:09:12 GMT): jimthematrix (Thu, 23 Feb 2017 21:09:18 GMT): jyellick (Thu, 23 Feb 2017 21:09:24 GMT): jimthematrix (Thu, 23 Feb 2017 21:13:55 GMT): jyellick (Thu, 23 Feb 2017 21:14:35 GMT): jimthematrix (Thu, 23 Feb 2017 21:14:38 GMT): jyellick (Thu, 23 Feb 2017 21:14:58 GMT): jyellick (Thu, 23 Feb 2017 21:15:23 GMT): jimthematrix (Thu, 23 Feb 2017 21:15:39 GMT): jimthematrix (Thu, 23 Feb 2017 21:15:59 GMT): jyellick (Thu, 23 Feb 2017 21:16:14 GMT): jyellick (Thu, 23 Feb 2017 21:17:09 GMT): jimthematrix (Thu, 23 Feb 2017 21:20:01 GMT): jimthematrix (Thu, 23 Feb 2017 21:23:25 GMT): jimthematrix (Thu, 23 Feb 2017 21:24:04 GMT): jyellick (Thu, 23 Feb 2017 21:26:58 GMT): rnair@itbit.com (Thu, 23 Feb 2017 21:49:18 GMT): ashutosh_kumar (Fri, 24 Feb 2017 00:44:28 GMT): greg.haskins (Fri, 24 Feb 2017 03:06:38 GMT): greg.haskins (Fri, 24 Feb 2017 03:07:02 GMT): greg.haskins (Fri, 24 Feb 2017 03:07:14 GMT): raulshen (Fri, 24 Feb 2017 05:36:21 GMT): raulshen (Fri, 24 Feb 2017 05:43:04 GMT): Ying (Fri, 24 Feb 2017 06:25:35 GMT): jansony1 (Fri, 24 Feb 2017 06:37:12 GMT): CarlXK (Fri, 24 Feb 2017 06:42:32 GMT): arvindupadhyaya (Fri, 24 Feb 2017 08:00:25 GMT): arvindupadhyaya (Fri, 24 Feb 2017 08:31:47 GMT): jansony1 (Fri, 24 Feb 2017 08:33:15 GMT): pd93 (Fri, 24 Feb 2017 08:33:28 GMT): arvindupadhyaya (Fri, 24 Feb 2017 08:33:38 GMT): pd93 (Fri, 24 Feb 2017 08:34:12 GMT): arvindupadhyaya (Fri, 24 Feb 2017 08:34:14 GMT): arvindupadhyaya (Fri, 24 Feb 2017 08:35:05 GMT): jansony1 (Fri, 24 Feb 2017 08:35:16 GMT): arvindupadhyaya (Fri, 24 Feb 2017 08:36:38 GMT): jansony1 (Fri, 24 Feb 2017 08:39:40 GMT): warm3snow (Fri, 24 Feb 2017 08:39:59 GMT): aratic (Fri, 24 Feb 2017 08:48:50 GMT): raulshen (Fri, 24 Feb 2017 08:49:29 GMT): aratic (Fri, 24 Feb 2017 08:51:48 GMT): pd93 (Fri, 24 Feb 2017 09:06:17 GMT): warm3snow (Fri, 24 Feb 2017 09:10:05 GMT): raulshen (Fri, 24 Feb 2017 10:30:36 GMT): jansony1 (Fri, 24 Feb 2017 11:26:25 GMT): uber.twin (Fri, 24 Feb 2017 12:44:19 GMT): uber.twin (Fri, 24 Feb 2017 12:44:20 GMT): arvindupadhyaya (Fri, 24 Feb 2017 12:54:14 GMT): albrandt (Fri, 24 Feb 2017 13:34:32 GMT): git123456 (Fri, 24 Feb 2017 14:24:30 GMT): git123456 (Fri, 24 Feb 2017 14:26:16 GMT): davidkel (Fri, 24 Feb 2017 15:06:36 GMT): cgrecu (Fri, 24 Feb 2017 15:23:00 GMT): davidkel (Fri, 24 Feb 2017 15:39:46 GMT): rehmke (Fri, 24 Feb 2017 17:00:43 GMT): julicjung (Fri, 24 Feb 2017 17:22:19 GMT): jansony1 (Fri, 24 Feb 2017 17:38:50 GMT): gdhh (Fri, 24 Feb 2017 18:02:54 GMT): kostas (Fri, 24 Feb 2017 18:37:44 GMT): muralisr (Fri, 24 Feb 2017 19:10:30 GMT): C0rWin (Fri, 24 Feb 2017 19:15:49 GMT): kostas (Fri, 24 Feb 2017 19:30:01 GMT): C0rWin (Fri, 24 Feb 2017 19:31:14 GMT): kostas (Fri, 24 Feb 2017 19:31:30 GMT): C0rWin (Fri, 24 Feb 2017 19:31:33 GMT): C0rWin (Fri, 24 Feb 2017 19:31:47 GMT): kostas (Fri, 24 Feb 2017 19:39:49 GMT): rahulhegde (Fri, 24 Feb 2017 19:45:53 GMT): rahulhegde (Fri, 24 Feb 2017 19:45:53 GMT): farhan3 (Fri, 24 Feb 2017 21:39:31 GMT): cdaughtr (Fri, 24 Feb 2017 21:41:21 GMT): cdaughtr (Fri, 24 Feb 2017 21:41:21 GMT): cdaughtr (Fri, 24 Feb 2017 21:41:21 GMT): cdaughtr (Fri, 24 Feb 2017 21:41:21 GMT): jyellick (Fri, 24 Feb 2017 21:54:21 GMT): jyellick (Fri, 24 Feb 2017 21:54:38 GMT): vpaprots (Fri, 24 Feb 2017 22:02:41 GMT): jyellick (Fri, 24 Feb 2017 22:05:40 GMT): jyellick (Fri, 24 Feb 2017 22:05:40 GMT): jyellick (Fri, 24 Feb 2017 22:07:11 GMT): jyellick (Fri, 24 Feb 2017 22:08:02 GMT): vpaprots (Fri, 24 Feb 2017 22:14:31 GMT): jyellick (Fri, 24 Feb 2017 22:17:06 GMT): vpaprots (Fri, 24 Feb 2017 22:17:18 GMT): vpaprots (Fri, 24 Feb 2017 22:17:24 GMT): jyellick (Fri, 24 Feb 2017 22:17:29 GMT): cdaughtr (Fri, 24 Feb 2017 22:38:20 GMT): rickr (Fri, 24 Feb 2017 23:38:59 GMT): rjones (Fri, 24 Feb 2017 23:47:00 GMT): rjones (Fri, 24 Feb 2017 23:48:15 GMT): rjones (Fri, 24 Feb 2017 23:48:15 GMT): lehors (Fri, 24 Feb 2017 23:49:27 GMT): rjones (Fri, 24 Feb 2017 23:50:45 GMT): rickr (Sat, 25 Feb 2017 00:38:46 GMT): rjones (Sat, 25 Feb 2017 00:40:01 GMT): rickr (Sat, 25 Feb 2017 00:40:33 GMT): rickr (Sat, 25 Feb 2017 00:42:25 GMT): rickr (Sat, 25 Feb 2017 00:42:25 GMT): slender (Sat, 25 Feb 2017 00:43:40 GMT): RyanElliott (Sat, 25 Feb 2017 00:43:44 GMT): RyanElliott (Sat, 25 Feb 2017 00:43:44 GMT): rickr (Sat, 25 Feb 2017 00:46:47 GMT): rjones (Sat, 25 Feb 2017 00:47:31 GMT): rickr (Sat, 25 Feb 2017 00:47:48 GMT): rjones (Sat, 25 Feb 2017 00:47:49 GMT): rickr (Sat, 25 Feb 2017 00:48:17 GMT): vdods (Sat, 25 Feb 2017 01:06:10 GMT): greg.haskins (Sat, 25 Feb 2017 01:54:43 GMT): greg.haskins (Sat, 25 Feb 2017 01:55:14 GMT): greg.haskins (Sat, 25 Feb 2017 01:56:04 GMT): vdods (Sat, 25 Feb 2017 02:11:01 GMT): jfiscella (Sat, 25 Feb 2017 05:44:01 GMT): warm3snow (Sat, 25 Feb 2017 08:21:41 GMT): rickr (Sat, 25 Feb 2017 13:20:03 GMT): blackskygg (Sat, 25 Feb 2017 14:23:01 GMT): blackskygg (Sat, 25 Feb 2017 14:25:12 GMT): blackskygg (Sat, 25 Feb 2017 14:28:39 GMT): blackskygg (Sat, 25 Feb 2017 14:30:47 GMT): itamar-m (Sat, 25 Feb 2017 15:05:39 GMT): cdaughtr (Sat, 25 Feb 2017 15:33:58 GMT): cdaughtr (Sat, 25 Feb 2017 15:33:58 GMT): cdaughtr (Sat, 25 Feb 2017 15:33:58 GMT): markparz (Sat, 25 Feb 2017 16:01:59 GMT): markparz (Sat, 25 Feb 2017 16:02:13 GMT): simsc (Sat, 25 Feb 2017 16:02:13 GMT): lehors (Sat, 25 Feb 2017 16:16:08 GMT): lehors (Sat, 25 Feb 2017 16:17:45 GMT): lehors (Sat, 25 Feb 2017 16:17:54 GMT): lehors (Sat, 25 Feb 2017 16:18:15 GMT): lehors (Sat, 25 Feb 2017 16:18:15 GMT): lehors (Sat, 25 Feb 2017 16:19:00 GMT): lehors (Sat, 25 Feb 2017 16:21:31 GMT): markparz (Sat, 25 Feb 2017 16:28:34 GMT): WilliamSparks (Sat, 25 Feb 2017 19:12:03 GMT): WilliamSparks (Sat, 25 Feb 2017 19:17:33 GMT): WilliamSparks (Sat, 25 Feb 2017 19:33:46 GMT): vdods (Sat, 25 Feb 2017 20:44:07 GMT): KillianTobin (Sat, 25 Feb 2017 21:06:51 GMT): greg.haskins (Sat, 25 Feb 2017 21:36:51 GMT): greg.haskins (Sat, 25 Feb 2017 21:37:34 GMT): vdods (Sat, 25 Feb 2017 21:38:02 GMT): tennenjl (Sat, 25 Feb 2017 22:31:23 GMT): vdods (Sat, 25 Feb 2017 22:36:50 GMT): vdods (Sat, 25 Feb 2017 22:37:23 GMT): tennenjl (Sat, 25 Feb 2017 22:43:07 GMT): vdods (Sat, 25 Feb 2017 22:45:54 GMT): weeds (Sat, 25 Feb 2017 22:47:04 GMT): weeds (Sat, 25 Feb 2017 22:47:47 GMT): tennenjl (Sat, 25 Feb 2017 22:56:16 GMT): tennenjl (Sat, 25 Feb 2017 22:59:35 GMT): dave.enyeart (Sun, 26 Feb 2017 02:31:14 GMT): weeds (Sun, 26 Feb 2017 03:04:19 GMT): weeds (Sun, 26 Feb 2017 03:04:55 GMT): weeds (Sun, 26 Feb 2017 03:04:59 GMT): weeds (Sun, 26 Feb 2017 03:06:01 GMT): bh4rtp (Sun, 26 Feb 2017 03:06:50 GMT): bh4rtp (Sun, 26 Feb 2017 03:09:28 GMT): bh4rtp (Sun, 26 Feb 2017 03:11:14 GMT): tuand (Sun, 26 Feb 2017 03:21:36 GMT): tuand (Sun, 26 Feb 2017 03:22:33 GMT): bh4rtp (Sun, 26 Feb 2017 03:25:54 GMT): rrader (Sun, 26 Feb 2017 10:16:07 GMT): mastersingh24 (Sun, 26 Feb 2017 13:15:46 GMT): Manikanda Gunasekaran (Sun, 26 Feb 2017 13:18:00 GMT): rrader (Sun, 26 Feb 2017 13:32:46 GMT): bh4rtp (Sun, 26 Feb 2017 14:35:44 GMT): tuand (Sun, 26 Feb 2017 14:48:36 GMT): tennenjl (Sun, 26 Feb 2017 18:36:29 GMT): nitingaur (Sun, 26 Feb 2017 20:46:40 GMT): nitingaur (Mon, 27 Feb 2017 01:57:18 GMT): tennenjl (Mon, 27 Feb 2017 02:01:10 GMT): zerppen (Mon, 27 Feb 2017 02:32:32 GMT): zerppen (Mon, 27 Feb 2017 02:32:32 GMT): rrader (Mon, 27 Feb 2017 06:59:42 GMT): raghavsood (Mon, 27 Feb 2017 07:00:29 GMT): raghavsood (Mon, 27 Feb 2017 07:00:29 GMT): zerppen (Mon, 27 Feb 2017 07:52:34 GMT): bh4rtp (Mon, 27 Feb 2017 09:46:50 GMT): yacovm (Mon, 27 Feb 2017 09:50:44 GMT): bh4rtp (Mon, 27 Feb 2017 10:11:55 GMT): yacovm (Mon, 27 Feb 2017 10:26:38 GMT): bh4rtp (Mon, 27 Feb 2017 11:28:22 GMT): sitomani (Mon, 27 Feb 2017 11:44:36 GMT): bh4rtp (Mon, 27 Feb 2017 11:46:13 GMT): yacovm (Mon, 27 Feb 2017 11:57:23 GMT): bh4rtp (Mon, 27 Feb 2017 12:43:43 GMT): yacovm (Mon, 27 Feb 2017 13:25:40 GMT): hshimo (Mon, 27 Feb 2017 13:38:06 GMT): weeds (Mon, 27 Feb 2017 13:38:54 GMT): joshhus (Mon, 27 Feb 2017 13:38:54 GMT): hshimo (Mon, 27 Feb 2017 13:40:26 GMT): hshimo (Mon, 27 Feb 2017 13:42:23 GMT): bh4rtp (Mon, 27 Feb 2017 13:52:51 GMT): yacovm (Mon, 27 Feb 2017 13:53:28 GMT): yacovm (Mon, 27 Feb 2017 13:53:28 GMT): bh4rtp (Mon, 27 Feb 2017 14:04:32 GMT): sloveland (Mon, 27 Feb 2017 16:00:28 GMT): kletkeman (Mon, 27 Feb 2017 16:20:00 GMT): kletkeman (Mon, 27 Feb 2017 16:21:43 GMT): medtech.venkat@gmail.com (Mon, 27 Feb 2017 18:58:53 GMT): greg.haskins (Mon, 27 Feb 2017 21:31:25 GMT): greg.haskins (Mon, 27 Feb 2017 21:31:32 GMT): mastersingh24 (Mon, 27 Feb 2017 21:42:27 GMT): greg.haskins (Mon, 27 Feb 2017 21:42:57 GMT): greg.haskins (Mon, 27 Feb 2017 21:43:10 GMT): yacovm (Mon, 27 Feb 2017 21:43:12 GMT): yacovm (Mon, 27 Feb 2017 21:43:34 GMT): greg.haskins (Mon, 27 Feb 2017 21:43:46 GMT): yacovm (Mon, 27 Feb 2017 21:43:55 GMT): greg.haskins (Mon, 27 Feb 2017 21:44:04 GMT): greg.haskins (Mon, 27 Feb 2017 21:44:16 GMT): greg.haskins (Mon, 27 Feb 2017 21:44:59 GMT): greg.haskins (Mon, 27 Feb 2017 21:45:09 GMT): greg.haskins (Mon, 27 Feb 2017 21:45:25 GMT): greg.haskins (Mon, 27 Feb 2017 21:45:54 GMT): muralisr (Mon, 27 Feb 2017 21:46:32 GMT): mastersingh24 (Mon, 27 Feb 2017 21:46:36 GMT): greg.haskins (Mon, 27 Feb 2017 21:47:06 GMT): muralisr (Mon, 27 Feb 2017 21:47:12 GMT): greg.haskins (Mon, 27 Feb 2017 21:47:31 GMT): greg.haskins (Mon, 27 Feb 2017 21:47:36 GMT): muralisr (Mon, 27 Feb 2017 21:47:41 GMT): muralisr (Mon, 27 Feb 2017 21:48:13 GMT): muralisr (Mon, 27 Feb 2017 21:48:27 GMT): muralisr (Mon, 27 Feb 2017 21:49:26 GMT): muralisr (Mon, 27 Feb 2017 21:49:39 GMT): greg.haskins (Mon, 27 Feb 2017 21:49:51 GMT): muralisr (Mon, 27 Feb 2017 21:50:03 GMT): muralisr (Mon, 27 Feb 2017 21:50:18 GMT): greg.haskins (Mon, 27 Feb 2017 21:50:21 GMT): muralisr (Mon, 27 Feb 2017 21:51:19 GMT): greg.haskins (Mon, 27 Feb 2017 21:51:29 GMT): mastersingh24 (Mon, 27 Feb 2017 21:51:46 GMT): greg.haskins (Mon, 27 Feb 2017 21:52:04 GMT): jimthematrix (Mon, 27 Feb 2017 21:52:08 GMT): jimthematrix (Mon, 27 Feb 2017 21:52:23 GMT): jimthematrix (Mon, 27 Feb 2017 21:52:50 GMT): mastersingh24 (Mon, 27 Feb 2017 21:52:58 GMT): jimthematrix (Mon, 27 Feb 2017 21:53:11 GMT): jimthematrix (Mon, 27 Feb 2017 21:53:18 GMT): jimthematrix (Mon, 27 Feb 2017 21:55:49 GMT): greg.haskins (Mon, 27 Feb 2017 21:56:11 GMT): greg.haskins (Mon, 27 Feb 2017 21:56:19 GMT): greg.haskins (Mon, 27 Feb 2017 21:56:23 GMT): bh4rtp (Tue, 28 Feb 2017 00:44:59 GMT): baohua (Tue, 28 Feb 2017 02:04:44 GMT): baohua (Tue, 28 Feb 2017 02:04:50 GMT): DuongNguyen1 (Tue, 28 Feb 2017 03:21:22 GMT): bh4rtp (Tue, 28 Feb 2017 03:44:35 GMT): Ying (Tue, 28 Feb 2017 03:49:28 GMT): bh4rtp (Tue, 28 Feb 2017 03:53:43 GMT): bh4rtp (Tue, 28 Feb 2017 04:08:45 GMT): tianyalangzi (Tue, 28 Feb 2017 04:57:16 GMT): warm3snow (Tue, 28 Feb 2017 06:01:59 GMT): warm3snow (Tue, 28 Feb 2017 06:02:53 GMT): bh4rtp (Tue, 28 Feb 2017 06:08:04 GMT): levinkwong (Tue, 28 Feb 2017 06:11:13 GMT): levinkwong (Tue, 28 Feb 2017 06:11:13 GMT): CsterKuroi (Tue, 28 Feb 2017 06:27:35 GMT): warm3snow (Tue, 28 Feb 2017 07:17:38 GMT): nvlasov (Tue, 28 Feb 2017 07:18:55 GMT): saridsa1 (Tue, 28 Feb 2017 09:26:35 GMT): saridsa1 (Tue, 28 Feb 2017 09:26:35 GMT): saridsa1 (Tue, 28 Feb 2017 09:26:35 GMT): saridsa1 (Tue, 28 Feb 2017 09:26:35 GMT): miika (Tue, 28 Feb 2017 09:27:36 GMT): gatakka (Tue, 28 Feb 2017 09:29:47 GMT): saridsa1 (Tue, 28 Feb 2017 09:30:57 GMT): gatakka (Tue, 28 Feb 2017 09:31:17 GMT): gatakka (Tue, 28 Feb 2017 09:31:35 GMT): saridsa1 (Tue, 28 Feb 2017 09:31:42 GMT): gatakka (Tue, 28 Feb 2017 09:31:55 GMT): gatakka (Tue, 28 Feb 2017 09:31:56 GMT): gatakka (Tue, 28 Feb 2017 09:32:31 GMT): gatakka (Tue, 28 Feb 2017 09:32:46 GMT): gatakka (Tue, 28 Feb 2017 09:33:10 GMT): gatakka (Tue, 28 Feb 2017 09:33:28 GMT): gatakka (Tue, 28 Feb 2017 09:39:55 GMT): gatakka (Tue, 28 Feb 2017 09:39:55 GMT): gatakka (Tue, 28 Feb 2017 09:40:22 GMT): saridsa1 (Tue, 28 Feb 2017 09:41:59 GMT): gatakka (Tue, 28 Feb 2017 09:42:45 GMT): saridsa1 (Tue, 28 Feb 2017 09:43:43 GMT): saridsa1 (Tue, 28 Feb 2017 09:47:18 GMT): gatakka (Tue, 28 Feb 2017 09:47:54 GMT): gatakka (Tue, 28 Feb 2017 09:49:06 GMT): saridsa1 (Tue, 28 Feb 2017 09:59:32 GMT): stchrysa (Tue, 28 Feb 2017 10:00:23 GMT): rickr (Tue, 28 Feb 2017 12:46:45 GMT): rickr (Tue, 28 Feb 2017 12:46:45 GMT): muralisr (Tue, 28 Feb 2017 13:56:43 GMT): jansony1 (Tue, 28 Feb 2017 15:04:25 GMT): saridsa1 (Tue, 28 Feb 2017 16:37:46 GMT): kletkeman (Tue, 28 Feb 2017 16:39:47 GMT): kletkeman (Tue, 28 Feb 2017 16:40:39 GMT): greg.haskins (Tue, 28 Feb 2017 17:32:58 GMT): greg.haskins (Tue, 28 Feb 2017 17:33:04 GMT): greg.haskins (Tue, 28 Feb 2017 17:33:20 GMT): greg.haskins (Tue, 28 Feb 2017 17:33:39 GMT): greg.haskins (Tue, 28 Feb 2017 17:35:27 GMT): greg.haskins (Tue, 28 Feb 2017 17:35:42 GMT): greg.haskins (Tue, 28 Feb 2017 17:36:12 GMT): greg.haskins (Tue, 28 Feb 2017 17:56:02 GMT): greg.haskins (Tue, 28 Feb 2017 17:56:08 GMT): greg.haskins (Tue, 28 Feb 2017 17:56:30 GMT): rjones (Tue, 28 Feb 2017 18:00:11 GMT): sstone1 (Tue, 28 Feb 2017 18:01:45 GMT): rjones (Tue, 28 Feb 2017 18:04:28 GMT): mrkiouak (Tue, 28 Feb 2017 18:06:32 GMT): david.stark (Tue, 28 Feb 2017 18:24:37 GMT): muralisr (Tue, 28 Feb 2017 18:48:37 GMT): rrader (Tue, 28 Feb 2017 18:49:56 GMT): kostas (Tue, 28 Feb 2017 19:39:15 GMT): pschnap (Tue, 28 Feb 2017 20:03:44 GMT): pschnap (Tue, 28 Feb 2017 20:05:25 GMT): pschnap (Tue, 28 Feb 2017 20:05:25 GMT): greg.haskins (Tue, 28 Feb 2017 20:15:37 GMT): jeroiraz (Tue, 28 Feb 2017 20:17:18 GMT): bretharrison (Tue, 28 Feb 2017 20:25:56 GMT): wlahti (Tue, 28 Feb 2017 20:29:47 GMT): wlahti (Tue, 28 Feb 2017 20:29:47 GMT): pschnap (Tue, 28 Feb 2017 20:34:48 GMT): greg.haskins (Tue, 28 Feb 2017 20:35:45 GMT): greg.haskins (Tue, 28 Feb 2017 20:35:46 GMT): greg.haskins (Tue, 28 Feb 2017 20:35:54 GMT): pschnap (Tue, 28 Feb 2017 20:36:14 GMT): greg.haskins (Tue, 28 Feb 2017 20:42:03 GMT): greg.haskins (Tue, 28 Feb 2017 20:42:03 GMT): greg.haskins (Tue, 28 Feb 2017 20:42:10 GMT): greg.haskins (Tue, 28 Feb 2017 20:42:19 GMT): greg.haskins (Tue, 28 Feb 2017 20:42:43 GMT): mastersingh24 (Tue, 28 Feb 2017 20:45:44 GMT): wlahti (Tue, 28 Feb 2017 20:59:43 GMT): greg.haskins (Tue, 28 Feb 2017 21:19:21 GMT): greg.haskins (Tue, 28 Feb 2017 21:20:12 GMT): greg.haskins (Tue, 28 Feb 2017 21:20:21 GMT): RyanElliott (Tue, 28 Feb 2017 22:50:11 GMT): snowy13 (Tue, 28 Feb 2017 23:00:35 GMT): connectio (Wed, 01 Mar 2017 00:34:34 GMT): Hangyu (Wed, 01 Mar 2017 01:39:01 GMT): greg.haskins (Wed, 01 Mar 2017 01:58:40 GMT): greg.haskins (Wed, 01 Mar 2017 01:58:51 GMT): greg.haskins (Wed, 01 Mar 2017 01:59:09 GMT): greg.haskins (Wed, 01 Mar 2017 01:59:16 GMT): RyanElliott (Wed, 01 Mar 2017 01:59:24 GMT): RyanElliott (Wed, 01 Mar 2017 01:59:26 GMT): greg.haskins (Wed, 01 Mar 2017 01:59:41 GMT): greg.haskins (Wed, 01 Mar 2017 01:59:49 GMT): RyanElliott (Wed, 01 Mar 2017 02:00:02 GMT): greg.haskins (Wed, 01 Mar 2017 02:00:17 GMT): greg.haskins (Wed, 01 Mar 2017 02:00:30 GMT): greg.haskins (Wed, 01 Mar 2017 02:00:39 GMT): greg.haskins (Wed, 01 Mar 2017 02:00:52 GMT): greg.haskins (Wed, 01 Mar 2017 02:01:04 GMT): greg.haskins (Wed, 01 Mar 2017 02:01:41 GMT): greg.haskins (Wed, 01 Mar 2017 02:03:52 GMT): RyanElliott (Wed, 01 Mar 2017 02:04:06 GMT): greg.haskins (Wed, 01 Mar 2017 02:06:42 GMT): levinkwong (Wed, 01 Mar 2017 02:08:31 GMT): jansony1 (Wed, 01 Mar 2017 02:08:40 GMT): RyanElliott (Wed, 01 Mar 2017 02:11:02 GMT): jansony1 (Wed, 01 Mar 2017 02:13:17 GMT): greg.haskins (Wed, 01 Mar 2017 02:16:38 GMT): greg.haskins (Wed, 01 Mar 2017 02:17:08 GMT): greg.haskins (Wed, 01 Mar 2017 02:17:22 GMT): RyanElliott (Wed, 01 Mar 2017 02:18:51 GMT): jansony1 (Wed, 01 Mar 2017 02:19:24 GMT): greg.haskins (Wed, 01 Mar 2017 02:19:56 GMT): nvlasov (Wed, 01 Mar 2017 02:20:15 GMT): greg.haskins (Wed, 01 Mar 2017 02:20:18 GMT): greg.haskins (Wed, 01 Mar 2017 02:20:23 GMT): greg.haskins (Wed, 01 Mar 2017 02:20:57 GMT): RyanElliott (Wed, 01 Mar 2017 02:21:07 GMT): greg.haskins (Wed, 01 Mar 2017 02:21:22 GMT): greg.haskins (Wed, 01 Mar 2017 02:21:59 GMT): greg.haskins (Wed, 01 Mar 2017 02:22:15 GMT): greg.haskins (Wed, 01 Mar 2017 02:23:10 GMT): greg.haskins (Wed, 01 Mar 2017 02:23:37 GMT): greg.haskins (Wed, 01 Mar 2017 02:23:45 GMT): greg.haskins (Wed, 01 Mar 2017 02:24:17 GMT): RyanElliott (Wed, 01 Mar 2017 02:31:00 GMT): greg.haskins (Wed, 01 Mar 2017 02:31:16 GMT): RyanElliott (Wed, 01 Mar 2017 02:32:08 GMT): jansony1 (Wed, 01 Mar 2017 02:39:54 GMT): greg.haskins (Wed, 01 Mar 2017 02:40:18 GMT): greg.haskins (Wed, 01 Mar 2017 02:40:22 GMT): jansony1 (Wed, 01 Mar 2017 02:41:03 GMT): greg.haskins (Wed, 01 Mar 2017 02:41:24 GMT): greg.haskins (Wed, 01 Mar 2017 02:41:34 GMT): greg.haskins (Wed, 01 Mar 2017 02:41:51 GMT): greg.haskins (Wed, 01 Mar 2017 02:42:23 GMT): greg.haskins (Wed, 01 Mar 2017 02:42:38 GMT): greg.haskins (Wed, 01 Mar 2017 02:42:46 GMT): greg.haskins (Wed, 01 Mar 2017 02:43:42 GMT): greg.haskins (Wed, 01 Mar 2017 02:47:39 GMT): jansony1 (Wed, 01 Mar 2017 02:49:42 GMT): jansony1 (Wed, 01 Mar 2017 02:50:56 GMT): DuongNguyen1 (Wed, 01 Mar 2017 03:17:48 GMT): saridsa1 (Wed, 01 Mar 2017 04:21:43 GMT): saridsa1 (Wed, 01 Mar 2017 04:26:19 GMT): saridsa1 (Wed, 01 Mar 2017 04:26:19 GMT): snehas (Wed, 01 Mar 2017 06:18:17 GMT): XinMei (Wed, 01 Mar 2017 06:26:22 GMT): zwsyjj (Wed, 01 Mar 2017 06:42:19 GMT): dave.enyeart (Wed, 01 Mar 2017 06:57:30 GMT): dave.enyeart (Wed, 01 Mar 2017 06:58:43 GMT): Sky (Wed, 01 Mar 2017 07:27:01 GMT): levinkwong (Wed, 01 Mar 2017 07:27:11 GMT): ibmamnt (Wed, 01 Mar 2017 07:36:27 GMT): levinkwong (Wed, 01 Mar 2017 07:41:16 GMT): ibmamnt (Wed, 01 Mar 2017 08:46:45 GMT): conroydave (Wed, 01 Mar 2017 08:57:31 GMT): DeeptiSingh (Wed, 01 Mar 2017 09:55:36 GMT): antitoine (Wed, 01 Mar 2017 10:39:04 GMT): SyneBlockChainTeam (Wed, 01 Mar 2017 11:40:18 GMT): isparkes (Wed, 01 Mar 2017 11:47:00 GMT): saridsa1 (Wed, 01 Mar 2017 12:07:10 GMT): gatakka (Wed, 01 Mar 2017 12:24:53 GMT): gatakka (Wed, 01 Mar 2017 12:24:53 GMT): wheelsinar (Wed, 01 Mar 2017 13:26:11 GMT): ScottRoberts (Wed, 01 Mar 2017 14:35:39 GMT): AVerevkin (Wed, 01 Mar 2017 14:35:39 GMT): jeffreypicard (Wed, 01 Mar 2017 15:11:11 GMT): jeffreypicard (Wed, 01 Mar 2017 15:20:04 GMT): jeffreypicard (Wed, 01 Mar 2017 15:20:46 GMT): greg.haskins (Wed, 01 Mar 2017 15:29:33 GMT): greg.haskins (Wed, 01 Mar 2017 15:29:41 GMT): greg.haskins (Wed, 01 Mar 2017 15:30:16 GMT): greg.haskins (Wed, 01 Mar 2017 15:30:17 GMT): greg.haskins (Wed, 01 Mar 2017 15:30:29 GMT): greg.haskins (Wed, 01 Mar 2017 15:30:47 GMT): jeffreypicard (Wed, 01 Mar 2017 15:31:04 GMT): greg.haskins (Wed, 01 Mar 2017 15:31:35 GMT): awalias (Wed, 01 Mar 2017 16:04:31 GMT): jeffreypicard (Wed, 01 Mar 2017 16:16:31 GMT): jeffreypicard (Wed, 01 Mar 2017 16:17:06 GMT): mohamoud.egal (Wed, 01 Mar 2017 17:07:32 GMT): mohamoud.egal (Wed, 01 Mar 2017 17:07:51 GMT): mohamoud.egal (Wed, 01 Mar 2017 17:08:41 GMT): mohamoud.egal (Wed, 01 Mar 2017 17:20:48 GMT): conroydave (Wed, 01 Mar 2017 18:01:43 GMT): conroydave (Wed, 01 Mar 2017 18:01:49 GMT): conroydave (Wed, 01 Mar 2017 18:01:55 GMT): conroydave (Wed, 01 Mar 2017 18:01:59 GMT): dselman (Wed, 01 Mar 2017 18:32:47 GMT): bkvellanki (Wed, 01 Mar 2017 20:14:44 GMT): DavidVorick (Wed, 01 Mar 2017 20:45:48 GMT): craftfortress (Wed, 01 Mar 2017 20:49:41 GMT): craftfortress (Wed, 01 Mar 2017 20:49:45 GMT): bkvellanki (Wed, 01 Mar 2017 21:01:44 GMT): bkvellanki (Wed, 01 Mar 2017 21:10:48 GMT): benjaminbollen (Wed, 01 Mar 2017 21:14:10 GMT): cgrecu (Wed, 01 Mar 2017 21:41:03 GMT): rameshthoomu (Wed, 01 Mar 2017 21:41:30 GMT): bkvellanki (Wed, 01 Mar 2017 21:42:18 GMT): rameshthoomu (Wed, 01 Mar 2017 21:42:36 GMT): pd93 (Wed, 01 Mar 2017 21:47:58 GMT): conroydave (Wed, 01 Mar 2017 22:29:08 GMT): samwood (Wed, 01 Mar 2017 22:35:54 GMT): kletkeman (Thu, 02 Mar 2017 02:24:00 GMT): kletkeman (Thu, 02 Mar 2017 02:24:32 GMT): kletkeman (Thu, 02 Mar 2017 02:25:03 GMT): greg.haskins (Thu, 02 Mar 2017 02:25:30 GMT): raghavsood (Thu, 02 Mar 2017 02:25:39 GMT): greg.haskins (Thu, 02 Mar 2017 02:25:44 GMT): raghavsood (Thu, 02 Mar 2017 02:25:58 GMT): kletkeman (Thu, 02 Mar 2017 02:26:47 GMT): raghavsood (Thu, 02 Mar 2017 02:27:16 GMT): greg.haskins (Thu, 02 Mar 2017 02:27:26 GMT): kletkeman (Thu, 02 Mar 2017 02:27:40 GMT): greg.haskins (Thu, 02 Mar 2017 02:27:56 GMT): greg.haskins (Thu, 02 Mar 2017 02:28:01 GMT): greg.haskins (Thu, 02 Mar 2017 02:28:23 GMT): kletkeman (Thu, 02 Mar 2017 02:28:24 GMT): greg.haskins (Thu, 02 Mar 2017 02:28:56 GMT): kletkeman (Thu, 02 Mar 2017 02:29:02 GMT): kletkeman (Thu, 02 Mar 2017 02:30:10 GMT): raghavsood (Thu, 02 Mar 2017 02:30:28 GMT): greg.haskins (Thu, 02 Mar 2017 02:30:38 GMT): kletkeman (Thu, 02 Mar 2017 02:30:53 GMT): kletkeman (Thu, 02 Mar 2017 02:31:07 GMT): kletkeman (Thu, 02 Mar 2017 02:31:15 GMT): greg.haskins (Thu, 02 Mar 2017 02:31:17 GMT): kletkeman (Thu, 02 Mar 2017 02:31:36 GMT): greg.haskins (Thu, 02 Mar 2017 02:31:48 GMT): kletkeman (Thu, 02 Mar 2017 02:32:00 GMT): greg.haskins (Thu, 02 Mar 2017 02:32:10 GMT): kletkeman (Thu, 02 Mar 2017 02:32:22 GMT): greg.haskins (Thu, 02 Mar 2017 02:32:30 GMT): kletkeman (Thu, 02 Mar 2017 02:32:30 GMT): kletkeman (Thu, 02 Mar 2017 02:32:47 GMT): kletkeman (Thu, 02 Mar 2017 02:32:55 GMT): greg.haskins (Thu, 02 Mar 2017 02:32:59 GMT): greg.haskins (Thu, 02 Mar 2017 02:33:14 GMT): greg.haskins (Thu, 02 Mar 2017 02:33:28 GMT): greg.haskins (Thu, 02 Mar 2017 02:33:40 GMT): greg.haskins (Thu, 02 Mar 2017 02:33:53 GMT): greg.haskins (Thu, 02 Mar 2017 02:34:04 GMT): kletkeman (Thu, 02 Mar 2017 02:35:12 GMT): kletkeman (Thu, 02 Mar 2017 02:35:23 GMT): greg.haskins (Thu, 02 Mar 2017 02:35:26 GMT): greg.haskins (Thu, 02 Mar 2017 02:35:37 GMT): kletkeman (Thu, 02 Mar 2017 02:35:41 GMT): greg.haskins (Thu, 02 Mar 2017 02:35:49 GMT): kletkeman (Thu, 02 Mar 2017 02:36:23 GMT): kletkeman (Thu, 02 Mar 2017 02:48:50 GMT): greg.haskins (Thu, 02 Mar 2017 02:51:57 GMT): kletkeman (Thu, 02 Mar 2017 02:54:00 GMT): kletkeman (Thu, 02 Mar 2017 02:54:44 GMT): Liew.SC (Thu, 02 Mar 2017 02:56:59 GMT): jasoncodingnow (Thu, 02 Mar 2017 02:57:14 GMT): kletkeman (Thu, 02 Mar 2017 02:59:47 GMT): conroydave (Thu, 02 Mar 2017 03:05:50 GMT): greg.haskins (Thu, 02 Mar 2017 03:06:31 GMT): greg.haskins (Thu, 02 Mar 2017 03:06:31 GMT): kletkeman (Thu, 02 Mar 2017 03:11:50 GMT): greg.haskins (Thu, 02 Mar 2017 03:12:16 GMT): kletkeman (Thu, 02 Mar 2017 03:12:24 GMT): greg.haskins (Thu, 02 Mar 2017 03:12:27 GMT): kletkeman (Thu, 02 Mar 2017 03:12:31 GMT): greg.haskins (Thu, 02 Mar 2017 03:12:59 GMT): kletkeman (Thu, 02 Mar 2017 03:13:00 GMT): greg.haskins (Thu, 02 Mar 2017 03:13:11 GMT): kletkeman (Thu, 02 Mar 2017 03:13:33 GMT): kletkeman (Thu, 02 Mar 2017 03:13:43 GMT): sameerreddy13 (Thu, 02 Mar 2017 03:14:02 GMT): kletkeman (Thu, 02 Mar 2017 03:14:50 GMT): kletkeman (Thu, 02 Mar 2017 03:15:29 GMT): conroydave (Thu, 02 Mar 2017 03:17:06 GMT): kletkeman (Thu, 02 Mar 2017 03:18:47 GMT): conroydave (Thu, 02 Mar 2017 03:19:02 GMT): conroydave (Thu, 02 Mar 2017 03:19:36 GMT): kletkeman (Thu, 02 Mar 2017 03:21:14 GMT): kletkeman (Thu, 02 Mar 2017 03:21:53 GMT): kletkeman (Thu, 02 Mar 2017 03:23:29 GMT): kletkeman (Thu, 02 Mar 2017 03:23:35 GMT): conroydave (Thu, 02 Mar 2017 03:30:27 GMT): conroydave (Thu, 02 Mar 2017 03:32:41 GMT): conroydave (Thu, 02 Mar 2017 03:33:53 GMT): kletkeman (Thu, 02 Mar 2017 04:23:58 GMT): vu3mmg (Thu, 02 Mar 2017 06:15:48 GMT): vu3mmg (Thu, 02 Mar 2017 06:16:40 GMT): qasimhbti (Thu, 02 Mar 2017 07:17:27 GMT): hanhzf (Thu, 02 Mar 2017 07:28:01 GMT): WeiHu (Thu, 02 Mar 2017 07:29:19 GMT): hanhzf (Thu, 02 Mar 2017 07:29:45 GMT): hanhzf (Thu, 02 Mar 2017 07:34:40 GMT): hanhzf (Thu, 02 Mar 2017 07:35:08 GMT): gatakka (Thu, 02 Mar 2017 07:41:54 GMT): hanhzf (Thu, 02 Mar 2017 07:42:42 GMT): hanhzf (Thu, 02 Mar 2017 07:46:03 GMT): gatakka (Thu, 02 Mar 2017 07:48:01 GMT): zerppen (Thu, 02 Mar 2017 07:53:24 GMT): sajz (Thu, 02 Mar 2017 08:32:20 GMT): sajz (Thu, 02 Mar 2017 08:32:29 GMT): sajz (Thu, 02 Mar 2017 08:36:04 GMT): sajz (Thu, 02 Mar 2017 08:40:28 GMT): sajz (Thu, 02 Mar 2017 08:40:28 GMT): sajz (Thu, 02 Mar 2017 08:40:28 GMT): sajz (Thu, 02 Mar 2017 08:40:28 GMT): sajz (Thu, 02 Mar 2017 08:40:28 GMT): kletkeman (Thu, 02 Mar 2017 13:23:29 GMT): cgrecu (Thu, 02 Mar 2017 13:25:32 GMT): kletkeman (Thu, 02 Mar 2017 13:26:41 GMT): jwolpert (Thu, 02 Mar 2017 15:14:16 GMT): binhn (Thu, 02 Mar 2017 15:41:52 GMT): john.d.sheehan (Thu, 02 Mar 2017 15:44:34 GMT): Vadim (Thu, 02 Mar 2017 15:49:48 GMT): john.d.sheehan (Thu, 02 Mar 2017 15:51:50 GMT): john.d.sheehan (Thu, 02 Mar 2017 15:52:51 GMT): Vadim (Thu, 02 Mar 2017 15:53:29 GMT): john.d.sheehan (Thu, 02 Mar 2017 15:54:25 GMT): Vadim (Thu, 02 Mar 2017 15:55:43 GMT): Vadim (Thu, 02 Mar 2017 15:57:16 GMT): john.d.sheehan (Thu, 02 Mar 2017 16:04:38 GMT): kletkeman (Thu, 02 Mar 2017 17:06:47 GMT): bkvellanki (Thu, 02 Mar 2017 19:42:18 GMT): bkvellanki (Thu, 02 Mar 2017 19:42:54 GMT): bkvellanki (Thu, 02 Mar 2017 19:43:53 GMT): bkvellanki (Thu, 02 Mar 2017 19:44:27 GMT): bkvellanki (Thu, 02 Mar 2017 19:45:33 GMT): bkvellanki (Thu, 02 Mar 2017 19:46:22 GMT): cbf (Thu, 02 Mar 2017 20:06:07 GMT): kletkeman (Thu, 02 Mar 2017 20:23:15 GMT): tennenjl (Thu, 02 Mar 2017 21:05:17 GMT): hartm (Thu, 02 Mar 2017 22:58:59 GMT): Willson (Fri, 03 Mar 2017 01:39:12 GMT): Willson (Fri, 03 Mar 2017 02:05:26 GMT): Willson (Fri, 03 Mar 2017 02:07:53 GMT): Hangyu (Fri, 03 Mar 2017 02:41:59 GMT): weeds (Fri, 03 Mar 2017 03:00:22 GMT): weeds (Fri, 03 Mar 2017 03:00:56 GMT): weeds (Fri, 03 Mar 2017 03:01:19 GMT): weeds (Fri, 03 Mar 2017 03:02:20 GMT): weeds (Fri, 03 Mar 2017 03:05:15 GMT): weeds (Fri, 03 Mar 2017 03:12:00 GMT): jimthematrix (Fri, 03 Mar 2017 03:12:07 GMT): jimthematrix (Fri, 03 Mar 2017 03:12:48 GMT): jimthematrix (Fri, 03 Mar 2017 03:14:46 GMT): jimthematrix (Fri, 03 Mar 2017 03:17:51 GMT): yong (Fri, 03 Mar 2017 03:21:08 GMT): yong (Fri, 03 Mar 2017 03:21:39 GMT): yong (Fri, 03 Mar 2017 03:21:51 GMT): jimthematrix (Fri, 03 Mar 2017 03:23:18 GMT): jimthematrix (Fri, 03 Mar 2017 03:23:31 GMT): yong (Fri, 03 Mar 2017 03:23:56 GMT): harsha (Fri, 03 Mar 2017 04:05:44 GMT): harsha (Fri, 03 Mar 2017 04:05:44 GMT): hanhzf (Fri, 03 Mar 2017 04:39:49 GMT): yong (Fri, 03 Mar 2017 05:38:00 GMT): guoger (Fri, 03 Mar 2017 06:12:52 GMT): guoger (Fri, 03 Mar 2017 06:13:09 GMT): harsha (Fri, 03 Mar 2017 07:01:06 GMT): yong (Fri, 03 Mar 2017 07:04:38 GMT): liuzhudong (Fri, 03 Mar 2017 07:26:02 GMT): levinkwong (Fri, 03 Mar 2017 08:42:10 GMT): Vadim (Fri, 03 Mar 2017 08:48:18 GMT): levinkwong (Fri, 03 Mar 2017 08:49:31 GMT): Vadim (Fri, 03 Mar 2017 08:49:46 GMT): levinkwong (Fri, 03 Mar 2017 08:50:13 GMT): levinkwong (Fri, 03 Mar 2017 09:00:10 GMT): Vadim (Fri, 03 Mar 2017 09:02:10 GMT): levinkwong (Fri, 03 Mar 2017 09:07:31 GMT): levinkwong (Fri, 03 Mar 2017 09:07:49 GMT): Vadim (Fri, 03 Mar 2017 09:16:44 GMT): Vadim (Fri, 03 Mar 2017 09:17:49 GMT): levinkwong (Fri, 03 Mar 2017 09:22:24 GMT): Vadim (Fri, 03 Mar 2017 09:23:18 GMT): levinkwong (Fri, 03 Mar 2017 09:23:49 GMT): Vadim (Fri, 03 Mar 2017 09:24:15 GMT): Vadim (Fri, 03 Mar 2017 09:24:34 GMT): Vadim (Fri, 03 Mar 2017 09:24:41 GMT): Vadim (Fri, 03 Mar 2017 09:24:53 GMT): levinkwong (Fri, 03 Mar 2017 09:25:24 GMT): levinkwong (Fri, 03 Mar 2017 09:26:04 GMT): Vadim (Fri, 03 Mar 2017 09:26:15 GMT): Vadim (Fri, 03 Mar 2017 09:26:42 GMT): mffrench (Fri, 03 Mar 2017 09:27:25 GMT): levinkwong (Fri, 03 Mar 2017 09:28:06 GMT): Vadim (Fri, 03 Mar 2017 09:28:48 GMT): Vadim (Fri, 03 Mar 2017 09:35:25 GMT): DannyWong (Fri, 03 Mar 2017 09:35:59 GMT): levinkwong (Fri, 03 Mar 2017 09:40:23 GMT): pd93 (Fri, 03 Mar 2017 11:02:51 GMT): pd93 (Fri, 03 Mar 2017 11:02:51 GMT): mnarayan (Fri, 03 Mar 2017 11:36:17 GMT): mffrench (Fri, 03 Mar 2017 13:26:41 GMT): mffrench (Fri, 03 Mar 2017 13:27:55 GMT): mffrench (Fri, 03 Mar 2017 13:28:57 GMT): mffrench (Fri, 03 Mar 2017 13:45:22 GMT): rrader (Fri, 03 Mar 2017 13:46:42 GMT): rrader (Fri, 03 Mar 2017 13:46:42 GMT): Vadim (Fri, 03 Mar 2017 13:47:34 GMT): Vadim (Fri, 03 Mar 2017 13:47:34 GMT): rrader (Fri, 03 Mar 2017 13:49:18 GMT): john.d.sheehan (Fri, 03 Mar 2017 14:14:30 GMT): weeds (Fri, 03 Mar 2017 14:16:44 GMT): weeds (Fri, 03 Mar 2017 14:17:01 GMT): weeds (Fri, 03 Mar 2017 14:18:34 GMT): Vadim (Fri, 03 Mar 2017 14:19:34 GMT): weeds (Fri, 03 Mar 2017 14:20:07 GMT): weeds (Fri, 03 Mar 2017 14:20:20 GMT): weeds (Fri, 03 Mar 2017 14:20:47 GMT): Vadim (Fri, 03 Mar 2017 14:22:25 GMT): pd93 (Fri, 03 Mar 2017 14:23:26 GMT): pd93 (Fri, 03 Mar 2017 14:23:26 GMT): pd93 (Fri, 03 Mar 2017 14:23:26 GMT): john.d.sheehan (Fri, 03 Mar 2017 14:26:08 GMT): weeds (Fri, 03 Mar 2017 14:27:40 GMT): pd93 (Fri, 03 Mar 2017 14:33:55 GMT): Ratnakar (Fri, 03 Mar 2017 14:36:12 GMT): Ratnakar (Fri, 03 Mar 2017 14:37:48 GMT): Ratnakar (Fri, 03 Mar 2017 14:40:50 GMT): Ratnakar (Fri, 03 Mar 2017 14:41:45 GMT): Ratnakar (Fri, 03 Mar 2017 14:42:26 GMT): pd93 (Fri, 03 Mar 2017 14:43:17 GMT): pd93 (Fri, 03 Mar 2017 14:43:17 GMT): pd93 (Fri, 03 Mar 2017 14:45:28 GMT): Ratnakar (Fri, 03 Mar 2017 14:46:59 GMT): pd93 (Fri, 03 Mar 2017 14:47:39 GMT): pd93 (Fri, 03 Mar 2017 14:47:39 GMT): Ratnakar (Fri, 03 Mar 2017 14:51:05 GMT): pd93 (Fri, 03 Mar 2017 14:54:52 GMT): pd93 (Fri, 03 Mar 2017 14:54:52 GMT): mlishok (Fri, 03 Mar 2017 15:00:52 GMT): kelly_ (Fri, 03 Mar 2017 17:13:04 GMT): forgeRW (Fri, 03 Mar 2017 17:44:57 GMT): rrader (Fri, 03 Mar 2017 18:43:31 GMT): mastersingh24 (Fri, 03 Mar 2017 18:54:11 GMT): mastersingh24 (Fri, 03 Mar 2017 18:54:19 GMT): rrader (Fri, 03 Mar 2017 18:56:31 GMT): rrader (Fri, 03 Mar 2017 19:05:22 GMT): rrader (Fri, 03 Mar 2017 19:05:22 GMT): rrader (Fri, 03 Mar 2017 20:07:45 GMT): weeds (Fri, 03 Mar 2017 20:19:01 GMT): fbenhamo (Sat, 04 Mar 2017 02:50:17 GMT): AlexKim (Sat, 04 Mar 2017 04:53:46 GMT): AlexKim (Sat, 04 Mar 2017 05:00:51 GMT): AlexKim (Sat, 04 Mar 2017 05:00:59 GMT): AlexKim (Sat, 04 Mar 2017 05:01:24 GMT): AlexKim (Sat, 04 Mar 2017 05:01:25 GMT): rrader (Sat, 04 Mar 2017 08:16:11 GMT): yacovm (Sat, 04 Mar 2017 08:23:33 GMT): yacovm (Sat, 04 Mar 2017 08:24:12 GMT): rrader (Sat, 04 Mar 2017 11:51:37 GMT): rickr (Sat, 04 Mar 2017 18:33:52 GMT): yacovm (Sat, 04 Mar 2017 18:39:17 GMT): rickr (Sat, 04 Mar 2017 18:49:42 GMT): rrader (Sat, 04 Mar 2017 19:32:59 GMT): asadhayat (Sat, 04 Mar 2017 22:11:28 GMT): rrader (Sun, 05 Mar 2017 09:21:54 GMT): calin.grecu (Sun, 05 Mar 2017 13:34:01 GMT): kostas (Sun, 05 Mar 2017 14:20:59 GMT): akm4 (Sun, 05 Mar 2017 16:52:40 GMT): jimthematrix (Sun, 05 Mar 2017 18:04:49 GMT): takemiyamakoto (Sun, 05 Mar 2017 18:04:49 GMT): MadhavaReddy (Sun, 05 Mar 2017 18:19:01 GMT): muralisr (Sun, 05 Mar 2017 18:19:49 GMT): muralisr (Sun, 05 Mar 2017 18:20:29 GMT): muralisr (Sun, 05 Mar 2017 18:20:52 GMT): MadhavaReddy (Sun, 05 Mar 2017 18:21:24 GMT): muralisr (Sun, 05 Mar 2017 18:24:22 GMT): muralisr (Sun, 05 Mar 2017 18:25:37 GMT): MadhavaReddy (Sun, 05 Mar 2017 18:29:05 GMT): MadhavaReddy (Sun, 05 Mar 2017 18:29:05 GMT): muralisr (Sun, 05 Mar 2017 18:31:40 GMT): muralisr (Sun, 05 Mar 2017 18:32:20 GMT): MadhavaReddy (Sun, 05 Mar 2017 18:33:10 GMT): muralisr (Sun, 05 Mar 2017 18:33:22 GMT): MadhavaReddy (Sun, 05 Mar 2017 18:35:33 GMT): saism (Sun, 05 Mar 2017 19:49:30 GMT): obernin (Sun, 05 Mar 2017 20:44:03 GMT): Hangyu (Mon, 06 Mar 2017 01:21:50 GMT): Ratnakar (Mon, 06 Mar 2017 01:42:52 GMT): Ratnakar (Mon, 06 Mar 2017 01:42:52 GMT): Hangyu (Mon, 06 Mar 2017 01:45:12 GMT): Ratnakar (Mon, 06 Mar 2017 01:59:13 GMT): Ratnakar (Mon, 06 Mar 2017 02:00:23 GMT): Ratnakar (Mon, 06 Mar 2017 02:04:29 GMT): jansony1 (Mon, 06 Mar 2017 02:20:20 GMT): greg.haskins (Mon, 06 Mar 2017 02:21:59 GMT): Ratnakar (Mon, 06 Mar 2017 02:23:02 GMT): greg.haskins (Mon, 06 Mar 2017 02:23:26 GMT): greg.haskins (Mon, 06 Mar 2017 02:23:52 GMT): greg.haskins (Mon, 06 Mar 2017 02:24:18 GMT): greg.haskins (Mon, 06 Mar 2017 02:24:23 GMT): greg.haskins (Mon, 06 Mar 2017 02:25:05 GMT): Ratnakar (Mon, 06 Mar 2017 02:26:05 GMT): Hangyu (Mon, 06 Mar 2017 02:31:11 GMT): GangZhao (Mon, 06 Mar 2017 02:58:02 GMT): yong (Mon, 06 Mar 2017 03:16:19 GMT): kostas (Mon, 06 Mar 2017 03:18:16 GMT): greg.haskins (Mon, 06 Mar 2017 03:19:07 GMT): kostas (Mon, 06 Mar 2017 03:19:26 GMT): greg.haskins (Mon, 06 Mar 2017 03:19:36 GMT): greg.haskins (Mon, 06 Mar 2017 03:19:44 GMT): kostas (Mon, 06 Mar 2017 03:20:26 GMT): greg.haskins (Mon, 06 Mar 2017 03:22:52 GMT): greg.haskins (Mon, 06 Mar 2017 03:24:21 GMT): yong (Mon, 06 Mar 2017 03:26:20 GMT): yong (Mon, 06 Mar 2017 03:30:31 GMT): kostas (Mon, 06 Mar 2017 03:31:06 GMT): yong (Mon, 06 Mar 2017 03:33:45 GMT): greg.haskins (Mon, 06 Mar 2017 03:34:36 GMT): greg.haskins (Mon, 06 Mar 2017 03:35:34 GMT): greg.haskins (Mon, 06 Mar 2017 03:36:00 GMT): greg.haskins (Mon, 06 Mar 2017 03:36:25 GMT): greg.haskins (Mon, 06 Mar 2017 03:37:26 GMT): yong (Mon, 06 Mar 2017 03:38:13 GMT): greg.haskins (Mon, 06 Mar 2017 03:38:58 GMT): greg.haskins (Mon, 06 Mar 2017 03:39:30 GMT): greg.haskins (Mon, 06 Mar 2017 03:39:49 GMT): greg.haskins (Mon, 06 Mar 2017 03:40:56 GMT): kelvinzhong (Mon, 06 Mar 2017 07:19:29 GMT): yong (Mon, 06 Mar 2017 07:48:05 GMT): yong (Mon, 06 Mar 2017 07:48:20 GMT): rrader (Mon, 06 Mar 2017 08:01:40 GMT): rrader (Mon, 06 Mar 2017 08:01:40 GMT): qingdu (Mon, 06 Mar 2017 08:43:55 GMT): gatakka (Mon, 06 Mar 2017 08:59:58 GMT): gatakka (Mon, 06 Mar 2017 08:59:58 GMT): gatakka (Mon, 06 Mar 2017 08:59:58 GMT): gatakka (Mon, 06 Mar 2017 08:59:58 GMT): Efdee (Mon, 06 Mar 2017 10:12:50 GMT): warm3snow (Mon, 06 Mar 2017 10:22:17 GMT): warm3snow (Mon, 06 Mar 2017 10:24:21 GMT): vu3mmg (Mon, 06 Mar 2017 11:07:51 GMT): Vadim (Mon, 06 Mar 2017 11:12:02 GMT): vu3mmg (Mon, 06 Mar 2017 11:18:15 GMT): vu3mmg (Mon, 06 Mar 2017 11:19:16 GMT): GiulioEffe (Mon, 06 Mar 2017 11:37:03 GMT): vu3mmg (Mon, 06 Mar 2017 11:37:40 GMT): Vadim (Mon, 06 Mar 2017 12:22:18 GMT): Vadim (Mon, 06 Mar 2017 12:24:02 GMT): vu3mmg (Mon, 06 Mar 2017 13:12:40 GMT): muralisr (Mon, 06 Mar 2017 13:25:44 GMT): gatakka (Mon, 06 Mar 2017 13:27:55 GMT): muralisr (Mon, 06 Mar 2017 13:28:25 GMT): muralisr (Mon, 06 Mar 2017 13:31:36 GMT): gatakka (Mon, 06 Mar 2017 13:32:25 GMT): muralisr (Mon, 06 Mar 2017 13:36:19 GMT): gatakka (Mon, 06 Mar 2017 13:39:04 GMT): greg.haskins (Mon, 06 Mar 2017 13:58:49 GMT): pd93 (Mon, 06 Mar 2017 14:09:56 GMT): gatakka (Mon, 06 Mar 2017 14:14:47 GMT): mrkiouak (Mon, 06 Mar 2017 14:56:54 GMT): zemtsov (Mon, 06 Mar 2017 14:57:49 GMT): zemtsov (Mon, 06 Mar 2017 14:58:08 GMT): mrkiouak (Mon, 06 Mar 2017 15:03:35 GMT): mrkiouak (Mon, 06 Mar 2017 15:03:47 GMT): cgrecu (Mon, 06 Mar 2017 15:05:14 GMT): tulioribeiro (Mon, 06 Mar 2017 15:08:13 GMT): tulioribeiro (Mon, 06 Mar 2017 15:08:38 GMT): tulioribeiro (Mon, 06 Mar 2017 15:11:57 GMT): pd93 (Mon, 06 Mar 2017 15:15:44 GMT): mrkiouak (Mon, 06 Mar 2017 15:16:13 GMT): tulioribeiro (Mon, 06 Mar 2017 15:16:49 GMT): pd93 (Mon, 06 Mar 2017 15:19:17 GMT): tulioribeiro (Mon, 06 Mar 2017 15:20:16 GMT): cgrecu (Mon, 06 Mar 2017 15:20:37 GMT): greg.haskins (Mon, 06 Mar 2017 15:20:53 GMT): cgrecu (Mon, 06 Mar 2017 15:21:28 GMT): greg.haskins (Mon, 06 Mar 2017 15:21:47 GMT): greg.haskins (Mon, 06 Mar 2017 15:23:44 GMT): tulioribeiro (Mon, 06 Mar 2017 15:26:07 GMT): tulioribeiro (Mon, 06 Mar 2017 15:27:58 GMT): muralisr (Mon, 06 Mar 2017 15:28:43 GMT): aso (Mon, 06 Mar 2017 15:28:43 GMT): tulioribeiro (Mon, 06 Mar 2017 15:29:36 GMT): samdeir (Mon, 06 Mar 2017 15:30:07 GMT): pd93 (Mon, 06 Mar 2017 16:06:25 GMT): pd93 (Mon, 06 Mar 2017 16:16:14 GMT): pd93 (Mon, 06 Mar 2017 16:16:14 GMT): dolanor (Mon, 06 Mar 2017 16:49:34 GMT): dolanor (Mon, 06 Mar 2017 16:50:01 GMT): wlahti (Mon, 06 Mar 2017 17:21:27 GMT): muralisr (Mon, 06 Mar 2017 17:24:48 GMT): muralisr (Mon, 06 Mar 2017 17:25:14 GMT): muralisr (Mon, 06 Mar 2017 17:27:00 GMT): muralisr (Mon, 06 Mar 2017 17:27:51 GMT): vkandy (Mon, 06 Mar 2017 18:06:37 GMT): uramoto (Mon, 06 Mar 2017 18:06:58 GMT): jorgedr (Mon, 06 Mar 2017 22:19:21 GMT): kostas (Mon, 06 Mar 2017 22:40:33 GMT): weeds (Mon, 06 Mar 2017 22:41:46 GMT): jorgedr (Mon, 06 Mar 2017 23:00:52 GMT): yong (Tue, 07 Mar 2017 01:09:22 GMT): greg.haskins (Tue, 07 Mar 2017 01:25:08 GMT): yong (Tue, 07 Mar 2017 01:27:59 GMT): tbrooke (Tue, 07 Mar 2017 01:39:30 GMT): rahulhegde (Tue, 07 Mar 2017 01:41:05 GMT): Sky (Tue, 07 Mar 2017 01:46:20 GMT): greg.haskins (Tue, 07 Mar 2017 01:57:19 GMT): greg.haskins (Tue, 07 Mar 2017 01:57:42 GMT): greg.haskins (Tue, 07 Mar 2017 01:58:07 GMT): greg.haskins (Tue, 07 Mar 2017 01:58:13 GMT): greg.haskins (Tue, 07 Mar 2017 01:58:26 GMT): greg.haskins (Tue, 07 Mar 2017 01:58:40 GMT): evafo (Tue, 07 Mar 2017 02:51:21 GMT): xf891220 (Tue, 07 Mar 2017 02:53:32 GMT): rahulhegde (Tue, 07 Mar 2017 02:56:30 GMT): rahulhegde (Tue, 07 Mar 2017 02:56:30 GMT): yong (Tue, 07 Mar 2017 02:56:48 GMT): yong (Tue, 07 Mar 2017 02:57:19 GMT): greg.haskins (Tue, 07 Mar 2017 02:58:54 GMT): greg.haskins (Tue, 07 Mar 2017 02:59:59 GMT): greg.haskins (Tue, 07 Mar 2017 03:00:35 GMT): greg.haskins (Tue, 07 Mar 2017 03:00:42 GMT): greg.haskins (Tue, 07 Mar 2017 03:03:06 GMT): greg.haskins (Tue, 07 Mar 2017 03:03:28 GMT): yong (Tue, 07 Mar 2017 03:04:03 GMT): greg.haskins (Tue, 07 Mar 2017 03:04:45 GMT): greg.haskins (Tue, 07 Mar 2017 03:04:45 GMT): greg.haskins (Tue, 07 Mar 2017 03:05:15 GMT): yong (Tue, 07 Mar 2017 03:05:22 GMT): greg.haskins (Tue, 07 Mar 2017 03:05:29 GMT): greg.haskins (Tue, 07 Mar 2017 03:06:27 GMT): rahulhegde (Tue, 07 Mar 2017 03:06:32 GMT): greg.haskins (Tue, 07 Mar 2017 03:07:01 GMT): yong (Tue, 07 Mar 2017 03:07:33 GMT): yong (Tue, 07 Mar 2017 03:07:50 GMT): rahulhegde (Tue, 07 Mar 2017 03:08:12 GMT): greg.haskins (Tue, 07 Mar 2017 03:09:04 GMT): greg.haskins (Tue, 07 Mar 2017 03:09:41 GMT): greg.haskins (Tue, 07 Mar 2017 03:11:42 GMT): greg.haskins (Tue, 07 Mar 2017 03:12:17 GMT): greg.haskins (Tue, 07 Mar 2017 03:13:08 GMT): greg.haskins (Tue, 07 Mar 2017 03:13:25 GMT): greg.haskins (Tue, 07 Mar 2017 03:14:04 GMT): greg.haskins (Tue, 07 Mar 2017 03:14:56 GMT): greg.haskins (Tue, 07 Mar 2017 03:15:34 GMT): rahulhegde (Tue, 07 Mar 2017 03:18:21 GMT): rahulhegde (Tue, 07 Mar 2017 03:18:21 GMT): greg.haskins (Tue, 07 Mar 2017 03:18:21 GMT): greg.haskins (Tue, 07 Mar 2017 03:18:47 GMT): greg.haskins (Tue, 07 Mar 2017 03:18:52 GMT): rameshthoomu (Tue, 07 Mar 2017 03:19:29 GMT): rameshthoomu (Tue, 07 Mar 2017 03:19:55 GMT): greg.haskins (Tue, 07 Mar 2017 03:20:11 GMT): greg.haskins (Tue, 07 Mar 2017 03:20:24 GMT): rameshthoomu (Tue, 07 Mar 2017 03:21:28 GMT): rameshthoomu (Tue, 07 Mar 2017 03:21:56 GMT): greg.haskins (Tue, 07 Mar 2017 03:22:12 GMT): greg.haskins (Tue, 07 Mar 2017 03:22:20 GMT): rameshthoomu (Tue, 07 Mar 2017 03:22:41 GMT): greg.haskins (Tue, 07 Mar 2017 03:23:10 GMT): rameshthoomu (Tue, 07 Mar 2017 03:24:25 GMT): rahulhegde (Tue, 07 Mar 2017 03:26:34 GMT): rahulhegde (Tue, 07 Mar 2017 03:27:23 GMT): greg.haskins (Tue, 07 Mar 2017 03:28:01 GMT): greg.haskins (Tue, 07 Mar 2017 03:28:18 GMT): greg.haskins (Tue, 07 Mar 2017 03:28:33 GMT): rahulhegde (Tue, 07 Mar 2017 03:28:43 GMT): greg.haskins (Tue, 07 Mar 2017 03:29:10 GMT): greg.haskins (Tue, 07 Mar 2017 03:29:24 GMT): rahulhegde (Tue, 07 Mar 2017 03:29:31 GMT): greg.haskins (Tue, 07 Mar 2017 03:29:53 GMT): greg.haskins (Tue, 07 Mar 2017 03:30:15 GMT): rahulhegde (Tue, 07 Mar 2017 03:30:16 GMT): greg.haskins (Tue, 07 Mar 2017 03:30:27 GMT): greg.haskins (Tue, 07 Mar 2017 03:30:31 GMT): greg.haskins (Tue, 07 Mar 2017 03:31:15 GMT): greg.haskins (Tue, 07 Mar 2017 03:31:31 GMT): greg.haskins (Tue, 07 Mar 2017 03:31:49 GMT): greg.haskins (Tue, 07 Mar 2017 03:31:49 GMT): rahulhegde (Tue, 07 Mar 2017 03:32:24 GMT): greg.haskins (Tue, 07 Mar 2017 03:33:00 GMT): rahulhegde (Tue, 07 Mar 2017 03:33:07 GMT): greg.haskins (Tue, 07 Mar 2017 03:33:12 GMT): greg.haskins (Tue, 07 Mar 2017 03:34:03 GMT): rahulhegde (Tue, 07 Mar 2017 03:34:49 GMT): greg.haskins (Tue, 07 Mar 2017 03:35:02 GMT): rahulhegde (Tue, 07 Mar 2017 03:35:15 GMT): greg.haskins (Tue, 07 Mar 2017 03:35:21 GMT): greg.haskins (Tue, 07 Mar 2017 03:35:41 GMT): greg.haskins (Tue, 07 Mar 2017 03:35:56 GMT): rahulhegde (Tue, 07 Mar 2017 03:36:01 GMT): greg.haskins (Tue, 07 Mar 2017 03:36:12 GMT): greg.haskins (Tue, 07 Mar 2017 03:36:49 GMT): greg.haskins (Tue, 07 Mar 2017 03:37:11 GMT): rahulhegde (Tue, 07 Mar 2017 03:37:16 GMT): rahulhegde (Tue, 07 Mar 2017 03:37:36 GMT): rahulhegde (Tue, 07 Mar 2017 03:37:36 GMT): greg.haskins (Tue, 07 Mar 2017 03:38:09 GMT): greg.haskins (Tue, 07 Mar 2017 03:38:28 GMT): greg.haskins (Tue, 07 Mar 2017 03:39:03 GMT): greg.haskins (Tue, 07 Mar 2017 03:39:23 GMT): rahulhegde (Tue, 07 Mar 2017 03:39:57 GMT): rahulhegde (Tue, 07 Mar 2017 03:39:57 GMT): greg.haskins (Tue, 07 Mar 2017 03:40:16 GMT): greg.haskins (Tue, 07 Mar 2017 03:40:44 GMT): greg.haskins (Tue, 07 Mar 2017 03:44:03 GMT): rahulhegde (Tue, 07 Mar 2017 03:46:00 GMT): greg.haskins (Tue, 07 Mar 2017 03:46:20 GMT): greg.haskins (Tue, 07 Mar 2017 03:46:36 GMT): greg.haskins (Tue, 07 Mar 2017 03:46:59 GMT): greg.haskins (Tue, 07 Mar 2017 03:47:33 GMT): greg.haskins (Tue, 07 Mar 2017 03:48:11 GMT): DannyWong (Tue, 07 Mar 2017 03:49:03 GMT): DannyWong (Tue, 07 Mar 2017 03:49:31 GMT): greg.haskins (Tue, 07 Mar 2017 03:49:56 GMT): greg.haskins (Tue, 07 Mar 2017 03:50:36 GMT): rahulhegde (Tue, 07 Mar 2017 03:50:53 GMT): greg.haskins (Tue, 07 Mar 2017 03:51:40 GMT): greg.haskins (Tue, 07 Mar 2017 03:51:59 GMT): greg.haskins (Tue, 07 Mar 2017 03:53:12 GMT): greg.haskins (Tue, 07 Mar 2017 03:53:21 GMT): greg.haskins (Tue, 07 Mar 2017 03:53:58 GMT): greg.haskins (Tue, 07 Mar 2017 03:54:22 GMT): greg.haskins (Tue, 07 Mar 2017 03:54:49 GMT): greg.haskins (Tue, 07 Mar 2017 03:55:27 GMT): greg.haskins (Tue, 07 Mar 2017 03:55:54 GMT): greg.haskins (Tue, 07 Mar 2017 03:56:42 GMT): DannyWong (Tue, 07 Mar 2017 03:57:41 GMT): greg.haskins (Tue, 07 Mar 2017 03:58:02 GMT): greg.haskins (Tue, 07 Mar 2017 03:58:15 GMT): DannyWong (Tue, 07 Mar 2017 03:58:19 GMT): DannyWong (Tue, 07 Mar 2017 03:58:22 GMT): greg.haskins (Tue, 07 Mar 2017 03:58:32 GMT): rahulhegde (Tue, 07 Mar 2017 03:59:36 GMT): greg.haskins (Tue, 07 Mar 2017 04:00:22 GMT): greg.haskins (Tue, 07 Mar 2017 04:00:43 GMT): greg.haskins (Tue, 07 Mar 2017 04:01:20 GMT): yuichiota (Tue, 07 Mar 2017 04:19:16 GMT): Willson (Tue, 07 Mar 2017 04:58:41 GMT): Tasdgt (Tue, 07 Mar 2017 06:08:42 GMT): alihendavi (Tue, 07 Mar 2017 06:32:16 GMT): levinkwong (Tue, 07 Mar 2017 07:38:45 GMT): levinkwong (Tue, 07 Mar 2017 07:38:45 GMT): Vadim (Tue, 07 Mar 2017 07:50:46 GMT): levinkwong (Tue, 07 Mar 2017 07:53:14 GMT): Vadim (Tue, 07 Mar 2017 07:53:38 GMT): Vadim (Tue, 07 Mar 2017 07:54:00 GMT): levinkwong (Tue, 07 Mar 2017 07:55:08 GMT): Vadim (Tue, 07 Mar 2017 07:56:43 GMT): Vadim (Tue, 07 Mar 2017 07:57:01 GMT): levinkwong (Tue, 07 Mar 2017 07:58:01 GMT): levinkwong (Tue, 07 Mar 2017 07:58:01 GMT): Vadim (Tue, 07 Mar 2017 07:58:50 GMT): levinkwong (Tue, 07 Mar 2017 08:05:12 GMT): zhangchao (Tue, 07 Mar 2017 08:05:49 GMT): Vadim (Tue, 07 Mar 2017 08:05:59 GMT): Vadim (Tue, 07 Mar 2017 08:06:53 GMT): Vadim (Tue, 07 Mar 2017 08:07:23 GMT): Vadim (Tue, 07 Mar 2017 08:07:23 GMT): zhangchao (Tue, 07 Mar 2017 08:18:05 GMT): levinkwong (Tue, 07 Mar 2017 08:24:12 GMT): Vadim (Tue, 07 Mar 2017 08:27:48 GMT): levinkwong (Tue, 07 Mar 2017 08:30:52 GMT): zhangchao (Tue, 07 Mar 2017 08:32:26 GMT): zhangchao (Tue, 07 Mar 2017 08:32:57 GMT): Vadim (Tue, 07 Mar 2017 08:37:39 GMT): Vadim (Tue, 07 Mar 2017 08:37:39 GMT): MartinMateev (Tue, 07 Mar 2017 08:53:08 GMT): MartinMateev (Tue, 07 Mar 2017 08:53:39 GMT): MartinMateev (Tue, 07 Mar 2017 08:54:16 GMT): Vadim (Tue, 07 Mar 2017 08:56:28 GMT): Vadim (Tue, 07 Mar 2017 08:56:54 GMT): MartinMateev (Tue, 07 Mar 2017 09:00:55 GMT): MartinMateev (Tue, 07 Mar 2017 09:01:14 GMT): Vadim (Tue, 07 Mar 2017 09:01:38 GMT): Vadim (Tue, 07 Mar 2017 09:02:34 GMT): Vadim (Tue, 07 Mar 2017 09:02:34 GMT): Vadim (Tue, 07 Mar 2017 09:03:15 GMT): Vadim (Tue, 07 Mar 2017 09:03:15 GMT): Vadim (Tue, 07 Mar 2017 09:03:47 GMT): MartinMateev (Tue, 07 Mar 2017 09:04:13 GMT): MartinMateev (Tue, 07 Mar 2017 09:04:20 GMT): MartinMateev (Tue, 07 Mar 2017 09:04:33 GMT): Vadim (Tue, 07 Mar 2017 09:05:16 GMT): Vadim (Tue, 07 Mar 2017 09:05:31 GMT): MartinMateev (Tue, 07 Mar 2017 09:10:29 GMT): Vadim (Tue, 07 Mar 2017 09:12:38 GMT): Vadim (Tue, 07 Mar 2017 09:12:44 GMT): Vadim (Tue, 07 Mar 2017 09:12:44 GMT): MartinMateev (Tue, 07 Mar 2017 09:13:27 GMT): MartinMateev (Tue, 07 Mar 2017 09:13:45 GMT): Vadim (Tue, 07 Mar 2017 09:14:51 GMT): Vadim (Tue, 07 Mar 2017 09:15:10 GMT): MartinMateev (Tue, 07 Mar 2017 09:16:04 GMT): Vadim (Tue, 07 Mar 2017 09:17:18 GMT): Vadim (Tue, 07 Mar 2017 09:18:04 GMT): Vadim (Tue, 07 Mar 2017 09:18:04 GMT): Vadim (Tue, 07 Mar 2017 09:18:04 GMT): Vadim (Tue, 07 Mar 2017 09:19:38 GMT): Vadim (Tue, 07 Mar 2017 09:21:36 GMT): MartinMateev (Tue, 07 Mar 2017 09:29:12 GMT): MartinMateev (Tue, 07 Mar 2017 09:29:22 GMT): Vadim (Tue, 07 Mar 2017 09:29:36 GMT): Vadim (Tue, 07 Mar 2017 09:29:55 GMT): MartinMateev (Tue, 07 Mar 2017 09:30:09 GMT): Vadim (Tue, 07 Mar 2017 09:30:41 GMT): MartinMateev (Tue, 07 Mar 2017 09:31:59 GMT): MartinMateev (Tue, 07 Mar 2017 09:32:21 GMT): Vadim (Tue, 07 Mar 2017 09:32:39 GMT): MartinMateev (Tue, 07 Mar 2017 09:32:48 GMT): Vadim (Tue, 07 Mar 2017 09:32:52 GMT): MartinMateev (Tue, 07 Mar 2017 09:32:53 GMT): Vadim (Tue, 07 Mar 2017 09:33:06 GMT): MartinMateev (Tue, 07 Mar 2017 09:33:30 GMT): Vadim (Tue, 07 Mar 2017 09:33:39 GMT): Vadim (Tue, 07 Mar 2017 09:33:48 GMT): MartinMateev (Tue, 07 Mar 2017 09:34:08 GMT): MartinMateev (Tue, 07 Mar 2017 09:34:17 GMT): Vadim (Tue, 07 Mar 2017 09:34:28 GMT): MartinMateev (Tue, 07 Mar 2017 09:34:39 GMT): MartinMateev (Tue, 07 Mar 2017 09:34:45 GMT): MartinMateev (Tue, 07 Mar 2017 09:34:49 GMT): MartinMateev (Tue, 07 Mar 2017 09:34:53 GMT): MartinMateev (Tue, 07 Mar 2017 09:34:55 GMT): Vadim (Tue, 07 Mar 2017 09:34:57 GMT): Vadim (Tue, 07 Mar 2017 09:35:04 GMT): Vadim (Tue, 07 Mar 2017 09:35:20 GMT): Vadim (Tue, 07 Mar 2017 09:36:18 GMT): MartinMateev (Tue, 07 Mar 2017 09:38:05 GMT): MartinMateev (Tue, 07 Mar 2017 09:38:19 GMT): Vadim (Tue, 07 Mar 2017 09:38:41 GMT): Vadim (Tue, 07 Mar 2017 09:40:48 GMT): Vadim (Tue, 07 Mar 2017 09:40:48 GMT): yury (Tue, 07 Mar 2017 09:42:22 GMT): yury (Tue, 07 Mar 2017 09:42:22 GMT): yury (Tue, 07 Mar 2017 09:42:22 GMT): yury (Tue, 07 Mar 2017 09:42:22 GMT): Vadim (Tue, 07 Mar 2017 09:43:10 GMT): yury (Tue, 07 Mar 2017 09:45:46 GMT): Vadim (Tue, 07 Mar 2017 09:46:08 GMT): Vadim (Tue, 07 Mar 2017 09:46:08 GMT): yury (Tue, 07 Mar 2017 09:46:29 GMT): yury (Tue, 07 Mar 2017 09:46:29 GMT): Vadim (Tue, 07 Mar 2017 09:46:53 GMT): Vadim (Tue, 07 Mar 2017 09:46:53 GMT): yury (Tue, 07 Mar 2017 09:47:02 GMT): enidz (Tue, 07 Mar 2017 10:01:45 GMT): AbhilekhSingh (Tue, 07 Mar 2017 10:06:26 GMT): AbhilekhSingh (Tue, 07 Mar 2017 10:22:51 GMT): AbhilekhSingh (Tue, 07 Mar 2017 10:59:46 GMT): AbhilekhSingh (Tue, 07 Mar 2017 10:59:48 GMT): mraikwar (Tue, 07 Mar 2017 11:40:13 GMT): mraikwar (Tue, 07 Mar 2017 11:51:58 GMT): soareschen (Tue, 07 Mar 2017 12:02:36 GMT): gatakka (Tue, 07 Mar 2017 12:35:30 GMT): mraikwar (Tue, 07 Mar 2017 12:35:58 GMT): gatakka (Tue, 07 Mar 2017 12:37:04 GMT): mraikwar (Tue, 07 Mar 2017 12:38:42 GMT): gatakka (Tue, 07 Mar 2017 12:39:15 GMT): gatakka (Tue, 07 Mar 2017 12:39:40 GMT): gatakka (Tue, 07 Mar 2017 12:40:23 GMT): mraikwar (Tue, 07 Mar 2017 12:47:10 GMT): gatakka (Tue, 07 Mar 2017 12:50:07 GMT): Vadim (Tue, 07 Mar 2017 12:52:41 GMT): mraikwar (Tue, 07 Mar 2017 13:05:18 GMT): enidz (Tue, 07 Mar 2017 13:36:51 GMT): Vadim (Tue, 07 Mar 2017 13:37:50 GMT): enidz (Tue, 07 Mar 2017 14:00:01 GMT): iscy (Tue, 07 Mar 2017 14:37:50 GMT): cgrecu (Tue, 07 Mar 2017 14:37:50 GMT): ercw (Tue, 07 Mar 2017 15:10:02 GMT): ercw (Tue, 07 Mar 2017 15:12:33 GMT): weeds (Tue, 07 Mar 2017 15:24:47 GMT): ercw (Tue, 07 Mar 2017 15:32:11 GMT): ercw (Tue, 07 Mar 2017 15:32:11 GMT): cshields (Tue, 07 Mar 2017 15:33:59 GMT): mdozturk (Tue, 07 Mar 2017 20:40:28 GMT): rahulhegde (Tue, 07 Mar 2017 21:53:15 GMT): rahulhegde (Tue, 07 Mar 2017 21:53:15 GMT): muralisr (Tue, 07 Mar 2017 23:17:25 GMT): muralisr (Tue, 07 Mar 2017 23:18:12 GMT): muralisr (Tue, 07 Mar 2017 23:18:37 GMT): rahulhegde (Tue, 07 Mar 2017 23:24:37 GMT): rahulhegde (Tue, 07 Mar 2017 23:24:37 GMT): JasonD (Wed, 08 Mar 2017 01:20:39 GMT): wufaxiang (Wed, 08 Mar 2017 01:48:35 GMT): JasonD (Wed, 08 Mar 2017 02:32:39 GMT): JasonD (Wed, 08 Mar 2017 02:32:40 GMT): rahulhegde (Wed, 08 Mar 2017 03:39:32 GMT): rahulhegde (Wed, 08 Mar 2017 03:39:32 GMT): rahulhegde (Wed, 08 Mar 2017 03:39:32 GMT): rahulhegde (Wed, 08 Mar 2017 03:39:32 GMT): rahulhegde (Wed, 08 Mar 2017 03:39:32 GMT): levinkwong (Wed, 08 Mar 2017 03:51:17 GMT): levinkwong (Wed, 08 Mar 2017 03:51:17 GMT): enjoyalife (Wed, 08 Mar 2017 04:00:31 GMT): yyyyyyy9 (Wed, 08 Mar 2017 04:23:59 GMT): mutisaki (Wed, 08 Mar 2017 06:35:31 GMT): levinkwong (Wed, 08 Mar 2017 06:51:27 GMT): xiangyw (Wed, 08 Mar 2017 08:10:24 GMT): yong (Wed, 08 Mar 2017 08:13:24 GMT): yong (Wed, 08 Mar 2017 08:14:36 GMT): xiangyw (Wed, 08 Mar 2017 08:15:11 GMT): xiangyw (Wed, 08 Mar 2017 08:15:21 GMT): xiangyw (Wed, 08 Mar 2017 08:15:40 GMT): xiangyw (Wed, 08 Mar 2017 08:17:00 GMT): xiangyw (Wed, 08 Mar 2017 08:17:14 GMT): Hangyu (Wed, 08 Mar 2017 08:17:34 GMT): xiangyw (Wed, 08 Mar 2017 08:18:08 GMT): yong (Wed, 08 Mar 2017 08:18:31 GMT): xiangyw (Wed, 08 Mar 2017 08:19:35 GMT): xiangyw (Wed, 08 Mar 2017 08:19:56 GMT): xiangyw (Wed, 08 Mar 2017 08:20:17 GMT): Hangyu (Wed, 08 Mar 2017 08:22:13 GMT): xiangyw (Wed, 08 Mar 2017 08:23:00 GMT): Hangyu (Wed, 08 Mar 2017 08:23:20 GMT): yong (Wed, 08 Mar 2017 08:24:51 GMT): yong (Wed, 08 Mar 2017 08:25:26 GMT): Hangyu (Wed, 08 Mar 2017 08:26:01 GMT): yong (Wed, 08 Mar 2017 08:26:15 GMT): Hangyu (Wed, 08 Mar 2017 08:27:34 GMT): xiangyw (Wed, 08 Mar 2017 08:30:13 GMT): xiangyw (Wed, 08 Mar 2017 08:30:37 GMT): xiangyw (Wed, 08 Mar 2017 08:31:25 GMT): Hangyu (Wed, 08 Mar 2017 08:33:27 GMT): Vadim (Wed, 08 Mar 2017 08:34:39 GMT): xiangyw (Wed, 08 Mar 2017 08:43:26 GMT): Vadim (Wed, 08 Mar 2017 08:43:50 GMT): xiangyw (Wed, 08 Mar 2017 08:45:44 GMT): xiangyw (Wed, 08 Mar 2017 08:46:33 GMT): Vadim (Wed, 08 Mar 2017 08:46:53 GMT): levinkwong (Wed, 08 Mar 2017 08:47:15 GMT): Vadim (Wed, 08 Mar 2017 08:48:03 GMT): Vadim (Wed, 08 Mar 2017 08:48:41 GMT): Vadim (Wed, 08 Mar 2017 08:48:54 GMT): levinkwong (Wed, 08 Mar 2017 08:50:46 GMT): Vadim (Wed, 08 Mar 2017 08:53:32 GMT): Vadim (Wed, 08 Mar 2017 08:54:53 GMT): levinkwong (Wed, 08 Mar 2017 08:55:23 GMT): Vadim (Wed, 08 Mar 2017 08:56:08 GMT): levinkwong (Wed, 08 Mar 2017 08:58:21 GMT): Vadim (Wed, 08 Mar 2017 08:58:47 GMT): Vadim (Wed, 08 Mar 2017 08:58:56 GMT): Vadim (Wed, 08 Mar 2017 08:59:13 GMT): Vadim (Wed, 08 Mar 2017 08:59:35 GMT): levinkwong (Wed, 08 Mar 2017 09:00:22 GMT): MartinMateev (Wed, 08 Mar 2017 09:00:33 GMT): MartinMateev (Wed, 08 Mar 2017 09:00:45 GMT): levinkwong (Wed, 08 Mar 2017 09:00:47 GMT): levinkwong (Wed, 08 Mar 2017 09:01:11 GMT): levinkwong (Wed, 08 Mar 2017 09:01:33 GMT): Vadim (Wed, 08 Mar 2017 09:01:40 GMT): levinkwong (Wed, 08 Mar 2017 09:01:47 GMT): MartinMateev (Wed, 08 Mar 2017 09:02:29 GMT): levinkwong (Wed, 08 Mar 2017 09:02:40 GMT): ziyuan (Wed, 08 Mar 2017 09:21:54 GMT): levinkwong (Wed, 08 Mar 2017 09:41:19 GMT): xiangyw (Wed, 08 Mar 2017 09:45:04 GMT): ChuckNiu (Wed, 08 Mar 2017 09:45:18 GMT): levinkwong (Wed, 08 Mar 2017 09:47:57 GMT): DannyWong (Wed, 08 Mar 2017 09:48:36 GMT): DannyWong (Wed, 08 Mar 2017 09:48:44 GMT): DannyWong (Wed, 08 Mar 2017 09:49:12 GMT): DannyWong (Wed, 08 Mar 2017 09:49:17 GMT): xiangyw (Wed, 08 Mar 2017 09:52:50 GMT): Vadim (Wed, 08 Mar 2017 09:54:59 GMT): Vadim (Wed, 08 Mar 2017 09:55:40 GMT): DannyWong (Wed, 08 Mar 2017 09:55:42 GMT): xiangyw (Wed, 08 Mar 2017 09:56:23 GMT): Vadim (Wed, 08 Mar 2017 09:57:26 GMT): Vadim (Wed, 08 Mar 2017 09:57:46 GMT): DannyWong (Wed, 08 Mar 2017 10:02:29 GMT): DannyWong (Wed, 08 Mar 2017 10:04:29 GMT): DannyWong (Wed, 08 Mar 2017 10:04:44 GMT): Vadim (Wed, 08 Mar 2017 10:04:55 GMT): talauliker.shreya (Wed, 08 Mar 2017 10:13:47 GMT): talauliker.shreya (Wed, 08 Mar 2017 10:14:41 GMT): talauliker.shreya (Wed, 08 Mar 2017 10:15:04 GMT): Vadim (Wed, 08 Mar 2017 10:16:59 GMT): Vadim (Wed, 08 Mar 2017 10:17:28 GMT): talauliker.shreya (Wed, 08 Mar 2017 10:50:35 GMT): Vadim (Wed, 08 Mar 2017 10:53:44 GMT): Vadim (Wed, 08 Mar 2017 10:55:17 GMT): clydedacruz (Wed, 08 Mar 2017 11:06:49 GMT): Ying (Wed, 08 Mar 2017 11:42:59 GMT): Ying (Wed, 08 Mar 2017 11:45:57 GMT): Vadim (Wed, 08 Mar 2017 11:46:50 GMT): talauliker.shreya (Wed, 08 Mar 2017 11:47:42 GMT): Ying (Wed, 08 Mar 2017 11:49:21 GMT): Vadim (Wed, 08 Mar 2017 11:49:36 GMT): Ying (Wed, 08 Mar 2017 11:49:45 GMT): Vadim (Wed, 08 Mar 2017 11:51:39 GMT): Ying (Wed, 08 Mar 2017 11:52:52 GMT): Vadim (Wed, 08 Mar 2017 11:53:44 GMT): Vadim (Wed, 08 Mar 2017 11:53:44 GMT): Ying (Wed, 08 Mar 2017 11:54:22 GMT): GaryDee (Wed, 08 Mar 2017 11:54:54 GMT): mraikwar (Wed, 08 Mar 2017 11:55:05 GMT): Vadim (Wed, 08 Mar 2017 11:55:46 GMT): mraikwar (Wed, 08 Mar 2017 11:57:41 GMT): pd93 (Wed, 08 Mar 2017 12:08:53 GMT): Vadim (Wed, 08 Mar 2017 12:10:38 GMT): Vadim (Wed, 08 Mar 2017 12:10:59 GMT): pd93 (Wed, 08 Mar 2017 12:11:24 GMT): pd93 (Wed, 08 Mar 2017 12:11:39 GMT): Vadim (Wed, 08 Mar 2017 12:12:01 GMT): pd93 (Wed, 08 Mar 2017 12:12:32 GMT): SushilChaturvedi (Wed, 08 Mar 2017 12:13:11 GMT): Vadim (Wed, 08 Mar 2017 12:13:40 GMT): Vadim (Wed, 08 Mar 2017 12:13:40 GMT): Vadim (Wed, 08 Mar 2017 12:14:01 GMT): Vadim (Wed, 08 Mar 2017 12:14:01 GMT): pd93 (Wed, 08 Mar 2017 12:15:05 GMT): Vadim (Wed, 08 Mar 2017 12:16:41 GMT): pd93 (Wed, 08 Mar 2017 12:17:54 GMT): Vadim (Wed, 08 Mar 2017 12:18:41 GMT): Vadim (Wed, 08 Mar 2017 12:19:08 GMT): pd93 (Wed, 08 Mar 2017 12:19:36 GMT): pd93 (Wed, 08 Mar 2017 12:20:03 GMT): Vadim (Wed, 08 Mar 2017 12:20:19 GMT): Vadim (Wed, 08 Mar 2017 12:20:38 GMT): pd93 (Wed, 08 Mar 2017 12:22:58 GMT): pd93 (Wed, 08 Mar 2017 12:23:23 GMT): mraikwar (Wed, 08 Mar 2017 13:36:25 GMT): Vadim (Wed, 08 Mar 2017 13:37:54 GMT): Vadim (Wed, 08 Mar 2017 13:38:03 GMT): mraikwar (Wed, 08 Mar 2017 13:38:23 GMT): Vadim (Wed, 08 Mar 2017 13:39:50 GMT): AbhilekhSingh (Wed, 08 Mar 2017 13:42:10 GMT): AbhilekhSingh (Wed, 08 Mar 2017 13:43:14 GMT): mraikwar (Wed, 08 Mar 2017 13:51:11 GMT): mraikwar (Wed, 08 Mar 2017 13:53:54 GMT): mraikwar (Wed, 08 Mar 2017 14:04:55 GMT): pd93 (Wed, 08 Mar 2017 14:17:32 GMT): pd93 (Wed, 08 Mar 2017 14:17:32 GMT):
FYI - if you're running the peer with debug on, there're a lot of messages from gossip subcomponents that you might want to shut off. To do that, you can enter the standard logging CLI `peer logging setlevel component/subcomponent level`. For example,
```
peer logging setlevel gossip/comm#-1 ERROR
```
The component/subcomponent above (gossip/comm#-1) comes from the code, and you may see them in the [] of the log message, example
```
2017-02-19 15:40:03.028 UTC [gossip/comm#-1] sendToEndpoint -> DEBU 6a9 Entering, Sending to 0.0.0.0:7051 , msg: tag:EMPTY memRes:
Has joined the channel.
Has joined the channel.
Has joined the channel.
@vu3mmg That's the exact reason I came to slack.
Please help me understand the difference between Hyperledger (image) and IBM supported Hyperledger image (docker).
How can I get the client certificate at the user-chain code level. I saw shim.GetCallerCertificate but this returns me empty bytes on the SFHackfest v1.0 Fabric Images.
Please let me know if I can use X509 package for parsing it?
Has joined the channel.
Hi. I noticed that the certifications ( tlsca.cert and tlsca.priv) were expired. so please rebuild certifications.
https://github.com/hyperledger/fabric/tree/v0.6/bddtests/
_hyperledger@ubuntu:/opt/gopath/src/github.com/hyperledger/fabric/bddtests$ openssl x509 -enddate -noout -in ./tlsca.cert _
notAfter=Apr 20 22:49:51 2016 GMT
so I change certifications to core/chaincode/testdata/ server1.pem / server1.key. then I happened same this. http://stackoverflow.com/questions/38837649/hyperledger-invalid-tls-certficate-error
[ ](https://chat.hyperledger.org/channel/fabric?msg=2ZwCPXvRZLWduYG7D) @tarima I solved myself. it change to this CORE_PEER_TLS_SERVERHOSTOVERRIDE=_dummy_
But tlsca.cert and tlsca.key are still expired. please rebuild this.
I found that the docker-compose.yml file is not available.
curl -o Dockerfile https://raw.githubusercontent.com/hyperledger/fabric/master/examples/sdk/node/Dockerfile
curl -o docker-compose.yml https://raw.githubusercontent.com/hyperledger/fabric/master/examples/sdk/node/docker-compose.yml
the above two files are not available.
is there any change in repository ?
So we have two identical VMs running 1.0
Both followed the getting started guide
Everything works fine on Machine A
But on Machine B node deploy.js says admin does not have a keyval store
and /tmp/fabric-somekeyvaldir is empty
While on Machine an admin file
Has joined the channel.
Has joined the channel.
Has joined the channel.
Hello, I'm a newcomer who is interested in consensus part. Is there anything I can do? Thanks.
@redpanda - are you looking to help with the code, testing, using it, etc? You might want to post to the #fabric-consensus channel and see if there's anything the folks working on things might need help with. currently, I'd say help on using and documentation would be greatly appreciated and probably would be helpful in coming up to speed on what's there
Has joined the channel.
hi
I am trying to work through the demos and I have a fabric error - is this the best place to ask?
sure, go ahead
I get this chaincode_start.go:22:2: cannot find package "github.com/hyperledger/fabric/core/chaincode/shim" in any of:
/usr/local/go/src/github.com/hyperledger/fabric/core/chaincode/shim (from $GOROOT)
/home/owner/workspace/hyperzillerium/src/github.com/hyperledger/fabric/core/chaincode/shim (from $GOPATH)
I am following the video here - https://www.youtube.com/watch?v=vxT7UQHrAfA
Has joined the channel.
do you have a fabric in your $gopath?
seems the issue is somehow the location
Has joined the channel.
I tried moving it but that did not help
are you trying to deploy a chaincode?
Has left the channel.
Hi all
I am typing go build ./ from the ./start in chaincode
try adding fabric to chaincode_dir/vendor/github.com/hyperledger
how do I add? Just copy it?
yes, create that path and copy it
but it should normally work if fabric is in your $gopath
my GOPATH is /home/owner/workspace/hyperzillerium
cant you do `ls $GOPATH/src/github.com/hyperledger/fabric` ?
can you do `ls $GOPATH/src/github.com/hyperledger/fabric` ?
@mastersingh24 Thank you
I am totally new to Hyperledger, what is fabric - some kind of library?
Fabric is one of the Hyperledger projects, I suppose you work with Fabric?
the demo requires it - I am just working through the demo
the demo is linked from one of the IBM's training courses
well from the error you posted, you are on fabric
I have a question to submit about Hyperledger/fabric functionalities
Is it possible in fabric clone chaincodes
Is it possible in fabric to clone chaincodes
in the last version ?
Hi all, got this error in peer node while deploying chaincode (v1.0)
```
2017-02-20 11:00:20.970 UTC [chaincode] notify -> DEBU 242 notifying Txid:2�']
I move the hyperledger folder - owner@ownerdesktop:~/workspace/hyperzillerium/src/hyperledger/fabric/fabric/core/chaincode/shim$ ls
chaincode.go handler.go interfaces.go mockstub.go shim_test.go table.proto
crypto inprocstream.go java mockstub_test.go table.pb.go
but I get this package not found error
owner@ownerdesktop:~/workspace/hyperzillerium/src/github.com/zillerium/learn-chaincode/start$ go build ./
chaincode_start.go:22:2: cannot find package "hyperledger/fabric/core/chaincode/shim" in any of:
/usr/local/go/src/hyperledger/fabric/core/chaincode/shim (from $GOROOT)
/home/owner/workspace/hyperzillerium/src/hyperledger/fabric/core/chaincode/shim (from $GOPATH)
owner@ownerdesktop:~/workspace/hyperzillerium/src/github.com/zillerium/learn-chaincode/start$ cd $GOPATH
here is the code - import (
"errors"
"fmt"
"hyperledger/fabric/core/chaincode/shim"
)
is Hyperledger better than Euthereum? Has anyone tested?
@TrevorOakley ~/workspace/hyperzillerium/src/hyperledger/fabric/fabric/core... <- correct path should be src/github.com/hyperledger/fabric, also you have "fabric" twice in the path
[ ](https://chat.hyperledger.org/channel/fabric?msg=AehasdLQhK4Sot5FZ) for private chains - much more convenient
I am testing both. Euthereum has a lot of flexibility but there is a gas cost. Also some speed issues. I am just starting with Hyperledger
@Vadim I am testing more - I changed the /fabric/fabric part and now a lot more errors arrived. I will have to understand shim a lot more to understand what is happening here. Thanks for your help
Ethereum is not suitable for private chains
also there is very limited storage in the chain
I was looking at IPFS for storage. Ethereum is slow from what I saw.
Hi, when a client tries to execute a chaincode, it could connect to any peer, or it needs to connect to an orderer ?
it needs a peer
orderers does not execute chaincodes
orderers do not execute chaincodes
Ok. So a CORE_PEER_ADDRESS and CORE_PEER_PORT should do the trick ?
(I'm trying to execute a chaincode from go)
I'm not familiar with environment variables config, but you can try
My code (which is very simple) is here : https://gist.github.com/dolanor/17161d8cfafb666b667da82aa729e963
is there something fishy ? Or it should work ?
(because it doesn't. It says grpc times out)
`
$ CORE_PEER_ADDRESS=localhost CORE_PEER_PORT=8051 ./lightclient
panic: Error getting endorser client chaincode: PEER_CONNECTIONERROR - Error trying to connect to local peer: grpc: timed out when dialing
goroutine 1 [running]:
panic(0x966520, 0xc42000ccf0)
/usr/local/go/src/runtime/panic.go:500 +0x1a1
main.main()
/home/dolanor/gohyp/src/github.com/dolanor/charging/lightclient/main.go:33 +0x395
`
(because it doesn't. It says grpc times out)
```
$ CORE_PEER_ADDRESS=localhost CORE_PEER_PORT=8051 ./lightclient
panic: Error getting endorser client chaincode: PEER_CONNECTIONERROR - Error trying to connect to local peer: grpc: timed out when dialing
goroutine 1 [running]:
panic(0x966520, 0xc42000ccf0)
/usr/local/go/src/runtime/panic.go:500 +0x1a1
main.main()
/home/dolanor/gohyp/src/github.com/dolanor/charging/lightclient/main.go:33 +0x395
```
It should be of the form: `CORE_PEER_ADDRESS=peer0:7051`
See here for more reference: https://github.com/hyperledger/fabric/blob/master/docs/install_instantiate.md
Ok, i tried again
`$ CORE_PEER_ADDRESS=localhost CORE_PEER_PORT=8051 ./lightclient
panic: Error getting endorser client chaincode: PEER_CONNECTIONERROR - Error trying to connect to local peer: grpc: timed out when dialing
goroutine 1 [running]:
panic(0x966520, 0xc42000ccf0)
/usr/local/go/src/runtime/panic.go:500 +0x1a1
main.main()
/home/dolanor/gohyp/src/github.com/dolanor/evcharging/lightclient/main.go:33 +0x395`
```
$ CORE_PEER_ADDRESS=localhost CORE_PEER_PORT=8051 ./lightclient
panic: Error getting endorser client chaincode: PEER_CONNECTIONERROR - Error trying to connect to local peer: grpc: timed out when dialing
goroutine 1 [running]:
panic(0x966520, 0xc42000ccf0)
/usr/local/go/src/runtime/panic.go:500 +0x1a1
main.main()
/home/dolanor/gohyp/src/github.com/dolanor/evcharging/lightclient/main.go:33 +0x395
```
(I have the sfhackfest running, which works with the NodeSDK, so the localhost:8051 goes to the peer0:7051 port in the container bridge
(I have the sfhackfest running, which works with the NodeSDK, so the localhost:8051 goes to the peer0:7051 port in the container bridge)
no...
can you try with the `localhost:8051` ?
maybe that'll work?
is it correct that for hyperledger v0.6 there are to possibilities to write to the blockchain?
1) putstate
and 2 ) using tables ?
*two
sorry @yacovm, my copy paste was wrong, I really did the
```
$ CORE_PEER_ADDRESS=localhost:8051 ./lightclient
panic: Error getting endorser client chaincode: PEER_CONNECTIONERROR - Error trying to connect to local peer: grpc: timed out when dialing
goroutine 1 [running]:
panic(0x966520, 0xc420202fc0)
/usr/local/go/src/runtime/panic.go:500 +0x1a1
main.main()
/home/dolanor/gohyp/src/code.tuxago.com/dolanor/evcharging/lightclient/main.go:33 +0x395
```
with CORE_PEER_ADDRESS=localhost:8051
By the way, is there a way to display debug log from the client ?
I tried --logging-level=debug, but didn't work. Just that grpc error
Is anyone really answering on that port? `netstat -nlop | grep 8051` will do the trick
Is anyone really listening on that port? `netstat -nlop | grep 8051` will do the trick
```
$ netstat -nlop | grep 8051
(Tous les processus ne peuvent être identifiés, les infos sur les processus
non possédés ne seront pas affichées, vous devez être root pour les voir toutes.)
tcp6 0 0 :::8051 :::* LISTEN - off (0.00/0/0)
```
Ne sais pas :(
```
$ sudo sudo netstat -nlop | grep :8051
tcp6 0 0 :::8051 :::* LISTEN 6460/docker-proxy off (0.00/0/0)
```
Forgot to launch with sudo
aha
well I still don't know
not familiar with this evcharging thing
evcharging is my project, it is just a POC now, with the code I put on gist.github.com
to be more concrete: can you write floating point numbers into the ledger?
@jyellick @muralisr Up untill last syncing with Fabric I was able to parse the returned proposal response from the bytecode
```
org.hyperledger.fabric.sdk.exception.TransactionException: sendTransaction: Protocol message had invalid UTF-8.
at org.hyperledger.fabric.sdk.Chain.sendTransaction(Chain.java:895)
at org.hyperledger.fabric.sdk.End2endIT.setup(End2endIT.java:168)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
```
ByteString payloadBytes = proposal.getProposalResponse().getPayload();
proposalResponsePayload = FabricProposal.ChaincodeProposalPayload.parseFrom(payloadBytes);
fabric level 9a0aedb1055184631170d400b854e8225607e1a7
@jyellick @muralisr Up untill last syncing with Fabric I was able to parse the returned proposal response payload from the bytecode
```
org.hyperledger.fabric.sdk.exception.TransactionException: sendTransaction: Protocol message had invalid UTF-8.
at org.hyperledger.fabric.sdk.Chain.sendTransaction(Chain.java:895)
at org.hyperledger.fabric.sdk.End2endIT.setup(End2endIT.java:168)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
```
ByteString payloadBytes = proposal.getProposalResponse().getPayload();
proposalResponsePayload = FabricProposal.ChaincodeProposalPayload.parseFrom(payloadBytes);
fabric level 9a0aedb1055184631170d400b854e8225607e1a7
[In v0.6 - yes - there's the put/get state functions, the table function and additional there are range query functions as well. In v1.0, we've removed the table APIs and enhanced the range query functionality by adding some convenience functions around composite keys ](https://chat.hyperledger.org/channel/fabric?msg=iCxyE56QwLJ3pvgnd) @thojest
@mastersingh24 thx alot, maybe you can also anwser my question concerning floating point numbers
@thojest - off the top of my head, I can't think of any issue off the top of my head (it's supported). @manish-sethi - anything come to mind?
Has joined the channel.
Has joined the channel.
Has joined the channel.
Hi All, how would i see the complete ledger for a chain code in 1.0, i tested example 02 chain code with multiple invokes now want to see complete ledger for this chain code
Has joined the channel.
@rickr I'm not sure about the proposal results, maybe @muralisr will know
@rickr only thing that comes to mind is maybe https://gerrit.hyperledger.org/r/#/c/6255 ? node SDK worked late yesterday
@muralisr , does chaincode has an ability to plug-in any tool/package etc ? That tool package will be able to invoke at runtime during chaincode execution.
@muralisr , does chaincode has an ability to plug-in any tool/package etc ? That tool/package will be able to invoke at runtime during chaincode execution.
@ashutosh_kumar - not sure what you mean? are you asking if one can included 3rd party Go / Java packages with their chaincode? The answer is yes
that is good @mastersingh24 . My use case is suppose the chaincode execute certain transaction , which involves muti-region , say from US to Europe , transaction. In that case , to meet Privacy requirement , somebody wants to scrub data or perform anonymization etc. Support for injection of third party tool/package into chaincode will be handy in this case.
Has joined the channel.
@MadhavaReddy query the blocks and transactions
Has joined the channel.
Has joined the channel.
Has joined the channel.
Has joined the channel.
@ashutosh_kumar you can certainly import any package into the chaincode. while to the tools, do u mean some tools to provide interfaces, and chaincode get data from it? e.g., RESTful interface. It should be OK if u have the networking connection.
Has joined the channel.
Hi I checked the proto about payloadVisibility (This was somehow available in fabric v0.6).
https://github.com/hyperledger/fabric/blob/master/protos/utils/txutils.go#L284
Looks like v1.0 is full visible. I tried to find (in JIRA db) if there is plan to address visibility, but I could not find it. I feel like this is regression from 0.6. Is there any plan for it ? Or become permanent restriction ? Also, I wonder if ledger data (both Block and Worldstate) are encrypted or not. As far as I checked, all the data is recorded as is on the Database, so malicious user may take a look at it whole records without any restrictions (correct me if I'm wrong).
Has joined the channel.
@elli-androulaki can you please answer ibmamnt questions above
Has joined the channel.
In regard to the v1.0 getting started, grpc seems to need its own npm install grpc, even after npm install
The [package.json](https://github.com/hyperledger/fabric-sdk-node/blob/master/examples/balance-transfer/package.json) doesn't list grpc as a dependency
Has joined the channel.
Has joined the channel.
hi @ibmamnt , visibility function is applied on the proposal at endorsement time, and outputs the parts and form of proposal that is to be included in the endorsement and thus the transaction. Indeed this functionality was not part of v0.6.
The idea was that visibility function was to take two values: i) fully-visible, where the full proposal (modulo the transient data) is included in what is endorsed, and ii) hashed, in which case the proposal's header would be fully visible, and proposal's payload would be hashed prior to the endorsement being computed. We were also considering a third scenario where visibility function would be set to "none", where only proposal header would reside into the endorsement.
In v1.0 and up till now as you mentioned we have only one mode supported, i.e., fully visible, while function definitions have placeholders to a visibility field.
[fabric-client is actually the NodeJS fabric client and it includes grpc](https://chat.hyperledger.org/channel/fabric?msg=fqGHewtQyaBNf3iod) @raghavsood
@ibmamnt, however, visibility function and associated functionality is orthogonal to any encryption that is to take place on the payload of the transactions/proposals.
In contradiction to v0.6, in v1.0 we do not offer encryption capabilities at the fabric-level. We plan though at some point to provide encryption libraries to support this at the application level.
In addition to this, community is to decide future directions on potential encryption features on fabric.
@ibmamnt, however, visibility function and associated functionality is orthogonal to any encryption that is to take place on the payload of the transactions/proposals.
In contradiction to v0.6, in v1.0 we do not offer encryption capabilities at the fabric-level. We plan though at some point to provide encryption libraries to support this at the application level.
In addition to this, community is to decide future directions on potential encryption features on fabric.
And you are right, from fabric-perspective data on ledger side is in cleartext as well as data in transactions.
Non-encryption based confidentiality features are offered in v1.0 through multi-channel architecture, where participants with private transactions may create their own channel.
However, one needs to keep in mind that the ordering service that creates this channel for the members that wish to transact privately, is trusted in any case to see the transaction plaintext.
[ ](https://chat.hyperledger.org/channel/fabric?msg=YvbTtyHbGvzcLmWNd) @mastersingh24 I realise that. I'm talking specifically about when you follow the getting-started guide. At [this](https://hyperledger-fabric.readthedocs.io/en/latest/asset_setup/) step, you run npm install and install stuff from [this package.json](https://github.com/hyperledger/fabric-sdk-node/blob/master/examples/balance-transfer/package.json). When you run the [next step](https://hyperledger-fabric.readthedocs.io/en/latest/asset_sdk/) of `GOPATH=$PWD node deploy.js`, you receive an error as grpc is not installed. The getting started guide does not ask us to install fabric-client, only to pull the example files from the balance-transfer example.
Running `npm install grpc` fixes this
@raghavsood - hmm - this is odd - so I just did
`curl -OOOOOO https://raw.githubusercontent.com/hyperledger/fabric-sdk-node/v1.0-alpha/examples/balance-transfer/{config.json,deploy.js,helper.js,invoke.js,query.js,package.json}`
`npm install`
`GOPATH=$PWD node deploy.js`
and I did not need to install grpc separately
@elli-androulaki I fully understood the current status and plan. I think the plan is good move. Thanks !
Do you by chance have grpc installed globally?
@ibmamnt sure!
[ no - just checked that as well](https://chat.hyperledger.org/channel/fabric?msg=4WE6vi2bs6CoJP7do) @raghavsood
why version of nodejs are you using?
7.5.0
I was using 6.9.5
Also tried it with 6.9.5
7.5.0 on OS X
6.9.5 on Ubuntu
6.95 on OSX for me
6.9.5 on OSX for me
Also, on OS X, hashtable via npm is broken. You need to install a forked version of it
hmm - not for me
I had to install https://github.com/fabrice102/node-hashtable
This is the issue on the original hashtable on Github for this specific issue: https://github.com/chad3814/node-hashtable/pull/31
It's been broken for a while for newer versions of OS X
Either case, I'll try the getting-started again on a fresh vm when I get home and see if grpc acts up. Thanks for double checking!
I've stayed on OSX 10.11.5 (El Capitan) because lots of things break across the board
sad - very sad
Has joined the channel.
i have been playing around with the hyperledger templates and have modified them for a simple proof of concept how the national association of realtors could track its realtor members involvement among the varying levels of membership (local state national)
https://github.com/NationalAssociationOfRealtors/EngagementOnChain
I will be implementing the v2 version soon, but any stars or follows on github would be appreciated
we have existing centralized systems that already do this but i wanted to develop prototype solutions based on blockchain that would help our organization get more familiar with pro’s and con's of this new technology
@conroydave looks really interesting! I'd be interested in helping you port this to #fabric-composer http://fabric-composer.org
cool. i feel like a noob not getting it to work on v2 of boilerplate prior to my large presentation this week
but, it worked fine on linux but not on mac and just didnt have the time to debug it
The data model looks like it should be easy to capture: https://github.com/NationalAssociationOfRealtors/EngagementOnChain/blob/master/src/build-chaincode/data/data.go
Use the Composer modeling language; https://fabric-composer.github.io/reference/cto_language.html
thursday this week i am presenting this project to the nation wide tech directors of each state association of realtors
in LA
most likely it will actually be high level, as much as i want to dive into a code review - half my objective is education
As far as I can tell, the Go code is just doing simple CRUD of the elements of your domain model, right?
my repo needs an overhaul no doubt though
yeah
an existing model we've had since '94
Composer will give you this for free, as well as exposing the model over REST and as Typescript. It will even generate a skeleton Angular app for you.
that is what i was hoping for
just had not committed the keyboard time into getting operational
If you want some help porting it -- let's bounce over to the #fabric-composer channel
basically we define the domain model together and then the rest "should just work" (as they say!)
i struggled with the idea of People vs Things
lol
One to Many, Many to Many
That may something about you... ;-)
when to use what
oh cmon
I know the difference just when tracking 1.2 million members you have to choose your data relationships very carefully
last thing i want is poorly implemented business rules, i'd end up with a slower and more complicated version of microsoft dynamics
@all hi everyone, i have questions about Hyperledger, please take a look and help me. Thanks
1. My first question, i have setup a Farbic network use http://hyperledger-fabric.readthedocs.io/en/v0.6/starter/fabric-starter-kit/ tutorial. So can i setup Hyperledger v1.0 on my environment? How to do it?
2. My second question, when i updated my Dockerfile, i need to re-deploy my chaincode, but i don't know where do old data storage? How can i keep old data of previous deployment time?
When you mention all, everyone in the room receives notification. Did you really intend to do so?
@sword_linux As I *just* said in #fabric-sdk-node... Please use `@all` sparingly... it sends a notifcation to everyone in this channel...
@sword_linux As I *just* said in #fabric-sdk-node ... Please use `@all` sparingly... it sends a notifcation to everyone in this channel...
@pd93 thanks, let me see
1 - the v1.0 docs have a getting started page http://hyperledger-fabric.readthedocs.io/en/latest/asset_setup/
2 - you probably want to mount a volume in your container for the persistant storage
@cbf thanks
Hello, is there any solution to deploy just using docker (not docker compose), in order to run it over heroku (https://devcenter.heroku.com/articles/container-registry-and-runtime) ?
[ ](https://chat.hyperledger.org/channel/fabric?msg=v6WDs32K8sQ8sKCX7) @kleman i use Rancher to setup Hyperledger
ok, it seems pretty to run hyperledger locally, but my aim is to deploy it remotely on heroku public cloud
@kleman - they key to running the Docker images anywhere is properly setting either the config (the YAML files) and/or setting / passing environment variable overrides (that's what makes the docker-compose stuff so convenient)
and of course, you have to properly set the endpoints based on the networking in your environment
BUT - I don't think you'll be able to run in Heroku because as I recall Heroku only allows you to expose things over HTTP and fabric nodes use GRPC which uses HTTP/2 as the underlying transport
also if you are running docker on mac you almost always have to modify the docker compose files
Has joined the channel.
Has joined the channel.
@mastersingh24 @raghavsood ive had trouble with the hfc npm dependency install as well. For example, in the vagrant dev env I've needed to globally install node-gyp, node-pre-gyp, set an 'npm set python
I spent quite a bit of time over the past few weeks working through similar hfc node client dependencies/issues (e.g. another one was g++ on red hat/centos and finding that groupinstall 'Development...' seemed to be the only gcc compiler install + settings that would be found by npm when running node-gyp as part of dependencies.
does anyone think there would be any interest in me putting together some kind of FAQ on these install issues and submitting to maintainer of docs? I *think* I've sorted out issues setting up on rhel/centos, windows & mac osx for the current sf hackfest/v1 alpha version and dependent toolsets
@mrkiouak - probably worth while. I think some of it would be appropriate pointers to requirements for various OS / platforms for installing node packages with native code (e.g. install Windows build tools)
ah yes, that's another piece I forgot to put in my notes, visual studio/msbuild tools
ok-- if theres any reference or template I should use to start from, please let me know
[ ](https://chat.hyperledger.org/channel/fabric?msg=3yhPateSMFAryk4Ks) @conroydave Could you elaborate?
The reason I ask is, I was the one who ported the build from vagrant-only to work with docker-for-mac, and I am not aware of any mods required for the compositions to run
I am curious what you are running into
hello
is there any example i can set via docker of fabric v1.0, with multiple peers and consensus?
is there any example i can set up via docker of fabric v1.0, with multiple peers and consensus?
help would be greatly appreciated
@magg - work in progress - but give http://hyperledger-fabric.readthedocs.io/en/latest/included/ a shot
it's behind where the master branch is, but it will at least get you a basic network up and running so you can explore the concepts
@mastersingh24 thanks, i will try that
what kind of testing does Fabric has to ensure crashing nodes do not affect the system. I want to see if the consensus can withstand crashing some nodes.
@scottz @magg ^^^
@magg: Work in progress (see: https://gerrit.hyperledger.org/r/#/c/6039/ and track JIRA items FAB-1335 and FAB-1306 as well)
@magg: Work in progress (see: https://gerrit.hyperledger.org/r/#/c/6039/ and track JIRA items FAB-1335 and FAB-1306 as well.)
@magg: Work in progress -- see: https://gerrit.hyperledger.org/r/#/c/6039/ and track JIRA items FAB-1335 and FAB-1306 as well
@magg: Work in progress — see: https://gerrit.hyperledger.org/r/#/c/6039/ and track JIRA items FAB-1335 and FAB-1306 as well
The intention is to cover crash scenarios via BDD tests.
Has joined the channel.
got it thanks
Has joined the channel.
Hi Guys i followed the documents at http://hyperledger-fabric.readthedocs.io/en/v0.6 and i was succeful in implementing using Docker
Thank you all for the help
just want to know can i do the same without docker conatiner ?I mean using actual machines instead of Docker?
Why you don't want to use docker?
With Docker i'm using docker-compose.yaml and it spins off the constiners .Now instaed of containers i need that to be physical/actual machines
@rrader ,Is there a way to map the physical/actual machines instead of conatiners ?
Has joined the channel.
@smfaizalkhan In master/mainline, just do "make native" and assuming you have all the prerequisites you can run the resulting binaries in your native environment
are the tables created by each chaincode deployment visible to other chaincode deployments? if not, how do you deploy new chaincode that can see the existing tables?
@jtrayfield No, and unless you are talking about upgrading an instance, you can't
@greg.haskins so how do you fix chaincode bugs?
Has joined the channel.
@magg you can also ask the people part of quality squad to give input on testing scenarios.
they are on fabric-quality channel
Has joined the channel.
Has joined the channel.
@magg We are also writing tests for the orderers under FAB-972 ; the testplan for these and more for peers and other components can be found under-development here: https://docs.google.com/spreadsheets/d/1_IdXCuYMKkqXr3Za0pVnFP3sP1jBcNbYnTJGV-nSkxI/edit?usp=sharing
Has joined the channel.
@jtrayfield Not sure what you mean
@greg.haskins how do you deploy chaincode fixes that can access the old data?
Upgrade function of lccc
That's what I meant by upgrading an instance
You can create an instance, and it gets its own private kvstore accessible only to itself or future upgrades to itself
@greg.haskins thanks
I see now we can get the chaincode creator (https://github.com/hyperledger/fabric/commit/458328b080663c2653242e638c672f059afba050)
will there any function to get the chaincode caller also ? (equivalent to Ethereum's msg.sender)
What is the different between Install Proposal and Instantiate Proposal???
Is there any document how to setup MSP inside peer ? ( CORE_PEER_MSPCONFIGPATH=/etc/hyperledger/fabric/msp/sampleconfig ). I have loaded my own "server-config.json" to pass it to fabric-ca, and then tried to deploy chaincode, I got:
```[2017-02-22 17:32:49.862] [INFO] DEPLOY - Executing Deploy
error: [Peer.js]: GRPC client got an error response from the peer. Error: Failed to deserialize creator identity, err MSP DEFAULT is unknown```
Looks like 'DEFAULT' is hard coded, but don't know how to resolve it. Appreciate any discussions. Thanks !
@ibmamnt what's your channel id
I had the same error returned when deploy chaincode by Node.js SDK, and was told can only use `testchainid` as channel id (or use CLI to setup your channel)
channelid is 'testchainid'.
Then I can't help, I am newbie to fabric :(
@levinkwong no worry ! I'm newbie to fabric v1.0 too!
Hello, i got very strange panic message on peer
peer0 | panic: runtime error: invalid memory address or nil pointer dereference
peer0 | [signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x93ad67]
peer0 |
peer0 | goroutine 1479 [running]:
peer0 | github.com/hyperledger/fabric/common/cauthdsl.compile(0x0, 0x0, 0x0, 0x0, 0x122fd40, 0xc421706f80, 0x0, 0x59, 0x59)
peer0 | /go/src/github.com/hyperledger/fabric/common/cauthdsl/cauthdsl.go:34 +0x37
peer0 | github.com/hyperledger/fabric/common/cauthdsl.(*provider).NewPolicy(0xc421948de0, 0x1285a60, 0x0, 0x0, 0xc421706f80, 0x0, 0x0, 0x50)
peer0 | /go/src/github.com/hyperledger/fabric/common/cauthdsl/policy.go:52 +0x181
peer0 | github.com/hyperledger/fabric/core/scc/vscc.(*ValidatorOneValidSignature).Invoke(0x12856a0, 0x1242b40, 0xc421bb7680, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0)
peer0 | /go/src/github.com/hyperledger/fabric/core/scc/vscc/validator_onevalidsignature.go:96 +0x5b5
peer0 | github.com/hyperledger/fabric/core/chaincode/shim.(*Handler).handleTransaction.func1(0xc420243f10, 0xc421b8d590)
peer0 | /go/src/github.com/hyperledger/fabric/core/chaincode/shim/handler.go:312 +0x6ef
peer0 | created by github.com/hyperledger/fabric/core/chaincode/shim.(*Handler).handleTransaction
peer0 | /go/src/github.com/hyperledger/fabric/core/chaincode/shim/handler.go:327 +0x49
This is happened when i make successful chaincode execution
@adc / @aso :arrow_double_up:
Has joined the channel.
in latest fabric 1.0 there is [version] in install or instantiate . Can I get some link or doc about version. [specially how to call previous version chaincode , how they communicate ... specially multichannel and multiversion]
has anyone worked with this demo - https://www.youtube.com/watch?v=vxT7UQHrAfA - I am trying to follow it but I am getting a lot of errors?
Here is my latest batch -
owner@ownerdesktop:~/workspace/hyperzillerium/src/github.com/zillerium/learn-chaincode/start$ go build ./
../../../../hyperledger/fabric/fabric/core/chaincode/shim/chaincode.go:33:2: cannot find package "github.com/hyperledger/fabric/core/chaincode/shim/crypto/attr" in any of:
/home/owner/workspace/hyperzillerium/src/hyperledger/fabric/fabric/vendor/github.com/hyperledger/fabric/core/chaincode/shim/crypto/attr (vendor tree)
/usr/local/go/src/github.com/hyperledger/fabric/core/chaincode/shim/crypto/attr (from $GOROOT)
/home/owner/workspace/hyperzillerium/src/github.com/hyperledger/fabric/core/chaincode/shim/crypto/attr (from $GOPATH)
../../../../hyperledger/fabric/fabric/core/chaincode/shim/chaincode.go:34:2: cannot find package "github.com/hyperledger/fabric/core/chaincode/shim/crypto/ecdsa" in any of:
/home/owner/workspace/hyperzillerium/src/hyperledger/fabric/fabric/vendor/github.com/hyperledger/fabric/core/chaincode/shim/crypto/ecdsa (vendor tree)
/usr/local/go/src/github.com/hyperledger/fabric/core/chaincode/shim/crypto/ecdsa (from $GOROOT)
/home/owner/workspace/hyperzillerium/src/github.com/hyperledger/fabric/core/chaincode/shim/crypto/ecdsa (from $GOPATH)
../../../../hyperledger/fabric/fabric/core/chaincode/shim/chaincode.go:35:2: cannot find package "github.com/hyperledger/fabric/core/comm" in any of:
/home/owner/workspace/hyperzillerium/src/hyperledger/fabric/fabric/vendor/github.com/hyperledger/fabric/core/comm (vendor tree)
/usr/local/go/src/github.com/hyperledger/fabric/core/comm (from $GOROOT)
/home/owner/workspace/hyperzillerium/src/github.com/hyperledger/fabric/core/comm (from $GOPATH)
../../../../hyperledger/fabric/fabric/core/chaincode/shim/chaincode.go:36:2: cannot find package "github.com/hyperledger/fabric/protos" in any of:
/home/owner/workspace/hyperzillerium/src/hyperledger/fabric/fabric/vendor/github.com/hyperledger/fabric/protos (vendor tree)
/usr/local/go/src/github.com/hyperledger/fabric/protos (from $GOROOT)
/home/owner/workspace/hyperzillerium/src/github.com/hyperledger/fabric/protos (from $GOPATH)
owner@ownerdesktop:~/workspace/hyperzillerium/src/github.com/zillerium/learn-chaincode/start$ vi start
owner@ownerdesktop:~/workspace/hyperzillerium/src/github.com/zillerium/learn-chaincode/start$ ls
chaincode_start.go
owner@ownerdesktop:~/workspace/hyperzillerium/src/github.com/zillerium/learn-chaincode/start$ subl chaincode_start.goowner@ownerdesktop:~/workspace/hyperzillerium/src/github.com/zillerium/learn-chaincode/start$ go build ./
chaincode_start.go:22:2: cannot find package "hyperledger/fabric/fabric/core/chaincode/shim" in any of:
/usr/local/go/src/hyperledger/fabric/fabric/core/chaincode/shim (from $GOROOT)
/home/owner/workspace/hyperzillerium/src/hyperledger/fabric/fabric/core/chaincode/shim (from $GOPATH)
I find I am not really making any progress
This is from the IBM tutorials teaching hyperledger - either the demos are out of date or I am a setup error.
is this the main channel for fabric and hyperledger?
@ibmamnt I got the exact same problem.
I think I started a few weeks ago, and what used to work doesn't anymore.
So I don't know what version do I need to use.
I started from the "Getting started" section in the docs section. And it doesn't work anymore.
@TrevorOakley @dolanor that part of the code has been removed from the v1. Those functionalities will be offered by a library directly at the chaincode level
I am only following demos from a training link at the IBM site - is this just dated now?
If so, where can I find training for Hyperledger?
I'm in the same situation. Should I just downgrade to the commit from the sfhackfest or is there an up to date documentation about the v1.0.0 ?
I'm supposed to deliver something for a POC today, and now that nothing works anymore, I'm not in a great situation.
@adc I'm in the same situation. Should I just downgrade to the commit from the sfhackfest or is there an up to date documentation about the v1.0.0 ?
I'm supposed to deliver something for a POC today, and now that nothing works anymore, I'm not in a great situation.
Could you please give me some pointers about the working of events
How do i listen for events
following is my scenario , I need to get a notification when transaction is committed
Has joined the channel.
How can we prevent user's execution of some operations in chaincode if he doesn't have some roles?
How can we prevent user's execution of some operations in chaincode if he doesn't have some roles? (v1.0)
@dolanor I would suggest downgrading to the commit from the sfhackfest if you have a POC today. There has been some changes due to some commits recently we are working through.
@greg.haskins the upgrade function is v1.0 function, not available in v0.6, correct?
https://jira.hyperledger.org/browse/FAB-1238
Has joined the channel.
I have some queries related to listening for events .
Could you please provide me some insights into the right architectural pattern
Scenario
=======
I wrote some data to ledger
Now my web app would like to get the event (This i could get with help of event sender and event listener examples) .
My Doubt.
=========
What is the best way to retrieve incremental addition to the ledger ?
When I get a {EventType: pb.EventType_BLOCK} , how should i extract the value of that transaction . I was not able to find the documentation for the same .
Any pointers will be really helpful .
MyUse case :
People are sending money .
I would like to redraw the UI after a new remittance happens .
@vu3mmg Response of .EventType_BLOCK is marshaled, you must unmashal it first. Actual data is in eventResponseData.GetBlock().Data.Data
Thank you
this is and proto.Envelope structure, and from there you can take all you need
this is a proto.Envelope structure, and from there you can take all you need
so each block contains exaclty one invocation ?
Has left the channel.
it contains data for one transaction that is commited to the ledger. One invocation can make more than one transaction
so GetBlock().Data.Data is list that holds all transactions
ok
here is a simple go code
envelope := new(common.Envelope)
if err := proto.Unmarshal(in.GetBlock().Data.Data[0], envelope); err != nil {
}
Has joined the channel.
hi, sorry for the stupid enquire, the Fabric troubleshooting guide goes like this
"Take these values and hard code them into your cli commands. For example:
CORE_PEER_COMMITTER_LEDGER_ORDERER=172.21.0.2:7050 peer channel create -c myc1
"
what would be what is referred as the "cli commands"?
is it the "command" section of the docker-compose spec?
@gatakka thank you .
I guess not, seems to be the channel_test.sh script
@weeds Thank you.
Before your answer, I tried again with a clean env and it didn't work. So yeah, back to the previous commits.
Has joined the channel.
Has joined the channel.
Has joined the channel.
Sweetspot Ethereum is ideal for public applications that wish to provide immutable program flow with 'untrusted' third parties. This allows the disintermediation of business models that once required a trusted middleman (like banks, retailers, clearers etc.) that would validate that a given action had taken place.
Hello Gang. I have a question. Can I encrypt data in fabric so that 1) it can be processed by some chaincode 2) it can be read by party A and party B and not Party C 3) where all nodes have the same data? or can this only be done with Channels in V1?
Not sure if this is the correct channel, but I am looking into trying to perform an installProposal request. I am using the nodeJS sdk code which I pulled down today. It looks like something worked as the peer contains a file on the chaincodes directory but the response I got back I couldn't send the transaction to the orderer as it looks like the content of the endorsement is null (I don't get back a signature of the peer).
```
[ { version: 0,
timestamp: null,
response: [Object],
payload:
Setting up a development environment on local machine. Got everything cloned from Garrett, logged into the virtual machine, went to the appropriate folder and made peer. I get a error, cannnot stat 'build/docker/gotools/bin/protoc-gen-go' : No such file or directory. I found the same folder on my local machine, put that folder in the directory location in the virtual machine, restarted the machine, but I still get the same error??????
Above question is using Vagrant VM as explained in the github repository for IBM Fabric. A question I have related to setting up a local development environment is if Docker can host the Fabric kernel independently of the Vagrant VM and what is the best practice for setting up a local development environment for Ubuntu 16.04?
Setting up v.06 BTW.
Has joined the channel.
Message Attachments
Hi All, i am having error in command :-
I am having error in command :-
npm install -g hfc
resolved : sudo apt install nodejs-legacy
Has joined the channel.
Has joined the channel.
@elli-androulaki can you please answer @stanacton quesiton up above
Hi @stanacton,
Hi @stanacton,
Hi
>Can I encrypt data in fabric so that 1) it can be processed by some chaincode 2) it can be read by party A and party B and not Party C 3) where all nodes have the same data? or can this only be done with Channels in V1?
So, Fabric v1.0 does not accommodate encryption features at the platform level like in 0.6. If two parties need to have transactions in private, then they would need to create a different channel with them as only participants for them to transact privately.
Has joined the channel.
Having said that, we plan to provide a library that would allow the application (client-sdk enhancement) and chaincode side to encrypt/decrypt chaincode state with cryptographic material that would be passed by the application to the chainode inside a transient data field of the proposal.
Transient data field of proposal is not included in any chain, its content is passed to the chaincode to use it.
@elli-androulaki thanks for the response. Is the encrypt/decrypt client-sdk feature going to be in v1?
It will be a separate library that the sdk could also use, but will be independently developed after full v1 cycle is in place.
It will be a separate library that the sdk could also use, but will be independently developed after full v1 cycle is in place/stabilized.
Great! That's fantastic information! I know everything is in flux, but is that written down anywhere?
So point (2) from your list above could be accommodated assuming that you would enrypt chaincode state with some keys, the application has pre-shared with A, and B, and which the application passes to the chaincode through transient data.
No, not yet, unfortunately; but we will share out design around this soon!
No, not yet, unfortunately; but we will share our proposed design around this soon!
@elli-androulaki Thanks for the info. So would it be possible then with that new tool to have chancode that has workflow for bonds.... and any two counterparties can use that code... but it will then encrypt it just for those counterparties?
@elli-androulaki in fact.. forget that question for now.. I can look at it when it comes out... thanks so much for your answer. @weeds thanks for the prompt
sure! will advertize to fabric-crypto when we have our proposal written down.
sure! will advertise to fabric-crypto when we have our proposal written down.
Has joined the channel.
Has joined the channel.
I have noticed that the endorser.enabled parameter has been removed from peer/core.yaml, does this mean that all the peer can endorse a transaction if installed with application chaincode?
Has joined the channel.
@elli-androulaki : We may take it to fabric-crypto , but why do want to get into the business of pre-shared key ? Why you do not want to use something like Public Key Encryption ?
@elli-androulaki : We may take it to fabric-crypto , but why do we want to get into the business of pre-shared key ? Why you do not want to use something like Public Key Encryption ?
Has joined the channel.
Why we need VM to setup
and poor doc
Has joined the channel.
Hello everyone
has anyone successfully setup HyperLedger Fabric on Ubuntu? I am running into issues when running "make peer" the error is with the context library in CCProviderImpl.go file. Any help is greatly appreciated
Has joined the channel.
[ ](https://chat.hyperledger.org/channel/fabric?msg=moAKuD8iHPNgXrkRa) @saridsa1 Never got your error, but may you try make dist-clean?
@ashutosh_kumar
>why do we want to get into the business of pre-shared key ?
So, the keys are shared on a per-invocation basis, for the chaincode to use it within its logic to decrypt/encrypt parts of the state, without touching the platform at all.
> Why you do not want to use something like Public Key Encryption ?
@ashutosh_kumar
>why do we want to get into the business of pre-shared key ?
So, the keys are shared on a per-invocation basis, for the chaincode to use it within its logic to decrypt/encrypt parts of the state, without touching the platform at all.
> Why you do not want to use something like Public Key Encryption ?
We could use some in the future, and to the direction that the community decides. There can be multiple ways to do so, but it could require that we change some part of the fabric. E.g., we could leverage the pk of the endorser and have the encrypted key residing to the blockchain but we would need to have endorsers decrypt that info (at the platform level) and be responsible for managing that key, we could have the chaincode have its own key, but we would require that this key is bound to the chaincode identifier such that all parties are certain of the encryption key to use when invoking it.
@ashutosh_kumar
>why do we want to get into the business of pre-shared key ?
So, the keys are shared on a per-invocation basis, for the chaincode to use it within its logic to decrypt/encrypt parts of the state, without touching the platform at all.
> Why you do not want to use something like Public Key Encryption ?
In reality, we do use cause transient data is moved to the chaincode through TLS. However, it is true that the keys do not reside (not even in encrypted form) to the chain.
On one hand the application(chaincode) would be able to do that and store encrypted keys as part of its state that is visible to the ledger.
@ashutosh_kumar
>why do we want to get into the business of pre-shared key ?
So, the keys are shared on a per-invocation basis, for the chaincode to use it within its logic to decrypt/encrypt parts of the state, without touching the platform at all.
> Why you do not want to use something like Public Key Encryption ?
In reality, we do use cause transient data is moved to the chaincode through TLS. However, it is true that the keys do not reside (not even in encrypted form) to the chain.
If (encrypted keys) are to be stored on the blockchain, the application(chaincode) would be able to do that and store encrypted keys as part of its state that is visible to the ledger.
Hello, i have some issue that cannot understand completely. When i try to endorse transaction i got this error:
rpc error: code = 2 desc = The proposal does not comply with the channel writers for channel myc1, error Failed to reach implicit threshold of 2 sub-policies, required 2 remaining
Can someone help me understand from where this requirement for 2 policies comes from and why request to Endorce transaction require this request to be endorsed. What I do not understand?
Thank you!
Has joined the channel.
Anyone know if Vagrant environments still supported in v1?
How to roll back a transaction? Just like the DAO, if this happens, how can we deal with this?
Has joined the channel.
[ ](https://chat.hyperledger.org/channel/fabric?msg=nW5LtDf9FDNRgaDEn) @pd93 yes, I'm using it on Win
Hello, I would like to know the legal consideration of Fabric, chaincode itself was kept in ledger and also a reference to some legal clause / paper, or some contracts template with stamps?
@Ying Thanks. I'm running Windows 10. Just trying to work out if there's any way of building/running without having to use Vagrant. The docs seem to suggest you can, but aren't specific.
It'd be great if I could install make for Windows and run natively
or, fabric is just a technical tool and platform, do not involves any suggestion on regulation and legal part itself, which belows to business procedure?
[ ](https://chat.hyperl edger.org/channel/fabric?msg=heGxThee3ixecBr5H) @pd93 err...sdk
sdk works fine in windows
@Ying. I mean building images for the peer etc.. nothing to do with the sdk
[ ](https://chat.hyperledger.org/channel/fabric?msg=HMZuRYHx9h6eckJRa) @pd93 guess that's a hard job, good luck
Has joined the channel.
Has joined the channel.
Has joined the channel.
@jyellick @muralisr This had been working before "out of the box" fabric / fabric_ca .. now seeing this :
java.lang.Exception: Not enough endorsers for install :0. Sending proposal to peer failed because of gRPC failure=Status{code=UNKNOWN, description=The proposal does not comply with the channel writers for channel testchainid, error Failed to reach implicit threshold of 1 sub-policies, required 1 remaining, cause=null}
at org.hyperledger.fabric.sdk.End2endIT.setup(End2endIT.java:136)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:68)
at com.intellij.rt.execution.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:51)
at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:237)
at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:70)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at com.intellij.rt.execution.application.AppMain.main(AppMain.java:147)
I have same issue, it is from update from yesterday.
this is what i found in logs
DEBU 32b Returning dummy reject all policy because Readers could not be found in /XXXFakeOrg/Readers
DEBU 32e Returning dummy reject all policy because Writers could not be found in /XXXFakeOrg/Writers
DEBU 330 Returning dummy reject all policy because Admins could not be found in /XXXFakeOrg/Admins
So it seems that it returns reject policy
And the core of the problem is this message:
No such policy type: Admins
Can some of the developers to help?
on step http://hyperledger-fabric.readthedocs.io/en/latest/asset_setup/#use-docker-to-spawn-network-entities-createjoin-a-channel
I got error "ERROR: In file './docker-compose-gettingstarted.yml' service 'version' doesn't have any configuration options. All top level keys in your docker-compose.yml must map to a dictionary of configuration options."
@rrader documentation is not actual, code is changed very fast. This is expected from product that is not in alpha version.
@rrader documentation is not actual, code is changing very fast. This is expected from product that is not in alpha version.
okay, bu how to fix?
okay, but how to fix?
i have no idea, sorry
Has joined the channel.
@muralisr ping
@rrader What is the docker compose version you have?
@rameshthoomu 1.5.2
@rrader @gatakka @rickr https://gerrit.hyperledger.org/r/#/c/6417/ this CR fixes the peer to properly encode that admins policy
thank you!
Pls upgrade docker compose version to >1.7
@rameshthoomu thanks, it works
also you must run it as sudo
@greg.haskins pong
@muralisr was just pinging about the ccSpec stuff that we already discussed in DM
ok. just wanted to make sure
@muralisr on a related topic, it looks like the LCCC uses a different CDS validation path
i am thinking it should use the proputils variant
any thoughts?
both LCCC and proputils do the simple unmarshal, but only proputils also calls platform.ValidateCDS()
@greg.haskins back
@muralisr currently testing this: http://pastebin.com/xgnk21A8
ok. now I see what you meant
looks good. on a different but related topic...we should also clean up "packaging" part of it... will have a JIRA soon for you to look
ok
https://gerrit.hyperledger.org/r/#/c/6433/ @muralisr
+2, if the CI fails it simply CANNOT be because of the fix :-)
+2ed, if the CI fails it simply CANNOT be because of the fix :-)
on a related note: we should discuss chaincode spec/deploymentspec/type
because how we have it now seems a bit illogical
issue 1) it probably doesnt make sense to send a deployment-spec in instantiate() and possibly upgrade() though I have a question about upgrade semantics
issue 2) it probably only makes sense to have chaincode.Type in deployment spec
anything else, the type doesn't matter...it just is what it is
issue 3) we really should probably target SCC invocations at Type=SYSTEM rather than GOLANG
I realize that system chaincode _is_ written in golang, but thats irrelevant in this context
to me, the Type should indicate the platform handler, and SCC is not currently tied into that at all
Has joined the channel.
Has joined the channel.
@johnwolpert I was speaking with Mark Parzygnat about coming up to speed and participating. He is out of office but mentioned you may be available.
@elli-androulaki as a follow up to our conversation yesterday, was this the feature that's been removed in 1.0? https://hyperledger-fabric.readthedocs.io/en/latest/FAQ/confidentiality_FAQ/#how-is-the-confidentiality-of-transactions-and-business-logic-achieved
@stanacton, correct
@elli-androulaki thanks again!
Sure!
Are there any docker images for v1 around yet or do I need to build them myself?
@pd93 there are alpha images, yes
Yeah for the preview
Where can I find them?
I'm checking now. I followed a tutorial last week that set it all up and I seem to have misplaced the link
here it is: http://hyperledger-fabric.readthedocs.io/en/latest/asset_setup/
Yeah, I saw the hackfest stuff, but didn't realise it was v1
Does that mean 0.7 == v1-preview?
@markparz I have a question about using Directed Acyclic Graphs on Hyperledger Fabric, who would be the best to consult ?
@pd93 it uses orderers and peers so I assume it's 1.0 stuff
could be wrong tho
Has joined the channel.
Ok cool. As long as it's 1.0 based, I'll use it for now
Thanks :)
Hi guys, I've searched and google a hyperledger docs but unfortunately I could not find the answer. Could someone help with this issue: "Error: Error endorsing chaincode: rpc error: code = 12 desc = unknown service protos.Endorser"?
With latest fabric 'Cleanup docs', which includes 'Fix break in master', node sdk end-to-end step2 (instantiate) which uses the default 'testchainid' is failing with:
```Peer.js]: GRPC client got an error response from the peer. Error: The proposal does not comply with the channel writers for channel testchainid, error Failed to reach implicit threshold of 1 sub-policies, required 1 remaining```
Does this require a change on the sdk side also?
Has joined the channel.
trying to install hackfest setup from http://hyperledger-fabric.readthedocs.io/en/latest/asset_setup/. Getting certificate error when pulling the image configuration for fabric-ca. is a fix on the way?
@pd93 http://hyperledger-fabric.readthedocs.io/en/latest/included/ is where you can find the hackfest images, but in next week we will have another update and have it run continuously
it is version 1.0 based in what i sent to you
@nickgaski Hi Nick- can you help @beckmann
wondering if we need to update the docs also as a result
@tulioribeiro I would suggesting going to the fabric-peer-endorser-comitter channel and asking
@errf
@weeds I've gone through the hackfest setup, but I'm getting `Don't have certificate for membership:
Not sure if that's related
@pd93 @nickgaski Nick- can i get you to help?
Yes I will help. Please give me thirty minutes. I am on my phone right now
thanks
@nickgaski Thanks, I'll be here
The issue is with the port. Can you curl the config.json from sdk/master branch and the other five node files from v1.0-alpha branch . You'll want to remove all the node code and node_modules pull those six and do an npm install again. See if that works, I will solve for you when I get back in office
I'll give it a go :thumbsup:
[ ](https://chat.hyperledger.org/channel/fabric?msg=Tp889sW8M6Nh3KM6Q) @cdaughtr issue was discussed earlier in this channel, see https://chat.hyperledger.org/channel/fabric?msg=YbNeC3GYiSAZXuGfh
@jyellick I have that fix installed ('Fix break in master' = 6417) and still see the problem.
Has joined the channel.
@nickgaski Tried with the files you suggested. I still have the same errors
@cdaughtr How are you creating the channel?
We don't create it, just use the default 'testchainid'.
Are you signing the proposal?
yes
@cdaughtr If you'd like to send me logs on debug, I would be happy to take a look to further help you
You want the docker logs?
Has joined the channel.
@pd93 - taking a look now.
@jyellick @cdaughtr the same problem was reported by the CI job, here's the docker log: https://jenkins.hyperledger.org/view/FIT/job/FIT-node-x86_64/156/artifact/gopath/src/github.com/hyperledger/fabric-sdk-node/test/fixtures/dockerlogfile.log
the corresponding log from the sdk tests: https://jenkins.hyperledger.org/view/FIT/job/FIT-node-x86_64/156/consoleFull
Thanks @jimthematrix looking now
in the sdk log you can see
```[Peer.js]: GRPC client got an error response from the peer. Error: The proposal does not comply with the channel writers for channel testchainid, error Failed to reach implicit threshold of 1 sub-policies, required 1 remaining```
@muralisr ^^^
I just moved up to the very latest and still see this too
yes the CI job runs the latest of all repos
```
[32mvp0_1 |[0m 2017-02-23 18:47:45.359 UTC [protoutils] validateChaincodeProposalMessage -> INFO 409[0m validateChaincodeProposalMessage info: header extension references chaincode name:"lccc"
[32mvp0_1 |[0m [36m2017-02-23 18:47:45.359 UTC [kvledger] retrieveTransactionByID -> DEBU 40a[0m retrieveTransactionByID() - txId = [f373d843970bf55ba9f2c4b1db69e6fd3a41c3426eb460c1e12f1f3ad3234bbf]
[35mvp1_1 |[0m [36m2017-02-23 18:47:45.359 UTC [cauthdsl] func2 -> DEBU 44b[0m Principal evaluation starts: (&{%!s(int32=0)}) (used [%!s(bool=false)])
[32mvp0_1 |[0m [36m2017-02-23 18:47:45.359 UTC [common/policies] GetPolicy -> DEBU 40b[0m Returning policy Application/Admins for evaluation
[35mvp1_1 |[0m [36m2017-02-23 18:47:45.360 UTC [cauthdsl] func2 -> DEBU 44c[0m Principal evaluation fails: (&{%!s(int32=0)})%!(EXTRA []bool=[false])
[32mvp0_1 |[0m [36m2017-02-23 18:47:45.359 UTC [cauthdsl] func1 -> DEBU 40c[0m Gate evaluation starts: (&{N:1 policies:
This looks to me like the identity supplied is not an admin identity and does not have authority to deploy chaincode
The policies are all properly encoded in the configuration, and the policies are found, but, when comparing the identity to the msp principal specified by the admins policy, it finds that the supplied identity does not satisfy that msp principal.
@jimthematrix @jimthematrix @cdaughtr From a policy perspective, this is all as expected. But it looks like the cert you are transacting with does not have admin rights.
@jimthematrix @rickr @cdaughtr From a policy perspective, this is all as expected. But it looks like the cert you are transacting with does not have admin rights.
ok, makes sense, so how is the default chain's admin policy set up?
It requires one signature from a certificate which satisfies the MSP's admin principal
so looks like the peer's local msp was not properly configured?
This is not about the peer's local MSP
This is the certificate material being embedded in the proposal sent to the peer
Can you paste the serial number of the cert being embedded into the tx?
ok i got confused, i thought the error happened in vadliation
(Or any other identifying piece of info for the cert)
but it's in endorser right?
so it's validating the app's signing identity
The endorser is evaluating the signature the SDK encodes on the proposal
It checks to see if the signing identity is an admin identity
ok
And, according to the MSP for that channel and that org, it is not
```Certificate:
Data:
Version: 3 (0x2)
Serial Number:
33:6d:4f:ed:e3:22:2e:d5:c7:81:91:d3:01:5f:48:04:d5:92:52:1f
Signature Algorithm: ecdsa-with-SHA256
Issuer: C=US, ST=California, L=San Francisco, O=Internet Widgets, Inc., OU=WWW, CN=example.com
Validity
Not Before: Feb 17 00:26:00 2017 GMT
Not After : Jan 16 08:26:00 2018 GMT
Subject: CN=admin
Subject Public Key Info:
Public Key Algorithm: id-ecPublicKey
EC Public Key:
pub:
04:f1:3b:c5:de:38:0f:b1:27:e9:47:89:35:3f:6b:
c3:b2:c8:20:a7:5f:6b:e3:a5:b8:1a:c9:5f:59:3c:
ca:48:c2:d6:fd:b3:4b:37:01:09:40:82:ab:90:eb:
79:fc:4f:16:dc:85:8c:03:db:0d:92:6d:c3:28:ba:
b1:2a:63:b9:a1
ASN1 OID: prime256v1
X509v3 extensions:
X509v3 Key Usage: critical
Certificate Sign
X509v3 Basic Constraints: critical
CA:FALSE
X509v3 Subject Key Identifier:
A8:F9:DD:63:68:78:69:6D:02:2B:5B:CE:CC:01:C6:9C:A4:62:A2:17
X509v3 Authority Key Identifier:
keyid:17:67:42:3D:AA:9E:82:3F:C4:C5:1D:9F:5B:C3:99:D1:B5:9C:48:10
Signature Algorithm: ecdsa-with-SHA256
30:45:02:20:02:dc:ff:d3:a7:5e:d8:d8:9a:68:98:a6:0d:ff:
82:35:bb:d6:ca:e0:38:7e:74:98:1c:d9:4d:f7:04:87:62:2f:
02:21:00:aa:39:42:e3:9f:95:8e:aa:ec:0f:da:5d:7e:24:6d:
f3:0f:47:d9:3c:36:ce:c4:88:c6:77:7c:89:0d:b6:15:18
```
Ah, yes, there is your problem
this is one of them, not exactly the one used by the CI job, but issued the same way (by fabric-ca using the default server key)
The only admin cert defined in the default MSP has serial number: `04:45:70:b1:2c:74:4e:6a:9d:6f:33:70:95:e3:41:07:3a:08:4f:4c`
So this is actually a positive result for the system, and it is working as expected
is that configurable at the moment?
if not, then we need the cert and private key for that signing identity
It is configurable if you put the additional admin cert in the MSP's admincerts directory before generating the MSPConfig
Or, that cert and signing key are in `fabric/msp/sampleconfig/admincerts/admincert.pem` and `fabric/msp/sampleconfig/keystore/key.pem` respectively
ok, makes sense. thanks Jason
final question, this policy is only enforced on chaincode instantiate call correct?
@jyellick ^^^
This is a better question for @muralisr but, this specific policy is only invoked around chaincode invocations which trigger the lifecycle system chaincode. So, you can expect for invocations of other chaincode generally not to require admin authority (though I believe they could be configured to require it)
Has joined the channel.
there should be some protection around private key. we might revisit it later.
[ ](https://chat.hyperledger.org/channel/fabric?msg=KKAP5kLA4DXj4vjNf) @pd93 There was a request to create v1-preview images but it was never completed
https://gerrit.hyperledger.org/r/#/c/5865/
https://gerrit.hyperledger.org/r/#/c/5871/
Has joined the channel.
When I first execute the make peer, I return an error message. How to solve this problem？'vagrant@hyperledger-devenv:v0.3.0-4eec836:/opt/gopath/src/github.com/hyperledger/fabric$ cd $GOPATH/src/github.com/hyperledger/fabric
vagrant@hyperledger-devenv:v0.3.0-4eec836:/opt/gopath/src/github.com/hyperledger/fabric$ make peer
mkdir -p build/image/ccenv/payload
cp build/docker/gotools/bin/protoc-gen-go build/bin/chaintool build/goshim.tar.bz2 build/image/ccenv/payload
cp: cannot stat 'build/docker/gotools/bin/protoc-gen-go': No such file or directory
Makefile:214: recipe for target 'build/image/ccenv/payload' failed
make: *** [build/image/ccenv/payload] Error 1
'
[ ](https://chat.hyperledger.org/channel/fabric?msg=jtySDvPRX7P2RG4we) @raulshen you may find that Dockerfile in build/images/ccenv and try it manually
Hi guys: Has anyone successfully go through all the test case on this doc(make all)http://hyperledger-fabric.readthedocs.io/en/latest/dev-setup/build/.
My question is : what is the success build mark after "make all" . I see this a sentence said "behave test will only work on vagrant env", so what should i do on docker on mac?? Any Ideas?
make docker
Hi guys, I'm getting an error with ubuntu on the `npm install` step here `https://hyperledger-fabric.readthedocs.io/en/latest/asset_setup/` I'm getting the error `Failed at the hashtable@2.0.2 install script 'node-gyp configure build'.`
I found this logged in JIRA `https://jira.hyperledger.org/browse/FAB-1215` but what's the resolution?
could you parse all the error?
@arvindupadhyaya what platform are you using? I've seen this before on Windows
ubuntu
Hmm.. The problem for me on Windows was that I needed the windows build tools. I also updated node-gyp and those fixed the problem
I've installed python.. but it didn't resolve the issue
thanks for the input @pd93 I'll search around for a similar thing for ubuntu..
not about python.I remember is a dependency problem , so i need the full output
`npm ERR! Linux 4.4.0-64-generic
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "install"
npm ERR! node v6.10.0
npm ERR! npm v3.10.10
npm ERR! code ELIFECYCLE
npm ERR! hashtable@2.0.2 install: `node-gyp configure build`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the hashtable@2.0.2 install script 'node-gyp configure build'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the hashtable package,
npm ERR! not with npm itself.`
well, Its come from different error.
Did anyone encounter this problem?
~~~
core/chaincode/ccproviderimpl.go:20:2: cannot find package "context" in any of:
/opt/gopath/src/github.com/hyperledger/fabric/vendor/context (vendor tree)
/usr/lib/go-1.6/src/context (from $GOROOT)
/opt/gopath/src/context (from $GOPATH)
Makefile:176: recipe for target 'build/bin/peer' failed
make: *** [build/bin/peer] Error 1
~~~
your go version might be too low, check with "go version", hyperledger requires v1.7+
@Ying Thank you very much. Do you mean that you need to manually create a folder
not extaclly, you could do "make clean" and then "make", to force it to redownload automatically, or you could change the makefile, from "curl xxx" to "cp backup_chaintool target_place"
[ ](https://chat.hyperledger.org/channel/fabric?msg=mhjYC8BbZnySR5oKG) @greg.haskins Do you have any idea when this might be completed? It'd make life quite a bit easier for Windows users who don't leverage Vagrant
@aratic thanks a lot.
@aratic Thank you, aratic. The problem is solved, my go version is too low.
HI fellows：
When I try to connect from client to ca-server，using this command：fabric-ca client enroll -config client-config.json admin adminpw http://127.0.0.1:7054 csr.json. And it give me back such error :
2017/02/24 01:31:27 [INFO] Fabric-ca Client Configuration File: client-config.json
open http://127.0.0.1:7054: no such file or directory
kinds of wired.. Any ideas? BTW, I have boot up my ca server in localhost:7054
hi can anyone advice on this error?
pg@pg-GL552JX:~/workspace/fabric-app$ GOPATH=$PWD node deploy.js
info: Returning a new winston logger with default configurations
info: [Chain.js]: Constructed Chain instance: name - fabric-client1, securityEnabled: true, TCert download batch size: 10, network mode: true
info: [Peer.js]: Peer.const - url: grpc://localhost:8051 options grpc.ssl_target_name_override=tlsca, grpc.default_authority=tlsca
info: [Peer.js]: Peer.const - url: grpc://localhost:8055 options grpc.ssl_target_name_override=tlsca, grpc.default_authority=tlsca
info: [Peer.js]: Peer.const - url: grpc://localhost:8056 options grpc.ssl_target_name_override=tlsca, grpc.default_authority=tlsca
info: [crypto_ecdsa_aes]: This class requires a KeyValueStore to save keys, no store was passed in, using the default store /home/pg/.hfc-key-store
info: [Client.js]: Successfully loaded user "admin" from local key value store
[2017-02-24 14:39:18.625] [INFO] Helper - Successfully loaded member from persistence
[2017-02-24 14:39:18.626] [INFO] DEPLOY - Successfully obtained enrolled user to deploy the chaincode
[2017-02-24 14:39:18.626] [INFO] DEPLOY - Executing Deploy
error: [Peer.js]: GRPC client got an error response from the peer. Error: Failed to deserialize creator identity, err MSP DEFAULT is unknown
@uber.twin : I ran into this issue and it occurs intermittently, just try the deploy once more
Has joined the channel.
Problem with VerifySignature to simple caller verification, this is what I have (very typical) :
.. continue.. sigma, err := stub.GetCallerMetadata()
payload, err := stub.GetPayload()
binding, err := stub.GetBinding()
pass, err := stub.VerifySignature(
certificate,
sigma,
append(payload, binding...),
) ... .... VerifySignature returned ""Invalid hash algorithm", any idea what was the problem?
As mentioned above I am also seeing the error Error: Failed to deserialize creator identity, err MSP DEFAULT is unknown. There was mention that you could get this error if the channel you are using hasn't been created but in my case I am using testchannelid and still get the issue. How would I go about trying to determine what the problem is as it is probably something I have done wrong
Has joined the channel.
Further to the above, I tried creating my own channel and using that instead. This time I get a different error message
Error: The creator's signature over the proposal is not valid, err The signature is invalid
Has joined the channel.
Has joined the channel.
[ ](https://chat.hyperledger.org/channel/fabric?msg=iw8uH2Dv83vKREwes) @jansony1
Anyone know that??
Has joined the channel.
As things stand right now, have we built logic into the peer to work with a list of orderers? i.e. if orderer1 in the latest config block is non-responsive, switch to orderer2, etc. /cc @muralisr @binhn
@kostas ^^^ a committer/gossip question I'd think @yacovm @C0rWin ?
@kostas @muralisr I have working item for this
@C0rWin: That's great. Do you happen to have a JIRA number handy so that I can track it?
There is an JIRA for sure, I am at the airport with phone, so will send you it to you later
No problem, thanks.
Or just seek for items in progress
Assigned to me
@C0rWin: Got it, thanks: https://jira.hyperledger.org/browse/FAB-1938
Posting sneha's question from #fabric-quality channel that uses SFHackfest Images - @snehas
```
Hi All,
In invode method of chaincode, instead of returning shim.Success() I am returning custom pb.Response object.
for with status value as 201.
Below is the method which I am calling instead of shim.Success()
func successResponse(payload []byte, status int32) pb.Response {
return pb.Response{
Status: status,
Payload: payload,
}
}
But I am getting error Error: Error endorsing invoke: rpc error: code = 2 desc =
If I use shim.Success(), it works.
Is it that we have to return shim.Success() or am I doing some mistake? Please provide your inputs.
```
We are using SF Hackfest Images. https://github.com/hyperledger/fabric/blob/master/core/chaincode/shim/response.go#L23
Posting sneha's question from #fabric-quality channel - @snehas
```
Hi All,
In invode method of chaincode, instead of returning shim.Success() I am returning custom pb.Response object.
for with status value as 201.
Below is the method which I am calling instead of shim.Success()
func successResponse(payload []byte, status int32) pb.Response {
return pb.Response{
Status: status,
Payload: payload,
}
}
But I am getting error Error: Error endorsing invoke: rpc error: code = 2 desc =
If I use shim.Success(), it works.
Is it that we have to return shim.Success() or am I doing some mistake? Please provide your inputs.
```
We are using SF Hackfest Images. https://github.com/hyperledger/fabric/blob/master/core/chaincode/shim/response.go#L23
Hi - How can I request access to Jira? I want to open a new issue.
Both java and node sdk's, with today's fabric are getting
```GRPC client got an error response from the peer. Error: The creator's signature over the proposal is not valid, err The signature is invalid```.
Both java and node sdk's, with today's fabric are getting
`GRPC client got an error response from the peer. Error: The creator's signature over the proposal is not valid, err The signature is invalid`.
Moving this discussion from #fabric-sdk-node to #fabric:
Both java and node sdk's, with today's fabric are getting
`GRPC client got an error response from the peer. Error: The creator's signature over the proposal is not valid, err The signature is invalid`.
node sdk on fabric 536a3fd632c0d38bde41563db3997148350bdcc2
Merge "Gossip- Don't log sending to empty slice of peers"
Moving this discussion from #fabric-consensus to #fabric:
Both java and node sdk's, with today's fabric are getting
`GRPC client got an error response from the peer. Error: The creator's signature over the proposal is not valid, err The signature is invalid`.
node sdk on fabric 536a3fd632c0d38bde41563db3997148350bdcc2
Merge "Gossip- Don't log sending to empty slice of peers"
This seems to be an error simply validating the signature, nothing to do with policies or config
@vpaprots Could this be related to BCCSP?
@jyellick perhaps, but I haven't changed the signing part, just how one gets to the keys. Would had expected an error earlier..
```
```
mspObj := mspmgmt.GetIdentityDeserializer(ChainID)
if mspObj == nil {
return fmt.Errorf("could not get msp for chain [%s]", ChainID)
}
// get the identity of the creator
creator, err := mspObj.DeserializeIdentity(creatorBytes)
if err != nil {
return fmt.Errorf("Failed to deserialize creator identity, err %s", err)
}
putilsLogger.Infof("checkSignatureFromCreator info: creator is %s", creator.GetIdentifier())
// ensure that creator is a valid certificate
err = creator.Validate()
if err != nil {
return fmt.Errorf("The creator certificate is not valid, err %s", err)
}
putilsLogger.Infof("checkSignatureFromCreator info: creator is valid")
// validate the signature
err = creator.Verify(msg, sig)
if err != nil {
return fmt.Errorf("The creator's signature over the proposal is not valid, err %s", err)
}
```
This appears to be the block of code throwing the error
```
mspObj := mspmgmt.GetIdentityDeserializer(ChainID)
if mspObj == nil {
return fmt.Errorf("could not get msp for chain [%s]", ChainID)
}
// get the identity of the creator
creator, err := mspObj.DeserializeIdentity(creatorBytes)
if err != nil {
return fmt.Errorf("Failed to deserialize creator identity, err %s", err)
}
putilsLogger.Infof("checkSignatureFromCreator info: creator is %s", creator.GetIdentifier())
// ensure that creator is a valid certificate
err = creator.Validate()
if err != nil {
return fmt.Errorf("The creator certificate is not valid, err %s", err)
}
putilsLogger.Infof("checkSignatureFromCreator info: creator is valid")
// validate the signature
err = creator.Verify(msg, sig)
if err != nil {
return fmt.Errorf("The creator's signature over the proposal is not valid, err %s", err)
}
```
This appears to be the block of code throwing the error
So, it appears to me that:
1. MSP Manager finds the right deserializing MSP
2. MSP maps the identity to the creator
3. Signature is not validated as having originated from the creator
Since this is broken in Java, and Node SDKs, and it used to be working, presumably, the signature is correct. Which is why I thought maybe BCCSP? That this has changed recently and could cause the signature validation to fail?
the only thing I can think of is the signature itself.. its not really 'typed', so protobufs just sees a []byte.. wouldnt be to hard to corrupt thing there.. stilll, that code was untouched. maybe we used wrong cert to sign? that could be what my change could had caused. we dont use many certs though..
@vpaprots can you work with @rickr to figure out if the right certs are being used?
second theory, that we are somehow getting hold of bad cert..
yep can do
Thanks!
@vpaprots I'm working this weekend, so let me know if you want me to try anything from the node sdk side. I have to get some new queries working by Monday and am not sure if this will block those as well. Will be implementing node sdk using backend of https://jira.hyperledger.org/browse/FAB-2234.
@vpaprots FYI opened a JIRA for this https://jira.hyperledger.org/browse/FAB-2463
Has joined the channel.
@lehors @rickr @markparz I set up a test project with a new JIRA workflow, could you try it out and let me know if you want something like it for fabric? https://jira.hyperledger.org/projects/WFT/issues/?filter=allopenissues
@lehors @rickr @markparz I set up a test project with a new JIRA workflow, could you try it out and let me know if you want something like it for cello? https://jira.hyperledger.org/projects/WFT/issues/?filter=allopenissues
Ok, thanks
you're all admins of the project, so you have super powers.
[ ](https://chat.hyperledger.org/channel/fabric?msg=fbQadvBsQT6kAWR2i) @rjones Looks good to me
@rickr is it better or worse than the default workflow?
unrelated but I wish JIRA would allow you to add additional watchers
Yeah just looking at I think it's an improment
Yeah just looking at I think it's an improvement
Has joined the channel.
Hi all, I have a build question. I'm on Max OS Sierra, and followed the instructions to setup my dev environment here https://hyperledger-fabric.readthedocs.io/en/latest/dev-setup/devenv/ but when trying to build with `make dist-clean all` it gave me the error ```Step 3/4 : ADD payload/goshim.tar.bz2 $GOPATH/src/
Error processing tar file(bzip2 data invalid: bad magic value in continuation file):
make: *** [build/image/ccenv/.dummy-x86_64-0.7.0-snapshot-bb5a53f] Error 1```
Can anyone tell me what this could be caused by? I installed gnu-tar, but maybe I didn't install it properly?
Hi all, I have a build question. I'm on Max OS Sierra, and followed the instructions to setup my dev environment here https://hyperledger-fabric.readthedocs.io/en/latest/dev-setup/devenv/ but when trying to build with `make dist-clean all` it gave me the error ```Step 3/4 : ADD payload/goshim.tar.bz2 $GOPATH/src/
Error processing tar file(bzip2 data invalid: bad magic value in continuation file):
make: *** [build/image/ccenv/.dummy-x86_64-0.7.0-snapshot-bb5a53f] Error 1```
Can anyone tell me what this could be caused by? I installed gnu-tar, but maybe I didn't install it properly?
@rjones Once again not really related but just to give you something else to do :) Is there any way to automatically link gerrit to JIRA? It be great to see in the JIRA references to the gerrit submissions
the plugin to do that has bugs and I can't roll it out right now
darn -- would be great
perhaps #general is a better forum?
why nothing much ever going on here on fabric is there ?
Hi all, how does one build the peer/orderer images with Java disabled? I have no desire to use Java, and I'd rather not store the extra gigabyte or so that the jdk and javaenv images take up
@vdods I dont think there is any way to build (today) without building the java support, but you can certainly get rid of javaenv after its done
the peer/orderer images will not have the JDK
you wont really be saving much though, since you do still need ccenv and most of what is in javaenv would also be in ccenv
Thanks!
Has joined the channel.
Can anyone help me with this?
```
xxx@ubuntu:/opt/gopath/src/github.com/hyperledger/fabric$ make
mkdir -p build/image/ccenv/payload
cp build/docker/gotools/bin/protoc-gen-go build/bin/chaintool build/goshim.tar.bz2 build/image/ccenv/payload
mkdir -p build/image/javaenv/payload
cp build/javashim.tar.bz2 build/protos.tar.bz2 settings.gradle build/image/javaenv/payload
LINT: Running code checks..
Checking ./core
./scripts/golinter.sh: line 11: goimports: command not found
Makefile:121: recipe for target 'linter' failed
make: *** [linter] Error 127
xxx@ubuntu:/opt/gopath/src/github.com/hyperledger/fabric$ which goimports
/opt/gopath/bin/goimports
hxy@ubuntu:/opt/gopath/src/github.com/hyperledger/fabric$
```
@vpaprots [ ](https://chat.hyperledger.org/channel/fabric?msg=4GyciNywrMGjH4dHk) @rickr @vpaprots @muralisr Any updates on this ?
Has joined the channel.
Hi, there. I was wondering the fabric developers' are considering integrating with EVM to provide the Gas-like mechanism.
Our team use hyperledger/fabric as our blockchian platform, but we noticed that fabric can't quantify the cost of chaincode executions
So I want to know if you're interested in integrating fabric with Ethereum's EVM, if so, I would like to help.
Has joined the channel.
@RyanElliott
Install Brew: http://brew.sh
run `brew install gnu-tar —-with-default-names`
@RyanElliott
Install Brew: http://brew.sh
run `brew install gnu-tar —-with-default-names`
@RyanElliott
Install Brew: http://brew.sh
run `brew install gnu-tar --with-default-names`
(the key to fixing the problem is 'with-default-names')
[ ](https://chat.hyperledger.org/channel/fabric?msg=fbQadvBsQT6kAWR2i) @rjones I have to ask a stupid question, what is this giving me over the boards? is this an overall view for all items? @Clayton Sims will like to see this too
@simsc
Has joined the channel.
@markparz this isn't about the view you get but the workflow: the different states a JIRA ticket goes through
what we currently have is very loose
and as a result confusing
it's not always clear what the next state should be
here is an example: https://jira.hyperledger.org/projects/FAB/issues/FAB-1918?filter=allopenissues
so, this is a different workflow taken from a different proejct Ry works on that we could adopt - possibly with some modification
@rjones: this looks pretty good to me, my only question is about review. I don't see review in the workflow and I saw we currently use it - not that I can say that we ought to have it!
AH got ya, I was looking at the wrong thing, even though ry did clearly say workflow... lol... I see now... yes, I like it too, only question is "resolve issue" I do like review, to me that says patch set is submitted in Gerrit and being reviewed/waiting to merge
Has joined the channel.
I have taken the fabric Slack archive saved as HTML by Ry Jones and converted to RTF so it is searchable. I also removed all the "has joined" and "has left" to reduce file size and ease scrolling. Have a look and edit anything you want to correct or add. Let me know if this effort is helpful. If so, I will go after fabric-consensus archive next. This is very time consuming. https://docs.google.com/document/d/1kKRDVi0oQkaS4ub__M9mvdVAGyAkEHh-a6DZi2X_PDs/edit?usp=sharing
It is a big document so it takes awhile to load.
Hi all, is the v1.0.0-preview the branch that the other various components (e.g. fabric-ca [on v1.0.0-preview branch, fabric-sdk-node) should be run against?
Has joined the channel.
@vdods I set that branch up by request to formalize the version of code that was used at a recent hackfest
However, the code has moved on since then and the preview release has yet to be embraced by all so I would suggest just use HEAD
@greg.haskins Ok, thanks!
Hi, hopefully this is the right channel to ask this question. When thinking about the proper architecture when you want to store information about a fairly large number of entities (which could be sensors, or patients, or even vehicles in a fleet), what type of architectural considerations are there around storing that information in the blockchain (world state, couchdb or something else ) versus storing that information external to the Blockchain. Can anyone point me to any articles, or docs on this topic? Thanks!
I'd say the main difference (maybe obvious, maybe not) is that using storage outside of the blockchain will require you to implement your own data distribution, validation, and authentication/encryption yourself. Fabric 1.0 provides (currently in beta mode) a MVCC abstraction via couchDB which in principle would let you access the full history of the data stored in the ledger, as well as delete versions of the data that you consider to be obsolete.
I'm still getting up to speed on the use of fabric 1.0, so I don't claim to be an expert :)
@vdods Thanks! I'm wondering if there are scaling issues that one needs to consider, on when it makes sense to store information within the Blockchain
I've been wondering about that too. Here's a few thoughts: If you read the pptx doc attached to https://jira.hyperledger.org/browse/FAB-758 it will give you a good idea as to the DB capabilities, and how transactions work relative to that consideration. The short story is that each transaction has a "read set" and a "write set" for versioned key/value pairs, and the orderer must decide on the ordering for transactions that may read/write an overlapping set of keys. I'd imagine that the more overlapping transactions there are at one time, the harder job the orderer will have. As to actual and specific performance/complexity, I don't know.
@dave.enyeart @manish-sethi maybe you can also help @tennenjl on this channel as well?
@blackskygg I would try the fabric-composer channel There was an introduction of some cool tools at the last Hyperledger hackfest that might work out for you
Thanks a bunch, I will take a look at the pptx and I need to start studying the V1 architecture, so far I've been playing primarily with v.6. When it comes to volume and sensitivity of data (e.g. health care records), I'm trying to get my head around what (and when things) should be kept in the Blockchain and what should be stored externally.
Would it be better for me to ask this question in the fabric-questions channel?
@tennenjl You can store the data on-chain, or store the data off-chain with a hash of the data on-chain as immutable evidence. It is up to you. Some of the decision criteria would be: Is the data content large and therefore you'd like to avoid putting it on-chain, to avoid passing around large amounts of data to all participants, and making state transfer and data management more efficient; do you have an off-chain way to share data with all participants; do you want to keep the actual data private from network participants.
one thing that I think is significantly different as well with version 1.0 that i could see being particularly useful "might" be channels in version 1.0
@tennenjl I know documentation is aggressively being updated- so you might want to take a look at what is up there now as it if I recall I did see some information on channels-
just for interest
http://hyperledger-fabric.readthedocs.io/en/latest/overview/
Has joined the channel.
hi, i almost did make all for the master branch of fabric. at last, it failed with an Exception CalledProcessError: Command '['docker-compose', '-f', u'docker-compose-next-4.yml', 'unpause']' returned non-zero exit status 1.
i don't know how to fix it. maybe these error messages help: Error Message:
The PEER1_CORE_PEER_MSPCFGPATH variable is not set. Defaulting to a blank string.
The PEER0_CORE_PEER_MSPCFGPATH variable is not set. Defaulting to a blank string.
The PEER3_CORE_PEER_MSPCFGPATH variable is not set. Defaulting to a blank string.
The PEER2_CORE_PEER_MSPCFGPATH variable is not set. Defaulting to a blank string.
The ORDERER0_ORDERER_GENERAL_LOCALMSPDIR variable is not set. Defaulting to a blank string.
The ORDERER_GENERAL_GENESISMETHOD variable is not set. Defaulting to a blank string.
The ORDERER_GENERAL_GENESISFILE variable is not set. Defaulting to a blank string.
No containers to unpause
there a lot of churn in the master branch as folks are putting in many updates for the end 2 end flow with signature verification for multiple orgs ... you might want to wait a day or two for things to calm down
or just build without running the behave tests ... look in the makefile for the target name
@tuand i got it. thank you very much.
hi, can someone explain why are necessary 2 images?
```
docker pull hyperledger/fabric-peer:latest
docker pull hyperledger/fabric-membersrvc:latest
```
hi @rrader - with v0.6, there are two primary types of components:
Peers - which handle chaincode, transactions, consensus, etc
Membersrvcs - which handles membership for the permissioned network
Has joined the channel.
@mastersingh24 is the same for v1?
@warm3snow you can fix it by installing golang.org/x/tools/cmd/goimports package into fabric-buildenv docker image.
@rrader more details on V1.0 on the wiki https://wiki.hyperledger.org/community/fabric-design-docs
@dave.enyart Thanks for the response, I follow everything that you are saying and it all makes sense, I am just wondering especially with the changes to V1 moving forward, what are some of the tipping points (especially when it comes to scale or use case), when does it make sense to store that data in the chain, for instance if I am dealing with data regarding a large number of patients for health care (EMR and more), or for a large number of sensors or vehicles, where we are using the Blockchain as this secure and (to varying degrees sharable) source of truth, how do we determine the right approach regarding where the data (besides the record of the transaction) is stored and are there any existing pilots where a decision has been made one way or the other and what were the lessons learned.
Has joined the channel.
@tennenjl good points. I have written extensively about the design points. (https://developer.ibm.com/blockchain/2017/01/01/7-principles-for-designing-a-blockchain-network-to-power-and-sustain-your-business/). There are always trade-offs, which we surface in our design thinking workshops - where business requirement dictates the choices and that drives the investment. Also on EMR records we have a POV (https://public.dhe.ibm.com/common/ssi/ecm/gb/en/gbe03790usen/GBE03790USEN.PDF) . Now we have done some extensive research on economic viability of a solution issues you raise certainly hit that very point, and data replication can over time add costs to the infrastructure (replication and CPU due to IO) so we have to factor in the business use case and the investment ( based on models we have in IBM design thinking workshop) and that would them be a business decision in terms of intent to invest. Also blockchain is NOT a security solution,it does elements of crypto/provenance that lends itself to trust system, but from what we have learned from other deployments -- design and architecture are key so some security elements ( like AAA) would have to dealt with current AAA systems. - Hope this helps. - Nitin
@nitingaur Nitin, as always, thanks a bunch. This definitely helps (as do the other articles you've written). I'll read through the provided links and I'm sure I'll have some additional questions ;-) Thanks again!
Hi,Satheeshk
I added some methods of fabric-sdk-java v0.6 to the fabric-JAVAchaincode like ChaincodeStub/Handler,such as getRows,setEvent.And I made peer successfully again.But,when I deployed the SimpleSample chaincode,peer node said that "[chaincode] Launch -> ERRO 019 launchAndWaitForRegister failed Timeout expired while starting chaincode". So, any idea for this?
I wonder if I can change the Java-shim(fabric/core/chaincode/shim/java for my Chaincode
it wil be possible to migrate from v0.6 to v1?
1.0 is breaking, iirc
1.0 is breaking, iiuc
I created two fabric v0.6 environments.Firstly,I excuted "make peer" and "SimpleSample chaincode" refering to JAVAChaincode.md successfully for two.i changed one Java-shim(fabric/core/chaincode/shim/java for my Chaincode,another is original.All "make peer" successfully.But when I tested the SimpleSample ,the first one show that " [chaincode] Launch -> ERRO 01a launchAndWaitForRegister failed Timeout expired while starting chaincode " .I noticed that the first one lost a step of "[genesis] funcl -> INFO 00f Creating genesis bock"when I excuted "peer node start" after raising startuptimeout and deploytimeout for serveral times.So,it is a bug?
I noticed that the main branch built peer does not suport 'peer chaincode deploy' command, does it?
@bh4rtp that is correct, the semantics have chained and now it's install and instantiate
@yacovm thank you. install does work. but running "peer chaincode install -n ex02 -p /root/chaincode_example02 -v 1.0 -c '{"args":["init","a","100","b","200"]}'" outputs an error: panic: runtime error: index out of range. is there anymore changes here for testing examples/chaincode/chaincode_example02?
The path of the cc needs tobe in your gopath
@yacovm the path is relative to $GOPATH. it does work. thank you again.
Has joined the channel.
install just passed. query failed. peer chaincode query -n example02 -c '{"function":"invoke","Args":["query","a"]}'
2017-02-27 11:42:47.747 UTC [SW_BCCSP] createKeyStoreIfNotExists -> INFO 001 KeyStore path [/etc/hyperledger/fabric/msp/sampleconfig/keystore] missing [false]: [
@bh4rtp it means that the peer hasn't joined the channel
@yacovm can i create a channel in the test_peer_1 container? i use test/docker-compose.yml which has not cli node.
which instructions are you following, @bh4rtp ?
The link to Dockerfile in following page is dead.
Starter Kit - Hyperledger Fabric
http://hyperledger-fabric.readthedocs.io/en/v0.6/starter/fabric-starter-kit/
@bmos299 @joshhus can you help get the link updated? see up above
Has joined the channel.
Where can I get latest v0.6 setup information?
This one?
https://github.com/yeasy/docker-hyperledger-peer/blob/0.6-dp/Dockerfile
@yacovm i found no exact instructions. because all the instructions are suitable for v0.6. can you give me some instructions to do fabric/test/docker-compose.yml? thank you!
A good place for that is #fabric-questions
A good place for that is #fabric-quality
@yacovm thank you.
Has joined the channel.
So I watched the video "Hyperledger install & instantiate code" today, and was left with some questions. I originally typed them in as comments, but deleted those before posting as I realized that this forum will be more likely to result in answers: "So if I understand the video, endorsers require install of chaincode in order to execute invokes. But what about queries? Do observers require install of chaincode so that applications can be targeted to the observer? In a globally distributed network, we will want observer peers all over the place so that we don't put pressure on the endorsers with queries. It looks like an install command for every global observer would be required in the new model (i.e. versus the v0.6 model where the chaincode is installed on every peer automatically no longer holds for this scenario). Would this be an accurate interpretation?"
I also noted in the sprint 4 video for the SDK that the Query stub API was deprecated and queries are run through the Invoke entry point now. I presume that this is still true? This would make me wonder if the queries now have write access? And the second question this change raises is whether queries can now see *uncommitted* state? Thanks.
Has joined the channel.
```error: [Chain.js]: Chain-sendPeersProposal - Promise is rejected: Error: Error: The proposal does not comply with the channel writers for channel testchainid, error Failed to reach implicit threshold of 1 sub-policies, required 1 remaining```
anyone know what this means?
@greg.haskins - seems like the identity used to sign the proposal was not issued by any of the MSPs configured as writers for the channel
any idea what causes that?
i was using the same basic flow that I always do, this is new
we should deprecate that testchain id if you ask me
with all these changes... does that thing even work?
very little works, it seems
are you running the peer with the --chainid = false flag?
all I want to do right now is qualify chaintool deployments
not unless that is the new default, no
is there a prescribed way to start a full setup these days?
i always use fabric.git/test/docker-compose.yml
(though I currently have devmode disabled)
what is everyone else using to run?
@greg.haskins I assume you are on the latest master ?
a ton of policy crap has been merged over the past week
@muralisr i was as of late last week...i just pulled the latest a few minutes ago and am in the process of recompiling it
ok
(in the hopes this will "go away" but lately, pull newer code just pulls newer issues ;)
so, not super hopeful
reason I asked was this - https://gerrit.hyperledger.org/r/#/c/6571/ will need a corresponding SDK change
@jimthematrix might have an ETA for that
its basically reverting to use SHA2
and yes, last week has been a bit ... interesting ? .... hopefully will stabilize
*hopefully* :-)
im probably hitting that...now the the SDK is blowing up with a proto incongruence
ok
that is weird... let me try a make proto
so the system is dead in the water until further notice?
yes, from SDK pov till that reversal is fixed in SDK
ok
you can set the hash in the SDK
we need to do a better job of coordinating breaking changes so at least we dont leave the system broken
@muralisr @greg.haskins https://gerrit.hyperledger.org/r/#/c/6585/ needs to be reviewed and merged
@mastersingh24 ^^^
caveat is that it's dependent on another of my changeset
funny - just merged them both
;-)
udaman
@greg.haskins feel free to give it another try
I did, got passed the proto error, hitting another bug now
i think someone broke the chaincodePath thing again
investigating
@greg.haskins hi haskins. i am using your contributed test case https://github.com/hyperledger/fabric/blob/master/test/docker-compose.yml. can you give me some instructions to do examples/chaincode/chaincode_example02? thank you.
fabric-contribution-lifecycle, welcome for any comments, thanks!
Message Attachments
Has joined the channel.
may i ask a dummy question? to install a chaincode in GO language, need i build it or just deploy the source code file?
[ ](https://chat.hyperledger.org/channel/fabric?msg=44u7zeLwWtTBLEjFi) @bh4rtp Provide the path to your source code to the command or sdk client. You don't have to build cc by yourself.
@Ying thank you.
i use github.com/hyperledger/fabric/examples/sfhackfest/docker-compose-gettingstarted.yml. and follow http://hyperledger-fabric.readthedocs.io/en/latest/asset_cli/ step by step. when deploy the chaincode, the command CORE_PEER_ADDRESS=peer0:7051 CORE_PEER_COMMITTER_LEDGER_ORDERER=orderer:7050 peer chaincode deploy -C myc2 -n mycc -p github.com/hyperledger/fabric/examples -c '{"Args":["init","a","100","b","200"]}' failed with errors: Error: Error endorsing chaincode: rpc error: code = 2 desc = Failed to deploy chaincode spec(Error creating image: %!s(
Has joined the channel.
hello, everyone. Is there someone encounter this problem? It stuck me.
```
LINT: Running code checks..
Checking ./core
./scripts/golinter.sh: line 11: goimports: command not found
Makefile:121: recipe for target 'linter' failed
make: *** [linter] Error 127
```
Any help would be appreciated.
I have goimports in $GOPATH/bin
```
xxx@ubuntu:/opt/gopath/src/github.com/hyperledger/fabric$ which goimports
/opt/gopath/bin/goimports
```
@warm3snow it does not relate to host environment, but built docker images. you can read the Makefile to find which images should be installed with github.com/x/tools/cmd/goimports package manually.
Hi all, when I send a proposal request (install, instantiate and invoke), will the fabric check if the creator(Me, using the enrolled admin user from fabric-ca) has right to perform such an action ? I cannot find it in the code, please help to point it out.
Hi all, when I send a proposal request (install, instantiate or invoke), will the fabric check if the creator(Me, using the enrolled admin user from fabric-ca) has right to perform such an action ? I cannot find it in the code, please help to point it out.
Has joined the channel.
@bh4rtp thank you very much. You help me a lot.
Hi everyone! Have anybody tried to deploy Fabric v0.6 on Amazon EC2 Container service? https://aws.amazon.com/ecs Any possible troubles you may foresee?
Hi, I am installing hyper ledge fabric on Ubutu 16.04 LTS using Azure. The installation process outlined at this URL
Hi, I am installing hyper ledge fabric on Ubutu 16.04 LTS using Azure. The installation process outlined at this URL root@Blockchain:/opt/gopath/src/github.com/hyperledger/fabric# make peer
build/bin/peer
CGO_CFLAGS=" " GOBIN=/opt/gopath/src/github.com/hyperledger/fabric/build/bin go install -ldflags "-X github.com/hyperledger/fabric/common/metadata.Version=0.7.0-snapshot-0c23ac1 -X github.com/hyperledger/fabric/common/metadata.BaseVersion=0.3.0 -X github.com/hyperledger/fabric/common/metadata.BaseDockerLabel=org.hyperledger.fabric" github.com/hyperledger/fabric/peer
core/chaincode/ccproviderimpl.go:20:2: cannot find package "context" in any of:
/opt/gopath/src/github.com/hyperledger/fabric/vendor/context (vendor tree)
/usr/lib/go-1.6/src/context (from $GOROOT)
/opt/gopath/src/context (from $GOPATH)
Makefile:177: recipe for target 'build/bin/peer' failed
make: *** [build/bin/peer] Error 1
root@Blockchain:/opt/gopath/src/github.com/hyperledger/fabric#
Hi, I am installing hyper ledge fabric on Ubutu 16.04 LTS using Azure. The installation process outlined at this URL root@Blockchain:/opt/gopath/src/github.com/hyperledger/fabric# make peer
build/bin/peer
CGO_CFLAGS=" " GOBIN=/opt/gopath/src/github.com/hyperledger/fabric/build/bin go install -ldflags "-X github.com/hyperledger/fabric/common/metadata.Version=0.7.0-snapshot-0c23ac1 -X github.com/hyperledger/fabric/common/metadata.BaseVersion=0.3.0 -X github.com/hyperledger/fabric/common/metadata.BaseDockerLabel=org.hyperledger.fabric" github.com/hyperledger/fabric/peer
core/chaincode/ccproviderimpl.go:20:2: cannot find package "context" in any of:
/opt/gopath/src/github.com/hyperledger/fabric/vendor/context (vendor tree)
/usr/lib/go-1.6/src/context (from $GOROOT)
/opt/gopath/src/context (from $GOPATH)
Makefile:177: recipe for target 'build/bin/peer' failed
make: *** [build/bin/peer] Error 1
root@Blockchain:/opt/gopath/src/github.com/hyperledger/fabric#
Hi, I am installing hyper ledge fabric on Ubutu 16.04 LTS using Azure. The installation process outlined at this URL https://www.ibm.com/developerworks/community/blogs/8d277a63-4204-4fd3-8cb8-b7cb222cd522/entry/Steps_to_setup_Blockchain_Hyperledger_Fabric_0_6_development_environment_on_Ubuntu?lang=en and getting the below error root@Blockchain:/opt/gopath/src/github.com/hyperledger/fabric# make peer
build/bin/peer
CGO_CFLAGS=" " GOBIN=/opt/gopath/src/github.com/hyperledger/fabric/build/bin go install -ldflags "-X github.com/hyperledger/fabric/common/metadata.Version=0.7.0-snapshot-0c23ac1 -X github.com/hyperledger/fabric/common/metadata.BaseVersion=0.3.0 -X github.com/hyperledger/fabric/common/metadata.BaseDockerLabel=org.hyperledger.fabric" github.com/hyperledger/fabric/peer
core/chaincode/ccproviderimpl.go:20:2: cannot find package "context" in any of:
/opt/gopath/src/github.com/hyperledger/fabric/vendor/context (vendor tree)
/usr/lib/go-1.6/src/context (from $GOROOT)
/opt/gopath/src/context (from $GOPATH)
Makefile:177: recipe for target 'build/bin/peer' failed
make: *** [build/bin/peer] Error 1
root@Blockchain:/opt/gopath/src/github.com/hyperledger/fabric#
Has joined the channel.
@saridsa1 what is GO version that you use?
1.6
I see, this is the problem
try 1.8
I did apt install golang-go
if you use 1.7 you must install context package
https://godoc.org/golang.org/x/net/context
ppa repo of ubuntu has very old GO version, it is easy to install it manualy
http://tecadmin.net/install-go-on-ubuntu/
just get latest (1.8) version from go website and follow this steps
for 1.8 you do not need to install context package
Hello, I am not sure is this issue is for here or for chaincode channel but if I try to listen for REJECTION event i do not get any event. I see this in logs:
peer0 | 2017-02-28 09:38:04.035 UTC [eventhub_producer] registerHandler -> DEBU ecf registerHandler REJECTION
peer0 | 2017-02-28 09:38:04.035 UTC [eventhub_producer] registerHandler -> DEBU ed0 registerHandler REGISTER
peer0 | 2017-02-28 09:38:04.035 UTC [eventhub_producer] register -> ERRO ed1 could not register : event type REGISTER does not exist
peer0 | 2017-02-28 09:38:04.035 UTC [eventhub_producer] registerHandler -> DEBU ed2 registerHandler CHAINCODE
peer0 | 2017-02-28 09:38:04.035 UTC [eventhub_producer] register -> ERRO ed3 could not register event_type:CHAINCODE : error registering handler for CHAINCODE: chaincode information not provided for registering
Can somebody give me a hint what is wrong
Hello, I am not sure is this issue is for here or for chaincode channel but if I try to listen for REJECTION event i do not get any events except for BLOCK. I see this in logs:
peer0 | 2017-02-28 09:38:04.035 UTC [eventhub_producer] registerHandler -> DEBU ecf registerHandler REJECTION
peer0 | 2017-02-28 09:38:04.035 UTC [eventhub_producer] registerHandler -> DEBU ed0 registerHandler REGISTER
peer0 | 2017-02-28 09:38:04.035 UTC [eventhub_producer] register -> ERRO ed1 could not register : event type REGISTER does not exist
peer0 | 2017-02-28 09:38:04.035 UTC [eventhub_producer] registerHandler -> DEBU ed2 registerHandler CHAINCODE
peer0 | 2017-02-28 09:38:04.035 UTC [eventhub_producer] register -> ERRO ed3 could not register event_type:CHAINCODE : error registering handler for CHAINCODE: chaincode information not provided for registering
Can somebody give me a hint what is wrong
I am working on Master
I tried installing go 1.8 but had not success CGO_CFLAGS=" " GOBIN=/opt/gopath/src/github.com/hyperledger/fabric/build/bin go install -ldflags "-X github.com/hyperledger/fabric/common/metadata.Version=0.7.0-snapshot-0c23ac1 -X github.com/hyperledger/fabric/common/metadata.BaseVersion=0.3.0 -X github.com/hyperledger/fabric/common/metadata.BaseDockerLabel=org.hyperledger.fabric" github.com/hyperledger/fabric/peer
# github.com/hyperledger/fabric/vendor/github.com/miekg/pkcs11
vendor/github.com/miekg/pkcs11/pkcs11.go:29:18: fatal error: ltdl.h: No such file or directory
compilation terminated.
Makefile:177: recipe for target 'build/bin/peer' failed
make: *** [build/bin/peer] Error 2
@saridsa1 apt-get install -y libltdl-dev
super @gatakka thank you so much, you saved the day
make membersrvc - fails with message make: *** No rule to make target 'membersrvc'. Stop. Any help?
try to make all, not only meberservice
make dist-clean all
@gatakka thank you trying it now..
Has joined the channel.
@binhn @muralisr What uniquely identifies chain code ? If you look at chaincode.proto _ChaincodeID_ it's description is totally out of date. I'd still like to have one proto object that will uniquely identify chain code. I should be able to use it in ALL grpc calls to identify it with all it's fields set. I've been told that path is sometimes needed here other times not. This in opinion seem very awkward something that's an *ID*. I'd vote to clean this up yet if path is not needed to identify chain code move it out of here and put in those operation separately where needed.
@binhn @muralisr What uniquely identifies chain code ? If you look at chaincode.proto _ChaincodeID_ it's description is totally out of date. I'd still like to have one proto object that will uniquely identify chain code. I should be able to use it in ALL grpc calls to identify it with all it's fields set. I've been told that path is sometimes needed here other times not. This in opinion seem very awkward for something that's an *ID*. I'd vote to clean this up yet if path is not needed to identify chain code move it out of here and put in those operation separately where needed.
@rickr @greg.haskins mentioned the same thing about cleaning up chaincode proto. Agree some overhaul is indicated
@kletkeman Hi， Could you provide me the link for the video of hyperledger install & instantiate code?
clean dist fails with this message Exception ImportError: No module named google.protobuf.message
Traceback (most recent call last):
File "/usr/local/bin/behave", line 11, in
@jansony1 Here is the Hyperledger YouTube channel: https://www.youtube.com/channel/UCCFdgCWH_1vCndMPVqQlwZw
And here is the install and instantiate video: https://www.youtube.com/watch?v=SXTAVFM2liU
@saridsa1 I had an error like that with clean dist yesterday ... it seemed to work when I repeated the command under sudo. That is missing from the instructions.
@muralisr heres a new one for you
```vp_1 | 2017-02-28 17:31:56.125 UTC [dev-jdoe-mycc-1] func2 -> INFO 2ed chaincode: error while loading shared libraries: libltdl.so.7: cannot open shared object file: No such file or directory```
I am getting this while trying to launch a CAR payload
I understand what the basic error is: what I cant figure out is why doesnt this happen to GOLANG too?
also, thought this was a UT only dep
oh wait, i bet I know
I think I need to update to https://gerrit.hyperledger.org/r/#/c/6467/
there seems to be an outage with aws/s3 right now
cant reach https://github.com/hyperledger/fabric-chaintool/releases/download/v0.10.3/chaintool
(similar issues building javaenv
that would explain why half the internet fell over
Docker Hub also dead
only so much we can do ¯\_(ツ)_/¯
Hi, was just looking at https://jira.hyperledger.org/browse/FAB-37 1206 devupdate attachment -- I had thought the app proposed transaction to orderer, orderer sought endorsements from peers, but this doc suggests app responsible for proposing transaction to multiple peers and receiving endorsement, then communicating to orderer? is this doc still accurate?
Has joined the channel.
@mrkiouak yes, that's accurate
hi, I want to try a "hello world" with v0.6, from there I should start?
(RE: S3 outage -- this captures it well: http://www.theverge.com/2017/2/28/14765208/is-it-down-right-now-down-right-now)
So, `peer chaincode deploy` doesn't appear to be working in the latest master, how can I deploy chaincode with the latest fabric? (I searched for documentation but it was TBD)
or is the AWS outage somehow causing that not to work too?
or is the AWS outage somehow causing that not to work too? :-D
https://techcrunch.com/2017/02/28/amazon-aws-s3-outage-is-breaking-things-for-a-lot-of-websites-and-apps/
Has joined the channel.
Hello... fabric build is down right now.. ....I understand that it is because Amazon is down
```
* Connected to github-cloud.s3.amazonaws.com (54.231.41.19) port 443 (#1)
* Server aborted the SSL handshake
* Closing connection 1
curl: (35) Server aborted the SSL handshake
```
@pschnap deploy has been split into "install" and "instantiate" commands now. Here's an example for installing/instantiating chaincode_example02: `peer chaincode install -n mycc -v 0 -p github.com/hyperledger/fabric/examples/chaincode/go/chaincode_example02` and `peer chaincode instantiate -n mycc -v 0 -p github.com/hyperledger/fabric/examples/chaincode/go/chaincode_example02 -c '{"Args":["init","a","100","b","200"]}'`
@pschnap deploy has been split into install and instantiate commands now. Here's an example for installing/instantiating chaincode_example02: `peer chaincode install -n mycc -v 0 -p github.com/hyperledger/fabric/examples/chaincode/go/chaincode_example02` and `peer chaincode instantiate -n mycc -v 0 -p github.com/hyperledger/fabric/examples/chaincode/go/chaincode_example02 -c '{"Args":["init","a","100","b","200"]}'`
thanks @wlahti ! I was told a while ago that I'd have to prefix my development deployment with `CORE_CHAINCODE_MODE=dev` and also that I'd have to restart the chaincode after deploying, is this still the case?
@pschnap you should be aware of this
https://jira.hyperledger.org/browse/FAB-2530
devmode does not currently work
oho, thanks Greg
that means, ignore errors
all: until S3 is repaired, you might be able to get _some_ work done by using the "-k" switch to make. that means, ignore errors
e.g. "make -k docker"
@mastersingh24 ^^^^
all bets are off, of course, but worth a try
ah right - interesting
Things that rely on S3 seem to be coming back up now. I was just able to run `make peer` successfully again.
same, my build is still in-progress but its certainly making it farther than it did
er, further
the line is blurry on that one
When building Fabric with `make all` toward the end of the build process, (I think in the unit testing), I'm getting some errors about missing Python libraries `protobuf` and `grpc`. I tried using pip to install them, but I still got an error saying that grpc.beta is missing from bddtests/chaincodeevent_pb2.py. Could that be related to the S3 issue, or perhaps did I install the wrong grpc library?
Has joined the channel.
Has joined the channel.
I just noticed that in fabric1.0 all the attribute-related interfaces are gone from ChaincodeStubInterface such as "ReadCertAttributes". Does this mean that for ACL, the v1.0 stops using the mechanism of taking attributes values from Tcert? If so, how would acl be enforced in v1.0 on the chaincode side?
@RyanElliott the short answer is "dont use 'make all'" ;)
that still calls behave, which in general hasnt been running right
and even if it is, you would need to run it in a supported environment like the vagrant devenv
what we should do is remove that from the "all" target
Ok, I'll just run `make native docker`
Thanks
yeah, note that even that would be kind of a special case
(generally you only want one or the other
Well, this is my first build :)
for instance, I tend to use "make docker" most of the time, only using native when I need to run the peer locally for whatever reason
ah, yeah, start with "make docker"
that will get you the suite of containers
(though if you need the CLI, also add "peer" to that
e.g. "make docker peer"
ill file a JIRA to remove behave from the all target
@RyanElliott https://jira.hyperledger.org/browse/FAB-2556
ok, thanks. My eventual goal is to start tinkering with the peer.
cool, good luck and dont be shy with questions
Hi all, when I send a proposal request (install, instantiate or invoke), will the fabric check if the creator(Me, using the enrolled admin user from fabric-ca) has right to perform such an action ? I cannot find it in the code, please help to point it out.
I am currently very confuse against the role of the creator of a chaincode and how the creator is related to the access control of the chaincode.
@RyanElliott Hi Rayn, as for grpc.beta ， maybe install grpcio would be help
@jansony1 Thanks, I'll try that it a little bit and report back the results.
@greg.haskins Hi grep. I think Rayn was following this doc http://hyperledger-fabric.readthedocs.io/en/latest/dev-setup/build/
And in this doc, it just told us to do the "make all". While there seems not so much other instruction tell us what to do the next, like build the channel, build up the peers things, any suggestion? Or could you give me some instruction about what is the next thing we should do after we "make all" the prerequsite for fabric.
yeah, its actually probably unfortunate that it mentions the all target, or unfortunate that we tied all the tests to it
that literally builds everything and runs all the tests we have, which is not generally something of interest to someone starting out that just wants to run it
I've heard good things about this guide: http://hyperledger-fabric.readthedocs.io/en/latest/included/
@jansony1 Yes, that's where I came from. @greg.haskins I went through much of that getting started guide, so it sounds like next step for me is to customize the yaml to use the docker images that I just built.
@greg.haskins Thanks, hope the doc could provide more deep dive instruction~
ah, ok, sorry
Hi guys, sorry to be annoying, but not sure everybody seen my question. Has anybody tried to deploy Fabric v0.6 on Amazon EC2 Container service? ( https://aws.amazon.com/ecs ) Any possible troubles you may think of?
@RyanElliott check out test/docker-compose.yml
thats what I use for my day-to-day
after you have "make docker" successfully, just "cd test && docker-compose up"
Cool, I was going to ask what devs generally use in their code/debug cycle.
actually, youll need to do a "make docker" in the fabric-ca project too come to think of it
in general, I update to the latest versions of fabric/fabric-ca, do "make clean docker" in each, and then fire up that composition i mentioned
I then have a basic environment to test against
thats obviously most useful if you are trying to just get an environment running but dont need to debug something like the peer
for that, I often hack up the composition locally (like remove the vp stanza) and then run the native peer under delve
etc etc
but its very rare that I need to debug all three, so I find the docker-based flow the easiest to deal with
@greg.haskins I think I get it. Keep your fingers crossed for me :relaxed:
will do, let us know how you make out
Thanks, I will.
@greg.haskins thanks for your instruction. After fire up the test/docke-compose it return the following error, is that corret?
vp_1 | 2017-03-01 02:32:42.046 UTC [nodeCmd] serve -> INFO 03d Deployed system chaincodes on testchainid
vp_1 | 2017-03-01 02:32:42.046 UTC [peer] Initialize -> INFO 03e Loading chain testchainid
vp_1 | 2017-03-01 02:32:42.046 UTC [ledgermgmt] OpenLedger -> INFO 03f Opening leadger with id = testchainid
vp_1 | 2017-03-01 02:32:42.046 UTC [peer] Initialize -> WARN 040 Failed to load ledger testchainid(Ledger already opened)
vp_1 | 2017-03-01 02:32:42.046 UTC [nodeCmd] serve -> INFO 041 Starting peer with ID=name:"jdoe" , network ID=dev, address=172.17.0.2:7051
vp_1 | 2017-03-01 02:33:57.055 UTC [gossip/comm#-1] func1 -> WARN 042 0.0.0.0:7051, PKIid:[] isn't responsive: EOF
vp_1 | 2017-03-01 02:34:47.059 UTC [gossip/comm#-1] func1 -> WARN 043 0.0.0.0:7051, PKIid:[] isn't responsive: EO
@jansony1 I think I get that too
let me check
Thanks and take your time ~~:grin:
i have a bunch of extra debug enabled, so I cant easily tell, but that does look familar
keep in mind, we are still pre-alpha in the master branch ;)
tomorrow that error will be gone, replaced with something new ;)
generally speaking, if the composition comes up, that is happy milestone (1)
and then if I can run my test against it and everything stays up, that is happy milestone (2)
anything else, I dont worry about
i def see the "Failed to load ledger testchainid"
(and it doesnt appear to break me)
:yum: I will make a try ~
And expect for the "new one" , lol
Hi, anyone have sample for upgrade chaincode on command line or nodejs SDK? I tried to run upgrade on chaincode_example02 but the values keep reset after upgrade, and seem like after upgrade old container of previous version still running. Thanks.
I am running into problem installing the behave module, is there any way I can skip the module while running a make clean-dist all
'Running behave tests
Exception ImportError: No module named b3j0f.aop' I keep running into this problem
`Running behave tests
Exception ImportError: No module named b3j0f.aop` I keep running into this problem
@dave.enyeart
Hi,
I am facing issue related to GetQueryResult API. In our chaincode we are calling GetQueryResult API of shim but it does not return expected response. Using sfhackfest images with version 1.0.
Below is the query used in GetQueryResult API
{"selector":{"docTypeId":3,"oriRe":"SMP","ctB":"CTB","valDt":"1990-12-24","orB":"YYY","tD":"TD","cuVoB":52,"cuIoBu":"AA","cuSt":"NA"}}
Query internally constructucted with data wrapper:(got from peer logs) {"selector":{"data.cuIoBu":"AA","data.cuVoB":52,"data.data.ctB":"CTB","data.data.cuSt":"NA","data.docTypeId":3,"data.oriRe":"SMP","data.orB":"YYY","data.tD":"TD","data.valDt":"1990-12-24"}}
If you see this query with data wrapper, for ctB and cuSt fields data.data is being appended instead of data and because of this it doesnot fetch record even though its present in ledger.
However if we remove one of the field from the query then it returns response and in this case data.data is not getting appended to fields.
Please find below query which returns response:-
original query:-
{"selector":{"docTypeId":3,"oriRe":"SMP","ctB":"CTB","valDt":"1990-12-24","orB":"YYY","tD":"TD","cuVoB":52,"cuIoBu":"AA"}}
query with data wrapper: {"selector":{"data.ctB":"CTB","data.cuIoBu":"AA","data.cuVoB":52,"data.docTypeId":3,"data.oriRe":"SMP","data.orB":"YYY","data.tD":"TD","data.valDt":"1990-12-24"}}
Please provide your inputs.
Has joined the channel.
Has joined the channel.
@snehas Please don't copy the same question to multiple channels. I've replied to your #fabric-ledger post.
Please delete this duplicate posting
Has joined the channel.
Hi all, I have a newbie question (new to both fabric and golang), I see the codes of reading config in many places, but where does the actual config really load the physical files ?
I believe it is in a "main" package (Golang best practice that all parsing goes to main package).
Thanks~ Not familiar with those * and & in Golang, very hard to trace
Haha, those are pointer things. One of designer of Golang is Ken Thompson who originally invented C language. C has pointers. :)
whats old is new again
Has joined the channel.
Has joined the channel.
Has joined the channel.
Has joined the channel.
I fixed a lot of import errors by installing the relevant packages, but not able to fix this one ```Exception ImportError: No module named devops_pb2``` any help is highly appreciated
Hello, I have a question about TCerts and there usage. When CA returns TCert it contains x509 certificates, but where is private key for those TCerts to sign requests when I use them. I have to use private key for user that requested TCerts or private key is encrypted in TCert somehow?
Thank you!
Hello, I have a question about TCerts and there usage. When CA returns TCert it contains x509 certificates, but where is private key for those TCerts to sign requests when I use them. I have to use private key from user that requested TCerts or private key is encrypted in TCert somehow and is unique PK for every TCert?
Thank you!
Has joined the channel.
Has joined the channel.
Has joined the channel.
Has joined the channel.
I'm currently trying to extend the example_cc.go code from from the sfhackfest example. I've added a function that calls stub.GetHistoryForKey, copied from the marbles example (https://github.com/hyperledger/fabric/blob/master/examples/chaincode/go/marbles02/marbles_chaincode.go#L502). I can build it fine with go build when I sit it in the examples directory, but when I launch it through docker compose and run the deploy.js node app it fails to deploy the chaincode.
```
error: [Peer.js]: GRPC client got an error response from the peer. Error: Failed to deploy chaincode spec(Error creating image: %!s(
Is there something about the version of the api with that example where that isn't supported, or could it be another issue?
@jeffreypicard it looks like something went south when the peer tried to compile the chaincode
there are a few switches to the peer that help debug this
CORE_LOGGING_LEVEL=debug
and
CORE_VM_DOCKER_ATTACHSTDOUT=true
if you re-run the peer with those set, we will likely get a more helpful error in the peer log
@greg.haskins Thanks! I'll give those a shot.
note to self: we need to figure out why we get "%!s" instead of the actual error string
Has joined the channel.
I ran through the example of creating and deployings another channel in the cli, but the error message still doesn't seem all that helpful.
```
CORE_PEER_COMMITTER_LEDGER_ORDERER=orderer:7050 peer channel create -c myc2
CORE_PEER_COMMITTER_LEDGER_ORDERER=orderer:7050 CORE_PEER_ADDRESS=peer0:7051 peer channel join -b myc2.block
CORE_PEER_COMMITTER_LEDGER_ORDERER=orderer:7050 CORE_PEER_ADDRESS=peer1:7051 peer channel join -b myc2.block
CORE_LOGGING_LEVEL=debug CORE_PEER_ADDRESS=peer0:7051 CORE_PEER_COMMITTER_LEDGER_ORDERER=orderer:7050 peer chaincode deploy -C myc2 -n mycc -p github.com/hyperledger/fabric/examples -c '{"Args":["init","a","100","b","200"]}'
```
and the output:
```
Error: Error endorsing chaincode: rpc error: code = 2 desc = Failed to deploy chaincode spec(Error creating image: %!s(
Hi. I tried running the command "npm run submitTransaction" and got the following error msg.
Message Attachments
Message Attachments
Basically, it seems that the node cli.js landregistry submit && node cli.js landregistry list are failing whenever I run the command "npm run submitTransaction"
so in your default connection profile
does it say local host
or the ip address of your docker vm
looks like u are on mac right
Please post Fabric Composer questions to the #fabric-composer channel. Thanks!
Has joined the channel.
Has joined the channel.
Has joined the channel.
hello
Hi..Getting an error with the fabric on git while building.. github.com/hyperledger/fabric/vendor/github.com/miekg/pkcs11
../../hyperledger/fabric/vendor/github.com/miekg/pkcs11/pkcs11.go:29:10: fatal error: 'ltdl.h' file not found
#include
I cloned the fabric and started writing chaincode but was facing the above error while building "go build". This was working with version 0.6
Has joined the channel.
hey guys, i am having an issue deploying a demo chaincode. I created a docker peer and set the config under /etc/hyperledger/fabric. Its core.yml mspConfigPath pointed to a location that had the fabric default certs (from the fabric repo, fabric/tree/master/msp/sampleconfig).
I successfully registered the chaincode, but when i try to deploy it, i am getting this error:
panic: Fatal error when setting up MSP from directory /etc/hyperledger/fabric/msp/sampleconfig: err Could not load a valid signer certificate from directory /etc/hyperledger/fabric/msp/sampleconfig/signcerts, err Could not read directory open /etc/hyperledger/fabric/msp/sampleconfig/signcerts: no such file or directory, err /etc/hyperledger/fabric/msp/sampleconfig/signcerts
The thing is, i can see all the certs in the right place when i connect to the docker container.
root@e5b7aa44203e:/# ls -la /etc/hyperledger/fabric/msp/sampleconfig/*
/etc/hyperledger/fabric/msp/sampleconfig/admincerts:
total 4
drwxrwxr-x 2 1001 1001 26 Mar 1 21:09 .
drwxrwxr-x 6 1001 1001 68 Mar 1 21:09 ..
-rw-rw-r-- 1 1001 1001 944 Mar 1 21:09 admincert.pem
/etc/hyperledger/fabric/msp/sampleconfig/cacerts:
total 4
drwxrwxr-x 2 1001 1001 23 Mar 1 21:09 .
drwxrwxr-x 6 1001 1001 68 Mar 1 21:09 ..
-rw-rw-r-- 1 1001 1001 887 Mar 1 21:09 cacert.pem
/etc/hyperledger/fabric/msp/sampleconfig/keystore:
total 4
drwxrwxr-x 2 1001 1001 20 Mar 1 21:09 .
drwxrwxr-x 6 1001 1001 68 Mar 1 21:09 ..
-rw-rw-r-- 1 1001 1001 227 Mar 1 21:09 key.pem
/etc/hyperledger/fabric/msp/sampleconfig/signcerts:
total 4
drwxrwxr-x 2 1001 1001 21 Mar 1 21:09 .
drwxrwxr-x 6 1001 1001 68 Mar 1 21:09 ..
-rw-rw-r-- 1 1001 1001 944 Mar 1 21:09 peer.pem
@bkvellanki did you install softhsm2 or libtool in your machine. @harrijk fixed this issue for me..
Hi ramesh. I got it working. I missed installing libtool and that solved it. Thanks for looking in to it
cool
Hey @rameshthoomu @bkvellanki, I have a similar error, but I'm running on Windows 10. Will something like cygwin gcc fix this?
`github.com/hyperledger/fabric/vendor/github.com/miekg/pkcs11 exec: "gcc": executable file not found in %PATH%`
need those build tools
Has joined the channel.
@here I just pulled the latest hyperledger and built it ... all worked until this step:
go: cannot find GOROOT directory: /usr/local/go
find: '/src/github.com/hyperledger/fabric/core/chaincode/shim': No such file or directory
Creating build/goshim.tar.bz2
tar: Cowardly refusing to create an empty archive
Try 'tar --help' or 'tar --usage' for more information.
Makefile:242: recipe for target 'build/goshim.tar.bz2' failed
make: *** [build/goshim.tar.bz2] Error 2
vagrant@hyperledger-devenv:v0.3.0-c68b3a1:/opt/gopath/src/github.com/hyperledger/fabric$ set | grep GOROOT
GOROOT=/opt/go
vagrant@hyperledger-devenv:v0.3.0-c68b3a1:/opt/gopath/src/github.com/hyperledger/fabric$ ls /opt/go
api AUTHORS bin blog CONTRIBUTING.md CONTRIBUTORS doc favicon.ico lib LICENSE misc PATENTS pkg README.md robots.txt src test VERSION
vagrant@hyperledger-devenv:v0.3.0-c68b3a1:/opt/gopath/src/github.com/hyperledger/fabric$
Since I obviously have a perfectly good GOROOT, I would think it should go there and not insist on /usr/local/go, which caused the failure.
Any thoughts?
I'n inside Vagrant if that matters ...
On a Mac
@kletkeman based on the behavior, it sounds like GOPATH isnt set
GOROOT should point to your go binary files, GOPATH to your code location
can you run "env | grep GO" ?
http://stackoverflow.com/a/10847122/1069068
I used set | grep go, which returned the same result as env:
vagrant@hyperledger-devenv:v0.3.0-c68b3a1:/opt/gopath/src/github.com/hyperledger/fabric$ env | grep GO
CGO_CFLAGS=
GOROOT=/opt/go
GOPATH=/opt/gopath
vagrant@hyperledger-devenv:v0.3.0-c68b3a1:/opt/gopath/src/github.com/hyperledger/fabric$
What's the output of `ls /usr/local/go/bin`?
@kletkeman ok, and now "ls $GOROOT/bin"
Just to be clear ... I've been working on the Hyperledger since Nov 2015 when it was still OBC ... I'm pretty used to gopath and goroot
@kletkeman I know who you are ;)
just trying to figure out whats up
the behavior you describe is when I see GOPATH unset...its clearly set, so now trying to diagnose
I know ... I'm just heading off any more links to the basics :-)
sure, sorry
weird ... it won't paster the colored letters ... I get:
go godoc gofmt
@raghavsood there is no /usr/local/go, but that should not matter as I installed Go elsewhere
Fair enough, just checking!
@kletkeman you are running everything within vagrant, yes?
ahhhhhhhh ..... our tools have a peculiar reliance on GOPATH being one folder, which of course is bad form
I use two folders as I include the IoT contract platform I wrote
I'm betting it is unhappy with the GOPATH
ah, that could be
hmmm ... but env shows only the one path ... that is weird
hmm, yeah, that is weird then
I know, I created a new shell for this one and have not set it there ... so it should be working
whats particularly odd is the system seems to be generally very unhappy with your environment
tell me about it :-)
there is anecdotal evidence in that log you pasted that both GOROOT and GOPATH are messed up
what would you do?
hmmm ... a full cleanup reinstall?
painful ...
well, before you do
(its actually relatively fast these days, but hold off on that)
can you run this from the vagrant prompt:
(and from the fabric folder
make clean docker 2>&1 | tee build.log
and then paste the build.log to something like pastebin.com
its building from fabric folder inside vagrant
what did "from the vagrant prompt" mean?
cool, send me the log when it fails
basically, i meant the same thing
ah
from a vagrant-shell would have been better phrasing
there were two ways to take it and I called the wrong side of the coin
@greg.haskins http://pastebin.com/mjkgu5KT
@kletkeman not sure I am misreading, but it looks like that build worked?
yes, seems to have
so was that a complete rebuild of the entire environment? perhaps I missed something inthe instructions previously?
Has joined the channel.
Has joined the channel.
fabric is up and running, so all is well ... many thanks Greg
Good work
@kletkeman I am not sure what went wrong, but "make clean docker" was a complete rebuild of the containers
@kletkeman I am not sure what went wrong initially, but "make clean docker" was a complete rebuild of the containers
@greg.haskins I apologize for abusing your time, but I am trying now to install my chaincode on peer0 and it says it cannot find my chaincode ... do you know where it is looking?
@kletkeman how are you installing?
CORE_PEER_ADDRESS=peer0:7051 peer chaincode install -n mycc -p github.com/ibm-watson-iot/blockchain-samples/fabricv1/examples/minimal -v v0
CLI? SDK?
cli\
hmm, I havent been in the CLI code recently, id have to look at how it does it
I'm assuming it is looking on the container file system
that would generally be correct for the SDK though
ok ... so perhaps I should just switch to the sdk ... a lot more work though ...
still, gotta bite that bullet soon anyway
Has joined the channel.
was just looking for a real quick test to see if I could talk to my iot platform samples
would you suggest using the end-toend test as a good starting point? or is there a better sample to get started on?
Is there a chance it's a 404
@conroydave I think it should be pulling from the file system, and of course I am running the CLI inside a container so I agree that it is a file not found ... the cli instructions have always been written for tire kickers working directly on example02 and this still seems to be the case
This project is pretty quick to get running https://github.com/IBM-Blockchain/fabric-boilerplate?files=1
The v2 TS branch is even easier
I'm not sure what a v2 TS is, but I really need to get our monitoring UI ported to v1 and the SDK ... so I have to take the hard path
I have my iot contract platform building, but REST is no longer available so it is looking like hours or days instead o minutes for this
ah ... a branch ... I'll poke around a bit to see if their client interface is useful, but in the end I need this inside our app
thanks
I joined the thread late thought you were just looking for some next steps after fabric was running
So what are peoples thoughts on the Ethereum enterprise meetings this week, and the partnership with microsoft, intel UBS ?
We got a full on arms race here? Plenty of room for competition?
Yes, the gauntlet is down.
do we have an example where i input the complete json for ctorMsg": {
"args": ......}
i think the example given with fabric takes each of the arguments as a string and give it through chain code , is there any other way ?
Has joined the channel.
with fabric 1.0, I've tried following event listener with chaincode "mycc" deployed, however, I can just get the **pb.Event_Block** event, while never received **pb.Event_ChaincodeEvent**, even though I've **SetEvent** in my chaincode's invoke function. Anyone can help me? Thank you
Has joined the channel.
Message Attachments
This is how I SetEvent in chaincode, when I invoke a transfer transaction, only block event is got when the block is committed to ledger
Message Attachments
@hanhzf not only pb.Event_ChaincodeEvent is not emitted, Rejection event is also not send. Probably is some work in progress, I ask same question before 2-3 days
@gatakka Thanks
That confused me for a while, and also I found examples/events/block_listener.go also does not handle ChaincodeEvent for now. :grin:
HL is developed realy fast, this type of issues are more than expected :)
Hi,I am using the lastest master branch of fabric.When run make peer and got the error "core/chaincode/shim/java/javabuild.sh: line 41: /usr/bin/gradle: No such file or directory" ,but before this I had got the message "Step 2/15 : RUN curl -sSL https://services.gradle.org/distributions/gradle-2.12-bin.zip > /tmp/gradle-2.12-bin.zip
" and "Step 3/15 : RUN unzip -qo /tmp/gradle-2.12-bin.zip -d /opt && rm /tmp/gradle-2.12-bin.zip" "Step 4/15 : RUN ln -s /opt/gradle-2.12/bin/gradle /usr/bin" .So,what's wrong?
Has joined the channel.
Hi there! Few questions about Fabric v1.
In the "Ordering Service" do we have a specific node that is elected (and how?) to gather the order of the tx before broadcasting this order to the committing peers (= all the peers of the network) ?
In fact, the "committing" peers are just regular peers that update their internal state locally according to what the orderer service peers decide?
We worked on the previous version of fabric and developed some convenient APIs. The problem is that now fabric v1 needs a SDK (which is around the Client App) to communicate with the chaincode, thus making absolete our API.
However we still want to keep the API because it makes it easier for anyone to interact with our chaincode without having to understand the complexity of the fabric SDK or re-write their code in java (for example, because the fabric SDK is in java)
How can we do that ?
We worked on the previous version of fabric and developed some convenient APIs. The problem is that now fabric v1 needs a SDK (which is around the Client App) to communicate with the chaincode, thus making absolete our API.
However we still want to keep the API because it makes it easier for anyone to interact with our chaincode without having to understand the complexity of the fabric SDK or re-write their code in java (for example, because the fabric SDK is in java)
How can we do that ? (also the SDK is handling the certificate of the Client locally, and if we use our API, we really don't want to "break" the identity-proof link by receiving request from the Client through our API on a server and then interacting (grpc) with the chaincode with its certificate our ours (1st case we will handle their certificate, we would rather not, 2nd case we will lose the traceability of whom made the tx)
We worked on the previous version of fabric and developed some convenient APIs. The problem is that now fabric v1 needs a SDK (which is around the Client App) to communicate with the chaincode, thus making absolete our API.
However we still want to keep the API because it makes it easier for anyone to interact with our chaincode without having to understand the complexity of the fabric SDK or re-write their code in java (for example, because the fabric SDK is in java)
How can we do that ? (also the SDK is handling the certificate of the Client locally, and if we use our API, we really don't want to "break" the identity-proof link by receiving request from the Client through our API on a server and then interacting (grpc) with the chaincode with its certificate or ours (1st case we will handle their certificate, we would rather not, 2nd case we will lose the traceability of whom made the tx)
We worked on the previous version of fabric and developed some convenient APIs. The problem is that now fabric v1 needs a SDK (which is around the Client App) to communicate with the chaincode, thus making absolete our API.
However we still want to keep the API because it makes it easier for anyone to interact with our chaincode without having to understand the complexity of the fabric SDK or re-write their code in java (for example, because the fabric SDK is in java)
How can we do that ? (also the SDK is handling the certificate of the Client locally, and if we use our API, we really don't want to "break" the identity-proof link by receiving request from the Client through our API on a server and then interacting (grpc) with the chaincode with its certificate or ours (1st case we will handle their certificate but we would rather not :), 2nd case we will lose the traceability of whom made the tx)
We worked on the previous version of fabric and developed some convenient APIs. The problem is that now fabric v1 needs a SDK (which is around the Client App) to communicate with the chaincode, thus making absolete our API.
However we still want to keep the API because it makes it easier for anyone to interact with our chaincode without having to understand the complexity of the fabric SDK or re-write their code in java (for example, because the fabric SDK is in java)
How can we do that ? (also the SDK is handling the certificate of the Client locally, and if we use our API, we really don't want to "break" the identity-proof link by receiving request from the Client through our API on a server and then interacting (grpc) with the chaincode with its certificate or ours (1st case we will handle their certificate but we would rather not, 2nd case we will lose the traceability of whom made the tx)
@vu3mmg @hanhzf We have an IoT contract platform that implements what I call simple recorder contracts. You can solve a lot of problems by remembering the state of an asset and that is what these do. We use JSON objects as input and output, defined in JSON Schema 4.0 and processed with out own Go script into a go file that can be returned to a client app that wants to perform some dynamic configuration based on the schema itself. In v0.6 we used POSTMAN to test the contracts, but in v1 we will be forced to use only our Monitoring application once I get that ported. We have built a lot of IoT contracts in the past and this is the distillation of that experience. Note that our platform emits an event carrying success or failure of each transaction and alert status changes (raised, cleared, active). This is different from unpacking block events to see what happened to individual transactions and/or receiving rejection events. If listening only to the EVT.IOTCP.INVOKE.RESULT chaincode event, you get notification of success or failure for every txn.
You might find something in there useful.
The platform is here: https://github.com/ibm-watson-iot/blockchain-samples/tree/master/contracts/platform
The track and trace sample is here: https://github.com/ibm-watson-iot/blockchain-samples/tree/master/contracts/industry/trackandtrace
PostMan env and collection is here: https://github.com/ibm-watson-iot/blockchain-samples/tree/master/contracts/platform/docs/testing/PostMan
Event listener in Go is here: https://github.com/ibm-watson-iot/blockchain-samples/tree/master/applications/event_listener
[ ](https://chat.hyperledger.org/channel/fabric?msg=xdLGciawYcHp9N2ku) @bkvellanki [ ](https://chat.hyperledger.org/channel/fabric?msg=xdLGciawYcHp9N2ku) @bkvellanki I have seen this error before. In my case, my linux machine was missing the library libltdl-devel. Once i installed it i had the header.
@sajz There is work on a REST interface for the SDK that you could feed with your requirements. Perhaps you can adjust your API to add security features to match what is done by the fabric itself.
A high school student approached me the other day — he wants to build a permissionless/trustless "channel" using Fabric v1.0. Wants to create a "Hypercoin". Now, I know most of us don't have this goal and aren't working on such a thing, but what would prevent or make it hard for this kid to do it?
Hyperledger TCS has just approved Fabric exiting incubator status
Hi all, in fabric v1.0, how do I debug chaincode? Using the instructions in `fabric/docs/install_instantiate.md` I install the chaincode,
```
root@9452e836c136:/opt/gopath/src/github.com/hyperledger/fabric/peer# CORE_PEER_ADDRESS=peer0:7051 peer chaincode install -n mykv -p github.com/hyperledger/fabric/examples/key_value -v v0
2017-03-02 15:23:06.579 UTC [logging] InitFromViper -> DEBU 001 Setting default logging level to DEBUG for command 'chaincode'
2017-03-02 15:23:06.597 UTC [msp] GetLocalMSP -> DEBU 002 Returning existing local MSP
2017-03-02 15:23:06.597 UTC [msp] GetDefaultSigningIdentity -> DEBU 003 Obtaining default signing identity
2017-03-02 15:23:06.615 UTC [golang/hash] collectChaincodeFiles -> DEBU 004 not using input for hash computation for path:"github.com/hyperledger/fabric/examples/key_value" name:"mykv" version:"v0"
2017-03-02 15:23:06.615 UTC [golang/hash] getCodeFromFS -> DEBU 005 getCodeFromFS github.com/hyperledger/fabric/examples/key_value
2017-03-02 15:23:06.615 UTC [util] HashFilesInDir -> DEBU 006 hashFiles /opt/gopath/src/github.com/hyperledger/fabric/examples/key_value
2017-03-02 15:23:06.627 UTC [container] WriteGopathSrc -> INFO 007 rootDirectory = /opt/gopath/src
2017-03-02 15:23:06.627 UTC [container] WriteFolderToTarPackage -> INFO 008 rootDirectory = /opt/gopath/src
2017-03-02 15:23:06.629 UTC [msp] Sign -> DEBU 009 Sign: plaintext: 0A96080A4E08032A4061373237336139...DDF97F000000FFFFFA94D922007A0000
2017-03-02 15:23:06.629 UTC [msp] Sign -> DEBU 00a Sign: digest: C4EFD84B51A404F79E6B66878CC013EF21A3774BF3E0BC1004117A58B1F71044
Installed remotely response:
@john.d.sheehan I'd say you have some errors in your go code and the fabric cannot build it
@Vadim `go build key_value.go` appears to work
```
%; go build key_value.go
03:50 PM ~/quickstart_fabric_v1/chaincode/key_value (chaincode)
```
I think it is a runtime issue, just not sure how to track it down, without running it :-)
do the example chaincodes work?
`chaincode_example02.go` works as outlined in `fabric/docs/install_instantiate.md`
well, you can try to comment out as much of your cc as possible till it starts working and then uncomment it back and find some line which causes it to fail. I would start specifically with the Init function.
I also think you can try to read the logs of the stopped container, run docker ps -a and then docker logs "container hash"
@Vadim I didn't realise docker held onto logs of exited containers, thanks for that - it appears to be a panic someplace
```
16:01:18.220 [BCCSP_FACTORY] DEBU : Initialize BCCSP [SW]
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x1008238c]
goroutine 43 [running]:
panic(0x10615440, 0xc420012050)
/opt/go/src/runtime/panic.go:500 +0x3a8
log.(*Logger).Output(0x0, 0x2, 0xc42034c1e0, 0x11, 0x0, 0x0)
/opt/go/src/log/log.go:147 +0x6c
log.(*Logger).Print(0x0, 0xc42037dca0, 0x3, 0x3)
/opt/go/src/log/log.go:178 +0x6c
main.(*KeyValue).Init(0x10976098, 0x1093d060, 0xc420380000, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0)
/chaincode/input/src/github.com/hyperledger/fabric/examples/key_value/key_value.go:19 +0x1a0
github.com/hyperledger/fabric/core/chaincode/shim.(*Handler).handleInit.func1(0xc42030c310, 0xc42025ab40)
/opt/gopath/src/github.com/hyperledger/fabric/core/chaincode/shim/handler.go:236 +0x8d0
created by github.com/hyperledger/fabric/core/chaincode/shim.(*Handler).handleInit
/opt/gopath/src/github.com/hyperledger/fabric/core/chaincode/shim/handler.go:257 +0x48
```
At least now I have some place to start :-)
@john.d.sheehan For basic debugging of chaincode, the tried and true printf has always been the gold standard in my opinion. This technique works really well when you can follow the instructions in the chaincode_setup document here: https://github.com/hyperledger/fabric/blob/master/docs/Setup/Chaincode-setup.md ... I have always used POSTMAN in v0.6 fabric and have collections for testing most of my sample contracts.
But REST is gone from v1 and the SDK is rather complex. I think you can still get away with the method where you run a peer and the chaincode in separate windows, but stimulating it is difficult without writing a bunch of SDK code. I have found the the cli instructions don't work when debugging code outside the fabric name space as only hyperledger project appears at /opt/gopath. In this case, I plan on testing my iot contract platform and samples using the install_and_instantiate doc to get the peers up and running (which I have now) and then installing and deploying the chaincode using the SDK. I will be writing individual small javascript modules to perform each API and simply running them as if CLI. A much longer process than REST on v0.6, but it is what we have.
I am working on hackfest v1. I have a few questions.
1) How do we deploy chaincode via CMDLine and test it using REST?
2) How do we define policies (Endorsement policy, etc)
3) Where do you configure the peer as endorser? I checked the core.yml file..etc, but could not find any reference?
4) I dont see any sample specs under proposal, any documentation?
If there is a documentation pertaining to all these, it would help me a lot as I am trying move POC project to V1.
https://chat.hyperledger.org/channel/fabric-maintainers?msg=mbCQfPqsgbpdkobCx
@bkvellanki re (1) I have been unable to deploy my own chaincode via CMDline, however if you copy your chaincode under the examples folder beside chaincode_example02, then you will be able to follow the install_and_instantiate document in the docs subfolder; as for REST, that no longer exists in v1, although there is a proposal to build a REST API on top of the SDK
Hi, This is a really general question, do we have any guidance on collecting analytics info from a Blockchain (KVS), or thoughts on architecture/best practices? Thanks!
This is a random question, but here goes: does anyone have an estimate of how many lines of code will be in Fabric 1.0?
Has joined the channel.
can anybody provide a example of JAVA SDK
can anybody provide a example of JAVA SDK as client to install,invoke and query the chaincode?thanks
@hanhzf @gatakka saw your messages about event, got a little interested, so I tried myself. Maybe you already knew that the block-listener has been updated for a while and it is now can deal with chaincode event. as for rejection event, the committer thought it was no long necesary. hope it can help
@WillsonKuang I assume you are downloading the latest java sdk from here:
https://github.com/hyperledger/fabric-sdk-java The readme has a lot of good information in it. I know that people writing the documentation are pretty aggressively updating sections. http://hyperledger-fabric.readthedocs.io/en/latest/
@willson see above. You can also try asking questions on fabric-sdk-java channel
@Willson ^^
@bkvellanki http://hyperledger-fabric.readthedocs.io/en/latest/ is getting updated fairly aggressively. have you looked at the getting started section?
@jimthematrix See @gatakka and @hanhzf comments on events above.
Please note that we Ramesh is posting on fabric-ci channel on the progress of publishing docker images and running through the ci
@gatakka @hanhzf all events are now processed through the block events, you can see here as an example of how to decode the block for the events you need: https://github.com/hyperledger/fabric-sdk-node/blob/master/fabric-client/lib/EventHub.js#L145
it's in node.js sdk but the protobuf structure to parse is the same for a go listener client
the kind of events that get extracted from the blocks: transaction commit, transaction reject, chaincode events
also, note that a GO SDK has just been proposed to include in hyperledger (and source code hosted in github): https://docs.google.com/document/d/1tYk3t8pF2mj4IGSzPvGopzKxSz8okTW749UyNqxTGZk/edit#heading=h.z6d96rq3y4w
[yong@bogon fabric]$ sudo -E make docker
Building build/docker/bin/peer
# github.com/hyperledger/fabric/vendor/github.com/miekg/pkcs11
vendor/github.com/miekg/pkcs11/pkcs11.go:30:18: fatal error: ltdl.h: No such file or directory
#include
I already install libtool-ltdl
how to resolve?
@yong first thing i would check is your go compiler version, I think 1.7 or higher is required
(I have 1.8)
[yong@bogon fabric]$ sudo -E go version
go version go1.7.5 linux/amd64
@yong you are missing a deb package [if you are on ubuntu] that provides ltdl.h, try installing `libltdl-dev`
@yong you are missing a deb package [if you are on ubuntu] that provides ltdl.h
@jimthematrix thanks for the explanation
@harsha I used fedora
Has joined the channel.
Hello, do we have a timeline for Fabric 1.0 release? thanks!
@yong then you should be installing `libtool-ltdl-devel`
yes,I installed libtool-ltdl-devel
Has joined the channel.
Anyone knows how to deserialize shim.getCreator() ??? I am trying to get the ECert in my chaincode
@levinkwong it's encoded as pem-certificate, but in the beginning there are some additional bytes which are not needed. I did not try to figure out what that is, just skipped it (it's 12 bytes). Then you can just parse pem like it's described here: https://golang.org/src/crypto/x509/example_test.go
thanks! I am trying to use a MSPManager which provides a DeserializeIndentity function
does it work?
Still coding
Turns out cannot do that , the Identity interface do not expose the cert itself
you need some specific data from the cert?
No, just some application logic, but I will check if I really need it
Very early stage of chaincode design
@levinkwong it does not expose the cert itself indeed. But it seems the GetCreator() returns the serialized SerializedIdentity, so if you parse it as SerializedIdentity, you can get the pem bytes.
I have to try that
But the deserializer return the Identity interface , cannot access the cert field inside
I mean, you just unmarshal it yourself
```
creatorByte, err := stub.GetCreator()
if err != nil {
return shim.Error("Error stub.GetCreator")
}
bl, _ := pem.Decode(creatorByte)
if bl == nil {
return shim.Error("Could not decode the PEM structure")
}
cert, err := x509.ParseCertificate(bl.Bytes)
if err != nil {
return shim.Error("ParseCertificate failed")
}
```
I came up with this
like
```
data, _ := stub.GetCreator()
serializedId := msp.SerializedIdentity{}
err := proto.Unmarshal(data, &serializedId)
```
`serializedId.IdBytes` should contain pem bytes
but does it work like that?
it has some prefix, so parsing fails, no?
I am now finding how to test it ....
Very new to this :joy:
so I also did it like you, but to make it work, I had to `bl, _ := pem.Decode(creatorByte[12:])`
the first 12 bytes is MSP ID if I correclty understand
Has joined the channel.
Thanks so much! Could you give me some reference for chaincode development? Like the testing I need to do now
I usually just deploy it and print the output, like fmt.Printf() in the easiest case
@levinkwong all right, so I can confirm that it works like this:
```
data, _ := stub.GetCreator()
serializedId := msp.SerializedIdentity{}
err := proto.Unmarshal(data, &serializedId)
bl, _ := pem.Decode(serializedId.IdBytes)
```
Has joined the channel.
Thanks!
Hey, trying to run the hackfest stuff. Everything works fine, but the channel_test.sh file doesn't get run.
I've tried running it manually by ssh-ing into the container and running, but I get a permission denied. So I'm guessing this is a permissions issue
Here are the permissions: `-rw-rw-r-- 1 1000 1000 2251 Mar 2 22:20 channel_test.sh`
Do I need to change them? and if so, where & how? in my local, on the remote or via docker?
I'm running Fabric with Ubuntu 16.04 natively
Hey, trying to run the hackfest stuff. Everything works fine, but the channel_test.sh file doesn't get run.
I've tried running it manually by jumping into the container and running, but I get a permission denied error. So I'm guessing this is a permissions issue
Here are the permissions: `-rw-rw-r-- 1 1000 1000 2251 Mar 2 22:20 channel_test.sh`
Do I need to change them? and if so, where & how? in my local, on the remote or via docker?
I'm running Fabric with Ubuntu 16.04 natively
Has joined the channel.
Hi there
I'm currently getting some import error when executing make behave :
```
$ make behave 1 ↵
mkdir -p build/image/peer/payload
cp build/docker/bin/peer peer/core.yaml build/msp-sampleconfig.tar.bz2 common/configtx/tool/configtx.yaml build/image/peer/payload
....
Running behave tests
Exception ImportError: No module named 'bootstrap_util'
Traceback (most recent call last):
File "/usr/local/bin/behave", line 11, in
so tried to find the package bootstrap_util but fail... can you point me the python package to install here ?
ok guess I found it : => ./bddtests/steps/bootstrap_util.py ;)
from this article https://medium.com/wearetheledger/first-steps-in-hyperledger-fabric-v0-6-2aefcc30b491#.nvxl5ffg3
where I can find this link https://github.com/hyperledger/fabric/blob/master/docs/dev-setup/devenv.md
is Vagrant and fabric environment for v0.6
from this article https://medium.com/wearetheledger/first-steps-in-hyperledger-fabric-v0-6-2aefcc30b491#.nvxl5ffg3
where I can find this link https://github.com/hyperledger/fabric/blob/master/docs/dev-setup/devenv.md ?
is Vagrant and fabric environment for v0.6
@rrader check https://github.com/hyperledger/fabric/tree/v0.6
@rrader check https://github.com/hyperledger/fabric/blob/v0.6/docs/dev-setup/devenv.md
@Vadim thanks
Hi, I can no longer create a channel. I just pulled the latest changes and the instructions in `docs/source/install_instantiate.rst` no longer seem to work. I can build the docker containers and connect to the cli container
```
docker exec -it cli bash
```
but when I run channel create
```
root@a8d768fb711a:/opt/gopath/src/github.com/hyperledger/fabric/peer# peer channel create -c myc
Error: Ordering service endpoint is not valid or missing
```
Is the `docs/source/docker-2peer.yml` no longer valid?
@pd93 I think you need to get up to the latest images honestly. There have been a lot of updates. @ratnakar posted this on another channel I think you might find useful- (of course the images are probably updated now since this was posted) Ratnakar tested the End-to-End flow based on chaincode_example02, docker compose and scripts are available in this repository https://github.com/ratnakar-asara/e2e (probably they will be moved to fabric/examples/e2e at some point of time).
You can build your images to use the docker-compose file available or you can use the below stable images and change your docker-compose file to point to those images.
rameshthoomu/fabric-orderer-x86_64:x86_64-0.7.0-snapshot-9a09ac0
rameshthoomu/fabric-peer-x86_64:x86_64-0.7.0-snapshot-9a09ac0
rameshthoomu/fabric-ccenv-x86_64:x86_64-0.7.0-snapshot-9a09ac0
This example does the below:
* Creates two organizations with each Organization containing two peers ( with an anchor peer from each Org )
* One orderer service.
* create a channel
* Join all the peers to the channel
* Install chaincode on two peers
* Instantiate the chaincode.
* Invoke transaction
* Query on chaincode.
@Ratnakar may be able to help you when you run into questions on this
@john.d.sheehan There is a change set - https://gerrit.hyperledger.org/r/#/c/6607/8 that they are trying to get checked in that i think will help you
@weeds what is an anchor peer?
@vadim The peer node that anchors a cluster of one, or more, peer nodes belonging to a Member participating in a Channel. Anchor peers are defined in the channel’s configuration and serve as a routing apparatus for gossip protocol.
@Vadim ^^
I would also suggest you could take a look here: http://hyperledger-fabric.readthedocs.io/en/latest/channel-setup.html?highlight=anchor%20peer
ok, thanks
@weeds thanks for the detailed reply. Very helpful. I'll work my way through the example. I've currently run `make docker` on the v1.0.0-preview commit level for fabric-ca and fabric. Are Ratnakar's images more up to date than this? Also, is it safe to build these from master or are there likely to be bugs?
@weeds thanks for the detailed reply. Very helpful. I'll work my way through the example. I've currently run `make docker` on the v1.0.0-preview commit level for fabric-ca and fabric. Are Ratnakar's images more up to date than this? Also, is it safe to build these from master or are there likely to be bugs?
-- edit -- nevermind, the answer to my questions are in the link you sent :thumbsup:
@weeds thanks for the detailed reply. Very helpful. I'll work my way through the example. I've currently run `make docker` on the v1.0.0-preview commit level for fabric-ca and fabric. Are Ratnakar's images more up to date than this? Also, is it safe to build these from master or are there likely to be bugs?
*-- edit --* nevermind, the answer to my questions are in the link you sent :thumbsup:
@weeds thank you for the info. That change set, is it similar to the repo you referenced https://github.com/ratnakar-asara/e2e ?
@Ratnakar I'll let you take the questions from John and PD93 since I was out yesterday- want to make sure the info is up to date and I don't answer incorrectly ;-).
@Ratnakar I don't seem to be able to run `make configtxgen` :/ Does this *have* to be run from Vagrant? I was trying to do things natively (Ubuntu 16.04) if it's possible
@pd93 It will take some time get the latest official images, till then it is preferable to generate your own images using `make docker` command
@john.d.sheehan Yes I have uploaded the same changes to my repo aswell, while the changes on fabric repo https://gerrit.hyperledger.org/r/#/c/6607 are still in review state . For now you can refer this https://github.com/ratnakar-asara/e2e
@pd93 It should be possible to generate the configtxgen on native ubuntu, However you cannot access the binary directly and you should use the command like this
`./build/bin/configtxgen -profile TwoOrgs -outputBlock
we were able to use this tool on our not vagrant environment like CI Jenkins.
@pd93 Please let me know if there if you see any issues
Ok great :) I'll give it a go and report back if I find any issues. Thanks for the help
@Ratnakar Ok great :) I'll give it a go and report back if I find any issues. Thanks for the help
@Ratnakar FYI, this link appears to be broken in your e2e guide https://github.com/hyperledger/fabric/blob/master/docs/configtxgen.md
@pd93 Thanks for pointing that , Yes yesterday there is a change which broken the links
Here is the right link https://github.com/hyperledger/fabric/blob/master/docs/source/configtxgen.rst
:thumbsup: thanks
:thumbsup: Thanks
Also Incase , if you want to use the latest stable images rameshthoomu is publishing them daily through his Jenkins , please take a look at this channel #fabric-ci
That's good to know. I guess you're less likely to run into bugs with those builds than you are with the master branch?
Also I'm getting `vendor/github.com/miekg/pkcs11/pkcs11.go:29:18: fatal error: ltdl.h: No such file or directory`
I know this is a missing library. But not sure what I need to install?
That's good to know. I guess you're less likely to run into bugs with those builds than you are with the master branch?
Also I'm getting `vendor/github.com/miekg/pkcs11/pkcs11.go:29:18: fatal error: ltdl.h: No such file or directory`
I know this is a missing library. But not sure what I need to install?
*-- edit --* Fixed with `sudo apt-get install libltdl-dev`
Has joined the channel.
I have a question regarding the ordering service on Fabric. What 'validity' checks do the orderers do? I know that Endorsers sign transactions first, do orderers check these signatures? Howe do the orderers know what signatures to check?
I recall reading that if there's a need to keep certain data private from a group of participants in the network, then multiple channels can be used, where one channel is open to everyone and another one is available only to that specific group in the network. In this case, would it be possible to use a single channel instead of using multiple channels? Is this addressed in v1? Thanks for sharing any insights on this
From this article https://medium.com/wearetheledger/first-steps-in-hyperledger-fabric-v0-6-2aefcc30b491#.9114zoev1
($GOPATH/src/github.com/hyperledger/fabric/peer). Open the core.yaml file and set the security.enabled value to true. Also modify the security.value to true.
I can't find security, in that file, can someone help?
@rrader - that was for the v0.6 release. if you are looking at the current stuff on fabric master that setting is no longer applicable
(security is always enabled)
ok, thanks
then I think this http://hyperledger-fabric.readthedocs.io/en/v0.6/Setup/Chaincode-setup/#running-the-validating-peer also should be modified
As I understand, all peers are stored in fabric in VM. Each peer stores all blockchain history.
When I want to build an application I should provide an interface where a user can make a change, that change will be saved in his peer and consensus network will add that change to all peers.
It is my understanding, please correct me if I am wrong.
As I understand, all peers are stored in fabric in VM. Each peer stores all blockchain history.
When I want to build an application I should provide an interface where a user can make a change, that change will be saved in his peer and consensus network will add that change to all peers.
It is my understanding, please correct me if I am wrong or confirm.
It should be something like https://www.altoros.com/blog/wp-content/uploads/2017/02/Hyperledger-Webinar-Thomas-Marckx-architecture.jpg ?
So, each application's user send request to application(backend API) and application send request to fabric(user's peer) ?
https://www.hyperledger.org/blog/2017/03/03/our-incubators-first-graduate-hyperledger-fabric
Has joined the channel.
Has joined the channel.
Hello, I am having an issue with bring up v0.6 fabric using docker-compose images....it worked fine with SLES12 4 months ago, but when I just tried again with RHEL7.2 or Windows 10, just getting this same error...
Message Attachments
has anyone seen this error before?
2017/03/04 04:48:02 grpc: addrConn.resetTransport failed to create client transport: connection error: desc = "transport: dial tcp 47.19.64.71:7054: i/o ti
vp_1 | 2017/03/04 04:48:22 grpc: addrConn.resetTransport failed to create client transport: connection error: desc = "transport: dial tcp 47.19.64.71:7054: i/o ti
vp_1 | 2017/03/04 04:48:42 grpc: addrConn.resetTransport failed to create client transport: connection error: desc = "transport: dial tcp 47.19.64.71:7054: i/o ti
vp_1 | 2017/03/04 04:49:02 grpc: addrConn.resetTransport failed to create client transport: connection error: desc = "transport: dial tcp 47.19.64.71:7054: i/o ti
vp_1 | 2017/03/04 04:49:22 grpc: addrConn.resetTransport failed to create client transport: connection error: desc = "transport: dial tcp 47.19.64.71:7054: i/o ti
vp_1 | 04:49:22.606 [crypto] Errorf -> ERRO 01e [validator.vp] Failed requesting read certificate [rpc error: code = 14 desc = grpc: RPC failed fast due to transp
vp_1 | 04:49:22.606 [crypto] Errorf -> ERRO 01f [validator.vp] Failed requesting ECA certificate [rpc error: code = 14 desc = grpc: RPC failed fast due to transpo
vp_1 | 04:49:22.606 [crypto] Errorf -> ERRO 020 [validator.vp] Failed getting ECA certificate [rpc error: code = 14 desc = grpc: RPC failed fast due to transport
vp_1 | 04:49:22.606 [crypto] Errorf -> ERRO 021 [validator.vp] Failed retrieving ECA certs chain [rpc error: code = 14 desc = grpc: RPC failed fast due to transpo
vp_1 | 04:49:22.606 [crypto] Errorf -> ERRO 022 [validator.vp] Failed registering node crypto engine [rpc error: code = 14 desc = grpc: RPC failed fast due to tra
vp_1 | 04:49:22.606 [crypto] Errorf -> ERRO 023 [validator.vp] Failed registering peer [vp]: [rpc error: code = 14 desc = grpc: RPC failed fast due to transport f
vp_1 | 04:49:22.606 [crypto] Errorf -> ERRO 024 [validator.vp] Failed registering [vp]: [rpc error: code = 14 desc = grpc: RPC failed fast due to transport failur
vp_1 | 04:49:22.606 [crypto] RegisterValidator -> ERRO 025 Failed registering validator [vp] with name [vp] [rpc error: code = 14 desc = grpc: RPC failed fast due
vp_1 | Error: rpc error: code = 14 desc = grpc: RPC failed fast due to transport failure
vp_1 | Usage:
vp_1 | peer node start [flags]
vp_1 |
vp_1 | Flags:
vp_1 | -h, --help help for start
vp_1 | --peer-chaincodedev Whether peer in chaincode development mode
vp_1 |
vp_1 | Global Flags:
vp_1 | --logging-level string Default logging level and overrides, see core.yaml for full syntax
vp_1 | --test.coverprofile string Done (default "coverage.cov")
vp_1 | -v, --version Display current version of fabric peer server
vp_1 |
dockercompose_vp_1 exited with code 1
Can someone help with this https://stackoverflow.com/questions/42587993/hyperledger-v0-6-anatomy ?
So, in v0.6 you can send requests using REST so a user can simply send the request to the peer itself
In v1.0 you have to use SDK which uses gRPC to communicate with the peer, @rrader so most likely a user will interact with a backend written in some language (i.e node.js / java)
If I want to build something like bitcoin in fabric, will one user correspond to one peer?
Seems peer and orderer docker containers are missing even basic network commands like `ping` `netstat` that could be very useful in debugging :(
you can install them - @rickr but you're right
Any consideration in putting the configtxgen in the orderer peer docker so users could run it with a version that matches an not get it via having to download the source ?
https://github.com/IBM-Blockchain/marbles/blob/master/docs/host_marbles_locally.md
I get error https://gist.github.com/anonymous/58eb7a97baca43989692aa6b1b4964f8
Has joined the channel.
As I understand in v0.6 the number of nodes and identities of those nodes be known ahead of time, this is required by PBFT consensus algorithm, in v1 will be the same?
Has joined the channel.
@rrader This will be the case for the ordering nodes in the SBFT variant.
Has joined the channel.
@takemiyamakoto without looking at the source code I can smell that the iOS app for Rocket.Chat is a "hybrid app" built with Cordova, it's got all the terrible "features" that come with it, laggy UI, refresh problems, page resize issues
Has joined the channel.
Hi All, am refering docker-compose.yml file which is present in "fabric/examples/e2e_cli", if i run docker-compose up it will get all images from github and build the containers, but if want to make changes to any config files say core.yml ( want to change leveldb to couchdb ) how can do it
@MadhavaReddy in general core.yaml properties can be overridden using ENV vars in docker-compose files
a typical docker compose probably has some examples of it...
youd start with CORE_ prefix and overrider the property in core.yaml
ok so i can have my own core.yml file defined locally and refer this in docker-compose.yml
well, your core.yaml is in the docker image... but the property theres can be overridden with env var in docker compose. For example `CORE_PEER_LOCALMSPID=Org0MSP` in examples/e2e_cli/docker_compose.yml overrides the `localMspId: DEFAULT` in core.yaml
ie, easier to override using env vars in docker compose files than change core.yaml
am planning to using couchdb for marble example so in that case i can add "CORE_LEDGER_STATE_COUCHDBCONFIG_COUCHDBADDRESS=couchdb0:5984" in docker-compose.yml right along with
couchdb0:
container_name: couchdb0
image: klaemo/couchdb:2.0.0
ports:
- "5984:5984"
networks:
- bridge
looks close... defintely worth a try
you'd want to make the couchdb starts before the peer
yes am maintaining seq in docker-compose file
ok
also order type is defined " ORDERER_GENERAL_ORDERERTYPE=solo " in docker-compose file but for Kafka i believe other than orderer type we may need define some other properties, is that correct?
Has joined the channel.
Has joined the channel.
@Ratnakar Hi, sorry to bother you. I just read your latest commit --"fabric/examples/e2e_cli", and I followed the steps described in end-to-end.rst. Everything works fine except one error kept coming up
'Illegal file mode detected for file src/github.com/hyperledger/fabric/examples/chaincode/go/chaincode_example02/chaincode_example02.go: 100777'
could you so kindly tell me where I did wrong? very much appreciate it.
@Hangyu Could you tell me what OS are you running your setup. we saw this issue reported by couple of people
@Hangyu Could you tell me what OS are you running your setup. we saw this issue reported by couple of window users
@Ratnakar Yes, I am runing vagrant on windows 8
Changing the mode of the file `examples/chaincode/go/chaincode_example02/chaincode_example02.go` to 0666 didn't helped you ?
I think @muralisr or @greg.haskins shall be able to address this issue. This issue is seen only on windows.
@rameshthoomu and couple of others also facing this issue and here is the issue for your reference https://jira.hyperledger.org/browse/FAB-2569
Hi team:
I know gensis block would have a basic configuration about a channel, and would send it to all the peers as the first block of corresponding ledger.
If there any ref could help me got a deep understanding of it?
@Ratnakar @Hangyu im guessing the user is using the CLI to deploy?
Yes @greg.haskins , even my guess is also the same
I think its all related to this: https://jira.hyperledger.org/browse/FAB-2493
the SDK was (partially) fixed (https://gerrit.hyperledger.org/r/#/c/6583/) and the CLI has not been addressed yet
as a work-around, either use the SDK or do not try to package your code up in a virtualbox shared drive
windows seems to mishandle perms
once the the CLI is fixed as part of 2493, windows+shared-drive will work once again
@greg.haskins Thankyou, that explains all :) , I will quote 2493 instead of 2569
@Ratnakar @greg.haskins Thanks a lot for the input.
Has joined the channel.
root@fu-yong:/opt/gopath/src/github.com/hyperledger/fabric/docs/source# docker-compose -f docker-2peer.yml up
Starting orderer
Starting peer1
Starting peer0
Starting cli
Attaching to orderer, peer0, peer1, cli
orderer | standard_init_linux.go:178: exec user process caused "exec format error"
peer0 | standard_init_linux.go:178: exec user process caused "exec format error"
orderer exited with code 1
peer1 | standard_init_linux.go:178: exec user process caused "exec format error"
peer0 exited with code 1
peer1 exited with code 1
^CGracefully stopping... (press Ctrl+C again to force)
Stopping cli ... done
my docker version：
root@fu-yong:/opt/gopath/src/github.com/hyperledger/fabric/docs/source# docker version
Client:
Version: 17.03.0-ce
API version: 1.26
Go version: go1.7.5
Git commit: 3a232c8
Built: Tue Feb 28 08:01:32 2017
OS/Arch: linux/amd64
Server:
Version: 17.03.0-ce
API version: 1.26 (minimum version 1.12)
Go version: go1.7.5
Git commit: 3a232c8
Built: Tue Feb 28 08:01:32 2017
OS/Arch: linux/amd64
Experimental: false
Setting my dev environment on a new laptop, and getting this error whenever I try to run a test:
```# github.com/hyperledger/fabric/vendor/github.com/miekg/pkcs11
../vendor/github.com/miekg/pkcs11/pkcs11.go:29:18: fatal error: ltdl.h: No such file or directory
#include
@kostas either use "make unit-test" which should insulate you from host dependencies, or install the libltdl-dev package for your platform
@greg.haskins: You are a gentleman and a scholar.
you might have to search around for the actual name
for instance, i think its -dev on OSX and -devel on centos
I've got an Ubuntu machine (first time!), but I think I'll roll with `make unit-test` since I'm going to be using this command anyway. Thanks!
@yong that is an odd one indeed
@yong pls run this and post result: `$ docker images | grep hyperledger`
hyperledger/fabric-zookeeper latest 788df3757715 18 hours ago 1.64 GB
hyperledger/fabric-zookeeper x86_64-0.7.0-snapshot-509d8ed 788df3757715 18 hours ago 1.64 GB
hyperledger/fabric-testenv latest 985627163c7e 18 hours ago 1.5 GB
hyperledger/fabric-testenv x86_64-0.7.0-snapshot-509d8ed 985627163c7e 18 hours ago 1.5 GB
hyperledger/fabric-buildenv latest 2cf953ebf274 18 hours ago 1.5 GB
hyperledger/fabric-buildenv x86_64-0.7.0-snapshot-509d8ed 2cf953ebf274 18 hours ago 1.5 GB
hyperledger/fabric-orderer latest a3f180d2b54d 18 hours ago 161 MB
hyperledger/fabric-orderer x86_64-0.7.0-snapshot-509d8ed a3f180d2b54d 18 hours ago 161 MB
hyperledger/fabric-peer latest 7b8d79b172f8 18 hours ago 161 MB
hyperledger/fabric-peer x86_64-0.7.0-snapshot-509d8ed 7b8d79b172f8 18 hours ago 161 MB
hyperledger/fabric-javaenv latest 627e889a0196 18 hours ago 1.5 GB
hyperledger/fabric-javaenv x86_64-0.7.0-snapshot-509d8ed 627e889a0196 18 hours ago 1.5 GB
hyperledger/fabric-ccenv latest bb061bdf3646 18 hours ago 1.48 GB
hyperledger/fabric-ccenv x86_64-0.7.0-snapshot-509d8ed bb061bdf3646 18 hours ago 1.48 GB
hyperledger/fabric-ca latest 8c84574989dc 18 hours ago 161 MB
hyperledger/fabric-ca x86_64-0.7.0-snapshot-f18b6b7 8c84574989dc 18 hours ago 161 MB
hyperledger/fabric-baseimage x86_64-0.3.0 1bee9664f867 23 hours ago 1.46 GB
hyperledger/fabric-baseimage x86_64-0.3.0-ubuntu f4751a503f02 5 weeks ago 1.27 GB
hyperledger/fabric-baseos x86_64-0.3.0 c3a4cf3b3350 5 weeks ago 161 MB
@kostas apt-get install libltdl-dev
@yong: Ah cool, thanks!
@greg.haskins sorry, What meaning is 'that is an odd one indeed'?
@yong your error message above, specifically `exec user process caused "exec format error"`
can you try this now: `$docker run -it --rm hyperledger/fabric-orderer /bin/bash`
if that works, you should get a root$ prompt inside the container
if so, try to run "orderer" and see what happens
actually looking at the compose file though, it looks suspect
@greg.haskins root@fu-yong:~# docker run -it --rm hyperledger/fabric-orderer /bin/bash
root@7bea2f7fff47:/#
yes,It work
I suspect running "orderer" will work too
I suspect the problem is that those "working_dir" directives look wrong
you can try editing the file just to remove them
@nickgaski any ideas on why the github.com/hyperledger/fabric/docs/source/docker-2peer.yml has explicit working_dir directives?
Has joined the channel.
@greg.haskins It still doesn't work，Still occur some problem
root@fu-yong:/opt/gopath/src/github.com/hyperledger/fabric/examples/e2e_cli# docker-compose up
WARNING: The CHANNEL_NAME variable is not set. Defaulting to a blank string.
Creating orderer
Creating peer0
Creating peer1
Creating peer2
Creating peer3
Creating cli
Attaching to orderer, peer0, peer1, peer2, peer3, cli
orderer | standard_init_linux.go:178: exec user process caused "exec format error"
peer0 | standard_init_linux.go:178: exec user process caused "exec format error"
peer1 | standard_init_linux.go:178: exec user process caused "exec format error"
peer2 | standard_init_linux.go:178: exec user process caused "exec format error"
peer3 | standard_init_linux.go:178: exec user process caused "exec format error"
Is somethere a explanation of how it all components work/interract like in this response http://stackoverflow.com/questions/42587993/hyperledger-v0-6-anatomy/42614834#42614834 ?
Is somethere a explanation of how all components work/interract like in this response http://stackoverflow.com/questions/42587993/hyperledger-v0-6-anatomy/42614834#42614834 ?
Has joined the channel.
Hello, I have some issue when installing chaincode. I execute:
peer chaincode install -n mycc -p github.com/hyperledger/fabric/examples/chaincode/go/chaincode_example01 -v v0 -o orderer:7050
And got:
```
panic: runtime error: index out of range
goroutine 1 [running]:
panic(0xc191a0, 0xc4200140b0)
/opt/go/src/runtime/panic.go:500 +0x1a1
github.com/hyperledger/fabric/core/chaincode/platforms/golang.(*Platform).ValidateSpec(0x1325598, 0xc420217480, 0x1325598, 0x0)
/opt/gopath/src/github.com/hyperledger/fabric/core/chaincode/platforms/golang/platform.go:87 +0x36d
github.com/hyperledger/fabric/peer/chaincode.checkSpec(0xc420217480, 0x6, 0xc42019ab8c)
/opt/gopath/src/github.com/hyperledger/fabric/peer/chaincode/common.go:51 +0xf1
github.com/hyperledger/fabric/peer/chaincode.getChaincodeBytes(0xc420217480, 0xc420217401, 0x0, 0x0, 0x0)
/opt/gopath/src/github.com/hyperledger/fabric/peer/chaincode/common.go:59 +0x147
github.com/hyperledger/fabric/peer/chaincode.chaincodeInstall(0xc4201db440, 0xc420212500, 0x0, 0x8, 0xc420209ef0, 0x9, 0x9)
/opt/gopath/src/github.com/hyperledger/fabric/peer/chaincode/install.go:107 +0x2b1
github.com/hyperledger/fabric/peer/chaincode.installCmd.func1(0xc4201db440, 0xc420212500, 0x0, 0x8, 0x0, 0x0)
/opt/gopath/src/github.com/hyperledger/fabric/peer/chaincode/install.go:46 +0x52
github.com/hyperledger/fabric/vendor/github.com/spf13/cobra.(*Command).execute(0xc4201db440, 0xc420212480, 0x8, 0x8, 0xc4201db440, 0xc420212480)
/opt/gopath/src/github.com/hyperledger/fabric/vendor/github.com/spf13/cobra/command.go:599 +0x234
github.com/hyperledger/fabric/vendor/github.com/spf13/cobra.(*Command).ExecuteC(0x12cfce0, 0xf, 0xc4201bd0e8, 0x7)
/opt/gopath/src/github.com/hyperledger/fabric/vendor/github.com/spf13/cobra/command.go:689 +0x367
github.com/hyperledger/fabric/vendor/github.com/spf13/cobra.(*Command).Execute(0x12cfce0, 0x28, 0xc4201bd0e8)
/opt/gopath/src/github.com/hyperledger/fabric/vendor/github.com/spf13/cobra/command.go:648 +0x2b
main.main()
/opt/gopath/src/github.com/hyperledger/fabric/peer/main.go:111 +0x52d
```
I am using master version build from vagrant make
Hello, I have some issue when installing chaincode. I execute:
peer chaincode install -n mycc -p github.com/hyperledger/fabric/examples/chaincode/go/chaincode_example01 -v v0 -o orderer:7050
And got:
```
panic: runtime error: index out of range
goroutine 1 [running]:
panic(0xc191a0, 0xc4200140b0)
/opt/go/src/runtime/panic.go:500 +0x1a1
github.com/hyperledger/fabric/core/chaincode/platforms/golang.(*Platform).ValidateSpec(0x1325598, 0xc420217480, 0x1325598, 0x0)
/opt/gopath/src/github.com/hyperledger/fabric/core/chaincode/platforms/golang/platform.go:87 +0x36d
github.com/hyperledger/fabric/peer/chaincode.checkSpec(0xc420217480, 0x6, 0xc42019ab8c)
/opt/gopath/src/github.com/hyperledger/fabric/peer/chaincode/common.go:51 +0xf1
github.com/hyperledger/fabric/peer/chaincode.getChaincodeBytes(0xc420217480, 0xc420217401, 0x0, 0x0, 0x0)
/opt/gopath/src/github.com/hyperledger/fabric/peer/chaincode/common.go:59 +0x147
github.com/hyperledger/fabric/peer/chaincode.chaincodeInstall(0xc4201db440, 0xc420212500, 0x0, 0x8, 0xc420209ef0, 0x9, 0x9)
/opt/gopath/src/github.com/hyperledger/fabric/peer/chaincode/install.go:107 +0x2b1
github.com/hyperledger/fabric/peer/chaincode.installCmd.func1(0xc4201db440, 0xc420212500, 0x0, 0x8, 0x0, 0x0)
/opt/gopath/src/github.com/hyperledger/fabric/peer/chaincode/install.go:46 +0x52
github.com/hyperledger/fabric/vendor/github.com/spf13/cobra.(*Command).execute(0xc4201db440, 0xc420212480, 0x8, 0x8, 0xc4201db440, 0xc420212480)
/opt/gopath/src/github.com/hyperledger/fabric/vendor/github.com/spf13/cobra/command.go:599 +0x234
github.com/hyperledger/fabric/vendor/github.com/spf13/cobra.(*Command).ExecuteC(0x12cfce0, 0xf, 0xc4201bd0e8, 0x7)
/opt/gopath/src/github.com/hyperledger/fabric/vendor/github.com/spf13/cobra/command.go:689 +0x367
github.com/hyperledger/fabric/vendor/github.com/spf13/cobra.(*Command).Execute(0x12cfce0, 0x28, 0xc4201bd0e8)
/opt/gopath/src/github.com/hyperledger/fabric/vendor/github.com/spf13/cobra/command.go:648 +0x2b
main.main()
/opt/gopath/src/github.com/hyperledger/fabric/peer/main.go:111 +0x52d
```
I am using master version build from vagrant make
Hello, I have some issue when installing chaincode. I execute:
```
peer chaincode install -n mycc -p github.com/hyperledger/fabric/examples/chaincode/go/chaincode_example01 -v v0 -o orderer:7050
```
And got:
```
panic: runtime error: index out of range
goroutine 1 [running]:
panic(0xc191a0, 0xc4200140b0)
/opt/go/src/runtime/panic.go:500 +0x1a1
github.com/hyperledger/fabric/core/chaincode/platforms/golang.(*Platform).ValidateSpec(0x1325598, 0xc420217480, 0x1325598, 0x0)
/opt/gopath/src/github.com/hyperledger/fabric/core/chaincode/platforms/golang/platform.go:87 +0x36d
github.com/hyperledger/fabric/peer/chaincode.checkSpec(0xc420217480, 0x6, 0xc42019ab8c)
/opt/gopath/src/github.com/hyperledger/fabric/peer/chaincode/common.go:51 +0xf1
github.com/hyperledger/fabric/peer/chaincode.getChaincodeBytes(0xc420217480, 0xc420217401, 0x0, 0x0, 0x0)
/opt/gopath/src/github.com/hyperledger/fabric/peer/chaincode/common.go:59 +0x147
github.com/hyperledger/fabric/peer/chaincode.chaincodeInstall(0xc4201db440, 0xc420212500, 0x0, 0x8, 0xc420209ef0, 0x9, 0x9)
/opt/gopath/src/github.com/hyperledger/fabric/peer/chaincode/install.go:107 +0x2b1
github.com/hyperledger/fabric/peer/chaincode.installCmd.func1(0xc4201db440, 0xc420212500, 0x0, 0x8, 0x0, 0x0)
/opt/gopath/src/github.com/hyperledger/fabric/peer/chaincode/install.go:46 +0x52
github.com/hyperledger/fabric/vendor/github.com/spf13/cobra.(*Command).execute(0xc4201db440, 0xc420212480, 0x8, 0x8, 0xc4201db440, 0xc420212480)
/opt/gopath/src/github.com/hyperledger/fabric/vendor/github.com/spf13/cobra/command.go:599 +0x234
github.com/hyperledger/fabric/vendor/github.com/spf13/cobra.(*Command).ExecuteC(0x12cfce0, 0xf, 0xc4201bd0e8, 0x7)
/opt/gopath/src/github.com/hyperledger/fabric/vendor/github.com/spf13/cobra/command.go:689 +0x367
github.com/hyperledger/fabric/vendor/github.com/spf13/cobra.(*Command).Execute(0x12cfce0, 0x28, 0xc4201bd0e8)
/opt/gopath/src/github.com/hyperledger/fabric/vendor/github.com/spf13/cobra/command.go:648 +0x2b
main.main()
/opt/gopath/src/github.com/hyperledger/fabric/peer/main.go:111 +0x52d
```
I am using master version build from vagrant make
Hello, I have some issue when installing chaincode. I execute:
```
peer chaincode install -n mycc -p github.com/hyperledger/fabric/examples/chaincode/go/chaincode_example01 -v v0 -o orderer:7050
```
And got:
```
panic: runtime error: index out of range
goroutine 1 [running]:
panic(0xc191a0, 0xc4200140b0)
/opt/go/src/runtime/panic.go:500 +0x1a1
github.com/hyperledger/fabric/core/chaincode/platforms/golang.(*Platform).ValidateSpec(0x1325598, 0xc420217480, 0x1325598, 0x0)
/opt/gopath/src/github.com/hyperledger/fabric/core/chaincode/platforms/golang/platform.go:87 +0x36d
github.com/hyperledger/fabric/peer/chaincode.checkSpec(0xc420217480, 0x6, 0xc42019ab8c)
/opt/gopath/src/github.com/hyperledger/fabric/peer/chaincode/common.go:51 +0xf1
github.com/hyperledger/fabric/peer/chaincode.getChaincodeBytes(0xc420217480, 0xc420217401, 0x0, 0x0, 0x0)
/opt/gopath/src/github.com/hyperledger/fabric/peer/chaincode/common.go:59 +0x147
github.com/hyperledger/fabric/peer/chaincode.chaincodeInstall(0xc4201db440, 0xc420212500, 0x0, 0x8, 0xc420209ef0, 0x9, 0x9)
/opt/gopath/src/github.com/hyperledger/fabric/peer/chaincode/install.go:107 +0x2b1
github.com/hyperledger/fabric/peer/chaincode.installCmd.func1(0xc4201db440, 0xc420212500, 0x0, 0x8, 0x0, 0x0)
/opt/gopath/src/github.com/hyperledger/fabric/peer/chaincode/install.go:46 +0x52
github.com/hyperledger/fabric/vendor/github.com/spf13/cobra.(*Command).execute(0xc4201db440, 0xc420212480, 0x8, 0x8, 0xc4201db440, 0xc420212480)
/opt/gopath/src/github.com/hyperledger/fabric/vendor/github.com/spf13/cobra/command.go:599 +0x234
github.com/hyperledger/fabric/vendor/github.com/spf13/cobra.(*Command).ExecuteC(0x12cfce0, 0xf, 0xc4201bd0e8, 0x7)
/opt/gopath/src/github.com/hyperledger/fabric/vendor/github.com/spf13/cobra/command.go:689 +0x367
github.com/hyperledger/fabric/vendor/github.com/spf13/cobra.(*Command).Execute(0x12cfce0, 0x28, 0xc4201bd0e8)
/opt/gopath/src/github.com/hyperledger/fabric/vendor/github.com/spf13/cobra/command.go:648 +0x2b
main.main()
/opt/gopath/src/github.com/hyperledger/fabric/peer/main.go:111 +0x52d
```
I am using master branch build from vagrant make
Has joined the channel.
Hi, did anyone encounter this problem? I followed the fabric/docs/gettingstarted.md
```
xyz@ubuntu:~/workspace/fabric_test$ GOPATH=$PWD node deploy.js
info: Returning a new winston logger with default configurations
info: [Chain.js]: Constructed Chain instance: name - fabric-client1, securityEnabled: true, TCert download batch size: 10, network mode: true
info: [Peer.js]: Peer.const - url: grpc://localhost:8051 options grpc.ssl_target_name_override=tlsca, grpc.default_authority=tlsca
info: [Peer.js]: Peer.const - url: grpc://localhost:8055 options grpc.ssl_target_name_override=tlsca, grpc.default_authority=tlsca
info: [Peer.js]: Peer.const - url: grpc://localhost:8056 options grpc.ssl_target_name_override=tlsca, grpc.default_authority=tlsca
info: [crypto_ecdsa_aes]: This class requires a KeyValueStore to save keys, no store was passed in, using the default store /home/hxy/.hfc-key-store
info: [Client.js]: Successfully loaded user "admin" from local key value store
[2017-03-06 02:14:43.711] [INFO] Helper - Successfully loaded member from persistence
[2017-03-06 02:14:43.714] [INFO] DEPLOY - Successfully obtained enrolled user to deploy the chaincode
[2017-03-06 02:14:43.715] [INFO] DEPLOY - Executing Deploy
[2017-03-06 02:14:43.724] [ERROR] DEPLOY - TypeError: chain.sendInstantiateProposal is not a function
at /home/xyz/workspace/fabric_test/deploy.js:79:16
```
and I have already successfully setup the fabric network. Just like:
```
xyz@ubuntu:~/workspace/fabric_test$ docker exec -it cli sh
# ls
anchorPeer.txt channel_test.sh log.txt myc1.block results.txt
# cat results.txt
SUCCESSFUL CHANNEL CREATION
SUCCESSFUL JOIN CHANNEL on PEER0
SUCCESSFUL JOIN CHANNEL on PEER1
SUCCESSFUL JOIN CHANNEL on PEER2
# ls -ltr myc1.block
-rw-r--r-- 1 root root 4627 Mar 6 10:06 myc1.block
```
Is this a version problem or someting else?
https://github.com/Pylons/waitress/
Dear Experts ,How can i provide temporary authentication to a participant to read a record during a time period . For example I want to provide access to a marklist of a job candidate to a potential employer for 1 day
@vu3mmg you can program it in your chaincode, something like
`if grantedParticipants[invoker].startTime > time.now() && grantedParticipants[invoker].endTime < time.now() return shim.Success(someData)` else return shimError("no access")`
thank you
is there any other way to use some timebased signed ceritficates , if the invoker sends a certificate and it is valid , then we give access . , or this could be a pail go code
Has joined the channel.
@Vadim grantedParticipants will we initialise during deployment phase ?
@vu3mmg I guess you can set up the CA which issues the certs in a way that they will have 1-2 days of lifetime, so if it's expired, the chaincode will fail
there should be a function in your chaincode which you call to grant temporaty access to somebody, this function will populate the grantedParticipants accordingly
ok
@gatakka perhaps your GOPATH is not set ?
@muralisr I am so stupid, I execute it in peer node, not in CLI node :) Thank you!
@gatakka if I had a dollar for everytime I did that ... :-)
@gatakka still, we should catch that gracefully and return error. Would you mind filing a JIRA bug against that ?
ok, i will. Can I login there using credentials from this chat?
not sure... but if get get an account from https://identity.linuxfoundation.org/ you shoukd be able to
done, https://jira.hyperledger.org/browse/FAB-2653. I hope that i describe it correctly, not very familiar with Jira and HL rules for bug reports.
@yong what do you get when you run `docker run -it --rm hyperledger/fabric-orderer orderer` ?
@gatakka I'd clarify your JIRA by stating the expected behavior as well as the issue. Currently it looks like you're saying that the error is a bug, which it is not. We simply want to make this error more graceful
@pd93 thank you, i will update it now
is it intentional that I can't pull the hyperledger/fabric-baseimage? 'docker pull hyperledger/fabric-baseimage' fails with manifest for "" not found, but e.g. 'docker pull hyperledger/fabric-peer' succeeds.
probably
just re-tag hyperledger/fabric-peer to whatever you need
yeah
thought it was odd I couldn't pull the base however
hey guys, what is the connection between sfhackfest docker images here https://hub.docker.com/u/sfhackfest22017 and those that are build from fabric and fabric-ca sources ?
i am new to the project and trying to put together few running containers with my own config
Hi guys, I'm facing this problem a few days and I can not to solve this issue, could some help me to fix this?
I have one Orderer, and one Peer instantiated.
Error: Error endorsing chaincode: rpc error: code = 2 desc = Failed to deserialize creator identity, err MSP DEFAULT is unknown
Sorry, I'll put all details....
Hi guys, I'm facing this problem a few days and I can not to solve this issue, could someone help me to fix this?
I have one Orderer, and one Peer instantiated.
Output of orderer: 2017-03-06 14:52:14.861 UTC [orderer/main] main -> INFO 120 Beginning to serve requests
Output of peer:
2017-03-06 15:11:08.781 UTC [msp] GetDefaultSigningIdentity -> DEBU 141b Obtaining default signing identity
2017-03-06 15:11:08.781 UTC [msp] Sign -> DEBU 141c Sign: plaintext: 18012A330A221A201FBBDFB6C7AE5BCA...85120D0888EEE083E2D2D4D41410F403
2017-03-06 15:11:08.781 UTC [msp] Sign -> DEBU 141d Sign: digest: E64AD3686BE599C8EC57749B0716BC0BE1FE3546D02F93EE790CF56DB0D6E80D
Output of chaincode: 14:53:43.379 [shim] DEBU : Received REGISTERED, ready for invocations
But when I execute this command:
CORE_PEER_ADDRESS=127.0.0.1:7051 peer chaincode instantiate -p github.com/hyperledger/fabric/examples/chaincode/go/eventsender -c '{"Function":"init", "Args":[]}' -o 127.0.0.1:5005 -n tarCCN -v 1 -C tarCC
The Error appears: Error endorsing chaincode: rpc error: code = 2 desc = Failed to deserialize creator identity, err MSP DEFAULT is unknown
I do not understand at all what does it means.
Could someone help-me?
Thanks a lot!!
@mrkiouak If you run `docker pull user/image` it will assume you are asking for the image tagged as *latest*
`hyperledger/fabric-baseimage` has no *latest* tag associated with it on docker-hub (mainly because of the different architectures). If you want to pull `hyperledger/fabric-baseimage` you must call it like so:
`docker pull hyperledger/fabric-baseimage:
@pd93 thanks
Hi @pd93, sorry to bother you, but could you help-me?
@tulioribeiro I'm afraid I don't know the answer to your question. Maybe @greg.haskins can help?
@pd93 thanks : )
@tulioribeiro i have seen this before. If you look into core.yaml you will see the MSP DEFAULT being defined. I have a feeling your peers are misconfigured.
[ ](https://chat.hyperledger.org/channel/fabric?msg=oBGQBHCug89cSBHvi) @cgrecu the images that were used for hackfest were captured after the fact in the "v1.0.0-preview" branch
ty @greg.haskins
[ ](https://chat.hyperledger.org/channel/fabric?msg=txWTSuG2kZMqiAA22) @mrkiouak Yes, this is by design
[ ](https://chat.hyperledger.org/channel/fabric?msg=GKppWxguKaymsFvS8) @pd93 I've seen that, but I do not know what the root cause is: I suspect perhaps a mismatch in keying material and/or config somewhere
At peer/core.yml what is a proper value for localMspId var?
In particular, the name of the local MSP ID of a peer needs to match the name of one of the MSPs in each of the channel that this peer is a member of.
What is the possible MSP's names?
Thanks @greg.haskins
@tulioribeiro will defer to @aso @jyellick but the simple answer is it defined by MSP definition associated with organizations in common/configtx/tool/configtx.yaml
Has joined the channel.
Thanks @muralisr I'll investigate configtx.yaml : )
Has joined the channel.
Having my own issue now. I've been playing with the e2e stuff and I'm getting this on `CHANNEL_NAME=mych docker-compose up`:
`Error creating configtx manager and handlers: Error unpacking configuration transaction: Error computing chain ID and sequence: Header not set:`
I've moved a few things around, but I'm not sure what is causing this? Has anyone seen the error before?
Ok I just tried running this from scratch with the latest fabric and got the same error :/
Ok I just tried running this from scratch with the latest fabric and got the same error :/
*-- edit --* Fixed this by rebuilding the docker images.. but would still love to know what caused the issue if anyone knows
Hello. I built fabric/peer with `go build main.go`, but when I launch it it doesn't get my env vars to be read.
```
CORE_PEER_ADDRESS=x.y.z.w:8051 ./main chaincode invoke -c testchainid -c '{"Args": ["init", "a", "100", "b", "200"]}' -n myccc
```
but I get :
```
2017-03-06 17:44:00.688 CET [msp] getPemMaterialFromDir -> INFO 001 Reading directory /home/dolanor/gohypvendor/src/github.com/hyperledger/fabric/msp/sampleconfig/cacerts
2017-03-06 17:44:00.688 CET [msp] getPemMaterialFromDir -> INFO 002 Inspecting file /home/dolanor/gohypvendor/src/github.com/hyperledger/fabric/msp/sampleconfig/cacerts/cacert.pem
2017-03-06 17:44:00.688 CET [msp] getPemMaterialFromDir -> INFO 003 Reading directory /home/dolanor/gohypvendor/src/github.com/hyperledger/fabric/msp/sampleconfig/signcerts
2017-03-06 17:44:00.688 CET [msp] getPemMaterialFromDir -> INFO 004 Inspecting file /home/dolanor/gohypvendor/src/github.com/hyperledger/fabric/msp/sampleconfig/signcerts/peer.pem
2017-03-06 17:44:00.688 CET [msp] getPemMaterialFromDir -> INFO 005 Reading directory /home/dolanor/gohypvendor/src/github.com/hyperledger/fabric/msp/sampleconfig/admincerts
2017-03-06 17:44:00.689 CET [msp] getPemMaterialFromDir -> INFO 006 Inspecting file /home/dolanor/gohypvendor/src/github.com/hyperledger/fabric/msp/sampleconfig/admincerts/admincert.pem
2017-03-06 17:44:00.689 CET [msp] getPemMaterialFromDir -> INFO 007 Reading directory /home/dolanor/gohypvendor/src/github.com/hyperledger/fabric/msp/sampleconfig/keystore
2017-03-06 17:44:00.689 CET [msp] getPemMaterialFromDir -> INFO 008 Inspecting file /home/dolanor/gohypvendor/src/github.com/hyperledger/fabric/msp/sampleconfig/keystore/key.pem
2017-03-06 17:44:00.689 CET [msp] NewBccspMsp -> INFO 009 Creating BCCSP-based MSP instance
2017-03-06 17:44:00.689 CET [peer] GetLocalMSP -> INFO 00a Created new local MSP
2017-03-06 17:44:00.689 CET [msp] Setup -> INFO 00b Setting up MSP instance DEFAULT
2017-03-06 17:44:00.689 CET [msp] newIdentity -> INFO 00c Creating identity instance for ID &{DEFAULT IDENTITY}
2017-03-06 17:44:00.689 CET [msp] newIdentity -> INFO 00d Creating identity instance for ID &{DEFAULT IDENTITY}
2017-03-06 17:44:00.690 CET [msp] newIdentity -> INFO 00e Creating identity instance for ID &{DEFAULT IDENTITY}
2017-03-06 17:44:00.713 CET [peer] GetManagerForChain -> INFO 00f Created new msp manager for chain testchainid
2017-03-06 17:44:00.713 CET [msp] Setup -> INFO 010 Setting up the MSP manager (1 msps)
2017-03-06 17:44:00.713 CET [msp] Setup -> INFO 011 Setting up MSP
2017-03-06 17:44:00.714 CET [msp] NewBccspMsp -> INFO 012 Creating BCCSP-based MSP instance
2017-03-06 17:44:00.714 CET [msp] Setup -> INFO 013 Setting up MSP instance DEFAULT
2017-03-06 17:44:00.714 CET [msp] newIdentity -> INFO 014 Creating identity instance for ID &{DEFAULT IDENTITY}
2017-03-06 17:44:00.714 CET [msp] newIdentity -> INFO 015 Creating identity instance for ID &{DEFAULT IDENTITY}
2017-03-06 17:44:00.714 CET [msp] newIdentity -> INFO 016 Creating identity instance for ID &{DEFAULT IDENTITY}
2017-03-06 17:44:00.714 CET [msp] Setup -> INFO 017 MSP manager setup complete, setup 1 msps
Error: Error getting broadcast client: Error connecting to 0.0.0.0:7050 due to grpc: timed out when dialing
```
Am I writing the CORE_PEER_ADDRESS wrong ?
To whom it may concern, I have opened a JIRA item to discuss the merits of changing Fabric's log output from os.Stderr to os.Stdout: https://jira.hyperledger.org/browse/FAB-2663. Based on the code review for a recent chaincode container logging change, I'm pretty sure at least @mastersingh24, @binhn, and @muralisr have some thoughts.
@dolanor a few things
1) `Error connecting to 0.0.0.0:7050 due to grpc: timed out when dialing` that refers to the orderers address and not CORE_PEER_ADDRESS
2) assuming you are on latest master, you will need a new param "-o
3) finally I don't build peer directly but do `make peer` in fabric/ director and run the peer from fabric/ folder
Has joined the channel.
Has joined the channel.
Hello guys/gals .. I have some clients that are trying to write a Fabric client using Go. There are only SDKs for JS, Java and Python. Does anyone know of a design document that would explain what gRPC calls they would have to make in go? Also if they don't use one of the SDKs supported, what are they missing (other than a more intuitive API).
@jorgedr: Worth having a look at this: https://github.com/securekey/fabric-sdk-go
@cgrecu I don't know that I saw your question answered as to what is the difference between docker images and what is in master now, or do I truly understand at what level of detail you are looking for. The docker images used at the hackfest were pulled out of Master at the end of January. There is a lot of code that has come in since then January into Masters... examples such as instead of deploy now, we now have install/instantiate where install puts chaincode code on the actual peer and instantiate is the first run transaction on a channel. Another feature that came in was ability to implement peer leader election within a channel gossip group to allow for multiple organizations within the network . We also are working on policies for endorsement. Some of these required protobuf changes, which are of course pretty substantial. In addition there is tools that got added such as configtx manager that allows you to bootstrap the network. A good place that I have been sending people is to go look at the CI that is running against the fabric that they were working to officially merge in - https://gerrit.hyperledger.org/r/#/c/6607/8
Thank you @kostas !
@greg.haskins I resolved,It's Makefile problem
@yong can you be more specific or file a CR with the fix?
@greg.haskins Sorry, I have something to deal with right now. Contact you later.
Has joined the channel.
May I know what is the Fabric-OS image that is required during instantiation of chain-code. Is CCENV image not sufficient enough to create a chain-code docker container? I did get to know this in the 4th March Fabric Images that are released and upon running E2E via Peer CLI approach.
How to set the block size?
@rahulhegde im not quite clear what you are asking
yes, ccenv should be sufficient to build either GOLANG or CAR chaincode
to be clear, there are no released images however
at least, not to my knowledge
this means, you have to build from source
but "make docker" should build everything you need
Has joined the channel.
Has joined the channel.
[ ](https://chat.hyperledger.org/channel/fabric?msg=WSiWhSMXzevfvLB3S) @greg.haskins
4th March Fabric Image is picked up from the fabric-ci channel. We did use E2E CLI that uses the new deployment model for install-instantiate-invoke-query process via Peer CLI command. Peer log pointed me to the missing fabric-baseos image and reference also points to https://github.com/hyperledger/fabric/blob/master/peer/core.yaml#L302.
May i know why is this image required now or is there a setup issue?
[ ](https://chat.hyperledger.org/channel/fabric?msg=WSiWhSMXzevfvLB3S) @greg.haskins
4th March Fabric Image is picked up from the fabric-ci channel. We did use E2E CLI https://github.com/hyperledger/fabric/tree/master/examples/e2e_cli that uses the new deployment model for install-instantiate-invoke-query process via Peer CLI command. Peer log pointed me to the missing fabric-baseos image and reference also points to https://github.com/hyperledger/fabric/blob/master/peer/core.yaml#L302.
May i know why is this image required now or is there a setup issue?
@greg.haskins build/image/ccenv/payload: gotools/build/gopath/bin/protoc-gen-go \
build/bin/chaintool \
build/goshim.tar.bz2
build/image/javaenv/payload: build/javashim.tar.bz2 \
build/protos.tar.bz2 \
settings.gradle
build/image/peer/payload: build/bin/peer \
peer/core.yaml \
build/msp-sampleconfig.tar.bz2 \
common/configtx/tool/configtx.yaml
build/image/orderer/payload: build/bin/orderer \
build/msp-sampleconfig.tar.bz2 \
orderer/orderer.yaml \
common/configtx/tool/configtx.yaml
build/image/buildenv/payload: build/gotools.tar.bz2 \
gotools/build/gopath/bin/protoc-gen-go
build/image/testenv/payload: build/bin/orderer \
orderer/orderer.yaml \
common/configtx/tool/configtx.yaml \
build/bin/peer \
peer/core.yaml \
build/msp-sampleconfig.tar.bz2 \
images/testenv/install-softhsm2.sh
build/image/zookeeper/payload: images/zookeeper/docker-entrypoint.sh
build/image/kafka/payload: images/kafka/docker-entrypoint.sh \
images/kafka/kafka-run-class.sh
build/image/couchdb/payload: images/couchdb/docker-entrypoint.sh \
images/couchdb/local.ini \
images/couchdb/vm.args
Makefile +189
@rahulhegde What image are you referring to?
@yong something doesnt smell right with that change
can you post as a diff, it will make it easier to understand whats changing
?
@rahulhegde roger, so IIUC you are saying there is a specific commit-id you are using from march 4th that was known to pass CI?
not that you are using an "image" per se, such as one from dockerhub
In docker-peer and docker-orderer, peer and orderer files are null. the files path is wrong by Make peer-docker
@yong I am always open to the idea that there could be a bug: however, what you describe seems improbably
@yong I am always open to the idea that there could be a bug: however, what you describe seems improbable
that is such a fundamental thing, no one's image would work but they all seem to work except yours
@greg.haskins sorry,my english is very bad
so Im guessing its something environmental
@yong do not take that as being defensive, i have no doubt you have a real issue, I just dont know if that could be the root cause or no one would be working ever
[ ](https://chat.hyperledger.org/channel/fabric?msg=PFya2Sd77EfbCAjzW) @greg.haskins Using it from docker-hub. But I was surprised with fabric-OS Image (what is it?) when I thought CCENV would be sufficient. so do you mean to say fabric-baseos image should have not been required?
@rahulhegde can you be specific about what you are using from dockerhub?
@greg.haskins me too.b
@greg.haskins
[ ](https://chat.hyperledger.org/channel/fabric?msg=WTPwwnM4coQp6AibF) @greg.haskins https://chat.hyperledger.org/channel/fabric-ci?msg=QoAi9v9EiHbBPBeGy
@rahulhegde ah, ok, so these are images published by @rameshthoomu
I wasnt involved in their creation, but I can tell you how its supposed to work architectually
the peer will take the yaml config and perform variable substituion
so for instance: https://github.com/hyperledger/fabric/blob/master/peer/core.yaml#L304
for `peer-x86_64:x86_64-0.7.0-snapshot-509d8ed`, it will try to load the matching ARCH/VERSION/BASEVERSION according to whats in that file
note the namespace
if @rameshthoomu left the core.yaml alone, its probably still pointing at hyperledger/ namespace
so, if I had to guess, his image is trying to load "hyperledger/fabric-ccenv-x86_64:x86_64-0.7.0-snapshot-509d8ed" from dockerhub, which of course does not exist
you can fix that by updating the config
I have them both
```
hyperledger/fabric-ccenv x86_64-0.7.0-snapshot-509d8ed 1635d9442585 2 days ago 1.294 GB
rameshthoomu/fabric-ccenv-x86_64 x86_64-0.7.0-snapshot-509d8ed 1635d9442585 2 days ago 1.294 GB
```
I have them both in my docker repo
```
hyperledger/fabric-ccenv x86_64-0.7.0-snapshot-509d8ed 1635d9442585 2 days ago 1.294 GB
rameshthoomu/fabric-ccenv-x86_64 x86_64-0.7.0-snapshot-509d8ed 1635d9442585 2 days ago 1.294 GB
```
note that you only would need to update the builder image, as the runtime image is not specific to his build
ah, ok, good, so that should work then
what are you seeing?
@greg.haskins these images are build with `make docker` and published without modifying any changes in config.. I have mentioned @rahulhegde to re-tag `rameshthoomu/fabric-ccenv-x86_64` to `hyperledger/fabric-ccenv:
@rahulhegde it's similar to sfhackfest setup..
@rameshthoomu thats what I figured...if you want to do this, just update the config to point to the alternate namespace
then it will likely work (though I would test it first)
I think change is required only here https://github.com/hyperledger/fabric/blob/master/peer/core.yaml#L300
do we need to change here as well https://github.com/hyperledger/fabric/blob/master/peer/core.yaml#L304?
no, just 300
would likely work in an envvar too,
yes..
CORE_CHAINCODE_BUILDER=rameshthoomu/fabric-ccenv:$(ARCH)-$(PROJECT_VERSION)
ok.. will be back in 30 mins..
Just went offline to retry this set once again and it tries to pull
2017-03-07 03:24:07.859 UTC [msp] Sign -> DEBU 007 Sign: digest: 868CDF51400EA9B4935DF1857D9F7ED17D1A0F616C3AD40DAD81BD643D3E4666
Error: Error endorsing chaincode: rpc error: code = 2 desc = Error starting container: Error while pulling image: Get https://index.docker.io/v1/repositories/hyperledger/fabric-baseos/images: dial tcp: lookup index.docker.io on [::1]:53: read udp [::1]:60010->[::1]:53: read: connection refused
Usage:
CORE_CHAINCODE_BUILDER=rameshthoomu/fabric-ccenv:$(ARCH)-$(PROJECT_VERSION)
Do i give this in Peer CLI - with values replaced?
@rahulhegde what do you mean by "went offline" ?
i assume you mean just to test
but I wanted to clarify if your environment has access to dockerhub?
haha - i just disconnected my network and rmi my fabric-os images to be absolute sure.
it would require access to dockerhub
at least for the first time
To show that it tries to pull fabric-os image and doesnt use the CCENV which is already present in the Docker Repository
yes, that is understood, sorry, i didnt know thats what you were asking
it will try to pull both the "builder" and "runtime" images from your config if they are not found
My bad too - if it was unclear - Np.
to build a chaincode
that is FAD
when you asked about it earlier, I assumed you mean "do I need to manage the pull myself"
to that, the answer is "no, it should get pulled automatically"
but it does need to get pulled on way or the other
but it does need to get pulled one way or the other
CORE_CHAINCODE_BUILDER=rameshthoomu/fabric-ccenv:$(ARCH)-$(PROJECT_VERSION) - do i need to set this param?
@rahulhegde ideally @rameshthoomu would set that for you if he is going to support those images
I will keep this with @rameshthoomu to try this out - Just pointed it to the forum.
you can either set that param, or manually retag the image
technically the images he published need either the config/envvar changed or instructions for manual tagging
Manually retag to - i already have it tagged - is this not good?
```
hyperledger/fabric-ccenv x86_64-0.7.0-snapshot-509d8ed 1635d9442585 2 days ago 1.294 GB
rameshthoomu/fabric-ccenv-x86_64 x86_64-0.7.0-snapshot-509d8ed 1635d9442585 2 days ago 1.294 GB
```
that looks correct to me
Still it doesnt work!!
afaict
what are you seeing?
(and keep in mind, this isn't released software ;)
```
2017-03-07 03:24:07.859 UTC [msp] Sign -> DEBU 007 Sign: digest: 868CDF51400EA9B4935DF1857D9F7ED17D1A0F616C3AD40DAD81BD643D3E4666
Error: Error endorsing chaincode: rpc error: code = 2 desc = Error starting container: Error while pulling image: Get https://index.docker.io/v1/repositories/hyperledger/fabric-baseos/images: dial tcp: lookup index.docker.io on [::1]:53: read udp [::1]:60010->[::1]:53: read: connection refused
Usage:
```
but i might know whats wrong if you describe it
you seem to be having connectivity issues to dockerhub
are you running the peer native or in docker?
I will keep it with @rameshthoomu to analyze and give us note - how to avoid using fabric-OS when CCENV is available.
[ ](https://chat.hyperledger.org/channel/fabric?msg=qpqtyQ2WcRS8s8KKh) @greg.haskins Docker.
[ ](https://chat.hyperledger.org/channel/fabric?msg=qpqtyQ2WcRS8s8KKh) @greg.haskins Docker - since these are the images provided by Ramesh.
@rahulhegde what do you mean by "how to avoid using fabric-OS when CCENV is available" ?
note that it is normal to need both ccenv and baseos
ccenv is used to compile the chaincode, and baseos is used to run the chaincode
is baseos == fabric-OS in your statement?
The question is why SF Hackfest images which had chain-code deployment worked only with CCENV and did not require fabric-baseos?
The question is why SF Hackfest images which had chain-code deployment worked or required only with CCENV and did not require fabric-baseos?
that was added recently
sf hackfest was from code snapshot in january, i believe...we have moved on since then
here is the commit for your reference: https://gerrit.hyperledger.org/r/#/c/6167/
So this brings a question do we still need CCENV now?
yes, ccenv has the compiler, etc
builder=ccenv, runtime=baseos
https://gerrit.hyperledger.org/r/#/c/6167/6/peer/core.yaml
it should be inconsequential to you: both are needed but both are managed for you too
(ccenv is based on baseos, too, fyi)
hello, i want to ask that in v1.0, we removed the "Query()" shim method and we only have invoke and init now, right?
So my question is, if a v1.0 invoke does not contain any state-changing operations, will Fabric write this tx proposal to ledger?
if i recall correctly, in v0.6, calling Query in shim should not write anything to ledger right?
@DannyWong there are two fundamental differences to a "query" in v1.0
1) if the chaincode were implemented as a true query, its proposal would only contain read-sets, no read-write-sets
[ ](https://chat.hyperledger.org/channel/fabric?msg=6WfqirK3BTAnaCGYm) @greg.haskins So is there a way to force during chaincode instantiation to use only CCENV as it contains the baseos?
2) the path through the SDK does not pass the proposal/endorsements to the call if you use the chain.query methods
so, in general, there is nothing to pass on for ordering/committing
now I suppose someone could call a query via the chain.invoke() path and then submit the read-sets to the committers, and I am not sure what effect that would have other than to be wasted time/space
but in general, you would have to try to do this
related: you could drop an endorsed rws proposal on the floor and its effectively a "query" too ;)
@rahulhegde yes, you can set your config to whatever you like
@rahulhegde just modify the "runtime" image to use whatever image:tag you would like
you could make them both "franken:beans" and it will dutifully invoke them
whether they exist and are functionally competent to perform the required tasks, I leave to you ;)
i can only vouch for the hyperledger/fabric-* branded releases we put out on dockerhub
@greg.haskins thanks for your explanation. I suspect this can be "detected" by "no-write-sets" too
@DannyWong me too, but I didnt want to assume this is how it works as I didnt work on that code
my guess is: this is what they do
ok, let me check the code too
thanks mate!
any time
thanks @greg.haskins
@rahulhegde yvw...this is probably understood, but note you are under no obligation to use the $() variables
you could literally hardcode a plain "image:tag", that will work
the variables are there for convenience for coupling the images to the peer version without needing to update the core.yaml, but you dont have to use the bindings
Has joined the channel.
Hello guys，when I use "configtxgen -profile TwoOrgs -outputBlock orderer.block" to generate orderer bootstrap block, I got an error like this: Error loading MSP configuration for org OrdererOrg: Could not load a valid ca certificate from directory examples/e2e_cli/crypto/orderer/localMspConfig/cacerts, err Could not read directory open examples/e2e_cli/crypto/orderer/localMspConfig/cacerts: no such file or directory, err examples/e2e_cli/crypto/orderer/localMspConfig/cacerts .But the path "examples/e2e_cli/crypto/orderer/localMspConfig/cacerts" is exist, anythig wrong?
Has joined the channel.
Has joined the channel.
Hi all, when I try to deploy my chaincode with cli, this error returns, the missing packages are used in my chaincode. What do I need to 'go get' the needed packages for the internal docker environement?
```
2017-03-07 07:32:29.203 UTC [dockercontroller] deployImage -> ERRO 260 Error building images: The command '/bin/sh -c go install phoenix/chaincode/identity && mv $GOPATH/bin/identity $GOPATH/bin/identity' returned a non-zero code: 1
2017-03-07 07:32:29.203 UTC [dockercontroller] deployImage -> ERRO 261 Image Output:
********************
Step 1/4 : FROM hyperledger/fabric-ccenv:x86_64-0.7.0-snapshot-c7b3fe0
---> 05dbf5bc5701
Step 2/4 : COPY src $GOPATH/src
---> ad10bd74dd92
Removing intermediate container fdd217e57dd7
Step 3/4 : WORKDIR $GOPATH
---> 2d5ab4c5e9b4
Removing intermediate container 34153d3db964
Step 4/4 : RUN go install phoenix/chaincode/identity && mv $GOPATH/bin/identity $GOPATH/bin/identity
---> Running in 0aa581bbe275
src/phoenix/chaincode/identity/main.go:11:2: cannot find package "github.com/golang/protobuf/proto" in any of:
/opt/go/src/github.com/golang/protobuf/proto (from $GOROOT)
/opt/gopath/src/github.com/golang/protobuf/proto (from $GOPATH)
src/phoenix/chaincode/identity/main.go:14:2: cannot find package "github.com/hyperledger/fabric/msp" in any of:
/opt/go/src/github.com/hyperledger/fabric/msp (from $GOROOT)
/opt/gopath/src/github.com/hyperledger/fabric/msp (from $GOPATH)
```
Hi all, when I try to deploy my chaincode with cli, this error returns, the missing packages are used in my chaincode. What do I need to do to 'go get' the needed packages for the internal docker environement?
```
2017-03-07 07:32:29.203 UTC [dockercontroller] deployImage -> ERRO 260 Error building images: The command '/bin/sh -c go install phoenix/chaincode/identity && mv $GOPATH/bin/identity $GOPATH/bin/identity' returned a non-zero code: 1
2017-03-07 07:32:29.203 UTC [dockercontroller] deployImage -> ERRO 261 Image Output:
********************
Step 1/4 : FROM hyperledger/fabric-ccenv:x86_64-0.7.0-snapshot-c7b3fe0
---> 05dbf5bc5701
Step 2/4 : COPY src $GOPATH/src
---> ad10bd74dd92
Removing intermediate container fdd217e57dd7
Step 3/4 : WORKDIR $GOPATH
---> 2d5ab4c5e9b4
Removing intermediate container 34153d3db964
Step 4/4 : RUN go install phoenix/chaincode/identity && mv $GOPATH/bin/identity $GOPATH/bin/identity
---> Running in 0aa581bbe275
src/phoenix/chaincode/identity/main.go:11:2: cannot find package "github.com/golang/protobuf/proto" in any of:
/opt/go/src/github.com/golang/protobuf/proto (from $GOROOT)
/opt/gopath/src/github.com/golang/protobuf/proto (from $GOPATH)
src/phoenix/chaincode/identity/main.go:14:2: cannot find package "github.com/hyperledger/fabric/msp" in any of:
/opt/go/src/github.com/hyperledger/fabric/msp (from $GOROOT)
/opt/gopath/src/github.com/hyperledger/fabric/msp (from $GOPATH)
```
@levinkwong put them to the vendor folder https://blog.gopheracademy.com/advent-2015/vendor-folder/
@Vadim Thanks! It is like the libraries in JAVA? But why the sample codes can import packages without these?
because they are in gopath of the container, apparently
this is more like node_modules in npm
So what packages will be available in the container? Can I config it?
don't think so, it uses some standard container, so you would have to create your own one
much easier is just to use the vendor folder
Is this the general golang practise or specified to fabric (since we need to fork a container to run those go code)
Is this the general golang practise or specified to fabric (since we need to fork a container to run those go code)?
it's a general golang practice (did you read a link I posted?)
Not quite understand the part explaining the pain points. I will google more and learn.
And thanks for your help!!
is there anyone who can give some information regarding how the transactions inside the block are encrypted to prevent from being viewed by other parties
it's not encrypted
you can use the channel mechanism to prevent others outside of channel seeing the transactions, but the ordering peer will still see everything
if you need full privacy, you should encrypt the data in the application level before sending it to the fabric
if you need full privacy, you should encrypt the data in the application layer before sending it to the fabric
it limits the use cases, fabric should handle this in the later version
@Vadim
As I remember the spec indicates we can encrypt the transaction, and have something like :
https://github.com/hyperledger/fabric/blob/v0.6/docs/images/sec-usrconf-deploy.png
Is that not yet developed or the whole concept not valid anymore in 1.0?
@levinkwong I cannot say anything about this as I'm not in the dev team. However, this scheme does not solve the issue when you want to hide the information from the other participants of the same chain. It only hides it from the rest of the world.
How so? Only users in [contract users] are provided with private key to decrypt the payload
someone have no access to these transactions can not view them, I get this message from the doc
is it in v1?
@levinkwong as far as I know, this key will have to be shared with orderer, because he needs to check the read/write sets of the endorsed transactions to avoid parallel access to the same key and invalidate the transactions correspondingly
@levinkwong as far as I know, this key will have to be shared with orderer, because he needs to check the read/write sets of the endorsed transactions to avoid parallel access to the same key/value and invalidate the transactions correspondingly
Has joined the channel.
can anyone comment on the security risks associated with running a stand-alone CouchDB instance
is it possible to lock down access to the DB engine so that read/write access can happen ONLY via the blockchain mechanisms?
my concern is someone hacking into a node and then hacing into the CouchDB server and reading the entire chain state
@MartinMateev if somebody hacked into a node, then he can just dump the CouchDB database file and read it with e.g. a hex editor, thus going around the database access mechanisms. Unless the data inside is encrypted and the key is not present on that node, of course.
so you'd better protect your instance against hacking
@Vadim thanks for the feedback - is it possible to encrypt the data stored in the CouchDB instance ?
so that even if someone gets physical access to the instance, dumping the database will not result in data exposure
well, I'm not really familiar with CouchDB, but if you encrypt it, where do you store the key?
you can also encrypt the data before you send it to the blockchain
you can also encrypt the data before you send it to the blockchain and it gets written to the storage
but then you need to protect your other nodes that have the key to decrypt ot
but then you need to protect your other nodes that have the key to decrypt it
so unless you use an HSM, there is no ultimate solution
yeah - in my case HSM will be used
and I know you can encrypt transaction payload
but the payload gets decrypted before getting written in CouchDB ...correct ?
well, if you write to blockchain encrypted data, then it stays encrypted
as far as I know, currently nothing is encrypted anyway
I remember that there's planned encyrption for transaction payload and transaction attributes
I can cite this FAQ: https://github.com/hyperledger/fabric/blob/0c07573430f11c50dae713a0add596f3e9959633/docs/source/FAQ/architecture_FAQ.rst
`Q. Even if there are multiple private chains, the Orderers can see all the transactions, which means they are the single point of trust. This is not acceptable in some use cases. Are there any plans to make orderers decentralized?
A. This is generally true. The orderers do receive a higher degree of trust, and they must necessarily see all channels and their membership. I would point out, however, that the orderers only see the information which passes through them. Certain pieces of the transaction, such as the proposal, can be configured not to go through ordering. Similarly, any data which is referenced by hash or encrypted would be opaque to the orderers. Clients can hash/encrypt the data that they submit to ledger.`
```Q. Even if there are multiple private chains, the Orderers can see all the transactions, which means they are the single point of trust. This is not acceptable in some use cases. Are there any plans to make orderers decentralized?
A. This is generally true. The orderers do receive a higher degree of trust, and they must necessarily see all channels and their membership. I would point out, however, that the orderers only see the information which passes through them. Certain pieces of the transaction, such as the proposal, can be configured not to go through ordering. Similarly, any data which is referenced by hash or encrypted would be opaque to the orderers. Clients can hash/encrypt the data that they submit to ledger.```
thanks
and btw what's the meaning of the 'channel' concept - this is a new thing for me
it's like a sub-chain, which isolates the chaincode and its state in one channel from other channels
but as I pointed out, orderers see all data in all channels
so if you write encrypted data into CouchDB, then how do you query for it ?
you query the encrypted data and then decrypt it in the application level or even in the chaincode through which you query it. But you need to pass it a key, so probably you want that this chaincode is running somewhere next to your application.
not sure this is a "best practise", but this is what I could come up so far
not sure this is a "best practicee", but this is what I could come up so far
not sure this is a "best practice", but this is what I could come up so far
this, however, limits the search possibilities of the CouchDB, because it only sees the encrypted data
also a relevant quote from the same FAQ:
```
Q. Is encryption of transaction and ledger removed from V1?
A. V1 does not have encryption at fabric level. The data at rest can be encrypted via file system encryption, and the data in transit is encrypted via TLS. In v1 it is possible to set up private channels so that you can share a ledger (and corresponding transactions) with the subset of network participants that are allowed to see the data. The submitting party now has full control - they can encrypt the complete set of data before submitting to ledger, encrypt sensitive portions only, or not encrypt if complete transparency/queryability is the goal.
```
well in my view, the transaction protocol should be extended to support meta information which could be indexed
so the data model resides on the actual transactions
what do you mean?
the chaincode shim has support for indexes
right now the state is saved outside of the transactions (i.e LevelDB, CouchDB, etc...)
is this bad?
it's not bad and I'm sure it has its pratical uses
but think of the Bitcoin protocol
well there is no state as such
right
it is recalculated each time from UTXO
the tokens are part of the protocl itself
and it's only account balances and nothing else
right and this is why most people would like to use a blockchain
really?
I'm not sure how this is an advantage
well I don't want to store my entire business logic on the blockchain
I only want to store transactions that tranfer value
hmm, I thought it was the whole point of the smart contracts
smart contracts are a misnomer
there's no such thing as a smart contract
it's not smart and it's not a contract
it's a stored procedure
: )
it's just a name
call it chaincode
or whatever, does not change what it does
so it Bitcoin you can store only the data, but not BL. Smart contracts enable you to store the logic too, thus defining a set of rules that nobody can break
it sounds great in theory
but history and ethereum shows us that it's a pretty bad idea in practice
I suspected you will come up with that dao thing ;)
so to keep the discussion short, I'd say that blockchains are about consensus and what happened with ethereum was also a result of consensus (miners migrating to the patched software) . But this was not a consensus enforced by PoW, rather, majority agreed. THis is pure democracy. (I also don't approve of what happened, btw)
so to keep the discussion short, I'd say that blockchains are about consensus and what happened with ethereum was also a result of consensus (miners migrating to the patched software) . But this was not a consensus enforced by PoW, rather, the majority agreed. THis is pure democracy. (I also don't approve of what happened, btw)
hi all, somebody have problem with start orderer on last commit in master branch?
'''peer-04 | 2017-03-07 09:35:50.608 UTC [gossip/service] InitializeChannel -> WARN 004 Delivery client is down won't be able to pull blocks for chain testchainid
peer-04 | create chain [testchainid]2017-03-07 09:35:50.613 UTC [peer] Initialize -> WARN 005 Failed to load ledger testchainid(Ledger already opened)'''
hi all, somebody have problem with start orderer on last commit in master branch?
'peer-04 | 2017-03-07 09:35:50.608 UTC [gossip/service] InitializeChannel -> WARN 004 Delivery client is down won't be able to pull blocks for chain testchainid
peer-04 | create chain [testchainid]2017-03-07 09:35:50.613 UTC [peer] Initialize -> WARN 005 Failed to load ledger testchainid(Ledger already opened)'
hi all, somebody have problem with start orderer on last commit in master branch?
peer-04 | 2017-03-07 09:35:50.608 UTC [gossip/service] InitializeChannel -> WARN 004 Delivery client is down won't be able to pull blocks for chain testchainid
peer-04 | create chain [testchainid]2017-03-07 09:35:50.613 UTC [peer] Initialize -> WARN 005 Failed to load ledger testchainid(Ledger already opened)
hi all, somebody have problem with start orderer on last commit in master branch?
peer-04 | 2017-03-07 09:35:50.608 UTC [gossip/service] InitializeChannel -> WARN 004 Delivery client is down won't be able to pull blocks for chain testchainid
peer-04 | create chain [testchainid]2017-03-07 09:35:50.613 UTC [peer] Initialize -> WARN 005 Failed to load ledger testchainid(Ledger already opened)
@yury have you tried to clean /var/hyperledger/*?
in this directory I haven't anything. Maybe it's I have another path... Can you tell me environment variable
that I don't knpw
that I don't know
[07/03/2017, 12:26:38] Yury: peer-02 | 2017-03-07 09:22:49.485 UTC [deliveryClient] NewDeliverService -> ERRO 002 Cannot dial to orderer:7050, because of grpc: timed out when dialing
peer-02 | 2017-03-07 09:22:49.485 UTC [gossip/service] InitializeChannel -> WARN 003 Cannot create delivery client, due to Wasn't able to connect to any of ordering service endpoints [orderer:7050]
[07/03/2017, 12:27:47] Yury: orderer | 2017/03/07 09:22:50 grpc: Server.Serve failed to create ServerTransport: connection error: desc = "transport: write tcp 172.25.0.2:7050->172.25.0.7:59748: write: broken pipe
peer-02 | 2017-03-07 09:22:49.485 UTC [deliveryClient] NewDeliverService -> ERRO 002 Cannot dial to orderer:7050, because of grpc: timed out when dialing
peer-02 | 2017-03-07 09:22:49.485 UTC [gossip/service] InitializeChannel -> WARN 003 Cannot create delivery client, due to Wasn't able to connect to any of ordering service endpoints [orderer:7050]
orderer | 2017/03/07 09:22:50 grpc: Server.Serve failed to create ServerTransport: connection error: desc = "transport: write tcp 172.25.0.2:7050->172.25.0.7:59748: write: broken pipe
seems like peer cannot reach the orderer
seems like the peer cannot reach the orderer
you are right
Has joined the channel.
Has joined the channel.
Hi I'm following these instructions for setting up fabric
http://hyperledger-fabric.readthedocs.io/en/latest/asset_setup.html
but when I run deploy.js
info: Returning a new winston logger with default configurations
info: [Peer.js]: Peer.const - url: grpc://localhost:8051 options grpc.ssl_target_name_override=tlsca, grpc.default_authority=tlsca
info: [Peer.js]: Peer.const - url: grpc://localhost:8055 options grpc.ssl_target_name_override=tlsca, grpc.default_authority=tlsca
info: [Peer.js]: Peer.const - url: grpc://localhost:8056 options grpc.ssl_target_name_override=tlsca, grpc.default_authority=tlsca
info: [Client.js]: Failed to load user "admin" from local key value store
info: [FabricCAClientImpl.js]: Successfully constructed Fabric CA service client: endpoint - {"protocol":"http","hostname":"localhost","port":8054}
info: [crypto_ecdsa_aes]: This class requires a CryptoKeyStore to save keys, using the store: {"opts":{"path":"/home/ubuntu/.hfc-key-store"}}
It stuck on this
I'm able to use the docker cli
but not with node sdk
Do I need to add keyvalue store? If yes how
Failed to load user "admin" from local key value store
How do I store admin user ?
Can anyone help me?
please
Has joined the channel.
Hii Everyone! I am new to hyperledger. Regarding installation part I am not getting what should be there in host and port part of POST url: http://
Has joined the channel.
@mraikwar what version of HL you are using?
@gatakka version 0.6
version 0.6 is not supported any more, it was just a POC. Strongly recommend you to use v1. A lot of concepts are different. 0.6 is no more!
@gatakka is there a well documentation for setting up HL v1 and running chaincode into it.
https://hyperledger-fabric.readthedocs.io/en/latest/
it is not perfect, it is constantly updated, but with couple of questions you will be able to manage it
just install vagrant from devenv folder, ssh to it and execute make all. This will create all docker containers
@gatakka Thanks a lot. BTW on which platform it's better to setup HL-windows or Linux. How to install vagrant from devenv folder. Will the devenv folder be created after installing HL?
if you use vagrant underling OS makes no difference. Checkout fabric source code from gerrit or github, there is a devenv folder that contains all scripts to provision Vagrant virtual machine. Then ssh to Vagrant and execute make all
@mraikwar basically, you just do something like
```
cd
@Vadim @gatakka Got it. Thanks
Hi I'm trying to compile HL v1.0.0.preview
I've got several "go context" error with go 1.6.x
with go 1.7 & 1.8 I fail on :
```
# github.com/hyperledger/fabric/vendor/github.com/miekg/pkcs11
vendor/github.com/miekg/pkcs11/pkcs11.go:29:18: fatal error: ltdl.h: No such file or directory
compilation terminated.
```
do you have an idea ?
@enidz sudo apt-get install libltdl-dev
THX ! ^^'
Has joined the channel.
[ ](https://chat.hyperledger.org/channel/fabric?msg=mGKvdBMpaBfspDpkm) @weeds thank you
Hello. I want to try out making transactions, making stress tests and writing chaincode. On the docs, I found "getting setup" and "setting up development enviroment". Am I correct in thinking that the dev environment purpose is to write Hyperledger code in Go, contribute to the project, fix bugs etc. and that the "getting setup" is where I want to be?
Will I be able to do what I want to do - setting up any number of peers/endorsers/validators/issuing various certificates without setting up a dev environment?
@ercw for version 1, you should be able to set up any number of peers, endorsers, validators and issue out various certificates. I'm wondering if it might be useful to look at what people are doing for testing version 1.0- they are on the fabric-quality channel as they already have a lot of tools (including for stress test/bootstrapping network,etc..) You can write Hyperledger code in Go, Java, or Node.js at this point in time- there are SDK's for Java/Node.js. There is also work being done on Python. Also, there is a team that has developed fabric-composer that is moving over to version 1.0 as well that allows you to write at a higher level abstraction to make it easier. The tool as I saw it in the last Hackfest allows you to model assets, participants, transactions and done utilizing javascript (they are on the fabric-composer channel)
Thank you @weeds. I don't think I am using version 1 as I just followed the guide on https://hyperledger-fabric.readthedocs.io/en/latest/asset_setup.html#
It looks like this downloads some example code from sfhackfest and not really where I should be looking if I want to try out v1,0 functionality
Thank you @weeds. I don't think I am using version 1 as I just followed the guide on https://hyperledger-fabric.readthedocs.io/en/latest/asset_setup.html#
It looks like this downloads some example code from sfhackfest and not really where I should be looking if I want to try out v1.0 functionality
Has joined the channel.
Has joined the channel.
@muralisr
For v1.0 - 4th March Fabric-CI Images
I see a chain-code instantiated with the same chain-code name (-n) on different chain-ids (-C) that is joined by the same peer is processed/handled using the same docker container - is this the expected behavior in terms of scalability and maintainance?
@muralisr
For v1.0 - 4th March Fabric-CI Images
I see a chain-code instantiated with the same chain-code name (-n) on different chain-ids (-C) that is joined by the same peer is processed/handled using the same docker container - is this the expected behavior?
@rahulhegde yes, the ledger context is switched
if you want a different container, just install the same chaincode with a different name
this generalizes and accomodates more deployment options
Is there a cause for scalability & maintenance? Haven't understood ` this generalizes and accomodates more deployment options `
Is there a cause for scalability (it's the same container serving for multiple chain-code running on multiple chain-id, we have somewhat a similar case for deployment) & maintenance (logger-prints, etc)?
Haven't understood ` this generalizes and accomodates more deployment options `
Has joined the channel.
Has joined the channel.
this is weird, cd $GOPATH/src/github.com/hyperledger/fabric
make peer, then shows this error:
make peer
Building docker base-image
BUILD-CACHE: exists!
usage: mktemp [-d] [-q] [-t prefix] [-u] template ...
mktemp [-d] [-q] [-u] -t prefix
make: *** [build/image/base/.dummy] Error 1
I ran today queue-2-query interface test using example02, example04 on Fabric-CI Images - 4th March. I thing i noticed and as per https://github.com/hyperledger/fabric/blob/master/core/chaincode/shim/interfaces.go#L57 - Invoke operation containing PutState will not be recorded to the ledger (irrespective if chaincode is running on the same or different channel of the same peer). And this is what i see as expected.
However looking at the go test written for example04 at https://github.com/hyperledger/fabric/blob/master/examples/chaincode/go/chaincode_example04/chaincode_example04_test.go#L109, the invoke operation containing PutState (records 10 unit asset transfer from A -> B) gets registered in MockStub implementation. This is defect and need to be handled.
I ran today queue-2-query interface test using example02, example04 on Fabric-CI Images - 4th March. I thing i noticed and as per https://github.com/hyperledger/fabric/blob/master/core/chaincode/shim/interfaces.go#L57 - Invoke operation containing PutState will not be recorded to the ledger (irrespective if chaincode is running on the same or different channel of the same peer). And this is what i see as expected.
However looking at the go test written for example04 at https://github.com/hyperledger/fabric/blob/master/examples/chaincode/go/chaincode_example04/chaincode_example04_test.go#L109, the invoke operation containing PutState (records 10 unit asset transfer from A => B) gets registered in MockStub implementation. This is defect and need to be handled.
I ran today queue-2-query interface test using example02, example04 on Fabric-CI Images - 4th March. I thing i noticed and as per https://github.com/hyperledger/fabric/blob/master/core/chaincode/shim/interfaces.go#L57 - Invoke operation containing PutState will not be recorded to the ledger (irrespective if chaincode is running on the same or different channel of the same peer). And this is what i see as expected.
However looking at the go test written for example04 at https://github.com/hyperledger/fabric/blob/master/examples/chaincode/go/chaincode_example04/chaincode_example04_test.go#L109, the invoke operation containing PutState (records 10 unit asset transfer from A -> B ) gets registered in MockStub implementation. This is defect and need to be handled.
I ran today chaincode-2-chaincode query interface test using example02, example04 on Fabric-CI Images - 4th March. I thing i noticed and as per https://github.com/hyperledger/fabric/blob/master/core/chaincode/shim/interfaces.go#L57 - Invoke operation containing PutState will not be recorded to the ledger (irrespective if chaincode is running on the same or different channel of the same peer). And this is what i see as expected.
However looking at the go test written for example04 at https://github.com/hyperledger/fabric/blob/master/examples/chaincode/go/chaincode_example04/chaincode_example04_test.go#L109, the invoke operation containing PutState (records 10 unit asset transfer from A -> B ) gets registered in MockStub implementation. This is defect and need to be handled.
I ran chaincode-2-chaincode query interface test using example02, example04 on Fabric-CI Images - 4th March. I thing i noticed and as per https://github.com/hyperledger/fabric/blob/master/core/chaincode/shim/interfaces.go#L57 - Invoke operation containing PutState will not be recorded to the ledger (irrespective if chaincode is running on the same or different channel of the same peer). And this is what i see as expected.
However looking at the go test written for example04 at https://github.com/hyperledger/fabric/blob/master/examples/chaincode/go/chaincode_example04/chaincode_example04_test.go#L109, the invoke operation containing PutState (records 10 unit asset transfer from A -> B ) gets registered in MockStub implementation. This is defect and need to be handled.
Hi all, I tried to deploy some chaincode into fabric (built from the getting setup guide) and get this error :
(I just want to hijack the network to test some chaincode I wrote)
```
Step 4/4 : RUN go install phoenix/chaincode/identity && mv $GOPATH/bin/identity $GOPATH/bin/identity
---> Running in 26d3d05ac35d
mv: cannot stat '/opt/gopath/bin/identity': No such file or directory
```
I can deploy the predefined chaincode from the guide but failed to deploy mine, as the error says I don't have the chaincode under the $GOPATH/bin directory. I would like to ask:
1) Why would I need that?
2) I find the predefined chaincode from the guide also don't have one, why I can deploy that ....
I have figured my problem ##Delete the problem
Has joined the channel.
Has joined the channel.
Has joined the channel.
Appreciate if anyone can help
Has joined the channel.
root@a3668733dca1:/opt/gopath/src/github.com/hyperledger/fabric/examples/chaincode/go/chaincode_example02# peer chaincode install -n test_cc -p /opt/gopath/src/github.com/hyperledger/fabric/examples/chaincode/go/chaincode_example02 -c '{"Args":["init","a","100","b","200"]}'
Error: Must supply value for chaincode path and version parameters.
how to resolve?
hello, is anybody known the following error?
root@peer0:/go/src/github.com/hyperledger/fabric# peer chaincode install -n test_cc -p github.com/hyperledger/fabric/examples/chaincode/go/chaincode_example02 -v 1.0
Error: Error getting broadcast client: Ordering service endpoint is not valid or missing
fabric version 1.0
@yong as the note mentioned,you must add version
just like :
you need to provide the ordererer port -o orderer:7050
peer chaincode install -n test_cc -p github.com/hyperledger/fabric/examples/chaincode/go/chaincode_example02 -v 1.0
@xiangyw Ok,Thanks!
@Hangyu where i should config this
i use docker-compose to start
and CORE_PEER_COMMITTER_LEDGER_ORDERER=orderer:7050 already config-ed in peer.yaml
but you need to add *-o orderer:7050* to the command as *peer chaincode install -n test_cc -p github.com/hyperledger/fabric/examples/chaincode/go/chaincode_example02 -v 1.0 -o orderer:7050*
ths very much, i try
this example might help https://github.com/hyperledger/fabric/blob/master/examples/e2e_cli/end-to-end.rst
@Hangyu environment:
- ORDERER_GENERAL_LEDGERTYPE=ram
- ORDERER_GENERAL_BATCHTIMEOUT=10s
- ORDERER_GENERAL_BATCHSIZE_MAXMESSAGECOUNT=10
- ORDERER_GENERAL_MAXWINDOWSIZE=1000
- ORDERER_GENERAL_ORDERERTYPE=solo
- ORDERER_GENERAL_LISTENADDRESS=0.0.0.0
- ORDERER_GENERAL_LISTENPORT=5005
- ORDERER_RAMLEDGER_HISTORY_SIZE=100
- ORDERER_GENERAL_LOCALMSPDIR=/etc/hyperledger/fabric/msp/sampleconfig
working_dir: /opt/gopath/src/github.com/hyperledger/fabric/orderer
command: orderer
ports:
- 5005:5005
networks:
- bridge
ORDERER_GENERAL_LISTENPORT and ports: , different?
Yes, in your case, different, -o orderer:5005 should be added to that command
ORDERER_GENERAL_LISTENPORT and ports change to 7050?
that doesn't matter, in your case, because it was set to 5005 in the docker-compose yaml, it should be 5005. It is 7050 by defualt
@Hangyu it works, how about the next error when instantiate :Error: Error endorsing chaincode: rpc error: code = 2 desc = Error starting container: Post http://unix.sock/containers/create?name=dev-peer0-test_cc-1.0: dial unix /var/run/docker.sock: connect: permission denied
i use root use testing and systemctl stared docker
should i create docker user for docker?
sorry, I never ran into that error
@xiangyw you don't need root to run fabric, also check if the user which runs fabric is in the "docker" group
@Vadim Docker version 1.12.5 is ok for fabric 1.0?
yes
when i tested 0.6 i start docker by sudo docker daemon --icc=true --api-cors-header=* -H tcp://0.0.0.0:2375 -H unix:///var/run/docker.sock ,but now i got error---->exec: "dockerd": executable file not found in $PATH, so i use --->sudo systemctl restart docker
this may cause permission error?
you don't need sudo
@Vadim
Hi Vadim, do you know how a peer setup a LocalMSP?
I tried to understand the MSP now but don't know why each peer local MSP have other Peers' certificates (I inspect into the getting start/heckfest project setting)
@xiangyw I mean, you don't need sudo to run containers, for daemon you need sudo
@levinkwong I don't think each peer needs other peer certificates
probably, it was just easier to provision it like that
so for all four folders under a peer (admincerts, cacerts, keystore, signcerts) all they need is its own certificates?
if you are referring to the e2e example, then there each peer is configured with its own MSP config, see it here: https://github.com/hyperledger/fabric/blob/master/examples/e2e_cli/scripts/script.sh#L36
and each MSP config includes those 4 folders
oh! Make much more sense! But how about the client(SDK), since they need to verify the proposal response, they must have all Peers (assume all peers are endorser) certificate.
they must have the CA certificates only
but how they retrieve all peers' CA cert ... everytime I add new peer to the network I need to update it?
well the CA is configured once
CA issues peer certs
nodes trust peer certs if they trust the CA
I'm also not sure whether SDKs are checking the signatures
I see, if a new organization (using its own CA) joins the network then we need to add that cert to client, right?
But it would be rare case
guys, is there a blockchain explorer module - that I can plug-n-play to monitor a blockchain
see blocks, transactions, etc...
Yes indeed
@MartinMateev You may find the blockchain-explorer channel
And the project : https://github.com/hyperledger/blockchain-explorer
@levinkwong yes, the root of trust is in the genesis block (or channel config block, not sure), so if a new org joins, a reconfiguration transaction needs to add a new root of trust
But only support v0.6 (as I remember)
@levinkwong thanks!
@Vadim Thanks so much!
Has joined the channel.
Anyone know about AnchorPeer? I cannot find document for it to study
where you got this noun, i only know endorse peer and commit peer
Has joined the channel.
Join channel command? (or create) forgot
in the fabric project.... channel
channel.go
under the gossip modue
module*
who can help me out from this--->
@levinkwong it's like a gateway node in a peer cluster, they route the gossip messages to another peers in a cluster. So your organization can decide to run multiple nodes for resilience, one of these nodes will be an anchor peer.
@xiangyw did you check whether the user which runs fabric belongs to the docker group?
so there will be some kind of "leader selection" within that cluster through "gossip"?
yes ,already add user to docker group
@DannyWong no, the anchor peer is hardcoded in the config transaction: https://github.com/hyperledger/fabric/blob/master/common/configtx/tool/configtx.yaml#L80
@xiangyw you might need to logoff and login again
@Vadim Oh, i thought it's a post-v1 feature! https://docs.google.com/document/d/157AvKxVRqgeaCTSpN86ICa5x-XihZ67bOrNMc5xLvEU/edit#
it should be related to the "organization.go" in the fabric go now
let me look deeper today later, thanks a lot @Vadim
you're welcome
Has joined the channel.
Hi, Can you allow peers to join a channel one a chaincode is deployed?
*once
@talauliker.shreya I'd say yes, as long as they belong to one of organizations in the channel
you can probably modify the e2e example to test it
Suppose we initially have peer1 , peer2 that are part of channel myc1. At a later point in time can i add peer3 to myc1 even if it wasnt originally in the myc1 channel? If so, how does the newly added peer i.e. peer3 sync its blocks with others?
@talauliker.shreya it just syncs the blocks, are you interested in the protocol details?
there is an example, e2e, which has very similar use case. But there all peers join the channel before chaincode in instantiated. So if you want to try, you can modify the script https://github.com/hyperledger/fabric/blob/master/examples/e2e_cli/scripts/script.sh in a way, that one peer joins the channel after the chaincode instantiation and invoking
Has joined the channel.
[ ](https://chat.hyperledger.org/channel/fabric?msg=XXN3LNJgqbigeHHXT) @Vadim
[ ](https://chat.hyperledger.org/channel/fabric? msg=XXN3LNJgqbigeHHXT) @Vadim I'm interested in it too. Do you mean even peer3 was not included during the channel initialization, it still could be added to scale the channel? Thanks
@Ying this is what I would expect. You can also try it and confirm it yourself following my suggestion above.
okay.. ill try it.. Thanks @Vadim
[ ](https://chat.hyperledger.org/channel/fabric?msg=GDAeQFeaQghPXpKBa) @Vadim thanks. Then another thing, how do you feel about the version of peer3? Is it a must that peer3 has the same version as peer1&2?
version of what?
Fabric
well so far it's only v1 and v0.6 versions, so it clearly won't work with v0.6, because the protocols are too different. As longs as there are no breaking changes in the protocol, it should work even if the versions are not exactly the same.
[ ](https://chat.hyperledger.org/channel/fabric?msg=nRXMyrb6Xz6iE6xt3) @Vadim is there any roadmap? 2017Q3?
I cannot answer this question.
I cannot answer this question (not in the dev team).
:slight_smile: Lot of thanks
Has joined the channel.
Hi! I am following https://github.com/hyperledger/fabric/blob/master/docs/source/channel-setup.rst . I am using vagrant, but while creating channel I am getting error : "Ordering service endpoint is not valid or missing"
is orderer running?
Yes orderer is running
`peer chaincode query -o orderer:7050 -C mych -n mycc -c '{"Args":["query"]}'`
keeps giving me `Error endorsing query: rpc error: code = 2 desc = Unknown invoke function: query`
I'm including all the correct env variables at the start of the command. (excluding here for simplicity).
Should I be calling query another way?
@pd93 which chaincode are you running?
it does not contain the "query" function, as the message says
I'm running my own chaincode, I think I may have the layout for it slightly wrong
I was my impression that there should be Invoke(), Init() and Query() methods
there is no Query method anymore, it's all handled by the Invoke
Ahhh ok, that makes sense. Thank you. Must have skipped that part of the upgrade :P
Has joined the channel.
@pd93
```
```
@pd93
```
func (t *MyChaincode) Invoke(stub shim.ChaincodeStubInterface) pb.Response {
function, args := stub.GetFunctionAndParameters()
switch function {
case "query":
return shim.Success("some results")
// ...
}
return shim.Error("Incorrect function name.")
}
```
should be in your case for the request you submit
should be in your case for the query you are trying to make
Ok cool, so what is the difference between the cli commands `peer chaincode query` and `peer chaincode invoke` ?
query does not expect state changes, so use it to read the state
Ok, so it's permission based. Presumably you could theoretically use invoke to do everything then? It's just obviously not good practise
@pd93 I guess you can use invoke to only query, never tried that
it could be that it will be adapted in the future to make it consistent with the chaincode
It feels a little clunky having two methods (query and invoke) both go to one function (invoke) in the chaincode.
Maybe invoke with a read only flag would be less confusing?
maybe, it's up to developers to decide
personally, for me query is not confusing
I agree having a query command isn't confusing in it's own right. But querying an invoke function sounds a bit odd to me when you can also invoke the invoke.
Either way, thanks for the help :P working now
Hi ! I am using https://github.com/hyperledger/fabric/blob/master/docs/source/install_instantiate.rst for but command: peer channel create -c myc throws an error : unknown command "channel" for "peer". Please help, i am stuck with it and with the above question posted. Any help will be appreciated.
@mraikwar looks like you have the wrong fabric version
what does `peer -v` show?
Fabric peer server version 0.6.1-preview
you need v1, follow the http://hyperledger-fabric.readthedocs.io/en/latest/asset_setup.html to get the correct fabric
How can I see ledger blocks data store on peer?
I don't see any option in peer cli
I see blockchain explorer but it only supports 0.6
curl -L https://raw.githubusercontent.com/hyperledger/fabric/master/examples/sfhackfest/sfhackfest.tar.gz -o sfhackfest.tar.gz 2> /dev/null; tar -xvf sfhackfest.tar.gz gives error "The system can not find specific path" . On which directory should i curl this one?
Ignore the question. Got it
C:\new\hackfest>docker-compose -f docker-compose-gettingstarted.yml build
ca uses an image, skipping
orderer uses an image, skipping
peer0 uses an image, skipping
peer1 uses an image, skipping
peer2 uses an image, skipping
cli uses an image, skipping
Building ccenv_latest
Traceback (most recent call last):
File "docker-compose", line 3, in
When I run a script (from docker-compose) in the cli container, it always exits the container when the script finishes. Can I stop it from doing this? I'd like to be able to `docker exec` into the cli container once the script finishes
When I run a script (from docker-compose) in the cli container, it always exits the container when the script finishes. Can I stop it from doing this? I'd like to be able to `docker exec` into the cli container once the script finishes
** -- edit -- **: ~~solved~~ botched this with the following: `command: /bin/bash -c './