Daniel (dB.) Doubrovkine

icon indicating a website link https://code.dblock.org icon indicating an email [email protected]

icon company @opensearch-project icon location New York, NY icon location @opensearch-project, ex-@aws, former CTO @artsy @ArtsyOpenSource, @vestris, active maintainer of @ruby-grape, hashie, @slack-ruby, @playplayio and more.

Results 3350 comments of Daniel (dB.) Doubrovkine

[BUG] Not displaying past value anomalies correctly on chart

[[Catch All Triage](https://github.com/opensearch-project/.github/blob/main/TRIAGING.md) - [1](https://github.com/dblock), [2](https://github.com/reta), [3](https://github.com/andrross/), [4](https://github.com/dolla24)]

[BUG] Cluster State API is undocumented and unavailable in clients

Should we move this to documentation-website as a documentation bug?

[BUG] Overriding field type in index pattern not working as it should

[Catch All Triage - [1](https://github.com/andrross), [2](https://github.com/dblock), [3](https://github.com/AmiStrn), [4](https://github.com/reta), [5](https://github.com/finnegancarroll)]

[AUTOCUT] Integration Test failed for anomalyDetectionDashboards: 1.3.18

[Catch All Triage - [1](https://github.com/dblock), [2](https://github.com/krisfreedain), [3](https://github.com/andrross), [4](https://github.com/reta)]

[FEATURE] Add option to set resources for initHelper container

[Catch All Triage - [1](https://github.com/dblock/), [2](https://github.com/krisfreedain), [3](https://github.com/reta)]

react-router-5.3.4.tgz: 1 vulnerabilities (highest severity is: 7.5)

[[Catch All Triage](https://github.com/opensearch-project/.github/blob/main/TRIAGING.md) - [1](https://github.com/dblock), [2](https://github.com/reta)]

sass-lint-auto-fix-0.21.2.tgz: 1 vulnerabilities (highest severity is: 5.3)

[[Catch All Triage](https://github.com/opensearch-project/.github/blob/main/TRIAGING.md) - [1](https://github.com/dblock), [2](https://github.com/reta)]

Was it intentional to hide the http response status from the error formatter?

I don't think this was intentional at all, please feel free to PR a change.

Was it intentional to hide the http response status from the error formatter?

@drewnichols I think I agree with @ericproulx 1. Does the workaround of `env[Grape::Env::API_ENDPOINT].status` work for you? 2. Maybe we can add a locally scoped `status` in the `error_formatter` context?

Was it intentional to hide the http response status from the error formatter?

So any ideas about making this change backwards compatible?