Fix AttributeError crash when AgentContext lacks type attribute (#923) #926
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.
Add defensive checks using hasattr() before accessing context.type to prevent AttributeError crashes when dealing with old or corrupted contexts that don't have the type attribute. This fixes the data loss issue reported in #923.
Changes:
All locations now use defensive pattern:
if hasattr(context, 'type') and context.type == AgentContextType.BACKGROUND
For serialization, default to USER type when attribute is missing:
context.type.value if hasattr(context, 'type') else AgentContextType.USER.value
Added comprehensive test suite to verify the fixes work correctly with:
All tests pass successfully.