1. Forum
  2. FidoNet
  3. SYNC SYSOPS

  • users unable to exit node to node chat

    From Rob Swindell@1:103/705 to GitLab note in main/sbbs on Mon Oct 24 22:48:06 2022
    https://gitlab.synchro.net/main/sbbs/-/issues/451#note_2803

    Could not reproduce on Vertrauen, both nodes running on same Linux system.[sbbs_exiting_chat](/uploads/e5397a861d13d8083725574bf4012021/sbbs_exiting_chat.png)
    --- SBBSecho 3.15-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Rob Swindell@1:103/705 to GitLab note in main/sbbs on Tue Oct 25 15:40:50 2022
    https://gitlab.synchro.net/main/sbbs/-/issues/451#note_2804

    The output of 'node -debug' when this problems happens could be useful (and note: which node was the node that successfully exited chat).
    --- SBBSecho 3.15-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Keyop Troy@1:103/705 to GitLab note in main/sbbs on Wed Oct 26 17:09:14 2022
    https://gitlab.synchro.net/main/sbbs/-/issues/451#note_2805

    Just replicated the issue as described in nelgin's description above and get the same problem.
    --- SBBSecho 3.15-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Rob Swindell@1:103/705 to GitLab note in main/sbbs on Wed Oct 26 17:15:26 2022
    https://gitlab.synchro.net/main/sbbs/-/issues/451#note_2806

    Do you have the output of 'node -debug' when this happens to help root-cause the issue?
    --- SBBSecho 3.15-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Nigel Reed@1:103/705 to GitLab note in main/sbbs on Wed Oct 26 17:30:10 2022
    https://gitlab.synchro.net/main/sbbs/-/issues/451#note_2807

    This is the output from node 1 and 2 before chat, during chat, after node 1 pressed CTRL-C, and after node 1 did ;SPY 2Let me know if there's anything else you need. [node-debug.txt](/uploads/a2018dd0ff8b4118ac281aac1086a886/node-debug.txt)
    --- SBBSecho 3.15-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Nigel Reed@1:103/705 to GitLab note in main/sbbs on Wed Oct 26 17:35:18 2022
    https://gitlab.synchro.net/main/sbbs/-/issues/451#note_2808

    This is another issue but since you're poking around, when we reestablished chat, on my end (node 1) I didn't get multinode I just got line by line. I can recreate later and open a new issue.
    --- SBBSecho 3.15-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Rob Swindell@1:103/705 to GitLab note in main/sbbs on Wed Oct 26 18:07:32 2022
    https://gitlab.synchro.net/main/sbbs/-/issues/451#note_2809

    Keyop, you replicated this on your own BBS or on Nelgin's?
    --- SBBSecho 3.15-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Keyop Troy@1:103/705 to GitLab note in main/sbbs on Wed Oct 26 18:11:46 2022
    https://gitlab.synchro.net/main/sbbs/-/issues/451#note_2810

    Nelgin's
    --- SBBSecho 3.15-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Rob Swindell@1:103/705 to GitLab note in main/sbbs on Wed Oct 26 18:13:36 2022
    https://gitlab.synchro.net/main/sbbs/-/issues/451#note_2811

    When a node is brought into chat by the sysop, they can't exit until the sysop exits chat. See how the node action is stuck in "22" (NODE_PCHT) after node 1 exited chat? That's why the second (user) node doesn't know the first node has exited chat, because the node 1's "action" value doesn't reflect that.How are you invoking the private node-to-node chat - using the stock Ctrl-P loadable module or some other method?If you're invoking the private chat via some custom menu and your custom menu isn't setting the node action value, then that would explain the problem and why no other sysops are experiencing this issue.
    --- SBBSecho 3.15-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Rob Swindell@1:103/705 to GitLab note in main/sbbs on Wed Oct 26 18:14:38 2022
    https://gitlab.synchro.net/main/sbbs/-/issues/451#note_2812

    Split-screen chat has very specific terminal requirements. Perhaps you were connecting using a non-conforming terminal (e.g. in dimensions)?
    --- SBBSecho 3.15-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Nigel Reed@1:103/705 to GitLab note in main/sbbs on Wed Oct 26 22:45:10 2022
    https://gitlab.synchro.net/main/sbbs/-/issues/451#note_2813

    I would hope that syncterm is a conforming terminal. Since it worked in the same session and the dimensions haven't changed. I assume that Keyop was using the same also. Would need him to confirm
    --- SBBSecho 3.15-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Keyop Troy@1:103/705 to GitLab note in main/sbbs on Thu Oct 27 05:40:24 2022
    https://gitlab.synchro.net/main/sbbs/-/issues/451#note_2814

    I was using telnet from my BBS.
    --- SBBSecho 3.15-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Rob Swindell@1:103/705 to GitLab note in main/sbbs on Thu Oct 27 09:40:18 2022
    https://gitlab.synchro.net/main/sbbs/-/issues/451#note_2815

    There's also a user setting to enable/disable split-screen chat. Both sides of the chat/conversation do not have to be split.
    --- SBBSecho 3.15-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Nigel Reed@1:103/705 to GitLab note in main/sbbs on Thu Oct 27 09:47:24 2022
    https://gitlab.synchro.net/main/sbbs/-/issues/451#note_2816

    I've tested both sides wit SyncTerm, using different users, with repeatable results, that the caller cannot quit chat when sysop initiates chat. Nothing has changed in the user profiles.
    --- SBBSecho 3.15-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Nigel Reed@1:103/705 to GitLab note in main/sbbs on Thu Oct 27 10:03:38 2022
    https://gitlab.synchro.net/main/sbbs/-/issues/451#note_2818

    I'm just using the section that's in chat_sec.js case 'P': bbs.private_chat(); break;Except I'm using N for node to node chat. case 'N': bbs.private_chat(); break;
    --- SBBSecho 3.15-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Nigel Reed@1:103/705 to GitLab issue in main/sbbs on Thu Oct 27 10:03:38 2022
    close https://gitlab.synchro.net/main/sbbs/-/issues/451
    --- SBBSecho 3.15-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Nigel Reed@1:103/705 to GitLab note in main/sbbs on Thu Oct 27 10:04:30 2022
    https://gitlab.synchro.net/main/sbbs/-/issues/451#note_2819

    The script was missing bbs.nodesync() after setting node_action. Thanks to DM for helping me figure that one out.
    --- SBBSecho 3.15-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)