~singpolyma/sgx-jmp

sgx-jmp/test d---------
Merge branch 'snikket'

* snikket:
  Initial bare-bones admin command for launching a snikket instance
Merge branch 'limit-credit-card-amount'

* limit-credit-card-amount:
  Limit size of credit card transaction by trust level
Limit size of credit card transaction by trust level
Merge branch 'limit-top-up-take-2'

* limit-top-up-take-2:
  Only one credit card transaction per customer per day
Only one credit card transaction per customer per day
Initial bare-bones admin command for launching a snikket instance
Fix test broken by hotfix
Revert "Merge branch 'limit-top-up-freq'"

This reverts commit 7a28753d7df5d7d6f5f890d302634b1bdbd25f73, reversing
changes made to e4ec9b8eb368ed0997887ebd99f8c79982640d20.
Merge branch 'limit-top-up-freq'

* limit-top-up-freq:
  Only allow one credit card transaction per customer per day
Only allow one credit card transaction per customer per day
Merge branch 'cancel-account'

* cancel-account:
  Admin command to cancel customer
  Move Customer factory/extractor to Customer
Admin command to cancel customer

Notify customer
Deregister from SGX
Deregister from Cheogram
Disconnect from Bandwidth
	If on special list, move intead of disconnect
Merge branch 'more-admin-info'

* more-admin-info:
  Test Admin Info with Numbers
  Refetch Customer on Repeated Customer Info Calls
  Trust Level in Customer Info
  Show Callability State in Customer Info
  PromiseHash
  No Settled Transactions is 0, not Null
Test Admin Info with Numbers

My current two AdminInfo tests have unregistered customers because it's
easier, but it means that some parts of the logic don't get tested.

This one digs a bit deeper to test this part of the forms, but it
requires injecting a repo
Trust Level in Customer Info

We have this thing, so we should probably be able to see it
Show Callability State in Customer Info

This shows relatively easily which class a given user finds themselves
in.

Whether they can't call because they have no balance, or if they have
lots of room, or if they're being asked.

Hopefully this will make it easier to tell at a glance if a calling
issue is due to a few things.
Revert "Merge branch 'three_d_secure'"

This reverts commit 36f441c031a5318385ec78d7d2e021a8e2fab186, reversing
changes made to 3b0ae3c9387d3be41b30bd6dd4552ff0a841d8ed.
Merge branch 'three_d_secure'

* three_d_secure:
  Send 3DS id when making a transaction
Merge branch 'change-billing-lock'

* change-billing-lock:
  ExpiringLock instead of require expired
  Atomic ExpiringLock
Send 3DS id when making a transaction
Next