Skip to content

Conversation

@leozc
Copy link
Contributor

@leozc leozc commented Apr 1, 2025

What changed? Why?

  1. This change includes a list of improvements from CipherOwl based on the original ChainStorage from Coinbase
  2. Key improvement:
    2.1 Adding LTC / Tron Support,
    2.2 Adding ZSTD support
    2.3 Making ChainStorage more friendly for opensource / k8s environment

How did you test the change?

  • [ X ] unit test
  • [ X ] integration test
  • functional test
  • adhoc test (described below)
  • running in production

ImNumber4 and others added 30 commits January 24, 2024 19:36
…replicator

# Conflicts:
#	internal/workflow/replicator.go
Signed-off-by: Henry Yang <henry.yang@cipherowl.com>
PikaZ76 and others added 30 commits October 30, 2025 19:34
…-handling

fix: Add watermark-based visibility control for Postgres metastorage
retry workflow for create temporal session failure by continue as new
Support {VAR} env placeholders in endpoint URLs
Add two layers of protection against truncated/corrupted JSON responses
from Tron REST API endpoints:

1. Content-Length validation in REST API client: Detects when actual
   response bytes don't match the Content-Length header, indicating
   premature connection close. This is retried at the HTTP level.

2. JSON validation in Tron client: Validates response is valid JSON
   before attempting to unmarshal. Catches cases where Content-Length
   is not present (chunked encoding) or data is corrupted.

Both validations include logging with response preview for debugging.
Errors are marked as retryable to allow automatic retry.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
…onse

fix: Add validation for truncated JSON responses in Tron client
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.