active 2026-04-07 → 2026-08-07 (UTC)
Activity over time
Daily event counts in the loaded window
Line chart, 123 days from 2026-04-07 to 2026-08-07. Pushes: 35 total, peak 32 in a day. Pull requests: 8 total, peak 7 in a day. Issues: 35 total, peak 32 in a day. Comments: 1 total, peak 1 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
| Contributor | Contributions | Pushes | PRs | Comments |
|---|---|---|---|---|
| SymoHTL | 72 | 29 | 7 | 1 |
| dependabot[bot] | 7 | 6 | 1 | 0 |
Recent activity
Latest issues, pull requests and releases
- Pull request#252dependabot[bot]2026-08-07 15:16
- Issue#239SymoHTL2026-07-04 11:15Disk multipart Complete rewrites all parts (O(total-size) concat+fsync) instead of referencing them
- Issue comment#97SymoHTL2026-07-04 09:58Bump Microsoft.NET.Test.Sdk from 17.14.1 to 18.7.0
- Pull request#230SymoHTL2026-07-04 05:26
- Pull request#215SymoHTL2026-07-04 04:28
- Pull request#211SymoHTL2026-07-04 04:17
- Issue#108SymoHTL2026-07-04 04:14Route retention/legal-hold replica repairs to re-apply Object Lock state instead of re-PUTting the object body
- Issue#119SymoHTL2026-07-04 04:13Make accepted checksum-algorithm set consistent across the multipart lifecycle so CRC64NVME uploads are not accepted then dead
- Issue#119SymoHTL2026-07-04 04:13Make accepted checksum-algorithm set consistent across the multipart lifecycle so CRC64NVME uploads are not accepted then dead
- Issue#101SymoHTL2026-07-04 03:59Verify per-chunk SigV4 signature chain for signed aws-chunked uploads so body bytes are cryptographically bound
- Issue#165SymoHTL2026-07-04 03:45Object header/attribute nits: default `Content-Type`, `Expires` opaque round-trip, `x-amz-tagging-count` on HEAD, `GetObjectAttributes` ObjectParts
- Issue#114SymoHTL2026-07-04 03:41Reject signed-streaming requests when no signing context is present instead of failing open in trailer-signature validation
- Issue#138SymoHTL2026-07-04 03:16CatalogStorageObjectStateStore materializes the entire bucket catalog on every point lookup
- Issue#164SymoHTL2026-07-04 03:12Error-code granularity: `BucketAlreadyOwnedByYou` not distinguished; `QuotaExceeded -> EntityTooLarge 413`; object-lock-requires-versioning uses `OperationAborted`
- Issue#120SymoHTL2026-07-04 03:09Translate TOCTOU delete/overwrite races on lock-free read and copy-source opens to 404 and open readers with FileShare.Delete
- Pull request#194SymoHTL2026-07-04 03:09
- Pull request#192SymoHTL2026-07-04 03:02
- Issue#131SymoHTL2026-07-04 02:58Verify signed x-amz-content-sha256 payload hash against received body (XAmzContentSHA256Mismatch)
- Pull request#191SymoHTL2026-07-04 02:58
- Issue#129SymoHTL2026-07-04 02:31S3 provider only catches AmazonS3Exception; transport failures (timeouts, resets, DNS) escape untranslated as raw exceptions
- Issue#110SymoHTL2026-07-04 02:20Wrap catalog UpsertObjectAsync demote+insert and RemoveBucketAsync deletes in a transaction to keep IsLatest and bucket/object state atomic
- Issue#110SymoHTL2026-07-04 02:20Wrap catalog UpsertObjectAsync demote+insert and RemoveBucketAsync deletes in a transaction to keep IsLatest and bucket/object state atomic
- Issue#111SymoHTL2026-07-04 02:20Catalog UpsertObjectAsync has no optimistic-concurrency token or transaction, so concurrent writes to the same key lose updates and can create two IsLatest=true rows
- Issue#111SymoHTL2026-07-04 02:20Catalog UpsertObjectAsync has no optimistic-concurrency token or transaction, so concurrent writes to the same key lose updates and can create two IsLatest=true rows
- Issue#147SymoHTL2026-07-04 02:19Multipart error family collapses to `409 InvalidRequest` (InvalidPart / InvalidPartOrder / NoSuchUpload / part-number range / duplicate parts)
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.