Skip to content
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

feat: logs exporter #685

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

feat: logs exporter #685

wants to merge 1 commit 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.

145 files out of 284 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.


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.
    • Generate unit testing code for this file.
    • 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 generate unit testing code for this file.
    • @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 generate unit testing code.
    • @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.

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 resolve resolve all the CodeRabbit review comments.
  • @coderabbitai plan to trigger planning for file edits and PR creation.
  • @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.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

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 66.90942% with 727 lines in your changes missing coverage. Please review.

Project coverage is 78.35%. Comparing base (1f81235) to head (820d90b).

Files with missing lines Patch % Lines
internal/controller/system/connectors_generated.go 0.00% 151 Missing ⚠️
internal/replication/runner.go 62.44% 75 Missing and 17 partials ⚠️
internal/controller/system/controller.go 41.05% 48 Missing and 8 partials ⚠️
internal/storage/system/store.go 64.13% 40 Missing and 12 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.11% 19 Missing and 9 partials ⚠️
...ternal/controller/ledger/controller_with_traces.go 28.94% 27 Missing ⚠️
internal/replication/drivers/errors.go 0.00% 24 Missing ⚠️
internal/replication/driver_facade.go 55.76% 22 Missing and 1 partial ⚠️
... and 35 more
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #685      +/-   ##
==========================================
- Coverage   82.00%   78.35%   -3.65%     
==========================================
  Files         137      176      +39     
  Lines        7512     9231    +1719     
==========================================
+ Hits         6160     7233    +1073     
- Misses       1036     1594     +558     
- Partials      316      404      +88     

☔ 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 4 times, most recently from fd9c363 to dea6216 Compare March 13, 2025 17:26
@gfyrag gfyrag changed the base branch from main to feat/upgrade-speakeasy March 13, 2025 17:26
@gfyrag gfyrag force-pushed the feat/upgrade-speakeasy branch 2 times, most recently from 4310124 to ae04486 Compare March 13, 2025 17:58
Base automatically changed from feat/upgrade-speakeasy to main March 13, 2025 18:17
@gfyrag gfyrag force-pushed the feat/data-ingestion branch 17 times, most recently from 2364257 to 313e7d6 Compare March 20, 2025 11:56
@gfyrag gfyrag force-pushed the feat/data-ingestion branch 3 times, most recently from 27b3bec to 820d90b Compare March 25, 2025 11:01
@gfyrag gfyrag force-pushed the feat/data-ingestion branch from 820d90b to 6d67360 Compare March 27, 2025 10:47
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.

1 participant