refactor(core): unify exception filter and resolve technical debt #65
soorqAnnotations
2 errors and 1 warning
|
Lint & Test
Process completed with exit code 1.
|
|
libs/health/src/controller/health.controlller.spec.ts > HealthController > checkHealth > should throw SERVICE_UNAVAILABLE when service status is "down":
libs/health/src/controller/health.controlller.spec.ts#L28
AssertionError: expected BaseException: Сервис MyService временно … { …(3) } to match object { status: 503, …(1) }
(3 matching properties omitted from actual)
- Expected
+ Received
+ BaseException {
+ "response": {
+ "code": "SERVICE_UNHEALTHY",
+ "details": [
{
- "response": "MyService service is unhealthy.",
+ "status": "down",
+ "target": "MyService",
+ "timestamp": "2026-04-19T21:43:40.707Z",
+ },
+ ],
+ "message": "Сервис MyService временно недоступен или работает некорректно",
+ },
"status": 503,
}
❯ libs/health/src/controller/health.controlller.spec.ts:28:51
|
|
Lint & Test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4, pnpm/action-setup@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|