-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[QUERY] Failed to de-serialize JSON on date 2020-02-18T10:14:43.06
#8266
Comments
/cc @jianghaolu |
The difference with track1 clientruntime-for-java is that track1 uses JodaModule, while track2 uses JavaTimeModule (well, of course). Code to reproduce:
|
|
I kind of able to hack it like this. But this is hard to be done in user space to
|
I will try unblock myself by this
|
Hi @weidongxu-microsoft, thanks for investigating into this, it looks like we could add a custom deserializer to handle ISO 8601 better (it appears we already have a custom serializer for it). There remains an open question on the proper way to handle an ISO 8601 date time without a time zone indicator, I feel that leaving it local may be the safest but it may be a service-by-service basis. Any chance we could follow-up with the service owners to determine what the behavior should be in this scenario? |
Agree. Normally it should be LocalDateTime. On mgmt. the code is auto-generated, so for same swagger definition we get same code. If data-plane has not encountered this behavior, I could put the customized de-serializer to core-management. That would leave a simpler core. Then my question is that whether the above For contacting service, if we encounter same issue on another service, I will contact them. Webapp service is not really keen to response to my query (I've got a much more critically query on authentication still pending). Meantime you can close the issue. Just let me know your opinion about the above |
Reopen it since @JonathanGiles requires us to remove serializer package in core-management. Hence it had to be mitigated in core.
|
Query/Question
De-serialize JSON failed on incorrect date e.g.
2020-02-18T10:14:43.06
. (lackZ
at last char)Error message
This probably is web service problem, but I don't think server will fix.
It happens for multiple mgmt services (include web, sql, etc.).
Let me know whether azure core would adapt for this.
Sample request
Sample response
Why is this not a Bug or a feature Request?
A clear explanation of why is this not a bug or a feature request?
More likely a service bug. I need to know whether core would adapt it.
Setup (please complete the following information if applicable):
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
The text was updated successfully, but these errors were encountered: