[Bug][Sonarqube] data too long

[irkhamdayat]

Search before asking

• [ ] I had searched in the issues and found no similar issues.

What happened

When running collect data sonarqube i am getting error that "data too long for column name. when i check in the mysql table column name varchar was 500

What do you expect to happen

The process should end without an error.

How to reproduce

Add SonarQube project and run.

Anything else

No response

Version

v0.21.0@ac4f7fe

Are you willing to submit PR?

• [ ] Yes I am willing to submit a PR!

Code of Conduct

• [X] I agree to follow this project's Code of Conduct

[dosubot[bot]]

Hey @irkhamdayat! 👋 I'm here to help you with any bugs, questions, or becoming a contributor. I'll assist you while waiting for a human maintainer.

To resolve the "data too long for column name" error in the _tool_sonarqube_scope_configs table during the data collection process for SonarQube in version v0.21.0@ac4f7fe, you can manually change the field length to varchar(255) or longer in MySQL.

Execute the following SQL command to increase the length of the name column:

ALTER TABLE _tool_sonarqube_scope_configs MODIFY COLUMN name VARCHAR(255);

This should resolve the error you're encountering ^[1].

To continue talking to Dosu, mention @dosu.

[irkhamdayat]

i was increase the lenght of the name, still get error

[d4x1]

@irkhamdayat I think it's name field in table _tool_sonarqube_accounts.

Can you check the actual length of account names in your SonarQube ?

We can update this column to a proper length later.

[irkhamhidayat]

my lenght of account names in _tool_sonarqube_accounts is

[d4x1]

@irkhamdayat I mean the username's length in sonarqube, not in devlake's database. We should change database's fields according to the real name's length.

[github-actions[bot]]

This issue has been automatically marked as stale because it has been inactive for 60 days. It will be closed in next 7 days if no further activity occurs.

[abeizn]

@irkhamhidayat You can try changing the 'name' field in the '_tool_sonarqube_accounts' table and the 'full_name' field in the 'accounts' table to 'text' type, and then try again. It seems you have some dirty data or very special data that is causing the 'name' field to be too long. We apologize, but we can't indefinitely expand the field length to accommodate all possible data, as no other users have encountered the same issue. So, we can only trouble you to make this temporary change for now.