Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

log_data should be a LONGBLOB #1022

Closed
4 tasks done
danog opened this issue Jul 12, 2022 · 0 comments · Fixed by #1050
Closed
4 tasks done

log_data should be a LONGBLOB #1022

danog opened this issue Jul 12, 2022 · 0 comments · Fixed by #1050
Labels
bug Something isn't working
Milestone

Comments

@danog
Copy link

danog commented Jul 12, 2022

Component

agent

Describe the bug

logs.log_data should be a LONGBLOB or greater: particularly long log lines (>65kb) causes issues with mysql's default BLOB type used by xorm for byte arrays: manually altering the table fixed the issue for me, but it would be probably better to alter the type for everyone :)
I don't use pipeline artifacts, but I bet the same problem would be present in files bigger than 65kb when using mysql.

System Info

`woodpeckerci/woodpecker-agent:next` on arm64

Additional context

No response

Validations

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants