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?
 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"


Make Alertmanager configurable by this component

Context
The OpenShift 4 documentation explains how to configure Alertmanager. This is done by creating the secret  alertmanager-main within the namespace openshift-monitoring.
The key alertmanager.yaml within that secret should be configurable by this component.

global:
  resolve_timeout: 5m
route:
  group_wait: 30s
  group_interval: 5m
  repeat_interval: 12h
  receiver: default
  routes:
  - match:
      alertname: Watchdog
    repeat_interval: 5m
    receiver: watchdog
receivers:
- name: default
- name: watchdog

The above snipped is the default Alertmanager config taken from the OpenShift documentation. Should we add this as the default to this component? Alternatively, we could omit the config and do nothing.

Closed by #6


Why docs ? The s is too much, no ?

I don't understand why only docs have s. Have you references/links ?

Hey!
Thank you for the question @kosssi !
Actually, I don't know if there's a proper way in English to say that.
But if you're right we need to update the documentation for sure!
@bcoe you are an English native speaker, what do you think about it?

As a native speaker, I find docs to be the more natural shorthand.
In English, doc is short for document, both noun and verb. To help with disambiguation the shorthand docs is typically used for documentation. It doesn't imply a plurality of changes like it would do with fix or feat, it implies the area the change is affecting.

🇮🇪He's from Ireland, he's right 😂
@kosssi is it fine for you the explanation or you do think it may be still discussed?

it's good explanation, thanks 👍

Perfect!
Thank you @kosssi  for asking about your doubt and to @kudos  for explaining it to us 😄
Closing this baby!


Sat Solver multithreading documentation

Hello,
I'm trying to accomplish multi-threading with the SAT solver, similar as how it's discussed here:
https://github.com/google/or-tools/issues/933
However, one link doesn't work anymore, but even going through what I think is the current link:
https://github.com/google/or-tools/blob/stable/docs/index.md I don't find the info.
Also, when going to the second link, I'm also not finding the info there.
Would it be possible to point me in the right direction?
Best regards

Which language?
In Python is solver.parameters.num_search_workers = 8 as seen in:
https://github.com/google/or-tools/blob/stable/examples/python/shift_scheduling_sat.py#L381

@stradivari96
Seems it's not compatible with SearchForAllSolutions in Python but thanks anyway for the info!

No, too complex to de-duplicate solutions in parallel.
Le dim. 22 sept. 2019 à 22:57, LanderBeeuwsaert<EMAIL_ADDRESS>a écrit :

@stradivari96 https://github.com/stradivari96
Seems it's not compatible with SearchForAllSolutions in Python but thanks
anyway for the info!
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/google/or-tools/issues/1591?email_source=notifications&email_token=ACUPL3PBM6OE3DTLCNINQVLQK7L45A5CNFSM4IZCSKT2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7JPCGI#issuecomment-533917977,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACUPL3N5J6PLUNUPRI6R3WDQK7L45ANCNFSM4IZCSKTQ
.


Hard to identify which extension is disabled

The Python extension is disabled but it's hard to notice

Oh, forgot to mention that I manually installed the v0.0.17 downloaded from the releases page 😅

