Skip to content

Fixing all lint errors#233

Merged
sofia-tekdatum merged 9 commits into
mainfrom
fix_lint_errors
Jan 26, 2026
Merged

Fixing all lint errors#233
sofia-tekdatum merged 9 commits into
mainfrom
fix_lint_errors

Conversation

@sofia-tekdatum

@sofia-tekdatum sofia-tekdatum commented Jan 23, 2026

Copy link
Copy Markdown
Collaborator

Fix all lint errors reported in github actions. See [this run] for the original errors. (https://github.com/protegrity/arrow/actions/runs/20860646944/job/59939104419).

Clean run (with a straggling R lint error which is not ours) is here.

@github-actions

Copy link
Copy Markdown

Thanks for opening a pull request!

If this is not a minor PR. Could you open an issue for this pull request on GitHub? https://github.com/apache/arrow/issues/new/choose

Opening GitHub issues ahead of time contributes to the Openness of the Apache Arrow project.

Then could you also rename the pull request title in the following format?

GH-${GITHUB_ISSUE_ID}: [${COMPONENT}] ${SUMMARY}

or

MINOR: [${COMPONENT}] ${SUMMARY}

See also:

@argmarco-tkd argmarco-tkd left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Thank you for this! - this was massive (not a criticism!!). LGTM - it seemed mainly like a re-formatting PR, let me know if there is anything in particular that may need closer attention.

Now, future looking question: what could/should we have done before so that we didn't get to this point (where we had to put in massive effort to correct formatting)?

catch (...) {
ARROW_LOG(ERROR) << "[DBPAExecutor] UNKNOWN EXCEPTION: " << operation_name << " failed with unknown exception";
throw; // Re-throw original exception
} catch (const std::exception& e) {

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

ew. but whatever it takes to make the linter happy :D

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

This one I do actually prefer :)

{"port", "5432"},
{"database", "testdb"}
};
{"host", "localhost"}, {"port", "5432"}, {"database", "testdb"}};

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

sigh. not as legible as the original. oh, well.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

Agreed

int64_t init_timeout_ms = 10*1000; //10 seconds
int64_t encrypt_timeout_ms = 30*1000; //30 seconds
int64_t decrypt_timeout_ms = 30*1000; //30 seconds.
int64_t init_timeout_ms = 10 * 1000; // 10 seconds

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

ugg, again :)

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

There were many, many uggs when I was doing this.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

My internal linter likes this actually :)

@sofia-tekdatum

Copy link
Copy Markdown
Collaborator Author

Thank you for this! - this was massive (not a criticism!!). LGTM - it seemed mainly like a re-formatting PR, let me know if there is anything in particular that may need closer attention.

Now, future looking question: what could/should we have done before so that we didn't get to this point (where we had to put in massive effort to correct formatting)?

Thanks for the review! Going forward, every PR should make sure the linter action is clean before merging :)

@avalerio-tkd avalerio-tkd left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

LGTM+

Thanks for all the changes @sofia-tekdatum ! Nothing major on the comments, except for one. If that's the only change, it's ok to leave as-is.

{parquet::Type::DOUBLE, dbps::external::Type::DOUBLE},
{parquet::Type::BYTE_ARRAY, dbps::external::Type::BYTE_ARRAY},
{parquet::Type::FIXED_LEN_BYTE_ARRAY, dbps::external::Type::FIXED_LEN_BYTE_ARRAY},
{parquet::Type::UNDEFINED, dbps::external::Type::UNDEFINED}};

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Probably a note for the future, but this one is likely to fail when we integrate the new dbps::external::Type without UNDEFINED.
Kind of a mental note, not related to this PR

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

@avalerio-tkd - I noticed this as well. We will deal with this once we bring the latest version of DBPA interface to Arrow. Not a biggie, and definitely not a blocker for this PR.

parquet_to_external_type_map;
static const std::unordered_map<::arrow::Compression::type,
dbps::external::CompressionCodec::type>
arrow_to_external_compression_map;

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

ufff.. :( If this passes the linter, then fine.

* @param encrypt_timeout Timeout for encrypt operations in milliseconds
* (default: 30000)
* @param decrypt_timeout Timeout for decrypt operations in milliseconds
* (default: 30000)

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Nit: Align as the previous line for consistency. If this is the only change, then it's ok to leave as-is.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

I am choosing to leave this as the linter is currently happy and I'll prioritize that.

std::string app_context, std::string column_key_id, Type::type data_type,
std::optional<int> datatype_length, CompressionCodec::type compression_type,
std::optional<std::map<std::string, std::string>> column_encryption_metadata)
override {

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

My internal linter doesn't like this, but leave it as-is if this passes the Arrow linter. :(

int64_t init_timeout_ms = 10*1000; //10 seconds
int64_t encrypt_timeout_ms = 30*1000; //30 seconds
int64_t decrypt_timeout_ms = 30*1000; //30 seconds.
int64_t init_timeout_ms = 10 * 1000; // 10 seconds

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

My internal linter likes this actually :)

std::move(meta_decryptor_factory),
std::move(data_decryptor_factory)};
CryptoContext ctx{
col->has_dictionary_page(), static_cast<int16_t>(row_group_ordinal_),

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

ufff...

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

Yep.

@sofia-tekdatum sofia-tekdatum merged commit 953bcb7 into main Jan 26, 2026
45 of 115 checks passed
@sofia-tekdatum sofia-tekdatum deleted the fix_lint_errors branch January 26, 2026 16:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Git merging > Cleanup final failing Github actions

3 participants