Skip to content

refactor: bad sgid session returns 400 instead of 500 (#2249) #891

refactor: bad sgid session returns 400 instead of 500 (#2249)

refactor: bad sgid session returns 400 instead of 500 (#2249) #891

Triggered via push February 23, 2024 02:47
Status Success
Total duration 30m 34s
Artifacts 1
Deploy frontend to AWS Amplify  /  deploy-frontend
3m 47s
Deploy frontend to AWS Amplify / deploy-frontend
Escape commit message to send in slack
0s
Escape commit message to send in slack
Deploy backend to AWS Elastic Beanstalk  /  set_environment
0s
Deploy backend to AWS Elastic Beanstalk / set_environment
Deploy worker to AWS Elastic Container Service  /  set_environment
0s
Deploy worker to AWS Elastic Container Service / set_environment
Deploy backend to AWS Elastic Beanstalk  /  lint-test
3m 30s
Deploy backend to AWS Elastic Beanstalk / lint-test
Deploy worker to AWS Elastic Container Service  /  lint
1m 10s
Deploy worker to AWS Elastic Container Service / lint
Send slack message when deployment starts
4s
Send slack message when deployment starts
Deploy backend to AWS Elastic Beanstalk  /  build_application
2m 35s
Deploy backend to AWS Elastic Beanstalk / build_application
Deploy worker to AWS Elastic Container Service  /  build_application
2m 26s
Deploy worker to AWS Elastic Container Service / build_application
Deploy backend to AWS Elastic Beanstalk  /  deploy_backend
19m 41s
Deploy backend to AWS Elastic Beanstalk / deploy_backend
Deploy backend to AWS Elastic Beanstalk  /  deploy_callback
9m 52s
Deploy backend to AWS Elastic Beanstalk / deploy_callback
Deploy worker to AWS Elastic Container Service  /  deploy_sending
4m 36s
Deploy worker to AWS Elastic Container Service / deploy_sending
Deploy worker to AWS Elastic Container Service  /  deploy_logging
4m 2s
Deploy worker to AWS Elastic Container Service / deploy_logging
End-to-end Test  /  set_environment
0s
End-to-end Test / set_environment
End-to-end Test  /  playwright-run
3m 44s
End-to-end Test / playwright-run
revert-on-e2e-failure
6s
revert-on-e2e-failure
Send Slack message about failed build and tag engineers if it's prod
0s
Send Slack message about failed build and tag engineers if it's prod
Send Slack message about successful build
9s
Send Slack message about successful build
Fit to window
Zoom out
Zoom in

Annotations

34 warnings
Send slack message when deployment starts
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: slackapi/slack-github-action@v1.23.0. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Deploy worker to AWS Elastic Container Service / lint
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/setup-node@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Deploy backend to AWS Elastic Beanstalk / lint-test
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/setup-node@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Deploy worker to AWS Elastic Container Service / build_application
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/setup-node@v3, aws-actions/configure-aws-credentials@v2, aws-actions/amazon-ecr-login@v1, docker/setup-buildx-action@v2, docker/build-push-action@v4. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Deploy frontend to AWS Amplify / deploy-frontend
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, aws-actions/configure-aws-credentials@v2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Deploy backend to AWS Elastic Beanstalk / build_application
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/setup-node@v3, aws-actions/configure-aws-credentials@v2, aws-actions/amazon-ecr-login@v1, docker/setup-buildx-action@v2, docker/build-push-action@v4. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Deploy worker to AWS Elastic Container Service / deploy_logging
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: aws-actions/configure-aws-credentials@v2, aws-actions/amazon-ecs-render-task-definition@v1, aws-actions/amazon-ecs-deploy-task-definition@v1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Deploy worker to AWS Elastic Container Service / deploy_logging
Ignoring property 'compatibilities' in the task definition file. This property is returned by the Amazon ECS DescribeTaskDefinition API and may be shown in the ECS console, but it is not a valid field when registering a new task definition. This field can be safely removed from your task definition file.
Deploy worker to AWS Elastic Container Service / deploy_logging
Ignoring property 'taskDefinitionArn' in the task definition file. This property is returned by the Amazon ECS DescribeTaskDefinition API and may be shown in the ECS console, but it is not a valid field when registering a new task definition. This field can be safely removed from your task definition file.
Deploy worker to AWS Elastic Container Service / deploy_logging
Ignoring property 'requiresAttributes' in the task definition file. This property is returned by the Amazon ECS DescribeTaskDefinition API and may be shown in the ECS console, but it is not a valid field when registering a new task definition. This field can be safely removed from your task definition file.
Deploy worker to AWS Elastic Container Service / deploy_logging
Ignoring property 'revision' in the task definition file. This property is returned by the Amazon ECS DescribeTaskDefinition API and may be shown in the ECS console, but it is not a valid field when registering a new task definition. This field can be safely removed from your task definition file.
Deploy worker to AWS Elastic Container Service / deploy_logging
Ignoring property 'status' in the task definition file. This property is returned by the Amazon ECS DescribeTaskDefinition API and may be shown in the ECS console, but it is not a valid field when registering a new task definition. This field can be safely removed from your task definition file.
Deploy worker to AWS Elastic Container Service / deploy_logging
Ignoring property 'registeredAt' in the task definition file. This property is returned by the Amazon ECS DescribeTaskDefinition API and may be shown in the ECS console, but it is not a valid field when registering a new task definition. This field can be safely removed from your task definition file.
Deploy worker to AWS Elastic Container Service / deploy_logging
Ignoring property 'registeredBy' in the task definition file. This property is returned by the Amazon ECS DescribeTaskDefinition API and may be shown in the ECS console, but it is not a valid field when registering a new task definition. This field can be safely removed from your task definition file.
Deploy worker to AWS Elastic Container Service / deploy_sending
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: aws-actions/configure-aws-credentials@v2, aws-actions/amazon-ecs-render-task-definition@v1, aws-actions/amazon-ecs-deploy-task-definition@v1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Deploy worker to AWS Elastic Container Service / deploy_sending
Ignoring property 'compatibilities' in the task definition file. This property is returned by the Amazon ECS DescribeTaskDefinition API and may be shown in the ECS console, but it is not a valid field when registering a new task definition. This field can be safely removed from your task definition file.
Deploy worker to AWS Elastic Container Service / deploy_sending
Ignoring property 'taskDefinitionArn' in the task definition file. This property is returned by the Amazon ECS DescribeTaskDefinition API and may be shown in the ECS console, but it is not a valid field when registering a new task definition. This field can be safely removed from your task definition file.
Deploy worker to AWS Elastic Container Service / deploy_sending
Ignoring property 'requiresAttributes' in the task definition file. This property is returned by the Amazon ECS DescribeTaskDefinition API and may be shown in the ECS console, but it is not a valid field when registering a new task definition. This field can be safely removed from your task definition file.
Deploy worker to AWS Elastic Container Service / deploy_sending
Ignoring property 'revision' in the task definition file. This property is returned by the Amazon ECS DescribeTaskDefinition API and may be shown in the ECS console, but it is not a valid field when registering a new task definition. This field can be safely removed from your task definition file.
Deploy worker to AWS Elastic Container Service / deploy_sending
Ignoring property 'status' in the task definition file. This property is returned by the Amazon ECS DescribeTaskDefinition API and may be shown in the ECS console, but it is not a valid field when registering a new task definition. This field can be safely removed from your task definition file.
Deploy worker to AWS Elastic Container Service / deploy_sending
Ignoring property 'registeredAt' in the task definition file. This property is returned by the Amazon ECS DescribeTaskDefinition API and may be shown in the ECS console, but it is not a valid field when registering a new task definition. This field can be safely removed from your task definition file.
Deploy worker to AWS Elastic Container Service / deploy_sending
Ignoring property 'registeredBy' in the task definition file. This property is returned by the Amazon ECS DescribeTaskDefinition API and may be shown in the ECS console, but it is not a valid field when registering a new task definition. This field can be safely removed from your task definition file.
Deploy backend to AWS Elastic Beanstalk / deploy_callback
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: aws-actions/configure-aws-credentials@v2, einaregilsson/beanstalk-deploy@v21. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Deploy backend to AWS Elastic Beanstalk / deploy_backend
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: aws-actions/configure-aws-credentials@v2, einaregilsson/beanstalk-deploy@v21. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Deploy backend to AWS Elastic Beanstalk / deploy_backend
Environment update finished, but health is Red and health status is Degraded. Giving it 480 seconds to recover...
Deploy backend to AWS Elastic Beanstalk / deploy_backend
Environment still has health: Yellow and health status Warning. Waiting 449 more seconds before failing...
Deploy backend to AWS Elastic Beanstalk / deploy_backend
Environment still has health: Red and health status Degraded. Waiting 418 more seconds before failing...
End-to-end Test / playwright-run
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/upload-artifact@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
revert-on-e2e-failure
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: aws-actions/configure-aws-credentials@v2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Send Slack message about successful build
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: slackapi/slack-github-action@v1.23.0. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

Artifacts

Produced during runtime
Name Size
playwright-report Expired
427 KB