After last Archlinux system upgrade - SIGSEGV

VSCode Version:
visual-studio-code-insiders-1533551722-1
visual-studio-code-insiders-1532668879
visual-studio-code-insiders-1531459376 - this version not SIGSEGV but just blink and turn off.

OS Version:
Linux lenovo-e450 4.17.12-arch1-1-ARCH #1 SMP PREEMPT Fri Aug 3 07:16:41 UTC 2018 x86_64 GNU/Linux

Steps to Reproduce:

run code-insiders

Does this issue occur when all extensions are disabled?: No

/usr/bin/code-insiders: line 35: 26692 Segmentation fault      (core dumped) ELECTRON_RUN_AS_NODE=1 "$ELECTRON" "$CLI" "$@"

I known this is primary a problem with nodejs - or something like that ... but I don't known what exactly it is... other Electron programs works fine. I test it with nodejs 10.8.0 and try downgrade to 10.7.0 and 10.6.0... but nothing helps...
EDIT:
And this is my packages update log (nothing extra like nodejs or other depends packages... :thinking: just new kernel etc... ):
[2018-08-07 08:36] [PACMAN] Running 'pacman -Syu'
[2018-08-07 08:36] [PACMAN] synchronizing package lists
[2018-08-07 08:37] [PACMAN] starting full system upgrade
[2018-08-07 08:38] [ALPM] transaction started
[2018-08-07 08:38] [ALPM] upgraded linux-api-headers (4.16.1-1 -> 4.17.11-1)
[2018-08-07 08:38] [ALPM] warning: /etc/locale.gen installed as /etc/locale.gen.pacnew
[2018-08-07 08:38] [ALPM] upgraded glibc (2.27-3 -> 2.28-1)
[2018-08-07 08:38] [ALPM-SCRIPTLET] Generating locales...
[2018-08-07 08:38] [ALPM-SCRIPTLET]   cs_CZ.UTF-8... done
[2018-08-07 08:38] [ALPM-SCRIPTLET]   en_GB.UTF-8... done
[2018-08-07 08:38] [ALPM-SCRIPTLET] Generation complete.
[2018-08-07 08:38] [ALPM] upgraded gcc-libs (8.1.1+20180531-1 -> 8.2.0-2)
[2018-08-07 08:38] [ALPM] upgraded libutil-linux (2.32.1-1 -> 2.32.1-2)
[2018-08-07 08:38] [ALPM] upgraded avahi (0.7+16+g1cc2b8e-1 -> 0.7+16+g1cc2b8e-2)
[2018-08-07 08:38] [ALPM] upgraded libxml2 (2.9.8-2 -> 2.9.8-3)
[2018-08-07 08:38] [ALPM] upgraded perl (5.26.2-2 -> 5.28.0-1)
[2018-08-07 08:38] [ALPM] upgraded libldap (2.4.46-1 -> 2.4.46-2)
[2018-08-07 08:38] [ALPM] upgraded bind-tools (9.13.0-2 -> 9.13.0-3)
[2018-08-07 08:38] [ALPM] upgraded binutils (2.30-5 -> 2.31.1-1)
[2018-08-07 08:38] [ALPM] upgraded python (3.6.6-1 -> 3.7.0-3)
[2018-08-07 08:38] [ALPM] upgraded xcb-proto (1.13-1 -> 1.13-2)
[2018-08-07 08:38] [ALPM] upgraded python-cairo (1.17.0-1 -> 1.17.0-2)
[2018-08-07 08:38] [ALPM] upgraded python-dbus-common (1.2.8-1 -> 1.2.8-2)
[2018-08-07 08:38] [ALPM] upgraded python-dbus (1.2.8-1 -> 1.2.8-2)
[2018-08-07 08:38] [ALPM] upgraded pygobject-devel (3.28.3-1 -> 3.28.3-2)
[2018-08-07 08:38] [ALPM] upgraded python-gobject (3.28.3-1 -> 3.28.3-2)
[2018-08-07 08:38] [ALPM] upgraded libtool (2.4.6+40+g6ca5e224-7 -> 2.4.6+42+gb88cebd5-1)
[2018-08-07 08:38] [ALPM] upgraded device-mapper (2.02.180-1 -> 2.02.181-1)
[2018-08-07 08:38] [ALPM] upgraded cryptsetup (2.0.3-2 -> 2.0.4-1)
[2018-08-07 08:38] [ALPM] upgraded util-linux (2.32.1-1 -> 2.32.1-2)
[2018-08-07 08:38] [ALPM] upgraded llvm-libs (6.0.1-1 -> 6.0.1-2)
[2018-08-07 08:38] [ALPM] upgraded libproxy (0.4.15-6 -> 0.4.15-8)
[2018-08-07 08:38] [ALPM] upgraded blueman (2.0.5-2 -> 2.0.5-3)
[2018-08-07 08:38] [ALPM] upgraded boost-libs (1.67.0-5 -> 1.67.0-6)
[2018-08-07 08:38] [ALPM] upgraded boost (1.67.0-5 -> 1.67.0-6)
[2018-08-07 08:38] [ALPM] upgraded brotli (1.0.5-1 -> 1.0.5-2)
[2018-08-07 08:38] [ALPM] upgraded btrfs-progs (4.17-1 -> 4.17-2)
[2018-08-07 08:39] [ALPM] upgraded gcc (8.1.1+20180531-1 -> 8.2.0-2)
[2018-08-07 08:39] [ALPM] upgraded libplist (2.0.0+11+gec9ba8b-1 -> 2.0.0+11+gec9ba8b-2)
[2018-08-07 08:39] [ALPM] upgraded libimobiledevice (1.2.0+66+g5a85432-1 -> 1.2.0+66+g5a85432-2)
[2018-08-07 08:39] [ALPM] upgraded libibus (1.5.18-1 -> 1.5.18-2)
[2018-08-07 08:39] [ALPM] upgraded libvoikko (4.1.1-1 -> 4.1.1-2)
[2018-08-07 08:39] [ALPM] upgraded mutter (3.28.3-2 -> 3.28.3+8+gd0d807801-1)
[2018-08-07 08:39] [ALPM] upgraded gnome-shell (3.28.3-1 -> 3.28.3+7+g721ce5403-1)
[2018-08-07 08:39] [ALPM] upgraded gpgme (1.11.1-1 -> 1.11.1-2)
[2018-08-07 08:39] [ALPM] upgraded net-snmp (5.7.3-8 -> 5.7.3-9)
[2018-08-07 08:39] [ALPM] upgraded perl-clone (0.39-4 -> 0.39-5)
[2018-08-07 08:39] [ALPM] upgraded perl-dbi (1.641-1 -> 1.641-2)
[2018-08-07 08:39] [ALPM] upgraded perl-xml-libxml (2.0132-1 -> 2.0132-2)
[2018-08-07 08:39] [ALPM] upgraded libmagick (<IP_ADDRESS>-1 -> <IP_ADDRESS>-2)
[2018-08-07 08:39] [ALPM] upgraded imagemagick (<IP_ADDRESS>-1 -> <IP_ADDRESS>-2)
[2018-08-07 08:39] [ALPM] upgraded liblouis (3.6.0-1 -> 3.6.0-2)
[2018-08-07 08:39] [ALPM] upgraded hplip (3.18.6-1 -> 3.18.7-1)
[2018-08-07 08:39] [ALPM] upgraded kcoreaddons (5.48.0-2 -> 5.48.0-3)
[2018-08-07 08:39] [ALPM] upgraded kauth (5.48.0-2 -> 5.48.0-3)
[2018-08-07 08:39] [ALPM] upgraded kcodecs (5.48.0-2 -> 5.48.0-3)
[2018-08-07 08:39] [ALPM] upgraded kwidgetsaddons (5.48.0-2 -> 5.48.0-3)
[2018-08-07 08:39] [ALPM] upgraded kconfig (5.48.0-2 -> 5.48.0-3)
[2018-08-07 08:39] [ALPM] upgraded kcompletion (5.48.0-2 -> 5.48.0-3)
[2018-08-07 08:39] [ALPM] upgraded kguiaddons (5.48.0-2 -> 5.48.0-3)
[2018-08-07 08:39] [ALPM] upgraded ki18n (5.48.1-2 -> 5.48.1-3)
[2018-08-07 08:39] [ALPM] upgraded kconfigwidgets (5.48.0-2 -> 5.48.0-3)
[2018-08-07 08:39] [ALPM] upgraded kdbusaddons (5.48.0-2 -> 5.48.0-3)
[2018-08-07 08:39] [ALPM] upgraded kitemmodels (5.48.0-2 -> 5.48.0-3)
[2018-08-07 08:39] [ALPM] upgraded kitemviews (5.48.0-2 -> 5.48.0-3)
[2018-08-07 08:39] [ALPM] upgraded kjobwidgets (5.48.0-2 -> 5.48.0-3)
[2018-08-07 08:39] [ALPM] upgraded lensfun (0.3.2-6 -> 0.3.2-7)
[2018-08-07 08:39] [ALPM] upgraded libbytesize (1.3-1 -> 1.3-2)
[2018-08-07 08:39] [ALPM] upgraded lvm2 (2.02.180-1 -> 2.02.181-1)
[2018-08-07 08:39] [ALPM] upgraded volume_key (0.3.10-1 -> 0.3.11-2)
[2018-08-07 08:39] [ALPM] upgraded libblockdev (2.18-1 -> 2.18-2)
[2018-08-07 08:39] [ALPM] upgraded libftdi (1.4-1 -> 1.4-2)
[2018-08-07 08:39] [ALPM] upgraded libgexiv2 (0.10.8-1 -> 0.10.8-2)
[2018-08-07 08:39] [ALPM] upgraded libixion (0.13.0-2 -> 0.13.0-3)
[2018-08-07 08:39] [ALPM] upgraded libmagick6 (<IP_ADDRESS>-1 -> <IP_ADDRESS>-2)
[2018-08-07 08:39] [ALPM] upgraded libnewt (0.52.20-1 -> 0.52.20-2)
[2018-08-07 08:39] [ALPM] upgraded liborcus (0.13.4-2 -> 0.13.4-3)
[2018-08-07 08:39] [ALPM] upgraded protobuf (3.5.2-1 -> <IP_ADDRESS>-1)
[2018-08-07 08:39] [ALPM] upgraded protobuf-c (1.3.0-2 -> 1.3.0-3)
[2018-08-07 08:39] [ALPM] upgraded libpurple (2.13.0-2 -> 2.13.0-4)
[2018-08-07 08:39] [ALPM] upgraded libreoffice-fresh (6.0.5-1 -> 6.0.6-1)
[2018-08-07 08:39] [ALPM] upgraded libreoffice-fresh-cs (6.0.5-1 -> 6.0.6-1)
[2018-08-07 08:39] [ALPM] upgraded libteam (1.27-1 -> 1.27-2)
[2018-08-07 08:39] [ALPM] upgraded linux (4.17.11-1 -> 4.17.12.arch1-1)
[2018-08-07 08:39] [ALPM] upgraded lirc (1:0.10.1-1 -> 1:0.10.1-2)
[2018-08-07 08:39] [ALPM] upgraded perl-encode-locale (1.05-3 -> 1.05-4)
[2018-08-07 08:39] [ALPM] upgraded perl-error (0.17026-1 -> 0.17026-2)
[2018-08-07 08:39] [ALPM] upgraded perl-http-date (6.02-4 -> 6.02-5)
[2018-08-07 08:39] [ALPM] upgraded perl-file-listing (6.04-4 -> 6.04-5)
[2018-08-07 08:39] [ALPM] upgraded perl-html-tagset (3.20-6 -> 3.20-7)
[2018-08-07 08:39] [ALPM] upgraded perl-html-parser (3.72-5 -> 3.72-6)
[2018-08-07 08:39] [ALPM] upgraded perl-lwp-mediatypes (6.02-4 -> 6.02-5)
[2018-08-07 08:39] [ALPM] upgraded perl-uri (1.74-1 -> 1.74-2)
[2018-08-07 08:39] [ALPM] upgraded perl-io-html (1.001-3 -> 1.001-4)
[2018-08-07 08:39] [ALPM] upgraded perl-http-message (6.18-1 -> 6.18-2)
[2018-08-07 08:39] [ALPM] upgraded perl-http-cookies (6.04-2 -> 6.04-3)
[2018-08-07 08:39] [ALPM] upgraded perl-http-daemon (6.01-5 -> 6.01-6)
[2018-08-07 08:39] [ALPM] upgraded perl-http-negotiate (6.01-4 -> 6.01-5)
[2018-08-07 08:39] [ALPM] upgraded perl-net-http (6.18-1 -> 6.18-2)
[2018-08-07 08:39] [ALPM] upgraded perl-www-robotrules (6.02-4 -> 6.02-5)
[2018-08-07 08:39] [ALPM] upgraded perl-try-tiny (0.30-1 -> 0.30-2)
[2018-08-07 08:39] [ALPM] upgraded perl-libwww (6.33-1 -> 6.33-2)
[2018-08-07 08:39] [ALPM] upgraded perl-timedate (2.30-4 -> 2.30-5)
[2018-08-07 08:39] [ALPM] upgraded perl-mailtools (2.20-1 -> 2.20-2)
[2018-08-07 08:39] [ALPM] upgraded perl-xml-parser (2.44-6 -> 2.44-7)
[2018-08-07 08:39] [ALPM] upgraded pidgin (2.13.0-2 -> 2.13.0-4)
[2018-08-07 08:39] [ALPM] upgraded postgresql-libs (10.4-3 -> 10.4-5)
[2018-08-07 08:39] [ALPM] upgraded postgresql (10.4-3 -> 10.4-5)
[2018-08-07 08:39] [ALPM] upgraded postgresql-old-upgrade (9.6.9-1 -> 9.6.9-2)
[2018-08-07 08:39] [ALPM] upgraded powerline-common (2.6-1 -> 2.6-3)
[2018-08-07 08:39] [ALPM] upgraded powerline-fonts (2.6-1 -> 2.6-3)
[2018-08-07 08:39] [ALPM] upgraded pygobject2-devel (2.28.7-1 -> 2.28.7-2)
[2018-08-07 08:39] [ALPM] upgraded python-six (1.11.0-1 -> 1.11.0-3)
[2018-08-07 08:39] [ALPM] upgraded python-anytree (2.4.3-1 -> 2.4.3-2)
[2018-08-07 08:39] [ALPM] upgraded python-appdirs (1.4.3-1 -> 1.4.3-2)
[2018-08-07 08:39] [ALPM] upgraded python-lxml (4.2.3-1 -> 4.2.4-1)
[2018-08-07 08:39] [ALPM] upgraded python-pyparsing (2.2.0-1 -> 2.2.0-2)
[2018-08-07 08:39] [ALPM] upgraded python-packaging (17.1-1 -> 17.1-2)
[2018-08-07 08:39] [ALPM] upgraded python-setuptools (1:39.2.0-2 -> 1:39.2.0-3)
[2018-08-07 08:39] [ALPM] upgraded python-pygments (2.2.0-1 -> 2.2.0-2)
[2018-08-07 08:39] [ALPM] upgraded python2-appdirs (1.4.3-1 -> 1.4.3-2)
[2018-08-07 08:39] [ALPM] upgraded python2-msgpack (0.5.6-1 -> 0.5.6-2)
[2018-08-07 08:39] [ALPM] upgraded python2-urllib3 (1.23-1 -> 1.23-2)
[2018-08-07 08:39] [ALPM] upgraded python2-pyparsing (2.2.0-1 -> 2.2.0-2)
[2018-08-07 08:39] [ALPM] upgraded python2-six (1.11.0-1 -> 1.11.0-3)
[2018-08-07 08:39] [ALPM] upgraded python2-packaging (17.1-1 -> 17.1-2)
[2018-08-07 08:39] [ALPM] upgraded python2-setuptools (1:39.2.0-2 -> 1:39.2.0-3)
[2018-08-07 08:39] [ALPM] upgraded python2-chardet (3.0.4-1 -> 3.0.4-2)
[2018-08-07 08:39] [ALPM] upgraded python2-idna (2.7-2 -> 2.7-3)
[2018-08-07 08:39] [ALPM] upgraded python2-requests (2.19.1-1 -> 2.19.1-2)
[2018-08-07 08:39] [ALPM] upgraded python2-cachecontrol (0.12.5-2 -> 0.12.5-4)
[2018-08-07 08:39] [ALPM] upgraded python2-cairo (1.17.0-1 -> 1.17.0-2)
[2018-08-07 08:39] [ALPM] upgraded python2-colorama (0.3.9-1 -> 0.3.9-2)
[2018-08-07 08:39] [ALPM] upgraded python2-dbus (1.2.8-1 -> 1.2.8-2)
[2018-08-07 08:39] [ALPM] upgraded python2-distlib (0.2.7-1 -> 0.2.7-2)
[2018-08-07 08:39] [ALPM] upgraded python2-distro (1.3.0-1 -> 1.3.0-2)
[2018-08-07 08:39] [ALPM] upgraded python2-gobject (3.28.3-1 -> 3.28.3-2)
[2018-08-07 08:39] [ALPM] upgraded python2-gobject2 (2.28.7-1 -> 2.28.7-2)
[2018-08-07 08:39] [ALPM] upgraded python2-webencodings (0.5.1-1 -> 0.5.1-2)
[2018-08-07 08:39] [ALPM] upgraded python2-html5lib (1.0.1-2 -> 1.0.1-3)
[2018-08-07 08:39] [ALPM] upgraded python2-lockfile (0.12.2-2 -> 0.12.2-3)
[2018-08-07 08:39] [ALPM] upgraded python2-pillow (5.2.0-1 -> 5.2.0-2)
[2018-08-07 08:39] [ALPM] upgraded python2-progress (1.4-1 -> 1.4-2)
[2018-08-07 08:39] [ALPM] upgraded python2-pytoml (0.1.16-1 -> 0.1.16-2)
[2018-08-07 08:39] [ALPM] upgraded python2-retrying (1.3.3-3 -> 1.3.3-4)
[2018-08-07 08:39] [ALPM] upgraded python2-pip (10.0.1-1 -> 18.0-1)
[2018-08-07 08:39] [ALPM] upgraded python2-psutil (5.4.6-1 -> 5.4.6-2)
[2018-08-07 08:39] [ALPM] upgraded python2-pycups (1.9.73-3 -> 1.9.73-4)
[2018-08-07 08:39] [ALPM] upgraded python2-reportlab (3.5.1-1 -> 3.5.1-2)
[2018-08-07 08:39] [ALPM] upgraded re2 (20180701-1 -> 20180801-1)
[2018-08-07 08:39] [ALPM] upgraded vim-runtime (8.1.0022-1 -> 8.1.0194-2)
[2018-08-07 08:39] [ALPM] upgraded vim (8.1.0022-1 -> 8.1.0194-2)
[2018-08-07 08:39] [ALPM] upgraded vlc (3.0.3-2 -> 3.0.3-3)
[2018-08-07 08:39] [ALPM] transaction completed
[2018-08-07 08:39] [ALPM] running '60-linux.hook'...
[2018-08-07 08:39] [ALPM] running '90-linux.hook'...
[2018-08-07 08:39] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
[2018-08-07 08:39] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
[2018-08-07 08:39] [ALPM-SCRIPTLET] ==> Starting build: 4.17.12-arch1-1-ARCH
[2018-08-07 08:39] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2018-08-07 08:39] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
[2018-08-07 08:39] [ALPM-SCRIPTLET]   -> Running build hook: [autodetect]
[2018-08-07 08:39] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2018-08-07 08:39] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2018-08-07 08:39] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2018-08-07 08:39] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2018-08-07 08:39] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2018-08-07 08:39] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2018-08-07 08:39] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux.img
[2018-08-07 08:39] [ALPM-SCRIPTLET] ==> Image generation successful
[2018-08-07 08:39] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
[2018-08-07 08:39] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
[2018-08-07 08:39] [ALPM-SCRIPTLET] ==> Starting build: 4.17.12-arch1-1-ARCH
[2018-08-07 08:39] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2018-08-07 08:39] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
[2018-08-07 08:39] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2018-08-07 08:39] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2018-08-07 08:39] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: aic94xx
[2018-08-07 08:39] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: wd719x
[2018-08-07 08:39] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2018-08-07 08:39] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2018-08-07 08:39] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2018-08-07 08:39] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2018-08-07 08:39] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-fallback.img
[2018-08-07 08:39] [ALPM-SCRIPTLET] ==> Image generation successful
[2018-08-07 08:39] [ALPM] running 'detect-old-perl-modules.hook'...
[2018-08-07 08:39] [ALPM] running 'fontconfig.hook'...
[2018-08-07 08:39] [ALPM] running 'glib-compile-schemas.hook'...
[2018-08-07 08:39] [ALPM] running 'gtk-update-icon-cache.hook'...
[2018-08-07 08:39] [ALPM] running 'systemd-daemon-reload.hook'...
[2018-08-07 08:39] [ALPM] running 'systemd-sysusers.hook'...
[2018-08-07 08:39] [ALPM] running 'systemd-tmpfiles.hook'...
[2018-08-07 08:39] [ALPM] running 'systemd-udev-reload.hook'...
[2018-08-07 08:39] [ALPM] running 'systemd-update.hook'...
[2018-08-07 08:39] [ALPM] running 'texinfo-install.hook'...
[2018-08-07 08:39] [ALPM] running 'update-desktop-database.hook'...
[2018-08-07 08:39] [ALPM] running 'update-mime-database.hook'...
[2018-08-07 08:39] [ALPM] running 'update-vlc-plugin-cache.hook'...
[2018-08-07 08:39] [ALPM] running 'xorg-mkfontdir.hook'...

