arkecosystem / deployer Goto Github PK

Releases

Last week there were no releases.

Contributors

Last week there was 1 contributor.

Thank you for your contribution! 🎉

Star Gazers

Last week there was 1 stargazer.

@GreyforestMedia

You are the star! 🌟

That's all activities since Mon, May 27, 2019 12:00 AM, please Watch and Star the repository ArkEcosystem/deployer to receive upcoming weekly updates.

You can also view all Weekly Digests by clicking here.

Exotic nodejs error when installing core

Expected Behavior

I expect that I can install deployer on Ubuntu 18.04

Current Behavior

It fails with an exotix nodejs error randomly.

Here is the (I think) relevant code snippet):

error /home/hydra/hydra-core/node_modules/sqlite3: Command failed.
Exit code: 1
Command: node-pre-gyp install --fallback-to-build
Arguments: 
Directory: /home/hydra/hydra-core/node_modules/sqlite3
Output:
node-pre-gyp info it worked if it ends with ok
node-pre-gyp info using [email protected]
node-pre-gyp info using [email protected] | linux | x64
node-pre-gyp WARN Using request for node-pre-gyp https download 
node-pre-gyp info check checked for "/home/hydra/hydra-core/node_modules/sqlite3/lib/binding/node-v67-linux-x64/node_sqlite3.node" (not found)
node-pre-gyp http GET https://mapbox-node-binary.s3.amazonaws.com/sqlite3/v4.0.2/node-v67-linux-x64.tar.gz
node-pre-gyp http 403 https://mapbox-node-binary.s3.amazonaws.com/sqlite3/v4.0.2/node-v67-linux-x64.tar.gz
node-pre-gyp WARN Tried to download(403): https://mapbox-node-binary.s3.amazonaws.com/sqlite3/v4.0.2/node-v67-linux-x64.tar.gz 
node-pre-gyp WARN Pre-built binaries not found for [email protected] and [email protected] (node-v67 ABI, glibc) (falling back to source compile with node-gyp) 
node-pre-gyp http 403 status code downloading tarball https://mapbox-node-binary.s3.amazonaws.com/sqlite3/v4.0.2/node-v67-linux-x64.tar.gz 
node-pre-gyp WARN Pre-built binaries not installable for [email protected] and [email protected] (node-v67 ABI, glibc) (falling back to source compile with node-gyp) 
node-pre-gyp WARN Hit error Connection closed while downloading tarball file 
gyp info it worked if it ends with ok
gyp info using [email protected]
gyp info using [email protected] | linux | x64
gyp info it worked if it ends with ok
gyp info using [email protected]
gyp info using [email protected] | linux | x64
gyp info ok 
gyp info ok 
gyp info it worked if it ends with ok
gyp info using [email protected]
gyp info using [email protected] | linux | x64
gyp info it worked if it ends with ok
gyp info using [email protected]
gyp info using [email protected] | linux | x64
gyp info spawn /usr/bin/python2
gyp info spawn args [ '/home/hydra/hydra-core/node_modules/node-gyp/gyp/gyp_main.py',
gyp info spawn args   'binding.gyp',
gyp info spawn args   '-f',
gyp info spawn args   'make',
gyp info spawn args   '-I',
gyp info spawn args   '/home/hydra/hydra-core/node_modules/sqlite3/build/config.gypi',
gyp info spawn args   '-I',
gyp info spawn args   '/home/hydra/hydra-core/node_modules/node-gyp/addon.gypi',
gyp info spawn args   '-I',
gyp info spawn args   '/home/hydra/.node-gyp/11.15.0/include/node/common.gypi',
gyp info spawn args   '-Dlibrary=shared_library',
gyp info spawn args   '-Dlibrary=shared_library',
gyp info spawn args   '-Dvisibility=default',
gyp info spawn args   '-Dnode_root_dir=/home/hydra/.node-gyp/11.15.0',
gyp info spawn args   '-Dnode_gyp_dir=/home/hydra/hydra-core/node_modules/node-gyp',
gyp info spawn args   '-Dnode_lib_file=/home/hydra/.node-gyp/11.15.0/<(target_arch)/node.lib',
gyp info spawn args   '-Dmodule_root_dir=/home/hydra/hydra-core/node_modules/sqlite3',
gyp info spawn args   '-Dnode_engine=v8',
gyp info spawn args   '--depth=.',
gyp info spawn args   '--no-parallel',
gyp info spawn args   '--generator-output',
gyp info spawn args   'build',
gyp info spawn args   '-Goutput_dir=.' ]
gyp info spawn /usr/bin/python2
gyp info spawn args [ '/home/hydra/hydra-core/node_modules/node-gyp/gyp/gyp_main.py',
gyp info spawn args   'binding.gyp',
gyp info spawn args   '-f',
gyp info spawn args   'make',
gyp info spawn args   '-I',
gyp info spawn args   '/home/hydra/hydra-core/node_modules/sqlite3/build/config.gypi',
gyp info spawn args   '-I',
gyp info spawn args   '/home/hydra/hydra-core/node_modules/node-gyp/addon.gypi',
gyp info spawn args   '-I',
gyp info spawn args   '/home/hydra/.node-gyp/11.15.0/include/node/common.gypi',
gyp info spawn args   '-Dlibrary=shared_library',
gyp info spawn args   '-Dvisibility=default',
gyp info spawn args   '-Dnode_root_dir=/home/hydra/.node-gyp/11.15.0',
gyp info spawn args   '-Dnode_gyp_dir=/home/hydra/hydra-core/node_modules/node-gyp',
gyp info spawn args   '-Dnode_lib_file=/home/hydra/.node-gyp/11.15.0/<(target_arch)/node.lib',
gyp info spawn args   '-Dmodule_root_dir=/home/hydra/hydra-core/node_modules/sqlite3',
gyp info spawn args   '-Dnode_engine=v8',
gyp info spawn args   '--depth=.',
gyp info spawn args   '--no-parallel',
gyp info spawn args   '--generator-output',
gyp info spawn args   'build',
gyp info spawn args   '-Goutput_dir=.' ]
gyp info ok 
gyp info ok 
gyp info it worked if it ends with ok
gyp info using [email protected]
gyp info using [email protected] | linux | x64
gyp info it worked if it ends with ok
gyp info using [email protected]
gyp info using [email protected] | linux | x64
gyp info spawn make
gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ]
make: Entering directory '/home/hydra/hydra-core/node_modules/sqlite3/build'
  ACTION deps_sqlite3_gyp_action_before_build_target_unpack_sqlite_dep Release/obj/gen/sqlite-autoconf-3240000/sqlite3.c
gyp info spawn make
gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ]
make: Entering directory '/home/hydra/hydra-core/node_modules/sqlite3/build'
  ACTION deps_sqlite3_gyp_action_before_build_target_unpack_sqlite_dep Release/obj/gen/sqlite-autoconf-3240000/sqlite3.c
  TOUCH Release/obj.target/deps/action_before_build.stamp
  CC(target) Release/obj.target/sqlite3/gen/sqlite-autoconf-3240000/sqlite3.o
  TOUCH Release/obj.target/deps/action_before_build.stamp
  CC(target) Release/obj.target/sqlite3/gen/sqlite-autoconf-3240000/sqlite3.o
Release/obj/gen/sqlite-autoconf-3240000/sqlite3.c: In function ‘sqlite3_db_status’:
Release/obj/gen/sqlite-autoconf-3240000/sqlite3.c: In function ‘sqlite3_db_status’:

Somewhy it cannot download the tarball files, and then the nodegyp fails. But sometimes its able to download it.

Possible Solution

I have a feeling that the coreIp in the config is somewhat related to this bug, because it worked, when I set it to 127.0.0.1

Any Idea?

[Weekly Digest] May 20, 2019 - May 26, 2019

Here's the Weekly Digest from Mon, May 20, 2019 12:00 AM to Sun, May 26, 2019 11:59 PM for ArkEcosystem/deployer.

Issues

Last week there was 1 issue. It is closed now.

Closed

@ArkEcosystemBot

#59 [Weekly Digest] May 6, 2019 - May 12, 2019

Pull Requests

Last week, no pull-requests were opened, closed or merged.

Releases

Last week there were no releases.

Contributors

Last week there were no contributors.

Star Gazers

Last week there were no stargazers.

That's all activities since Mon, May 20, 2019 12:00 AM, please Watch and Star the repository ArkEcosystem/deployer to receive upcoming weekly updates.

You can also view all Weekly Digests by clicking here.

[Weekly Digest] Sep 9, 2019 - Sep 15, 2019

Here's the Weekly Digest from Mon, Sep 9, 2019 12:00 AM to Sun, Sep 15, 2019 11:59 PM for ArkEcosystem/deployer.

Issues

Last week there were no issues.

Pull Requests

Last week, 1 pull-request was opened, closed or merged.

Merged

Last week, 1 pull-request was merged.

#86 [WIP] refactor: core 2.5 & general fixes

Releases

Last week there were no releases.

Contributors

Last week there was 1 contributor.

Thank you for your contribution! 🎉

Star Gazers

Last week there were no stargazers.

That's all activities since Mon, Sep 9, 2019 12:00 AM, please Watch and Star the repository ArkEcosystem/deployer to receive upcoming weekly updates.

You can also view all Weekly Digests by clicking here.

Performance: High CPU Usage

Please see https://github.com/ArkEcosystem/ark-explorer/issues/123 for details.

webpack-dev-server seems to be the reason.
Is there an alternate way to run a sidechain explorer without high CPU usage?
TY

License fails with "©"

Vanilla install
/home/bridgechain/ark-deployer/app/args.sh: line 239: export: `©': not a valid identifier

Version used: latest, 6/12/19
Environment name and version (e.g. node.js v10.15.3):
bridgechain@lasvegas-nv-datacenter:~$ node -v
v11.15.0
Operating System and version: Ubuntu 18

Additional argument for Explorer Node IP as well as Explorer IP

This is to allow for explorer to be installed on a separate machine/environment

[Weekly Digest] May 13, 2019 - May 19, 2019

Here's the Weekly Digest from Mon, May 13, 2019 12:00 AM to Sun, May 19, 2019 11:59 PM for ArkEcosystem/deployer.

Issues

Last week there was 1 issue. It is closed now.

Closed

@ArkEcosystemBot

#57 [Weekly Digest] Apr 29, 2019 - May 5, 2019

Pull Requests

Last week, no pull-requests were opened, closed or merged.

Releases

Last week there were no releases.

Contributors

Last week there were no contributors.

Star Gazers

Last week there were no stargazers.

That's all activities since Mon, May 13, 2019 12:00 AM, please Watch and Star the repository ArkEcosystem/deployer to receive upcoming weekly updates.

You can also view all Weekly Digests by clicking here.

[Weekly Digest] Jul 22, 2019 - Jul 28, 2019

Here's the Weekly Digest from Mon, Jul 22, 2019 12:00 AM to Sun, Jul 28, 2019 11:59 PM for ArkEcosystem/deployer.

Issues

Last week there was 1 issue. It is still open.

Opened

@mudlee

#82 Exotic nodejs error when installing core

Pull Requests

Last week, 2 pull-requests were opened, closed or merged.

Merged

Last week, 2 pull-requests were merged.

Releases

Last week there were no releases.

Contributors

Last week there was 1 contributor.

Thank you for your contribution! 🎉

Star Gazers

Last week there were no stargazers.

That's all activities since Mon, Jul 22, 2019 12:00 AM, please Watch and Star the repository ArkEcosystem/deployer to receive upcoming weekly updates.

You can also view all Weekly Digests by clicking here.

Script does not stop on error in dependencies.sh

I am running ./bridgechain.sh install-node --name MyTest --database ark_mytest --token MYTEST --symbol MT --node-ip 192.168.178.41 on a system without npm installed. Now the issue is that the script continues after the failure "npm: command not found"

Setting up libcairo2-dev:amd64 (1.15.10-2) ...
Setting up build-essential (12.4ubuntu1) ...
Processing triggers for libc-bin (2.27-3ubuntu1) ...
Processing triggers for systemd (237-3ubuntu10) ...
Processing triggers for ureadahead (0.100.0-20) ...
==> Program Dependencies Installed!
/home/simon/ark-deployer/lib/dependencies.sh: line 50: npm: command not found
/home/simon/ark-deployer/lib/dependencies.sh: line 50: npm: command not found
/home/simon/ark-deployer/lib/dependencies.sh: line 50: npm: command not found
/home/simon/ark-deployer/lib/dependencies.sh: line 50: npm: command not found
[ forever grunt-cli node-sass angular-cli ] are not installed. Do you want to install them? [y/N]: y
==> Installing NodeJS Dependencies...
sh: 1: npm: not found

How do I access the wallet with the premined coins?

/home/user/ark-deployer/app/process-node.sh: line 96: cd: /home/user/ark-sidechain: No such file or directory

user@host:~/ark-user-chain$ ../ark-deployer/sidechain.sh stop-node
==> Stopping...
/home/user/ark-deployer/app/process-node.sh: line 96: cd: /home/user/ark-sidechain: No such file or directory

missing use of variable?

[Weekly Digest] Jun 10, 2019 - Jun 16, 2019

Here's the Weekly Digest from Mon, Jun 10, 2019 12:00 AM to Sun, Jun 16, 2019 11:59 PM for ArkEcosystem/deployer.

Issues

Last week there were 3 issues. Of these, 2 issues have been closed and 1 issues are still open.

Opened

@jdar

#77 License fails with "©"

Closed

@ArkEcosystemBot

Pull Requests

Last week, 2 pull-requests were opened, closed or merged.

Merged

Last week, 2 pull-requests were merged.

Releases

Last week there were no releases.

Contributors

Last week there was 1 contributor.

Thank you for your contribution! 🎉

Star Gazers

Last week there was 1 stargazer.

@mkubdev

You are the star! 🌟

That's all activities since Mon, Jun 10, 2019 12:00 AM, please Watch and Star the repository ArkEcosystem/deployer to receive upcoming weekly updates.

You can also view all Weekly Digests by clicking here.

[Weekly Digest] Apr 8, 2019 - Apr 14, 2019

Here's the Weekly Digest from Mon, Apr 8, 2019 12:00 AM to Sun, Apr 14, 2019 11:59 PM for ArkEcosystem/deployer.

Issues

Last week there were 3 issues. Of these, 3 issues have been closed and 0 issues are still open.

Closed

@ArkEcosystemBot

Pull Requests

Last week, 1 pull-request was opened, closed or merged.

Merged

Last week, 1 pull-request was merged.

#49 fix: remove unnecessary milestone option

Releases

Last week there were no releases.

Contributors

Last week there was 1 contributor.

Thank you for your contribution! 🎉

Star Gazers

Last week there were no stargazers.

That's all activities since Mon, Apr 8, 2019 12:00 AM, please Watch and Star the repository ArkEcosystem/deployer to receive upcoming weekly updates.

You can also view all Weekly Digests by clicking here.

[Weekly Digest] Jun 3, 2019 - Jun 9, 2019

Here's the Weekly Digest from Mon, Jun 3, 2019 12:00 AM to Sun, Jun 9, 2019 11:59 PM for ArkEcosystem/deployer.

Issues

Last week there was 1 issue. It is still open.

Opened

@bitriyal

#73 compile

Pull Requests

Last week, no pull-requests were opened, closed or merged.

Releases

Last week there were no releases.

Contributors

Last week there were no contributors.

Star Gazers

Last week there was 1 stargazer.

@pemtajo

You are the star! 🌟

That's all activities since Mon, Jun 3, 2019 12:00 AM, please Watch and Star the repository ArkEcosystem/deployer to receive upcoming weekly updates.

You can also view all Weekly Digests by clicking here.

[Weekly Digest] Mar 11, 2019 - Mar 17, 2019

Here's the Weekly Digest from Mon, Mar 11, 2019 12:00 AM to Sun, Mar 17, 2019 11:59 PM for ArkEcosystem/deployer.

Issues

Last week there was 1 issue. It is closed now.

Closed

@ArkEcosystemBot

#39 [Weekly Digest] Jan 28, 2019 - Feb 3, 2019

Pull Requests

Last week, no pull-requests were opened, closed or merged.

Releases

Last week there were no releases.

Contributors

Last week there were no contributors.

Star Gazers

Last week there were no stargazers.

That's all activities since Mon, Mar 11, 2019 12:00 AM, please Watch and Star the repository ArkEcosystem/deployer to receive upcoming weekly updates.

You can also view all Weekly Digests by clicking here.

Additional argument for specifying PORT(s)

Installing multiple sidechains per host for various reasons can have port conflicts.

Let's make sure they're not hardcoded. Node and explorer ports.

You need to install postgresql-server-dev-X.Y for building a server-side extension | Ubuntu 16.04

Got that issue on Ubuntu 16.04 :
https://zupimages.net/up/18/04/sajf.png
Solved with :
https://www.postgresql.org/download/linux/ubuntu/ &
sudo apt-get install postgresql
sudo apt-get install python-psycopg2
sudo apt-get install libpq-dev

[Weekly Digest] Aug 12, 2019 - Aug 18, 2019

Here's the Weekly Digest from Mon, Aug 12, 2019 12:00 AM to Sun, Aug 18, 2019 11:59 PM for ArkEcosystem/deployer.

Issues

Last week there were no issues.

Pull Requests

Last week, 1 pull-request was opened, closed or merged.

Opened

Last week, 1 pull-request was opened.

#86 Deployer updates

Releases

Last week there were no releases.

Contributors

Last week there was 1 contributor.

Thank you for your contribution! 🎉

Star Gazers

Last week there were no stargazers.

That's all activities since Mon, Aug 12, 2019 12:00 AM, please Watch and Star the repository ArkEcosystem/deployer to receive upcoming weekly updates.

You can also view all Weekly Digests by clicking here.

[Weekly Digest] Apr 15, 2019 - Apr 21, 2019

Here's the Weekly Digest from Mon, Apr 15, 2019 12:00 AM to Sun, Apr 21, 2019 11:59 PM for ArkEcosystem/deployer.

Issues

Last week there was 1 issue. It is closed now.

Closed

@ArkEcosystemBot

#48 [Weekly Digest] Apr 1, 2019 - Apr 7, 2019

Pull Requests

Last week, 3 pull-requests were opened, closed or merged.

Opened

Last week, 1 pull-request was opened.

#53 feat: improvements to setup of deployer

Closed

Last week, 1 pull-request was closed.

#51 fix: do not use CORE_PATH_CONFIG and --network flag

Merged

Last week, 1 pull-request was merged.

@alexbarnsley @faustbrian

#52 refactor: let core auto-detect configuration

Releases

Last week there were no releases.

Contributors

Last week there were 2 contributors.

Thank you for your contributions! 🎉

Star Gazers

Last week there were no stargazers.

That's all activities since Mon, Apr 15, 2019 12:00 AM, please Watch and Star the repository ArkEcosystem/deployer to receive upcoming weekly updates.

You can also view all Weekly Digests by clicking here.

[Weekly Digest] Sep 16, 2019 - Sep 22, 2019

Here's the Weekly Digest from Mon, Sep 16, 2019 12:00 AM to Sun, Sep 22, 2019 11:59 PM for ArkEcosystem/deployer.

Issues

Last week there were no issues.

Pull Requests

Last week, 3 pull-requests were opened, closed or merged.

Opened

Last week, 1 pull-request was opened.

#96 fix: use correct external IP on EC2 instances

Merged

Last week, 2 pull-requests were merged.

Releases

Last week there were no releases.

Contributors

Last week there was 1 contributor.

Thank you for your contribution! 🎉

Star Gazers

Last week there was 1 stargazer.

You are the star! 🌟

That's all activities since Mon, Sep 16, 2019 12:00 AM, please Watch and Star the repository ArkEcosystem/deployer to receive upcoming weekly updates.

You can also view all Weekly Digests by clicking here.

Is dependency angular-cli still used

There is a dependency on the globally installed node module angular-cli. I did not find any place where this is actually required. Is the dependency obsolete?

Runaway forever logs

Hiya,
Have a bridgechain running for a month and noticed the ~/.forever/xxxx.log growing into the GBs.

Is there a way to set up log rotation and a reasonable size target size?

The logs seem to log a lot of debug which may not be needed for a long running bridge chain.
How can we adjust that?

Let's say you fix the log rotation, what is the proper way to upgrade the code already running?

This brings up lots of questions as to how to best run bridgechains longterm.

[Weekly Digest] Jan 28, 2019 - Feb 3, 2019

Here's the Weekly Digest from Mon, Jan 28, 2019 12:00 AM to Sun, Feb 3, 2019 11:59 PM for ArkEcosystem/deployer.

Issues

Last week there were no issues.

Pull Requests

Last week, no pull-requests were opened, closed or merged.

Releases

Last week there were no releases.

Contributors

Last week there were no contributors.

Star Gazers

Last week there were no stargazers.

That's all activities since Mon, Jan 28, 2019 12:00 AM, please Watch and Star the repository ArkEcosystem/deployer to receive upcoming weekly updates.

You can also view all Weekly Digests by clicking here.

[Weekly Digest] May 6, 2019 - May 12, 2019

Here's the Weekly Digest from Mon, May 6, 2019 12:00 AM to Sun, May 12, 2019 11:59 PM for ArkEcosystem/deployer.

Issues

Last week there was 1 issue. It is closed now.

Closed

@ArkEcosystemBot

#56 [Weekly Digest] Apr 22, 2019 - Apr 28, 2019

Pull Requests

Last week, 1 pull-request was opened, closed or merged.

Opened

Last week, 1 pull-request was opened.

#58 fix: remove the core_ prefix and use the $TOKEN as database username and prefix

Releases

Last week there were no releases.

Contributors

Last week there was 1 contributor.

Thank you for your contribution! 🎉

Star Gazers

Last week there was 1 stargazer.

@khaninejad

You are the star! 🌟

That's all activities since Mon, May 6, 2019 12:00 AM, please Watch and Star the repository ArkEcosystem/deployer to receive upcoming weekly updates.

You can also view all Weekly Digests by clicking here.

[Weekly Digest] Mar 18, 2019 - Mar 24, 2019

Here's the Weekly Digest from Mon, Mar 18, 2019 12:00 AM to Sun, Mar 24, 2019 11:59 PM for ArkEcosystem/deployer.

Issues

Last week there were no issues.

Pull Requests

Last week, 1 pull-request was opened, closed or merged.

Merged

Last week, 1 pull-request was merged.

#41 feat: deployer for core v2

Releases

Last week there were no releases.

Contributors

Last week there was 1 contributor.

https://github.com/ArkEcosystem/ark-node/blob/c1df3762a4301deab54f7ab0f7935a7975497cd5/modules/accounts.js#L51

Thank you for your contribution! 🎉

Star Gazers

Last week there were no stargazers.

That's all activities since Mon, Mar 18, 2019 12:00 AM, please Watch and Star the repository ArkEcosystem/deployer to receive upcoming weekly updates.

You can also view all Weekly Digests by clicking here.

Desktop Wallet unable to retrieve/refresh genesys wallet info/balance on remote server node

It seems that unless a peer is added with the IP address of the server and port, the wallet cannot function properly. No balance, no transactions possible.

This is a remote server install with wallet not on the same machine.

Some endpoints are unavailable (e.g. getAllAccounts)

This is due to some being debug endpoints that need the DEBUG env to be set:

Edit: This example endpoint might be depreciated. Regardless, will add an argument such as --debug-endpoints

[Weekly Digest] Jul 29, 2019 - Aug 4, 2019

Here's the Weekly Digest from Mon, Jul 29, 2019 12:00 AM to Sun, Aug 4, 2019 11:59 PM for ArkEcosystem/deployer.

Issues

Last week there were 6 issues. Of these, 6 issues have been closed and 0 issues are still open.

Closed

#22 Some endpoints are unavailable (e.g. getAllAccounts)

@bitriyal

#73 compile

@mudlee

@sambengtson

#32 Running in a docker container

@webmaster128

#25 Installing global npm packages needs sudo

Pull Requests

Last week, 1 pull-request was opened, closed or merged.

Closed

Last week, 1 pull-request was closed.

#58 fix: remove the core_ prefix and use the $TOKEN as database username and prefix

Releases

Last week there were no releases.

Contributors

Last week there were no contributors.

Star Gazers

Last week there were no stargazers.

That's all activities since Mon, Jul 29, 2019 12:00 AM, please Watch and Star the repository ArkEcosystem/deployer to receive upcoming weekly updates.

You can also view all Weekly Digests by clicking here.

[Weekly Digest] Mar 25, 2019 - Mar 31, 2019

Here's the Weekly Digest from Mon, Mar 25, 2019 12:00 AM to Sun, Mar 31, 2019 11:59 PM for ArkEcosystem/deployer.

Issues

Last week there were no issues.

Pull Requests

Last week, 1 pull-request was opened, closed or merged.

Merged

Last week, 1 pull-request was merged.

#43 fix: total premine

Releases

Last week there were no releases.

Contributors

Last week there was 1 contributor.

https://github.com/ArkEcosystem/ark-node/blob/development/helpers/constants.js#L44

Thank you for your contribution! 🎉

Star Gazers

Last week there were no stargazers.

That's all activities since Mon, Mar 25, 2019 12:00 AM, please Watch and Star the repository ArkEcosystem/deployer to receive upcoming weekly updates.

You can also view all Weekly Digests by clicking here.

Deployer cannot install devnet properly - missing virtual delegates

Expected Behavior

I'm expecting that if I build a new core with the deployer, it comes up with a predefined (51 as default) virtual delegates as forgers. When I start the core, it should bring up a relay genesis node and forger nodes.

I used this guide.

Current Behavior

When I do the core install process with testnet, it works. When I do it with devnet or mainnet, it does not work.
I get this error, and I see that the genesis node is running, but there is no forger started.

Possible Solution

I don't know if it's an expected behavior or not, but app/app-core.sh I see a line (258) for testnet that does not exist for devnet and mainnet:

cp "$CONFIG_PATH_TESTNET/delegates.json" "$BRIDGECHAIN_PATH/packages/core/bin/config/testnet/"

So at the end, the core has a delegates.json under devnet and mainnet with empty secrets, hence it cannot start any forger and gives me the error.

Steps to Reproduce (for bugs)

Start the deployer with devnet or mainnet.

Context

I'm unable to create a devnet without errors.

Your Environment

Version used: latest
Environment name and version (e.g. node.js v10.15.3): latest
Server type and version: GCP n1-standard
Operating System and version: Ubuntu 18.04
Link to your project: -

Ability to change maximum possible tokens

This is through a parameter, relating to the below value:

An issue occurs whereby if --total-premine is greater than is value initially, the network won't even start.

Side-chain timestamps are messed up

Describe the bug
Timestamp are messed up if we try to create an ARK side-chain with core-deployer :

Default timestamp in genesisBlock are set to 0 which corresponds to 21/03/2017 14:00. It should be set to Timestamp(today) - Timestamp(21/03/2017 14:00), at the time deployer is runned or even better at the time first block is added to the blockchain on network first start.
No idea why, but timestamp of forged blocks after genesis block are computed wrongly : They start from date 01/01/2019, but time is correct.

To Reproduce
Steps to reproduce the behavior:

Run deployer from core-deployer packages with some
legit parameters
Use the generated configuration files on fresh core installation
After nodes start to forge, check timestamps in blocks table from database
Do the maths : 1490101200 + block timestamp, then convert to date
Or run an explorer to have some nice display of the data

Screenshots

Server (please complete the following information):

OS: Ubuntu Server
Version 16.04

[Weekly Digest] Aug 19, 2019 - Aug 25, 2019

Here's the Weekly Digest from Mon, Aug 19, 2019 12:00 AM to Sun, Aug 25, 2019 11:59 PM for ArkEcosystem/deployer.

Issues

Last week there were no issues.

Pull Requests

Last week, 1 pull-request was opened, closed or merged.

Opened

Last week, 1 pull-request was opened.

#88 wip: add update-core command to upgrade deployer chains to 2.5.19

Releases

Last week there were no releases.

Contributors

Last week there was 1 contributor.

Thank you for your contribution! 🎉

Star Gazers

Last week there were 2 stargazers.

@57-Wolve @thbland

You all are the stars! 🌟

That's all activities since Mon, Aug 19, 2019 12:00 AM, please Watch and Star the repository ArkEcosystem/deployer to receive upcoming weekly updates.

You can also view all Weekly Digests by clicking here.

[Weekly Digest] Sep 2, 2019 - Sep 8, 2019

Here's the Weekly Digest from Mon, Sep 2, 2019 12:00 AM to Sun, Sep 8, 2019 11:59 PM for ArkEcosystem/deployer.

Issues

Last week there were no issues.

Pull Requests

Last week, 3 pull-requests were opened, closed or merged.

Merged

Last week, 3 pull-requests were merged.

Releases

Last week there were no releases.

Contributors

Last week there was 1 contributor.

Thank you for your contribution! 🎉

Star Gazers

Last week there were no stargazers.

That's all activities since Mon, Sep 2, 2019 12:00 AM, please Watch and Star the repository ArkEcosystem/deployer to receive upcoming weekly updates.

You can also view all Weekly Digests by clicking here.

[Enhancement] - Provide chain parameters through config JSON

Great work - thank you for this functionality! It is an amazing start.

If I may make a few suggestions for improvements.

I would suggest creating a JSON to pass the initialization parameters of the chain: "initConfig.json"

In ark-node you already use: "networks.json". I believe it would be more clear if you created a json for this project that supersedes that json. Then line 51 in "app/app-node.sh" could be a simple:
mv "initConfig.json" "$SIDECHAIN_PATH/networks.json"

It would also be nice to set totalpremine on line 69 of "tasks/createGenesisBlock.js". Again this could be part of the "initConfig.json".
You could also increase the scope of the variables a new chain could implement by modifying "helpers/constants.js". I believe it would be good to allow developers to set the following parameters:
fees
totalAmount

This would require adding a link to the networks.json...
var networks = require('../networks.json');

Hopefully I can get some time and I'll try a fork to test this out. But I wanted to throw this out there...

Again - great work. It is great to see regular progress on a project!

Apt package installed method not working reliably

There are two issues with the currently used method to check package installations:

Installed packages not detected

On Ubuntu 18.04, libcairo2-dev is installed with name "libcairo2-dev:amd64" and thus dpkg -l "libcairo2-dev" 2>/dev/null | fgrep "libcairo2-dev" | egrep "^[a-zA-Z]" | awk '{print $2}' returns "libcairo2-dev:amd64", which is unequal "libcairo2-dev".

Not installed packages are not detected

I don't have curl installed

$ curl --version

Command 'curl' not found, but can be installed with:

sudo apt install curl

but dpkg -l "curl" 2>/dev/null | fgrep "curl" | egrep "^[a-zA-Z]" | awk '{print $2}' returns "curl", even if its installation status is "un " (unknown / not installed / no error).

This issue is mainly for documentation and discussion. PR is in the making.

npm dependency causes install failure

npm WARN optional Skipping failed optional dependency /angular-cli/chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture: [email protected]
npm WARN optional Skipping failed optional dependency /forever/chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture: [email protected]
npm WARN @angular/[email protected] requires a peer of rxjs@^5.0.1 but none was installed.
npm ERR! Linux 4.13.0-1007-azure
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "install" "-g" "forever" "grunt-cli" "node-sass" "angular-cli"
npm ERR! node v4.2.6
npm ERR! npm v3.5.2
npm ERR! path /usr/local/lib
npm ERR! code EACCES
npm ERR! errno -13
npm ERR! syscall access

npm ERR! Error: EACCES: permission denied, access '/usr/local/lib'
npm ERR! at Error (native)
npm ERR! { [Error: EACCES: permission denied, access '/usr/local/lib']
npm ERR! errno: -13,
npm ERR! code: 'EACCES',
npm ERR! syscall: 'access',
npm ERR! path: '/usr/local/lib' }
npm ERR!
npm ERR! Please try running this command again as root/Administrator.

npm ERR! Please include the following file with any support request:
npm ERR! /home/arkadmin/npm-debug.log
==> Stopping...

Trying to get a single script to handle installation into an Ubuntu 16.04LTS VM. Running into this issue right now on a clean VM where the only packages installed before running ./sidechain install-node are: npm, jq. Both of these packages require sudo privileges to install from my testing.

Attempting to install npm without sudo results in "Could not open lock file /var/lib/dpkg/lock - open (13: Permission denied)" not sure if that is behavior others experience with fresh 16.04LTS machines?

Running in a docker container

I'm pretty familiar with docker, but I'm having a hard time building an image with ark-deployer included. Most of the problems seem to be node and gyp related.

While running bridgechain.sh install-node ... there are quite a few errors spamming the terminal. The first one is:

tput: unknown terminal "unknown"

I could see it being beneficial for the ark team to officially support this?

[Weekly Digest] Apr 1, 2019 - Apr 7, 2019

Here's the Weekly Digest from Mon, Apr 1, 2019 12:00 AM to Sun, Apr 7, 2019 11:59 PM for ArkEcosystem/deployer.

Issues

Last week there were no issues.

Pull Requests

Last week, 3 pull-requests were opened, closed or merged.

Merged

Last week, 3 pull-requests were merged.

Releases

Last week there were no releases.

Contributors

Last week there was 1 contributor.

Thank you for your contribution! 🎉

Star Gazers

Last week there were no stargazers.

That's all activities since Mon, Apr 1, 2019 12:00 AM, please Watch and Star the repository ArkEcosystem/deployer to receive upcoming weekly updates.

You can also view all Weekly Digests by clicking here.

Postgres Username fails with hyphens

[Weekly Digest] Sep 23, 2019 - Sep 29, 2019

Here's the Weekly Digest from Mon, Sep 23, 2019 12:00 AM to Sun, Sep 29, 2019 11:59 PM for ArkEcosystem/deployer.

Issues

Last week there were no issues.

Pull Requests

Last week, 1 pull-request was opened, closed or merged.

Merged

Last week, 1 pull-request was merged.

#96 fix: use correct external IP on EC2 instances

Releases

Last week there were no releases.

Contributors

Last week there was 1 contributor.

Thank you for your contribution! 🎉

Star Gazers

Last week there were 2 stargazers.

@RyanKruse @zanjs

You all are the stars! 🌟

That's all activities since Mon, Sep 23, 2019 12:00 AM, please Watch and Star the repository ArkEcosystem/deployer to receive upcoming weekly updates.

You can also view all Weekly Digests by clicking here.

rewardHeight deployer option error

I'm using deployer-v2 branch to deploy a bridgechain and I've got the following error message:

/home/ark/ark-deployer/datadir/packages/core-deployer/bin/deployer:213
network.constants[1].height = options.rewardHeight
                            ^

TypeError: Cannot set property 'height' of undefined
    at Object.<anonymous> (/home/ark/ark-deployer/datadir/packages/core-deployer/bin/deployer:213:31)
    at Module._compile (internal/modules/cjs/loader.js:688:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:699:10)
    at Module.load (internal/modules/cjs/loader.js:598:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:537:12)
    at Function.Module._load (internal/modules/cjs/loader.js:529:3)
    at Function.Module.runMain (internal/modules/cjs/loader.js:741:12)
    at startup (internal/bootstrap/node.js:285:19)
    at bootstrapNodeJSCore (internal/bootstrap/node.js:739:3)

Config:

ubuntu 18.10
default config file (startRewardHeight at 75600)

My workaround was to remove the --rewardHeight option into deployer/app-node.sh

Please replace forever with pm2

After having a sidechain run for several weeks autoforging, the system crashed running out of disk space.

This is because of forever logs filling up the disk, which don't rotate. Apparently forever doesn't have this basic capability. The system logrotate service can't be used since the forever logs have random filenames and can't be specified upon service restart. Forever also appears to be an unmaintained project for the last two years.

To have feasible, long running blockchains, we need a more advanced process manager for node.js.
Doing some research brought me to PM2 - http://pm2.keymetrics.io/

Please replace forever with pm2

Installing global npm packages needs sudo

Some node packages need sudo to be installed globally, e.g. forever

$ npm install -g forever
npm WARN checkPermissions Missing write access to /usr/local/lib
[...]

but in https://github.com/ArkEcosystem/ark-deployer/blob/master/lib/dependencies.sh#L63 they are tried to be installed without sudo

[Weekly Digest] Apr 29, 2019 - May 5, 2019

Here's the Weekly Digest from Mon, Apr 29, 2019 12:00 AM to Sun, May 5, 2019 11:59 PM for ArkEcosystem/deployer.

Issues

Last week there was 1 issue. It is closed now.

Closed

@ArkEcosystemBot

#54 [Weekly Digest] Apr 15, 2019 - Apr 21, 2019

Pull Requests

Last week, no pull-requests were opened, closed or merged.

Releases

Last week there were no releases.

Contributors

Last week there were no contributors.

Star Gazers

Last week there were no stargazers.

That's all activities since Mon, Apr 29, 2019 12:00 AM, please Watch and Star the repository ArkEcosystem/deployer to receive upcoming weekly updates.

You can also view all Weekly Digests by clicking here.

compile

when run :
./bridgechain.sh install-core --config "$CONFIG_PATH" --autoinstall-deps --non-interactive
i get ;
[1560021762310] ERROR (ark-tester-cli/21199 on msalek): "explorerUrl" must be a valid uri with a scheme matching the http|https pattern

any idea !

[Weekly Digest] Apr 22, 2019 - Apr 28, 2019

Here's the Weekly Digest from Mon, Apr 22, 2019 12:00 AM to Sun, Apr 28, 2019 11:59 PM for ArkEcosystem/deployer.

Issues

Last week there was 1 issue. It is closed now.

Closed

@ArkEcosystemBot

#50 [Weekly Digest] Apr 8, 2019 - Apr 14, 2019

Pull Requests

Last week, 1 pull-request was opened, closed or merged.

Merged

Last week, 1 pull-request was merged.

#55 chore: clone 2.2.2 until 2.3.0 is tested

Releases

Last week there were no releases.

Contributors

Last week there was 1 contributor.