Skip to content

chore: fix 'Dereference of a possibly null reference.' warning #5317

chore: fix 'Dereference of a possibly null reference.' warning

chore: fix 'Dereference of a possibly null reference.' warning #5317

Triggered via pull request November 19, 2024 09:47
Status Success
Total duration 1m 43s
Artifacts

code-style.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

8 warnings
build
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-dotnet@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
build
The target framework 'net7.0' is out of support and will not receive security updates in the future. Please refer to https://aka.ms/dotnet-core-support for more information about the support policy.
build
The target framework 'net7.0' is out of support and will not receive security updates in the future. Please refer to https://aka.ms/dotnet-core-support for more information about the support policy.
build
The target framework 'net7.0' is out of support and will not receive security updates in the future. Please refer to https://aka.ms/dotnet-core-support for more information about the support policy.
build: src/Playwright.Tests/TestConstants.cs#L28
'TimeoutAttribute' is obsolete: '.NET No longer supports aborting threads as it is not a safe thing to do. Update your tests to use CancelAfterAttribute instead'
build
The target framework 'net7.0' is out of support and will not receive security updates in the future. Please refer to https://aka.ms/dotnet-core-support for more information about the support policy.
build
The target framework 'net7.0' is out of support and will not receive security updates in the future. Please refer to https://aka.ms/dotnet-core-support for more information about the support policy.
build: src/Playwright.Tests/TestConstants.cs#L28
'TimeoutAttribute' is obsolete: '.NET No longer supports aborting threads as it is not a safe thing to do. Update your tests to use CancelAfterAttribute instead'