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.

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

Fresh deployment of DREM fails in the LeaderboardDeployToS3 stage #82

Open
davidfsmith opened this issue Dec 21, 2024 · 1 comment
Open

Comments

@davidfsmith
Copy link
Contributor

Fresh pull of the code and deployment is resulting in LeaderboardDeployToS3 failing.

Code build error is below

Status: Downloaded newer image for public.ecr.aws/sam/build-nodejs18.x:latest
npm notice
npm notice New major version of npm available! 10.7.0 -> 11.0.0
npm notice Changelog: https://github.com/npm/cli/releases/tag/v11.0.0
npm notice To update run: npm install -g [email protected]
npm notice
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: [email protected]
npm error Found: [email protected]
npm error node_modules/typescript
npm error   peerOptional typescript@"^5" from [email protected]
npm error   node_modules/i18next
npm error     peer i18next@">= 23.2.3" from [email protected]
npm error     node_modules/react-i18next
npm error       react-i18next@"^13.2.0" from the root project
npm error   peer typescript@">=4.2.0" from [email protected]
npm error   node_modules/ts-api-utils
npm error     ts-api-utils@"^1.0.1" from @typescript-eslint/[email protected]
npm error     node_modules/@typescript-eslint/eslint-plugin
npm error       dev @typescript-eslint/eslint-plugin@"^6.5.0" from the root project
npm error       1 more (eslint-plugin-jest)
npm error     ts-api-utils@"^1.0.1" from @typescript-eslint/[email protected]
npm error     node_modules/@typescript-eslint/type-utils
npm error       @typescript-eslint/type-utils@"6.21.0" from @typescript-eslint/[email protected]
npm error       node_modules/@typescript-eslint/eslint-plugin
npm error         dev @typescript-eslint/eslint-plugin@"^6.5.0" from the root project
npm error         1 more (eslint-plugin-jest)
npm error     1 more (@typescript-eslint/typescript-estree)
npm error
npm error Could not resolve dependency:
npm error peerOptional typescript@"^3.2.1 || ^4" from [email protected]
npm error node_modules/react-scripts
npm error   react-scripts@"5.0.1" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/typescript
npm error   peerOptional typescript@"^3.2.1 || ^4" from [email protected]
npm error   node_modules/react-scripts
npm error     react-scripts@"5.0.1" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/empty-cache/_logs/2024-12-21T17_01_21_838Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/empty-cache/_logs/2024-12-21T17_01_21_838Z-debug-0.log
[Container] 2024/12/21 17:01:46.346323 Command did not exit successfully docker run --rm -v $(pwd):/foo -w /foo public.ecr.aws/sam/build-nodejs18.x:latest bash -c 'npm install --cache /tmp/empty-cache && npm run build' exit status 1
[Container] 2024/12/21 17:01:46.350513 Phase complete: BUILD State: FAILED
[Container] 2024/12/21 17:01:46.350530 Phase context status code: COMMAND_EXECUTION_ERROR Message: Error while executing command: docker run --rm -v $(pwd):/foo -w /foo public.ecr.aws/sam/build-nodejs18.x:latest bash -c 'npm install --cache /tmp/empty-cache && npm run build'. Reason: exit status 1
[Container] 2024/12/21 17:01:46.388561 Entering phase POST_BUILD
[Container] 2024/12/21 17:01:46.390581 Phase complete: POST_BUILD State: SUCCEEDED
[Container] 2024/12/21 17:01:46.390596 Phase context status code:  Message: 
[Container] 2024/12/21 17:01:46.431124 Set report auto-discover timeout to 5 seconds
[Container] 2024/12/21 17:01:46.431167 Expanding base directory path:  .
[Container] 2024/12/21 17:01:46.432645 Assembling file list
[Container] 2024/12/21 17:01:46.432656 Expanding .
[Container] 2024/12/21 17:01:46.434180 Expanding file paths for base directory .
[Container] 2024/12/21 17:01:46.434189 Assembling file list
[Container] 2024/12/21 17:01:46.434192 Expanding **/*
[Container] 2024/12/21 17:01:46.437253 No matching auto-discover report paths found
[Container] 2024/12/21 17:01:46.437274 Report auto-discover file discovery took 0.006150 seconds
[Container] 2024/12/21 17:01:46.437285 Phase complete: UPLOAD_ARTIFACTS State: SUCCEEDED
[Container] 2024/12/21 17:01:46.437293 Phase context status code:  Message: 
davidfsmith added a commit to davidfsmith/guidance-for-aws-deepracer-event-management that referenced this issue Dec 21, 2024
@davidfsmith
Copy link
Contributor Author

Updates to website-leaderboard/package.json as part of #80 resolve the issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant