AssertionError: expected Error: Couldn't connect to server to be an instance of TypeError ❯ Proxy.<anonymous> node_modules/@vitest/expect/dist/index.js:1336:17 ❯ Proxy.<anonymous> node_modules/@vitest/expect/dist/index.js:972:17 ❯ Proxy.methodWrapper node_modules/chai/chai.js:1610:25 ❯ Curl.<anonymous> test/curl/callbacks.spec.ts:136:25 ❯ Curl.emit node:events:517:28 ❯ Curl.onError lib/Curl.ts:312:10 ❯ Easy.<anonymous> lib/Curl.ts:101:19 This error originated in "test/curl/callbacks.spec.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "should not accept undefined return". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

AssertionError: expected 7 to be 42 // Object.is equality - Expected + Received - 42 + 7 ❯ Curl.<anonymous> test/curl/callbacks.spec.ts:222:31 ❯ Curl.emit node:events:517:28 ❯ Curl.onError lib/Curl.ts:312:10 ❯ Easy.<anonymous> lib/Curl.ts:101:19 This error originated in "test/curl/callbacks.spec.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "should abort request on false". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

AssertionError: expected 'Couldn\'t connect to server' to be 'thrown error inside callback' // Object.is equality Expected: "thrown error inside callback" Received: "Couldn't connect to server" ❯ Curl.<anonymous> test/curl/callbacks.spec.ts:254:35 ❯ Curl.emit node:events:517:28 ❯ Curl.onError lib/Curl.ts:312:10 ❯ Easy.<anonymous> lib/Curl.ts:101:19 This error originated in "test/curl/callbacks.spec.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "should rethrow error thrown inside callback". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

AssertionError: expected 'Couldn\'t connect to server' to be 'Return value from the Trailer callbac…' // Object.is equality Expected: "Return value from the Trailer callback must be an array of strings or false." Received: "Couldn't connect to server" ❯ Curl.<anonymous> test/curl/callbacks.spec.ts:287:35 ❯ Curl.emit node:events:517:28 ❯ Curl.onError lib/Curl.ts:312:10 ❯ Easy.<anonymous> lib/Curl.ts:101:19 This error originated in "test/curl/callbacks.spec.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "should throw an error on invalid return value". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

AssertionError: expected false to be true // Object.is equality - Expected + Received - true + false ❯ Curl.<anonymous> test/curl/callbacks.spec.ts:339:31 ❯ Curl.emit node:events:517:28 ❯ Curl.onError lib/Curl.ts:312:10 ❯ Easy.<anonymous> lib/Curl.ts:101:19 This error originated in "test/curl/callbacks.spec.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "should abort request on Abort return value". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

AssertionError: expected false to be true // Object.is equality - Expected + Received - true + false ❯ Curl.<anonymous> test/curl/callbacks.spec.ts:363:31 ❯ Curl.emit node:events:517:28 ❯ Curl.onError lib/Curl.ts:312:10 ❯ Easy.<anonymous> lib/Curl.ts:101:19 This error originated in "test/curl/callbacks.spec.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "should rethrow error thrown inside callback". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

AssertionError: expected false to be true // Object.is equality - Expected + Received - true + false ❯ Curl.<anonymous> test/curl/callbacks.spec.ts:389:31 ❯ Curl.emit node:events:517:28 ❯ Curl.onError lib/Curl.ts:312:10 ❯ Easy.<anonymous> lib/Curl.ts:101:19 This error originated in "test/curl/callbacks.spec.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "should throw an error on invalid return value". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

AssertionError: expected [Function] to throw error matching /^Response body parser for/ but got 'Couldn\'t connect to server' - Expected: /^Response body parser for/ + Received: "Couldn't connect to server" ❯ test/curl/curly.spec.ts:265:7

AssertionError: expected [Function] to throw error matching /^`curlyResponseBodyParser` passed to …/ but got 'Couldn\'t connect to server' - Expected: /^`curlyResponseBodyParser` passed to curly must be/ + Received: "Couldn't connect to server" ❯ test/curl/curly.spec.ts:277:7

AssertionError: expected [Function] to throw error matching /^error here/ but got 'Couldn\'t connect to server' - Expected: /^error here/ + Received: "Couldn't connect to server" ❯ test/curl/curly.spec.ts:291:7

AssertionError: expected Error: Couldn't connect to server to be an instance of TypeError ❯ Proxy.<anonymous> node_modules/@vitest/expect/dist/index.js:1336:17 ❯ Proxy.<anonymous> node_modules/@vitest/expect/dist/index.js:972:17 ❯ Proxy.methodWrapper node_modules/chai/chai.js:1610:25 ❯ Curl.<anonymous> test/curl/callbacks.spec.ts:136:25 ❯ Curl.emit node:events:519:28 ❯ Curl.onError lib/Curl.ts:312:10 ❯ Easy.<anonymous> lib/Curl.ts:101:19 This error originated in "test/curl/callbacks.spec.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "should not accept undefined return". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

AssertionError: expected 7 to be 42 // Object.is equality - Expected + Received - 42 + 7 ❯ Curl.<anonymous> test/curl/callbacks.spec.ts:222:31 ❯ Curl.emit node:events:519:28 ❯ Curl.onError lib/Curl.ts:312:10 ❯ Easy.<anonymous> lib/Curl.ts:101:19 This error originated in "test/curl/callbacks.spec.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "should abort request on false". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

AssertionError: expected 'Couldn\'t connect to server' to be 'thrown error inside callback' // Object.is equality Expected: "thrown error inside callback" Received: "Couldn't connect to server" ❯ Curl.<anonymous> test/curl/callbacks.spec.ts:254:35 ❯ Curl.emit node:events:519:28 ❯ Curl.onError lib/Curl.ts:312:10 ❯ Easy.<anonymous> lib/Curl.ts:101:19 This error originated in "test/curl/callbacks.spec.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "should rethrow error thrown inside callback". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

AssertionError: expected 'Couldn\'t connect to server' to be 'Return value from the Trailer callbac…' // Object.is equality Expected: "Return value from the Trailer callback must be an array of strings or false." Received: "Couldn't connect to server" ❯ Curl.<anonymous> test/curl/callbacks.spec.ts:287:35 ❯ Curl.emit node:events:519:28 ❯ Curl.onError lib/Curl.ts:312:10 ❯ Easy.<anonymous> lib/Curl.ts:101:19 This error originated in "test/curl/callbacks.spec.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "should throw an error on invalid return value". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

AssertionError: expected false to be true // Object.is equality - Expected + Received - true + false ❯ Curl.<anonymous> test/curl/callbacks.spec.ts:339:31 ❯ Curl.emit node:events:519:28 ❯ Curl.onError lib/Curl.ts:312:10 ❯ Easy.<anonymous> lib/Curl.ts:101:19 This error originated in "test/curl/callbacks.spec.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "should abort request on Abort return value". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

AssertionError: expected false to be true // Object.is equality - Expected + Received - true + false ❯ Curl.<anonymous> test/curl/callbacks.spec.ts:363:31 ❯ Curl.emit node:events:519:28 ❯ Curl.onError lib/Curl.ts:312:10 ❯ Easy.<anonymous> lib/Curl.ts:101:19 This error originated in "test/curl/callbacks.spec.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "should rethrow error thrown inside callback". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

AssertionError: expected false to be true // Object.is equality - Expected + Received - true + false ❯ Curl.<anonymous> test/curl/callbacks.spec.ts:389:31 ❯ Curl.emit node:events:519:28 ❯ Curl.onError lib/Curl.ts:312:10 ❯ Easy.<anonymous> lib/Curl.ts:101:19 This error originated in "test/curl/callbacks.spec.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "should throw an error on invalid return value". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

AssertionError: expected [Function] to throw error matching /^Response body parser for/ but got 'Couldn\'t connect to server' - Expected: /^Response body parser for/ + Received: "Couldn't connect to server" ❯ test/curl/curly.spec.ts:265:7

AssertionError: expected [Function] to throw error matching /^`curlyResponseBodyParser` passed to …/ but got 'Couldn\'t connect to server' - Expected: /^`curlyResponseBodyParser` passed to curly must be/ + Received: "Couldn't connect to server" ❯ test/curl/curly.spec.ts:277:7

AssertionError: expected [Function] to throw error matching /^error here/ but got 'Couldn\'t connect to server' - Expected: /^error here/ + Received: "Couldn't connect to server" ❯ test/curl/curly.spec.ts:291:7

AssertionError: expected Error: Couldn't connect to server to be an instance of TypeError ❯ Proxy.<anonymous> node_modules/@vitest/expect/dist/index.js:1336:17 ❯ Proxy.<anonymous> node_modules/@vitest/expect/dist/index.js:972:17 ❯ Proxy.methodWrapper node_modules/chai/chai.js:1610:25 ❯ Curl.<anonymous> test/curl/callbacks.spec.ts:136:25 ❯ Curl.emit node:events:524:28 ❯ Curl.onError lib/Curl.ts:312:10 ❯ Easy.<anonymous> lib/Curl.ts:101:19 This error originated in "test/curl/callbacks.spec.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "should not accept undefined return". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

AssertionError: expected 7 to be 42 // Object.is equality - Expected + Received - 42 + 7 ❯ Curl.<anonymous> test/curl/callbacks.spec.ts:222:31 ❯ Curl.emit node:events:524:28 ❯ Curl.onError lib/Curl.ts:312:10 ❯ Easy.<anonymous> lib/Curl.ts:101:19 This error originated in "test/curl/callbacks.spec.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "should abort request on false". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

AssertionError: expected 'Couldn\'t connect to server' to be 'thrown error inside callback' // Object.is equality Expected: "thrown error inside callback" Received: "Couldn't connect to server" ❯ Curl.<anonymous> test/curl/callbacks.spec.ts:254:35 ❯ Curl.emit node:events:524:28 ❯ Curl.onError lib/Curl.ts:312:10 ❯ Easy.<anonymous> lib/Curl.ts:101:19 This error originated in "test/curl/callbacks.spec.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "should rethrow error thrown inside callback". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

AssertionError: expected 'Couldn\'t connect to server' to be 'Return value from the Trailer callbac…' // Object.is equality Expected: "Return value from the Trailer callback must be an array of strings or false." Received: "Couldn't connect to server" ❯ Curl.<anonymous> test/curl/callbacks.spec.ts:287:35 ❯ Curl.emit node:events:524:28 ❯ Curl.onError lib/Curl.ts:312:10 ❯ Easy.<anonymous> lib/Curl.ts:101:19 This error originated in "test/curl/callbacks.spec.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "should throw an error on invalid return value". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

AssertionError: expected false to be true // Object.is equality - Expected + Received - true + false ❯ Curl.<anonymous> test/curl/callbacks.spec.ts:339:31 ❯ Curl.emit node:events:524:28 ❯ Curl.onError lib/Curl.ts:312:10 ❯ Easy.<anonymous> lib/Curl.ts:101:19 This error originated in "test/curl/callbacks.spec.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "should abort request on Abort return value". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

AssertionError: expected false to be true // Object.is equality - Expected + Received - true + false ❯ Curl.<anonymous> test/curl/callbacks.spec.ts:363:31 ❯ Curl.emit node:events:524:28 ❯ Curl.onError lib/Curl.ts:312:10 ❯ Easy.<anonymous> lib/Curl.ts:101:19 This error originated in "test/curl/callbacks.spec.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "should rethrow error thrown inside callback". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

AssertionError: expected false to be true // Object.is equality - Expected + Received - true + false ❯ Curl.<anonymous> test/curl/callbacks.spec.ts:389:31 ❯ Curl.emit node:events:524:28 ❯ Curl.onError lib/Curl.ts:312:10 ❯ Easy.<anonymous> lib/Curl.ts:101:19 This error originated in "test/curl/callbacks.spec.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "should throw an error on invalid return value". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

AssertionError: expected [Function] to throw error matching /^Response body parser for/ but got 'Couldn\'t connect to server' - Expected: /^Response body parser for/ + Received: "Couldn't connect to server" ❯ test/curl/curly.spec.ts:265:7

AssertionError: expected [Function] to throw error matching /^`curlyResponseBodyParser` passed to …/ but got 'Couldn\'t connect to server' - Expected: /^`curlyResponseBodyParser` passed to curly must be/ + Received: "Couldn't connect to server" ❯ test/curl/curly.spec.ts:277:7

AssertionError: expected [Function] to throw error matching /^error here/ but got 'Couldn\'t connect to server' - Expected: /^error here/ + Received: "Couldn't connect to server" ❯ test/curl/curly.spec.ts:291:7

AssertionError: expected Error: Couldn't connect to server to be an instance of TypeError ❯ Proxy.<anonymous> node_modules/@vitest/expect/dist/index.js:1336:17 ❯ Proxy.<anonymous> node_modules/@vitest/expect/dist/index.js:972:17 ❯ Proxy.methodWrapper node_modules/chai/chai.js:1610:25 ❯ Curl.<anonymous> test/curl/callbacks.spec.ts:136:25 ❯ Curl.emit node:events:518:28 ❯ Curl.onError lib/Curl.ts:312:10 ❯ Easy.<anonymous> lib/Curl.ts:101:19 This error originated in "test/curl/callbacks.spec.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "should not accept undefined return". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

AssertionError: expected 7 to be 42 // Object.is equality - Expected + Received - 42 + 7 ❯ Curl.<anonymous> test/curl/callbacks.spec.ts:222:31 ❯ Curl.emit node:events:518:28 ❯ Curl.onError lib/Curl.ts:312:10 ❯ Easy.<anonymous> lib/Curl.ts:101:19 This error originated in "test/curl/callbacks.spec.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "should abort request on false". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

AssertionError: expected 'Couldn\'t connect to server' to be 'thrown error inside callback' // Object.is equality Expected: "thrown error inside callback" Received: "Couldn't connect to server" ❯ Curl.<anonymous> test/curl/callbacks.spec.ts:254:35 ❯ Curl.emit node:events:518:28 ❯ Curl.onError lib/Curl.ts:312:10 ❯ Easy.<anonymous> lib/Curl.ts:101:19 This error originated in "test/curl/callbacks.spec.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "should rethrow error thrown inside callback". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

AssertionError: expected 'Couldn\'t connect to server' to be 'Return value from the Trailer callbac…' // Object.is equality Expected: "Return value from the Trailer callback must be an array of strings or false." Received: "Couldn't connect to server" ❯ Curl.<anonymous> test/curl/callbacks.spec.ts:287:35 ❯ Curl.emit node:events:518:28 ❯ Curl.onError lib/Curl.ts:312:10 ❯ Easy.<anonymous> lib/Curl.ts:101:19 This error originated in "test/curl/callbacks.spec.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "should throw an error on invalid return value". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

AssertionError: expected false to be true // Object.is equality - Expected + Received - true + false ❯ Curl.<anonymous> test/curl/callbacks.spec.ts:339:31 ❯ Curl.emit node:events:518:28 ❯ Curl.onError lib/Curl.ts:312:10 ❯ Easy.<anonymous> lib/Curl.ts:101:19 This error originated in "test/curl/callbacks.spec.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "should abort request on Abort return value". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

AssertionError: expected false to be true // Object.is equality - Expected + Received - true + false ❯ Curl.<anonymous> test/curl/callbacks.spec.ts:363:31 ❯ Curl.emit node:events:518:28 ❯ Curl.onError lib/Curl.ts:312:10 ❯ Easy.<anonymous> lib/Curl.ts:101:19 This error originated in "test/curl/callbacks.spec.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "should rethrow error thrown inside callback". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

AssertionError: expected false to be true // Object.is equality - Expected + Received - true + false ❯ Curl.<anonymous> test/curl/callbacks.spec.ts:389:31 ❯ Curl.emit node:events:518:28 ❯ Curl.onError lib/Curl.ts:312:10 ❯ Easy.<anonymous> lib/Curl.ts:101:19 This error originated in "test/curl/callbacks.spec.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "should throw an error on invalid return value". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

AssertionError: expected [Function] to throw error matching /^Response body parser for/ but got 'Couldn\'t connect to server' - Expected: /^Response body parser for/ + Received: "Couldn't connect to server" ❯ test/curl/curly.spec.ts:265:7

