Stefan Negru

Trying to see if I understood it correctly in order to properly implement it: * Assumption 1: it seems that this error will appear only if the `datasetId` or `assemblyId`...

I see, then if the responses you illustrated above are to implemented, maybe some suggestions to consider: - `error` in `BeaconDatasetAlleleResponse` object should not contain an `errorCode`, because that error...

@sdelatorrep you are right, I should have explained 1st bullet point better: In https://github.com/ga4gh-beacon/specification/blob/master/beacon.md#errors it is specified: > The error type SHOULD be chosen from this table and be accompanied...

@jrambla I am sorry this is a bit confusing to me and how any services making use of the Beacon API should process these: > HTTP return code: 200 Beacon...

Sorry for the long message, but I wanted to detail my point of view. @jrambla I was hoping that it was clear that using `200` as an error would be...

@mbaudis thanks for the suggestions - currently we are not using `info` key to add specific keys as the beacon specification does not set `additionalProperties: false` so in practice additional...

Building on what @teemukataja mentioned, we made this suggestion based on our experience loading and analysing the data from 1000 genome project. We are tackling one issue at a time,...

@mbaudis probably should have mentioned i was focusing on content (and how to it could be used), not structure

@sdelatorrep ok, super! ... I was proposing something more general, but I think your regex makes more sense (in the current context). Thanks! @mbaudis sounds good.

noticed a similar behaviour in 1.16.1 where I got the following ``` Status: Presented: false Processing: false Reason: unexpected non-ACME API error: context deadline exceeded State: errored Events: Type Reason...