refactor: move message handling internals to use async/await
#1570
Triggered via pull request
November 16, 2025 10:23
arthurschreiber
Status
Failure
Total duration
12m 30s
Artifacts
–
nodejs.yml
on: pull_request
Matrix: test-windows
Matrix: test
Linting
30s
Azure SQL Server / Node.js 18.x
5m 32s
Azure SQL Server / Node.js 18.x
5m 20s
Azure SQL Server / Node.js 18.x
2m 12s
Azure SQL Server / Node.js 18.x
7m 22s
Pre-Release
0s
Annotations
7 errors and 35 warnings
|
Linting
Process completed with exit code 1.
|
|
Linting:
test/integration/rpc-test.js#L11
'config' is defined but never used
|
|
Linting:
src/connection.ts#L3343
Missing semicolon
|
|
Azure SQL Server / Node.js 18.x
Process completed with exit code 6.
|
|
Azure SQL Server / Node.js 18.x
Process completed with exit code 8.
|
|
Azure SQL Server / Node.js 18.x
Process completed with exit code 8.
|
|
Azure SQL Server / Node.js 18.x
Process completed with exit code 2.
|
|
Linting
Failed to restore: Cache service responded with 400
|
|
Azure SQL Server / Node.js 18.x
Failed to restore: Cache service responded with 400
|
|
Azure SQL Server / Node.js 18.x
Failed to restore: Cache service responded with 400
|
|
Azure SQL Server / Node.js 18.x
Failed to restore: Cache service responded with 400
|
|
SQL Server Linux / Node.js 20.x
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0cKcZaQAAAAAemfit30DrRJmRJEs0MYf/UEhMMzBFREdFMDEwNgBFZGdl
|
|
SQL Server Linux / Node.js 20.x
Failed to restore: Cache service responded with 400
|
|
SQL Server Linux / Node.js 21.x
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0dacZaQAAAAD4OhzeRakLT7LAXZMG2cNXUEFPRURHRTA2MDcARWRnZQ==
|
|
SQL Server Linux / Node.js 21.x
Failed to restore: Cache service responded with 400
|
|
SQL Server Linux / Node.js 18.x
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0h6cZaQAAAADRCFvJ8HWEQaAiVk5DS32PUEhMMzBFREdFMDQwOQBFZGdl
|
|
SQL Server Linux / Node.js 18.x
Failed to restore: Cache service responded with 400
|
|
Azure SQL Server / Node.js 18.x
Failed to restore: Cache service responded with 400
|
|
SQL Server 2022 Windows / Node.js 18.x
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0rKgZaQAAAAAaJOPlnpTDSI0xUY/oqTuzUEhMMzBFREdFMDQyMQBFZGdl
|
|
SQL Server 2022 Windows / Node.js 18.x
Failed to restore: Cache service responded with 400
|
|
SQL Server 2022 Windows / Node.js 21.x
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0sagZaQAAAACIUL3Xs3+wTrHkatqEDRqmUEhMMzBFREdFMDExNABFZGdl
|
|
SQL Server 2022 Windows / Node.js 21.x
Failed to restore: Cache service responded with 400
|
|
SQL Server 2019 Windows / Node.js 20.x
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0vKgZaQAAAAD12Sj2wf89T4KY1EgufsX5RE0yRURHRTA5MTcARWRnZQ==
|
|
SQL Server 2019 Windows / Node.js 20.x
Failed to restore: Cache service responded with 400
|
|
SQL Server 2017 Windows / Node.js 21.x
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0vagZaQAAAACVde4jPQzHSqpz4dtBQdpEUEhMMzBFREdFMDEwNgBFZGdl
|
|
SQL Server 2017 Windows / Node.js 21.x
Failed to restore: Cache service responded with 400
|
|
SQL Server 2017 Windows / Node.js 18.x
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0xqgZaQAAAABkIJ9t5UYbS7WePMwClusVUEhMMzBFREdFMDIxNQBFZGdl
|
|
SQL Server 2017 Windows / Node.js 18.x
Failed to restore: Cache service responded with 400
|
|
SQL Server 2022 Windows / Node.js 20.x
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0yqgZaQAAAABL5tRVRMiyR729t8zygEO7UEFPRURHRTA2MDkARWRnZQ==
|
|
SQL Server 2022 Windows / Node.js 20.x
Failed to restore: Cache service responded with 400
|
|
SQL Server 2019 Windows / Node.js 18.x
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>00KgZaQAAAACjWFCrTKlaQoko5BIMqxg8UEhYMzFFREdFMDUxOQBFZGdl
|
|
SQL Server 2019 Windows / Node.js 18.x
Failed to restore: Cache service responded with 400
|
|
SQL Server 2016 Windows / Node.js 18.x
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>00qgZaQAAAADe7KV7eqPnRaPXOCNH4OiAUEhMMzBFREdFMDQyMABFZGdl
|
|
SQL Server 2016 Windows / Node.js 18.x
Failed to restore: Cache service responded with 400
|
|
SQL Server 2019 Windows / Node.js 21.x
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>04qgZaQAAAADtmdIPw8o4QINjjp7l+7mnUEhMMzBFREdFMDQxMwBFZGdl
|
|
SQL Server 2019 Windows / Node.js 21.x
Failed to restore: Cache service responded with 400
|
|
SQL Server 2017 Windows / Node.js 20.x
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>05qgZaQAAAAAbuG1fdCv9T7oQx+JOJ1Q2UEFPRURHRTA2MTYARWRnZQ==
|
|
SQL Server 2017 Windows / Node.js 20.x
Failed to restore: Cache service responded with 400
|
|
SQL Server 2016 Windows / Node.js 21.x
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>07qgZaQAAAABRovXUCXNUSIHAXlZTmUJ4Q0hJMzBFREdFMDIxNABFZGdl
|
|
SQL Server 2016 Windows / Node.js 21.x
Failed to restore: Cache service responded with 400
|
|
SQL Server 2016 Windows / Node.js 20.x
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>08KgZaQAAAACAhSyVtK2kS7chUtslTfJoQ0hJMzBFREdFMDMxOQBFZGdl
|
|
SQL Server 2016 Windows / Node.js 20.x
Failed to restore: Cache service responded with 400
|