ianco
commented
4 years ago You're getting a "pool timeout" error, which means the demo is not able to connect to the Indy ledger. What steps are you following to run the demo?
Open guilherme-funchal opened 4 years ago
ianco
commented
4 years ago You're getting a "pool timeout" error, which means the demo is not able to connect to the Indy ledger. What steps are you following to run the demo?
guilherme-funchal
commented
4 years ago HI!
Thank you so much for responding quickly
Open two shells, and in each shell run:
git clone https://github.com/bcgov/von-network.git cd von-network ./manage build ./manage start ... and in the second shell:
git clone https://github.com/AnonSolutions/indy-community-demo.git
chmod -R a+rwx indy-community-demo/indy_community_demo cd indy-community-demo/docker ./manage start
ianco
commented
4 years ago Try to open a browser on http://localhost:9000/ and make sure you can see the ledger browser. This will verify the Indy network is actually running
What platform are you running on? (Windows, MacOS, etc?)
guilherme-funchal
commented
4 years ago Ok 1.It's running normal, I can see all nodes in uptime
DID: Gw6pDLhcBcoQesN72qfotTgFa7cbuqZpkX3Xo6pLhPhv
Uptime: 1 hours, 20 minutes, 19 seconds
Txns: 0 config, 5 ledger, 4 pool, 0.0407/s read, 0/s write
indy-node version: 1.9.2Node2
DID: 8ECVSk179mjsjKRLWiQtssMLgp6EPhWXtaYyStWPSGAb
Uptime: 1 hours, 20 minutes, 18 seconds
Txns: 0 config, 5 ledger, 4 pool, 0.0407/s read, 0/s write
indy-node version: 1.9.2Node3
DID: DKVxG2fXXTU8yT5N7hGEbXB3dfdAnYv1JczDUHpmDxya
Uptime: 1 hours, 20 minutes, 18 seconds
Txns: 0 config, 5 ledger, 4 pool, 0.0386/s read, 0/s write
indy-node version: 1.9.2Node4
DID: 4PS3EDQ3dW1tci1Bp6543CfuuebjFrg36kLAUcskGfaA
Uptime: 1 hours, 20 minutes, 18 seconds
Txns: 0 config, 5 ledger, 4 pool, 0.0361/s read, 0/s write
indy-node version: 1.9.2Hmmm it's a strange error. I haven't tested the scrips on Ubuntu (or run this repo recently). I'll give it a try but likely won't have time today, I'll report back on the weekend.
It looks like a schema was created (you should be able to see the transaction through the ledger browser - click on the "Domain" link below the list of nodes) but not the credential definition. Weird.
guilherme-funchal
commented
4 years ago For me looks its OK
-- | --
guilherme-funchal
commented
4 years ago I can see the need to change in yaml.load function for yaml.safe_load in the loads_schemas.py and loads_orgs.py files.
I hope I helped you
guilherme-funchal
commented
4 years ago Hello
Whem I run base-image file, I can see this error :
error[E0119]: conflicting implementations of trait std::convert::From<&_> for type types::to_sql::ToSqlOutput<'_>:
--> /home/indy/.cargo/registry/src/github.com-1ecc6299db9ec823/rusqlite-0.13.0/src/types/to_sql.rs:26:1 |
18 | / impl<'a, T: ?Sized> From<&'a T> for ToSqlOutput<'a> 19 | where &'a T: Into<ValueRef<'a>> 20 | { 21 | fn from(t: &'a T) -> Self { 22 | ToSqlOutput::Borrowed(t.into()) 23 | } 24 | } | _- first implementation here 25 | 26 | impl<'a, T: Into |
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ conflicting implementation for types::to_sql::ToSqlOutput<'_> |
|---|
= note: downstream crates may implement trait std::convert::From<&_> for type types::value::Value
error: aborting due to previous error
For more information about this error, try rustc --explain E0119.
error: could not compile rusqlite.
warning: build failed, waiting for other jobs to finish...
error: build failed
ianco
commented
4 years ago There's been some Indy SDK re-factoring, so it looks like the script is picking up incompatible versions of something. Depending on what you're trying to accomplish, there may be some more up-to-date frameworks that you can work with. Have you looked at Aries Cloud Agent? (https://github.com/hyperledger/aries-cloudagent-python) There is some demo Python code and a recent PR with some sample application code that uses this agent (https://github.com/hyperledger/aries-cloudagent-python/pull/318). Let me know what you're trying to do and I can give you some pointers.
guilherme-funchal
commented
4 years ago I tried to test django-indy-community example in my job. I am working on a project that will use Hyperledger, and I am trying to get an idea of the difficulties of using Django for this.
I tried to test : git clone https://github.com/AnonSolutions/django-indy-community.git
chmod -R a+rwx django-indy-community/indy_community_demo cd django-indy-community/docker ./base-image ./manage start
ianco
commented
4 years ago Django itself is pretty easy to use with Hyperledger. The problem is with the dependencies (Indy SDK, VCX, etc) which are constantly changing. One thing you can try is to use the published docker image (i.e. skip the "./base-image" step and it should download a docker image rather than build one). Eventually (when I have time) this library is going to me migrated to use the newer agent code (i.e. aries cloud agent rather than VCX), so I am currently recommending to people to look at Aries. The Aries cloud agent provides a REST API so it is very easy to use and integrate into pretty much any framework.
guilherme-funchal
commented
4 years ago I tried to use :
git clone https://github.com/AnonSolutions/django-indy-community.git
chmod -R a+rwx django-indy-community/indy_community_demo cd django-indy-community/docker ./manage start
Error : wallet-db_1 | 2020-01-06 16:21:28.553 UTC [45] STATEMENT: CREATE DATABASE o_faber_college
indy-django_1 | Traceback (most recent call last):
indy-django_1 | File "manage.py", line 15, in
ianco
commented
4 years ago You will need to reset your environment.
First stop all your docker containers by running "./manage stop", and then run "./manage rm" to delete any persistent volumes. (You can "
guilherme-funchal
commented
4 years ago I tried...but same bug occurs
guilherme-funchal
commented
4 years ago What do I need to change to use Aries?
ianco
commented
4 years ago There is some documentation in the Aries repo, I suggest looking at the demo first.
ianco
commented
4 years ago I've made some changes to the README file in the django-indy-community project (and added some comments to the issue you logged in that repo).
Please see the updated README and those comments and let me know if you have any questions. This should fix a lot of the issues you have been having running these demo's. (Caused mainly by incompatible Indy versions in this code vs. the latest von-network).
Hi
I need help, I tried to use the demo version, but I get the following error in the terminal :
indy-django_1 | Traceback (most recent call last): indy-django_1 | File "manage.py", line 15, in indy-django_1 | execute_from_command_line(sys.argv) indy-django_1 | File "/home/indy/.pyenv/versions/3.6.5/lib/python3.6/site-packages/django/core/management/init.py", line 381, in execute_from_command_line indy-django_1 | utility.execute() indy-django_1 | File "/home/indy/.pyenv/versions/3.6.5/lib/python3.6/site-packages/django/core/management/init.py", line 375, in execute indy-django_1 | self.fetch_command(subcommand).run_from_argv(self.argv) indy-django_1 | File "/home/indy/.pyenv/versions/3.6.5/lib/python3.6/site-packages/django/core/management/base.py", line 323, in run_from_argv indy-django_1 | self.execute(*args, *cmd_options) indy-django_1 | File "/home/indy/.pyenv/versions/3.6.5/lib/python3.6/site-packages/django/core/management/base.py", line 364, in execute indy-django_1 | output = self.handle(args, *options) indy-django_1 | File "/home/indy/indy_community_demo/indy_community_demo/indy_community/management/commands/loads_orgs.py", line 91, in handle indy-django_1 | org = org_signup(user, password, name, org_attrs=org_attrs, org_relation_attrs=relation_attrs, org_role=org_role, org_ico_url=ico_url) indy-django_1 | File "/home/indy/indy_community_demo/indy_community_demo/indy_community/registration_utils.py", line 74, in org_signup indy-django_1 | org = org_provision(org, raw_password, org_role) indy-django_1 | File "/home/indy/indy_community_demo/indy_community_demo/indy_community/registration_utils.py", line 59, in org_provision indy-django_1 | creddef = create_creddef(org.wallet, schema, schema.schema_name + '-' + org.wallet.wallet_name, schema.schema_template) indy-django_1 | File "/home/indy/indy_community_demo/indy_community_demo/indy_community/agent_utils.py", line 180, in create_creddef indy-django_1 | cred_def = run_coroutine_with_args(CredentialDef.create, 'credef_uuid', creddef_name, indy_schema.ledger_schema_id, 0) indy-django_1 | File "/home/indy/indy_community_demo/indy_community_demo/indy_community/utils.py", line 91, in run_coroutine_with_args indy-django_1 | return loop.run_until_complete(coroutine(args)) indy-django_1 | File "/home/indy/.pyenv/versions/3.6.5/lib/python3.6/asyncio/base_events.py", line 468, in run_until_complete indy-django_1 | return future.result() indy-django_1 | File "/home/indy/.pyenv/versions/3.6.5/lib/python3.6/site-packages/vcx/api/credential_def.py", line 76, in create indy-django_1 | c_params) indy-django_1 | File "/home/indy/.pyenv/versions/3.6.5/lib/python3.6/site-packages/vcx/api/vcx_base.py", line 47, in _create indy-django_1 | cls.create.cb) indy-django_1 | vcx.error.VcxError: (<ErrorCode.CreateCredentialDefErr: 1034>, {'backtrace': '', 'cause': 'Error: Unknown libindy error\n Caused by: Error: Pool timeout\n Caused by: Consensus is impossible\n\n', 'error': 'Call to create Credential Definition failed', 'message': 'Error: Call to create Credential Definition failed\n Caused by: Error: Unknown libindy error\n Caused by: Error: Pool timeout\n Caused by: Consensus is impossible\n\n\n'})