Drop the filelock override once a litellm release allows filelock 4
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 49/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- python
- Domain
- build-system
Research direction
Wait until a litellm release allows filelock 4, then read the lock headers in requirements.lock.txt and requirements-ci.lock.txt, the install locations listed in the issue, SECURITY.md, and CONTRIBUTING.md. Remove the override, recompile both locks, decide whether the listed installs should keep --no-deps, and update the security paragraph and lock recipe. Done when the locks use a compatible litellm release and the override file and references are removed.
Written by the indexing model from the issue text.
Description
#375 locks filelock 4.2.4, which fixes the thirteen filelock 3.32.7 advisories, although every released litellm still declares filelock<4.0. litellm has lifted that cap on its main (filelock>=3.16.1,<5, BerriAI/litellm#49137, merged 2026-10-30); no release carries it yet (1.106.6 is the newest stable at the time of writing).
Once a litellm release allows filelock 4:
- delete
dokimi/requirements-overrides.txt; - drop
--override=requirements-overrides.txtfrom the header commands ofrequirements.lock.txtandrequirements-ci.lock.txt, and recompile both (this also moves litellm to the new release); - decide whether to keep
--no-depson the installs ofrequirements.lock.txt(12 workflow steps,.agent-eval/Dockerfile,make dev): the locks are the full closure, so it can stay, or it can go back to a resolving install; - update the filelock paragraph in
SECURITY.mdand the lock recipe inCONTRIBUTING.md.
Until then, pip install dokimi outside the locks still resolves a filelock below 4, as SECURITY.md says.
- Dominant language
- Python
- Stars
- 11
- Forks
- 9
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 318
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from intel/dokimi
-
Difficulty 4/5 3-5 days Newbie friendliness 53/100
Maintainers usually reply within 1 day
-
repo: Bash reads dropped where the shell could not have moved (conservative limits of #369)Possibly taken @antonwolfy claimed this today. Open
Difficulty 3/5 1-2 days Newbie friendliness 55/100
intel/dokimi#374 · 2 comments · 1 assignee ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 8/100
Maintainers usually reply within 1 day
-
eval reference: stamp a digest of the questions file so headroom catches an edit at the same pathOpen
Difficulty 3/5 1-2 days Newbie friendliness 32/100
Maintainers usually reply within 1 day
Similar issues
-
bug severity:low
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 2 days
-
curriculum documentation quality
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
githubnext/gh-aw-workshop#5367 ·
Maintainers usually reply within 3 days
-
OAuth documentation for GET /api/v2/users/me/ appears inconsistent with required global read scopeOpen
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Create Noise Latents ignores randomize_seed and produces the same noise every runPossibly taken @griptapeops claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
griptape-ai/griptape-nodes-library-diffusers#127 ·
Maintainers usually reply within 1 day
-
Jenkins capacity report: metrics history is lost when archiving a month failsPossibly taken @RaphaelFakhri claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
adoptium/infrastructure#4568 ·
Maintainers usually reply within 1 day