Skip to content

Conversation

@manishkr
Copy link
Contributor

@manishkr manishkr commented Dec 23, 2025

Which issue does this PR close?

Rationale for this change

To consider offset in slicing of RunArray.

What changes are included in this PR?

  1. Considered offset in slicing of RunArray.
  2. Enhanced RunArray slice API.

Are these changes tested?

yes

Are there any user-facing changes?

Yes, extended API to access RunArray slices directly than getting it from index.

@github-actions github-actions bot added the arrow Changes to the arrow crate label Dec 23, 2025
@manishkr
Copy link
Contributor Author

manishkr commented Dec 23, 2025

Looking into test(intermittent) case failure.

@manishkr manishkr force-pushed the 9018-fix-runarray-kernel branch from b17d380 to d9e54fb Compare December 24, 2025 12:31
@manishkr
Copy link
Contributor Author

Need help on.
Archery test With other arrows
The hosted runner lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.

@Jefffrey
Copy link
Contributor

Need help on. Archery test With other arrows The hosted runner lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.

Can ignore, it's an unrelated issue: #9024

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

arrow Changes to the arrow crate

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Kernels don't account for slicing of RunArrays

2 participants