Provide a static helper to list known boards

This PR is a resolution for #122.
It exposes a new static method named listKnownBoards using the keys from the byName object which is keyed by the board name. I went with this over listBoards as I figured that might be useful in future as an instance method which also includes things such as custom boards.
I also added aliasing to remove the duplication mentioned in the stream today, and verified that both names come back appropriately in the resulting call to listKnownBoards. It might be that we don't want the aliases to come back in this list though, if so just let me know and I can tweak it to omit them.
Here's an example output:
> avr.listKnownBoards()
[ 'uno',
  'micro',
  'imuduino',
  'leonardo',
  'arduboy',
  'feather',
  'little-bits',
  'blend-micro',
  'nano',
  'duemilanove168',
  'duemilanove328',
  'tinyduino',
  'tinduino',
  'bqZum',
  'mega',
  'adk',
  'sf-pro-micro',
  'pro-mini',
  'qduino',
  'pinoccio',
  'lilypad-usb',
  'yun' ]

Feel free to make any changes you think should be made, or just let me know and I can make them as needed :D!

As a side note, the byName property is a little redundant and could probably be removed in future in favour of module.exports = boardLookupTable().

Coverage increased (+1.04%) to 45.161% when pulling 58a6c855fc2d16b311d338591df8a0d457f82522 on zackehh:issue-122 into 2e4ddc417be1fb461bc960d5082b1255611e10c9 on noopkat:master.

@zackehh yayyy!! Thank you for turning this around so quick!
I agree with you on the redundant byName prop - I used to have a couple of different mappings that were removed. Could you be so kind as to refactor that out (using your suggested approach) as well? Would clean things up nicely! ☺

also - I am going to mull over the alias filtering for the outputted list. Not sure what is the best call, but I'll let you know later today 👍

@noopkat sure thing, I'll also push the byName prop change when you decide so as to reduce the commit noise 🔔 Have a great Sunday!

@zackehh hai so I think we should filter out aliases from the returned list, if it's not too much trouble. I know it's more work for you - apologies

@noopkat no problemo! I've pushed that change, let me know if you need anything else changing!

Coverage increased (+0.7%) to 44.84% when pulling 8e2b694f0062ebb804f23d1fea62384953f63b8a on zackehh:issue-122 into 2e4ddc417be1fb461bc960d5082b1255611e10c9 on noopkat:master.

thanks again, @zackehh ! 🙇♀


feat: add debug flag for image loading. fixes #272

@adnan-wahab Please make sure your PR's are in good shape and clean before submitting.


discord: clicking links does not open them in browser

Describe the bug
clicking on links posted to discord chats does not open the links in any browser.
Other people on different distros have reported this same bug and some have had success fixing it by installing xdg-utils (see this issue).
However installing xdg-utils on nixos does not solve the issue.
To Reproduce
Steps to reproduce the behavior:

install discord & firefox
click on link in any discord chat, or try to view original image on an image
browser does not open

Expected behavior
browser opens with clicked link
Notify maintainers
@ldesgoui @MP2E @tadeokondrak
Metadata

system: "x86_64-linux"
host os: Linux 5.4.87, NixOS, 20.09.2538.0cfd08f4881 (Nightingale)
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.3.10
channels(sage): ""
channels(root): "nixos-20.09.2538.0cfd08f4881, nixos-unstable-21.03pre262471.ad97cdf81d1"
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos

Maintainer information:
# a list of nixpkgs attributes affected by the problem
attribute: discord
# a list of nixos modules affected by the problem
module:

That's weird, works by default for me, maybe desktop settings are wrong?

That's weird, works by default for me, maybe desktop settings are wrong?

On other distros the results are very mixed too, I have a friend who uses nixos and has this same issue though. We do both have kde installed, I use DWM and he uses KDE. Dunno what other info might be relevant.

On other distros the results are very mixed too, I have a friend who uses nixos and has this same issue though. We do both have kde installed, I use DWM and he uses KDE. Dunno what other info might be relevant.

Oh here we go, I ran strace Discord 2>&1 | grep discordapp and tried to open an image and got
xdg-open: no method available for opening 'https://cdn.discordapp.com/attachments/...'

However running xdg-open  with the url it gave opens the image in firefox fine

Oh here we go, I ran strace Discord 2>&1 | grep discordapp and tried to open an image and got
xdg-open: no method available for opening 'https://cdn.discordapp.com/attachments/...'

However running xdg-open  with the url it gave opens the image in firefox fine

Just a guess, since I don't use KDE, but discord has xdg-utils provided to it by its wrapper as far as I'm aware, but KDE might have its own xdg-open binary with different logic to select the browser.

Just a guess, since I don't use KDE, but discord has xdg-utils provided to it by its wrapper as far as I'm aware, but KDE might have its own xdg-open binary with different logic to select the browser.

Interesting, I didn't realize the wrapper provided xdg-utils. Anyways I've uninstalled kde and this didn't solve the issue so... I'll keep on looking but it may not be kde related.

Interesting, I didn't realize the wrapper provided xdg-utils. Anyways I've uninstalled kde and this didn't solve the issue so... I'll keep on looking but it may not be kde related.

Just deleted my .config/discord/ folder to see if it's related to that, it also failed to open my browser to detect a discord account on first boot.

Just deleted my .config/discord/ folder to see if it's related to that, it also failed to open my browser to detect a discord account on first boot.

Just a guess, since I don't use KDE, but discord has xdg-utils provided to it by its wrapper as far as I'm aware, but KDE might have its own xdg-open binary with different logic to select the browser.

how does discord provide xdg-utils with it's wrapper? I don't see it in the code, the wrapper mostly provides libraries, it doesn't touch the path which is how xdg-utils would be found because it's a binary not a library.

Just a guess, since I don't use KDE, but discord has xdg-utils provided to it by its wrapper as far as I'm aware, but KDE might have its own xdg-open binary with different logic to select the browser.

how does discord provide xdg-utils with it's wrapper? I don't see it in the code, the wrapper mostly provides libraries, it doesn't touch the path which is how xdg-utils would be found because it's a binary not a library.

Here, I dumped the strace to a file and found more relevant lines
poll([{fd=12, events=POLLIN}, {fd=13, events=POLLIN}, {fd=44, events=POLLIN}, {fd=45, events=POLLIN}], 4, 12554XPCOMGlueLoad error for file /nix/store/wnxlbpsmfw54v61fhw3rgpna8pvbfcpb-firefox-unwrapped-84.0.1/lib/firefox/libmozgtk.so:
/nix/store/33idnvrkvfgd5lsx2pwgwwi955adl6sk-glibc-2.31/lib/libc.so.6: version `GLIBC_2.32' not found (required by /nix/store/l2isbpjy5zdalr6xjgxaniqwkbf9b2gz-glib-2.66.4/lib/libglib-2.0.so.0)
Couldn't load XPCOM.
/nix/store/f4q2jcvxrpgrrxkdm0l0ba61zzg1nsmp-xdg-utils-1.1.3/bin/xdg-open: line 881: x-www-browser: command not found
XPCOMGlueLoad error for file /nix/store/wnxlbpsmfw54v61fhw3rgpna8pvbfcpb-firefox-unwrapped-84.0.1/lib/firefox/libmozgtk.so:
/nix/store/33idnvrkvfgd5lsx2pwgwwi955adl6sk-glibc-2.31/lib/libc.so.6: version `GLIBC_2.32' not found (required by /nix/store/l2isbpjy5zdalr6xjgxaniqwkbf9b2gz-glib-2.66.4/lib/libglib-2.0.so.0)
Couldn't load XPCOM.
/nix/store/f4q2jcvxrpgrrxkdm0l0ba61zzg1nsmp-xdg-utils-1.1.3/bin/xdg-open: line 881: iceweasel: command not found
/nix/store/f4q2jcvxrpgrrxkdm0l0ba61zzg1nsmp-xdg-utils-1.1.3/bin/xdg-open: line 881: seamonkey: command not found
/nix/store/f4q2jcvxrpgrrxkdm0l0ba61zzg1nsmp-xdg-utils-1.1.3/bin/xdg-open: line 881: mozilla: command not found
/nix/store/f4q2jcvxrpgrrxkdm0l0ba61zzg1nsmp-xdg-utils-1.1.3/bin/xdg-open: line 881: epiphany: command not found
/nix/store/f4q2jcvxrpgrrxkdm0l0ba61zzg1nsmp-xdg-utils-1.1.3/bin/xdg-open: line 881: konqueror: command not found
/nix/store/8ri2cwyw0xgwfx63r6h472f50xdr7cdw-chromium-unwrapped-87.0.4280.141/libexec/chromium/chromium: /nix/store/33idnvrkvfgd5lsx2pwgwwi955adl6sk-glibc-2.31/lib/libc.so.6: version `GLIBC_2.32' not found (required by /nix/store/l2isbpjy5zdalr6xjgxaniqwkbf9b2gz-glib-2.66.4/lib/libglib-2.0.so.0)
/nix/store/8ri2cwyw0xgwfx63r6h472f50xdr7cdw-chromium-unwrapped-87.0.4280.141/libexec/chromium/chromium: /nix/store/33idnvrkvfgd5lsx2pwgwwi955adl6sk-glibc-2.31/lib/libc.so.6: version `GLIBC_2.32' not found (required by /nix/store/69b2zfzyrc5jk9470mzvchfrni9yrwv1-libpulseaudio-14.0/lib/libpulse.so.0)
/nix/store/8ri2cwyw0xgwfx63r6h472f50xdr7cdw-chromium-unwrapped-87.0.4280.141/libexec/chromium/chromium: /nix/store/33idnvrkvfgd5lsx2pwgwwi955adl6sk-glibc-2.31/lib/libc.so.6: version `GLIBC_2.32' not found (required by /nix/store/rqrklqsvw4ydpcg5kdcvn506fhcbqxk2-glibc-2.32-10/lib/librt.so.1)
/nix/store/8ri2cwyw0xgwfx63r6h472f50xdr7cdw-chromium-unwrapped-87.0.4280.141/libexec/chromium/chromium: /nix/store/33idnvrkvfgd5lsx2pwgwwi955adl6sk-glibc-2.31/lib/libc.so.6: version `GLIBC_2.32' not found (required by /nix/store/86lr3wqvpf0zg3sxr9kc0y4yw972p98r-avahi-0.8/lib/libavahi-common.so.3)
/nix/store/8ri2cwyw0xgwfx63r6h472f50xdr7cdw-chromium-unwrapped-87.0.4280.141/libexec/chromium/chromium: /nix/store/33idnvrkvfgd5lsx2pwgwwi955adl6sk-glibc-2.31/lib/libc.so.6: version `GLIBC_2.32' not found (required by /nix/store/4i7s80g57bqha7nna9yqcr50my0fva80-systemd-247.2/lib/libsystemd.so.0)
/nix/store/8ri2cwyw0xgwfx63r6h472f50xdr7cdw-chromium-unwrapped-87.0.4280.141/libexec/chromium/chromium: /nix/store/33idnvrkvfgd5lsx2pwgwwi955adl6sk-glibc-2.31/lib/libc.so.6: version `GLIBC_2.32' not found (required by /nix/store/69b2zfzyrc5jk9470mzvchfrni9yrwv1-libpulseaudio-14.0/lib/pulseaudio/libpulsecommon-14.0.so)
/nix/store/8ri2cwyw0xgwfx63r6h472f50xdr7cdw-chromium-unwrapped-87.0.4280.141/libexec/chromium/chromium: /nix/store/33idnvrkvfgd5lsx2pwgwwi955adl6sk-glibc-2.31/lib/libc.so.6: version `GLIBC_2.32' not found (required by /nix/store/zwi0s4xqknfpd5si3pr0c3ijx4kqanhv-gcc-10.2.0-lib/lib/libgomp.so.1)
/nix/store/8ri2cwyw0xgwfx63r6h472f50xdr7cdw-chromium-unwrapped-87.0.4280.141/libexec/chromium/chromium: /nix/store/33idnvrkvfgd5lsx2pwgwwi955adl6sk-glibc-2.31/lib/libc.so.6: version `GLIBC_2.32' not found (required by /nix/store/l2isbpjy5zdalr6xjgxaniqwkbf9b2gz-glib-2.66.4/lib/libglib-2.0.so.0)
/nix/store/8ri2cwyw0xgwfx63r6h472f50xdr7cdw-chromium-unwrapped-87.0.4280.141/libexec/chromium/chromium: /nix/store/33idnvrkvfgd5lsx2pwgwwi955adl6sk-glibc-2.31/lib/libc.so.6: version `GLIBC_2.32' not found (required by /nix/store/69b2zfzyrc5jk9470mzvchfrni9yrwv1-libpulseaudio-14.0/lib/libpulse.so.0)
/nix/store/8ri2cwyw0xgwfx63r6h472f50xdr7cdw-chromium-unwrapped-87.0.4280.141/libexec/chromium/chromium: /nix/store/33idnvrkvfgd5lsx2pwgwwi955adl6sk-glibc-2.31/lib/libc.so.6: version `GLIBC_2.32' not found (required by /nix/store/rqrklqsvw4ydpcg5kdcvn506fhcbqxk2-glibc-2.32-10/lib/librt.so.1)
/nix/store/8ri2cwyw0xgwfx63r6h472f50xdr7cdw-chromium-unwrapped-87.0.4280.141/libexec/chromium/chromium: /nix/store/33idnvrkvfgd5lsx2pwgwwi955adl6sk-glibc-2.31/lib/libc.so.6: version `GLIBC_2.32' not found (required by /nix/store/86lr3wqvpf0zg3sxr9kc0y4yw972p98r-avahi-0.8/lib/libavahi-common.so.3)
/nix/store/8ri2cwyw0xgwfx63r6h472f50xdr7cdw-chromium-unwrapped-87.0.4280.141/libexec/chromium/chromium: /nix/store/33idnvrkvfgd5lsx2pwgwwi955adl6sk-glibc-2.31/lib/libc.so.6: version `GLIBC_2.32' not found (required by /nix/store/4i7s80g57bqha7nna9yqcr50my0fva80-systemd-247.2/lib/libsystemd.so.0)
/nix/store/8ri2cwyw0xgwfx63r6h472f50xdr7cdw-chromium-unwrapped-87.0.4280.141/libexec/chromium/chromium: /nix/store/33idnvrkvfgd5lsx2pwgwwi955adl6sk-glibc-2.31/lib/libc.so.6: version `GLIBC_2.32' not found (required by /nix/store/69b2zfzyrc5jk9470mzvchfrni9yrwv1-libpulseaudio-14.0/lib/pulseaudio/libpulsecommon-14.0.so)
/nix/store/8ri2cwyw0xgwfx63r6h472f50xdr7cdw-chromium-unwrapped-87.0.4280.141/libexec/chromium/chromium: /nix/store/33idnvrkvfgd5lsx2pwgwwi955adl6sk-glibc-2.31/lib/libc.so.6: version `GLIBC_2.32' not found (required by /nix/store/zwi0s4xqknfpd5si3pr0c3ijx4kqanhv-gcc-10.2.0-lib/lib/libgomp.so.1)
/nix/store/f4q2jcvxrpgrrxkdm0l0ba61zzg1nsmp-xdg-utils-1.1.3/bin/xdg-open: line 881: google-chrome: command not found
/nix/store/f4q2jcvxrpgrrxkdm0l0ba61zzg1nsmp-xdg-utils-1.1.3/bin/xdg-open: line 881: www-browser: command not found
/nix/store/f4q2jcvxrpgrrxkdm0l0ba61zzg1nsmp-xdg-utils-1.1.3/bin/xdg-open: line 881: links2: command not found
/nix/store/f4q2jcvxrpgrrxkdm0l0ba61zzg1nsmp-xdg-utils-1.1.3/bin/xdg-open: line 881: elinks: command not found
/nix/store/f4q2jcvxrpgrrxkdm0l0ba61zzg1nsmp-xdg-utils-1.1.3/bin/xdg-open: line 881: links: command not found
/nix/store/f4q2jcvxrpgrrxkdm0l0ba61zzg1nsmp-xdg-utils-1.1.3/bin/xdg-open: line 881: lynx: command not found
/nix/store/f4q2jcvxrpgrrxkdm0l0ba61zzg1nsmp-xdg-utils-1.1.3/bin/xdg-open: line 881: w3m: command not found
xdg-open: no method available for opening 'https://cdn.discordapp.com/attachments/792502884164042783/797973612421971978/Normal_alt_2.png'

Here, I dumped the strace to a file and found more relevant lines
poll([{fd=12, events=POLLIN}, {fd=13, events=POLLIN}, {fd=44, events=POLLIN}, {fd=45, events=POLLIN}], 4, 12554XPCOMGlueLoad error for file /nix/store/wnxlbpsmfw54v61fhw3rgpna8pvbfcpb-firefox-unwrapped-84.0.1/lib/firefox/libmozgtk.so:
/nix/store/33idnvrkvfgd5lsx2pwgwwi955adl6sk-glibc-2.31/lib/libc.so.6: version `GLIBC_2.32' not found (required by /nix/store/l2isbpjy5zdalr6xjgxaniqwkbf9b2gz-glib-2.66.4/lib/libglib-2.0.so.0)
Couldn't load XPCOM.
/nix/store/f4q2jcvxrpgrrxkdm0l0ba61zzg1nsmp-xdg-utils-1.1.3/bin/xdg-open: line 881: x-www-browser: command not found
XPCOMGlueLoad error for file /nix/store/wnxlbpsmfw54v61fhw3rgpna8pvbfcpb-firefox-unwrapped-84.0.1/lib/firefox/libmozgtk.so:
/nix/store/33idnvrkvfgd5lsx2pwgwwi955adl6sk-glibc-2.31/lib/libc.so.6: version `GLIBC_2.32' not found (required by /nix/store/l2isbpjy5zdalr6xjgxaniqwkbf9b2gz-glib-2.66.4/lib/libglib-2.0.so.0)
Couldn't load XPCOM.
/nix/store/f4q2jcvxrpgrrxkdm0l0ba61zzg1nsmp-xdg-utils-1.1.3/bin/xdg-open: line 881: iceweasel: command not found
/nix/store/f4q2jcvxrpgrrxkdm0l0ba61zzg1nsmp-xdg-utils-1.1.3/bin/xdg-open: line 881: seamonkey: command not found
/nix/store/f4q2jcvxrpgrrxkdm0l0ba61zzg1nsmp-xdg-utils-1.1.3/bin/xdg-open: line 881: mozilla: command not found
/nix/store/f4q2jcvxrpgrrxkdm0l0ba61zzg1nsmp-xdg-utils-1.1.3/bin/xdg-open: line 881: epiphany: command not found
/nix/store/f4q2jcvxrpgrrxkdm0l0ba61zzg1nsmp-xdg-utils-1.1.3/bin/xdg-open: line 881: konqueror: command not found
/nix/store/8ri2cwyw0xgwfx63r6h472f50xdr7cdw-chromium-unwrapped-87.0.4280.141/libexec/chromium/chromium: /nix/store/33idnvrkvfgd5lsx2pwgwwi955adl6sk-glibc-2.31/lib/libc.so.6: version `GLIBC_2.32' not found (required by /nix/store/l2isbpjy5zdalr6xjgxaniqwkbf9b2gz-glib-2.66.4/lib/libglib-2.0.so.0)
/nix/store/8ri2cwyw0xgwfx63r6h472f50xdr7cdw-chromium-unwrapped-87.0.4280.141/libexec/chromium/chromium: /nix/store/33idnvrkvfgd5lsx2pwgwwi955adl6sk-glibc-2.31/lib/libc.so.6: version `GLIBC_2.32' not found (required by /nix/store/69b2zfzyrc5jk9470mzvchfrni9yrwv1-libpulseaudio-14.0/lib/libpulse.so.0)
/nix/store/8ri2cwyw0xgwfx63r6h472f50xdr7cdw-chromium-unwrapped-87.0.4280.141/libexec/chromium/chromium: /nix/store/33idnvrkvfgd5lsx2pwgwwi955adl6sk-glibc-2.31/lib/libc.so.6: version `GLIBC_2.32' not found (required by /nix/store/rqrklqsvw4ydpcg5kdcvn506fhcbqxk2-glibc-2.32-10/lib/librt.so.1)
/nix/store/8ri2cwyw0xgwfx63r6h472f50xdr7cdw-chromium-unwrapped-87.0.4280.141/libexec/chromium/chromium: /nix/store/33idnvrkvfgd5lsx2pwgwwi955adl6sk-glibc-2.31/lib/libc.so.6: version `GLIBC_2.32' not found (required by /nix/store/86lr3wqvpf0zg3sxr9kc0y4yw972p98r-avahi-0.8/lib/libavahi-common.so.3)
/nix/store/8ri2cwyw0xgwfx63r6h472f50xdr7cdw-chromium-unwrapped-87.0.4280.141/libexec/chromium/chromium: /nix/store/33idnvrkvfgd5lsx2pwgwwi955adl6sk-glibc-2.31/lib/libc.so.6: version `GLIBC_2.32' not found (required by /nix/store/4i7s80g57bqha7nna9yqcr50my0fva80-systemd-247.2/lib/libsystemd.so.0)
/nix/store/8ri2cwyw0xgwfx63r6h472f50xdr7cdw-chromium-unwrapped-87.0.4280.141/libexec/chromium/chromium: /nix/store/33idnvrkvfgd5lsx2pwgwwi955adl6sk-glibc-2.31/lib/libc.so.6: version `GLIBC_2.32' not found (required by /nix/store/69b2zfzyrc5jk9470mzvchfrni9yrwv1-libpulseaudio-14.0/lib/pulseaudio/libpulsecommon-14.0.so)
/nix/store/8ri2cwyw0xgwfx63r6h472f50xdr7cdw-chromium-unwrapped-87.0.4280.141/libexec/chromium/chromium: /nix/store/33idnvrkvfgd5lsx2pwgwwi955adl6sk-glibc-2.31/lib/libc.so.6: version `GLIBC_2.32' not found (required by /nix/store/zwi0s4xqknfpd5si3pr0c3ijx4kqanhv-gcc-10.2.0-lib/lib/libgomp.so.1)
/nix/store/8ri2cwyw0xgwfx63r6h472f50xdr7cdw-chromium-unwrapped-87.0.4280.141/libexec/chromium/chromium: /nix/store/33idnvrkvfgd5lsx2pwgwwi955adl6sk-glibc-2.31/lib/libc.so.6: version `GLIBC_2.32' not found (required by /nix/store/l2isbpjy5zdalr6xjgxaniqwkbf9b2gz-glib-2.66.4/lib/libglib-2.0.so.0)
/nix/store/8ri2cwyw0xgwfx63r6h472f50xdr7cdw-chromium-unwrapped-87.0.4280.141/libexec/chromium/chromium: /nix/store/33idnvrkvfgd5lsx2pwgwwi955adl6sk-glibc-2.31/lib/libc.so.6: version `GLIBC_2.32' not found (required by /nix/store/69b2zfzyrc5jk9470mzvchfrni9yrwv1-libpulseaudio-14.0/lib/libpulse.so.0)
/nix/store/8ri2cwyw0xgwfx63r6h472f50xdr7cdw-chromium-unwrapped-87.0.4280.141/libexec/chromium/chromium: /nix/store/33idnvrkvfgd5lsx2pwgwwi955adl6sk-glibc-2.31/lib/libc.so.6: version `GLIBC_2.32' not found (required by /nix/store/rqrklqsvw4ydpcg5kdcvn506fhcbqxk2-glibc-2.32-10/lib/librt.so.1)
/nix/store/8ri2cwyw0xgwfx63r6h472f50xdr7cdw-chromium-unwrapped-87.0.4280.141/libexec/chromium/chromium: /nix/store/33idnvrkvfgd5lsx2pwgwwi955adl6sk-glibc-2.31/lib/libc.so.6: version `GLIBC_2.32' not found (required by /nix/store/86lr3wqvpf0zg3sxr9kc0y4yw972p98r-avahi-0.8/lib/libavahi-common.so.3)
/nix/store/8ri2cwyw0xgwfx63r6h472f50xdr7cdw-chromium-unwrapped-87.0.4280.141/libexec/chromium/chromium: /nix/store/33idnvrkvfgd5lsx2pwgwwi955adl6sk-glibc-2.31/lib/libc.so.6: version `GLIBC_2.32' not found (required by /nix/store/4i7s80g57bqha7nna9yqcr50my0fva80-systemd-247.2/lib/libsystemd.so.0)
/nix/store/8ri2cwyw0xgwfx63r6h472f50xdr7cdw-chromium-unwrapped-87.0.4280.141/libexec/chromium/chromium: /nix/store/33idnvrkvfgd5lsx2pwgwwi955adl6sk-glibc-2.31/lib/libc.so.6: version `GLIBC_2.32' not found (required by /nix/store/69b2zfzyrc5jk9470mzvchfrni9yrwv1-libpulseaudio-14.0/lib/pulseaudio/libpulsecommon-14.0.so)
/nix/store/8ri2cwyw0xgwfx63r6h472f50xdr7cdw-chromium-unwrapped-87.0.4280.141/libexec/chromium/chromium: /nix/store/33idnvrkvfgd5lsx2pwgwwi955adl6sk-glibc-2.31/lib/libc.so.6: version `GLIBC_2.32' not found (required by /nix/store/zwi0s4xqknfpd5si3pr0c3ijx4kqanhv-gcc-10.2.0-lib/lib/libgomp.so.1)
/nix/store/f4q2jcvxrpgrrxkdm0l0ba61zzg1nsmp-xdg-utils-1.1.3/bin/xdg-open: line 881: google-chrome: command not found
/nix/store/f4q2jcvxrpgrrxkdm0l0ba61zzg1nsmp-xdg-utils-1.1.3/bin/xdg-open: line 881: www-browser: command not found
/nix/store/f4q2jcvxrpgrrxkdm0l0ba61zzg1nsmp-xdg-utils-1.1.3/bin/xdg-open: line 881: links2: command not found
/nix/store/f4q2jcvxrpgrrxkdm0l0ba61zzg1nsmp-xdg-utils-1.1.3/bin/xdg-open: line 881: elinks: command not found
/nix/store/f4q2jcvxrpgrrxkdm0l0ba61zzg1nsmp-xdg-utils-1.1.3/bin/xdg-open: line 881: links: command not found
/nix/store/f4q2jcvxrpgrrxkdm0l0ba61zzg1nsmp-xdg-utils-1.1.3/bin/xdg-open: line 881: lynx: command not found
/nix/store/f4q2jcvxrpgrrxkdm0l0ba61zzg1nsmp-xdg-utils-1.1.3/bin/xdg-open: line 881: w3m: command not found
xdg-open: no method available for opening 'https://cdn.discordapp.com/attachments/792502884164042783/797973612421971978/Normal_alt_2.png'

I have firefox and chromium installed. It looks like it tries to execute a ton of browsers, and on the ones actually installed get an error about GLIBC_2.32 not found, and something about XPCOM?

I have firefox and chromium installed. It looks like it tries to execute a ton of browsers, and on the ones actually installed get an error about GLIBC_2.32 not found, and something about XPCOM?

Okay I solved the issue for myself, was user error. I was using discord from nixos-unstable while my OS is on nixos-20.09. I was doing this for packages that updated more frequently than every 6 months not realizing that nixos backports many such updates. I'm still interested in how discord is wrapped, if it used the xdg-open from my path this wouldn't have been an issue in the first place.

Okay I solved the issue for myself, was user error. I was using discord from nixos-unstable while my OS is on nixos-20.09. I was doing this for packages that updated more frequently than every 6 months not realizing that nixos backports many such updates. I'm still interested in how discord is wrapped, if it used the xdg-open from my path this wouldn't have been an issue in the first place.

Thanks for the help hopefully this helps people in the future that run into this issue.

Thanks for the help hopefully this helps people in the future that run into this issue.

I've been having this issue on pure 20.09 for some time.

@Ralith i've only experienced this issue by using the discord from unstable and not stable, (tested today) i went from unstable and back to stable everything works as it should.

I'm on 20.09.3888.4263ba5e133, with Discord installed via home-manager from nixpkgs. Maybe it's https://github.com/NixOS/nixpkgs/pull/110825?

After i rebooted it wouldn't work, but I started discord and outputed all errors to a file and saw this error.
Seems like it's missing the nss libary.
Couldn't load XPCOM.
XPCOMGlueLoad error for file /nix/store/wl0q8dbgy21sqiyh49dfw79jims66371-firefox-88.0/lib/firefox/libxul.so:
/nix/store/bli00bnggzsir939wzy6b0jr2myw2qvd-nss-3.56/lib/libnss3.so: version `NSS_3.58' not found (required by /nix/store/wl0q8dbgy21sqiyh49dfw79jims66371-firefox-88.0/lib/firefox/libxul.so)
Couldn't load XPCOM.
xdg-open: no method available for opening 'https://github.com/readme/nasa-ingenuity-helicopter'

That error suggests that the library was available, but it was the wrong version.

Looks like #78961: https://nixos.wiki/wiki/Discord

Yep, (discord.override { nss = nss_latest; }) did the trick; will move discussion there, thanks!

I can't believe I actually found a bunch of other Nix users that had this issue, saved me some hair.
One other note, the below works just fine but make sure you match it up to your discord package (i.e., if you use unstable channel, make sure you override unstable)
(discord.override { nss = nss_latest; })

For those of you who clicking links does work, what browser and desktop environment are you using?

Kububtu 24.04
KDE Plasma Version: 5.27.11
KDE Frameworks Version: 5.115.0
Qt Version: 5.15.13
Graphics Platform: X11
xdg-utils is already the newest version (1.1.3-4.1ubuntu3)
Firefox 129.0.2 (64-bit) - provided by Snap

I try verifying my email on discord but the links does not open in my browser


feat (docker): Create docker image SBOM on release

Resolves first part of Issue #171 (other parts are waiting on changes to cargo-dist). Adds a GitHub action to create an SPDX SBOM for the Hipcheck docker image after we create and push that image during the normal release workflow. The SBOM should be automatically added as an artifact to the same release.
Draft because this has not been tested yet. We need to come up with a good way to test this that does not involve creating many unnecessary docker images.

@mchernicoff looks like this has a merge conflict with the changes @patrickjcasey made for checking Docker README size. Can you rebase?

Going to close this. I'm in the process of some more substantial reworking of how releases work, and while I definitely want SBOM building to be a part of that, I don't think it'll necessarily take this form. I'll be sure to refer back to this though, and @mchernicoff I appreciate the work you did on it!


Documentation : Update flag changes in kyverno website

The flag names will be changed according to the issue https://github.com/kyverno/kyverno/issues/1991.
We have to document these flag changes in kyverno website.

@anushkamittal20 - can you help on this issue?


Should assemblyscript-json be used in a production environment due to its massive overhead?

Hello there! 👋🏼
Wanted to pose this question as multiple people are experiencing memory issues when using assemblyscript-json. It seems that when parsing larger datasets, assemblyscript-json will allocate a class for each value which creates massive overhead. Taking a look at the documentation, it seems that classes are allocated for each value and these classes have copious amounts of methods, properties, and accessors resulting in a overhead in allocation, load, and store operations. When parsing a Vec3, 4 other classes (JSON.Obj, Map<string, JSON.Value, JSON.Value, and JSON.Float) are allocated along with a combined 69 methods.
Parsing 1 Megabyte of Vec3 instances (300,000) results in 1,200,000 classes with an attached 20,700,000 methods. Parsing over 1 Megabyte is simply incomprehensible.

https://github.com/near/assemblyscript-json/issues/322
https://github.com/near/assemblyscript-json/issues/146

The use case for this library was never meant to be for large datasets.  Rather it was needed for RPC calls passing JSON strings encoding function arguments. Thus it was focused on correctness rather with little work toward efficiency.
I agree that too many allocations are used, but each class's methods are only added to the binary once. That is they are part of the code and allocation does not add another copy of the class's code, only it's data. So not sure where your 20 million methods are coming from.
Also both issues you point to don't seem related.
And in general I would advise against using this in production. This library is not maintained and is now out of date. it uses 0.19.5 and the compiler is now up to 0.27.0.

Thank you, @willemneal!
This information helps a lot.
I suppose that I assumed that since it was used in the old near as sdk, it should be ready for production as in high and large data loads, but that is not the case. I did try with #146 (on a old version) and I did get a memory overflow error when I ran it 100 times, but that does not matter.
Thanks for responding and I'll close this now. Just wanted to inquire about this :)


Add .env to .gitignore in nextjs package #797

Add .env to .gitignore in nextjs package #797 - Although Next docs has this and makes complete sense. But sometimes people tinkering with both hardhat and nextjs package might loose the context and add secrets to .env in nextjs assuming it is gitignored similar to hardhat pacakge
Discussed with @technophile-04 on telegram
Related Issues
_Closes #797 _
Your ENS/address: websculpt.eth

Thanks @nathan-websculpt ! 100% agree.


Main window position is not saved on multi-monitor systems

Hello. I use ImGuiConfigFlags_ViewportsEnable setting and hello_imgui_demo_classic.exe does not save the main window position and its size on milti-monitor system.

Hello,
Can you clarify what you mean by "main window" ?
If by "main window", you mean the native window created by the backend (be it SDL, Glfw, or Qt); IMHO imgui in itself (and thus hello_imgui) does not provide any way to remember/restore this as a setting (since this window is created be the backnd long before imgui is inited).
See this answer from the imgui author. This was in 2019, but I suspect this is still valid.

I mean native Windows window. I consider hello_imgui as a windows management system so I believe it shall be responsible for saving/restoring all windows sizes, positions etc. though customers could do such a job themselves indeed.

I understand the need. May be this would be a nice thing to implement, although it needs some more thinking (i.e how to store this in imgui.ini, how to handle the different backends).
I keep this issue opened so that the idea stays prominent.

Hi,
Window position can be saved in the latest version. Autosize is also available.
See: https://github.com/pthom/hello_imgui/blob/master/src/hello_imgui/hello_imgui_api.md#application-window-params


added Richard profile data to community.jsn

Hackathon Git Labs Project PR 🎉🎉
👉 Please remove the below and replace with your own values, leaving the headers where they are. 👈
PR contains:
-Added the following profile record to the community.jsn file
 {     "name": "Richard",     "course_start": "2022",     "course_stage": "Student",     "favorite_language": "Java",     "currently_learning": "HTML/CSS"   }

Following the basic.md guide was definitely a learning experience in how to set up a multi-coder work environment. I found the guide instructional and was unsure if some of the challenges I faced were intentional. The two items I had to research were: 1) the permissions error when setting up my upstream link and 2) finding the location of the community jason file.

Hacktoberfest 2022:
Breaking changes

'None'

Screenshots

'None'

Apologies Andrew, I'm new to all this and didn't see your request. Is there anything I still need to do?
Cheers


Page 344 Navigate - New parameter to the Event OnAfterNavigateFindRecords

Could you add the new parameter ExtDocNo to the Event OnAfterNavigateFindRecords?
New definition
[IntegrationEvent(true, false)]
local procedure OnAfterNavigateFindRecords(var DocumentEntry: Record "Document Entry"; DocNoFilter: Text; PostingDateFilter: Text; var 	NewSourceRecVar: Variant; ExtDocNo: Code[250])
begin
end;

Use
local procedure FindRecords()
...
OnAfterNavigateFindRecords(Rec, DocNoFilter, PostingDateFilter, NewSourceRecVar, ExtDocNo);

Thank you

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 46009.


useAsyncData/useFetch types do not reflect pick or transform changes anymore

Environment

Operating System: Linux
Node Version:     v18.18.0
Nuxt Version:     3.9.3
CLI Version:      3.10.0
Nitro Version:    2.8.1
Package Manager<EMAIL_ADDRESS>Builder:          -
User Config:      devtools
Runtime Modules:  -
Build Modules:    -

Reproduction
<script setup lang="ts">
const { data } = useAsyncData<{ data: { test: 1 } }>(
  'key',
  async (): Promise<any> => {
    return { data: { test: 1 } };
  },
  {
    pick: ['data'],
  }
);

const test = computed(() => data.value?.test);
</script>
<template>
  <div>
    {{ test }}
  </div>
</template>

Typcheck fails with app.vue:12:41 - error TS2339: Property 'test' does not exist on type '{ data: { test: 1; }; }'.
Describe the bug
useFetch/useAsyncData should augment the provided type via generic when pick or transform is present.
Additional context
No response
Logs
No response

Hi @manniL . I'm the guy who wrote the comment in YouTube about this issue. Thanks for taking the time to report this issue. I have like 68 error messages like this in my project since I updated from 3.8.2 to 3.9.3 and have no clue on how to get rid of them ^_^U

I am not 100% sure if this applies to this issue. But I was able to resolve type errors in our project by explicitly pinning "vue": "3.4.15" after upgrading Nuxt to 3.9.x.

This appears to be an issue just with pick as transform works fine (FWIW):
const { data } = useAsyncData(() => Promise.resolve({ data: { test: 1 } }), {
  pick: ['data'],
  // transform: data => data.data,
})
const test = computed(() => data.value?.test)

Looking to reproduce, this code (with pick) has a type error all the way back to at least v3.6.0 in the Nuxt playground.

@danielroe Attached a repro (that I wanted to put there before, sorry) also showing transform issues I think.

Would there be no way of having the useFetch return a globalThis.Ref (without using transform or pick) instead of Ref like before?

This isn't actually a bug. (It got us all!) pick doesn't return only that key, it just restricts the keys of an object to the keys passed in the array. (That's why it's an array, not a single string.)


Install LORA SERVER LORA APP SERVER LORA GATEWAY in Windows 7 64 Bit

Is this a bug or a feature request?
I am new to LORA. Am using Windows 64 bit in my system.I have installed MQTT,Redis database,PostgreSQL.
What did you expect?
Help to install LORA server Lora app server and lora gateway in windows 7.
there is no configfile too..how to install that??
What happened?
While installing loraserver using exe file in cmd prompt.
What version are your using?
LORASERVER version   loraserver_1.0.0_windows_amd64
How can your issue be reproduced?
Kindly help me to install loraserver loraappserver lora gateway.
Could you share your log output?

I think the error explains it all. Configuration examples are available on www.loraserver.io.

I have installed the following before installing LORA SERVER,LORA APP SERVER AND LORA GATEWAY ,
1.MQTT version 1.4.15
2.Redis version <IP_ADDRESS>3
3.PostgreSQL version 9.6
I have downloaded loraserver.exe while running exe in cmd prompt it is showing ping database error..will retry in 2s...
For configuration , i have referred this link https://www.loraserver.io/install/configuration/ and got .toml fileis created in my current working directory.
am not aware of .toml..what to do with that??
Still the above mentioned error is persisting...
kindly explain me..


all pokestop in range was already visited

help me

Appears your using RocketMaps. Have you tried waiting 4 minutes for it to reset the pokestops?

is not that

seems not be pokemongo-bot

what do you mean ?it's pokemongo bot

console is not the same, i see something about pokemaster?Rocketapi? What fork are u using?

Wrong bot. Definitely wrong one. TO use our bot, please down see documentation: https://github.com/PokemonGoF/PokemonGo-Bot/blob/master/docs/installation.md or https://github.com/PokemonGoF/PokemonGo-Bot/blob/master/docs/manual_installation.md also visit us in discord if you need help with the bot


removed raylib-d

Because the repository and the author's GitHub profile doesn't exist anymore

@AKDev21 Oooh... that's sad...


Update target from_configuration

Summary
This PR updates logic of method:from_configuration() of class:Target in qiskit/transpiler/target.py
Credit:
@nkanazawa1989 , this logic is heavily influenced by  https://github.com/Qiskit/qiskit-ibm-provider/pull/413
@to24toro  , for all the kind help and motivation :)
fixes: #10168

This is Work In Progress, I will let know when I am done :)

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
-0.02%

Covered Lines:
59232

Relevant Lines:
67668

💛  - Coveralls

I am sure this requires some further work, if the code remains the same there has to be some changes in the docstrings.
Probably should add some more tests to increase coverage :)
A review could provide me with better guidance for next steps :)
@nkanazawa1989 ,  please see if this good enough :)

I will let know when I am done :)

I often see implicitly defined required_operations (they are mostly measure and delay) in multiple places in the Qiskit codebase. I think Target must provide this information with its class attribute so that developers can easily find the minimum instruction requirements for transpiler. What do you think @mtreinish ?

Not, sure my vote counts, but
1 Vote in for "adding required_operations as class attribute in Target"

@nkanazawa1989 , please see if this is good enough :)

@nkanazawa1989 , Please, see if this is good enough :)

@1ucian0 , Things have changed in Qiskit, I doubt if the PR is required anymore,
does this PR stands a chance of merging, if yes, what should be the direction of this PR ?


refactor(autoware_predicted_path_checker): prefix package and namespace with autoware

Description
prefix package and namespace with autoware
Related links
Parent Issue:

https://github.com/autowarefoundation/autoware/issues/4569

How was this PR tested?
Notes for reviewers
None.
Interface changes
None.

Effects on system behavior
None.

Closing, it's been a while since this PR was updated.


A few changes to the catching the errors.

Awesome work on the PR. I tried to tighten the catches up to be closer to the calls out to the hed-validator. Also made it use Issue objects errorToIssue function for pretty printing the error call stack.
One thing I'm not sure about is emitting an error or warning. I switched it to emit a warning so that datasets would still upload to openneuro and other apps that need no errors to proceed. I've gone back and forth on this, let me know what you think.

Should approve me to run the workflows, I've got lost of tests failing locally that I'm trying to fix, be nice to see them fail in CircleCI.

Should approve me to run the workflows, I've got lost of tests failing locally that I'm trying to fix, be nice to see them fail in CircleCI.

@rwblair I approved you, but the CircleCI tests didn't run, just the test-bids-examples GitHub action.

Got the number failing down to 7, with 2 of which match the 2 that are failing in main PR.
Things like code mismatches expecting 205 but getting 116. Would that happen if I was running the latest hed-validator?

2ce8f94 should fix the issues we see being thrown by circle.

I'm bumping the dependency version to 3.1.1 in this PR, so I'll have to fix the codes. I'll do that once this side PR is merged. Do I commit the modified lock file or do you handle that?

I didn't push any changes to the lock file.
I'm okay with failing hed tests getting merged since well be doing #1299 next which will hopefully straighten all this out.
If you are ok with the changes in this PR, once you merge it into  happy5214/reorder-hed-execution I'll go ahead and merge bids-standard/bids-validator/pull/1298

Well, I mean who will fix the lock file? Will it be done automatically, or who is responsible for committing the change to 3.1.1? I only changed the package.json in the PR.

Gotcha, I went ahead and committed mine. It isn't done automatically unfortunately.


Show comment creation dates within the pull request

I miss the ability to see when a comment was made - maybe it's very old and outdated, maybe it's brand new and there's a fresh conversation to be had. So the idea is within comment boxes that appears in the pull request there, to show the creation date.
Thanks!

I think it's a duplicate of https://github.com/microsoft/vscode-pull-request-github/issues/121

It is, thank you @laurentlb.


Feature Request: Support Column Masking

Describe the feature
Support Column Masking as part of the YAML definition:
{% macro create_hash_function() %}
    CREATE OR REPLACE FUNCTION my_catalog.my_schema.hash_mask(raw_value STRING)
    RETURN sha2(raw_value, 256);
{% endmacro %}

on-run-start: "{{ create_hash_function() }}"

models:
  - name: foo
    description: I'm a teapot
    columns:
      - name: id
      - name: bank_details
        column_mask: my_catalog.my_schema.hash_mask

Describe alternatives you've considered
Doing this in a post-hook. It works fine but it's a bit messy,
Additional context
Please include any other relevant context here.
Who will this benefit?
Anyone who wants to define masking for their models
Are you interested in contributing this feature?
Yes

We've been talking about this, and mostly we've been holding off until we can implement the full column spec, or, until Databricks allows you to specify advanced column features without specifying the column type; in the absence of that change, we can only add the mask with an alter statement, which seems a pretty weak implementation.  However, if you wanted to work on a PR for this, I'd be happy to work with you on getting it into the adapter.


{{ 1 + 1 }}

Windows Terminal version
1.75.5
Windows build number
10.0.9125
Other Software
testing
Steps to reproduce
testingf\
Expected Behavior
testing
Actual Behavior
testing

Please do now use our repository for "testing" without prior permission.


Using Local Repo -- Uncaught Error: You must pass a block type.

I checked out slate-edit-table and yarn linked into my other app. When I call insertTable I get the error below. I tried this against master and 0.8.4.
block.js:143 Uncaught Error: You must pass a block `type`.
    at Function.create (http://localhost:3808/webpack/frontend.js:31596:35)
    at Object.block (http://localhost:3808/webpack/frontend.js:28144:30)
    at Object.Transforms.insertBlock (http://localhost:3808/webpack/frontend.js:223492:31)
    at Transform.Object.keys.forEach.Transform.(anonymous function) [as insertBlock] (http://localhost:3808/webpack/frontend.js:221152:32)
    at insertTable (http://localhost:3808/webpack/frontend.js:146533:20)
    at Toolbar.insertTable (http://localhost:3808/webpack/frontend.js:150653:19)
    at Toolbar.proxiedMethod (http://localhost:3808/webpack/frontend.js:214867:30)
    at GridSelect.insertTable (http://localhost:3808/webpack/frontend.js:150048:18)
    at GridSelect.proxiedMethod (http://localhost:3808/webpack/frontend.js:214867:30)
    at Object.ReactErrorUtils.invokeGuardedCallback (http://localhost:3808/webpack/frontend.js:59996:16)
    at executeDispatch (http://localhost:3808/webpack/frontend.js:38408:21)
    at Object.executeDispatchesInOrder (http://localhost:3808/webpack/frontend.js:38428:7)
    at executeDispatchesAndRelease (http://localhost:3808/webpack/frontend.js:24554:22)
    at executeDispatchesAndReleaseTopLevel (http://localhost:3808/webpack/frontend.js:24565:10)
    at Array.forEach (native)
    at forEachAccumulated (http://localhost:3808/webpack/frontend.js:97619:9)
    at Object.processEventQueue (http://localhost:3808/webpack/frontend.js:24768:7)
    at runEventQueueInBatch (http://localhost:3808/webpack/frontend.js:204913:18)
    at Object.handleTopLevel [as _handleTopLevel] (http://localhost:3808/webpack/frontend.js:204924:5)
    at handleTopLevelImpl (http://localhost:3808/webpack/frontend.js:205006:24)
    at ReactDefaultBatchingStrategyTransaction.perform (http://localhost:3808/webpack/frontend.js:38771:20)
    at Object.batchedUpdates (http://localhost:3808/webpack/frontend.js:96405:26)
    at Object.batchedUpdates (http://localhost:3808/webpack/frontend.js:17126:27)
    at dispatchEvent (http://localhost:3808/webpack/frontend.js:205081:20)

Hi, this error is result of usage of two Slate instances. Just tell webpack to use only project node_modules by setting absolute path in resolve.modules = [ path.resolve(__dirname, 'node_modules') in webpack config.

Thanks!


hmm.py example not working

Just want to run the hmm.py example, and got the following error:
      691 Loading data
      722 ----------------------------------------
      722 Training model_1 on 229 sequences
Traceback (most recent call last):
  File "hmm.py", line 295, in <module>
    main(args)
  File "hmm.py", line 244, in main
    guide = AutoDelta(poutine.block(model, expose_fn=lambda msg: msg["name"].startswith("probs_")))
TypeError: block() got an unexpected keyword argument 'expose_fn'

look like the function argument is been updated. Then, I changed the "expose_fn" to "expose" as I found in Pyro docs. It still breaks:
      682 Loading data
      711 ----------------------------------------
      711 Training model_1 on 229 sequences
Traceback (most recent call last):
  File "hmm.py", line 295, in <module>
    main(args)
  File "hmm.py", line 245, in main
    guide = AutoDelta(poutine.block(model, expose=lambda msg: msg["name"].startswith("probs_")))
  File "/opt/conda/lib/python3.6/site-packages/pyro/poutine/handlers.py", line 209, in block
    hide_types=hide_types, expose_types=expose_types)
  File "/opt/conda/lib/python3.6/site-packages/pyro/poutine/block_messenger.py", line 79, in __init__
    assert set(hide).isdisjoint(set(expose)), \
TypeError: 'function' object is not iterable

anyone can check what is the problem?

Hi @tongjiyiming can you verify that your Pyro version matches the example version? I suspect you're using an older Pyro with a newer examples/hmm.py. The example currently works on dev branch.

I got "0.2.1".
So, should I install the dev version?

Yes, the example only works with dev branch for now. We're planning another release in a few weeks, just after PyTorch 1.0 is released.

unfortunately, after I upgrade to dev branch by
pip install git+https://github.com/uber/pyro.git#egg=project[extras]

It still failed with:

Thank you! It works now.


My happiness using Microsoft SQL

[Enter feedback here]
it is a great pleasure for my that I am using Microsoft SQL Server to boost up my Data base Skill
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: b9261422-8fd0-f534-8503-b3f144853958
Version Independent ID: 0c05cc4f-8260-a264-e724-2f3801f82862
Content: Tutorials for SQL Server - SQL Server
Content Source: docs/sql-server/tutorials-for-sql-server-2016.md
Service: sql
Sub-service: ****
GitHub Login: @MikeRayMSFT
Microsoft Alias: mikeray

@samsorrahman -- Samsor, thank you for sharing such positive feedback!  Best wishes in your pursuit of learning and advancement!
cc @MikeRayMSFT & @rothja

Completely agree! Thank you @samsorrahman for your feedback. I'm the manager of the Database Docs team. Let me know if you have any feedback on how we can improve.


Allow newer versions of bytestring dependency

I believe that the next major version of bytestring (0.11.x.x) should be compatible with this library.

Thanks! Ping me if I don't make a release soon. I'll try and do it tomorrow morning.

@wraithm Great, thanks for the quick turnaround!


Feature/86-VolunteersProfile

Is your feature request related to a problem? Please describe.
Not applicable
Describe the solution you'd like
The idea of this issue it is that the users log in as volunteers can see their profile information and update it. Use the volunteers API for it and you can use the same style and structure than in the admin screen
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
If there is any doubt of the style, you can have an overlook to the mockups

Story Points: 5
See the discussion in Frontend S2
Powered by Parabol


Opening projetcs from Windows Jumplist takes minutes, from start menu only seconds

Type: Bug
When opening a project or even just a New Window from the Windows (10) jumplist, it takes minutes to open VS Code. Opening vscode from the start menu (even with the same project) takes just seconds to open. I also cleared the most recent list but that didn't help.
Happy to provide additonal logs if needed.
VS Code version: Code 1.80.1 (74f6148eb9ea00507ec113ec51c489d6ffb4b771, 2023-07-12T17:22:07.651Z)
OS version: Windows_NT x64 10.0.19045
Modes:

I have a Windows 10 VM that I tried this out on, and I cannot reproduce this slowness, even on a resource constrained VM.

We closed this issue because we are unable to reproduce the problem with the steps you describe. Chances are we've already fixed your problem in a recent version of VS Code. If not, please ask us to reopen the issue and provide us with more detail. Our issue reporting guidelines might help you with that.
Happy Coding!


Keep mouse drag when mouse action is neutral

Previously, when the mouse action was neutral, the Dragged state of the mouse was reset to false. This change fixes it by keeping it set to true as long as one of the mouse buttons is down, requiring a mouse release before the Dragged state is exited.

Awesome! Thanks for your help!


Check for NetID conflicts

To avoid accidentally having multiple checklists with the same NetIDs (and/or CUID's), a check should run on all Rosters first to guarantee that none of them have these attributes conflicting

Included as of fc5bb009e8e388cf625f9045f40e66f05018e7f5, forgot to close


Add transform constants for AES-GCM

Closes #138
No NSS support due to https://github.com/lsh123/xmlsec/issues/233.

Codecov Report

Merging #154 into master will decrease coverage by 0.03%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #154      +/-   ##
==========================================
- Coverage   88.39%   88.35%   -0.04%
==========================================
  Files          12       12
  Lines        2076     2044      -32
==========================================
- Hits         1835     1806      -29
+ Misses        241      238       -3

Impacted Files
Coverage Δ

src/constants.c
96.32% <100.00%> (+0.02%)
:arrow_up:

src/main.c
81.11% <0.00%> (-2.23%)
:arrow_down:

src/exception.c
40.00% <0.00%> (-0.91%)
:arrow_down:

src/tree.c
95.32% <0.00%> (-0.13%)
:arrow_down:

src/template.c
90.36% <0.00%> (-0.07%)
:arrow_down:

src/platform.h
100.00% <0.00%> (+16.00%)
:arrow_up:

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 39c3bca...2a6cd99. Read the comment docs.

@hoefling  Hi there -- sorry for this dumb question 🙏🏻  What version of python-xmlsec did this PR get released with? 1.3.9? I couldn't find it anywhere, apologies if it is published somewhere and I didn't see it.


Azure RedHat OpenShift 2022-09-04

ARM API Information (Control Plane)
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Azure 1st Party Service can try out the Shift Left experience to initiate API design review from ADO code repo.  If you are interested, may request engineering support by filling in with the form https://aka.ms/ShiftLeftSupportForm.
Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

[ ] new service onboarding
[x] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
September 7th
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
September 20th
By default, Azure SDKs of all languages (.NET/Python/Java/JavaScript for both management-plane SDK and data-plane SDK, Go for management-plane SDK only ) MUST be refreshed with/after swagger of new version is published. If you prefer NOT to refresh any specific SDK language upon swagger updates in the current PR, please leave details with justification here.

Contribution checklist (MS Employees Only):

[x] I commit to follow the Breaking Change Policy of "no breaking changes"
[x] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

Applicability: :warning:
If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

Change to data plane APIs
Adding new properties
All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

[x] Check this box if any of the following apply to the PR so that the label "ARMReview" and "WaitForARMFeedback" will be added by bot to kick off ARM API Review.  Missing to check this box in the following scenario may result in delays to the ARM manifest review and deployment.

Adding a new service
Adding new API(s)
Adding a new API version

[x] To review changes efficiently, ensure you copy the existing version into the new directory structure for first commit and then push new changes, including version updates, in separate commits. You can use OpenAPIHub to initialize the PR for adding a new version. For more details refer to the wiki.

[x] Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[x] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If you have any breaking changes as defined in the Breaking Change Policy, request approval from the Breaking Change Review Board.
Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Additional details on the process and office hours are on the Breaking Change Wiki.
NOTE: To update API(s) in public preview for over 1 year (refer to Retirement of Previews)
Please follow the link to find more details on PR review process.

Pleae follow the instructions in the checklist before sumitting the PR. This PR is not created correctly :

@raosuhas thank you for the feedback. I was still working on some of the definitions/descriptions. I wasn't aware that the PR was adding/removing the labels for you to review it so soon. I will address all your comments in my next push

@raosuhas thank you for the feedback. I was still working on some of the definitions/descriptions. I wasn't aware that the PR was adding/removing the labels for you to review it so soon. I will address all your comments in my next push

np .. there seems to be a bug in the label setting alogrithm which the team is working on , so I am just manually checking PRs for now .. so I might be looking at some PRs incorrectly

Fixed the labels , please remove ARMCHangesRequested label when you want the ARM reviewer to look at this again.

/azp run

/azp run

/azp run

/azp run

/azp run

/azp run

/azp run unifiedPipeline

/azp run unifiedPipeline

/azp run

@leni-msft would you be able to review this PR? I see you have worked with ARO team in our previous API release.

@ross-bryan Adding new API requires ARM sign-off. I see ARM has requested changes, please check.

Hi @leni-msft , I made the changes that were requested see this thread https://github.com/Azure/azure-rest-api-specs/pull/20463#discussion_r975526618
Also, this was passing all validation last week. Now there are new rules that are added that is causing more validation to fail. It is unreasonable for me to keep trying to pass linting validation when it is a constantly moving target. Can you please advise?
It seems the label bot is broken in this PR.

Hi @leni-msft I am working on making the checks pass for this. I have some questions:
The checks were indicating that we must have a pattern parameter for resourceName and childResourceName. We don't have any name constraints on our side, but when I add a pattern now I'm getting a violation "1036 - ConstraintChanged". Please let me know if there's some way of working around this conflict.
I don't understand why we're getting CreateOperationAsyncResponseValidation errors for several of our PUT operations. These are not async long-running operations, so we are not setting x-ms-long-running-operation. Can you clarify what the expectation is here?

Hi @leni-msft I am working on making the checks pass for this. I have some questions:
The checks were indicating that we must have a pattern parameter for resourceName and childResourceName. We don't have any name constraints on our side, but when I add a pattern now I'm getting a violation "1036 - ConstraintChanged". Please let me know if there's some way of working around this conflict.
I don't understand why we're getting CreateOperationAsyncResponseValidation errors for several of our PUT operations. These are not async long-running operations, so we are not setting x-ms-long-running-operation. Can you clarify what the expectation is here?

Adding pattern in resource name is a new ARM rule, please request breaking change review for "1036 - ConstraintChanged",
For CreateOperationAsyncResponseValidation, since @jianyexi is OOF, @rkmanda would you be able to take a look if it's a valid issue?

@ross-bryan please avoid force pushing the branch - it's hard to review what's the new change

Thank you for the feedback. I found the code that implements CreateOperationAsyncResponseValidation, and it looks like any PUT that results in a 201 Created is considered a long running operation. To work around this, we are removing the 201 responses and will use 200 OK instead.

Thank you for the feedback. I found the code that implements CreateOperationAsyncResponseValidation, and it looks like any PUT that results in a 201 Created is considered a long running operation. To work around this, we are removing the 201 responses and will use 200 OK instead.

@ventifus Does your service return 201? if so, you must define 201 in swagger. To workaround the lint error, we can suppress it. See https://dev.azure.com/azure-sdk/internal/_wiki/wikis/internal.wiki/85/Swagger-Suppression-Process

any PUT that results in a 201 Created is considered a long running operation

+@jianyexi to check the logic

HI @leni-msft Going back to the "pattern" restrictions and the resulting breaking change, I joined the Breaking Change office hours and they advised that the requirement for pattern restrictions is just a "staging" check and that we should not implement them at this time. (Also they noted that the client does not perform validation and so the restrictions would not have any effect anyway.) I'll submit a new commit reverting the pattern restrictions.
Regarding the 201 responses, yes we had originally designed our API to return 201 Created for PUT requests as that made the most sense. We would prefer to use 201, I will look into the suppression process.

@leni-msft I have removed the pattern restrictions and restored the 201 Created responses for our PUTs. Since both of these are staging checks, do we still need to go through the swagger suppression process? The regular "Swagger LintDiff" is reporting green.

@leni-msft I have removed the pattern restrictions and restored the 201 Created responses for our PUTs. Since both of these are staging checks, do we still need to go through the swagger suppression process? The regular "Swagger LintDiff" is reporting green.

You're right, no need for the staging lint check.

/azp run

@jianyexi @leni-msft can we get an approval here? This PR has been open for many many weeks now. We are delayed on delivering highly demanded features such as multi-version support because of this PR pending approval. Please either request changes, or grant us your blessings and approval :pray:

If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Hi @ross-bryan , this PR is blocked on ARM review. I will merge this PR after ARM sign-off.

Looks like this is not getting an ARM review because it still has the tag ARMChangesRequested. I don't have permissions to remove it, @leni-msft @raosuhas can you help?

Please close this PR in favor of #21248.


k8s: Use Resource[*Pod] in pod watcher for the local pod watching

Now that Resource[*Pod] has been added as a shared resource and it is seeing use from multiple modules, refactor the pod watcher to also use it for the normal case of watching just the local pods.
The "handover" case of watching all pods still creates a separate informer, but this should affect very small set of deployments.

/test

Labelled this a kind/bug as duplicate informers on the pod resource is not great - I don't think the release-blocker label would be approriate though, as it only occurs if IPAM multi-pool is used which is beta.


Migrated TM1637 to nanoFramework

Description

Updated references and code to work with nanoFramework.
Motivation and Context

Fixes https://github.com/nanoframework/Home/issues/866

How Has This Been Tested?

I validated sample runs successfully with KeeYees ESP-WROOM-32 CP2102 and HiLetgo 4-Digit Tube LED TM1637
Screenshots
Types of changes

[ ] Improvement (non-breaking change that improves a feature, code or algorithm)
[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Config and build (change in the configuration and build system, has no impact on code or features)
[ ] Dependencies (update dependencies and changes associated, has no impact on code or features)
[ ] Unit Tests (work on Unit Tests, has no impact on code or features)
[x] Documentation (changes or updates in the documentation, has no impact on code or features)

Checklist:

[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

I double checked and I think its already in devices.  I had copied TM1637 folder from generated_devices to devices and then deleted TM1637 from generated_devices.

I double checked and I think its already in devices. I had copied TM1637 folder from generated_devices to devices and then deleted TM1637 from generated_devices.

So something wrong with your git then:

Check the Files tab here and you'll see all is on devices_generated folder like this one except the sln.

and at the same time, you seems right as the pipeline sees it properly:
![image](https://user-images.githubusercontent.com/8145578/137512146-b4d44578-a7c1-46b6-a094-cb5347191e4f.pn
Can you delete the folder in the devices_generated and push the change so we can try to make sure things are clear?

I can't delete it because it doesn't exist locally.  I thought the screenshot you provided meant the file moved from devices_generated to devices:


Cost plus m3 sensors

Added cost and m3 sensors
Description

Added 2 new sensors to track costs and 1 for m3 volumetric gas conversion. These can be used in the energy dashboard
Motivation and Context

This provides all the sensors to track consumption for gas and electric as well as costs on the energy dashboard

How Has This Been Tested?

Tested on my own HA install

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

No idea how to fix the DeepSource error after several attempts. Happy for anyone to contribute...

I have been running this branch for the last few days without issue. Nice work

I've merge this into my pull request https://github.com/HandyHat/ha-hildebrandglow-dcc/pull/40


Logstash crash

Error:
message=>"Lumberjack input: The circuit breaker has detected a slowdown or stall in the pipeline, the input is closing the current connection and rejecting new connection until the pipeline recover.", :exception=>LogStash::CircuitBreaker::OpenBreaker, :level=>:warn}
:message=>"Lumberjack input: the pipeline is blocked, temporary refusing new connection.", :level=>:warn}
Possily related:
http://search-devops.com/m/zmSSfoizfd1hLQVI1&subj=+Logstash+Nonstop+Lumberjack+pipeline+is+blocked+messages
https://github.com/logstash-plugins/logstash-input-lumberjack/issues/47

Check out logstash 2.0.0 release version.

See filebeat. It may be a replacement for logstash-forwarder.
https://www.elastic.co/blog/beats-beta4-filebeat-lightweight-log-forwarding

Related to memory allocation limit in elasticsearch. see https://github.com/elastic/elasticsearch/issues/9357

Updated limit in /etc/security/limits.conf

Moved to BETA Milestone

if es core or ls core has not enough memory (or potentially other errors) it doesn’t return an error.

Issue seams to be from attached child process. Fix for issue #142 is linked to this one. Currently running es dore dmon instance using custom init script. If it runs for more than 5 day it will confirm the fix.

Fixed by use of init script.


Add command /move to move a range of messages to another channel.

The command would have an almost identical interface to /purge, with the exception of channel:

start (String) - The ID of the start message.
end (String) - The ID of the end message.
authors (User(s)) - The author(s) whose messages are to be moved to another channel.

If unset, all messages falling into the range will be moved.

channels (Channel(s)) - The channel(s) to move the messages to.

Specifying more than one channel will make Logos post the same messages into multiple channels.

Notes:

The messages would be sent using webhooks to imitate the original user.
Logos will lock the target channel(s) until all of the messages are moved. This is to prevent the natural flow of the messages being broken up by incoming messages.

TODO: Does the source channel also get locked?

Not enough value for the effort for the time being. Language features take priority.


Support For Custom Field Resolvers - Gen 2

Describe the feature you'd like to request
The ability to resolve a custome field on a graphQL data type. Example:
type Book {
   id: ID!
   title: String!
   author:String
   imageUrl(size: Int): String! // this is what I want
}

I know the above is not in amplify syntax, but you get the idea. ImageUrl is a custom field resolver that should be calculated at request time based on the size input.
Describe the solution you'd like
It would be awesome if we could resolve this in the same or in a similar way to our custom query lambdas.
Describe alternatives you've considered
We could define this as a custom query, but then your queries get pretty verbose and pretty decoupled from the related data, so not really ideal.
Additional context
No response
Is this something that you'd be interested in working on?

[ ] 👋 I may be able to implement this feature request

Would this feature include a breaking change?

[ ] ⚠ This feature might incur a breaking change

Hi @alexwhb  👋 , Thank you for your request. We will label this as a feature request for the team to review in more detail.

@AnilMaktala Awesome! Thanks for the update. 🎉

Any update on this?  I'm interested for the use case of establishing relationships between custom types:
//...,
Todo: a.customType({
  id: a.id().required(),
  description: a.string(),
  user_id: a.id().required(),
  user: a.belongsTo('UserProfile, 'user_id') // currently doesn't work
}),
UserProfile: a.customType({
  id: a.id().required(),
  first_name: a.string(),
  last_name: a.string()
  todos: a.hasMany('Todo', 'user_id') // currently doesn't work
})


With different routes on the same router you don't get the methods

When using different routes to redirect to the clusters, it generates the following message Method not found: access-route/access.AccessService/GetMenuAndChild. Code: 12.
admin:
  access_log_path: /tmp/admin_access.log
  address:
    socket_address: {
      address: <IP_ADDRESS>,
      port_value: 9902
    }

static_resources:
  listeners:
  - name: local_listener
    address:
      socket_address: {
        address: <IP_ADDRESS>,
        # port of this proxy route
        port_value: 8989
      }
    filter_chains:
    - filters:
      - name: envoy.http_connection_manager
        typed_config:
          "@type": type.googleapis.com/envoy.config.filter.network.http_connection_manager.v2.HttpConnectionManager
          codec_type: AUTO
          stat_prefix: ingress_http
          route_config:
            name: local_route_access
            virtual_hosts:
            - name: local_access_service
              domains: ["*"]
              routes:
              - match: {
                  prefix: "/access-route"
                }
                route: {
                  cluster: access_cluster,
                  max_grpc_timeout: 0s
                }
              - match: {
                  prefix: "/dictionary-route"
                }
                route: {
                  cluster: dictionary_cluster,
                  max_grpc_timeout: 0s
                }
              - match: {
                  prefix: "/businessdata-route"
                }
                route: {
                  cluster: business_data_cluster,
                  max_grpc_timeout: 0s
                }
              - match: {
                  prefix: "/enrollment-route"
                }
                route: {
                  cluster: enrollment_cluster,
                  max_grpc_timeout: 0s
                }
              cors:
                allow_origin_string_match:
                  - safe_regex:
                      google_re2: {}
                      regex: \*
                # This directive holds the list of HTTP request methods. If the
                # requests are more than one then the request are separated by commas.
                allow_methods: GET, PUT, DELETE, POST, PATCH, OPTIONS
                # is a response-type header that is used to indicate the HTTP headers.
                allow_headers: authorization,keep-alive,user-agent,cache-control,content-type,content-transfer-encoding,custom-header-1,x-accept-content-transfer-encoding,x-accept-response-streaming,x-user-agent,x-grpc-web,grpc-timeout
                # It specifies how many maximum seconds can the result be cached. Note: If -1 is present then caching is disabled.
                max_age: "1728000"
                # Is a response header that is used to expose the headers that have been mentioned in it.
                expose_headers: custom-header-1,grpc-status,grpc-message,x-envoy-upstream-service-time
          http_filters:
          - name: envoy.grpc_web
          - name: envoy.cors
          - name: envoy.router

  clusters:
  - name: access_cluster
    connect_timeout: 0.25s
    type: logical_dns
    http2_protocol_options: {}
    lb_policy: round_robin
    load_assignment:
      cluster_name: access_cluster
      endpoints:
      - lb_endpoints:
        - endpoint:
            address:
              socket_address:
                # replace the 'localhost' address with your access host address
                address: localhost
                # it is the default port, unless the server port is changed it is recommended not to change
                # https://github.com/erpcya/adempiere-gRPC-Server/blob/master/src/main/java/org/spin/grpc/util/AccessServer.java#L128
                port_value: 50050

  - name: dictionary_cluster
    connect_timeout: 0.25s
    type: logical_dns
    http2_protocol_options: {}
    lb_policy: round_robin
    load_assignment:
      cluster_name: dictionary_cluster
      endpoints:
      - lb_endpoints:
        - endpoint:
            address:
              socket_address:
                # replace the 'localhost' address with your dictionary host address
                address: localhost
                # it is the default port, unless the server port is changed it is recommended not to change
                # https://github.com/erpcya/adempiere-gRPC-Server/blob/master/src/main/java/org/spin/grpc/util/DictionaryServer.java#L128
                port_value: 50051

  - name: business_data_cluster
    connect_timeout: 0.25s
    type: logical_dns
    http2_protocol_options: {}
    lb_policy: round_robin
    load_assignment:
      cluster_name: business_data_cluster
      endpoints:
      - lb_endpoints:
        - endpoint:
            address:
              socket_address:
                # replace the 'localhost' address with your business data host address
                address: localhost
                # it is the default port, unless the server port is changed it is recommended not to change
                # https://github.com/erpcya/adempiere-gRPC-Server/blob/master/src/main/java/org/spin/grpc/util/BusinessDataServer.java#L128
                port_value: 50052

  - name: enrollment_cluster
    connect_timeout: 0.25s
    type: logical_dns
    http2_protocol_options: {}
    lb_policy: round_robin
    load_assignment:
      cluster_name: enrollment_cluster
      endpoints:
      - lb_endpoints:
        - endpoint:
            address:
              socket_address:
                # replace the 'localhost' address with your enrollment host address
                address: localhost
                # it is the default port, unless the server port is changed it is recommended not to change
                # https://github.com/erpcya/adempiere-gRPC-Server/blob/master/src/main/java/org/spin/grpc/util/EnrollmentServer.java#L127
                port_value: 50047

however using only one router for each route works well, this is not the most appropriate
https://github.com/erpcya/gRPC-Envoy-Proxy/blob/master/envoy.yaml

I think the "Method not found error" is coming from your GRPC server, not Envoy. The normal format for GRPC paths is /service/Method so I'd expect your GRPC upstreams to want /access.AccessService/GetMenuAndChild. Perhaps you need to use prefix_rewrite to strip /access-route from the start of your path?

Thank you @zuercher, it worked correctly as you indicated with prefix_rewrite as follows:

              routes:
              - match: {
                  prefix: "/access-route/"
                  # prefix: "/access"
                }
                route: {
                  prefix_rewrite: "/",
                  cluster: access_cluster,
                  max_grpc_timeout: 0s
                }
              - match: {
                  prefix: "/dictionary-route/"
                }
                route: {
                  prefix_rewrite: "/",
                  cluster: dictionary_cluster,
                  max_grpc_timeout: 0s
                }
              - match: {
                  prefix: "/businessdata-route/"
                }
                route: {
                  prefix_rewrite: "/",
                  cluster: business_data_cluster,
                  max_grpc_timeout: 0s
                }
              - match: {
                  prefix: "/enrollment-route/"
                }
                route: {
                  prefix_rewrite: "/",
                  cluster: enrollment_cluster,
                  max_grpc_timeout: 0s
                }


Unexpected number of runs for trigger "When one or more messages arrive in a queue (peek-lock)"

Describe the Bug with repro steps

Create a new Stateful workflow and use the Service Bus trigger (Not the in app version) for either "When one or more messages arrive in a queue (peek-lock)" or "When one or more messages arrive in a topic (peek-lock)", the bug is the same for both.
Leave default settings, i.e. split on = true and concurrency = off.
Use Managed Identity (system assigned) to connect to the service bus.
Set the maximum message count to a low value, in this case 2.
Set the recurrence frequency to day and interval to 10 (high enough so it does not mess with the test.
Create an action which completes the message.
Add 10 messages to the queue.
Run the trigger (twice... since the first one often does not fire in the portal)

Before running trigger
Message count in the queue equals: 10
Max deliver count: 2
Expected result
Number of triggers fired: 1.
Number of history runs: 2.
Message count in the queue after the run should be: 8.
Actual result
Number of triggers fired: 16.
Number of history runs: 10.
Message count in the queue after the run equals: 0.
The bug is the same for:
"When one or more messages arrive in a queue (peek-lock)"
"When one or more messages arrive in a topic (peek-lock)".
My colleagues have the same problem.
This used to work when using Logic Apps Comsumption.
What type of Logic App Is this happening in?
Standard (Portal)
Are you using new designer or old designer
New Designer
Did you refer to the TSG before filing this issue? https://aka.ms/lauxtsg
Yes
Workflow JSON
{
    "definition": {
        "$schema": "https://schema.management.azure.com/providers/Microsoft.Logic/schemas/2016-06-01/workflowdefinition.json#",
        "actions": {
            "Complete_the_message_in_a_queue": {
                "inputs": {
                    "host": {
                        "connection": {
                            "referenceName": "servicebus-2"
                        }
                    },
                    "method": "delete",
                    "path": "/@{encodeURIComponent(encodeURIComponent(parameters('serviceBusQueueName')))}/messages/complete",
                    "queries": {
                        "lockToken": "@{triggerBody()?['LockToken']}",
                        "queueType": "Main",
                        "sessionId": ""
                    }
                },
                "runAfter": {},
                "type": "ApiConnection"
            }
        },
        "contentVersion": "<IP_ADDRESS>",
        "outputs": {},
        "triggers": {
            "When_one_or_more_messages_arrive_in_a_queue_(peek-lock)": {
                "inputs": {
                    "host": {
                        "connection": {
                            "referenceName": "servicebus-2"
                        }
                    },
                    "method": "get",
                    "path": "/@{encodeURIComponent(encodeURIComponent(parameters('serviceBusQueueName')))}/messages/batch/head/peek",
                    "queries": {
                        "maxMessageCount": 2,
                        "queueType": "Main",
                        "sessionId": "None"
                    }
                },
                "recurrence": {
                    "frequency": "Day",
                    "interval": 10
                },
                "splitOn": "@triggerBody()",
                "type": "ApiConnection"
            }
        }
    },
    "kind": "Stateful"
}

Screenshots or Videos
Queue Settings

Queue Before Run

Workflow Trigger Before Manual Run

Workflow Trigger After Manual Run

Queue After Run

Browser
Microsoft Edge
Additional context
No response
AB#24933340

Hi @MrRosendahl, thanks for reporting your issue, this appears to be a backend bug so I'm going to move this over to the repo that our backend devs keep an eye on for triage.


Add scan interval option

Goal of this PR
Fixes #243
This PR introduces a new option, --attack-interval, shortened as -I, which allows users to perform attacks on remote cameras with an interval between each attempt, in order to keep the attack hidden from network monitoring tools that are setup to detect bruteforce attacks.
It also fixes some unclear documentation about the use of duration type options, such as the --timeout option and the new --attack-interval option. It now properly describes that they are not taking an amount of milliseconds, but a duration (such as 2ms).
How to test it

Ensure that increasing the interval value increases the time it takes to attack a camera.
Ensure that by default, no interval is added.
Ensure that negative values can not be given.

This screenshot demonstrates the feature (the time the operation took can be seen in the prompt below, 8 seconds with a 2000ms interval and 40 seconds with a 10000ms interval).

I analyzed the traffic on the sniffer and the -I parameter only works until "Attacking routes of 1 streams ...". "After Attacking credentials of 1 streams ..." the delay resets to 0ms.

It looks as if only the transition stages of the attack support the delay but the users and passwords are checked without delay.

The delay is added between each curl request:

Each time a password guess is attempted
Each time a username guess is attempted
Each time the definition of the auth type is attempted
Each time the validation of the stream is attempted

The delay never resets to 0ms, AFAIK. If you see a mistake somewhere, please point out the line that you think resets the delay

I don't know much about it and I can't run an image manually with corrections in the attack.go file. I use docker-terminal for windows with virtualbox. I run "docker run -t ullaakut / cameradar -t  -I 5000ms". However, the unchanged image is downloaded in the attack.go file.

I corrected the lines in the attack.go file and managed to build an image from path. Delay works well. Good job.

Hi @Robin6464. What lines did you need to correct? 🤔

I corrected the lines like this: https://github.com/Ullaakut/cameradar/pull/246/commits/ec96963fcd455641d7567b0654e06cafce79a1ab. I deleted lines 82, 108 and added lines 158, 175.

Feel free to make a PR to add those passwords and usernames to the dictionary 👍 Currently I use an automated script to fetch them from the internet but obviously some are more difficult to get.
And thanks for the testing :)


PEAR-1997: Fix for Cases Table - Customize Columns dropdown is partially cutoff from view

Description
Checklist

[N/A] Added proper unit tests
[N/A] Left proper TODO messages for any remaining tasks
[N/A] Scanned for web accessibility with aXe, and mitigated or documented
flagged issues

Screenshots/Screen Recordings (if Appropriate)

works for me! 👍


[BUG] Sync icon constantly indicating sync

The sync icon flashes between syncing and done while the plugin is disabled on Obsidian 1.7.7 running macOS. The sync log states "Fully synced"
Plugin version: 1.2.17

Do you know if this started happening only after upgrading to Obsidian 1.8? Also what dos the Sync Log say?

Hi! I can confirm issue with "flashing Obsidian Sync" icon (only) after upgrade to 1.8.0 (no other changes), and Image Converter 1.2.17, but Obsidian Sync has no changes (e..g still happens while Obsidian Sync is "fully synced").
Seems to be related to "cache cleanup", e.g. while opening developer tools, I see constant spamming of below messages
Automatic cache cleanup...
Cache cleanup time: 0.85107421875 ms
1 Cache cleaned: {}

Thanks for the screenshot 🙏 Probably those excessive console logs will be the culprit, they are removed in future versions 🧹
Although, OP mentioned "while the plugin is disabled" which means either me or Obsidian is not unloading event listeners properly, so would need clarification from @ThorstenRhau what do they mean by that

Hi! I had this happen with Obsidian 1.7.7 and Image Converter 1.2.17. It started happening after updating the plugin to this version.

Thanks for the screenshot 🙏 Probably those excessive console logs will be the culprit, they are removed in future versions 🧹
Although, OP mentioned "while the plugin is disabled" which means either me or Obsidian is not unloading event listeners properly, so would need clarification from @ThorstenRhau what do they mean by that

When the plugin is disabled or uninstalled obsidian behaves as expected, no excessive logs, and the sync icon only shows syncing when actual files are synced, after that the icon shows a green check-mark indicating all-synced.

The cache cleanup was indeed the culprit.
The default value was set in minutes, disregarding the fact that the actual calculation would be done in milliseconds. So the default 60 in essence was being interpreted as 0.001min - which was way too rapid. Should be fixed now.
Patched in 1.2.19

Hi! Thanks for the swift response and fix here; I can confirm the cache cleanup "bug" is no longer is an issue in Obsidian 1.8.0, after updating to 1.2.19 and manually updating the auto-cleanup interval from 0.001 to 60 (not changed automatically).
PS: I don't know if it's possible to (automatically) write a partially default update (one-shot), or if the manual change is required by all users? Point being; maybe some users don't review the release notes, and never (manually) change the ato-cleanup interval value, hence it would be nice to automatically update the default (for this value), if possible. Anyways, thanks a million; really love this extensions, and your work here 🙌! Merry xmas 🎅.

I had noticed this too yesterday, didn't need to make a bug report ... fixed already 🙂. Thanks!

Hi! Thanks for the swift response and fix here; I can confirm the cache cleanup "bug" is no longer is an issue in Obsidian 1.8.0, after updating to 1.2.19 and manually updating the auto-cleanup interval from 0.001 to 60 (not changed automatically).
PS: I don't know if it's possible to (automatically) write a partially default update (one-shot), or if the manual change is required by all users? Point being; maybe some users don't review the release notes, and never (manually) change the ato-cleanup interval value, hence it would be nice to automatically update the default (for this value), if possible. Anyways, thanks a million; really love this extensions, and your work here 🙌! Merry xmas 🎅.

That's a good point!
That's because when Obsidian updates the plugin it keeps all plugin settings inside data.json 😭 usually that's a good thing, but not in this case.. so any default values which ship with the plugin would not get applied if that file already exists. Plugin reinstall would fix this, and it would create new clean data.json with all new defaults. But as you say, not everyone reads release notes.
Before I start implementing something more robust (like proper settings migration), I've pushed a quick mini update where I simply changed 1 variable name, which in theory now even if old data.json existed, the plugin would simply not know what to do with that old variable, and thus the new default would kick in. Merry xmas 🎅


Use react-transform-hmr

The package react-transform-webpack-hmr was renamed to react-transform-hmr. This PR simply update the dependencies/scripts.

I haven't had a chance to try out the new package locally yet; any idea about why this is build is failing? Your configuration looks correct at a glance. From the Travis log:
 Error: locals[0] does not appear to be a `module` object with Hot Module replacement API enabled. You should disable react-transform-hmr in production by using `env` section in Babel configuration. See the example in README: https://github.com/gaearon/react-transform-hmr

Thanks for this though, I'll gladly pull it in once the build is fixed.

Ah, it's actually because you need to explicitly define it in development:
  "env": {
    // only enable it when process.env.NODE_ENV is 'development' or undefined
    "development": {
      "plugins": ["react-transform"],
      "extra": {
        // must be defined and be an array
        "react-transform": [{
          "target": "react-transform-hmr",
          // if you use React Native, pass "react-native" instead:
          "imports": ["react"],
          // this is important for Webpack HMR:
          "locals": ["module"]
        }]

Sorry I didn't check the build, my bad! Should be good now.
Thanks for this repo, checked a couple of boilerplates/starters out there, and fell in love with yours :)

No problem, thanks for your help :).
And that's awesome, it's good to hear some people are finding it helpful. Thanks again!


android: Drop support for API < 23.

As Discussed in CZO, Last time (9-2020) we checked, the total
user base using API < 23 is less than 1 percent and hence it is
safe for us to update the API version (according to the update
policy [2] we have).
The advantage of this change would be simplification in some of the
code that we use / will be using which will be changed / added in
other commits.
The changes in this commit Involved:

Changing android/build.gradle.
Setting up chrome version to 44 (set according to what is
written in platform-versions.md).
Modifications to the documentation.

Marking P1 since Notification UI is built on top of this PR.

@gnprice, @chrisbobbe let me know if I missed anything, thank you.

@chrisbobbe did the changes you asked for waiting on @gnprice to comment on

Hmm, and that makes me think we should maybe bump the numbers in the following, a bit above that:
 * * For Android, core functionality needs to work on Chrome 44.
 *   Graceful degradation is acceptable below Chrome 74.

Hmm, and that makes me think we should maybe bump the numbers in the following, a bit above that:
 * * For Android, core functionality needs to work on Chrome 44.
 *   Graceful degradation is acceptable below Chrome 74.

Yeah, there's probably a helpful related change to do here along those lines. It doesn't actually have a particular need to be coupled to this minSdkVersion change, though -- this one is about the minimum version of Android that we support, so the data it's based on is the distribution of Android versions our users have, while that one would be about the minimum versions of Chrome that we support to various degrees, so the data it'd be based on is the distribution of Chrome versions our users have. Those distributions are quite different from each other, because Android's Chrome auto-updates independently of the OS.
Before this change, we nominally had three levels of support for different Chrome versions:

37 to below 44: sometimes fix issues, when trivial
44 to below 74: core functionality needs to work, but graceful degradation acceptable
74 and up: fully supported

I'm kind of inclined to drop that lowest tier, because I'm not sure the extra distinction was really buying us that much. If we run into something that's busted only on ancient Chrome versions like 44, we can consider reintroducing it, or perhaps just dropping support for Android 6 M altogether (and consequently for Chrome older than 51.)
The current version of this PR does that. Keeping it that way means leaving the mention of Chrome 44 as is, to be in sync with Android 6 M as our oldest supported Android version.
For updating the "fully supported" / "graceful degradation below" version, it looks like our last update was 92d24025171a672ad2475d877fd8c484c71de89c, earlier this year. Updating it to Chrome 83 would mean updating to a Chrome version released 2020-05 (thank you Wikipedia -- one of the niches Wikipedia tends to do a great job at is chronicling old versions of all kinds of major software). That seems pretty reasonable; that's over a year ago, 9 versions before the current latest, and our previous look at some data suggests that 90% of users will be on just the two latest versions.

This all looks good; merging. Thanks @AkashDhiman for taking care of this!
In the previous comment, I guess I reached the conclusion that a good followup would be to replace that mention of Chrome 74 with Chrome 83. I don't think that involves changing any other lines.
A separate nice followup would be to remove the handful of spots in the js.js source code that are there just for the sake of old browsers we no longer support. Searching the file for "Chrome" finds them. Looks like there's a couple of polyfills, and a conditional inside midMessagePeer. Cutting out that conditional will also mean we get to delete a paragraph of the long comment above it.
For cutting those all out, it'd be good to try the app with Chrome 44 (by firing up an emulator with a stock Android 6 M image) and confirm that things seem to work. Also ideally on iOS 12, I guess (for the oldest Safari we support); but iOS 12 is a few years newer than Chrome 44, so even if our notes are mistaken it's a lot less likely that these features would be missing there.

And merged! I made just one change, expanding the summary line:
2e7ea833e android: Drop support for API < 23, aka Android 6 Marshmallow.
I tend to find the API numbers hard to keep track of, so when they appear in text I like to accompany them with the Android version number and letter (or the dessert the letter stands for, though starting with Android 9 P they've de-emphasized the letter and dessert, and starting with Android 10 Q the letter doesn't stand for anything.) Those have consistently advanced by one each year since before the oldest Android versions we care about, so I can always count backward from the latest to orient myself to how old a given number/letter is.


Replace "multibillionaire" with "oxyphenbutazone"

As described in #180

Thanks mate! You could have merged the PR, it's very simple. But it feels good to merge it, so no problem.