bugs when someone sends invalid values

[girino]

The ponzi was breaking everytime someone sent values above the top limit. At first it wouldn't display anything, then, when i added checks for null/undefined fields. the values where all wrong. Figured out that the "amount" for those guys was accounted for, but not the "topay", which is always 0. I now ignore both.

[PawlicaWeb]

But that's the correct behaviour. Transactions with values under minimum or over maximum are treated as a donation.

[girino]

I don't think you understand. This is not the current behaviour. The javascript for the system stops working whenever one of those "donations" occur, because the it tries to manipulate a null value. The code i submited fixes this bug. Check it out.

[PawlicaWeb]

Okay, but can you at least rename new variables in index.php? 'tmp20140808' doesn't look very good.

[djmalter]

This fixes a small Authentication Key Vault auth bug.

An incomplete sops.azure-kv config with tenantId and clientId, but no clientSecret or clientCertificate, was slipping into the managed identity path. That hides a bad secret and picks the wrong auth mode.

The fix makes that config fail fast. clientId only still uses managed identity, so existing MI setups keep working.

Repro:

Create a decryption secret with:
sops.azure-kv: |
tenantId: some-tenant-id
clientId: some-client-id
Before this patch, TokenCredentialFromAADConfig returns *azidentity.ManagedIdentityCredential and no error.
After this patch, it returns an error.
Validation:
make tidy fmt vet && make test