Ben Sheldon [he/him]

Also, I should comment that I appreciate you using Github Issues for tracking outstanding features/bugs rather than littering the code with 'todos'. Project management: you're doing it right.

As a starting place, here are the test helpers that I include in projects (The `VanityDispatcher` object is described in #379): ```ruby module VanityHelpers def vanity_stub_choice(vanity_id:, experiment_id:, choice:) @stubbed_experiments.add(experiment_id) VanityDispatcher.new(vanity_id).within_context...

The underlying issue seems to be that the message is being generated by the Options parser, which somewhat makes sense given that the Options parser isn't (currently) responsible for environment...

oops, sorry this got submitted in a half-written state. Cat on keyboard problems 😸

@presidentbeef I updated the code based on your feedback. Thank you! 🙏🏻 I also made one behavior change: I added a method called `string_or_modified_string?` that recurses down the target to...

> In real code, would we expect to see string literals like the test cases? 🤔 This was the code we discovered (lightly anonymized): ```ruby result = @active_record_resource.a_hash_value .keys .select...

The best best way to stop and discard is to restart your worker or web-async processes. Jobs marked "running" in the Dashboard means that the record has been Advisory Locked;...

Also, thinking about longer-term features (not to distract from your current incident), there is discussion in #509 about a feature to kill a process from the Dashboard.

@34code thank for suggesting `ActiveJob-traffic_control`! I wasn't aware of that gem; and it's good to know there is an existing option until the feature exists in GoodJob. I'd like to...

@aried3r thank you for sharing that! It's helpful to have the strategies enumerated. The strategy I'm thinking of is a moving window, because I think that would be easiest to...