Christopher Sundersingh
Christopher Sundersingh
@dhruvbansal @hanna-becker - Could you try this tagged version and let me know if this solves your problem? ``` npm i -g @aws-amplify/[email protected] ```
@PeteDuncanson Thanks for confirming. PR# 1305 includes this fix.
Could you try with `11.0.3`? This includes the fix https://github.com/aws-amplify/amplify-category-api/pull/1305 released with the `10.5.3-circular-dep-fix.0` tagged version.
@zirkelc @naedx - I can see that resolver deduping could be the cause of the problem but I'm unable to reproduce a case where it produces circular dependency between child...
Related to https://github.com/aws-amplify/amplify-category-api/issues/2153.
Our team is working on a feature which may be related to your ask. Please take a look at the [Amplify AI RFC](https://github.com/aws-amplify/amplify-ui/issues/5773).
Reopening based on offline conversation with @cliren. The provided steps didn't solve the original request.
@blipps199 Fix for https://github.com/aws-amplify/amplify-category-api/issues/2946 has been published. The next time you make a deployment, you should receive the fix automatically. Could you check if this addresses your issue?
The fix https://github.com/aws-amplify/amplify-codegen/pull/879 is pending codegen release.
There are two control-plane APIs (`create-function` and `update-function`) that contribute to these throttling errors during stack update. Both these APIs have throttle limits of 70 tps each per accountId. Each...