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

kafka4beam / kafka_protocol Public

Notifications You must be signed in to change notification settings
Fork 63
Star 95

Code
Issues 4
Pull requests 1
Actions
Projects
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Actions
Projects
Security
Insights

fix: socket write error should not result in a crash report#124

Merged

zmstone merged 2 commits intokafka4beam:masterkafka4beam/kafka_protocol:masterfrom zmstone:0827-fix-einval-crashzmstone/kafka_protocol:0827-fix-einval-crashCopy head branch name to clipboard

Aug 27, 2024

+4-1

Conversation Commits2 (2)Checks Files changed

Commits

Commits on Aug 27, 2024

fix: socket write error should not result in a crash report
zmstone
committed
docs: add changelog
zmstone
committed

Footer

© 2025 GitHub, Inc.

Footer navigation

Terms
Privacy
Security
Status
Docs
Contact

You can’t perform that action at this time.