AssertionError: expected [Function] to throw error matching /^`curlyResponseBodyParser` passed to …/ but got 'Couldn\'t connect to server' - Expected: /^`curlyResponseBodyParser` passed to curly must be/ + Received: "Couldn't connect to server" ❯ test/curl/curly.spec.ts:277:7

AssertionError: expected [Function] to throw error matching /^error here/ but got 'Couldn\'t connect to server' - Expected: /^error here/ + Received: "Couldn't connect to server" ❯ test/curl/curly.spec.ts:291:7

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

Treating cmake as a formula. For the cask, use homebrew/cask/cmake or specify the `--cask` flag. To silence this message, use the `--formula` flag.

wget 1.25.0 is already installed and up-to-date. To reinstall 1.25.0, run: brew reinstall wget

cmake 3.31.2 is already installed and up-to-date. To reinstall 3.31.2, run: brew reinstall cmake

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

Treating cmake as a formula. For the cask, use homebrew/cask/cmake or specify the `--cask` flag. To silence this message, use the `--formula` flag.

wget 1.25.0 is already installed and up-to-date. To reinstall 1.25.0, run: brew reinstall wget

cmake 3.31.2 is already installed and up-to-date. To reinstall 3.31.2, run: brew reinstall cmake

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

Treating cmake as a formula. For the cask, use homebrew/cask/cmake or specify the `--cask` flag. To silence this message, use the `--formula` flag.

wget 1.25.0 is already installed and up-to-date. To reinstall 1.25.0, run: brew reinstall wget

cmake 3.31.2 is already installed and up-to-date. To reinstall 3.31.2, run: brew reinstall cmake

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

Treating cmake as a formula. For the cask, use homebrew/cask/cmake or specify the `--cask` flag. To silence this message, use the `--formula` flag.

wget 1.25.0 is already installed and up-to-date. To reinstall 1.25.0, run: brew reinstall wget

cmake 3.31.2 is already installed and up-to-date. To reinstall 3.31.2, run: brew reinstall cmake

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

Treating cmake as a formula. For the cask, use homebrew/cask/cmake or specify the `--cask` flag. To silence this message, use the `--formula` flag.

wget 1.25.0 is already installed and up-to-date. To reinstall 1.25.0, run: brew reinstall wget

cmake 3.31.2 is already installed and up-to-date. To reinstall 3.31.2, run: brew reinstall cmake

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

Treating cmake as a formula. For the cask, use homebrew/cask/cmake or specify the `--cask` flag. To silence this message, use the `--formula` flag.

wget 1.25.0 is already installed and up-to-date. To reinstall 1.25.0, run: brew reinstall wget

cmake 3.31.2 is already installed and up-to-date. To reinstall 3.31.2, run: brew reinstall cmake

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

Treating cmake as a formula. For the cask, use homebrew/cask/cmake or specify the `--cask` flag. To silence this message, use the `--formula` flag.

wget 1.25.0 is already installed and up-to-date. To reinstall 1.25.0, run: brew reinstall wget

cmake 3.31.2 is already installed and up-to-date. To reinstall 3.31.2, run: brew reinstall cmake

Treating cmake as a formula. For the cask, use homebrew/cask/cmake or specify the `--cask` flag. To silence this message, use the `--formula` flag.

wget 1.25.0 is already installed and up-to-date. To reinstall 1.25.0, run: brew reinstall wget

cmake 3.31.2 is already installed and up-to-date. To reinstall 3.31.2, run: brew reinstall cmake

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

Treating cmake as a formula. For the cask, use homebrew/cask/cmake or specify the `--cask` flag. To silence this message, use the `--formula` flag.

wget 1.25.0 is already installed and up-to-date. To reinstall 1.25.0, run: brew reinstall wget

cmake 3.31.2 is already installed and up-to-date. To reinstall 3.31.2, run: brew reinstall cmake

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

Treating cmake as a formula. For the cask, use homebrew/cask/cmake or specify the `--cask` flag. To silence this message, use the `--formula` flag.

wget 1.25.0 is already installed and up-to-date. To reinstall 1.25.0, run: brew reinstall wget

cmake 3.31.2 is already installed and up-to-date. To reinstall 3.31.2, run: brew reinstall cmake