FasterXML / FasterXML/jackson-dataformats-binary
[GLD Serializer Benchmark] Java jackson-cbor 2.19.0 — spec compliance misses
- 主要言語
- Java
- スター
- 347
- フォーク
- 156
- 平均マージ
- 3日 3時間
- マージ済み PR(30日)
- 22
説明
Hi — this is a friendly report from the [GLD Serializer Benchmark](https://github.com/leo-gan/GLD.SerializerBenchmark), 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 **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-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/java/jackson-cbor
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-cbor/json` (or `yaml`, `cbor`, …).
## Benchmark timings (same pin)
The same suite also publishes encode / decode time and payload size for this library on Java:
https://leo-gan.github.io/GLD.SerializerBenchmark/dashboard/?lang=java&data=document@n=1&mode=bytes#dashboard
Details table (this library pre-selected):
https://leo-gan.github.io/GLD.SerializerBenchmark/dashboard/?lang=java&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.
コントリビューションガイド
このリポジトリのコントリビューションガイドは索引されていません
評価
この issue はまだ評価されていません。