Release version 0.4.1 #13
Annotations
39 warnings
build (ubuntu-latest)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-dotnet@v1, simon-k/dotnet-code-coverage-badge@v1.0.0. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
build (ubuntu-latest):
src/Toimik.CommonCrawl/Wat/WatRecordFactory.cs#L65
Possible null reference argument for parameter 'digestFactory' in 'WatMetadataRecord.WatMetadataRecord(string version, Uri recordId, DateTime date, DigestFactory digestFactory, Uri baseUrl)'.
|
build (ubuntu-latest):
tests/Toimik.CommonCrawl.Tests/WatUrlExtractorTest.cs#L51
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits.
|
build (ubuntu-latest):
tests/Toimik.CommonCrawl.Tests/WatUrlExtractorTest.cs#L92
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits.
|
build (ubuntu-latest):
tests/Toimik.CommonCrawl.Tests/WatUrlExtractorTest.cs#L149
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits.
|
build (ubuntu-latest):
tests/Toimik.CommonCrawl.Tests/WarcParserStreamerTest.cs#L62
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits.
|
build (ubuntu-latest):
tests/Toimik.CommonCrawl.Tests/WatUrlExtractorTest.cs#L199
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits.
|
build (ubuntu-latest):
tests/Toimik.CommonCrawl.Tests/WatUrlExtractorTest.cs#L263
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits.
|
build (ubuntu-latest):
tests/Toimik.CommonCrawl.Tests/WatUrlExtractorTest.cs#L234
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits.
|
build (ubuntu-latest):
tests/Toimik.CommonCrawl.Tests/WarcParserStreamerTest.cs#L177
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits.
|
build (ubuntu-latest):
tests/Toimik.CommonCrawl.Tests/WarcParserStreamerTest.cs#L125
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits.
|
build (ubuntu-latest)
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/
|
build (ubuntu-latest)
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/
|
build (macos-latest)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-dotnet@v1, simon-k/dotnet-code-coverage-badge@v1.0.0. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
build (macos-latest)
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/
|
build (macos-latest)
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/
|
build (macos-latest):
src/Toimik.CommonCrawl/Wat/WatRecordFactory.cs#L65
Possible null reference argument for parameter 'digestFactory' in 'WatMetadataRecord.WatMetadataRecord(string version, Uri recordId, DateTime date, DigestFactory digestFactory, Uri baseUrl)'.
|
build (macos-latest):
tests/Toimik.CommonCrawl.Tests/WatUrlExtractorTest.cs#L51
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits. (https://xunit.net/xunit.analyzers/rules/xUnit1030)
|
build (macos-latest):
tests/Toimik.CommonCrawl.Tests/WatUrlExtractorTest.cs#L92
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits. (https://xunit.net/xunit.analyzers/rules/xUnit1030)
|
build (macos-latest):
tests/Toimik.CommonCrawl.Tests/WatUrlExtractorTest.cs#L149
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits. (https://xunit.net/xunit.analyzers/rules/xUnit1030)
|
build (macos-latest):
tests/Toimik.CommonCrawl.Tests/WarcParserStreamerTest.cs#L62
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits. (https://xunit.net/xunit.analyzers/rules/xUnit1030)
|
build (macos-latest):
tests/Toimik.CommonCrawl.Tests/WarcParserStreamerTest.cs#L125
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits. (https://xunit.net/xunit.analyzers/rules/xUnit1030)
|
build (macos-latest):
tests/Toimik.CommonCrawl.Tests/WatUrlExtractorTest.cs#L199
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits. (https://xunit.net/xunit.analyzers/rules/xUnit1030)
|
build (macos-latest):
tests/Toimik.CommonCrawl.Tests/WarcParserStreamerTest.cs#L177
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits. (https://xunit.net/xunit.analyzers/rules/xUnit1030)
|
build (macos-latest):
tests/Toimik.CommonCrawl.Tests/WarcParserStreamerTest.cs#L211
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits. (https://xunit.net/xunit.analyzers/rules/xUnit1030)
|
build (macos-latest):
tests/Toimik.CommonCrawl.Tests/WarcParserStreamerTest.cs#L237
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits. (https://xunit.net/xunit.analyzers/rules/xUnit1030)
|
build (windows-latest)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-dotnet@v1, simon-k/dotnet-code-coverage-badge@v1.0.0. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
build (windows-latest):
src/Toimik.CommonCrawl/Wat/WatRecordFactory.cs#L65
Possible null reference argument for parameter 'digestFactory' in 'WatMetadataRecord.WatMetadataRecord(string version, Uri recordId, DateTime date, DigestFactory digestFactory, Uri baseUrl)'.
|
build (windows-latest):
tests/Toimik.CommonCrawl.Tests/WatUrlExtractorTest.cs#L51
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits.
|
build (windows-latest):
tests/Toimik.CommonCrawl.Tests/WatUrlExtractorTest.cs#L92
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits.
|
build (windows-latest):
tests/Toimik.CommonCrawl.Tests/WatUrlExtractorTest.cs#L149
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits.
|
build (windows-latest):
tests/Toimik.CommonCrawl.Tests/WatUrlExtractorTest.cs#L199
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits.
|
build (windows-latest):
tests/Toimik.CommonCrawl.Tests/WatUrlExtractorTest.cs#L234
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits.
|
build (windows-latest):
tests/Toimik.CommonCrawl.Tests/WatUrlExtractorTest.cs#L263
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits.
|
build (windows-latest):
tests/Toimik.CommonCrawl.Tests/WarcParserStreamerTest.cs#L125
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits.
|
build (windows-latest):
tests/Toimik.CommonCrawl.Tests/WarcParserStreamerTest.cs#L62
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits.
|
build (windows-latest):
tests/Toimik.CommonCrawl.Tests/WarcParserStreamerTest.cs#L177
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits.
|
build (windows-latest)
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/
|
build (windows-latest)
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/
|