-
Notifications
You must be signed in to change notification settings - Fork 985
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
enablePeriodicRefresh has problematic behavior when service is shut down(close)
#3089
opened Dec 18, 2024 by
Kvicii
Add note about shaded jars not being released any more
status: good-first-issue
An issue that can only be worked on by brand new contributors
type: documentation
A documentation update
OutOfMemoryError leads to NullPointerException disabling redis connections
#3087
opened Dec 17, 2024 by
stevenschlansker
Unable to connect to AWS ElastiCache Redis after few days of successful working
#3086
opened Dec 17, 2024 by
srikarrampa
Introduce For an external project and not something we can fix
status: waiting-for-triage
Predicate<T extends StatefulConnection>
to ConnectionPoolSupport
to customize pooled connection validation
for: external-project
#3081
opened Dec 16, 2024 by
mp911de
Lettuce 6.2.7, redis 6.2, lettuce-eventExecutorLoop-thread pool LinkedBlockingQueue, fill up memory
status: waiting-for-feedback
We need additional information before we can continue
#3074
opened Dec 11, 2024 by
yaozi899
Migrate to newer versions of the JavaParser library
status: help-wanted
An issue that a contributor can help us with
LettuceConnectionFactory is not establishing the connection when using a Japanese username and password
status: mre-available
Minimal Reproducible Example is available
type: bug
A general bug
Unit test shouldNotEmitEventForAbsentJfrEventType Failed
status: help-wanted
An issue that a contributor can help us with
type: bug
A general bug
type: regression
A regression from a previous release
#3066
opened Dec 2, 2024 by
XuexuanWang
Client-side caching invalidation messages not parsed correctly
status: mre-available
Minimal Reproducible Example is available
type: bug
A general bug
#3064
opened Nov 29, 2024 by
tishun
Refactor An issue we need to discuss as a team to make progress
status: waiting-for-triage
mget
Method in RedisAdvancedClusterReactiveCommandsImpl.java
to Use Java Streams for Improved Readability and Efficiency
for: team-attention
#3060
opened Nov 23, 2024 by
ori0o0p
Questions about the acquire of boundAsyncPool
for: team-attention
An issue we need to discuss as a team to make progress
status: waiting-for-triage
#3055
opened Nov 19, 2024 by
soafftt
Abnormal Mget latency increase issue
for: team-attention
An issue we need to discuss as a team to make progress
status: waiting-for-triage
#3031
opened Oct 29, 2024 by
ackerL
Unable to connect to AWS ElastiCache cluster
status: waiting-for-feedback
We need additional information before we can continue
#3018
opened Oct 16, 2024 by
hudda10
SentinelConnector set KnownNodes empty during redis failover, which causes app could not access redis any more
for: team-attention
An issue we need to discuss as a team to make progress
status: help-wanted
An issue that a contributor can help us with
type: feature
A new feature
#3017
opened Oct 16, 2024 by
jiajunsu
None recovering Redis command timed out
status: waiting-for-feedback
We need additional information before we can continue
#3010
opened Oct 11, 2024 by
mshahmoradi87
Support storing initialization vector alongside ciphertext when using CipherCodec
status: help-wanted
An issue that a contributor can help us with
type: feature
A new feature
#2994
opened Sep 26, 2024 by
tmccombs
Getting "org.springframework.dao.QueryTimeoutException: Redis command timed out" sporadically in Springboot Cloud Gateway code.
status: waiting-for-feedback
We need additional information before we can continue
#2984
opened Sep 10, 2024 by
sanketkeskar
Why bitField offset argument is int type?
for: team-attention
An issue we need to discuss as a team to make progress
status: good-first-issue
An issue that can only be worked on by brand new contributors
type: bug
A general bug
fix: activation command may get retried in a different connection, or failed due to queue full or dangled due to auto flush is false
status: waiting-for-feedback
We need additional information before we can continue
#2963
opened Aug 16, 2024 by
okg-cxf
Revise the Advanced usage section
type: documentation
A documentation update
#2954
opened Aug 9, 2024 by
tishun
Previous Next
ProTip!
Find all open issues with in progress development work with linked:pr.