-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
feat: support wrapped plugin ops #5721
Conversation
ebe7d23
to
8315f2b
Compare
@piscisaureus Any idea why this only fails on windows? |
d5b8f02
to
e0604ad
Compare
Thanks @afinch7 could you please rebase this branch and add some test case? |
Going to rebase this and add a test case with json ops. |
e0604ad
to
753dcb1
Compare
I decided the json op test was too complicated, so I just did something simpler. |
e694c07
to
45fe95e
Compare
I think I finally figured out what causes that segfault on windows. The default drop implementation for the closure created in I think the "correct" solution here is to make sure that all of a plugins ops are unregistered first when it is dropped. |
5d2075e
to
34c20d1
Compare
@bartlomieju This is ready for review. |
@afinch7 thanks, I'll leave review to @piscisaureus as he's refactoring the ops now. |
The issue I have with this is that I see that you're wrapping ops but I have no idea why this is needed at all.. |
34c20d1
to
8cc590f
Compare
It's not needed, but it's not currently possible to implement anything like |
With the recent changes to the op registry I found it was actually fairly easy to implement my "correct" solution of actually unregistering a plugins ops when it is closed. |
This is quite stale now. We should either rebase or close. |
I'm gonna close this PR without a merge because it's stale. In light of #8490 it's not clear if we want to make those changes, remove plugins completely or rework them. |
Add support for op wrapping pattern used in cli:
fixes #5478