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
Open Fuzzy Finder (if this does not trigger the exception, keep following steps)
Enable file-icons
Open Fuzzy Finder
Disable file-icons
Open Fuzzy Finder
Icons may or may not be present when the exception occurs.
Alternatively:
Disable file-icons
Enable file-icons
Disable file-icons
Open Fuzzy Finder
Fuzzy Finder should report that the project is empty with the uncaught exception notification in the background.
Atom: 1.25.0-dev-b7258bdc8 x64 Electron: 1.6.15 OS: Microsoft Windows 10 Home Insider Preview Thrown From: file-icons package 2.1.14
Stack Trace
Uncaught TypeError: Cannot read property 'on' of null
At C:\Users\user\.atom\packages\file-icons\lib\options.js:67
TypeError: Cannot read property 'on' of null
at Options.onDidChange (/packages/file-icons/lib/options.js:67:22)
at /packages/file-icons/lib/service/icon-node.js:28:12)
at Function.forElement (/packages/file-icons/lib/service/icon-node.js:177:17)
at /packages/file-icons/lib/service/icon-service.js:80:31)
at IconServices.updateIcon (~/AppData/Local/Atom x64/app-dev/resources/app/node_modules/fuzzy-finder/lib/get-icon-services.js:58:37)
at Object.elementForItem (~/AppData/Local/Atom x64/app-dev/resources/app/node_modules/fuzzy-finder/lib/fuzzy-finder-view.js:152:51)
at $.ol.items.map (~/AppData/Local/Atom x64/app-dev/resources/app/node_modules/atom-select-list/src/select-list-view.js:166:37)
at Array.map (native)
at SelectListView.renderItems (~/AppData/Local/Atom x64/app-dev/resources/app/node_modules/atom-select-list/src/select-list-view.js:165:29)
at SelectListView.render (~/AppData/Local/Atom x64/app-dev/resources/app/node_modules/atom-select-list/src/select-list-view.js:156:18)
at updateSync (~/AppData/Local/Atom x64/app-dev/resources/app/node_modules/atom-select-list/node_modules/etch/lib/component-helpers.js:99:40)
at ~/AppData/Local/Atom x64/app-dev/resources/app/node_modules/atom-select-list/node_modules/etch/lib/component-helpers.js:72:13
at DefaultScheduler.performUpdates (~/AppData/Local/Atom x64/app-dev/resources/app/node_modules/atom-select-list/node_modules/etch/lib/default-scheduler.js:48:40)
Additionally reproducible with find-and-replace and archive-view:
Disable file-icons
Enable file-icons
Disable file-icons
Perform a project search/open an archive
find-and-replace: Uncaught exception should be in console and no project find results should appear.
archive-view: Uncaught exception notification should appear and no archive view should be generated.
The fact that you need to disable file-icons twice for these issues to occur lead me to believe that there may be something wrong going on with package deactivation?
Just an FYI if you're unaware of my current situation: my MacBook died, and my only remaining computer is a dinosaur Dell running OpenBSD 6.2 (which is limited to an 80×25 display due to hardware/driver issues yet to be solved).
So I'm only able to use Atom from borrowed computers, and I've been unable to investigate this (or do most Atom-related stuff, for that matter).
Alhadis
added
the
bug
Confirmed defect in package logic, deprecation notices, and PRs which fix them.
label
Oct 15, 2018
Icons may or may not be present when the exception occurs.
Alternatively:
Fuzzy Finder should report that the project is empty with the uncaught exception notification in the background.
Atom: 1.25.0-dev-b7258bdc8 x64
Electron: 1.6.15
OS: Microsoft Windows 10 Home Insider Preview
Thrown From: file-icons package 2.1.14
Stack Trace
Uncaught TypeError: Cannot read property 'on' of null
Commands
Non-Core Packages
Related: #682
The text was updated successfully, but these errors were encountered: