I was able to resolve this for now by removing package-lock.json and running
yarn install again. However now I am running into a different issue with
the JWT authentication in ConfigService:
ERROR [2026-05-11 19:33:08,224] org.apache.texera.auth.JwtParser$: Failed
to parse JWT: JWT
(claims->{"sub":"texera","userId":1,"googleId":null,"email":"texera","role":"ADMIN","googleAvatar":null,"exp":1777324924})
rejected due to invalid claims or other invalid content. Additional
details: [[1] The JWT is no longer valid - the evaluation time
NumericDate{1778527988 -> May 11, 2026, 12:33:08 PM PDT} is on or after the
Expiration Time (exp=NumericDate{1777324924 -> Apr 27, 2026, 2:22:04 PM
PDT}) claim value (even when providing 30 seconds of leeway to account for
clock skew).]
ERROR [2026-05-11 19:33:08,224] org.apache.texera.auth.JwtParser$: Failed
to parse JWT: JWT
(claims->{"sub":"texera","userId":1,"googleId":null,"email":"texera","role":"ADMIN","googleAvatar":null,"exp":1777324924})
rejected due to invalid claims or other invalid content. Additional
details: [[1] The JWT is no longer valid - the evaluation time
NumericDate{1778527988 -> May 11, 2026, 12:33:08 PM PDT} is on or after the
Expiration Time (exp=NumericDate{1777324924 -> Apr 27, 2026, 2:22:04 PM
PDT}) claim value (even when providing 30 seconds of leeway to account for
clock skew).]
WARN [2026-05-11 19:33:08,224] org.apache.texera.auth.JwtAuthFilter:
Invalid JWT: Unable to parse token
WARN [2026-05-11 19:33:08,224] org.apache.texera.auth.JwtAuthFilter:
Invalid JWT: Unable to parse token
INFO [2026-05-11 19:33:08,264] org.eclipse.jetty.server.RequestLog:
[0:0:0:0:0:0:0:1] - "GET /api/config/user-system HTTP/1.1" 401
INFO [2026-05-11 19:33:08,264] org.eclipse.jetty.server.RequestLog:
[0:0:0:0:0:0:0:1] - "GET /api/config/gui HTTP/1.1" 401
I found this possible related PR: https://github.com/apache/texera/pull/4903
Thanks,
Ryan
On Mon, May 11, 2026 at 12:20 PM Ryan Zhang <[email protected]> wrote:
> Hi Texera team,
>
> After I pulled from the latest main today, I encountered two errors
> related to our dependencies for the frontend.
>
> The first error is related to the *tslib *version, which was resolved
> when I upgraded from 2.3.1 to the latest 2.8.1. The error output was this:
>
> ./node_modules/ng-zorro-antd/fesm2022/ng-zorro-antd-tree.mjs:1736:19-36 -
> Error: export '__runInitializers' (imported as '__runInitializers') was not
> found in 'tslib' (possible exports: __assign, __asyncDelegator,
> __asyncGenerator, __asyncValues, __await, __awaiter,
> __classPrivateFieldGet, __classPrivateFieldSet, __createBinding,
> __decorate, __exportStar, __extends, __generator, __importDefault,
> __importStar, __makeTemplateObject, __metadata, __param, __read, __rest,
> __spread, __spreadArray, __spreadArrays, __values)
>
> The second error is a dependency conflict between monaco-breakpoints and
> monaco-editor which I have not been able to resolve. When installing, I
> get this error:
>
> npm error code ERESOLVE
> npm error ERESOLVE unable to resolve dependency tree
> npm error
> npm error While resolving: [email protected]
> npm error Found: [email protected]
> npm error node_modules/monaco-editor
> npm error monaco-editor@"npm:@codingame/[email protected]"
> from the root project
> npm error
> npm error Could not resolve dependency:
> npm error peer monaco-editor@"^0.39.0" from [email protected]
> npm error node_modules/monaco-breakpoints
> npm error monaco-breakpoints@"0.2.0" from the root project
>
> Has anyone else encountered this error or know a solution?
>
> Thanks,
> Ryan
>
