Unable to login: thread 'main' panicked at 'failed to start cosmic-idle': src/main.rs:495

No idea if it could be related to #453
I'm on bb2350119400c47be764c348e67f1b38e858435f
EDIT: I seem to have the same problem with 322cf87a. I wonder if it's caused by a nixpkgs update.
EDIT2: ad9d5f38 seems to be working.
oct 31 13:32:12 desktop cosmic-session[2661]: thread 'main' panicked at 'failed to start cosmic-idle': src/main.rs:495
                                                 0: <backtrace::capture::Backtrace as core::default::Default>::default
                                                 1: log_panics::Config::install_panic_hook::{{closure}}
                                                 2: std::panicking::rust_panic_with_hook
                                                 3: std::panicking::begin_panic_handler::{{closure}}
                                                 4: std::sys::backtrace::__rust_end_short_backtrace
                                                 5: rust_begin_unwind
                                                 6: core::panicking::panic_fmt
                                                 7: cosmic_session::start_component::{{closure}}
                                                 8: cosmic_session::start::{{closure}}
                                                 9: <core::pin::Pin<P> as core::future::future::Future>::poll
                                                10: tokio::runtime::scheduler::current_thread::CurrentThread::block_on
                                                11: tokio::runtime::runtime::Runtime::block_on
                                                12: cosmic_session::main
                                                13: std::sys::backtrace::__rust_begin_short_backtrace
                                                14: std::rt::lang_start::{{closure}}
                                                15: std::rt::lang_start_internal
                                                16: main
                                                17: __libc_start_call_main
                                                18: __libc_start_main_alias_2
                                                19: _start

full log
2024-10-31T13:32:11-04:00 desktop greetd[2525]: gkr-pam: unable to locate daemon control file
2024-10-31T13:32:11-04:00 desktop greetd[2525]: gkr-pam: stashed password to try later in open session
2024-10-31T13:32:11-04:00 desktop greetd[2429]: pam_unix(greetd:session): session closed for user cosmic-greeter
2024-10-31T13:32:11-04:00 desktop greetd[2429]: pam_systemd(greetd:session): New sd-bus connection (system-bus-pam-systemd-2429) opened.
2024-10-31T13:32:11-04:00 desktop systemd-logind[858]: Session 1 logged out. Waiting for processes to exit.
2024-10-31T13:32:11-04:00 desktop greetd[2525]: pam_unix(greetd:session): session opened for user bbigras(uid=1000) by (uid=0)
2024-10-31T13:32:11-04:00 desktop greetd[2525]: pam_systemd(greetd:session): New sd-bus connection (system-bus-pam-systemd-2525) opened.
2024-10-31T13:32:11-04:00 desktop systemd-logind[858]: New session 3 of user bbigras.
2024-10-31T13:32:11-04:00 desktop systemd[1]: Created slice Slice /user/1000.
2024-10-31T13:32:11-04:00 desktop systemd[1]: Starting User Runtime Directory /run/user/1000...
2024-10-31T13:32:11-04:00 desktop systemd[1]: Finished User Runtime Directory /run/user/1000.
2024-10-31T13:32:11-04:00 desktop systemd[1]: Starting User Manager for UID 1000...
2024-10-31T13:32:11-04:00 desktop (systemd)[2578]: pam_unix(systemd-user:session): session opened for user bbigras(uid=1000) by (uid=0)
2024-10-31T13:32:11-04:00 desktop systemd-logind[858]: New session 4 of user bbigras.
2024-10-31T13:32:11-04:00 desktop systemd[2578]: Queued start job for default target Main User Target.
2024-10-31T13:32:11-04:00 desktop systemd[2578]: Created slice User Application Slice.
2024-10-31T13:32:11-04:00 desktop systemd[2578]: Reached target Paths.
2024-10-31T13:32:11-04:00 desktop systemd[2578]: Reached target Timers.
2024-10-31T13:32:11-04:00 desktop systemd[2578]: Starting D-Bus User Message Bus Socket...
2024-10-31T13:32:11-04:00 desktop systemd[2578]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
2024-10-31T13:32:11-04:00 desktop systemd[2578]: Listening on GnuPG cryptographic agent and passphrase cache.
2024-10-31T13:32:11-04:00 desktop systemd[2578]: Listening on PipeWire PulseAudio.
2024-10-31T13:32:11-04:00 desktop systemd[2578]: Listening on PipeWire Multimedia System Sockets.
2024-10-31T13:32:11-04:00 desktop systemd[2578]: Listening on D-Bus User Message Bus Socket.
2024-10-31T13:32:11-04:00 desktop systemd[2578]: Reached target Sockets.
2024-10-31T13:32:11-04:00 desktop systemd[2578]: Reached target Basic System.
2024-10-31T13:32:11-04:00 desktop systemd[1]: Started User Manager for UID 1000.
2024-10-31T13:32:11-04:00 desktop systemd[2578]: Starting gamemoded...
2024-10-31T13:32:11-04:00 desktop systemd[1]: Started Session 3 of User bbigras.
2024-10-31T13:32:11-04:00 desktop systemd[2578]: Starting Run user-specific NixOS activation...
2024-10-31T13:32:11-04:00 desktop systemd[2578]: Started Syncthing - Open Source Continuous File Synchronization.
2024-10-31T13:32:11-04:00 desktop systemd[2578]: Created slice User Core Session Slice.
2024-10-31T13:32:11-04:00 desktop systemd[2578]: Starting D-Bus User Message Bus...
2024-10-31T13:32:11-04:00 desktop greetd[2525]: gkr-pam: gnome-keyring-daemon started properly and unlocked keyring
2024-10-31T13:32:11-04:00 desktop systemd[2578]: Finished Run user-specific NixOS activation.
2024-10-31T13:32:11-04:00 desktop dbus-broker-launch[2603]: Ignoring duplicate name 'org.freedesktop.systemd1' in service file '/run/current-system/sw/share/dbus-1/services/org.freedesktop.systemd1.service'
2024-10-31T13:32:11-04:00 desktop dbus-broker-launch[2603]: Ignoring duplicate name 'ca.desrt.dconf' in service file '/nix/store/q1swl4zvd5vx317cg0cdrwmc4rab6876-system-path/share/dbus-1/services/ca.desrt.dconf.service'
2024-10-31T13:32:11-04:00 desktop dbus-broker-launch[2603]: Policy to allow eavesdropping in /etc/dbus-1/session.conf +27: Eavesdropping is deprecated and ignored
2024-10-31T13:32:11-04:00 desktop dbus-broker-launch[2603]: Policy to allow eavesdropping in /etc/dbus-1/session.conf +29: Eavesdropping is deprecated and ignored
2024-10-31T13:32:11-04:00 desktop dbus-broker-launch[2603]: Ignoring duplicate name 'com.feralinteractive.GameMode' in service file '/nix/store/q1swl4zvd5vx317cg0cdrwmc4rab6876-system-path/share/dbus-1/services/com.feralinteractive.GameMode.service'
2024-10-31T13:32:11-04:00 desktop dbus-broker-launch[2603]: Ignoring duplicate name 'org.bluez.obex' in service file '/nix/store/q1swl4zvd5vx317cg0cdrwmc4rab6876-system-path/share/dbus-1/services/org.bluez.obex.service'
2024-10-31T13:32:11-04:00 desktop dbus-broker-launch[2603]: Ignoring duplicate name 'org.flatpak.Authenticator.Oci' in service file '/nix/store/q1swl4zvd5vx317cg0cdrwmc4rab6876-system-path/share/dbus-1/services/org.flatpak.Authenticator.Oci.service'
2024-10-31T13:32:11-04:00 desktop dbus-broker-launch[2603]: Ignoring duplicate name 'org.freedesktop.Flatpak' in service file '/nix/store/q1swl4zvd5vx317cg0cdrwmc4rab6876-system-path/share/dbus-1/services/org.freedesktop.Flatpak.service'
2024-10-31T13:32:11-04:00 desktop dbus-broker-launch[2603]: Ignoring duplicate name 'org.freedesktop.impl.portal.PermissionStore' in service file '/nix/store/q1swl4zvd5vx317cg0cdrwmc4rab6876-system-path/share/dbus-1/services/org.freedesktop.impl.portal.PermissionStore.service'
2024-10-31T13:32:11-04:00 desktop dbus-broker-launch[2603]: Ignoring duplicate name 'org.freedesktop.impl.portal.Secret' in service file '/nix/store/q1swl4zvd5vx317cg0cdrwmc4rab6876-system-path/share/dbus-1/services/org.freedesktop.impl.portal.Secret.service'
2024-10-31T13:32:11-04:00 desktop dbus-broker-launch[2603]: Ignoring duplicate name 'org.freedesktop.impl.portal.desktop.cosmic' in service file '/nix/store/q1swl4zvd5vx317cg0cdrwmc4rab6876-system-path/share/dbus-1/services/org.freedesktop.impl.portal.desktop.cosmic.service'
2024-10-31T13:32:11-04:00 desktop dbus-broker-launch[2603]: Ignoring duplicate name 'org.freedesktop.impl.portal.desktop.gtk' in service file '/nix/store/q1swl4zvd5vx317cg0cdrwmc4rab6876-system-path/share/dbus-1/services/org.freedesktop.impl.portal.desktop.gtk.service'
2024-10-31T13:32:11-04:00 desktop dbus-broker-launch[2603]: Ignoring duplicate name 'org.freedesktop.portal.Desktop' in service file '/nix/store/q1swl4zvd5vx317cg0cdrwmc4rab6876-system-path/share/dbus-1/services/org.freedesktop.portal.Desktop.service'
2024-10-31T13:32:11-04:00 desktop dbus-broker-launch[2603]: Ignoring duplicate name 'org.freedesktop.portal.Documents' in service file '/nix/store/q1swl4zvd5vx317cg0cdrwmc4rab6876-system-path/share/dbus-1/services/org.freedesktop.portal.Documents.service'
2024-10-31T13:32:11-04:00 desktop dbus-broker-launch[2603]: Ignoring duplicate name 'org.freedesktop.portal.Flatpak' in service file '/nix/store/q1swl4zvd5vx317cg0cdrwmc4rab6876-system-path/share/dbus-1/services/org.freedesktop.portal.Flatpak.service'
2024-10-31T13:32:11-04:00 desktop dbus-broker-launch[2603]: Ignoring duplicate name 'org.freedesktop.secrets' in service file '/nix/store/q1swl4zvd5vx317cg0cdrwmc4rab6876-system-path/share/dbus-1/services/org.freedesktop.secrets.service'
2024-10-31T13:32:11-04:00 desktop dbus-broker-launch[2603]: Ignoring duplicate name 'org.freedesktop.systemd1' in service file '/nix/store/q1swl4zvd5vx317cg0cdrwmc4rab6876-system-path/share/dbus-1/services/org.freedesktop.systemd1.service'
2024-10-31T13:32:11-04:00 desktop dbus-broker-launch[2603]: Ignoring duplicate name 'org.gnome.keyring' in service file '/nix/store/q1swl4zvd5vx317cg0cdrwmc4rab6876-system-path/share/dbus-1/services/org.gnome.keyring.service'
2024-10-31T13:32:11-04:00 desktop dbus-broker-launch[2603]: Ignoring duplicate name 'org.gtk.vfs.AfcVolumeMonitor' in service file '/nix/store/q1swl4zvd5vx317cg0cdrwmc4rab6876-system-path/share/dbus-1/services/org.gtk.vfs.AfcVolumeMonitor.service'
2024-10-31T13:32:11-04:00 desktop dbus-broker-launch[2603]: Ignoring duplicate name 'org.gtk.vfs.Daemon' in service file '/nix/store/q1swl4zvd5vx317cg0cdrwmc4rab6876-system-path/share/dbus-1/services/org.gtk.vfs.Daemon.service'
2024-10-31T13:32:11-04:00 desktop dbus-broker-launch[2603]: Ignoring duplicate name 'org.gtk.vfs.GPhoto2VolumeMonitor' in service file '/nix/store/q1swl4zvd5vx317cg0cdrwmc4rab6876-system-path/share/dbus-1/services/org.gtk.vfs.GPhoto2VolumeMonitor.service'
2024-10-31T13:32:11-04:00 desktop dbus-broker-launch[2603]: Ignoring duplicate name 'org.gtk.vfs.GoaVolumeMonitor' in service file '/nix/store/q1swl4zvd5vx317cg0cdrwmc4rab6876-system-path/share/dbus-1/services/org.gtk.vfs.GoaVolumeMonitor.service'
2024-10-31T13:32:11-04:00 desktop dbus-broker-launch[2603]: Ignoring duplicate name 'org.gtk.vfs.MTPVolumeMonitor' in service file '/nix/store/q1swl4zvd5vx317cg0cdrwmc4rab6876-system-path/share/dbus-1/services/org.gtk.vfs.MTPVolumeMonitor.service'
2024-10-31T13:32:11-04:00 desktop dbus-broker-launch[2603]: Ignoring duplicate name 'org.gtk.vfs.Metadata' in service file '/nix/store/q1swl4zvd5vx317cg0cdrwmc4rab6876-system-path/share/dbus-1/services/org.gtk.vfs.Metadata.service'
2024-10-31T13:32:11-04:00 desktop dbus-broker-launch[2603]: Ignoring duplicate name 'org.gtk.vfs.UDisks2VolumeMonitor' in service file '/nix/store/q1swl4zvd5vx317cg0cdrwmc4rab6876-system-path/share/dbus-1/services/org.gtk.vfs.UDisks2VolumeMonitor.service'
2024-10-31T13:32:11-04:00 desktop dbus-broker-launch[2603]: Ignoring duplicate name 'org.mpris.MediaPlayer2.playerctld' in service file '/nix/store/q1swl4zvd5vx317cg0cdrwmc4rab6876-system-path/share/dbus-1/services/org.mpris.MediaPlayer2.playerctld.service'
2024-10-31T13:32:11-04:00 desktop dbus-broker-launch[2603]: Ignoring duplicate name 'org.bluez.obex' in service file '/nix/store/hfp3xwh0b0kiw7yai4ibf67hmfi9gg94-bluez-5.78/share/dbus-1/services/org.bluez.obex.service'
2024-10-31T13:32:11-04:00 desktop dbus-broker-launch[2603]: Ignoring duplicate name 'org.gtk.vfs.AfcVolumeMonitor' in service file '/nix/store/bbn6haii99i7ix9n9ii98cpqavfg6chy-gvfs-1.54.2/share/dbus-1/services/org.gtk.vfs.AfcVolumeMonitor.service'
2024-10-31T13:32:11-04:00 desktop dbus-broker-launch[2603]: Ignoring duplicate name 'org.gtk.vfs.Daemon' in service file '/nix/store/bbn6haii99i7ix9n9ii98cpqavfg6chy-gvfs-1.54.2/share/dbus-1/services/org.gtk.vfs.Daemon.service'
2024-10-31T13:32:11-04:00 desktop dbus-broker-launch[2603]: Ignoring duplicate name 'org.gtk.vfs.GPhoto2VolumeMonitor' in service file '/nix/store/bbn6haii99i7ix9n9ii98cpqavfg6chy-gvfs-1.54.2/share/dbus-1/services/org.gtk.vfs.GPhoto2VolumeMonitor.service'
2024-10-31T13:32:11-04:00 desktop dbus-broker-launch[2603]: Ignoring duplicate name 'org.gtk.vfs.GoaVolumeMonitor' in service file '/nix/store/bbn6haii99i7ix9n9ii98cpqavfg6chy-gvfs-1.54.2/share/dbus-1/services/org.gtk.vfs.GoaVolumeMonitor.service'
2024-10-31T13:32:11-04:00 desktop dbus-broker-launch[2603]: Ignoring duplicate name 'org.gtk.vfs.MTPVolumeMonitor' in service file '/nix/store/bbn6haii99i7ix9n9ii98cpqavfg6chy-gvfs-1.54.2/share/dbus-1/services/org.gtk.vfs.MTPVolumeMonitor.service'
2024-10-31T13:32:11-04:00 desktop dbus-broker-launch[2603]: Ignoring duplicate name 'org.gtk.vfs.Metadata' in service file '/nix/store/bbn6haii99i7ix9n9ii98cpqavfg6chy-gvfs-1.54.2/share/dbus-1/services/org.gtk.vfs.Metadata.service'
2024-10-31T13:32:11-04:00 desktop dbus-broker-launch[2603]: Ignoring duplicate name 'org.gtk.vfs.UDisks2VolumeMonitor' in service file '/nix/store/bbn6haii99i7ix9n9ii98cpqavfg6chy-gvfs-1.54.2/share/dbus-1/services/org.gtk.vfs.UDisks2VolumeMonitor.service'
2024-10-31T13:32:11-04:00 desktop dbus-broker-launch[2603]: Ignoring duplicate name 'org.freedesktop.impl.portal.Secret' in service file '/nix/store/acf24806dwiw6fyb40saqsbjcf5cfq3s-gnome-keyring-46.2/share/dbus-1/services/org.freedesktop.impl.portal.Secret.service'
2024-10-31T13:32:11-04:00 desktop dbus-broker-launch[2603]: Ignoring duplicate name 'org.freedesktop.secrets' in service file '/nix/store/acf24806dwiw6fyb40saqsbjcf5cfq3s-gnome-keyring-46.2/share/dbus-1/services/org.freedesktop.secrets.service'
2024-10-31T13:32:11-04:00 desktop dbus-broker-launch[2603]: Ignoring duplicate name 'org.gnome.keyring' in service file '/nix/store/acf24806dwiw6fyb40saqsbjcf5cfq3s-gnome-keyring-46.2/share/dbus-1/services/org.gnome.keyring.service'
2024-10-31T13:32:11-04:00 desktop dbus-broker-launch[2603]: Ignoring duplicate name 'org.gnome.keyring.PrivatePrompter' in service file '/nix/store/vx88h4r05n9mq83f1kgf7qq4bylrzd1v-gcr-3.41.2/share/dbus-1/services/org.gnome.keyring.PrivatePrompter.service'
2024-10-31T13:32:11-04:00 desktop dbus-broker-launch[2603]: Ignoring duplicate name 'org.gnome.keyring.SystemPrompter' in service file '/nix/store/vx88h4r05n9mq83f1kgf7qq4bylrzd1v-gcr-3.41.2/share/dbus-1/services/org.gnome.keyring.SystemPrompter.service'
2024-10-31T13:32:11-04:00 desktop dbus-broker-launch[2603]: Ignoring duplicate name 'org.flatpak.Authenticator.Oci' in service file '/nix/store/53r7zva6y2kimr9s96slf3fr21hdkw49-flatpak-1.14.10/share/dbus-1/services/org.flatpak.Authenticator.Oci.service'
2024-10-31T13:32:11-04:00 desktop dbus-broker-launch[2603]: Ignoring duplicate name 'org.freedesktop.Flatpak' in service file '/nix/store/53r7zva6y2kimr9s96slf3fr21hdkw49-flatpak-1.14.10/share/dbus-1/services/org.freedesktop.Flatpak.service'
2024-10-31T13:32:11-04:00 desktop dbus-broker-launch[2603]: Ignoring duplicate name 'org.freedesktop.portal.Flatpak' in service file '/nix/store/53r7zva6y2kimr9s96slf3fr21hdkw49-flatpak-1.14.10/share/dbus-1/services/org.freedesktop.portal.Flatpak.service'
2024-10-31T13:32:11-04:00 desktop dbus-broker-launch[2603]: Ignoring duplicate name 'ca.desrt.dconf' in service file '/nix/store/2v7kx8gawy8dr2awwad90j26434irpf6-dconf-0.40.0/share/dbus-1/services/ca.desrt.dconf.service'
2024-10-31T13:32:11-04:00 desktop dbus-broker-launch[2603]: Ignoring duplicate name 'org.freedesktop.impl.portal.PermissionStore' in service file '/nix/store/3rm3n29rmhr1289q82p5i67366j8akc0-xdg-desktop-portal-1.18.4/share/dbus-1/services/org.freedesktop.impl.portal.PermissionStore.service'
2024-10-31T13:32:11-04:00 desktop dbus-broker-launch[2603]: Ignoring duplicate name 'org.freedesktop.portal.Desktop' in service file '/nix/store/3rm3n29rmhr1289q82p5i67366j8akc0-xdg-desktop-portal-1.18.4/share/dbus-1/services/org.freedesktop.portal.Desktop.service'
2024-10-31T13:32:11-04:00 desktop dbus-broker-launch[2603]: Ignoring duplicate name 'org.freedesktop.portal.Documents' in service file '/nix/store/3rm3n29rmhr1289q82p5i67366j8akc0-xdg-desktop-portal-1.18.4/share/dbus-1/services/org.freedesktop.portal.Documents.service'
2024-10-31T13:32:11-04:00 desktop dbus-broker-launch[2603]: Ignoring duplicate name 'org.freedesktop.impl.portal.desktop.cosmic' in service file '/nix/store/z5qm8fmskb3wqg1palbl3g8f6xqhyagw-xdg-desktop-portal-cosmic-1.0.0-alpha.2-unstable-2024-10-10/share/dbus-1/services/org.freedesktop.impl.portal.desktop.cosmic.service'
2024-10-31T13:32:11-04:00 desktop dbus-broker-launch[2603]: Ignoring duplicate name 'org.freedesktop.impl.portal.desktop.gtk' in service file '/nix/store/8x1nggil4xpy6z6abc8mf83nqfplps8k-xdg-desktop-portal-gtk-1.15.1/share/dbus-1/services/org.freedesktop.impl.portal.desktop.gtk.service'
2024-10-31T13:32:11-04:00 desktop dbus-broker-launch[2603]: Ignoring duplicate name 'org.freedesktop.impl.portal.Secret' in service file '/nix/store/acf24806dwiw6fyb40saqsbjcf5cfq3s-gnome-keyring-46.2/share/dbus-1/services/org.freedesktop.impl.portal.Secret.service'
2024-10-31T13:32:11-04:00 desktop dbus-broker-launch[2603]: Ignoring duplicate name 'org.freedesktop.secrets' in service file '/nix/store/acf24806dwiw6fyb40saqsbjcf5cfq3s-gnome-keyring-46.2/share/dbus-1/services/org.freedesktop.secrets.service'
2024-10-31T13:32:11-04:00 desktop dbus-broker-launch[2603]: Ignoring duplicate name 'org.gnome.keyring' in service file '/nix/store/acf24806dwiw6fyb40saqsbjcf5cfq3s-gnome-keyring-46.2/share/dbus-1/services/org.gnome.keyring.service'
2024-10-31T13:32:11-04:00 desktop systemd[2578]: Started D-Bus User Message Bus.
2024-10-31T13:32:11-04:00 desktop dbus-broker-launch[2603]: Ready
2024-10-31T13:32:11-04:00 desktop systemd[2578]: Started gamemoded.
2024-10-31T13:32:11-04:00 desktop systemd[2578]: Reached target Main User Target.
2024-10-31T13:32:11-04:00 desktop systemd[2578]: Startup finished in 155ms.
2024-10-31T13:32:11-04:00 desktop systemd[1]: session-1.scope: Deactivated successfully.
2024-10-31T13:32:11-04:00 desktop systemd[1]: session-1.scope: Consumed 2.736s CPU time, 346M memory peak.
2024-10-31T13:32:11-04:00 desktop systemd-logind[858]: Removed session 1.
2024-10-31T13:32:11-04:00 desktop kernel: fbcon: Taking over console
2024-10-31T13:32:11-04:00 desktop cosmic-session[2661]: Starting cosmic-session
2024-10-31T13:32:11-04:00 desktop cosmic-session[2661]: starting process ' COSMIC_SESSION_SOCK=12 cosmic-comp '
2024-10-31T13:32:11-04:00 desktop systemd[1]: systemd-vconsole-setup.service: Deactivated successfully.
2024-10-31T13:32:11-04:00 desktop systemd[1]: Stopped Virtual Console Setup.
2024-10-31T13:32:11-04:00 desktop systemd[1]: Stopping Virtual Console Setup...
2024-10-31T13:32:11-04:00 desktop systemd[1]: Starting Virtual Console Setup...
2024-10-31T13:32:11-04:00 desktop systemd[1]: run-credentials-systemd\x2dvconsole\x2dsetup.service.mount: Deactivated successfully.
2024-10-31T13:32:12-04:00 desktop kernel: Console: switching to colour frame buffer device 160x45
2024-10-31T13:32:12-04:00 desktop systemd[1]: Finished Virtual Console Setup.
2024-10-31T13:32:12-04:00 desktop .cosmic-comp-wrapped[2670]: Failed to read config 'workspaces'
2024-10-31T13:32:12-04:00 desktop .cosmic-comp-wrapped[2670]: failed to read local shortcuts config 'system_actions': NoConfigDirectory
2024-10-31T13:32:12-04:00 desktop .cosmic-comp-wrapped[2670]: Key-Binding 'Period' only matched case insensitive for "period"
2024-10-31T13:32:12-04:00 desktop .cosmic-comp-wrapped[2670]: Key-Binding 'Comma' only matched case insensitive for "comma"
2024-10-31T13:32:12-04:00 desktop .cosmic-comp-wrapped[2670]: Key-Binding 'Period' only matched case insensitive for "period"
2024-10-31T13:32:12-04:00 desktop .cosmic-comp-wrapped[2670]: Key-Binding 'Comma' only matched case insensitive for "comma"
2024-10-31T13:32:12-04:00 desktop .cosmic-comp-wrapped[2670]: shortcuts custom config error: GetKey("custom", Os { code: 2, kind: NotFound, message: "No such file or directory" })
2024-10-31T13:32:12-04:00 desktop .cosmic-comp-wrapped[2670]: tiling exceptions custom config error: GetKey("tiling_exception_custom", Os { code: 2, kind: NotFound, message: "No such file or directory" })
2024-10-31T13:32:12-04:00 desktop .cosmic-comp-wrapped[2670]: Unable to become drm master, assuming unprivileged mode
2024-10-31T13:32:12-04:00 desktop cosmic-session[2661]: got environmental variables from cosmic-comp: [("WAYLAND_DISPLAY", "wayland-1"), ("DISPLAY", ":1")]
2024-10-31T13:32:12-04:00 desktop cosmic-session[2661]: starting process ' cosmic-settings-daemon '
2024-10-31T13:32:12-04:00 desktop systemd[2578]: Reached target Session services which should run early before the graphical session is brought up.
2024-10-31T13:32:12-04:00 desktop systemd[2578]: Reached target Cosmic Session Target.
2024-10-31T13:32:12-04:00 desktop systemd[2578]: Started polkit-gnome.
2024-10-31T13:32:12-04:00 desktop systemd[2578]: Started systembus-notify daemon.
2024-10-31T13:32:12-04:00 desktop systemd[2578]: Reached target Current graphical user session.
2024-10-31T13:32:12-04:00 desktop systemd[2578]: Starting Certificate and Key Storage...
2024-10-31T13:32:12-04:00 desktop systemd[2578]: Starting Secret Storage Service...
2024-10-31T13:32:12-04:00 desktop systemd[2578]: Starting SSH Key Agent...
2024-10-31T13:32:12-04:00 desktop systemd[2578]: Starting User folders update...
2024-10-31T13:32:12-04:00 desktop cosmic-session[2661]: starting process ' WAYLAND_DISPLAY=wayland-1 DISPLAY=:1 XDG_SESSION_TYPE=wayland DAEMON_NOTIFICATIONS_FD=22 WAYLAND_SOCKET=24 cosmic-notifications '
2024-10-31T13:32:12-04:00 desktop systembus-notify[2753]: connecting to d-bus user   bus: ok: unix:path=/run/user/1000/bus
2024-10-31T13:32:12-04:00 desktop systembus-notify[2753]: connecting to d-bus system bus: ok: unix:path=/run/dbus/system_bus_socket
2024-10-31T13:32:12-04:00 desktop systembus-notify[2753]: waiting for d-bus signals on system bus: type='signal',interface='net.nuetzlich.SystemNotifications',member='Notify'
2024-10-31T13:32:12-04:00 desktop systemd[2578]<EMAIL_ADDRESS>Skipped due to 'exec-condition'.
2024-10-31T13:32:12-04:00 desktop systemd[2578]: Condition check resulted in Secret Storage Service being skipped.
2024-10-31T13:32:12-04:00 desktop systemd[2578]<EMAIL_ADDRESS>Skipped due to 'exec-condition'.
2024-10-31T13:32:12-04:00 desktop systemd[2578]: Condition check resulted in SSH Key Agent being skipped.
2024-10-31T13:32:12-04:00 desktop systemd[2578]<EMAIL_ADDRESS>Skipped due to 'exec-condition'.
2024-10-31T13:32:12-04:00 desktop systemd[2578]: Condition check resulted in Certificate and Key Storage being skipped.
2024-10-31T13:32:12-04:00 desktop systemd[2578]: Started User folders update.
2024-10-31T13:32:12-04:00 desktop systemd[2578]: Reached target Startup of XDG autostart applications.
2024-10-31T13:32:12-04:00 desktop cosmic-session[2661]: sending 1 fds
2024-10-31T13:32:12-04:00 desktop cosmic-session[2661]: starting process ' WAYLAND_DISPLAY=wayland-1 DISPLAY=:1 XDG_SESSION_TYPE=wayland PANEL_NOTIFICATIONS_FD=20 WAYLAND_SOCKET=24 cosmic-panel '
2024-10-31T13:32:12-04:00 desktop cosmic-session[2661]: sending 1 fds
2024-10-31T13:32:12-04:00 desktop cosmic-session[2661]: starting process ' WAYLAND_DISPLAY=wayland-1 DISPLAY=:1 XDG_SESSION_TYPE=wayland WAYLAND_SOCKET=24 cosmic-app-library '
2024-10-31T13:32:12-04:00 desktop cosmic-session[2661]: sending 1 fds
2024-10-31T13:32:12-04:00 desktop cosmic-session[2661]: starting process ' WAYLAND_DISPLAY=wayland-1 DISPLAY=:1 XDG_SESSION_TYPE=wayland WAYLAND_SOCKET=38 cosmic-launcher '
2024-10-31T13:32:12-04:00 desktop cosmic-session[2661]: sending 1 fds
2024-10-31T13:32:12-04:00 desktop cosmic-session[2661]: starting process ' WAYLAND_DISPLAY=wayland-1 DISPLAY=:1 XDG_SESSION_TYPE=wayland WAYLAND_SOCKET=44 cosmic-workspaces '
2024-10-31T13:32:12-04:00 desktop cosmic-session[2661]: sending 1 fds
2024-10-31T13:32:12-04:00 desktop cosmic-session[2661]: starting process ' WAYLAND_DISPLAY=wayland-1 DISPLAY=:1 XDG_SESSION_TYPE=wayland WAYLAND_SOCKET=50 cosmic-osd '
2024-10-31T13:32:12-04:00 desktop cosmic-session[2661]: sending 1 fds
2024-10-31T13:32:12-04:00 desktop cosmic-session[2661]: starting process ' WAYLAND_DISPLAY=wayland-1 DISPLAY=:1 XDG_SESSION_TYPE=wayland WAYLAND_SOCKET=56 cosmic-bg '
2024-10-31T13:32:12-04:00 desktop acpid[806]: client connected from 2737[1000:100]
2024-10-31T13:32:12-04:00 desktop acpid[806]: 1 client rule loaded
2024-10-31T13:32:12-04:00 desktop cosmic-session[2661]: sending 1 fds
2024-10-31T13:32:12-04:00 desktop cosmic-session[2661]: starting process ' WAYLAND_DISPLAY=wayland-1 DISPLAY=:1 XDG_SESSION_TYPE=wayland WAYLAND_SOCKET=60 cosmic-greeter '
2024-10-31T13:32:12-04:00 desktop cosmic-session[2661]: sending 1 fds
2024-10-31T13:32:12-04:00 desktop cosmic-session[2661]: starting process ' WAYLAND_DISPLAY=wayland-1 DISPLAY=:1 XDG_SESSION_TYPE=wayland WAYLAND_SOCKET=67 cosmic-files-applet '
2024-10-31T13:32:12-04:00 desktop systemd[1]: Starting Locale Service...
2024-10-31T13:32:12-04:00 desktop systemd[2578]: Started cosmic-app-library.scope.
2024-10-31T13:32:12-04:00 desktop systemd[2578]: Started cosmic-launcher.scope.
2024-10-31T13:32:12-04:00 desktop systemd[2578]: Started cosmic-workspaces.scope.
2024-10-31T13:32:12-04:00 desktop cosmic-session[2661]: sending 1 fds
2024-10-31T13:32:12-04:00 desktop cosmic-session[2661]: starting process ' WAYLAND_DISPLAY=wayland-1 DISPLAY=:1 XDG_SESSION_TYPE=wayland WAYLAND_SOCKET=73 cosmic-idle '
2024-10-31T13:32:12-04:00 desktop systemd[2578]: Started cosmic-osd.scope.
2024-10-31T13:32:12-04:00 desktop systemd[1]: Started Locale Service.
2024-10-31T13:32:12-04:00 desktop cosmic-session[2661]: thread 'main' panicked at 'failed to start cosmic-idle': src/main.rs:495
                                                           0: <backtrace::capture::Backtrace as core::default::Default>::default
                                                           1: log_panics::Config::install_panic_hook::{{closure}}
                                                           2: std::panicking::rust_panic_with_hook
                                                           3: std::panicking::begin_panic_handler::{{closure}}
                                                           4: std::sys::backtrace::__rust_end_short_backtrace
                                                           5: rust_begin_unwind
                                                           6: core::panicking::panic_fmt
                                                           7: cosmic_session::start_component::{{closure}}
                                                           8: cosmic_session::start::{{closure}}
                                                           9: <core::pin::Pin<P> as core::future::future::Future>::poll
                                                          10: tokio::runtime::scheduler::current_thread::CurrentThread::block_on
                                                          11: tokio::runtime::runtime::Runtime::block_on
                                                          12: cosmic_session::main
                                                          13: std::sys::backtrace::__rust_begin_short_backtrace
                                                          14: std::rt::lang_start::{{closure}}
                                                          15: std::rt::lang_start_internal
                                                          16: main
                                                          17: __libc_start_call_main
                                                          18: __libc_start_main_alias_2
                                                          19: _start
