You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Platform: Linux lap 5.10.11-arch1-1 #1 SMP PREEMPT Wed, 27 Jan 2021 13:53:16 +0000 x86_64 GNU/Linux
Reproduced the bug on electron 10.3.1 and 11.2.1, with node 12.16.3 and 12.18.3 respectively
I'm running node 10.13.0 on my system using nvm but I don't think that affects the code running inside electron?
What steps will reproduce the bug?
The running of isFile() (from require('fs').promises) on this line. That project is not the simplest to build so I'm not expecting you to do that but some pointers for where I could look when debugging would be helpful. Will maybe produce a simpler reproduction in my debugging.
How often does it reproduce? Is there a required condition?
Every time
What is the expected behavior?
Not printing this error
What do you see instead?
In the electron console
main.js:12 TypeError: Cannot read property 'Symbol(type)' of undefined
at isFile (internal/fs/utils.js:104)
at main.js:60
at Array.filter (<anonymous>)
at e.f (main.js:60)
at u (main.js:1)
at e._n (main.js:1)
at e._n (main.js:1)
at main.js:1
Linux lap 5.10.11-arch1-1 #1 SMP PREEMPT Wed, 27 Jan 2021 13:53:16 +0000 x86_64 GNU/Linux
Reproduced the bug on electron 10.3.1 and 11.2.1, with node 12.16.3 and 12.18.3 respectively
I'm running node 10.13.0 on my system using nvm but I don't think that affects the code running inside electron?
What steps will reproduce the bug?
The running of isFile() (from require('fs').promises) on this line. That project is not the simplest to build so I'm not expecting you to do that but some pointers for where I could look when debugging would be helpful. Will maybe produce a simpler reproduction in my debugging.
How often does it reproduce? Is there a required condition?
Every time
What is the expected behavior?
Not printing this error
What do you see instead?
In the electron console
when clicking into internal/fs/utils.js:104
This issue looks a bit similar but not the same #24546 since they were having problems with http2, something I don't believe I'm using.
The text was updated successfully, but these errors were encountered: