It patches all bar rows. However, when clients receive this event through websocket null will be returned for the bar rows. Server application was started using pm2 start src/ -i 2. Worth mentioning that feathers-client was used in an angular app that basically only performs a request to the API in order to reproduce the problem. This issue only occurs when using feathers-sync with multiple processes.
Expected behavior
When bulk patching (not tried create, update, remove etc) another service from within a service the values of the patched rows should be returned through websocket.
Steps to reproduce
Issue occurs when running node in cluster mode while using feathers-sync.
Consider the following hook in service
foo
afterget
.It patches all
bar
rows. However, when clients receive this event through websocketnull
will be returned for thebar
rows. Server application was started usingpm2 start src/ -i 2
. Worth mentioning thatfeathers-client
was used in an angular app that basically only performs a request to the API in order to reproduce the problem. This issue only occurs when using feathers-sync with multiple processes.Expected behavior
When bulk patching (not tried create, update, remove etc) another service from within a service the values of the patched rows should be returned through websocket.
Actual behavior
When bulk patching another service from within a service
null
values of the patched rows are returned through websocket. Screenshot showing the returned null values.System configuration
Running feathers-sync with redis.
Module versions (especially the part that's not working):
NodeJS version: 8.12.0
Operating System: Linux (Ubuntu 16.04)
Browser Version: Google Chrome 69.0.3497.100
React Native Version: Not applicable
Module Loader: CommonJS
Github repository: Github repository reproducing this issue