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.

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

remove exit-future #5183

Merged
merged 3 commits into from
Feb 27, 2024
Merged

remove exit-future #5183

merged 3 commits into from
Feb 27, 2024

Conversation

jxs
Copy link
Member

@jxs jxs commented Feb 5, 2024

Issue Addressed

the last release was 4 years ago and its repo has been archived. We already have async-channel in the repo, so use it instead

@jxs jxs changed the title remove exit-future usage, remove exit-future Feb 5, 2024
@jxs jxs force-pushed the remove-exit-future branch 2 times, most recently from 1687d97 to 6e4d3d3 Compare February 6, 2024 15:38
as it is non maintained, and replace with async-channel which is already in the repo.
@jxs jxs force-pushed the remove-exit-future branch from 6e4d3d3 to b29f6e5 Compare February 6, 2024 15:50
@AgeManning
Copy link
Member

The tests need to be fixed. Seems the update has removed a field.

Copy link
Member

@AgeManning AgeManning left a comment

Choose a reason for hiding this comment

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

The tests need to be corrected for the new version

@AgeManning AgeManning added the waiting-on-author The reviewer has suggested changes and awaits thier implementation. label Feb 8, 2024
@jxs jxs force-pushed the remove-exit-future branch from 8720a6c to 4be6084 Compare February 12, 2024 11:32
@jxs jxs added ready-for-review The code is ready for review and removed waiting-on-author The reviewer has suggested changes and awaits thier implementation. labels Feb 12, 2024
@jxs jxs requested a review from AgeManning February 23, 2024 15:39
@AgeManning
Copy link
Member

@Mergifyio queue

Copy link

mergify bot commented Feb 27, 2024

queue

🛑 The pull request has been removed from the queue default

The queue conditions cannot be satisfied due to failing checks.

You can take a look at Queue: Embarked in merge queue check runs for more details.

In case of a failure due to a flaky test, you should first retrigger the CI.
Then, re-embark the pull request into the merge queue by posting the comment
@mergifyio refresh on the pull request.

mergify bot added a commit that referenced this pull request Feb 27, 2024
@jxs
Copy link
Member Author

jxs commented Feb 27, 2024

@Mergifyio queue

@sigp sigp deleted a comment from mergify bot Feb 27, 2024
Copy link

mergify bot commented Feb 27, 2024

queue

✅ The pull request has been merged automatically

The pull request has been merged automatically at 65c4ff0

@mergify mergify bot merged commit 65c4ff0 into sigp:unstable Feb 27, 2024
29 checks passed
pawanjay176 pushed a commit to pawanjay176/lighthouse that referenced this pull request Mar 5, 2024
* remove exit-future usage,

as it is non maintained, and replace with async-channel which is already in the repo.

* Merge branch 'unstable' of https://github.com/sigp/lighthouse into remove-exit-future

* Merge branch 'unstable' of https://github.com/sigp/lighthouse into remove-exit-future
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ready-for-review The code is ready for review
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants