Skip to content

Navigation Menu

Appearance settings

View all features
- BY COMPANY SIZE
  Enterprises
  Small and medium teams
  Startups
  Nonprofits
- BY USE CASE
  App Modernization
  DevSecOps
  DevOps
  CI/CD
  View all use cases
- BY INDUSTRY
  Healthcare
  Financial services
  Manufacturing
  Government
  View all industries
View all solutions
- EXPLORE BY TOPIC
  AI
  Software Development
  DevOps
  Security
  View all topics
- EXPLORE BY TYPE
  Customer stories
  Events & webinars
  Ebooks & reports
  Business insights
  GitHub Skills
- SUPPORT & SERVICES
  Documentation
  Customer support
  Community forum
  Trust center
  Partners
View all resources
- COMMUNITY
  GitHub SponsorsFund open source developers
- PROGRAMS
  Security Lab
  Maintainer Community
  Accelerator
  GitHub Stars
  Archive Program
- REPOSITORIES
  Topics
  Trending
  Collections
- ENTERPRISE SOLUTIONS
  Enterprise platformAI-powered developer platform
- AVAILABLE ADD-ONS
  GitHub Advanced SecurityEnterprise-grade security features
  Copilot for BusinessEnterprise-grade AI features
  Premium SupportEnterprise-grade 24/7 support
Pricing

Search code, repositories, users, issues, pull requests...

Search

Clear

Search syntax tips

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Saved searches

Use saved searches to filter your results more quickly

Name

Query

To see all available qualifiers, see our documentation.

Appearance settings

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

Dismiss alert

replit / river-python Public

Notifications You must be signed in to change notification settings
Fork 2
Star 4

Code
Issues
Pull requests 5
Actions
Projects
Security and quality
Insights

Additional navigation options

Code
Issues
Pull requests
Actions
Projects
Security and quality
Insights

feat/river schema v2 compatibility#106

Merged

blast-hardcheese merged 193 commits into

mainreplit/river-python:mainfrom

dstewart/feat/river-v2-codegenreplit/river-python:dstewart/feat/river-v2-codegenCopy head branch name to clipboard

Apr 8, 2025

Conversation Commits193 (193)Checks Files changed

Merged

feat/river schema v2 compatibility#106
blast-hardcheese merged 193 commits into
mainfrom
dstewart/feat/river-v2-codegen

Commits

Commits on Apr 8, 2025

