Linux not starting up

I need help, today I tried to start up Linux using crouton which I've had installed for about a month now.  It was working perfectly yesterday but today I tried to load it and the normal transition started but after the normal few seconds of black screen, instead of Unity Linux it brought me back to crosh.  This is the full feed
"
crosh> shell
chronos@localhost / $ sudo startunity
Entering /usr/local/chroots/precise...
_XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root
X.Org X Server 1.15.1
Release Date: 2014-04-13
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.42-75-generic x86_64 Ubuntu
Current Operating System: Linux localhost 3.8.11 #1 SMP Fri May 8 12:21:21 PDT 2015 x86_64
Kernel command line: cros_secure console= loglevel=7 init=/sbin/init cros_secure oops=panic panic=-1 root=/dev/dm-0 rootwait ro dm_verity.error_behavior=3 dm_verity.max_bios=-1 dm_verity.dev_wait=1 dm="1 vroot none ro 1,0 2506752 verity payload=PARTUUID=043bcab0-1025-3e40-b108-a02541d36d19/PARTNROFF=1 hashtree=PARTUUID=043bcab0-1025-3e40-b108-a02541d36d19/PARTNROFF=1 hashstart=2506752 alg=sha1 root_hexdigest=9c34243a267c1af24486c5915d23642a322eebf7 salt=354cef49d2003d8b6815c8a5bb4c371c5f9f79569645357355f37b8be8d67824" noinitrd vt.global_cursor_default=0 kern_guid=043bcab0-1025-3e40-b108-a02541d36d19 add_efi_memmap boot=local noresume noswap i915.modeset=1 tpm_tis.force=1 tpm_tis.interrupts=0 nmi_watchdog=panic,lapic iTCO_vendor_support.vendorsupport=3
Build Date: 12 February 2015  03:37:52PM
xorg-server 2:1.15.1-0ubuntu2~precise5 (For technical support please see http://www.ubuntu.com/support)
Current version of pixman: 0.30.2
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(++) Log file: "/tmp/Xorg.crouton.1.log", Time: Sat May 30 13:17:47 2015
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
Initializing built-in extension Generic Event Extension
Initializing built-in extension SHAPE
Initializing built-in extension MIT-SHM
Initializing built-in extension XInputExtension
Initializing built-in extension XTEST
Initializing built-in extension BIG-REQUESTS
Initializing built-in extension SYNC
Initializing built-in extension XKEYBOARD
Initializing built-in extension XC-MISC
Initializing built-in extension SECURITY
Initializing built-in extension XINERAMA
Initializing built-in extension XFIXES
Initializing built-in extension RENDER
Initializing built-in extension RANDR
Initializing built-in extension COMPOSITE
Initializing built-in extension DAMAGE
Initializing built-in extension MIT-SCREEN-SAVER
Initializing built-in extension DOUBLE-BUFFER
Initializing built-in extension RECORD
Initializing built-in extension DPMS
Initializing built-in extension X-Resource
Initializing built-in extension XVideo
Initializing built-in extension XVideo-MotionCompensation
Initializing built-in extension XFree86-VidModeExtension
Initializing built-in extension XFree86-DGA
Initializing built-in extension XFree86-DRI
Initializing built-in extension DRI2
Loading extension GLX
xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted)
setversion 1.4 failed: Permission denied
xf86: found device 0
crouton: version 1-20150511154233~master:392b84e4
release: precise
architecture: amd64
xmethod: xorg
targets: unity
host: version 6812.88.0 (Official Build) stable-channel peppy
kernel: Linux localhost 3.8.11 #1 SMP Fri May 8 12:21:21 PDT 2015 x86_64 x86_64 x86_64 GNU/Linux
freon: yes
No Chromium OS X server is available.
Running exit commands...
/usr/bin/xinit: connection to X server lost
waiting for X server to shut down Hangup
(EE) Server terminated successfully (0). Closing log file.
.
Unmounting /usr/local/chroots/precise...
chronos@localhost / $
"
Please tell me if I can fix this and if so how.

@ShadowIceStorm Try updating your chroot see https://github.com/dnschneid/crouton/wiki/Common-issues-and-reporting