2024-10-31T13:32:12-04:00 desktop systemd[2578]: Stopped target Cosmic Session Target.
2024-10-31T13:32:12-04:00 desktop systemd[2578]: Stopped target Current graphical user session.
2024-10-31T13:32:12-04:00 desktop systemd[2578]: Stopped target Session services which should run early before the graphical session is brought up.
2024-10-31T13:32:12-04:00 desktop greetd[2525]: pam_unix(greetd:session): session closed for user bbigras
2024-10-31T13:32:12-04:00 desktop systemd[2578]: Stopped target Startup of XDG autostart applications.
2024-10-31T13:32:12-04:00 desktop greetd[2525]: pam_systemd(greetd:session): New sd-bus connection (system-bus-pam-systemd-2525) opened.
2024-10-31T13:32:12-04:00 desktop systemd[2578]: Stopping polkit-gnome...
2024-10-31T13:32:12-04:00 desktop systemd[2578]: Stopped polkit-gnome.
2024-10-31T13:32:12-04:00 desktop systemd-logind[858]: Session 3 logged out. Waiting for processes to exit.
2024-10-31T13:32:13-04:00 desktop greetd[2799]: pam_unix(greetd:session): session opened for user cosmic-greeter(uid=983) by (uid=0)
2024-10-31T13:32:13-04:00 desktop greetd[2799]: pam_systemd(greetd:session): New sd-bus connection (system-bus-pam-systemd-2799) opened.
2024-10-31T13:32:13-04:00 desktop systemd-logind[858]: New session 5 of user cosmic-greeter.
2024-10-31T13:32:13-04:00 desktop systemd[1]: Started Session 5 of User cosmic-greeter.
2024-10-31T13:32:13-04:00 desktop systemd[1]: session-3.scope: Deactivated successfully.
2024-10-31T13:32:13-04:00 desktop systemd[1]: session-3.scope: Consumed 346ms CPU time, 199.1M memory peak.
2024-10-31T13:32:13-04:00 desktop systemd-logind[858]: Removed session 3.
2024-10-31T13:32:13-04:00 desktop greetd[2799]: gkr-pam: gnome-keyring-daemon started properly
2024-10-31T13:32:13-04:00 desktop cosmic-greeter[2807]: 2024-10-31T17:32:13.544857Z ERROR cosmic_comp::config: Failed to read config 'workspaces' err=NoConfigDirectory
2024-10-31T13:32:13-04:00 desktop .cosmic-comp-wrapped[2807]: Failed to read config 'workspaces'
2024-10-31T13:32:13-04:00 desktop cosmic-greeter[2807]: 2024-10-31T17:32:13.547407Z ERROR cosmic_settings_config::shortcuts: failed to read local shortcuts config 'system_actions': NoConfigDirectory
2024-10-31T13:32:13-04:00 desktop .cosmic-comp-wrapped[2807]: failed to read local shortcuts config 'system_actions': NoConfigDirectory
2024-10-31T13:32:13-04:00 desktop .cosmic-comp-wrapped[2807]: Key-Binding 'Period' only matched case insensitive for "period"
2024-10-31T13:32:13-04:00 desktop cosmic-greeter[2807]: 2024-10-31T17:32:13.547466Z  WARN cosmic_settings_config::shortcuts::sym: Key-Binding 'Period' only matched case insensitive for "period"
2024-10-31T13:32:13-04:00 desktop cosmic-greeter[2807]: 2024-10-31T17:32:13.547475Z  WARN cosmic_settings_config::shortcuts::sym: Key-Binding 'Comma' only matched case insensitive for "comma"
2024-10-31T13:32:13-04:00 desktop cosmic-greeter[2807]: 2024-10-31T17:32:13.547478Z  WARN cosmic_settings_config::shortcuts::sym: Key-Binding 'Period' only matched case insensitive for "period"
2024-10-31T13:32:13-04:00 desktop cosmic-greeter[2807]: 2024-10-31T17:32:13.547482Z  WARN cosmic_settings_config::shortcuts::sym: Key-Binding 'Comma' only matched case insensitive for "comma"
2024-10-31T13:32:13-04:00 desktop .cosmic-comp-wrapped[2807]: Key-Binding 'Comma' only matched case insensitive for "comma"
2024-10-31T13:32:13-04:00 desktop cosmic-greeter[2807]: 2024-10-31T17:32:13.547518Z ERROR cosmic_settings_config::shortcuts: shortcuts custom config error: GetKey("custom", Os { code: 2, kind: NotFound, message: "No such file or directory" })
2024-10-31T13:32:13-04:00 desktop .cosmic-comp-wrapped[2807]: Key-Binding 'Period' only matched case insensitive for "period"
2024-10-31T13:32:13-04:00 desktop .cosmic-comp-wrapped[2807]: Key-Binding 'Comma' only matched case insensitive for "comma"
2024-10-31T13:32:13-04:00 desktop .cosmic-comp-wrapped[2807]: shortcuts custom config error: GetKey("custom", Os { code: 2, kind: NotFound, message: "No such file or directory" })
2024-10-31T13:32:13-04:00 desktop cosmic-greeter[2807]: 2024-10-31T17:32:13.547646Z ERROR cosmic_settings_config::window_rules: tiling exceptions custom config error: GetKey("tiling_exception_custom", Os { code: 2, kind: NotFound, message: "No such file or directory" })
2024-10-31T13:32:13-04:00 desktop .cosmic-comp-wrapped[2807]: tiling exceptions custom config error: GetKey("tiling_exception_custom", Os { code: 2, kind: NotFound, message: "No such file or directory" })
2024-10-31T13:32:13-04:00 desktop cosmic-greeter[2807]: 2024-10-31T17:32:13.645902Z  WARN smithay::backend::drm::device::fd: Unable to become drm master, assuming unprivileged mode
2024-10-31T13:32:13-04:00 desktop .cosmic-comp-wrapped[2807]: Unable to become drm master, assuming unprivileged mode
2024-10-31T13:32:13-04:00 desktop cosmic-greeter[2868]: [2024-10-31T17:32:13Z WARN  cosmic_greeter::greeter] failed to read session directory "/var/lib/cosmic-greeter/.local/share/flatpak/exports/share/wayland-sessions": Os { code: 2, kind: NotFound, message: "No such file or directory" }
2024-10-31T13:32:13-04:00 desktop cosmic-greeter[2868]: [2024-10-31T17:32:13Z WARN  cosmic_greeter::greeter] failed to read session directory "/var/lib/flatpak/exports/share/wayland-sessions": Os { code: 2, kind: NotFound, message: "No such file or directory" }
2024-10-31T13:32:13-04:00 desktop cosmic-greeter[2868]: [2024-10-31T17:32:13Z WARN  cosmic_greeter::greeter] failed to read session directory "/var/lib/cosmic-greeter/.nix-profile/share/wayland-sessions": Os { code: 2, kind: NotFound, message: "No such file or directory" }
2024-10-31T13:32:13-04:00 desktop cosmic-greeter[2868]: [2024-10-31T17:32:13Z WARN  cosmic_greeter::greeter] failed to read session directory "/nix/profile/share/wayland-sessions": Os { code: 2, kind: NotFound, message: "No such file or directory" }
2024-10-31T13:32:13-04:00 desktop cosmic-greeter[2868]: [2024-10-31T17:32:13Z WARN  cosmic_greeter::greeter] failed to read session directory "/var/lib/cosmic-greeter/.local/state/nix/profile/share/wayland-sessions": Os { code: 2, kind: NotFound, message: "No such file or directory" }
2024-10-31T13:32:13-04:00 desktop cosmic-greeter[2868]: [2024-10-31T17:32:13Z WARN  cosmic_greeter::greeter] failed to read session directory "/etc/profiles/per-user/cosmic-greeter/share/wayland-sessions": Os { code: 2, kind: NotFound, message: "No such file or directory" }
2024-10-31T13:32:13-04:00 desktop cosmic-greeter[2868]: [2024-10-31T17:32:13Z WARN  cosmic_greeter::greeter] failed to read session directory "/nix/var/nix/profiles/default/share/wayland-sessions": Os { code: 2, kind: NotFound, message: "No such file or directory" }
2024-10-31T13:32:13-04:00 desktop cosmic-greeter[2868]: [2024-10-31T17:32:13Z WARN  cosmic_greeter::greeter] failed to read session directory "/run/current-system/sw/share/wayland-sessions": Os { code: 2, kind: NotFound, message: "No such file or directory" }
2024-10-31T13:32:13-04:00 desktop cosmic-greeter[2868]: [2024-10-31T17:32:13Z WARN  cosmic_greeter::greeter] failed to read session directory "/nix/store/c1mxhjj0422wqbc28dl0xvhkv0ijc97j-cosmic-comp-1.0.0-alpha.2-unstable-2024-10-25/share/wayland-sessions": Os { code: 2, kind: NotFound, message: "No such file or directory" }
2024-10-31T13:32:13-04:00 desktop cosmic-greeter[2868]: [2024-10-31T17:32:13Z WARN  cosmic_greeter::greeter] failed to read session directory "/nix/store/63ii8w5pngrfkslf83rf088v64yp99yr-cosmic-settings-1.0.0-alpha.2-unstable-2024-10-30/share/wayland-sessions": Os { code: 2, kind: NotFound, message: "No such file or directory" }
2024-10-31T13:32:13-04:00 desktop cosmic-greeter[2868]: [2024-10-31T17:32:13Z WARN  cosmic_greeter::greeter] failed to read session directory "/nix/store/3w5xq1af6fhw0di21mp0ra8z7yl8g24b-cosmic-icons-1.0.0-alpha.2-unstable-2024-10-02/share/wayland-sessions": Os { code: 2, kind: NotFound, message: "No such file or directory" }
2024-10-31T13:32:13-04:00 desktop cosmic-greeter[2868]: [2024-10-31T17:32:13Z WARN  cosmic_greeter::greeter] failed to read session directory "/nix/store/vzvr6yzbikfh0dhxbg9fpsbgxzpk3ppx-cosmic-greeter-1.0.0-alpha.2-unstable-2024-10-14/share/wayland-sessions": Os { code: 2, kind: NotFound, message: "No such file or directory" }
2024-10-31T13:32:13-04:00 desktop cosmic-greeter[2868]: [2024-10-31T17:32:13Z WARN  cosmic_greeter::greeter] failed to read session directory "/nix/store/63ii8w5pngrfkslf83rf088v64yp99yr-cosmic-settings-1.0.0-alpha.2-unstable-2024-10-30/share/wayland-sessions": Os { code: 2, kind: NotFound, message: "No such file or directory" }
2024-10-31T13:32:13-04:00 desktop cosmic-greeter[2868]: [2024-10-31T17:32:13Z WARN  cosmic_greeter::greeter] failed to read session directory "/nix/store/3w5xq1af6fhw0di21mp0ra8z7yl8g24b-cosmic-icons-1.0.0-alpha.2-unstable-2024-10-02/share/wayland-sessions": Os { code: 2, kind: NotFound, message: "No such file or directory" }
2024-10-31T13:32:13-04:00 desktop cosmic-greeter[2868]: [2024-10-31T17:32:13Z WARN  cosmic_greeter::greeter] failed to read session directory "/var/lib/cosmic-greeter/.local/share/flatpak/exports/share/xsessions": Os { code: 2, kind: NotFound, message: "No such file or directory" }
2024-10-31T13:32:13-04:00 desktop cosmic-greeter[2868]: [2024-10-31T17:32:13Z WARN  cosmic_greeter::greeter] failed to read session directory "/var/lib/flatpak/exports/share/xsessions": Os { code: 2, kind: NotFound, message: "No such file or directory" }
2024-10-31T13:32:13-04:00 desktop cosmic-greeter[2868]: [2024-10-31T17:32:13Z WARN  cosmic_greeter::greeter] failed to read session directory "/var/lib/cosmic-greeter/.nix-profile/share/xsessions": Os { code: 2, kind: NotFound, message: "No such file or directory" }
2024-10-31T13:32:13-04:00 desktop cosmic-greeter[2868]: [2024-10-31T17:32:13Z WARN  cosmic_greeter::greeter] failed to read session directory "/nix/profile/share/xsessions": Os { code: 2, kind: NotFound, message: "No such file or directory" }
2024-10-31T13:32:13-04:00 desktop cosmic-greeter[2868]: [2024-10-31T17:32:13Z WARN  cosmic_greeter::greeter] failed to read session directory "/var/lib/cosmic-greeter/.local/state/nix/profile/share/xsessions": Os { code: 2, kind: NotFound, message: "No such file or directory" }
2024-10-31T13:32:13-04:00 desktop cosmic-greeter[2868]: [2024-10-31T17:32:13Z WARN  cosmic_greeter::greeter] failed to read session directory "/etc/profiles/per-user/cosmic-greeter/share/xsessions": Os { code: 2, kind: NotFound, message: "No such file or directory" }
2024-10-31T13:32:13-04:00 desktop cosmic-greeter[2868]: [2024-10-31T17:32:13Z WARN  cosmic_greeter::greeter] failed to read session directory "/nix/var/nix/profiles/default/share/xsessions": Os { code: 2, kind: NotFound, message: "No such file or directory" }
2024-10-31T13:32:13-04:00 desktop cosmic-greeter[2868]: [2024-10-31T17:32:13Z WARN  cosmic_greeter::greeter] failed to read session directory "/run/current-system/sw/share/xsessions": Os { code: 2, kind: NotFound, message: "No such file or directory" }
2024-10-31T13:32:13-04:00 desktop cosmic-greeter[2868]: [2024-10-31T17:32:13Z WARN  cosmic_greeter::greeter] failed to read session directory "/nix/store/c1mxhjj0422wqbc28dl0xvhkv0ijc97j-cosmic-comp-1.0.0-alpha.2-unstable-2024-10-25/share/xsessions": Os { code: 2, kind: NotFound, message: "No such file or directory" }
2024-10-31T13:32:13-04:00 desktop cosmic-greeter[2868]: [2024-10-31T17:32:13Z WARN  cosmic_greeter::greeter] failed to read session directory "/nix/store/63ii8w5pngrfkslf83rf088v64yp99yr-cosmic-settings-1.0.0-alpha.2-unstable-2024-10-30/share/xsessions": Os { code: 2, kind: NotFound, message: "No such file or directory" }
2024-10-31T13:32:13-04:00 desktop cosmic-greeter[2868]: [2024-10-31T17:32:13Z WARN  cosmic_greeter::greeter] failed to read session directory "/nix/store/3w5xq1af6fhw0di21mp0ra8z7yl8g24b-cosmic-icons-1.0.0-alpha.2-unstable-2024-10-02/share/xsessions": Os { code: 2, kind: NotFound, message: "No such file or directory" }
2024-10-31T13:32:13-04:00 desktop cosmic-greeter[2868]: [2024-10-31T17:32:13Z WARN  cosmic_greeter::greeter] failed to read session directory "/nix/store/vzvr6yzbikfh0dhxbg9fpsbgxzpk3ppx-cosmic-greeter-1.0.0-alpha.2-unstable-2024-10-14/share/xsessions": Os { code: 2, kind: NotFound, message: "No such file or directory" }
2024-10-31T13:32:13-04:00 desktop cosmic-greeter[2868]: [2024-10-31T17:32:13Z WARN  cosmic_greeter::greeter] failed to read session directory "/nix/store/63ii8w5pngrfkslf83rf088v64yp99yr-cosmic-settings-1.0.0-alpha.2-unstable-2024-10-30/share/xsessions": Os { code: 2, kind: NotFound, message: "No such file or directory" }
2024-10-31T13:32:13-04:00 desktop cosmic-greeter[2868]: [2024-10-31T17:32:13Z WARN  cosmic_greeter::greeter] failed to read session directory "/nix/store/3w5xq1af6fhw0di21mp0ra8z7yl8g24b-cosmic-icons-1.0.0-alpha.2-unstable-2024-10-02/share/xsessions": Os { code: 2, kind: NotFound, message: "No such file or directory" }
2024-10-31T13:32:13-04:00 desktop cosmic-greeter[2868]: [2024-10-31T17:32:13Z WARN  cosmic_greeter::greeter] failed to load keyboard layouts: No such file or directory (os error 2)
2024-10-31T13:32:13-04:00 desktop cosmic-greeter[2868]: [2024-10-31T17:32:13Z WARN  cosmic_greeter::greeter] output wl_output@6: unsupported source Single([0.063, 0.165, 0.298])
2024-10-31T13:32:17-04:00 desktop acpid[806]: client 2737[1000:100] has disconnected
2024-10-31T13:32:23-04:00 desktop systemd[1]: Stopping User Manager for UID 1000...
2024-10-31T13:32:23-04:00 desktop systemd[2578]: Activating special unit Exit the Session...
2024-10-31T13:32:23-04:00 desktop systemd[2578]: Stopped target Main User Target.
2024-10-31T13:32:23-04:00 desktop systemd[2578]: Stopping gamemoded...
2024-10-31T13:32:23-04:00 desktop systemd[2578]: Stopping Syncthing - Open Source Continuous File Synchronization...
2024-10-31T13:32:23-04:00 desktop systemd[2578]: Stopping systembus-notify daemon...
2024-10-31T13:32:23-04:00 desktop systemd[2578]: Stopped gamemoded.
2024-10-31T13:32:23-04:00 desktop systemd[2578]: Stopped systembus-notify daemon.
2024-10-31T13:32:23-04:00 desktop systemd[2578]: Stopped Syncthing - Open Source Continuous File Synchronization.
2024-10-31T13:32:23-04:00 desktop systemd[2578]: syncthing.service: Consumed 706ms CPU time, 103M memory peak.
2024-10-31T13:32:23-04:00 desktop systemd[2578]: Stopped target Basic System.
2024-10-31T13:32:23-04:00 desktop systemd[2578]: Stopped target Paths.
2024-10-31T13:32:23-04:00 desktop systemd[2578]: Stopped target Sockets.
2024-10-31T13:32:23-04:00 desktop systemd[2578]: Stopped target Timers.
2024-10-31T13:32:23-04:00 desktop systemd[2578]: Closed GnuPG cryptographic agent (ssh-agent emulation).
2024-10-31T13:32:23-04:00 desktop systemd[2578]: Closed GnuPG cryptographic agent and passphrase cache.
2024-10-31T13:32:23-04:00 desktop systemd[2578]: Closed PipeWire PulseAudio.
2024-10-31T13:32:23-04:00 desktop systemd[2578]: Closed PipeWire Multimedia System Sockets.
2024-10-31T13:32:23-04:00 desktop dbus-broker[2617]: Dispatched 458 messages @ 1(±2)μs / message.
2024-10-31T13:32:23-04:00 desktop systemd[2578]: Stopping D-Bus User Message Bus...
2024-10-31T13:32:23-04:00 desktop systemd[2578]: Stopped D-Bus User Message Bus.
2024-10-31T13:32:23-04:00 desktop systemd[2578]: Removed slice User Core Session Slice.
2024-10-31T13:32:23-04:00 desktop systemd[2578]: Closed D-Bus User Message Bus Socket.
2024-10-31T13:32:23-04:00 desktop systemd[2578]: Removed slice User Application Slice.
2024-10-31T13:32:23-04:00 desktop systemd[2578]: app.slice: Consumed 766ms CPU time, 119M memory peak.
2024-10-31T13:32:23-04:00 desktop systemd[2578]: Reached target Shutdown.
2024-10-31T13:32:23-04:00 desktop systemd[2578]: Finished Exit the Session.
2024-10-31T13:32:23-04:00 desktop systemd[2578]: Reached target Exit the Session.
2024-10-31T13:32:23-04:00 desktop systemd[1]<EMAIL_ADDRESS>Deactivated successfully.
2024-10-31T13:32:23-04:00 desktop systemd[1]: Stopped User Manager for UID 1000.
2024-10-31T13:32:23-04:00 desktop systemd[1]<EMAIL_ADDRESS>Consumed 927ms CPU time, 127.3M memory peak, 69.9K incoming IP traffic, 48.6K outgoing IP traffic.
2024-10-31T13:32:23-04:00 desktop systemd[1]: Stopping User Runtime Directory /run/user/1000...
2024-10-31T13:32:23-04:00 desktop systemd[1]: run-user-1000.mount: Deactivated successfully.
2024-10-31T13:32:23-04:00 desktop systemd[1]<EMAIL_ADDRESS>Deactivated successfully.
2024-10-31T13:32:23-04:00 desktop systemd[1]: Stopped User Runtime Directory /run/user/1000.
2024-10-31T13:32:23-04:00 desktop systemd-logind[858]: Removed session 4.
2024-10-31T13:32:42-04:00 desktop systemd[1]: systemd-localed.service: Deactivated successfully.

