Skip to content

Navigation Menu

Explore
By company size
By use case
By industry
View all solutions
Topics
- AI
- DevOps
- Security
- Software Development
- View all
Explore
- GitHub Sponsors
  Fund open source developers
- The ReadME Project
  GitHub community articles
Repositories
- Enterprise platform
  AI-powered developer platform
Available add-ons
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.

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

connectrpc / connect-es Public

Notifications You must be signed in to change notification settings
Fork 87
Star 1.5k

Code
Issues 30
Pull requests 11
Discussions
Actions
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Discussions
Actions
Security
Insights

V2: Ensure that a signal exists for a completed RPC#1282

Merged

timostamm merged 4 commits intov2connectrpc/connect-es:v2from tstamm/v2/revert-1234connectrpc/connect-es:tstamm/v2/revert-1234Copy head branch name to clipboard

Oct 18, 2024

Conversation Commits4 (4)Checks Files changed

Commits

Commits on Oct 18, 2024

Revert "V2: Don't trigger handler signal on success (#1234 )"
timostamm
committed
Keep propagating errors.
timostamm
committed
Update JSDoc for clarity.
timostamm
committed
Keep propagating errors.
timostamm
committed

Footer

© 2025 GitHub, Inc.

Footer navigation

Terms
Privacy
Security
Status
Docs
Contact

You can’t perform that action at this time.