ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #leetcode
LeetCode’s public GraphQL API relies on a session cookie (LEETCODE_SESSION) for authentication, while CI/CD pipelines require a stable, token‑based mechanism for long‑running automation. The goal is to enable unattended submission and result polling without manual re‑authentication or manual back‑off handling. Current constraints include opaque cookie lifeti
Recursive Python solutions are common on LeetCode, and local development environments often allow increasing the recursion limit. The judge environment is documented to use a default recursion limit and to restrict attempts to raise it. The precise interaction between sys.setrecursionlimit and the judge's runtime is not clearly specified in the public langua
Percentile reference pool scope LeetCode shows runtime and memory percentiles on the submission results page for supported languages. The displayed percentiles compare a submission against a pool of recent submissions for the same problem and language, but LeetCode does not publish the exact size, time window, or refresh frequency of that pool. Consequently,
LeetCode accepts solutions written in Python, but the platform does not disclose the exact interpreter version employed during judging. Community observations suggest the default may be Python 3.8, yet some submissions using features introduced in Python 3.10 (such as the match statement) have been reported as accepted, indicating a possible version upgrade
Determine whether LeetCode's GraphQL endpoint applies the same rate‑limit and validation rules to mutation operations when the request is authenticated with a token generated for a test account versus a token from a regular production account. Because the platform does not publish an official API, the undocumented GraphQL endpoint is used via the CLI or cust
LeetCode's online judge evaluates submissions in a language-specific sandbox, yet problem statements typically express constraints as input-size bounds and target complexity rather than explicit wall-clock or memory budgets. The custom-test / Run Code path and the Submit path are not guaranteed to behave identically; hidden cases and stricter resource enforc
Filtering Constraints in Premium Problem Sets LeetCode Premium allows users to isolate problems tagged by specific companies to streamline interview preparation. This feature enables the intersection of company tags with other metadata, such as difficulty levels and specific topic categories. There is uncertainty regarding the behavior of the filtering engin
LeetCode utilizes containerized environments to execute code with strict constraints on execution time and memory. When a solution fails with a 'Time Limit Exceeded' or 'Memory Limit Exceeded' error, the platform does not distinguish between an infinite loop and algorithmic complexity that merely exceeds the defined threshold. There is currently no documente
LeetCode’s Account Settings include an "Export Data" feature that produces a JSON file containing a user’s submission history, including timestamps, language, code snippets, and verdicts. The platform does not provide an official import or restore function, so users who wish to recover their data must manually re‑submit the saved code via the web interface o
python