Should be fixed in https://github.com/lilyinstarlight/nixos-cosmic/commit/95ce80ae072d1ce2ff8919fce2e4a50dd94e68ef. I'll be able to test and confirm myself later today

And yeah, entirely unrelated to #453, that one is a graphics driver error :)

Yes! 95ce80ae072d1ce2ff8919fce2e4a50dd94e68ef works!
Thank you very much!


Setting the @Id field by hand makes @InheritanceType("SINGLE_COLLECTION") not set @DiscriminatorField into document automatically

Test case 1: http://pastie.org/private/o3corybxeqsdyagkxklbq
Test case 2: http://pastie.org/private/nas7gbfqlwngko7d8zbea
When setting the Id column by hand makes ODM not set the DiscriminatorField on persist() / flush()

would love do donate a few beers / bucks do whoever fixes this issue :)

Made the following patch http://pastie.org/private/woagrfgsxrmtew26ze6yw
looks like it uses prepareUpsertData when I set the ID by hand rather than prepareInsertData, tthat normally sets the Discriminator field last in the method in lib/Doctrine/ODM/MongoDB/Persisters/PersistenceBuilder.php

Thanks, this is fixed now https://github.com/doctrine/mongodb-odm/commit/02b01da6bd7460bc2e046f0a3f73ffe8a5824471

