text:
Calling warpd from terminal makes some delay

Every time want to call this command from the terminal warpd --click 1 --query < hints there will be a few moments delay.
Can call query like speed activated mode?
One more question
Can after pressing the button on the query not quit from query mode?
Example:
I want stay in query mode and I create a script like this
warpd --click 1 --query < hints ; sleep 0.1 ; warpd --click 1 --query < hints ; sleep 0.1 ; warpd --click 1 --query < hints ; sleep 0.1 ; warpd --click 1 --query < hints
yes 4 times because I do not want to quit from query mode, is there a better way to do it?

my problem is if use history, sometimes the history on coordinate is gone, and I must click again for saved history

I try with this command, but just show hints a

What platform are you using? (wayland/X/macos). Are you using the latest version? What is the output of warpd -v?

What platform are you using? (wayland/X/macos). Are you using the latest version? What is the output of warpd -v?

I'm using Manjaro latest with X and  warpd v1.3.5 (built from: 5d27d1c)
if call warpd script on terminal take 2 seconds to show hint

How big is your hint file, can you post it?

How big is your hint file, can you post it?

not too much, just this

Why was the issue closed?

Sorry, I accidentally must have clicked closed instead of comment. In general the X implementation is a bit slow and relies on the daemon for caching which means non-daemon options like --query will incur the initialization overhead. I will investigate when I have some time and see if/what optimizations are possible

Sorry, I accidentally must have clicked 'close issue' instead of comment. In general the X implementation is a bit slow and relies on the daemon for caching which means non-daemon options like --query will incur the initialization overhead. I will investigate when I have some time and see if/what optimizations are possible. In the meantime try setting a border radius of 0 (if it isn't already), since that incurs the greatest overhead on X.

thank you for your concern about this matter.

I just tried this is and it seems to be nearly instantaneous on my machine. Can you post your config? What desktop environment are you using? Are you using a compositor like compton?

I just tried this is and it seems to be nearly instantaneous on my machine. Can you post your config? What desktop environment are you using? Are you using a compositor like compton?

After telling you  machine then I tried to use i3 for testing and  warpd no problem,
I just heard about this compton, I don't think I've ever installed it, but this my log on GNOME 43
[I]➜ journalctl --since "1 min ago" Nov 26 10:49:44 drm-workstation geoclue[21073]: Service not used for 60 seconds. Shutting down.. Nov 26 10:49:44 drm-workstation systemd[1]: geoclue.service: Deactivated successfully. Nov 26 10:49:44 drm-workstation audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=geoclue comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Nov 26 10:49:44 drm-workstation kernel: audit: type=1131 audit(1669434584.103:521): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=geoclue comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Nov 26 10:49:59 drm-workstation dbus-daemon[21361]: [session uid=1000 pid=21361] Activating via systemd: service name='org.gtk.vfs.Metadata' unit='gvfs-metadata.service' requested by ':1.21' (uid=1000 pid=21733 comm="/usr/bin/gnome-she> Nov 26 10:49:59 drm-workstation systemd[21331]: Starting Virtual filesystem metadata service... Nov 26 10:49:59 drm-workstation dbus-daemon[21361]: [session uid=1000 pid=21361] Successfully activated service 'org.gtk.vfs.Metadata' Nov 26 10:49:59 drm-workstation systemd[21331]: Started Virtual filesystem metadata service. Nov 26 10:50:02 drm-workstation gnome-shell[21733]: [INFO   ][Another window session manager] Session saved to /tmp/another-window-session-manager/sessions/currentSession/kitty/0x500000e.json! Nov 26 10:50:02 drm-workstation dbus-daemon[817]: [system] Activating via systemd: service name='org.freedesktop.locale1' unit='dbus-org.freedesktop.locale1.service' requested by ':1.295' (uid=1000 pid=22156 comm="/usr/bin/gnome-softwa> Nov 26 10:50:02 drm-workstation audit: BPF prog-id=68 op=LOAD Nov 26 10:50:02 drm-workstation audit: BPF prog-id=69 op=LOAD Nov 26 10:50:02 drm-workstation audit: BPF prog-id=70 op=LOAD Nov 26 10:50:02 drm-workstation systemd[1]: Starting Locale Service... Nov 26 10:50:02 drm-workstation kernel: audit: type=1334 audit(1669434602.107:522): prog-id=68 op=LOAD Nov 26 10:50:02 drm-workstation kernel: audit: type=1334 audit(1669434602.107:523): prog-id=69 op=LOAD Nov 26 10:50:02 drm-workstation kernel: audit: type=1334 audit(1669434602.107:524): prog-id=70 op=LOAD Nov 26 10:50:02 drm-workstation gnome-shell[21733]: [INFO   ][Another window session manager] Session saved to /tmp/another-window-session-manager/sessions/currentSession/kitty/0x500000e.json! Nov 26 10:50:02 drm-workstation dbus-daemon[817]: [system] Successfully activated service 'org.freedesktop.locale1' Nov 26 10:50:02 drm-workstation systemd[1]: Started Locale Service. Nov 26 10:50:02 drm-workstation audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-localed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Nov 26 10:50:02 drm-workstation kernel: audit: type=1130 audit(1669434602.183:525): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-localed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=suc> Nov 26 10:50:14 drm-workstation gnome-shell[21733]: [INFO   ][Another window session manager] Session saved to /tmp/another-window-session-manager/sessions/currentSession/kitty/0x500000e.json! Nov 26 10:50:14 drm-workstation gnome-shell[21733]: [INFO   ][Another window session manager] Session saved to /tmp/another-window-session-manager/sessions/currentSession/kitty/0x500000e.json! Nov 26 10:50:14 drm-workstation gnome-shell[21733]: [INFO   ][Another window session manager] Session saved to /tmp/another-window-session-manager/sessions/currentSession/kitty/0x500000e.json! Nov 26 10:50:14 drm-workstation gnome-shell[21733]: [INFO   ][Another window session manager] Session saved to /tmp/another-window-session-manager/sessions/currentSession/kitty/0x500000e.json! Nov 26 10:50:31 drm-workstation systemd[21331]: Started Application launched by gsd-media-keys. Nov 26 10:50:31 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x5200001.json not found while restoring! Nov 26 10:50:31 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x5200002.json not found while restoring! Nov 26 10:50:31 drm-workstation gnome-shell[21733]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). Nov 26 10:50:31 drm-workstation gnome-shell[21733]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). Nov 26 10:50:31 drm-workstation gnome-shell[21733]: Window manager warning: Overwriting existing binding of keysym ff54 with keysym ff54 (keycode 74). Nov 26 10:50:31 drm-workstation gnome-shell[21733]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). Nov 26 10:50:31 drm-workstation gnome-shell[21733]: Window manager warning: Overwriting existing binding of keysym ff52 with keysym ff52 (keycode 6f). Nov 26 10:50:31 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x5200003.json not found while restoring! Nov 26 10:50:31 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x5200004.json not found while restoring! Nov 26 10:50:31 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x5200005.json not found while restoring! Nov 26 10:50:31 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x5200006.json not found while restoring! Nov 26 10:50:31 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x5200007.json not found while restoring! Nov 26 10:50:31 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x5200008.json not found while restoring! Nov 26 10:50:31 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x5200009.json not found while restoring! Nov 26 10:50:31 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x520000a.json not found while restoring! Nov 26 10:50:31 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x520000b.json not found while restoring! Nov 26 10:50:31 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x520000c.json not found while restoring! Nov 26 10:50:31 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x520000d.json not found while restoring! Nov 26 10:50:31 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x520000e.json not found while restoring! Nov 26 10:50:31 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x520000f.json not found while restoring! Nov 26 10:50:31 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x5200010.json not found while restoring! Nov 26 10:50:31 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x5200011.json not found while restoring! Nov 26 10:50:31 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x5200012.json not found while restoring! Nov 26 10:50:31 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x5200013.json not found while restoring! Nov 26 10:50:31 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x5200014.json not found while restoring! Nov 26 10:50:31 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x5200015.json not found while restoring! Nov 26 10:50:31 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x5200016.json not found while restoring! Nov 26 10:50:31 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x5200017.json not found while restoring! Nov 26 10:50:31 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x5200018.json not found while restoring! Nov 26 10:50:31 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x5200019.json not found while restoring! Nov 26 10:50:31 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x520001a.json not found while restoring! Nov 26 10:50:31 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x520001b.json not found while restoring! Nov 26 10:50:31 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x520001c.json not found while restoring! Nov 26 10:50:32 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x520001d.json not found while restoring! Nov 26 10:50:32 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x520001e.json not found while restoring! Nov 26 10:50:32 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x520001f.json not found while restoring! Nov 26 10:50:32 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x5200020.json not found while restoring! Nov 26 10:50:32 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x5200021.json not found while restoring! Nov 26 10:50:32 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x5200022.json not found while restoring! Nov 26 10:50:32 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x5200023.json not found while restoring! Nov 26 10:50:32 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x5200024.json not found while restoring! Nov 26 10:50:32 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x5200025.json not found while restoring! Nov 26 10:50:32 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x5200026.json not found while restoring! Nov 26 10:50:32 drm-workstation systemd[1]: systemd-localed.service: Deactivated successfully. Nov 26 10:50:32 drm-workstation audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-localed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Nov 26 10:50:32 drm-workstation kernel: audit: type=1131 audit(1669434632.217:526): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-localed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=suc> Nov 26 10:50:32 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x5200027.json not found while restoring! Nov 26 10:50:32 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x5200028.json not found while restoring! Nov 26 10:50:32 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x5200029.json not found while restoring! Nov 26 10:50:32 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x520002a.json not found while restoring! Nov 26 10:50:32 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x520002b.json not found while restoring! Nov 26 10:50:32 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x520002c.json not found while restoring! Nov 26 10:50:32 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x520002d.json not found while restoring! Nov 26 10:50:32 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x520002e.json not found while restoring! Nov 26 10:50:32 drm-workstation audit: BPF prog-id=0 op=UNLOAD Nov 26 10:50:32 drm-workstation audit: BPF prog-id=0 op=UNLOAD Nov 26 10:50:32 drm-workstation audit: BPF prog-id=0 op=UNLOAD Nov 26 10:50:32 drm-workstation kernel: audit: type=1334 audit(1669434632.350:527): prog-id=0 op=UNLOAD Nov 26 10:50:32 drm-workstation kernel: audit: type=1334 audit(1669434632.350:528): prog-id=0 op=UNLOAD Nov 26 10:50:32 drm-workstation kernel: audit: type=1334 audit(1669434632.350:529): prog-id=0 op=UNLOAD Nov 26 10:50:32 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x520002f.json not found while restoring! Nov 26 10:50:32 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x5200030.json not found while restoring! Nov 26 10:50:32 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x5200031.json not found while restoring! Nov 26 10:50:32 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x5200032.json not found while restoring! Nov 26 10:50:32 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x5200033.json not found while restoring! Nov 26 10:50:32 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x5200034.json not found while restoring! Nov 26 10:50:32 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x5200035.json not found while restoring! Nov 26 10:50:32 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x5200036.json not found while restoring! Nov 26 10:50:32 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x5200037.json not found while restoring! Nov 26 10:50:32 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x5200038.json not found while restoring! Nov 26 10:50:32 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x5200039.json not found while restoring! Nov 26 10:50:32 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x520003a.json not found while restoring! Nov 26 10:50:32 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x520003b.json not found while restoring! Nov 26 10:50:32 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x520003c.json not found while restoring! Nov 26 10:50:32 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x520003d.json not found while restoring! Nov 26 10:50:32 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x520003e.json not found while restoring! Nov 26 10:50:32 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x520003f.json not found while restoring! Nov 26 10:50:32 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x5200040.json not found while restoring! Nov 26 10:50:32 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x5200041.json not found while restoring! Nov 26 10:50:32 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x5200042.json not found while restoring! Nov 26 10:50:34 drm-workstation sh[25068]: 1728 972 Nov 26 10:50:34 drm-workstation gnome-shell[21733]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). Nov 26 10:50:34 drm-workstation gnome-shell[21733]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). Nov 26 10:50:34 drm-workstation gnome-shell[21733]: Window manager warning: Overwriting existing binding of keysym ff54 with keysym ff54 (keycode 74). Nov 26 10:50:34 drm-workstation gnome-shell[21733]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). Nov 26 10:50:34 drm-workstation gnome-shell[21733]: Window manager warning: Overwriting existing binding of keysym ff52 with keysym ff52 (keycode 6f). Nov 26 10:50:35 drm-workstation systemd[21331]: Started Application launched by gsd-media-keys. Nov 26 10:50:35 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x5200001.json not found while restoring! Nov 26 10:50:35 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x5200002.json not found while restoring! Nov 26 10:50:35 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x5200003.json not found while restoring! Nov 26 10:50:35 drm-workstation gnome-shell[21733]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). Nov 26 10:50:35 drm-workstation gnome-shell[21733]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). Nov 26 10:50:35 drm-workstation gnome-shell[21733]: Window manager warning: Overwriting existing binding of keysym ff54 with keysym ff54 (keycode 74). Nov 26 10:50:35 drm-workstation gnome-shell[21733]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). Nov 26 10:50:35 drm-workstation gnome-shell[21733]: Window manager warning: Overwriting existing binding of keysym ff52 with keysym ff52 (keycode 6f). Nov 26 10:50:35 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x5200004.json not found while restoring! Nov 26 10:50:35 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x5200005.json not found while restoring! Nov 26 10:50:35 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x5200006.json not found while restoring! Nov 26 10:50:35 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x5200007.json not found while restoring! Nov 26 10:50:35 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x5200008.json not found while restoring! Nov 26 10:50:35 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x5200009.json not found while restoring! Nov 26 10:50:35 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x520000a.json not found while restoring! Nov 26 10:50:35 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x520000b.json not found while restoring! Nov 26 10:50:35 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x520000c.json not found while restoring! Nov 26 10:50:35 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x520000d.json not found while restoring! Nov 26 10:50:35 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x520000e.json not found while restoring! Nov 26 10:50:35 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x520000f.json not found while restoring! Nov 26 10:50:35 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x5200010.json not found while restoring! Nov 26 10:50:35 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x5200011.json not found while restoring! Nov 26 10:50:35 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x5200012.json not found while restoring! Nov 26 10:50:35 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x5200013.json not found while restoring! Nov 26 10:50:35 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x5200014.json not found while restoring! Nov 26 10:50:35 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x5200015.json not found while restoring! Nov 26 10:50:35 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x5200016.json not found while restoring! Nov 26 10:50:35 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x5200017.json not found while restoring! Nov 26 10:50:35 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x5200018.json not found while restoring! Nov 26 10:50:35 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x5200019.json not found while restoring! Nov 26 10:50:35 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x520001a.json not found while restoring! Nov 26 10:50:35 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x520001b.json not found while restoring! Nov 26 10:50:35 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x520001c.json not found while restoring! Nov 26 10:50:35 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x520001d.json not found while restoring! Nov 26 10:50:35 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x520001e.json not found while restoring! Nov 26 10:50:35 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x520001f.json not found while restoring! Nov 26 10:50:36 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x5200020.json not found while restoring! Nov 26 10:50:36 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x5200021.json not found while restoring! Nov 26 10:50:36 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x5200022.json not found while restoring! Nov 26 10:50:36 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x5200023.json not found while restoring! Nov 26 10:50:36 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x5200024.json not found while restoring! Nov 26 10:50:36 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x5200025.json not found while restoring! Nov 26 10:50:36 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x5200026.json not found while restoring! Nov 26 10:50:36 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x5200027.json not found while restoring! Nov 26 10:50:36 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x5200028.json not found while restoring! Nov 26 10:50:36 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x5200029.json not found while restoring! Nov 26 10:50:36 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x520002a.json not found while restoring! Nov 26 10:50:36 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x520002b.json not found while restoring! Nov 26 10:50:36 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x520002c.json not found while restoring! Nov 26 10:50:36 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x520002d.json not found while restoring! Nov 26 10:50:36 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x520002e.json not found while restoring! Nov 26 10:50:36 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x520002f.json not found while restoring! Nov 26 10:50:36 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x5200030.json not found while restoring! Nov 26 10:50:36 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x5200031.json not found while restoring! Nov 26 10:50:36 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x5200032.json not found while restoring! Nov 26 10:50:36 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x5200033.json not found while restoring! Nov 26 10:50:36 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x5200034.json not found while restoring! Nov 26 10:50:36 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x5200035.json not found while restoring! Nov 26 10:50:36 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x5200036.json not found while restoring! Nov 26 10:50:36 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x5200037.json not found while restoring! Nov 26 10:50:36 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x5200038.json not found while restoring! Nov 26 10:50:36 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x5200039.json not found while restoring! Nov 26 10:50:36 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x520003a.json not found while restoring! Nov 26 10:50:36 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x520003b.json not found while restoring! Nov 26 10:50:36 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x520003c.json not found while restoring! Nov 26 10:50:36 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x520003d.json not found while restoring! Nov 26 10:50:36 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x520003e.json not found while restoring! Nov 26 10:50:36 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x520003f.json not found while restoring! Nov 26 10:50:36 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x5200040.json not found while restoring! Nov 26 10:50:36 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x5200041.json not found while restoring! Nov 26 10:50:36 drm-workstation gnome-shell[21733]: [WARNING][Another window session manager] /tmp/another-window-session-manager/sessions/currentSession/warpd/0x5200042.json not found while restoring! Nov 26 10:50:37 drm-workstation sh[25087]: 1728 972 Nov 26 10:50:37 drm-workstation gnome-shell[21733]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). Nov 26 10:50:37 drm-workstation gnome-shell[21733]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). Nov 26 10:50:37 drm-workstation gnome-shell[21733]: Window manager warning: Overwriting existing binding of keysym ff54 with keysym ff54 (keycode 74). Nov 26 10:50:37 drm-workstation gnome-shell[21733]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). Nov 26 10:50:37 drm-workstation gnome-shell[21733]: Window manager warning: Overwriting existing binding of keysym ff52 with keysym ff52 (keycode 6f).

