feat(deploy): ARM64 架构预检 + 默认 verbose 日志 - #106
Conversation
项目仅支持 ARM64(容器为 linux/arm64 构建)。在 x86_64 机器上部署原本会在 docker build 中途抛出晦涩的 "exec /bin/sh: exec format error";现在 deploy.sh 在 i18n helper 就绪后、app 选择器与任何交互提示之前就用 uname -m 探测,非 arm64/aarch64 直接明确报错并指向 ARM64 机器(Apple Silicon Mac / AWS Graviton)。 架构是硬前置条件,故放在最早处。 README 部署两节与 FAQ(中英)补充 ARM64 前置说明。i18n 新增文案改变 OAuth Lambda 打包 asset 哈希,一并刷新快照。
|
Warning Review limit reached
Next review available in: 11 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (5)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
部署常在 cdk bootstrap / cdk deploy 处无声停顿,详细日志正是定位这类卡顿 的关键。故默认给两处 cdk 调用加 -v(流式输出每步进度与 AWS SDK 调用); 新增 --quiet / -q 可恢复精简输出。空 flag 展开不产生多余空参数。
ddpie
changed the title
1 participant
改动
两处部署健壮性 / 可观测性增强。
部署前检测非 ARM64 架构并提前报错
项目仅支持 ARM64（容器为
linux/arm64构建）。在 x86_64 机器上部署，原本会在 docker build 中途抛出晦涩的exec /bin/sh: exec format error。deploy.sh现在在 i18n 就绪后、app 选择器与任何交互提示之前就用uname -m探测架构，非arm64/aarch64直接明确报错，并指向 ARM64 机器（Apple Silicon Mac 或 AWS Graviton 实例如 t4g / c7g）。README 部署两节与 FAQ（中英）补充 ARM64 前置说明。默认打开 cdk verbose 日志
部署常在
cdk bootstrap/cdk deploy处无声停顿，详细日志正是定位这类卡顿的关键。故默认给这两处 cdk 调用加-v（流式输出每步进度与 AWS SDK 调用）；新增--quiet/-q可恢复精简输出。config/i18n.json被 OAuth Lambdaimport，新增文案改了打包 asset 哈希，故刷新 CDK 快照。Changes
Two deploy robustness / observability enhancements.
Detect non-ARM64 architecture before deploying and fail early
The project is ARM64-only (the container is built for
linux/arm64). Deploying on an x86_64 machine used to fail mid-docker buildwith a crypticexec /bin/sh: exec format error.deploy.shnow checksuname -mright after i18n is ready — before the app picker or any prompt — and on non-arm64/aarch64fails early with a clear message pointing at an ARM64 machine (Apple Silicon Mac or an AWS Graviton instance such as t4g / c7g). The README Deploy sections and the FAQ (zh/en) note the prerequisite.Verbose cdk logs on by default
Deploys often stall silently at
cdk bootstrap/cdk deploy, and detailed logs are what make that diagnosable. Both cdk calls now pass-v(streaming per-step progress + AWS SDK calls) by default;--quiet/-qrestores terse output.config/i18n.jsonisimported by the OAuth Lambda, so the new strings changed its bundle asset hash — CDK snapshot refreshed.