-
Notifications
You must be signed in to change notification settings - Fork 15
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
Fix ci merge versioning #129
Fix ci merge versioning #129
Conversation
* refactor: small improvements * test: worker to queue and index video vec
refactor: moving tests to sub-folders
fix: video worker handles disconnection to RabbitMQ
ci: fix location for video requirment file
fix: video operator locaiton in Dockerfile
ci: video worker dockerfile for graviton
feat: worker for audio operator
test: benchmarking scripts for audiovec operator
fix: updating vidvec benchmark scripts
refactor: config file for video worker
ci: audiovec benchmark graviton dockerfile
refactor: merging development to main
refactor: updating dev from main
refactor: merge development to main
|
GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
---|---|---|---|---|---|
9699964 | Triggered | Username Password | 22bb325 | src/test.env | 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!
- Removed integration tests and required components - Used unittest for unit tests - Disabled audio from disk test
No description provided.