Edge tpu m.2 not working

Followed all instructions as per coral tpu getting started web page, I am using PCIe m.2 tpu
ValueError: Failed to load delegate from libedgetpu.so.1 while running the inference code(classify image.py) example
ls /dev/apex_0  returns nothing
I am using RockPi 4b rk3399.
Any idea?
Thanks

@Nishanth009 could you also provide some logs from lightdm? Maybe there are some hints we can find.
I'm not able to see anything from this log suggesting any faulty from our drivers, but our drivers doesn't do anything related to display.

Debug msg from lightdm
[+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.00s] DEBUG: Starting Light Display Manager 1.26.0, UID=0 PID=637
[+0.00s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-disable-guest.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-disable-log-backup.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-greeter-wrapper.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-guest-wrapper.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-slick-greeter.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-ubuntu-mate.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-ubuntu.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-xserver-command.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/90-nvidia.conf
[+0.00s] DEBUG:   [SeatDefaults] is now called [Seat:], please update this configuration
[+0.00s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
[+0.00s] DEBUG: Registered seat module local
[+0.00s] DEBUG: Registered seat module xremote
[+0.00s] DEBUG: Registered seat module unity
[+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
[+0.01s] DEBUG: Monitoring logind for seats
[+0.01s] DEBUG: New seat added from logind: seat0
[+0.01s] WARNING: Seat type 'xlocal' is deprecated, use 'type=local' instead
[+0.01s] DEBUG: Seat seat0: Loading properties from config section Seat:
[+0.01s] DEBUG: Seat seat0: Starting
[+0.01s] DEBUG: Seat seat0: Creating user session
[+0.01s] DEBUG: Loading users from org.freedesktop.Accounts
[+0.01s] DEBUG: User /org/freedesktop/Accounts/User1000 added
[+0.18s] DEBUG: Seat seat0: Creating display server of type x
[+0.18s] DEBUG: Using VT 7
[+0.18s] DEBUG: Seat seat0: Starting local X display on VT 7
[+0.18s] DEBUG: XServer 0: Logging to /var/log/lightdm/x-0.log
[+0.18s] DEBUG: XServer 0: Writing X server authority to /var/run/lightdm/root/:0
[+0.18s] DEBUG: XServer 0: Launching X Server
[+0.19s] DEBUG: Launching process 646: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+0.19s] DEBUG: XServer 0: Waiting for ready signal from X server :0
[+0.19s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
[+0.19s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0
[+1.20s] DEBUG: Process 646 terminated with signal 6
[+1.20s] DEBUG: XServer 0: X server stopped
[+1.20s] DEBUG: Releasing VT 7
[+1.20s] DEBUG: XServer 0: Removing X server authority /var/run/lightdm/root/:0
[+1.20s] DEBUG: Seat seat0: Display server stopped
[+1.20s] DEBUG: Launching process 653: /sbin/prime-switch
[+1.22s] DEBUG: Process 653 exited with return value 0
[+1.22s] DEBUG: Seat seat0: Exit status of /sbin/prime-switch: 0
[+1.22s] DEBUG: Seat seat0: Stopping session
[+1.22s] DEBUG: Seat seat0: Session stopped
[+1.22s] DEBUG: Seat seat0: Stopping display server, no sessions require it
[+1.22s] DEBUG: Seat seat0: Active display server stopped, starting greeter
[+1.22s] DEBUG: Seat seat0: Creating greeter session
[+1.22s] DEBUG: Seat seat0: Creating display server of type x
[+1.22s] DEBUG: Using VT 7
[+1.22s] DEBUG: Seat seat0: Starting local X display on VT 7
[+1.22s] DEBUG: XServer 0: Logging to /var/log/lightdm/x-0.log
[+1.22s] DEBUG: XServer 0: Writing X server authority to /var/run/lightdm/root/:0
[+1.22s] DEBUG: XServer 0: Launching X Server
[+1.22s] DEBUG: Launching process 656: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+1.22s] DEBUG: XServer 0: Waiting for ready signal from X server :0
[+1.98s] DEBUG: Process 656 terminated with signal 6
[+1.98s] DEBUG: XServer 0: X server stopped
[+1.98s] DEBUG: Releasing VT 7
[+1.98s] DEBUG: XServer 0: Removing X server authority /var/run/lightdm/root/:0
[+1.98s] DEBUG: Seat seat0: Display server stopped
[+1.98s] DEBUG: Launching process 669: /sbin/prime-switch
[+2.00s] DEBUG: Process 669 exited with return value 0
[+2.00s] DEBUG: Seat seat0: Exit status of /sbin/prime-switch: 0
[+2.00s] DEBUG: Seat seat0: Stopping session
[+2.00s] DEBUG: Seat seat0: Session stopped
[+2.00s] DEBUG: Seat seat0: Stopping display server, no sessions require it
[+2.00s] DEBUG: Seat seat0: Stopping; greeter display server failed to start
[+2.00s] DEBUG: Seat seat0: Stopping
[+2.00s] DEBUG: Seat seat0: Stopped
[+2.00s] DEBUG: Required seat has stopped
[+2.00s] DEBUG: Stopping display manager
[+2.00s] DEBUG: Display manager stopped
[+2.00s] DEBUG: Stopping daemon
[+2.01s] DEBUG: Exiting with return value 1
[+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.00s] DEBUG: Starting Light Display Manager 1.26.0, UID=0 PID=675
[+0.00s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-disable-guest.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-disable-log-backup.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-greeter-wrapper.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-guest-wrapper.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-slick-greeter.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-ubuntu-mate.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-ubuntu.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-xserver-command.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/90-nvidia.conf
[+0.00s] DEBUG:   [SeatDefaults] is now called [Seat:], please update this configuration
[+0.00s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
[+0.00s] DEBUG: Registered seat module local
[+0.00s] DEBUG: Registered seat module xremote
[+0.00s] DEBUG: Registered seat module unity
[+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
[+0.01s] DEBUG: Monitoring logind for seats
[+0.01s] DEBUG: New seat added from logind: seat0
[+0.01s] WARNING: Seat type 'xlocal' is deprecated, use 'type=local' instead
[+0.01s] DEBUG: Seat seat0: Loading properties from config section Seat:
[+0.01s] DEBUG: Seat seat0: Starting
[+0.01s] DEBUG: Seat seat0: Creating user session
[+0.02s] DEBUG: Loading users from org.freedesktop.Accounts
[+0.02s] DEBUG: User /org/freedesktop/Accounts/User1000 added
[+0.04s] DEBUG: Seat seat0: Creating display server of type x
[+0.04s] DEBUG: Using VT 7
[+0.04s] DEBUG: Seat seat0: Starting local X display on VT 7
[+0.04s] DEBUG: XServer 0: Logging to /var/log/lightdm/x-0.log
[+0.04s] DEBUG: XServer 0: Writing X server authority to /var/run/lightdm/root/:0
[+0.04s] DEBUG: XServer 0: Launching X Server
[+0.04s] DEBUG: Launching process 681: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+0.04s] DEBUG: XServer 0: Waiting for ready signal from X server :0
[+0.04s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
[+0.04s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0
[+0.99s] DEBUG: Process 681 terminated with signal 6
[+0.99s] DEBUG: XServer 0: X server stopped
[+0.99s] DEBUG: Releasing VT 7
[+0.99s] DEBUG: XServer 0: Removing X server authority /var/run/lightdm/root/:0
[+0.99s] DEBUG: Seat seat0: Display server stopped
[+0.99s] DEBUG: Launching process 683: /sbin/prime-switch
[+1.01s] DEBUG: Process 683 exited with return value 0
[+1.01s] DEBUG: Seat seat0: Exit status of /sbin/prime-switch: 0
[+1.01s] DEBUG: Seat seat0: Stopping session
[+1.01s] DEBUG: Seat seat0: Session stopped
[+1.01s] DEBUG: Seat seat0: Stopping display server, no sessions require it
[+1.01s] DEBUG: Seat seat0: Active display server stopped, starting greeter
[+1.01s] DEBUG: Seat seat0: Creating greeter session
[+1.01s] DEBUG: Seat seat0: Creating display server of type x
[+1.01s] DEBUG: Using VT 7
[+1.01s] DEBUG: Seat seat0: Starting local X display on VT 7
[+1.01s] DEBUG: XServer 0: Logging to /var/log/lightdm/x-0.log
[+1.01s] DEBUG: XServer 0: Writing X server authority to /var/run/lightdm/root/:0
[+1.01s] DEBUG: XServer 0: Launching X Server
[+1.01s] DEBUG: Launching process 686: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+1.01s] DEBUG: XServer 0: Waiting for ready signal from X server :0
[+1.76s] DEBUG: Process 686 terminated with signal 6
[+1.76s] DEBUG: XServer 0: X server stopped
[+1.76s] DEBUG: Releasing VT 7
[+1.76s] DEBUG: XServer 0: Removing X server authority /var/run/lightdm/root/:0
[+1.76s] DEBUG: Seat seat0: Display server stopped
[+1.76s] DEBUG: Launching process 695: /sbin/prime-switch
[+1.77s] DEBUG: Process 695 exited with return value 0
[+1.77s] DEBUG: Seat seat0: Exit status of /sbin/prime-switch: 0
[+1.77s] DEBUG: Seat seat0: Stopping session
[+1.77s] DEBUG: Seat seat0: Session stopped
[+1.77s] DEBUG: Seat seat0: Stopping display server, no sessions require it
[+1.77s] DEBUG: Seat seat0: Stopping; greeter display server failed to start
[+1.77s] DEBUG: Seat seat0: Stopping
[+1.77s] DEBUG: Seat seat0: Stopped
[+1.77s] DEBUG: Required seat has stopped
[+1.77s] DEBUG: Stopping display manager
[+1.77s] DEBUG: Display manager stopped
[+1.77s] DEBUG: Stopping daemon
[+1.78s] DEBUG: Exiting with return value 1
[+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.00s] DEBUG: Starting Light Display Manager 1.26.0, UID=0 PID=733
[+0.00s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-disable-guest.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-disable-log-backup.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-greeter-wrapper.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-guest-wrapper.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-slick-greeter.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-ubuntu-mate.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-ubuntu.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-xserver-command.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/90-nvidia.conf
[+0.00s] DEBUG:   [SeatDefaults] is now called [Seat:], please update this configuration
[+0.00s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
[+0.00s] DEBUG: Registered seat module local
[+0.00s] DEBUG: Registered seat module xremote
[+0.00s] DEBUG: Registered seat module unity
[+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
[+0.02s] DEBUG: Monitoring logind for seats
[+0.02s] DEBUG: New seat added from logind: seat0
[+0.02s] WARNING: Seat type 'xlocal' is deprecated, use 'type=local' instead
[+0.02s] DEBUG: Seat seat0: Loading properties from config section Seat:
[+0.02s] DEBUG: Seat seat0: Starting
[+0.02s] DEBUG: Seat seat0: Creating user session
[+0.03s] DEBUG: Loading users from org.freedesktop.Accounts
[+0.03s] DEBUG: User /org/freedesktop/Accounts/User1000 added
[+0.05s] DEBUG: Seat seat0: Creating display server of type x
[+0.05s] DEBUG: Using VT 7
[+0.05s] DEBUG: Seat seat0: Starting local X display on VT 7
[+0.05s] DEBUG: XServer 0: Logging to /var/log/lightdm/x-0.log
[+0.05s] DEBUG: XServer 0: Writing X server authority to /var/run/lightdm/root/:0
[+0.05s] DEBUG: XServer 0: Launching X Server
[+0.05s] DEBUG: Launching process 774: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+0.06s] DEBUG: XServer 0: Waiting for ready signal from X server :0
[+0.06s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
[+0.06s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0
[+0.76s] DEBUG: Process 774 terminated with signal 6
[+0.76s] DEBUG: XServer 0: X server stopped
[+0.76s] DEBUG: Releasing VT 7
[+0.76s] DEBUG: XServer 0: Removing X server authority /var/run/lightdm/root/:0
[+0.76s] DEBUG: Seat seat0: Display server stopped
[+0.76s] DEBUG: Launching process 795: /sbin/prime-switch
[+0.77s] DEBUG: Process 795 exited with return value 0
[+0.77s] DEBUG: Seat seat0: Exit status of /sbin/prime-switch: 0
[+0.77s] DEBUG: Seat seat0: Stopping session
[+0.77s] DEBUG: Seat seat0: Session stopped
[+0.77s] DEBUG: Seat seat0: Stopping display server, no sessions require it
[+0.77s] DEBUG: Seat seat0: Active display server stopped, starting greeter
[+0.77s] DEBUG: Seat seat0: Creating greeter session
[+0.77s] DEBUG: Seat seat0: Creating display server of type x
[+0.77s] DEBUG: Using VT 7
[+0.77s] DEBUG: Seat seat0: Starting local X display on VT 7
[+0.77s] DEBUG: XServer 0: Logging to /var/log/lightdm/x-0.log
[+0.77s] DEBUG: XServer 0: Writing X server authority to /var/run/lightdm/root/:0
[+0.77s] DEBUG: XServer 0: Launching X Server
[+0.77s] DEBUG: Launching process 798: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+0.77s] DEBUG: XServer 0: Waiting for ready signal from X server :0
[+1.47s] DEBUG: Process 798 terminated with signal 6
[+1.47s] DEBUG: XServer 0: X server stopped
[+1.47s] DEBUG: Releasing VT 7
[+1.47s] DEBUG: XServer 0: Removing X server authority /var/run/lightdm/root/:0
[+1.47s] DEBUG: Seat seat0: Display server stopped
[+1.47s] DEBUG: Launching process 801: /sbin/prime-switch
[+1.48s] DEBUG: Process 801 exited with return value 0
[+1.48s] DEBUG: Seat seat0: Exit status of /sbin/prime-switch: 0
[+1.48s] DEBUG: Seat seat0: Stopping session
[+1.48s] DEBUG: Seat seat0: Session stopped
[+1.48s] DEBUG: Seat seat0: Stopping display server, no sessions require it
[+1.48s] DEBUG: Seat seat0: Stopping; greeter display server failed to start
[+1.48s] DEBUG: Seat seat0: Stopping
[+1.48s] DEBUG: Seat seat0: Stopped
[+1.48s] DEBUG: Required seat has stopped
[+1.48s] DEBUG: Stopping display manager
[+1.48s] DEBUG: Display manager stopped
[+1.48s] DEBUG: Stopping daemon
[+1.49s] DEBUG: Exiting with return value 1
[+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.00s] DEBUG: Starting Light Display Manager 1.26.0, UID=0 PID=807
[+0.00s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-disable-guest.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-disable-log-backup.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-greeter-wrapper.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-guest-wrapper.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-slick-greeter.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-ubuntu-mate.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-ubuntu.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-xserver-command.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/90-nvidia.conf
[+0.00s] DEBUG:   [SeatDefaults] is now called [Seat:], please update this configuration
[+0.00s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
[+0.00s] DEBUG: Registered seat module local
[+0.00s] DEBUG: Registered seat module xremote
[+0.00s] DEBUG: Registered seat module unity
[+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
[+0.02s] DEBUG: Monitoring logind for seats
[+0.02s] DEBUG: New seat added from logind: seat0
[+0.02s] WARNING: Seat type 'xlocal' is deprecated, use 'type=local' instead
[+0.02s] DEBUG: Seat seat0: Loading properties from config section Seat:
[+0.02s] DEBUG: Seat seat0: Starting
[+0.02s] DEBUG: Seat seat0: Creating user session
[+0.03s] DEBUG: Loading users from org.freedesktop.Accounts
[+0.03s] DEBUG: User /org/freedesktop/Accounts/User1000 added
[+0.05s] DEBUG: Seat seat0: Creating display server of type x
[+0.06s] DEBUG: Using VT 7
[+0.06s] DEBUG: Seat seat0: Starting local X display on VT 7
[+0.06s] DEBUG: XServer 0: Logging to /var/log/lightdm/x-0.log
[+0.06s] DEBUG: XServer 0: Writing X server authority to /var/run/lightdm/root/:0
[+0.06s] DEBUG: XServer 0: Launching X Server
[+0.07s] DEBUG: Launching process 813: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+0.07s] DEBUG: XServer 0: Waiting for ready signal from X server :0
[+0.07s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
[+0.07s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0
[+0.80s] DEBUG: Process 813 terminated with signal 6
[+0.80s] DEBUG: XServer 0: X server stopped
[+0.80s] DEBUG: Releasing VT 7
[+0.80s] DEBUG: XServer 0: Removing X server authority /var/run/lightdm/root/:0
[+0.80s] DEBUG: Seat seat0: Display server stopped
[+0.80s] DEBUG: Launching process 815: /sbin/prime-switch
[+0.81s] DEBUG: Process 815 exited with return value 0
[+0.81s] DEBUG: Seat seat0: Exit status of /sbin/prime-switch: 0
[+0.81s] DEBUG: Seat seat0: Stopping session
[+0.81s] DEBUG: Seat seat0: Session stopped
[+0.81s] DEBUG: Seat seat0: Stopping display server, no sessions require it
[+0.81s] DEBUG: Seat seat0: Active display server stopped, starting greeter
[+0.81s] DEBUG: Seat seat0: Creating greeter session
[+0.81s] DEBUG: Seat seat0: Creating display server of type x
[+0.81s] DEBUG: Using VT 7
[+0.81s] DEBUG: Seat seat0: Starting local X display on VT 7
[+0.81s] DEBUG: XServer 0: Logging to /var/log/lightdm/x-0.log
[+0.81s] DEBUG: XServer 0: Writing X server authority to /var/run/lightdm/root/:0
[+0.81s] DEBUG: XServer 0: Launching X Server
[+0.82s] DEBUG: Launching process 818: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+0.82s] DEBUG: XServer 0: Waiting for ready signal from X server :0
[+1.58s] DEBUG: Process 818 terminated with signal 6
[+1.58s] DEBUG: XServer 0: X server stopped
[+1.58s] DEBUG: Releasing VT 7
[+1.58s] DEBUG: XServer 0: Removing X server authority /var/run/lightdm/root/:0
[+1.58s] DEBUG: Seat seat0: Display server stopped
[+1.58s] DEBUG: Launching process 820: /sbin/prime-switch
[+1.59s] DEBUG: Process 820 exited with return value 0
[+1.59s] DEBUG: Seat seat0: Exit status of /sbin/prime-switch: 0
[+1.59s] DEBUG: Seat seat0: Stopping session
[+1.59s] DEBUG: Seat seat0: Session stopped
[+1.59s] DEBUG: Seat seat0: Stopping display server, no sessions require it
[+1.59s] DEBUG: Seat seat0: Stopping; greeter display server failed to start
[+1.59s] DEBUG: Seat seat0: Stopping
[+1.59s] DEBUG: Seat seat0: Stopped
[+1.59s] DEBUG: Required seat has stopped
[+1.59s] DEBUG: Stopping display manager
[+1.59s] DEBUG: Display manager stopped
[+1.59s] DEBUG: Stopping daemon
[+1.60s] DEBUG: Exiting with return value 1
[+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.00s] DEBUG: Starting Light Display Manager 1.26.0, UID=0 PID=832
[+0.00s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-disable-guest.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-disable-log-backup.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-greeter-wrapper.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-guest-wrapper.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-slick-greeter.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-ubuntu-mate.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-ubuntu.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-xserver-command.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/90-nvidia.conf
[+0.00s] DEBUG:   [SeatDefaults] is now called [Seat:], please update this configuration
[+0.00s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
[+0.00s] DEBUG: Registered seat module local
[+0.00s] DEBUG: Registered seat module xremote
[+0.00s] DEBUG: Registered seat module unity
[+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
[+0.02s] DEBUG: Monitoring logind for seats
[+0.02s] DEBUG: New seat added from logind: seat0
[+0.02s] WARNING: Seat type 'xlocal' is deprecated, use 'type=local' instead
[+0.02s] DEBUG: Seat seat0: Loading properties from config section Seat:
[+0.02s] DEBUG: Seat seat0: Starting
[+0.02s] DEBUG: Seat seat0: Creating user session
[+0.03s] DEBUG: Loading users from org.freedesktop.Accounts
[+0.03s] DEBUG: User /org/freedesktop/Accounts/User1000 added
[+0.04s] DEBUG: Seat seat0: Creating display server of type x
[+0.05s] DEBUG: Using VT 7
[+0.05s] DEBUG: Seat seat0: Starting local X display on VT 7
[+0.05s] DEBUG: XServer 0: Logging to /var/log/lightdm/x-0.log
[+0.05s] DEBUG: XServer 0: Writing X server authority to /var/run/lightdm/root/:0
[+0.05s] DEBUG: XServer 0: Launching X Server
[+0.05s] DEBUG: Launching process 848: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+0.05s] DEBUG: XServer 0: Waiting for ready signal from X server :0
[+0.05s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
[+0.05s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0
[+0.80s] DEBUG: Process 848 terminated with signal 6
[+0.80s] DEBUG: XServer 0: X server stopped
[+0.80s] DEBUG: Releasing VT 7
[+0.80s] DEBUG: XServer 0: Removing X server authority /var/run/lightdm/root/:0
[+0.80s] DEBUG: Seat seat0: Display server stopped
[+0.80s] DEBUG: Launching process 931: /sbin/prime-switch
[+0.82s] DEBUG: Process 931 exited with return value 0
[+0.82s] DEBUG: Seat seat0: Exit status of /sbin/prime-switch: 0
[+0.82s] DEBUG: Seat seat0: Stopping session
[+0.82s] DEBUG: Seat seat0: Session stopped
[+0.82s] DEBUG: Seat seat0: Stopping display server, no sessions require it
[+0.82s] DEBUG: Seat seat0: Active display server stopped, starting greeter
[+0.82s] DEBUG: Seat seat0: Creating greeter session
[+0.82s] DEBUG: Seat seat0: Creating display server of type x
[+0.82s] DEBUG: Using VT 7
[+0.82s] DEBUG: Seat seat0: Starting local X display on VT 7
[+0.82s] DEBUG: XServer 0: Logging to /var/log/lightdm/x-0.log
[+0.82s] DEBUG: XServer 0: Writing X server authority to /var/run/lightdm/root/:0
[+0.82s] DEBUG: XServer 0: Launching X Server
[+0.82s] DEBUG: Launching process 935: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+0.82s] DEBUG: XServer 0: Waiting for ready signal from X server :0
[+1.54s] DEBUG: Process 935 terminated with signal 6
[+1.54s] DEBUG: XServer 0: X server stopped
[+1.54s] DEBUG: Releasing VT 7
[+1.54s] DEBUG: XServer 0: Removing X server authority /var/run/lightdm/root/:0
[+1.54s] DEBUG: Seat seat0: Display server stopped
[+1.54s] DEBUG: Launching process 951: /sbin/prime-switch
[+1.56s] DEBUG: Process 951 exited with return value 0
[+1.56s] DEBUG: Seat seat0: Exit status of /sbin/prime-switch: 0
[+1.56s] DEBUG: Seat seat0: Stopping session
[+1.56s] DEBUG: Seat seat0: Session stopped
[+1.56s] DEBUG: Seat seat0: Stopping display server, no sessions require it
[+1.56s] DEBUG: Seat seat0: Stopping; greeter display server failed to start
[+1.56s] DEBUG: Seat seat0: Stopping
[+1.56s] DEBUG: Seat seat0: Stopped
[+1.56s] DEBUG: Required seat has stopped
[+1.56s] DEBUG: Stopping display manager
[+1.56s] DEBUG: Display manager stopped
[+1.56s] DEBUG: Stopping daemon
[+1.57s] DEBUG: Exiting with return value 1
[+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.00s] DEBUG: Starting Light Display Manager 1.26.0, UID=0 PID=957
[+0.00s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-disable-guest.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-disable-log-backup.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-greeter-wrapper.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-guest-wrapper.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-slick-greeter.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-ubuntu-mate.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-ubuntu.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-xserver-command.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/90-nvidia.conf
[+0.00s] DEBUG:   [SeatDefaults] is now called [Seat:], please update this configuration
[+0.00s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
[+0.00s] DEBUG: Registered seat module local
[+0.00s] DEBUG: Registered seat module xremote
[+0.00s] DEBUG: Registered seat module unity
[+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
[+0.02s] DEBUG: Monitoring logind for seats
[+0.02s] DEBUG: New seat added from logind: seat0
[+0.02s] WARNING: Seat type 'xlocal' is deprecated, use 'type=local' instead
[+0.02s] DEBUG: Seat seat0: Loading properties from config section Seat:
[+0.02s] DEBUG: Seat seat0: Starting
[+0.02s] DEBUG: Seat seat0: Creating user session
[+0.03s] DEBUG: Loading users from org.freedesktop.Accounts
[+0.03s] DEBUG: User /org/freedesktop/Accounts/User1000 added
[+0.04s] DEBUG: Seat seat0: Creating display server of type x
[+0.05s] DEBUG: Using VT 7
[+0.05s] DEBUG: Seat seat0: Starting local X display on VT 7
[+0.05s] DEBUG: XServer 0: Logging to /var/log/lightdm/x-0.log
[+0.05s] DEBUG: XServer 0: Writing X server authority to /var/run/lightdm/root/:0
[+0.05s] DEBUG: XServer 0: Launching X Server
[+0.05s] DEBUG: Launching process 963: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+0.05s] DEBUG: XServer 0: Waiting for ready signal from X server :0
[+0.05s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
[+0.05s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0
[+0.77s] DEBUG: Process 963 terminated with signal 6
[+0.77s] DEBUG: XServer 0: X server stopped
[+0.77s] DEBUG: Releasing VT 7
[+0.77s] DEBUG: XServer 0: Removing X server authority /var/run/lightdm/root/:0
[+0.77s] DEBUG: Seat seat0: Display server stopped
[+0.77s] DEBUG: Launching process 965: /sbin/prime-switch
[+0.78s] DEBUG: Process 965 exited with return value 0
[+0.78s] DEBUG: Seat seat0: Exit status of /sbin/prime-switch: 0
[+0.78s] DEBUG: Seat seat0: Stopping session
[+0.78s] DEBUG: Seat seat0: Session stopped
[+0.78s] DEBUG: Seat seat0: Stopping display server, no sessions require it
[+0.78s] DEBUG: Seat seat0: Active display server stopped, starting greeter
[+0.78s] DEBUG: Seat seat0: Creating greeter session
[+0.79s] DEBUG: Seat seat0: Creating display server of type x
[+0.79s] DEBUG: Using VT 7
[+0.79s] DEBUG: Seat seat0: Starting local X display on VT 7
[+0.79s] DEBUG: XServer 0: Logging to /var/log/lightdm/x-0.log
[+0.79s] DEBUG: XServer 0: Writing X server authority to /var/run/lightdm/root/:0
[+0.79s] DEBUG: XServer 0: Launching X Server
[+0.79s] DEBUG: Launching process 968: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+0.79s] DEBUG: XServer 0: Waiting for ready signal from X server :0
[+1.46s] DEBUG: Process 968 terminated with signal 6
[+1.46s] DEBUG: XServer 0: X server stopped
[+1.46s] DEBUG: Releasing VT 7
[+1.46s] DEBUG: XServer 0: Removing X server authority /var/run/lightdm/root/:0
[+1.46s] DEBUG: Seat seat0: Display server stopped
[+1.46s] DEBUG: Launching process 970: /sbin/prime-switch
[+1.47s] DEBUG: Process 970 exited with return value 0
[+1.47s] DEBUG: Seat seat0: Exit status of /sbin/prime-switch: 0
[+1.47s] DEBUG: Seat seat0: Stopping session
[+1.47s] DEBUG: Seat seat0: Session stopped
[+1.47s] DEBUG: Seat seat0: Stopping display server, no sessions require it
[+1.47s] DEBUG: Seat seat0: Stopping; greeter display server failed to start
[+1.47s] DEBUG: Seat seat0: Stopping
[+1.47s] DEBUG: Seat seat0: Stopped
[+1.47s] DEBUG: Required seat has stopped
[+1.47s] DEBUG: Stopping display manager
[+1.47s] DEBUG: Display manager stopped
[+1.47s] DEBUG: Stopping daemon
[+1.47s] DEBUG: Exiting with return value 1
[+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.00s] DEBUG: Starting Light Display Manager 1.26.0, UID=0 PID=976
[+0.00s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-disable-guest.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-disable-log-backup.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-greeter-wrapper.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-guest-wrapper.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-slick-greeter.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-ubuntu-mate.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-ubuntu.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-xserver-command.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/90-nvidia.conf
[+0.00s] DEBUG:   [SeatDefaults] is now called [Seat:], please update this configuration
[+0.00s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
[+0.00s] DEBUG: Registered seat module local
[+0.00s] DEBUG: Registered seat module xremote
[+0.00s] DEBUG: Registered seat module unity
[+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
[+0.02s] DEBUG: Monitoring logind for seats
[+0.02s] DEBUG: New seat added from logind: seat0
[+0.02s] WARNING: Seat type 'xlocal' is deprecated, use 'type=local' instead
[+0.02s] DEBUG: Seat seat0: Loading properties from config section Seat:
[+0.02s] DEBUG: Seat seat0: Starting
[+0.02s] DEBUG: Seat seat0: Creating user session
[+0.03s] DEBUG: Loading users from org.freedesktop.Accounts
[+0.03s] DEBUG: User /org/freedesktop/Accounts/User1000 added
[+0.04s] DEBUG: Seat seat0: Creating display server of type x
[+0.05s] DEBUG: Using VT 7
[+0.05s] DEBUG: Seat seat0: Starting local X display on VT 7
[+0.05s] DEBUG: XServer 0: Logging to /var/log/lightdm/x-0.log
[+0.05s] DEBUG: XServer 0: Writing X server authority to /var/run/lightdm/root/:0
[+0.05s] DEBUG: XServer 0: Launching X Server
[+0.05s] DEBUG: Launching process 982: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+0.05s] DEBUG: XServer 0: Waiting for ready signal from X server :0
[+0.06s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
[+0.06s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0
[+0.82s] DEBUG: Process 982 terminated with signal 6
[+0.82s] DEBUG: XServer 0: X server stopped
[+0.82s] DEBUG: Releasing VT 7
[+0.82s] DEBUG: XServer 0: Removing X server authority /var/run/lightdm/root/:0
[+0.82s] DEBUG: Seat seat0: Display server stopped
[+0.82s] DEBUG: Launching process 984: /sbin/prime-switch
[+0.83s] DEBUG: Process 984 exited with return value 0
[+0.83s] DEBUG: Seat seat0: Exit status of /sbin/prime-switch: 0
[+0.83s] DEBUG: Seat seat0: Stopping session
[+0.83s] DEBUG: Seat seat0: Session stopped
[+0.83s] DEBUG: Seat seat0: Stopping display server, no sessions require it
[+0.83s] DEBUG: Seat seat0: Active display server stopped, starting greeter
[+0.83s] DEBUG: Seat seat0: Creating greeter session
[+0.83s] DEBUG: Seat seat0: Creating display server of type x
[+0.83s] DEBUG: Using VT 7
[+0.83s] DEBUG: Seat seat0: Starting local X display on VT 7
[+0.83s] DEBUG: XServer 0: Logging to /var/log/lightdm/x-0.log
[+0.83s] DEBUG: XServer 0: Writing X server authority to /var/run/lightdm/root/:0
[+0.83s] DEBUG: XServer 0: Launching X Server
[+0.83s] DEBUG: Launching process 987: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+0.83s] DEBUG: XServer 0: Waiting for ready signal from X server :0
[+1.54s] DEBUG: Process 987 terminated with signal 6
[+1.54s] DEBUG: XServer 0: X server stopped
[+1.54s] DEBUG: Releasing VT 7
[+1.54s] DEBUG: XServer 0: Removing X server authority /var/run/lightdm/root/:0
[+1.54s] DEBUG: Seat seat0: Display server stopped
[+1.54s] DEBUG: Launching process 989: /sbin/prime-switch
[+1.56s] DEBUG: Process 989 exited with return value 0
[+1.56s] DEBUG: Seat seat0: Exit status of /sbin/prime-switch: 0
[+1.56s] DEBUG: Seat seat0: Stopping session
[+1.56s] DEBUG: Seat seat0: Session stopped
[+1.56s] DEBUG: Seat seat0: Stopping display server, no sessions require it
[+1.56s] DEBUG: Seat seat0: Stopping; greeter display server failed to start
[+1.56s] DEBUG: Seat seat0: Stopping
[+1.56s] DEBUG: Seat seat0: Stopped
[+1.56s] DEBUG: Required seat has stopped
[+1.56s] DEBUG: Stopping display manager
[+1.56s] DEBUG: Display manager stopped
[+1.56s] DEBUG: Stopping daemon
[+1.58s] DEBUG: Exiting with return value 1
[+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.00s] DEBUG: Starting Light Display Manager 1.26.0, UID=0 PID=995
[+0.00s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-disable-guest.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-disable-log-backup.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-greeter-wrapper.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-guest-wrapper.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-slick-greeter.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-ubuntu-mate.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-ubuntu.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-xserver-command.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/90-nvidia.conf
[+0.00s] DEBUG:   [SeatDefaults] is now called [Seat:], please update this configuration
[+0.00s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
[+0.00s] DEBUG: Registered seat module local
[+0.00s] DEBUG: Registered seat module xremote
[+0.00s] DEBUG: Registered seat module unity
[+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
[+0.02s] DEBUG: Monitoring logind for seats
[+0.02s] DEBUG: New seat added from logind: seat0
[+0.02s] WARNING: Seat type 'xlocal' is deprecated, use 'type=local' instead
[+0.03s] DEBUG: Seat seat0: Loading properties from config section Seat:
[+0.03s] DEBUG: Seat seat0: Starting
[+0.03s] DEBUG: Seat seat0: Creating user session
[+0.03s] DEBUG: Loading users from org.freedesktop.Accounts
[+0.03s] DEBUG: User /org/freedesktop/Accounts/User1000 added
[+0.06s] DEBUG: Seat seat0: Creating display server of type x
[+0.07s] DEBUG: Using VT 7
[+0.07s] DEBUG: Seat seat0: Starting local X display on VT 7
[+0.07s] DEBUG: XServer 0: Logging to /var/log/lightdm/x-0.log
[+0.07s] DEBUG: XServer 0: Writing X server authority to /var/run/lightdm/root/:0
[+0.07s] DEBUG: XServer 0: Launching X Server
[+0.07s] DEBUG: Launching process 1001: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+0.07s] DEBUG: XServer 0: Waiting for ready signal from X server :0
[+0.07s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
[+0.07s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0
[+0.80s] DEBUG: Process 1001 terminated with signal 6
[+0.80s] DEBUG: XServer 0: X server stopped
[+0.80s] DEBUG: Releasing VT 7
[+0.80s] DEBUG: XServer 0: Removing X server authority /var/run/lightdm/root/:0
[+0.80s] DEBUG: Seat seat0: Display server stopped
[+0.80s] DEBUG: Launching process 1003: /sbin/prime-switch
[+0.81s] DEBUG: Process 1003 exited with return value 0
[+0.81s] DEBUG: Seat seat0: Exit status of /sbin/prime-switch: 0
[+0.81s] DEBUG: Seat seat0: Stopping session
[+0.81s] DEBUG: Seat seat0: Session stopped
[+0.81s] DEBUG: Seat seat0: Stopping display server, no sessions require it
[+0.81s] DEBUG: Seat seat0: Active display server stopped, starting greeter
[+0.81s] DEBUG: Seat seat0: Creating greeter session
[+0.81s] DEBUG: Seat seat0: Creating display server of type x
[+0.81s] DEBUG: Using VT 7
[+0.81s] DEBUG: Seat seat0: Starting local X display on VT 7
[+0.81s] DEBUG: XServer 0: Logging to /var/log/lightdm/x-0.log
[+0.81s] DEBUG: XServer 0: Writing X server authority to /var/run/lightdm/root/:0
[+0.81s] DEBUG: XServer 0: Launching X Server
[+0.81s] DEBUG: Launching process 1006: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+0.81s] DEBUG: XServer 0: Waiting for ready signal from X server :0
[+1.63s] DEBUG: Process 1006 terminated with signal 6
[+1.63s] DEBUG: XServer 0: X server stopped
[+1.63s] DEBUG: Releasing VT 7
[+1.63s] DEBUG: XServer 0: Removing X server authority /var/run/lightdm/root/:0
[+1.63s] DEBUG: Seat seat0: Display server stopped
[+1.63s] DEBUG: Launching process 1008: /sbin/prime-switch
[+1.64s] DEBUG: Process 1008 exited with return value 0
[+1.64s] DEBUG: Seat seat0: Exit status of /sbin/prime-switch: 0
[+1.64s] DEBUG: Seat seat0: Stopping session
[+1.64s] DEBUG: Seat seat0: Session stopped
[+1.64s] DEBUG: Seat seat0: Stopping display server, no sessions require it
[+1.64s] DEBUG: Seat seat0: Stopping; greeter display server failed to start
[+1.64s] DEBUG: Seat seat0: Stopping
[+1.64s] DEBUG: Seat seat0: Stopped
[+1.64s] DEBUG: Required seat has stopped
[+1.64s] DEBUG: Stopping display manager
[+1.64s] DEBUG: Display manager stopped
[+1.64s] DEBUG: Stopping daemon
[+1.65s] DEBUG: Exiting with return value 1
[+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.00s] DEBUG: Starting Light Display Manager 1.26.0, UID=0 PID=1014
[+0.00s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-disable-guest.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-disable-log-backup.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-greeter-wrapper.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-guest-wrapper.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-slick-greeter.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-ubuntu-mate.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-ubuntu.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-xserver-command.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/90-nvidia.conf
[+0.00s] DEBUG:   [SeatDefaults] is now called [Seat:], please update this configuration
[+0.00s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
[+0.00s] DEBUG: Registered seat module local
[+0.00s] DEBUG: Registered seat module xremote
[+0.00s] DEBUG: Registered seat module unity
[+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
[+0.02s] DEBUG: Monitoring logind for seats
[+0.02s] DEBUG: New seat added from logind: seat0
[+0.02s] WARNING: Seat type 'xlocal' is deprecated, use 'type=local' instead
[+0.02s] DEBUG: Seat seat0: Loading properties from config section Seat:
[+0.02s] DEBUG: Seat seat0: Starting
[+0.02s] DEBUG: Seat seat0: Creating user session
[+0.02s] DEBUG: Loading users from org.freedesktop.Accounts
[+0.02s] DEBUG: User /org/freedesktop/Accounts/User1000 added
[+0.05s] DEBUG: Seat seat0: Creating display server of type x
[+0.06s] DEBUG: Using VT 7
[+0.06s] DEBUG: Seat seat0: Starting local X display on VT 7
[+0.06s] DEBUG: XServer 0: Logging to /var/log/lightdm/x-0.log
[+0.06s] DEBUG: XServer 0: Writing X server authority to /var/run/lightdm/root/:0
[+0.06s] DEBUG: XServer 0: Launching X Server
[+0.06s] DEBUG: Launching process 1020: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+0.06s] DEBUG: XServer 0: Waiting for ready signal from X server :0
[+0.06s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
[+0.06s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0
[+0.90s] DEBUG: Process 1020 terminated with signal 6
[+0.90s] DEBUG: XServer 0: X server stopped
[+0.90s] DEBUG: Releasing VT 7
[+0.90s] DEBUG: XServer 0: Removing X server authority /var/run/lightdm/root/:0
[+0.90s] DEBUG: Seat seat0: Display server stopped
[+0.90s] DEBUG: Launching process 1023: /sbin/prime-switch
[+0.91s] DEBUG: Process 1023 exited with return value 0
[+0.91s] DEBUG: Seat seat0: Exit status of /sbin/prime-switch: 0
[+0.91s] DEBUG: Seat seat0: Stopping session
[+0.91s] DEBUG: Seat seat0: Session stopped
[+0.91s] DEBUG: Seat seat0: Stopping display server, no sessions require it
[+0.91s] DEBUG: Seat seat0: Active display server stopped, starting greeter
[+0.91s] DEBUG: Seat seat0: Creating greeter session
[+0.91s] DEBUG: Seat seat0: Creating display server of type x
[+0.91s] DEBUG: Using VT 7
[+0.91s] DEBUG: Seat seat0: Starting local X display on VT 7
[+0.91s] DEBUG: XServer 0: Logging to /var/log/lightdm/x-0.log
[+0.91s] DEBUG: XServer 0: Writing X server authority to /var/run/lightdm/root/:0
[+0.91s] DEBUG: XServer 0: Launching X Server
[+0.91s] DEBUG: Launching process 1026: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+0.91s] DEBUG: XServer 0: Waiting for ready signal from X server :0
[+1.62s] DEBUG: Process 1026 terminated with signal 6
[+1.62s] DEBUG: XServer 0: X server stopped
[+1.62s] DEBUG: Releasing VT 7
[+1.62s] DEBUG: XServer 0: Removing X server authority /var/run/lightdm/root/:0
[+1.62s] DEBUG: Seat seat0: Display server stopped
[+1.62s] DEBUG: Launching process 1028: /sbin/prime-switch
[+1.63s] DEBUG: Process 1028 exited with return value 0
[+1.63s] DEBUG: Seat seat0: Exit status of /sbin/prime-switch: 0
[+1.63s] DEBUG: Seat seat0: Stopping session
[+1.63s] DEBUG: Seat seat0: Session stopped
[+1.63s] DEBUG: Seat seat0: Stopping display server, no sessions require it
[+1.63s] DEBUG: Seat seat0: Stopping; greeter display server failed to start
[+1.63s] DEBUG: Seat seat0: Stopping
[+1.63s] DEBUG: Seat seat0: Stopped
[+1.63s] DEBUG: Required seat has stopped
[+1.63s] DEBUG: Stopping display manager
[+1.63s] DEBUG: Display manager stopped
[+1.63s] DEBUG: Stopping daemon
[+1.64s] DEBUG: Exiting with return value 1
[+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.00s] DEBUG: Starting Light Display Manager 1.26.0, UID=0 PID=1034
[+0.00s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-disable-guest.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-disable-log-backup.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-greeter-wrapper.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-guest-wrapper.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-slick-greeter.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-ubuntu-mate.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-ubuntu.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-xserver-command.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/90-nvidia.conf
[+0.00s] DEBUG:   [SeatDefaults] is now called [Seat:], please update this configuration
[+0.00s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
[+0.00s] DEBUG: Registered seat module local
[+0.00s] DEBUG: Registered seat module xremote
[+0.00s] DEBUG: Registered seat module unity
[+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
[+0.02s] DEBUG: Monitoring logind for seats
[+0.02s] DEBUG: New seat added from logind: seat0
[+0.02s] WARNING: Seat type 'xlocal' is deprecated, use 'type=local' instead
[+0.02s] DEBUG: Seat seat0: Loading properties from config section Seat:
[+0.02s] DEBUG: Seat seat0: Starting
[+0.02s] DEBUG: Seat seat0: Creating user session
[+0.03s] DEBUG: Loading users from org.freedesktop.Accounts
[+0.03s] DEBUG: User /org/freedesktop/Accounts/User1000 added
[+0.05s] DEBUG: Seat seat0: Creating display server of type x
[+0.06s] DEBUG: Using VT 7
[+0.06s] DEBUG: Seat seat0: Starting local X display on VT 7
[+0.06s] DEBUG: XServer 0: Logging to /var/log/lightdm/x-0.log
[+0.06s] DEBUG: XServer 0: Writing X server authority to /var/run/lightdm/root/:0
[+0.06s] DEBUG: XServer 0: Launching X Server
[+0.06s] DEBUG: Launching process 1039: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+0.06s] DEBUG: XServer 0: Waiting for ready signal from X server :0
[+0.06s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
[+0.06s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0
[+0.89s] DEBUG: Process 1039 terminated with signal 6
[+0.89s] DEBUG: XServer 0: X server stopped
[+0.89s] DEBUG: Releasing VT 7
[+0.89s] DEBUG: XServer 0: Removing X server authority /var/run/lightdm/root/:0
[+0.89s] DEBUG: Seat seat0: Display server stopped
[+0.89s] DEBUG: Launching process 1043: /sbin/prime-switch
[+0.90s] DEBUG: Process 1043 exited with return value 0
[+0.90s] DEBUG: Seat seat0: Exit status of /sbin/prime-switch: 0
[+0.90s] DEBUG: Seat seat0: Stopping session
[+0.90s] DEBUG: Seat seat0: Session stopped
[+0.90s] DEBUG: Seat seat0: Stopping display server, no sessions require it
[+0.90s] DEBUG: Seat seat0: Active display server stopped, starting greeter
[+0.90s] DEBUG: Seat seat0: Creating greeter session
[+0.90s] DEBUG: Seat seat0: Creating display server of type x
[+0.90s] DEBUG: Using VT 7
[+0.90s] DEBUG: Seat seat0: Starting local X display on VT 7
[+0.90s] DEBUG: XServer 0: Logging to /var/log/lightdm/x-0.log
[+0.90s] DEBUG: XServer 0: Writing X server authority to /var/run/lightdm/root/:0
[+0.90s] DEBUG: XServer 0: Launching X Server
[+0.90s] DEBUG: Launching process 1046: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+0.91s] DEBUG: XServer 0: Waiting for ready signal from X server :0
[+1.65s] DEBUG: Process 1046 terminated with signal 6
[+1.65s] DEBUG: XServer 0: X server stopped
[+1.65s] DEBUG: Releasing VT 7
[+1.65s] DEBUG: XServer 0: Removing X server authority /var/run/lightdm/root/:0
[+1.65s] DEBUG: Seat seat0: Display server stopped
[+1.65s] DEBUG: Launching process 1048: /sbin/prime-switch
[+1.66s] DEBUG: Process 1048 exited with return value 0
[+1.66s] DEBUG: Seat seat0: Exit status of /sbin/prime-switch: 0
[+1.66s] DEBUG: Seat seat0: Stopping session
[+1.66s] DEBUG: Seat seat0: Session stopped
[+1.66s] DEBUG: Seat seat0: Stopping display server, no sessions require it
[+1.66s] DEBUG: Seat seat0: Stopping; greeter display server failed to start
[+1.66s] DEBUG: Seat seat0: Stopping
[+1.66s] DEBUG: Seat seat0: Stopped
[+1.66s] DEBUG: Required seat has stopped
[+1.66s] DEBUG: Stopping display manager
[+1.66s] DEBUG: Display manager stopped
[+1.66s] DEBUG: Stopping daemon
[+1.67s] DEBUG: Exiting with return value 1

So sorry, we've been a little behind schedule as our new edgetpu runtime release. The issues looks like lightdm failed to start due to xserver stopping. I'm not an expert in lightdm, but as I mentioned, our drivers shouldn't do anything with the lightdm process.
Are able to turn it back on with this:
$ lightdm --test-mode --debug

I imagine that this could be a side effect of the weird hack we did to fix the linux-header package, for this I suggest contacting the Rock Pi team for help as linux-headers should have been compiled correctly in the first place. Another thing I'd check is to make sure that the board are getting enough power.

@Namburger FYI I'm experiencing the same issue as OP of the TPU pcie driver affecting Debian KDE on Rock Pi (mine is 4C). Desktop loads fine before installing the TPU drivers, then after the TPU drivers are installed KDE does not load (blank screen with cursor).
Once gasket-dkms and libedgetpu1-std are uninstalled through a remote shell session, the KDE comes back after reboot. This can be reproduced many times over.
There appears to be an interaction between the drivers and KDE, where the driver code prevents the subsequent init/load of KDE. Manual compilation of literally a handful of files in the linux-headers package (recordmcount.c, fixdep.c, file2alias.c, devicetable-offsets.c, modpost.c) referred above as a weird hack could not possibly cause the side-effect of hosing the entire KDE. More probable is a resource conflict created by the installed driver.
This may be regarded as low severity but should be evaluated for cause and remedy. Since in this case desktop and TPU drivers cannot coexist, users who need to use KDE for normal operation are effectively blocked from being able to use your product.

Hi!
Could you check /var/log/Xorg.0.log ?
If you see msg like Cannot run in framebuffer mode. Please specify busIDs        for all framebuffer devices  you should check X.org config files. In my case, I fixed it by adding to /etc/X11/xorg.conf.d/01-armbian-defaults.conf:
Section "Device"
    Identifier	"Rockchip"
    Driver "fbdev"
EndSection

It looks like xserver is confused with TPU pci device. Normally it see only framebuffer device. It does not know what device it should use so it shutdowns.

This confirms the interaction between KDE (X11) and tpu driver/software suspected earlier.
@marcin-kamionowski did you get it all to work reliably with the Radxa software after adding the above change? I first saw this issue with the Radxa linux distrib for Rock Pi 4C but since it didn't have a good camera (imx219) support I abandoned the OEM distrib. Armbian server (no desktop) works ok for me.


ExploreOffers with tests

subjectId is removed from searchParams when you select the category
https://github.com/Space2Study-UA-1156/Client-01/assets/56509285/28ddcb8f-723e-45e5-8051-b1f891ee2d9a

Search parameters for the field (tutor) are now set only when you click the Search or Enter button.


Weight of SO

Thanks for skia4delphi — looks great!
One question: is there a way to reduce the size of SO-files if I only need Lottie support for Android? I have an app ~15MB. Now with SO-files its weight is ~20+MB :(

Hi @kazuser,
The best way to reduce the size would be through static linking. We plan to implement static linking on all non-windows platforms in the future. Now this is not our current focus.


Cart is not user safe

@Crinsane
Pertaining to a previous issue I raised #163, I disagree with the point that the Cart is user safe.
I have two sample users. I added an item using one of the users. Logged out. Then I logged in using the second user account. I can still view the items in the shopping cart added by the previous user. And I am pretty sure that both the accounts are different, as one is an account having admin privileges and the other is not.
I understand the concept of the usage of sessions here. If I log in the same user through a different browser, one browser shows the products in the cart, while other browser doesnt show it.
However, my concern is, if 2 users use the same browser to view the carts, then the contents should be separate for both right? Destroying the contents of the cart when the user logs out is a solution. But ideally, shouldnt be.

I'll look into this later. But for now the best way to make a cart (the session) specific for a given user, is use a custom instance. So for instance try something like: Cart::instance(auth()->id())->add(...);

The other option would indeed be to clear the cart session when the user logs out.

Yes it wiil by nice to look into this i have abs.same problem.

@Crinsane
Thanks for the tip.I ended up creating my own small shopping cart implementation using Eloquent databases instead of using Sessions. Persistence served my purpose. Your tip was working, but I didnt want any user to lose the items they added to their cart if they didnt check out immediately.

Ok but this with instance is working fine,i just have doubt thath this is right method.

This is the way how i did it. I'm defining 2 listeners in EventServiceProvider
'auth.login' => [
'App\Listeners\RestoreCartOnLogin',
],
'auth.logout' => [
'App\Listeners\StoreCartOnLogout',
],
then 2 listeners. one with method Cart::store(auth()->id());, other Cart::restore(auth()->id());.Everythink work like charm.
You need Cart::instance(auth()->id()) like Crinsane tip.
Best regards.

@Crinsane
Is there any method of the Cart class which can be used to save all the cart items in a database?
Best Regards
Vozo

Is this issue still open?

I save shopping cart to database with Cart::store(auth()->id()); It works..
But how can I fetch that row from the database? I tried Cart::restore(auth()->id()), but it only deletes the row from the database..


y-axis forceNiceScale only works when the range is larger than 10

forceNiceScale option, https://apexcharts.com/docs/options/yaxis/#forceNiceScale works fine when the range between min/max value is larger than 10, as can be seen in this codepen example:
https://codepen.io/anon/pen/agxvxO
But when the difference is less than 10, the value rounding is not working as can be seen here:
https://codepen.io/anon/pen/gNyaPw

What about below 2? This is NEEDED.

I have the same issue with sub-2 ranges.

Same here. It's impossible to get nice scales for percentage figures

Up on this.
With percentages, if there are values equal to 100%, yaxis displays 108, which makes no sense when max is set on 100…

any update on this? currently seeing the issue when the number is 2 or less


Carthage compatibility

Version 1.0.3 is not Carthage compatible.
carthage update --platform ios
...
Dependency "AZAPicker" has no shared framework schemes for any of the platforms: iOS

fixed in 1.0.5


[Quest] quest is now called checklist

Description
The other day, I had a chat with a friend who also uses Raycast. He was looking for an extension that offers the same functionality as Quest, but unfortunately, he couldn't find it.
That's why I propose renaming the extension to Checklist. This pull request implements this change.
Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

I think just adding a keywords field could be a better option, as it keeps the unique name, but also allows for searching with checklist
kinda unrelated:
the todo list extension seems extremely similar...

I do agree, keywords could also be the solution here @zeekrey

Thank you guys for the feedback. I apologize for the delay in my response. I thought about it and I have come to the conclusion that "Quest" was not the most suitable name initially. In my opinion, a tool or extension should be named based on its functionality and how it can assist users. Therefore, I believe Checklist is a better choice.
I also appreciate the suggestion of adding keywords. I have taken that advice and included some relevant keywords to enhance the visibility of the extension.
Furthermore, I took the time to explore the Todo list extension. It is a straightforward implementation of a todo list. On the other hand, Quest/Checklist is an extension that enables the creation of checklists (which can also be referred to as todo lists) that can be completed repeatedly. By utilizing a checklist, the overall quality of repetitive tasks can be significantly improved.


test: Test PR from an unknown account -FOR TESTING ONLY - DO NOT MERGE

This PR was only to test if an external contributor is able to open a PR without scheduling the CI automatically. This works, someone frrom Epinio team should activate the CI, then the PR could be reviewed and accepted, then merging.
Close this fake PR.


docs: Document ELF and ACPI tables

Document ELF and ACPI tables code and structures.
This is related to issue #74 Document COCONUT-SVSM.

@00xc this is the new PR, as you can see I have included the discussed changes as well as code examples for ELF. We need to ignore the Rust check in this case because it can't use my_elf_parser which ELF's doc code examples depends on.

@00xc this is the new PR, as you can see I have included the discussed changes as well as code examples for ELF. We need to ignore the Rust check in this case because it can't use my_elf_parser which ELF's doc code examples depends on.

Um, no, we just need to provide valid code snippets.
For example, the doctest for Elf64AddrRange::len() is failing because the example not only has an invalid import, but also is invalid code - Elf64Addr it is an alias, not a type constructor. This fixes it:
diff --git a/src/elf/mod.rs b/src/elf/mod.rs
index 379ddca..bf04804 100644
--- a/src/elf/mod.rs
+++ b/src/elf/mod.rs
@@ -216,11 +216,11 @@ impl Elf64AddrRange {
     /// # Examples
     ///
     /// ```rust
-    /// use my_elf_parser::{Elf64AddrRange, Elf64Addr};
+    /// use svsm::elf::{Elf64AddrRange, Elf64Addr};
     ///
     /// let range = Elf64AddrRange {
-    ///     vaddr_begin: Elf64Addr(0x1000),
-    ///     vaddr_end: Elf64Addr(0x1100),
+    ///     vaddr_begin: 0x1000,
+    ///     vaddr_end: 0x1100,
     /// };
     ///
     /// assert_eq!(range.len(), 0x100);

Here's another example: the patch below fixes the load_acpi_cpu_info() doctest. You will also notice the generated docs will only include the relevant parts of the code, since we use #.

diff --git a/src/acpi/tables.rs b/src/acpi/tables.rs
index 9d8b8d8..74660ec 100644
--- a/src/acpi/tables.rs
+++ b/src/acpi/tables.rs
@@ -450,10 +450,22 @@ pub struct ACPICPUInfo {
 /// # Example
 ///
 /// ```
-/// use svsm::acpi::load_acpi_cpu_info;
+/// use svsm::acpi::tables::load_acpi_cpu_info;
 /// use svsm::fw_cfg::FwCfg;
+/// use svsm::io::IOPort;
 ///
-/// let fw_cfg = FwCfg::new(/* initialize your FwCfg interface */);
+/// struct MyIo;
+///
+/// impl IOPort for MyIo {
+/// #     fn outb(&self, _port: u16, _value: u8) {}
+/// #     fn outw(&self, _port: u16, _value: u16) {}
+/// #     fn inb(&self, _port: u16) -> u8 { 0 }
+/// #     fn inw(&self, _port: u16) -> u16 { 0 }
+///     // your implementation
+/// }
+///
+/// let io = MyIo;
+/// let fw_cfg = FwCfg::new(&io);
 /// match load_acpi_cpu_info(&fw_cfg) {
 ///     Ok(cpu_info) => {
 ///         for info in cpu_info {

Happy to help! Doctests look good, but there's still a few uses of square brackets on variable names, we should get rid of those.

@00xc I have updated the PR following your feedback :+1:

Okay this looks really good now, but I just noticed there are still some warnings with cargo doc --document-private-items (just realized this flag exists). They should be pretty straightforward to fix.

You're correct @00xc . I have fixed those warnings :)


Bulk extension support

Hey,
Is the bulk extension already supported in some way?
If not, what would be the best way to add it?

Currently the project doesn't support any extensions. So there's some up front work that needs to be done around supporting extensions in the mime types. I also want to make extensions optional through the configuration options.
Once that's done I anticipate adding support for bulk should be fairly straight forward. The architecture was designed with this in mind. If bulk is supported the Request should create multiple Operations. I believe that's all that will need to be done, though there may be some additional changes needed to generate the proper responses.
I'd also like to consider the option of supporting custom extensions (code that doesn't exist in the JR gem). It may make sense to create all extensions as custom and provide appropriate hooks in the base code. So I'd like to take the implementation slowly see if we can provide a nice architecture to allow adding extensions.

@lgebhardt Thanks for the detailed answer. I think we could need the bulk extension in the next few months. Let me know when the front work is done and how I could help from there!

Any update on the bulk extension support. I will need it soon, maybe I can help with the implementation? I've the feeling that adding extensions support would required a deep understanding of JR.

What's the status on the Bulk Extension?  We have "Extensions are an experimental feature and should be considered a work in progress. There is no official support for extensions in the base JSON API specification." and "The 'Bulk extension' is an official extension of the JSON API specification." That leaves me wondering how much things will change in the future.

JSON API 1.1 has two primary goals:

support for an extension mechanism
an official extension or two to support multiple operations in a single request

We are trying to complete 1.1 beta by Sept. 30. 1.1 final should be launched Dec. 31.
Just today we have put forward a proposal for an "operations extension" - see https://github.com/json-api/json-api/issues/795.  This extension will probably replace the json-patch extension, which is not additive to the base spec.
It is likely that the bulk extension will also be supported as an "official extension".
We still need to formalize the extension mechanism.
Hopefully JR can begin supporting these extensions after 1.1 beta. Of course, there's still much TBD between now and then.

Thanks for the updates, sounds promising!

Any updates on this?

+1

+1

I'm wondering if this extension was recently deprecated via https://github.com/json-api/json-api/pull/1026
@dgeb am I reading that correctly? If so, would this issue get closed?

+1

+1

Will give this a whirl, thank you

+1

I believe the bulk extension has been deprecated?

Yes, with the extension deprecated this should have been closed a while ago.


Correct Typo: "802x86" becomes "80x86"

So weird that this error propagated to several different  another page.

@veganaize : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@ghogen Can you review this pull request? Thanks.

Thanks @ghogen and @veganaize


sensors: ccs811: Implement sampling mode switching

CCS811 measurement mode selection is implemented with sensor attributes.
A new measurement interval sensor attribute is introduced.

Codecov Report

Merging #7320 into master will decrease coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           master   #7320      +/-   ##
=========================================
- Coverage      55%     55%   -0.01%
=========================================
  Files         474     474
  Lines       51719   51719
  Branches     9935    9935
=========================================
- Hits        28447   28446       -1
- Misses      19310   19311       +1
  Partials     3962    3962

Impacted Files
Coverage Δ

lib/posix/pthread.c
69.34% <0%> (-0.51%)
:arrow_down:

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 c5615aa...2fb2df0. Read the comment docs.

@Mani-Sadhasivam I've not implemented switching to Mode 4 because SENSOR_CHAN_CO2 and SENSOR_CHAN_VOC readings cannot be used in Mode 4. I'm mostly just interested in changing the measurement mode due to the lower power consumption of the other modes.

@tkln SInce we support CURRENT and VOLTAGE measurements in the driver, the corresponding mode should also be enabled. I can't figure out a valid usecase for this but it would be good to have.

@Mani-Sadhasivam I've now added Mode 4 and also made the polling delays to adjust accordingly with the measurement time.


Can't install on windows

pip install isn't working, and I tried manually installing as well. Am I missing something?
PS super dope project!!

Hi!
Thanks for your interest in the project! :D
It seems that a dependency (n2) of my rendering lib is not supporting windows yet.
You can manually install https://github.com/matrach/img2unicode with commenting out the "n2" from the setup.py file, but
only the "block renderers" (also called dual renderers) will work. You will have to use plt.show('block')
Also, if you're using standard Windows terminal, the rendering will look buggy due to a hacky ZERO LENGHT SPACE inserted after every character, in order to fix right-to-left handling by Gnome Terminal – in Windows' cmd it occupies a separate cell.
I was going to write some terminal detection to infer whether the RTL-sentinel should be emitted, but... I'm going to do that some day...
Anyway, you're welcome to send PR-s :)

Fixed in 0.1a4. Just update the package :).


Issue in after_id being automatically called

Hi @FahadNoor I was trying to get the jobs data of an organization, and in the params dictionary it is automatically sending after_id, even when the limit is 2. Everytime limit 2 and updated after_id is being sent to crunchbase, this leads to continuous data pull. I tried to create custom Pagination and and updated the query builder a little bit to only send limit not after_id along with it. But could you please explain what can be a solution?
right now my custom pagination code is below:
  class CustomPaginated(Paginated):
      def __init__(self, api_client, entity_id, card_id, card_field_ids, limit):
          super().__init__()
          self.api_client = api_client
          self.entity_id = entity_id
          self.card_id = card_id
          self.card_field_ids = card_field_ids
          self.limit = limit
          self.next_id = None
          self.previous_id = None
          self.total_results = 0

      def set_next(self, current_list):
          pass

      def set_previous(self, current_list):
          pass

      def execute(self) -> list:
          if self.total_results >= self.limit:
              return []

          params = {
              'limit': self.limit,
              'card_field_ids': ','.join(self.card_field_ids)
          }
          response = self.api_client.request(self.entity_id, self.card_id, params)
          data = response.get('data', [])
          self.total_results += len(data)

          if self.total_results >= self.limit:
              return data[:self.limit - self.total_results]

          return data

      def reset_pagination(self):
          self.next_id = None
          self.previous_id = None
          self.total_results = 0

Hi @yash85763, can you please share the code so that I can reproduce the issue? I am not clear on what exactly is the issue you are facing.

card_fields_ids = ['is_current', 'person_identifier', 'identifier', 'short_description',
                      'organization_identifier', 'created_at', 'started_on', 'ended_on',
                      'employee_featured_order', 'title', 'updated_at', 'job_type']
# Access the organizations API
org_api = pycb.organizations_api()

# Define the cards for organization jobs
cards = Cards.Organization

call_limit = 1

# Fetch the organization entity data
entity = org_api.get_cards(
    entity_id=Company_2_look_4,
    card_id= cards.jobs,
    card_field_ids=card_fields_ids,
    limit=call_limit
)

output:
With params: {'limit': 1, 'card_field_ids': 'ended_on,title,short_description,organization_identifier,started_on,employee_featured_order,person_identifier,created_at,job_type,updated_at,is_current,identifier'}
Response Status Code: 200
and the output continues with updated next_id and previous_id


Post-schema refactor fixes

This PR:

Implements the TODO in _search() mentioned in code review
Fixes up RST parsing of schema help strings

For the latter, I decided move to processing schelp using the Python standard "trim()" function for preprocessing docstrings that we were already using for the flows/pdks/libs/etc. documentation. The previous regex approach was stripping away newlines, which made it impossible to do fancier RST formatting, such as lists.
The new approach strips off a calculated amount of leading spaces to preserve additional indentation (for inserting things like codeblocks), and preserves newlines. A consequence of this change is that there will be newlines in the help string, but I think this is a worthwhile tradeoff, since it makes the actual docs look much nicer:
Before

After

This is great. Thank you fro the clean up! Yes, this is much better. At some point, we may make a pass through the schema and expand some of the long descriptions and this is great preparation.


[BUG] v2  Beta - Module error in console

Describe the bug
When i activate the Module Beta i get an error in the console. If i try to open the calendar from the sidebar, i get another error.
To Reproduce
Steps to reproduce the behavior:

Start the world
activate the module
try to open the tool in the sidebar

Screenshots
errors:

Foundry Information

Foundry Version: [9.255]
Game System: [DSA/TDE 5th Edition Version 3.2.3]
Simple Calendar Configuration: [no config]

Browser (please complete the following information):

OS: [WIN10]
Browser [chrome]
Browser Version [99]

Hey, sorry about this. It is an issue when using languages other than English.
Switching to English will allow the module to load.
Or if you are comfortable in doing this you can extract the attached zip in the directory where Foundry stores its data, open the modules folder, then the simple calendar folder and finally the lang folder
( on windows it would be %LocalAppData%\FoundryVTT\Data\modules\foundryvtt-simple-calendar\lang )
lang.zip
I have made the fix and it will be in the next version of the beta but this would allow you do not have to wait for that to be released.

Ah thank you. I used the zip file and it worked. Now i can start testing.


Can't checkout particular MAJOR-MINOR-BUILD

I am trying the following commands:
docker pull anapsix/alpine-java:8u202b08
docker pull anapsix/alpine-java:8u172b11
and get the outputs:
Error response from daemon: manifest for anapsix/alpine-java:8u202b08 not found
Error response from daemon: manifest for anapsix/alpine-java:8u172b11 not found
What is the problem with these particular builds?

you need to pick server-jre or jdk
docker pull anapsix/alpine-java:8u172b11_server-jre
docker pull anapsix/alpine-java:8u172b11_jdk
docker pull anapsix/alpine-java:8u202b08_jdk
docker pull anapsix/alpine-java:8u202b08_server-jre

see available tags on Docker Hub
https://cloud.docker.com/repository/docker/anapsix/alpine-java/tags


MQTT support

What kind of issue is this?

[x] Feature Request

MQTT is a lightweight messaging (pub-sub) protocol. Right now I'm using another dependency for this, but seeing as it is a networking protocol, it'd be a nice-to-have in the OkHttp dependency itself, so that I don't need another one.
Here is the dependency I currently use:
https://github.com/eclipse/paho.mqtt.android

Unlikely we’ll do this. We wanna stay focused on HTTP.

@swankjesse do yo change your mind?

No. OkHttp is broad enough in scope!

@swankjesse  we need help, can you give some advice for okhttp + mqtt

@swankjesse we need help, can you give some advice for okhttp + mqtt

at @gojek we create an abstraction on top of Paho. which you can see at https://github.com/gojek/courier-android


remove expand facets in getRecords' parameters

Hi
expanded_facet is not in getRecords parameter after Bug 14419 commit, in Koha since 19.11.00 release.

Added in PR #90


Delay in updating seasons/shows aired episodes information

If someone wouldn't mind helping me out here, it seems there is often a large delay in updating the aired episodes value for both season and show items.
I've been doing some checks over the past few days it often seems to take a day or two for this information to be updated on some item.
As of writing this issue, Brooklyn Nine Nine is currently showing:  "aired_episodes": 125 while the last released episode was released near 5 hours ago.  I apologize as I know this is not as big of a gap that I'm describing but it's an example of the issue.
The Last Episode API response for the show in question returns the following aired/updated information:
"first_aired": "2019-04-26T01:00:00.000Z",
"updated_at": "2019-04-26T05:07:49.000Z",

Is it possible the show/season information is not being refreshed when a related episode item is aired/updated?

This is most probably due to caching. Trakt can't invalidate the cache of specific requests like that every time an info is updated. Try to have a look at the cache headers of the response to make sure.

Yes, this is because of how those methods are cached. We unfortunately can’t invalidate quicker with the Cloudflare plan we are using.
Sent with GitHawk

That's fair enough, I'll make some changes on my end to try and identify and workaround it using the users local database.
I appreciate the help.


⚠ Phillips Ormonde Fitzpatrick - IPSys has degraded performance

In 5f353b5, Phillips Ormonde Fitzpatrick - IPSys (https://ipsys.pof.com.au) experienced degraded performance:

HTTP code: 200
Response time: 16904 ms

Resolved: Phillips Ormonde Fitzpatrick - IPSys performance has improved in d60d661 after 10 minutes.


cc.MenuItemSprite.extend didn't work in jsb

Cocos2d-js 3.2,  cc.MenuItemSprite.extend didn't work, it will be break when MenuItem is click.

Duplicated: https://github.com/cocos2d/cocos2d-js/issues/1251
I solved it, and will send a PR in a while

I tested in 3.3, it's ok now, but selected() and unselected() can't be override in jsb.

You are right, these functions can not be bound in JSB yet, it's due to complication of JSB's implementation


Installaition question“/home/geff/kaldi-ctc-master/tools/warp-ctc/src/ctc_entrypoint.cu(1): error: this declaration has no storage class or type specifier”

Hello,when i install warp-ctc ,i get this question:
[ 14%] Building NVCC (Device) object CMakeFiles/warpctc.dir/src/warpctc_generated_ctc_entrypoint.cu.o
/home/geff/kaldi-ctc-master/tools/warp-ctc/src/ctc_entrypoint.cu(1): error: this declaration has no storage class or type specifier
/home/geff/kaldi-ctc-master/tools/warp-ctc/src/ctc_entrypoint.cu(1): error: expected a ";"
2 errors detected in the compilation of "/tmp/tmpxft_00001c98_00000000-16_ctc_entrypoint.compute_52.cpp1.ii".
CMake Error at warpctc_generated_ctc_entrypoint.cu.o.cmake:266 (message):
Error generating file
/home/geff/kaldi-ctc-master/tools/warp-ctc/build/CMakeFiles/warpctc.dir/src/./warpctc_generated_ctc_entrypoint.cu.o
CMakeFiles/warpctc.dir/build.make:187: recipe for target 'CMakeFiles/warpctc.dir/src/warpctc_generated_ctc_entrypoint.cu.o' failed
make[2]: *** [CMakeFiles/warpctc.dir/src/warpctc_generated_ctc_entrypoint.cu.o] Error 1
CMakeFiles/Makefile2:141: recipe for target 'CMakeFiles/warpctc.dir/all' failed
make[1]: *** [CMakeFiles/warpctc.dir/all] Error 2
Makefile:127: recipe for target 'all' failed
make: *** [all] Error 2
anyone has encountered such problem? Can you give me some advices on this ?Any help would be appreciated .thanks

Can you give more details such as which OS you are on (i.e. Ubuntu version, etc.) and which CUDA version you are using?  Have you modified the source in any way or is this a clean checkout?

Thank you for your reply, the error has been resolved, it seems that I did not install torch. After the installation，the error does not reappear.

I get a similar error (see below).  I'm running CentOS 7, CUDA 7.5.  Any solution that doesn't involve installing Torch?  I'm attempting to use with TensorFlow, so I'd rather not go through the Torch hoops if I don't have to.
make
[ 14%] Building NVCC (Device) object CMakeFiles/warpctc.dir/src/warpctc_generated_reduce.cu.o
[ 28%] Building NVCC (Device) object CMakeFiles/warpctc.dir/src/warpctc_generated_ctc_entrypoint.cu.o
/home/jrein/warp-ctc/src/ctc_entrypoint.cu(1): error: this declaration has no storage class or type specifier
/home/jrein/warp-ctc/src/ctc_entrypoint.cu(1): error: expected a ";"
2 errors detected in the compilation of "/tmp/tmpxft_00004086_00000000-16_ctc_entrypoint.compute_52.cpp1.ii".
CMake Error at warpctc_generated_ctc_entrypoint.cu.o.cmake:282 (message):
Error generating file
/home/jrein/warp-ctc/build/CMakeFiles/warpctc.dir/src/./warpctc_generated_ctc_entrypoint.cu.o
make[2]: *** [CMakeFiles/warpctc.dir/src/warpctc_generated_ctc_entrypoint.cu.o] Error 1
make[1]: *** [CMakeFiles/warpctc.dir/all] Error 2
make: *** [all] Error 2

Can you post the nvcc command line that it is using the try to compile ctc_entrypoint.cu (you can get it show you using make VERBOSE=1.  Just wondering if cmake is throwing something weird in there since I haven't been able to reproduce this.
Are you using gcc 4.8.2 and glibc 2.17?

nvcc command line is below.  Note that it's a non-standard CUDA_BIN_PATH, if that's relevant.
gcc version 6.1.0
glibc version 2.17
/cm/shared/apps/cuda75/toolkit/7.5.18/bin/nvcc /home/jrein/warp-ctc/src/ctc_entrypoint.cu -c -o /home/jrein/warp-ctc/build/CMakeFiles/warpctc.dir/src/./warpctc_generated_ctc_entrypoint.cu.o -ccbin /usr/bin/cc -m64 -Dwarpctc_EXPORTS -Xcompiler ,"-fopenmp","-O2","-fPIC","-g" -gencode arch=compute_30,code=sm_30 -O2 -gencode arch=compute_35,code=sm_35 -gencode arch=compute_50,code=sm_50 -gencode arch=compute_52,code=sm_52 --std=c++11 -Xcompiler -fopenmp -DNVCC -I/cm/shared/apps/cuda75/toolkit/7.5.18/include -I/home/jrein/warp-ctc/include

I suspect the problem comes from using gcc 6.1 which is not supported by cuda.  For cuda 7.5 on CentOS 7.x, only gcc 4.8.2 is supported.  I don't think gcc 6 is supported by any cuda version on any platforms yet.

I get the same error building with gcc 4.8.5, which is what my HPC's cuda was built with.  I suppose 4.8.5 > 4.8.2, but the cuda test scripts and TensorFlow seem to be running fine, so I'm not sure that a cuda compilation error is the issue.

Update: I ended up installing Torch in the hopes that the original poster's fix would work, but no luck; same error.

I get the same error ,later make succes that stop torch or cuda

I experienced this same issue and fixed it.  The problem is that the ctc_entrypoint.cu file needs to be a symlink.  So, go to src dir and run:

rm ctc_entrypoint.cu
ln -s ctc_entrypoint.cpp ctc_entrypoint.cu

Then run make.

@rachelmint  I have the same problem, and I tried your method, but it didn't work.  Here is the Error message:
make
-- cuda found TRUE
-- Building shared library with GPU support
-- Configuring done
-- Generating done
-- Build files have been written to: /warp-ctc-pytorch_bindings/build
[ 16%] Building NVCC (Device) object CMakeFiles/warpctc.dir/src/warpctc_generated_ctc_entrypoint.cu.o
nvcc error   : 'cicc' died due to signal 11 (Invalid memory reference)
nvcc error   : 'cicc' core dumped
CMake Error at warpctc_generated_ctc_entrypoint.cu.o.cmake:264 (message):
Error generating file
/warp-ctc-pytorch_bindings/build/CMakeFiles/warpctc.dir/src/./warpctc_generated_ctc_entrypoint.cu.o
make[2]: *** [CMakeFiles/warpctc.dir/src/warpctc_generated_ctc_entrypoint.cu.o] Error 1
make[1]: *** [CMakeFiles/warpctc.dir/all] Error 2

I experienced this same issue and fixed it. The problem is that the ctc_entrypoint.cu file needs to be a symlink. So, go to src dir and run:

rm ctc_entrypoint.cu
ln -s ctc_entrypoint.cpp ctc_entrypoint.cu

Then run make.

that work，thanks

ctc_entrypoint

thanks a lot

I experienced this same issue and fixed it. The problem is that the ctc_entrypoint.cu file needs to be a symlink. So, go to src dir and run:

rm ctc_entrypoint.cu
ln -s ctc_entrypoint.cpp ctc_entrypoint.cu

Then run make.

@sangenan @jjz-learning Thank you very much. this solution works. Sorry, I mistaked the src dir befor.

i run this instruction 'ln -s ctc_entrypoint.cpp ctc_entrypoint.cu'
but i got  this error

can you help me please

Same issue as @chafikblm

@yash-bhat
for me, I solve it
my problem was in the directory which the file called "ctc_entrypoint.cu" and "ctc_entrypoint.cpp"  exist, I had whitespace
the character " " in the directory so, make sure you don't have whitespace character " "  in both of the directory of file "ctc_entrypoint.cu" and "ctc_entrypoint.cpp"
path1/to/ctc_entrypoint.cpp # without  whitespace character " "
path2/to/ctc_entrypoint.cpp #  without   whitespace character " "
then you can run :

ln -s ctc_entrypoint.cpp ctc_entrypoint.cu

Will work.

@yash-bhat https://github.com/yash-bhat
for me, I solved it
my problem was in the directory which the file called "ctc_entrypoint.cu"
and "ctc_entrypoint.cpp" exist, I had whitespace
the character " " in the directory so, make sure you don't have whitespace
character " " in both of the directories of file "ctc_entrypoint.cu" and
"ctc_entrypoint.cpp"
like that:
path1/to/ctc_entrypoint.cu# without whitespace character " "
path2/to/ctc_entrypoint.cpp # without whitespace character " "
then you can run :
ln -s ctc_entrypoint.cpp ctc_entrypoint.cu
Will work.
Le dim. 24 mai 2020 à 23:13, Yashaswini Bhat<EMAIL_ADDRESS>a
écrit :

Same issue as @chafikblm https://github.com/chafikblm
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/baidu-research/warp-ctc/issues/49#issuecomment-633314428,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANVDBFETYBKUB2QTJ3A5ALDRTGS2PANCNFSM4CUDIY3Q
.

我通过以下方法解决了问题：
如果要使用最新的pytorch 1.8，请安装cuda 10.2而不是cuda11。如果确实使用cuda 11，则需要注释掉CMakeList.txt文件中的第35-38行，也就是这些代码


ws signer delayed reconnect

now the user has to open the wallet first and enter the page where antenna establishes link. Otherwise, the user has to refresh the page. Can we add the feaure for the ws signer to reconnect in delayed cases?

this is a client-side issue


Suggestion: --auto-jobs should maybe use physical core count

Observed behaviour
My CPU has hyperthreading to double the thread count, but there is no time difference between 8 and 16 threads.
Expected behaviour
Using more threads should be faster but may fail due to synchronization or memory copying back and forth or whatever. Not using more cores than necessary could reduce waste until the code and/or Python gets better at multiprocessing.
Resources and exact process needed to replicate
https://psutil.readthedocs.io/en/latest/index.html?highlight=cpu_count#psutil.cpu_count provides the physical core count. Not sure if easily possible without the dependency.
Maybe some people could compare times here between core counts?

I think this is going to be a not-gonna-do-it. Getting "physical" cores is OS-specific and auto-jobs is allowed to be heuristic.


docs: Arrange the usage in README.md file, according to the serial number in the categorical list below.

e5f0b8f solves this issue


OrganisationClaim vs OrganisationTask: authoredOn cardinality and MS does not fit

@NathanPeeters @SmalsJulien ,
The authoredOn field is not present in the logical model. Do we need it from a technical perspective?
Please advise!

see https://github.com/hl7-be/referral/issues/400


[enhancement] clear useless txn log

What type of PR is this：

[ ] bugfix
[ ] feature
[x] enhancement
[ ] refactor
[ ] others

Which issues of this PR fixes ：

Fixes #
Problem Summary(Required) ：

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] I have added user document for my new feature or new function

[FE PR Coverage Check]
:heart_eyes: pass : 30 / 34 (88.24%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/alter/SchemaChangeHandler.java
8
10
80.00%
[1045, 1048]

:large_blue_circle:
com/starrocks/system/HeartbeatMgr.java
10
12
83.33%
[91, 95]

:large_blue_circle:
com/starrocks/transaction/DatabaseTransactionMgr.java
5
5
100.00%
[]

:large_blue_circle:
com/starrocks/transaction/GlobalTransactionMgr.java
7
7
100.00%
[]

run starrocks_admit_test

run starrocks_admit_test


changes in appId

Made final changes

Hi
Your project is complete!  There is nothing else to say other than... it's time to merge it :shipit:
Congratulations! 🎉🔥🔥💯💯

Highlights ✨✨
📌 No Linters error ✅
📌 Descriptive pull request✅
📌 Great working on the functionality✅
📌 Good commit messages ✅
📌Professional README ✅
Optional suggestions
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me in your question so I can receive the notification.

As described in the Code reviews limits policy  you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.


CI: Reduce storybook build output

Currently the storybook build is outputting every % step as it builds to the CI log.  This makes the log hard to parse.  Reducing this by adding the --quiet and adding the --loglevel error.
Testing instructions
Check the output from the build

Click to expand "Build"
Scroll to the bottom, check that the storybook build only reports a failure.

Commands affect:

npm run storybook
npm run build-storybook

Ready-for-merge Checklist
Check off items as they are completed.  Feel free to delete items if they are not applicable.

[x] Expected files: all files in this pull request are related to one request or issue (no stragglers or scope-creep).
[x] Repository compiles and tests pass.

Merging
Please squash when merging and ensure your commit message uses conventional commit formatting.
Be sure to share your updates with the<EMAIL_ADDRESS>mailing list!

Storybook build output looks good! 👍
Build & test step isn't passing 🛑.  I don't think it's related to this change though.

@heyMP Yeah I'm seeing jump links blipping on Vue since the 1.0 merge. The bug fixes we're working on should resolve that.


doctrine.event_subscriber is deprecated

Describe the bug
DoctrineBundle 2.10 deprecated EventSubscribers in favor of EventListeners.
I think that means we need to use the doctrine.event_listener tag in the extension, instead of doctrine.event_subscriber: https://github.com/stof/StofDoctrineExtensionsBundle/blob/main/src/DependencyInjection/StofDoctrineExtensionsExtension.php#L31
However, we'll need to apply multiple tags, one for each event that each listener is listening to.
There's an issue on the doctrine extensions repo (https://github.com/doctrine-extensions/DoctrineExtensions/issues/2615) to update the documentation for this.
To Reproduce
Steps to reproduce the behavior:

Upgrade to DoctrineBundle 2.10+
Be sure to have at least one of the extensions enabled
Clear your cache and check deprecations logs
See User Deprecated: Since symfony/doctrine-bridge 6.3: Using Doctrine subscribers as services is deprecated, declare listeners instead

Expected behavior
No deprecation messages.

The depreciation alert is still present
"stof/doctrine-extensions-bundle": "v1.8.0"
"doctrine/doctrine-bundle": "2.10.2"

@johnkhansrc can you share a reproducer project ? I don't have those deprecations

OK, the bold part in the deprecation message is the service id for which the deprecation is triggered. This bundle does not use the class name as service id.
So those deprecations means that you are not using the bundle to manage the listeners but that you manage them in a different way. This means that you are responsible for solving the deprecation (or you should switch back to using the bundle to manage the listeners)


Add a new rule which forbids any Test classes in the unittests folder which don't correspond to an object (orphans)

Will help when there are issues with orphaned classes due to renaming.
Could potentially allow it as an unsafe fix as well.

Should be able to turn this off in a setting.

Would be good to action #62 around the same time.


helmfile list --output json outputs invalid json when hook is present with showlogs

Operating system
fedora 37
Helmfile Version
helmfile version 0.152.0
Helm Version
version.BuildInfo{Version:"v3.8.0", GitCommit:"d14138609b01886f544b2025f5000351c9eb092e", GitTreeState:"clean", GoVersion:"go1.17.5"}
Bug description
helmfile list --output json outputs
When hooks has showLogs

hook[prepare] logs |
<JSON_HERE>

Example helmfile.yaml
- chart: bitnami/keycloak
  name: keycloak
  version: 10.1.5
  wait: true
  hooks:
    - events: [ "prepare" ]
      showlogs: false
      command: "./preview.sh"

preview.sh:
#!/bin/sh

Error message you've seen (if any)
error happens when parsing
Steps to reproduce
explained above
Working Helmfile Version
none
Relevant discussion
No response

@yelhouti PR is welcome.


App chat breaks across regions

It seems to me that the app is using the same chat ID across multiple regions. This would break. A chat ID must be specific for a region.

Done in https://github.com/digitalfabrik/integreat-app/pull/2957.


Custom .eslintrc not respected

We have two different eslint configuration files. One is intended for production and final builds and the other one is for development purposes and thus less strict (allows console.log for example). The configFile option doesn't seem to work for me.
folder structure:
/
  .dev.eslintrc
  webpack.config.js

My webpack config
...
module: {
  preLoaders: [
    {test: /\.js$/, loader: 'eslint-loader', exclued: /node_modules/}
  ],
  loaders: [
    {test: /\.js$/, loader: 'babel-loader', exclude: /node_modules/}
  ],
  eslint: {
    configFile: path.join(__dirname, '.dev.eslintrc')
  }
}

The eslint section should not be in module section.

Awesome thanks!


Mac Excel error - "Dictionary.cls is not supposed in VBE. The file can't be loaded."

Hi, I'm new to VBA and I'm trying to load a macro on my Mac Excel that uses Scripting.Dictionary, and I'm trying to use VBA-Dictionary as a replacement for it, but I'm running into some errors.
Importing the Dictionary.cls file throws an error saying that it's not supported in VBE and can't be loaded:

And I was trying to put it into a module and run it, but then that throws a compile error:

Any idea how I can load VBA-Dictionary? I'm on Excel for Mac 2011 (v14.5.1), would love any help.

Hi @sayem I have seen some line-ending encoding issues with downloading from Github, see this comment for resolution details: https://github.com/VBA-tools/VBA-Dictionary/issues/5#issuecomment-77081615
Let me know if that doesn't work for you.

Yup, simply downloading the entire repo and then importing did the trick. Thanks!


Flatten Saga nested transactions

Ⅰ. Describe what this PR did
Saga nested transaction(SubState Machine)will create a new Global transaction, it is not necessary, We need make it Flatten.
Ⅱ. Does this pull request fix one issue?
#1974
Ⅳ. Describe how to verify it
run unit test at seata/test/src/test/java/io/seata/saga

Codecov Report

Merging #1975 into develop will increase coverage by 0.01%.
The diff coverage is 0%.

@@              Coverage Diff              @@
##             develop    #1975      +/-   ##
=============================================
+ Coverage      55.25%   55.26%   +0.01%
  Complexity      2431     2431
=============================================
  Files            431      431
  Lines          14442    14443       +1
  Branches        1708     1709       +1
=============================================
+ Hits            7980     7982       +2
  Misses          5735     5735
+ Partials         727      726       -1

Impacted Files
Coverage Δ
Complexity Δ

...o/seata/saga/statelang/domain/DomainConstants.java
0% <ø> (ø)
0 <0> (ø)
:arrow_down:

.../statelang/parser/impl/StateMachineParserImpl.java
70.73% <0%> (-1.77%)
8 <0> (ø)

...very/registry/zk/ZookeeperRegisterServiceImpl.java
63.77% <0%> (-0.79%)
25% <0%> (ø)

...server/store/file/FileTransactionStoreManager.java
57.46% <0%> (+0.95%)
29% <0%> (ø)
:arrow_down:


JQuery Bugs fixed in popup.html & popup.js

Any suggestions?

build/jquery.datetimepicker.min.js, build/jquery.datetimepicker.full.min.js
What are these files ?

These files are needed to use JQuery DateTimePicker.

Okay
Have you checked the extension locally ?

@ritz301 Merging this.
Thanks

I remember my first PR. The weight of this one is way too high than this one. Great job @ritz301 !

And it would not have been possible without you friends. Thanks!

@kshitij10496 Yes I have checked it locally. Do you encounter any problem in that?

Nope.
Its fine