Multiple ECONNREFUSED errors even with server.boundary

[Akkuma]

Locally I'm seeing no issues, but on CI I'm seeing this:

⎯⎯⎯⎯ Unhandled Rejection ⎯⎯⎯⎯⎯
Error: connect ECONNREFUSED 67.220.250.8:80
 ❯ TCPConnectWrap.afterConnect [as oncomplete] node:net:1555:16
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { errno: -111, code: 'ECONNREFUSED', syscall: 'connect', address: '67.220.250.8', port: 80, '$metadata': { attempts: 3, totalRetryDelay: 142 } }
This error originated in "functions/codat/list-companies.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running.
⎯⎯⎯⎯ Unhandled Rejection ⎯⎯⎯⎯⎯
Error: connect ECONNREFUSED 67.220.250.8:80
 ❯ TCPConnectWrap.afterConnect [as oncomplete] node:net:1555:16
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { errno: -111, code: 'ECONNREFUSED', syscall: 'connect', address: '67.220.250.8', port: 80, '$metadata': { attempts: 3, totalRetryDelay: 140 } }
This error originated in "functions/codat/get-inflow-outflow-chart.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running.
⎯⎯⎯⎯ Unhandled Rejection ⎯⎯⎯⎯⎯
Error: connect ECONNREFUSED 67.220.244.191:80
 ❯ TCPConnectWrap.afterConnect [as oncomplete] node:net:1555:16
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { errno: -111, code: 'ECONNREFUSED', syscall: 'connect', address: '67.220.244.191', port: 80, '$metadata': { attempts: 3, totalRetryDelay: 84 } }
This error originated in "functions/codat/get-profit-and-loss-report.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running.
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯

My setup file for vitest:

import { afterAll, afterEach, beforeAll, vi } from 'vitest';
import { server } from './msw/node.js';

beforeAll(() => {
	server.listen({
		onUnhandledRequest: 'error',
	});
});

afterEach(() => {
	server.resetHandlers();
});

afterAll(() => {
	server.close();
});

The ./msw/node.js

import { setupServer } from 'msw/node';
import { handlers } from './handlers.js';

export const server = setupServer(...handlers);

Test of get-profit-and-loss-report.test.ts

import { describe, expect, it } from 'vitest';
import { HttpResponse } from 'msw';
import { logger } from '../logger.js';
import type { ProfitLossInput } from '../../../graphql/index.js';
import { getProfitLoss } from './get-profit-and-loss-report.js';
import type { CodatProfitAndLossReport } from './mappings/profit-and-loss-report.js';
import {
	codatApiUrl,
	createProfitAndLossReport,
} from '#/test/fixtures/codat.js';
import { type ResBody, http } from '#/test/msw/http.js';
import { server } from '#/test/msw/node.js';

const profitAndLostUrl = `${codatApiUrl}/companies/:companyId/data/financials/profitAndLoss`;
describe('get-profit-and-loss-report', () => {
	describe('getProfitLoss', () => {
		it('triggers expected actions', async () => {
			server.boundary(async () => {
				const report = createProfitAndLossReport();
				server.use(
					http.get<ResBody<CodatProfitAndLossReport>>(profitAndLostUrl, () => {
						return HttpResponse.json(report);
					}),
				);

				const curYear = new Date().getFullYear();
				const input: ProfitLossInput = {
					companyId: '123',
					fromDate: new Date(curYear - 10, 0).toISOString(),
					toDate: new Date(curYear + 10, 11).toISOString(),
				};

				const result = await getProfitLoss({ input, logger });
				expect(result.reports).toHaveLength(report.reports.length);
			});
		});
	});
});

Update:
Ok realized I probably need:

