Skip to content

Prepare for 2.2.2 version.#349

Merged
fcostaoliveira merged 10 commits into2.2from
cp-to-v2.2
Feb 26, 2026
Merged

Prepare for 2.2.2 version.#349
fcostaoliveira merged 10 commits into2.2from
cp-to-v2.2

Conversation

@fcostaoliveira
Copy link
Collaborator

@fcostaoliveira fcostaoliveira commented Feb 26, 2026

Summary

  • Cherry-pick of bugfixes and non-feature updates from master to the 2.2 branch (post 2.2.1)

Cherry-picked PRs:

Test plan

  • CI passes on all workflows
  • Cursor bugbot has 0 issues

Note

Medium Risk
Moderate risk due to changes in client connection lifecycle/idle detection and significant CI workflow restructuring; most other edits are formatting/doc/version bumps with low runtime impact.

Overview
Prepares the 2.2.2 release by bumping configure.ac version and ensuring user-supplied CXXFLAGS are respected.

Adds repo-wide clang-format support (.clang-format, make format/format-check) and a new Code Style GitHub Action that enforces formatting in PRs; includes large-scale formatting-only reflows across multiple C/C++ files and vendored headers.

Refactors GitHub Actions to run on release branches only, splits sanitizer workflows (ASAN/TSAN/UBSAN) and Ubuntu CI into separate build and matrix test jobs with uploaded artifacts, and updates org/repo references from RedisLabs/redislabs to redis (including Docker workflow gating).

Fixes a test-completion hang scenario by extending the connection manager interface with all_connections_idle() and adding disconnect_all()/idle detection in client, enabling cleaner shutdown when multiple connections still have pending responses.

Written by Cursor Bugbot for commit 9180243. This will update automatically on new commits. Configure here.

fcostaoliveira and others added 7 commits February 26, 2026 14:27
Cherry-picked and re-applied clang-format configuration, CI workflow,
Makefile targets, and DEVELOPMENT.md docs from master. Source files
reformatted against the 2.2.x branch codebase.
* Concurrent ubuntu test jobs for faster CI

* Prevent duplicate workflow runs on push+PR by filtering branches

* Fixed coverage workflow

* Concurrent ASAN, TSAN, and UBSAN test jobs using matrix strategy
* Fix rate-limit induced hanging at test completion

* include a null check for conns in all_connections_idle

* Remove crufty ctx reference

* Extend CI with higher shard count scenario.

* Extra logging on 99 shards scenario

* Verbose was already defined on CI. Using 49 shards to expedite CI

* Using RLTEST_DEBUG to avoid overriding old behaviour

* Shard count 99 in rate-limiting test

---------

Co-authored-by: fcostaoliveira <filipe@redis.com>
Add documentation to help AI assistants work effectively with the
memtier_benchmark codebase, following the https://agents.md/ conventions.

AGENTS.md includes:
- Project overview and repository structure
- Build system and commands (autotools)
- Code style (clang-format)
- Testing with RLTest (standalone, cluster, TLS, sanitizers)
- Key technical details
- Common development tasks
- Debugging guide (GDB, crash handler, core dumps, sanitizers)
- License header requirements

CLAUDE.md points to AGENTS.md for shared guidelines.

References:
- https://agents.md/ - Standard for AI agent documentation
- https://docs.anthropic.com/en/docs/agents - Anthropic agent guidelines
@fcostaoliveira
Copy link
Collaborator Author

cursor review

@jit-ci
Copy link

jit-ci bot commented Feb 26, 2026

🛡️ Jit Security Scan Results

CRITICAL HIGH MEDIUM

✅ No security findings were detected in this PR


Security scan by Jit

Add branch pattern '[0-9]+.[0-9]+' to push/pull_request triggers for
ci, code-style, asan, tsan, and ubsan workflows so CI runs on PRs
targeting release branches like 2.2.
@fcostaoliveira fcostaoliveira changed the title Cherry-pick bugfixes and updates to 2.2 branch Cherry-pick bugfixes and updates to 2.2 branch. Prepare for 2.2.2 version Feb 26, 2026
fcostaoliveira and others added 2 commits February 26, 2026 16:43
The rate-limiting timer was only created on the first connection
(when get_reqs_processed() == 0). After a reconnect triggered by
--reconnect-interval, disconnect() properly freed the timer, but
handle_event() never recreated it because requests had already been
processed. This left m_request_per_cur_interval permanently at 0,
causing fill_pipeline() to return immediately on every call.

Move timer creation outside the first-connection guard so it is
recreated on every successful connect/reconnect when m_event_timer
is NULL.

Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
@fcostaoliveira
Copy link
Collaborator Author

cursor review

Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Bugbot reviewed your changes and found no new issues!

Comment @cursor review or bugbot run to trigger another review on this PR

@fcostaoliveira fcostaoliveira changed the title Cherry-pick bugfixes and updates to 2.2 branch. Prepare for 2.2.2 version Prepare for 2.2.2 version. Feb 26, 2026
@fcostaoliveira fcostaoliveira merged commit 3347cb9 into 2.2 Feb 26, 2026
45 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants