Merging CipherOwl Improvements #115
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
fix merge error for workflow
Add metrics for replicator
TIT-157 Support BCH and LTC
…replicator # Conflicts: # internal/workflow/replicator.go
TIT-158 continuous replicator
Signed-off-by: Henry Yang <henry.yang@cipherowl.com>
* Remove sdk address
* Port ethereum beacon support
fix compression in replicator
fix replicator to process skipped blocks
retry workflow for create temporal session failure by continue as new
add abstract
Support {VAR} env placeholders in endpoint URLs
Feature/seismic
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
* chore: Migrate AWS SDK from v1 to v2 This commit completes the migration from github.com/aws/aws-sdk-go (v1) to github.com/aws/aws-sdk-go-v2 (v2) to address CVE-2020-8911 security vulnerability. Changes: - internal/aws/*: Rewrite config and retryer for v2, delete session.go - internal/storage/metastorage/dynamodb/*: Migrate to v2 DynamoDB API - dynamodbattribute -> attributevalue - types.AttributeValue instead of *dynamodb.AttributeValue - internal/s3/*: Migrate to v2 S3 API with manager package - internal/storage/blobstorage/s3/*: Update ACL to use v2 types - internal/dlq/sqs/*: Migrate to v2 SQS API - cmd/admin/migrate.go: Update DynamoDB client usage - Regenerate all mocks for v2 interfaces - Update test files to use v2 SDK types The v1 SDK has been removed from direct dependencies in go.mod. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * remove unused file * chore: Upgrade Go version from 1.22 to 1.24 in Dockerfile Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * fix: Use thread-safe WriteAtBuffer from AWS SDK v2 for S3 downloads Replace custom writeAtBuffer implementation with manager.WriteAtBuffer from AWS SDK v2. The S3 Downloader uses 5 concurrent goroutines by default, and the custom implementation was not thread-safe, potentially causing race conditions and data corruption. Also fix minor formatting in migrate.go. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
13 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changed? Why?
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?