# devopsgym / testgen__fasterxml__jackson-core-1182 - taskset: [devopsgym](https://harnessreport.com/tasks/devopsgym.md) - difficulty: hard - category: test-generation - language: - runnable from the site: no - agent timeout: 3000s ## Results by harness _none yet_ ## Instruction ``` The following text contains a user issue (in <issue/> brackets) posted at a repository. Further, you are provided with file contents of several files in the repository that contain relevant code (in <code> brackets). It may be necessary to use code from third party dependencies or files not contained in the attached documents however. Your task is to identify the issue and implement a test case that verifies a proposed solution to this issue. More details at the end of this text. <issue> Currently `JsonParser` has method `getNumberType()`, with semantics that are loose for many textual formats. Basically formats like JSON do not have similar types as programming languages: so while we have separate `NumberType` entries representing `float` (32-bit binary FP), `double` (64-bit "double"precision binary FP) and `BigDecimal` (unlimited-precision, decimal FP), there is no efficient mechanism to actually produce correct `NumberType` for floating-point values. Because of this, basically all FP values claim to be of `NumberType.DOUBLE` for such formats. This can be problematic if values are converted first to `double`, then to `BigDecimal`, since former cannot accurately represent all decimal numbers. However, binary formats often have specific storage representations that can provide this type information. The problem comes when converting to Java types: both `java.lang.Number` (or generally `java.lang.Object`) and `JsonNode`. In this case we would ideally use either: 1. Exact type if known (binary formats) OR 2. Well-known type -- `Double` OR `BigDecimal`, based on configuration 3. In some edge cases (not-a-number aka `NaN`), `Double` as that can represent such values. (further complicating things, we also have secondary means of producing `NaN` values: value overflow for `double` (and theoretically, but not practically, `float`) which can produce `+INFINITY`) Given all above confusion, I think we need a new method like `getNumberTypeFP()` -- with matching `enum NumberTypeFP` (to be able to express value `UNKNOWN`, no need for integer types). That will allow deserializers to know if "true number type", and base logic on that, specifically avoiding conversions in case of Binary formats and allowing their use for Textual formats (or in general formats without explicit type information for FP numbers). **EDIT**: originally thought we'd need `getNumberTypeExplicit()`, but since the need is specifically for floating-point numbers, let's call it `getNumberTypeFP()` instead; no need for non-FP types. And can indicate semantics are for strict/explicit type. </issue> Please generate test cases that check whether an implemented solution resolves the issue of the user (at the top, within <issue/> brackets). You may apply changes to several files. Apply as much reasoning as you please and see necessary. Make sure to implement only test cases and don't try to fix the issue itself. You are not allowed to read git history. ``` --- Harness Report runs agent harnesses from their GitHub repos on Harbor tasks and records every model call. Every page is also `.md` and `.json`; index: https://harnessreport.com/llms.txt · MCP: https://harnessreport.com/mcp