warpd query getting better after turn off extension Gnome "Another Window Session Manager"

authors: ajfpay rvaiya

repo: rvaiya/warpd


text:
Background class hard coded

Hi,
I am evaluating my dataset which has 2 classes on efficientdet-d0 based on Pascal metrics
I see while the mode.eval() mode, the test loss is increasing crazy. Also, there is a Warning: WARNING: image 0 does not have groundtruth difficult flag specified.
Is it something to do with not providing the background class while loading the groundtruth annotations into the model?
Also, I cannot make out why the tp_fp_labels always False and 0 which gives 0 mAP.
Any leads appreciated
TIA

0 is always the background class for class targets output from the dataset.
You can ignore that warning, I haven't supported passing difficult flag for Pascal and group_of flag for OpenImages to the evaluator, so detections marked as difficult or group_of won't be treated differently for eval.
As for what's wrong, I don't have any insight. Every dataset is different and there's lots of room to get something not quite right.

@rwightman,
That's a very good point and insight.
Some writers/authors say while converting the class label(target class
names) to the class_id(integers), to mention the first class as 0 while
some say to mention background as 0.
On Mon, Oct 26, 2020, 11:28 PM Ross Wightman notifications@github.com
wrote:

0 is always the background class for class targets output from the dataset.
You can ignore that warning, I haven't supported passing difficult flag
for Pascal and group_of flag for OpenImages to the evaluator, so detections
marked as difficult or group_of won't be treated differently for eval.
As for what's wrong, I don't have any insight. Every dataset is different
and there's lots of room to get something not quite right.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/rwightman/efficientdet-pytorch/issues/107#issuecomment-717016326,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMQBWSNP4TAC3CI2UZXXMDLSMZR7PANCNFSM4S77LKIQ
.

@rwightman, since I was getting the mAP 0 every time, and due to the
different author's I was confused with the first class_id hard coded as 0
or not.
Also, I really understand background class is 0.
Thanks
On Tue, Oct 27, 2020, 2:49 AM Ekta Bhojwani ebhojwani246@gmail.com wrote:

@rwightman,
That's a very good point and insight.
Some writers/authors say while converting the class label(target class
names) to the class_id(integers), to mention the first class as 0 while
some say to mention background as 0.
On Mon, Oct 26, 2020, 11:28 PM Ross Wightman notifications@github.com
wrote:

0 is always the background class for class targets output from the
dataset.
You can ignore that warning, I haven't supported passing difficult flag
for Pascal and group_of flag for OpenImages to the evaluator, so detections
marked as difficult or group_of won't be treated differently for eval.
As for what's wrong, I don't have any insight. Every dataset is different
and there's lots of room to get something not quite right.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/rwightman/efficientdet-pytorch/issues/107#issuecomment-717016326,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMQBWSNP4TAC3CI2UZXXMDLSMZR7PANCNFSM4S77LKIQ
.

that log is output every x % 1000 == 0 samples when the flags aren't set, has nothing to do with the class labels

source: gharchive/issue

repo: rwightman/efficientdet-pytorch

license_type: permissive

license_source: github-api


text:
Unable to build on Linux

The build process fails for me. Here's the captured output:
compiling (unix)...
src/main.c:2:10: fatal error: SDL2/SDL.h: No such file or directory
    2 | #include <SDL2/SDL.h>
      |          ^~~~~~~~~~~~
compilation terminated.
In file included from src/rencache.h:5,
                 from src/rencache.c:2:
src/renderer.h:4:10: fatal error: SDL2/SDL.h: No such file or directory
    4 | #include <SDL2/SDL.h>
      |          ^~~~~~~~~~~~
compilation terminated.
In file included from src/api/renderer.c:2:
src/renderer.h:4:10: fatal error: SDL2/SDL.h: No such file or directory
    4 | #include <SDL2/SDL.h>
      |          ^~~~~~~~~~~~
compilation terminated.
src/api/system.c:1:10: fatal error: SDL2/SDL.h: No such file or directory
    1 | #include <SDL2/SDL.h>
      |          ^~~~~~~~~~~~
compilation terminated.
In file included from src/api/renderer_font.c:2:
src/renderer.h:4:10: fatal error: SDL2/SDL.h: No such file or directory
    4 | #include <SDL2/SDL.h>
      |          ^~~~~~~~~~~~
compilation terminated.
In file included from src/renderer.c:6:
src/renderer.h:4:10: fatal error: SDL2/SDL.h: No such file or directory
    4 | #include <SDL2/SDL.h>
      |          ^~~~~~~~~~~~
compilation terminated.
cleaning up...
done

OS: Debian 11, Gnome 3.38.5
Lua: 5.4.3
Lite: 1.11

lite depends also on SDL2 C library and you need to install it, command lower should work(of course if SDL2 exists in repositories)
sudo apt-get install libsdl2-dev

That did it. Thanks again.

authors: AKonia Pound-Hash

repo: rxi/lite

license: MIT


text:
[Snyk] Security upgrade python from 3.9-slim to 3.12.0b1-slim

This PR was automatically created by Snyk using the credentials of a real user.Keeping your Docker base image up-to-date means you’ll benefit from security fixes in the latest version of your chosen image.
Changes included in this PR

cmd/suggestion/chocolate/v1beta1/Dockerfile

We recommend upgrading to python:3.12.0b1-slim, as this image has only 69 known vulnerabilities. To do this, merge this pull request, then verify your application still works as expected.
Some of the most important vulnerabilities in your base image include:

Severity
Priority Score / 1000
Issue
Exploit Maturity

150
Improper Verification of Cryptographic Signature SNYK-DEBIAN12-APT-1541449
No Known Exploit

150
Improper Input Validation SNYK-DEBIAN12-COREUTILS-1543939
No Known Exploit

150
Use of a Broken or Risky Cryptographic Algorithm SNYK-DEBIAN12-LIBGCRYPT20-1550206
No Known Exploit

150
Cryptographic Issues SNYK-DEBIAN12-OPENSSL-1555825
No Known Exploit

571
CVE-2023-45853 SNYK-DEBIAN12-ZLIB-6008963
No Known Exploit

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
🛠 Adjust project settings

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Use of a Broken or Risky Cryptographic Algorithm
🦉 Improper Input Validation

Pull Request Test Coverage Report for Build 6593010877

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 72.857%

Totals

Change from base Build 4411813555:
0.0%

Covered Lines:
3111

Relevant Lines:
4270

💛  - Coveralls

source: gharchive/pull-request

authors: coveralls ryan-ally

repo: ryan-ally/katib


text:
Why does this need to access ALL of my Sheets?

Please change the scope to https://www.googleapis.com/auth/spreadsheets.currentonly so that it only accesses the current Sheet. Best practices in programming is to limit the scope of such requests. thanks

@brandonfake69 great idea! These options were unfortunately not available when I built the application (you had not direct scope control back then).

@brandonfake69 Unfortunately I tried to make this change today, and it looks like it is no longer possible.
The link you sent is dead, and the new list of scopes no longer has an option for speadsheets.currentonly (https://developers.google.com/identity/protocols/oauth2/scopes#script). The only two available options are readonly and the scope the library currently uses. Unfortunately readonly cannot be used because this would not allow the library to be used with formulas while the sheet is closed (see #22).
I'm going to close this for now. Feel free to open it if you see a scope I missed. I'll keep an eye on the scopes in the future and update the library if they reinstate currentonly.

repo: ryan-d-williams/MMM-GoogleSheets


text:
Support for Nike+ GPS Watch ?

Hi,
I've got a Nike+ SportWatch GPS "Powered by TomTom" (http://www.tomtom.com/lib/doc/Nike-SportWatch-QuickStartGuide-EN.pdf), and would love to be able to grab the raw GPS datafiles from it (prior to them being munged by the Nike+ Fat client and uploaded to Nike+).
I was hoping that it would really be a "TomTom" watch - but it seems that this isn't the case, as with the watch connected to a Ubuntu 10.04 LTS box, I'm getting:
# ttwatch -a
Unable to open watch
Is there any chance that support could be added ?  I'm hoping it's "close enough" to being a TomTom watch :-)  I'm not much of a programmer, but am happy to help re USB sniffing etc.
This is how the device presents in my Mac (the output of system_profiler)
SportWatch:

  Product ID:   0x5455
  Vendor ID:    0x11ac
  Version:  2.00
  Serial Number:    105F94461E000B00
  Speed:    Up to 12 Mb/sec
  Manufacturer: Nike
  Location ID:  0xfa140000 / 8
  Current Available (mA):   500
  Current Required (mA):    500
  Capacity: 66 KB (66,048 bytes)
  Removable Media:  Yes
  Detachable Drive: Yes
  BSD Name: disk1
  Partition Map Type:   MBR (Master Boot Record)
  S.M.A.R.T. status:    Not Supported
  Volumes:
SportWatch:
  Capacity: 65 KB (65,024 bytes)
  Available:    62 KB (62,464 bytes)
  Writable: No
  File System:  MS-DOS FAT12
  BSD Name: disk1s1
  Mount Point:  /Volumes/SportWatch
  Content:  DOS_FAT_12
  Volume UUID:  F50B099E-1E3A-30BE-9AD7-474EBC44661B

Here's someones report (when they were playing around with this type of watch) for a University project:
https://www.os3.nl/_media/2013-2014/courses/ccf/smartwatches-hristo-leendert.pdf
With Thanks in Advance
Patrick Rynhart

Interesting. If you're feeling brave, you could edit libttwatch/libttwatch.h and change TOMTOM_VENDOR_ID and TOMTOM_MULTISPORT_PRODUCT_ID to the values of your Nike watch then recompile and try to use it. If you start with simple commands (like getting version information) then it shouldn't cause problems if it doesn't work exactly the same. From the document you linked to, it looks like it should work just fine, so you might be really lucky!

I tried this today and it seems not to work.
I executed ./ttwatch --version, but when send_packet(watch, MSG_UNKNOWN_0D, 0, 0, 20, 0) is called from ttwatch_send_startup_message_group, then libusb_interrupt_transfer(...) returns -1 (LIBUSB_ERROR_IO). I guess this means that the device is not supported? :-/

Yeah that's the same point that I got to also - in libttwatch.cpp, this line returns LIBUSB_ERROR_IO:
result = libusb_interrupt_transfer(watch->device, write_usb_endpoint, packet, packet_size, &count, 10000);

called for 09 02 00 0D (dumped using print_packet(packet, packet_size)).
My guess is that the watch is the "same", but the addresses for write and read usb_endpoint are different.  Not sure how to determine them - guess you would need to USB sniff the official Nike+ fat client....

USB endpoints are fairly easy to find. Run lsusb -v -d11ac and look at the output. Look for an Interface Descriptor with bInterfaceClass equal to 3 Human Interface Device. There should be two Endpoint Descriptors under that. The addresses are listed as bEndpointAddress for each one. Simply copy these values to the code. You can also check the required packet size for the OUT endpoint - the wMaxPacketSize parameter.
Or if you want to list the output of lsusb -v -d11ac I can tell you which numbers to use.

@ryanbinns I've tried a few things as suggested in the comments above, but failed to get it recognized with ttwatch.
Output from lsusb:
$ lsusb -v -d 11ac:5455

Bus 002 Device 005: ID 11ac:5455 Nike
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0
  bDeviceProtocol         0
  bMaxPacketSize0         8
  idVendor           0x11ac Nike
  idProduct          0x5455
  bcdDevice            2.00
  iManufacturer           1 Nike
  iProduct                2 SportWatch
  iSerial                 3 2FBE93462B001700
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           64
    bNumInterfaces          2
    bConfigurationValue     1
    iConfiguration          4 SportWatch
    bmAttributes         0x80
      (Bus Powered)
    MaxPower              500mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass         3 Human Interface Device
      bInterfaceSubClass      0 No Subclass
      bInterfaceProtocol      0 None
      iInterface              6 SportWatch HID
        HID Device Descriptor:
          bLength                 9
          bDescriptorType        33
          bcdHID               1.01
          bCountryCode            0 Not supported
          bNumDescriptors         1
          bDescriptorType        34 Report
          wDescriptorLength      36
          Report Descriptor: (length is 36)
            Item(Global): Usage Page, data= [ 0x00 0xff ] 65280
                            (null)
            Item(Local ): Usage, data= [ 0x01 ] 1
                            (null)
            Item(Main  ): Collection, data= [ 0x01 ] 1
                            Application
            Item(Global): Report ID, data= [ 0x01 ] 1
            Item(Global): Report Count, data= [ 0x3f ] 63
            Item(Global): Report Size, data= [ 0x08 ] 8
            Item(Global): Logical Maximum, data= [ 0x01 ] 1
            Item(Global): Logical Minimum, data= [ 0x01 ] 1
            Item(Local ): Usage, data= [ 0x01 ] 1
                            (null)
            Item(Main  ): Input, data= [ 0x02 ] 2
                            Data Variable Absolute No_Wrap Linear
                            Preferred_State No_Null_Position Non_Volatile Bitfield
            Item(Global): Report ID, data= [ 0x09 ] 9
            Item(Global): Report Count, data= [ 0x3f ] 63
            Item(Global): Report Size, data= [ 0x08 ] 8
            Item(Global): Logical Maximum, data= [ 0x01 ] 1
            Item(Global): Logical Minimum, data= [ 0x01 ] 1
            Item(Local ): Usage, data= [ 0x01 ] 1
                            (null)
            Item(Main  ): Output, data= [ 0x02 ] 2
                            Data Variable Absolute No_Wrap Linear
                            Preferred_State No_Null_Position Non_Volatile Bitfield
            Item(Main  ): End Collection, data=none
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               1
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x01  EP 1 OUT
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               1
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        1
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass         8 Mass Storage
      bInterfaceSubClass      6 SCSI
      bInterfaceProtocol     80 Bulk-Only
      iInterface              5 SportWatch Drive
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x82  EP 2 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               1
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               1
Device Status:     0x0000
  (Bus Powered)

It looks like it uses different endpoint addresses. I'm not sure if it will work, but you could try. Try replacing lines 225-238 of libttwatch.cpp with this:
write_usb_endpoint = 0x01;
read_usb_endpoint = 0x81;

Compile and try again. Don't do anything that writes to the watch though. Use -v to read version number to start with. If that works, you can be a little more adventurous, but still be careful at first.

Sadly, I tried that and it still couldn't detect it.

Hi Ryan (cc Alex)
Sorry for not replying - I did try a few things at the time, but got
stuck.  If I set up SSH access to the dev box I was using with the watch
plugged in, do you think you might be able to have a look ?  I'm not
running much at the moment :-)
Thanks,
Patrick
On 15/05/17 7:34 PM, Alex Williams wrote:

Sadly, I tried that and it still couldn't detect it.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ryanbinns/ttwatch/issues/72#issuecomment-301398776,
or mute the thread
https://github.com/notifications/unsubscribe-auth/APCDi-Qztzg0Q1D9S1mA9WyM6tlBZ-s9ks5r6AAjgaJpZM4H-stG.

I don't think I'd be able to do anything useful. I think to make any more progress, you'd need to capture the USB packets transmitted between the watch and the Windows software when the watch is plugged in and the software does its stuff.

Hi Ryan,
Apologies - I've been putting this off, because it sounded too difficult (and because I didn't have a bare-metal Windows box).  However, I've just had a go now, and it's much easier than I thought.
I have captured using the latest build of USBPcap (1.2.0.2) using the current version of the Nike Connect+ Software (Version 6.6.34.141).
I thought we would start with the simplest possible case:

All drivers installed along with the Fat Client
The watch plugged in and empty (i.e. no runs)
Start the PCAP packet trace
Open the Fat Client, wait for it to communicate with the device, then close the Fat Client
Stop the packet trace

I've done this, and the PCAP capture file is attached.  I've opened it okay in Wireshark and can see communication with the device.
Very happy to upload runs etc as needed (or to switch features on and off using the Fat Client under a packet trace).
Thanks again - and apologies for not following up sooner.
Patrick
NikeWatchWithoutRuns.zip

Oops - I did not mean to close this ticket :)

Hi.  Nike just announced they will be retiring the only applications that pull data off their watch by April 30, so I'm guessing this thread will receive more interest.

Yeah I know - amazing they can give less than 2 weeks notice on this - the link to the FAQ is https://en-gb-help.nike.com/app/answer/article/why-cant-i-sync/a_id/73653/country/nz

So, reading through the thread, it appears that you were able to capture some data, but that ryanbinns or someone else still needs some run data before being able to create a version of the software(s) that works with the Nike+ sportwatch?  Correct me if I misunderstand.

Unfortunately the strap on my Nike+ GPS Sportwatch broke very recently and it won't connect up to any of my computers (a common fault with these watches).  However, what you're saying above is correct - i.e. a patch needs to be created for the Nike version of this TomTom watch. Capturing the USB packets was straight forward on Windows (I followed the instructions at https://wiki.wireshark.org/CaptureSetup/USB) - so in theory anyone with a Windows box, the watch, and the Nike+ Connect Software (while it is still running) should be able to capture the protocol exchange between the client and the watch.

Ok.  I guess I better get on that then.  I assume I need to run a variety of use cases.  First I will try to capture watch connection with 1 run to transfer/upload.

I managed to capture a single run transfer.  I have never used wireshark before, so I suspect that the file may also contain traffic from other USB ports.  Any directions on how to remove information from the other ports?

The capture used the 64 bit version of wireshark with USBPcap included with the wireshark installation.  Easy enough to use once I got it installed correctly.  I suppose I should read the wireshark wiki on how to analyse the resultant file.

one run filtered for bus1 and device ID6.zip
Ok - I think I did that correctly - I did the capture and then created a new file filtered only for bus1 and device ID that correlated to the watch.  I noticed that the address seemed to change from 1.6.0 to 1.6.1 but that appears to be the correct data/traffic.

Nice work. Not sure what the next step would be though - need someone who can look at the comms in the packet capture and compare this with what’s happening in the source. Would be good to get something underway before the shutdown, but at least these captures are around while the Nike client is still working.
Other things that could be captured while the client still works (probably with the runs empty) would be the settings - e.g. comms when the colours are inverted, weight of runner, enable/disable beep. I.e. All the control / admin features if the watch. Maybe do a trace for one at a time (so as little is changing as possible).
Get Outlook for iOShttps://aka.ms/o0ukef

From: cgibson33 notifications@github.com
Sent: Saturday, April 21, 2018 12:56:40 PM
To: ryanbinns/ttwatch
Cc: Rynhart, Patrick; State change
Subject: Re: [ryanbinns/ttwatch] Support for Nike+ GPS Watch ? (#72)
one run filtered for bus1 and device ID6.ziphttps://github.com/ryanbinns/ttwatch/files/1934020/one.run.filtered.for.bus1.and.device.ID6.zip
Ok - I think I did that correctly - I did the capture and then created a new file filtered only for bus1 and device ID that correlated to the watch. I noticed that the address seemed to change from 1.6.0 to 1.6.1 but that appears to be the correct data/traffic.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHubhttps://github.com/ryanbinns/ttwatch/issues/72#issuecomment-383255579, or mute the threadhttps://github.com/notifications/unsubscribe-auth/APCDi_94PH8f6qzWL5uO2FMprVvryecBks5tqoPIgaJpZM4H-stG.

Will do.  Do you think it would be ok if I left the watch plugged in the whole time, but just recorded each action separately using different file names?
Also, I think there is a watch reset function that I should record because that might be the only way to clear the watch memory when it is getting full.

I think I should share my research notes.
All the relevant information can be filtered by entering usb.capdata into wireshark's display filter — it's a leftover capture data that we're interested in.
This leftover data is 64 bytes long. First byte is a direction (09 into watch, 01 from watch), second byte is a packet size, third one is just a counter. For the query that goes into watch, fourth byte is a command, next bytes are arguments. For the respond that we receive from watch fourth byte and next bytes are the reply data, last byte is some sort of check byte, it has to be the same as a counter byte.
The system nike client uses to download tracks is pretty dumb — it sends the '09 05 xx 10 00 00 00 ..' packet, the watch responds with a complete eeprom dump and the client is analyzing it afterwards.
Typical response is '01 3d xx 01 xx xx xx (significant_data_bytes) xx' when we still have data to receive and '01 (size_of_packet) xx 00 xx xx xx (significant_data_bytes) 00 .. 00 xx' when it is the last packet.
It seems that I have a corrupted watch, so I couldn't analyze what I am getting from the watch.

Ok - last minute I recorded a bunch of settings interactions including a factory reset
Documents.zip

When I did the settings changes, you could see packages transferring as soon as I typed any number or changed any setting on the fly, so I didn't bother removing the watch at any point

And Nike has checked out of the building - I assume that will get people's attention.

Ok - so now what?  Do I need to do some further analysis on the captures?  Is this watch too different than the other watches serviced by this code?

Hi guys, other solution would be to run a local proxy interpecting calls to Nike+ from the local app running and then store the data locally. But this is in case this project can't support the watch because as @prynhart  suggested would be very different to the 'other'
TomTom watches

Hi guys - unfortunately nothing to add, I don't know how different this watch is.  Hopefully someone else watching this thread can advise.  Thanks, Patrick

@iglezouton your suggested proxy solution doesn't work, because there are pre-flight validations on services that don't work anymore, even before the upload service is called.

@cgibson33 could you post your guide to watch the packets? I've tried USB Probe (mac only) and Wireshark with no luck.

The main problems I had with wireshark were just getting installed with USBPCap included - that can be accomplished just by selecting that option during install - assuming you have the version of wirecap with USBPCap and WinPCAP (gui) included.
Once installed, its easy: Just start capturing and then add display filters at the top using the expression button or autocomplete - at a minimum you will have to filter for Bus and device ID (use AND expression).  The PC seems to randomly assign ID numbers but I usually found the watch traffic on Bus 1 and ID 6, 7, or 8.  Wireshark will still be recording ALL USB traffic.  Once done, stop recording and save the file - you can re-filter it later at any time and then just save the filtered packets if you want.

Note that it is now impossible to record any actual communications for GPS updates or Run uploads since Nike has shut down the server - the only thing you can record is settings changes.

С мая 2018 года компания Nike прекратила поддержку Nike sportwatch gps описанный в вашей статье. Не удалось ли создать install программу ... с конвертацией в gpx?

Hi everybody,
is it possible, after uninstalling the Nike app, to use an "USB tool" to try to engage the watch and let it transfer the data? What tool should be used to try?

Maybe someone can figure it out?
https://www.os3.nl/_media/2013-2014/courses/ccf/smartwatches-hristo-leendert.pdf

The code posted here seems to be able to download binary data from the watch and parse it into XML.
There is also this project, but I'm not sure what are its capabilities.

authors: MauroMarini ViktorNest aw cgibson33 iglezouton internecivusraptus martinruenz prynhart rvernica ryanbinns slavutichd tomasdev

repo: ryanbinns/ttwatch

license: mit

license_source: bigquery


text:
[Bug]: Device is not auto selected when coming from interface page for assignment

NetBox access-list plugin version
1.0.0
NetBox version
3.2.7
Steps to Reproduce

Go to a device's interface page
Click on Add Access list
Notice that only interface is filled in the drop down

Expected Behavior
Both device and interface should be pre-filled
Observed Behavior
Only the interface is pre-filled

This is not technically a bug because nothing is broken per say.  The interface is all that maters for the assignment, but I get your point.
The current functionality filters the interface based on the device or vm.
I can look to have it do also set the device based on the interface you select, BUT I was reserving device and virtual_machine filtering on the ACL name and vice versa.  I thought it would be more helpful that if you selected the ACL, it would immediately filter popular the host the ACL is associated to OR if you selected the host it would filter the ACL.  It may be challenging to tackle all iterations.
Maybe if someone more seasoned than I with django or netbox plugins has a suggestion on the approach or a PR, I'd be super interested.
What are your thoughts @abhi1693

Honestly, all I was looking for the values to be displayed in the form. Sometimes people forget which interface they clicked and came from to be landed on the page. I believe this to be an easy fix to pass device_id= or virtual_machine_id= along with the current parameters and it will populate the fields. So far, I've not checked the code but I can in a few hours.

Yea agreed.  I should probably open a different issue to filter the host (vm or device) based on ACL, but its not so easy with Generic Foreign Keys.

repo: ryanmerolle/netbox-access-lists


text:
Fix broken headings in Markdown files

GitHub changed the way Markdown headings are parsed, so this change fixes it.
See bryant1410/readmesfix for more information.
Tackles bryant1410/readmesfix#1

Thanks for fixing this! Sorry it took so long to merge!

repo: ryantenney/metrics-spring


text:
Illegible colors for light themes

Theme Issue:

OS: Windows/Mac
Sublime Text version: 3109
Materialize version: Latest
Description of issue:
I am using the Material Solaried Light theme . I have noticed that the tab fore color and the selected file forecolor in the sidebar is white, which makes it ineligible to read the headings.
Steps to reproduce (if appropriate):

Change theme to Material Solarized Light
Open a few files in few tabs
Notice the color of the current file in the tab bar as well as the sidebar.

Screenshot of issue (if appropriate):

This is an issue that I'll have to fix for the older light themes (Solarized Light and Spacegray Light) as I didn't know much about theme customization back then. I believe Material Primer Light should be fine as I did that one pretty recently.

Yep, I just checked with the primer light and it does work well out of the box - Thanks for the information.

How do these look?
Solarized Light

Spacegray Light

I am liking what I am seeing. However , can you please add a bit more
contrast to the tabs which are not the current tab (for example - index.js
from your snapshots) ?. It would make for easier reading.
Thanks and Regards
Gagan

With Regards
Gagan Janjua
On Mon, Mar 21, 2016 at 10:09 AM, Saad Quadri notifications@github.com
wrote:

How do these look?
Solarized Light
[image: screen shot 2016-03-21 at 10 08 14 am]
https://cloud.githubusercontent.com/assets/5678694/13921166/f396b5c4-ef4c-11e5-807c-0c34a75801ca.png
Spacegray Light
[image: screen shot 2016-03-21 at 10 08 55 am]
https://cloud.githubusercontent.com/assets/5678694/13921176/fd0c1ffe-ef4c-11e5-9c49-96b274425668.png
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/saadq/Materialize/issues/55#issuecomment-199301102

What exactly do you mean by contrast? Are you asking to make the names less visible for the tabs that aren't the current one?

I was suggesting otherwise. I was asking if the names could be made more readable for the tabs that aren't the current one. Sorry for the confusion - that was my bad.
Thanks and Regards
Gagan

I've darkened the fonts for the unselected tabs, your themes should be updating shortly.

Thanks

repo: saadq/Materialize


text:
Activating Open Collective

Hi, I'm making updates for Open Collective. Either you or a supporter signed this repo up for Open Collective. This pull request adds backers and sponsors from your Open Collective https://opencollective.com/resumake ❤
It adds two badges at the top to show the latest number of backers and sponsors. It also adds placeholders so that the avatar/logo of new backers/sponsors can automatically be shown without having to update your README.md. [more info]. See how it looks on this repo.
We have also added a postinstall script to let people know after npm|yarn install that you are welcoming donations (optional). [More info]
You can also add a "Donate" button to your website and automatically show your backers and sponsors there with our widgets. Have a look here: https://opencollective.com/widgets
P.S: As with any pull request, feel free to comment or suggest changes. The only thing "required" are the placeholders on the README because we believe it's important to acknowledge the people in your community that are contributing (financially or with code!).
Thank you for your great contribution to the open source community. You are awesome! 🙌
And welcome to the open collective community! 😊
Come chat with us in the #opensource channel on https://slack.opencollective.com - great place to ask questions and share best practices with other open source sustainers!

Hey @monkeywithacupcake, thanks a lot for the PR. I'm not sure if I understand correctly... the PR seems to only add the postinstall npm script. Was it supposed to do anything more than that?

Very weird. Yes, it was also supposed to change the readme. Lemme see if I can update it.

authors: monkeywithacupcake saadq

repo: saadq/resumake


text:
Input Values from First Step Appear in Second Step Despite Unique IDs and Names

Hi, I found an error in the step form. The input values from the first step appear in the second, even though they have different names and IDs (the code below I changed from the example in the documentation):
import { Text, Spacer, ButtonGroup } from '@chakra-ui/react'
import {
  FormLayout,
  PrevButton,
  NextButton,
  FormStepper,
  StepsCompleted,
  FormValue,
  LoadingOverlay,
  LoadingSpinner,
  LoadingText,
  PropertyList,
  Property,
} from '@saas-ui/react'
import { StepForm } from '@saas-ui/forms/zod'
import * as zod from 'zod'

export default function CreateProject() {
  const steps = [
    {
      name: 'project',
      schema: zod.object({
        name: zod.string().nonempty(),
        description: zod.string(),
      }),
    },
    {
      name: 'project2',
      schema: zod.object({
        name2: zod.string().nonempty(),
        description2: zod.string(),
      }),
    },
    {
      name: 'members',
      schema: zod.object({
        members: zod.string(),
      }),
    },
  ]

  const onSubmit = (params) => {
    console.log(params)
    return new Promise((resolve) => {
      setTimeout(resolve, 1000)
    })
  }

  return (
    <StepForm
      steps={steps}
      defaultValues={{
        name: '',
        email: '',
        password: '',
      }}
      onSubmit={onSubmit}
    >
      {({ Field, FormStep }) => (
        <FormLayout>
          <FormStepper>
            <FormStep name="project" title="Project details">
              <FormLayout>
                <Field name="name" isRequired label="Name" />
                <Field name="description" label="Description" />
              </FormLayout>
            </FormStep>
             <FormStep name="project2" title="Project details">
              <FormLayout>
                <Field name="name2" isRequired label="Name 2" />
                <Field name="description2" label="Description 2" />
              </FormLayout>
            </FormStep>
            <FormStep name="members" title="Invite your team">
              <FormLayout>
                <Field
                  name="members"
                  type="textarea"
                  label="Invite people"
                  placeholder="hello@saas-ui.dev, etc"
                  autoFocus
                />
              </FormLayout>
            </FormStep>
            <FormStep name="confirm" title="Confirm">
              <FormLayout>
                <Text>Please confirm that your information is correct.</Text>
                <PropertyList>
                  <Property label="Name" value={<FormValue name="name" />} />
                  <Property
                    label="Description"
                    value={<FormValue name="description" />}
                  />
                </PropertyList>
              </FormLayout>
            </FormStep>

            <StepsCompleted>
              <LoadingOverlay>
                <LoadingSpinner />
                <LoadingText>
                  We are setting up your project, just a moment...
                </LoadingText>
              </LoadingOverlay>
            </StepsCompleted>
          </FormStepper>
          <ButtonGroup w="full">
            <PrevButton variant="ghost" />
            <Spacer />
            <NextButton />
          </ButtonGroup>
        </FormLayout>
      )}
    </StepForm>
  )
}

Thanks for reporting, I reproduced the issue and try to get this fixed asap.
In meantime you can add a unique 'key' prop to the fields to prevent this from happening.

The unique key solve my issue, tks so much!

I actually fail to reproduce it properly, it doesn't happen in storybook.
In what framework do you get this issue?

Released a bunch of fixes, please re-open this issue if you still run into this problem.

I actually fail to reproduce it properly, it doesn't happen in storybook.
In what framework do you get this issue?

Sorry for not responding right away, to your email and I couldn't respond right away, I ended up forgetting. I'll test it in my applications, I'll let you know anything. Thank you very much!

authors: Pagebakers PedroHenriqueFernandes

repo: saas-js/saas-ui


text:
HelpingMapper.swift: Invalid redeclaration of '<--' which differs only by the kind of optional passed as an inout argument ('Transform.Object!' vs. 'Transform.Object?')

Xcode gives redeclaration warnings.
Invalid redeclaration of '<--' which differs only by the kind of optional passed as an inout argument ('Transform.Object!' vs. 'Transform.Object?')

Hi @shroff-kandarp , is it causing any problem for now?

Ok sure, will look into it. Also, let me know if you are facing any issues with current client.

Hi @shroff-kandarp , i have updates library to support swift 4.2. Try to update it. Let me know if you face any issues :)


text:
Bill split CSS issue (native JS)

Describe the bug
CSS issue with navbar in "Bill split" challenge
Expected behavior
The navbar should look proper like in the other challenges
Screenshots

Possible reason
Conflicts with core CSS

@arpansaha13 hey Arpanaha could you please assign this to me

issue resolved you can check and merge it
https://deploy-preview-241--preeminent-tapioca-4294b2.netlify.app/machine-coding/bill-spilt/

Thanks a lot for fixing the issue
A maintainer will review and merge soon within today

repo: sadanandpai/frontend-mini-challenges


text:
Migrate from setuptools to hatch

Fixes issues with editable builds, broken by new versions of setuptools
Migrates project to pyproject.toml, as recommended

Pull Request Test Coverage Report for Build 9405222719
Details

0 of 0   changed or added relevant lines in 0 files are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.05%) to 93.795%

Files with Coverage Reduction
New Missed Lines
%

gnosis/eth/tests/clients/test_sourcify_client.py
2
91.11%

Totals

Change from base Build 9399920971:
-0.05%

Covered Lines:
8238

Relevant Lines:
8783

💛  - Coveralls

Pull Request Test Coverage Report for Build 9415679263
Details

0 of 0   changed or added relevant lines in 0 files are covered.
2 unchanged lines in 2 files lost coverage.
Overall coverage remained the same at 93.84%

Files with Coverage Reduction
New Missed Lines
%

gnosis/eth/ethereum_client.py
1
86.16%

gnosis/safe/tests/utils.py
1
60.0%

Totals

Change from base Build 9399920971:
0.0%

Covered Lines:
8242

Relevant Lines:
8783

💛  - Coveralls

Pull Request Test Coverage Report for Build 9415690900
Details

0 of 0   changed or added relevant lines in 0 files are covered.
5 unchanged lines in 4 files lost coverage.
Overall coverage decreased (-0.02%) to 93.818%

Files with Coverage Reduction
New Missed Lines
%

gnosis/eth/ethereum_client.py
1
86.16%

gnosis/safe/tests/utils.py
1
60.0%

gnosis/safe/safe_tx.py
1
90.97%

gnosis/eth/tests/clients/test_sourcify_client.py
2
91.11%

Totals

Change from base Build 9399920971:
-0.02%

Covered Lines:
8240

Relevant Lines:
8783

💛  - Coveralls

Pull Request Test Coverage Report for Build 9418356877
Details

0 of 0   changed or added relevant lines in 0 files are covered.
3 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.01%) to 93.556%

Files with Coverage Reduction
New Missed Lines
%

gnosis/eth/tests/clients/test_sourcify_client.py
1
64.44%

gnosis/eth/clients/sourcify_client.py
2
78.43%

Totals

Change from base Build 9417161895:
-0.01%

Covered Lines:
8217

Relevant Lines:
8783

💛  - Coveralls

Pull Request Test Coverage Report for Build 9418356877
Details

0 of 0   changed or added relevant lines in 0 files are covered.
3 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.01%) to 93.556%

Files with Coverage Reduction
New Missed Lines
%

gnosis/eth/tests/clients/test_sourcify_client.py
1
64.44%

gnosis/eth/clients/sourcify_client.py
2
78.43%

Totals

Change from base Build 9417161895:
-0.01%

Covered Lines:
8217

Relevant Lines:
8783

💛  - Coveralls

Pull Request Test Coverage Report for Build 9418395500
Details

0 of 0   changed or added relevant lines in 0 files are covered.
3 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.01%) to 93.556%

Files with Coverage Reduction
New Missed Lines
%

gnosis/eth/tests/clients/test_sourcify_client.py
1
64.44%

gnosis/eth/clients/sourcify_client.py
2
78.43%

Totals

Change from base Build 9417161895:
-0.01%

Covered Lines:
8217

Relevant Lines:
8783

💛  - Coveralls

Pull Request Test Coverage Report for Build 9418395500
Details

0 of 0   changed or added relevant lines in 0 files are covered.
3 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.01%) to 93.556%

Files with Coverage Reduction
New Missed Lines
%

gnosis/eth/tests/clients/test_sourcify_client.py
1
64.44%

gnosis/eth/clients/sourcify_client.py
2
78.43%

Totals

Change from base Build 9417161895:
-0.01%

Covered Lines:
8217

Relevant Lines:
8783

💛  - Coveralls

Pull Request Test Coverage Report for Build 9418620199
Details

0 of 0   changed or added relevant lines in 0 files are covered.
3 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.01%) to 93.556%

Files with Coverage Reduction
New Missed Lines
%

gnosis/eth/tests/clients/test_sourcify_client.py
1
64.44%

gnosis/eth/clients/sourcify_client.py
2
78.43%

Totals

Change from base Build 9417161895:
-0.01%

Covered Lines:
8217

Relevant Lines:
8783

💛  - Coveralls

Pull Request Test Coverage Report for Build 9418907146
Details

0 of 0   changed or added relevant lines in 0 files are covered.
3 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.01%) to 93.556%

Files with Coverage Reduction
New Missed Lines
%

gnosis/eth/tests/clients/test_sourcify_client.py
1
64.44%

gnosis/eth/clients/sourcify_client.py
2
78.43%

Totals

Change from base Build 9417161895:
-0.01%

Covered Lines:
8217

Relevant Lines:
8783

💛  - Coveralls

repo: safe-global/safe-eth-py


text:
Windows Version Error

Works on Mac without problem.
On Windows I get an error message:
An internal error has occurred: [string "JSON.lua"]:383: nil passed to JSON:decode()

Hmmm... JSON.lua is from an external source, but could be the implementation of it here is not Windows-friendly, somehow, since the developer of this app did say he'd only tested on Mac (and it worked). I can also confirm that it works (and quite well) on OS X. (Sorry I cannot be of any help to resolving an issue on Windows since I don't have a machine with Windows installed right now.)
I've also confirmed it works well with the latest version of the JSON.lua file from Jeffrey Friedl, so maybe that would resolve this issue. I can offer a pull request since I've got that change locally and confirmed it at least doesn't seem to break anything I've noticed. I think the newer version does include quite a few fixes, plus a lot more documentation of that file and a couple areas that look like they offer new functionality (which may or may not be useful for this project).
@safx Thanks for sharing this cool plugin... and documenting it so well, too. I'm surprised there aren't a lot more users for this. I'll write a little article about it and maybe see if that helps bring a bit more attention and/or people who can also verify/help fix any bug for Windows users.

@LowellMontgomery the patch you submitted for JSON.lua doesn't fix the underlying bug. I just cherry-picked your change and I am still seeing the nil error. I dug into the bug a bit and in ClarifaiAPI.lua the "local body, reshdrs = LrHttp.postMultipart(tagAPIURL, mimeChunks, headers);" line in the getTags_impl method is failing. From what I can tell, on Windows the thumbnailPath which is set just above the LrHttp.post call is a path to a file that is an invalid JPEG. Photoshop errors with "Could not complete your request because an invalid DQT JPEG segment QTable number is found (it must be < 4)". I have no idea what this means but the return's from the LrHttp.post call are all nil and if the file it's trying to submit is invalid... I have a hunch I found the source of the issue.

And now I'm stuck with "{error={errorCode="unknown",name="The parameter is incorrect." after trying the LrHttp.postMultipart call. I think we have a bug on the Windows platform or newer releases of LR.

