[Bug][Azure DevOps Go] Error in extractApiTimelineRecords Data too long for column 'name'

[jmezach]

Search before asking

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

What happened

We are seeing some issues in our environment for some repositories in our Azure DevOps instance. Specifically we're seeing the following error:

subtask extractApiTimelineRecords ended unexpectedly Wraps: (2) Error 1406 (22001): Data too long for column 'name' at row 24 (500) Wraps: (3) Error 1406 (22001): Data too long for column 'name' at row 24 Error types: (1) *hintdetail.withDetail (2) *hintdetail.withDetail (3) *mysql.MySQLError

Looks like the name column is too short for the data we have.

What do you expect to happen

I would expect these repositories to be processed successfully.

How to reproduce

I guess this really depends on the data you have since this does not happen for all our repositories. But it does reproduce fairly consistently.

Anything else

No response

Version

1.0.2-beta6

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Code of Conduct

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

[dosubot]

Hello, @jmezach! I'm here to help you with any bugs, questions, or contributions you have for the project. Let's tackle this issue together!

A similar issue was previously reported regarding a "data too long" error, but it was related to the avatar_url field. The solution suggested was to change the column type from VARCHAR(255) to TEXT to accommodate longer URLs ^[1].

In your case, the name column in the Azure DevOps Go plugin's database schema is currently defined as varchar with a length of 100 ^[2]. You might consider altering the column type to a longer varchar or TEXT to resolve the issue. If you are willing to submit a pull request, you can propose this change to accommodate longer names.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}

[klesh]

Looking forward to your PR

[jmezach]

@klesh I've tested changing the column type of the name column in the _tool_azuredevops_go_timeline_records to text. That worked, but then I ran into an issue with the cicd_tasks table, since that also has a name column so I had to change that to be of type text as well. Now my pipeline is running smoothly.

Is there an objection to also changing the column type for the domain table? Or should we perhaps just truncate the name instead?

[klesh]

@jmezach Hmm, I'm not sure. Both options seem reasonable to me. In my opinion, for most analysis scenarios, it's not crucial to store the entire name. What's your take? Does truncating the name seem acceptable to you?
cc @Startrekzky

[jmezach]

@klesh Yeah, I think truncating the name would be fine. I don't think anything is matching on name at the moment, so it should just work. I'll send in a PR with this change.

[klesh]

I agree.