Waveshare PN532 NFC hat using SPI

Bug
What I did
Trying to use RPi jukebox with a Waveshare PN532 NFC hat, SPI configuration. I followed the one-script install guide, and used Reader.py.experimental. RegisterDevice.py shows MFRC522 and RDM6300.
What happened
When I select MFRC522 I can run the python sample code from Waveshare, and it detects my RFID card.
https://www.waveshare.com/wiki/PN532_NFC_HAT
However, in the web-interface the RFid card does not show up under the Card ID tab. I am guessing that I have to change some settings in Reader.py?
I expected this to happen
Detecting the RFid cards in the web interface.
Further information that might help
tail -n 500 /var/log/syslog
May  3 16:06:13 raspberrypi avahi-daemon[390]: Withdrawing address record for fe80::ba27:ebff:fe5f:8103 on wlan0.
May  3 16:06:13 raspberrypi avahi-daemon[390]: Leaving mDNS multicast group on interface wlan0.IPv6 with address fe80::ba27:ebff:fe5f:8103.
May  3 16:06:13 raspberrypi avahi-daemon[390]: Interface wlan0.IPv6 no longer relevant for mDNS.
May  3 16:06:13 raspberrypi lightdm[479]: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Accounts was not provided by any .service files
May  3 16:06:13 raspberrypi polkitd[450]: started daemon version 0.105 using authority implementation `local' version `0.105'
May  3 16:06:13 raspberrypi dbus-daemon[362]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
May  3 16:06:13 raspberrypi systemd[1]: Started Authorization Manager.
May  3 16:06:13 raspberrypi systemd[1]: Received SIGRTMIN+21 from PID 174 (plymouthd).
May  3 16:06:13 raspberrypi systemd[1]: Received SIGRTMIN+21 from PID 174 (plymouthd).
May  3 16:06:13 raspberrypi systemd[1]: plymouth-quit-wait.service: Succeeded.
May  3 16:06:13 raspberrypi systemd[1]: Started Hold until boot process finishes up.
May  3 16:06:13 raspberrypi systemd[1]: Started Light Display Manager.
May  3 16:06:13 raspberrypi systemd[1]: plymouth-start.service: Succeeded.
May  3 16:06:13 raspberrypi systemd[1]: Started Getty on tty1.
May  3 16:06:13 raspberrypi systemd[1]: Reached target Login Prompts.
May  3 16:06:14 raspberrypi systemd[1]: Started The PHP 7.3 FastCGI Process Manager.
May  3 16:06:14 raspberrypi raspi-config[398]: Checking if shift key is held down: No. Switching to ondemand scaling governor.
May  3 16:06:14 raspberrypi systemd[1]: Started LSB: Switch to ondemand cpu governor (unless shift key is pressed).
May  3 16:06:14 raspberrypi systemd[1]: Started Disk Manager.
May  3 16:06:14 raspberrypi udisksd[350]: Acquired the name org.freedesktop.UDisks2 on the system message bus
May  3 16:06:14 raspberrypi systemd[1]: Started Lighttpd Daemon.
May  3 16:06:15 raspberrypi daemon_rfid_reader.py[456]: Please run RegisterDevice.py first
May  3 16:06:15 raspberrypi systemd[1]: systemd-rfkill.service: Succeeded.
May  3 16:06:15 raspberrypi systemd[1]: phoniebox-rfid-reader.service: Main process exited, code=exited, status=1/FAILURE
May  3 16:06:15 raspberrypi systemd[1]: phoniebox-rfid-reader.service: Failed with result 'exit-code'.
May  3 16:06:15 raspberrypi exim4[454]: Starting MTA: exim4.
May  3 16:06:15 raspberrypi systemd[1]: Started LSB: exim Mail Transport Agent.
May  3 16:06:15 raspberrypi systemd[1]: phoniebox-rfid-reader.service: Service RestartSec=100ms expired, scheduling restart.
May  3 16:06:15 raspberrypi systemd[1]: phoniebox-rfid-reader.service: Scheduled restart job, restart counter is at 1.
May  3 16:06:15 raspberrypi systemd[1]: Stopped Phoniebox RFID-Reader Service.
May  3 16:06:15 raspberrypi systemd[1]: Started Phoniebox RFID-Reader Service.
May  3 16:06:15 raspberrypi daemon_rfid_reader.py[830]: Please run RegisterDevice.py first
May  3 16:06:15 raspberrypi systemd[1]: phoniebox-rfid-reader.service: Main process exited, code=exited, status=1/FAILURE
May  3 16:06:15 raspberrypi systemd[1]: phoniebox-rfid-reader.service: Failed with result 'exit-code'.
May  3 16:06:16 raspberrypi systemd[1]: phoniebox-rfid-reader.service: Service RestartSec=100ms expired, scheduling restart.
May  3 16:06:16 raspberrypi systemd[1]: phoniebox-rfid-reader.service: Scheduled restart job, restart counter is at 2.
May  3 16:06:16 raspberrypi systemd[1]: Stopped Phoniebox RFID-Reader Service.
May  3 16:06:16 raspberrypi systemd[1]: Started Phoniebox RFID-Reader Service.
May  3 16:06:16 raspberrypi daemon_rfid_reader.py[835]: Please run RegisterDevice.py first
May  3 16:06:16 raspberrypi systemd[1]: phoniebox-rfid-reader.service: Main process exited, code=exited, status=1/FAILURE
May  3 16:06:16 raspberrypi systemd[1]: phoniebox-rfid-reader.service: Failed with result 'exit-code'.
May  3 16:06:16 raspberrypi systemd[1]: phoniebox-rfid-reader.service: Service RestartSec=100ms expired, scheduling restart.
May  3 16:06:16 raspberrypi systemd[1]: phoniebox-rfid-reader.service: Scheduled restart job, restart counter is at 3.
May  3 16:06:16 raspberrypi systemd[1]: Stopped Phoniebox RFID-Reader Service.
May  3 16:06:16 raspberrypi systemd[1]: Started Phoniebox RFID-Reader Service.
May  3 16:06:17 raspberrypi lightdm[853]: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Accounts was not provided by any .service files
May  3 16:06:17 raspberrypi systemd[1]: Created slice User Slice of UID 1000.
May  3 16:06:17 raspberrypi systemd[1]: Starting User Runtime Directory /run/user/1000...
May  3 16:06:17 raspberrypi systemd[1]: Started User Runtime Directory /run/user/1000.
May  3 16:06:17 raspberrypi systemd[1]: Starting User Manager for UID 1000...
May  3 16:06:17 raspberrypi daemon_rfid_reader.py[847]: Please run RegisterDevice.py first
May  3 16:06:17 raspberrypi systemd[1]: phoniebox-rfid-reader.service: Main process exited, code=exited, status=1/FAILURE
May  3 16:06:17 raspberrypi systemd[1]: phoniebox-rfid-reader.service: Failed with result 'exit-code'.
May  3 16:06:17 raspberrypi systemd[861]: Starting D-Bus User Message Bus Socket.
May  3 16:06:17 raspberrypi systemd[861]: Reached target Paths.
May  3 16:06:17 raspberrypi systemd[861]: Reached target Timers.
May  3 16:06:17 raspberrypi systemd[861]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
May  3 16:06:17 raspberrypi systemd[861]: Listening on GnuPG cryptographic agent and passphrase cache.
May  3 16:06:17 raspberrypi systemd[861]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
May  3 16:06:17 raspberrypi systemd[861]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
May  3 16:06:17 raspberrypi systemd[861]: Listening on GnuPG network certificate management daemon.
May  3 16:06:17 raspberrypi systemd[1]: phoniebox-rfid-reader.service: Service RestartSec=100ms expired, scheduling restart.
May  3 16:06:17 raspberrypi systemd[1]: phoniebox-rfid-reader.service: Scheduled restart job, restart counter is at 4.
May  3 16:06:17 raspberrypi systemd[1]: Stopped Phoniebox RFID-Reader Service.
May  3 16:06:17 raspberrypi systemd[1]: Started Phoniebox RFID-Reader Service.
May  3 16:06:17 raspberrypi systemd[861]: Listening on D-Bus User Message Bus Socket.
May  3 16:06:17 raspberrypi systemd[861]: Reached target Sockets.
May  3 16:06:17 raspberrypi systemd[861]: Reached target Basic System.
May  3 16:06:17 raspberrypi systemd[1]: Started User Manager for UID 1000.
May  3 16:06:17 raspberrypi systemd[861]: Starting Music Player Daemon...
May  3 16:06:17 raspberrypi systemd[1]: Started Session c1 of user pi.
May  3 16:06:17 raspberrypi lightdm[479]: Error opening audit socket: Protocol not supported
May  3 16:06:17 raspberrypi systemd[861]: Started D-Bus User Message Bus.
May  3 16:06:18 raspberrypi daemon_rfid_reader.py[875]: Please run RegisterDevice.py first
May  3 16:06:18 raspberrypi systemd[1]: phoniebox-rfid-reader.service: Main process exited, code=exited, status=1/FAILURE
May  3 16:06:18 raspberrypi systemd[1]: phoniebox-rfid-reader.service: Failed with result 'exit-code'.
May  3 16:06:18 raspberrypi dhcpcd[431]: wlan0: carrier acquired
May  3 16:06:18 raspberrypi dhcpcd[431]: wlan0: connected to Access Point `kucknet2'
May  3 16:06:18 raspberrypi dhcpcd[431]: unknown option: SSID
May  3 16:06:18 raspberrypi dhcpcd[431]: unknown option: SSID
May  3 16:06:18 raspberrypi kernel: [   14.281176] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
May  3 16:06:18 raspberrypi dhcpcd[431]: wlan0: IAID eb:5f:81:03
May  3 16:06:18 raspberrypi dhcpcd[431]: wlan0: adding address fe80::ba27:ebff:fe5f:8103
May  3 16:06:18 raspberrypi avahi-daemon[390]: Joining mDNS multicast group on interface wlan0.IPv6 with address fe80::ba27:ebff:fe5f:8103.
May  3 16:06:18 raspberrypi avahi-daemon[390]: New relevant interface wlan0.IPv6 for mDNS.
May  3 16:06:18 raspberrypi avahi-daemon[390]: Registering new address record for fe80::ba27:ebff:fe5f:8103 on wlan0.*.
May  3 16:06:18 raspberrypi dhcpcd[431]: wlan0: rebinding lease of <IP_ADDRESS>
May  3 16:06:18 raspberrypi kernel: [   14.500302] Bluetooth: Core ver 2.22
May  3 16:06:18 raspberrypi kernel: [   14.500366] NET: Registered protocol family 31
May  3 16:06:18 raspberrypi kernel: [   14.500369] Bluetooth: HCI device and connection manager initialized
May  3 16:06:18 raspberrypi kernel: [   14.500384] Bluetooth: HCI socket layer initialized
May  3 16:06:18 raspberrypi kernel: [   14.500392] Bluetooth: L2CAP socket layer initialized
May  3 16:06:18 raspberrypi kernel: [   14.500417] Bluetooth: SCO socket layer initialized
May  3 16:06:18 raspberrypi dhcpcd[431]: wlan0: probing address <IP_ADDRESS>/24
May  3 16:06:18 raspberrypi kernel: [   14.541892] Bluetooth: HCI UART driver ver 2.3
May  3 16:06:18 raspberrypi kernel: [   14.541904] Bluetooth: HCI UART protocol H4 registered
May  3 16:06:18 raspberrypi kernel: [   14.541979] Bluetooth: HCI UART protocol Three-wire (H5) registered
May  3 16:06:18 raspberrypi kernel: [   14.542116] Bluetooth: HCI UART protocol Broadcom registered
May  3 16:06:18 raspberrypi btuart[360]: bcm43xx_init
May  3 16:06:18 raspberrypi btuart[360]: Flash firmware /lib/firmware/brcm/BCM4345C0.hcd
May  3 16:06:18 raspberrypi btuart[360]: Set BDADDR UART: b8:27:eb:a0:7e:fc
May  3 16:06:18 raspberrypi btuart[360]: Set Controller UART speed to 3000000 bit/s
May  3 16:06:18 raspberrypi btuart[360]: Device setup complete
May  3 16:06:18 raspberrypi systemd[1]: phoniebox-rfid-reader.service: Service RestartSec=100ms expired, scheduling restart.
May  3 16:06:18 raspberrypi systemd[1]: phoniebox-rfid-reader.service: Scheduled restart job, restart counter is at 5.
May  3 16:06:18 raspberrypi systemd[1]: Started Configure Bluetooth Modems connected by UART.
May  3 16:06:18 raspberrypi systemd[1]: Stopped Phoniebox RFID-Reader Service.
May  3 16:06:18 raspberrypi systemd[1]: phoniebox-rfid-reader.service: Start request repeated too quickly.
May  3 16:06:18 raspberrypi systemd[1]: phoniebox-rfid-reader.service: Failed with result 'exit-code'.
May  3 16:06:18 raspberrypi systemd[1]: Failed to start Phoniebox RFID-Reader Service.
May  3 16:06:18 raspberrypi systemd[1]: Starting Load/Save RF Kill Switch Status...
May  3 16:06:18 raspberrypi systemd[1]: Started Load/Save RF Kill Switch Status.
May  3 16:06:18 raspberrypi systemd[1]: Created slice system-bthelper.slice.
May  3 16:06:18 raspberrypi systemd[1]: Starting Bluetooth service...
May  3 16:06:18 raspberrypi dhcpcd[431]: wlan0: soliciting an IPv6 router
May  3 16:06:18 raspberrypi bluetoothd[901]: Bluetooth daemon 5.50
May  3 16:06:18 raspberrypi systemd[1]: Started Bluetooth service.
May  3 16:06:18 raspberrypi systemd[1]: Started BluezALSA proxy.
May  3 16:06:18 raspberrypi systemd[1]: Started Raspberry Pi bluetooth helper.
May  3 16:06:18 raspberrypi systemd[1]: Reached target Bluetooth.
May  3 16:06:18 raspberrypi bluetoothd[901]: Starting SDP server
May  3 16:06:18 raspberrypi kernel: [   15.034643] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
May  3 16:06:18 raspberrypi kernel: [   15.034655] Bluetooth: BNEP filters: protocol multicast
May  3 16:06:18 raspberrypi kernel: [   15.034674] Bluetooth: BNEP socket layer initialized
May  3 16:06:18 raspberrypi systemd[1]<EMAIL_ADDRESS>Succeeded.
May  3 16:06:18 raspberrypi dbus-daemon[362]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.13' (uid=0 pid=901 comm="/usr/lib/bluetooth/bluetoothd ")
May  3 16:06:18 raspberrypi bluetoothd[901]: Bluetooth management interface 1.14 initialized
May  3 16:06:18 raspberrypi systemd[1]: Starting Hostname Service...
May  3 16:06:18 raspberrypi bluetoothd[901]: Sap driver initialization failed.
May  3 16:06:18 raspberrypi bluetoothd[901]: sap-server: Operation not permitted (1)
May  3 16:06:18 raspberrypi bluetoothd[901]: Endpoint registered: sender=:1.14 path=/org/bluez/hci0/A2DP/SBC/Source/1
May  3 16:06:18 raspberrypi bluetoothd[901]: Endpoint registered: sender=:1.14 path=/org/bluez/hci0/A2DP/SBC/Source/2
May  3 16:06:19 raspberrypi kernel: [   15.153844] Bluetooth: RFCOMM TTY layer initialized
May  3 16:06:19 raspberrypi kernel: [   15.153871] Bluetooth: RFCOMM socket layer initialized
May  3 16:06:19 raspberrypi kernel: [   15.153893] Bluetooth: RFCOMM ver 1.11
May  3 16:06:19 raspberrypi bluetoothd[901]: Failed to set privacy: Rejected (0x0b)
May  3 16:06:19 raspberrypi mopidy[472]: /usr/lib/python2.7/dist-packages/mopidy/ext.py:202: PkgResourcesDeprecationWarning: Parameters to load are deprecated.  Call .resolve and .require separately.
May  3 16:06:19 raspberrypi mopidy[472]:   extension_class = entry_point.load(require=False)
May  3 16:06:19 raspberrypi systemd[1]: Started Session c2 of user pi.
May  3 16:06:19 raspberrypi dbus-daemon[362]: [system] Successfully activated service 'org.freedesktop.hostname1'
May  3 16:06:19 raspberrypi systemd[1]: Started Hostname Service.
May  3 16:06:19 raspberrypi dbus-daemon[887]: [session uid=1000 pid=887] Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' requested by ':1.3' (uid=1000 pid=878 comm="/usr/bin/lxsession -s LXDE-pi -e LXDE ")
May  3 16:06:19 raspberrypi systemd[861]: Starting Virtual filesystem service...
May  3 16:06:19 raspberrypi dbus-daemon[887]: [session uid=1000 pid=887] Successfully activated service 'org.gtk.vfs.Daemon'
May  3 16:06:19 raspberrypi systemd[861]: Started Virtual filesystem service.
May  3 16:06:20 raspberrypi kernel: [   16.160840] fuse init (API version 7.27)
May  3 16:06:20 raspberrypi systemd[1]: Condition check resulted in FUSE Control File System being skipped.
May  3 16:06:20 raspberrypi dhcpcd[431]: wlan0: Router Advertisement from fe80::1e24:cdff:fe46:b1e0
May  3 16:06:20 raspberrypi dhcpcd[431]: wlan0: adding address 2a02:120b:7ff:54c0:ba27:ebff:fe5f:8103/64
May  3 16:06:20 raspberrypi avahi-daemon[390]: Leaving mDNS multicast group on interface wlan0.IPv6 with address fe80::ba27:ebff:fe5f:8103.
May  3 16:06:20 raspberrypi avahi-daemon[390]: Joining mDNS multicast group on interface wlan0.IPv6 with address 2a02:120b:7ff:54c0:ba27:ebff:fe5f:8103.
May  3 16:06:20 raspberrypi dhcpcd[431]: wlan0: adding route to 2a02:120b:7ff:54c0::/64
May  3 16:06:20 raspberrypi avahi-daemon[390]: Registering new address record for 2a02:120b:7ff:54c0:ba27:ebff:fe5f:8103 on wlan0.*.
May  3 16:06:20 raspberrypi avahi-daemon[390]: Withdrawing address record for fe80::ba27:ebff:fe5f:8103 on wlan0.
May  3 16:06:20 raspberrypi dhcpcd[431]: wlan0: requesting DHCPv6 information
May  3 16:06:20 raspberrypi dhcpcd[431]: wlan0: fe80::1e24:cdff:fe46:b1e0 is reachable again
May  3 16:06:20 raspberrypi dhcpcd[431]: wlan0: adding default route via fe80::1e24:cdff:fe46:b1e0
May  3 16:06:20 raspberrypi kernel: [   16.809168] ICMPv6: process `dhcpcd' is using deprecated sysctl (syscall) net.ipv6.neigh.wlan0.retrans_time - use net.ipv6.neigh.wlan0.retrans_time_ms instead
May  3 16:06:21 raspberrypi dbus-daemon[887]: [session uid=1000 pid=887] Activating via systemd: service name='org.gtk.vfs.UDisks2VolumeMonitor' unit='gvfs-udisks2-volume-monitor.service' requested by ':1.7' (uid=1000 pid=984 comm="pcmanfm --desktop --profile LXDE-pi ")
May  3 16:06:21 raspberrypi systemd[861]: Starting Virtual filesystem service - disk device monitor...
May  3 16:06:21 raspberrypi dbus-daemon[887]: [session uid=1000 pid=887] Successfully activated service 'org.gtk.vfs.UDisks2VolumeMonitor'
May  3 16:06:21 raspberrypi systemd[861]: Started Virtual filesystem service - disk device monitor.
May  3 16:06:21 raspberrypi dbus-daemon[887]: [session uid=1000 pid=887] Activating via systemd: service name='org.gtk.vfs.MTPVolumeMonitor' unit='gvfs-mtp-volume-monitor.service' requested by ':1.7' (uid=1000 pid=984 comm="pcmanfm --desktop --profile LXDE-pi ")
May  3 16:06:21 raspberrypi systemd[861]: Starting Virtual filesystem service - Media Transfer Protocol monitor...
May  3 16:06:21 raspberrypi dbus-daemon[887]: [session uid=1000 pid=887] Successfully activated service 'org.gtk.vfs.MTPVolumeMonitor'
May  3 16:06:21 raspberrypi systemd[861]: Started Virtual filesystem service - Media Transfer Protocol monitor.
May  3 16:06:21 raspberrypi dbus-daemon[887]: [session uid=1000 pid=887] Activating via systemd: service name='org.gtk.vfs.AfcVolumeMonitor' unit='gvfs-afc-volume-monitor.service' requested by ':1.7' (uid=1000 pid=984 comm="pcmanfm --desktop --profile LXDE-pi ")
May  3 16:06:21 raspberrypi systemd[861]: Starting Virtual filesystem service - Apple File Conduit monitor...
May  3 16:06:21 raspberrypi mpd[876]: exception: failed to open log file "/var/log/mpd/mpd.log" (config line 40): Permission denied
May  3 16:06:21 raspberrypi gvfs-afc-volume-monitor[1035]: Volume monitor alive
May  3 16:06:21 raspberrypi dbus-daemon[887]: [session uid=1000 pid=887] Successfully activated service 'org.gtk.vfs.AfcVolumeMonitor'
May  3 16:06:21 raspberrypi systemd[861]: Started Virtual filesystem service - Apple File Conduit monitor.
May  3 16:06:21 raspberrypi dbus-daemon[887]: [session uid=1000 pid=887] Activating via systemd: service name='org.gtk.vfs.GoaVolumeMonitor' unit='gvfs-goa-volume-monitor.service' requested by ':1.7' (uid=1000 pid=984 comm="pcmanfm --desktop --profile LXDE-pi ")
May  3 16:06:21 raspberrypi systemd[861]: Starting Virtual filesystem service - GNOME Online Accounts monitor...
May  3 16:06:21 raspberrypi systemd[861]: mpd.service: Main process exited, code=exited, status=1/FAILURE
May  3 16:06:21 raspberrypi systemd[861]: mpd.service: Failed with result 'exit-code'.
May  3 16:06:21 raspberrypi systemd[861]: Failed to start Music Player Daemon.
May  3 16:06:21 raspberrypi systemd[861]: Reached target Default.
May  3 16:06:21 raspberrypi dbus-daemon[887]: [session uid=1000 pid=887] Successfully activated service 'org.gtk.vfs.GoaVolumeMonitor'
May  3 16:06:21 raspberrypi systemd[861]: Started Virtual filesystem service - GNOME Online Accounts monitor.
May  3 16:06:21 raspberrypi systemd[861]: Startup finished in 4.433s.
May  3 16:06:21 raspberrypi dbus-daemon[887]: [session uid=1000 pid=887] Activating via systemd: service name='org.gtk.vfs.GPhoto2VolumeMonitor' unit='gvfs-gphoto2-volume-monitor.service' requested by ':1.7' (uid=1000 pid=984 comm="pcmanfm --desktop --profile LXDE-pi ")
May  3 16:06:21 raspberrypi systemd[861]: Starting Virtual filesystem service - digital camera monitor...
May  3 16:06:21 raspberrypi dbus-daemon[887]: [session uid=1000 pid=887] Successfully activated service 'org.gtk.vfs.GPhoto2VolumeMonitor'
May  3 16:06:21 raspberrypi systemd[861]: Started Virtual filesystem service - digital camera monitor.
May  3 16:06:21 raspberrypi mopidy[472]: INFO     Starting Mopidy 2.2.2
May  3 16:06:21 raspberrypi mopidy[472]: INFO     Loading config from builtin defaults
May  3 16:06:21 raspberrypi mopidy[472]: INFO     Loading config from /etc/mopidy/mopidy.conf
May  3 16:06:21 raspberrypi mopidy[472]: INFO     Loading config from command line options
May  3 16:06:22 raspberrypi mopidy[472]: INFO     Enabled extensions: iris, mpd, http, stream, m3u, softwaremixer, file, local-images, local
May  3 16:06:22 raspberrypi mopidy[472]: INFO     Disabled extensions: none
May  3 16:06:22 raspberrypi mopidy[472]: INFO     Starting Mopidy mixer: SoftwareMixer
May  3 16:06:22 raspberrypi mopidy[472]: INFO     Mixer volume set to 30
May  3 16:06:22 raspberrypi mopidy[472]: INFO     Starting Mopidy audio
May  3 16:06:22 raspberrypi mopidy[472]: INFO     Starting Mopidy backends: StreamBackend, M3UBackend, FileBackend, LocalBackend
May  3 16:06:22 raspberrypi mopidy[472]: INFO     No local library metadata cache found at /var/lib/mopidy/local/library.json.gz. Please run `mopidy local scan` to index your local music library. If you do not have a local music collection, you can disable the local backend to hide this message.
May  3 16:06:22 raspberrypi mopidy[472]: INFO     Loaded 0 local tracks using json
May  3 16:06:22 raspberrypi mopidy[472]: INFO     Starting Mopidy core
May  3 16:06:22 raspberrypi mopidy[472]: INFO     Audio output set to "alsasink"
May  3 16:06:22 raspberrypi mopidy[472]: INFO     Starting Mopidy frontends: IrisFrontend, MpdFrontend, HttpFrontend
May  3 16:06:22 raspberrypi mopidy[472]: INFO     Starting Iris 3.43.0
May  3 16:06:22 raspberrypi mopidy[472]: INFO     MPD server running at [::ffff:<IP_ADDRESS>]:6600
May  3 16:06:22 raspberrypi mopidy[472]: INFO     HTTP server running at [::ffff:<IP_ADDRESS>]:6680
May  3 16:06:22 raspberrypi mopidy[472]: INFO     Starting GLib mainloop
May  3 16:06:22 raspberrypi dhcpcd[431]: wlan0: leased <IP_ADDRESS> for 86400 seconds
May  3 16:06:22 raspberrypi avahi-daemon[390]: Joining mDNS multicast group on interface wlan0.IPv4 with address <IP_ADDRESS>.
May  3 16:06:22 raspberrypi avahi-daemon[390]: New relevant interface wlan0.IPv4 for mDNS.
May  3 16:06:22 raspberrypi avahi-daemon[390]: Registering new address record for <IP_ADDRESS> on wlan0.IPv4.
May  3 16:06:22 raspberrypi dhcpcd[431]: wlan0: adding route to <IP_ADDRESS>/24
May  3 16:06:22 raspberrypi dhcpcd[431]: wlan0: adding default route via <IP_ADDRESS>
May  3 16:06:23 raspberrypi systemd[1]: systemd-rfkill.service: Succeeded.
May  3 16:06:24 raspberrypi systemd[1]: Started Samba NMB Daemon.
May  3 16:06:24 raspberrypi systemd[1]: Starting Samba SMB Daemon...
May  3 16:06:25 raspberrypi systemd[1]: Started Samba SMB Daemon.
May  3 16:06:25 raspberrypi systemd[1]: Reached target Multi-User System.
May  3 16:06:25 raspberrypi systemd[1]: Reached target Graphical Interface.
May  3 16:06:25 raspberrypi systemd[1]: Starting Update UTMP about System Runlevel Changes...
May  3 16:06:25 raspberrypi systemd[1]: systemd-update-utmp-runlevel.service: Succeeded.
May  3 16:06:25 raspberrypi systemd[1]: Started Update UTMP about System Runlevel Changes.
May  3 16:06:25 raspberrypi systemd[1]: Startup finished in 1.634s (kernel) + 19.939s (userspace) = 21.573s.
May  3 16:06:31 raspberrypi dhcpcd[431]: wlan0: fe80::1e24:cdff:fe46:b1e0 is reachable again
May  3 16:06:31 raspberrypi dhcpcd[431]: wlan0: fe80::1e24:cdff:fe46:b1e0 is reachable again
May  3 16:06:39 raspberrypi systemd[1]: systemd-fsckd.service: Succeeded.
May  3 16:06:50 raspberrypi systemd-timesyncd[309]: Synchronized to time server for the first time [2a02:1205:34d5:5070:b26e:bfff:fe1d:e19b]:123 (2.debian.pool.ntp.org).
May  3 16:06:58 raspberrypi systemd[1]: systemd-hostnamed.service: Succeeded.
May  3 16:07:22 raspberrypi systemd[1]: phoniebox-idle-watchdog.service: Succeeded.
May  3 16:09:01 raspberrypi CRON[1667]: (root) CMD (  [ -x /usr/lib/php/sessionclean ] && if [ ! -d /run/systemd/system ]; then /usr/lib/php/sessionclean; fi)
May  3 16:09:03 raspberrypi systemd[1]: Starting Clean php session files...
May  3 16:09:03 raspberrypi systemd[1]: phpsessionclean.service: Succeeded.
May  3 16:09:03 raspberrypi systemd[1]: Started Clean php session files.
May  3 16:16:40 raspberrypi systemd[1]: Reloading.
May  3 16:16:40 raspberrypi systemd[1]: /lib/systemd/system/smbd.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/samba/smbd.pid → /run/samba/smbd.pid; please update the unit file accordingly.
May  3 16:16:40 raspberrypi systemd[1]: /lib/systemd/system/nmbd.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/samba/nmbd.pid → /run/samba/nmbd.pid; please update the unit file accordingly.
May  3 16:16:40 raspberrypi systemd[1]: /lib/systemd/system/lighttpd.service:6: PIDFile= references path below legacy directory /var/run/, updating /var/run/lighttpd.pid → /run/lighttpd.pid; please update the unit file accordingly.
May  3 16:16:54 raspberrypi systemd[1]: Reloading.
May  3 16:16:55 raspberrypi systemd[1]: /lib/systemd/system/smbd.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/samba/smbd.pid → /run/samba/smbd.pid; please update the unit file accordingly.
May  3 16:16:55 raspberrypi systemd[1]: /lib/systemd/system/nmbd.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/samba/nmbd.pid → /run/samba/nmbd.pid; please update the unit file accordingly.
May  3 16:16:55 raspberrypi systemd[1]: /lib/systemd/system/lighttpd.service:6: PIDFile= references path below legacy directory /var/run/, updating /var/run/lighttpd.pid → /run/lighttpd.pid; please update the unit file accordingly.
May  3 16:16:55 raspberrypi systemd[1]: Reloading.
May  3 16:16:55 raspberrypi systemd[1]: /lib/systemd/system/smbd.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/samba/smbd.pid → /run/samba/smbd.pid; please update the unit file accordingly.
May  3 16:16:55 raspberrypi systemd[1]: /lib/systemd/system/nmbd.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/samba/nmbd.pid → /run/samba/nmbd.pid; please update the unit file accordingly.
May  3 16:16:55 raspberrypi systemd[1]: /lib/systemd/system/lighttpd.service:6: PIDFile= references path below legacy directory /var/run/, updating /var/run/lighttpd.pid → /run/lighttpd.pid; please update the unit file accordingly.
May  3 16:16:56 raspberrypi systemd[1]: Reloading.
May  3 16:16:56 raspberrypi systemd[1]: /lib/systemd/system/smbd.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/samba/smbd.pid → /run/samba/smbd.pid; please update the unit file accordingly.
May  3 16:16:56 raspberrypi systemd[1]: /lib/systemd/system/nmbd.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/samba/nmbd.pid → /run/samba/nmbd.pid; please update the unit file accordingly.
May  3 16:16:56 raspberrypi systemd[1]: /lib/systemd/system/lighttpd.service:6: PIDFile= references path below legacy directory /var/run/, updating /var/run/lighttpd.pid → /run/lighttpd.pid; please update the unit file accordingly.
May  3 16:16:58 raspberrypi systemd[1]: Reloading.
May  3 16:16:59 raspberrypi systemd[1]: /lib/systemd/system/smbd.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/samba/smbd.pid → /run/samba/smbd.pid; please update the unit file accordingly.
May  3 16:16:59 raspberrypi systemd[1]: /lib/systemd/system/nmbd.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/samba/nmbd.pid → /run/samba/nmbd.pid; please update the unit file accordingly.
May  3 16:16:59 raspberrypi systemd[1]: /lib/systemd/system/lighttpd.service:6: PIDFile= references path below legacy directory /var/run/, updating /var/run/lighttpd.pid → /run/lighttpd.pid; please update the unit file accordingly.
May  3 16:17:01 raspberrypi CRON[2102]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
May  3 16:17:11 raspberrypi systemd[1]: Started Phoniebox Idle Watchdog Service.
May  3 16:17:12 raspberrypi systemd[1]: Started Phoniebox RFID-Reader Service.
May  3 16:17:12 raspberrypi systemd[1]: Starting Phoniebox Startup Sound...
May  3 16:17:12 raspberrypi mpg123[2154]: High Performance MPEG 1.0/2.0/2.5 Audio Player for Layers 1, 2 and 3
May  3 16:17:12 raspberrypi mpg123[2154]: #011version 1.25.10; written and copyright by Michael Hipp and others
May  3 16:17:12 raspberrypi mpg123[2154]: #011free software (LGPL) without any warranty but with best wishes
May  3 16:17:12 raspberrypi mpg123[2154]: Directory: /home/pi/RPi-Jukebox-RFID/shared/
May  3 16:17:12 raspberrypi mpg123[2154]: Playing MPEG stream 1 of 1: startupsound.mp3 ...
May  3 16:17:12 raspberrypi mpg123[2154]: MPEG 1.0 L III vbr 44100 j-s
May  3 16:17:14 raspberrypi mpg123[2154]: [0:02] Decoding of startupsound.mp3 finished.
May  3 16:17:14 raspberrypi systemd[1]: Started Phoniebox Startup Sound.
May  3 16:18:12 raspberrypi systemd[1]: phoniebox-idle-watchdog.service: Succeeded.
May  3 16:20:16 raspberrypi lighttpd[685]: chmod: changing permissions of '/home/pi/RPi-Jukebox-RFID/scripts/../settings/edition': Operation not permitted
May  3 16:20:16 raspberrypi lighttpd[685]: rm: cannot remove '/home/pi/RPi-Jukebox-RFID/scripts/../settings/global.conf': No such file or directory
May  3 16:20:16 raspberrypi lighttpd[685]: chmod: changing permissions of '/home/pi/RPi-Jukebox-RFID/settings/global.conf': Operation not permitted
May  3 16:20:17 raspberrypi mopidy[472]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:20:17 raspberrypi mopidy[472]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:20:22 raspberrypi mopidy[472]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:20:49 raspberrypi mopidy[472]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:20:49 raspberrypi mopidy[472]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:20:49 raspberrypi systemd[1]: Stopping Mopidy music server...
May  3 16:20:49 raspberrypi mopidy[472]: INFO     GLib mainloop got SIGTERM. Exiting...
May  3 16:20:49 raspberrypi mopidy[472]: INFO     Stopping Mopidy frontends
May  3 16:20:49 raspberrypi mopidy[472]: INFO     Stopping Iris
May  3 16:20:49 raspberrypi mopidy[472]: INFO     Stopping Mopidy core
May  3 16:20:49 raspberrypi mopidy[472]: INFO     Stopping Mopidy backends
May  3 16:20:49 raspberrypi mopidy[472]: INFO     Stopping Mopidy audio
May  3 16:20:49 raspberrypi mopidy[472]: INFO     Stopping Mopidy mixer
May  3 16:20:49 raspberrypi systemd[1]: mopidy.service: Succeeded.
May  3 16:20:49 raspberrypi systemd[1]: Stopped Mopidy music server.
May  3 16:20:50 raspberrypi systemd[1]: Created slice User Slice of UID 112.
May  3 16:20:50 raspberrypi systemd[1]: Starting User Runtime Directory /run/user/112...
May  3 16:20:50 raspberrypi systemd[1]: Started User Runtime Directory /run/user/112.
May  3 16:20:50 raspberrypi systemd[1]: Starting User Manager for UID 112...
May  3 16:20:50 raspberrypi systemd[2558]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
May  3 16:20:50 raspberrypi systemd[2558]: Starting D-Bus User Message Bus Socket.
May  3 16:20:50 raspberrypi systemd[2558]: Listening on GnuPG network certificate management daemon.
May  3 16:20:50 raspberrypi systemd[2558]: Reached target Paths.
May  3 16:20:50 raspberrypi systemd[2558]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
May  3 16:20:50 raspberrypi systemd[2558]: Reached target Timers.
May  3 16:20:50 raspberrypi systemd[2558]: Listening on GnuPG cryptographic agent and passphrase cache.
May  3 16:20:50 raspberrypi systemd[2558]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
May  3 16:20:50 raspberrypi systemd[2558]: Listening on D-Bus User Message Bus Socket.
May  3 16:20:50 raspberrypi systemd[2558]: Reached target Sockets.
May  3 16:20:50 raspberrypi systemd[2558]: Reached target Basic System.
May  3 16:20:50 raspberrypi systemd[1]: Started User Manager for UID 112.
May  3 16:20:50 raspberrypi systemd[2558]: Starting Music Player Daemon...
May  3 16:20:50 raspberrypi systemd[1]: Started Session c3 of user mopidy.
May  3 16:20:51 raspberrypi mpd[2571]: exception: failed to open log file "/var/log/mpd/mpd.log" (config line 40): Permission denied
May  3 16:20:51 raspberrypi systemd[2558]: mpd.service: Main process exited, code=exited, status=1/FAILURE
May  3 16:20:51 raspberrypi systemd[2558]: mpd.service: Failed with result 'exit-code'.
May  3 16:20:51 raspberrypi systemd[2558]: Failed to start Music Player Daemon.
May  3 16:20:51 raspberrypi systemd[2558]: Reached target Default.
May  3 16:20:51 raspberrypi systemd[2558]: Startup finished in 1.325s.
May  3 16:20:52 raspberrypi systemd[2558]: Started D-Bus User Message Bus.
May  3 16:20:54 raspberrypi lighttpd[685]: echo: write error: Broken pipe
May  3 16:20:55 raspberrypi systemd[1]: session-c3.scope: Succeeded.
May  3 16:20:55 raspberrypi systemd[1]: Starting Mopidy music server...
May  3 16:20:55 raspberrypi systemd[1]: Started Mopidy music server.
May  3 16:20:56 raspberrypi mopidy[2620]: /usr/lib/python2.7/dist-packages/mopidy/ext.py:202: PkgResourcesDeprecationWarning: Parameters to load are deprecated.  Call .resolve and .require separately.
May  3 16:20:56 raspberrypi mopidy[2620]:   extension_class = entry_point.load(require=False)
May  3 16:20:56 raspberrypi lighttpd[685]: mpd error: Connection refused
May  3 16:20:57 raspberrypi mopidy[2620]: INFO     Starting Mopidy 2.2.2
May  3 16:20:57 raspberrypi mopidy[2620]: INFO     Loading config from builtin defaults
May  3 16:20:57 raspberrypi mopidy[2620]: INFO     Loading config from /etc/mopidy/mopidy.conf
May  3 16:20:57 raspberrypi mopidy[2620]: INFO     Loading config from command line options
May  3 16:20:57 raspberrypi mopidy[2620]: INFO     Enabled extensions: iris, mpd, http, stream, m3u, softwaremixer, file, local-images, local
May  3 16:20:57 raspberrypi mopidy[2620]: INFO     Disabled extensions: none
May  3 16:20:57 raspberrypi mopidy[2620]: INFO     Starting Mopidy mixer: SoftwareMixer
May  3 16:20:57 raspberrypi mopidy[2620]: INFO     Mixer volume set to 30
May  3 16:20:57 raspberrypi mopidy[2620]: INFO     Starting Mopidy audio
May  3 16:20:57 raspberrypi mopidy[2620]: INFO     Starting Mopidy backends: StreamBackend, M3UBackend, FileBackend, LocalBackend
May  3 16:20:57 raspberrypi mopidy[2620]: INFO     Audio output set to "alsasink"
May  3 16:20:57 raspberrypi mopidy[2620]: INFO     Loaded 58 local tracks using json
May  3 16:20:57 raspberrypi mopidy[2620]: INFO     Starting Mopidy core
May  3 16:20:57 raspberrypi mopidy[2620]: INFO     Starting Mopidy frontends: IrisFrontend, MpdFrontend, HttpFrontend
May  3 16:20:57 raspberrypi mopidy[2620]: INFO     Starting Iris 3.43.0
May  3 16:20:57 raspberrypi mopidy[2620]: INFO     MPD server running at [::ffff:<IP_ADDRESS>]:6600
May  3 16:20:57 raspberrypi mopidy[2620]: INFO     HTTP server running at [::ffff:<IP_ADDRESS>]:6680
May  3 16:20:57 raspberrypi mopidy[2620]: INFO     Starting GLib mainloop
May  3 16:21:00 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:21:00 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:21:05 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:21:05 raspberrypi systemd[1]: Stopping User Manager for UID 112...
May  3 16:21:05 raspberrypi systemd[2558]: Stopped target Default.
May  3 16:21:05 raspberrypi systemd[2558]: Stopping D-Bus User Message Bus...
May  3 16:21:05 raspberrypi systemd[2558]: dbus.service: Succeeded.
May  3 16:21:05 raspberrypi systemd[2558]: Stopped D-Bus User Message Bus.
May  3 16:21:05 raspberrypi systemd[2558]: Stopped target Basic System.
May  3 16:21:05 raspberrypi systemd[2558]: Stopped target Paths.
May  3 16:21:05 raspberrypi systemd[2558]: Stopped target Sockets.
May  3 16:21:05 raspberrypi systemd[2558]: gpg-agent-extra.socket: Succeeded.
May  3 16:21:05 raspberrypi systemd[2558]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
May  3 16:21:05 raspberrypi systemd[2558]: gpg-agent-ssh.socket: Succeeded.
May  3 16:21:05 raspberrypi systemd[2558]: Closed GnuPG cryptographic agent (ssh-agent emulation).
May  3 16:21:05 raspberrypi systemd[2558]: gpg-agent-browser.socket: Succeeded.
May  3 16:21:05 raspberrypi systemd[2558]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers).
May  3 16:21:05 raspberrypi systemd[2558]: gpg-agent.socket: Succeeded.
May  3 16:21:05 raspberrypi systemd[2558]: Closed GnuPG cryptographic agent and passphrase cache.
May  3 16:21:05 raspberrypi systemd[2558]: dirmngr.socket: Succeeded.
May  3 16:21:05 raspberrypi systemd[2558]: Closed GnuPG network certificate management daemon.
May  3 16:21:05 raspberrypi systemd[2558]: Stopped target Timers.
May  3 16:21:05 raspberrypi systemd[2558]: dbus.socket: Succeeded.
May  3 16:21:05 raspberrypi systemd[2558]: Closed D-Bus User Message Bus Socket.
May  3 16:21:05 raspberrypi systemd[2558]: Reached target Shutdown.
May  3 16:21:05 raspberrypi systemd[2558]: systemd-exit.service: Succeeded.
May  3 16:21:05 raspberrypi systemd[2558]: Started Exit the Session.
May  3 16:21:05 raspberrypi systemd[2558]: Reached target Exit the Session.
May  3 16:21:05 raspberrypi systemd[1]<EMAIL_ADDRESS>Succeeded.
May  3 16:21:05 raspberrypi systemd[1]: Stopped User Manager for UID 112.
May  3 16:21:05 raspberrypi systemd[1]: Stopping User Runtime Directory /run/user/112...
May  3 16:21:05 raspberrypi systemd[861]: run-user-112.mount: Succeeded.
May  3 16:21:05 raspberrypi systemd[1]: run-user-112.mount: Succeeded.
May  3 16:21:05 raspberrypi systemd[1]<EMAIL_ADDRESS>Succeeded.
May  3 16:21:05 raspberrypi systemd[1]: Stopped User Runtime Directory /run/user/112.
May  3 16:21:05 raspberrypi systemd[1]: Removed slice User Slice of UID 112.
May  3 16:21:10 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:21:13 raspberrypi systemd[1]: Starting Cleanup of Temporary Directories...
May  3 16:21:13 raspberrypi systemd[1]: systemd-tmpfiles-clean.service: Succeeded.
May  3 16:21:13 raspberrypi systemd[1]: Started Cleanup of Temporary Directories.
May  3 16:21:15 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:21:21 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:21:27 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:21:34 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:21:39 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:21:46 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:21:52 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:21:58 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:22:04 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:22:10 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:22:15 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:22:22 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:22:27 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:22:34 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:22:40 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:22:45 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:22:51 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:22:57 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:23:04 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:23:09 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:23:15 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:23:21 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:23:28 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:23:33 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:23:39 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:23:45 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:23:51 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:23:53 raspberrypi dhcpcd[431]: wlan0: part of Router Advertisement expired
May  3 16:23:55 raspberrypi avahi-daemon[390]: Registering new address record for fe80::ba27:ebff:fe5f:8103 on wlan0.*.
May  3 16:23:58 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:24:04 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:24:09 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:24:15 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:24:22 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:24:27 raspberrypi avahi-daemon[390]: Withdrawing address record for fe80::ba27:ebff:fe5f:8103 on wlan0.
May  3 16:24:28 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:24:33 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:24:39 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:24:45 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:24:51 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:24:57 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:25:01 raspberrypi dbus-daemon[362]: [system] Activating via systemd: service name='org.freedesktop.PackageKit' unit='packagekit.service' requested by ':1.31' (uid=0 pid=3587 comm="/usr/bin/gdbus call --system --dest org.freedeskto")
May  3 16:25:01 raspberrypi systemd[1]: Starting PackageKit Daemon...
May  3 16:25:01 raspberrypi PackageKit: daemon start
May  3 16:25:01 raspberrypi dbus-daemon[362]: [system] Successfully activated service 'org.freedesktop.PackageKit'
May  3 16:25:01 raspberrypi systemd[1]: Started PackageKit Daemon.
May  3 16:25:03 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:25:08 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:25:14 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:25:20 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:25:26 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:25:32 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:25:38 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:25:45 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:25:51 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:25:56 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:26:05 raspberrypi lighttpd[685]: echo: write error: Broken pipe
May  3 16:26:05 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:26:05 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:26:14 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:26:17 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:26:18 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:26:26 raspberrypi lighttpd[685]: echo: write error: Broken pipe
May  3 16:26:33 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:26:33 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:26:33 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:26:38 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:26:39 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:26:45 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:26:50 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:26:56 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:26:59 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:26:59 raspberrypi gpio-buttons.py[452]: volume: 30%   repeat: off   random: off   single: off   consume: off
May  3 16:27:03 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:27:08 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:27:14 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:27:20 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:27:26 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:27:32 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:27:39 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:27:45 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:27:51 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:27:56 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:28:02 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:28:08 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:28:14 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:28:20 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:28:26 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:28:32 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:28:38 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:28:44 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:28:51 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:28:56 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:29:03 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:29:09 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:29:14 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:29:20 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:29:26 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:29:32 raspberrypi mopidy[2620]: INFO     New MPD connection from [::ffff:<IP_ADDRESS>]:6600
May  3 16:30:07 raspberrypi PackageKit: daemon quit
May  3 16:30:07 raspberrypi systemd[1]: packagekit.service: Main process exited, code=killed, status=15/TERM
May  3 16:30:07 raspberrypi systemd[1]: packagekit.service: Succeeded.

May  3 16:38:01 raspberrypi avahi-daemon[390]: Withdrawing address record for fe80::ba27:ebff:fe5f:8103 on wlan0.
May  3 16:39:01 raspberrypi CRON[4687]: (root) CMD (  [ -x /usr/lib/php/sessionclean ] && if [ ! -d /run/systemd/system ]; then /usr/lib/php/sessionclean; fi)
May  3 16:39:03 raspberrypi systemd[1]: Starting Clean php session files...
May  3 16:39:04 raspberrypi systemd[1]: phpsessionclean.service: Succeeded.
May  3 16:39:04 raspberrypi systemd[1]: Started Clean php session files.
May  3 16:47:54 raspberrypi dhcpcd[431]: wlan0: part of Router Advertisement expired
May  3 16:47:59 raspberrypi avahi-daemon[390]: Registering new address record for fe80::ba27:ebff:fe5f:8103 on wlan0.*.
May  3 16:48:26 raspberrypi avahi-daemon[390]: Withdrawing address record for fe80::ba27:ebff:fe5f:8103 on wlan0.
May  3 16:49:26 raspberrypi dhcpcd[431]: wlan0: part of Router Advertisement expired
May  3 16:49:26 raspberrypi avahi-daemon[390]: Registering new address record for fe80::ba27:ebff:fe5f:8103 on wlan0.*.
May  3 16:49:59 raspberrypi avahi-daemon[390]: Withdrawing address record for fe80::ba27:ebff:fe5f:8103 on wlan0.