@mcrosson That's getting into parts of the project I haven't really dug into yet, but I've actually also seen the exact same error now (albeit only occasionally) on Mac. If you are getting that error consistently, I suspect you have found a significant bug in the plugin logic for Windows, but that same error is seen (apparently) if something just glitches (network issues?) and no JSON response is received or something other than what is expected (i.e. something from the server side). Anyway, we should try to fix that, but it would be helpful to have Windows users testing and/or helping find a workaround since the consistent failure only seems to happen on Windows. For the occasional failures, we should improve the behavior to maybe try again and/or at least provide a more "human" message for users.

@LowellMontgomery I gave up on trying to put together a fix. I ended up going a different direction...
I created my own Lightroom export plugin that leverages the Clarifai API for tagging. It uses the export process instead of a menu item to initiate the tagging and has quite a few extra features. Features like choosing the model/detection to use, more resizing options, auto-tagging, API usage stats and more. It should work out of the box on Windows / Mac.
Project page: https://github.com/mcrosson/lr_plugin_computer_vision_tagging
Features/Changelog: https://github.com/mcrosson/lr_plugin_computer_vision_tagging/blob/master/docs/ProjectPlan.md

Hi Mike,
Thanks for getting back to me so quickly.
Your implementation sounds awesome. I have done quite a bit in terms of feature expansion in my fork of the safx/LightroomPlugin-ClarifaiTagger, but maybe I should try your “extra features” and try to merge the best of both worlds. It sounds like you have done some interesting things there. Personally, I still want to be able to do additional metadata processing after the initial Clarifai-powered tagging. Does using it as an export process mean it’s the last step in your workflow, or was that just a way of sending the images to the system?
Some of the feature improvements I’ve added to the original safx implementation include:

Support for finding “already existing terms” in a hierarchical list instead of just a flat list. Without this, it created more work than it saved since adding terms meant creating duplicate terms that I then had to manually merge with existing terms, a tedious process.

Related to the above, I can also skip sections of the tree to look for existing keywords if I wouldn’t want to use those terms, e.g. “downtown” is a sub-location keyword for some region-specific keywords (created using John Beardsworths Search/Replace/Transfer plugin to copy geolocation metadata into a keyword hierarchy). So I skip the LOCATIONS section of my term tree. I also skip my people, and some long lists of plant and animal species since Clarifai isn’t yet smart enough to send those terms, anyway (so ignoring these very long sections of my term tree makes the plugin’s processes more efficient).

If two or more keywords have the same name, I provide checkboxes for both. Keywords with parents (all of mine), display a tooltip with the full “ancestry” if you hover over the checkbox or keyword.

I auto-select terms that are existing in my keyword list (as the safx version originally supported), but I now also support modifying that behavior to only select terms where Clarifai has set a high probability (the level of probability required is configurable in the settings panel).

And there are a few other small improvements I have in mind. But the additional features in your implementation also really sound cool, so I’ll have to see if we can bring the best features into one project.
Thanks again for your quick response,
Lowell

On Oct 13, 2016, at 2:47 AM, Mike C notifications@github.com wrote:
@LowellMontgomery https://github.com/LowellMontgomery I gave up on trying to put together a fix. I ended up going a different direction...
I created my own Lightroom export plugin that leverages the Clarifai API for tagging. It uses the export process instead of a menu item to initiate the tagging and has quite a few extra features. Features like choosing the model/detection to use, more resizing options, auto-tagging, API usage stats and more. It should work out of the box on Windows / Mac.
Project page: https://github.com/mcrosson/lr_plugin_computer_vision_tagging https://github.com/mcrosson/lr_plugin_computer_vision_tagging
Features/Changelog: https://github.com/mcrosson/lr_plugin_computer_vision_tagging/blob/master/docs/ProjectPlan.md https://github.com/mcrosson/lr_plugin_computer_vision_tagging/blob/master/docs/ProjectPlan.md
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/safx/LightroomPlugin-ClarifaiTagger/issues/1#issuecomment-253380228, or mute the thread https://github.com/notifications/unsubscribe-auth/AImZNBmTA_t033BIsaasd6vY0zVz1cQFks5qzX-bgaJpZM4IwDSY.

@LowellMontgomery The export process is just the first step in the work flow, it's how I send images to Clarifai (or others hopefully). I still show a tagging dialog and ok/cancel button after the export runs. The real difference between the two projects is how you kick off the process (menu item here, export in mine).
I saw your pull request with some of the new features and was hoping to see if you'd be interested in changing gears a bit. All 4 of your points are awesome ideas and I'd appreciate any help getting them integrated into the plugin I put together. If you're interested in hacking on my plugin a bit, please let me know. I think we can work together to get everything you're suggesting into the project.
To speak to each point directly:

I saw this in your pull request and it would definitely be something I'd want to see implemented. I currently don't have this functionality built.
This sounds like a very useful addition to point 1. I currently don't have this functionality built.
This sounds like a really good addition to 1 and 2. I'm not sure how I'd put it together but if 1 and 2 end up added, I think this functionality would be a huge gain.
My plugin will auto-select existing terms and has an option to auto-apply tags with a minimum p value. However, auto-selecting tags with a minimum p value should be a pretty straight forward change and I'd be willing to add it as additional functionality.

@mcrosson I'd be happy to help bring those features (1-4) into your project and brainstorm with you about other possible improvements. I think it's best we have regular communication so we can prioritize and be "on the same page" with regard to feature development. I'd rather not spend lots of time developing features that you aren't interested in seeing merged into the master and end up with a permanent fork that (at some point) wouldn't be merge-friendly. If you or safx weren't open to those features, I guess I'd be looking at creating a third project (a permanent fork) to deal with these things that I consider high priorities.
Having looked over your feature list and project screenshots, my interest is definitely piqued. I'll add a fork and create a feature branch for the above points and I'll see how simple it is to implement them... then we can also discuss some other interesting features that your plan doesn't (yet) include.
Anyway, since we are now getting far "off-topic" for this "issue ticket", I'd like to continue this conversation via private email and/or tickets on your project.

@LowellMontgomery Agreed, I can be reached via the e-mail in my github profile or feel free to open tickets on the project page.

authors: LowellMontgomery mcrosson samsamson

repo: safx/LightroomPlugin-ClarifaiTagger


text:
lama-fourier query

lama-fourier: is it trained with tanh activation or sigmoid (last layer of generator)?

Hello! It was trained with sigmoid. See https://github.com/saic-mdal/lama/blob/main/configs/training/generator/ffc_resnet_075.yaml for details of the lama-fourier generator architecture.

authors: UmarSpa elimohl

repo: saic-mdal/lama


text:
Start training from a pretrained model

I can't load the trained checkpoint, how can I modify the code to load it?

I found out how to load checkpoints, but the pre-trained model given by the author does not have the parameters of the discriminator. Can the author also release the parameters of the trained discriminator? 👀

In order to continue training, you have to add +trainer.kwargs.resume_from_checkpoint=path_to_model.ckpt to arguments of train.py.
Regarding full checkpoints - I think yes, we can do that

can you release full checkpoints?

In order to continue training, you have to add +trainer.kwargs.resume_from_checkpoint=path_to_model.ckpt to arguments of train.py.
Regarding full checkpoints - I think yes, we can do that

Thanks again!

Full checkpoints released - please refer to #96


text:
calculator for finding gamma function of any number

I would like to add a calculator finding gamma function of any number

Go ahead
Deadline 10 May,2021

Go ahead
Deadline 10 May,2021


text:
Bug in ARC Length Calculator not getting answer

Describe the bug
After giving input in Arc Length Calculator it is showing all values are required to obtain answer
Screenshots

Hi, I want to work on this issue I will start working on it as soon as I get assigned!! I am a part of GSSoC'21.
Kindly assign this issue to me!
Discord Username : Abhijeet Sinha(P)
Discord Tag: #4018


text:
Paraboloid calculator not getting displayed

Describe the bug

A clear and concise description of what the bug is.

Possible solution

Describe the solution you thought of.

Screenshots

If applicable, add screenshots to help explain your problem.

Hi, I want to work on this issue I will start working on it as soon as I get assigned!! I am a part of GSSoC'21.
Kindly assign this issue to me!
Discord Username : Abhijeet Sinha(P)
Discord Tag: #4018