@Jippi could you please send Pull Request with your test to mongodb-odm repository, instead of simple public them at pastie.
PS There is awesome paste service called Gist http://gist.github.com/


Remove dead code of "xwalk_core_unittests_apk"

The "xwalk_core_unittests" and "xwalk_core_unittests_apk" are totally
dead code, There is 'java_in_dir': 'test/android/unittestjava' in this
target,but we cannot find it in xwalk src project. Those targets are
not referenced at all.

@rakuco  @lincsoon  Thanks.

Please add [Android] in the commit title.
Should runtime/common/android/xwalk_core_tests.cc also be removed concurrently?

@wuhengzhi, Thanks for reminder,  runtime/common/android/xwalk_core_tests.cc should be removed too.

@wuhengzhi  @rakuco   PR updated.

LGTM, thanks.

@rakuco  please help to merge this, then I'll abandon the test/android/BUILD.gn  int the GN-android patch too.

will do; I'm finishing setting up the new Android GN bots first.


Incompatible with Dart2?

This sounded like a great library, but did not work here. I'm on Dart 2.0.0-dev.61.0, trying to use logging_service in AngularDart 5.0.0-alpha+13 and I got this exception in Chome:
Error compiling dartdevc module:logging_service|lib/configure_logging_for_browser.ddc.js

[error] The argument type '(Level) → String' can't be assigned to the parameter type '(dynamic) → dynamic'. (package:logging_service/configure_logging_for_browser.dart, line 93, col 64)
[error] The argument type '(Level) → Level' can't be assigned to the parameter type '(dynamic) → dynamic'. (package:logging_service/configure_logging_for_browser.dart, line 93, col 94)

Please fix all errors before compiling (warnings are okay).

I fixed the above error with this PR
However, now we get a Cannot read property 'error' of undefined here https://github.com/wrike/logging_service/blob/master/lib/src/js_console_proxy.dart#L21
So, dart.global.loggingServiceOriginalConsoleMethods must be undefined. I'm assuming this is also Dart 2 related?

I updated the PR, now it works for me.

Sorry it seems Travis didn't like it. Don't have time to fix it for all Dart versions atm, unfortunately.

Fixed with https://github.com/wrike/logging_service/pull/9/files


Update windows-in-place-upgrade.md

Added an important dialogue box regarding the image plan information not being updated post performing the In-place upgrade.

@ju-shim
Can you review the proposed changes?
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@Court72 - I added a suggestion. Are you able to apply that change and then merge this PR? Thank you.


improve conditional_dispatcher

Codecov Report

Merging #87 (a31db44) into master (4998449) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##            master       #87   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           19        19
  Lines         1555      1563    +8
=========================================
+ Hits          1555      1563    +8

Impacted Files
Coverage Δ

triad/utils/dispatcher.py
100.00% <100.00%> (ø)

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 4998449...a31db44. Read the comment docs.


Quick Actions Plugin Rendering Greyed Icons

Quick Action is rendering Drawables properly in one build type when released to the play store, but fails to render when building in type release to the play store.
The build was generated for both using
flutter build appbundle --no-shrink
Build Type: Profile

Build Type: Release

The Drawables are generated by Vector Assets for all - build types.
keep.xml is generated and resource is added to style.xml as well.
The issue is not present when running
flutter run --release

Please help me understand why this is happening.
Any help is appreciated. Thanks!

Plugin used quick_actions:1.0.0

Hi @vjk10
Did you check this note? https://pub.dev/packages/quick_actions#android

If the drawables used as icons are not referenced other than in your Dart code, you may need to explicitly mark them to be kept to ensure that they will be available for use in release builds.

Hey @huycozy ,
Yes it was done. And this was only happening in the app bundle uploaded to the play store and only for the release variant. When uploading an app bundle with the profile variant everything works fine.

Hi @vjk10
I saw your comment in #51455, it looks like you tried all workarounds there (https://github.com/flutter/flutter/issues/51455#issuecomment-593152837 and https://github.com/flutter/flutter/issues/51455#issuecomment-649388878), right?
Also, did you try building to appbundle and installing it with bundletool to see if the issue can reproduce locally? And which build command have you used?
Please provide a completed and minimal reproducible code sample so that we may verify this. Also, please provide the output of flutter doctor -v as well.
Thank you!

The issue started appearing after I created multiple build types. I was able to resolve this by clearing shortcuts and re-initializing them. Thanks for the time.


VG::distance_to_tail can't work, breaks softclips

While investigating some bad mappings in the graph bake-off, I noticed that end softclip handling wasn't always running when it should be. I think I traced the problem to an error in converting some functions to support oriented nodes.
Softclip handling depends on VG::distance_to_tail, which is supposed to tell you how far your node is from the tail of the graph. If a read dangles off a node that isn't anywhere near the tail of the graph, softclip handling shouldn't happen there.
It looks like the function is trying to take an arbitrary edge from the node given, towards the edge of the graph, and when it gets to a tail or hits its limit in bases, it will stop. However, it's calling VG::sides_from on a node ID, and that function is now only defined on a NodeSide. There's a constructor to build a NodeSide from a node ID, which implicitly creates the start side of the node. So we're looking for edges off the start side of this node, when I think the function means to be looking for edges off the end side of the node.
Really, the function ought to take in an oriented node (NodeTraversal) and keep going right to abritrary nodes with next_nodes(). If we can guarantee we only use the function on ordered and oriented alignment graphs, though, it might be possible to keep it as is and just use the correct side.
The other problem with the function is that if it hits its length limit exactly, but hasn't reached the end, it will return the length limit instead of the special -1 value. The limit is easy to hit right now if you have a length-1 node last, because it will look for a place to go, not find one (since it's looking off the start instead of the end), and visit the same node again.
The final problem is that if it does return its -1 value, I think the softclip code will take -1 as meaning the tail is closer than the ending softclip distance and run the softclip code anyway.

It doesn't help that the reported distances to tails are actually calculated with the distance_to_head function, unlike the ones actually used for decision-making.

Looks bad. Sorry about this. I guess it proves that it's not done until
it's tested.
On Feb 4, 2016 11:18 PM, "adamnovak"<EMAIL_ADDRESS>wrote:

It doesn't help that the reported distances to tails
https://github.com/ekg/vg/blob/master/src/mapper.cpp#L1152 are actually
calculated with the distance_to_head function, unlike the ones actually
used for decision-making.
—
Reply to this email directly or view it on GitHub
https://github.com/ekg/vg/issues/192#issuecomment-180098267.

I can take this on as soon as I finish unroll, which should be soon. In the
meantime patches are welcome.

I'm going to guess that this is a large part of the problem with alignment against graphs. Perhaps related to https://github.com/ekg/vg/issues/173.
@adamnovak have you hacked on this, or should I dig in?

I haven't tried to fix this at all yet; for the bake-off I think we're
going to try just throwing out the read alignments that look obviously like
bad soft clips, and eat the hit to variant calling power.
-Adam
On Sun, Feb 7, 2016 at 7:23 AM, Erik Garrison<EMAIL_ADDRESS>wrote:

I'm going to guess that this is a large part of the problem with alignment
against graphs. Perhaps related to #173
https://github.com/ekg/vg/issues/173.
@adamnovak https://github.com/adamnovak have you hacked on this, or
should I dig in?
—
Reply to this email directly or view it on GitHub
https://github.com/ekg/vg/issues/192#issuecomment-181031852.

It sounds reasonably easy to fix. We might be seeing an artifact of it
elsewhere. I'll look into it today.
On Feb 8, 2016 3:06 AM, "adamnovak"<EMAIL_ADDRESS>wrote:

I haven't tried to fix this at all yet; for the bake-off I think we're
going to try just throwing out the read alignments that look obviously like
bad soft clips, and eat the hit to variant calling power.
-Adam
On Sun, Feb 7, 2016 at 7:23 AM, Erik Garrison<EMAIL_ADDRESS>wrote:

I'm going to guess that this is a large part of the problem with
alignment
against graphs. Perhaps related to #173
https://github.com/ekg/vg/issues/173.
@adamnovak https://github.com/adamnovak have you hacked on this, or
should I dig in?
—
Reply to this email directly or view it on GitHub
https://github.com/ekg/vg/issues/192#issuecomment-181031852.

—
Reply to this email directly or view it on GitHub
https://github.com/ekg/vg/issues/192#issuecomment-181175716.


--init flag

Might be useful to have an initialization flag that, when present, initializes a configuration file in the current working directory with, perhaps, an interactive walk-through with questions that the user can answer to setup directories to watch and commands to execute.
Also might be a bit overkill, though, which is why I've marked this as enhancement and not feature.

Even better is to have this as a single flag mode that makes it more like other tools, e.g.
stickybeak init

Closed by PR #30


Add FreeBSD support

This add FreeBSD support. The only disadvantage is that the sensu package needs to be installed manually or be available in a private repo (since the sensu package is not available via the official FreeBSD pkg sources)

The travis builds seems to be failing because of the changes to handler.pp. This will probably be "fixed" by adding
let(:facts) { { :osfamily => 'RedHat' } }
to sensu_handler_spec.rb
This is already done to sensu_check_spec.rb - probably to have the build pass on Windows?


Add macOS support

Solves #10 .

Ok, looks fine.  Will merge after confirmation that your local testing is working on Macos.

Thanks, and please also check on linux to make sure it won't break anything.

Tested on Ubuntu 24, working fine.  Merging.


Update of Dynatrace OneAgent Bosh Release

Update of repository location.
Version bump of the release.

superseded by #38
Creating version 1.0.2 should totally work now ;)

merged #38.


UI issues with keypad elements

Your recent fix for UI issues has improved things but as you can see from the screenshots it’s still an issue.
This shows when entering the setting keypad numbers and also the alarm keypad numbers .

No they appear perfectly fine. The screenshots are the only UI issues I’ve come across

Ok, I will try to make the dialogs the same size as the alarm options menu to see if that helps.  Ideally I wanted a layout just for your device but it appears I can't determine the specific DPI (screen density) of your particular model.   I have the resolution but DPI determines the actual layout values and icon sizes. From just resolution alone, your device would be the same as a Pixel 2 XL or a Nexus 10 Tablet.  However, these do not have the same issue as your device.

This isn’t a cut off issue but more a UI inconstancy but would it make sense for the disabled state to show an unlocked padlock as opposed to a locked one?

Now you are scope creeping.   It might make sense but then I would have to pullout my secret ninja photoshop skills.   I would consider that a feature request :).

No problems.

Ok, you have your own beta program now.  I added a beta version of the Alarm Control panel with new layouts for 640dpi and 720 dpi devices for you to test.  This way I don't accidentally disrupt those with working layouts.
Here is the link to join the beta program: https://play.google.com/apps/testing/com.thanksmister.iot.mqtt.alarmpanel.
It may take a while for the beta to be available through Google Play

One out of two ain’t bad.

Oops...

Downloaded and tested, all looking good now. Tested in landscape and portrait. Happy to close this issue.

Great, yes close the issue and I will roll out the beta after I test this on my own tablets.


Warn when using -fobjc-arc without -use-arc. fixes #195

@advayDev1  done

done

done

done

LGTM - merging in now

One last thing - please squash the commits

@brunobowden It is still only one commit.

Might have just needed a browser refresh on my end. In any case, merging now...


Update Important note

Issue in ./help/tags/extensions/client/media-analytics-3x/overview.md
Please update the Important note on this page to read:
This extension deploys with Media 3.x SDK, which is not backward compatible with Media 2.x SDK. Because Media 2.x. SDK is deprecated, please update to Media 3.x SDK.

Thank you for submitting this issue. We will review the documentation and make the necessary updates as quickly as possible. Tracking internally in PLAT-140476.

We've updated the documentation accordingly. Closing this issue.


Fix: additional check to determine whether source file exists or not

This PR adds additional check to determine if the asset exists in the source site or not.
Right now, in some of the pages if the asset is not present and we try to transform the page, the process just stops without throwing an error. This is also quite an edge case, but would be good to have this check in place so that the transformation doesn't stop.

Thanks @gautamdsheth . The more robust and reliable we can make page transformation the better and that's only possible by also handling the edge cases. Will ensure this one get's processed before the next release.


Apache Storm #610

Deploy preview for landscape ready!
Built with commit 3e4d6209b81f1869d91b1842f8a3cd56042f3f43
https://deploy-preview-613--landscape.netlify.com


[GH-234] Added fast get_block_by_height to Chain

Added refs for n-th prev blocks for n beeing a power of 2
Refactored Chain.Worker
Added function to get block by height using the refs

Work-In-Progress

this seems to add a lot of complexity to existing code, what do we need block_by_height for at all?

It can be used for block sync so it can be done from bottom to the top. (This has several advantages.)
I also used that in my Voting implementation to reference old balances of accounts.
As for the complexity: a lot of changes are refactoring and aside from those I add one calculation code to add_validated_block and the block_by_height function.

Okay, we will refactor the sync to do headers first, so we solve this problem in the future.

Ok, so we might close this for now and only merge if it will be useful in the future.

Okay, lets try to optimize this PR and then merge it. We can include an endpoint for the explorer. But I think the best approach to get block by height is to keep an index %{height => hash}

@thepiwo The problem is how will we be able to distinguish between forks?
I did following changes:

wrap chainstates and blocks in one (unnamed) structure - block_info, this way asociating new data with block is easy and we have only one map.
add the refs table to every block. This table contains hashes of prev_block, 2nd prev, 4th prev, 8th prev and so on... (for every n-th such that n is a power of 2)
using the refs we can easily traverse chain backwards. (this is what the get_block_info_by_height does) Let's say the top block of the longest chain (or of the fork we would like to traverse) has height 11011011 (represented in binary). And we would like to get the block with height 10010101. To do that we do the following:

get 2nd prev of top block, we get block with height 11011001
get 4th prev of block with height 11011001, we get a block with height 11010101
get 64th prev of block with height 11010101, we get the target block with height 10010101
One can easily see we will do at most log2 (n) steps. So this is very fast :)

What one could argue is that we could recalculate the %{height => hash} map every time some forking happens, but this solution is more stable and can explore forks without any problems.

(This solution works for any tree and can be for example used to calculate Lowest Common Ancestor - that is the place when the chain forked. The reason I coded this solution is that it was known to me previously, It's also available in detail on Wikipedia, but for some reason only on polish version of the article, English version contains other solutions.)

is it necessary to use :array erlang-style functions?

I propose to merge this as it is soon, but we should remove the chain_state at hash functions and only keep snapshots, e.g. each 10000 blocks to ease recalculation when forking

is it necessary to use :array erlang-style functions?

I can use Enum.get and lists. In theory that will be slower, becouse it requires going through the whole list (of 30 elements so that's not much) and arrays are constant time access.
I suppose the price for this simplification is low so I will change that.

As for the snapshots: that would be out of scope of this PR. I can work on that, but that's a separate change.

yes sure, snapshot will be a separate task

@thepiwo It should be ready now. Because I wanted to save the refs in Rox and load them on start, I added a new rox "family" that can be used also for storing headers. Separating headers from blocks and loading them on start should be simple now and should only require changes to Aecore.Chain.Worker.
I also experienced problems with loading Persistance data on start. I have to call Kernel.send(Process.whereis(Aecore.Chain.Worker),:timeout) to get the data loaded. I will investigate.

wait for #263 to merge

@cytadela8 ready to merge?

@thepiwo Ready for merge. I changed few things in the way blocks are removed from memory and how such blocks are handled later so:

there shouldn't be any errors when invoking any functions on removed blocks
it works now as I intended.

Let me go through the changes again and fix some small mistakes made in merging.

feel free to merge, whenever


jake --always-make

GNU make has
 -B, --always-make
      Unconditionally make all targets.

Basically, it builds without checking a file modification date which is useful when not all dependencies are specified. Would be nice to have the same for Jake.

I would also love this. It was the first thing I looked for when transitioning from make to jake.
For many release managers they just want to force all tasks to run before pushing to prod.

That's what I get for being lazy, and not writing a always-make task for those preexisting files. :) This is fixed in 47491fc376c661314182af3f96747959af5eee86 Let me know if it's kosher.

That's what I get for being lazy, and not writing a always-make task for those preexisting files. :) This is fixed in 47491fc376c661314182af3f96747959af5eee86 Let me know if it's kosher.

Let me know if this isn't working.

Seems to work well. Thanks!

Tested working well for me, too.

Thanks. :)


Ignoring folders defined in .gitignore

Is it possible to ignore files/folders defined in a .gitignore? I tried searching if this is already supported or already asked but it doesn't seem to be the case.
ctags already supports something similar with the<EMAIL_ADDRESS>pattern.

There's no feature in Gutentags to do this per se (most of my projects ignore files that I do want to include in tags generation), but if there's some argument you can pass to ctags to make it do what you want, you can look at either a .gutctags file in your project root to pass project-specific ctags parameters, or a global g:gutentags_ctags_extra_args (which sadly isn't documented yet, I'll fix that).

Thanks @ludovicchabant.
I did not look at .gutctags or g:gutentags_ctags_extra_args. I will look at the argument more closely. Although ctags itself doesn't have a feature to ignore files found in .gitignore: https://github.com/universal-ctags/ctags/issues/218
I was able to find the following solution however:
let g:gutentags_file_list_command = 'rg --files'

which works very well.

Cool, thanks for the tip!

If you want to check if rg is available to make it portable, here you go:
if executable('rg')
  let g:gutentags_file_list_command = 'rg --files'
endif

For people who do not use ag, I use this config :
let g:gutentags_file_list_command = {
      \ 'markers': {
      \ '.git': '{ git ls-files; git ls-files --others --exclude-standard; }',
      \ },
      \ }

It allows having :

git tracked files
git untracked files with .gitignore files/dirs excluded


Replace ComponentTip.razor with MudTooltip

Will need to use both ComponentTip.razor and MudTooltip depending on component and context. Bring look and feel of ComponentTip.razor in line with MudTooltip.


Don't apply the refactoring tool when there are no hints

I noticed that automatic refactorings with refactor would even change files for which hlint reported no hints.
This can be observed for example with trailing whitespace which refactor will remove.
I think that mostly for performance reasons it would be better if the application of the refactoring tool would be skipped entirely in such cases.

This bug report probably belongs with the refactor tool at https://github.com/mpickering/apply-refact

I'd prefer if the refactoring would be skipped for any refactoring tool. So I think it would be nice if hlint's behavior could be changed here.
I'll try to make a PR if you agree.

My worry is that if people abuse the refactoring tool for other reasons, e.g. reports, context sensitive markup etc then it won't work if we skip empty files. That said, I don't think anyone has actually done that, so I'm on the fence.

I think this was resolved by #685

Thanks @mitchellwrosen! :+1:


file extension

Hello.
I download skewer-0.2.2-linux-x86_64 file on (https://sourceforge.net/projects/skewer/). I'm not sure of what type of file it is. Could you let me know the extension of this file like .gz, .tar, .zip?
Thank you in advance!

I found skewer-0.2.2-linux-x86_64 is an executable file itself!


List view pattern

Can be converted from angular-patternfly to patternfly-ng.
Angular-patternfly implementation:
http://www.patternfly.org/angular-patternfly/#/api/patternfly.views.component:pfListView

Closing due to inactivity.


Disable tests on most of platforms

@zachjs tests for macOS are there, but just for macOS-11 with c++11 only, so one test run for Linux and one for macOS. macOS-10.5 is maybe not even needed but it is good to check compilation on older OS, and for it tests are fully disabled

@mmicko Ah, I misread. That makes sense to me!


How to add label on sections

How to add label on sections for speedometer.

Hi @maliatli,
Have you read about Ticks and custom tick label? Or maybe Notes? You may find what you are looking for there.
Please explain more if that wasn't what you want.


Fix Number() inconsistency with String(), add better error handling, make String() better handle integers

Number() was not accepting strings created by String() if they are more than 15 characters. This made it impossible to load results from previous calculations. Moreover, Number() was not handling error cases correctly because of its use of atof.
The solution is to remove length limitation and to use strtod function which provides better error handling.
String() was printing decimal point even for exact integer values. This change makes it better handle exact integer values up to 53 bits in size ( -9007199254740991 <= |value| <=<PHONE_NUMBER>740991)
Test program:
c1 =<PHONE_NUMBER>99999
for i = 1 to 13 {
	c1 *=<PHONE_NUMBER>99999
}

s = string(c1)
? "c1 = " + s
c2 = number(s)
? "c2 = " + c2

? "c2 - c1 = " + (c2 - c1)

str1 = "-2222044646462"
c = Number(str1)
str2 = String (c)

if str1 = str2 {
	? "Strings identical"

else
	? "Strings mismatch!!"
}

Thanks for the update
Keep up the GREAT WORK


trufflehog: 3.54.1 -> 3.54.3

Changelog: https://github.com/trufflesecurity/trufflehog/releases/tag/v3.54.3
Description of changes

Things done

Built on platform(s)

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

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 252935 run on x86_64-linux 1

1 package built:

trufflehog


Automapper equivalent to "As"

Hi,
Thanks for your work on this amazing lib :)
I just moved all my project from AutoMapper to Mapster, now I've got small issues.
I would like to know if there is some kind of alternative for .As<TObject>() in AutoMapper
https://docs.automapper.org/en/stable/Mapping-inheritance.html?highlight=.As<#as
I'm using it this way on automapper

Here is an object that is

I'm mapping from my Database Entities to my GameObjects but it's used as DTOs.
This is the mapping Configuration I was trying to get working as I expected

Here goes the error

Here is the mapping code
Basically, I would like to override the destination type to the GameObject (which always inherits from the DTO)

Thanks by advance !

What you did is correct, Mapster doesn't provide method equivalent to As.
If you use ConstructUsing, You can just create target instance.
TypeAdapterConfig<Recipe, RecipeDTO>.NewConfig()
    .ConstructUsing(s => new Game.Recipe());

Hope this help.

Going to take a look tomorrow if I have time :)

