Skip to content

Conversation

@ksobolew
Copy link
Contributor

@ksobolew ksobolew commented Feb 2, 2023

Description

The in parameter recently changed type from SliceInput to DataSeekableInputStream, the latter of which does not implement toString. Error Prone complains with ObjectToString because of that.

Note that this only happens with #14933 merged, because otherwise the verify method is not a @FormatMethod and Error Prone can't verify correctness of its invocations.

Passing location instead of in as the format string arguments is correct, because the stream is derived from a file at the location named by location.

Additional context and related issues

It's kind of a shameless plug to promote #14933, which got stuck in reviews for some reason.

Release notes

(x) This is not user-visible or docs only and no release notes are required.
( ) Release notes are required, please propose a release note for me.
( ) Release notes are required, with the following suggested text:

# Section
* Fix some things. ({issue}`issuenumber`)

@cla-bot cla-bot bot added the cla-signed label Feb 2, 2023
@ksobolew ksobolew requested review from findepi and kokosing February 2, 2023 09:01
The `in` parameter recently changed type from `SliceInput` to
`DataSeekableInputStream`, the latter of which does not implement
`toString`. Error Prone complains with `ObjectToString` because of that.

Note that this only happens with trinodb#14933 merged, because otherwise the
`verify` method is not a `@FormatMethod` and Error Prone can't verify
correctness of its invocations.

Passing `location` instead of `in` as the format string arguments is
correct, because the stream is derived from a file at the location named
by `location`.
@ksobolew ksobolew force-pushed the kudi/fix-verify-call branch from 73320a1 to fa5e7bf Compare February 2, 2023 09:02
@findepi findepi merged commit 2767c5c into trinodb:master Feb 2, 2023
@github-actions github-actions bot added this to the 407 milestone Feb 2, 2023
@ksobolew ksobolew deleted the kudi/fix-verify-call branch February 3, 2023 07:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Development

Successfully merging this pull request may close these issues.

3 participants