-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Trouble using Witness object #11
Comments
Works here:
However, I am on Chain_id is not part of info(), same as with bitshares (uptick vs. peerplays):
|
Still not working for me after upgrading:
|
I created a fresh virtual env, downloaded a zip of the develop branch, unzipped it and changed to the python-peerplays-develop folder. I installed with
Are you sure all your dependencies are declared in the setup? I'm Running python version 3.5.3 on I now suspect there is a Debian issue. This is Debian 9 'Stretch'. I had to create a symbolic link to readline.so.6 --> readline.so.7, but even with that I can't get the witness_node to compile, so the platform apparently has issues. If it weren't for the fact people have reported docker issues on other platforms, I'd blame by docker problem on the OS as well. I dunno what the $^%#^ is missing / screwed up, but I highly suspect the OS now, especially since xeroc has looked at this and can't duplicate the issue. Seems real odd it works for some accounts but not others, but with this extensive list of Stretch issues I have serious doubts about Debian's latest OS release. See the notes about it here: https://www.debian.org/releases/stretch/arm64/release-notes/ch-information.en.html |
Baxter is the public testnet, not main net. |
Why do you assume I want to connect to Baxter? The witness name I'm using is on main net, and the api nodes are as well. This effort pre-dated the release of the bookie beta, but it was undertaken with that in mind. I could try it on the testnet but this is a bare bones simple example that should work and doesn't. I also see that the bookie beta docker img was released on a Debian 9 OS base. I have not been able to make that work yet, but obviously it's possible. That is separate from python-peerplays, which should insulate python programs from OS peculiarities, generally speaking. |
After resolving the ssl certificate problem on all of my nodes and successfully being able to connect to them using python-peerplays, I am getting an exception:
This exact, simple code works in python-bitshares, but not in python-peerplays. The only differences I can see is that in bitshares my witness account name has no dashes in it whereas in peerplays it does, and the length of the name is much longer in the failure case. I added the active key for the witness account to the SQLite wallet after pulling it from my active witness wallet using "dump_private_keys". I also verified the key is correct by comparing to what I saved in my key vault.
I also tried this to eliminate issues with private key, length and the dash as possible causes:
All failed except init0. I then tried to verify the chainId using:
and it printed everything except the chainId (which is 6b6b5f0ce7a36d323768e534f3edb41c6d6332a541a95725b98e28d140850134):
{'recently_missed_count': 0, 'current_witness': '1.6.12', 'last_budget_time': '2018-03-29T23:00:00', 'witness_budget': 321175, 'head_block_number': 8463816, 'id': '2.1.0', 'random': 'e6a71bc39291540dfc3c2011d68144ab8d4561f7', 'time': '2018-03-29T23:38:00', 'recent_slots_filled': '340282366920938463463374607431768211455', 'dynamic_flags': 0, 'next_maintenance_time': '2018-03-30T00:00:00', 'head_block_id': '008125c8681c2396a9a146ba3958d11714fd9b7a', 'last_irreversible_block_num': 8463803, 'current_aslot': 8512624, 'accounts_registered_this_interval': 0}
If I'm doing something wrong (I'm now rather doubtful I am) it is mighty subtle.
The text was updated successfully, but these errors were encountered: