Bump mediocregopher/radix to v4

[nghiant3223]

Problem

The ratelimit package currently depends on mediocregopher/radix v3, which does not support context-aware operations.

As a result, when a context is canceled (e.g., due to client timeouts), ratelimit may still:

1. Wait for a connection from the Redis connection pool
2. Execute Redis commands after the request has been canceled

This leads to unnecessary resource usage and potential latency under load.

Proposal

Upgrade to mediocregopher/radix v4, which introduces support for context.Context in command execution.

Benefits

• Proper context cancellation handling
• Reduced resource usage when requests are aborted
• Better integration with modern Go context patterns

[nghiant3223]

Hi @collin-lee. Please take a look. Thank you!

[github-actions]

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or "no stalebot" or other activity occurs. Thank you for your contributions.

[github-actions]

This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as "help wanted" or "no stalebot". Thank you for your contributions.

[upgle]

@nghiant3223 @collin-lee
This is still a valid issue.

I've opened a PR for this #1041,
so could someone please add the "no stalebot" label and reopen it? Thank you.

[collin-lee]

no stalebot

[github-actions]

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or "no stalebot" or other activity occurs. Thank you for your contributions.

[jamesog]

@upgle I was trying to understand the change to the pipeline window. I see in

ratelimit/src/redis/driver_impl.go

Lines 151 to 155 in e9ce92c

	// Set WriteFlushInterval for cluster mode (grouped pipeline uses auto buffering)
	if isCluster && pipelineWindow > 0 {
	poolConfig.Dialer.WriteFlushInterval = pipelineWindow
	logger.Debugf("Cluster mode: setting WriteFlushInterval to %v", pipelineWindow)
	}

that it's only applied for cluster mode. Does that mean it would not have any benefit to single instance mode? I didn't see any mention about this in Radix's docs so wanted to check.

[github-actions]

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or "no stalebot" or other activity occurs. Thank you for your contributions.