[
https://issues.apache.org/jira/browse/GEODE-8168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17113381#comment-17113381
]
ASF GitHub Bot commented on GEODE-8168:
---------------------------------------
lgtm-com[bot] commented on pull request #5145:
URL: https://github.com/apache/geode/pull/5145#issuecomment-632222963
This pull request **introduces 1 alert** when merging
88207102901c01f9ece3f771ecaf8eb6288d790e into
07bf3dd827f29a5deb8619f79203d94847a1a823 - [view on
LGTM.com](https://lgtm.com/projects/g/apache/geode/rev/pr-cd7393a609c32b83904400f15c3be9d2ff7efd7f)
**new alerts:**
* 1 for Useless null check
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Redis pipelined command responses can be corrupted
> --------------------------------------------------
>
> Key: GEODE-8168
> URL: https://issues.apache.org/jira/browse/GEODE-8168
> Project: Geode
> Issue Type: Bug
> Components: redis
> Reporter: Jens Deppe
> Assignee: Jens Deppe
> Priority: Major
>
> Redis clients can send pipelined commands where commands are sent as batches.
> Responses are expected in the same order as the commands.
> Since we switched the responses of PUBLISH commands to be asynchronous, now
> command responses can be interleaved incorrectly which results in clients to
> break. For example the client is expecting a response from PUBLISH but,
> instead, gets a response to HMSET.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
