Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Feature Gate: stop_sibling_instruction_search_at_parent #27289

Closed
Lichtso opened this issue Aug 22, 2022 · 0 comments
Closed

Feature Gate: stop_sibling_instruction_search_at_parent #27289

Lichtso opened this issue Aug 22, 2022 · 0 comments
Assignees
@Lichtso
Labels
feature-gate Pull Request adds or modifies a runtime feature gate

Comments

@Lichtso
Copy link
Contributor

Lichtso commented Aug 22, 2022 •
edited
Loading

Description

Currently the get_processed_sibling_instruction() syscall only stops its search at top level instructions. This is a bit inconsistent and it should be interrupted whenever the current level hits a gap.

Feature ID

EYVpEP7uzH1CoXzbD6PubGhYmnxRXPeq3PPsm1ba3gpo

Activation Method

Single Core Contributor

Minimum Beta Version

1.16.0

Minimum Stable Version

No response

Testnet Activation Epoch

506

Devnet Activation Epoch

569

Mainnet-Beta Activation Epoch

547
@Lichtso Lichtso added the feature-gate Pull Request adds or modifies a runtime feature gate label Aug 22, 2022
@Lichtso Lichtso self-assigned this Aug 22, 2022
@Lichtso Lichtso mentioned this issue Aug 22, 2022
Merged
@Lichtso Lichtso changed the title Feature Gate: stop_sibling_instruction_search_at_rising_edge Feature Gate: stop_sibling_instruction_search_at_parent Aug 22, 2022
@Lichtso Lichtso mentioned this issue Jan 18, 2024
Merged
@Lichtso Lichtso closed this as completed Jan 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Lichtso Lichtso

Labels
feature-gate Pull Request adds or modifies a runtime feature gate
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Lichtso