journalctl -u mopidy
-- Logs begin at Sun 2020-05-03 16:06:07 BST, end at Sun 2020-05-03 16:49:59 BST
May 03 16:06:12 raspberrypi systemd[1]: Starting Mopidy music server...
May 03 16:06:12 raspberrypi systemd[1]: Started Mopidy music server.
May 03 16:06:19 raspberrypi mopidy[472]: /usr/lib/python2.7/dist-packages/mopidy
May 03 16:06:19 raspberrypi mopidy[472]:   extension_class = entry_point.load(re
May 03 16:06:21 raspberrypi mopidy[472]: INFO     Starting Mopidy 2.2.2
May 03 16:06:21 raspberrypi mopidy[472]: INFO     Loading config from builtin de
May 03 16:06:21 raspberrypi mopidy[472]: INFO     Loading config from /etc/mopid
May 03 16:06:21 raspberrypi mopidy[472]: INFO     Loading config from command li
May 03 16:06:22 raspberrypi mopidy[472]: INFO     Enabled extensions: iris, mpd,
May 03 16:06:22 raspberrypi mopidy[472]: INFO     Disabled extensions: none
May 03 16:06:22 raspberrypi mopidy[472]: INFO     Starting Mopidy mixer: Softwar
May 03 16:06:22 raspberrypi mopidy[472]: INFO     Mixer volume set to 30
May 03 16:06:22 raspberrypi mopidy[472]: INFO     Starting Mopidy audio
May 03 16:06:22 raspberrypi mopidy[472]: INFO     Starting Mopidy backends: Stre
May 03 16:06:22 raspberrypi mopidy[472]: INFO     No local library metadata cach
May 03 16:06:22 raspberrypi mopidy[472]: INFO     Loaded 0 local tracks using js
May 03 16:06:22 raspberrypi mopidy[472]: INFO     Starting Mopidy core
May 03 16:06:22 raspberrypi mopidy[472]: INFO     Audio output set to "alsasink"
May 03 16:06:22 raspberrypi mopidy[472]: INFO     Starting Mopidy frontends: Iri
May 03 16:06:22 raspberrypi mopidy[472]: INFO     Starting Iris 3.43.0
May 03 16:06:22 raspberrypi mopidy[472]: INFO     MPD server running at [::ffff:
May 03 16:06:22 raspberrypi mopidy[472]: INFO     HTTP server running at [::fff

Software
Base image and version
Raspbian GNU/Linux 10
RaspberryPi version
3 B+
RFID Reader
Waveshield PN532 NFC Hat in SPI mode

Thank you for your help!

I've added basic support for PN532 RFID readers via I2C. So you might be able to get your RFID reader to work with that as well. Check out the develop branch and see https://github.com/MiczFlor/RPi-Jukebox-RFID/tree/develop/components/rfid-reader/PN532 for more info.
If you want/need to use SPI you will most likely need to do some hacking yourself.
BTW: I don't consider this to be a bug. This should be a feature-request.

Hi @borsic77
thanks for the input. You write "in the web-interface the RFid card does not show up under the Card ID tab" and I am not sure what you expect in that tab.
In the web UI this tab allows you to connect RFID tags with audio folders or system commands. Swiping the card should display the RFID ID in the form. The card itself is not shown there.

Hey @borsic77, is this still an issue?

I can confirm the Waveshare PN532 hat doesn't work out of the box over I2C.
https://www.waveshare.com/wiki/PN532_NFC_HAT
While running run_register_rfid_reader.py I did see the following error
/bin/sh: 1: ./setup.inc.sh: Permission denied
which may be related.

I can confirm the waveshare hat DOES work out of the box over I2C when configured with the pins and jumpers as shown here:
https://www.waveshare.com/wiki/PN532_NFC_HAT
I think the ticket confusion here is on the expectation of the cards screen. I too expected it to show cards as swiped.  I suggest updating the empty state message to "No cards registered. Add one below to get started" or similar.

Labeled also for future 3.

Confirmed it works both with recent 2.x versions and 3.x


Use the addon on openframeworks 0.11.0

Hello,
OF version 0.11.0 does not come with poco as a core addon.
Is there a workaround to use this addon on OF 0.11.0?
Tried to find some ofxPoco susbstitute, but no luck.
Thanks!
Antonio.

Creating the ofxpoco addon as a community addon should be pretty straight
forward. If fact you could probably just use the old one from the last
release
On Fri, Jan 27, 2023, 6:33 AM gizmow @.***> wrote:

Hello,
OF version 0.11.0 does not come with poco as a core addon.
Is there a workaround to use this addon on OF 0.11.0?
Tried to find some ofxPoco susbstitute, but no luck.
Thanks!
Antonio.
—
Reply to this email directly, view it on GitHub
https://github.com/bakercp/ofxSMTP/issues/18, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACJLRHE2JYYPJUEKXUELA3WUPFA7ANCNFSM6AAAAAAUIWQJJU
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Outstanding!

https://new.christopherbaker.net
On Fri, Jan 27, 2023 at 9:34 AM gizmow @.***> wrote:

Hey, thanks... Just did that abd worked perfectly!
Thanks!
El vie, 27 ene 2023 16:23, Christopher Baker @.***>
escribió:

Creating the ofxpoco addon as a community addon should be pretty straight
forward. If fact you could probably just use the old one from the last
release
On Fri, Jan 27, 2023, 6:33 AM gizmow @.***> wrote:

Hello,
OF version 0.11.0 does not come with poco as a core addon.
Is there a workaround to use this addon on OF 0.11.0?
Tried to find some ofxPoco susbstitute, but no luck.
Thanks!
Antonio.
—
Reply to this email directly, view it on GitHub
https://github.com/bakercp/ofxSMTP/issues/18, or unsubscribe
<

https://github.com/notifications/unsubscribe-auth/AACJLRHE2JYYPJUEKXUELA3WUPFA7ANCNFSM6AAAAAAUIWQJJU

.
You are receiving this because you are subscribed to this
thread.Message
ID: @.***>

—
Reply to this email directly, view it on GitHub
https://github.com/bakercp/ofxSMTP/issues/18#issuecomment-1406652124,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AA5LTGFMO6MYJMJLKCJCAQDWUPSARANCNFSM6AAAAAAUIWQJJU
.
You are receiving this because you authored the thread.Message ID:
@.***>

—
Reply to this email directly, view it on GitHub
https://github.com/bakercp/ofxSMTP/issues/18#issuecomment-1406743935,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACJLRGQLMCJLEOG5GLGWNTWUP2HXANCNFSM6AAAAAAUIWQJJU
.
You are receiving this because you commented.Message ID:
@.***>


Fixed #28206 -- Fixed RawQuerySet.resolve_model_init_order() to handle features.uppercases_column_names.

Ticket 28206.

buildbot, test on oracle.

buildbot, test on oracle.

This fixes the issue for us. Thank you! :+1:

Funny enough, I was one who dropped SmartyPantsHTMLTranslator from Sphinx and that broke the docs. Opened PR #8515 which should fix it.

@timgraham Thanks for review. What do you think about the new commit message?

buildbot, test on oracle.

buildbot, test on oracle.

Looks good -- is the crash Oracle specific? Might add "on Oracle" if so.

You're right, it crashed only on Oracle.


Alternative to Bootstrap

Card to document research and implementation of alternatives to Bootstrap
@xAsdfaf found this :) https://tailwindcss.com/

Confirmed: using tailwind


Add support for RFC 4043 and RFC 7585

Add module and test for RFC 4043 and RFC 7585

Codecov Report

Merging #104 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #104      +/-   ##
==========================================
+ Coverage   99.37%   99.37%   +<.01%
==========================================
  Files          95       97       +2
  Lines        5941     5967      +26
==========================================
+ Hits         5904     5930      +26
  Misses         37       37

Impacted Files
Coverage Δ

pyasn1_modules/rfc4043.py
100% <100%> (ø)

pyasn1_modules/rfc7585.py
100% <100%> (ø)

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 b61bbfa...2c00ba6. Read the comment docs.

Thank you!


What is the advantage over http-server package.

Hi this is a question.
I have been using https://github.com/http-party/http-server until recently someone told me I may give  local-web-server a try. So I was wondering what is the advantage over http-server package ?
Thanks!

Sorry, I have never used http-server before. You can find plenty of information about local-web-server on the wiki. Local-web-server is regularly maintained, supports HTTP2 and is 100% customisable. There is a plugin available to support most features, or you can create your own middleware plugin.

@qiulang  did you try local-web-server? What is your opinion?

I have tried it but the hard part is to persuade my team members to try it instead of  http-server. Hence the question.

The main issue with http-server right now is that ecstatic, for which http-server is basically a wrapper, is no longer developed.


jsonp.php?callback not working anymore?

Modernizr tries to use the http://caniuse.com/jsonp.php?callback=caniusecb for accessing some data during testing of its code:
https://github.com/Modernizr/Modernizr/blob/c2e5e48dbf12f975e89127143dc222ef43d0f9d4/test/browser/integration.jade#L38
Seems like the switch to https left this URL behind or is the Modernizr call wrong (calling it via https isnt working neither)
Or is this access dead for good / are there any plans to revive it?

Sorry to bother, but could I get a feedback on this @Fyrd ?

While I'd recommend you used the data from this repo instead, I'll see how hard it'll be to revive the jsonp functionality. Give me a day or so.

Dont put too much thought in it, working on a branch that uses the data from github directly. Since nobody else seems to miss the api besides us, it shouldnt be necessary to keep the old api just for us.

Dont put too much thought in it, working on a branch that uses the data from github directly. Since nobody else seems to miss the api besides us, it shouldnt be necessary to keep the old api just for us. Just wanted to know what youre thoughts were on this.

Made the move to using the caniuse-github-data mentioned in my previous comment. No need for any php apis anymore :-)


routine npm audit + remove nightwatch

nightwatch had a critical level vulnerability through its dep growl
nightwatch itself is installed part of vue but we are not using it
figured we can remove it so we will have less depds

@weiweitoo please review by:
deleting your node_modules folder
run npm ci
then confirm everything runs ok


Dependency issue while finetuning: lingvo 0.12.7 requires tensorflow~=2.9.2

Hi all,
I installed timesfm through poetry on Ubuntu 20.04
I have the following environment: Nvidia H100 GPUs available, nvidia 550 driver, cuda 12.4 installed.
Python is 3.10.12
After poetry install --only  pax and poetry shell
a) timesfm module still can't be found in the python path (no idea why, need to followup with pip install timesfm)
b) after timesfm package is installed, I realized that libcudart.so.11.0 was missing, which is normal since I have cuda 12.4. libcudart.so.11.0 is being asked because lingvo 0.12.7 requires TF 2.9.2 (which has direct dependency to cuda 11!)
Then I realized, isn't that a direct conflict? Timesfm has a dependency you need jax 0.4.26 which requires cuda 12.1!
jax = { version = ">=0.4.26", extras = ["cuda12"], python = ">=3.10,<3.11" }.
How is that supposed to work? Currently as it stands, and following the installation guide, I need both cuda 12 and cuda 11?
Any help would be greatly appreciated.

