-
Notifications
You must be signed in to change notification settings - Fork 331
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
Initial implementation of DO-attached containers API #3354
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The generated output of |
jasnell
reviewed
Jan 17, 2025
jasnell
reviewed
Jan 17, 2025
jasnell
reviewed
Jan 17, 2025
jasnell
reviewed
Jan 17, 2025
jasnell
reviewed
Jan 17, 2025
jasnell
reviewed
Jan 17, 2025
jasnell
reviewed
Jan 17, 2025
jasnell
reviewed
Jan 17, 2025
jasnell
reviewed
Jan 17, 2025
kentonv
force-pushed
the
kenton/containers
branch
from
January 22, 2025 17:09
3eca402
to
86db375
Compare
shrima-cf
approved these changes
Jan 24, 2025
No methods are implemented yet, but if a container capability is passed in when creating an actor, then `ctx.container` will be populated.
kentonv
force-pushed
the
kenton/containers
branch
from
January 24, 2025 18:48
86db375
to
738fd4d
Compare
jasnell
reviewed
Jan 24, 2025
jasnell
reviewed
Jan 24, 2025
Couple of nits remaining but otherwise LGTM |
Tests are currently in the internal codebase, since that's where the mock container service lives, but probably some of that should be ported out here later, especially once we figure out how local testing of containers will work.
This is really two changes: 1. Make these lazy properties. This is a strict win since the properties cannot change value during the lifetime of the object, so there's no reason to call into C++ on every access. This might even be a non-negligible performance gain for people who use `ctx.storage` a lot without memoizing it. 2. Make them writable. There's no real reason to prevent people from overwriting these if they really want to. Moreover, introducing `container` as a read-only property could arguably break someone who is, for whatever reason, monkey-patching this property in today.
kentonv
force-pushed
the
kenton/containers
branch
from
January 24, 2025 20:09
738fd4d
to
f978634
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Implemented here:
Not implemented yet:
listenTcp()
).