Permit emitting pydantic inputs in snapshot tests
blast-hardcheese
committed
Converting TypedDict<->pydantic parity tests over to snapshot testing
blast-hardcheese
committed
Address error message
blast-hardcheese
committed
Making input and init types optional, gating on protocol version
blast-hardcheese
committed
Moving library call render method out to reduce local scope
blast-hardcheese
committed
v2 client
blast-hardcheese
committed
Adding and threading through protocol_version
blast-hardcheese
committed
Conditionally emit v2 Clients
blast-hardcheese
committed
Expose protocol-version to CLI
blast-hardcheese
committed
Pivoting rendered parameters based on protocol_version
blast-hardcheese
committed
Relax the RiverProcedure field requirements so we can parse v2
blast-hardcheese
committed
Missing render
blast-hardcheese
committed
Moving type ascriptions down to the method level
blast-hardcheese
committed
Just avoid calling add_msg_to_stream if it should not be called
blast-hardcheese
committed
Adding missing STREAM_CLOSED_BIT
blast-hardcheese
committed
v2 closed bit
blast-hardcheese
committed
v2 cancel bit
blast-hardcheese
committed
Reflowing v2 send_stream to have modern semantics
blast-hardcheese
committed
v2 send_stream codegen
blast-hardcheese
committed
Reflowing v2 send_upload to have modern semantics
blast-hardcheese
committed
v2 send_upload codegen
blast-hardcheese
committed
Distribute PROTOCOL_VERSION constant
blast-hardcheese
committed
Describing the control packet structures
blast-hardcheese
committed
Translating a little more of PROTOCOL into code
blast-hardcheese
committed
These are all self calls
blast-hardcheese
committed
Typing all self parameters
blast-hardcheese
committed
WIP
blast-hardcheese
committed
:thinking: Avoid sending more messages when we know we are closed
blast-hardcheese
committed
Skipping heartbeats when we know we're closed
blast-hardcheese
committed
One more I think
blast-hardcheese
committed
Unsure, was ws unset by this point?
blast-hardcheese
committed
Missing parameter in v1 client
blast-hardcheese
committed
Upgrade to the new websocket impl
blast-hardcheese
committed
Removing transport_options parameter
blast-hardcheese
committed
Formatting
blast-hardcheese
committed
Switch to raw bytes recv() call to avoid round-tripping through str
blast-hardcheese
committed
wat
blast-hardcheese
committed
Bite the bullet and merge client_session and session together
blast-hardcheese
committed
This is what Semaphores are for
blast-hardcheese
committed
Inline ws creation
blast-hardcheese
committed
Goodbye session_lock
blast-hardcheese
committed
Moving throw over into rate_limiter
blast-hardcheese
committed
More lifecycle management
blast-hardcheese
committed
Just use _state instead of having two
blast-hardcheese
committed
Patch circular import
blast-hardcheese
committed
Block ensure_connected until connected
blast-hardcheese
committed
Do our best to avoid contention on ensure_connected
blast-hardcheese
committed
Fix bugs
blast-hardcheese
committed
Stripping WIP logging
blast-hardcheese
committed
Adding a missing debug log
blast-hardcheese
committed
More logging around message receipt
blast-hardcheese
committed
Prevent _handle_messages_from_ws from terminating early
blast-hardcheese
committed
Break out _serve from Session
blast-hardcheese
committed
Merging _handle_messages_from_ws
blast-hardcheese
committed
Flattening try:while:try:
blast-hardcheese
committed
Colocating functions from common_session
blast-hardcheese
committed
Flip while:try: to try:while:
blast-hardcheese
committed
Compartmentalize initializers
blast-hardcheese
committed
Boom
blast-hardcheese
committed
Deprecated
blast-hardcheese
committed
try:try:
blast-hardcheese
committed
Fix state transition logic
blast-hardcheese
committed
REVERTME
blast-hardcheese
committed
Missing state transition
blast-hardcheese
committed
We have a new enumeration state for this!
blast-hardcheese
committed
Gotcha
blast-hardcheese
committed
Readability reordering
blast-hardcheese
committed
c-style strings work with format strings as well
blast-hardcheese
committed
Wake up tasks pending connected state so they can exit cleanly
blast-hardcheese
committed
Migrating all background tasks to just use block_until_connected
blast-hardcheese
committed
Redundant
blast-hardcheese
committed
Allow _check_to_close_session to exit normally if we are done
blast-hardcheese
committed
Abort if the session is rejected by the server
blast-hardcheese
committed
Expand CONNECTING to the various ConnectingStates
blast-hardcheese
committed
More lifecycle tweaks during shutdown so we exit cleanly.
blast-hardcheese
committed
More logging
blast-hardcheese
committed
try:try:
blast-hardcheese
committed
more state logging
blast-hardcheese
committed
Switch from active heartbeat to passive heartbeat
blast-hardcheese
committed
Whoops
blast-hardcheese
committed
Avoid circular awaits
blast-hardcheese
committed
Permit method filtering based on supplied file
blast-hardcheese
committed
Updating snapshots
blast-hardcheese
committed
nit
blast-hardcheese
committed
Type error instead of runtime error
blast-hardcheese
committed
Avoid explosions when given incorrect input
blast-hardcheese
committed
Document
blast-hardcheese
committed
Inline add_msg_to_stream
blast-hardcheese
committed
4da3dbb192b7476fae8e930c0544ecfb1d523d72
blast-hardcheese
committed
These are part of the codegen serdes that point at the v1 client, they are unchanged
blast-hardcheese
committed
Unused
blast-hardcheese
committed
_ws_unwrapped -> _ws, we never wrap it
blast-hardcheese
committed
Dead code
blast-hardcheese
committed
We have nanoid types
blast-hardcheese
committed
Avoid double close
blast-hardcheese
committed
Debugging code
blast-hardcheese
committed
Avoid using logging directly
blast-hardcheese
committed
No sense threading this all the way through
blast-hardcheese
committed
Break out _do_ensure_connected
blast-hardcheese
committed
send_message -> _send_message
blast-hardcheese
committed
noqa
blast-hardcheese
committed
Just use asyncio.Event to represent "connected"
blast-hardcheese
committed
Terminate _serve early if we are terminal
blast-hardcheese
committed
Switch from "queue_full Lock to space_available Event
blast-hardcheese
committed
Switch message_enqueued semaphore to Event to avoid out-of-sync bugs
blast-hardcheese
committed
Better background task management
blast-hardcheese
committed
v2 ack payload type
blast-hardcheese
committed
Tweaking debug logs
blast-hardcheese
committed
Avoid exceptions for flow control
blast-hardcheese
committed
Renaming PENDING to NO_CONNECTION to match TS
blast-hardcheese
committed
Update dead code to be the place where this method lives
blast-hardcheese
committed
None of these were async either
blast-hardcheese
committed
v2 avoid message ordering issues
blast-hardcheese
committed
Permit sensible message_buffer state transitions
blast-hardcheese
committed
Clarify SessionClosedRiverServiceException
blast-hardcheese
committed
Private method
blast-hardcheese
committed
Add span to send_close_stream
blast-hardcheese
committed
Break out send_cancel_stream
blast-hardcheese
committed
Increment seq immediately
blast-hardcheese
committed
Useless comments
blast-hardcheese
committed
Cancel streams on exception
blast-hardcheese
committed
Alter send_message to be generic over return value
blast-hardcheese
committed
Introduce backpressure for emitters
blast-hardcheese
committed
Making space for v2 tests
blast-hardcheese
committed
Cleaning up budget exhausted errors in do_ensure_connected
blast-hardcheese
committed
Transitioning back to NO_CONNECTION needs to start blocking connection waiters
blast-hardcheese
committed
Adding more debug messages
blast-hardcheese
committed
Clarifying "output" channel type
blast-hardcheese
committed
Avoid sending service/procedure names on CLOSE
blast-hardcheese
committed
event -> backpressure_waiter name clarification
blast-hardcheese
committed
Wake up backpressured writers on commit()
blast-hardcheese
committed
Tighter controls around lifecycle management
blast-hardcheese
committed
Wait for graceful shutdown
blast-hardcheese
committed
Add v2 stream tests
blast-hardcheese
committed
Codegen should provide useful errors
blast-hardcheese
committed
Ensure that the whole test state has been consumed
blast-hardcheese
committed
Add v2 rpc tests
blast-hardcheese
committed
Add capacity for self-closing messages
blast-hardcheese
committed
Unique names for tests
blast-hardcheese
committed
Avoid waking up streams that are not waiting
blast-hardcheese
committed
We still need to be awake to catch heartbeat timeouts even if we know we are disconnected
blast-hardcheese
committed
Ripping out all the heartbeat stuff in favor of server-directed signaling
blast-hardcheese
committed
Transition connecting
blast-hardcheese
committed
Make ensure_connected callable based on our own internal state
blast-hardcheese
committed
Exploratory, just transition_no_connection from close checker
blast-hardcheese
committed
Renaming _serve to _recv_from_ws
blast-hardcheese
committed
# type: ignore is no longer necessary
blast-hardcheese
committed
Establish symmetry between ConnectingStates and TerminalStates for ActiveStates
blast-hardcheese
committed
Shoring up state transitions
blast-hardcheese
committed
Avoid renaming parameters
blast-hardcheese
committed
Avoid redundant exceptions
blast-hardcheese
committed
check_to_close_connection is irrelevant
blast-hardcheese
committed
Add missing "else" for clarity
blast-hardcheese
committed
Pushing error metadata into the exception
blast-hardcheese
committed
Clarify finalize_attempt()
blast-hardcheese
committed
Only one exception can be raised from putting on an aiochannel
blast-hardcheese
committed
naming
blast-hardcheese
committed
Unused extra_control_flags
blast-hardcheese
committed
Clarify _with_stream semantics
blast-hardcheese
committed
Taking a stand on request nullability in river v2
blast-hardcheese
committed
Pretty sure this is handled now
blast-hardcheese
committed
stream -> output for consistency
blast-hardcheese
committed
Clarify enqueue vs send semantics
blast-hardcheese
committed
Avoid breaking in buffered_message_sender
blast-hardcheese
committed
Permit errors from buffered_message_sender to bubble back to the calling thread
blast-hardcheese
committed
clarify client/transport/session_id parameters
blast-hardcheese
committed
Send CANCEL correctly
blast-hardcheese
committed
Dunno
blast-hardcheese
committed
Forgot the last part, which is reconnect immediately instead of waiting.
blast-hardcheese
committed
Whoops.
blast-hardcheese
committed
Missing wait_for_connected.clear()
blast-hardcheese
committed
Turns out the new hotness is not available in 12.0
blast-hardcheese
committed
Deleting dead code
blast-hardcheese
committed
Delete dead parameters
blast-hardcheese
committed
Didn't actually use watchdog
blast-hardcheese
committed
Dangling unnecessary #ignore
blast-hardcheese
committed
session_id -> stream_id, as well as close error_channel
blast-hardcheese
committed
Adding Span to _streams
blast-hardcheese
committed
Push exception emission up into close_session directly
blast-hardcheese
committed
Communicate handshake errors back to callers as well
blast-hardcheese
committed
Just describe StreamMeta instead of ever-embiggening tuples
blast-hardcheese
committed
Decouple error channel from backpressure channel
blast-hardcheese
committed
PR feedback
blast-hardcheese
committed
Fix a bug where we were over-emitting encoder_ members for pydantic
blast-hardcheese
committed
Line length lint
blast-hardcheese
committed
Typing the output channel slightly
blast-hardcheese
committed
Use handshake_timeout_ms
blast-hardcheese
committed
Removing overly-broad "except"
blast-hardcheese
committed
PR feedback
blast-hardcheese
committed
Avoid deadlocking client if streams don't clean up after themselves
blast-hardcheese
committed
Missed that sessions should send close at the end of input
blast-hardcheese
committed
Missing "continue"s
blast-hardcheese
committed
Trying to debug hanging messages during disconnect
blast-hardcheese
committed

Footer

© 2026 GitHub, Inc.

Footer navigation

Terms
Privacy
Security
Status
Community
Docs
Contact

You can’t perform that action at this time.