Thanks for your reply, here is my env:
tensorboard==2.9.1
tensorboard-data-server==0.6.1
tensorboard-plugin-wit==1.8.1
tensorflow==2.9.3
tensorflow-datasets==4.8.3
tensorflow-estimator==2.9.0
tensorflow-hub==0.16.1
tensorflow-io-gcs-filesystem==0.37.1
tensorflow-metadata==1.12.0
tensorflow-text==2.9.0
tensorstore==0.1.55
jax==0.4.26
jax-bitempered-loss==0.0.2
jax-cuda12-pjrt==0.4.26
jax-cuda12-plugin==0.4.26
jaxlib==0.4.26
jaxtyping==0.2.28
lingvo==0.12.7
As far as I see we have the same exact env (as it should), but still the jax version has issues (see below)
According to the official documentation https://www.tensorflow.org/install/source#gpu
As a result, trying to run tests/test_timesfm.py results to:
(timesfm-py3.10) test@zms3a:~/tsforecasting/timesfm/tests$ python test_timesfm.py
TimesFM v1.2.0. See https://github.com/google-research/timesfm/blob/master/README.md for updated APIs.
Loaded Jax TimesFM.
2024-10-10 20:33:13.559005: W tensorflow/stream_executor/platform/default/dso_loader.cc:64] Could not load dynamic library 'libcudart.so.11.0'; dlerror: libcudart.so.11.0: cannot open shared object file: No such file or directory
Could you please help? Perhaps you have a leftover libcudart.so.11.0 in your system that just works?

Hi @jmanous,
Did you try forecasting after that message. I also get that message but everything works beyond that.


Make rustls provider option configurable

This should allow downstream projects to configure the rustls provider that they need to be consistent across all their dependencies. This should address an issue in atuin where the rustls tls backend needs to be moved back to ring due to other workflows breaking. @tessus does this look good for that?
Closes #515

I think that should do it.

It looks like this needs to be a little more fleshed out, unfortunately.
With default features turned off, and the push-gateway feature enabled, the package fails to build because we try to use hyper_rustls::HttpsConnectorBuilder::with_native_roots, which needs the rustls-native-certs  feature and either the ring or aws-lc-rs feature. Since we have no provider feature enabled, it fails to compile. Since exporters are meant to be featureful by default, I want push-gateway to do the right thing, even if default features have been disabled.
Thinking out loud, I think we need to do three things:

change the push-gateway feature to actually enable hyper-rustls/aws-lc-rs
add a new feature -- push-gateway-no-tls-provider? -- that does what push-gateway does now so you can opt out of push-gateway and the default choice of AWS-LC
update the actual code in the exporter to use rustls::crypto::CryptoProvider::get_default and then switch to calling HttpsConnectorBuilder::with_provider_and_native_roots using the provider we get

Doing number 3 would mean we also need to essentially copy the error message that rustls emits when there's no provider feature flags and no default provider set, since that would still be a possibility for folks using push-gateway-no-tls-provider.
How does that sound?

push-gateway-no-tls-provider should work. Just fearful if this would eventually propagate to other variations, but probably it's not relevant for a while.
Let me get a second pair of eyes from Fedora rust packaging to check if we don't need to do other tweaks.

Thinking out loud, I think we need to do three things:

You mean all of them or one of them? The first one is probably the simplest, as long as when one wanted to use ring they wouldn't have to list too many deps after having to specify --no-default-features.

You mean all of them or one of them? The first one is probably the simplest, as long as when one wanted to use ring they wouldn't have to list too many deps after having to specify --no-default-features.

All of them.
Essentially, if we only had a feature flag called push-gateway-no-tls-provider, and a user wanted TLS support, then they would need to manually import rustls in their application, pick a provider, and install it as a default. That's unnecessary friction that I'm not willing to force on them.
This means we need at least two feature flags -- one that includes proper defaults, and one that includes no default -- which are represented by the first and second work items in the list. The third work item is the necessary code changes to support both of those variants, since the current code depends on hyper-rustls having a specific provider enabled, which doesn't work for the "no TLS provider" scenario.

Thanks for the explanation.
While I think that at one point in the future (and I want to stress that this point might not be as soon as we'd hope) the defaults will be ok across the board, I also think that there's considerable work to be done to support aws-lc-rs in the current ecosystem. e.g. as soon as aws-lc-rs is used, pipelines on illumos fail. Not that I will ever understand why someone would want to run a pipeline on illumos. But this shows that the transition from ring was not as seemless as people hoped.
I can only suggest to make it work with ring as well. At least for the time being. As soon as the transitional phase is over, ring might be deprecated anyway. But right now it is certainly part of many projects and thus I think it makes sense to support it in metrics as well.

Yeah, I mean, I think what I'd want to do, if anything, is something like:

push-gateway: enables Push Gateway support using crypto provider A in rustls/hyper-rustls
push-gateway-tls-provider-<name>: enables Push Gateway support using crypto provider <name> in rustls/hyper-rustls
push-gateway-no-tls-provider: enables Push Gateway support without any default cryptography provider configured for rustls/hyper-rustls

In this scenario, crypto provider A would be whatever we decide the default should be, and <name> would really just be the other one, since rustls only has Ring and AWS-LC anyways. :) MY personal feeling is that I'd probably want AWS-LC to be the default in this scenario.
(As a side note: I tend to want to standardize on AWS-LC to help drive adoption, and fixing of bugs, so that by being forced to deal with these sharp edges when they occur, people -- myself included -- are incentivized to fix them. Over time, being responsible for supporting contributions that I personally don't use or depend on, it ends up being a large amount of time that has to be spent dealing with this stuff... so I'd rather have the experience be a little worse for some users but much much better for the majority, by focusing my time on pushing the majority of users towards the things I know are well-supported.
This is all to say that I currently use AWS-LC at work, and for a bunch of personal projects, so I know if there's a build issue on Linux, Windows, or macOS, I will likely notice it very quickly and be able to help diagnose or contribute to fixing the problem.)


Multiline list of attributes

Hi,
Is there a way to split long attribute lists into several lines ? I tried:
input[
  type="text"
  class="form-control"
  name="plop"]

without success.

Same here. It gives me
(Slime.TemplateSyntaxError) Can't find matching delimiter "]" in line " id="asdf""
(slime) lib/slime/parser.ex:308: Slime.Parser.parse_wrapped_attributes/2
(slime) lib/slime/parser.ex:216: Slime.Parser.parse_line/2
(slime) lib/slime/parser.ex:75: Slime.Parser.parse_line/1
(slime) lib/slime/parser.ex:47: Slime.Parser.parse_lines/2
(slime) lib/slime/renderer.ex:20: Slime.Renderer.precompile/1
(phoenix_slime) lib/phoenix_slime/engine.ex:9: PhoenixSlime.Engine.compile/2
(phoenix) lib/phoenix/template.ex:378: Phoenix.Template.compile/2

Howdy @HenriMorlaye and @johannesE, this is not currently supported.  We could certainly look into it, if either of you'd like to give it a shot PRs are welcomed 👍

I'm still new to elixir, but I'm giving it a try :)
My first Idea was to join these lines in the preprocessor, but if I look at the way you handle the rest of the stuff (e.g. eex lines), I guess you'd want me to add it in the parser.
Btw I love how fast the tests run. No database, dependency or anything. :-)


fix: add ignore_error executor field

Describe the bug
TES v1.1 defines an ignore_error field as a property of an executor (defined here). Currently, the TesExecutor model does not have this attribute. As a result, the following error occurs when a response with the ignore_error is provided:
TypeError: Executor.__init__() got an unexpected keyword argument 'ignore_error'
Full traceback:

Executor causing error:

Software
Using proTES with Funnel

Thanks for reporting. This issue is due to Funnel, but not proTES, having adopted TES v1.1.0. The library that throws this error is py-tes.
A few points:

Upgrading py-tes to use the v1.1.0 branch should resolve this issue, but it's possible that we might run into other issues. For example, proTES may not forward the ignore_error value.
Alternatively, downgrading Funnel to a version that adopts v1.0.0 should also fix the issue. However, as far as I know, the latest Funnel version addresses a number of issues and is not just an upgrade to TES v1.1.0, so this would rather be a short-term solution.
The best way forward is probably to upgrade the proTES models to properly support v1.1.0, but making sure that it remains backwards-compatible.
Apart from dealing with ignore_error in one way or another, py-tes should not actually throw this error. This is because additionalProperties is not set to false in the TES specs, meaning that returning additional specs is not violating the specs and should not throw an error. We should open an issue about that.

Do you want to take care of these issues, @athith-g? That is:

Pick one of solutions 1.-3. to make the immediate problem go away.
Open an issue in the py-tes repo to let Liam and Kyle know that they should handle additional properties gracefully.

@uniqueg For sure I'll update the proTES models and open up that issue.


fix markdown check issue[skip ci]

fix markdown checker permissions issue and reference links issue

this pr is to fix the GitHub permissions issue, but I believe there are some other issues in the link check library, because there are some reference links marked as dead, but actually, they can be accessed, please see the log for more detail

and this link is not dead

I can not find a perfect workaround  or fix for now

I have a concern that the updated link check is referring to a personal github repository.  I notice other repos that use gaurav-nelson/github-action-markdown-link-check have fixed this issue without creating forks.  Is it possible for us to explore a bit further?
Also, some links are legitimately broken, and without this check we are missing those.  For example, the links on https://github.com/NVIDIA/spark-rapids/blob/branch-22.06/docs/dev/shims.md for the following text are broken:

ShimExpression For 3.0.x and 3.1.x
ShimExpression For 3.2.x

add a safe directory before the actions/checkout step to work around the permission issue.

build


Use Typescript to lint JSDoc annotations

A re-upload of #219 from my new repository.
#65

Awwwwsome.
Could you please minimize the diff (there are a lot of unnecessary changes like "!" added/removed). And it's good to go.
Also, npm-debug is not needed.

As soon as annotations are "compatible" with typescript it should be easy to generate TS definitions from JSDoc with something like this:

https://github.com/brettle/jsdoc-to-typescript-declaration
https://www.npmjs.com/package/tsd-jsdoc


Webpack config option to generate patch instead of new bundle

Feature request

What is the expected behavior?
Webpack bundle to have option to generate patch instead of a new bundle
What is motivation or use case for adding/changing the behavior?
This feature is meant for bug fixes in production and not for feature releases. Lets say I fix a bug making a line of change. Pushing a new bundle to production seems to be a heavy task. Instead of that, webpack should generate a patch file and only this patch will be pushed to production.
Doing this will help to make a proper use of browser's cache.
How should this be implemented in your opinion?
Any bundle should look for patches, If there are no patch bundle should run as it is.
If there is a patch(if a line of code is changed, patch should be the entire function), the patch code should be able to override the original function in the bundle.
Are you willing to work on this yourself?
yes - Preferably If this can be done without relying on webpack code. Reason is, working from scratch helps building fast than working on existing code base.

@imvetri how do you imagine the implementation of this? It is sound very difficult and impossible.

Technically possible, but in my opinion not worth it. You can split your bundle into parts which are individually cached, which has similar effect.

Thanks @sokra, @evilebottnawi . I think it is not a relevant topic to discuss here. Continuing it in stackoverflow.

@imvetri Can we close issue?

Yes. Thanks !


change package.json name field when scaffolding skeleton-navigation

?? (auto-reminder?)

https://github.com/monterey-framework/monterey/issues/12#issuecomment-230340010

Btw, we need to set name in package.json to name of project when installing from the github skeletons, else they all have same name.


Add plot_correlations() to plot series and acf/pacf

Reference Issues/PRs

Adds functionality requested in #817.
What does this implement/fix? Explain your changes.

This adds a function to plot with subplots that show a series (re-uses plot_series(), and its ACF/PACF plots.
Does your contribution introduce a new dependency? If yes, which one?

Adds dependency on pytest-mpl for testing plotting functionality against baseline plot output.
What should a reviewer concentrate their feedback on?

Any other comments?

In addition to plot_correlations() the PR makes a tweaks to plot_series() so that if a user supplies an Axe object the plot_series() plot will be created there instead of in a new figure (makes it easy to use plot_series() in other figures with additional subplots).
PR checklist

For all contributions

[X] I've added myself to the list of contributors.
[ ] Optionally, I've updated sktime's CODEOWNERS to receive notifications about future changes to these files.
[ ] I've added unit tests and made sure they pass locally.

For new estimators

[ ] I've added the estimator to the online documentation.
[ ] I've updated the existing example notebooks or provided a new one to showcase how my estimator works.

@mloning I believe I've got some useful working tests for the plotting functionality. These include input/output tests as well as tests to compare the generated plots against baseline plots. To do the baseline plot comparison, I'm using pytest-mpl.
Everything is passing locally on my machine, but I've installed pytest-mpl and we'd need this as part of the build-test process.
Since this would introduce a new build dependency, I've got a few questions on how best to do that:

Should I make a seperate PR or include that in this PR?
To add the testing dependency, would that just be adding pytest-mpl to sktime/build_tools/requirements.txt?

Hi @RNKuhns, I had a look at pytest-mpl and a few other discussion threads on the topic. I'm not sure if we want to actually compare images (see for example the answer here https://stackoverflow.com/questions/27948126/how-can-i-write-unit-tests-against-code-that-uses-matplotlib). Running numerical tests on the returned axis object may be a better idea. What do you think?
I'm happy to try it out on this PR, but I'm always hesitant to add dependencies and potential complications of the CI routines. I think build_tools/requirements.txt would be the only place where you would have to add pytest-mpl

@mloning I've pushed the code with the pytest-mpl dependency and unit test checks for you to take a look at. Note that I also added an option to let users customize the x-axis and y-axis labels in the call to plot_series
I was reading more and it seems like the biggest issue with the image comparison tests is the text varying with different versions of FreeType. I've used the option to remove text in pytest-mpl. I also opened up a Issue with them because that option wasn't removing the axis label text (I have a workaround in test_plotting.py that does it for now).
After you take a look, we can decide whether we want to actually do the image comparison checks. If not, I can remove that dependency and the image comparison unit tests.
I think the other unit tests give us reasonable coverage if we decide not to use pytest-mpl, since they are checking correct errors are raised and that the plotting functions execute without error.

@mloning I forgot to mention that I was thinking about the numerical tests on the axis. I'm actually not sure we need to go down that road. I'm also open to not adding the pytest-mpl dependency based on your thoughts after you take a look.
The approach I took, for the tests outside of the pytest-mpl tests is to assume matplotlib and seaborn will draw the plots correctly based on what is passed as x and y. So I focused my tests on making sure that the plot_series and plot_correlations run without error and can be drawn, as well as some checks to verify expected function input/output and correct error raising. Given that those are both pretty heavily used and tested, I don't see that as a bad strategy.
The only other thing I didn't really check in plot_series that I could see being a useful check to include is verifying that the creation of the combined x values from the series matches expectation. Let me know if you think it would be useful to add that test too.

@mloning I'm fine with removing dependency on pytest-mpl. I think we are fine assuming that checks that the plots execute without error (and raise errors as appropriate) should be fine.
I'll push an update without that later today.

FYI, @mloning, you can compare to hashes in pytest-mpl, that would solve the issue with the images carried around.
But generally, I don't lean either way on this issue.

I wanted to explore whether it made sense to include unit tests of the plot themselves. But I'm leaning towards excluding them for the time being. Whether the tests are on the images themselves or hashes, we are really testing the functionality of the underlying plotting library (e.g. matplotlib).
For our purposes, I think that tests that the plotting functions run without error (and the plots can be drawn) and any of our non-plotting logic works as expected should suffice.
So I'd vote that we exclude the pytest-mpl dependency for the time being. Caveat being that we always have the ability to add it later on if we find we are running into any issues.
@mloning and @fkiraly are you fine if I go that route and remove the pytest-mpl part of the request? I think other than that, this is probably largely ready to go.

@RNKuhns yes I agree with your comments!

@mloning I've made the changes I mentioned. Let me know if you see anything you want me to change after you take a look.

@mloning, I pushed commits with the changes you mentioned in your comments.

In plotting.py

Added series to plot_correlations() docstring
Removed unnecessary import of seaborn in plot_correlations()

test_plotting.py

Added note to clarify why I defined _plot_series()
Removed unnecessary import seaborn in some tests
Got rid of the elif statement for pd.DataFrame case in label and marker tests (pd.DataFrames are not valid input to functions)
Updated invalid input tests to also check pd.DataFrame case

Note that I left the import of matplotlib in the unit tests it was included in. The import was needed in those tests because the tests needed to reference the library outside of the function being tested (for example, to check the output of the function is the correct matplotlib type). Without importing the matplotlib library in the test this errored out.
Also note, when adding the pd.DataFrame invalid input case, I discovered that check_y() is raising a ValueError for pd.DataFrame input (b/c that is what _check_univariate() is raising, but TypeError for other types of invalid input. I've handled that in the plotting tests. This may be something we want to unifying (pd.DataFrame should raise TypeError in check_y()), but that should be another PR since it could affect other tests.

Now merged!


Issue with specifying the resourceUri definition

To avoid confusion, can we please change the below
"For Azure Application Managed Apps plans, the resourceUri is the Managed App resource group Id"
to
"For Azure Application Managed Apps plans, the resourceUri is the Managed App resource Id"
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: d4318999-c1d5-319f-a90d-33d077702d2b
Version Independent ID: 35343ad4-d893-016b-c4e2-2732c8c241eb
Content: Metering service APIs - Microsoft commercial marketplace
Content Source: articles/marketplace/marketplace-metering-service-apis.md
Service: marketplace
Sub-service: partnercenter-marketplace-publisher
GitHub Login: @arifgani
Microsoft Alias: argani

@santhoshb-msft - Thanks again for bringing this to our attention. We have updated the Doc and it will be live once its merged.  We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


C++ Demo - Facial Expression Recognition

This Pull Request introduces a C++ demo for utilizing and visualizing the Facial Expression Recognition (FER) model requested in issue #135 . The changes include:

demo.cpp: This file contains the demo implementation, featuring a class YuNet for face detection (adapted from face_detection_yunet/demo.cpp to create a stand-alone demo) and a class FER for preprocessing and inference with the Facial Expression Recognition model.

CMakeLists.txt: The related CMakeLists file necessary for building the program.

README.md: The README file has been updated to include information about this new demo.

The demo offers two modes of inference: real-time using the camera or processing a static image.
The coding style in demo.cpp aligns with the conventions used in other demos and follows the structure of the corresponding demo.py. Notably, I opted to utilize the estimateAffine2D function from the OpenCV library instead of reimplementing a similar mechanism, as was done in the Python version.
Testing
The program has been tested both with a single person and with multiple people at the same time.
Here are some screenshots:
Single Person from the cam

Multi-person from static image

Build & Run

Hi @fengyuentau thank you for your review. I just fixed the minor issues you pointed out.

Oops, sorry. I thought it was std::format. Please ignore this comment.

发件人: Daniele Affinita @.>
发送时间: Monday, February 26, 2024 9:11:08 PM
收件人: opencv/opencv_zoo @.>
抄送: Yuantao Feng @.>; Mention @.>
主题: Re: [opencv/opencv_zoo] C++ Demo - Facial Expression Recognition (PR #233)
@DaniAffCH commented on this pull request.

In models/facial_expression_recognition/demo.cpphttps://github.com/opencv/opencv_zoo/pull/233#discussion_r1502589679:

   Mat faces = faceDetectionModel.infer(frame);

   vector<String> expressions;

   for (int i = 0; i < faces.rows; ++i)

   {

       Mat face = faces.row(i);

       String exp = expressionRecognitionModel.infer(frame, face);

       expressions.push_back(exp);

       int x1 = static_cast<int>(faces.at<float>(i, 0));

       int y1 = static_cast<int>(faces.at<float>(i, 1));

       int w = static_cast<int>(faces.at<float>(i, 2));

       int h = static_cast<int>(faces.at<float>(i, 3));

       float conf = faces.at<float>(i, 14);

       std::cout << cv::format("%d: x1=%d, y1=%d, w=%d, h=%d, conf=%.4f expression=%s\n", i, x1, y1, w, h, conf, exp.c_str());

Do you mean the format?
―
Reply to this email directly, view it on GitHubhttps://github.com/opencv/opencv_zoo/pull/233#discussion_r1502589679, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AEDL63UZ6YD3UDPTRUPTGS3YVSCWZAVCNFSM6AAAAABDZGVPJOVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMYTSMBQHAZTSMBZGI.
You are receiving this because you were mentioned.Message ID: @.***>

@DaniAffCH Thank you for the contribution.


Replace Uptime Robot with some kind of uptime/outage detector

Azavea used Uptime Robot to determine whether OpenDataPhilly was available and alert if there was a problem. We need to separate this out from the rest of the Azavea/Element84 accounts. Should we simply create a new account with Uptime Robot or do something else?

I think the 3 cases for the site going down are:

GitHub is down -nothing really to do.
publish a bad site - unlikely, but would need a solution that checks content as well which makes it more complicated.  I'm thinking we don't try to do this and just check that it's up.
misconfiguration - mostly set it and forget it.  Once we are on the new setup this should be pretty static.

I'm not sure we need an uptime checker given these - and plenty would work for free including Uptime Robot.
If we want to do a basic check and are ok doing one check per hour I've got a slight preference for the open source - but hosted for free at our rate GlitchTip.  Was looking at using them at Azavea but they didn't have the features we needed at the time but have since added some of them (features not relevant for ODP though).

GlitchTip actually has support for checking for specific words being on the page - which seems like a good check.
Setup a GlitchTip org and we can just signin with GitHub if I understand correctly.

I also have a preference for an open source solution. If you recommend GlitchTip, let's go with that.

@BryanQuigley set up a GlitchTip account and it is now monitoring the site. I have removed the entry from Uptime Robot.


Is ELEN should be known in compile time?

According to Krste's slide, it said Vector ISA designed to allow same binary code to work across variations in VLEN and SLEN, so is it mean the toolchain (or others) need to take care about not portable part of implementation-defined parameters?
For example, in widening instruction case, if destination 2*SEW is larger than ELEN, user will get the illegal instruction exception in runtime.
But if ELEN is known in compile time, maybe compiler can check the widening instruction is legal or not for given ELEN value, or maybe loader can do a check the elf's ELEN is workable on current HW config.

The compiler should be able to assume (or be told by the user) the minimal value of ELEN. ELEN of course might be larger on the implementation.

Thanks.

Since ELEN≥max(XLEN, FLEN), perhaps it suffices to record the ABI for compatibility.  Specifically, ELEN≥32 for rv32f and ELEN≥64 for rv{32,64}d and rv64f.


Support clipboard write method to support other formats

This PR fixes #
Support clipboard write method so that other formats like html etc are also supported part from plain text

@gupta1 What is the purpose of this PR? Is the new, added code called from anywhere?

@gupta1 What is the purpose of this PR? Is the new, added code called from anywhere?

@alexdima Yes, it will be called from Azure Data Studio to support copy paste query and results scenario with html formatting.

I have discussed this with the team and they are in agreement that it does not make sense for us to have dead code in vscode. In fact, we have had in the past multiple efforts to remove dead code (e.g. https://github.com/microsoft/vscode/issues/38414). At this time (without a feature making use of this new method), it does not make sense to us to accept the PR. We recommend that you create a PR when the implementations are complete (e.g. the implementation for web currently throws) and when there is a valid use-case for the method in vscode (e.g. a vscode feature that uses the code).


Desktop - Unread count is incorrect when joining a thread

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Clicked on a thread made by other users that already had comments
Didn't add any comment
Left the thread
The thread disappeared from LHN

Expected Result:
New messages inside those threads should not be counted on my unread indications
Actual Result:
New messages on the threads that I can't see on my LHN are counting towards the unread counter on the app icon
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[ ] MacOS / Chrome / Safari
[x] MacOS / Desktop

Version Number: 1.3.67-1
Reproducible in staging?: n/a
Reproducible in production?: n./a
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
n/a
Expensify/Expensify Issue URL:
Issue reported by: @danieldoglas
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1694447504126939
View all open jobs on GitHub

This is super annoying and front-end fixable so I'm going to make it external

At a high level, I think we maybe just need to call Report.leaveRoom when you navigate away from a thread that you have not commented on

I think we should address those edge cases in the back-end – maybe in FixAccount, which I think still runs as part of OpenApp?

Bumped the PR to investigate the checks that weren't successful.

Since plenty of work was done here and we got pretty deep into the PR I think this counts for pay.
Summary of payments on this issue:

Urgency bonus: No
Contributor: @dukenv0307 $500 paid via Upwork
Reviewer: @fedirjh $500

@fedirjh accept the new offer and I'll pay out.

All paid up.


Global Create Menu - Error message when creating New Workspace

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:
Precondition: Create a new expensifail account and  Validate it

Launch the app and log in with a new account
Open Global Create Menu
Click "Create New Workspace"

Expected Result:
Workspace edit page opens when clicking "create new workspace"
Actual Result:
An error message appears when clicking "Create New Workspace" and won't open the workspace edit page, regardless new or old account.
Workaround:
Unknown
Platform:

Where is this issue occurring?

Web
iOS
Android
Desktop App
Mobile Web

Version Number: <IP_ADDRESS>
Reproducible in staging?: Yes
Reproducible in production?: Yes
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://user-images.githubusercontent.com/93399543/153475838-39a6c5b2-3561-4973-ac8d-13177f54f25b.mp4
Expensify/Expensify Issue URL:
Issue reported by: Applause
Slack conversation:
View all open jobs on GitHub

I'm not able to reproduce this. What account is this? We can check logs to see if there was an error, but only if we know which account was used.

@marcaaron Tester login credentials<EMAIL_ADDRESS>, Password: 9879869Clemen.

Hmm, I am not sure, but I don't see anything in the logs like an attempt to create the policy so guessing this is an authentication error or something else. Is it consistently reproducible? Going to close, but feel free to reopen if there are reliable reproduction steps.


maybe a doc thing, how do i get data from the map?

my map is drawn. I want to know the the bounding rectangle as shown.
I want to draw new markers from my database inside that rectangle
and then if the user changes it, I want to do that again ...  new center, new markers..   for move and zoom
(I assume use watch on the ref)
and I also want to add a slider for user to zoom in/out..

see #100


feat: Add Azure AI Search integration

Related Issues

fixes #950

Proposed Changes:
Implement a document store for Azure AI Search.
How did you test it?
Add unit tests for document store
Notes for the reviewer
Ready for an early feedback to detect any major changes needed in design.
Current status: Adding filters and search operations. The filter_documents() method is incomplete.
Checklist

I have read the contributors guidelines and the code of conduct
I have updated the related issue with new insights and changes
I added unit tests and updated the docstrings
I've used one of the conventional commit types for my PR title: fix:, feat:, build:, chore:, ci:, docs:, style:, refactor:, perf:, test:.

@vblagoje ready for your to give a high level feedback.

@Amnah199 looks like a step in the right direction. We also need to:

update values in integrations/azure_ai_search/pydoc/config.yml file
exercise this integration in examples dir (see other integrations)
Continue building examples for retriever and other required components

Examples dir and example scripts added are not only helpful to users but to you and reviewers to get a feel if everything is alright with this component from DX/UX perspective. With examples it is then easy to continue with writing a Notion docs page @dfokina use to create a new Haystack docs page we'll need for eventual merge.

@vblagoje thanks for the review. I will work on the examples after completing the implementation of filters and retrievers.

Closing this PR due to unresolved conflicts. A new PR has been opened here.


Adopt orbax

MEMO:
Msgpack is supported in orbax:
https://github.com/google/orbax/blob/main/docs/checkpoint.md#aggregatehandler
And therefore, probably, from_state_dict that is used in bobbin for variable addressing will still be around for a while.

This will be done under the hood in flax. so nothing will be required in bobbin.


Migrate CootWorker to TS

This update migrates the coot worker to TS. A few considerations.

Changes to CootWorker.ts will trigger a reload (during development) but the changes will not be actually included. If a change is done to the worker TS file then the file has to be transpiled by running npm run transpile-ts-worker . Another quick alternative (only for development) is to modify the JS file, but then it's important to add those changes back to the TS file.
Any production build script has to be aware of this. I think I have taken care of this but @stuartjamesmcnicholas please check that I didn't break electron builds in package.json. I have tested npm run-script make-linux on my machine and it produced a working electron app.

sed command needs to be invoked after transpiling the worker code otherwise the result is not a valid JS worker file. Problem is described here and here.

Need to add '.bu' sub-option to -i, I think
sed -i.bu '/export {}/d' public/baby-gru/CootWorker.js


start-server files

start-server files still point to tdsm.exe which is now TerrariaServer.exe

Thanks for the reminder. Those should be good now.
There are specific ones for OTA, as well as TDSM. The difference is TDSM uses server.config, whereas OTA is the default serverconfig.txt.


ISPN-7686 Stat getNumberOfEntries should not include expired entries.

https://issues.jboss.org/browse/ISPN-7686
@tristantarrant I've only updated the implementation of CacheMgmtInterceptor as calling StatsImpl::getNumberOfEntries in DistributedCacheStatsCallable::call is the equivalent of executing the SizeCommand on all nodes. Logic regarding numOwners and distributed mode is already handled in ClusterCacheStatsImpl.

I believe we still don't have a way to show the actual size of the caches / containers in the cluster from the management endpoints, including passivated entries.

Hrmm, is this not Cache.size ? This should include counts from all stores as well as in memory excluding expired entries.

@wburns I am talking about JMX and DMR

Oh I misunderstood. You mean they are not exposed through there. 👍

@tristantarrant @wburns updated.

Pushed to master, thanks


fixed a couple of deprecations

this is a first attempt to remove feature gates for features that are not going to make it into Rust in their current form, or have already been deprecated.
For instance plugins are (AFAIK) probably going to be rewritten. Unfortunately this means that compile_time_calculation is no longer solvable.
I'm not trying to remove feature gates for features that are currently being stabilized (like step_by), as theoretically they should make it into the stable part of the language.

I think this is the right step towards 1.0. Looks good to me.