Files

Michel Weststrate 80d3659e3f Don't kill WS connection if individual message handling fails

Summary:
GraphQL plugin sends garbage JSON at the moment (see T129428800). Still figuring out if that is caused by the plugin on client side, or that the Flipper SDK should escape that properly.

In the mean time, closing the Flipper connection on not being able to handle an individual message seems a cause of unnecessary connection ping-pong and instability. Changing the strategy to instead merely log and drop the message.

Changelog: Stop applications from disconnecting if a single plugin message cannot be processed.

Reviewed By: LukeDefeo

Differential Revision: D38825940

fbshipit-source-id: 4d45c8eea457375ec677238ad09b5e02bc2eb5bf

2022-08-18 06:58:59 -07:00

src

Don't kill WS connection if individual message handling fails

2022-08-18 06:58:59 -07:00

package.json

isPluginCompatible for flipper-server-core

2022-07-11 07:04:55 -07:00

README.md

Remove RSocket documentation references

2022-02-21 06:22:44 -08:00

tsconfig.json

flipper-server refactor

2022-06-07 02:42:16 -07:00

README.md

flipper-server-core

Package that manages connections with flipper clients, queries for adb/idb clients, accepts incoming websocket connections and takes care of certificate exchange.

Used by Flipper desktop, flipper-server and flipper-dump