-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
🌸 Cherry pick request for 26484 into 26356 (cherry-picked) #26483
Comments
/cc @gmajoulet |
Prod rolled back already right? Is there a second cherry-pick coming? I thought that was the case. |
The other cherry-pick is here: #26477 Both should be cherry-picked into prod before it is rollforwarded |
Approved |
We decided to not cherry-pick production and skip this week's production release. Reassigning to @powerivq for the mini post mortem. |
closing this issue |
Cherry-pick request
Why does this issue meet the cherry-pick criteria?
This is a production-affecting bug.
Why is a RC cherry-pick not needed?
Not applicable.
Mini-postmortem
Summary
We are refactoring several interfaces out from
resources
service to amutator
service. amp-auto-lightbox uses the API fromresources
service and was not switched to the new one. It was not caught until on production, and console error log triggered the alarm.Root Causes
amp-auto-lightbox uses
element.getResources
to obtain the service object, and the type checker is not able to find the type reference of that method. The type checker therefore failed to check whether the method call exists.There is insufficient traffic for this single extension on canary that would have triggered an alarm.
Action Items
Lessons Learned
Things that went well
Things that went wrong
/cc @ampproject/wg-approvers @ampproject/cherry-pick-approvers
The text was updated successfully, but these errors were encountered: