-
Notifications
You must be signed in to change notification settings - Fork 1k
Issues: redis/lettuce
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
The KEYS command needs to be keyless
type: breaking
Breaking change
type: improvement
An improvement to the existing implementation
#3311
opened May 27, 2025 by
tishun
Avoid calling URI.toString when populating tracing span tags
status: waiting-for-triage
type: improvement
An improvement to the existing implementation
#3308
opened May 23, 2025 by
GnawNom
Support Redis 8 vector sets
type: feature
A new feature
type: tracking-issue
An issue container, effectively an epic
#3296
opened May 19, 2025 by
tishun
Consider upgrading to Netty 4.2
status: waiting-for-triage
type: improvement
An improvement to the existing implementation
#3294
opened May 15, 2025 by
mp911de
Improvements to the Client-Side Caching feature
type: tracking-issue
An issue container, effectively an epic
#3288
opened May 7, 2025 by
tishun
Undefined results when using ReadFrom with SCAN family commands
status: waiting-for-triage
#3287
opened May 6, 2025 by
Dishant18
Lettuce clientOptions config & NioSocketChannel may trigger memory leak
status: waiting-for-triage
#3286
opened May 3, 2025 by
adar-v
Change default to Breaking change
type: improvement
An improvement to the existing implementation
epoll
and not io_uring
type: breaking
#3277
opened Apr 25, 2025 by
tishun
SentinelAclIntegrationTests needs to be enabled again
type: bug
A general bug
#3274
opened Apr 25, 2025 by
tishun
Fix Thread-safety race condition in AbstractRedisReactiveCommands.getScheduler()
status: feedback-reminder
We've sent a reminder that we need additional information before we can continue
status: waiting-for-feedback
We need additional information before we can continue
#3272
opened Apr 24, 2025 by
ori0o0p
use RedisCommands<String, byte[]> zadd set member string Exception
status: feedback-reminder
We've sent a reminder that we need additional information before we can continue
status: waiting-for-feedback
We need additional information before we can continue
#3267
opened Apr 18, 2025 by
xiaoliefengfeng
Enforce Noninstantiability in Utility Class with Private Constructor
type: breaking
Breaking change
#3265
opened Apr 18, 2025 by
ori0o0p
Previous Next
ProTip!
Follow long discussions with comments:>50.