AssertionError [ERR_ASSERTION]: false == true #47

misterfresh · 2017-06-25T22:08:39Z

I get the error
assert.js:60
throw new errors.AssertionError({
at PriorityNode.removeChild (node_modules\spdy-transport\lib\spdy-transport\priority.js:74:3)
at PriorityNode.remove ( node_modules\spdy-transport\lib\spdy-transport\priority.js:62:15)
at PriorityTree.add ( node_modules\spdy-transport\lib\spdy-transport\priority.js:163:23)
at Stream._initPriority ( node_modules\spdy-transport\lib\spdy-transport\stream.js:101:25)
at new Stream ( node_modules\spdy-transport\lib\spdy-transport\stream.js:76:8)
at Connection._createStream ( node_modules\spdy-transport\lib\spdy-transport\connection.js:388:16)
at Connection._handleHeaders ( node_modules\spdy-transport\lib\spdy-transport\connection.js:436:21)
at Connection._handleFrame ( node_modules\spdy-transport\lib\spdy-transport\connection.js:319:10)
at Parser. ( node_modules\spdy-transport\lib\spdy-transport\connection.js:156:10)
at emitOne (events.js:115:13)
at Parser.emit (events.js:210:7)
at addChunk ( node_modules\readable-stream\lib_stream_readable.js:283:12)
at readableAddChunk ( node_modules\readable-stream\lib_stream_readable.js:270:11)
at Parser.Readable.push ( node_modules\readable-stream\lib_stream_readable.js:237:10)
at Parser.Transform.push ( node_modules\readable-stream\lib_stream_transform.js:146:32)
at next ( node_modules\spdy-transport\lib\spdy-transport\protocol\base\parser.js:53:12)

This happens on http2 push from server

misterfresh · 2017-06-25T22:17:52Z

I commented the line 74 "assert(index !== -1)" in spdy-transport\lib\spdy-transport\priority.js:74:3
and now the server is not crashing any more...

To give context, I am pushing a lot of files with http2 push, and for every file that is not actually requested by the client, I get the error
link /js/vendors/aphrodite push error Error: Got RST: REFUSED_STREAM
at Stream._handleRST ( node_modules\spdy-transport\lib\spdy-transport\stream.js:281:24)
at Stream._handleFrame ( node_modules\spdy-transport\lib\spdy-transport\stream.js:126:10)
at Connection._handleFrame ( node_modules\spdy-transport\lib\spdy-transport\connection.js:324:12)
at Parser. ( node_modules\spdy-transport\lib\spdy-transport\connection.js:156:10)
at emitOne (events.js:115:13)
at Parser.emit (events.js:210:7)
at addChunk ( node_modules\readable-stream\lib_stream_readable.js:283:12)
at readableAddChunk ( node_modules\readable-stream\lib_stream_readable.js:270:11)
at Parser.Readable.push ( node_modules\readable-stream\lib_stream_readable.js:237:10)
at Parser.Transform.push ( node_modules\readable-stream\lib_stream_transform.js:146:32)
at next ( node_modules\spdy-transport\lib\spdy-transport\protocol\base\parser.js:53:12)
at node_modules\spdy-transport\lib\spdy-transport\protocol\http2\parser.js:72:5
at Parser.onRSTFrame (node_modules\spdy-transport\lib\spdy-transport\protocol\http2\parser.js:368:3)
at Parser.onFrameBody ( node_modules\spdy-transport\lib\spdy-transport\protocol\http2\parser.js:144:10)
at Parser.execute ( node_modules\spdy-transport\lib\spdy-transport\protocol\http2\parser.js:64:8)
at Parser._consume ( node_modules\spdy-transport\lib\spdy-transport\protocol\base\parser.js:95:8)

matthewp · 2017-06-26T18:05:28Z

I submitted #48 which should fix your issue here.

When a node is removed it gets removed from the tree's `map` but not the tree's `list`, so this memory is leaked. This also fixes the assertion errors seen in spdy-http2#47 and spdy-http2/node-spdy#318 and elsewhere.

misterfresh · 2017-06-27T21:33:06Z

With your fix, I'm getting a slightly different error, but the server still crashes when a resource pushed by http2 server push is not requested by the client.

assert.js:60
throw new errors.AssertionError({
^

AssertionError [ERR_ASSERTION]: false == true
at PriorityNode.removeChild ( node_modules\spdy-transport\lib\spdy-transport\priority.js:74:3)
at PriorityNode.remove ( node_modules\spdy-transport\lib\spdy-transport\priority.js:62:15)
at Stream._handlePriority ( node_modules\spdy-transport\lib\spdy-transport\stream.js:305:18)
at Stream._handleFrame ( node_modules\spdy-transport\lib\spdy-transport\stream.js:128:10)
at Connection._handleFrame ( node_modules\spdy-transport\lib\spdy-transport\connection.js:324:12)
at Parser. ( node_modules\spdy-transport\lib\spdy-transport\connection.js:156:10)
at emitOne (events.js:115:13)
at Parser.emit (events.js:210:7)
at addChunk ( node_modules\readable-stream\lib_stream_readable.js:283:12)
at readableAddChunk ( node_modules\readable-stream\lib_stream_readable.js:270:11)
at Parser.Readable.push ( node_modules\readable-stream\lib_stream_readable.js:237:10)
at Parser.Transform.push ( node_modules\readable-stream\lib_stream_transform.js:146:32)
at next ( node_modules\spdy-transport\lib\spdy-transport\protocol\base\parser.js:53:12)
at node_modules\spdy-transport\lib\spdy-transport\protocol\http2\parser.js:72:5
at Parser.onPriorityFrame ( node_modules\spdy-transport\lib\spdy-transport\protocol\http2\parser.js:539:3)
at Parser.onFrameBody ( node_modules\spdy-transport\lib\spdy-transport\protocol\http2\parser.js:154:10)

matthewp · 2017-06-28T12:03:44Z

@misterfresh I have noticed that as well. My fix fixes some of the issues but the error can still happen if there is a PRIORITY frame and the node has already been removed. So it needs to check in that spot as well if the node is part of the tree.

Jaeiya · 2018-02-27T19:39:35Z

Is there a workaround for this?
I just loaded up my webapp in firefox and got this error. For some reason I do not get this error when opening in Chrome.

misterfresh · 2018-02-27T20:46:46Z

Here's a temporary fix : in your project's main package.json add:

"scripts": {
    "postinstall": "node ./conf/quickfix.js"
}

and in the quickfix.js file :

let fs = require('fs')
let path = require('path')
let file = path.join(
    process.cwd(),
    'node_modules/spdy-transport/lib/spdy-transport/priority.js'
)

let data = fs
    .readFileSync(file)
    .toString()
    .split('\n')
if (data.length < 190) {
    data.splice(73, 0, '/*')
    data.splice(75, 0, '*/')
    data.splice(
        187,
        0,
        `
	var index = utils.binarySearch(this.list, node, compareChildren);
 	this.list.splice(index, 1);
`
    )
    let text = data.join('\n')

    fs.writeFile(file, text, function(err) {
        if (err) return console.log(err)
    })
}

now everytime you install spdy it will be patched if needed.

also node-http2 native is available, just not yet compatible with express

Jaeiya · 2018-02-27T20:48:47Z

Thanks for this.
Do you know when the native will be compatible with express?

misterfresh · 2018-02-27T21:33:44Z

no... there is an issue on it but I dont think they have a date yet

th3nate · 2018-04-18T10:17:18Z

hello,
im experiencing the same issue,
although using node-spdy im getting the same error about the transport module with version 2.0.20
was this issue fixed in the newest version?

AssertionError [ERR_ASSERTION]: false == true
at PriorityNode.removeChild (/app/node_modules/spdy-transport/lib/spdy-transport/priority.js:74:3)
at PriorityNode.remove (/app/node_modules/spdy-transport/lib/spdy-transport/priority.js:62:15)
at Stream._handlePriority (/app/node_modules/spdy-transport/lib/spdy-transport/stream.js:305:18)
at Stream._handleFrame (/app/node_modules/spdy-transport/lib/spdy-transport/stream.js:128:10)
at Connection._handleFrame (/app/node_modules/spdy-transport/lib/spdy-transport/connection.js:324:12)
at Parser. (/app/node_modules/spdy-transport/lib/spdy-transport/connection.js:156:10)
at emitOne (events.js:116:13)
at Parser.emit (events.js:211:7)
at addChunk (/app/node_modules/readable-stream/lib/_stream_readable.js:284:12)
at readableAddChunk (/app/node_modules/readable-stream/lib/_stream_readable.js:271:11)
at Parser.Readable.push (/app/node_modules/readable-stream/lib/_stream_readable.js:238:10)
at Parser.Transform.push (/app/node_modules/readable-stream/lib/_stream_transform.js:146:32)
at next (/app/node_modules/spdy-transport/lib/spdy-transport/protocol/base/parser.js:53:12)
at /app/node_modules/spdy-transport/lib/spdy-transport/protocol/http2/parser.js:72:5

UPDATE:
updated the pkg to 2.1.0 but still the issue exists.
so now I've reverted back to 2.0.20 and used the patch from the previous comment, ill share if it solved the issue.

if anyone has a better idea i'd greatly appreciate it,
thanks!

wmertens · 2018-05-24T11:59:24Z

How about just replacing the assert(index !== -1) with if (index === -1) return? Seems unsafe to let the function remove the last child from the list…

vytautas-pranskunas- · 2018-07-18T14:58:01Z

Any progress on this one? Or SPDY package with 100k weekly downloads has ment to be used with hacks and memory leaks?

mrbinky3000 · 2018-09-06T19:38:05Z

I suddenly started experiencing this issue with webpack and webpack-dev-server.

AssertionError [ERR_ASSERTION]: false == true
    at PriorityNode.removeChild (/Users/me/myproject/node_modules/spdy-transport/lib/spdy-transport/priority.js:74:3)
    at PriorityNode.remove (/Users/me/myproject/node_modules/spdy-transport/lib/spdy-transport/priority.js:62:15)
    at PriorityTree.add (/Users/me/myproject/node_modules/spdy-transport/lib/spdy-transport/priority.js:163:23)
    at Stream._initPriority (/Users/me/myproject/node_modules/spdy-transport/lib/spdy-transport/stream.js:101:25)
    at new Stream (/Users/me/myproject/node_modules/spdy-transport/lib/spdy-transport/stream.js:76:8)
    at Connection._createStream (/Users/me/myproject/node_modules/spdy-transport/lib/spdy-transport/connection.js:388:16)
    at Connection._handleHeaders (/Users/me/myproject/node_modules/spdy-transport/lib/spdy-transport/connection.js:436:21)
    at Connection._handleFrame (/Users/me/myproject/node_modules/spdy-transport/lib/spdy-transport/connection.js:319:10)
    at Parser.<anonymous> (/Users/me/myproject/node_modules/spdy-transport/lib/spdy-transport/connection.js:156:10)
    at emitOne (events.js:116:13)
    at Parser.emit (events.js:211:7)
    at addChunk (/Users/me/myproject/node_modules/readable-stream/lib/_stream_readable.js:291:12)
    at readableAddChunk (/Users/me/myproject/node_modules/readable-stream/lib/_stream_readable.js:278:11)
    at Parser.Readable.push (/Users/me/myproject/node_modules/readable-stream/lib/_stream_readable.js:245:10)
    at Parser.Transform.push (/Users/me/myproject/node_modules/readable-stream/lib/_stream_transform.js:148:32)
    at next (/Users/me/myproject/node_modules/spdy-transport/lib/spdy-transport/protocol/base/parser.js:53:12)

Relevant dev dependencies

    "webpack": "^4.16.0",
    "webpack-bundle-analyzer": "^2.9.1",
    "webpack-cli": "^3.0.8",
    "webpack-combine-loaders": "^2.0.3",
    "webpack-dev-middleware": "^3.1.3",
    "webpack-dev-server": "^3.1.7",
    "webpack-merge": "^4.1.1",

Started happening after I updated to Google Chrome 69.0.3497.81. Trying Firefox as a work around, but would really like to be able to use Chrome.

jordibartolome · 2018-09-07T14:58:14Z

Same problem here when updating to Chrome 69

assert.js:85
  throw new assert.AssertionError({
  ^
AssertionError: false == true
    at PriorityNode.removeChild (/Users/jordi/Work/webapp/client/node_modules/spdy-transport/lib/spdy-transport/priority.js:74:3)
    at PriorityNode.remove (/Users/jordi/Work/webapp/client/node_modules/spdy-transport/lib/spdy-transport/priority.js:62:15)
    at PriorityTree.add (/Users/jordi/Work/webapp/client/node_modules/spdy-transport/lib/spdy-transport/priority.js:163:23)
    at Stream._initPriority (/Users/jordi/Work/webapp/client/node_modules/spdy-transport/lib/spdy-transport/stream.js:101:25)
    at new Stream (/Users/jordi/Work/webapp/client/node_modules/spdy-transport/lib/spdy-transport/stream.js:76:8)
    at Connection._createStream (/Users/jordi/Work/webapp/client/node_modules/spdy-transport/lib/spdy-transport/connection.js:388:16)
    at Connection._handleHeaders (/Users/jordi/Work/webapp/client/node_modules/spdy-transport/lib/spdy-transport/connection.js:436:21)
    at Connection._handleFrame (/Users/jordi/Work/webapp/client/node_modules/spdy-transport/lib/spdy-transport/connection.js:319:10)
    at Parser.<anonymous> (/Users/jordi/Work/webapp/client/node_modules/spdy-transport/lib/spdy-transport/connection.js:156:10)
    at emitOne (events.js:96:13)
    at Parser.emit (events.js:188:7)
    at addChunk (/Users/jordi/Work/webapp/client/node_modules/readable-stream/lib/_stream_readable.js:284:12)
    at readableAddChunk (/Users/jordi/Work/webapp/client/node_modules/readable-stream/lib/_stream_readable.js:271:11)
    at Parser.Readable.push (/Users/jordi/Work/webapp/client/node_modules/readable-stream/lib/_stream_readable.js:238:10)
    at Parser.Transform.push (/Users/jordi/Work/webapp/client/node_modules/readable-stream/lib/_stream_transform.js:146:32)
    at next (/Users/jordi/Work/webapp/client/node_modules/spdy-transport/lib/spdy-transport/protocol/base/parser.js:53:12)

jordibartolome · 2018-09-07T15:15:42Z

The solution that @misterfresh posted on Feb 27th seems to fix it!

limbosounds · 2018-09-10T08:40:33Z

Due to this issue WDS is falling every 10-20 minutes. Madness.
Confirming that this appeared after I upgraded my Chrome to 69.

eyz · 2018-09-10T18:17:33Z

I only started seeing this after upgrading to Chrome 69 as well; same NPMs, same NodeJS version as before it was happening

rathpc · 2018-09-11T14:17:44Z

I also experienced this issue with the following config:

Operating System: macOS Sierra (10.12.6)
Node Version: 8.11.2
NPM Version: 6.1.0
webpack Version: 2.7.0
webpack-dev-server Version: 2.11.2

I am using the patch fix mentioned by @misterfresh with some additional logic until an official fix is released.

wmertens · 2018-09-11T15:51:17Z

is there anybody maintaining a forked npm package with the fix applied?

eyz · 2018-09-12T00:29:12Z

The #47 (comment) fix is working well for me; no crashes from Chrome 69 clients after applying that. It would be nice to see this reviewed by the spdy-http2 folks and given priority as soon as possible. Does anyone have this fix as a PR to this project already?

@misterfresh have you submitted this fix already as a PR to this project? Is there anything blocking you from doing so, if not already submitted?

johntran · 2018-09-13T01:01:30Z

@diasdavid is looking for maintainers for this repo and the org in general: spdy-http2/node-spdy#339

eyz · 2018-09-13T01:03:14Z

Sorry to be slightly off-topic, but I just got this stack trace today, and thus I am no longer using the spdy NPM due to the error from the OP as well as this new one today. Should I create a new issue for this one? Is this related to the Chrome 69 compatibility we've been discussing, or something else?

events.js:167
      throw er; // Unhandled 'error' event
      ^

Error: Stream write aborted
    at /opt/cde/node_modules/spdy-transport/lib/spdy-transport/stream.js:141:16
    at process._tickCallback (internal/process/next_tick.js:61:11)
Emitted 'error' event at:
    at Stream.onStreamError (/opt/cde/node_modules/spdy/lib/spdy/handle.js:110:18)
    at Stream.emit (events.js:182:13)
    at Stream.EventEmitter.emit (domain.js:442:20)
    at onwriteError (/opt/cde/node_modules/readable-stream/lib/_stream_writable.js:449:12)
    at onwrite (/opt/cde/node_modules/readable-stream/lib/_stream_writable.js:470:11)
    at WritableState.onwrite (/opt/cde/node_modules/readable-stream/lib/_stream_writable.js:180:5)
    at /opt/cde/node_modules/spdy-transport/lib/spdy-transport/stream.js:239:23
    at /opt/cde/node_modules/spdy-transport/lib/spdy-transport/stream.js:141:7
    at process._tickCallback (internal/process/next_tick.js:61:11)

thisVioletHydra · 2018-09-21T11:39:00Z

v10.11.0:
MSYS_NT-10.0 macOS 2.10.0(0.325/5/3) 2018-06-13 23:34 x86_64 Msys (it`s WINDOWS x64):
Subsystem:

[04:04:30] AssertionError [ERR_ASSERTION]: The expression evaluated to a falsy value:

  assert(index !== -1)

    at PriorityNode.removeChild (D:\FRONTEND\www\company-m4leads-com\node_modules\spdy-transport\lib\spdy-transport\priority.js:74:3)
    at PriorityNode.remove (D:\FRONTEND\www\company-m4leads-com\node_modules\spdy-transport\lib\spdy-transport\priority.js:62:15)
    at PriorityTree.add (D:\FRONTEND\www\company-m4leads-com\node_modules\spdy-transport\lib\spdy-transport\priority.js:163:23)
    at Stream._initPriority (D:\FRONTEND\www\company-m4leads-com\node_modules\spdy-transport\lib\spdy-transport\stream.js:101:25)
    at new Stream (D:\FRONTEND\www\company-m4leads-com\node_modules\spdy-transport\lib\spdy-transport\stream.js:76:8)
    at Connection._createStream (D:\FRONTEND\www\company-m4leads-com\node_modules\spdy-transport\lib\spdy-transport\connection.js:388:16)
    at Connection._handleHeaders (D:\FRONTEND\www\company-m4leads-com\node_modules\spdy-transport\lib\spdy-transport\connection.js:436:21)
    at Connection._handleFrame (D:\FRONTEND\www\company-m4leads-com\node_modules\spdy-transport\lib\spdy-transport\connection.js:319:10)
    at Parser.<anonymous> (D:\FRONTEND\www\company-m4leads-com\node_modules\spdy-transport\lib\spdy-transport\connection.js:156:10)
    at Parser.emit (events.js:182:13)
    at Parser.EventEmitter.emit (domain.js:460:23)
    at addChunk (D:\FRONTEND\www\company-m4leads-com\node_modules\readable-stream\lib\_stream_readable.js:291:12)
    at readableAddChunk (D:\FRONTEND\www\company-m4leads-com\node_modules\readable-stream\lib\_stream_readable.js:278:11)
    at Parser.Readable.push (D:\FRONTEND\www\company-m4leads-com\node_modules\readable-stream\lib\_stream_readable.js:245:10)
    at Parser.Transform.push (D:\FRONTEND\www\company-m4leads-com\node_modules\readable-stream\lib\_stream_transform.js:148:32)
    at next (D:\FRONTEND\www\company-m4leads-com\node_modules\spdy-transport\lib\spdy-transport\protocol\base\parser.js:53:12)

hello, i coding new site, after update or update same modules, i not understand, my watch started to break and throw an error.
a week ago this was not, I use for http2 spdy, gulp, webpack.
If you need any further information I can provide.

What causes the error? After every 10-15 minutes coding site there is such a bug, without a clue how this happens.

pcnate · 2018-10-02T14:39:22Z

Same issue on Debian Linux. Same version of spdy-http2. I am using socket.io/socket.io-client with redbird proxy.

ivnmaksimovic · 2018-10-04T09:30:30Z

Do not use Chrome Canary or new Chrome. I downgraded to Chrome 67 and I can develop without the watcher breaking all the time.

jordibartolome · 2018-10-04T11:27:47Z

Do not use Chrome Canary or new Chrome. I downgraded to Chrome 67 and I can develop without the watcher breaking all the time.

This is probably the worst reply I've read in time 😂
This is not "a bug" in chrome fixed in a specific version, this has been like this for the last 2 stable versions, so you cannot hold the old Chrome version forever.

ivnmaksimovic · 2018-10-04T11:42:46Z

@jordibartolome I am just referring to those having issue with webpack watch, that constantly breaks with "assert(index !== -1)" in spdy-transport\lib\spdy-transport\priority.js:74:3". I am not trying to contribute in fixing this issue. It's just a workaround for me, to be able to keep working on a project without having to rebuild every few minutes. It might help someone.

pcnate · 2018-10-04T13:23:12Z

@ivnmaksimovic a work around was posted above using a post install script
#47 (comment)

nihlton · 2018-10-08T18:31:10Z

i've got the work around working - and thats great.

any word on this being fixed properly?

pcnate · 2018-10-09T13:38:47Z

@nihlton #57 looks to fix the issue. Hopefully someone can get this confirmed and merged soon

mlncstr · 2018-10-12T17:02:21Z

Could this also potentially affect pre-flight OPTIONS requests?

Getting this on a client's site when attempting an API call to Azure:
ERR_SPDY_INADEQUATE_TRANSPORT_SECURITY

…pdy-http2/spdy-transport#47 Change-Id: Ib5f495ecf82f5b7c667c08e699b2c4ca2aab721b Reviewed-on: https://git-amr-3.devtools.intel.com/gerrit/190589 Tested-by: webrtctest <webrtctest@intel.com> Reviewed-by: Zhu, Jianjun <jianjun.zhu@intel.com>

intafon · 2018-10-15T20:13:59Z

~~Also using Chrome 69 -- ran @misterfresh 's patch, but still keeps crashing. . . anyone have any luck with any other fix patch?~~

EDIT: not sure what changed from my original attempt, but I have noticed that with this patch the crashing occurs much less often (maybe once a day as opposed to on nearly every edit before, so disregard my original comment. ;-)

…pdy-http2/spdy-transport#47 Change-Id: Ib5f495ecf82f5b7c667c08e699b2c4ca2aab721b Reviewed-on: https://git-amr-3.devtools.intel.com/gerrit/190589 Tested-by: webrtctest <webrtctest@intel.com> Reviewed-by: Zhu, Jianjun <jianjun.zhu@intel.com>

preeti-tm · 2018-10-23T08:47:11Z

I got the same error.

Grantlyk · 2018-11-02T12:01:05Z

Hey i've now started getting this error randomly today in my project, has anyone merged in a PR or got a release that fixes this issue?

preeti-tm · 2018-11-02T12:23:33Z

This solution #57 is working in my case

jacobheun · 2018-11-08T11:03:00Z

New versions of spdy (4.0.0) and spdy-transport (3.0.0) include this fix.

odinho · 2018-11-08T12:19:38Z

Awesome, opened a pull request for webpack-dev-server: webpack/webpack-dev-server#1563

benlind · 2018-11-30T18:20:36Z

If you are using yarn and want this fix for webpack-dev-server, add this to your package.json:

"resolutions": {
  "webpack-dev-server/**/spdy-transport": "^3.0.0"
}

Then run yarn.

matthewp mentioned this issue Jun 26, 2017

Fix memory leak when removing nodes #48

Closed

wmertens mentioned this issue May 24, 2018

AssertionError on production spdy-http2/node-spdy#336

Closed

bdpartridge mentioned this issue Sep 6, 2018

AssertionError in spdy-transport consistently causing failures while running in Chrome 69 webpack/webpack-dev-server#1491

Closed

2 tasks

JamesIves mentioned this issue Oct 15, 2018

Assertion error Fix - Fixed Assertion true === false error #57

Merged

pcnate mentioned this issue Nov 4, 2018

unexpectedly stopped routing pcnate/red-ampp#6

Closed

jianjunz mentioned this issue Nov 5, 2018

Revert "BUGFIX[1659] Temporarily fixed the #47 bug of spdy …" open-webrtc-toolkit/owt-client-javascript#19

Merged

Mydayyy mentioned this issue Nov 6, 2018

SyntaxError: Unexpected identifier #59

Closed

jacobheun closed this as completed Nov 8, 2018

odinho mentioned this issue Nov 8, 2018

fix(package): update spdy v3.4.1...4.0.0 (assertion error) (#1491) webpack/webpack-dev-server#1563

Merged

6 tasks

jacobheun mentioned this issue Mar 27, 2019

AssertionError [ERR_ASSERTION]: assert(index !== -1) #62

Closed

jacobheun mentioned this issue May 9, 2019

AssertionError [ERR_ASSERTION]: false == true #63

Closed

AssertionError [ERR_ASSERTION]: false == true #47

AssertionError [ERR_ASSERTION]: false == true #47

Comments

misterfresh commented Jun 25, 2017

misterfresh commented Jun 25, 2017

matthewp commented Jun 26, 2017

misterfresh commented Jun 27, 2017

matthewp commented Jun 28, 2017

Jaeiya commented Feb 27, 2018

misterfresh commented Feb 27, 2018

Jaeiya commented Feb 27, 2018

misterfresh commented Feb 27, 2018

th3nate commented Apr 18, 2018 • edited Loading

wmertens commented May 24, 2018

vytautas-pranskunas- commented Jul 18, 2018 • edited Loading

mrbinky3000 commented Sep 6, 2018 • edited Loading

jordibartolome commented Sep 7, 2018 • edited Loading

jordibartolome commented Sep 7, 2018 • edited Loading

limbosounds commented Sep 10, 2018 • edited Loading

eyz commented Sep 10, 2018

rathpc commented Sep 11, 2018

wmertens commented Sep 11, 2018

eyz commented Sep 12, 2018 • edited Loading

johntran commented Sep 13, 2018

eyz commented Sep 13, 2018 • edited Loading

thisVioletHydra commented Sep 21, 2018

pcnate commented Oct 2, 2018

ivnmaksimovic commented Oct 4, 2018

jordibartolome commented Oct 4, 2018 • edited Loading

ivnmaksimovic commented Oct 4, 2018

pcnate commented Oct 4, 2018

nihlton commented Oct 8, 2018

pcnate commented Oct 9, 2018

mlncstr commented Oct 12, 2018

intafon commented Oct 15, 2018 • edited Loading

preeti-tm commented Oct 23, 2018

Grantlyk commented Nov 2, 2018

preeti-tm commented Nov 2, 2018

jacobheun commented Nov 8, 2018

odinho commented Nov 8, 2018

benlind commented Nov 30, 2018

th3nate commented Apr 18, 2018 •

edited

Loading

vytautas-pranskunas- commented Jul 18, 2018 •

edited

Loading

mrbinky3000 commented Sep 6, 2018 •

edited

Loading

jordibartolome commented Sep 7, 2018 •

edited

Loading

jordibartolome commented Sep 7, 2018 •

edited

Loading

limbosounds commented Sep 10, 2018 •

edited

Loading

eyz commented Sep 12, 2018 •

edited

Loading

eyz commented Sep 13, 2018 •

edited

Loading

jordibartolome commented Oct 4, 2018 •

edited

Loading

intafon commented Oct 15, 2018 •

edited

Loading