Skip to content

fix: use irc-unknown when irc server couldn't be loaded - #5419

Merged
pajlada merged 2 commits into
masterfrom
fix/empty-irc-logging-crash
May 25, 2024
Merged

pajlada merged 2 commits into
masterfrom
fix/empty-irc-logging-crash

Conversation

@pajlada

@pajlada pajlada commented May 25, 2024 •

Copy link
Copy Markdown
Member

If logging is enabled and you have joined an IRC server/channel before that's now been removed somehow (by irc server being removed or irc support being disabled), the channel logger will now log the channel contents to irc-unknown instead of erroring out

@pajlada

pajlada commented May 25, 2024

Copy link
Copy Markdown
Member Author

image

@pajlada
pajlada enabled auto-merge (squash) May 25, 2024 11:27
@Mm2PL

Mm2PL commented May 25, 2024 •

Copy link
Copy Markdown
Collaborator

I think if a server doesn't exist we shouldn't even attempt to log these messages. The core issue is that this:

by irc server being removed or irc support being disabled

can happen and we still receive and handle a message.

@pajlada

pajlada commented May 25, 2024

Copy link
Copy Markdown
Member Author

If we stop the message I noticed getting through from coming through, then we fix that crash. All it would take is another message coming through to cause another crash - regardless of what we do, this should still be the preferred behaviour over crashing

@pajlada
pajlada merged commit c5802a0 into master May 25, 2024
@pajlada
pajlada deleted the fix/empty-irc-logging-crash branch May 25, 2024 11:53
babicekmarek pushed a commit to babicekmarek/streamally-chatterino that referenced this pull request Sep 14, 2026
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.

2 participants