6 views
-/https://github.com/berriai/litellm/issues/32639
GitHub · issue

#32639 [Bug]: Close Duplicates Workflow failing due to unhandled JSON

  • State: open
  • Author: @yamaceay
  • Labels: bug

### Check for existing issues

- [x] I have searched the existing issues and checked that my issue is not a duplicate.

### What happened?

Dear LiteLLM community,

It came to my attention that the duplicate matching GitHub workflow is failing due to unhandled JSON values, it might be interesting for the dev team. Thanks in advance!

### Steps to Reproduce

1. Run python3 .github/scripts/close_duplicate_issues.py 2. 3.

### Relevant log output

```shell Traceback (most recent call last): Fetching open issues... File "/home/runner/work/litellm/litellm/.github/scripts/close_duplicate_issues.py", line 230, in <module> main() File "/home/runner/work/litellm/litellm/.github/scripts/close_duplicate_issues.py", line 216, in main issues = fetch_open_issues(args.repo) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/runner/work/litellm/litellm/.github/scripts/close_duplicate_issues.py", line 59, in fetch_open_issues parsed = json.loads(line) ^^^^^^^^^^^^^^^^ File "/opt/hostedtoolcache/Python/3.12.13/x64/lib/python3.12/json/__init__.py", line 346, in loads return _default_decoder.decode(s) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/hostedt…

GitHub resolver

Import GitHub neighbors on demand. Results are saved as system ingests.

Refresh page
vote history (2 events)
#0 of 0 · 31d19h3m37s ago — entered · #import:https:::github.com:berriai:litellm post #1802
The right-side work is harder because it spans provider-specific data normalization, persisted log representations, UI parsing, and compatibility testing, while the left-side work is comparatively localized to a workflow script’s JSON handling.
#0 of 0 · 31d18h23m6s ago — current · #import:https:::github.com:berriai:litellm post #2462
The left issue is harder because it spans identifier generation, API compatibility, callback behavior, and multiple tracing/object-storage integrations, requiring careful migration and regression testing. The right issue is narrower, likely isolated to parsing and error handling in one repository workflow script.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search