Steven Jeuris

Results 120 issues of Steven Jeuris

While the information to calculate this field is available, it is not clear to non-Kotlin clients how to consume it. Therefore, this should probably always be serialized.

enhancement

Currently, only expected data, as specified in the study protocol, can be uploaded to the data subsystem. This means that all data that needs to be uploaded needs to be...

needs discussion

There might be bugs when multiple repo calls happen within single application service calls (which are expected to be single transactions). Should we include some notion of repository transaction management...

bug

RPC examples are generated by running the `rpc` project. Currently, whenever doing a release, the output of this `build/rpc-examples` needs to be manually appended to releases on GitHub. This should...

enhancement

Some sensors assume a fixed sampling rate, and when retrieving data from them, they only provide a timestamp for the first data point. We follow a principle that clients shouldn't...

feature
needs discussion

Currently, when calling `DataStreamService.openDataStreams`, a `IllegalStateException` is thrown when data streams for the same `studyDeploymentId` have already been configured. This [exception currently is caught and ignored in `DeploymentService` when deploying...

enhancement
needs discussion

To implement `ApiMigration`, which supports migrations for backwards compatibility of incoming API requests and responses, a `ApiJsonObjectMigrationBuilder` and `ApiJsonArrayMigrationBuilder` were created. These facilitate doing common JSON transformations. However, these seem...

enhancement

It is often relevant to know fixed sensor _specifications_ of sensors used to collect data. E.g., a PPG sensor may specify the wavelength of the LEDs, which impacts how deep...

feature
needs discussion

Currently, JSON schemas for all request objects are validated in `JsonSchemasTest`. But, this does not include tests for all extending domain types. An instance for all extending types is available...

enhancement

The backend now has the notion of "staged" participant groups: sets of participants with assigned master devices _before_ they are deployed. https://github.com/cph-cachet/carp.core-kotlin/issues/255 But, we are still missing endpoints to add/remove/change...

feature
needs discussion