From cedd61592201b4e9870ec5146a6bfcc8ff6ef36c Mon Sep 17 00:00:00 2001 From: TPTBusiness Date: Fri, 17 Apr 2026 22:38:15 +0200 Subject: [PATCH] fix(ci): set JAVA_TOOL_OPTIONS UTF-8 in Codacy workflow Fixes MalformedInputException when Codacy SARIF formatter reads Python files containing non-ASCII characters. Co-Authored-By: Claude Sonnet 4.6 --- .github/workflows/codacy.yml | 7 ++----- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/.github/workflows/codacy.yml b/.github/workflows/codacy.yml index 1b7f8a8f..6e23c782 100644 --- a/.github/workflows/codacy.yml +++ b/.github/workflows/codacy.yml @@ -41,17 +41,14 @@ jobs: # Execute Codacy Analysis CLI and generate a SARIF output with the security issues identified during the analysis - name: Run Codacy Analysis CLI uses: codacy/codacy-analysis-cli-action@d840f886c4bd4edc059706d09c6a1586111c540b + env: + JAVA_TOOL_OPTIONS: "-Dfile.encoding=UTF-8" with: - # Check https://github.com/codacy/codacy-analysis-cli#project-token to get your project token from your Codacy repository - # You can also omit the token and run the tools that support default configurations project-token: ${{ secrets.CODACY_PROJECT_TOKEN }} verbose: true output: results.sarif format: sarif - # Adjust severity of non-security issues gh-code-scanning-compat: true - # Force 0 exit code to allow SARIF file generation - # This will handover control about PR rejection to the GitHub side max-allowed-issues: 2147483647 # Upload the SARIF file generated in the previous step