Open davidar opened 7 years ago
can you share the stacktrace and say when it happens? (presumably on receiving path?)
-- Matthew Hodgson Matrix.org
On 18 Feb 2017, at 10:43, David A Roberts notifications@github.com wrote:
Something in matrix-js-sdk keeps throwing an exception that just says Unknown error code: Unknown message, which isn't particularly helpful. The stack trace only contains node_modules/olm/olm.js:19, which seems to appear in every stack trace anyway.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.
This happened around 2017-02-23 18:40 UTC:
/sync error Unknown error code: Unknown message
{ [Unknown error code: Unknown message]
errcode: undefined,
name: 'Unknown error code',
message: 'Unknown message',
data: {},
httpStatus: 500 }
Starting keep-alive
/sync error Unknown error code: Unknown message
{ [Unknown error code: Unknown message]
errcode: undefined,
name: 'Unknown error code',
message: 'Unknown message',
data: {},
httpStatus: 500 }
Starting keep-alive
/sync error Unknown error code: Unknown message
{ [Unknown error code: Unknown message]
errcode: undefined,
name: 'Unknown error code',
message: 'Unknown message',
data: {},
httpStatus: 500 }
Starting keep-alive
/sync error Unknown error code: Unknown message
{ [Unknown error code: Unknown message]
errcode: undefined,
name: 'Unknown error code',
message: 'Unknown message',
data: {},
httpStatus: 500 }
Starting keep-alive
/home/david/mubot/node_modules/olm/olm.js:19
"undefined"!==typeof module&&(module.exports=a);process.on("uncaughtException",function(a){if(!(a instanceof T))throw a;});a.inspect=function(){return"[Emscripten Module object]"}}else if(ma)a.print||(a.print=print),"undefined"!=typeof printErr&&(a.printErr=printErr),a.read="undefined"!=typeof read?read:function(){throw"no read() available (jsc?)";},a.readBinary=function(a){if("function"===typeof readbuffer)return new Uint8Array(readbuffer(a));a=read(a,"binary");z("object"===typeof a);return a},"undefined"!=
^
Unknown error code: Unknown message
@davidar how are You using it? I had the same problem and it's because the fetch function didn't behave as the sdk spected
@pbruna it happens sometime during whatever internal sync loop runs after calling startClient
Happened again a couple of days ago, slightly different error:
/sync error Unknown error code: Unknown message
{ [Unknown error code: Unknown message]
errcode: undefined,
name: 'Unknown error code',
message: 'Unknown message',
data: '<html><body><h1>504 Gateway Time-out</h1>\nThe server didn\'t respond in time.\n</body></html>\n',
httpStatus: 504 }
Starting keep-alive
/home/david/mubot/node_modules/olm/olm.js:19
"undefined"!==typeof module&&(module.exports=a);process.on("uncaughtException",function(a){if(!(a instanceof T))throw a;});a.inspect=function(){return"[Emscripten Module object]"}}else if(ma)a.print||(a.print=print),"undefined"!=typeof printErr&&(a.printErr=printErr),a.read="undefined"!=typeof read?read:function(){throw"no read() available (jsc?)";},a.readBinary=function(a){if("function"===typeof readbuffer)return new Uint8Array(readbuffer(a));a=read(a,"binary");z("object"===typeof a);return a},"undefined"!=
^
Unknown error code: Unknown message
Again, earlier today:
m.new_device event from @leer10:matrix.org:QOCAUKYEVA for rooms !UCnwUWwIKhcpaPTHtR:sw1v.org
Known device; ignoring
/home/david/mubot/node_modules/olm/olm.js:19
"undefined"!==typeof module&&(module.exports=a);process.on("uncaughtException",function(a){if(!(a instanceof T))throw a;});a.inspect=function(){return"[Emscripten Module object]"}}else if(ma)a.print||(a.print=print),"undefined"!=typeof printErr&&(a.printErr=printErr),a.read="undefined"!=typeof read?read:function(){throw"no read() available (jsc?)";},a.readBinary=function(a){if("function"===typeof readbuffer)return new Uint8Array(readbuffer(a));a=read(a,"binary");z("object"===typeof a);return a},"undefined"!=
^
Unknown error code: Unknown message
Something in matrix-js-sdk keeps throwing an exception that just says
Unknown error code: Unknown message
, which isn't particularly helpful. The stack trace only containsnode_modules/olm/olm.js:19
, which seems to appear in every stack trace anyway.