fix(socket-handler): Fix socket handler race condition by differentiating between async and sync handlers. Now, async socket handlers complete their setup before initial data is emitted, ensuring that no data is lost. Documentation and tests have been updated to reflect this change.
This commit is contained in:
@ -1,5 +1,12 @@
|
||||
# Changelog
|
||||
|
||||
## 2025-05-29 - 19.5.1 - fix(socket-handler)
|
||||
Fix socket handler race condition by differentiating between async and sync handlers. Now, async socket handlers complete their setup before initial data is emitted, ensuring that no data is lost. Documentation and tests have been updated to reflect this change.
|
||||
|
||||
- Added detailed explanation in readme.hints.md about the race condition issue, root cause, and solution implementation.
|
||||
- Provided a code snippet that checks if the socket handler returns a Promise and waits for its resolution before emitting initial data.
|
||||
- Updated tests (test.socket-handler-race.ts, test.socket-handler.simple.ts, test.socket-handler.ts) to verify correct behavior of async handlers.
|
||||
|
||||
## 2025-05-28 - 19.5.0 - feat(socket-handler)
|
||||
Add socket-handler support for custom socket handling in SmartProxy
|
||||
|
||||
|
Reference in New Issue
Block a user