We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using https://github.com/garth/socket-editor start two peers
pnpm install -r cd peer pnpm start:ios
in a second terminal
cd peer pnpm dev
click "Edit" in both clients and see that they are in sync.
close the macOS peer and start it again
pnpm dev
Notice that messages are now only sent in one direction, the iOS peer no longer receives any messages from the macOS peer.
Extensive console logs have been added to give a clear picture of peer interactions
If both peers are restarted then messages are again received by both peers.
uname -a
Darwin Garths-MacBook-Pro.local 23.2.0 Darwin Kernel Version 23.2.0: Wed Nov 15 21:53:18 PST 2023; root:xnu-10002.61.3~2/RELEASE_ARM64_T6000 arm64
0.5.4 (97fa3f7c) Installation path: /Users/garth/Projects/socket-editor/node_modules/.pnpm/@[email protected]/node_modules/@socketsupply/socket-darwin-arm64/
I also tried this on the latest master branch but the results are the same.
0.5.4 (ef7fb555) Installation path: /Users/garth/.local/share/socket/
node --version v20.11.0
The clients should be able to send messages in both directions after a peer is restarted.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Using https://github.com/garth/socket-editor start two peers
in a second terminal
click "Edit" in both clients and see that they are in sync.
close the macOS peer and start it again
Notice that messages are now only sent in one direction, the iOS peer no longer receives any messages from the macOS peer.
Extensive console logs have been added to give a clear picture of peer interactions
If both peers are restarted then messages are again received by both peers.
What OS are you using (
uname -a
, or Windows version)?What version Socket Runtime are you using?
I also tried this on the latest master branch but the results are the same.
What programming language are you using (C/C++/Go/Rust)?
What did you expect to see and what you saw instead?
The clients should be able to send messages in both directions after a peer is restarted.
The text was updated successfully, but these errors were encountered: