Hi,
Ok, I just created a Jira ticket:
SYNCOPE-1541 - Syncope response message timestamps missing millisecs component
if "0 msecs"
and marked it as an "Improvement".
Thanks,Jim
On Wednesday, February 12, 2020, 12:15:11 PM UTC, Francesco Chicchiriccò
wrote:
Hi,
I have replicated
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, Francesco Chicchiriccò
wrote:
Hi,
I have replicated the behavior (as I was suspecting, it's happening only with
XML) via this simple snippet:
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 since then, to try to reproduce
it, but so far, I have not been able to replicate the problem.
Luckily I did save off the response where we saw the
Hi,
when calling the public demo (2.1.6-SNAPSHOT) as follows:
curl -X GET
"https://syncope-vm.apache.org/syncope/rest/tasks/executions/recent?max=1; -H
"accept: application/json"
response is
[
{
"start": "2020-02-11T04:01:20.034+",
"end": "2020-02-11T04:01:20.411+",
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 includes
the and elements, which have the start and ending timestamps.
These ending part of these timestamps are supposed to be formatted:
H:M:S.fZ
