Skip to content

fix: prevent fallback to legacy store #954

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 86 commits into from

Conversation

gfyrag
Copy link
Contributor

@gfyrag gfyrag commented Jun 2, 2025

  • feat: handle missing compatibility layer with v2.1
  • fix: release workflow
  • fix: wrong encoding on a migration
  • fix: transactions commit with special chars in metadata
  • fix: GET /_info breaking change (fix: GET /_info breaking change #666)
  • chore: add openapi tag to satisfy global sdk (chore: add openapi tag #670)
  • fix: migration using azure postgres with no superuser provileges
  • fix: next migration
  • fix: next migration (fix: import from 2.1 #689)
  • fix: incompatibility between v1 and v2 api format when using numbers with more than 7 digits (fix(v2.2): incompatibility on create transaction #697)
  • fix: potential inconsistent ledger creation
  • fix: missing filter on list logs (fix: missing filter on list logs #708)
  • fix: make ledger creations atomic
  • fix(ledger) tx reversion handles empty middle accounts (fix(ledger): tx reversion handles empty middle accounts #711)
  • fix: transaction list missing reference filter
  • fix: failing queries (GET /accounts?expand=volumes) when migrations are not terminated
  • fix: migrations with pg 13
  • fix: regression regarding v2.1
  • fix: metadata override
  • feat: don't check all buckets on all health checks
  • chore: dirty
  • fix: parallelize bucket migration rollback detection (fix: parallelize bucket migration rollback detection #755)
  • fix: Revert "feat: don't check all buckets on all health checks"
  • fix: version api field
  • feat: prevent potential deadlocks
  • feat: upgrade skeapeasy and use streaming file system for logs imports (feat: upgrade skeapeasy and use streaming file system for logs imports #766)
  • fix: import regression
  • feat: hide textual errors on internal server errors
  • feat: add version as otlp resource attributes
  • fix: invalid unicode conversion while computing hash
  • fix: local test server in benchmarks
  • feat: remove one UPDATE sql query in case of metadata usage
  • feat: improve pulumi
  • feat: add multi ledger generator on pulumi program
  • fix: remove not used pulumi properties
  • fix: missing env var
  • feat: add capability to retain rds component on deletion
  • fix: debug flag on migrate command
  • feat: make tracing of logs import more granular
  • feat: add additional annotations on storage service
  • fix: invalid post commit volumes format
  • fix: use full qualified name when using function aggregate_objects
  • fix: invalid pcv
  • chore: upgrade go libs
  • fix: accounts metadata not overriden
  • feat: add otel env vars to migration job
  • feat: add traces all along the migration path
  • fix(openapi): bulk response definition
  • fix: inconsistent accounts list
  • fix: invalid migration
  • fix: missing metadata on reverts
  • fix: incorrect metadata on reversing transactions
  • fix: backport get balances from main
  • chore: simplify
  • feat: simplify
  • fix: invalid revert events (fix: invalid revert events #868)
  • fix: potential invalid balance during upgrade
  • fix: Migration 29
  • fix: updated_at not set
  • fix: missing denormalized data in logs
  • fix: incorrect join with specific combination of filters
  • fix: potential non atomic ledger creation
  • fix: invalid date format
  • fix: too big trace on imports
  • feat: remove sql transaction on imports
  • test: add import test with error
  • fix: from coredabbit
  • fix: missing decorator around the ledger controller
  • fix: useless comment
  • feat: add some tracing
  • feat: backport json streaming from 2.3
  • fix: missing default options when connecting to default postgres
  • fix: missing yaml tag
  • fix: reverse query param on transactions list
  • fix: pageSize not effective when a cursor is used
  • fix: build with go 1.24.3
  • fix: return 400 instead of 500 for idempotency key reuse with different body (fix: return 400 instead of 500 for idempotency key reuse with different body #919)
  • fix: add sql transaction by log when importing
  • fix: memento format
  • feat: extract compute_hash function
  • feat(pulumi): expose rds cluster id
  • fix: image-pull-policy ignored
  • fix: configure sequences after import
  • fix: pagination with custom column (transaction list)
  • fix: invalid state assigned
  • fix: prevent fallback to legacy store when migrating

gfyrag and others added 30 commits January 2, 2025 15:24
Improve performance of rollback detection by processing buckets concurrently using a worker pool. Added configurable parallel workers with a default of 100, and implemented error handling for multiple potential failures during the process.
#766)

* feat: upgrade skeapeasy and use streaming file system for logs imports

* feat: use speakeasy workflow to regenerate the sdk

* fix: add staticcheck for speakeasy
gfyrag and others added 26 commits April 24, 2025 18:13
…nt body (#919)

* feat: implement idempotency key handling for account and transaction metadata operations

* test: enhance idempotency key tests for transaction metadata operations

* test: update comments to English and improve idempotency key handling in metadata tests

* refactor: streamline error handling for idempotency key conflicts in account and transaction metadata operations

* test: update metadata deletion tests to use Expect for improved readability and error handling

* refactor: update error handling for write operations and improve comments in error handling functions

* feat: add Idempotency-Key header to metadata deletion endpoints in OpenAPI specifications

* chore: update SDK for add Idempotency-Key support in metadata deletion requests

* test: refactor metadata deletion tests to utilize idempotency key in requests and improve error handling

* refactor: update error handling in ledger metadata operations to use common write error handler

* test: reactivate and refine idempotency key tests for account and transaction metadata operations

* test: remove specific error code expectation from ledger accounts and transactions metadata tests

* refactor: remove account address validation from addAccountMetadata function

* docs: add Idempotency-Key header details to metadata deletion endpoint documentation
@gfyrag gfyrag requested a review from a team as a code owner June 2, 2025 16:05
Copy link

coderabbitai bot commented Jun 2, 2025

Important

Review skipped

More than 25% of the files skipped due to max files limit. The review is being skipped to prevent a low-quality review.

112 files out of 274 files are above the max files limit of 100. Please upgrade to Pro plan to get higher limits.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

✨ Finishing Touches
  • 📝 Generate Docstrings

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@gfyrag gfyrag closed this Jun 2, 2025
@gfyrag gfyrag deleted the hotfix/v2.2/prevent-fallback-to-legacy-store branch June 2, 2025 16:11
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.

2 participants