it('triggers expected actions', server.boundary(async () => {
	const report = createProfitAndLossReport();
	server.use(
		http.get<ResBody<CodatProfitAndLossReport>>(profitAndLostUrl, () => {
			return HttpResponse.json(report);
		}),
	);

	const curYear = new Date().getFullYear();
	const input: ProfitLossInput = {
		companyId: '123',
		fromDate: new Date(curYear - 10, 0).toISOString(),
		toDate: new Date(curYear + 10, 11).toISOString(),
	};

	const result = await getProfitLoss({ input, logger });
	expect(result.reports).toHaveLength(report.reports.length);
}));

This then runs into a bit of a compatibility issue with vitest, The first argument inside a fixture must use object destructuring pattern, e.g. ({ test } => {}). Instead, received "...args".

[Akkuma]

Ok so I still have issues on CI and part of the potential solution here is a little bit tedious if you use vitest context throught extend

If you aren't using extend or vitest context:

it('test name', server.boundary(async () => {
	server.use(
		http.get('someUrl, () => {
			return HttpResponse.json(someData);
		}),
	);

	const result = await someFn({ input, logger });
	expect(result.data).toHaveLength(fixture.data.length);
}));

If you are using vitest's context:

it('test name', async ({ extraContextStuff, expect }) => {
	const fn = server.boundary(async () => {
		server.use(
			http.ge(url, () => {
				return HttpResponse.json(data);
			}),
		);

		const result = await someFn()

		expect(result).toMatchObject(objToMatch);
	});

	await fn();
});

or

it('test name', async ({ extraContextStuff, expect }) => {
	await server.boundary(async () => {
		server.use(
			http.ge(url, () => {
				return HttpResponse.json(data);
			}),
		);

		const result = await someFn()

		expect(result).toMatchObject(objToMatch);
	})()
});

[Akkuma]

So with the above changes done everywhere I still get:

⎯⎯⎯⎯ Unhandled Rejection ⎯⎯⎯⎯⎯
Error: connect ECONNREFUSED 67.220.251.8:80
 ❯ TCPConnectWrap.afterConnect [as oncomplete] node:net:1555:16
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { errno: -111, code: 'ECONNREFUSED', syscall: 'connect', address: '67.220.251.8', port: 80, '$metadata': { attempts: 3, totalRetryDelay: 51 } }
This error originated in "functions/codat/list-companies.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running.
⎯⎯⎯⎯ Unhandled Rejection ⎯⎯⎯⎯⎯
Error: connect ECONNREFUSED 67.220.251.8:80
 ❯ TCPConnectWrap.afterConnect [as oncomplete] node:net:1555:16
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { errno: -111, code: 'ECONNREFUSED', syscall: 'connect', address: '67.220.251.8', port: 80, '$metadata': { attempts: 3, totalRetryDelay: 91 } }
This error originated in "functions/codat/index.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running.
⎯⎯⎯⎯ Unhandled Rejection ⎯⎯⎯⎯⎯
Error: connect ECONNREFUSED 67.220.251.8:80
 ❯ TCPConnectWrap.afterConnect [as oncomplete] node:net:1555:16
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { errno: -111, code: 'ECONNREFUSED', syscall: 'connect', address: '67.220.251.8', port: 80, '$metadata': { attempts: 3, totalRetryDelay: 108 } }
This error originated in "functions/codat/get-inflow-outflow-chart.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running.
⎯⎯⎯⎯ Unhandled Rejection ⎯⎯⎯⎯⎯
Error: connect ECONNREFUSED 67.220.251.8:80
 ❯ TCPConnectWrap.afterConnect [as oncomplete] node:net:1555:16
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { errno: -111, code: 'ECONNREFUSED', syscall: 'connect', address: '67.220.251.8', port: 80, '$metadata': { attempts: 3, totalRetryDelay: 124 } }
This error originated in "functions/codat/get-profit-and-loss-report.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running.
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯

[Akkuma]

Alright, so I tracked down this issue. @aws-sdk/client-ssm has some form of compatibility issue w/msw. It'll work almost all the time fine locally (I did notice that https always failed locally), but as soon as this is up on CI it failed no matter what.

I'll need to make a simple test case so this could potentially be examined closer.