Following the directions from that link you gave me I still am unable to run Linux. There was also an error somewhere but I don't know how to read crosh
"
crosh> shell
chronos@localhost / $ sudo edit-chroot -a
precise
chronos@localhost / $ sudo sh ~/Downloads/crouton -n precise -u
Downloading latest crouton installer...
######################################################################## 100.0%
Migrating data from legacy chroots directory /usr/local/chroots to /mnt/stateful_partition/crouton/chroots...
/usr/local/chroots/precise already exists; updating it...
Preparing chroot environment...
Installing brightness into the chroot...
Installing croutonpowerd into the chroot...
Installing croutonversion into the chroot...
Installing host-dbus into the chroot...
Installing host-x11 into the chroot...
Installing pulseaudio-default.pa into the chroot...
Installing croutoncycle into the chroot...
Installing croutontriggerd into the chroot...
Installing croutonxinitrc-wrapper into the chroot...
Installing setres into the chroot...
Installing xinit into the chroot...
Installing xbindkeysrc.scm into the chroot...
Installing xorg-intel-sna.conf into the chroot...
Installing xserverrc into the chroot...
Installing xserverrc-xorg into the chroot...
Installing xserverrc-local.example into the chroot...
Installing startunity into the host...
Installing crouton-noroot into the chroot...
Installing startunity into the chroot...
Installing gnome-session-wrapper into the chroot...
Installing crouton-unity-autostart into the chroot...
Installing unity-autostart.desktop into the chroot...
Installing unity-profiled into the chroot...
Installing enter-chroot into the host...
Installing delete-chroot into the host...
Installing edit-chroot into the host...
Installing mount-chroot into the host...
Installing unmount-chroot into the host...
Installing crash_reporter_wrapper into the host...
dpkg: dependency problems prevent configuration of libatspi2.0-0:amd64:
libatspi2.0-0:amd64 depends on libc6 (>= 2.7); however:
Package libc6:amd64 is not installed.
libatspi2.0-0:amd64 depends on libglib2.0-0 (>= 2.37.3); however:
Version of libglib2.0-0:amd64 on system is 2.32.4-0ubuntu1.
dpkg: error processing package libatspi2.0-0:amd64 (--configure):
dependency problems - leaving unconfigured
Setting up libgtk-3-common (3.10.8-0ubuntu1.4) ...
dpkg: dependency problems prevent configuration of libcairo2:amd64:
libcairo2:amd64 depends on libc6 (>= 2.14); however:
Package libc6:amd64 is not installed.
dpkg: error processing package libcairo2:amd64 (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libpython3.4-minimal:amd64:
libpython3.4-minimal:amd64 depends on libc6 (>= 2.14); however:
Package libc6:amd64 is not installed.
dpkg: error processing package libpython3.4-minimal:amd64 (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libgraphite2-3:amd64:
libgraphite2-3:amd64 depends on libc6 (>= 2.14); however:
Package libc6:amd64 is not installed.
dpkg: error processing package libgraphite2-3:amd64 (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libgdk-pixbuf2.0-0:amd64:
libgdk-pixbuf2.0-0:amd64 depends on libc6 (>= 2.14); however:
Package libc6:amd64 is not installed.
libgdk-pixbuf2.0-0:amd64 depends on libglib2.0-0 (>= 2.37.6); however:
Version of libglib2.0-0:amd64 on system is 2.32.4-0ubuntu1.
dpkg: error processing package libgdk-pixbuf2.0-0:amd64 (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libjson-c2:amd64:
libjson-c2:amd64 depends on libc6 (>= 2.14); however:
Package libc6:amd64 is not installed.
dpkg: error processing package libjson-c2:amd64 (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of glib-networking:amd64:
glib-networking:amd64 depends on libc6 (>= 2.14); however:
Package libc6:amd64 is not installed.
glib-networking:amd64 depends on libglib2.0-0 (>= 2.39.4); however:
Version of libglib2.0-0:amd64 on system is 2.32.4-0ubuntu1.
dpkg: error processing package glib-networking:amd64 (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libudev1:amd64:
libudev1:amd64 depends on libc6 (>= 2.17); however:
Package libc6:amd64 is not installed.
dpkg: error processing package libudev1:amd64 (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libapt-inst1.5:amd64:
libapt-inst1.5:amd64 depends on libc6 (>= 2.14); however:
Package libc6:amd64 is not installed.
dpkg: error processing package libapt-inst1.5:amd64 (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of gtk3-engines-unico:amd64:
gtk3-engines-unico:amd64 depends on libc6 (>= 2.2.5); however:
Package libc6:amd64 is not installed.
gtk3-engines-unico:amd64 depends on libcairo2 (>= 1.10); however:
Package libcairo2:amd64 is not configured yet.
gtk3-engines-unico:amd64 depends on libglib2.0-0 (>= 2.37.3); however:
Version of libglib2.0-0:amd64 on system is 2.32.4-0ubuntu1.
dpkg: error processing package gtk3-engines-unico:amd64 (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libgirepository-1.0-1:
libgirepository-1.0-1 depends on libc6 (>= 2.14); however:
Package libc6:amd64 is not installed.
libgirepository-1.0-1 depends on libglib2.0-0 (>= 2.39.0); however:
Version of libglib2.0-0:amd64 on system is 2.32.4-0ubuntu1.
dpkg: error processing package libgirepository-1.0-1 (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libcgmanager0:amd64:
libcgmanager0:amd64 depends on libc6 (>= 2.2.5); however:
Package libc6:amd64 is not installed.
dpkg: error processing package libcgmanager0:amd64 (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libpangocairo-1.0-0:amd64:
libpangocairo-1.0-0:amd64 depends on libc6 (>= 2.4); however:
Package libc6:amd64 is not installed.
libpangocairo-1.0-0:amd64 depends on libcairo2 (>= 1.12.10); however:
Package libcairo2:amd64 is not configured yet.
libpangocairo-1.0-0:amd64 depends on libglib2.0-0 (>= 2.37.3); however:
Version of libglib2.0-0:amd64 on system is 2.32.4-0ubuntu1.
libpangocairo-1.0-0:amd64 depends on libpango-1.0-0 (>= 1.32.4); however:
Package libpango-1.0-0 is not installed.
dpkg: error processing package libpangocairo-1.0-0:amd64 (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libgtk-3-0:amd64:
libgtk-3-0:amd64 depends on libc6 (>= 2.14); however:
Package libc6:amd64 is not installed.
libgtk-3-0:amd64 depends on libcairo2 (>= 1.13.0~20140204); however:
Package libcairo2:amd64 is not configured yet.
libgtk-3-0:amd64 depends on libgdk-pixbuf2.0-0 (>= 2.27.1); however:
Package libgdk-pixbuf2.0-0:amd64 is not configured yet.
libgtk-3-0:amd64 depends on libglib2.0-0 (>= 2.39.4); however:
Version of libglib2.0-0:amd64 on system is 2.32.4-0ubuntu1.
libgtk-3-0:amd64 depends on libpango-1.0-0 (>= 1.32.4); however:
Package libpango-1.0-0 is not installed.
libgtk-3-0:amd64 depends on libpangocairo-1.0-0 (>= 1.32.4); however:
Package libpangocairo-1.0-0:amd64 is not configured yet.
dpkg: error processing package libgtk-3-0:amd64 (--configure):
dependency problems - leaving unconfigured
Setting up gsettings-desktop-schemas (3.10.1-0ubuntu1) ...
dpkg: dependency problems prevent configuration of libpango1.0-0:amd64:
libpango1.0-0:amd64 depends on libpango-1.0-0 (= 1.36.3-1ubuntu1.1); however:
Package libpango-1.0-0 is not installed.
libpango1.0-0:amd64 depends on libpangocairo-1.0-0 (= 1.36.3-1ubuntu1.1); however:
Package libpangocairo-1.0-0:amd64 is not configured yet.
libpango1.0-0:amd64 depends on libpangoxft-1.0-0 (= 1.36.3-1ubuntu1.1); however:
Package libpangoxft-1.0-0 is not installed.
libpango1.0-0:amd64 depends on libpangox-1.0-0 (>= 0.0.2-2~); however:
Package libpangox-1.0-0 is not installed.
dpkg: error processing package libpango1.0-0:amd64 (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libjbig0:amd64:
libjbig0:amd64 depends on libc6 (>= 2.4); however:
Package libc6:amd64 is not installed.
dpkg: error processing package libjbig0:amd64 (--configure):
dependency problems - leaving unconfigured
Setting up ttf-freefont (20120503-4) ...
dpkg: dependency problems prevent configuration of libtiff5:amd64:
libtiff5:amd64 depends on libc6 (>= 2.14); however:
Package libc6:amd64 is not installed.
libtiff5:amd64 depends on libjbig0 (>= 2.0); however:
Package libjbig0:amd64 is not configured yet.
dpkg: error processing package libtiff5:amd64 (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libharfbuzz0b:amd64:
libharfbuzz0b:amd64 depends on libc6 (>= 2.14); however:
Package libc6:amd64 is not installed.
libharfbuzz0b:amd64 depends on libgraphite2-3 (>= 1.2.2); however:
Package libgraphite2-3:amd64 is not configured yet.
dpkg: error processing package libharfbuzz0b:amd64 (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of librsvg2-2:amd64:
librsvg2-2:amd64 depends on libc6 (>= 2.4); however:
Package libc6:amd64 is not installed.
librsvg2-2:amd64 depends on libcairo2 (>= 1.2.4); however:
Package libcairo2:amd64 is not configured yet.
librsvg2-2:amd64 depends on libgdk-pixbuf2.0-0 (>= 2.22.0); however:
Package libgdk-pixbuf2.0-0:amd64 is not configured yet.
librsvg2-2:amd64 depends on libglib2.0-0 (>= 2.37.3); however:
Version of libglib2.0-0:amd64 on system is 2.32.4-0ubuntu1.
librsvg2-2:amd64 depends on libpango-1.0-0 (>= 1.36.0); however:
Package libpango-1.0-0 is not installed.
librsvg2-2:amd64 depends on libpangocairo-1.0-0 (>= 1.36.0); however:
Package libpangocairo-1.0-0:amd64 is not configured yet.
dpkg: error processing package librsvg2-2:amd64 (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of glib-networking-services:
glib-networking-services depends on libc6 (>= 2.2.5); however:
Package libc6:amd64 is not installed.
glib-networking-services depends on libglib2.0-0 (>= 2.39.3); however:
Version of libglib2.0-0:amd64 on system is 2.32.4-0ubuntu1.
dpkg: error processing package glib-networking-services (--configure):
dependency problems - leaving unconfigured
Setting up libgdk-pixbuf2.0-common (2.30.7-0ubuntu1) ...
dpkg: dependency problems prevent configuration of librsvg2-common:amd64:
librsvg2-common:amd64 depends on libc6 (>= 2.2.5); however:
Package libc6:amd64 is not installed.
librsvg2-common:amd64 depends on libgdk-pixbuf2.0-0 (>= 2.22.0); however:
Package libgdk-pixbuf2.0-0:amd64 is not configured yet.
librsvg2-common:amd64 depends on librsvg2-2 (= 2.40.2-1); however:
Package librsvg2-2:amd64 is not configured yet.
dpkg: error processing package librsvg2-common:amd64 (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libgtk-3-bin:
libgtk-3-bin depends on libc6 (>= 2.2.5); however:
Package libc6:amd64 is not installed.
libgtk-3-bin depends on libglib2.0-0 (>= 2.37.5); however:
Version of libglib2.0-0:amd64 on system is 2.32.4-0ubuntu1.
libgtk-3-bin depends on libgtk-3-0 (>= 3.10.8-0ubuntu1.4); however:
Package libgtk-3-0:amd64 is not configured yet.
dpkg: error processing package libgtk-3-bin (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libatk1.0-0:amd64:
libatk1.0-0:amd64 depends on libc6 (>= 2.2.5); however:
Package libc6:amd64 is not installed.
libatk1.0-0:amd64 depends on libglib2.0-0 (>= 2.37.3); however:
Version of libglib2.0-0:amd64 on system is 2.32.4-0ubuntu1.
dpkg: error processing package libatk1.0-0:amd64 (--configure):
dependency problems - leaving unconfigured
Setting up glib-networking-common (2.40.0-1) ...
dpkg: dependency problems prevent configuration of libwayland-client0:amd64:
libwayland-client0:amd64 depends on libc6 (>= 2.14); however:
Package libc6:amd64 is not installed.
dpkg: error processing package libwayland-client0:amd64 (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of gir1.2-glib-2.0:
gir1.2-glib-2.0 depends on libgirepository-1.0-1 (>= 1.40.0-1ubuntu0.2); however:
Package libgirepository-1.0-1 is not configured yet.
gir1.2-glib-2.0 depends on libglib2.0-0 (>= 2.39.91); however:
Version of libglib2.0-0:amd64 on system is 2.32.4-0ubuntu1.
dpkg: error processing package gir1.2-glib-2.0 (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libwayland-cursor0:amd64:
libwayland-cursor0:amd64 depends on libc6 (>= 2.14); however:
Package libc6:amd64 is not installed.
libwayland-cursor0:amd64 depends on libwayland-client0 (>= 1.3.92); however:
Package libwayland-client0:amd64 is not configured yet.
dpkg: error processing package libwayland-cursor0:amd64 (--configure):
dependency problems - leaving unconfigured
Setting up ttf-dejavu-core (2.34-1ubuntu1) ...
dpkg: dependency problems prevent configuration of libxkbcommon0:amd64:
libxkbcommon0:amd64 depends on libc6 (>= 2.17); however:
Package libc6:amd64 is not installed.
dpkg: error processing package libxkbcommon0:amd64 (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libpangoft2-1.0-0:amd64:
libpangoft2-1.0-0:amd64 depends on libc6 (>= 2.2.5); however:
Package libc6:amd64 is not installed.
libpangoft2-1.0-0:amd64 depends on libglib2.0-0 (>= 2.37.3); however:
Version of libglib2.0-0:amd64 on system is 2.32.4-0ubuntu1.
libpangoft2-1.0-0:amd64 depends on libharfbuzz0b (>= 0.9.9); however:
Package libharfbuzz0b:amd64 is not configured yet.
libpangoft2-1.0-0:amd64 depends on libpango-1.0-0 (>= 1.36.0); however:
Package libpango-1.0-0 is not installed.
dpkg: error processing package libpangoft2-1.0-0:amd64 (--configure):
dependency problems - leaving unconfigured
Setting up gnome-desktop3-data (3.8.4-0ubuntu3.1) ...
dpkg: dependency problems prevent configuration of cron:
cron depends on libc6 (>= 2.7); however:
Package libc6:amd64 is not installed.
dpkg: error processing package cron (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libjson0:amd64:
libjson0:amd64 depends on libjson-c2; however:
Package libjson-c2:amd64 is not configured yet.
dpkg: error processing package libjson0:amd64 (--configure):
dependency problems - leaving unconfigured
Setting up libatk1.0-data (2.10.0-2ubuntu2) ...
dpkg: error processing package libc6:i386 (--configure):
package libc6:i386 cannot be configured because libc6:amd64 is not ready (current status 'half-installed')
dpkg: dependency problems prevent configuration of libatk-bridge2.0-0:amd64:
libatk-bridge2.0-0:amd64 depends on libatk1.0-0 (>= 2.10.0); however:
Package libatk1.0-0:amd64 is not configured yet.
libatk-bridge2.0-0:amd64 depends on libatspi2.0-0 (>= 2.9.90); however:
Package libatspi2.0-0:amd64 is not configured yet.
libatk-bridge2.0-0:amd64 depends on libc6 (>= 2.4); however:
Package libc6:amd64 is not installed.
libatk-bridge2.0-0:amd64 depends on libglib2.0-0 (>= 2.37.3); however:
Version of libglib2.0-0:amd64 on system is 2.32.4-0ubuntu1.
dpkg: error processing package libatk-bridge2.0-0:amd64 (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libgnome-desktop-3-7:
libgnome-desktop-3-7 depends on libc6 (>= 2.14); however:
Package libc6:amd64 is not installed.
libgnome-desktop-3-7 depends on libcairo2 (>= 1.2.4); however:
Package libcairo2:amd64 is not configured yet.
libgnome-desktop-3-7 depends on libgdk-pixbuf2.0-0 (>= 2.22.0); however:
Package libgdk-pixbuf2.0-0:amd64 is not configured yet.
libgnome-desktop-3-7 depends on libglib2.0-0 (>= 2.37.3); however:
Version of libglib2.0-0:amd64 on system is 2.32.4-0ubuntu1.
libgnome-desktop-3-7 depends on libgtk-3-0 (>= 3.3.6); however:
Package libgtk-3-0:amd64 is not configured yet.
dpkg: error processing package libgnome-desktop-3-7 (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of gir1.2-freedesktop:
gir1.2-freedesktop depends on gir1.2-glib-2.0 (= 1.40.0-1ubuntu0.2); however:
Package gir1.2-glib-2.0 is not configured yet.
dpkg: error processing package gir1.2-freedesktop (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
libatspi2.0-0:amd64
libcairo2:amd64
libpython3.4-minimal:amd64
libgraphite2-3:amd64
libgdk-pixbuf2.0-0:amd64
libjson-c2:amd64
glib-networking:amd64
libudev1:amd64
libapt-inst1.5:amd64
gtk3-engines-unico:amd64
libgirepository-1.0-1
libcgmanager0:amd64
libpangocairo-1.0-0:amd64
libgtk-3-0:amd64
libpango1.0-0:amd64
libjbig0:amd64
libtiff5:amd64
libharfbuzz0b:amd64
librsvg2-2:amd64
glib-networking-services
librsvg2-common:amd64
libgtk-3-bin
libatk1.0-0:amd64
libwayland-client0:amd64
gir1.2-glib-2.0
libwayland-cursor0:amd64
libxkbcommon0:amd64
libpangoft2-1.0-0:amd64
cron
libjson0:amd64
libc6:i386
libatk-bridge2.0-0:amd64
libgnome-desktop-3-7
gir1.2-freedesktop
Failed to complete chroot setup.
Unmounting /mnt/stateful_partition/crouton/chroots/precise...
"

You have update problems you need to solve. Use sudo enter-chroot -n precise then resolve your problems on the chroot command line, until you can successfully run the following command there. sudo apt-get update && sudo apt-get upgrade Then try updating your chroot again with the command sudo sh ~/Downloads/crouton -n precise -u in a crosh shell like you did above. I don't know what you installed or maybe added other apt sources that would get you those dpkg errors. However googling them will most likely give you an answer to solve those.

Alright thanks

Why is this open now?

Can this be shut yet?


Airflow 1413 Fix FTPSensor failing on error message with unexpected text.

Dear Airflow maintainers,
Please accept this PR. I understand that it will not be reviewed until I have checked off all the steps below fixing the issue outlined in https://issues.apache.org/jira/browse/AIRFLOW-1413
The FTPSensor relies on an error message returned by the FTPHook. The expected message is "Can't check for file existence" and is used to check for errors in following way:
try:
hook.get_mod_time(self.path)
except ftplib.error_perm as e:
error = str(e).split(None, 1)
if error[1] != "Can't check for file existence":
raise e
However on my system (Linux/Antregos) this message text is different, leading to inevitable dag termination. Moreover the actual format of the exception on my system is different and the split returns '-' instead of the actual message.
This patch changes the operation to inspect error code rather than message text.
It also adds option to ignore certain classes of errors such as Host Unavailable that are recoverable, thus the performed action can and should be retried according to ftp spec. The default setting is to fail on all errors in order to preserve current behaviour.
Additional test cases added in contrib/sensors/test_ftp_sensor.py

Codecov Report

Merging #2450 into master will increase coverage by 0.02%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #2450      +/-   ##
==========================================
+ Coverage    69.4%   69.43%   +0.02%
==========================================
  Files         146      146
  Lines       11289    11289
==========================================
+ Hits         7835     7838       +3
+ Misses       3454     3451       -3

Impacted Files
Coverage Δ

airflow/jobs.py
76.62% <0%> (+0.29%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 751e936...1c6e352. Read the comment docs.

@Fokko

(Better late than never with a review right? Sorry it took sooooo long!)

(Better late than never with a review right? Sorry it took sooooo long!)

lol:) I forgot about this PR... will do the changes. Thanks.

Restarted the failed job to check if the error is transient

seems like all checks passed...:)


UHF-7219: 3.x release

Notes:

Figure out how to update existing image styles to use breakpoint group provided by helfi_image_styles module.
Translations (config/install)
Uninstall token filter module
Check all hook_enable_paragraph_fields() hooks
Install hook for blocks
Document manual changes required to paragraph field storage configs, for example: field.storage.paragraph.field_columns_right_column.yml requires

dependencies:
  enforced:
    config:
      - paragraphs.paragraphs_type.columns

Closed in favor of 3.x branch.


Support English spelling - LICENCE

https://github.com/microcosm-cc/bluemonday/pull/46 seems to be relevant. /cc @dorsha

Thanks!

Renamed mine anyway :)


Fix a regression due to #104: mdbook clean would delete the entire local repo

fixes #112

Note that after pulling this, if you have built the book with a revision that includes #104, you should delete the html and linkcheck directories in the root. (I could have left those in .gitignore, but I figured this would affect very few people.)


faster find_loading_address

Hello, this commit is to make find_loading_address faster.
It's complexity optimized from O(MNdefault_check_count) to O(M*N)

Hello, @liumuqing
Sorry for the delay, I tested your code and it can't find the load address with this firmware file. (please disable quick_test method before tests)
➜  example_firmware git:(master) ✗ r2 -a ppc -b 32 image_vx6_ppc_big_endian.bin
 -- Don't wait for Travis
[0x00000000]> #!pipe python3 ../firmware_tools/vxhunter_r2_py3.py
Running with python version: 3.7.7 (default, Mar 10 2020, 15:43:03)
[Clang 11.0.0 (clang-1<IP_ADDRESS>)]
Auto detected VxWorks version: None
Please input the VxWorks main version type 'c' to exit
Available (5/6/c): 6
vx_version:6
firmware_path: image_vx6_ppc_big_endian.bin
[INFO    ][vxhunter_r2_py3.find_symbol_table] symbol table start offset: 0xd35d34
[INFO    ][vxhunter_r2_py3.find_symbol_table] symbol table end offset: 0xde8c68
[INFO    ][vxhunter_r2_py3._check_vxworks_endian] VxWorks endian: Big endian

###### Start analyze firmware ######
[INFO    ][vxhunter_r2_py3.find_string_table_by_key_function_index] found string table start address at 0xc034e8
[INFO    ][vxhunter_r2_py3.find_string_table_by_key_function_index] found string table end at 0xcd6e34
[INFO    ][vxhunter_r2_py3.find_string_table_by_key_function_index] found a string tab at: 0xc034e8 to 0xcd6e34
[INFO    ][vxhunter_r2_py3.find_loading_address] Start analyse
[ERROR   ][vxhunter_r2_py3.find_loading_address] We didn't find load address in this firmware, sorry!
Can't find image load address, exit.
[0x00000000]>

Please reopen an PR to the dev branch and skip file vx_target_standalone.py, this file is outdated.

I see, let me close pr first


Update emailservice Dockerfile to use alpine and multistage build

Changes
Once again some updates to one of the Dockerfiles, this time for emailservice (ruby):

Do a multistage build
Use alpine

This brings down the image size to 90MB (from 447MB) on arm64 and the build time improves (from 20 down to 12s)

447 mb and 20s build time to 90 mb and 13s. Nice!


Is there a test scenario?

I just built my first usbvalve and was wondering if there is a test scenario that is available to see the possible issue that can show up on the screen, and to make sure that everything works?

To test on the pc, you can simply connect it and, for example, access the readme or delete it, or copy a file to it.
You can test the host usb, e.g. with a keyboard, mouse or usb stick.
Google is your friend when it comes to RubberDuckies, there are relatively simple DIY options

Yep, thanks @NagelTuev that was exactly what I would have suggested.


reanimate-svg: disable tests & unmark broken

Description of changes
I discovered that reanimate-svg is not actually broken, just the tests are; I believe this is since they depend on an external tool.
I unmarked it as broken and disabled tests on it.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

@schuelermine Thanks for sending this.  A couple requests:

Could you rebase this on the haskell-updates branch?  We normally ask all haskell-related changes to be merged into that branch.  We have a separate release process for merging haskell-updates into master: https://github.com/NixOS/nixpkgs/pull/178022
pkgs/development/haskell-modules/hackage-packages.nix generally shouldn't be edited by hand, since it is automatically generated.  Instead, you can run maintainers/scripts/haskell/regenerate-hackage-packages.sh in order to regenerate it.
You should add dontCheck for reanimate-svg in pkgs/development/haskell-modules/configuration-common.nix.  Grep through that file for dontCheck to see how other packages do it.  Also make sure to add a comment for why dontCheck is necessary.

@sternenseemann How do you do that?

Regenerate it from what?

The current hackage state, as well as a bunch of files in pkgs/development/haskell-modules that are used as inputs.  Although that shouldn't matter for this PR.  But definitely feel free to read through that script to see exactly what is going on.

How do you do that? It seems like these packages only define Haskell dependencies

Here's the first example I found:
https://github.com/NixOS/nixpkgs/blob/e1e08fe28bf0588a41cd556eac40b98d2793da99/pkgs/development/haskell-modules/configuration-nix.nix#L121-L124
This kind of thing can sometimes be a little tricky to get right, so feel free to ask questions if you get stuck or have problems.

How do you unmark it as broken without manually editing the autogenerated file?

@schuelermine
That's correct!  Remove the package from configuration-hackage2nix/broken.yaml and re-run maintainers/scripts/haskell/regenerate-hackage-packages.sh.

I have no clue why these tests fail. Here is a log.
https://gist.github.com/1176b5db51180aefff059dfb39b7cba9

I found out what the problem is, but I don’t know why it arises.
This image

when cycled through reanimate-svg is rendered instead as

…but I have no clue why this would happen here and not elsewhere. The only guess I have is that rsvg-convert itself is busted somehow.

Maybe it’s the version of rsvg-convert? Nixpkgs is 2.54.3 & Ubuntu is 2.50.7.

@schuelermine Thanks for looking into us.
For the maintainers of the Haskell stuff in Nixpkgs, our biggest concern is that we accidentally mark a package unbroken, when really it is broken.  In general, we are somewhat concerned about marking a package as dontCheck when it seems like the tests (and library itself) may actually be broken.
I don't know enough about reanimate-svg or librsvg to know how to handle this situation you're seeing.  We could just mark it dontCheck and be done with it, but we ideally don't want to introduce known-broken packages to our users.  After having played around with it, what is your feeling here?  Does it seem like reanimate-svg may actually be broken here in Nixpkgs?
Also, if you're having trouble here, I'd really suggest creating an issue upstream.  The upstream maintainer may be able to easily say something like, "oh this isn't a problem in practice, feel free to disable the tests".  We could at least link to that discussion in a comment when marking reanimate-svg as dontCheck.

@cdepillabout I tested some more and I’m 99% certain that the issue is with rsvg-convert. I bundled the Nixpkgs-built rsvg-convert with nix bundle and copied it to my Ubuntu VM, and the exact same tests fail.

Nice digging!
Sounds like even more reason to open up an issue upstream (or maybe one on both the reanimate-svg and librsvg repos).

I made an issue: https://github.com/reanimate/reanimate-svg/issues/42


[One Time Password] Quick insert

Extension
https://www.raycast.com/lachero/one-time-password
Description
Add a shortcut (cmd+enter) which automatically inserts the value in the last focused input instead of adding it to the clipboard.
Who will benefit from this feature?

quicker and easier usage
everybody who don't want to change their clipboard
clipboard readers can't access it anymore
there is no more accidentally pasted keys

Anything else?
No response

Can you elaborate? I'm not sure I got it

Sure. So the current behavior is something like this:

press cmd + space (Open Raycast)
press o + enter (my alias for the extension)
select the OTP you want to insert
press enter to copy
select the input where the OTP is needed
press ctr+v to insert

And the feature would work something like this:
1. open a login form and put your cursor in the input where the OTP is needed
2. press cmd + space (Open Raycast)
3. press o + enter (my alias for the extension)
4. select the OTP you want to insert
5. press a shortcut (my suggestion is cmd+enter but that is used now for other stuff so shift+enter is probably better) to insert
6. the OTP is inserted into the previously focused input
The idea came from the Authy OTP extension but their desktop app is discontinued and it had some network request when you open it in raycast which is now blocked by my company so I can't use it anymore.
I'm guessing that the way they implemented it is to simulate keyboard presses to avoid touching the clipboard.
The speed gain while marginal still felt easier and your clipboard is safe in 2 sense. Your OTP was never there so attackers can't access it that way and your workflow is not interrupted when let's say you had something on your clipboard but the page you wanted to insert it showed a login prompt.

Got it, will take a look into it

I realised that raycast uses React so I can just implement these so I made a PR about it #13003


updated webpack  for icons

created default icons in src/resources/icons

thanks @effordDev :dancers:


alignment issue placeholder

Description
alignment issue in search placeholder
Steps to reproduce
go to website and go on contributor page.
Screenshots

Desktop (please complete the following information)
No response
Smartphone (please complete the following information)
No response
Additional information
No response
Record

[X] I agree to follow this project's Code of Conduct
[X] I have checked the existing issues
[X] I'm a GSSoC'23 contributor
[X] I want to work on this issue

Hi @biplavmz, please add some more minor issues to this or solve this with another minor issue as this is a one line fix

ok @narayan954

Hii @narayan954
want to redesign search result
before:-

After :-

Hii @narayan954 want to redesign search result before:-
After :-

Hi @biplavmz instead of changing border radius, try to fix the card alignment, as they're not completely at center, there's some space off on one side

ok @narayan954


Connections and Comparers

Hello,
Is it possible to save information on connections and/or comparers in the .txt or .xlsx file? Or how to include them by hand in the .txt or .xlsx file?
Thanks in advance
R

Hello,
I have the same issue with saving information about connections and comparers. Mb is it possible to make change in the code?


Error in running Introduction to Submodular Optimization tutorial: AttributeError: 'FeatureBasedSelection' object has no attribute 'indices'

AttributeError                            Traceback (most recent call last)
 in
3 selector = FeatureBasedSelection(20)
4 selector.fit_transform(X_shap)
----> 5 Xi2 = X[selector.indices]
6 yi2 = y[selector.indices]
7
AttributeError: 'FeatureBasedSelection' object has no attribute 'indices'

Thanks for the report. I think you meant the tutorial "3. Model-Based Selection." I reproduced the error and updated the code cells to use model.ranking rather than model.indices.

Thanks for the update. Yes, I meant Model-Based Selection.


PAT analysis notebook

I added some comments to make things clearer and added labels, etc. to the plots.
There was also an odd line in pat_fitting.pre_process_pat that I commented out. @CJvanDiepen can you please check if it's ok to remove it? Also, can you please have a look at the detect_peaks function and the last section of the example where it is used? there's still a question whether the period is needed, and currently the function is returning an empty dictionary which I don't understand. It might also be good to somehow show the weights in the example.
@peendebak

@jpdehollain Taking out the commented out line which overwrites y_data in pre_process_pat looks fine to me, especially if the example notebook looks good after it.
I cleaned up the last cell in the jupyter notebook where the detect_peaks functions is being demonstrated.
I adjusted the weights in detect_peaks such that they are correct. However they are not being used in the fit_pat function, hence I would not add them to the documentation in the jupyter notebook. Removing them completely would be a pity, because in principle assigning weights to the detected peaks looks like a good approach to me, hence they might be used again, possibly after adjusting the way there are calculated, in the future.

@peendebak @jpdehollain That sounds good to me as well!


Published version v1.0.0-beta1 takes precedence over v1.0.0-beta.2

I don't know what caused this, since I see no tag v1.0.0-beta1, but according to semver v1.0.0-beta1 (notice the missing dot) will always take precedence over anything after a dot (like v1.0.0-beta.2).
https://pkg.go.dev/github.com/tetratelabs/wazero?tab=versions

The solution is to withdraw v1.0.0-beta1 (which I don't know how to do) or to not use the dot going forward.

yeah that tag was an accident and go.mod didn't like it.. I'll look into seeing if there's a way to sort that out

https://go.dev/ref/mod#go-mod-file-retract will try this

later fixed up to
// Wrong naming convention
retract v1.0.0-beta1

// Has memory bug and quickly fixed in v1.0.0-beta.2.
retract v1.0.0-beta.1

Note that #790 is not sufficient.
You now need to tag this retraction as v1.0.0-beta.3 (and get it into the module cache), or it never gets "published", and we never get to see the retraction.
Hence the section in https://go.dev/ref/mod#go-mod-file-retract about a retraction retracting itself.
This… is complicated.

or maybe I won't need to say the exact beta after that.. let's try first

I guess in any case we have to wait for propagation to take place. Meanwhile, I'll keep #792 to ensure folks don't paste a command to get the broken tag.

beta 3 shows up but the other tag still does too :) https://pkg.go.dev/github.com/tetratelabs/wazero?tab=versions

oh... I hope it isn't what I think it is, which is that the redacted version will stay until a release has a semver higher than it..

ok so problem is beta is dead. we can't really use the broken version pattern because if we do, it is invalid from go's mod version syntax.
We need to switch to a word lexicographically later than beta

suggesting on gophers slack #wazero channel to use "pre" as that allows us to use "rc" later, and also gets us into a position where people won't accidentally upgrade into a broken version

going with "pre" as it is literally the example given for a pre-release and also comes before rc which we'll almost surely want prior to real 1.0 https://go.dev/ref/mod#glos-pre-release-version

https://github.com/tetratelabs/wazero/pull/792

ok it isn't in the public versions cache, yet, but at least considered an upgrade :)
$ go get -u<EMAIL_ADDRESS>go: downloading github.com/tetratelabs/wazero v1.0.0-pre.1
go: upgraded github.com/tetratelabs/wazero v1.0.0-beta1 => v1.0.0-pre.1

Thanks tons @ncruces!


Idea: Easy-Flows to Node-RED

Just wanted to throw an idea out there regarding workflow options given it looks like the usage of Easy Flows is still in a exploratory phase.
Node-RED is a open-source tool for wiring together APIs and services in interesting ways. It provides a browser-based editor that makes it easy to wire together flows using the wide range of nodes that can be deployed to its runtime in a single-click. There is also a OpenShift Operator available as well.
The project has been around for 10 years, backed by IBM and there are currently over 4000 nodes and flows available that can be used for just about any use case.
Documention
Example Interesting Nodes:
aws-nodes
azure-nodes
google-cloud-nodes
jenkins-nodes

The goal is to be able to hook up any workflow framework under the covers, provided that meets our contracts. So another java based workflow library could be put in place.
For Node-RED specifically, this looks to be more of a mature stand-alone product that a Parodos WorkFlowTask could call out too. Example:

Node-RED contains flows to stand up AWS
Parodos has a workflow to not only stand up AWS environments, pipelines, permissions for each of the tools (AD entitlements). Some of this can be delegated to Node-RED, others will be tasks/integrations that might be custom to the environment

The user provides code/project that Parodos assesses and an InfrastructureOption (tools/environments/permissions) is provided to the user. The user picks one of them (for example AWS + Pipelines + supporting tools + all permissions).
Under the covers Parodos will make the calls to stand it all up, including to Node-RED (were some of this logic exists). So in short, Node-RED would be a downstream client to Parodos.
We could build pre-made Parodos InfrastructureWorkFlow tasks that contain everything that is needed to make a call to Node-RED.
Does this make sense?

The goal is to be able to hook up any workflow framework under the covers, provided that meets our contracts. So another java based workflow library could be put in place.
For Node-RED specifically, this looks to be more of a mature stand-alone product that a Parodos WorkFlowTask could call out too. Example:

Node-RED contains flows to stand up AWS

Parodos has a workflow to not only stand up AWS environments, pipelines, permissions for each of the tools (AD entitlements). Some of this can be delegated to Node-RED, others will be tasks/integrations that might be custom to the environment

The user provides code/project that Parodos assesses and an InfrastructureOption (tools/environments/permissions) is provided to the user. The user picks one of them (for example AWS + Pipelines + supporting tools + all permissions).
Under the covers Parodos will make the calls to stand it all up, including to Node-RED (were some of this logic exists). So in short, Node-RED would be a downstream client to Parodos.
We could build pre-made Parodos InfrastructureWorkFlow tasks that contain everything that is needed to make a call to Node-RED.
Does this make sense?

Thanks for the detailed response. So you are not looking to limit the usage of a specific workflow tool and Parados will basically have a universal WorkflowAPI that allows you to call different WorkFlowTasks that can be extended to "open-source drivers" which is what Humanitec calls them, am I correct?
Flexibility is always good 🙂 but things can begin to get tricky when you start to come across use-cases that have tasks that have input/output dependencies where you maybe have task-1 that makes use of tool-a that needs to provide a instanceID output to task-2 that's using tool-b.
Node-RED is super extensible and almost limitless given it can be extended by creating new nodesand simply placing them into your palette.Nodes can be published as npm modules or added to the Node-RED Flow Library to make them available to the community.

"but things can begin to get tricky when you start to come across use-cases that have tasks that have input/output dependencies where you maybe have task-1 that makes use of tool-a that needs to provide a instanceID output to task-2 that's using tool-b." <- We have added support for this. Basically certain workflow steps might generate a 'manual task', like an approval, that occurs outside of the Workflow implementation. Data generated by this 'manual task', an approval ID for example, would be needed to complete the remaining of the Parodos WorkFlow tasks. We believe we have a good solution for this and will be open sourcing this enhancement soon. Just working through some user feedback on our implementation


Replace x instanceof Array with Array.isArray(x)

Assuming rewrite no longer wishes to support IE<9, this fixes #1390.

@barneycarroll Could you fix the conflicts (run npm run bundle before you commit the merge)?

@isiahmeadows I won't have access to a PC for the next 24 hours or so, sorry — if anyone else has the time and you think this is a good idea then I won't mind in the slightest if someone else forks the patch and does it under another PR…

small update: I ran the jsperf that @isiahmeadows had setup, and turns out Array.isArray is an order of magnitude slower than instanceof in Edge
I'm not sure it's a good trade-off to slow down Edge for use cases involving frames or Nashorn.

you could alias one or the other at init. best of both worlds. browser sniffing FTW.

Builds now pass if we want to allow safe cross-realm array usage

@lhorie Will it cause any actual slowdown in rendering (even in microbenchmarks)? That's much more helpful than some JSPerf test on whether Array.isArray(foo) or foo instanceof Array is faster in some super tight loop where it's the only thing.

Stick with Array.isArray(...). I did a huge amount of real-world testing on this with Inferno and it was vastly better than instanceof unless you care about IE perf still?

@barneycarroll Could you resolve these merge conflicts?

@trueadm I suspect the deopts weren't quite that simple. Not to mention that V8 Crankshaft doesn't do codegen for Array.isArray (TurboFan does), so that's another confounding factor.

@isiahmeadows done again, but if nobody gets round to merging this in the next week and it falls into conflict again might I suggest whoever wants to merge it resolves those conflicts themselves? This is a trivial PR - the only conflicts are down to build process and simply involve deleting bundled output and rebundling after merge.

Since the bundle will auto-generate after this is merged I'd say just remove mithril.js and mithril.min.js from your PR entirely.

Might be worth sticking them in gitignore if Gandalf can do that for us?

Rebased built artefacts. Ready for merge again!


fix annotation_summary slowness

For example:
400 mutations, reduce consuming time from 3m15s to 0.4s (local)

Codecov Report

Merging #280 into master will decrease coverage by 0.16%.
The diff coverage is 66.66%.

@@             Coverage Diff             @@
##             master    #280      +/-   ##
===========================================
- Coverage     18.96%   18.8%   -0.17%
+ Complexity      135     134       -1
===========================================
  Files           161     161
  Lines          2014    2010       -4
  Branches        259     258       -1
===========================================
- Hits            382     378       -4
  Misses         1599    1599
  Partials         33      33

Impacted Files
Coverage Δ
Complexity Δ

.../internal/VariantAnnotationSummaryServiceImpl.java
0% <ø> (ø)
0 <0> (ø)
:arrow_down:

...ome_nexus/service/internal/EnsemblServiceImpl.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...nexus/service/annotation/EntrezGeneIdResolver.java
75% <100%> (-1.48%)
3 <0> (-1)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 3c4e33e...337ab42. Read the comment docs.

@onursumer fixed, thanks!


Ensure that each log line is newline-terminated

When writing logs with timestamps to the terminal, ensure that each line is newline-terminated, so we don't end up with an unreadable mess with timestamps interspersed with the actual content being displayed.
An partial fix of the (easy) part of the issue from #2500

Turns this:
2019-03-03T21:01:16.219396456-05:00 2019-03-03T21:01:16.220405553-05:00 [root@2c195fd79044 /]# 2019-03-03T21:01:21.297124753-05:00
2019-03-03T21:01:21.297629293-05:00 2019-03-03T21:01:21.298103445-05:00 [root@2c195fd79044 /]# 2019-03-03T21:01:21.479471092-05:00
2019-03-03T21:01:21.480303413-05:00 2019-03-03T21:01:21.480527759-05:00 [root@2c195fd79044 /]# 2019-03-03T21:01:21.657164737-05:00

Into this:
2019-03-03T21:11:28.902196159-05:00
2019-03-03T21:11:28.902858904-05:00 [root@d5003ddef6a5 /]#
2019-03-03T21:11:29.459544487-05:00
2019-03-03T21:11:29.460010936-05:00
2019-03-03T21:11:29.460432834-05:00 [root@d5003ddef6a5 /]#
2019-03-03T21:11:29.60151061-05:00
2019-03-03T21:11:29.602178337-05:00
2019-03-03T21:11:29.602316019-05:00 [root@d5003ddef6a5 /]#

Now, we're still printing user-entered newlines on separate lines, and if I was to type in asdf each character would appear on a separate line, but this is definitely an improvement in readability

The real fix here is probably to wait until we find a newline before printing, but that will probably require a complete rewrite of the output logic for --follow, so I'm going to avoid that part today

I found a more complete solution that emulates the expected output from Docker a lot more closely (though it's not without its quirks - Docker prints only when a complete line is entered, we print any time a character is entered, but only print a timestamp at the start of the line). It's a very close approximation, aside from our timestamps not matching (Docker uses time when the enter key was pressed, we use time when the first character of the line was typed).

@mheon The change you have made so far, code looks good.  But are you done?

@rhatdan I think this is good enough. The timestamps issue is annoying, but fixing it would require a wholesale rewrite of most of this code; we can do almost everything Docker can with this five or so line change. This should be ready for merge.

@vrothberg @baude @TomSweeneyRedHat @giuseppe PTAL

LGTM

/lgtm


#369: feat - add support for alerts into Serenity-js 2.0

Hope I've done something along the right lines here Jan - feedback welcome 😄. I did have problem running the tests following npm run verify from top level project:
@integration/cucumber-2-runner: src/support/configure_serenity.ts(10,9): error TS2345: Argument of type 'ChildProcessReporter' is not assignable to parameter of type 'StageCrewMember'.
@integration/cucumber-2-runner:   Types of property 'assignedTo' are incompatible.
@integration/cucumber-2-runner:     Type '(stage: import("/Users/nick/dev/git-personal/serenity-js/integration/testing-tools/node_modules/@serenity-js/core/lib/stage/Stage").Stage) => import("serenity-js/integration/testing-tools/node_modules/@serenity-js/core/lib/stage/StageCrewMember").StageCrewMember' is not assignable to type '(stage: import("/Users/nick/dev/git-personal/serenity-js/packages/core/lib/stage/Stage").Stage) => import("/Users/nick/dev/git-personal/serenity-js/packages/core/lib/stage/StageCrewMember").StageCrewMember'.
@integration/cucumber-2-runner:       Types of parameters 'stage' and 'stage' are incompatible.
@integration/cucumber-2-runner:         Type 'import("/Users/nick/dev/git-personal/serenity-js/packages/core/lib/stage/Stage").Stage' is not assignable to type 'import("/Users/nick/dev/git-personal/serenity-js/integration/testing-tools/node_modules/@serenity-js/core/lib/stage/Stage").Stage'.
@integration/cucumber-2-runner:           Types have separate declarations of a private property 'dressingRoom'.

This looks like an incompatibility in the integration/testing-tools module which is not something I've changed?
Note that the travis build #870 does not reflect the latest version of the PR as I've force pushed a few more commits in since the first as I make adjustments ...

I'm going to close this one and hope the new one triggers builds!


Share Extension Task Failing

Hi!  We have a custom build extension that we've been deploying for 6+ months.  Today I ran a build against a new commit and the Share Extension build step fails with an error of:
No api-version was supplied for the "POST" request.  The version must be supplied either as part of the Accept header (e.g. "application/json; api-version=1.0") or as a query parameter (e.g. "?api-version=1.0").
I'm not sure if anyone else is experiencing this issue.  Help would be greatly appreciated!
I've made several attempts to fix this issue:

Re-Built a commit that was successfully deployed before.  (Same Error)
Upgraded Share Extension task version from 0.* to 1.* and rebuilt.  (Same Error)
Removed and re-added the Share Extension build task and rebuilt.  (Same Error)

Our Build/Deployment Process:

Get Sources  (Success)
Package Extension  (Success)
Publish Artifact  (Success)
Publish Extension  (Success)
Share Extension  (Error)

Error Detail:
2017-04-03T14:48:36.1924334Z Found tfx in current task folder d:\a\1\s\node_modules.bin\tfx.cmd
2017-04-03T14:48:36.1944346Z 22868630-60ed-44f4-b395-c9772bb048f2 exists true
2017-04-03T14:48:36.1976011Z [command]d:\a\1\s\node_modules.bin\tfx.cmd extension share --token ******** --service-url https://marketplace.visualstudio.com/ --publisher ***** --extension-id ***** --share-with *****
2017-04-03T14:48:36.8154271Z TFS Cross Platform Command Line Interface v0.4.1
2017-04-03T14:48:36.8154271Z Copyright Microsoft Corporation
2017-04-03T14:48:36.9124271Z error: Error: No api-version was supplied for the "POST" request. The version must be supplied either as part of the Accept header (e.g. "application/json; api-version=1.0") or as a query parameter (e.g. "?api-version=1.0").
2017-04-03T14:48:36.9274265Z ##[error]tfx failed with error: Error: d:\a\1\s\node_modules.bin\tfx.cmd failed with return code:<PHONE_NUMBER>

There is a breaking change in tfx 0.4.1 and to get unstuck, add an npm task
to execute:
npm install<EMAIL_ADDRESS>--prefix $(agent.workfolder)_tools
Answered from phone so I hope Iwrote it all correctly.
On Apr 3, 2017 7:50 PM, "tim71070"<EMAIL_ADDRESS>wrote:

Hi! We have a custom build extension that we've been deploying for 6+
months. Today I ran a build against a new commit and the Share Extension
build step fails with an error of:
No api-version was supplied for the "POST" request. The version must be
supplied either as part of the Accept header (e.g. "application/json;
api-version=1.0") or as a query parameter (e.g. "?api-version=1.0").
I'm not sure if anyone else is experiencing this issue. Help would be
greatly appreciated!
I've made several attempts to fix this issue:

Re-Built a commit that was successfully deployed before. (Same
Error)
Upgraded Share Extension task version from 0.* to 1.* and rebuilt.
(Same Error)
Removed and re-added the Share Extension build task and rebuilt.
(Same Error)

Our Build/Deployment Process:

Get Sources (Success)
Package Extension (Success)
Publish Artifact (Success)
Publish Extension (Success)
Share Extension (Error)

Error Detail:
2017-04-03T14:48:36.1924334Z Found tfx in current task folder
d:\a\1\s\node_modules.bin\tfx.cmd
2017-04-03T14:48:36.1944346Z 22868630-60ed-44f4-b395-c9772bb048f2 exists
true
2017-04-03T14:48:36.1976011Z [command]d:\a\1\s\node_modules.bin\tfx.cmd
extension share --token ******** --service-url https://marketplace.
visualstudio.com/ --publisher ***** --extension-id ***** --share-with

2017-04-03T14:48:36.8154271Z TFS Cross Platform Command Line Interface
v0.4.1
2017-04-03T14:48:36.8154271Z Copyright Microsoft Corporation
2017-04-03T14:48:36.9124271Z error: Error: No api-version was supplied for
the "POST" request. The version must be supplied either as part of the
Accept header (e.g. "application/json; api-version=1.0") or as a query
parameter (e.g. "?api-version=1.0").
2017-04-03T14:48:36.9274265Z ##[error]tfx failed with error: Error:
d:\a\1\s\node_modules.bin\tfx.cmd failed with return code:<PHONE_NUMBER>
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/vsts-extension-build-release-tasks/issues/49,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AD-uS0T6jwqDW0sM8PFPefvYmWnS4_qEks5rsTFVgaJpZM4Mx39C
.

tfx-cli 0.4.2 was just released and that fixes the problem.


Add Vertex AI support

This PR adds support for Vertex AI in Google Cloud.
At this time, the Application Default Credentials (ADC) must be set in the gcloud command to use Vertex AI.

nice pr can you provide more detail to tell us how to config with Google cloud？

@EasyChris
Below is a simple setup procedure.

Enable Vertex AI API and Claude 3.5 Sonnet model in your own project in Google Cloud Console
https://cloud.google.com/vertex-ai/generative-ai/docs/partner-models/use-claude
Install gcloud CLI and configure ADC
https://cloud.google.com/docs/authentication/provide-credentials-adc
Configure claude-dev

API Provider: GC Vertex AI
Google Cloud Project ID: <Your project ID>
Google Cloud Region: us-east5 or europe-west1

Claude 3.5 Sonnet is available in the following regions:

us-east5 (Ohio)
europe-west1 (Belgium)

It doesn't work for me. I am using Cloud Shell on Google Cloud and I set up my project id and location. When I write the prompt, it does nothing and it gets blocked.
1: I send the prompt

2: I cannot interact anymore and also don't get any feedback from the extension:

Hi @u-minor thank you for the contribution! For security reasons I don't accept PRs that change the package-lock.json, so please uninstall the @anthropic-ai/vertex-sdk package and I will install that myself after I've merged your changes.

Hi @saoudrizwan, I rebased branch and removed changes in package.json.

Hi @u-minor, Could you please add the vertex models: gemini-flash and gemini-pro within this PR?

@saoudrizwan Followed the latest main branch.

Hi @u-minor, Could you please add the vertex models: gemini-flash and gemini-pro within this PR?

@s106916 Sorry, this PR uses @anthropic-ai/vertex-sdk and is not intended for use with non-anthropic models.

@u-minor much appreiciated of your work! that is super super awesome!!! and being tested it works for me.

could we set the output token to 8192 which makes it could handling the long coding task?

could we set the output token to 8192 which makes it could handling the long coding task?

@giranntu
I tried adding a custom header in the same way as api/anthropic.ts, but could not raise max_tokens  and got the following error...
API Request Failed
400 {"type":"error","error":{"type":"invalid_request_error","message":"max_tokens: 8192 > 4096, which is the maximum allowed number of output tokens for claude-3-5-sonnet-20240620"}}

could we set the output token to 8192 which makes it could handling the long coding task?

@giranntu I tried adding a custom header in the same way as api/anthropic.ts, but could not raise max_tokens and got the following error...
API Request Failed
400 {"type":"error","error":{"type":"invalid_request_error","message":"max_tokens: 8192 > 4096, which is the maximum allowed number of output tokens for claude-3-5-sonnet-20240620"}}

thanks @u-minor  it might be the current issue for vertex AI couldn't add the additional header, and will wait if we could solve it for the future release.

Vertex does not currently support the beta features as they are pre-release and in testing, but they will be supported once GA

@saoudrizwan
Added support for service account keys.
https://github.com/saoudrizwan/claude-dev/issues/83#issuecomment-2290208269

Create a new service account in IAM & admin -> Service Accounts
e.g. claude-dev<EMAIL_ADDRESS>Create new key (JSON) for the created service account and download credential json
Attach Vertex AI User role to the created service account in IAM & admin -> IAM
base64 encode the credential json as follows
base64 -w0 ****.json

Please be careful not to use online Base64 encoding tools

I tested authentication via Service Account Key (macOS base64 does not understand -w0 btw, just leaving that out worked converting the .json file to an unbroken Base64 string)  and I can confirm that this works, Sonnet-3.5 is happily answering requests this way via Vertex AI / GCP.
BTW: I did not have to create a new Service Account for this to get this working, it worked using the "Compute Engine Default Service Account", which gets automatically created for every new project in GCP (it seems). Or is this a bad idea somehow? (I am using GCP only for a week or so, I do not really have a clue what I am doing in this complex thing, but it works for me so far)

Hi @fry69

macOS base64 does not understand -w0
Sorry, I was using the base64 coreutils version installed with homebrew.

is using this account a bad idea somehow?
As the default compute service account has a very strong ‘Editor role’, I strongly recommend creating a dedicated service account with only the ‘Vertex AI User role’.

is using this account a bad idea somehow?

As the default compute service account has a very strong Editor role, I strongly recommend creating a dedicated service account with only the Vertex AI User role.

Thank you! 👍 I'll create a new Service Account.

@giranntu
Now support 8192 tokens for claude-3-5-sonnet@20240620!
https://x.com/alexalbert__/status/1825920737326281184

what is the hold-back to get that merged

I can't speak for @saoudrizwan, but from my experience a little guidance in form of a short howto is needed to successfully connect to Claude models through Vertex AI. This is not trivial/self explanatory, IMHO.

@saoudrizwan, @u-minor has successfully addressed all concerns and added valuable features:

Vertex AI support implemented and tested
Service account key authentication added
Max tokens increased to 8192 for claude-3-5-sonnet
Package-lock.json changes removed as requested
The community is eager to use this feature. Are there any remaining blockers? If not, can we set a target date for merging?

@fry69, most GCP users are familiar with basic operations. We can proceed with this version that works for the majority, and refine based on user feedback if needed. This approach allows us to get the feature out quickly while leaving room for future improvements.
Let's aim to merge this week. The incremental improvements approach will benefit users sooner rather than later. Thanks to all contributors for their efforts and patience.

Workaround until this PR gets merged:
Build from source and generate VSIX, then install from VSIX in VSCode, with these simple instructions:
$ git clone https://github.com/saoudrizwan/claude-dev
$ cd claude-dev
$ git fetch origin pull/45/head:vertexai
$ git switch -c localbuild
$ git merge vertexai # should not produce merge errors
$ npm add google-auth-library @anthropic-ai/vertex-sdk
$ git add . && git commit -m "[WIP] add necessary dependencies"
$ npm run install:all
$ npm install -g vsce
$ vsce package

And install the generated package e.g. claude-dev-1.3.4.vsix inside VSCode.
Repeat if new version gets released (and fix possible merge conflicts).

Sorry it wasn't my intention to not accept the PR, in fact it helped me a ton. There were just a couple things I had to do differently + merge conflicts. I will try to be more ontop of PRs in the future.


runtime: significant number of bounds checks in growslice

While inspecting the runtime.growslice code I noticed that it contains a lot of bounds checks. They all come from runtime.roundupsize.
What version of Go are you using (go version)?

$ go version
go version devel go1.21-8d5065ce6e Tue May 9 11:45:59 2023 +0300 windows/amd64

However also happens with go1.20.4.
Does this issue reproduce with the latest release?
Yes and with tip.
What did you do?
Inspecting runtime.growslice and seeing:
$ go tool objdump -s runtime.growslice ./somebinary
...
  0x445f0f              488d052a320500          LEAQ type:*+45376(SB), AX
  0x445f16              488d1dfb3c0800          LEAQ runtime.buildVersion.str+720(SB), BX
  0x445f1d              0f1f00                  NOPL 0(AX)
  0x445f20              e87bd0feff              CALL runtime.gopanic(SB)
                        return uintptr(class_to_size[size_to_class128[divRoundUp(size-smallSizeMax, largeSizeDiv)]])
  0x445f25              b944000000              MOVL $0x44, CX
  0x445f2a              e891860100              CALL runtime.panicIndex(SB)
  0x445f2f              b9f9000000              MOVL $0xf9, CX
  0x445f34              e8a7860100              CALL runtime.panicIndexU(SB)
                        return uintptr(class_to_size[size_to_class8[divRoundUp(size, smallSizeDiv)]])
  0x445f39              b944000000              MOVL $0x44, CX
  0x445f3e              6690                    NOPW
  0x445f40              e87b860100              CALL runtime.panicIndex(SB)
  0x445f45              b981000000              MOVL $0x81, CX
  0x445f4a              e891860100              CALL runtime.panicIndexU(SB)
                        return uintptr(class_to_size[size_to_class128[divRoundUp(size-smallSizeMax, largeSizeDiv)]])
...

What did you expect to see?
I'm not sure how much they affect performance, but triggering that many in roundupsize does seem a bit concerning.

I tried to do the trivial patch with zero-filling the tables to exactly 256 elements https://go-review.googlesource.com/c/go/+/493796, however, I'm not convinced that this is the best way to address this. Either way, I'm willing to take a stab at fixing it.

Do you have some benchmark results for how much the CL helps? Thanks.

It might also make sense to try and see how it will interact with https://github.com/golang/go/issues/49480 and https://go-review.googlesource.com/c/go/+/493836.

Hmm, maybe it's due to needing to convert the division result into a uint8 and hence ending up emitting a MOVZX:
  msize.go:16		0x4444b1		400fb6ff		MOVZX DI, DI
  msize.go:16		0x4444b5		4c8d0504c80d00		LEAQ runtime.size_to_class8(SB), R8
  msize.go:16		0x4444bc		420fb63c07		MOVZX 0(DI)(R8*1), DI
  msize.go:16		0x4444c1		4c8d0538cc0d00		LEAQ runtime.class_to_size(SB), R8
  msize.go:16		0x4444c8		410fb73c78		MOVZX 0(R8)(DI*2), DI

Also, maybe it's possible to usa a single lookup instead of a two lookup.

I guess one option would be to teach BCE about division and calculations, such as for https://go.godbolt.org/z/ccf4Gbs8E. But, I have no clue how complicated that would be.

I haven't yet dug into the reasons for things getting slower.

My best guess is that the performance is very sensitive to code alignment on Threadripper 2950X amd64 Windows... for some reason. Anyways, I submitted the basic change.

From my experiments and benchmarks, it seems that the benefit is at most ~2ns... and almost imperceptible due to code alignment affecting benchmark results about the same.
So, it seems there's no performance win here. However, supporting division in BCE might be a good idea nevertheless.


Workspace setup

add workspace-setup script

We decided to tell the user to change the the Exercise 3 and Exercise 4 directories instead of moving files around.


Gm support

updated branch name -
Fluent 11 Support
GM Master Support
Added Testing

Ok to skip travis for now, there's a lot of threads about postgres issues on that platform.


Development website playbook

Ongoing work following https://github.com/openmicroscopy/infrastructure/pull/88 on a playbook for deploying a Jekyll-based website /cc @manics @kennethgillen

@openmicroscopy/devops Does anyone have thoughts on putting things into subdirs vs putting them all into the ansible dir?

Re https://github.com/openmicroscopy/infrastructure/pull/94#issuecomment-239819851, would the proposal be:
ansibles/playbooks/subdir1
ansibles/playbooks/subdir2
...

or rather
ansibles/subdir1/<playbook>.yml
ansibles/subdir1/host_vars/
...
ansibles/subdir2/<playbook>.yml
ansibles/subdir2/inventory/
...

and would you match the set of subdir with the listing of https://github.com/openmicroscopy/management_tools/tree/master/ansible?

The general idea would be to try and push most of the common functionality into roles, and in future this is what we'd publicise to external people.
This means playbooks could be tailored for our specific servers, which they already are to a certain extent, especially the ones which create or modify LVMs, and putting them into subdirectories makes it clearer what playbooks should be run to manage particular servers. See e.g. the current idrsytems-playbooks/ (there are current two top level playbooks, idrsystems-deployment.yml idrsystems-provision.yml which call the individual playbooks in idrsytems-playbooks/*, and I'm doing a similar refactoring with the idr openstack playbooks: https://github.com/openmicroscopy/infrastructure/compare/master...manics:refactor-idr.
Depending on how big the web work is you could either have a separate web directories, or make it part of a combined ci directory. Or if you prefer wait till more people are using it and there's a clearer idea of requirements.

Discussed at SA meeting, refactoring of the playbook into roles might happen as we use it in many servers. Merging for now as the current state is deployed in production.


Bi-directional flow using EquationNodes; smoothing and targeting

Flows

Can use both derivative of generation and the gradient of generation to update weights.
Using these, can set up a flow to give global weights to all elements, perhaps even to coefficients.
One can also do this with initial distributions, for example by making a Markov chain where we jump to the initial distribution with given probability.

Smoothing

We may be given just a goal, which is a type for which we have no known term.
We can use a flow as above to get a distribution of types, then optimize to generate (most of) the ones that are inhabited.
This is the starting point for a local prover.
We can also relativize, i.e. optimize given some generators.

Approached changed to local, adversarial learning #260


remove commented code

@Sayalic0 Thanks for your contribution. I think there're multiple files that need to be cleaned up in terms of removing unused code fragements, etc. I'll leave this open as a reminder, thank you.


[WIP] Added support for BeforeStep hooks

This goes along with my pull request for cucumber-ruby-core for the same functionality.
This is to add support for @BeforeStep hooks, which are executed prior to each step within a scenario.

Closing due to inactivity.

any update on this 'adding support for @BeforeStep hooks, which are executed prior to each step within a scenario.'? are you planning to have a fix?

any update on this ' adding support for @BeforeStep hooks, which are executed prior to each step within a scenario.'? Are you planning to have a fix?

We need a pull request. Would you like to help put one together @dionysiaA?

This would be really helpful for us at the moment.
I understand this is closed due to inactivity. I'm happy to help get this across the line. What is left to be completed?
@almostwhitehat @mattwynne

For the record, I helped @aesnyder use the events API to do this via a gitter chat.

yep - and it worked flawlessly! thanks you so much @mattwynne


crash on start after upgrade to 0.7.0, same issue

firezone/embedded/service/firezone

execute[setcap_beam] action run

execute setcap 'cap_net_admin+eip' /opt/firezone/embedded/service/firezone/erts-13.1/bin/beam.smp

file[environment-variables] action create (up to date)

execute[database schema] action run
================================================================================
Error executing action run on resource 'execute[database schema]'
Mixlib::ShellOut::ShellCommandFailed
Expected process to exit with [0], but received '1'
---- Begin output of bin/firezone eval "FzHttp.Release.migrate" ----
STDOUT: 15:49:42.631 [info] == Running<PHONE_NUMBER>0406 FzHttp.Repo.Migrations.MigratePksToUuid.change/0 forward
15:49:42.637 [info] alter table connectivity_checks
STDERR: ** (Postgrex.Error) ERROR 23502 (not_null_violation) column "id" of relation "connectivity_checks" contains null values
table: connectivity_checks
column: id
(ecto_sql 3.9.2) lib/ecto/adapters/sql.ex:913: Ecto.Adapters.SQL.raise_sql_call_error/1
(elixir 1.14.0) lib/enum.ex:1658: Enum."-map/2-lists^map/1-0-"/2
(ecto_sql 3.9.2) lib/ecto/adapters/sql.ex:1005: Ecto.Adapters.SQL.execute_ddl/4
(ecto_sql 3.9.2) lib/ecto/migration/runner.ex:326: Ecto.Migration.Runner.log_and_execute_ddl/3
(ecto_sql 3.9.2) lib/ecto/migration/runner.ex:117: anonymous fn/6 in Ecto.Migration.Runner.flush/0
(elixir 1.14.0) lib/enum.ex:2468: Enum."-reduce/3-lists^foldl/2-0-"/3
(ecto_sql 3.9.2) lib/ecto/migration/runner.ex:116: Ecto.Migration.Runner.flush/0
nofile:1: (file)

---- End output of bin/firezone eval "FzHttp.Release.migrate" ----
Ran bin/firezone eval "FzHttp.Release.migrate" returned 1
Resource Declaration:
In /var/opt/firezone/cache/cache/cookbooks/firezone/recipes/app.rb
59: execute 'database schema' do
60:   command 'bin/firezone eval "FzHttp.Release.migrate"'
61:   cwd node['firezone']['app_directory']
62:   environment(Firezone::Config.app_env(node))
63:   user node['firezone']['user']
64: end
Compiled Resource:
Declared in /var/opt/firezone/cache/cache/cookbooks/firezone/recipes/app.rb:59:in `from_file'
execute("database schema") do
action [:run]
default_guard_interpreter :execute
command "bin/firezone eval "FzHttp.Release.migrate""
declared_type :execute
cookbook_name "firezone"
recipe_name "app"
domain nil
user "firezone"
cwd "/opt/firezone/embedded/service/firezone"
environment { secret_info_you_may_not_see_here }
end
System Info:
chef_version=17.10.0
platform=ubuntu
platform_version=20.04
ruby=ruby 2.7.6p219 (2022-04-12 revision c9c2245c0a) [x86_64-linux]
program_name=/opt/firezone/embedded/bin/chef-client
executable=/opt/firezone/embedded/bin/chef-client

Recipe: firezone::phoenix

component_runit_service[phoenix] action restart

service[phoenix] action nothing (skipped due to action :nothing)
runit_service[phoenix] action restart (up to date)
(up to date)

Running handlers:
[2023-01-13T15:49:43+00:00] ERROR: Running exception handlers
Running handlers complete
[2023-01-13T15:49:43+00:00] ERROR: Exception handlers complete
Infra Phase failed. 23 resources updated in 16 seconds
[2023-01-13T15:49:43+00:00] FATAL: Stacktrace dumped to /var/opt/firezone/cache/cache/chef-stacktrace.out
[2023-01-13T15:49:43+00:00] FATAL: ---------------------------------------------------------------------------------------
[2023-01-13T15:49:43+00:00] FATAL: PLEASE PROVIDE THE CONTENTS OF THE stacktrace.out FILE (above) IF YOU FILE A BUG REPORT
[2023-01-13T15:49:43+00:00] FATAL: ---------------------------------------------------------------------------------------
[2023-01-13T15:49:43+00:00] FATAL: Mixlib::ShellOut::ShellCommandFailed: execute[database schema] (firezone::app line 59) had an error: Mixlib::ShellOut::ShellCommandFailed: Expected process to exit with [0], but received '1'
---- Begin output of bin/firezone eval "FzHttp.Release.migrate" ----
STDOUT: 15:49:42.631 [info] == Running<PHONE_NUMBER>0406 FzHttp.Repo.Migrations.MigratePksToUuid.change/0 forward
15:49:42.637 [info] alter table connectivity_checks
STDERR: ** (Postgrex.Error) ERROR 23502 (not_null_violation) column "id" of relation "connectivity_checks" contains null values
table: connectivity_checks
column: id
(ecto_sql 3.9.2) lib/ecto/adapters/sql.ex:913: Ecto.Adapters.SQL.raise_sql_call_error/1
(elixir 1.14.0) lib/enum.ex:1658: Enum."-map/2-lists^map/1-0-"/2
(ecto_sql 3.9.2) lib/ecto/adapters/sql.ex:1005: Ecto.Adapters.SQL.execute_ddl/4
(ecto_sql 3.9.2) lib/ecto/migration/runner.ex:326: Ecto.Migration.Runner.log_and_execute_ddl/3
(ecto_sql 3.9.2) lib/ecto/migration/runner.ex:117: anonymous fn/6 in Ecto.Migration.Runner.flush/0
(elixir 1.14.0) lib/enum.ex:2468: Enum."-reduce/3-lists^foldl/2-0-"/3
(ecto_sql 3.9.2) lib/ecto/migration/runner.ex:116: Ecto.Migration.Runner.flush/0
nofile:1: (file)

---- End output of bin/firezone eval "FzHttp.Release.migrate" ----
Ran bin/firezone eval "FzHttp.Release.migrate" returned 1

Hey @jahlib, the blame it on me - looks like our test data did not cover the migration case you hit into, I'll push a fix for a migration.

Closing as duplicate of #1295.


Add Favicon

Currently, there is no favicon on my site. Need to add it in head tag

I would like to handle this


gtime.String() lost timezone

1. What version of Go and system type/arch are you using?
go version go1.21.3 darwin/arm64
2. What version of GoFrame are you using?
gf v2.5.7
3. Can this issue be re-produced with the latest release?
yes
4. What did you do?
marshal a map which contains gtime.Time, the result lost timezone.
package main

import (
	"fmt"

	"github.com/gogf/gf/v2/encoding/gjson"
	"github.com/gogf/gf/v2/frame/g"
	"github.com/gogf/gf/v2/os/gtime"
)

func main() {
	time := gtime.NewFromStr("2023-12-01T00:00:00.000000Z")

	msg := g.Map{
		"time1": time,
		"time2": time.Local(),
	}

	fmt.Print(gjson.New(msg).MustToJsonIndentString())
}

5. What did you expect to see?
with local timezone
{
        "time1": "2023-12-01 08:00:00",
        "time2": "2023-12-01 08:00:00"
}

or same result as encoding/json marshal
{
        "time1": "2023-12-01T00:00:00.000000Z",
        "time2": "2023-12-01T00:00:00.000000Z"
}

6. What did you see instead?
{
        "time1": "2023-12-01 00:00:00",
        "time2": "2023-12-01 08:00:00"
}

Since gtime.String() loses timezone, can it be formatted to the local timezone by default?

https://github.com/gogf/gf/blob/master/os/gtime/gtime_time.go#L265

return t.wrapper.String()

change to:
return t.Local().wrapper.String()

@gqcn

@qinyuguang gtime.Time does not convert the time with time.Local unless you manually call .Local().

code
package main

import (
	"fmt"
	"time"

	"github.com/gogf/gf/v2/encoding/gjson"
	"github.com/gogf/gf/v2/os/gtime"
	"github.com/gogf/gf/v2/util/gconv"
)

type T1 struct {
	Time1 *gtime.Time `json:"time1"`
	Time2 *gtime.Time `json:"time2"`
}

type T2 struct {
	Time1 *time.Time `json:"time1"`
	Time2 *time.Time `json:"time2"`
}

func main() {
	str := `{"time1": "2023-12-01T00:00:00.000000Z", "time2": "2023-12-01T00:00:00.000000+08:00"}`

	var (
		t1 *T1
		t2 *T2
	)

	_ = gconv.Struct(str, &t1)
	_ = gconv.Struct(str, &t2)

	s1 := gjson.New(t1).MustToJsonIndentString()
	s2 := gjson.New(t2).MustToJsonIndentString()

	fmt.Println(s1)
	fmt.Println(s2)
}

output
{
        "time1": "2023-12-01 00:00:00",
        "time2": "2023-12-01 00:00:00"
}
{
        "time1": "2023-12-01T00:00:00Z",
        "time2": "2023-12-01T00:00:00+08:00"
}

Is this result expected?
time.Time retains the timezone, but gtime.Time loses the timezone.
If use gtime.Time, need to additionally know the potential meaning of each time field.
What I mean is that instead of letting people know the timezone of each field, after conversion, all time fields become the current timezone set by gtime.

anything new?

I find the gdb debug mode can output the raw sql, will this problem cause the output raw sql is not the sql that the database really execute？ for example when use postgre database，the field type is timestamp with time zone , I did find the debug mode sql seems not the real query sql, this makes me confused。
yesterday，our sandbox database change the timezone from Asia/Shanghai to UTF8, then I find some test case can't pass,
finally，I find this fix：https://github.com/gogf/gf/commit/1a271ce6270b31118e1cf87c352496e7a6429250， I think this may
be bug（the time param to build the sql is not expected：loss time zone info） that have fixed，so I upgrade my gf version from 2.0.3 to 2.6.2.
for example: the following debug sql is part of one of mysql unit test case:
SELECT * FROM table WHERE ((updated_at < '2024-02-02 14:46:58' or (updated_at = '2024-02-02 14:46:58' and id <<PHONE_NUMBER>25467905 )) AND ("subsidy_id"=498831613224812545)) AND "deleted_at" IS NULL ORDER BY "updated_at" desc,"id" desc LIMIT 2

I find the gdb debug mode can output the raw sql, will this problem cause the output raw sql is not the sql that the database really execute？ for example when use postgre database，the field type is timestamp with time zone , I did find the debug mode sql seems not the real query sql, this makes me confused。
yesterday，our sandbox database change the timezone from Asia/Shanghai to UTF8, then I find some test case can't pass,
finally，I find this fix：https://github.com/gogf/gf/commit/1a271ce6270b31118e1cf87c352496e7a6429250， I think this may
be bug（the time param to build the sql is not expected：loss time zone info） that have fixed，so I upgrade my gf version from 2.0.3 to 2.6.2. but I find some of unit test can not pass that can pass in old version. so I checkout two branch and open the debug mode, want to find what happened, but the two branch debug sql，both of them are like the following：
SELECT * FROM table WHERE ((updated_at < '2024-02-02 14:46:58' or (updated_at = '2024-02-02 14:46:58' and id <<PHONE_NUMBER>25467905 )) AND ("subsidy_id"=498831613224812545)) AND "deleted_at" IS NULL ORDER BY "updated_at" desc,"id" desc LIMIT 2。

but the fact is 2.0.3 can pass，2.6.2 can’t。


Parser crashes on 'active 1910-30'

# partial stack trace
....
  File "/Users/markfinger/Projects/agsa/var/go.sh-venv/lib/python2.7/site-packages/edtf/fields.py", line 117, in pre_save
    setattr(instance, g, getattr(edtf, attr)())
  File "/Users/markfinger/Projects/agsa/var/go.sh-venv/lib/python2.7/site-packages/edtf/parser/parser_classes.py", line 66, in upper_strict
    return self._strict_date(lean=LATEST)
  File "/Users/markfinger/Projects/agsa/var/go.sh-venv/lib/python2.7/site-packages/edtf/parser/parser_classes.py", line 292, in _strict_date
    r = self.upper._strict_date(lean)
  File "/Users/markfinger/Projects/agsa/var/go.sh-venv/lib/python2.7/site-packages/edtf/parser/parser_classes.py", line 216, in _strict_date
    'month': self._precise_month(lean),
  File "/Users/markfinger/Projects/agsa/var/go.sh-venv/lib/python2.7/site-packages/edtf/parser/parser_classes.py", line 189, in _precise_month
    return int(self.month)
TypeError: int() argument must be a string or a number, not 'dict'

Quoth the Greg

It might be trying to interpret 1910-30 as the 30th month in 1910…

It was actually the 'active ' part of the input string that was causing regex.match to fail, since match only looks at the start of the string.


[Docker 1.8] NetworkMode changed to "default"

Been using docker 1.8 (1.8.1 but I believe this is a 1.8 change) and I had to change connectable to detect NetworkMode=("bridge" || "default") because of the new networking layer. Are you interested in these changes? Since docker 1.8 is now a stable release, I'd reckon supporting it is a priority.

That'd be great.


Content is for kids. Not enterprise standard. Cant use these concepts in real time.

Content is for kids. Not enterprise standard.

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: b7077b5a-b7a6-9319-9df6-bd8cf8b332dc
Version Independent ID: b06640ac-13e3-c3d1-a0da-2265f371236c
Content: Machine learning and AI with ONNX in Azure SQL Edge
Content Source: articles/azure-sql-edge/onnx-overview.md
Service: sql-edge
Sub-service: machine-learning
GitHub Login: @WilliamDAssafMSFT
Microsoft Alias: wiassaf

@bvenkat88
Thanks for your feedback! We will investigate and update as appropriate.

Thanks for the feedback, @bvenkat88.

#please-close

#assign:WilliamDAssafMSFT


cleanup(rules): transition rule BPF Program Not Profiled to maturity incubating

…y incubating

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind feature

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area rules

/area registry

/area build

/area documentation

Proposed rule maturity level

Uncomment one (or more) /area <> lines (only for PRs that add or modify rules):

/area maturity-stable

/area maturity-incubating

/area maturity-sandbox

/area maturity-deprecated

What this PR does / why we need it:
cleanup(rules): transition rule BPF Program Not Profiled to maturity incubating as it is considered a critical baseline detection.
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: incertum
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [incertum]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: darryk10, incertum
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [incertum]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: 896a7bc3dc0ed60a86e437b7c0f083b97bcf8571

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: darryk10, incertum, LucaGuerra
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [LucaGuerra,incertum]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Using default JSON stringify method instead of JSON5's

#8
I had to change some test cases, as they used JSON5 exclusive features

Rad, thank you!

Thanks for your help @brunomperes! I've added you as an owner of this project. Let me know your npm user name and I'll add you there as well. Thanks!

Cool! Thanks @shama, on npm it's the same username :)


Official ngx-translate plunkr demo does not work

I'm submitting a ...
[x] bug report
[ ] support request
[ ] feature request

Current behavior
Your official plunkr demo doesn't work. It fails with the error I put below.
Expected/desired behavior
Should work!
Reproduction of the problem
Go to the plunkr demo https://plnkr.co/edit/01UjWY3TKfP6pgwXKuEa, which is officially published as "Simple example using ngx-translate", and get nothing.  The error which I see in the console is
zone.js:192 Error: (SystemJS) Error: XHR error (404) loading https://run.plnkr.co/62AYyTiID1zUYsH0/tslib
	    at XMLHttpRequest.wrapFn [as _onreadystatechange] (https://unpkg.com/zone.js@0.6.21/dist/zone.js:628:29)
	    at ZoneDelegate.invokeTask (https://unpkg.com/zone.js@0.6.21/dist/zone.js:225:37)
	    at Zone.runTask (https://unpkg.com/zone.js@0.6.21/dist/zone.js:125:47)
	    at XMLHttpRequest.ZoneTask.invoke (https://unpkg.com/zone.js@0.6.21/dist/zone.js:293:33)
	Error loading https://run.plnkr.co/62AYyTiID1zUYsH0/tslib as "tslib" from https://unpkg.com/rxjs/Subject.js

Browser: [Chrome 59| Firefox 54]

Some times ago (2 months?) I played with that demo and that was ok...

Thanks, it's fixed. All angular plunkr have been broken somehow, even the official one :)

It seems it doesn't work again

@gelevanog Slightly adjusted the plunker. https://plnkr.co/edit/O6EYGMBBF2zp2mOOKjBG?p=preview


Testnet Node always throws 401 because Auth Token is always NULL

Environment

I'm running Testnet OT Node v6 as described here

Node has a whitelisted IP and appropriate wallets set up

Private and public keys can be found in debug log as well

8900 and 9000 ports are open and working - From browser IP:8900 returns "Not Found", IP:8900/info returns "Unauthorized" as expected

Repro steps

Download ChatDKG Demo from official repo
Add appropriate variables in .env
Run it

Expected Result
Everything runs as expected
Actual Result

401 error is thrown in JS application
OT Node PrintsINFO: [AUTH] Received unauthenticated request.

Additional comments

I've tested everything with the official example for easier reproduction
Code throwing the same error we use const dkg = new DKG({
     endpoint: process.env.OT_NODE_HOSTNAME,
     blockchain: {
       name: "otp::testnet",
       publicKey: process.env.WALLET_PUBLIC_KEY,
       privateKey: process.env.WALLET_PRIVATE_KEY,
     },
 });

 const nodeInfo = await dkg.node.info();
 context.log(`Node info: ${JSON.stringify(nodeInfo)}`);

We've exhausted all ideas what the problem might be

From what it seems the auth token is never generated
Although OT Node checks if IP is whitelisted, that most likely isn't the problem because authToken being null is more likely to cause errors
This was tested with previous versions of dkg.js as well (6.0.6, 6.0.7, 6.0.15)
Not sure if format of keys is correct but it matches in the App and the OT Node

Hey @i-ralic it looks like auth token isn't a problem here. Token based authentication is disabled by default and you don't have it enabled in your configs. Problem is probably in IPs you set to be white listed.
If you want to enable token authentication we can provide with instructions
On a side note your private key isn't in 0x.... format.

Thanks, I've intentionally added parts of the keys because of that.
I've added IP to the whitelist after it refused to work beforehand.
So maybe it is a setup problem, I'll most likely reinstall the OT node with the 0x format of the private key and give it a go once more.

Once you've done that, please update us with how it went.
If you encounter any issues or need assistance, feel free to let us know. If you want to switch to token authentication and disable IP authentication, we're here to help you through the process.


⚠ Bofrost.de has degraded performance

In 02787db, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 793 ms

Resolved: Bofrost.de performance has improved in faaed84 after 6 minutes.


Elaborate on the updated goals for source-build

Fixes: https://github.com/dotnet/source-build/issues/3039

Thanks for enhancing the documentation @omajid.


Plot interaction methods

Closes #734.
I went with option 2 described in #734. This is a small breaking change and updating shouldn't be difficult. In the long run we can use this to add even more methods for interacting with the plot.
Might be a bit rough around the edges so feel free to suggest improvements.

I had completely missed your review and only just saw it. Sorry about the delay. I agree with all of your suggestions and have made the changes.

I tested this today and am pretty happy with how it works. I'd like to add the following features as well though:

Access to Ui inside the closure as well. Either through the plot_ui struct or as a second argument.
A plot_to_screen conversion, to enable custom drawing in screen coordinates based on items in the plot.
A way to get the current plot bounds.


data source connection should have multiple configuration

Description
This is how github connection page looks like at the moment, let's separate all fields into to 2 parts

connection part: including the very essential settings that allow DevLake to connect to github api server
configuration part: settings used for data extraction, standardization, enrichment, things of that natue

This works fine when user need to download data from a single repo on github.
However, during v0.9 patching process, we ran into following situation:

We have to collect multiple repos from github into a single DevLake database
Those repos share the same connection part, but may or may not share the same configuration part (repos from same org likely to share same configuration part, but not neccessary)

The workaround we chose, was to change configuration part right before we collect each repo. Obviously, this is not a long term solution that can be presented to users:

Recurring pipeline (blueprint) would not work
Due to reason 1, user have to manually collect multiple repos, go back and forth between connection and pipeline

Describe the solution you'd like
I don't have a clean solution at this point, so, let me list out some factors that have to be considered:

configuration part is specific to the plugin, like github configuration can be completely different than jira's.
configuration part may need validation
configuration part may rely on connection part on usablility, like jira epic key need jira connection to fetch options for user to select.
plugin may or may not need connection/configuration settings, like refdiff, it needs neither
we may have to solve Multi-DataSource before this, because they could have like 1 vs Many relationship
repos are connecting to configurations, do we save their relationship or accepting configuration id from options, or accepting whole configuration from options?

Has the Feature been Requested Before?
No

Need design @yumengwang03

This is addressed in the new config UI.


Feature/fuckinghtmlsyntax

Because fuckingblocksyntax.com deserves to have the correct fuckinghtmlsyntax :)

Hey! Sorry, don't know how I missed this. Looks fantastic :+1:
Thanks so much!


Items marked hidden will not be displayed immediately.

Since I use translators, it may not translate correctly.
HEI Version: 4.21.1

Turn on the mode for hiding objects.
You start clicking on items, but they don't stand out in red right away, but if you let's say you change the page in HEI from one to the same one again, then the item you clicked on will stand out in red.

Solved by disabling Buffer Ingredient Renders


Fix installation instructions in README

Updated to current zig-gamedev practices

The old instructions result in a cloned repo that fails to build.


Upgrade did not work

I followed the procedure from the documentation (https://exrm.readme.io/docs/upgradesdowngrades) but I'm getting an error when I issue the upgrade command:
# bin/bullhorn upgrade "0.0.3"
Using /app/releases/0.0.2/bullhorn.sh
Release 0.0.3 not found, attempting to unpack releases/0.0.3/bullhorn.tar.gz
Installed versions:
* 0.0.2	permanent
Unpack failed: {enoent,"/app/releases/0.0.3/bullhorn.rel"}

The current version of the app is 0.0.2 and the new version is 0.0.3. I have copied the tgz to the correct place I think:
# ls -l /app/releases/0.0.3/
total 103688
-rw-r--r-- 1 root root 106174702 Feb 16 10:06 bullhorn.tar.gz

The file that is referred to in the error is present in the tgz:
# tar -ztvf /app/releases/0.0.3/bullhorn.tar.gz |grep bullhorn.rel
-rw-r--r-- 1000/50        1404 2016-02-16 09:59 releases/0.0.3/bullhorn.rel

Should I be doing anything different? I'm using exrm 0.19.9.

I've been replacing the releases since the upgrade did not work, and now I get a different error when I try the upgrade:
# bin/bullhorn upgrade "0.0.6"
Using /app/releases/0.0.5/bullhorn.sh
Release 0.0.6 is already unpacked, now installing.
Generating vm.args/sys.config for upgrade...
sys.config ready!
vm.args ready!
Release 0.0.6 is already unpacked, now installing.
escript: exception error: no case clause matching
                 {error,
                     {'EXIT',
                         {which_children_failed,
                             [{release_handler_1,
                                  maybe_supervisor_which_children,3,
                                  [{file,"release_handler_1.erl"},{line,642}]},
                              {release_handler_1,get_procs,2,
                                  [{file,"release_handler_1.erl"},{line,616}]},
                              {release_handler_1,get_procs,2,
                                  [{file,"release_handler_1.erl"},{line,616}]},
                              {release_handler_1,get_supervised_procs,4,
                                  [{file,"release_handler_1.erl"},{line,590}]},
                              {lists,foldl,3,[{file,"lists.erl"},{line,1262}]},
                              {release_handler_1,eval,2,
                                  [{file,"release_handler_1.erl"},{line,375}]},
                              {lists,foldl,3,[{file,"lists.erl"},{line,1262}]},
                              {release_handler_1,eval_script,5,
                                  [{file,"release_handler_1.erl"},
                                   {line,102}]}]}}}

I'm still using exrm 0.19.9.

I suspect you are encountering the same issues as in #297, looks like this was an issue in Ecto that has been fixed.


Implementing Python Client Library

Implement functions in Python (like R package) that enable use of the YABA API (unlike the existing R package, this will use the API rather than ODBC database connection).This will be used for both scripted workflows and as a backend to the UI.
Completion criteria:

Commit with client.py
Integration with UI.

Client Library implemented in latest commit.

PR #13


Facial recognition using OpenCV to identify users and provide authentication

Make sure to make a folder in "C" drive named "recognition". Here the trained model will be stored which will be able to identify user. When user runs Benji for first time, it will take 1000 facial images and store it in a folder "dataset".
Next time, Benji will recognize the user. If user wants to add another user, he/she can use "face id", here "id" should be an integer value. This is because "OpenCV" supports integer values. For eg., "face 2", "face 3". By default the id for first time users will be "1". So make sure you don't use "1" as your id again and again.
For now, if the user is not identified by Benji, then Benji will not run. This is for the "testing purpose". If this fetch good results, then I will change the code to directly shutdown the system.
NOTE: The users should feed different images(facial expressions, etc.) so that the model get better trained at recognizing the user.

@abhimanyuthakre great work indeed!
Two cents:

Can you include this activity in the activities.md? This might help users to learn how to use it.
Please also send a working .gif

Merging this :tada: