Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Jan 31 22:22
    reyeshh commented #757
  • Jan 31 20:00

    unnawut on 489-upgrade

    Prepare commands and docs for v… Bump up to v.1.1.0-pre.2 (#741) Fix documentation downloading s… and 10 more (compare)

  • Jan 31 18:06
    sirn synchronize #763
  • Jan 31 18:06

    sirn on 756-assets-path-e2e

    Move public/ and private/ into … (compare)

  • Jan 31 17:22
    sirn synchronize #763
  • Jan 31 17:22

    sirn on 756-assets-path-e2e

    Use MFA function to resolve dis… Remove relic of the past. Refactor dist_path/0 into stati… and 1 more (compare)

  • Jan 31 13:00

    jarindr on 570-revamp-account-base-admin-panel

    add user account service and pa… add admin page list (compare)

  • Jan 31 11:49
    wafflebot[bot] labeled #570
  • Jan 31 11:49
    wafflebot[bot] assigned #570
  • Jan 31 11:49

    jarindr on 570-revamp-account-base-admin-panel

    test side nav V2 fix route account base rearrange menu and 17 more (compare)

  • Jan 31 11:44
    ripzery edited #719
  • Jan 31 11:44
    ripzery edited #719
  • Jan 31 11:44
    ripzery edited #719
  • Jan 31 11:43
    ripzery synchronize #719
  • Jan 31 11:43

    ripzery on 335-implement-pagination-via-start-id

    :pencil: Update swagger :bug: Fix unhandled error unaut… :pencil: Add `TODO` for removin… and 1 more (compare)

  • Jan 31 11:42
    jarindr opened #764
  • Jan 31 10:34

    unnawut on 489-upgrade

    Bring back microseond timestamp… Upgrade Sentry (compare)

  • Jan 31 10:27
    ripzery edited #719
  • Jan 31 10:06
  • Jan 31 09:53
    sirn commented #763
Unnawut Leepaisalsuwanna
@unnawut
@antigravitysystem @atestpk_twitter This pre-release fixes the issues you were having as well. ;)
Unnawut Leepaisalsuwanna
@unnawut
Hi everyone! v1.1.0 has arrived. Enjoy!
https://github.com/omisego/ewallet/releases/tag/v1.1.0
Johnny Jiang
@antigravitysystem
Some ewallet UI/UX suggestion:
  1. the token can be duplicated, eg: I can create another token called OMG
  2. the token should have some symbol restriction, eg: I can create another token call ,000 OMG which could lead to some confusing problem in the future.
Johnny Jiang
@antigravitysystem
alt
Johnny Jiang
@antigravitysystem
Or perhaps the UI can display the token ID somewhere on balance column
Unnawut Leepaisalsuwanna
@unnawut

Johnny, you’re right! We actually intended not to enforce rules on the name and symbol. And we only use the token ID as the identifier.

This is because we can’t enforce upstream (the blockchain) to follow our rules. Also if an admin decides to mischief by abusing the token name, the problem is inherently much bigger as the admin who can create a token can abuse in many other ways with his/her granted role.

Having said that, we’re integrating Ethereum as we speak, and we definitely have to consider that once we start to allow ERC-20 token imports from the blockchain.
Your suggestion that the token ID should be displayed is a very good point though. We’ll add that in future releases. ❤️
Hillmer Reyes
@hiremu
Version 1.1. is looking good! Thanks for that.
Hillmer Reyes
@hiremu
I am considering AWS Fargate to run the containers in a production environment. I´ve been testing it using https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-cli-tutorial-fargate.html as a guideline.
However, I cannot figure out how to use the docker-compose run commands through the AWS tools.
ecs-cli compose run ewallet "initdb"
ecs-cli compose run ewallet "seed"
ecs-cli compose service up
Tried the above commands and they seem to do something, but not the desired outcome.
Any thoughts?
Unnawut Leepaisalsuwanna
@unnawut
Hmm I have never used Fargate before. Do you have any output for us to see?
Hillmer Reyes
@hiremu
@unnawut Here are the commands and their output:
https://gist.github.com/reyeshh/4d2686e3cb3c69bb23c4dbff509c15fc
Hillmer Reyes
@hiremu
Beyond the specifics of the scenario described above, the question is how we can deploy a highly available and scalable solution using containers
Kridsada Thanabulpong
@sirn
@reyeshh: interesting, looks like ECS doesn’t support full sets of Docker-Compose v3 definition yet
There doesn’t seems to be a way to run commands via ecs compose either from what I can tell:
Probably the best way to go is to use Helm with ECS, I’m not quite sure how they work together, but will look into it.
Here’s our official Helm chart for eWallet: https://github.com/omisego/charts/tree/master/ewallet
It’s light on documentation at the moment, but it’s what we’re running internally in our GKE cluster.
Hillmer Reyes
@hiremu
@sirn Thanks!
Enya
@enyan94
Hi, I wanted to help out with some GitHub issues. Are there any particular ones that would be best for me to work on right now?
Unnawut Leepaisalsuwanna
@unnawut
@enyan94 You can have a look at https://github.com/omisego/ewallet/labels/flag%2Fgood%20first%20issue%20%3Achildren_crossing%3A These ones are not as heavy-lifting as the rest. Thanks!
Johnny Jiang
@antigravitysystem
I see some error on docker container logs
ewallet             | 03:32:15.530 [info] [swarm on ewallet@0ecc9ee3f173] [tracker:init] started
ewallet             | 03:32:16.030 [error]
ewallet             | ** Cannot get connection id for node :ewallet@0ecc9ee3f173
My docker-compose.yml configuation:
version: "3"
services:
  mailhog:
    image: mailhog/mailhog:latest
    container_name: mailhog
    restart: unless-stopped
    networks:
      - intnet
    ports:
      - 8025:8025

  ewallet:
    image: omisego/ewallet:latest
    container_name: ewallet
    restart: unless-stopped
    networks:
      - intnet
    depends_on:
      - postgres_ewallet
    environment:
      DATABASE_URL: "postgresql://postgres:password@postgres_ewallet:5432/ewallet"
      LOCAL_LEDGER_DATABASE_URL: "postgresql://postgres:password@postgres_ewallet:5432/local_ledger"
      EWALLET_SECRET_KEY: "/FoJwBzsRbG5ntuD4U1jrlfs0z7VRwHro1N+JsuTJcU="
      LOCAL_LEDGER_SECRET_KEY: "/FoJwBzsRbG5ntuD4U1jrlfs0z7VRwHro1N+JsuTJcU="
      SMTP_HOST: mailhog
      SMTP_PORT: 1025
    ports:
      - 4000:4000

  postgres_ewallet:
    container_name: postgres_ewallet
    image: postgres:9.6-alpine
    restart: unless-stopped
    user: postgres
    volumes:
      - ./volumes/database:/var/lib/postgresql/data
    networks:
      - intnet
    environment:
      POSTGRESQL_PASSWORD: password
    healthcheck:
      test: ["CMD-SHELL", "pg_isready", "-U", "postgres"]
      interval: 30s
      retries: 3

networks:
  intnet:
Unnawut Leepaisalsuwanna
@unnawut
@sirn Can you take this one? Seems swarm/node related :point_up:
Enya
@enyan94
Hi, are there any issues on GitHub that you guys need help on outside of those labelled "flag/good first issue"?
Thibault
@T-Dnzt
@enyan94 You can pick anything in the “Buffer/Cleanup” or “Whishlist” columns from Waffle actually (https://waffle.io/omisego/ewallet). Once you’ve picked something, you can let us know in the issue how you’re planning to fix/implement it :)
vipul patel
@vipul-hirani
Hi
How to integrate Omnise Ewallet in my system?
I already setup project in my system using guide
https://github.com/omisego/ewallet
Unnawut Leepaisalsuwanna
@unnawut
Hi vipul, do you mind elaborate your use case a bit? After setting up the eWallet, it totally depends on your use case.
vipul patel
@vipul-hirani
In my project 4 level of money sender and receiver
  1. User send money to distributor.
  2. Distributor send money to the supplier
  3. Supplier send money to cultivate
  4. Cultivator receives money from the supplier

  1. How to create user in e-wallet?
  2. How to work this cycle using block-chain?
Hillmer Reyes
@hiremu
Hi guys. I am having trouble inviting a new member in the Account Settings. Both admin and viewer give me the same error message: "The given redirect_urlis not allowed. Got: 'http://IP-addr:4000/admin/invite/?token={token}&email={email}'. Where can I look to figure out what's going on?
Thibault
@T-Dnzt
Hello @reyeshh, which version of the eWallet are you running?
Hillmer Reyes
@hiremu
Version 1.1 (I installed the stable docker container 4 weeks ago).
Thibault
@T-Dnzt
You need to go on the configuration page and add your URL to the list of allowed URLs
James Kehoe
@jimpeebles
Working on implementing the admin api, trying to create a user but getting error: "Invalid API version. Given: 'application/json, text/plain, /'." Any idea what the issue could be?
For authentication, using OMGProvider Base64(key:secret)
James Kehoe
@jimpeebles
Scratch that, didn't have Accept header set. Now i'm receiving another error - "The provided authentication scheme is not supported." I'm using the api key/secret, not an auth token. Is an auth token required for some requests?
Hillmer Reyes
@hiremu
@T-Dnzt Any documentation or tips on how to view logs , database backup/restore?
Hillmer Reyes
@hiremu
And TLS setup (all for the Docker version)
Hillmer Reyes
@hiremu
A new 1.3 installation seems to work ok, but I'm getting a lot of these errors.
02:46:24.506 [error]
** Cannot get connection id for node :ewallet@97004851eb34
Unnawut Leepaisalsuwanna
@unnawut
Hey reyeshh. Let me bring that to the team and get back to you in a bit.
Hillmer Reyes
@hiremu
@unnawut Great!
Unnawut Leepaisalsuwanna
@unnawut

A new 1.3 installation seems to work ok, but I'm getting a lot of these errors.
02:46:24.506 [error]
** Cannot get connection id for node :ewallet@97004851eb34

Can you let us know a bit more of your setup? The commands used, the docker-compose file, environment variables, etc.

Unnawut Leepaisalsuwanna
@unnawut
I tried to reproduce by following the readme but it’s not showing the error.
Hillmer Reyes
@hiremu

I tried to reproduce by following the readme but it’s not showing the error.

I am following instructions on the the gihub page for docker. Running Ubuntu 18.04 and docker 18.06.1 on Digital Ocean (2GB 1CPU 50GB Disk). I am seeing this in the logs (docker logs WALLET_CONTAINER)

Unnawut Leepaisalsuwanna
@unnawut
I was able to reproduce your issue now but will probably need some more time to look at it. It shouldn’t impact your usage for testing/development since this error is in a cluster feature. omisego/ewallet#1139
Hillmer Reyes
@hiremu

I was able to reproduce your issue now but will probably need some more time to look at it. It shouldn’t impact your usage for testing/development since this error is in a cluster feature. omisego/ewallet#1139

Ok. Thanks!