[BUG] Facing java.time.format.DateTimeParseException when listing emerging issues from ResourceHealthManager

[drmoeller]

Describe the bug
While trying to list emerging issues from ResourceHealthManager, following exception is thrown:

Exception or Stack Trace

Caused by: java.time.format.DateTimeParseException: Text '2025-01-24 07:34:05Z' could not be parsed at index 10
	at java.base/java.time.format.DateTimeFormatter.parseResolved0(DateTimeFormatter.java:2108)
	at java.base/java.time.format.DateTimeFormatter.parseBest(DateTimeFormatter.java:2056)
	at com.azure.core.util.CoreUtils.parseBestOffsetDateTime(CoreUtils.java:793)
	at com.azure.resourcemanager.resourcehealth.fluent.models.EmergingIssue.lambda$fromJson$4(EmergingIssue.java:153)
	at com.azure.json.JsonReader.getNullable(JsonReader.java:238)
	at com.azure.resourcemanager.resourcehealth.fluent.models.EmergingIssue.lambda$fromJson$7(EmergingIssue.java:153)
	at com.azure.json.JsonReader.readMapOrObject(JsonReader.java:551)
	at com.azure.json.JsonReader.readObject(JsonReader.java:455)
	at com.azure.resourcemanager.resourcehealth.fluent.models.EmergingIssue.fromJson(EmergingIssue.java:145)
	at com.azure.resourcemanager.resourcehealth.fluent.models.EmergingIssuesGetResultInner.lambda$fromJson$0(EmergingIssuesGetResultInner.java:216)
	at com.azure.json.JsonReader.readMapOrObject(JsonReader.java:551)
	at com.azure.json.JsonReader.readObject(JsonReader.java:455)
	at com.azure.resourcemanager.resourcehealth.fluent.models.EmergingIssuesGetResultInner.fromJson(EmergingIssuesGetResultInner.java:203)
	at com.azure.resourcemanager.resourcehealth.models.EmergingIssueListResult.lambda$fromJson$2(EmergingIssueListResult.java:116)
	at com.azure.json.JsonReader.readArray(JsonReader.java:494)
	at com.azure.resourcemanager.resourcehealth.models.EmergingIssueListResult.lambda$fromJson$3(EmergingIssueListResult.java:116)
	at com.azure.json.JsonReader.readMapOrObject(JsonReader.java:551)
	at com.azure.json.JsonReader.readObject(JsonReader.java:455)
	at com.azure.resourcemanager.resourcehealth.models.EmergingIssueListResult.fromJson(EmergingIssueListResult.java:108)
[...]

To Reproduce
Steps to reproduce the behavior: See code below.

Code Snippet
Kotlin code:

import com.azure.resourcemanager.resourcehealth.ResourceHealthManager

[...]

    ResourceHealthManager.authenticate(credential, profile)
      .emergingIssues()
      .list()
      .forEach { println("--- $it") }

Expected behavior
Either proper parsing of timestamp provided by Azure API, or adaption of Azure API response with properly formatted timestamp.

Screenshots
If applicable, add screenshots to help explain your problem.

Setup (please complete the following information):

• OS: Linux
• IDE: Same when executed via IntelliJ or shell
• Library/Libraries: implementation("com.azure.resourcemanager:azure-resourcemanager-resourcehealth:1.1.0-beta.3")
• Java version: 21
• App Server/Environment: Local test case execution
• Frameworks: Micronaut

Additional context
Add any other context about the problem here.

Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report

• Bug Description Added
• Repro Steps Added
• Setup information Added

[github-actions]

Thank you for your feedback. Tagging and routing to the team member best able to assist.

[weidongxu-microsoft]

@drmoeller

It looks like a server bug. The "2025-01-24 07:34:05Z" is not a RFC3339 date-time.
https://datatracker.ietf.org/doc/html/rfc3339#section-5.8

It should be e.g. 2025-01-24T07:34:05Z

[drmoeller]

DEBUG logging does not uncover received response body (only its headers), but stack trace shows that problem occurs when parsing (at least) "refreshTimestamp" field:

if ("refreshTimestamp".equals(fieldName)) {
    deserializedEmergingIssue.refreshTimestamp = reader
        .getNullable(nonNullReader -> CoreUtils.parseBestOffsetDateTime(nonNullReader.getString()));  // <== HERE

[weidongxu-microsoft]

Client-side logging can be enabled via https://github.com/Azure/azure-sdk-for-java/tree/main/sdk/resourcemanager#enabling-logging

Note that if the response body is big, the logging may not print its content.

Here is the log on my test

"body":"{\"value\":[{\"id\":\"/providers/Microsoft.ResourceHealth/emergingissues/default\",\"type\":\"/providers/Microsoft.ResourceHealth/emergingissues\",\"name\":\"default\",\"properties\":{\"refreshTimestamp\":\"2025-01-24 08:51:03Z\",\"statusBanners\":[],\"statusActiveEvents\":[]}}]}"

And yes, "2025-01-24 08:51:03Z" is from server.

[drmoeller]

Same on my machine:

09:12:22.351Z [Test worker] INFO  - {"az.sdk.message":"HTTP request","method":"GET","url":"https://management.azure.com/providers/Microsoft.ResourceHealth/emergingIssues?api-version=2023-10-01-preview","tryCount":1,"Date":"Fri, 24 Jan 2025 09:12:21 GMT","x-ms-client-request-id":"dfe215bb-9b8e-4c02-8a0b-ca0046dc00be","Accept":"application/json","User-Agent":"azsdk-java-com.azure.resourcemanager.resourcehealth/1.1.0-beta.3 (21.0.5; Linux; 6.8.0-51-generic; auto-generated)","redactedHeaders":"Authorization,Content-Type","content-length":0}
09:12:22.576Z [reactor-http-epoll-9] INFO  - {"az.sdk.message":"HTTP response","statusCode":200,"url":"https://management.azure.com/providers/Microsoft.ResourceHealth/emergingIssues?api-version=2023-10-01-preview","durationMs":233,"content-length":256,"Date":"Fri, 24 Jan 2025 09:12:22 GMT","Expires":"-1","Pragma":"no-cache","Cache-Control":"no-cache","x-ms-request-id":"60f0b95a-cfaf-4443-b524-3f0f7e908437,60f0b95a-cfaf-4443-b524-3f0f7e908437","redactedHeaders":"x-ms-correlation-request-id,Strict-Transport-Security,X-MSEdge-Ref,X-Content-Type-Options,x-ms-routing-request-id,Content-Type,X-Cache,x-ms-ratelimit-remaining-tenant-resource-requests","content-length":256,"body":"{\"value\":[{\"id\":\"/providers/Microsoft.ResourceHealth/emergingissues/default\",\"type\":\"/providers/Microsoft.ResourceHealth/emergingissues\",\"name\":\"default\",\"properties\":{\"refreshTimestamp\":\"2025-01-24 09:06:10Z\",\"statusBanners\":[],\"statusActiveEvents\":[]}}]}"}
09:12:22.576Z [reactor-http-epoll-11] INFO  - {"az.sdk.message":"HTTP response","statusCode":200,"url":"https://management.azure.com/providers/Microsoft.ResourceHealth/emergingIssues?api-version=2023-10-01-preview","durationMs":221,"content-length":256,"Date":"Fri, 24 Jan 2025 09:12:22 GMT","Expires":"-1","Pragma":"no-cache","Cache-Control":"no-cache","x-ms-request-id":"11124ffe-f488-4e97-898b-b550be03706a,11124ffe-f488-4e97-898b-b550be03706a","redactedHeaders":"x-ms-correlation-request-id,Strict-Transport-Security,X-MSEdge-Ref,X-Content-Type-Options,x-ms-routing-request-id,Content-Type,X-Cache,x-ms-ratelimit-remaining-tenant-resource-requests","content-length":256,"body":"{\"value\":[{\"id\":\"/providers/Microsoft.ResourceHealth/emergingissues/default\",\"type\":\"/providers/Microsoft.ResourceHealth/emergingissues\",\"name\":\"default\",\"properties\":{\"refreshTimestamp\":\"2025-01-24 09:07:06Z\",\"statusBanners\":[],\"statusActiveEvents\":[]}}]}"}