ndb crashes after launching script #204

vaxerski · 2018-12-01T14:40:38Z

Steps to reproduce:
I'm launching ndb with ndb bot.js and it launches, starts the script and crashes, the same when i click "start" inside ndb and for example toggle "pause on exceptions" or change tab.

ndb version: 1.0.37
Platform / OS version: Microsoft Windows [Version 10.0.17134.407]
Node.js version: 10.14.1

There seems to be no problem with code since it works on normal node, but when i open it in ndb, then it crashes.

What happens instead?

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

Error [ERR_IPC_CHANNEL_CLOSED]: Channel closed
at ChildProcess.target.send (internal/child_process.js:628:16)
at Rpc.routeMessage_ (C:\Users\user\AppData\Roaming\npm\node_modules\ndb\node_modules\carlo\rpc\rpc.js:379:9)
at page_.exposeFunction.data (C:\Users\user\AppData\Roaming\npm\node_modules\ndb\node_modules\carlo\lib\carlo.js:327:71)
at Page._onBindingCalled (C:\Users\user\AppData\Roaming\npm\node_modules\ndb\node_modules\puppeteer-core\lib\Page.js:516:56)
at CDPSession.Page.client.on.event (C:\Users\user\AppData\Roaming\npm\node_modules\ndb\node_modules\puppeteer-core\lib\Page.js:134:54)
at CDPSession.emit (events.js:182:13)
at CDPSession._onMessage (C:\Users\user\AppData\Roaming\npm\node_modules\ndb\node_modules\puppeteer-core\lib\Connection.js:216:12)
at Connection._onMessage (C:\Users\user\AppData\Roaming\npm\node_modules\ndb\node_modules\puppeteer-core\lib\Connection.js:99:19)
at PipeTransport._dispatch (C:\Users\user\AppData\Roaming\npm\node_modules\ndb\node_modules\puppeteer-core\lib\PipeTransport.js:65:24)
at Socket.PipeTransport._eventListeners.helper.addEventListener.buffer (C:\Users\user\AppData\Roaming\npm\node_modules\ndb\node_modules\puppeteer-core\lib\PipeTransport.js:30:64)
Emitted 'error' event at:
at process.nextTick (internal/child_process.js:632:35)
at process._tickCallback (internal/process/next_tick.js:61:11)

I've tried re-installing ndb, reinstalling all dependencies, reinstalling ms build tools, different flags and stuff. It did work, but lately stopped.

I can add that when this started occuring, the ndb got slow, instead of showing my files immediately, it showed them after 10s, and there are windows popping up, which weren't before (node.EXE and npm)

Thanks in advance.

The text was updated successfully, but these errors were encountered:

alexkozy · 2018-12-02T22:21:18Z

The issue should be fixed in [email protected], I will separately take a look on popping up windows. Thanks for report and feel free to comment here if you can reproduce it on 1.0.39.

alexkozy · 2018-12-02T23:08:09Z

popping up windows are fixed in [email protected].

vaxerski · 2018-12-03T18:50:09Z

okay, ndb 1.0.41

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

Error [ERR_IPC_CHANNEL_CLOSED]: Channel closed
at ChildProcess.target.send (internal/child_process.js:644:16)
at Rpc.routeMessage_ (C:\Users\user\AppData\Roaming\npm\node_modules\ndb\node_modules\carlo\rpc\rpc.js:379:9)
at page_.exposeFunction.data (C:\Users\user\AppData\Roaming\npm\node_modules\ndb\node_modules\carlo\lib\carlo.js:379:71)
at Page._onBindingCalled (C:\Users\user\AppData\Roaming\npm\node_modules\ndb\node_modules\puppeteer-core\lib\Page.js:516:56)
at CDPSession.Page.client.on.event (C:\Users\user\AppData\Roaming\npm\node_modules\ndb\node_modules\puppeteer-core\lib\Page.js:134:54)
at CDPSession.emit (events.js:182:13)
at CDPSession._onMessage (C:\Users\user\AppData\Roaming\npm\node_modules\ndb\node_modules\puppeteer-core\lib\Connection.js:216:12)
at Connection._onMessage (C:\Users\user\AppData\Roaming\npm\node_modules\ndb\node_modules\puppeteer-core\lib\Connection.js:99:19)
at PipeTransport._dispatch (C:\Users\user\AppData\Roaming\npm\node_modules\ndb\node_modules\puppeteer-core\lib\PipeTransport.js:59:22)
at Socket.PipeTransport._eventListeners.helper.addEventListener.buffer (C:\Users\user\AppData\Roaming\npm\node_modules\ndb\node_modules\puppeteer-core\lib\PipeTransport.js:30:64)
Emitted 'error' event at:
at process.nextTick (internal/child_process.js:648:35)
at process.internalTickCallback (internal/process/next_tick.js:70:11)

the same error on any file that runs forever and does stuff on event.

alexkozy · 2018-12-03T18:52:47Z

What version of Chrome do you have locally installed?

vaxerski · 2018-12-03T19:00:30Z

Version 70.0.3538.110 (Official) (64-bit)

vaxerski · 2018-12-04T20:14:10Z

maybe it's a problem with my system specifically, tell me what to check if there are any possible causes.

vaxerski · 2018-12-05T20:10:24Z

sorry for the multiple comments but here's a list of things I'd want to add, because they might be helpful in finding the cause.

My windows C drive has recently got some files NTFS compressed. Idk why, I've reverted most of them and disabled it. Maybe some critical ndb files got affected still? (appdata/npm isn't compressed anymore)
When launching ndb, it takes AGES to show the project folder despite it being not so large (3k lines of code in main .js file)
When ndb launches and i wait those AGES for the folder to show up, the CMD takes 70% of CPU, which is pretty much a lot for a script editor, it stops when the folder appears in ndb.

My best guess would be windows NTFS compression since the crashes started occurring randomly and about a week later i found about 25GB of compressed files, so that may be the cause.

If it can be, tell me which files does ndb use for me to check if they aren't compressed.

De-compressed and anti-compress locked folders that may relate to ndb as of right now are:

project folder
AppData/roaming/npm
AppData/roaming/npm-cache
whole AppData/Local

Hope we can find the cause,
cheers!

alexkozy · 2018-12-05T20:12:51Z

Thanks a lot for your diagnostic, I will take a look on Windows as soon as I get my windows machine back, it should happen in next day or two.

linqFR · 2018-12-06T00:04:14Z

i have the same issue and same message with:

ndb 1.0.42
chrome Version 71.0.3578.80 (Build officiel) (64 bits)
node 10.14.1 and previous

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

Error [ERR_IPC_CHANNEL_CLOSED]: Channel closed
at ChildProcess.target.send (internal/child_process.js:628:16)
at Rpc.routeMessage_ (C:\Users\user\AppData\Roaming\npm\node_modules\ndb\node_modules\carlo\rpc\rpc.js:379:9)
at page_.exposeFunction.data (C:\Users\user\AppData\Roaming\npm\node_modules\ndb\node_modules\carlo\lib\carlo.js:380:71)
at Page._onBindingCalled (C:\Users\user\AppData\Roaming\npm\node_modules\ndb\node_modules\puppeteer-core\lib\Page.js:516:56)
at CDPSession.Page.client.on.event (C:\Users\user\AppData\Roaming\npm\node_modules\ndb\node_modules\puppeteer-core\lib\Page.js:134:54)
at CDPSession.emit (events.js:182:13)
at CDPSession._onMessage (C:\Users\user\AppData\Roaming\npm\node_modules\ndb\node_modules\puppeteer-core\lib\Connection.js:216:12)
at Connection._onMessage (C:\Users\user\AppData\Roaming\npm\node_modules\ndb\node_modules\puppeteer-core\lib\Connection.js:99:19)
at PipeTransport._dispatch (C:\Users\user\AppData\Roaming\npm\node_modules\ndb\node_modules\puppeteer-core\lib\PipeTransport.js:65:24)
at Socket.PipeTransport._eventListeners.helper.addEventListener.buffer (C:\Users\user\AppData\Roaming\npm\node_modules\ndb\node_modules\puppeteer-core\lib\PipeTransport.js:30:64)
Emitted 'error' event at:
at process.nextTick (internal/child_process.js:632:35)
at process._tickCallback (internal/process/next_tick.js:61:11)`

i tried to debug till event.js:167 with nbd, but when i added a breakpoint to this line, ndb added lots of breakpoints of other node modules... so i could not track the bug...

vaxerski · 2018-12-08T12:35:52Z

reverted to [email protected] - everything's fine.

EDIT: [email protected] - still fine

Yuan-Zi-Yuan · 2018-12-28T09:23:33Z

reverted to [email protected] - everything's fine.

EDIT: [email protected] - still fine

i try the version of 1.0.13,
it seem 's ok，but the breakpoint is not effective。

[email protected] can work

Kladdkaka · 2018-12-28T12:26:00Z

Hi, also got this issue.

I'm on Windows 10, with node v11.6.0, and [email protected].

Any way I could help out?

EDIT: [email protected] seems to work, 1.0.27 & 1.0.28 just gives me a blank window

fdeitelhoff · 2019-01-06T17:50:58Z

I've the same problem.

[email protected] is working except the breakpoints have no effect at all.

pfftdammitchris · 2019-01-15T03:29:24Z

Reverting to [email protected] works

ankur123 · 2019-01-18T15:50:53Z

m seeing the same issue

avarshney@avarshneypc MINGW64 ~/Desktop/IR2.0/gitHub/nrf-herder (feat/saved-search)
$ ndb -v
v1.0.42

avarshney@avarshneypc MINGW64 ~/Desktop/IR2.0/gitHub/nrf-herder (feat/saved-search)
$ node -v
v10.15.0

EDIT [email protected] works for me as well

Mehuge · 2019-04-15T16:35:09Z

ndb 1.0.44
chrome 73.0.3683.103
node v10.11.0
Error [ERR_IPC_CHANNEL_CLOSED]: Channel closed

ndb 1.0.26 works, including breakpoints

TimWillis · 2019-04-15T16:45:36Z

I noticed that any kind of error, and I think warning would cause ndb to crash. I would run normally with 'node your_server.js' to be able to see the errors/warnings, fix any errors or warnings, then run with ndb.

…

On Mon, Apr 15, 2019 at 12:35 PM Mehuge ***@***.***> wrote: ndb 1.0.44 chrome 73.0.3683.103 node v10.11.0 Error [ERR_IPC_CHANNEL_CLOSED]: Channel closed ndb 1.0.26 works, including breakpoints — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#204 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AIEUTQcNwqm-_6FoRcK5M862ouQA5YLdks5vhKpHgaJpZM4Y87HJ> .

alexnwalters · 2019-05-25T20:15:44Z

node v10.15.3
ndb v1.0.44
chrome 74.0.3729.169

I'm installing ndb for the first time and having the same issue, any suggestions on a fix?

muzhaqi16 · 2019-06-08T16:58:09Z

I have the same issue. it was working fine with node v10.16.0 and then I removed it and installed 12.4.0 and now after I open it and try to run a script it crashes. I removed it and installed it a couple of times but that didn't work.

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

Error [ERR_IPC_CHANNEL_CLOSED]: Channel closed
    at ChildProcess.target.send (internal/child_process.js:678:16)
    at Rpc.routeMessage_ (C:\Users\artan\AppData\Roaming\npm\node_modules\ndb\node_modules\carlo\rpc\rpc.js:379:9)
    at C:\Users\artan\AppData\Roaming\npm\node_modules\ndb\node_modules\carlo\lib\carlo.js:388:71
    at Page._onBindingCalled (C:\Users\artan\AppData\Roaming\npm\node_modules\ndb\node_modules\puppeteer-core\lib\Page.js:548:56)
    at CDPSession.<anonymous> (C:\Users\artan\AppData\Roaming\npm\node_modules\ndb\node_modules\puppeteer-core\lib\Page.js:136:54)
    at CDPSession.emit (events.js:200:13)
    at CDPSession._onMessage (C:\Users\artan\AppData\Roaming\npm\node_modules\ndb\node_modules\puppeteer-core\lib\Connection.js:200:12)
    at Connection._onMessage (C:\Users\artan\AppData\Roaming\npm\node_modules\ndb\node_modules\puppeteer-core\lib\Connection.js:112:17)
    at PipeTransport._dispatch (C:\Users\artan\AppData\Roaming\npm\node_modules\ndb\node_modules\puppeteer-core\lib\PipeTransport.js:59:22)      
    at Socket.<anonymous> (C:\Users\artan\AppData\Roaming\npm\node_modules\ndb\node_modules\puppeteer-core\lib\PipeTransport.js:30:64)
Emitted 'error' event at:
    at internal/child_process.js:682:35
    at processTicksAndRejections (internal/process/task_queues.js:82:9)

alexnwalters · 2019-06-08T17:35:41Z

not an ideal fix but as someone noted above rolling ndb back seems to work, I went back to ndb v1.0.26 and it has been working with node v10.15.3

alexkozy · 2019-06-20T05:49:38Z

One of the possible reasons of this crash was a broken native terminal dependency. I updated it in [email protected] and it should at least not to crash.
Another possible reason is reusing installed Chrome by carlo. I am going to force carlo to download latest Chromium to address this problem. I will release version with this fix soon (#260).

alexkozy · 2019-06-22T01:47:01Z

Could someone with reproducible issue check out [email protected]? Most problems related to ndb crashes should be fixed there.
This build includes nice way to profile your app as well, just add --prof right after ndb, e.g. ndb --prof index.js.

davidlehn · 2019-06-26T17:52:50Z

Since the ECONNRESET issues point here, I'll add another datapoint that I just updated and get ECONNRESET with 1.0.48+. 1.0.47 works ok. Is there any particular debug info that would help?

alexkozy · 2019-06-26T18:18:38Z

@davidlehn could you try to clean install ndb? npm uninstall -g ndb && npm install -g ndb.
The biggest change after 1.0.47 is that ndb fetches chromium by itself and do not reuse installed Chrome. I can assume that something went wrong when ndb was fetching Chromium.

What OS do you use?

Another useful information can be get by following steps:

mkdir test && cd test
npm init -y && npm install ndb - it creates new node package and install ndb locally,
try to run ./node_modules/.bin/ndb
if it does not work try to start fetched by ndb Chromium, you can find it inside ./node_modules/carlo/lib/.local-data/linux-624492/, on linux you need to run ./chrome-linux/chrome from this folder. Does it start?

ForsakenHarmony · 2019-07-07T01:40:30Z

I'm on 1.0.48 (node 12.6.0) and it's still the same error.

First time you try to launch a script nothing happens, when you click again
Error [ERR_IPC_CHANNEL_CLOSED]: Channel closed

ZeldOcarina · 2019-07-07T21:07:28Z

I'm having the same error as well, any updates on this?

alexkozy · 2019-07-08T18:24:28Z

@ZeldOcarina could you check [email protected]? (I do not have access to windows machine right now - I will check it this evening).

Thank you for your help! It is critical with platform specific bugs like these.

ZeldOcarina · 2019-07-08T18:50:41Z

I've taken my time to test it in different ways, with both global and local installs.
Now the debugger is not crashing but it's still not stopping on errors as you can see in the screenshot.

alexkozy · 2019-07-08T19:15:57Z

Thanks, @ZeldOcarina. Does debugger statement work? I have some idea why breakpoints can be broken on windows, I will debug it this evening. I definitely need to get windows machine and test ndb much better there.

ZeldOcarina · 2019-07-08T19:43:01Z

@ak239 Yes Aleksey with debugger keyword in place the code actually stops. It's only the manual green flags that aren't working!

alexkozy · 2019-07-09T02:41:40Z

@ZeldOcarina what node version do you use?

I built some similar with your's script and set couple breakpoints there. All of them works as expected. At the same time if you would like to trigger pause on error or exception you can activate pause on exception DevTools feature. If you'd like to restart your app - you can use Ctrl + R. If you'd like to kill current process without restarting you can hover it in Node processes section and click Kill button.

You snippet contains a little mistake - it does not require url module but uses url.parse - I am not sure is it expected in the test or not.

ZeldOcarina · 2019-07-09T20:55:47Z

Thanks @ak239. I've corrected the bug in the code. The breakpoints set with the green flag are not working for me but it's fine, I can use "debuger" keyword to handle this.

Thanks for the tips on Ctrl + R and killing the current process.

Now the program is functional and that is what matters the most!

hritique · 2019-07-10T11:51:05Z

Hi, @ak239 I am using [email protected] and [email protected] .
I am getting the same issue, the breakpoints are not working but the debugger keyword is working but it is not that handy in some cases.

alexkozy · 2019-07-10T14:17:29Z

@hritique thank you. I believe that I detected problem with breakpoints. It is all about spaces in paths on Windows, DevTools frontend does not replace space with %20 properly. I will fix it.

hritique · 2019-07-10T14:49:04Z

Thanks @ak239 , I hope it will get fixed.

Starting with v10, Node uses file urls in inspector protocol. Breakpoints work iff file path reported using file url. Otherwise provisional breakpoint will use path with spaces, instead of %20. Bug: #204

alexkozy · 2019-07-10T17:17:24Z

@hritique please try 1.1.2, it should contain breakpoints fix.

ZeldOcarina · 2019-07-10T17:30:22Z

@ak239 Great this works for me now!
I don't understand anyways why all files seem to be empty:

It also added a weird "r" directory after the "starter" folder, which is not present in the real file tree.

alexkozy · 2019-07-10T18:20:39Z

This one needs better fix, once and for everything. I will work on it this week. For now I reverted fix from 1.1.2 and publish 1.1.3 without it.
Thanks for your feedback @ZeldOcarina , I think we are close to make windows users happy!

ZeldOcarina · 2019-07-10T18:51:06Z

Thanks @ak239 I'm starting to realize why Windows isn't that popular amongst developers!

FileSystem works only with file urls. All breakpoints are set by path and by url. Frontend gets only file urls from ndb backend and passes only file urls to backend. There is only one exception - 'Run this script' frontend action convert script file url to path on frontend side. Over the protocol any url is always returned as file urls (frontend patches messages from Node 8). Debugger.setBreakpointByUrl replaces url with regex pattern: path|url to work with Node 8 and later Nodes. #204

darcyparker · 2019-08-20T14:08:23Z

I had same problem on Debian, and found I had to run:

 sudo sysctl -w kernel.unprivileged_userns_clone=1

https://github.com/GoogleChrome/puppeteer/blob/ff6d2a33f3edb8837bde3ab687c6d06510b5d4de/docs/troubleshooting.md#setting-up-chrome-linux-sandbox

In my case it is for a dev machine, so I am not too worried about changing this option.

ishaantaylor · 2019-10-17T18:49:42Z

I'm also having this issue. It fails in the same way after a few seconds. I've been using ndb with this project for a while and have never seen this issue. Could be our project just grew past some limit?

Environment:

ndb version: 1.1.5
Platform / OS version: macOS 10.14.5
Node.js version: 10.16.0

Problem:

➜  ndb
/Users/ishaantaylor/.nvm/versions/node/v10.16.0/lib/node_modules/ndb/lib/process_utility.js:14
    throw error;
    ^

Error: Error: CharacterIdMap ran out of capacity!
Error: CharacterIdMap ran out of capacity!
    at Common.CharacterIdMap.toChar (https://domain/ndb.js:1:141718)
    at https://domain/ndb.js:3:160732
    at Array.map (<anonymous>)
    at Persistence.PathEncoder.encode (https://domain/ndb.js:3:160711)
    at Persistence.Automapping.FilePathIndex.addPath (https://domain/ndb.js:3:142687)
    at Persistence.Automapping._onUISourceCodeAdded (https://domain/ndb.js:3:137592)
    at https://domain/ndb.js:3:135752
    at Workspace.Workspace.dispatchEventToListeners (https://domain/ndb.js:1:91157)
    at Persistence.FileSystemWorkspaceBinding.FileSystem.addUISourceCode (https://domain/ndb.js:1:658133)
    at Persistence.FileSystemWorkspaceBinding.FileSystem._fileChanged (https://domain/ndb.js:3:134868)
    at Rpc.dispatchMessageLocally_ (/Users/ishaantaylor/.nvm/versions/node/v10.16.0/lib/node_modules/ndb/node_modules/carlo/rpc/rpc.js:423:16)
    at Rpc.routeMessage_ (/Users/ishaantaylor/.nvm/versions/node/v10.16.0/lib/node_modules/ndb/node_modules/carlo/rpc/rpc.js:371:12)
    at process.emit (events.js:198:13)
    at emit (internal/child_process.js:832:12)
    at process._tickCallback (internal/process/next_tick.js:63:19)
events.js:174
      throw er; // Unhandled 'error' event
      ^

Error [ERR_IPC_CHANNEL_CLOSED]: Channel closed
    at ChildProcess.target.send (internal/child_process.js:636:16)
    at Rpc.routeMessage_ (/Users/ishaantaylor/.nvm/versions/node/v10.16.0/lib/node_modules/ndb/node_modules/carlo/rpc/rpc.js:379:9)
    at page_.exposeFunction.data (/Users/ishaantaylor/.nvm/versions/node/v10.16.0/lib/node_modules/ndb/node_modules/carlo/lib/carlo.js:388:71)
    at Page._onBindingCalled (/Users/ishaantaylor/.nvm/versions/node/v10.16.0/lib/node_modules/ndb/node_modules/puppeteer-core/lib/Page.js:548:56)
    at CDPSession.Page.client.on.event (/Users/ishaantaylor/.nvm/versions/node/v10.16.0/lib/node_modules/ndb/node_modules/puppeteer-core/lib/Page.js:136:54)
    at CDPSession.emit (events.js:198:13)
    at CDPSession._onMessage (/Users/ishaantaylor/.nvm/versions/node/v10.16.0/lib/node_modules/ndb/node_modules/puppeteer-core/lib/Connection.js:200:12)
    at Connection._onMessage (/Users/ishaantaylor/.nvm/versions/node/v10.16.0/lib/node_modules/ndb/node_modules/puppeteer-core/lib/Connection.js:112:17)
    at PipeTransport._dispatch (/Users/ishaantaylor/.nvm/versions/node/v10.16.0/lib/node_modules/ndb/node_modules/puppeteer-core/lib/PipeTransport.js:59:22)
    at Socket.PipeTransport._eventListeners.helper.addEventListener.buffer (/Users/ishaantaylor/.nvm/versions/node/v10.16.0/lib/node_modules/ndb/node_modules/puppeteer-core/lib/PipeTransport.js:30:64)
Emitted 'error' event at:
    at process.nextTick (internal/child_process.js:640:35)
    at process._tickCallback (internal/process/next_tick.js:61:11)

penkong · 2020-06-01T05:05:27Z

i had same problem with npm (os fedora 32 workstation)
solution worked for me : delete node_modules and related stuff.
use yarn to re install, and run ndb with yarn.

maddie-j · 2020-07-01T00:46:45Z

I think #290 is the same as this. I'm having this issue on MacOS and ndb v1.1.5 as well. I put some of my pokings in the other thread.

shapkarin · 2021-02-17T21:45:00Z

Does anyone solve that?

Mehuge · 2021-02-18T13:14:54Z

Does anyone solve that?

Both ndb 1.1.4 and 1.1.5 work for me on macOS Catalina

shapkarin · 2021-02-18T14:52:27Z

@Mehuge I have v1.1.5 but looks like this current issue is not related to ndb itself. But I hope to get some info from people that solved it somehow.

att14 · 2021-04-23T05:32:20Z

I am getting a similar issue after upgrading to macOS Big Sur from macOS Catalina. No problems on Catalina. I'm running ndb v1.1.5, node v14.16.0, macOS v11.2.3, and Chromium 73.0.3679.0.

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

Error: write EPIPE
    at WriteWrap.onWriteComplete [as oncomplete] (internal/stream_base_commons.js:94:16)
Emitted 'error' event on Socket instance at:
    at emitErrorNT (internal/streams/destroy.js:106:8)
    at emitErrorCloseNT (internal/streams/destroy.js:74:3)
    at processTicksAndRejections (internal/process/task_queues.js:80:21) {
  errno: -32,
  code: 'EPIPE',
  syscall: 'write'
}

liuliangsir · 2021-07-02T05:57:29Z

@att14 try this solution.

alexkozy closed this as completed Dec 2, 2018

alexkozy reopened this Dec 3, 2018

alexkozy added the bug Something isn't working label Jun 20, 2019

alexkozy mentioned this issue Jun 22, 2019

Error: read ECONNRESET #248

Closed

alexkozy mentioned this issue Jul 10, 2019

fix(backend): report file urls for file system #286

Merged

alexkozy mentioned this issue Jul 16, 2019

fix(frontend): frontend uses file urls instead of paths #291

Merged

ndb crashes after launching script #204

ndb crashes after launching script #204

Comments

vaxerski commented Dec 1, 2018 • edited

alexkozy commented Dec 2, 2018

alexkozy commented Dec 2, 2018

vaxerski commented Dec 3, 2018

alexkozy commented Dec 3, 2018

vaxerski commented Dec 3, 2018

vaxerski commented Dec 4, 2018

vaxerski commented Dec 5, 2018

alexkozy commented Dec 5, 2018

linqFR commented Dec 6, 2018

vaxerski commented Dec 8, 2018 • edited

Yuan-Zi-Yuan commented Dec 28, 2018

Kladdkaka commented Dec 28, 2018 • edited

fdeitelhoff commented Jan 6, 2019

pfftdammitchris commented Jan 15, 2019

ankur123 commented Jan 18, 2019 • edited

Mehuge commented Apr 15, 2019

TimWillis commented Apr 15, 2019 via email

alexnwalters commented May 25, 2019

muzhaqi16 commented Jun 8, 2019

alexnwalters commented Jun 8, 2019

alexkozy commented Jun 20, 2019

alexkozy commented Jun 22, 2019

davidlehn commented Jun 26, 2019

alexkozy commented Jun 26, 2019

ForsakenHarmony commented Jul 7, 2019 • edited

ZeldOcarina commented Jul 7, 2019

alexkozy commented Jul 8, 2019

ZeldOcarina commented Jul 8, 2019

alexkozy commented Jul 8, 2019

ZeldOcarina commented Jul 8, 2019

alexkozy commented Jul 9, 2019

ZeldOcarina commented Jul 9, 2019

hritique commented Jul 10, 2019 • edited

alexkozy commented Jul 10, 2019

hritique commented Jul 10, 2019

alexkozy commented Jul 10, 2019

ZeldOcarina commented Jul 10, 2019

alexkozy commented Jul 10, 2019

ZeldOcarina commented Jul 10, 2019

darcyparker commented Aug 20, 2019

ishaantaylor commented Oct 17, 2019

penkong commented Jun 1, 2020

maddie-j commented Jul 1, 2020

shapkarin commented Feb 17, 2021

Mehuge commented Feb 18, 2021

shapkarin commented Feb 18, 2021

att14 commented Apr 23, 2021 • edited

liuliangsir commented Jul 2, 2021

vaxerski commented Dec 1, 2018 •

edited

vaxerski commented Dec 8, 2018 •

edited

Kladdkaka commented Dec 28, 2018 •

edited

ankur123 commented Jan 18, 2019 •

edited

ForsakenHarmony commented Jul 7, 2019 •

edited

hritique commented Jul 10, 2019 •

edited

att14 commented Apr 23, 2021 •

edited