autogen
autogen copied to clipboard
AutoGen logging using Azure Cosmos DB
Why are these changes needed?
Related issue number
Checks
- [ ] I've included any doc changes needed for https://microsoft.github.io/autogen/. See https://microsoft.github.io/autogen/docs/Contribute#documentation to build and test documentation locally.
- [ ] I've added tests (if relevant) corresponding to the changes introduced in this PR.
- [ ] I've made sure all auto checks have passed.
Codecov Report
Attention: Patch coverage is 36.00000% with 64 lines in your changes are missing coverage. Please review.
Project coverage is 13.85%. Comparing base (
11d9336) to head (d811e6a). Report is 10 commits behind head on main.
| Files | Patch % | Lines |
|---|---|---|
| autogen/logger/cosmos_db_logger.py | 36.47% | 53 Missing and 1 partial :warning: |
| autogen/logger/logger_factory.py | 23.07% | 10 Missing :warning: |
Additional details and impacted files
@@ Coverage Diff @@
## main #2760 +/- ##
===========================================
- Coverage 33.60% 13.85% -19.75%
===========================================
Files 87 94 +7
Lines 9336 9527 +191
Branches 1987 2153 +166
===========================================
- Hits 3137 1320 -1817
- Misses 5933 8196 +2263
+ Partials 266 11 -255
| Flag | Coverage Δ | |
|---|---|---|
| unittests | 13.81% <36.00%> (-19.79%) |
:arrow_down: |
Flags with carried forward coverage won't be shown. Click here to find out more.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
pls merge main for a CI fix
️✅ 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. 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.
please let us know, if this PR is still active? @wmwxwa
Ah I see the type checks are failing. Going to close this as it seems abandoned, @wmwxwa feel free to reopen if you wish to pursue this