Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: access-api createStoreProxy uses patched fetch that will log any non-ok responses (to debug) #364

Merged
merged 2 commits into from
Jan 19, 2023

Conversation

gobengo
Copy link
Contributor

@gobengo gobengo commented Jan 18, 2023

…that logs unexpected responses with status=530

Motivation:

Plan

  • gather info, then revert this PR

@gobengo gobengo requested a review from Gozala January 18, 2023 22:20
@gobengo gobengo temporarily deployed to dev January 18, 2023 22:21 — with GitHub Actions Inactive
…that logs unexpected responses with status=530
@gobengo gobengo force-pushed the 1674080303-proxy-log-530 branch from 5d4a3ef to 6aada8e Compare January 18, 2023 22:24
@gobengo gobengo temporarily deployed to dev January 18, 2023 22:26 — with GitHub Actions Inactive
@gobengo gobengo changed the title access-api service does createStoryProxy with patched fetch function … access-api service does createStoreProxy with patched fetch function … Jan 18, 2023
…which checks for response.ok, and not only handling 530 response statuses
@gobengo gobengo temporarily deployed to dev January 18, 2023 22:44 — with GitHub Actions Inactive
@gobengo gobengo requested a review from yusefnapora January 18, 2023 22:44
@gobengo gobengo changed the title access-api service does createStoreProxy with patched fetch function … feat: access-api createStoreProxy uses patched fetch that will log any non-ok responses (to debug) Jan 18, 2023
Copy link
Contributor

@yusefnapora yusefnapora left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This seems like a good (temporary) hack, given that the error only seems to happen in prod. Hopefully comparing the output between prod & staging will flush out something...

@gobengo gobengo merged commit e741bc0 into main Jan 19, 2023
@gobengo gobengo deleted the 1674080303-proxy-log-530 branch January 19, 2023 17:55
gobengo pushed a commit that referenced this pull request Jan 19, 2023
🤖 I have created a release *beep* *boop*
---


##
[4.5.0](access-api-v4.4.0...access-api-v4.5.0)
(2023-01-19)


### Features

* access-api createStoreProxy uses patched fetch that will log any
non-ok responses (to debug)
([#364](#364))
([e741bc0](e741bc0))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).
gobengo added a commit that referenced this pull request Apr 11, 2023
…y non-ok responses (to debug) (#364)

…that logs unexpected responses with status=530

Motivation:
* gather more info for [this error happening in
production](#363 (comment))

Plan
* gather info, then revert this PR
gobengo pushed a commit that referenced this pull request Apr 11, 2023
🤖 I have created a release *beep* *boop*
---


##
[4.5.0](access-api-v4.4.0...access-api-v4.5.0)
(2023-01-19)


### Features

* access-api createStoreProxy uses patched fetch that will log any
non-ok responses (to debug)
([#364](#364))
([f13f00e](f13f00e))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants