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.

Sign up for GitHub

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

Jump to bottom

Cloudformation messages are printed in the wrong order #6578

Closed
attilah opened this issue Feb 9, 2021 · 1 comment · Fixed by #6803
Closed

Cloudformation messages are printed in the wrong order #6578

attilah opened this issue Feb 9, 2021 · 1 comment · Fixed by #6803
Labels
bug Something isn't working platform Issues tied to the general CLI platform

Comments

@attilah
Copy link
Contributor

attilah commented Feb 9, 2021

Describe the bug

The CLI polls CF for status messages and getting it in chunks. Then we are printing it to the screen as we have received it, but it is in the wrong order, the latest entry is on the top:

image

Amplify CLI Version
4.41.2

To Reproduce
Push any project, observe the timestamps of the printed messages

Expected behavior
Print messages in correct order
@attilah attilah added bug Something isn't working platform Issues tied to the general CLI platform labels Feb 9, 2021
watilde added a commit to watilde/amplify-cli that referenced this issue Mar 5, 2021
@watilde
fix(amplify-provider-awscloudformation): print events order by timestamp
2f3a503 
Fixes aws-amplify#6578
@watilde watilde mentioned this issue Mar 5, 2021
Merged
watilde added a commit to watilde/amplify-cli that referenced this issue Mar 6, 2021
@watilde
fix(amplify-provider-awscloudformation): reverse asc events
0e5ed2c 
Fixes aws-amplify#6578
ammarkarachi pushed a commit that referenced this issue Mar 19, 2021
@watilde
fix(amplify-provider-awscloudformation): reverse asc events (#6803)
ae02803 
Fixes #6578
@github-actions
Copy link

This issue has been automatically locked since there hasn't been any recent activity after it was closed. Please open a new issue for related bugs.

Looking for a help forum? We recommend joining the Amplify Community Discord server *-help channels for those types of questions.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 25, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
bug Something isn't working platform Issues tied to the general CLI platform
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix(amplify-provider-awscloudformation): reverse asc events watilde/amplify-cli
1 participant
@attilah