Possible bug - or Strange (or at least unexpected) behavior to Syncope 2.1.5 REST endpoint (tasks/executions/recent/?max=1)

6 messages Options
Possible bug - or Strange (or at least unexpected) behavior to Syncope 2.1.5 REST endpoint (tasks/executions/recent/?max=1) – Hi, We are using the Syncope 2.1.5 API, and we send a GET request to the tasks/executions/recent/?max=1 URI, and we get a response message that i...
Hi, when calling the public demo (2.1.6-SNAPSHOT) as follows: curl -X GET "https://syncope-vm.apache.org/syncope/rest/tasks/executions/re...
Hi Francesco, This problem is NOT happening every time...  In fact, it has only occurred ONCE so far, and I have been doing a LOT of testing sin...
Hi, I have replicated the behavior (as I was suspecting, it's happening only with XML) via this simple snippet: https://paste.apache.org/308ln...
Hi, Thanks for checking on this!!  And yes, I will do as you suggest in a bit. Jim On Wednesday, February 12, 2020, 12:15:11 PM UTC, F...
Hi, Ok, I just created a Jira ticket: SYNCOPE-1541 - Syncope response message timestamps missing millisecs component if "0 msecs" ...