Fix completion tokens none issue 6352 #6665
Merged
Conversation
This file contains hidden or 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
…on guide- Fix version format from 0.4.0-dev-1 to 0.4.0-dev.1 for all packages- Remove reference to non-existent Microsoft.AutoGen.Extensions package- Add correct extension packages: Aspire, MEAI, and SemanticKernel- Fix typo: RuntimeGatewway -> RuntimeGateway- Improve documentation structure with clear section headersFixes #6244
Fix issue #6277 where TextMessage was used but not imported in three code cells of the custom agents documentation, causing NameError when users run the examples. Changes: - Add TextMessage to imports in ArithmeticAgent section - Add TextMessage to imports in GeminiAssistantAgent section - Add TextMessage to imports in Declarative GeminiAssistantAgent section The CountDownAgent section already had the correct import. Fixes #6277
Fixes #6352 - Add null checks for prompt_tokens and completion_tokens to prevent TypeError when individual usage properties are None.
…stallation guide- Fix version format from 0.4.0-dev-1 to 0.4.0-dev.1 for all packages- Remove reference to non-existent Microsoft.AutoGen.Extensions package- Add correct extension packages: Aspire, MEAI, and SemanticKernel- Fix typo: RuntimeGatewway -> RuntimeGateway- Improve documentation structure with clear section headersFixes #6244" This reverts commit 6d9fb2e.
…tation" This reverts commit d07898b.
ekzhu
approved these changes
Jun 26, 2025
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #6665 +/- ##
=======================================
Coverage 79.73% 79.74%
=======================================
Files 232 232
Lines 17403 17403
=======================================
+ Hits 13877 13878 +1
+ Misses 3526 3525 -1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
…b.com/tejas-dharani/autogen into fix-completion-tokens-none-issue-6352
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.
Why are these changes needed?
This PR fixes a TypeError that occurs when logging LLM events in the OpenAI integration. The issue arises when
result.usage.completion_tokensorresult.usage.prompt_tokensareNoneeven whenresult.usageitself is notNone. This causes "unsupported operand type(s) for +=: 'int' and 'NoneType'" errors during logging operations.The fix adds proper null checks for both
prompt_tokensandcompletion_tokensproperties, ensuring usage statistics default to 0 when individual properties are None. This prevents the TypeError and ensures robust handling of OpenAI API responses where token counts might be missing.Related issue number
Closes #6352
Checks