Upgrade to electron 5.0.12

[darangi]

This upgrades atom from 4.2.7 to 5.0.12, this helps prevent the crash happening on Mac OS 10.15 (Catalina)

TODO

• Update CI config to use node v12.13.1 and npm v6.12.1
• Get CI passing
• Run through Atom's Electron upgrade test manifest (below) to identify any regressions

ISSUES TO RESOLVE

• Bump leveldown@4.0.0 to leveldown@5.4.1 in electron-link to fix build error
• publish a new version for electron-link@0.4.1 https://github.com/atom/electron-link
• Bump oniguruma@6.2.1 to oniguruma@7.2.1 in apm to fix build error
• publish a new version for apm@2.4.4 version https://github.com/atom/apm
• Fix git-utils build error Fix compilation errors on node 12 git-utils#98
  • publish a new version for git-utils@5.6.2 https://github.com/atom/git-utils
  • Bump git-utils@5.6.1 to git-utils@5.6.2 in atom/atom and apm to fix build error
• Fix fuzzy-native build error Fix compilation errors on node 12 fuzzy-native#8 thrown from fuzzy-finder https://github.com/atom/fuzzy-finder
  • publish a new version for fuzzy-native@1.1.2 https://github.com/atom/fuzzy-native/releases/tag/v1.1.2
  • Bump fuzzy-native@1.1.1 to fuzzy-native@1.1.2 in fuzzy-finder to fix build error ⬆️@atom/fuzzy-native@1.1.2 fuzzy-finder#409
  • publish a new version for fuzzy-finder@1.14.2 https://github.com/atom/fuzzy-finder/releases/tag/v1.14.2
  • Bump fuzzy-finder@1.14.1 to fuzzy-finder@1.14.2 in atom/atom to fix build error
• Bump fs-admin@0.5.0 to fs-admin 0.12.0 to fix build error
• Fix compilation errors thrown from text-buffer Fix Node 12 compilation error text-buffer#317
• Resolve Fails to compile on node 12 node-ctags#16, (Fixes node 12 compilation errors node-ctags#17)
• Resolve Fails to compile on node 12 tree-sitter/tree-sitter-c#35
• Resolve Fails to compile on node 12 tree-sitter/tree-sitter-css#10
  • Bump tree-sitter-css@0.13.7 to tree-sitter-css@0.13.8 in language-css to fix build error
  • Publish a new version of language-css https://github.com/atom/language-css/releases/tag/v0.44.4
• Resolve Fails to compile on node 12 tree-sitter/tree-sitter-embedded-template#3 (Fixes node 12 compilation error tree-sitter/tree-sitter-embedded-template#4)
  • Bump tree-sitter-embedded-template@0.15.0 to tree-sitter-embedded-template@0.15.2 in language-html to fix build error
  • Publish a new version for language-html@0.53.1 https://github.com/atom/language-html/releases/tag/v0.53.1
• Bump tree-sitter-go@0.15.0 to tree-sitter-go@0.15.1 in language-go to fix build error
  • Publish a new version for language-go@0.47.1 https://github.com/atom/language-go/releases/tag/v0.47.2
• Publish new patch for tree-sitter-javascript@0.15.2 https://github.com/tree-sitter/tree-sitter-javascript/releases/tag/v0.15.2
  • Bump tree-sitter-javascript@0.15.0 to tree-sitter-javascript@0.15.2 in language-javascript to fix build error.
  • Publish a new version for language-javascript@0.133.2 https://github.com/atom/language-javascript/releases/tag/v0.134.1
• Bump tree-sitter-json@0.14.0 to tree-sitter-json@0.15.1 in language-json to fix build error
  • Publish a new version for language-json@1.0.5 https://github.com/atom/language-json/releases/tag/v1.0.5
• Bump tree-sitter-python@0.15.0 to tree-sitter-json@0.15.1 in language-python to fix build error
  • Publish a new version for language-python@0.53.4 https://github.com/atom/language-python/releases/tag/v0.53.4
• Publish new patch for tree-sitter-typescript@0.15.2 https://github.com/tree-sitter/tree-sitter-typescript/releases/tag/v0.15.2
  • Bump tree-sitter-typescript@0.15.1 to tree-sitter-typescript@0.15.2 in language-typescript to fix build error.
  • Publish a new version for language-typescript@0.6.1 https://github.com/atom/language-typescript/releases/tag/v0.6.1
• Bump language-java@0.31.3 to language-java@0.13.4 in atom/atom
• Bump tree-sitter-rust@0.15.1 to tree-sitter-rust@0.15.1 in language-rust-bundled to fix build errors
• Fix errors thrown from github package
  • Resolve Fails to compile on node 12 whats-my-line#6
  • Bump whats-my-line@0.1.1 to whats-my-line@0.1.2 in github
• Resolve Unable to transform source code for module  #20236
• Resolve chrome-sandbox bug on linux chrome-sandbox permission error  #20289 (18da630)
• Resolve Tests not running on CI #20306 (4715435)
• Resolve Tests timing out on CI Tests time out on CI #20290 (1bc0650)
• Resolve Failed to load a language-rust-bundled package grammar Failed to load a language-rust-bundled package grammar #20354 (67d61c0)
• Resolve Failed to load a language-shellscript package grammar Failed to load a language-shellscript package grammar #20353 (2a9c63d)
• Resolve Failed to load a language-typescript package grammar Failed to load a language-typescript package grammar #20355 (081dd60)

FAILING TESTS

• TreeSitterLanguageMode Failing test in TreeSitterLanguageMode #20371
• Failing tests in Reporter package Failing tests in Reporter package #20399
• Failing tests in snippet package Failing test in snippet package #20386
• Failing tests in find and replace package Failing tests in Find and replace package #20376
• GIthub package tests exits on CI Github package tests exits on CI #20411

Regressions to fix before merging

Known bugs resolved by this upgrade

Fixes #20034

Electron Upgrade Test Manifest

• Review issues tagged with electron to see if any of them are fixed

• Verify that you can collaborate with Teletype

  • Host using Atom's current stable release can collaborate with guest using Atom with the new version of Electron
  • Guest using Atom's current stable release can collaborate with host using Atom with the new version of Electron
  • Host and guest can collaborate when both are using Atom with the new version of Electron
  Steps

  1. Open a file
  2. Share a portal
  3. Have a guest join the portal
  4. When guest edits the text in the file, verify that the host sees those changes

Check for regressions experienced in previous upgrades

Text Input/Keybindings

See how to setup keyboard layouts.

