CI: e2e auth full failing: jose generateJWT 'payload must be an instance of Uint8Array' (jwt.ts:66)

未关闭
#5,092 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
45/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
github-actions, node.js, typescript

调研方向

Start with the failing tests in test/emailChangeConfirmation.e2e.full.test.ts and test/auth-api.e2e.full.test.ts, and with the JWT signing code at jwt.ts:66, which calls jose's SignJWT. Check how the secret reaches that call in the e2e environment, and run the workflow .github/workflows/e2e-webapp-auth-full.yml locally or in CI. Done means both failing tests pass and the workflow is green on main; the fix may be encoding the secret in the same realm or upgrading jose.

由索引模型根据 Issue 内容生成。

描述

What fails

Workflow .github/workflows/e2e-webapp-auth-full.yml fails on main in job 🛡️ E2E Auth Tests (full).

Error

FAIL test/emailChangeConfirmation.e2e.full.test.ts > redirects off the token URL and confirms only when the rendered form is submitted
TypeError: payload must be an instance of Uint8Array
 ❯ new FlattenedSign node_modules/.pnpm/[email protected]/node_modules/jose/dist/node/esm/jws/flattened/sign.js:14:19
 ❯ new CompactSign node_modules/.pnpm/[email protected]/node_modules/jose/dist/node/esm/jws/compact/sign.js:5:27
 ❯ SignJWT.sign node_modules/.pnpm/[email protected]/node_modules/jose/dist/node/esm/jwt/sign.js:12:21
FAIL test/auth-api.e2e.full.test.ts > API > Query dashboards — GET /api/v1/query/dashboards (sanity) > JWT read:query: auth passes
AssertionError: expected 403 not to be 403
 Test Files  2 failed | 7 passed (9)
      Tests  4 failed | 254 passed (258)

When it started

Likely cause

[email protected] receives a non-Uint8Array (cross-realm/TextEncoder) secret in the test env.

Suggested fix

Pass the secret via new TextEncoder().encode in the same realm, or bump jose.

主要语言
TypeScript
星标
16.5k
派生
1.5k
平均合并
1 天 15 小时
30 天内合并 PR
17

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

triggerdotdev/trigger.dev 的其他 Issue

查看 triggerdotdev/trigger.dev 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。