Skip to content

Resolving category and elems error in fhir converter #554

Resolving category and elems error in fhir converter

Resolving category and elems error in fhir converter #554

Triggered via pull request September 19, 2024 17:53
Status Success
Total duration 4m 20s
Artifacts
python-linting  /  python-linting
12s
python-linting / python-linting
unit-test-python-containers
29s
unit-test-python-containers
integration-test-python-containers
3m 20s
integration-test-python-containers
unit-test-dotnet-fhir-converter
26s
unit-test-dotnet-fhir-converter
build-container
25s
build-container
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
build-container
The following actions use a deprecated Node.js version and will be forced to run on node20: docker/setup-buildx-action@v2, docker/build-push-action@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
unit-test-dotnet-fhir-converter
The following actions use a deprecated Node.js version and will be forced to run on node20: 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/
unit-test-dotnet-fhir-converter: containers/fhir-converter/CustomFhir/CustomFilters.cs#L257
Possible null reference argument for parameter 'data' in 'string Filters.ToHtmlStringJoinBr(object data)'.
unit-test-python-containers
The following actions use a deprecated Node.js version and will be forced to run on node20: codecov/codecov-action@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/