It is absolutely a pain and its a bit unfortunate its still in use. this
was the longest it took me to update 4 lines in a repo that I can remember.
That said, it has been committed. I don't see it yet reflected on the live
page but I assume (hope) there is some amount of auto-deployment. Otherwis
.
> That said, it has been committed. I don't see it yet reflected on the live
> page but I assume (hope) there is some amount of auto-deployment.
>
I think it's hourly, and I see it now at
https://incubator.apache.org/ip-clearance/cassandra-easy-cass-stress.html
Please merge the PR before
> This makes me really, really concerned with how it scales, and how likely it
> is to be able to schedule automatically without blowing up.
It seems to me that resource-aware throttling would be the solution here, or
from a more primitive case, just hard bounding threadpool size, throughput
ra
> breaking it up into several smaller patches.
This immediately made me think of poor Blake and the "remove singletons"
sisyphean task. That was 700 smaller patches! :D Which to be fair isn't
"several" by any measure, but...
All of which is to say - it's a continuum between big-banging it in o
Jordan - could you please open an INFRA ticket for them to look into this
issue?
On Sun, May 11, 2025 at 12:34 PM Jordan West wrote:
> It is absolutely a pain and its a bit unfortunate its still in use. this
> was the longest it took me to update 4 lines in a repo that I can remember.
> That sa
The infra ticket is here and has been open for a bit
https://issues.apache.org/jira/browse/INFRA-26785
Will merge the PR when Im back at my machine
Jordan
On Sun, May 11, 2025 at 14:44 Mick Semb Wever wrote:
>
> .
>
>
>> That said, it has been committed. I don't see it yet reflected on th