UPDATE: with version visual-studio-code-insiders-1531459376 :
$ code-insiders --verbose
[8621:0807/100911.462218:ERROR:sandbox_linux.cc(343)] InitializeSandbox() called with multiple threads in process gpu-process.
[main 10:09:11] Starting VS Code
[main 10:09:11] from: /opt/visual-studio-code-insiders/resources/app
[main 10:09:11] args: { _: [],
  help: false,
  h: false,
  version: false,
  v: false,
  wait: false,
  w: false,
  diff: false,
  d: false,
  add: false,
  a: false,
  goto: false,
  g: false,
  'new-window': false,
  n: false,
  'unity-launch': false,
  'reuse-window': false,
  r: false,
  'open-url': false,
  performance: false,
  p: false,
  'prof-startup': false,
  verbose: true,
  logExtensionHostCommunication: false,
  'disable-extensions': false,
  disableExtensions: false,
  'list-extensions': false,
  'show-versions': false,
  nolazy: false,
  issue: false,
  'skip-getting-started': false,
  'skip-release-notes': false,
  'sticky-quickopen': false,
  'disable-restore-windows': false,
  'disable-telemetry': false,
  'disable-updates': false,
  'disable-crash-reporter': false,
  'skip-add-to-recently-opened': false,
  status: false,
  s: false,
  'file-write': false,
  'file-chmod': false,
  'driver-verbose': false }
[main 10:09:11] Resolving machine identifier...
[main 10:09:11] Resolved machine identifier: 7b5440f874c3fbfa3410613f574cb38e50c3dfe847530b4fc5ef23cab041ee77
[main 10:09:11] update#setState idle
[main 10:09:11] TypeError: Cannot read property 'lastIndexOf' of undefined
    at Object.o [as basename] (/opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-main/main.js:46:538)
    at Object.t.getWorkspaceLabel (/opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-main/main.js:334:880)
    at e.createOpenRecentMenuItem (/opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-main/main.js:367:142)
    at e.setOpenRecentMenu (/opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-main/main.js:366:326)
    at e.setFileMenu (/opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-main/main.js:362:537)
    at e.install (/opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-main/main.js:358:166)
    at new e (/opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-main/main.js:354:849)
    at t.create (/opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-main/main.js:52:365)
    at e._createInstance (/opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-main/main.js:207:10)
    at e.createInstance (/opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-main/main.js:206:269)
    at t.afterWindowOpen (/opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-main/main.js:521:583)
    at /opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-main/main.js:516:699
    at e.invokeFunction (/opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-main/main.js:205:920)
    at /opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-main/main.js:516:663
    at n.Class.define.cancel.then (/opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-main/main.js:90:201)
    at /opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-main/main.js:516:523
    at n.Class.define.cancel.then (/opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-main/main.js:90:201)
    at t.startup (/opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-main/main.js:515:912)
    at /opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-main/main.js:527:539
    at Object.v [as _notify] (/opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-main/main.js:83:572)
    at Object.enter (/opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-main/main.js:86:924)
    at n.Class.derive._oncancel._run (/opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-main/main.js:88:790)
    at n.Class.derive._oncancel._completed (/opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-main/main.js:88:231)
    at Server.<anonymous> (/opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-main/main.js:168:908)
    at Object.onceWrapper (events.js:293:19)
    at emitNone (events.js:86:13)
    at Server.emit (events.js:188:7)
    at emitListeningNT (net.js:1290:10)
    at _combinedTickCallback (internal/process/next_tick.js:77:11)
    at process._tickCallback (internal/process/next_tick.js:104:9)
