Skip to content

Accept FL/FD Infinity in Microsoft.Health.Dicom.Client metadata parse - #3533

Closed
Haywood CompuMed (HaywoodInPixels) wants to merge 1 commit into
microsoft:mainfrom
HaywoodInPixels:fix/client-fl-infinity-json
Closed

Accept FL/FD Infinity in Microsoft.Health.Dicom.Client metadata parse#3533
Haywood CompuMed (HaywoodInPixels) wants to merge 1 commit into
microsoft:mainfrom
HaywoodInPixels:fix/client-fl-infinity-json

Conversation

@HaywoodInPixels

Copy link
Copy Markdown

Description

Microsoft.Health.Dicom.Client 10.0.535 throws Malformed DICOM json, number expected when WADO-RS metadata contains an FL/FD value encoded as "-Infinity". Azure Health Data Services returns HTTP 200 with that string because JSON has no numeric infinity.

This PR:

  • Bumps fo-dicom 5.1.55.2.6 so the client’s DicomJsonConverter accepts "NaN" / "Infinity" / "-Infinity"
  • Adds an HttpMessageHandler repro: RetrieveStudyMetadataAsync against ["-Infinity", -1] must parse, and a finite-value control case

Related issues

Addresses #3532.

Testing

dotnet test src/Microsoft.Health.Dicom.Client.UnitTests/Microsoft.Health.Dicom.Client.UnitTests.csproj -p:Platform=x64 — 2 passed.

Please publish a new Microsoft.Health.Dicom.Client after merge so 10.0.535 consumers can pick this up.

AHDS already emits ""-Infinity"" in DICOM JSON; bump fo-dicom to 5.2.6 and add an HttpMessageHandler repro so RetrieveStudyMetadataAsync no longer fails the whole study.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant