You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The new release of lintr has a new feature - giving a warning when code is commented out - which is causing the lintr-containing CI job to fail. We could have pinned to a previous version of lintr, but that seem like a useful feature & the lines of code which trigger it seem like reasonable exceptions, so I've just added a #nolint flag on each of them.
DuckDB failure will be unrelated to these changes. Wouldn't usually merge with a pending review but given this is such a trivial change and already has one approval, I'll merge this now so that people working on other PRs can rebase and not have failing CI.
The new release of lintr has a new feature - giving a warning when code is commented out - which is causing the lintr-containing CI job to fail. We could have pinned to a previous version of lintr, but that seem like a useful feature & the lines of code which trigger it seem like reasonable exceptions, so I've just added a #nolint flag on each of them.
Authored-by: Nic Crane <[email protected]>
Signed-off-by: Nic Crane <[email protected]>
fatemehp
pushed a commit
to fatemehp/arrow
that referenced
this pull request
Oct 17, 2022
The new release of lintr has a new feature - giving a warning when code is commented out - which is causing the lintr-containing CI job to fail. We could have pinned to a previous version of lintr, but that seem like a useful feature & the lines of code which trigger it seem like reasonable exceptions, so I've just added a #nolint flag on each of them.
Authored-by: Nic Crane <[email protected]>
Signed-off-by: Nic Crane <[email protected]>
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The new release of lintr has a new feature - giving a warning when code is commented out - which is causing the lintr-containing CI job to fail. We could have pinned to a previous version of lintr, but that seem like a useful feature & the lines of code which trigger it seem like reasonable exceptions, so I've just added a #nolint flag on each of them.