Potentially set a maximum string length for metadata fields
Maintainers usually reply within 2 days
@kahrendt is already working on this.
Since Nov 4, 2026.
Assessment
This issue has not been assessed yet.
Description
Currently, the metadata text fields are unlimited in length. This makes it difficult to plan memory usage on constrained devices (and requires runtime heap allocations that cause fragmentation). If we set a reasonable limit (255 characters or something, just off the top of my head), clients could plan for that worst case scenario and then avoid heap churn.
Related:
- https://github.com/Sendspin/spec/pull/339 capped server sent friendly names
- https://github.com/Sendspin/spec/pull/329 capped client sent friendly names
- https://github.com/Sendspin/spec/pull/340 proposal for capping group id length
- Dominant language
- Python
- Stars
- 135
- Forks
- 11
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 38
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 Sendspin/spec
-
Difficulty 1/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 2 days
-
Difficulty 1/5 Under an hour Newbie friendliness 84/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Sendspin/spec#145 · 2 comments ·
Maintainers usually reply within 2 days
-
Describe what a server should do when it can't keep up under loadPossibly taken @kahrendt claimed this 24 days ago. Open
Sendspin/spec#309 · 1 comment · 1 assignee ·
Maintainers usually reply within 2 days
-
Difficulty 5/5 Over a week Newbie friendliness 8/100
Sendspin/spec#305 · 2 comments ·
Maintainers usually reply within 2 days
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
RunestoneInteractive/rs#1661 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
streamlink/streamlink#7192 · 4 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
aws-samples/sample-per-model-bedrock#795 ·
Maintainers usually reply within 1 day
-
pm_eval_model crashes with TypeError after the evaluation when --out_fname is not given (regression from #617)Possibly taken @Siddhanthguptaa claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
JdeRobot/PerceptionMetrics#675 ·
Maintainers usually reply within 1 day