fix: close targetSocket when proxy replies with non-200 status (#561) #23
Annotations
6 warnings
|
Your workflow is using a version of actions/cache that is scheduled for deprecation, actions/cache@v2. Please update your workflow to use the latest version of actions/cache to avoid interruptions. Learn more: https://github.blog/changelog/2024-09-16-notice-of-upcoming-deprecations-and-changes-in-github-actions-services/
|
|
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-node@v1, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/setup-node@v1, actions/cache@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
Run npm run lint:
src/tcp_tunnel_tools.ts#L46
Unexpected console statement
|
|
Run npm run lint:
src/tcp_tunnel_tools.ts#L49
Unexpected any. Specify a different type
|
|
Run npm run lint:
src/utils/nodeify.ts#L7
Unexpected any. Specify a different type
|
Loading