You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The trace-server (built from incubator
4b14d71637df2cedecd48d4287851315418a2d31) returns XY model data which
is inconsistent with the openapi specification.
The XY endpoint to fetch the model
(https://localhost:8080/tsp/api/experiments/{expUUID}/outputs/XY/{outputId}/xy)
lists in its response schema that yValues is an array of int64, but
the actual values returned by the trace-server are encoded as doubles.
In org.eclipse.tracecompass.incubator, the series is serialized by SeriesModelSerializer.java which takes in an ISeriesModel and
writes its data to JSON. The relevant part is:
public void serialize(ISeriesModel value, ...)
...
gen.writeObjectField("yValues", value.getData())
...
getData is defined by the interface ISeriesModel as:
/**
* Get the y values
*
* @return An array of y values
*/
double[] getData();
A consumer following the specification will attempt to parse the yValues as an int64 and either fail or truncate the values.
The trace-server (built from incubator
4b14d71637df2cedecd48d4287851315418a2d31) returns XY model data which
is inconsistent with the openapi specification.
The XY endpoint to fetch the model
(
https://localhost:8080/tsp/api/experiments/{expUUID}/outputs/XY/{outputId}/xy
)lists in its response schema that
yValues
is an array of int64, butthe actual values returned by the trace-server are encoded as doubles.
In org.eclipse.tracecompass.incubator, the series is serialized by
SeriesModelSerializer.java
which takes in anISeriesModel
andwrites its data to JSON. The relevant part is:
getData
is defined by the interfaceISeriesModel
as:A consumer following the specification will attempt to parse the
yValues
as an int64 and either fail or truncate the values.Example of a series:
To me it makes sense that the
yValues
should listed as doubles inthe openapi specification, and that that's where the issue lies.
The text was updated successfully, but these errors were encountered: