-
-
Notifications
You must be signed in to change notification settings - Fork 751
Wrong encoding guessed for Metabase API responses #1713
Copy link
Copy link
Closed
Labels
a: moderationRelated to community moderation functionality: (moderation, defcon, verification)Related to community moderation functionality: (moderation, defcon, verification)p: 2 - normalNormal PriorityNormal Priorityt: bugSomething isn't workingSomething isn't working
Metadata
Metadata
Assignees
Labels
a: moderationRelated to community moderation functionality: (moderation, defcon, verification)Related to community moderation functionality: (moderation, defcon, verification)p: 2 - normalNormal PriorityNormal Priorityt: bugSomething isn't workingSomething isn't working
Type
Fields
Give feedbackNo fields configured for issues without a type.
Sentry Issue: BOT-130
The response doesn't include an encoding in the headers, so aiohttp has to guess. It sometimes guesses incorrectly, leading to decoding errors. The API does not document what the encoding of responses is. Would it be safe to assume it's always UTF-8?