[Bug][Azure DevOps] subtask collectAzuredevopsBuilds ended unexpectedly

[ichuniaiev]

Search before asking

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

What happened

time="2024-04-17 09:58:17" level=error msg=" [pipeline service] [pipeline #1] [task #2] [collectAzuredevopsBuilds] ERROR: DataError: (raised as a result of Query-invoked autoflush; consider using a session.no_autoflush block if this flush is occurring prematurely)"
time="2024-04-17 09:58:17" level=error msg=" [pipeline service] [pipeline #1] [task #2] [collectAzuredevopsBuilds] (MySQLdb.DataError) (1406, \"Data too long for column 'url' at row 1\")"
time="2024-04-17 09:58:17" level=error msg=" [pipeline service] [pipeline #1] [task #2] [collectAzuredevopsBuilds] [SQL: INSERT INTO _raw_azuredevops_builds (params, data, url, input, created_at) VALUES (%!!(MISSING)s(MISSING), %!!(MISSING)s(MISSING), %!!(MISSING)s(MISSING), %!!(MISSING)s(MISSING), %!!(MISSING)s(MISSING))]"

What do you expect to happen

The pipeline runs without an error.

How to reproduce

I checked it on my private Azure DevOps project.
But flow was standard: Create project; configure data connection; run collect data
I've used python plugin

Anything else

every run

Version

v1.0.0-beta1, v1.0.0-beta4

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

[klesh]

Was it the python or the golang version?

[ichuniaiev]

Was it the python or the golang version?

It's a python version

[klesh]

Would you like to try the go version and see if it fixes your problem?

[ichuniaiev]

yeah, with go version it works perfectly, but fails on shallow clone :)
That's why I've raised another issue for it - #7343

[Startrekzky]

For users who have encountered this issue, please use the Go version Azure plugin as a workaround. This issue will be fixed later.

[klesh]

@ichuniaiev The shallow clone issue has been fixed

[github-actions]

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.

[github-actions]

This issue has been closed because it has been inactive for a long time. You can reopen it if you encounter the similar problem in the future.