-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
Data Processor: Resolve several bugs found while publishing a Studio #19309
Conversation
|
GitGuardian id | Secret | Commit | Filename | |
---|---|---|---|---|
5685611 | Generic High Entropy Secret | c10c882 | tests/tests_data/streaming/test_resolver.py | View secret |
5685611 | Generic High Entropy Secret | c10c882 | tests/tests_data/streaming/test_resolver.py | View secret |
5685611 | Generic High Entropy Secret | c10c882 | tests/tests_data/streaming/test_resolver.py | View secret |
5685611 | Generic High Entropy Secret | c10c882 | tests/tests_data/streaming/test_resolver.py | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secret safely. Learn here the best practices.
- Revoke and rotate this secret.
- 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
- following these best practices for managing and storing secrets including API keys and other credentials
- install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.
🦉 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.
Our GitHub checks need improvements? Share your feedbacks!
for more information, see https://pre-commit.ci
⚡ Required checks status: All passing 🟢Groups summary🟢 lightning_data: CPU workflow
These checks are required after the changes to 🟢 lightning_app: Tests workflow
These checks are required after the changes to 🟢 lightning_app: Examples
These checks are required after the changes to 🟢 lightning_app: Docs
These checks are required after the changes to 🟢 mypy
These checks are required after the changes to 🟢 installThese checks are required after the changes to Thank you for your contribution! 💜
|
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## master #19309 +/- ##
==========================================
- Coverage 84% 51% -32%
==========================================
Files 445 440 -5
Lines 37332 37404 +72
==========================================
- Hits 31182 19135 -12047
- Misses 6150 18269 +12119 |
What does this PR do?
This PR resolves some issues:
Fixes #<issue_number>
Before submitting
PR review
Anyone in the community is welcome to review the PR.
Before you start reviewing, make sure you have read the review guidelines. In short, see the following bullet-list:
Reviewer checklist
cc @Borda