[main 10:09:11] Lifecycle#kill()
[main 10:09:11] Lifecycle#window-closed 1
[main 10:09:11] Lifecycle#onShutdown.fire()
[main 10:09:11] telemetry/optInStatus { optIn: true }

@scippio I had a similar problem after an upgrade. In my case, the problem was with glibc. Reinstalling glibc 2.27.3 fixed the problem for me.

@AndyHeasman Thanks! It's works!

@scippio you're welcome!

@scippio I had a similar problem after an upgrade. In my case, the problem was with glibc. Reinstalling glibc 2.27-3 fixed the problem for me.

That's extraordinarily dangerous, glibc is backwards-compatible with programs built against older glibc, but not forwards-compatible with programs built against newer glibc. Any packages built after the glibc update stand a high chance of not running due to symbols too new for your ignored glibc package to provide.

Apparently lots of software using the prebuilt electron distributions instead of the system electron provided by the Arch Linux official repos, are breaking. But the only common denominator is that they all use electron... so it would seem to be an electron issue.

Can you clarify VS Code's version? (code --version)

The issue is upstream Electron, just downloading the prebuilt .zip file and running ./electron causes the same segfault. The distribution-provided electron binary runs VSCode just fine (since it's linked against a compatible glibc version). Also, VSCode segfaults before it can actually execute code --version correctly. The version I'm personally testing against is from commit ac60be30a.

Reported upstream as https://github.com/electron/electron/issues/13972

The electron package from the Arch Linux community repository was actually built using glibc 2.27, nice try. ;)
$ bsdtar -xOf /var/cache/pacman/pkg/electron-2.0.6-1-x86_64.pkg.tar.xz .BUILDINFO| grep glibc
installed = glibc-2.27-3-x86_64

@eli-schwartz while I also see that entry, when I "lsof" electron shows "/usr/lib/libc-2.28.so (path dev=0,27)"
Ya, this issue bites as I'm also seeing the issue for skypeforlinux which has also been reported.
Electron does load by itself and so does Riot.

I'm just going to rebuild Electron overnight and see what happens. If the Arch package works, I'll try a clean build with the default settings and no patches applied.

@eli-schwartz while I also see that entry, when I "lsof" electron shows "/usr/lib/libc-2.28.so (path dev=0,27)"

/usr/lib/libc.so.6 is a symlink to libc-${version}.so where ${version} is whatever version you have installed. It doesn't matter -- applications are only looking for the former and don't care how it is provided.

Right:
community/electron 2.0.6-1 [installed]
community/riot-desktop 0.16.0-1 [installed]

They both work (acknowledging riot uses system-electron) while vscode and skypeforlinux do not.
The question in the meantime is whether there is a workaround where we can tell the MS stuff to use the system electron instead.
Trying to think here... but if vscode/skype are using electron built around glibc 2.27 and crashes but the system electron .BUILDINFO is claiming to be built for 2.27 but is functioning with 2.28... something isn't meshing for me here.

Looking at the symbols, the prebuilt binaries aren't built against glibc 2.27, they're built against 2.17. That's a pretty big version discrepancy, though it should still be compatible.

For reference:
~/Downloads/electron
❯ objdump -T ./electron | grep -o 'GLIBC_[0-9.]*' | cut '-d_' -f2 | sort -uV
2.2.5
2.3
2.3.2
2.3.3
2.3.4
2.4
2.6
2.7
2.9
2.11
2.14
2.15
2.17

~/Downloads/electron
❯ objdump -T =electron | grep -o 'GLIBC_[0-9.]*' | cut '-d_' -f2 | sort -uV
2.2.5
2.3
2.3.2
2.3.3
2.3.4
2.4
2.6
2.7
2.9
2.14
2.15
2.27

For more reference: Electron Dockerfile, libchromiumcontent Dockerfile, points to Ubuntu 16.04, which uses glibc 2.23, but it could be no symbols are linked from that.

Rebuilding Electron from source with Arch patches + glibc 2.28 works fine. Going to try a clean build now.

So yeah, building using the default toolchain (scripts/bootstrap.py && scripts/build.py) produces a segfaulting binary. The debug build doesn't load at all, seems to be related to a Freetype version mismatch in the build env and the actual Arch system. The backtrace is, unfortunately, underwhelming, though it does point to an issue inside Node.

OK, turns out the build actually happens inside a Debian chroot that has glibc 2.19.
I've also tried building Electron with the stock build setup and minimal patches using the system libraries, specifically applying these patches:

don't use the Debian sysroot
make breakpad build with recent glibc
fix linking with system libs

This fails to dirty build, but I'm going to try a clean build overnight to see if that helps.

Nifty patch/workaround (possibly) until this gets fixed: https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=slack-desktop
Note the patchelf at the bottom. I didn't know that could be done.
With that said, I still haven't gotten skype/vscode to work after patching them (sigtrap).

@vindicatorr I can confirm that the patch you linked to does what it says on the tin. My insider build is now working again.

I've submitted a pull request to Electron upstream that contains a fix: https://github.com/electron/electron/pull/13988

@vindicatorr Thanks, the patchelf trick actually works!
For reference:
patchelf --set-interpreter "/opt/glibc-2.27/usr/lib/ld-linux-x86-64.so.2" code
patchelf --set-rpath "/usr/share/VSCode-linux-x64/:/opt/glibc-2.27/usr/lib/" code

For the insiders version, this is what I had to run:
patchelf --set-preter "/opt/glibc-2.27/usr/lib/ld-linux-x86-64.so.2" /opt/visual-studio-code-insiders/code-insiders
patchelf --set-rpath "/opt/visual-studio-code-insiders/:/opt/glibc-2.27/usr/lib/" /opt/visual-studio-code-insiders/code-insiders

An additional note is that you need to have glibc-2.7 extracted in the /opt/glibc-2.27 directory. The download link I used is from the arch-desktop PKGBUILD: https://archive.archlinux.org/packages/g/glibc/glibc-2.27-3-x86_64.pkg.tar.xz

You shouldn't need this workaround any more, the glibc package in the repos has the problematic commit reverted for now.

We have early experimental builds for Electron 3, could people verify whether this repro's in this build?
https://az764295.vo.msecnd.net/exploration/acdabe28fb63ed8b3bdd9ba685bfe595c2daf750/code-exploration-1533993531.tar.gz

Electron 3 builds work fine, as Electron itself is built with a newer toolchain. Either way, nice to have confirmation.

Electron 3 works fine in Fedora Rawhide but the glibc issue has not been fixed, preventing Electron 2 based apps(code, atom, skype) from running.

It's not a glibc issue, it's an Electron issue. We've figured out a fix, but it's a pretty invasive change, so it might take a bit more time to make it into a release.

Not sure if this is somehow related: https://github.com/Microsoft/vscode/issues/51917#issuecomment-412751708

There shouldn't be anything fancy involved, just
#!/bin/sh

exec electron /path/to/app "$@"

@eli-schwartz For me that results in vscode opening its own app dir into a workspace, in addition to whichever file or folder I pass in, but it completely ignores any command-line switches I pass to it. At least it's usable though!
From casually looking at the bin/code script included, I'm guessing the actual code binary as well as resources/app/out/cli.js are meant to work together to handle everything properly. (Editing bin/code to point at /usr/bin/electron instead, results in the opposite: command-line switches are recognized, but no window is ever opened)

PS: I have Electron 3.0.0-beta.5 in my Arch.

@opensas I tried:
electron /opt/visual-studio-code-insiders/resources/app/
$ electron /opt/visual-studio-code-insiders/resources/app/
Error: The module '/opt/visual-studio-code-insiders/resources/app/node_modules.asar.unpacked/spdlog/build/Release/spdlog.node'
was compiled against a different Node.js version using
NODE_MODULE_VERSION 57. This version of Node.js requires
NODE_MODULE_VERSION 64. Please try re-compiling or re-installing
the module (for instance, using `npm rebuild` or `npm install`).
    at process.module.(anonymous function) [as dlopen] (ELECTRON_ASAR.js:166:20)
    at Object.Module._extensions..node (internal/modules/cjs/loader.js:740:18)
    at Object.module.(anonymous function) [as .node] (ELECTRON_ASAR.js:180:18)
    at Module.load (internal/modules/cjs/loader.js:620:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:559:12)
    at Function.Module._load (internal/modules/cjs/loader.js:551:3)
    at Module.require (internal/modules/cjs/loader.js:658:17)
    at n (/opt/visual-studio-code-insiders/resources/app/out/vs/loader.js:15:513)
    at bindings (/opt/visual-studio-code-insiders/resources/app/node_modules.asar/bindings/bindings.js:81:44)
    at Object.<anonymous> (/opt/visual-studio-code-insiders/resources/app/node_modules.asar/spdlog/index.js:3:35)
    at Object.<anonymous> (/opt/visual-studio-code-insiders/resources/app/node_modules.asar/spdlog/index.js:21:3)
    at Module.i._compile (/opt/visual-studio-code-insiders/resources/app/out/vs/loader.js:15:731)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:722:10)
    at Module.load (internal/modules/cjs/loader.js:620:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:559:12)
    at Function.Module._load (internal/modules/cjs/loader.js:551:3)
    at Module.require (internal/modules/cjs/loader.js:658:17)
    at require (internal/modules/cjs/helpers.js:20:18)
    at Function.i [as __$__nodeRequire] (/opt/visual-studio-code-insiders/resources/app/out/vs/loader.js:30:770)
    at Object.t.createSpdLogService (/opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-main/main.js:227:185)
    at /opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-main/main.js:543:65
    at Object.v [as _notify] (/opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-main/main.js:84:807)
    at Object.enter (/opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-main/main.js:88:85)
    at n.Class.derive._oncancel._run (/opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-main/main.js:89:932)
    at n.Class.derive._oncancel._completed (/opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-main/main.js:89:373)
    at Server.<anonymous> (/opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-main/main.js:171:126)
    at Object.onceWrapper (events.js:273:13)
    at Server.emit (events.js:182:13)
    at emitListeningNT (net.js:1364:10)
    at process._tickCallback (internal/process/next_tick.js:63:19)
Error: The module '/opt/visual-studio-code-insiders/resources/app/node_modules.asar.unpacked/native-keymap/build/Release/keymapping.node'
was compiled against a different Node.js version using
NODE_MODULE_VERSION 57. This version of Node.js requires
NODE_MODULE_VERSION 64. Please try re-compiling or re-installing
the module (for instance, using `npm rebuild` or `npm install`).
    at process.module.(anonymous function) [as dlopen] (ELECTRON_ASAR.js:166:20)
    at Object.Module._extensions..node (internal/modules/cjs/loader.js:740:18)
    at Object.module.(anonymous function) [as .node] (ELECTRON_ASAR.js:180:18)
    at Module.load (internal/modules/cjs/loader.js:620:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:559:12)
    at Function.Module._load (internal/modules/cjs/loader.js:551:3)
    at Module.require (internal/modules/cjs/loader.js:658:17)
    at n (/opt/visual-studio-code-insiders/resources/app/out/vs/loader.js:15:513)
    at NativeBinding._init (/opt/visual-studio-code-insiders/resources/app/node_modules.asar/native-keymap/index.js:15:22)
    at NativeBinding.onDidChangeKeyboardLayout (/opt/visual-studio-code-insiders/resources/app/node_modules.asar/native-keymap/index.js:37:10)
    at Object.exports.onDidChangeKeyboardLayout (/opt/visual-studio-code-insiders/resources/app/node_modules.asar/native-keymap/index.js:61:18)
    at e.onDidChangeKeyboardLayout (/opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-main/main.js:312:245)
    at t.registerListeners (/opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-main/main.js:529:849)
    at t (/opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-main/main.js:526:763)
    at t.create (/opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-main/main.js:51:535)
    at e._createInstance (/opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-main/main.js:209:703)
    at e.createInstance (/opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-main/main.js:208:959)
    at /opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-main/main.js:543:119
    at Object.v [as _notify] (/opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-main/main.js:84:807)
    at Object.enter (/opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-main/main.js:88:85)
    at n.Class.derive._oncancel._run (/opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-main/main.js:89:932)
    at n.Class.derive._oncancel._completed (/opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-main/main.js:89:373)
    at Server.<anonymous> (/opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-main/main.js:171:126)
    at Object.onceWrapper (events.js:273:13)
    at Server.emit (events.js:182:13)
    at emitListeningNT (net.js:1364:10)
    at process._tickCallback (internal/process/next_tick.js:63:19)
[main 18:31:52] update#setState idle

Looks like for Fedora specifically it's working on 28, just not Rawhide.

Everyone using the Arch Linux package, please upgrade to 1.26.0-3 which includes fixes for glibc issues with the open file/folder dialogs as well as the original segfault. If you see any more problems, share them on AUR.

I using archlinux，My vscode is also awake.
visual-studio-code-bin of aur.

when i “code . ” in zsh ，
it say：
(core dumped) ELECTRON_RUN_AS_NODE=1 "$ELECTRON" "$CLI" "$@"

Update your visual-studio-code-bin package.

It turns out that there is a delay in the mirror station, Replace the mirror address，and Obtained a new version，it can run normally

FYI, glibc 2.28-4 is now available in the Arch repositories and vscode runs just fine again (or at least the .gz release from the website does, which is what I usually use anyway).

@jaromero I can confirm that after the update to glibc 2.28-4, my installation of VS Code Insiders is working (Installed through AUR yesterday).

Why does https://vscode-update.azurewebsites.net/latest/linux-x64/stable, aka the official Linux binary download, still contain the broken version?
From a mere user experience point of view, downloading the official tar and the being prompted with a Segmentation fault, is... awkward

The segfault is fixed on the glibc side in Arch, for now. The proper fix is merged into Electron and will be in the next point release, at which point VSCode will be able to update to a new Electron release and fix the issue properly.

@phil294 currently we recommend using the community package on AUR for Arch https://code.visualstudio.com/docs/setup/linux#_aur-package-for-arch-linux

all problems described in https://github.com/Microsoft/vscode/issues/56342 seem to be fixed in 1.26.1
thanks :+1:  :tada:

@Tyriar @bpasero Electron 2.0.8 is out with the proper fix, bump?

I'm with the same problem. Any fix?

Tried downloading Atom instead when this problem happened on me, but same problems happens when starting Atom.

Can people seeing this issue please try out this build that uses Electron 2.0.9: Download

@bpasero I can confirm that the Electron 2.0.9 based build you've linked resolves this issue for me. This is on Ubuntu Cosmic Cuttlefish (18.10) [amd64], with libc 2.28-0ubuntu1.
On the same environment, the current deb package of code-insiders from packages.microsoft.com (1.28.0-1536643513) crashes at startup with SIGSEGV.

Thanks, closing. We will ship this update for our September release.

Verifier: start VSCode on an ArchLinux distribution.

I am able to start an insider build using an up to date Arch Linux. Downloaded the insider tar.gz and extracted then ran  code-insiders. Where 1.26.1 crashes with the glibc_2.28 error.
Version: 1.28.0-insider
Commit: d59d9f5aa5708c006e409c1a7b197c27fecb54a4
Date: 2018-09-18T09:05:00.360Z
Electron: 2.0.9
Chrome: 61.0.3163.100
Node.js: 8.9.3
V8: 6.1.534.41
Architecture: x64

Adding verified label since @kbrosnan verified


UsbSerialDevice Null Pointer

java.lang.NullPointerException: Attempt to invoke virtual method 'boolean java.nio.ByteBuffer.isDirect()' on a null object reference
at android.hardware.usb.UsbRequest.dequeue(UsbRequest.java:156)
at android.hardware.usb.UsbDeviceConnection.requestWait(UsbDeviceConnection.java:230)
at com.felhr.usbserial.UsbSerialDevice$WorkerThread.run(UsbSerialDevice.java:213)
Line 213:
UsbRequest request = UsbSerialDevice.this.connection.requestWait();
May need to null check UsbSerialDevice.this.connection != null before requestWait() is called.
This happens every once in a while if a UsbSerial device (Arduino in my case) is detached while running. I'm using the UsbSerialDevice.UsbReadCallback for reading so I could work around this issue by directly reading the interface but the callback is more convenient for my event driven applicaiton.

Hi @eXsolacyst
This looks related to #40
I coded a solution in a branch called bug_40
Could you give it a try?

Will give it a try as soon as I can and let you know how it goes. Apologies
for opening a new issue for something that's already been brought to your
attention. Thanks for the awesome library btw. I really appreciate your
work.
Ryan L
On Jul 5, 2016 9:48 AM, "Felipe Herranz"<EMAIL_ADDRESS>wrote:

Hi @eXsolacyst https://github.com/eXsolacyst
This looks related to #40 https://github.com/felHR85/UsbSerial/issues/40
I coded a solution in a branch called bug_40
Could you give it a try?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/felHR85/UsbSerial/issues/58#issuecomment-230500204,
or mute the thread
https://github.com/notifications/unsubscribe/AKeL2L2tNnW5x9zVXDtZVlesHQrrTK6gks5qSm6sgaJpZM4JE8jP
.


chore(curriculum): Front End catagories links standardized.

Checklist:

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

Closes #47691

This is my second pull request on this because the last one I forgot to change the "a" tag,
Sorry about that.

no worries @IvanoskiHarmonia - thanks for the PR 🎉
Mind changing that Closes #47695 in the PR description to Closes #47691 - the issue that it closes. Thanks.

Hey @moT01,
I just made the change, let me know what you think.

Hey @IvanoskiHarmonia
This PR seems to make similar changes as the existing PR #47694. As such, we are going to close this as duplicate.
If you feel you have additional changes to expand upon this PR, please feel free to push your commits and request this PR be reopened.
Thanks again! 😊

If you have any questions, feel free to ask questions on the "Contributors" category on our forum or the contributors chat room.

Hey @ieahleen
Yea I understand,
I got a question though: my changes were exactly the same and were done before his pull request, how do you guys decide who's pull request gets to be merged?
Thank you in advance, and sorry for the probably weird question, but just curious.

Hey @IvanoskiHarmonia, Your PR is 47698, the merged one is 47694, it was created earlier, I was opening PRs in order from the issue.
Also, not linking the issue could mean that reviewers don't see your PR, so make sure that you link the issue (closes #xxxxx), as even if yours is the first, it doesn't matter if it's reviewed last.

@ieahleen yeah I made a slight mistake when I was referencing the issue the first time but I fixed it later.
My bad about that I didn't see the exact time of when the merged repo had made the pull request.
Thanks for the explanation I will make sure I don't make the same mistake again in the future.


Extension needs an icon

Hey there New Relic friends, nice extension you have here! We've featured your extension in the VS Code marketplace for this month and it looks like you could use an icon. 😄 ❤

Hi @fiveisprime thank you for featuring our extension! I'm able to see an icon in the marketplace. Do you mind verifying again if it's still missing?

How strange, I wasn't seeing it on any of my devices... until I turned off my ad blocker. I'll go ahead and close this and thanks!


Type of 2.2.2. BasedOn is not a valueSet (ReferralPrescription  Business rules V0.5)

Why is BasedOn mentioned under ValueSet?

What does this mean "basedOn mentioned under ValueSet"? where is it?

@annenerenhausen Can you clarify this? Why is basedOn considered as a valueSet? It is a Reference...

Disappeared from document in #65


add topic tags

I suggest adding the topics bcgstab, gmres, linear-algebra, sparse-linear-algebra in the About section, as explained at https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics

Hello, Beliavsky!
Thank you very much for your attention to my repository.
This is my first experience on GitHub and I plan to continue working with
GitHub.
In the About section I have added the information you recommended:
bicgstab, gmres, linear-algebra, sparse-linear-algebra
Sincerely, JNSResearcher
пн, 1 апр. 2024 г. в 19:40, Beliavsky @.***>:

I suggest adding the topics bcgstab, gmres, linear-algebra,
sparse-linear-algebra in the About section, as explained at
https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics
—
Reply to this email directly, view it on GitHub
https://github.com/JNSresearcher/SOLVERS_BCGSTAB_GMRES/issues/1, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/BD5FI4UIOAYGC6ROADTW3HLY3GEZPAVCNFSM6AAAAABFR3RU22VHI2DSMVQWIX3LMV43ASLTON2WKOZSGIYTQNRTGU3TCMA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


[API] Authorization token documentation incorrect

(basic Auth allowed only!)
swagger docs:
curl -X GET "http://localhost:3000/api/v1/users/test01/tokens" -H "accept: application/json" -H "Authorization: dGVzdDAxOnRlc3QwMQ=="
working solution:
curl -X GET "http://localhost:3000/api/v1/users/test01/tokens" -H "accept: application/json" -H "authorization: Basic dGVzdDAxOnRlc3QwMQ=="

@lunny can you add lable kind/api pleace?

It's wrong documentation. I think I've tried looking into fixing this before and couldn't.

ping @stale

Some Notes from discord:

It looks like swagger-ui return wrong curl suggestion

we should add docu about basicAuth to https://github.com/go-gitea/gitea/blob/master/routers/api/v1/api.go#L32 and below

rename reqToken to make it clear that it acept token and basic auth

handle authorization case-insensitive (https://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.2)

reverences:
https://tools.ietf.org/html/rfc7617
https://swagger.io/docs/specification/2-0/authentication/basic-authentication/

we should add docu about basicAuth to https://github.com/go-gitea/gitea/blob/master/routers/api/v1/api.go#L32 and below

We can't add anything to that yaml bit AFAIU. The spec does not allow for a desc on type: basic.

handle authorization case-insensitive

AFAICS we already do.


The supabase npm package was mistyped

just a text change in the readme file for the the name on an npm package.

Thank you :)


一定得linux环境吗？Windows Demo跑不通啊？

一开始报gameid的错，把他改成1后又报这个错。
Connect to dispatcher1 failed: dial tcp <IP_ADDRESS>:13001: connectex: No connection could be made because the target machine actively refused it.

同问

@mogebingxue  solved
first you should

goworld build [yourpath]
then
goworld start [yourpath]

and you should change your go env

GOOS=linux


Authorization Code Flow's Error: Uncaught SpotifyWebAPI\SpotifyWebAPIAuthException: code must be supplied in

I don't know if it can be useful for someone but after set my Authorization Code Flow I'm having this error:
PHP Fatal error:  Uncaught SpotifyWebAPI\SpotifyWebAPIAuthException: code must be supplied in {$INSTALL_PATH}\vendor\jwilsson\spotify-web-api-php\src\Request.php:54
Commenting the line header('Location: app.php'); in callback.php I noticed that the code variable was not gettable by the variabile $_GET['code'] . Infact it always was returned as NULL value and the $_GET as an empty array. So, in the callback.php, I changed the parameter of that call from:
$session->requestAccessToken($_GET['code'])
to that with the 'superglobal' $_REQUEST variable:
$session->requestAccessToken($_REQUEST['code'])
In this way, the code was being not NULL anymore and the access token was properly generated.
After that you can save $accessToken in a session variabile i.e. $_SESSION['accessToken'] = $accessToken; to make the access token visible to app.php.

Hey!
That's really strange that the $_GET array was empty. I'm glad you got it working with $_REQUEST though and shared it here.
I'm going to close this issue since it's not anything wrong with the library but thanks again for sharing it here!


OpenPilot Unavailable, Waiting for GPS

Describe the bug
When I turn on my car, comma 3 says "openpilot unavailable" and "waiting for controls to start" and "Waiting for GPS."
Tried rebooting the comma 3 several times. Tried reinstalling openpilot. Also tried driving around for a few minutes, giving it time.
Doesn't seem to ever load GPS. In https://useradmin.comma.ai/, every drive has false in the "can" folder.
Provide a route where the issue occurs
db2f545ea314b36d|2023-04-02--14-52-35--0
openpilot version
0.9.1
Additional info
dongle_id: db2f545ea314b36d

Double checked the wiring and it appears correct (will describe below). But wanted to note the red panda has a blinking blue LED when my car is off, starts blinking red instead when my car is on.
Order: osb2 -= Ethernet => non-harness black box => USB c => comma main port. Comma 3 aux port => usb-a adapter => red panda => usb-c => car harness => car / camera.

There are no CAN messages on your routes, which indicates the hardware may not be setup properly. Did you follow the setup guide at https://comma.ai/setup/comma-three? Your description sounds correct, but it's ambiguous, so I'd double check with the guide.

Ah, I see you have a support ticked opened and determined this is a hardware issue.


Section3

@AsfaMumtaz Image is available for testing. docker pull stakater/workshop-excercise:SNAPSHOT-PR-22-9713bf46


Support 4 bit color depth

Reading a PNG image created from a PDF file via convert, which in turn calls gs, I get this error:
Error: Unsupported bit depth 4

Apparently, 4 bit depth is the maximum the pngalpha driver for GhostScript supports, and is the default ImageMagick uses. It would be nice if these files could be read without hassle.

@gagern  I find it  https://github.com/darkskyapp/pngparse
please test it parse function. if ok i will integration into node-png

Yes, pngparse does work, it does support 1, 2, 4 and 8 bits per pixel. It seems somewhat slower than node-png, though.

@gagern I'll look. add you into collaborators.

There are a number of fragmented writers with different support. I've been refactoring pngjs to have support for any bit size.
https://github.com/lukeapage/pngjs2
@liangzeng I wanted ownership since I was making significant changes. I also wanted the name pngjs2 since it is currently the most popular library and this allows it to be found easier in npm.
If you (or anyone else) is interested I can make a pngjs organisation and add you to collaborators.


How process only selection right before use?

Info

Operating System: EndeavourOS (Archlinux)
Shell: fish 3.6.1
Terminal: kitty 0.31.0
nvim --version: NVIM v0.9.4 LuaJIT 2.1.1699392533
fzf --version: 0.43.0 (d3311d9f)

function Split(s, delimiter)
  local result = {};
  for match in (s .. delimiter):gmatch("(.-)" .. delimiter) do
    table.insert(result, match);
  end
  return result;
end

_G.fif_grep = function(opts)
  local fzf_lua = require 'fzf-lua'
  opts = opts or {}
  if opts.buffer ~= "" and opts.buffer ~= nil then
    opts.prompt = "fif  :'" .. opts.buffer .. "'❯ "
  elseif opts.search ~= "" and opts.search ~= nil then
    opts.prompt = "fif  :'" .. opts.search .. "'❯ "
  elseif opts.buffer ~= "" and opts.buffer ~= nil and opts.search ~= "" and opts.search ~= nil then
    opts.prompt = "fif  :'" .. opts.buffer .. "'  :'" .. opts.buffer .. "'❯ "
  else
    opts.prompt = "fif❯ "
  end
  opts.git_icons = true
  opts.file_icons = true
  opts.color_icons = true
  opts.actions = fzf_lua.defaults.actions.files
  opts.previewer = "builtin"

  -- opts.fzf_cli_args = '-q ' .. vim.fn.shellescape('none l')

  opts.actions = {
    -- ["<bind1>"] = { fn = function(selected) end, reload = true }
    -- ["<o>"] = { fn = require'fzf-lua'.actions.file_edit, reload = true }
    ["default"] = { fn = require 'fzf-lua'.actions.file_edit_or_qf },
    ["ctrl-s"]  = { fn = require 'fzf-lua'.actions.file_split },
    ["ctrl-v"]  = { fn = require 'fzf-lua'.actions.file_vsplit },
    ["ctrl-t"]  = { fn = require 'fzf-lua'.actions.file_tabedit },
    ["alt-q"]   = { fn = require 'fzf-lua'.actions.file_sel_to_qf },
    ["alt-l"]   = { fn = require 'fzf-lua'.actions.file_sel_to_ll }
  }

  local tags = table.concat(vim.opt.tags:get(), ' ')
  local cmd = { "cat", "tags",  "|", "rg", "-v", "'^!'" }
  cmd = table.concat(cmd, " ")
  print(cmd)

  return fzf_lua.fzf_exec(cmd, opts)
end

-- example keymaps
vim.keymap.set("n", ";t", function() _G.fif_grep({ search = "" }) end)
vim.keymap.set("n", "<leader>t", function() _G.fif_grep({ search = "" }) end)
vim.keymap.set("n", ";T", function() _G.fif_grep({ search = vim.fn.expand('<cword>') }) end)
vim.keymap.set("n", "<leader>T", function() _G.fif_grep({ search = vim.fn.expand('<cword>') }) end)

Description
How to process lines but only these choosen? To pass only choosen to execution.
When I have > 300.000 tags this transform slows down fzf input very much:
  opts.fn_transform = function(x)
    -- 1 tag
    -- 2 filename
    -- 5 line number
    local el = Split(x, "\t")
    local no = Split(el[5], ":")[2]
    return string.format("%s:%s:%s", el[2], no, el[1])
  end

I was thinking rather about function which could  convert selection for action.
I would even go without decoration, for speed.
We expect compatible line to be passed down to action, right? It should be in some specific format to execute actions.

I was thinking rather about function which could convert selection for action.

Not sure what you mean, do you mean a custom action? That’s easily achieved via actions.

Let me know if I understand your issue correctly first:

You’re using your own tags variant (why not use builtin tags btw?)
You need a custom action to execute a function on the selected output
Selected entries require processing inside your custom action function
You have a performance issue when selecting large amount of items so you’re trying to optimize performance of the custom action?

Does that sound about right?

Ok, for starters. I found that with built in Tags/BTags uses only first tag file, hence the reason of this approach.
Want to have multiple tag files. Some of them are not in current working directory.
I want to jump to source, open in tabs, for current project and to related libraries, when it's not supported by LSP.
Yes I have somewhat custom variant of tag files, because I am using very custom configuration.
But still, this is ctags.
Universal Ctags 6.0.0(p6.0.20221218.0), Copyright (C) 2015-2022 Universal Ctags Team
Universal Ctags is derived from Exuberant Ctags.
Exuberant Ctags 5.8, Copyright (C) 1996-2009 Darren Hiebert
  Compiled: Feb 24 2023, 18:05:01
  URL: https://ctags.io/
  Output version: 0.0
  Optional compiled features: +wildcards, +regex, +iconv, +option-directory, +xpath, +json, +interactive, +sandbox, +yaml, +packcc, +optscript, +pcre2

I was checking few command combinations for best performance, and on my machine this is the one:
cat tags ~/lib/tags | rg -v '^!'

When I feed output from it into fzf-lua it gets rendered, but enter to execute action fails because it's not compatible.
When I do transform for fzf-lua, I have performance issues.

When I do transform for fzf-lua, I have performance issues.

That’s why I suggested you do that transform in the external process. However, IMHO that is over complicating things and you’ll also need to optimize your transform function for speed.

When I feed output from it into fzf-lua it gets rendered, but enter to execute action fails because it's not compatible.

Something like:
local fn_transform_tbl = function(tbl)
  -- format all entires as “fzf-lua compatible”
  return vim.tbl_map(selected, function(x)
    -- your “fn_transform” code goes here
    return string.format(…, x)
  end)
end

opts.actions = {
    ["default"] = function(selected, opts)
      require 'fzf-lua'.actions.file_edit_or_qf(fn_transform_tbl(selected), opts)
    end,
}

Ok, here's the status.
I needed to make extra script which is decorating tags on the fly with absolute path to tags file.

When I want to get tags for buffer outside of project, I need to remove path to directory with tags file.

Relevant helper functions:

Gist with code: https://gist.github.com/akemrir/b1c791e46dccd119e855ed8e0938dfc9
Thanks for your help, your hint worked very well.

Looks great @akemrir!
Closing, feel free to reopen if you need more help in this regard.


Add documentation for intellisense when publishing package

Pull Request
What does this PR do?
This PR add the xml doc to the package in order to have it displayed in intellisense for end users.
During dev time, warnings will be displayed for missing documentation and is disabled when releasing a new version to avoid polluting build logs.
In case you want all the documentation mandatory after fixing the warnings you may want to remove this from the Meilisearch.csproj
<!-- Warnings for missing XML documentation are only visible during dev time -->
<!-- You may want to remove the NoWarn node in case documentation will be mandatory in the future -->
<NoWarn Condition=" '$(Configuration)' == 'Release'">$(NoWarn);1591</NoWarn>

PR checklist
Please check if your PR fulfills the following requirements:

[X] Does this PR fix an existing issue, or have you listed the changes applied in the PR description (and why they are needed)?
[X] Have you read the contributing guidelines?
[X] Have you made sure that the title is accurate and descriptive of the changes?

Thank you so much for contributing to Meilisearch!

bors merge


unpack_strategy/zip: fix extraction issues on macOS without developer mode

Before:
> UnpackStrategy::Zip.ancestors
[UnpackStrategy::Zip::MacOSZipExtension, UnpackStrategy, SystemCommand::Mixin, UnpackStrategy::Zip, UnpackStrategy, Object, SystemCommand::Mixin, JSON::Ext::Generator::GeneratorMethods::Object, Kernel, BasicObject]

After:
> UnpackStrategy::Zip.ancestors
[UnpackStrategy::Zip::MacOSZipExtension, UnpackStrategy::Zip, UnpackStrategy, Object, SystemCommand::Mixin, JSON::Ext::Generator::GeneratorMethods::Object, Kernel, BasicObject]

We were skipping the generic OS extract_to_dir and directly going to the unpack strategy baseclass.
For some reason, this didn't happen with Sorbet Runtime enabled as it seems to break the ancestor rules (coincidentally to our favour on this occasion).
Fixes #16287.

Thanks @Bo98!


Redesign SailModel to support AutoCloseable

(Migrated from https://openrdf.atlassian.net/browse/SES-2292 )
SailModel currently takes a SailConnection as an input, which makes it difficult to reliably close the connection if the SailModel is passed out of the current scope. It could be redesigned to take a Sail as an input and create and manage SailConnection resources internally, while implementing AutoCloseable to indicate that it needs to have close called on it.

The Model API is intended for in-memory management of triples. The only use (within Sesame) is for inferencing and in that situation the model should NOT be closing the connection. I can't think of a use-case for having a closable connection that implements Model API, but if there is, it is easy enough to extend the SailModel in a project that needs it.


I can't verifier emails of database

Hello.
I have a problem. I have a data base in mysql with emails. I need verifier this emails with you script. I get the emails in php with mysqli_fetch_array but this don't run with this function. I have tried to show that result of mysli_fetch_array by screen and this show correctly the address.
If i write ane address in code this run correctly, but if i use the funcion not run.
Please, can you help me?
This is my code example:
`
require_once('verifyEmail-master/verify.class.php');
$link = mysqli_connect("xxxx", "xxxx", "xxxx", "xxxx");
$result = mysqli_query($link, "select * from correos limit 0,10");
while( $datos = mysqli_fetch_array($result) )
{
$ve = new VE\VerifyEmail($datos[correo], 'myemail@myemail.com');
    if($ve->verify()==true)
    {
        echo "
 The email $datos[correo] is correct.";
    }
    else
    {
        echo "
 The email $datos[correo] is not correct.";
    }

}

`
Very thanks.

Are you sure this returns the right value?
$datos[correo]
Check your syntax my friend.
http://php.net/manual/en/function.mysql-fetch-array.php

Yes. I can show the value in screen. This is correct.

If i use mysqi_fectch_array the values are corrects. I recive this error of your script:
"No suitable MX records found.".
If i write the value of mysli_fetch_array direct on my code this run, but if save the value in a var and later i use in your script, this don't run.
Help?
Thanks.

Can you also use the debug function to print out debug messages?
print_r($ve->get_debug());

This said:
bool(false)
Array
(
[0] => initialized with Email<EMAIL_ADDRESS>Verifier Email<EMAIL_ADDRESS>Port: 25
[1] => Verify function was called.
[2] => Finding MX record...
[3] => No MX record was found.
)
Array
(
[errors] => Array
(
[0] => Array
(
[code] => 100
[message] => No suitable MX records found.
)
    )

)
But this only happen if i read the emails of data base. For example, if a write a email in source code in "$ve = new VE\VerifyEmail(emailtoverifier, myemail);" this run, but if i read this same email of database this don't run and i have check and the read of data base is correct.
Thanks.

What are  the actual emails in the debug messages. It seems like the email might have a typo or something that it does not have an MX record.
Without the email I probably won't be able to tell you what the issue is.


Dreambooth: Problem with resuming training

When I want to resume training my 2g model, it somehow says 1.71g, also noting weights not used
Is this normal or not? Because my model that was resume trained do succ

it's the transformers cache, just ignore that, it's not a problem.

it's the transformers cache, just ignore that, it's not a problem.

Thank you
By the way, is increasing the number of instance images worth it when training the art style of an artist?
How many steps would you recommend for 50 images with a 15% text encoder?

try 30, with 10% or 20% textenc, best settings would be 10K steps including 1k or 2k textenc


Can't build example project on Xcode 12.5

I just cloned the repository to know the project and when compiling there was an error:
- RCT-Folly/folly/synchronization/DistributedMutex-inl.h:1051:5: 'atomic_notify_one<unsigned long>' is unavailable

Maybe it's related with this conversation: https://stackoverflow.com/questions/66189325/xcode-throws-atomic-notify-oneunsigned-long-is-unavailable

I was able to build with following changes:
# filename: example/ios/Podfile

-  :hermes_enabled => true
+  :hermes_enabled => false

...

- use_flipper!({ 'Flipper' => '0.74.0' })

However I'm not sure if it's the correct solution.

yeah I believe that's a flipper issue, maybe this will work on RN 65?


Release Google.Cloud.Firestore.Admin.V1 version 3.8.0

Changes in this release:
New features

Change netstandard2.1 target to netstandard2.0 (commit 82bea85)
Add Vector Index API (commit 6d2a003)

Created release for Google.Cloud.Firestore.Admin.V1-3.8.0


test: add static group auth tests for references-style relationships

Description of changes
Add static group auth tests for references-style relationships.
Note: I manually assigned the following tests to be run in us-east-2 to pick up the most recent Lambda layer, which hasn't finished deploying to all supported regions:

assoc-field.test.ts
bind-sql-ids.test.ts
static-group-auth.test.ts

This will ensure that these tests run against a layer that supports primary key arguments for list queries.
Checklist

[x] PR description included
[x] yarn test passes
[x] E2E tests pass
[x] Tests are changed or added

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Looks good. Love the structure!
It would be cool to get to the point that we're defining all the test cases once and running through them all for each data source combination of primary and related to cut down of the repetitive code in the .test.ts files. But that's for another day 😄

Yes, I toyed with a couple of ways of doing this, and decided not to go down that particular rabbit hole just yet. :)


:alien: :lipstick:

the :rocket: reached us :alien:.

features:

windows supports :shipit:
colorful response :rainbow:

Not bad :+1:

I would also like to thank @gpedro for the contributions he made.


Add collapse all button

Motivation
Add icon for collapse all action.
Changes

IconCollapseAll component

Screenshots

LGTM, thanks
Side note: it would be cooler to have a single icon that has a visual transition / animation between the two states collapse and not collapsed. Generally speaking I think it would be neat to add more visual small animations to the dapp

Thanks for your feedback. Let's start with the in:fade first :)


Move db connection out of config

This is one small step towards a new world order inside of Ghost core, where things are what they say they are, and aren't all interdependent.
A special shout out to @esatterwhite for this one - I'd have cherry-picked the commits but I couldn't get a valid reference.
refs #5047

database connections are not configuration

This is really exciting!!!

I'm glad someone else feels that way! I was dancing around when I got it working yesterday :dancers:


v 3+ (BUG) GRAPHICAL EDITS FOR INFO SCREEN (i.e. move filter icons & delete the word / option 'oval' from the 'Leaf Shape' list)

ToDO:
These are small graphic edits for Info screen.

this is just a text/graphic edit (feature is going to be released as a 'Coming Soon' in V4). But the beta testflight build # 67 shows the word 'Oval' and it just needs to be deleted.

move the filter buttons 'Genus' and 'Species' down a little closer to the 'Search' box. Note: CHECK THAT THIS doesn't mess up Info menu formatting in Android AND iOS

Reviewed with @bestw07 - fixed & closing


Add /version endpoint and --version cli flag

Summary
Closes #18
Allow the server operator a way to view the current RAS version with either the CLI or API.
The CLI allows for -v, --v, -version or --version. There's also -h output
GoReleaser by default sets the main.version, main.commit, and main.date variables.
Testing
Help output
./retro_aim_server -h
Usage of ./retro_aim_server:
  -v    Display build information
  -version
        Display build information

On a non-release build, it will show a dev version with no commit or date information.
./retro_aim_server --version
version:   dev
commit:    none
date:      unknown

curl -s localhost:8080/version | jq
{
  "version": "dev",
  "commit": "none",
  "date": "unknown"
}

I made a release build by running  make release-dry-run. The latest tag I had checked out was 0.8.0 so that's the version it built with, but in a normal situation this should show the latest tag. The output shows the version, latest commit, and the date it was built.
./retro_aim_server -v
version:   0.8.0
commit:    2e0cf4181ab3cb4df6ebc4f84d7c16a591aacb8d
date:      2024-08-29T20:28:00Z

curl -s localhost:8080/version | jq
{
  "version": "0.8.0",
  "commit": "2e0cf4181ab3cb4df6ebc4f84d7c16a591aacb8d",
  "date": "2024-08-29T20:28:00Z"
}

Also added unit tests for the /version endpoint which pass

very nice 🌮


Json in c

Provide a functions to deal with json like js_JSONstringify and js_JSONparse in the c api header file

If you want to call JSON.stringify from C there is a simple way to do it in a few lines of code. These are easily wrapped up in a convenience functions should you need to.
js_getglobal(J, "JSON");
js_getproperty(J, -1, "parse");
js_rot2(J);
js_pushstring(J, your_string_to_parse);
js_call(J, 1);

Got This One:
js_getglobal(ctx,"JSON"); //get the global JSON object
js_getproperty(ctx,-1,"stringify"); //get the stringify method
js_getglobal(ctx,"JSON");  // push the global JSON object as this argument to stringify
js_copy(ctx,0); // copy the first argument that passed to my function
js_call(ctx,1); // call the function
mujs is so easy and amazing


add missing giveth addresses

add addresses for GIVx and some EOA deployer keys and fund handlers

/validate 459efe8b0ba4f42bcbfed7873ee27e735fcfe610


Add kissat to portfolio solver

cc @ninehusky @vcanumalla
I'm not actually sure whether kissat is a solver that can be added, or if it's a sub-solver that we can switch to using flags on the top-level SMT solvers we're using (CVC5 and Bitwuzla).


We can't set variable value outside the function

I am working on the stdlib and I write code like this:
# System functions
import "stdlib/str.jou"

declare getenv(varname: byte*) -> byte*

def is_windows() -> bool:
    return getenv("OS") != NULL and strstr(getenv("OS"), "Windows") != NULL

def is_macos() -> bool:
    return getenv("OSTYPE") != NULL and starts_with(getenv("OSTYPE"), "darwin")

def platform() -> byte*:
    return getenv("OS")

WINDOWS = is_windows()
MACOS = is_macos()

and it tell me:
jou sys.jou
compiler error in file "sys.jou", line 15: expected a definition or declaration, got a variable name 'WINDOWS'
The process failed with status 1.

So how can I give a value to variable outside the functions?

Jou doesn't do something magically and hide it. If you say WINDOWS = is_windows(), Jou will not run the is_windows() function when the program starts. If you want something to run when the program starts, it needs to go to the main() function or _windows_startup.jou.
But instead of having these functions in the stdlib, it would be better if you could detect the OS at compile time rather than at runtime. Maybe there would be special compile-time constants WINDOWS and MACOS. This way it would be possible to declare functions that don't exist in all systems. For example:
if WINDOWS:
    declare GetModuleFileNameA(hModule: void*, lpFilename: byte*, nSize: int) -> int
elif MACOS:
    declare _NSGetExecutablePath(buf: byte*, bufsize: int*) -> int
else:
    declare readlink(linkpath: byte*, result: byte*, result_size: long) -> long

def find_current_executable() -> byte*:
    if WINDOWS:
        # use GetModuleFileNameA()
    elif MACOS:
        # use _NSGetExecutablePath()
    else:
        # use readlink()

Currently this is not possible, because:

there are no compile-time if statements
there is no special WINDOWS constant whose value is known at compile time.

As a temporary solution that made this kinda work, I added some spaghetti with a few hard-coded function names to the compiler:
https://github.com/Akuli/jou/blob/914200d20bfbcd17d660c18689ac2f910a94c2da/src/codegen.c#L189-L196


test-branch/execute-job/wrong-commit-sha-on-pr/39d9ef53-b222-49f8-8935-8d60d769cde2

PR for testing a8781283c29270e23a10464056598be80d29896c

/canonical/self-hosted-runners/run-workflows 18e36da89352492fbe5b5488c9dee12702aa7ac9


fix error in example for import-group element

This fixes an error in the example for the ImportGroup Element.

@zochris : Thanks for your contribution! The author, @mikejo5000, has been notified to review your proposed change.

#sign-off


Auto update gradle dependencies

Author the user story for this feature
As a Flank developer, I want to automatically update dependencies so I can develop features using the latest libraries.

There are probably gradle plugins or other ideas that will auto update deps. Maybe we should use dependabot from GitHub?
https://github.com/dependabot/dependabot-core/issues/2238
or use a gradle plugin?

Tutorial:
https://proandroiddev.com/automate-dependency-updates-in-gradle-projects-with-dependabot-8f0092a89de9


Blacklist more Rojo build/compile files

Blacklist more Rojo build/compile files

what does that do ?

nvm i dont wanna know

Magic


Add a pad segment

What would a "pad" segment do, compared to either "bin" or using align/subalign?

The idea would be just advance the linker script by some amount (e.g. . += 0x10).
Bin would still dump a file of zeros which seems wasteful. However, I did not know about align, but it does seem all the use cases I know of seem to be aligned to 0x40 boundaries so maybe it would work.

Tried manually putting an . = ALIGN(., 64) but that did not seem to work, so I don't think just using align/subalign would work.


Implement dsl_tee_demuxer_max_branches_get/set services for the Demuxer Tee component

New services to get set the max-branches setting for a Demuxer Tee. The values controls how many sink pads are requested from the nvstreamdemux on Pipeline play. New Sinks/Branches can be added to the Demuxer Tee while the Pipeline is playing up to the point that max-branches is reached.
/**
 * @brief Gets the current max-branches setting for the name Deumuxer Tee
 * @param[in] name name of the Demuxer Tee to query
 * @param[out] max_branches current setting for max-branches
 * @return DSL_RESULT_SUCCESS on success, DSL_RESULT_DEMUXER_RESULT on failure
 */
DslReturnType dsl_tee_demuxer_max_branches_get(const wchar_t* name,
    uint* max_branches);

/**
 * @brief Sets the max-branches setting for the name Deumuxer Tee to use.
 * @param[in] name name of the Demuxer Tee to update
 * @param[in] max_branches new setting for max-branches
 * @return DSL_RESULT_SUCCESS on success, DSL_RESULT_DEMUXER_RESULT on failure
 */
DslReturnType dsl_tee_demuxer_max_branches_set(const wchar_t* name,
    uint max_branches);

Work has been pushed to the v0.27.alpha branch


logs contain sensitive information

the logs contain some sensitive information, including the JWT token used for authentication. this should be filtered out automatically before being sent out to the log sink. this would enable more people to have access the log informations.

this is fixed


Documentation incorrect for setting tool modes

Prerequisites

[x] Are you running the latest version?
[x] Are you reporting to the correct repository?
[x] Did you perform a cursory search?

For more information, see the CONTRIBUTING guide.
Description
Looks like the cTools v3 docs are wrong: https://tools.cornerstonejs.org/anatomy-of-a-tool/#modes: setToolModeActive should be setToolActive, etc...

Fixed at https://github.com/cornerstonejs/cornerstoneTools/pull/973

@all-contributors, please add @biharck for docs


Inconsistency between linux and windows on getch

I stumpled upon this during https://github.com/gyscos/Cursive/issues/210
Getch bahaves different under windows (10) and linux. A uniform solution would be nice.
To reproduce this, just use the getch example under windows and under linux.

What kind of behaviour are you looking for exactly? I fixed the panicing on unexpected values, pancurses should now return larger input values as Input::Unknown's as it should in commit 8f2b77922974d7bfe047cd73921d55490e6e0a9c