Please also try Include.
TypeAdapterConfig<Recipe, RecipeDTO>.NewConfig().Include<Recipe, Game.Recipe>();

only using ConstructUsing didn't work, going to check with include :+1:

Using .Include<Recipe, Game.Recipe>(); does not work too

Strangely, this work in the following unit tests
[Fact]
        public void Check_Map_To_ChildClass()
        {
            MappingInitializer.InitializeMapping();
            short recipeId = 1;
            MapsterMapper<Recipe, RecipeDTO> mapper = new MapsterMapper<Recipe, RecipeDTO>();

            Check.That(mapper.MapToDto(new Recipe { RecipeId = recipeId }, out RecipeDTO dto)).IsTrue();

            var recipe = (WingsEmu.Game.Recipe)dto;

            Check.That(dto).IsInstanceOf<WingsEmu.Game.Recipe>();
            Check.That(dto.RecipeId).IsEqualTo(recipeId);
        }

        [Fact]
        public void Check_Map_To_ChildClasses()
        {
            MappingInitializer.InitializeMapping();
            short recipeId = 1;
            MapsterMapper<Recipe, RecipeDTO> mapper = new MapsterMapper<Recipe, RecipeDTO>();

            List<Recipe> list = new List<Recipe>
            {
                new Recipe { RecipeId = recipeId }, new Recipe { RecipeId = recipeId }
            };
            Check.That(mapper.MapToDtos(list, out IEnumerable<RecipeDTO> dtos)).IsTrue();

            foreach (RecipeDTO dto in dtos)
            {
                var obj = (WingsEmu.Game.Recipe)dto;
                Check.That(dto).IsInstanceOf<WingsEmu.Game.Recipe>();
                Check.That(dto.RecipeId).IsEqualTo(recipeId);
            }
        }

xUnit, NFluent

Fixed, I got some forgotten configuration on IoC :(


Setting seed does not make mock data generation deterministic in case of pydantic factory

Setting the random seed on a pydantic factory does not make it deterministic. When running below code we see different records being generated.
from random import Random
from polyfactory.factories.pydantic_factory import ModelFactory
from pydantic import BaseModel, constr, condate
import datetime
from typing import Any

class Person(BaseModel):
    name: str
    date_of_birth: condate(ge=datetime.date(1900, 1, 1), lt=datetime.date.today())

class Factory(ModelFactory[Any]):
    __model__ = Person
    __random_seed__ = 42
    _random__ = Random(42)

for i in range(10):
    print(Factory.build())

Funding

If you would like to see an issue prioritized, make a pledge towards it!
We receive the pledge once the issue is completed & verified

Please show me the output of two runs of the test. The test in the example doesn't demonstrate the issue

You are right, it has to be ran twice. The issue occurs with constrained string (so not normal string as above, my mistake)
A bit better test case:
from random import Random
from polyfactory.factories.pydantic_factory import ModelFactory
from pydantic import BaseModel, constr, condate
import datetime
from typing import Any

class Person(BaseModel):
    name: constr(max_length=24)
    date_of_birth: condate(ge=datetime.date(1900, 1, 1), lt=datetime.date.today())

def generate_examples(n=10):

    class Factory(ModelFactory[Any]):
        __model__ = Person
        __random_seed__ = 42
        _random__ = Random(42)

    examples = []
    for i in range(n):
        examples.append(Factory.build())
    return examples

Now below will return False
examples = generate_examples()
repeated_examples = generate_examples()
assert examples == repeated_examples

`


Engine roll caused failures in "Linux framework_tests_misc"

The Engine roll here https://github.com/flutter/flutter/pull/96244 caused failures in Linux framework_tests_misc with logs here:
https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8825733661309369041/+/u/run_test.dart_for_framework_tests_shard_and_subshard_misc/test_stdout
Engine roll reverted here: https://github.com/flutter/flutter/pull/96259
Speculative revert of the Dart roll in the Engine roll: https://github.com/flutter/engine/pull/30729

The commits in the Dart roll are here https://dart.googlesource.com/sdk.git/+log/f59531cc2973..5f2c54513b7d

The Engine roll is green on the Framework tree following the Dart SDK revert.

The failing tests are in the dev/devicelab suite in the framework tree.  I tried running these tests on a LUCI bot and noticed that they failed repeatedly due to a race in the tests and the devicelab framework.
The devicelab framework has a runProcessCleanup flow that queries for Dart processes on the system before and after running the devicelab test.  If a process exists after the task completes but not before it started, then it is assumed to be a leak and is then killed:
https://github.com/flutter/flutter/blob/master/dev/devicelab/lib/framework/framework.dart#L182
However, multiple tests may be running concurrently in the test harness, and some the dev/devicelab tests spawn tasks that do runProcessCleanup.  If one test checks for leaked processes it may see Dart processes that were spawned by another test and kill them, causing the other test to fail.
I did not notice any correlation between these failures and the version of the Dart SDK.  But it's possible that a Dart roll altered the timing of test execution and made this race more likely to fail.
It might make sense to disable the process leak detector by default and enable it only in scenarios where the user knows that only one devicelab process will be running.
@CaseyHillers @jonahwilliams

/cc @christopherfujino @godofredoc

Also @dnfield (from https://github.com/flutter/flutter/pull/29196)

runProcessCleanup was never intended to be used when concurrent tests are running on the same hardware - it's meant to be a generic check that a test does not leave running dart processes spawned. However, IIRC it never quite did everything we really needed and we still ended up configuring LUCI to just kill stray processes on test exit.

Related: https://github.com/flutter/flutter/pull/96320 /cc @Hixie

I'm trying to verify a fix locally

https://github.com/flutter/flutter/pull/96320 fixes run_test.dart which used to terminate dart processes even during unit tests (the other unit tests already disabled this).

yup, https://github.com/flutter/flutter/pull/96320 looks like it will resolve this

#96320 has landed.

Thanks! I'm going to start bringing in small manual Dart rolls.

The rolls are moving again.


Add floating toolbar display mode option

Summary of changes:
This commit introduces a new display mode option for the ChatGPT extension, allowing users to choose between a sidebar and a floating toolbar. The changes span across three files, implementing the new feature and updating the configuration options.
Key changes:

In src/config/index.mjs:

Added a new DisplayMode object with two options: sidebar and floating toolbar.
Updated the defaultConfig object to include a displayMode property.

In src/content-script/index.jsx:

Implemented logic to render either the existing sidebar or the new floating toolbar based on the user's display mode preference.
Added code to create and position the floating toolbar container.

In src/popup/sections/GeneralPart.jsx:

Added a new dropdown menu in the extension's settings to allow users to select their preferred display mode.

Overall, this commit enhances the extension's flexibility by giving users the option to choose how they want the ChatGPT interface to be displayed on web pages.

Made some improvements, changed to a switch option, and made the effect comply with the user's trigger mode settings.


Multiple gem servers

We use multiple gem sources in a single gemfile. It would be nice to point to gemstash and it will pull from all of them.

:+1:

I think that it is by definition a priority based linear system, that is, as you said, try the first, if it’s not there, try the second, and so on
also think that we should have as many storage folders as upstream servers
so, we should first go through all the storage, and if we don’t find it, then we should cache it back
simply:
storages.each { return gem if i_have_this_gem }
upstream_servers.each { cache_and_return if it_has_this_gem }
both storages and upstream servers are priority based lists, and the upstream knows which storage to use to do the caching, probably because we need to build the “http client” for the caching itself

So, we just to define our upstream servers in order of priority (most important first) and then we can just figure out the caching and fetching strategy from there.

This is a good idea! Rather than putting the cache for every server in one place, let's separate caches on a per-server basis. Bundler was originally built with multiple servers and "order of priority", and it turned out so terribly that we had to issue a CVE: http://bundler.io/blog/2014/08/14/bundler-may-install-gems-from-a-different-source-than-expected-cve-2013-0334.html
I think a way to make this work that is straightforward is to add a configuration file that allows mapping gemstash URLs to specific servers. For example:
# config.yml
gem_servers:
  gemfury: https://gemfury.io

Then, source "https://gemstash.local/gemfury" or bundle config mirror.https://gemfury.io https://gemstash.local/gemfury ensures that gemstash can be used as a passthrough cache for the Gemfury source.

@indirect I like that! So would that source then only bundle against the gemfury upstream?
One thing I would like in a Gemfile we use is to have the gemstash server deal with all upstreams for us. We ran into some strange issues with bundler when trying to bundle against a couple of upstreams... we got some gem not found errors that we didn't expect and had to hack around it to get the gems (heh, probably should have opened a ticket on that, sorry!).
After reading the CVE, it looks like a priority system is a bad idea, and it should instead error out if you try to get a gem that exists on multiple upstreams. Maybe something like this:
# config.yml
gem_servers:
  gemfury: https://gemfury.io
  rubygems: https://www.rubygems.org

Then, if you try to make an api call against gemstash and the gem exists on multiple of the upstreams (if you use https://gemstash.local rather than a scoped upstream like https://gemstash.local/gemfury), it will error out, and to resolve it you must either append something on the url like https://gemstash.local?rubygems=rake,rack&gemfury=sinatra or add configuration like:
# config.yml
gem_servers:
  gemfury: https://gemfury.io
  rubygems: https://www.rubygems.org
gem_resolutions:
  rubygems:
  - rake
  - rack
  gemfury:
  - sinatra

I presume we must have the gem fully hosted from one upstream too... so if I have some versions of rack on 2 different upstreams, it can only ever install rack from one of the upstreams, so it would be an error regardless of if the version needed is hosted on one and not the other (otherwise that seems like it would be a security vulnerability).
There's a weird scenario though... what if I install rack when only 1 upstream has the gem, then I bundle on a new machine... but at this point, another upstream has rack. Should gemstash be calling out to the various upstreams and see if it exists on more than one upstream? I'm thinking, once it is cached, it should just fetch from there with no web calls, and it seems like a reasonable and secure way of doing it... then when I bundle update, I would get the error about multiple sources for the gem.
Thoughts?

I really like the idea of multiple endpoints and explicit resolutions for specific gems.
I'm guessing that the main use case for multiple upstream servers is having the ability to mix those servers for different purposes, for ex: using the pro version of sidekiq, which is provided with a gem server for that specific gem.
Is this a valid use case for multiple upstream servers?
If so, having the mapping for specific gems makes a lot of sense. This mapping configurations could also be provided by whoever is serving this to simplify the setup. We could even handle auth tokens in the same configuration file with this approach. Maybe something like:
# config.yml
upstream-servers:
  gemfury:
    url: https://gemfury.io
    auth-token: xxxxx
    gems:
      - sinatra
  rubygems:
    url: https://www.rubygems.org
    gems:
      - rake
      - rack
    default-upstream: true
  sidekiq:
    url: https://sidekiq.org
    auth-token: yyyyy
    gems:
      - sidekiq

With this we could support mirroring an upstream server to a specific path, as you propose @indirect, also we could set up mixed servers in the default endpoint for specific gems.
Regarding having the gem cached, I think we should just serve it without making any further calls. The upstream servers should only be used to fetch those gems initially, but once they are cached, they should be served from the local storage.
This also matches in behavior with the idea of privately hosted gems: if we have the gem, we just serve it.
Regarding having multiple upstream sources for the same gem, is there a way of getting a hash of the gem (etags maybe?) to check if they are the same?
This could be a simple way of resolving the conflict: request the header of all the upstreams that have the gem, and compare the etags, if we find a difference  we could only trust the authoritative source (rubygems) or force this conflict resolution into the user. Finally, on download, check the hash just to be sure.

So, good news! The mapping for specific gems is already taken care of by Bundler, in the Gemfile, via source blocks. That means that gemstash only needs to be able to provide the gems that Bundler asks for, and everything will work correctly.
After some further conversation about this feature at ROSSConf, I think it would probably be even better to add header-based source selection: that is, cache gems on a per-source basis, but select the source based on a header sent by Bundler. That way there doesn't need to be a gemstash configuration file, but gems also don't get mixed together.
Here's what I mean:
# Gemfile
source "https://rubygems.org"
gem "rack"
source<EMAIL_ADDRESS>do
  gem "secret"
end

$ bundle config mirror.https://rubygems.org https://gemstash.local
$ bundle config mirror.https://gemfury.io https://gemstash.local
$ bundle install

During that bundle install is where the interesting stuff happens: Bundler uses the same URL both times, but when requesting indexes for rubygems.org, sends a request like this:
GET https://gemstash.local/
X-Gemfile-Source: https://rubygems.org

Then, while requesting indexes from the gemfury.io source, the request looks like this:
GET https://gemstash.local/
X-Gemfile-Source: https://gemfury.io

Then gemstash is able to use the combination of X-Gemfile-Source, username, and password to know which directory to use as the cache. I think a directory naming scheme like this would be good:
remote_data = [gemfile_source, username, password].join("")
hash = Digest::MD5(remote_data)
directory = "#{uri.host}-#{hash}"

That way the cache directories have names like rubygems.org-abc123cde456, which are both perfectly unique but also human-readable.

I love this idea. Totally zeroconf from the server point of view.
Is this implemented in bundler already?

The X-Gemfile-Source header is not implemented yet, but you can definitely work on gemstash as if it is implemented—adding it should not take long.

Could a source block indicate it is mirroring to automatically send the header? Like maybe:
source "https://gemstash.local", mirroring: "https://rubygems.org"

source "https://gemstash.local", mirroring: "https://gemfury.io" do
  # ...
end

Thus avoiding external bundler config? In my use case, we are going to have all bundles going through gemstash, so it would be neat to not have an external config to see where the mirrors are pointing at.

Or alternatively
source "https://rubygems.org", mirror: "https://gemstash.local"

source "https://gemfury.io", mirror: "https://gemstash.local" do
  # ...
end

Hmmmm... I didn't think about the case where you control both the Gemfile and the gemstash and you want to always use it. :) I was thinking of the cases where you're working with shared or open source repos, and so the mirror config is only used on your own machine.
In the case where you control the Gemfile, I think it probably makes sense to add something like a mirror: option. That could even allow fallback if the mirror is down...

Then there are 2 ways of configuring this: in your local bundler config by setting the mirror for a given url, and in the gem itself at the level of a set of gems or the whole source.
In both cases, gemstash should be smart enough to capture the auth setup for the upstream server so it is forwarded, and then we need to keep gems separated and just return them if all the settings (name, auth, etc) are the same, enabling caching private gems this way.
We need a smarter fetcher and smarter gem naming in the storage.

After thinking about this some more, I think I would prefer to not offer a mirror option in the Gemfile, simply because having two ways to do the same thing offers a chance for conflicts and confusion.
@smellsblue how do you feel about simply adding a bundle config mirror command to your project's bin/setup script instead of putting it in the Gemfile? Or you could even do bundle config --global in the machine configuration scripts to change it for the entire machine, instead of just for a single project.

@indirect we have a far from normal Rails project unfortunately... it's a Java project with Rails tacked on with JRuby. We could probably get by with something like bin/setup, but our setup is not quite as straightforward across all environments.
My fear with putting it in Bundler config separate from the Gemfile is that a new developer (or one who isn't really familiar with our Rails side of things) might see the Gemfile and not understand where the gems are coming from, which might lead to confusion if something goes wrong like the Gemstash server being unreachable for some reason. I would vastly prefer the Gemfile directly point to Gemstash. However, I think we already have the answer to this without needing the mirror option. We can go back to your original idea:
source "https://gemstash.local/rubygems"

source "https://gemstash.local/gemfury" do
  # ...
end

This adds configuration requirements back to Gemstash, but I think that might be fine. We can support header based upstream selection as well as URL based upstream selection, and the user can pick whichever works best for them :-)
Thoughts?

I just had another idea... we could do something like this:
source "https://gemstash.local?upstream=https://rubygems.org"

source "https://gemstash.local?upstream=https://gemfury.io" do
  # ...
end

This could function exactly like the header, removing config requirement for Gemstash, yet still dropping the config from Bundler.
Hmmm.... except I suppose that would break how Bundler needs to invoke the server (unless Bundler will preserve parameters like when making calls to things like /api/v1/dependencies).... if params aren't preserved, this might be better:
source "https://gemstash.local/upstream/https://rubygems.org"

source "https://gemstash.local/upstream/https://gemfury.io" do
  # ...
end

What I like is that there is no change in behavior from the gemstash point of view, just different ways of setting where the gem comes from.
We can start with the simplest one and then build from there.
Which one could be? What is bundler supporting right now?

With the caveat that the URL needs to be escaped, https://gemstash.local/upstream/https%3A%2F%2Frubygems.org/ seems fine to me as well. :+1:

@indirect How do you feel about querystring parameters?

The backend needs to be url-escaped either way, and I'm worried that the query string parameter would interfere with urls on the backend, so I think making it a subdirectory is more likely to work.

This is done


Validate rego when parsing rule types

Summary
This adds rego module parsing as part of the rule type validation. This
enables us to catch errors faster as opposed to needing to evaluate a
policy to figure out if the rule type was valid.
If we have a rule with invalid rego, we'd get errors as follows:
$ mindev ruletype lint -r rule-types/github/no_binaries_in_repo.yaml
error validating rule type from file rule-types/github/no_binaries_in_repo.yaml: invalid rule type
invalid rule type definition: rego definition is invalid: 1 error occurred: minder-ruletype-def.rego:16: rego_parse_error: unexpected eof token
	  msg := sprintf("Binary artifact found: %s", [current_file])
	                                                            ^
Error: failed linting rule type
Message: Error on execute
Details: failed linting rule type

Change Type
Mark the type of change your PR introduces:

[x] Bug fix (resolves an issue without affecting existing features)
[x] Feature (adds new functionality without breaking changes)
[ ] Breaking change (may impact existing functionalities or require documentation updates)
[ ] Documentation (updates or additions to documentation)
[ ] Refactoring or test improvements (no bug fixes or new functionality)

Testing
Outline how the changes were tested, including steps to reproduce and any relevant configurations.
Attach screenshots if helpful.
Review Checklist:

[x] Reviewed my own code for quality and clarity.
[ ] Added comments to complex or tricky code sections.
[ ] Updated any affected documentation.
[ ] Included tests that validate the fix or feature.
[ ] Checked that related changes are merged.

coverage: 54.763%. remained the same
when pulling e31bd807047925b8b1c3675ac09b3a2d3578f36b on JAORMX:rego-validate
into ebc9be89e185768106304ba4834a4f59263b7920 on mindersec:main.


Overcoat 4.0

[x] Add CI support f32b881 6f68148
[x] Use AFNetworking 3.x 94dbd0b

[x] Drop support of NSURLConnection 94dbd0b

[x] Drop support of Mantle 1.x 3138846
[x] Support to ReactiveCocoa 3.x/4.x #110
[x] Support to Bolts Tasks (Move to 4.1 or future)
[x] Split PromiseKit and ReactiveCocoa support to another framework/podspec
[x] Carthage Support #95 4b7a5c2
[x] Model request serializer #83 (Move to 4.1 or future)
[x] Response Class Matcher for same URL but different HTTP methods #64 f4e82e6
[ ] Rewrite documentation

:+1:

Mantle 1.x dropped by 3d30c83

Updates sound awesome! Can't wait.

The first beta 4.0.0-beta.1 is available in CocoaPods and has a git tag for Carthage now.
Please test it :)
and Happy Holidays. (So if there are some issues in the beta, I may fix it after the holidays. But still, you're welcome to submit PRs for it)

@sodastsai Happy holidays! :)


Loot Esp Not Working

Hello i'm using 3.6.1 and the loot Esp doesn't show the items, i've tried using no mods, putting all possible names for the item, when i put "tracklist" it shows is looking for my wishlist tracked items, all loot options are enabled but nothing happens and have this error on console
[Exception] : NullReferenceException: Object reference not set to an instance of an object
EFT.Trainer.Features.LootItems.FindItemsInContainers (EFT.GameWorld world, System.Collections.Generic.List1[T] records) (at <1b4003a3e7fc405aa87bec9c929f23f2>:0) EFT.Trainer.Features.LootItems.RefreshData () (at <1b4003a3e7fc405aa87bec9c929f23f2>:0) EFT.Trainer.Features.CachableFeature1+d__6[T].MoveNext () (at <1b4003a3e7fc405aa87bec9c929f23f2>:0)
UnityEngine.SetupCoroutine.InvokeMoveNext (System.Collections.IEnumerator enumerator, System.IntPtr returnValueAddress) (at <85d1d3e7744a4a47b5f51883bf40bba2>:0)
UnityEngine.DebugLogHandler:LogException(Exception, Object)
Class312:UnityEngine.ILogHandler.LogException(Exception, Object)
UnityEngine.MonoBehaviour:StartCoroutine(IEnumerator)
EFT.Trainer.Features.d__6:MoveNext()
UnityEngine.SetupCoroutine:InvokeMoveNext(IEnumerator, IntPtr)

Please upgrade to 3.7.0 as it is now available. We do not support anything except the current release of SPT-AKI. You could try building from branch dev-<IP_ADDRESS>06 but beyond that I'd just upgrade to the latest release as the trainer works with that version.

it was build in  Try #1 Compilation succeed for dev-<IP_ADDRESS>06 branch.


aligned_alloc: memcpy the pointer to the full allocation, not the first bytes of the allocation

Merged, thanks.


Patch 1

I'm going to change the characters to be more efficient.

² and ³ each take 2 bytes, and ∑ uses 3 bytes .-.

Ok, I added a character table to use for our own character encoding.


Fix knight number placement

There was no bounds check on the knight setup code, which meant that knights near the board edge were causing tiles to be incorrectly marked. This can be seen in the top right tile of this game:

I've added this bounds check, as well as slightly reducing the repetition in the relevant code.

Never mind, just noticed that you did the same thing a few minutes ago 😆


Wrong orientation in Android

Hi, it seems as with Android the exif orientation tag is not recognized and some images have wrong orientation. In addition when saving images as blob exif data will not be kept.
Any idea to solve this issue?

@domax Hi, may you have a look on the orientation tag with Android?

Duplicates #7