Closed Bug 955300 Opened 11 years ago Closed 5 years ago

CTCP parse error

Categories

(Chat Core :: IRC, defect)

defect
Not set
minor

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: aleth, Unassigned)

Details

Attachments

(1 file)

*** Original post on bio 1867 at 2013-01-28 21:16:00 UTC *** Timestamp: 01/28/2013 09:54:02 PM Error: Error running command PRIVMSG with handler CTCP: {"rawMessage":":Mic!Mic@moz-D88BA... PRIVMSG #instantbird :I'm getting lots of warnings like \"Warning: Failed to convert NOTICE aleth :\u0001VERSION Instantbird 1.4a1pre\u0001 from Unicode to UTF-8,ISO-8859-1.\", \"Warning: Failed to convert PONG gravel.mozilla.org from Unicode to UTF-8,ISO-8859-1.\" at the moment by the way.","command":"PRIVMSG","params":["#instantbird","I'm getting lots of warnings like \"Warning: Failed to convert NOTICE aleth : from Unicode to UTF-8,ISO-8859-1.\", \"Warning: Failed to convert PONG gravel.mozilla.org from Unicode to UTF-8,ISO-8859-1.\" at the moment by the way."],"nickname":"Mic","user":"Mic","host":"moz-D88BA...","source":"Mic@moz-D88BA...","ctcp":{"rawMessage":"VERSION Instantbird 1.4a1pre","command":"VERSION","param":"Instantbird 1.4a1pre"}} aMessage is undefined Source File: resource:///modules/ircHandlers.jsm Line: 120 Source Code: prpl-irc
*** Original post on bio 1867 at 2013-01-28 21:19:05 UTC *** The message displayed in the conversation was "I'm getting lots of warnings like "Warning: Failed to convert NOTICE aleth : from Unicode to UTF-8,ISO-8859-1.", "Warning: Failed to convert PONG gravel.mozilla.org from Unicode to UTF-8,ISO-8859-1." at the moment by the way."
*** Original post on bio 1867 as attmnt 2212 at 2013-01-28 21:24:00 UTC *** For more information, we saw: 3:54:03 PM - Mic: I'm getting lots of warnings like "Warning: Failed to convert NOTICE aleth : from Unicode to UTF-8,ISO-8859-1.", "Warning: Failed to convert PONG gravel.mozilla.org from Unicode to UTF-8,ISO-8859-1." at the moment by the way. Mic saw the attached.

There's no steps to reproduce this and I think moznet has completely changed out their servers since 2013.

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: