Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[GLD Serializer Benchmark] Kotlin jackson-cbor 2.19.0 — spec compliance misses

Open
  • Is something wrong?
#790 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Active
Tech stack
java, kotlin
Domain
backend

Research direction

Start with the Compliance view for Kotlin/jackson-cbor and open each scored FAIL cell to read its cited specification paragraph. Use the compliance and reading-results pages to determine whether each miss is a real encoder/decoder defect or an intentional default. Done means documenting the rationale for intentional behavior, or identifying the affected implementation and adding a fix with regression coverage if the miss is a bug.

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-cbor 2.19.0 on Kotlin. 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 Kotlin with jackson-cbor 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/kotlin/jackson-cbor

How the catalog is built, and how to read a FAIL line:

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/kotlin/jackson-cbor/json (or yaml, cbor, …).

Benchmark timings (same pin)

The same suite also publishes encode / decode time and payload size for this library on Kotlin:

https://leo-gan.github.io/GLD.SerializerBenchmark/dashboard/?lang=kotlin&data=document@n=1&mode=bytes#dashboard

Details table (this library pre-selected):

https://leo-gan.github.io/GLD.SerializerBenchmark/dashboard/?lang=kotlin&ser=jackson-cbor&data=document@n=1&mode=bytes#detailed-analytics

That page is the live L1 snapshot, not a claim that one library is “best.”

Ask

Please look at the Compliance view for jackson-cbor. 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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from FasterXML/jackson-dataformats-binary

All issues in FasterXML/jackson-dataformats-binary

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.