Skip to content

chore: introduce nightly feature flag to provide error backtrace #1340

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

BugenZhao
Copy link

What changes are included in this PR?

In nightly toolchain, there's an unstable feature error_generic_member_access which allows accessing the error to extract additional information. A common convention is to provide error backtrace here.

This PR introduces a new non-default feature named nightly to iceberg crate. When it's enabled, we will provide the backtrace if it's captured in iceberg::Error.

Are these changes tested?

Copy link
Contributor

@liurenjie1024 liurenjie1024 left a comment

Choose a reason for hiding this comment

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

Hi, @BugenZhao IIRC, this will require unstable rust toolchain? If so, I don't think we should introduce this.

@Xuanwo
Copy link
Member

Xuanwo commented May 16, 2025

Is it a good idea to expose fn backtrace() -> &Backtrace for you? Relying on nightly toolchain (even hide under a feature) can be a pain for us.

liurenjie1024 pushed a commit that referenced this pull request May 19, 2025
Signed-off-by: xxchan <[email protected]>

## Which issue does this PR close?

#1340

## What changes are included in this PR?


## Are these changes tested?

---------

Signed-off-by: xxchan <[email protected]>
xxchan added a commit to xxchan/iceberg-rust that referenced this pull request May 19, 2025
Signed-off-by: xxchan <[email protected]>

## Which issue does this PR close?

apache#1340

## What changes are included in this PR?


## Are these changes tested?

---------

Signed-off-by: xxchan <[email protected]>
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.

3 participants