[ISSUE 390] Production Image Caching #393
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Fixes #390
Time to review: 10 mins
Changes proposed
This PR fixes 2 issues:
Image
component in next.jsnodejs
user as owner of that particular directoryContext for reviewers
This one is going to be tough to test individually, but I don't see any more errors in our AWS logs. The cache issue only happens in production.
Additional information
Broken
Fixed
Note: appears the health check endpoint is failing now and causing the task to restart repeatedly, but that's a separate issue.