-
Notifications
You must be signed in to change notification settings - Fork 1.5k
synclink integration #1258
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
synclink integration #1258
Conversation
I think before we get any more working we need to:
This is what we need to keep the Python plugin API both sane and moderately similar to what already exists. Another option would be to break all the existing plugins and work on fixing them in a subsequent PR. Maybe this needs to go into a long-lived workers branch. |
@antocuni we should probably have a meeting on worker migration... |
I think the last commit broke some tests in |
f61e798
to
668db62
Compare
I'm sorry it's apparently called import type { Remote as SynclinkProxy } from "synclink"; |
This requires converting to an I have changed it to |
This is surely because of a wrong type somewhere else. You shouldn't be saying
This will mean merging this PR with a fair number of wrong types: things that are typed as |
Like I said, I changed it to |
The issue is that |
Very weird that c68f550 broke a test... it shouldn't change runtime behavior. |
This is likely a flaky |
Thanks for letting me know @madhur-tandon! I fixed the rest of the types locally. I'll push the fixes when github is back up. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason wi 6D40 ll be displayed to describe this comment to others. Learn more.
wooo, I think we are very close to merge it!
I hope that the build will be green now
Originally 81 errors / failed tests --> Now down to 32 errors / failed tests.
This is a step for moving towards WebWorkers eventually.
CC: @hoodmane @antocuni