Skip to content
GitHub Explorer

pwhelan/rustis

View on GitHub ↗Related repositories →

simple in-memory key-value store, inspired by Redis, written in Rust.

active 2025-10-20 → 2025-10-24 (UTC)

Complete coverage26,436 / 26,436 hourly files (100%) · 2 absent upstream2023-08-15 → 2026-08-20 (UTC)
Events
53
Pushes
2
Pull requests
0
Issues
50
Stars
0
Forks
0

Activity over time

Daily event counts in the loaded window

Line chart, 5 days from 2025-10-20 to 2025-10-24. Pushes: 2 total, peak 1 in a day. Pull requests: 0 total, peak 0 in a day. Issues: 50 total, peak 48 in a day. Comments: 0 total, peak 0 in a day. Stars: 0 total, peak 0 in a day.

  • Pushes
  • Pull requests
  • Issues
  • Comments
  • Stars

Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.

Top contributors

Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity

ContributorContributionsPushesPRsComments
pwhelan52200

Recent activity

Latest issues, pull requests and releases

  • Issue#1pwhelan2025-10-24 00:56
    Integrate a modern, structured logging library (like tracing) and get it configured.
  • Issue#3pwhelan2025-10-24 00:56
    Make sure we're logging key events, like:
  • Issue#19pwhelan2025-10-23 01:42
    Add Configuration so that listeners can be define by address, port and protocol.
  • Issue#18pwhelan2025-10-23 01:42
    Implement a dedicated parser and serializer just for this binary format.
  • Issue#17pwhelan2025-10-23 01:42
    Design the structure for this new binary protocol (like message headers and how data is encoded).
  • Issue#17pwhelan2025-10-23 01:42
    Design the structure for this new binary protocol (like message headers and how data is encoded).
  • Issue#17pwhelan2025-10-23 01:42
    Design the structure for this new binary protocol (like message headers and how data is encoded).
  • Issue#17pwhelan2025-10-23 01:42
    Design the structure for this new binary protocol (like message headers and how data is encoded).
  • Issue#17pwhelan2025-10-23 01:42
    Design the structure for this new binary protocol (like message headers and how data is encoded).
  • Issue#17pwhelan2025-10-23 01:42
    Design the structure for this new binary protocol (like message headers and how data is encoded).
  • Issue#16pwhelan2025-10-23 01:42
    Decide on the base binary format for the binary protocol
  • Issue#16pwhelan2025-10-23 01:42
    Decide on the base binary format for the binary protocol
  • Issue#15pwhelan2025-10-23 01:42
    Develop some serious stress tests to confirm the safety and see how fast our key-level locking is when things get busy.
  • Issue#14pwhelan2025-10-23 01:42
    Review other Rust concurrency patterns to make sure we're keeping lock times as short as possible.
  • Issue#14pwhelan2025-10-23 01:42
    Review other Rust concurrency patterns to make sure we're keeping lock times as short as possible.
  • Issue#14pwhelan2025-10-23 01:42
    Review other Rust concurrency patterns to make sure we're keeping lock times as short as possible.
  • Issue#14pwhelan2025-10-23 01:42
    Review other Rust concurrency patterns to make sure we're keeping lock times as short as possible.
  • Issue#14pwhelan2025-10-23 01:42
    Review other Rust concurrency patterns to make sure we're keeping lock times as short as possible.
  • Issue#13pwhelan2025-10-23 01:42
    Research and test key-level locking. Write up a brief describing how it works.
  • Issue#13pwhelan2025-10-23 01:42
    Research and test key-level locking. Write up a brief describing how it works.
  • Issue#13pwhelan2025-10-23 01:42
    Research and test key-level locking. Write up a brief describing how it works.
  • Issue#13pwhelan2025-10-23 01:42
    Research and test key-level locking. Write up a brief describing how it works.
  • Issue#13pwhelan2025-10-23 01:42
    Research and test key-level locking. Write up a brief describing how it works.
  • Issue#13pwhelan2025-10-23 01:42
    Research and test key-level locking. Write up a brief describing how it works.
  • Issue#12pwhelan2025-10-23 01:42
    Implement missing VERBS.

Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 0 stars here means stars gained during the window, not the repo's star count.