I don't know which behaviour should be favored, but all platforms should behave uniform.

On linux, pancurses doesn't parse anything, and directly returns the raw utf8 bytes one by one.

On Windows on the other hand it will return the char directly as one char instead of two separate ones.
I hope I could make clear what my concern is. I can test the code tomorrow.

It's not so much that pancurses changes things, the logic is actually the same on both platforms. If the output differs it's because there's a difference between PDCurses and ncurses. It would be good for pancurses to correctly parse characters though.

On linux, ncurses returns individual bytes. The actual encoding depends on the terminal configuration, but it's often utf8.
Returning input_byte as u8 as char is a bit weird:

For codepoints values under 128 (ASCII), in both utf8 and utf16, the input value equals the unicode number, so this conversion works.
For codepoints between 128 and 255, utf8 will produce two bytes, and each will be wrongly treated as a char. UTF16 still coincides with codepoints, so on windows these values are still properly parsed.
For codepoints above 255, the value will no longer fit in a u8, so it will be returned as "unknown" on windows. On linux, it will still return multiple weird characters.
And that's not even considering different locales/terminal configurations.

I see two possibilities:

Not parse anything, but be honest about it, and return either a u8 on linux or a u16 on windows. Problem: this means the datatype itself changes between platforms (we could return a u16 in both cases but it's not as clean).
Parse the input correctly for each platform. This is a bit tricky, as it means:

On windows, parse as utf-16 (is it even actually utf-16?)
On linux, parse the bytes depending on the terminal configuration. Should this depend on the locale? Or should we assume it's utf8?

Here's an attempt: b5480c613432c88dbdb907b805f050f1fb3e099f
It assumes that it's UTF-16 on Windows, this works on Windows 10 for me atleast.
Similarly it assumes UTF-8 on Linux which has also worked in my limited testing. For future work it would probably make sense to detect the locale and not try and parse non-utf8 data as utf-8, I need to see if I can setup an environment where I can test this easily.

Closing this with the release of v0.15 which includes the improvements to input handling. I didn't add support for anything other than UTF-8 on Linux, that's left for some time in the future.


Samsung Galaxy A51 issue

Samsung Galaxy A51 - FaceUnlock detected, but doesn't work!

https://user-images.githubusercontent.com/1887383/125315699-0bc7fd00-e340-11eb-92e8-1a99747edd55.mp4

Seems like solved


Remove support for FLAG_UNSECTORED

Fixes #4
There's the possibility that a newer patch updates BW's Storm and then some tools start creating maps that use this flag, but it still seems that at least 1.17's Storm doesn't support it (That is, it cannot open SC2 replays from 2009)

That is a very interesting map protection scheme, lol


docker inspect format json failing

Hello,
I have a very strange error on one machine. docker inspect --format {{json ...} fails  but docker inspect works.
# docker inspect --format "{{json .Config.Labels}}" 0d0dc58585ff
Template parsing error: template: :1: unclosed action

# docker inspect --format "{{.Config.Labels}}" 0d0dc58585ff
map[]

I have the same errors on image or containers, with or without labels present.
# docker inspect --format "{{.Config.Labels}}" 0f6fe6506ec2
map[wl.docker-builder.user:a512753 wl.source.changeset:5f0edffb82bf38361ed12917dccf9e7e198f8f04 wl.source.url:https://gitlab.xxxxxxx/docker/docker-builder.git wl.docker-builder.secret:xxxxxxxxxxxx]

# docker inspect --format "{{json .Config.Labels}}" 0f6fe6506ec2
Template parsing error: template: :1: unclosed action

I have an another server with the same Docker version, but without this issue.
When I look at the logs, no query are sent to the Docker Server with using format JSON:
# docker inspect --format "{{.Config.Labels}}" 0d0dc58585ff
Nov 18 09:17:58 xxxxx docker: time="2015-11-18T09:17:58.154997705+01:00" level=info msg="GET /v1.20/containers/0d0dc58585ff/json"
map[]

# docker inspect --format "{{json .Config.Labels}}" 0d0dc58585ff
Template parsing error: template: :1: unclosed action

Please find below some information on my machine:
uname -a
Linux xxxxxx 3.10.0-229.7.2.el7.x86_64 #1 SMP Tue Jun 23 22:06:11 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

# docker version
Client:
 Version:      1.8.2
 API version:  1.20
 Package Version: docker-1.8.2-7.el7.centos.x86_64
 Go version:   go1.4.2
 Git commit:   bb472f0/1.8.2
 Built:
 OS/Arch:      linux/amd64

Server:
 Version:      1.8.2
 API version:  1.20
 Package Version:
 Go version:   go1.4.2
 Git commit:   bb472f0/1.8.2
 Built:
 OS/Arch:      linux/amd64

# docker info
Containers: 2
Images: 29
Storage Driver: devicemapper
 Pool Name: docker-253:7-524-pool
 Pool Blocksize: 65.54 kB
 Backing Filesystem: extfs
 Data file: /dev/loop0
 Metadata file: /dev/loop1
 Data Space Used: 1.576 GB
 Data Space Total: 107.4 GB
 Data Space Available: 56.27 GB
 Metadata Space Used: 2.249 MB
 Metadata Space Total: 2.147 GB
 Metadata Space Available: 2.145 GB
 Udev Sync Supported: true
 Deferred Removal Enabled: false
 Data loop file: /var/lib/docker/devicemapper/devicemapper/data
 Metadata loop file: /var/lib/docker/devicemapper/devicemapper/metadata
 Library Version: 1.02.93-RHEL7 (2015-01-28)
Execution Driver: native-0.2
Logging Driver: json-file
Kernel Version: 3.10.0-229.7.2.el7.x86_64
Operating System: CentOS Linux 7 (Core)
CPUs: 4
Total Memory: 7.798 GiB
Name: xxxx
ID: GLD5:E5TV:HU4Q:LCVP:DK66:WNZ4:F2H6:TF6O:2R66:TDDU:L56Z:WBEC

I am running Docker on a virtual machine (VmWare)

Hi. Could you please paste in a full Info, to see what's going on?
Also, for me, now it returns a null in case there is no info to display. (1.9).
I'm guessing that there was a parse error in docker when the returned value was null (empty map) but that got fixed in 1.9. Could you please re-try this with that version?
Cheers,
Gergely.

I see this as well, running Docker 1.9.1 on Windows Mingw64.
[10:07:10] $ docker version
Client:
 Version:      1.9.1
 API version:  1.21
 Go version:   go1.4.3
 Git commit:   a34a1d5
 Built:        Fri Nov 20 17:56:04 UTC 2015
 OS/Arch:      windows/amd64

Server:
 Version:      1.10.0
 API version:  1.22
 Go version:   go1.5.3
 Git commit:   590d5108
 Built:        2016-02-04T19:55:25.696148927+00:00
 OS/Arch:      linux/amd64

[10:07:10] $ docker info
Containers: 1
Images: 295
Server Version: 1.10.0
Storage Driver: aufs
 Root Dir: /mnt/sda1/var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 204
 Dirperm1 Supported: true
Execution Driver: native-0.2
Logging Driver: json-file
Kernel Version: 4.1.17-boot2docker
Operating System: Boot2Docker 1.10.0 (TCL 6.4.1); master : b09ed60 - Thu Feb  4 20:16:08 UTC 2016
CPUs: 1
Total Memory: 996.2 MiB
Name: default
ID: 7DU3:32ZU:3O3U:UOA7:376I:O2GS:ZEGV:YGVK:6IPE:5ULI:4DD6:LBKQ
Debug mode (server): true
 File Descriptors: 10
 Goroutines: 22
 System Time: 2016-03-25T16:11:23.207214184Z
 EventsListeners: 0
 Init SHA1:
 Init Path: /usr/local/bin/docker
 Docker Root Dir: /mnt/sda1/var/lib/docker
Labels:
 provider=virtualbox

Previous reports mentioned the presence or absence of spaces, which seems to be relevant here. With spaces, I get the parsing error; without, I do not.
[10:07:10] $ docker inspect --format="{{ .State.Status }}" "foo"
Template parsing error: template: :1: unexpected unclosed action in command
[10:07:10] $ docker inspect --format="{{.State.Status}}" "foo"
exited

@shpros are you seeing the same issue on 1.10.3 (windows)? It's possible that it's a Windows issue in your case; fwiw, running the same on 1.10.3 on linux doesn't give that error

closing because there's no activity, but happy to reopen if you're still having this issue, and have more information


feat: archway

Made with reference to archway mainnet version v4.0.2

@pratikbin  you need to update .github/workflows/publish.yml and the README.md file

ser @CharlesJUDITH done


Including hammer.js breaks tap-highlight

I noticed that when I include hammer.js for use with drag open addon, tapping a menu item no longer highlights it. Together with the setSelected issue for iPhone (see pull request #403,) I can't tell if I tapped on a menu item or not.
The issue is caused because hammer.js adds -webkit-tap-highlight-color: rgba(0, 0, 0, 0); to mmenu. The fix is to re-enable tap-highlight for menu items. For example:
.mm-menu .mm-listview > li a { -webkit-tap-highlight-color: rgba(0, 0, 0, 0.2); }

Thanks, I'll look into adding the CSS


On using dark mode Copy button for code get invisible

Copy button get invisible on using dark mode.It makes harder to copy code.On light mode it works fine.

fixed.


EthStorage Devs Meeting #97 Agenda

Meeting Info

Sep 10, 2024, 11:00 UTC+8
Duration: 60 minutes
Meeting link
Anyone can comment on the agenda where they would like this to be discussed.

Agenda

Protocol/App/Research progress
BD/Marketing progress

Study Alt-DA spec and design doc
Go through L2 BLOBs PRs: https://github.com/ethstorage/optimism/pull/23 && https://github.com/ethstorage/op-geth/pull/2
Code review: https://github.com/ethstorage/ethstorage-sdk/pull/22
Study pre-confirmations: the sequencing & preconf call #1

Study the batch/frame/channel code
Submit grants for retro fund 5
Read https://oplabs.notion.site/Interop-Reasoning-about-Cross-Safety-Management-and-Reorgs-65f2d84c663947e88acfdb7a3023e91b and provide some comments to Mark
Discuss Alt-DA and its impact on finality with Qiang and Alan, and write a summary https://github.com/qizhou/research/blob/main/op/reorg.py
Revisit https://gov.optimism.io/t/introducing-backstop-grants/8031

#125 Preconf update
#121 Optimism derivation re-understanding

Read and Test commit-boost-client
Continue development on blockstm block executor.

read cannon specs:

https://github.com/ethereum-optimism/specs/blob/main/specs/fault-proof/index.md
https://github.com/ethereum-optimism/specs/blob/main/specs/fault-proof/cannon-fault-proof-vm.md

discuss about genesis inbox contract with Mark
TODO: investigate how PreimageOracle works.

https://github.com/ethstorage/storage-contracts-v1/pull/108
https://github.com/ethstorage/storage-contracts-v1/pull/110
https://github.com/ethstorage/es-node/pull/289

Fix Support optimism blob comment.
Supports obtaining hashes in batches.
Fix Supports batch acquisition of hashes.

es-node integration: https://github.com/ethstorage/es-node/issues/308

[x] Code change:

[ ] ES-Node Changes: https://github.com/ethstorage/es-node/pull/313 (Updated: support multi-shard, verify RPC data, cover mining based on memory data)

EthStorage x Taiko:

[x] investigation: read docs and go through the taiko codes
[ ] run test node and client (under test and debug)
[ ] change contract code (under test and debug)
[ ] integration test

Investigate how to fetch subclaims from calldata
Write a simple calldata decoder
Revise OP's retro5 grant
Investigate preconfirmation https://github.com/ethstorage/pm/discussions/123#discussion-7158760


bucket already exists when calling amplify init

How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
v14.19.1
Amplify CLI Version
12
What operating system are you using?
Mac
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
No
Describe the bug
When running amplify init, sometimes observe an error like "amplify-test-staging-194222-deployment already exists"

This is referring to the s3 bucket name created to hold amplify app resources.
It seems like the generated bucket name of amplify-{appName}-{envName}-{randomNumber}-deployment" is not random enough and is sometimes already used by another bucket. It succeeds when I retry the amplify init` command.
If it's possible to make the {randomNumber} section more random to reduce likelihood of naming collisions, that would prevent the issue.
Expected behavior
amplify init should always succeed without conflicting resource names
Reproduction steps
amplify init, but it's not a reliable reproduction
Project Identifier
No response
Log output

# Put your logs below this line

Additional information
No response
Before submitting, please confirm:

[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

Marking this as feature request to random number generation improvements.
But would make sense for cli to just skip the number if the bucket name already exists.


fix: Potential fix for interop with rust subscriptions

Codecov Report
Patch coverage: 50.00% and project coverage change: +0.01 :tada:

Comparison is base (a959b09) 82.98% compared to head (4a0bf4b) 83.00%.

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #418      +/-   ##
==========================================
+ Coverage   82.98%   83.00%   +0.01%
==========================================
  Files          48       48
  Lines       11874    11878       +4
  Branches     1280     1283       +3
==========================================
+ Hits         9854     9859       +5
+ Misses       2020     2019       -1

Impacted Files
Coverage Δ

src/index.ts
70.38% <50.00%> (+0.07%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


(&azcore.ResponseError{RawResponse: &http.Response{}}).Error() panics

Bug Report

import path of package in question: "github.com/Azure/azure-sdk-for-go/sdk/azcore"
SDK version: v1.9.0
output of go version: go version go1.21.4 linux/amd64

Similar issue to #21838.
The expression (&azcore.ResponseError{RawResponse: &http.Response{}}).Error() panics.  This is because runtime.Payload(&http.Response{}) panics, because it calls the standard library function io.ReadAll on a nil resp.Body and io.ReadAll doesn't nil-check its Reader (https://github.com/golang/go/issues/64714).
For completeness, note that runtime.Payload(nil) also panics because it doesn't nil-check resp, but I think that code path is not reachable via azcore.ResponseError.  It'd be nice to fix for other callers of runtime.Payload() though.
This isn't something that we see is causing a production problem (although perhaps there is a minor robustness issue in the highly improbable production case that any of these fields is not set).
But, it's something that trips us up from time to time in a unit test context - when unit testing some other behavior, it's possible to inadvertently instantiate a ResponseError that will then cause a panic when Error() is called.
If only to simplify unit testing, it would be neat if (*azcore.ResponseError) Error() did not panic on &azcore.ResponseError{RawResponse: &http.Response{}}.

We can fix this, but note that per the docs, the response body will never be nil (http.NoBody when there's no body).

Fix will be in<EMAIL_ADDRESS>to be released in early Jan.

Release will go out week of 2/5


Build Previews started failing overnight with "Executing custom build scripts is not yet implemented"

Before opening, please confirm:

[X] I have checked to see if my question is addressed in the FAQ.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

App Id
dg7jtgfxh9v63
AWS Region
eu-west-1
Amplify Hosting feature
Deployments, Frontend builds
Frontend framework
React
Next.js version
N/A
Next.js router
N/A
Describe the bug
The Preview builds started failing with the error in backend build:
Executing custom build scripts is not yet implemented

The same commit worked 23rd of August and fails 25th of August.
The thing is that the main pipeline works just fine...
Expected behavior
Without changing anything in the Amplify configuration, the builds should pass consistently.
Reproduction steps
Sorry, but there's not much to say here... one day it worked and the next it doesn't I did nothing for this to happen, so I'm not sure how to reproduce it in another environment... I'll do my best:

Have an amplify.yml file in the root folder
The main branch work
Open a branch in GitHub
Create a PR to merge to main
The Preview build for that PR fails.

Build Settings
version: 1
frontend:
  phases:
    preBuild:
      commands:
        - npm ci
    build:
      commands:
        - npm run build
  artifacts:
    baseDirectory: build
    files:
      - '**/*'
  cache:
    paths:
      - node_modules/**/*

Log output

# Put your logs below this line
2023-08-25T09:38:48.847Z [INFO]: Successfully cleaned up Git credentials
2023-08-25T09:38:48.848Z [INFO]: # Checking for Git submodules at: /codebuild/output/src3647155142/src/proppex-frontend/.gitmodules
2023-08-25T09:38:48.857Z [INFO]: # Retrieving environment cache...
2023-08-25T09:38:49.276Z [INFO]: # Retrieved environment cache
2023-08-25T09:38:49.276Z [INFO]: ---- Setting Up SSM Secrets ----
2023-08-25T09:38:49.277Z [INFO]: SSM params {"Path":"/amplify/dg7jtgfxh9v63/dev/","WithDecryption":true}
2023-08-25T09:38:49.892Z [INFO]: No live updates for this build run
2023-08-25T09:38:49.895Z [INFO]: # Retrieving cache...
2023-08-25T09:38:56.295Z [INFO]: # Extracting cache...
2023-08-25T09:39:05.747Z [INFO]: # Extraction completed
2023-08-25T09:39:05.861Z [INFO]: # Retrieved cache
                                 ## Checking for associated backend environment...
                                 ## Backend environment association found
2023-08-25T09:39:43.350Z [INFO]: Amplify AppID found: dg7jtgfxh9v63. Amplify App name is: proppex
2023-08-25T09:39:43.399Z [INFO]: Backend environment dev found in Amplify Console app: proppex
2023-08-25T09:39:46.094Z [WARNING]: - Fetching updates to backend environment: dev from the cloud.
2023-08-25T09:39:47.104Z [WARNING]: - Building resource api/proppexV1
2023-08-25T09:39:47.139Z [WARNING]: - Building resource auth/proppexAuth
2023-08-25T09:39:47.291Z [WARNING]: - Building resource auth/userPoolGroups
2023-08-25T09:39:47.462Z [WARNING]: - Building resource storage/proppexPublicBucket
2023-08-25T09:39:47.491Z [WARNING]: ✔ Successfully pulled backend environment dev from the cloud.
2023-08-25T09:39:47.810Z [WARNING]: Browserslist: caniuse-lite is outdated. Please run:
                                    npx update-browserslist-db@latest
                                    Why you should do it regularly: https://github.com/browserslist/update-db#readme
2023-08-25T09:39:47.926Z [INFO]: ✅
2023-08-25T09:39:49.292Z [INFO]: Note: It is recommended to run this command from the root of your app directory
2023-08-25T09:39:50.524Z [WARNING]: - Initializing your environment: dev
2023-08-25T09:39:51.313Z [WARNING]: - Building resource api/proppexV1
2023-08-25T09:39:51.354Z [WARNING]: - Building resource auth/proppexAuth
2023-08-25T09:39:51.527Z [WARNING]: - Building resource auth/userPoolGroups
2023-08-25T09:39:51.732Z [WARNING]: - Building resource storage/proppexPublicBucket
2023-08-25T09:39:51.765Z [WARNING]: ✔ Initialized provider successfully.
2023-08-25T09:40:13.991Z [WARNING]: ✖ There was an error initializing your environment.
2023-08-25T09:40:13.995Z [INFO]: 🛑 Executing custom build scripts is not yet implemented
2023-08-25T09:40:13.995Z [INFO]: Learn more at: https://docs.amplify.aws/cli/project/troubleshooting/
2023-08-25T09:40:13.998Z [INFO]:
2023-08-25T09:40:13.999Z [INFO]: Session Identifier: c866c4ec-b474-4e44-a9e5-4bb59f797285
2023-08-25T09:40:14.255Z [WARNING]: - Uploading files.
2023-08-25T09:40:14.262Z [WARNING]: - Uploading files.
2023-08-25T09:40:15.363Z [WARNING]: - Uploading files.
2023-08-25T09:40:26.188Z [WARNING]: - Uploading files.
2023-08-25T09:40:33.551Z [WARNING]: - Uploading files.
2023-08-25T09:40:33.562Z [WARNING]: - Uploading files.
2023-08-25T09:40:33.572Z [WARNING]: - Uploading files.
2023-08-25T09:40:34.095Z [WARNING]: - Uploading files.
2023-08-25T09:40:34.233Z [WARNING]: - Uploading files.
2023-08-25T09:40:37.078Z [WARNING]: - Uploading files.
2023-08-25T09:40:38.584Z [WARNING]: - Uploading files.
2023-08-25T09:40:39.194Z [ERROR]: !!! Build failed
2023-08-25T09:40:39.195Z [ERROR]: !!! Non-Zero Exit Code detected
2023-08-25T09:40:39.195Z [INFO]: # Starting environment caching...
2023-08-25T09:40:39.195Z [INFO]: # Uploading environment cache artifact...
2023-08-25T09:40:39.241Z [INFO]: # Uploaded environment cache artifact
2023-08-25T09:40:39.242Z [INFO]: # Environment caching completed
Terminating logging...

Additional information
Image of the same commit working and then failing.

Same issue here.  When will this issue be assigned?

Hi @proppex 👋 , thanks for raising this!
@clownbaby We have an ongoing thread related to this GitHub issue on our Discord community server: https://discord.com/channels/705853757799399426/1145839309484740658

Duplicating what I wrote in the discord:
When I run into this error message, it's always in amplify CONSOLE CI/CD.  It happens with amplify cli 12.2.3 or latest.
Running an amplify push locally with THE SAME COMMIT will SUCCEED with amplify cli 12.2.3.
I run into this error message in console when I add a new function as a 'nodejs/npm' function with a 'build' entry in the new function's build.json.
This USED TO work.  I have several functions that work with this configuration, in the same backend.
I also run into this error message in console when I add a new function as "nodejs/custom build script," which puts the build script in the new function's amplify.state.
The next permutation of things that should work that I'm going to try is the typescript examples in amplify documentation.
https://docs.amplify.aws/cli/function/build-options/
You can see my application d5i79jkckfr0q for lots of examples of this error breaking backend builds

New test case -- Just ran 'amplify add function' and did a git commit.  No custom build steps at all.  Just whatever 'amplify add function' added to my project.
Ran git push, and console backend build failed with 'Executing custom build scripts is not yet implemented' again.

Hi everyone 👋 , thanks for your continued cooperation. Here is a brief summary on the issue:
Pain Point
Amplify backend builds for standard and preview branches are failing with Executing custom build scripts is not yet implemented.
Root Cause
The custom build feature was introduced by amplify-cli v12.2.0:

https://docs.amplify.aws/cli/function/build-options/
https://github.com/aws-amplify/amplify-cli/releases/tag/v12.2.0

This particular feature does not seem to be backward compatible with older amplify-cli versions. The build container in an Amplify app uses amplify-cli v10.5.2 and Node v16 by default. This can be overridden using live package updates feature by setting amplify-cli package to latest.
We identified this behavior as a bug where if you set the amplify-cli package version as latest the build environment continues to use v10.5.2 and this breaks the backend builds as we are not patching the amplify-cli version correctly.
Workaround
There are a couple of workarounds that you can leverage to unblock your builds:
Option 1

Remove the amplify-cli live package update
Add the following as the first two commands in the preBuild section of the build spec:

rm -rf ~/.amplify
npm i -g @aws-amplify/cli@latest

Option 2

Remove the node live package update
Set the amplify-cli to latest

Thank you @Jay2113 , the latter worked for me pretty fine!


setting lastTimestamp on start()

I was unable to animate anything because the library would set the targetValue immediately.
update(timestamp) is called by the browser via requestAnimationFrame. Per spec it will provide a timestamp. According to MDN, this is the same number returned by performance.now(). In my case, interactive tweens never worked, because the update() function started a few seconds in, so it always just jumped to the end of an animation. Setting this.lastTimestamp to performance.now() on start means, that the exact value of timestamp does not matter. I have tested this in current firefox (102), Edge (103) and Chromium (103). I have not tested pause() and resume().

Good catch 👍 Thank you 🐹


Proper frequency unit

What could be the proper frequency unit?

12 since the data is collected every month, so it's 12 times per year

Oh yeah, that could be proper.

I am still confused on this?

I have answered it here, https://github.com/ubsuny/23-Homework5G3/issues/19#issuecomment-1807310870


Update README.md

Update example for using datafusion-cli
How cool is this PR?

🍨  : 10
Because you can actually query this data with datafusion-cli (and this inspired a few upstream fixes https://github.com/apache/arrow-datafusion/pull/10080 https://github.com/apache/arrow-datafusion/pull/10078 https://github.com/apache/arrow-datafusion/pull/10079)

FYI @jakthom


JoelLimJing-Intro.md

This issue should be against a repo in the org nus-cs2103-AY1617S2 not against the repo in se-edu org :-)
Closing...