DEV Community: sot528

Delete CircleCI's invisible AWS credentials

sot528 — Sat, 14 Jan 2023 12:07:00 +0000

Problem

AWS notified me to rotate AWS credentials that are (seemingly) not registered with CircleCI.

Hello,

AWS is reaching out to you on behalf of CircleCI as a follow-up to the security issue they disclosed on January 4, 2023 [1] involving their platform. AWS infrastructure and services were not affected by this issue.

However, CircleCI believes the following AWS access keys, associated with your account, may be affected by this issue.
AKIA4**************


AWS recommends you rotate these keys immediately.

Occasion

Because the AWS Permission of the CircleCI project, which was used since time immemorial, was still alive even though it was discontinued in the UI.

Solution

AWS Credentials Are Not Found

${CIRCLECI_VCS} with either "github" or "bitbucket"
${CIRCLECI_ORG} with the name of your org
${CIRCLECI_PROJECT} with the name of your project/repository
${CIRCLECI_TOKEN} with a Personal API Token

curl -X PUT -d "{\"aws\":{\"keypair\":null}}" "https://circleci.com/api/v1.1/project/${CIRCLECI_VCS}/${CIRCLECI_ORG}/${CIRCLECI_PROJECT}/settings?circle-token=${CIRCLECI_TOKEN}" -H "Content-Type:application/json"

Note

WTF🤣

Remove unnecessary Docker resources.

sot528 — Fri, 19 Apr 2019 11:15:02 +0000

Problem

Using Docker for Mac long time uses large storage spaces.

sot-mbp:clean_docker_resources sot528$ docker system df
TYPE                TOTAL               ACTIVE              SIZE                RECLAIMABLE
Images              152                 2                   37.57GB             35.79GB (95%)
Containers          4                   0                   35.8MB              35.8MB (100%)
Local Volumes       4                   0                   7.118MB             7.118MB (100%)
Build Cache         0                   0                   0B                  0B

Solution

docker system prune

Then, SIZE is be around 30GB.
And remove old images without recent 10 images.

docker rmi -f $(docker images | sed -n '10,$p')

Result

Good!

sot-mbp:clean_docker_resources sot528$ docker system df
TYPE                TOTAL               ACTIVE              SIZE                RECLAIMABLE
Images              7                   0                   5.337GB             5.337GB (100%)
Containers          0                   0                   0B                  0B
Local Volumes       4                   0                   7.118MB             7.118MB (100%)
Build Cache         0                   0                   0B                  0B

Environment

macOS Mojave 10.14.3（18D109）
Docker version 18.09.2, build 6247962

Install and Update Solidity(solc) in Mac

sot528 — Wed, 26 Dec 2018 06:16:03 +0000

You can install and update solc:

brew update
brew upgrade
brew tap ethereum/ethereum
brew install solidity
brew link --overwrite solidity

Errors

If you got the error below, you have to update xcode.

==> Installing solidity from ethereum/ethereum
Error: Your Xcode (9.0) is too outdated.
Please update to Xcode 10.1 (or delete it).
Xcode can be updated from the App Store.

Try Vyper in Truffle v5.

sot528 — Wed, 19 Dec 2018 12:21:59 +0000

Truffle v5 supported Vyper.
I made Docker image to try it easialy.(Dockerfile)

How to use

docker run -it sot528/truffle-vyper-test

In the container

It unboxed vyper-example-box. So you can use below.

$ truffle test

Using network 'test'.



  Contract: VyperStorage
    ✓ ...should store the value 89. (114ms)


  1 passing (129ms)

It works.
You can try anything via editing ./contracts/VyperStorage.vy and truffle compile.

stored_data: uint256

@public
def set(new_value : uint256):
    self.stored_data = new_value

@public
@constant
def get() -> uint256:
    return self.stored_data

The test file is ./test/vyperStorage.js.

const VyperStorage = artifacts.require("VyperStorage");

contract("VyperStorage", () => {
  it("...should store the value 89.", async () => {
    const storage = await VyperStorage.deployed();

    // Set value of 89
    await storage.set(89);

    // Get stored value
    const storedData = await storage.get();

    assert.equal(storedData, 89, "The value 89 was not stored.");
  });
});

If you see the error below, then you should remove all of the files in build.

Error parsing /code/contracts/VyperStorage.vy: ParsedContract.sol:1:1: ParserError: Expected pragma, import directive or contract/interface/library definition.
stored_data: uint256
^---------^
Compilation failed. See above.
Truffle v5.0.0 (core: 5.0.0)

Run levelDB + Node.js in 1 min on Docker

sot528 — Fri, 14 Dec 2018 03:30:37 +0000

I tried levelDB with Node.js imprementation on Docker.

Usage

docker run -it sot528/leveldbtest

Run on the Docker container

node index.js

You can try anything as edit index.js.

Try to run libp2p(js-libp2p) anyway.

sot528 — Thu, 13 Dec 2018 06:36:54 +0000

I tried to run js-libp2p that Javascript implementation of libp2p.

What to do.

I tried to run transfer.

How to do.

I made a docker image of the process above.

docker run -it sot528/libp2pjstest

Run 3.js in the container.

root@73b031df5d57:~/work# node 3.js

Then, 3 nodes will run and connect each other.

node 1 is listening on:
/ip4/127.0.0.1/tcp/32907/ipfs/QmVSd89zgVLqC3cUVzN3R3dpA8xextxEFBuACd8uSMXXLM
/ip4/172.17.0.4/tcp/32907/ipfs/QmVSd89zgVLqC3cUVzN3R3dpA8xextxEFBuACd8uSMXXLM
node 2 is listening on:
/ip4/127.0.0.1/tcp/40709/ipfs/QmWe7Md6CyDDXaApaXPijKuXYhpK3uktmMamuw5MzW3zWu
/ip4/172.17.0.4/tcp/40709/ipfs/QmWe7Md6CyDDXaApaXPijKuXYhpK3uktmMamuw5MzW3zWu
/ip4/127.0.0.1/tcp/10000/ws/ipfs/QmWe7Md6CyDDXaApaXPijKuXYhpK3uktmMamuw5MzW3zWu
node 3 is listening on:
/ip4/127.0.0.1/tcp/20000/ws/ipfs/QmeKhkwXHPQ29BzbRJuqzMdkKDzWVwwFreWKRRJDLRvw1H
node 3 failed to dial to node 1 with: Circuit not enabled and all transports failed to dial peer QmVSd89zgVLqC3cUVzN3R3dpA8xextxEFBuACd8uSMXXLM!
node 1 dialed to node 2 successfully
node 2 dialed to node 3 successfully

You can try what you want as editing 3.js.

Ethereum:New Solidity constructor

sot528 — Sat, 19 May 2018 13:07:11 +0000

Since Solidity v0.4.23, Solidity has new constructor notation.

And The old one was deprecated.

Old

pragma solidity 0.4.23;

contract Foo {
  function Foo() public {
    // ...
  }
}

New

pragma solidity 0.4.23;

contract Foo {
  constructor() public {
    // ...
  }
}

Note

The old one raise below.

Warning: Defining constructors as functions with the same name as the contract is deprecated. Use "constructor(...) { ... }" instead.

"Route did not stabilize in expected time" on CloudFromation

sot528 — Sun, 25 Mar 2018 13:27:01 +0000

This error occurred via template below:

...

  PNNatGateway:
    Type: 'AWS::EC2::NatGateway'
    Properties:
      AllocationId: eipalloc-xxxxxx
      SubnetId: !Ref PNPublicSubnet
  PNPrivateRouteTable:
    Type: 'AWS::EC2::RouteTable'
    Properties:
      VpcId: !Ref PrivateNet
  PNPrivateRoute:
    Type: 'AWS::EC2::Route'
    Properties:
      RouteTableId: !Ref PNPrivateRouteTable
      DestinationCidrBlock: 0.0.0.0/0
      GatewayId: !Ref PNNatGateway

...

FIX

It fixed when I changed GatewayId to NatGatewayId

...

  PNNatGateway:
    Type: 'AWS::EC2::NatGateway'
    Properties:
      AllocationId: eipalloc-xxxxxx
      SubnetId: !Ref PNPublicSubnet
  PNPrivateRouteTable:
    Type: 'AWS::EC2::RouteTable'
    Properties:
      VpcId: !Ref PrivateNet
  PNPrivateRoute:
    Type: 'AWS::EC2::Route'
    Properties:
      RouteTableId: !Ref PNPrivateRouteTable
      DestinationCidrBlock: 0.0.0.0/0
      NatGatewayId: !Ref PNNatGateway

...

What a unkind error message it is!

EC2にEthereumメインネットのparityノードを立てる

sot528 — Sat, 03 Feb 2018 03:08:42 +0000

AWSのEC2インスタンスにメインネットのparityのノード(light client mode)を構築して開発に使用する手順を記載する。
最短で構築するために意識は低くマネコンから作業。以下のビデオを参考にする。

https://youtu.be/4ac5ZeTveSs

インスタンスを立てる

ビデオを参考に以下の設定を行ったインスタンスを立てる。

AMI: Canonical, Ubuntu, 16.04 LTS, amd64 xenial image build on 2017-11-21
ポート解放: 8545
ストレージ容量確保: 20GB

parityをインストール

ビデオを参考にSSH接続してparityをインストール。

bash <(curl https://get.parity.io -kL)

parityを起動

ここはビデオと異なり、--lightオプションを付加してlight client modeとする。

parity --jsonrpc-hosts all --jsonrpc-interface all --light

クライアントから接続して同期状態を確認

ビデオを参考にインスタンスのipを取得し、以下のようなスクリプト(getBlockNumber.js)を記載(xx.xx.xx.xxは取得したipに書き換え)

W3 = require('web3')
web3 = new W3(new W3.providers.HttpProvider('http://xx.xx.xx.xx:8545'))
web3.eth.getBlockNumber().then(result => {console.log(result)})

実行
```
node getBlockNumber.js
```
以下のようにブロックナンバーが出力されれば同期が成功し、進行している。
```
308485
```
最新のブロックがいくつかはethstatsをチェック。2018/02時点で500万ブロックくらい。
- light client modeでも完全同期まで数日かかる。

parityが途中で落ちる場合はデーモン化する

parityをlight client modeで動かしているとしばらく同期したあとで落ちる場合がある。
その場合はデーモン化すると良い。supervisorを使用してデーモン化する手順をまとめる。

supervisorをインストール

sudo apt-get update
sudo apt-get install supervisor
sudo mkdir /var/log/supervisor/jobs

以下のような設定ファイルを /etc/supervisor/conf.d/ 以下にparity.confとして配置。

[program:Parity]
command=/usr/bin/parity --jsonrpc-hosts all --jsonrpc-interface all --light
user=root
autorestart=true
stdout_logfile=/var/log/supervisor/jobs/parity.log
stdout_logfile_maxbytes=1MB
stdout_logfile_backups=5
stdout_capture_maxbytes=1MB
redirect_stderr=true

supervisorを起動

sudo supervisord
sudo supervisorctl start all

ログを確認しparityが同期を開始していればOK。
```
tail -f /var/log/supervisor/jobs/parity.log
```

落ちても再度立ち上がる。
ちゃんとやるならsupervisor自体をサービス化しておく(割愛)。

備考

Parity: v1.9.0-beta
2018/02現在、上記手順で最新のブロックまで同期できることを確認(数日かかる)。
gethでも良いが、parityはまだ多少安定している印象。しかしフルノード(非light client mode)だと完全に同期するまで何週間も待つ場合がある。
light client modeはまだ実験段階なので本番運用は要注意。

暗号通貨の相場をターミナルで表示する

sot528 — Fri, 12 Jan 2018 04:07:33 +0000

暗号通貨ジャンキーのエンジニアの為に。
暗号通貨の相場はCoinmonを使ってターミナルで確認しましょう。

    npm install -g coinmon
    coinmon

日本円で表示する

    coinmon -c jpy

通貨を指定して表示する

    coinmon -f btc

以上。
これで職場でも安心ですね。

Renamed tools in Ethereum

sot528 — Wed, 20 Dec 2017 15:26:44 +0000

New name(Old name)

OpenEthereum (Parity Ethereum)
Remix (Browser-Solidity)
solidity-coverage (Solcover)
ganache-cli (test-rpc)
Vyper(viper)
OpenZeppelin Contracts(OpenZeppelin Solidity, Zeppelin Solidity)
OpenZeppelin SDK(ZeppelinOS)
OpenZeppelin starter kit(ZEPKIT)