Commit e1bdbc9
fix: Resolve LogRecord attribute conflict in event manager logging (#802)
## Summary
- Renamed `extra={'message': message}` to `extra={'raw_message':
message}` in `ApifyEventManager._process_platform_messages` — the
`message` key overwrites Python's built-in `LogRecord.message`
attribute, corrupting the log record (especially visible on Python
3.13+).
- Added `caplog.set_level(logging.INFO, logger='apify')` to
`test_unknown_event_is_logged` — the unknown event is logged at `INFO`
level but `caplog` only captures `WARNING`+ by default, causing the
assertion to always fail.
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>1 parent c07461e commit e1bdbc9
2 files changed
Lines changed: 2 additions & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
133 | 133 | | |
134 | 134 | | |
135 | 135 | | |
136 | | - | |
| 136 | + | |
137 | 137 | | |
138 | 138 | | |
139 | 139 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
266 | 266 | | |
267 | 267 | | |
268 | 268 | | |
| 269 | + | |
269 | 270 | | |
270 | 271 | | |
271 | 272 | | |
| |||
0 commit comments