Updating notebooks to work with testing automation #341
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov ReportAll modified and coverable lines are covered by tests ✅
Flags with carried forward coverage won't be shown. Click here to find out more. |
* Adding notebook testing automation (#340) * Fixing path in GitHub action * Renaming job action and updating notebook * Testing new notebook * Standardizing notebooks * More updating more testing * More standardizing * Updating more notebooks * Testing all ipynb directly under examples * Standardizing notebooks * Updating notebooks * adding branch to action * typo * Updating Action to read agentops.log for each notebook. Fixing recording-events.ipynb * Fixing Action to save agentops.log * Fixing Action * iterating workflow * Should continue executing notebooks when one fails * Workflow now for all ipynb. Fixing lots of notebooks * Fixing notebooks * Adding multion key * workflow finishing touches
|
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
|---|---|---|---|---|---|
| 12083425 | Triggered | Generic High Entropy Secret | fc99a6f | tests/core_manual_tests/agentchat_agentops.ipynb | View secret |
| 12083425 | Triggered | Generic High Entropy Secret | fc99a6f | tests/core_manual_tests/agentchat_agentops.ipynb | 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 secrets safely. Learn here the best practices.
- Revoke and rotate these secrets.
- 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.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
📥 Pull Request
📘 Description
Adding pip installs, standardizing how we fetch env variables, and updating anything we've deprecated
🎯 Goal
Standardize the notebooks such that they can be automatically tested with test-notebooks.yml GitHub Action
🧪 Testing
test-notebooks.yml GitHub Action