5105269223
100%

Ran 28 May 2023 04:10PM UTC

Jobs 1

Files 28

Run time 1s

Badge

Embed ▾

Committed 28 May 2023 04:10PM UTC coverage: 100.0%. Remained the same

Build # 5105269223

Build Type

push

github

Committed by

mbland

Commit Message

Check MAX_BULK_SEND_CAPACITY without count/scan

`elistman send` no longer counts current subscribers before calling
Mailer.BulkCapacityAvailable. Instead, Throttle.BulkCapacityAvailable
now only checks whether MaxBulkSendable is less than SentLast24Hours.

As documented in the README, it's up to the operator to ensure that
MAX_BULK_SEND_CAPACITY is tuned to help avoid exceeding the 24 hour send
quota.

MaxBulkSendable is still computed based on Max24HourSend *
MAX_BULK_SEND_CAPACITY. However, after all that work, I decided I wasn't
comfortable with scanning the table every time to get the count of
subscribers. That count basically doubles the DynamoDB read capacity
cost for every `elistman send`, to avoid what should be a relatively
rare occurence of quota exhaustion.

Run Details

1673 of 1673 relevant lines covered (100.0%)

19.11 hits per line

Jobs

ID	Job ID	Ran	Files	Coverage
1	5105269223.1	28 May 2023 04:10PM UTC	0	100.0	GitHub Action Run

Source Files on build 5105269223

Detailed source file information is not available for this build.

mbland / elistman / 5105269223
100%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 5105269223

mbland / elistman / 5105269223 100%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 5105269223

mbland / elistman / 5105269223
100%

README BADGES
x