PostHog/posthog

Feature flags: Do not know how to serialize a BigInt type error

Open

#19367 opened on Dec 15, 2023

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Python (16,704 stars) (988 forks)batch import
bugfeature/feature-flagsgood first issueteam/feature-flags

Description

Bug description

Please describe.
The above is showing up on a feature flag page If you are on PostHog Cloud it would be really valuable if you can share any links where the problem occurs. This speeds up our ability to troubleshoot tremendously.

How to reproduce

Environment

Additional context

Thank you for your bug report – we love squashing them!

Contributor guide

Tech stack
pythondjango
Domain
backend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
PythonDjangoJSON serialization
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Investigate the source of the BigInt type error in the feature flags functionality. Look for any integer fields in feature flag models that may exceed JavaScript's safe integer range, and check the serialization logic (possibly using Django REST Framework) to ensure custom serialization for large integers. The error occurs on the feature flag page, so trace the API response that feeds that page.