feat: Add isolated_object package#121
Conversation
|
Warning Review limit reached
More reviews will be available in 1 hour. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (15)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
nielsenko
force-pushed
the
feat-isolated-object
branch
4 times, most recently
from
c723aff to
75b828a
Compare
Extract the IsolatedObject concurrency primitive - previously duplicated, and drifted, between serverpod_shared and relic's relic_core - into a standalone, dependency-free package. Reconciled from serverpod's superset implementation (keepIsolateAlive, an isClosed guard, and a teardown that fails in-flight calls rather than letting them hang), with relic's test suite ported over plus new tests covering the superset behavior.
nielsenko
force-pushed
the
feat-isolated-object
branch
from
75b828a to
446682d
Compare
|
Rebased on main |
3 participants
New dependency-free
isolated_objectpackage extracts theIsolatedObjectconcurrency primitive (previously duplicated and drifted betweenserverpodandrelic) into one shared home, with a merged test suite.