Skip to content

fix: using jsonwebtoken to decode token payload instead of atob and json parse token #1164

fix: using jsonwebtoken to decode token payload instead of atob and json parse token

fix: using jsonwebtoken to decode token payload instead of atob and json parse token #1164

You are viewing an older attempt in the history of this workflow run. View latest attempt.
Re-run triggered July 9, 2024 22:22
Status Cancelled
Total duration 1m 11s
Artifacts

analysis.yml

on: pull_request
Matrix: Unit Tests
Trivy Security Scan
29s
Trivy Security Scan
Analysis Results
0s
Analysis Results
Fit to window
Zoom out
Zoom in

Annotations

5 errors and 2 warnings
Unit Tests (doc-gen-service)
The job was canceled because "admin-frontend" failed.
Unit Tests (backend)
The job was canceled because "admin-frontend" failed.
Unit Tests (frontend)
The job was canceled because "admin-frontend" failed.
src/__tests__/App.spec.ts > App > when the route changes to /user-management, and the user doesn't have permission to view the breadbrumb trail > breadcrumb trail is hidden: admin-frontend/src/__tests__/App.spec.ts#L130
AssertionError: expected true to be falsy Ignored nodes: comments, script, style <html> <head /> <body /> </html>... - Expected + Received - true + false ❯ src/__tests__/App.spec.ts:130:62 ❯ runWithExpensiveErrorDiagnosticsDisabled node_modules/@testing-library/dom/dist/config.js:47:12 ❯ checkCallback node_modules/@testing-library/dom/dist/wait-for.js:124:77 ❯ Timeout.checkRealTimersCallback node_modules/@testing-library/dom/dist/wait-for.js:118:16
Unit Tests (admin-frontend)
Process completed with exit code 1.
Unit Tests (backend)
Docker network rm failed with exit code 1
Unit Tests (frontend)
Docker network rm failed with exit code 1