Cauan Cabral

Na hora do almoço vou dar uma olhada nisso para reproduzir o erro. Faltou incluir essas colunas no Migration @agripinoduarte ?

@tobiasgnu estou adicionando suporte ao Travis em todos os plugins usados pelo Comitiva e em outros que minha empresa disponibiliza aqui no github, e ainda não consegui chegar ao final...

Hi, I think we have similar error. Any update? We try to add `revalidate` _props_ with 30 seconds on every page, but we are seeing cache persisting for exactly 5...

Hi folks, any news about domain routing with Amplify? Theres some way we can work around it by ourselves in the meantime (without having to work with multiple branches or...

We will celebrate 1 year with that and the #2345 issues without ANY solution, explanation, or workaround, that's sad.

Hi, any update about this?

Hi @ferdingler, I would like to define defaults from Console, but any of alternatives are good enough. Defining timeout default as 30s is really appreciate move. How about also update...

Thanks @calavera , keep us up to date, please. More frustrating than the issue is the lack of any feedback from AWS team about it.

@williamrjribeiro That's the way the new Amplify platform WEB_COMPUTE works (they manage all resources internally). Only the old platform WEB_DYNAMIC have CloudFront and associated Lambdas visible. I don't know if...

Hi! We also have the same issue. How we can get that behavior: 1. Create a Next.js page with revalidation every X minutes 2. At `getStaticProps` of your page, do...