Skip to content
New issue

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

Nodejs client server test #1223

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Conversation

pcfreak30
Copy link

PANIC test to check a node js client and server with 1 simple action.

Test not confirmed to be working as IDK how to test it. Copied and modified from load.js. I have attempted do disable radata with require('gun/lib/radix').file['radata'] = true; since there's no option for it as its not needed and causes different behavior.

@amark
Copy link
Owner

amark commented Mar 18, 2022

@pcfreak30 Thanks. I ran it, and I don't know why the 2 NodeJS instances are not syncing given that the classic AXE bug has already been addressed. Usually this works out of the box and other NodeJS<->NodeJS sync is still working in PANIC tests that init via browser API calls, so its odd this simpler example is not working, hopefully just something stupid internally in an adapter (since all core code, browser & NodeJS, is shared). Sadly however, debugging this is priority ranked under single-peer AXE relay performance (Browser<-WebRTC->Browser && Browser<->NodeJS<->Browser fallback) which we're testing against the 50M monthly users (check my twitter blogging about these updates, with the ~100K concurrent users/second). Fixing NodeJS<->NodeJS is obviously important to scaling the DHT, but each NodeJS (well, and Rust) needs to individually be maxed out first before testing larger setups.

This issue will stay open. Helpful steps forward would either be:
(A) Since you have the PANIC test setup already, debug yourself by adding console.logs into the in/out hooks to see where the messages drop, whether at the API, the transport adapters, or receiving end. This is easy in browser (just pop open network tab) but takes a tad more time (for me, at least) in NodeJS which slows me down, so if you can make progress on it and notify me that might let us figure out the quick fix sooner.
(B) Have a larger in-production user-base/use-case than the teams we're currently supporting or able to fund some other devs to help debug if you can't.
(C) Help us finish the higher priority task so this then becomes the high priority task.

Obviously (A) is the best/simplest.

@draeder
Copy link
Contributor

draeder commented Mar 18, 2022

@pcfreak30 FYI, to run npm i mocha -g --save, then mocha node-server-client.js... if I remember correctly. Haven't played with PANIC for a couple weeks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants