Fix/code smells 720 #238
Triggered via pull request
April 2, 2026 11:35
Schmarvinius
opened
#775
Status
Success
Total duration
26m 11s
Artifacts
2
pr.yml
on: pull_request_target
Waiting for PR approval as this workflow runs on pull_request_target
0s
Matrix: build-and-test / build
Matrix: build-and-test / integration-tests
build-and-test
/
SonarQube Scan
3m 3s
build-and-test
/
Deploy snapshot to Artifactory
0s
Annotations
20 errors and 41 warnings
|
build-and-test / Build (Java 17)
2026-04-02 11:42:09,178 ERROR [main] []: Exception on update (service 'PersistenceService$Default', event 'UPDATE', entity 'TestService.Items.attachments') [com.sap.cds.adapter.odata.v4.processors.CdsProcessor] [2c62f8a3-13e4-47d4-9e42-903c8ec7f698]
|
|
build-and-test / Build (Java 17)
2026-04-02 11:42:09,106 ERROR [main] []: Exception on update (service 'PersistenceService$Default', event 'UPDATE', entity 'TestService.AttachmentEntity') [com.sap.cds.adapter.odata.v4.processors.CdsProcessor] [6a3f7f2d-89ec-4bcd-9e13-bc19f0ba80b7]
|
|
build-and-test / Build (Java 17)
2026-04-02 11:42:07,481 ERROR [main] []: Exception on update (service 'PersistenceService$Default', event 'UPDATE', entity 'TestService.Items.attachments') [com.sap.cds.adapter.odata.v4.processors.CdsProcessor] [39e7c63a-9512-4294-adda-3c021b3b6aae]
|
|
build-and-test / Build (Java 17)
2026-04-02 11:42:06,674 ERROR [main] []: Exception on update (service 'PersistenceService$Default', event 'UPDATE', entity 'TestService.Items.attachments') [com.sap.cds.adapter.odata.v4.processors.CdsProcessor] [ec4f5be4-45d6-4570-aaf2-eb8c5a9cd571]
|
|
build-and-test / Build (Java 17)
2026-04-02 11:42:06,483 ERROR [main] []: Exception on update (service 'PersistenceService$Default', event 'UPDATE', entity 'TestService.AttachmentEntity') [com.sap.cds.adapter.odata.v4.processors.CdsProcessor] [d400bada-869f-46ba-a5dd-6a2e2137af31]
|
|
build-and-test / Build (Java 17)
2026-04-02 11:42:06,484 ERROR [ForkJoinPool.commonPool-worker-1] []: Error scanning attachment 9baa001a-7673-426e-a9a4-ded5a83a04d6 in entity TestService.AttachmentEntity. [com.sap.cds.feature.attachments.service.handler.transaction.EndTransactionMalwareScanRunner] []
|
|
build-and-test / Build (Java 17)
11:40:49.074 [ForkJoinPool.commonPool-worker-2] ERROR com.sap.cds.feature.attachments.service.handler.transaction.EndTransactionMalwareScanRunner -- Error scanning attachment d43e358a-6497-4fa9-9f6b-7ef1b3830a06 in entity null.
|
|
build-and-test / Build (Java 17)
11:40:48.966 [ForkJoinPool.commonPool-worker-2] ERROR com.sap.cds.feature.attachments.service.handler.transaction.EndTransactionMalwareScanRunner -- Error scanning attachment 57b86867-b0c3-4a3d-8d08-8a9fa1c33468 in entity null.
|
|
build-and-test / Build (Java 17)
11:40:45.866 [main] ERROR com.sap.cds.feature.attachments.service.malware.DefaultAttachmentMalwareScanner -- Error while scanning attachment null.
|
|
build-and-test / Build (Java 17)
11:40:45.737 [main] ERROR com.sap.cds.feature.attachments.service.malware.DefaultAttachmentMalwareScanner -- Error while scanning attachment null.
|
|
build-and-test / Build (Java 21)
2026-04-02 11:42:40,645 ERROR [ForkJoinPool.commonPool-worker-1] []: Error scanning attachment 78cf7254-3e1e-4a22-bc6f-26799365af21 in entity TestService.Items.attachments. [com.sap.cds.feature.attachments.service.handler.transaction.EndTransactionMalwareScanRunner] []
|
|
build-and-test / Build (Java 21)
2026-04-02 11:42:40,569 ERROR [main] []: Exception on update (service 'PersistenceService$Default', event 'UPDATE', entity 'TestService.AttachmentEntity') [com.sap.cds.adapter.odata.v4.processors.CdsProcessor] [fd041026-c916-4d98-96ed-294e8ec8a070]
|
|
build-and-test / Build (Java 21)
2026-04-02 11:42:38,766 ERROR [main] []: Exception on update (service 'PersistenceService$Default', event 'UPDATE', entity 'TestService.Items.attachments') [com.sap.cds.adapter.odata.v4.processors.CdsProcessor] [5df26285-3b13-4ce6-9f8d-fda178e9dc04]
|
|
build-and-test / Build (Java 21)
2026-04-02 11:42:37,912 ERROR [main] []: Exception on update (service 'PersistenceService$Default', event 'UPDATE', entity 'TestService.Items.attachments') [com.sap.cds.adapter.odata.v4.processors.CdsProcessor] [866d3230-54dd-4d69-8a69-09f8944a125b]
|
|
build-and-test / Build (Java 21)
2026-04-02 11:42:37,725 ERROR [main] []: Exception on update (service 'PersistenceService$Default', event 'UPDATE', entity 'TestService.AttachmentEntity') [com.sap.cds.adapter.odata.v4.processors.CdsProcessor] [7e6ef83f-26f2-4a00-a0f7-6414e3dd4a76]
|
|
build-and-test / Build (Java 21)
2026-04-02 11:42:37,726 ERROR [ForkJoinPool.commonPool-worker-1] []: Error scanning attachment e7346a9e-70be-4d56-a52e-e2db7abddd37 in entity TestService.AttachmentEntity. [com.sap.cds.feature.attachments.service.handler.transaction.EndTransactionMalwareScanRunner] []
|
|
build-and-test / Build (Java 21)
11:41:12.540 [ForkJoinPool.commonPool-worker-2] ERROR com.sap.cds.feature.attachments.service.handler.transaction.EndTransactionMalwareScanRunner -- Error scanning attachment 29f9cf8d-1fd5-40f2-b380-2a90aa78a97a in entity null.
|
|
build-and-test / Build (Java 21)
11:41:12.435 [ForkJoinPool.commonPool-worker-2] ERROR com.sap.cds.feature.attachments.service.handler.transaction.EndTransactionMalwareScanRunner -- Error scanning attachment 4b7be1bb-cbb9-4ff3-9f5a-6fc7af8048a8 in entity null.
|
|
build-and-test / Build (Java 21)
11:41:09.625 [main] ERROR com.sap.cds.feature.attachments.service.malware.DefaultAttachmentMalwareScanner -- Error while scanning attachment null.
|
|
build-and-test / Build (Java 21)
11:41:09.493 [main] ERROR com.sap.cds.feature.attachments.service.malware.DefaultAttachmentMalwareScanner -- Error while scanning attachment null.
|
|
build-and-test / Build (Java 17)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: SAP/project-piper-action@main, stCarolas/setup-maven@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
build-and-test / Build (Java 17)
11:40:49.895 [main] WARN com.sap.cds.feature.attachments.service.malware.client.MalwareScanClientProvider -- Basic authentication for Malware Scanning service is deprecated and will be removed in a future release. Use mTLS authentication instead. See https://help.sap.com/docs/malware-scanning-servce/sap-malware-scanning-service/ for details.
|
|
build-and-test / Build (Java 17)
11:40:49.882 [main] WARN com.sap.cds.feature.attachments.service.malware.client.MalwareScanClientProvider -- Basic authentication for Malware Scanning service is deprecated and will be removed in a future release. Use mTLS authentication instead. See https://help.sap.com/docs/malware-scanning-servce/sap-malware-scanning-service/ for details.
|
|
build-and-test / Build (Java 17)
11:40:49.879 [main] WARN com.sap.cds.feature.attachments.configuration.Registration -- OutboxService 'DefaultOutboxUnordered' is not available. AttachmentService will not be outboxed.
|
|
build-and-test / Build (Java 17)
11:40:49.872 [main] WARN com.sap.cds.feature.attachments.service.malware.client.MalwareScanClientProvider -- Basic authentication for Malware Scanning service is deprecated and will be removed in a future release. Use mTLS authentication instead. See https://help.sap.com/docs/malware-scanning-servce/sap-malware-scanning-service/ for details.
|
|
build-and-test / Build (Java 17)
11:40:48.420 [main] WARN com.sap.cds.feature.attachments.service.malware.client.MalwareScanClientProvider -- Basic authentication for Malware Scanning service is deprecated and will be removed in a future release. Use mTLS authentication instead. See https://help.sap.com/docs/malware-scanning-servce/sap-malware-scanning-service/ for details.
|
|
build-and-test / Build (Java 17)
11:40:48.047 [main] WARN com.sap.cds.feature.attachments.service.malware.client.MalwareScanClientProvider -- Basic authentication for Malware Scanning service is deprecated and will be removed in a future release. Use mTLS authentication instead. See https://help.sap.com/docs/malware-scanning-servce/sap-malware-scanning-service/ for details.
|
|
build-and-test / Build (Java 17)
11:40:46.355 [main] WARN com.sap.cds.feature.attachments.service.malware.client.DefaultMalwareScanClient -- Document is infected with malware, response status from scan was: malwareDetected = true, encryptedContentDetected = true
|
|
build-and-test / Build (Java 17)
11:40:46.347 [main] WARN com.sap.cds.feature.attachments.service.malware.client.DefaultMalwareScanClient -- Document is infected with malware, response status from scan was: malwareDetected = false, encryptedContentDetected = true
|
|
build-and-test / Build (Java 17)
11:40:46.335 [main] WARN com.sap.cds.feature.attachments.service.malware.client.DefaultMalwareScanClient -- Document is infected with malware, response status from scan was: malwareDetected = true, encryptedContentDetected = false
|
|
build-and-test / Build (Java 17)
11:40:45.911 [main] WARN com.sap.cds.feature.attachments.service.malware.DefaultAttachmentMalwareScanner -- More than one attachment found in entity unit.test.Attachment.
|
|
build-and-test / Build (Java 21)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: SAP/project-piper-action@main, stCarolas/setup-maven@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
build-and-test / Build (Java 21)
11:41:11.782 [main] WARN com.sap.cds.feature.attachments.service.malware.client.MalwareScanClientProvider -- Basic authentication for Malware Scanning service is deprecated and will be removed in a future release. Use mTLS authentication instead. See https://help.sap.com/docs/malware-scanning-servce/sap-malware-scanning-service/ for details.
|
|
build-and-test / Build (Java 21)
11:41:11.359 [main] WARN com.sap.cds.feature.attachments.service.malware.client.MalwareScanClientProvider -- Basic authentication for Malware Scanning service is deprecated and will be removed in a future release. Use mTLS authentication instead. See https://help.sap.com/docs/malware-scanning-servce/sap-malware-scanning-service/ for details.
|
|
build-and-test / Build (Java 21)
11:41:10.100 [main] WARN com.sap.cds.feature.attachments.service.malware.client.DefaultMalwareScanClient -- Document is infected with malware, response status from scan was: malwareDetected = true, encryptedContentDetected = true
|
|
build-and-test / Build (Java 21)
11:41:10.091 [main] WARN com.sap.cds.feature.attachments.service.malware.client.DefaultMalwareScanClient -- Document is infected with malware, response status from scan was: malwareDetected = false, encryptedContentDetected = true
|
|
build-and-test / Build (Java 21)
11:41:10.083 [main] WARN com.sap.cds.feature.attachments.service.malware.client.DefaultMalwareScanClient -- Document is infected with malware, response status from scan was: malwareDetected = true, encryptedContentDetected = false
|
|
build-and-test / Build (Java 21)
11:41:09.665 [main] WARN com.sap.cds.feature.attachments.service.malware.DefaultAttachmentMalwareScanner -- More than one attachment found in entity unit.test.Attachment.
|
|
build-and-test / Build (Java 21)
WARNING: Dynamic loading of agents will be disallowed by default in a future release
|
|
build-and-test / Build (Java 21)
WARNING: If a serviceability tool is not in use, please run with -Djdk.instrument.traceUsage for more information
|
|
build-and-test / Build (Java 21)
WARNING: If a serviceability tool is in use, please run with -XX:+EnableDynamicAgentLoading to hide this warning
|
|
build-and-test / Build (Java 21)
WARNING: A Java agent has been loaded dynamically (/home/runner/.m2/repository/net/bytebuddy/byte-buddy-agent/1.17.7/byte-buddy-agent-1.17.7.jar)
|
|
build-and-test / CodeQL Analysis
Starting April 2026, the CodeQL Action will skip computing file coverage information on pull requests to improve analysis performance. File coverage information will still be computed on non-PR analyses.
To opt out of this change, set the `CODEQL_ACTION_FILE_COVERAGE_ON_PRS` environment variable to `true`. Alternatively, create a custom repository property with the name `github-codeql-file-coverage-on-prs` and the type "True/false", then set this property to `true` in the repository's settings.
|
|
build-and-test / CodeQL Analysis
Cannot build an overlay database because build-mode is set to "manual" instead of "none". Falling back to creating a normal full database instead.
|
|
build-and-test / SonarQube Scan
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: SAP/project-piper-action@main, stCarolas/setup-maven@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
build-and-test / SonarQube Scan
11:58:40.245 WARN Invalid character encountered in file /home/runner/work/cds-feature-attachments/cds-feature-attachments/doc/img/Restore_Documents.png at line 1 for encoding UTF-8. Please fix file content or configure the encoding to be used using property 'sonar.sourceEncoding'.
|
|
build-and-test / SonarQube Scan
11:58:40.222 WARN Invalid character encountered in file /home/runner/work/cds-feature-attachments/cds-feature-attachments/doc/img/Delete_Success.vsdx at line 1 for encoding UTF-8. Please fix file content or configure the encoding to be used using property 'sonar.sourceEncoding'.
|
|
build-and-test / SonarQube Scan
11:58:40.217 WARN Invalid character encountered in file /home/runner/work/cds-feature-attachments/cds-feature-attachments/doc/img/Create_Success.png at line 1 for encoding UTF-8. Please fix file content or configure the encoding to be used using property 'sonar.sourceEncoding'.
|
|
build-and-test / SonarQube Scan
11:58:40.200 WARN Invalid character encountered in file /home/runner/work/cds-feature-attachments/cds-feature-attachments/doc/img/Read_wrong_status.vsdx at line 1 for encoding UTF-8. Please fix file content or configure the encoding to be used using property 'sonar.sourceEncoding'.
|
|
build-and-test / SonarQube Scan
11:58:40.176 WARN Invalid character encountered in file /home/runner/work/cds-feature-attachments/cds-feature-attachments/doc/img/Delete_Success.png at line 1 for encoding UTF-8. Please fix file content or configure the encoding to be used using property 'sonar.sourceEncoding'.
|
|
build-and-test / SonarQube Scan
11:58:39.976 WARN Use of preview features have been detected during analysis. Enable DEBUG mode to see them.
|
|
build-and-test / SonarQube Scan
11:58:39.974 WARN Unresolved imports/types have been detected during analysis. Enable DEBUG mode to see them.
|
|
build-and-test / SonarQube Scan
11:58:39.970 WARN Dependencies/libraries were not provided for analysis of SOURCE files. The 'sonar.java.libraries' property is empty. Verify your configuration, as you might end up with less precise results.
|
|
build-and-test / SonarQube Scan
11:58:33.719 WARN Could not find ref 'main' in refs/heads, refs/remotes, refs/remotes/upstream or refs/remotes/origin
|
|
build-and-test / SonarQube Scan
11:58:21.547 WARN File '/home/runner/work/cds-feature-attachments/cds-feature-attachments/v1_501_0/piper' is bigger than 20MB and as consequence is removed from the analysis scope.
|
|
build-and-test / Integration Tests (Java 17, latest-version)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: stCarolas/setup-maven@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
build-and-test / Integration Tests (Java 21, latest-version)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: stCarolas/setup-maven@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
build-and-test / Integration Tests (Java 21, build-version)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: stCarolas/setup-maven@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
build-and-test / Integration Tests (Java 17, build-version)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: stCarolas/setup-maven@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
build-and-test / Integration Tests (Java 21, oss)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: stCarolas/setup-maven@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
build-and-test / Integration Tests (Java 17, oss)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: stCarolas/setup-maven@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
build-artifacts-java-17
Expired
|
1 MB |
sha256:f479d9cd2e0a2c0a72e06301c5e424d3f41bd06f171fe0d30565a58437ada692
|
|
|
build-artifacts-java-21
Expired
|
1.05 MB |
sha256:4639ffb6624228a58730e26cfa01e26ca987cf5a044dd80de5f7b2854d025909
|
|