Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - kanguro

Pages: [1]
1
Technical Support / What value should I use for the "url-to-proposal"?
« on: January 16, 2018, 03:04:02 pm »
Hi guys, I have one question in the CLI call to create a witness node:

create_witness <accountname> "http://<url-to-proposal>" true

What value should I use for the "url-to-proposal"?
Is that just any domain I own?
Is that a domain associated with my node?
Is that a domain associated with our Bitshares-ui?
Is that a domain associated with our business web site?
does the domain need to be up and available?

I have not found any description as to what that URL is supposed to refer to.

thanks :)

2
Technical Support / Re: Error on import_key, need help thanks
« on: January 16, 2018, 02:58:21 pm »
Thanks, node completed downloading blocks and it works now. I do have one other question but will use a new thread for that.
Thank you very much  :)

3
Technical Support / Re: Error on import_key, need help thanks
« on: January 16, 2018, 02:26:21 am »
Do I have to wait until my node has downloaded all the blocks?

4
Technical Support / Re: Error on import_key, need help thanks
« on: January 16, 2018, 02:23:55 am »
How would I know/check that?
I am running a full node myself. It seems to be working ok,  although it is still getting the blocks (has gotten to about 8M blocks so far)
Both Node and CLI are running on Docker images. CLI sets password and unlocks fine.

5
Technical Support / Error on import_key, need help thanks
« on: January 16, 2018, 01:00:40 am »
Hi, I am trying to follow the instructions to setup a witness node as in:
http://docs.bitshares.org/bitshares/tutorials/witness-howto.html

In the instructions below, what should I put in "accountname" and "owner wif key"?
I got the Owner Private Key for my account from the Web UI
(Permissions->Owner tab, clicking on the key icon and then the Show button in the dialog),

but for account name I tried both my login (account) id or the public key followed by the owner private key and no combination seems to work

This is the part of the tutorial I am trying to do:

>>> import_key <accountname> <owner wif key>
true
>>> import_key <accountname> <active wif key>
true
>>> list_my_accounts

But when I try the first import_key I get this:

10 assert_exception: Assert Exception
rec && rec->name == account_name_or_id:
    {}
    th_a  wallet.cpp:597 get_account

Any ideas? Any help appreciated, thanks :)

6
Ok, I got past this issue. Problem was that my Dockerfile was pulling an older version of Nodejs. There is some other issue I am facing, but will use a new post if I can resolve it. Thanks anyhow guys :)

7
Hi,
I am trying to build for production  BitShares UI https://github.com/bitshares/bitshares-ui

My build is failing apparently because the webpack config is not in strict mode and uses "let".
How can I get past this? is there a way to pass in some parameter that would make it run in strict mode?

I mean would be easy to modify the code with a "use strict", but I am trying to avoid modifying the code. This I would think is being built by other people as is.
Has anyone seen this issue? How can I resolve?

Below is the error, thanks  :)

Step 13/19 : RUN npm run build
 ---> [Warning] Your kernel does not support swap limit capabilities or the cgroup is not mounted. Memory limited without swap.
 ---> Running in 7cfc6910af6a

> BitShares2-light@2.0.180108 build /build
> cross-env NODE_ENV=production webpack --env.prod

/build/webpack.config.js:70
        let outputDir = env.electron ? "electron" : env.hash ? `hash-history_${baseUrl.replace("/", "")}` : "dist";
        ^^^

SyntaxError: Block-scoped declarations (let, const, function, class) not yet supported outside strict mode
    at exports.runInThisContext (vm.js:53:16)
    at Module._compile (module.js:374:25)
    at Object.Module._extensions..js (module.js:417:10)
    at Module.load (module.js:344:32)
    at Function.Module._load (module.js:301:12)
    at Module.require (module.js:354:17)
    at require (internal/module.js:12:17)
    at requireConfig (/build/node_modules/webpack/bin/convert-argv.js:97:18)
    at /build/node_modules/webpack/bin/convert-argv.js:104:17
    at Array.forEach (native)

npm ERR! Linux 4.13.0-26-generic
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "run" "build"
npm ERR! node v4.2.6
npm ERR! npm  v3.5.2
npm ERR! code ELIFECYCLE
npm ERR! BitShares2-light@2.0.180108 build: `cross-env NODE_ENV=production webpack --env.prod`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the BitShares2-light@2.0.180108 build script 'cross-env NODE_ENV=production webpack --env.prod'.
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 BitShares2-light package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     cross-env NODE_ENV=production webpack --env.prod
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs BitShares2-light
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls BitShares2-light
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /build/web/npm-debug.log
The command '/bin/sh -c npm run build' returned a non-zero code: 1



Pages: [1]