[GLD Serializer Benchmark] Java jackson-smile 2.19.0 — spec compliance misses
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start with the Java jackson-smile compliance view in the linked GLD Serializer Benchmark dashboard and open each FAIL cell to read its cited specification paragraph. Reproduce the reported cases against jackson-smile 2.19.0, then determine whether each miss is a real encoder/decoder bug or an intentional documented behavior. Done means the cases are fixed or their intentional behavior is explained in the issue.
Written by the indexing model from the issue text.
Description
Hi — this is a friendly report from the GLD Serializer Benchmark, an independent multi-language suite that times serializers and checks them against the published format specs (RFC 8259, YAML 1.2, …).
We measured jackson-smile 2.19.0 on Java. The suite recorded spec-profile misses for this pin. The catalog is report-only: a miss is not a CI failure, and some cases are older or stricter profiles (for example RFC 4627 vs RFC 8259) rather than a crash.
Compliance results (please start here)
This link opens the live heatmap on Java with jackson-smile already selected (All standards). Click a scored cell for each FAIL and the cited spec paragraph:
https://leo-gan.github.io/GLD.SerializerBenchmark/dashboard/#compliance/java/jackson-smile
How the catalog is built, and how to read a FAIL line:
- https://leo-gan.github.io/GLD.SerializerBenchmark/compliance/
- https://leo-gan.github.io/GLD.SerializerBenchmark/compliance/reading-results/
I am not pasting the case list here so you can use the Dashboard (filters, heatmap, and spec links) rather than a static dump.
Optional: one standard family only — #compliance/java/jackson-smile/json (or yaml, cbor, …).
Benchmark timings (same pin)
The same suite also publishes encode / decode time and payload size for this library on Java:
Details table (this library pre-selected):
That page is the live L1 snapshot, not a claim that one library is “best.”
Ask
Please look at the Compliance view for jackson-smile. If a miss is a real decoder/encoder bug you want to fix, great. If it is an intentional default (accepting NaN, YAML 1.1 bools, …), a short note here is enough — we will keep the catalog as-is unless the library’s documented contract changes.
Thanks for the library.
- Dominant language
- Java
- Stars
- 348
- Forks
- 159
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 44
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 FasterXML/jackson-dataformats-binary
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
FasterXML/jackson-dataformats-binary#790 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
FasterXML/jackson-dataformats-binary#788 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
FasterXML/jackson-dataformats-binary#766 ·
Maintainers usually reply within 1 day
-
protobuf
Difficulty 4/5 3-5 days Newbie friendliness 35/100
FasterXML/jackson-dataformats-binary#630 · 3 comments ·
Maintainers usually reply within 1 day
-
avro pr-needed
Difficulty 3/5 1-2 days Newbie friendliness 55/100
FasterXML/jackson-dataformats-binary#611 · 4 comments ·
Maintainers usually reply within 1 day
All issues in FasterXML/jackson-dataformats-binary
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
scylladb/scylla-cdc-source-connector#350 ·
Maintainers usually reply within 1 day
-
agent:working documentation enhancement go:build lane:needs-decision
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Sanne/incus-spawn#1435 · 3 comments ·
Maintainers usually reply within 1 day
-
area:shuffle bug priority:high requires-triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
apache/datafusion-comet#7062 ·
Maintainers usually reply within 1 day
-
wait for review
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
enhancement good first issue up-for-grabs
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
AnikethTS/ChangeRadar#22 ·
Maintainers usually reply within 1 day