-
Notifications
You must be signed in to change notification settings - Fork 8
Update #51
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
Update #51
Conversation
Great job! It looks like there's a couple unresolved conflicts though |
@realrasengan I would say delete/reject this PR as it is over a year old. I have 2 JBNC projects:
Well, but I like it works well. There is one thing that I don't understand about the last PR: #56 I should remove the |
Ah - I see! Makes sense and thank you for pushing those PR's up! In terms of the bug, I will take a look as well! Thank you again! |
@realrasengan yesterday to test logs I replaced this:
by
and also here:
instead I put this ( https://github.com/freenode/jbnc/blob/master/bouncer.js#L1183 ):
Log IRC: The problem does not come from the The problem could be related to one of the following lines but not sure:
|
Here is a log from yesterday:
it does it all the time afterwards even when restarting the web client. To stop this from happening, you have to disconnect jbnc and reconnect to it It may be related to the away and its timer or I don't know |
Currently I am testing this for 24 hours: At line 1194 https://github.com/freenode/jbnc/blob/master/bouncer.js#L1194 I added this:
I was able to retrieve the json log with There is no channel name
To see for tomorrow |
Since yesterday there is no longer any problem with "undefined joins". |
Changelog:
Creation of the MsgRedistribution option. If enabled, will override the entire old system installed by default, and it will save the last 300 lines for both privmsgs and notices (except ctcp) and all separately by channel and by recipient. It records everything even if the client is logged into JBNC or not.
As soon as the client reconnects to JBNC, it will send all privmsgs / notices to the client. The IRC client should sort the msgids by checking if they are already received, if they are not received then the client updates the new messages. Once the client has updated all the new messages, then it should automatically send "/jbnc logclear" to remove the entire "privmsgnotice" array from the client connected to the JBNC.
[To the lines 426, 633, 726, 789, 1361 and 1428]
Add the SASL account so that it is stored
[To the line 942]
Addition of the away-notify cap to display the raws of the away and back
[To the line 883]
Attempt to correct some miscellaneous bugs
[To the lines 253, 524, 659, 1108, 1215 and 1218]
In test/prod for several weeks on an UnrealIRCd 5.0.9 with irc-framework latest version, it works well, sometimes with spikes of 180 clients connected simultaneously