For the past two weeks, we have been focused on testing, debugging and fixing bugs in version 1.1. We’ve also spent time preparing and planning our next work cycle, which will include Ethereum integration.

Completed

Here are the main items we’ve knocked out since the last update:

Improvements:

  • Allow the retrieval of balances for multiple wallets from local ledger #629
  • E2E (end to end) storage setup #637
  • Increase asynchronous tests and test coverage #630 #643
  • Add Dialyzer in build steps #650
  • Refactored URL Dispatcher and server tasks #656
  • Improved Slack notifications #659
  • Updated stale documentation #662
  • Better handling for export failures #663
  • Refactored config command to prevent double-argv parsing #665

Bug fixes:

  • Added missing redirect_url parameter for me.update_email doc endpoint #638
  • Fixed {:error, noent} error in EWalletConfig.Storage.LocalTest #641
  • Handle Goth supervisor properly (start/stop when needed) #642
  • Fixed json validation for configuration #644
  • Moved InvalidDateFormatError from EWallet.Errors to Utils.Errors #646
  • Fixed error 500 when updating an email with an invalid email format #648
  • Fixed a race condition while testing for simultaneous transfers on an insufficient fund #654
  • Exclude soft-deleted API keys from /api_key.all #658
  • Fixed test factory inserting roles with conflicting priorities #669
  • Minor fix for user email update #670
  • Corrected some bad grammar and typos within the application #671
  • Changed Mix.env() to Application.get_env(:ewallet, :env) #675

In review

These tasks have been completed, pending review by wallet team admins:

  • Fixed configuration string splitting #672
  • Cleaned up README #674
  • Better wallet endpoints and retrieval in the admin panel #679

In progress

These are the tasks we’re focusing on right now:

  • Planning and design for the initial blockchain features!

We’re dealing with some last minute bugs, but the final release of 1.1 is well under way. We’re keeping it as a release candidate until we’re satisfied we are putting out a fully-tested version of the eWallet.

As always, you can also follow our progress on the eWallet Waffle board and in our GitHub Milestones page.

Did this answer your question?