XREAD behavior when COUNT is not provided but BLOCKING is provided #308TDIGEST.ADD,TDIGEST.BYRANK,TDIGEST.BYREVRANK,TDIGEST.CDF, TDIGEST.CREATE, TDIGEST.INFO,
+ TDIGEST.MAX, TDIGEST.MERGE, TDIGEST.MIN, TDIGEST.QUANTILE, TDIGEST.RANK, TDIGEST.RESET, TDIGEST.REVRANK,
+ TDIGEST.TRIMMED_MEAN.Self from typing vs. typing_extensionFAKEREDIS_LUA_VERSION #287++Note: Since connection params are defaulted to be the same between async and sync connections, different FakeRedis +connections with the same connection params (or without connection parameters) will share the same server data +structure.
+
xinfo_stream raises exception when stream does not exist #296TOPK.INFO, TOPK.LIST, TOPK.RESERVE,
+ TOPK.ADD, TOPK.COUNT, TOPK.QUERY, TOPK.INCRBY) #278@testtools.run_test_if_redispy_verXREAD bug #256PUBSUB NUMPAT #195, SSUBSCRIBE #199, SPUBLISH #198,
+ SUNSUBSCRIBE #200, PUBSUB SHARDCHANNELS #196, PUBSUB SHARDNUMSUB #197We'd like to thank all the contributors who worked on this release!
+ +version for async FakeRedis #205BLMOVE #182,HRANDFIELD #156JSON.MSETConnection.read_response arguments used in redis-py 4.5.5 and 5.0.0XREAD #147FakeConnection.xrangexrevrangeXTRIMMAXLEN, MAXID, LIMIT arguments for XADD commandZRANGE arguments for ZRANGE command #127JSON.ARRINDEX, JSON.OBJLEN, JSON.OBJKEYS ,
+ JSON.ARRPOP, JSON.ARRTRIM, JSON.NUMINCRBY, JSON.NUMMULTBY,
+ XADD, XLEN, XRANGE, XREVRANGEJSON.TYPE, JSON.ARRLEN and JSON.ARRAPPENDstreams_mixin.py and test_streams_commands.pyFull Changelog: https://github.com/cunla/fakeredis-py/compare/v2.5.0...v2.6.0
+BITPOS (bitmap command) (#112)We'd like to thank all the contributors who worked on this release!
+ +Full Changelog: https://github.com/cunla/fakeredis-py/compare/v2.4.0...v2.5.0
+Full Changelog: https://github.com/cunla/fakeredis-py/compare/v2.3.0...v2.4.0
+GETEX (#102)JSON.STRAPPEND (json command) (#98)JSON.STRLEN, JSON.TOGGLE and fix bugs with JSON.DEL (#96)PUBSUB CHANNELS, PUBSUB NUMSUBFull Changelog: https://github.com/cunla/fakeredis-py/compare/v2.2.0...v2.3.0
+JSON.CLEAR (#87)Full Changelog: https://github.com/cunla/fakeredis-py/compare/v2.1.0...v2.2.0
+We'd like to thank all the contributors who worked on this release!
+@hyeongguen-song, @the-wondersmith
+Full Changelog: https://github.com/cunla/fakeredis-py/compare/v2.0.0...v2.1.0
+Full Changelog: https://github.com/cunla/fakeredis-py/compare/v1.10.1...v2.0.0
+zmscore by @the-wondersmith in #67Full Changelog: https://github.com/cunla/fakeredis-py/compare/v1.10.0...v1.10.1
+GETDEL and SINTERCARD support in #57BZPOPMIN/BZPOPMAX support in #60Full Changelog: https://github.com/cunla/fakeredis-py/compare/v1.9.4...v1.10.0
+Full Changelog: https://github.com/cunla/fakeredis-py/compare/v1.9.2...v1.9.3
+Full Changelog: https://github.com/cunla/fakeredis-py/compare/v1.9.1...v1.9.2
+Full Changelog: https://github.com/cunla/fakeredis-py/compare/v1.9.0...v1.9.1
+Full Changelog: https://github.com/cunla/fakeredis-py/compare/v1.8.2...v1.9.0
+publish GitHub action to create an issue on failure by @terencehonles
+ in #33release draft job in #37Full Changelog: https://github.com/dsoftwareinc/fakeredis-py/compare/v1.8.1...v1.8.2
+Full Changelog: https://github.com/dsoftwareinc/fakeredis-py/compare/v1.8...v1.8.1
+Full Changelog: https://github.com/dsoftwareinc/fakeredis-py/compare/v1.7.6.1...v1.8
+redis.asyncio by @zhongkechen in #10Full Changelog: https://github.com/dsoftwareinc/fakeredis-py/compare/v1.7.5...v1.7.6
+Full Changelog: https://github.com/dsoftwareinc/fakeredis-py/compare/v1.7.4...v1.7.5
+Full Changelog: https://github.com/dsoftwareinc/fakeredis-py/compare/1.7.1...v1.7.4
+ + + + + + + + + + + + + + + + + + +First off, thanks for taking the time to contribute! ❤️
+All types of contributions are encouraged and valued. +See the table of contents for different ways to help and details about how this project handles +them. Please make sure to read the relevant section before making your contribution. It will make it a lot easier for +the maintainers and smooth out the experience for all involved. The community looks forward to your contributions. 🎉
+++And if you like the project, but just don't have time to contribute, that's fine.
+There are other easy ways to support the project and show your appreciation, which we would also be very happy about:
++
+- Star the project
+- Tweet about it
+- Refer to this project in your project's readme
+- Mention the project at local meetups and tell your friends/colleagues
+
This project and everyone participating in it is governed by the +fakeredis Code of Conduct. +By participating, you are expected to uphold this code. Please report unacceptable behavior +to daniel@moransoftware.ca.
+++If you want to ask a question, we assume that you have read the +available Documentation.
+
Before you ask a question, it is best to search for existing Issues that +might help you. In case you have found a suitable issue and still need clarification, you can write your question in +this issue. It is also advisable to search the internet for answers first.
+If you then still feel the need to ask a question and need clarification, we recommend the following:
+We will then take care of the issue as soon as possible.
+ + +++Legal Notice ¶
+When contributing to this project, you must agree that you have authored 100% of the content, that you have the +necessary rights to the content and that the content you contribute may be provided under the project license.
+
A good bug report shouldn't leave others needing to chase you up for more information. +Therefore, we ask you to investigate carefully, collect information and describe the issue in detail in your report. +Please complete the following steps in advance to help us fix any potential bug as fast as possible.
+++You must never report security related issues, vulnerabilities or bugs, including sensitive information +to the issue tracker, or elsewhere in public. +Instead, sensitive bugs must be sent by email to daniel@moransoftware.ca.
+
We use GitHub issues to track bugs and errors. If you run into an issue with the project:
+Once it's filed:
+needs-repro. Bugs
+ with the needs-repro tag will not be addressed until they are reproduced.needs-fix, as well as possibly other tags (such
+ as critical), and the issue will be left to be implemented by someone.This section guides you through submitting an enhancement suggestion for fakeredis, including completely new features +and minor improvements to existing functionality. Following these guidelines will help maintainers and the community +to understand your suggestion and find related suggestions.
+Enhancement suggestions are tracked as GitHub issues.
+Unsure where to begin contributing? You can start by looking through +help-wanted issues.
+Never contributed to open source before? Here are a couple of friendly +tutorials:
+ +pip install poetrypoetry installpoetry run pytest -vdocker-compose up redis6 or docker-compose up redis7 to run redis.poetry run pytest -v --cov=fakeredis --cov-branch
+ and then you can run coverage report.docs/ folder.Taken from conventional commits
+ +The commit contains the following structural elements to communicate intent to the consumers of your library:
+fix: a commit of the type fix patches a bug in your codebase (this correlates with PATCH in Semantic Versioning).feat: a commit of the type feat introduces a new feature to the codebase (this correlates with MINOR in Semantic
+ Versioning).BREAKING CHANGE: a commit that has a footer BREAKING CHANGE:, or appends a ! after the type/scope, introduces a
+ breaking API change (correlating with MAJOR in Semantic Versioning). A BREAKING CHANGE can be part of commits of any
+ type.fix: and feat: are allowed, for example, @commitlint/config-conventional (based on the Angular
+ convention) recommends build:, chore:, ci:, docs:, style:, refactor:, perf:, test:, and others.BREAKING CHANGE: <description> may be provided and follow a convention similar to
+ git trailer format.Additional types are not mandated by the Conventional Commits specification, and have no implicit effect in Semantic +Versioning (unless they include a BREAKING CHANGE). A scope may be provided to a commit’s type, to provide additional +contextual information and is contained within parenthesis, e.g., feat(parser): add ability to parse arrays.
+If you wish to be added to the project team as a collaborator, please send +a message to daniel@moransoftware.ca with explanation.
+ + + + + + + + + + + + + + + +The legal stuff.
+BSD 3-Clause License
+Copyright © 2022-, Daniel Moran, 2017-2018, Bruce Merry, 2011 James Saryerwinnie, +All rights reserved.
+Redistribution and use in source and binary forms, with or without +modification, are permitted provided that the following conditions are met:
+Redistributions of source code must retain the above copyright notice, this + list of conditions and the following disclaimer.
+Redistributions in binary form must reproduce the above copyright notice, + this list of conditions and the following disclaimer in the documentation + and/or other materials provided with the distribution.
+Neither the name of the copyright holder nor the names of its + contributors may be used to endorse or promote products derived from + this software without specific prior written permission.
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" +AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE +DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE +FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR +SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER +CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, +OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE +OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+ + + + + + + + + + + + + + + +