futureporn-qa lacks Mux allocator #66

New Issue

Closed

opened 2023-10-03 07:30:17 +00:00 by CJ_Clippy · 0 comments

CJ_Clippy commented

2023-10-03 07:30:17 +00:00

Owner

Regression during September update.

I pulled Mux processing in part due to it's potential to overcharge me for accidental allocations. An allocation mistake in late September caused a $500 bill.

The other part was related to rushing #35, quickly refactoring the old futureporn-qa into something more distributed without porting over every task runner.

New update needs to implement strict controls for adding to Mux, where a human operator must approve every allocation.

Regression during September update. I pulled Mux processing in part due to it's potential to overcharge me for accidental allocations. An allocation mistake in late September caused a $500 bill. The other part was related to rushing #35, quickly refactoring the old futureporn-qa into something more distributed without porting over every task runner. New update needs to implement strict controls for adding to Mux, where a human operator must approve every allocation.

CJ_Clippy added the

label 2023-10-03 07:30:17 +00:00

CJ_Clippy closed this issue

2024-01-11 12:05:13 +00:00

Sign in to join this conversation.

No Label

No Milestone

No project

No Assignees

1 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: futureporn/pm#66

No description provided.