Skip to content

Conversation

@zeroshade
Copy link
Member

Rationale for this change

Additional checks for io.EOF to avoid flaky tests

@zeroshade zeroshade requested review from kou and lidavidm June 18, 2025 20:54
rows := 0
for rows < maxBatchSize && r.rows.Next() {
if err := r.rows.Scan(r.rowdest...); err != nil {
if err := r.rows.Scan(r.rowdest...); err != nil && err.Error() != io.EOF.Error() {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Huh...it's quite weird that this can return EOF

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

From what I can tell, it's something weird with the sqlite handler implementation. it shouldn't be returning EOF, which looks like it isn't even returning io.EOF and instead just returns the string "EOF" it's really weird.

@zeroshade zeroshade merged commit 146f999 into apache:main Jun 19, 2025
58 of 59 checks passed
@zeroshade zeroshade deleted the additional-eof-checks branch June 19, 2025 14:35
zeroshade added a commit to zeroshade/arrow-go that referenced this pull request Jun 20, 2025
### Rationale for this change
Additional checks for `io.EOF` to avoid flaky tests
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants