rgcouto opened a new issue, #8471: URL: https://github.com/apache/incubator-devlake/issues/8471
## What and why to refactor I've encountered an issue with running SonarQube Cloud analysis where the task would fail consistently due to the `component` column being too small on certain tables. The error I'd see on logs was: > time="2025-06-18 08:32:04" level=error msg=" [pipeline service] [pipeline #8] [task #78] subtask convertIssueCodeBlocks ended unexpectedly\n\tWraps: (2) error adding result to batch (500)\n\tWraps: (3) Error 1406 (22001): Data too long for column 'component' at row 95 (500)\n\tWraps: (4) Error 1406 (22001): Data too long for column 'component' at row 95\n\tError types: (1) *hintdetail.withDetail (2) *hintdetail.withDetail (3) *hintdetail.withDetail (4) *mysql.MySQLError" This error would lead to a failed analysis with consequently failing everything else on that Blueprint pipeline. ## Describe the solution you'd like I've figured out that changing the type of the `component` column on the database on tables `cq_issue_code_blocks` and `_tool_sonarqube_issue_code_blocks`, to `varchar(500)` did the trick. There might be other tables where this could also be applicable, probably. If you find this useful I think it would be a good improvement. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@devlake.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
