8000 feat: logs exporter by gfyrag · Pull Request #685 · formancehq/ledger · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

feat: logs exporter #685

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

Open
wants to merge 13 commits into
base: main
Choose a base branch
from
Open

feat: logs exporter #685

wants to merge 13 commits into from

Conversation

gfyrag
Copy link
Contributor
@gfyrag gfyrag commented Feb 14, 2025

No description provided.

@gfyrag gfyrag requested a review from a team as a code owner February 14, 2025 16:00
@gfyrag gfyrag changed the base branch from main to feat/leadership February 14, 2025 16:01
Copy link
coderabbitai bot commented Feb 14, 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.

137 files out of 272 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
🧪 Generate Unit Tests
  • Create PR with Unit Tests
  • Commit Unit Tests in branch feat/data-ingestion
  • Post Copyable Unit Tests in Comment

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 auto-generate unit tests to generate unit tests for 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 force-pushed the feat/data-ingestion branch 5 times, most recently from 54afbef to f5f8248 Compare February 19, 2025 17:15
@gfyrag gfyrag changed the base branch from feat/leadership to main February 19, 2025 17:15
@gfyrag gfyrag force-pushed the feat/data-ingestion branch 6 times, most recently from dc9d5af to 4ef6b8c Compare February 20, 2025 17:32
Copy link
codecov bot commented Feb 20, 2025

Codecov Report

Attention: Patch coverage is 55.65431% with 1447 lines in your changes missing coverage. Please review.

Project coverage is 74.22%. Comparing base (83c057f) to head (ef62013).

Files with missing lines Patch % Lines
...nternal/replication/grpc/replication_service.pb.go 26.25% 523 Missing and 5 partials ⚠️
...al/replication/grpc/replication_service_grpc.pb.go 24.08% 215 Missing and 12 partials ⚠️
internal/replication/manager.go 61.32% 98 Missing and 25 partials ⚠️
internal/replication/controller_grpc_server.go 23.63% 78 Missing and 6 partials ⚠️
internal/replication/controller_grpc_client.go 36.17% 54 Missing and 6 partials ⚠️
internal/storage/system/store.go 58.33% 42 Missing and 13 partials ⚠️
internal/replication/drivers/registry.go 59.00% 28 Missing and 13 partials ⚠️
internal/replication/drivers/batcher.go 69.42% 28 Missing and 9 partials ⚠️
internal/replication/drivers/clickhouse/driver.go 61.64% 19 Missing and 9 partials ⚠️
internal/replication/drivers/errors.go 0.00% 24 Missing ⚠️
... and 36 more

❗ There is a different number of reports uploaded between BASE (83c057f) and HEAD (ef62013). Click for more details.

HEAD has 1 upload less than BASE
Flag BASE (83c057f) HEAD (ef62013)
2 1
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #685      +/-   ##
==========================================
- Coverage   82.36%   74.22%   -8.14%     
==========================================
  Files         141      184      +43     
  Lines        7829    10806    +2977     
==========================================
+ Hits         6448     8021    +1573     
- Misses       1056     2342    +1286     
- Partials      325      443     +118     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@gfyrag gfyrag force-pushed the feat/data-ingestion branch 3 times, most recently from 065b173 to 995c122 Compare February 24, 2025 14:23
Copy link
gitguardian bot commented Feb 24, 2025

️✅ There are no secrets present in this pull request anymore.

If these secrets were true positive and are still valid, we highly recommend you to revoke them.
While these secrets were previously flagged, we no longer have a reference to the
specific commits where they were detected. Once a secret has been leaked into a git
repository, you should consider it compromised, even if it was deleted immediately.
Find here more information about risks.


🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

@gfyrag gfyrag force-pushed the feat/data-ingestion branch 6 times, most recently from ab7ceeb to d3be2d9 Compare February 28, 2025 08:29
@gfyrag gfyrag force-pushed the feat/data-ingestion branch 3 times, most recently from 413465b to 11fdf35 Compare March 7, 2025 14:45
@gfyrag gfyrag force-pushed the feat/data-ingestion branch from 3c64fe8 to 42ac092 Compare May 12, 2025 14:03
@gfyrag gfyrag changed the base branch from main to fix/uint64-ids May 12, 2025 15:40
@gfyrag gfyrag force-pushed the feat/data-ingestion branch 2 times, most recently from 66d0d57 to d414dd5 Compare May 12, 2025 16:09
Base automatically changed from fix/uint64-ids to main May 13, 2025 07:37
@gfyrag gfyrag force-pushed the feat/data-ingestion branch 2 times, most recently from b9d82b0 to 91085b1 Compare May 13, 2025 10:17
@gfyrag gfyrag force-pushed the feat/data-ingestion branch 4 times, most recently from dbf81d3 to ef62013 Compare May 22, 2025 14:51
@gfyrag gfyrag force-pushed the feat/data-ingestion branch from ef62013 to 4f3698e Compare June 13, 2025 09:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants
0