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(snapshot-backfill): control log store back pressure in backfill executor #18798

Merged
merged 31 commits into from
Oct 18, 2024

Merge branch 'main' into yiming/snapshot-backfill-executor-backpressure

72274be
Select commit
Loading
Failed to load commit list.
Merged

feat(snapshot-backfill): control log store back pressure in backfill executor #18798

Merge branch 'main' into yiming/snapshot-backfill-executor-backpressure
72274be
Select commit
Loading
Failed to load commit list.
GitGuardian / GitGuardian Security Checks failed Oct 17, 2024 in 7s

7 secrets uncovered!

7 secrets were uncovered from the scan of 31 commits in your pull request. ❌

Please have a look to GitGuardian findings and remediate in order to secure your code.

Details

🔎 Detected hardcoded secrets in your pull request

  • Pull request #18798: yiming/snapshot-backfill-executor-backpressure 👉 main
GitGuardian id GitGuardian status Secret Commit Filename
9425213 Triggered Generic Password 604b5b6 e2e_test/source/tvf/postgres_query.slt View secret
9425213 Triggered Generic Password 43c944c e2e_test/source/tvf/postgres_query.slt View secret
9425213 Triggered Generic Password 1b617b3 ci/scripts/e2e-source-test.sh View secret
9425213 Triggered Generic Password 43c944c e2e_test/source/tvf/postgres_query.slt View secret
9425213 Triggered Generic Password 604b5b6 e2e_test/source/tvf/postgres_query.slt View secret
9425213 Triggered Generic Password 1b013f1 ci/scripts/e2e-source-test.sh View secret
9425213 Triggered Generic Password 0b01544 ci/scripts/e2e-source-test.sh View secret

🛠 Guidelines to remediate hardcoded secrets

  1. Understand the implications of revoking this secret by investigating where it is used in your code.
  2. Replace and store your secrets safely. Learn here the best practices.
  3. Revoke and rotate these secrets.
  4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider


🦉 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.