• IME not working (1.19.0-beta2: Cursor stucks at the first letter when using macOS Chinese IME #14911)

  • macOS
  • Windows 10
  • Ubuntu
  Repro steps

  1. Install an IME layout, for example Pinyin simplified
  2. Open Atom and use the layout you installed as the keyboard layout
  3. Example, if you picked Pinyin simplified type in zhongwenshuru

  Expected: in Pinyin simplified 中文输入 is expected

  

  Issues we've seen: Only shows latin first character and not every character typed.

  

• macOS: Key binding with composition characters are ignored (key-mappings with alt don't suppress Mac OS composition characters anymore (atom-1.19) #15189)

  Repro steps

  1. Open your keymap.cson file and add the following:

     'atom-text-editor':
       # use hjkl; vim-like when pressing alt (word by word, paragraph by paragraph)
       # or alt (letter by letter)
       'alt-h': 'core:move-left'
       'alt-j': 'core:move-down'
       'alt-k': 'core:move-up'
       'alt-l': 'core:move-right'

  2. Save keymap.cson and reload atom.
  3. Try the new keymappings under ABC - Extended keyboard layout

  Expected: the keybindings work

  Issues we've seen: it types out the modified keys and ignores the key mapping

• macOS: Composition characters mess up insertion point (Composition characters mess up insertion point #15344)

  Repro steps

  1. Open keymap.cson and add the following:

     'atom-text-editor':
       'alt-n': 'core:move-down'
       'alt-o': 'core:move-down'

  2. Have the following in your buffer:

     Foo
     Bar
     

  3. Have the cursor at the beginning of file(before F character) Type alt-n, then arrow right, then insert a character. Observe that the character is inserted at the beginning of the line (where the alt-n left you).
  4. Repeat steps using alt-o instead of alt-n.

  Expected: Both alt-o and alt-n behave the same

  Issues we've seen:
  

• Ubuntu: Keystrokes involving ctrl resolve to the default layout instead of the active layout (Keystrokes involving ctrl on Linux resolve to the default layout instead of the active layout #13170)

  Repro steps

  This should be tested on Linux with gnome

  1. Install a Linux ditro with gnome, for example Ubuntu
  2. Install French AZERTY and English US QWERTY layouts
  3. Change the default layout to be French AZERTY
  4. Open Atom and switch to English US QWERTY layout
  5. Press ctrl-w

  Expected: core:close to dispatch (Or the keybinding-resolver to resolve to ctrl-w). Should be resolving to the keyboard layout that is chosen and not the OS default layout.

  Issues we've seen: core:undo dispatched because it was resolved as ctrl-z because AZERTY has Z where W is on QWERTY.

• Other keyboard layouts on new Electron version

  • macOS: ABC - Extended
  • macOS: Slovak
  • macOS: U.S. International
  • macOS: Squirrel (https://github.com/rime/squirrel)
  • macOS: Full-Width Alphanumeric (Google) - Japanese layout (https://www.google.co.jp/ime/)
  • Windows: U.S.
  • Linux: Pinyin Simplified

UI

• tree-view drag image (Display the correct drag image on Electron >= 1.14 tree-view#1054)

  • macOS
  • Windows 10
  • Ubuntu
  Repro steps

  1. Open a project in Atom with multiple files and a few folders
  2. Drag a file into a folder

  Expected:
  

  Issues we've seen:

  

• drag-and-drop indicator (Fix missing drop indicator on Electron >= 1.14 tree-view#1055, Fix missing drop indicator on Electron >= 1.4 tabs#426, Fix mistakenly shown docks drop indicator on Electron >= 1.4 tabs#437)

  • macOS
  • Windows 10
  • Ubuntu
  Repro steps

  1. Open Atom with a few folder projects on tree-view (you can do this on terminal in a directory that has existing folder and having a space between each folder. Example: atom folderA folderB folderC)
  2. Drag and drop all of the folders to reorder them on Atom

  Expected:
  The placeholder indicates where the folder/project is being dropped to.

  

  Issues we've seen:
  No placeholder shows up after drag and dropping

  

• Large file rendering (Bad rendering after ~1 million lines #16591)

  • macOS
  • Windows 10
  • Ubuntu
  Repro steps

  1. Open a file that has over one million lines
  2. Scroll down to the bottom

  Expected: To not regress the number of lines that can be rendered. Rendering to be correct for lines past a certain point. Atom 1.25 can render around 800k to 1 million lines correctly.

  Issues we've seen: Increased number of lines rendered but bad rendering past a certain point

  

• Loss of subpixel AA when the cursor is at the end of long lines (Loss of subpixel AA on soft-wrapped line #16889, Don't break subpixel AA when cursor is at the end of longest line #16595)

  • macOS
  • Windows 10
  • Ubuntu
  Repro steps

  1. Open text-editor.js in Atom
  2. Copy the first 21 lines to a new untitled window
  3. Turn on soft wrapping and change language mode to javascript
  4. Resize the Window so it's soft wrapped
  5. On line 15 type a until the you reach the end of the window

  Expected: To not lose subpixel AA

  Issues we've seen: Loss of subpixel AA. Both when soft wrapping was enabled and disabled.

  

• Scrolling horizontally shift + scroll wheel (Upgrade Electron to v1.6.x #12696 (comment))

  • macOS
  • Windows 10
  • Ubuntu
  Repro steps

  1. Open a file that has long lines
  2. Turn off soft wrapping and resize the window so you have a horizontal scrollbar
  3. Press shift and scroll in both directions using the mouse wheel

  Expected: File to scroll horizontally in both directions

  Issues we've seen: File does not scroll horizontally at all in any direction

• Scrollbars misbehaving on the first file that is opened (Upgrade Electron to v1.6.x #12696 (comment))

  Repro steps

  1. Open Atom
  2. Open some file that has content enough to have a vertical scrollbar
  3. Close Atom
  4. Open Atom and look at the vertical scrollbar

  Expected: Scrollbar to be visible

  Issues we've seen: Scrollbar is not visible and is flickering when you are editing

• Middle clicking on unsaved tab (1.19, Linux: Middle-clicking an unsaved tab causes entire desktop to be unresponsive to clicks #15197)

  • macOS
  • Ubuntu
  Repro steps

  1. Open Atom and open a new unsaved file.
  2. Make edits to the unsaved file and middle click on the tab.

  Expected:
  Clicking save/cancel or the options on the dialog works.

  Issues we've seen:
  The UI and the dialog is unable to receive mouse clicks. You can still choose options via Keyboard, but not mouse.

• Linux: Atom scrolls even when not focused (Atom scrolls even when not focused #15482)

  Repro steps

  1. Open Atom with a large enough file that has a scrollbar
  2. Open a different application and place it over the Atom window
  3. Scroll with the mouse inside the other window
  4. Focus the Atom window

  Expected: Atom window should keep the original scroll position

  Issues we've seen: The Atom window scrolls after it is focused

Other

• Deprecation warnings (Upgrade Electron to v1.6.x #12696 (comment))

  • macOS
  • Windows 10
  • Ubuntu
  Repro steps

  This should be tested on macOS, Linux and Windows with community packages installed

  1. Open Atom
  2. Open the Developer tools console on the master branch and check for deprecation warnings
  3. Open the Developer tools console on the electron upgrade branch and check for deprecation warnings
  4. Compare the two outputs

  Expected: No new deprecation warnings

  Issues we've seen: New deprecation warnings both from core and community packages

• Supported Versions of OS (Atom 1.19.0 crashes instantly after launching #15297)

  • macOS
  • Windows 10
  • Ubuntu
  Repro steps

  1. Check the list of supported platforms Electron Master
  2. Check what version is listed as minimum for each platform on https://atom.io and https://atom.io/faq

  Expected: https://atom.io and https://atom.io/faq to display the same versions as the Electron documentation

  Issues we've seen: macOS version support changed and https://atom.io and https://atom.io/faq was not updated

• macOS : Native tabs (Native tabs on macOS #14711)

  Repro steps

  1. Open two atom windows on mac
  2. Go to View in menus and check Show Tab Bar
     
  3. Do this for both Atom windows.
  4. Drag one atom window to the other via tab bar

  Expected:
  Native Tab bar shows up and able to drag different windows to each other. Also make sure UI isn't messed up.

  Issues we've seen:
  Native Tab Bar doesn't work and messes up UI when enabled

• Ubuntu with KDE: Menu uses 100% CPU (Globalmenu consumes 100% CPU and does not work electron/electron#8455, Menus not working in plasma 5.9 with global menu enabled #13885)

  Repro steps

  1. Install Atom on Ubuntu KDE. [instructions]
  2. Enable KDE plasma global menu: Right-click on the desktop -> Add Panel => Application Menu Bar. [demo]
  3. Start Atom.
  4. Try to use the desktop menu.

  Expected:
  Desktop menu items work

  Issues we've seen:
  Desktop menu items do nothing when you click on things.

• macOS: Slovak QWERTZ (Slovak QWERTZ does not resolve keys correctly on macOS atom-keymap#223)

  Repro steps

  1. Install Slovak keyboard layout on mac
  2. Open keyboard viewer to see the keys are are suppose to show up and open keyboard resolver on atom.
  3. hit cmd+'.

  Expected: Resolves to cmd+' like it shows on keyboard viewer on mac.

  Issues we've seen: It resolves to ctrl+§

• macOS: IME jump (1.20.0: Popup jump when using macOS Chinese IME #15696)

  Repro steps

  1. Install an IME layout, for example Chinese pinyin
  2. Type one character

  Expected:
  Expected the IME to be positioned at under the character you entered
  Issues we've seen: The IME window is in the top left corner. When you enter the second character it jumps to be positioned under the text

[remagpie]

The most recent stable version of the electron is 7.1.2 now.
Is there any reason for picking the old version?

[darangi]

@remagpie, electron upgrades on atom are done one version at a time until the latest version is reached.

[remagpie]

You can simplify some of your commits such as e882b80 and 6c82230.
I think it'd be nice to polish patches a bit so that other people can track history easier.

[darangi]

You can simplify some of your commits such as e882b80 and 6c82230.
I think it'd be nice to polish patches a bit so that other people can track history easier.

Thanks for the recommendation 😃

[mfonville]

Congrats on your progress for the Electron-upgrade process. Is there any ETA for which release/milestone of Atom the electron-upgrade will be applied?

[aminya]

@darangi Thank you for upgrading. Is there any plan for continuing upgrading Electron to upper versions?
https://www.electronjs.org/blog

[darangi]

@darangi Thank you for upgrading. Is there any plan for continuing upgrading Electron to upper versions?
https://www.electronjs.org/blog

@aminya Thanks! Yes, we have plans in the future to do that 👍

[aminya]

@darangi Thank you for upgrading. Is there any plan for continuing upgrading Electron to upper versions?
electronjs.org/blog

@aminya Thanks! Yes, we have plans in the future to do that 👍

Awesome! That's a very good way to enhance the Atom's overall performance.

Would you please take a look at this? Maybe this is related to this PR
#20531