At the moment the extensions list share style with the sidebar tree, the disabled extension change only opacity to the default list color (that i can't change.) For now i will close until we will have the ability to separate styles between sidebar tree and extensions list.


Falcon graph compilation error fix for when bs>1

This add a code block from transformers to fix the gc error when bs>1
Before submitting

[ ] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
[ ] Did you make sure to update the documentation with your changes?
[ ] Did you write any new necessary tests?

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.


--iree-stream-resource-memory-model=discrete has scalability limits

When handling large, streamed gathers, the discrete memory model trips various scalability limits in the task/wait scheduling system. We will temporarily change the default to "unified" while this is fixed since it provides a path for certain large, external parameter models to work today in a limited fashion (i.e. will hit other resource limits on Windows, has issues with GPU, etc).
Once limits are corrected, please change the default back to "discrete".
Since this is a brand new feature, we will default to the state that has slightly better support to get things moving.

it was bothering me that unified worked when discrete didn't... just realized it's because I haven't implemented queue-ordered allocations on local-task yet and the unified path loading on parameter at a time is queue allocating each parameter to read synchronously - thus it never ends up with a lot of pending waits. If queue-ordered allocations were implemented then it'd hit the same limits/issues that the gather path hits.


BUILD_FAILED : glog:x86-windows-static Visual studio 2015

LOG
-- CURRENT_INSTALLED_DIR=E:/3rdparty/vcpkg/installed/x86-windows-static
-- DOWNLOADS=E:/3rdparty/vcpkg/downloads
-- CURRENT_PACKAGES_DIR=E:/3rdparty/vcpkg/packages/glog_x86-windows-static
-- CURRENT_BUILDTREES_DIR=E:/3rdparty/vcpkg/buildtrees/glog
-- CURRENT_PORT_DIR=E:/3rdparty/vcpkg/ports/glog/.
-- Warning: Static building not supported yet. Building dynamic.
-- Using cached E:/3rdparty/vcpkg/downloads/glog-0472b91c5defdf90cff7292e3bf7bd86770a9a0a.zip
-- Testing integrity of cached file...
-- Testing integrity of cached file... OK
-- Extracting done
-- Configuring x86-windows-static-rel
                                                                                -- Configuring x86-windows-static-rel done
-- Configuring x86-windows-static-dbg
-- Configuring x86-windows-static-dbg done
-- Package x86-windows-static-rel
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:14 (message):
    Command failed: E:/3rdparty/vcpkg/downloads/cmake-3.8.0-rc1-win32-x86/bin/cmake.exe;--build;.;--config;Release;--target;install;--;/p:VCPkgLocalAppDataDisabled=true;/p:UseIntelMKL=No;/m
    Working Directory: E:/3rdparty/vcpkg/buildtrees/glog/x86-windows-static-rel
    See logs for more information:
      E:\3rdparty\vcpkg\buildtrees\glog\package-x86-windows-static-rel-out.log
      E:\3rdparty\vcpkg\buildtrees\glog\package-x86-windows-static-rel-err.log

Call Stack (most recent call first):
  scripts/cmake/vcpkg_install_cmake.cmake:27 (vcpkg_execute_required_process)
  ports/glog/portfile.cmake:29 (vcpkg_install_cmake)
  scripts/ports.cmake:73 (include)

Error: Building package glog:x86-windows-static failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with `.\vcpkg update`, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
  Package: glog:x86-windows-static
  Vcpkg version: 0.0.76-5f3597927266a0b40172ba73c583fb0da5d3404e

Additionally, attach any relevant sections from the log files above.```

I believe I've fixed this with 90019d3 -- could you try pulling and building again?

Thank you it's working now.


Nvidia gpu doesn't work

I am using EndeavourOs. My laptop have intel and nvidia gpu . I activate the nvidia mode and restart . When I type envycontrol --query it says nvidia . But nvidia gpu doesnt work.
I can confirm nvidia drivers are working fine .  I disable integrated gpu from bios and it working.

What am I doing wrong? Because I don't get any errors.


Set the car Charging Level

First of all many thanks for this well working integration.
In the android app for the 500e it is possible to set the charging level (1-5). It would be great to have that possibility also in the FiatChamp.
Is there any chance to get that integrated in future?

I'd love that too


Support deploying a specific SHA or branch

Hello 👋
As part of being able to quickly revert a change to a specific point in time we were wondering if it'd be possible for the branch-deploy action to support deploying a specific SHA or branch-name to a given environment.
Something like .deploy SHA to production or .deploy <my-fav-branch> to production would be what I had in mind 😊
Thanks!

I'll work on implementing this feature
.deploy [sha|tag|branch] to <environment> should be supported

@tiagonbotelho This is now implemented in pre-release v8.1.0. Test it out and let me know what you think! 🎉


Language match for 62493, S W England

Language currently assigned is corn1251, Cornish. However, both songs assigned to society are in English. So, I think a better match would be east2827, East Cornwall-Devon English. One song is from Cornwall and one is from Devon.

Done


Security Audit & Recommendations

Placeholder at the moment in order to address the goals of milestone v0.7. The intention of this ticket is to provide a timeboxed window for us for a top to bottom audit of what is provided by ddev v0.6 to determine if there are any obvious security areas to address.

Given that this is more of a "meta" issue with an implied chunk of research, I suggest this as acceptace criteria:

[ ] Review and decison on OSXFS https://github.com/drud/ddev/issues/282
[ ] Drupal "Private" directory outside of webroot (may require https://github.com/drud/ddev/issues/189).
[ ] Identification of any remaining hot button security items related to file mounts, OS user/groups, container defaults, etc.

Bonus items:

[ ] Remove /etc/host dependency and replace with local DNS solution (possily related to https://github.com/drud/ddev/issues/277).

Switching actionable because beyond this list, I don't see any other major security items beyond what is already been tagged in this release.

Related https://github.com/drud/ddev/issues/175

No longer relevant for v0.7. Closing out.


Please enable coveralls for repo

Repo is ready for coverage reports, please just login on https://coveralls.io and enable KeepSafe/aiohttp project.
I cannot do that because I have no admin rights for aiohttp.

this service wants access to all my private repos. this won't  happen.

Ok. Sorry.
I've removed coveralls from .travis.yaml
On Sat, Jan 3, 2015 at 9:31 PM, Nikolay Kim<EMAIL_ADDRESS>wrote:

this service wants access to all my private repos. this won't happen.
—
Reply to this email directly or view it on GitHub
https://github.com/KeepSafe/aiohttp/issues/210#issuecomment-68606453.

--
Thanks,
Andrew Svetlov

Wait, let me check. Maybe Phillip can admin role to you
On Saturday, January 3, 2015, Andrew Svetlov<EMAIL_ADDRESS>wrote:

Ok. Sorry.
I've removed coveralls from .travis.yaml
On Sat, Jan 3, 2015 at 9:31 PM, Nikolay Kim<EMAIL_ADDRESS><javascript:_e(%7B%7D,'cvml','notifications@github.com');>>
wrote:

this service wants access to all my private repos. this won't happen.
—
Reply to this email directly or view it on GitHub
https://github.com/KeepSafe/aiohttp/issues/210#issuecomment-68606453.

--
Thanks,
Andrew Svetlov
—
Reply to this email directly or view it on GitHub
https://github.com/KeepSafe/aiohttp/issues/210#issuecomment-68606643.

I like to see coveralls progress but can live without it.
Of course it should be for aiohttp project only, not for all KeepSafe
private repos,
On Sat, Jan 3, 2015 at 9:38 PM, Nikolay Kim<EMAIL_ADDRESS>wrote:

Wait, let me check. Maybe Phillip can admin role to you
On Saturday, January 3, 2015, Andrew Svetlov<EMAIL_ADDRESS>wrote:

Ok. Sorry.
I've removed coveralls from .travis.yaml
On Sat, Jan 3, 2015 at 9:31 PM, Nikolay Kim<EMAIL_ADDRESS><javascript:_e(%7B%7D,'cvml','notifications@github.com');>>
wrote:

this service wants access to all my private repos. this won't happen.
—
Reply to this email directly or view it on GitHub
https://github.com/KeepSafe/aiohttp/issues/210#issuecomment-68606453.

--
Thanks,
Andrew Svetlov
—
Reply to this email directly or view it on GitHub
https://github.com/KeepSafe/aiohttp/issues/210#issuecomment-68606643.

—
Reply to this email directly or view it on GitHub
https://github.com/KeepSafe/aiohttp/issues/210#issuecomment-68606708.

--
Thanks,
Andrew Svetlov


Unable to integrate hipchat

I have downloaded the hipchat plug in and have it in docker-cabot folder. I have also modified the env file to show like this
CABOT_PLUGINS_ENABLED=cabot_alert_hipchat
Hipchat integration
HIPCHAT_URL=https://hipchat.****.com/v2/room/7660/notification
HIPCHAT_ALERT_ROOM=7660
HIPCHAT_API_KEY=abcdefghijklmnop123456789
is there anything else I need to do it?

Isn’t Hipchat now discontinued?

No. Not yet.
Regards,
Ravi Paramasivan
1<PHONE_NUMBER>
On Fri, Feb 22, 2019, 5:02 AM Jean-Frédéric<EMAIL_ADDRESS>wrote:

Isn’t Hipchat now discontinued
https://www.atlassian.com/partnerships/slack/faq?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/cabotapp/cabot-alert-hipchat/issues/7#issuecomment-466359741,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AtpY6L5ankf_6OdkwKKDIthGSg00umLLks5vP846gaJpZM4bH53j
.

Hipchat support is discontinued. But the companies who got the license is still continuing.

I have fixed the issue though. But I want to know if we can post message on multiple rooms at same time the same message?


feat(search): do search as you type

no need for pressing enter to search 😊

ah, I added pressing enter to search on purpose so as to minimize the number of queries made, but thanks anyway!


docs: updated track usage && added exports.

What is it?

[ ] Feature / enhancement
[ ] Bug
[x] Docs / tests

Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Use cases and why

One use case

Another use case

Checklist:

[x] My code follows the developer guidelines of this project
[x] I have performed a self-review of my own code
[x] I have made corresponding changes to the documentation
[ ] Added new tests to cover the fix / functionality

Looking great! let's merge it!

Awesome updates, thanks


Content Incorrect or Misleading

"If you already use the Microsoft Authenticator app for two-step verification. Go to the Accounts screen of the app, select the drop-down arrow for your work or school account, and then select Enable phone sign-in."
In the Authenticator app there is NO drop-down arrow. Windows 10 Phone.

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

ID: fd8c41de-1751-6ecd-24b9-ab687f7ae467
Version Independent ID: 11d17688-b87e-f681-cf84-ce90f93e26ce
Content: Microsoft Authenticator phone sign-in - Azure and Microsoft accounts
Content Source: articles/active-directory/user-help/microsoft-authenticator-app-phone-signin-faq.md
Service: active-directory
GitHub Login: @eross-msft
Microsoft Alias: lizross

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

@laultman Please note that as stated here, if you have key icon on your phone. You’ve already set up phone sign-in. In that case you will not see the drop down.

I spent considerable time reading this page and others before giving feedback. I have not seen such icon as shown on my Windows 10 phone. Therefore the document is still incomplete or confusing or just plain WRONG. I am unable to sign in with my Microsoft account without a password. It wants to authorize AFTER the password.
Sent from my Windows 10 device

From: Mohit Garg<EMAIL_ADDRESS>Sent: Wednesday, October 3, 2018 4:35:01 PM
To: MicrosoftDocs/azure-docs
Cc: Larry Aultman; Mention
Subject: Re: [MicrosoftDocs/azure-docs] Content Incorrect or Misleading (#16131)
@laultmanhttps://github.com/laultman Please note that as stated herehttps://docs.microsoft.com/en-us/azure/active-directory/user-help/microsoft-authenticator-app-phone-signin-faq#to-turn-on-phone-sign-in-for-your-account, if you have key icon on your phone. You’ve already set up phone sign-in. In that case you will not see the drop down.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/issues/16131#issuecomment-426791777, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ATVSMgp4wQBAbZ1-SFhjg-Nc8rMcEuraks5uhR91gaJpZM4XGj2t.

This is covered in the last question of the FAQ:
Can I use phone sign-in with my Windows Phone? | No. This feature isn’t supported by the Microsoft Authenticator app on Windows Phone.

@libbro2006 Thanks for your help in clarifying the query.
@laultman We will now proceed to close this thread. If there are further questions regarding this matter, please open a new issue and we will gladly continue the discussion.
Please note that you can post this as a feedback @ https://feedback.azure.com/forums/169401-azure-active-directory. This will allow the community to upvote and for the product team to include into their plans. We also have the "Give Product Feedback" button in our documents now to take you directly to the appropriate feedback page.

Why not simply put a note in the documentation indicating the lack of support for this on Windows Phone (version) instead of making customers hunt it down?  I obviously could not find this. This is the kind of thing that really irritates customer, documentation that is not clear and concise, but scattered across the site.
I suggest this because it clearly indicates Windows 10 support and my Windows Phone is Windows 10 as I suspect most remaining Windows Phone users are using.
Regards,
Larry
Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows 10

From: Libby Brown<EMAIL_ADDRESS>Sent: Wednesday, October 3, 2018 6:51:24 PM
To: MicrosoftDocs/azure-docs
Cc: Larry Aultman; Mention
Subject: Re: [MicrosoftDocs/azure-docs] Content Incorrect or Misleading (#16131)
This is covered in the last question of the FAQ:
Can I use phone sign-in with my Windows Phone? | No. This feature isn’t supported by the Microsoft Authenticator app on Windows Phone.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/issues/16131#issuecomment-426829535, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ATVSMleJUkQndNbTNJ1D1LYbUOHyTRKsks5uhT9sgaJpZM4XGj2t.

@laultman  Thank you for your feedback about the discoverability (or lack thereof) of this information. We plan to refactor this content over the coming months to try to fix these issues along with other customer concerns. If you have additional issues, please continue to let us know so we can make things better for everyone. Thanks again!

My company is CSP Direct Reseller. We have support our customers so accurate, concise, and complete documentation is critical to our success. And by extension, Microsoft’s.
Sent from my Windows 10 device

From: Elizabeth Ross<EMAIL_ADDRESS>Sent: Thursday, October 4, 2018 1:36:53 PM
To: MicrosoftDocs/azure-docs
Cc: Larry Aultman; Mention
Subject: Re: [MicrosoftDocs/azure-docs] Content Incorrect or Misleading (#16131)
@laultmanhttps://github.com/laultman Thank you for your feedback about the discoverability (or lack thereof) of this information. We plan to refactor this content over the coming months to try to fix these issues along with other customer concerns. If you have additional issues, please continue to let us know so we can make things better for everyone. Thanks again!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/issues/16131#issuecomment-427106035, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ATVSMnj0UW3xFWoAPG1xw91qOPueN9m4ks5uhkc1gaJpZM4XGj2t.


Unable to authenticate with DefaultAzureCredential for table service under storage

Package Name:  azure-identity
Package Version:  1.13.0
Operating System: Windows11
Python Version:  3.10.4

Describe the bug
While connecting to the azure table using the DefaultAzureCredential, I expect to follow a chain of option and connect.
But it fails at the environment credential and does not move to the next chain. https://learn.microsoft.com/en-us/azure/developer/python/sdk/authentication-overview
Error:
Instantiate a TableServiceClient using a TokenCredential
DefaultAzureCredential failed to retrieve a token from the included credentials.
Attempted credentials:
EnvironmentCredential: EnvironmentCredential authentication unavailable. Environment variables are not fully configured.
To Reproduce
Steps to reproduce the behavior:
from datetime import datetime
import asyncio
async def creat_ent():
    print("Instantiate a TableServiceClient using a TokenCredential")
    # [START auth_from_aad]
    from azure.data.tables import TableServiceClient
    from azure.identity import DefaultAzureCredential

    with TableServiceClient(endpoint="https://XXXXXXXXXXX.table.core.windows.net/", credential=DefaultAzureCredential()) as table_service_client:
        properties = table_service_client.get_service_properties()
        print("properties are")
        print(f"{properties}")
asyncio.run(creat_ent())

Expected behavior
As per the documentation https://learn.microsoft.com/en-us/azure/developer/python/sdk/authentication-overview
it should try for environmental then managed identity and then for the azure cli.
But it is failing at the initial setup.

Tried the same but same result

@kollachaitanyakrishna Thanks for your feedback!
@xiangyan99 Can you help to take a look why having issues in using DefaultAzureCredential? We are using the same credential in our samples and tests, and it works well.

Thanks for reaching out.
Let's take one step back.
Have you tried:
from datetime import datetime
import asyncio
async def creat_ent():
    print("Instantiate a TableServiceClient using a TokenCredential")
    # [START auth_from_aad]
    from azure.data.tables.aio import TableServiceClient
    from azure.identity.aio import DefaultAzureCredential   # We need async DefaultAzureCredential here

    async with TableServiceClient(endpoint="https://XXXXXXXXXXX.table.core.windows.net/", credential=DefaultAzureCredential()) as table_service_client:
        properties = await table_service_client.get_service_properties()
        print("properties are")
        print(f"{properties}")
asyncio.run(creat_ent())

?
And which type of credential you expected to work?
It seems to me the output:
Attempted credentials:
EnvironmentCredential: EnvironmentCredential authentication unavailable. Environment variables are not fully configured.
is correct because you did not have environment variables configured.

@xiangyan99 : No we have not not configured any environment variables that starts with "AZURE_....", None of the variables are configured.
my expectation is it should work with developer cli in developer machine and work with managed identity on any hosted solutions.
When we try this option, it works.
def create_azure_credential() -> ChainedTokenCredential:
    """Creates an Azure Developer CLI Credential client.

    Returns:
        ChainedTokenCredential instance.
    """
    credential_chain = (
        AzureCliCredential(),
        ManagedIdentityCredential(),
    )
    credential = ChainedTokenCredential(*credential_chain)
    return credential

But if we change the chain, it fails
def create_azure_credential() -> ChainedTokenCredential:
    """Creates an Azure Developer CLI Credential client.

    Returns:
        ChainedTokenCredential instance.
    """
    credential_chain = (
        ManagedIdentityCredential(),
        AzureCliCredential(),

    )
    credential = ChainedTokenCredential(*credential_chain)
    return credential

Thanks for the confirmation.
Can you enable logging so we can look into what happened?
You can add code like:
import logging
logging.basicConfig(filename='c:/temp/log.log', level=logging.DEBUG)   # you need to modify the filename if you are using non-windows.

log.log
Sharing the log as requested.

Thanks. Did you configure the managed identity on your hosted VM?

This can be closed
As our organization run behind a proxy. after setting the http_proxy variable. it is fixed.


[Discord integration] Move the DynamicPager component to the Discord SDK

As this component is meant to be used by extensions, it should be placed in the Discord SDK. Even today multiple extensions are using it and incorrectly referencing the core package.

Solved by #87.


Roman Numeral Converter Tests Do Not Account For a Number in the 400s

On the code challenge, "https://www.freecodecamp.com/challenges/roman-numeral-converter", the tests do not account for a number in the 400s. My code passed even though when 400 was passed to the function it returned "CCCC". It should only accept "CD".

@bryanjenkins Would you mind sharing your code as well. It would be quicker to identify the and a test for the use case.
Thanks.

Sure, no problem.
The following code passes even though it outputs "CCCC" for 400.
function numToRomanNumeralLetter(num) {

  switch(num) {
    case 1:
      return "I";
    case 4:
      return "IV";
    case 5:
      return "V";
    case 6:
      return "VI";
    case 9:
      return "IX";
    case 10:
      return "X";
    case 40:
      return "XL";
    case 50:
      return "L";
    case 90:
      return "XC";
    case 100:
      return "C";
    case 500:
      return "D";
    case 900:
      return "CM";
    case 1000:
      return "M";
  }
}

function convertToRoman(num) {

  var romanNumeral = "";

  console.log("Num originally is: " + num);

  do {

    if (num>=1000) {

      num -= 1000;
      romanNumeral += numToRomanNumeralLetter(1000);
      console.log("Num is now 1000 less: "+ num);

    } else if (num>=900) {

      num -= 900;
      romanNumeral += numToRomanNumeralLetter(900);
      console.log("Num is now 900 less: "+ num);

    } else if (num>=500) {

      num -= 500;
      romanNumeral += numToRomanNumeralLetter(500);
      console.log("Num is now 500 less: "+ num);

    } else if (num>=100) {

      num -= 100;
      romanNumeral += numToRomanNumeralLetter(100);
      console.log("Num is now 100 less: "+ num);

    } else if (num>=90) {

      num -= 90;
      romanNumeral += numToRomanNumeralLetter(90);
      console.log("Num is now 100 less: "+ num);

    } else if (num>=50) {

      num -= 50;
      romanNumeral += numToRomanNumeralLetter(50);
      console.log("Num is now 50 less: "+ num);

    } else if (num>=40) {

      num -= 40;
      romanNumeral += numToRomanNumeralLetter(40);
      console.log("Num is now 40 less: "+ num);

    } else if (num>=10) {

      num -= 10;
      romanNumeral += numToRomanNumeralLetter(10);
      console.log("Num is now 10 less: "+ num);

    } else if (num>=5) {

      if (num === 9) {

        num -= 9;
        romanNumeral += numToRomanNumeralLetter(9);
        console.log("Num is now 9 less: "+ num);

      } else if (num === 6) {

        num -= 6;
        romanNumeral += numToRomanNumeralLetter(6);
        console.log("Num is now 6 less: "+ num);

      } else {

        num -= 5;
        romanNumeral += numToRomanNumeralLetter(5);
        console.log("Num is now 5 less: "+ num);

      }

    } else if (num>=1) {

      if (num === 4) {

        num -= 4;
        romanNumeral += numToRomanNumeralLetter(4);
        console.log("Num is now 4 less: "+ num);

      } else {

        num -= 1;
        romanNumeral += numToRomanNumeralLetter(1);
        console.log("Num is now 1 less: "+ num);

      }
    }

  } while (num >= 1)

  console.log("Roman numeral is: " +romanNumeral);
  return romanNumeral;

}

convertToRoman(400);

It should only pass with this code:
function numToRomanNumeralLetter(num) {

  switch(num) {
    case 1:
      return "I";
    case 4:
      return "IV";
    case 5:
      return "V";
    case 6:
      return "VI";
    case 9:
      return "IX";
    case 10:
      return "X";
    case 40:
      return "XL";
    case 50:
      return "L";
    case 90:
      return "XC";
    case 100:
      return "C";
    case 400:
      return "CD";
    case 500:
      return "D";
    case 900:
      return "CM";
    case 1000:
      return "M";
  }
}

function convertToRoman(num) {

  var romanNumeral = "";

  console.log("Num originally is: " + num);

  do {

    if (num>=1000) {

      num -= 1000;
      romanNumeral += numToRomanNumeralLetter(1000);
      console.log("Num is now 1000 less: "+ num);

    } else if (num>=900) {

      num -= 900;
      romanNumeral += numToRomanNumeralLetter(900);
      console.log("Num is now 900 less: "+ num);

    } else if (num>=500) {

      num -= 500;
      romanNumeral += numToRomanNumeralLetter(500);
      console.log("Num is now 500 less: "+ num);

    } else if (num>=400) {

      num -= 400;
      romanNumeral += numToRomanNumeralLetter(400);
      console.log("Num is now 400 less: "+ num);

    } else if (num>=100) {

      num -= 100;
      romanNumeral += numToRomanNumeralLetter(100);
      console.log("Num is now 100 less: "+ num);

    } else if (num>=90) {

      num -= 90;
      romanNumeral += numToRomanNumeralLetter(90);
      console.log("Num is now 100 less: "+ num);

    } else if (num>=50) {

      num -= 50;
      romanNumeral += numToRomanNumeralLetter(50);
      console.log("Num is now 50 less: "+ num);

    } else if (num>=40) {

      num -= 40;
      romanNumeral += numToRomanNumeralLetter(40);
      console.log("Num is now 40 less: "+ num);

    } else if (num>=10) {

      num -= 10;
      romanNumeral += numToRomanNumeralLetter(10);
      console.log("Num is now 10 less: "+ num);

    } else if (num>=5) {

      if (num === 9) {

        num -= 9;
        romanNumeral += numToRomanNumeralLetter(9);
        console.log("Num is now 9 less: "+ num);

      } else if (num === 6) {

        num -= 6;
        romanNumeral += numToRomanNumeralLetter(6);
        console.log("Num is now 6 less: "+ num);

      } else {

        num -= 5;
        romanNumeral += numToRomanNumeralLetter(5);
        console.log("Num is now 5 less: "+ num);

      }

    } else if (num>=1) {

      if (num === 4) {

        num -= 4;
        romanNumeral += numToRomanNumeralLetter(4);
        console.log("Num is now 4 less: "+ num);

      } else {

        num -= 1;
        romanNumeral += numToRomanNumeralLetter(1);
        console.log("Num is now 1 less: "+ num);

      }
    }

  } while (num >= 1)

  console.log("Roman numeral is: " +romanNumeral);
  return romanNumeral;

}

convertToRoman(400);

@bryanjenkins can you confirm that this is still an issue?

Yes, I just checked and it still outputs CCCC and passes all tests.

Stop
On Jan 3, 2017 11:22 PM, "Bryan Jenkins"<EMAIL_ADDRESS>wrote:

Yes, I just checked and it still outputs CCCC and passes all tests.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/FreeCodeCamp/FreeCodeCamp/issues/8127#issuecomment-270308932,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AXtMU0N-rZ4PQb7yJsCAAtXZtWmVnyDTks5rO0i6gaJpZM4IIAGe
.

Hello!
Looks like you may have accidentally subscribed to all notifications for the FreeCodeCamp repository. To stop receiving notifications please visit the subscriptions page or click on the image below and select "Not watching".

We are sorry for your inconvenience!

@bryanjenkins Thanks for confirming this. I've added the help wanted tag.

@QuincyLarson I had submitted a PR for this issue in staging. It was reported in this issue.
Maybe the changes would reflect when staging is merged with the production branch.

Closing, thanks @Manish-Giri !


feat: add postgresql dependency

User should deploy dependencies on their own. Adding postgresql from bitnami there also mean we have to do the same with mysql, ..etc. Result in complexity and increase maintenance effort.


cloudsql: fix thrashing on IsUpToDate by ignoring attr ref fields

Description of your changes

Fixes #77
Checklist

I have:

[x] Run make reviewable to ensure this PR is ready for review.
[x] Ensured this PR contains a neat, self documenting set of commits.
[x] Updated any relevant documentation, examples, or release notes.
[x] Updated the dependencies in app.yaml to include any new role permissions.

@negz yep, sorry about that!


Dexie module does not have named export

Hello,
The Dexie typescript definition file indicates that Dexie is exported as the default export and as 'Dexie' named export but the real javascript module only expose it as the default export.
So this:
import { Dexie } from 'Dexie';

causes this error while bundling:
export 'Dexie' was not found in 'dexie'

but typescript is not complaining.

Ok. I thought I did it in dexie-static-props.ts but I understand now that it only works for the umd version.

If we'd export {Dexie} together with export default Dexie in index.ts we create problems for rollup to generate the UMD version. For UMD outputs, rollup handles the case when only a default export is used so it is similar to module.exports = Dexie. Having a mixed export would require the UMD to let the final exported module become {Dexie: Dexie, default: Dexie}, which works bad for UMD exports.
I think it's fixable if we separate the UMD and ES builds a bit (different module entries and different rollup configs).
Working on it.


Add Address Field to showcase

The showcase here... https://bullettrain.co/docs/showcase is super helpful, but it does not currently include the new address_field.

Noted 👍

I've added a note in Issue https://github.com/bullet-train-co/bullet_train-core/issues/533, that's the repo in which we'll be documenting the field in Bullet Train's light theme's showcase previews.


chore: update Fastlane version to latest

Description
This PR comes as an attempt to fix the latest ios beta failures due to Could not install WWDR certificate. Starting first with the easy route by updating to latest fastlane, if this doesn't work, happy to take the long route as well 😄

PR Checklist

[ ] I have tested my changes on iOS and Android.
[x] I hid my changes behind a feature flag, or they don't need one.
[x] I have included screenshots or videos, or I have not changed the UI.
[x] I have added tests, or my changes don't require any.
[x] I added an app state migration, or my changes do not require one.
[x] I have documented any follow-up work that this PR will require, or it does not require any.
[x] I have added a changelog entry below, or my changes do not require one.

To the reviewers 👀

[ ] I would like at least one of the reviewers to run this PR on the simulator or device.

Changelog updates
Changelog updates

Cross-platform user-facing changes

iOS user-facing changes

Android user-facing changes

Dev changes

update fastlane to latest - mounir

Need help with something? Have a look at our docs, or get in touch with us.

I triggered a build - let's hope it fixed the issue


lv() and cv2() raising an error for too short spike trains

Currently the functions lv() and cv2() in statistics raise an error if the spike trains in input has less three spikes. It might be preferable to replace this with a warning message and returning NaN or None instead (suggested in #108 ). For example this avoids to break for loops over list of spike trains.

I think this is a very general design decision to make: The safe solution is to error, the often more practical solution is to nan. Would it make sense to have functions such as the ones mentioned here error on default, but optionally only warn and return nan's?

I agree with Michael's suggestion - have error as default, but add an optional argument to return NaN, so that the user has to be explicitly aware of the choice. (This means the error message needs to include information about the NaN option)

@EmanueleLucrezia can you fix this issue? Thanks!

I can try to adapt the code from here: https://github.com/NeuralEnsemble/elephant/pull/171/files, where the same issue arose for empty spike trains and an argument 'with_nan' was introduced


Need to update the dimension of the blog post cover image

https://www.loginradius.com/engineering/blog/index-in-mongodb/
The cover image for the above blog is of not recommended size, You can upload a new image or update the cover image of the above mention blog to 3:2 ratio and minimum size to 1200px:800px

Hi @puneetsingh24 ,
I would like to fix this issue. Should I replace the Cover image with MongoDB logo image of required size?

Assigned you @hastagAB . MongoDB logo with a nice background will work.
And LoginRadius is also giving swags to people who will be contributing, so please make sure to read our blog and submit your info to get free goodies.
https://www.loginradius.com/engineering/page/hacktoberfest2020

Hi @puneetsingh24  is this issue still on? Would like to work on it.

Hi @puneetsingh24, I would like to work on this issue

Hi @puneetsingh24, this issue is open? Would like to work.

Issue has been done


Disable cloudbees jenkins builds, using travis instead

NetflixOSS » SimianArmy » SimianArmy-pull-requests #64 FAILURE
Looks like there's a problem with this pull request


Extension view filter missing some suggestions

Issue Type: Bug
Sidebar extension view filter in the Insiders release does not behave properly:, some entries are not properly suggested. For example, "@inst" should suggest "@installed" and "@sort:installs", it works fine in the latest Code release but the last 3-4 Insiders releases only show the "@sort:" option.
Note, if I type "@installed" then the extension list is filtered correctly.

VS Code version: Code - Insiders 1.29.0-insider (931c22033db3cc8d5dff265889307ed4076ac2d3, 2018-10-12T05:17:15.739Z)
OS version: Windows_NT x64 10.0.17763

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz (8 x 2808)

GPU Status
2d_canvas: enabledchecker_imaging: disabled_offflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwarerasterization: enabledvideo_decode: enabledvideo_encode: enabledwebgl: enabledwebgl2: enabled

Memory (System)
31.86GB (15.59GB free)

Process Argv

Screen Reader
no

VM
0%

This also affects the settings editor (UI).

This happens in the new settings editor search as well. Try typing @i. In stable 1.28, you will still see 2 results, but in Insiders you see none. cc @roblourens
@jrieken This issue got introduced with the commit https://github.com/Microsoft/vscode/commit/d00e5cb041fbbb610851acc572db9969201557bf#diff-6dba103c08842c74d9919a87c5561c11

Do these providers use overwriteBefore/After?

Yeah, looks like they do...

@ramya-rao-a @roblourens Where are those providers implemented?

Nevermind, found it: https://github.com/Microsoft/vscode/blob/121c60f64af7f6b2e4f489a1cf2c0881d2a193dd/src/vs/workbench/parts/codeEditor/electron-browser/suggestEnabledInput.ts#L185


⚠ Carbubu has degraded performance

In 098cc9d, Carbubu (https://carbubu.fr) experienced degraded performance:

HTTP code: 200
Response time: 3257 ms

Resolved: Carbubu performance has improved in d6f7e97 after 12 minutes.


Left side of IsoTriangle does not render for the first triangle

Version

Phaser Version: 3.23.0

Operating system:  macOS 10.15

Browser: Chrome

Description
When adding an IsoTriangle, the first one is missing the left-side. Any triangles added afterwards render OK.
Example Test Code
I've made a codesandbox here:
https://codesandbox.io/s/phaser-isotriangle-bug-w9q4h?file=/package.json
If you comment out the first triangle, the 2nd triangle will be missing its left side.
This is also reproducible with the IsoTriangle example from the Phaser website
https://labs.phaser.io/edit.html?src=src/game objects/shapes/iso triangle.js&v=3.23.0

Thank you for submitting this issue. We have fixed this and the fix has been pushed to the master branch. It will be part of the next release. If you get time to build and test it for yourself we would appreciate that.


Azure Application Insights showing duplicate entries

We are using Azure Function App, Azure SQL server and API management a very simply solution and we are reporting all our telemetry back to Application Insights. Right now we are trying to review some performance issue and what we are observing is that Application Insights is showing duplicate records (screenshot below). Anyone know how we can avoid this duplicate entries and have a clean hierarchical flow of telemetry data?

UPDATE: 01/05/2022: We created a new Application Insights Instance and just created out of the box Function App From Azure portal and attached this instance of App Insights (no custom code nothing just sample code) and still we see DUPLICATE telemetry for that new function App as shown below from the App Insights logs:

Also posted the same issue here:  https://stackoverflow.com/questions/70475470/azure-application-insights-showing-duplicate-entries

If you're running the application in Azure Functions, please file an issue here.

hello @cijothomas this issue is not alone with Function Apps, this is happening across all azure service we have on board .. and Telemetry for all these Azure components is  getting duplicated, I just posted my question with simple one service (function app in this case) but in my environment I have SQL Server logs, Service bus, functions apps, etc.. and Telemetry is duplicated for everything.

Can you share a non-function repro app showing this behavior for us to review if the config is correct?
Also check this FAQ: https://docs.microsoft.com/en-us/azure/azure-monitor/app/telemetry-channels#does-the-application-insights-channel-guarantee-telemetry-delivery-if-not-what-are-the-scenarios-in-which-telemetry-can-be-lost
Additionally, the duplication is possible in backend as well. (you'll need to open support ticket to get someone to investigate that)

Same issue for me : Duplication of log entries in application insights.
I'm using bot framework composer and i have configured the instrumentation key and connection string in advanced app setting json and publishing profile.

Hi, This issue still persists any possible resolution?

Hi,
Actually I face this still. I double checked with my Dev resources but when
it comes to prod resource, still I'm facing the same problem.
On Fri, 24 Jun 2022, 14:52 Sudheerkumar Muramshetty, <
@.***> wrote:

Hi, This issue still persists any possible resolution?
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/ApplicationInsights-dotnet/issues/2509#issuecomment-1165381648,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AY2ST4X5SM3P2JCP3ALAF23VQV45ZANCNFSM5LKLGVIQ
.
You are receiving this because you commented.Message ID:
@.***>

Same problem here for nearly a year. All logs are duplicating.

If your using workspace application insights, refer this https://docs.microsoft.com/en-us/answers/questions/775202/workspace-based-app-insights-vs-diagnostic-setting.html
Usage of both both diagnostic settings and workspace-based Application Insights cause double data

I can confirm this behavior in my case as well (no Azure function, but a customized Dynamics 365 Finops instance). Especially parallelized (10+ Threads) tasks emit the effect. There is a lot of data, that doesn't get duplicated, that tends not to run parallelized as well. We might have a synchronization problem here. Unfortunately, this also means that I have not yet been able to explicitly trigger the effect on my installation.

Our application have duplicate logs & custom events in our Application Insights (running in workspace-based mode with another Log Analytics). I confirmed that we don't have a diagnostic setting that forwards the logs.
We are running on Java and are using 'com.microsoft.azure:applicationinsights-runtime-attach:3.3.1' & 'com.microsoft.azure:applicationinsights-core:2.6.4'. But still want to share here. Maybe this isn't an agent specific problem.

I'm having a similar issue where I see the same log twice in an Azure Function slot. One log has set the SessionId and ParentId while the other does not.
Also noticed that the SDKVersion seems to be different in the telemetry:

I wonder what the problem is since I have the same code deployed to two different slots (Prod and PPE), and only the PPE slot is having this issue.

Does anyone know why this is happening? I have the same problem, but the only duplicated entries are coming from exceptions

Same issue happening for me - Logs from APIM being duplicated. No diagnostic setting present.


Integration tests for tools

Integration tests for basic tools: setuptools, venv and git.
PR enabled to check all tests on the CI server, DO NOT MERGE yet.
Update versions for CI (GitHub Actions and pre-commit).

Codecov Report

Merging #43 (5c3bab9) into main (932e250) will increase coverage by 30.49%.
The diff coverage is 85.71%.

@@             Coverage Diff             @@
##             main      #43       +/-   ##
===========================================
+ Coverage   60.97%   91.46%   +30.49%
===========================================
  Files          13       13
  Lines         574      586       +12
===========================================
+ Hits          350      536      +186
+ Misses        224       50      -174

Impacted Files
Coverage Δ

incipyt/tools/git.py
89.18% <85.71%> (+89.18%)
:arrow_up:

incipyt/_internal/templates.py
89.37% <0.00%> (+0.62%)
:arrow_up:

incipyt/commands.py
93.10% <0.00%> (+24.13%)
:arrow_up:

incipyt/_internal/sanitizers.py
76.92% <0.00%> (+76.92%)
:arrow_up:

incipyt/__main__.py
85.13% <0.00%> (+85.13%)
:arrow_up:

incipyt/tools/setuptools.py
97.91% <0.00%> (+97.91%)
:arrow_up:

incipyt/signals.py
100.00% <0.00%> (+100.00%)
:arrow_up:

incipyt/tools/base.py
100.00% <0.00%> (+100.00%)
:arrow_up:

incipyt/tools/venv.py
100.00% <0.00%> (+100.00%)
:arrow_up:

... and 1 more

Continue to review full report at Codecov.

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

first integration tests failing on windows CI is due to non platform-agnostic path matching at testing.py:23
(diff is + {'my_project\\.env\\pyvenv.cfg'} which should be ignored)


Feature: Add a dynamic rule

Add a class DynamicRule which receives a closure on initializing. The validation is done by this closure.
This easily allows to use custom logic for validation without creating a new class, which is especially useful when the validation depends on other circumstances in the validating scope.
Contains simple tests for DynamicRule.

[Current coverage][cc-pull] is 88.76%

Merging [#128][cc-pull] into [master][cc-base-branch] will decrease coverage by 0.07%

@@             master       #128   diff @@
==========================================
  Files            24         25     +1
  Lines           421        436    +15
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits            374        387    +13
- Misses           47         49     +2
  Partials          0          0

Powered by Codecov. Last updated by [8f224ab...6b07ce8][cc-compare]
[cc-base-branch]: https://codecov.io/gh/jpotts18/SwiftValidator/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/jpotts18/SwiftValidator/compare/8f224aba83e67ad58157bd18dad1b7e212e583b5...6b07ce8a2966141bd962af2671dbe0e2b5559f62
[cc-pull]: https://codecov.io/gh/jpotts18/SwiftValidator/pull/128?src=pr


Add support for androidx.sqlite.db

Currently the android.database.sqlite package is supported. This needs to be expanded to also include androidx.sqlite.db.
After adding support for androidx.sqlite.db the libraries below will be able to utilize Batch Light

SQLDelight
Room

To implement there should be a new androidsqlitesupport package that has an implementation of Binder and BinderConfig. The new package should be documented and have 100%  test coverage.

Adde in https://github.com/YelloCo/Batchlight/pull/4


Reusing spine atlas frames

Hi!
Is there any way to use spine atlas frames as Phaser images? I know there's atlas image loaded into cache and I can use it but it doesn't contain any frames.

There's also an SpineCache available that contains Spine's .atlas file in which you should be able to extract the frame from.
You can access this with:
var atlasData = this.game.cache.getSpine(<spineName>).atlas;

You can check out spine.Atlas and spine.AtlasReader on how to extract data from this file

Does this.game.cache.getSpine(<spineName>).atlas; suppose to contain just a string?

I've managed to get in working. For people looking for similar solution this is what I did (basically rewrote createSpine fucntion):
https://gist.github.com/lukz/0867e9f1875f9771873fc540862e6179

where does addSpineCache() get called?


#170 Fix wrong url to examples

@alex-semenyuk/z this pull request is too small, just 2 lines changed (less than 10), there will be no formal code review, see §53 and §28; in the future, try to make sure your pull requests are not too small; @yegor256/z please review this and merge or reject

@alex-semenyuk/z this pull request is too small, just 2 lines changed (less than 10), there will be no formal code review, see §53 and §28; in the future, try to make sure your pull requests are not too small; @yegor256/z please review this and merge or reject

@alex-semenyuk thanks!

@alex-semenyuk thanks!

Job gh:yegor256/eo#171 is not assigned, can't get performer

Job gh:yegor256/eo#171 is not assigned, can't get performer


Separate Libraries

Steps that need to be done:

[ ] 1. Make the new repository
[ ] 2. Create a nuget package
[ ] 3. Make the migration in BlastPDF

I have some ideas for each of the extra libraries that I want to do but they aren't related to BlastPDF in anyway.
Also just for the ease of it we can move the BlastType stuff as well.
BlastIMG  -> SharperImage
BlastType -> SharpTTF
For SharperImage, I want to add image processing pipelines and be able to output / convert between formats
For SharpTTF, I just feel like it can live as it's own thing. I would definitely want to be able to produce TTF files with it and possibly a GUI font designer

BlastIMG was moved to SharperImage completely.
Working on moving BlastSharp to MyLib. Pretty close to being good
BlastTTF will live for a while longer until I can actually parse and query against the font file

BlastSharp was moved to MyLib just BlastType left to move over!


Clicking on 'view my ts webpage' in the returned consultant results should bring user to the consultants webpage

Expected behavior
After searching for a consultant, when the results are displayed, if user clicks on the 'view my ts webpage' they should be brought to the consultants webpage.

Actual behavior
After searching for a consultant, when the results are displayed, if user clicks on the 'view my ts webpage', the system just selects the consultant.

Steps to reproduce behavior
Search for a consultants. When results are displayed, click on 'view my ts webpage'.

On it: TST-128

7-31 SH  - Clicking on the view my TS page is now going to our current sitecore ts.com vs the new big commerce consultant webpage:

Jared let us know in Slack that he was going to update the API URLs to reflect the correct environment.
Currently, we get URLs like this:
https://www.tastefullysimple.com/web/lleichinger

Confirmed that I'm still getting tastefullysimple.com URLs from the Tech Sandbox as of this morning.

@monicakarnes I believe this one should not be assigned to me. Per our standup yesterday, there are no code modifications needed on our end. The API response values need to be updated.

8-5 SH - Now getting a 404 error page when clicking the view my TS page link.
https://us04web.zoom.us/j/78041793840?pwd=bVJxLzNZWmpOa2JwMWkxUEkwQUhhUT09

This was deployed to the Tech Sandbox.

8/6 @wbyrnetx I think you updated the wrong bug. Looks like you meant to update #231 for the BBOK item vs this one that is for the cons webpage link. I am still getting the 404 error on this.

Clicking the View My TS Webpage should affiliate the user with the consultant.

We've identified the issue here and are working on it.

Created a ticket for this 404 issue: TST-168

8-17 SH - Fixed.


Cannot index folder appeared in .gitignore

A demo project here:
https://github.com/k8w/vscode-gitignore-problem-example
Why ignore folder should be index?
My project structure:
|- __shared
|- frontend
    |- shared  // a symlink to ../__shared
|- backend
    |- shared  // a symlink to ../__shared

In order to not submit a symlink, .gitignore is:
/frontend/shared
/backend/shared

And when I open frontend or backend via vscode, shared cannot be indexed by tsimporter

There is tsimporter.filesToExclude already, no need to exclude folders appeared in .gitignore automatically.

It seems like vscode.workspace.findFiles ignored those files.
Have logged a issue here https://github.com/Microsoft/vscode/issues/36617


Support selecting packages

Currently test runner will run all tests within a Scarb workspace. We should provide a mechanism for selecting specific packages using globs, similarly to cargo test.
Useful:

scarb metadata package filters
glob can be used for that, additionally

Duplicate of #250


How often do researchers generate graphs outside of the OpenSAFELY pipeline?

We know that some people only use the OpenSAFELY pipeline to generate CSVs and then generate the graphs locally, so they can have a faster feedback loop and use newer libraries. I expect that working with released (not published) files will not be possible in Codespaces, so they will need to continue to use local development environments for this.
It would be good to find out how many researchers this affects. We could do this by counting the number of workspaces that have released CSVs compared to workspaces that have released images.
Timebox: 2 hours

From Job Server ReleaseFiles, categorise by extension:
extension_categories = {
    'html':"report",
    'png':"image",
    'csv':"tabular",
    'json':"tabular",
    'jpeg':"image",
    'txt':"tabular",
    'svg':"image",
    'jpg':"image",
    'gz':"other",
    'ods':"tabular",
    'log':"other",
    'ipynb':"report",
    'pdf':"report",
    'db':"other",
    'eps':"image",
    'tiff':"image",
    'csv#':"tabular",
    'xls':"tabular"}

Then group by project id, file category, count number of files. For each project, calculate the proportion of "finished" (image and report) files of total files released (excluding "other"):
count    92.000000
mean      0.328568
std       0.322190
min       0.000000
25%       0.000000
50%       0.247652
75%       0.542579
max       1.000000

So you could say that on average, 25% of the released outputs of a project are those that could have been produced post-release. Now, this is clearly a bit wrong because tabular data itself is an output that may be used in a manuscript, and there will be instances where both a tabular and graphical representation of the same data are released.
27 (of 92) projects have only ever released tabular data.
Any one got any more ideas how this could be analysed?

I think breaking down over time could be helpful.
I would expect more images to have been released in early OS life, and less as time has gone on (based on the assumption that users have realised they don't need to, and its a PITA to do so).

What's the dotted line?
Am also suspicious we can conclude much from the downward trend, because we've been so much quieter for the last 6mo?


decodeMessageVersion takes 3 positional arguments but 4 were given. Cannot connect to the agent using SNMP Walk

I have been getting this issue whilst running both snmpsim and normal snmp services. While running snmp sim invoking the
snmpsim-command-responder --data-dir=./data --agent-udpv4-endpoint=<IP_ADDRESS>:1024
The server runs, also invoking the responder.py file with related commands successfully opens the service,
While using snmpwalk or cmd2rec however the server side crashes with the provided image. I am guessing its a dependancy issue that i couldnt get a hold of. I am running python 3.10.6 with the latest versions of whatever software is required.

Solved the  issue, the problem was installation. I thought just an installation would do the trick but i guess you do need a venv.
If you can however answer how i can set oid values to selected oid that'd be great.

Running the server and trying to access the oid by snmpset returns me No such Instance error. I have also tried launching it with variation module options to create a db for the changes to no avail.

Got the same error:

Installed with:
$ virtualenv venv $ source venv/bin/activate $ pip install snmpsim
Running local or inside a docker container. Running with:
snmpsimd.py --data-dir=./data --agent-udpv4-endpoint=<IP_ADDRESS>:1024

I see similar problems on macOS with python3.11 from Homebrew when executing snmprec:
python3 -m venv venv
. venv/bin/activate
pip install snmpsim

snmprec.py ...

Also tried using python3.8 from Homebrew, but same issue:
python3.8 -m venv venv
. venv/bin/activate
pip install snmpsim

snmprec.py ...

I eventually gave up and just launched an Ubuntu 22.04 container in Docker and used apt-get install snmpsim to get something functional.

I see similar problems on macOS with python3.11 from Homebrew when executing snmprec:
python3 -m venv venv
. venv/bin/activate
pip install snmpsim

snmprec.py ...

Also tried using python3.8 from Homebrew, but same issue:
python3.8 -m venv venv
. venv/bin/activate
pip install snmpsim

snmprec.py ...

I eventually gave up and just launched an Ubuntu 22.04 container in Docker and used apt-get install snmpsim to get something functional.

please, can you show your Dockerfile and how to run the container to make it work?

There wasn't a Dockerfile involved, it was just an interactive container so I could grab a few snmprec recordings:
docker image pull ubuntu:22.04
docker run -it --rm ubuntu:22.04

apt-get update
apt-get install snmpsim
snmprec ...

docker cp <containerid>:/<snmprec_file> ./<snmprec_file>

For those that are experiencing this issue, do the tutorial step by step. You need to run it on a venv with the right dependancies.

Can you point at where the tutorial is located?
Trying to navigate to http://snmplabs.com/snmpsim/ as linked in the README.md (https://github.com/etingof/snmpsim#documentation) leads to a redirect that is blocked by uBlock Origin in my browser, which doesn't inspire confidence...

https://snmplabs.thola.io/snmpsim/

Keep in mind that while this tool is good for just serverside applications its not very useful for customization for individual devices. I would recommend using https://github.com/delimitry/snmp-server alongside docker to achieve multiple agent support whilst being able to customize the codebase to your needs.

What part of the following does not match https://snmplabs.thola.io/snmpsim/quickstart.html#installation?
python3 -m venv venv
. venv/bin/activate
pip install snmpsim

snmprec.py --agent-udpv4-endpoint=w.x.y.z:161 --community=xxx --start-object=<IP_ADDRESS>.<IP_ADDRESS> --stop-object=<IP_ADDRESS>.<IP_ADDRESS> --output-file=foo
...
ERROR TypeError: decodeMessageVersion.<locals>.<lambda>() takes 3 positional arguments but 4 were given;

Am I missing something?

Its been a while since ive solved the issue my memory doesnt serve me well but i think i installed it manually from this depo and not from snmpsim. I remember seeing that the install of the snmpsim library is not up to date. If this is not the case i would suggest using ChatGPT to debug as it pointed out where the dependency issues were.

So the problem appears to be the latest version of pyasn1 (0.5.0) that gets installed if you just pip install snmpsim is not compatible.
The fix appears to be manually install the older 0.4.8 release first:
python3 -m venv venv
. venv/bin/activate
pip install pyasn1==0.4.8
pip install snmpsim

Has this solved the issue?

If you use the forked package snmpsim-lextudio and https://pysnmp.com, you might find there are less troubles.
More details can be found in https://github.com/etingof/pysnmp/issues/429

If you use the forked package snmpsim-lextudio and https://pysnmp.com, you might find there are less troubles.
More details can be found in etingof/pysnmp#429

Yes, this seems to work for me w/o any of the previous issues, thank you!
python3 -m venv venv
. venv/bin/activate
pip install snmpsim-lextudio

snmpsim-record-commands --agent-udpv4-endpoint=w.x.y.z:161 --community=xxx --start-object=<IP_ADDRESS>.<IP_ADDRESS> --stop-object=<IP_ADDRESS>.<IP_ADDRESS> --output-file=foo

So the problem appears to be the latest version of pyasn1 (0.5.0) that gets installed if you just pip install snmpsim is not compatible.
The fix appears to be manually install the older 0.4.8 release first:
python3 -m venv venv
. venv/bin/activate
pip install pyasn1==0.4.8
pip install snmpsim

Thank you so much, this worked! So the problem is with pyasn1 (0.5.0), just need to downgrade the version, for anyone who still having issues.

A summary of the issue is,

@Scrafya for some reason installed pyasn1 0.5.0-rc, and that broke pysnmp and snmpsim. By switching to a virtual environment, probably that environment only pulled down production pyasn1 (0.4.x at that time), so the issue was resolved and closed.
pyasn1 0.5.0 was released by its new maintainers a few days ago, which in turn breaks more pysnmp 4.4.x users like @EricChandia and @norrisjeremy. The solution you found is of course to downgrade pyasn1 to 0.4.x.

In the long run, we will see what happens on pyasn1 side. The maintainers are so new that they probably need more time to learn enough about the package.
If you like, you can read https://github.com/etingof/pysnmp/issues/429 to learn more about the entire ecosystem today. Sites like https://snmplabs.thola.io/snmpsim/ are rather problematic as their owners didn't really want to take over the bits. You might check out https://pysnmp.com and the *-lextudio packages maintained by my team.