Next Button for the Text Search

I'm trying to figure out how to make a next button for the text search field to enable cycling through multiple instances of a search term (such as "Mike", which I have several of in my current hosts list). I don't really know Pure Basic, but I think I'm figuring out the structure and might be able to figure out how to create the feature on my own. If you like the idea and want to implement it before I have the time to figure it out around my regular work, here is the idea. I'm simply planning on shortening the #text_search field by enough to add a button with the text "Next" on it that will go to the next instance of the text found in the hosts list. I don't know how to do that yet, but I'm sure I'll eventually figure it out. If I do and you haven't already implemented this feature yourself, I'll upload the code for your approval if you'd like.

I like the idea, but I've not had the time myself to implement it or
figure out how to do it.  If you can figure it out, would be a good
addition for sure.
Daniel
------ Original Message ------
From: "ITN1nja"<EMAIL_ADDRESS>To: "OldNESJunkie/uVNCRemoteControl"
<EMAIL_ADDRESS>Cc: "Subscribed"<EMAIL_ADDRESS>Sent: 12/15/2020 5:13:55 PM
Subject: [OldNESJunkie/uVNCRemoteControl] Next Button for the Text
Search (#1)

I'm trying to figure out how to make a next button for the text search
field to enable cycling through multiple instances of a search term
(such as "Mike", which I have several of in my current hosts list). I
don't really know Pure Basic, but I think I'm figuring out the
structure and might be able to figure out how to create the feature on
my own. If you like the idea and want to implement it before I have the
time to figure it out around my regular work, here is the idea. I'm
simply planning on shortening the #text_search field by enough to add a
button with the text "Next" on it that will go to the next instance of
the text found in the hosts list. I don't know how to do that yet, but
I'm sure I'll eventually figure it out. If I do and you haven't already
implemented this feature yourself, I'll upload the code for your
approval if you'd like.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/OldNESJunkie/uVNCRemoteControl/issues/1, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AP7TS6UINXOWIGANVEM56LDSU7UTHANCNFSM4U5DMIVA.

I'll work on it as I have time. I downloaded a demo of PureBasic, but it keeps giving compile errors. I don't know if I just need to purchase a license for API support, or what. Either way, I'll tinker and see what I can do when I can. I'm not really a software engineer by trade, so it will take a bit. 👍

Lol, I'm not either as the source shows 😋
On Tue, Dec 15, 2020, 5:53 PM ITN1nja<EMAIL_ADDRESS>wrote:

I'll work on it as I have time. I downloaded a demo of PureBasic, but it
keeps giving compile errors. I don't know if I just need to purchase a
license for API support, or what. Either way, I'll tinker and see what I
can do when I can. I'm not really a software engineer by trade, so it will
take a bit. 👍
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/OldNESJunkie/uVNCRemoteControl/issues/1#issuecomment-745640273,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AP7TS6VNGFLKNKBZ453WIBLSU7ZI5ANCNFSM4U5DMIVA
.

Check out the latest release to see the new search function.

Check out the latest release to see the new search function.


Update keyring to v1.1.6

Recent versions of kwallet have removed the old support for the kde4
compatible kwallet dbus interface. This means newer kde5 based
OS installs (e.g. kubuntu 20.04) can no longer use the kwallet backend
with aws-okta.
This was fixed upstream in the keyring lib back in 2019 but the
dependency hasn't been bumped since then.

I'm gonna consider this a "ship it and see" merge. If it breaks anybody, we'll immediately revert.

I'm gonna consider this a "ship it and see" merge. If it breaks anybody, we'll immediately revert.


CI - Reduce the number of build warnings

New Feature
Reduce the number of build warnings - work ongoing from #253
Motivation for New Feature
We want to minimise the number of build warnings, enforce a common coding style and identify any common gotchas in the code
Steps to Reproduce the Problem
Do a build ;)
Specifications
n/a

@binarymash much appreciated, just had a quick look! Only a few things that i commented on and they are my mistakes!  Was just in the water poet near Liverpool Street. Was a Huddersfield exciles sticker in the bogs. Exciting.

Warnings now 0...
Used a pragma to squash the warning about AddBaseUrl being obsolete as it was test code (and setup code at that). Also, I switched off package analysis to shut up the warning about the summary text (see https://github.com/NuGet/Home/issues/4587 for more).

@simonjefford awesome!! Thanks 👍
AddBaseUrl is some crap that wasn't very well thought out :( I need to get rid of it but focusing on other features at the moment. We have an issue for it!

@binarymash not sure if you want to re-open this but will leave closed for now as @simonjefford (a friend of mine from real life..yes I have two of them!) has helped out here!


btrfs-progs doesn't cross compile

Issue description
these derivations will be built:
  /nix/store/kqwb525yy9y19chcf29mhasayzkgcbkf-btrfs-progs-4.19-armv7l-unknown-linux-gnueabihf.drv
building '/nix/store/kqwb525yy9y19chcf29mhasayzkgcbkf-btrfs-progs-4.19-armv7l-unknown-linux-gnueabihf.drv'...
unpacking sources
unpacking source archive /nix/store/3z7xbd91mpm3r1y9h8vpcwzbyhmd1lax-btrfs-progs-v4.19.tar.xz
source root is btrfs-progs-v4.19
setting SOURCE_DATE_EPOCH to timestamp<PHONE_NUMBER> of file btrfs-progs-v4.19/config/install-sh
patching sources
updateAutotoolsGnuConfigScriptsPhase
Updating Autotools / GNU config script to a newer upstream version: ./config/config.sub
Updating Autotools / GNU config script to a newer upstream version: ./config/config.guess
configuring
configure flags: --disable-static --prefix=/nix/store/kig6dwdh89fy65jb4lw4z6vk0fllsrry-btrfs-progs-4.19-armv7l-unknown-linux-gnueabihf --build=x86_64-unknown-linux-gnu --host=armv7l-unknown-linux-gnueabihf
checking for armv7l-unknown-linux-gnueabihf-gcc... armv7l-unknown-linux-gnueabihf-gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... yes
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether armv7l-unknown-linux-gnueabihf-gcc accepts -g... yes
checking for armv7l-unknown-linux-gnueabihf-gcc option to accept ISO C89... none needed
checking how to run the C preprocessor... armv7l-unknown-linux-gnueabihf-gcc -E
checking for grep that handles long lines and -e... /nix/store/k7sszlqy0f9ixbnjp3ghvmdis03m5qqz-gnugrep-3.1/bin/grep
checking for egrep... /nix/store/k7sszlqy0f9ixbnjp3ghvmdis03m5qqz-gnugrep-3.1/bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking minix/config.h usability... no
checking minix/config.h presence... no
checking for minix/config.h... no
checking whether it is safe to define __EXTENSIONS__... yes
checking for armv7l-unknown-linux-gnueabihf-gcc... (cached) armv7l-unknown-linux-gnueabihf-gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether armv7l-unknown-linux-gnueabihf-gcc accepts -g... (cached) yes
checking for armv7l-unknown-linux-gnueabihf-gcc option to accept ISO C89... (cached) none needed
checking whether C compiler accepts -std=gnu90... yes
checking build system type... x86_64-unknown-linux-gnu
checking host system type... armv7l-unknown-linux-gnueabihf
checking for an ANSI C-conforming const... yes
checking for working volatile... yes
checking whether byte ordering is bigendian... no
checking for special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... 64
checking for a BSD-compatible install... /nix/store/rlrf0k4z6vasy9sqswxj66cg5vmnvpsk-coreutils-8.30/bin/install -c
checking whether ln -s works... yes
checking for armv7l-unknown-linux-gnueabihf-ar... armv7l-unknown-linux-gnueabihf-ar
checking for rm... /nix/store/rlrf0k4z6vasy9sqswxj66cg5vmnvpsk-coreutils-8.30/bin/rm
checking for rmdir... /nix/store/rlrf0k4z6vasy9sqswxj66cg5vmnvpsk-coreutils-8.30/bin/rmdir
checking for openat... yes
checking for reallocarray... yes
checking for armv7l-unknown-linux-gnueabihf-pkg-config... no
checking for pkg-config... /nix/store/l6wsvyviggk0af6c829w7qsvk1ncb3r2-pkg-config-0.29.2/bin/pkg-config
configure: WARNING: using cross tools not prefixed with host triplet
checking pkg-config is at least version 0.9.0... yes
checking execinfo.h usability... yes
checking execinfo.h presence... yes
checking for execinfo.h... yes
checking for backtrace... yes
checking for backtrace_symbols_fd... yes
checking for xmlto... /nix/store/hn2imdqln90y9xl8xinrp52wl24ks0sl-xmlto-0.0.28/bin/xmlto
checking for mv... /nix/store/rlrf0k4z6vasy9sqswxj66cg5vmnvpsk-coreutils-8.30/bin/mv
checking for a sed that does not truncate output... /nix/store/kb2h4llzakvphmryvwqljvyqqnxnslvm-gnused-4.5/bin/sed
checking for asciidoc... /nix/store/37iqfzb070cr8kcxay97ld0yizgk87zr-asciidoc-8.6.9/bin/asciidoc
checking for asciidoctor... no
checking for ext2fs... yes
checking for com_err... yes
checking for reiserfscore >= 3.6.27... no
checking for FIEMAP_EXTENT_SHARED defined in linux/fiemap.h... yes
checking for blkid... yes
checking for uuid... yes
checking for zlib... yes
checking for libzstd >= 1.0.0... yes
checking for a Python interpreter with version >= 3.4... python
checking for python... /nix/store/q7wqmmq18r2m4n4yfb7zkkbpnirc6k91-python3-3.7.1/bin/python
checking for python version... 3.7
checking for python platform... linux
checking for python script directory... ${prefix}/lib/python3.7/site-packages
checking for python extension module directory... ${exec_prefix}/lib/python3.7/site-packages
checking for python-3.7... no
configure: error: Package requirements (python-3.7) were not met:

No package 'python-3.7' found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables PYTHON_CFLAGS
and PYTHON_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.
builder for '/nix/store/kqwb525yy9y19chcf29mhasayzkgcbkf-btrfs-progs-4.19-armv7l-unknown-linux-gnueabihf.drv' failed with exit code 1
error: build of '/nix/store/kqwb525yy9y19chcf29mhasayzkgcbkf-btrfs-progs-4.19-armv7l-unknown-linux-gnueabihf.drv' failed

Steps to reproduce
$ cat ./btrfs-progs.sh
   #!/bin/sh
   nix-build -I nixpkgs=/home/void/nixpkgs -E 'let t1 = import <nixpkgs> {}; in let pkgs = import <nixpkgs> { crossSystem = t1.l ib.systems.examples.armv7l-hf-multiplatform // { system = "armv7l-linux"; }; }; in pkgs.btrfs-progs '

Im on nixpkgs/staging.

Tries to locate python3 via pkg-config. Below is the config.log.
647 configure:6455: checking for a Python interpreter with version >= 3.4
 648 configure:6472: python -c import sys # split strings by '.' and convert to numeric. Append some zeros # because we need at least 4 digits for \
     the hex conversion. # map returns an iterator in Python 3.0 and a list in 2.x minver = list(map(int, '3.4'.split('.'))) + [0, 0, 0] minverhex \
     = 0 # xrange is not present in Python 3.0 and range returns an iterator for i in list(range(0, 4)): minverhex = (minverhex << 8) + minver[i] s\
     ys.exit(sys.hexversion < minverhex)
 649 configure:6475: $? = 0
 650 configure:6481: result: python
 651 configure:6489: checking for python
 652 configure:6507: found /nix/store/1sf1lkplgwrp0c3b7m8329gcrbw1isk0-python3-3.7.1/bin/python
 653 configure:6519: result: /nix/store/1sf1lkplgwrp0c3b7m8329gcrbw1isk0-python3-3.7.1/bin/python
 654 configure:6537: checking for python version
 655 configure:6544: result: 3.7
 656 configure:6556: checking for python platform
 657 configure:6563: result: linux
 658 configure:6589: checking for python script directory
 659 configure:6624: result: ${prefix}/lib/python3.7/site-packages
 660 configure:6633: checking for python extension module directory
 661 configure:6668: result: ${exec_prefix}/lib/python3.7/site-packages
 662 configure:6683: checking for python-3.7
 663 configure:6690: $PKG_CONFIG --exists --print-errors "python-${PYTHON_VERSION}"
 664 Package python-3.7 was not found in the pkg-config search path.
 665 Perhaps you should add the directory containing `python-3.7.pc'
 666 to the PKG_CONFIG_PATH environment variable
 667 No package 'python-3.7' found
 668 configure:6693: $? = 1
 669 configure:6707: $PKG_CONFIG --exists --print-errors "python-${PYTHON_VERSION}"
 670 Package python-3.7 was not found in the pkg-config search path.
 671 Perhaps you should add the directory containing `python-3.7.pc'
 672 to the PKG_CONFIG_PATH environment variable
 673 No package 'python-3.7' found
 674 configure:6710: $? = 1
 675 configure:6724: result: no
 676 No package 'python-3.7' found
 677 configure:6740: error: Package requirements (python-3.7) were not met:
 678
 679 No package 'python-3.7' found

Apparently, there is no such pc:
 [nix-shell:~/pi/btrfs-progs-v4.19]$ pkg-config --list-all|grep python

I was able to add the following and pkg-config work.
  PKG_CONFIG_PATH = "${buildPackages.python3Packages.python}/lib/pkgconfig";

Then I've got the following:
  9987 rm btrfs-man5.xml btrfs-ioctl.xml
  9988     [PY]     libbtrfsutil
  9989 In file included from /nix/store/1sf1lkplgwrp0c3b7m8329gcrbw1isk0-python3-3.7.1/include/python3.7m/Python.h:53:0,
  9990                  from btrfsutilpy.h:27,
  9991                  from error.c:20:
  9992 /nix/store/1sf1lkplgwrp0c3b7m8329gcrbw1isk0-python3-3.7.1/include/python3.7m/pyport.h:699:2: error: #error "LONG_BIT definition appears wrong for platform (bad gcc/glibc config?)."
  9993  #error "LONG_BIT definition appears wrong for platform (bad gcc/glibc config?)."
  9994   ^~~~~
  9995 error: command 'armv7l-unknown-linux-gnueabihf-gcc' failed with exit status 1
  9996 make: *** [Makefile:435: libbtrfsutil_python] Error 1
  9997 builder for '/nix/store/hwmp1f51iryjwf9afka3f4rw7g3sr7ac-btrfs-progs-4.19-armv7l-unknown-linux-gnueabihf.drv' failed with exit code 2
  9998 error: build of '/nix/store/hwmp1f51iryjwf9afka3f4rw7g3sr7ac-btrfs-progs-4.19-armv7l-unknown-linux-gnueabihf.drv' failed

ping @matthewbauer

python3.7 is in nativeBuildInputs I am not sure pkg-config will pick it up from there.

Yeah no buildPackages is needed here - it needs to link against the cross built python.

For what it's worth, I've successfully built btrfs-progs for arm on my cross-compilation branches. Perhaps this has to do with python cross-compilation support (nixpkgs currently produces broken python3 extensions), which I'll be submitting some more patches for.

This doesn't work pretty much.
python3.overrideAttrs(old: {
  7            configureFlags = old.configureFlags ++ ["--disable-ipv6"];
  8            CONFIG_SITE = writeScript "config.site" ''
  9              ac_cv_file__dev_ptmx=no
 10              ac_cv_file__dev_ptc=no
 11            '';
 12            });

I think https://github.com/matthewbauer/nixpkgs/commit/e23b753259173daa94183d211931a7058b922fed will fix this.

Hey @matthewbauer,
I'm recompiling from scratch after https://github.com/NixOS/nixpkgs/issues/50915
Please hold while I get the error once more & verify your fix.

820927c was reverted in 713f5e2

https://github.com/Mic92/nixpkgs/commit/3c31069680adc077800c998b114687c70a55905d should fix this

This got further by now - it's now failing here:
config.status: creating config.h

        btrfs-progs v5.3.1

        prefix:             /nix/store/svm0v31chiv7l3vd4bsl28m3ka1hjkpn-btrfs-progs-5.3.1-armv7l-unknown-linux-gnueabihf
        exec prefix:        ${prefix}

        bindir:             ${exec_prefix}/bin
        libdir:             ${exec_prefix}/lib
        includedir:         ${prefix}/include

        compiler:           armv7l-unknown-linux-gnueabihf-gcc
        cflags:             -g -O2 -Wall -D_FORTIFY_SOURCE=2
        ldflags:

        programs:           yes
        shared libraries:   yes
        static libraries:   no
        documentation:      yes
        doc generator:      asciidoc
        backtrace support:  yes
        btrfs-convert:      yes (ext2)
        btrfs-restore zstd: yes
        Python bindings:    yes
        Python interpreter: /nix/store/c2n0xp0j3nacr1l17lmrdzwp16ljsvll-python3-3.7.5/bin/python

        Type 'make' to compile.

building
build flags: SHELL=/nix/store/jg730c9crhf06bf800jyv85cmq0n285k-bash-4.4-p23/bin/bash
    [CC]     btrfs.o
    [CC]     dir-item.o
    [CC]     inode-map.o
    [CC]     qgroup.o
    [CC]     kernel-lib/list_sort.o
    [CC]     props.o
    [CC]     kernel-shared/ulist.o
    [CC]     check/qgroup-verify.o
    [CC]     backref.o
    [CC]     common/string-table.o
    [CC]     common/task-utils.o
    [CC]     inode.o
    [CC]     file.o
    [CC]     find-root.o
    [CC]     common/help.o
    [CC]     send-dump.o
    [CC]     common/fsfeatures.o
    [CC]     common/format-output.o
    [CC]     common/device-utils.o
    [CC]     cmds/subvolume.o
    [CC]     cmds/filesystem.o
    [CC]     cmds/device.o
    [CC]     cmds/scrub.o
    [CC]     cmds/inspect.o
    [CC]     cmds/balance.o
    [CC]     cmds/send.o
    [CC]     cmds/receive.o
    [CC]     cmds/quota.o
    [CC]     cmds/qgroup.o
    [CC]     cmds/replace.o
    [CC]     check/main.o
    [CC]     cmds/restore.o
    [CC]     cmds/rescue.o
    [CC]     cmds/rescue-chunk-recover.o
    [CC]     cmds/rescue-super-recover.o
    [CC]     cmds/property.o
    [CC]     cmds/filesystem-usage.o
    [CC]     cmds/inspect-dump-tree.o
    [CC]     cmds/inspect-dump-super.o
    [CC]     cmds/inspect-tree-stats.o
    [CC]     cmds/filesystem-du.o
    [CC]     mkfs/common.o
    [CC]     check/mode-common.o
    [CC]     check/mode-lowmem.o
    [CC]     send-stream.o
    [CC]     send-utils.o
    [CC]     kernel-lib/rbtree.o
    [CC]     btrfs-list.o
    [CC]     kernel-lib/radix-tree.o
    [CC]     extent-cache.o
    [CC]     extent_io.o
    [CC]     kernel-lib/crc32c.o
    [CC]     common/messages.o
    [CC]     uuid-tree.o
    [CC]     utils-lib.o
    [CC]     common/rbtree-utils.o
    [CC]     ctree.o
    [CC]     disk-io.o
    [CC]     extent-tree.o
    [CC]     delayed-ref.o
    [CC]     print-tree.o
    [CC]     free-space-cache.o
    [CC]     root-tree.o
    [CC]     volumes.o
    [CC]     transaction.o
    [CC]     free-space-tree.o
    [CC]     repair.o
    [CC]     inode-item.o
    [CC]     file-item.o
    [CC]     kernel-lib/raid56.o
    [CC]     kernel-lib/tables.o
    [CC]     common/device-scan.o
    [CC]     common/path-utils.o
    [CC]     common/utils.o
    [CC]     libbtrfsutil/subvolume.o
    [CC]     libbtrfsutil/stubs.o
    [AR]     libbtrfs.a
    [CC]     libbtrfsutil/errors.o
    [CC]     libbtrfsutil/filesystem.o
    [CC]     libbtrfsutil/qgroup.o
    [AR]     libbtrfsutil.a
    [LD]     btrfs
    [CC]     mkfs/main.o
    [CC]     mkfs/rootdir.o
    [LD]     mkfs.btrfs
    [CC]     btrfs-map-logical.o
    [LD]     btrfs-map-logical
    [CC]     image/main.o
    [CC]     image/sanitize.o
    [LD]     btrfs-image
    [CC]     btrfs-find-root.o
    [LD]     btrfs-find-root
    [CC]     btrfstune.o
    [LD]     btrfstune
    [CC]     btrfs-select-super.o
    [LD]     btrfs-select-super
    [CC]     convert/main.o
    [CC]     convert/common.o
    [CC]     convert/source-fs.o
    [CC]     convert/source-ext2.o
    [CC]     convert/source-reiserfs.o
    [LD]     btrfs-convert
    [LN]     btrfsck
    [CC]     btrfs-corrupt-block.o
    [LD]     btrfs-corrupt-block
    [LD]     libbtrfs.so.0.1
    [LD]     libbtrfsutil.so.1.1.1
    [LN]     libbtrfs.so.0
    [LN]     libbtrfs.so
    [LN]     libbtrfsutil.so.1
    [LN]     libbtrfsutil.so
Making all in Documentation
    [ASCII]  btrfs-ioctl.xml
    [XMLTO]  btrfs-ioctl.3
    [ASCII]  btrfs-man5.xml
    [XMLTO]  btrfs-man5.5
rm btrfs-man5.xml btrfs-ioctl.xml
    [PY]     libbtrfsutil
In file included from /nix/store/c2n0xp0j3nacr1l17lmrdzwp16ljsvll-python3-3.7.5/include/python3.7m/Python.h:63,
                 from btrfsutilpy.h:27,
                 from error.c:20:
/nix/store/c2n0xp0j3nacr1l17lmrdzwp16ljsvll-python3-3.7.5/include/python3.7m/pyport.h:699:2: error: #error "LONG_BIT definition appears wrong for platform (bad gcc/glibc config?)."
 #error "LONG_BIT definition appears wrong for platform (bad gcc/glibc config?)."
  ^~~~~
error: command 'armv7l-unknown-linux-gnueabihf-gcc' failed with exit status 1
make: *** [Makefile:485: libbtrfsutil_python] Error 1
builder for '/nix/store/58gap3r2886bdpcprhnjbxxc9r9iivg1-btrfs-progs-5.3.1-armv7l-unknown-linux-gnueabihf.drv' failed with exit code 2
cannot build derivation '/nix/store/li0r3iffiyxmz1bw40rdmfr85bg13fpn-force-path.patch.drv': 1 dependencies couldn't be built

This now fails in zstd:
these derivations will be built:
  /nix/store/8qj0ps73vg5qqva1zkrn9szmy94vqwy0-zstd-1.4.5-aarch64-unknown-linux-gnu.drv
  /nix/store/lcnx19n47gzi37ha259v67cnwq023ll3-btrfs-progs-5.6-aarch64-unknown-linux-gnu.drv
building '/nix/store/8qj0ps73vg5qqva1zkrn9szmy94vqwy0-zstd-1.4.5-aarch64-unknown-linux-gnu.drv' on<EMAIL_ADDRESS>unpacking sources
unpacking source archive /nix/store/ksa1p2xrkg3aymdbbqkp1whgdgx8dw24-source
source root is source
patching sources
applying patch /nix/store/g12z5ybwlh1p6dv8jza621qnfvn0fxbl-playtests-darwin.patch
patching file tests/playTests.sh
applying patch /nix/store/dz671cdl6d2p8r8i5aqvscrh91c8hgcv-2163.patch
patching file lib/legacy/zstd_v04.c
updateAutotoolsGnuConfigScriptsPhase
configuring
fixing cmake files...
cmake flags: -DCMAKE_FIND_USE_SYSTEM_PACKAGE_REGISTRY=OFF -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_BUILD_TYPE=Release -DCMAKE_SKIP_BUILD_RPATH=ON -DBUILD_TESTING=OFF -DCMAKE_INSTALL_LOCALEDIR=/nix/store/qk8fh1inf89rbd5c9d6ydkrpsvn2zycw-zstd-1.4.5-aarch64-unknown-linux-gnu/share/locale -DCMAKE_INSTALL_LIBEXECDIR=/nix/store/qk8fh1inf89rbd5c9d6ydkrpsvn2zycw-zstd-1.4.5-aarch64-unknown-linux-gnu/libexec -DCMAKE_INSTALL_LIBDIR=/nix/store/qk8fh1inf89rbd5c9d6ydkrpsvn2zycw-zstd-1.4.5-aarch64-unknown-linux-gnu/lib -DCMAKE_INSTALL_DOCDIR=/nix/store/qk8fh1inf89rbd5c9d6ydkrpsvn2zycw-zstd-1.4.5-aarch64-unknown-linux-gnu/share/doc/ -DCMAKE_INSTALL_INFODIR=/nix/store/xfm72dlsd9lvsq2qaggkvzflamfydik2-zstd-1.4.5-aarch64-unknown-linux-gnu-bin/share/info -DCMAKE_INSTALL_MANDIR=/nix/store/d22hgjjfcvinfsf439d0qli8js9vcbmm-zstd-1.4.5-aarch64-unknown-linux-gnu-man/share/man -DCMAKE_INSTALL_OLDINCLUDEDIR=/nix/store/10b3gzfkpjmvgf7xgr4pzdi2w6a7zr7h-zstd-1.4.5-aarch64-unknown-linux-gnu-dev/include -DCMAKE_INSTALL_INCLUDEDIR=/nix/store/10b3gzfkpjmvgf7xgr4pzdi2w6a7zr7h-zstd-1.4.5-aarch64-unknown-linux-gnu-dev/include -DCMAKE_INSTALL_SBINDIR=/nix/store/xfm72dlsd9lvsq2qaggkvzflamfydik2-zstd-1.4.5-aarch64-unknown-linux-gnu-bin/sbin -DCMAKE_INSTALL_BINDIR=/nix/store/xfm72dlsd9lvsq2qaggkvzflamfydik2-zstd-1.4.5-aarch64-unknown-linux-gnu-bin/bin -DCMAKE_INSTALL_NAME_DIR=/nix/store/qk8fh1inf89rbd5c9d6ydkrpsvn2zycw-zstd-1.4.5-aarch64-unknown-linux-gnu/lib -DCMAKE_POLICY_DEFAULT_CMP0025=NEW -DCMAKE_OSX_SYSROOT= -DCMAKE_OSX_ARCHITECTURES=x86_64 -DCMAKE_FIND_FRAMEWORK=last -DCMAKE_STRIP=/nix/store/x8f9rbkl7pgnk93cznv07wdaiyi2sabk-aarch64-unknown-linux-gnu-binutils-2.31.1/bin/aarch64-unknown-linux-gnu-strip -DCMAKE_RANLIB=/nix/store/x8f9rbkl7pgnk93cznv07wdaiyi2sabk-aarch64-unknown-linux-gnu-binutils-2.31.1/bin/aarch64-unknown-linux-gnu-ranlib -DCMAKE_AR=/nix/store/x8f9rbkl7pgnk93cznv07wdaiyi2sabk-aarch64-unknown-linux-gnu-binutils-2.31.1/bin/aarch64-unknown-linux-gnu-ar -DCMAKE_C_COMPILER=aarch64-unknown-linux-gnu-gcc -DCMAKE_CXX_COMPILER=aarch64-unknown-linux-gnu-g++ -DCMAKE_INSTALL_PREFIX=/nix/store/qk8fh1inf89rbd5c9d6ydkrpsvn2zycw-zstd-1.4.5-aarch64-unknown-linux-gnu -DZSTD_BUILD_SHARED:BOOL=ON -DZSTD_LEGACY_SUPPORT:BOOL=OFF -DZSTD_BUILD_TESTS:BOOL=ON -DCMAKE_SYSTEM_NAME=Linux -DCMAKE_SYSTEM_PROCESSOR=aarch64 -DCMAKE_HOST_SYSTEM_NAME=Linux -DCMAKE_HOST_SYSTEM_PROCESSOR=x86_64
/nix/store/s8j52cp531jqndrl5aa6y47y99hxc4j0-cmake-3.17.2-aarch64-unknown-linux-gnu/nix-support/setup-hook: line 107: /nix/store/s8j52cp531jqndrl5aa6y47y99hxc4j0-cmake-3.17.2-aarch64-unknown-linux-gnu/bin/cmake: cannot execute binary file: Exec format error
builder for '/nix/store/8qj0ps73vg5qqva1zkrn9szmy94vqwy0-zstd-1.4.5-aarch64-unknown-linux-gnu.drv' failed with exit code 126

I don't really understand why it tries to invoke the aarch64 cmake - it's passed into nativeBuildInputs… :thinking:

for me it still fails with the above-mentioned LONG_BIT error.
i was told to cc @FRidh as he might have valuable insight

It takes the header from x86 instead of arm hence it fails because long is shorter.

Aah, I see - it fails at zstd already when trying via pkgs.pkgsCross.aarch64-multiplatform, but for  pkgsCross.armv7l-hf-multiplatform.btrfs-progs, I can reproduce the build failure from above.

Actually, no. pkgs.pkgsCross.aarch64-multiplatform.btrfs and pkgsCross.armv7l-hf-multiplatform.btrfs-progs both fail in zstd.
The btrfs-progs build failure here is another one, only surfacing when you try to build a whole NixOS closure via (pkgs.Cross.{…}.nixos ./path-to-configuration.nix).config.system.build.toplevel. Weird.

@flokli i can't confirm that building btrfs-progs fails at zstd (see attached log)
nix-build '<nixpkgs>' -A pkgsCross.armv7l-hf-multiplatform.btrfs-progs output.log
<nixpkgs> points to nixos-unstable-channel (at rev: 0a146054bdf6f70f66de4426f84c9358521be31e)

@betaboon try nix-build -A pkgsCross.armv7l-hf-multiplatform.btrfs-progs from a nixpkgs checkout pointing to 1357624fa9e (latest master as of now)

@flokli on 22c98819ccdf042b30103d827d35644ed0f17831 i can reproduce that it now fails on zstd

@betaboon zstd cross has been fixed by https://github.com/NixOS/nixpkgs/pull/91177, so now it should be btrfs-progs again ;-)

The original issue sounds like precisely the sort of thing my pkg-config wrapper we supposed to fix. I bet @matthewbauer's change, unreverted, will get us close.

OK this builds for me now after https://github.com/NixOS/nixpkgs/pull/91177, no changes needed.

@Ericson2314 i can confirm that this now cross-compiles for pkgsCross.aarch64-multiplatform.
for pkgsCross.armv7l-hf-multiplatform it still fails with #error "LONG_BIT definition appears wrong for platform for me on current master.

I can confirm the same findings, with nixpkgs master at d8d19f249793966d1cce391d54203cc717764e63.

pkgsCross.aarch64-multiplatform.btrfs-progs succeeds
pkgsCross.armv7l-hf-multiplatform.btrfs-progs fails

This breaks the minimal cross build, as udisks2 is pulled in by default in the minimal image.
Reasoning on why we usually want udisks: https://github.com/NixOS/nixpkgs/pull/49270#issuecomment-434743638

Possibly related issue: #63043 (problems cross compiling with python, the same LONG_BIT error, and so on) Haven't checked whether #91178 make a difference to it yet.

I'm thinking it very well might

@Ericson2314 If you're referring to #91178 making a difference to #63043, I checked and it doesn't.

This is fixed by #98915.


Change dateCreated descriptor property from epoch time to higher precision format

Requirements:

Adopt ISO 8601 UTC format with microsecond precision enforcement, disallowing timezone selector (even 'Z'):
2022-10-14T10:20:30.405060 would be an accepted string.
2022-10-14T10:20:30.405060Z would NOT be an accepted string.
2022-10-14T10:20:30.405 would NOT be an accepted string.

This allows us to compare time using a direct string compare.

Can we even get microsecond on all platforms/envs? I guess you'd just write in 0s if not, right?

Pretty sure all modern machine can get microsecond precision, if not implementor can either fill with 0s, or random generate 3 digits.

Have a doubt , the current format is number and all comparisons happen with the same but to support format like 2022-10-14T10:20:30.405060 we will have to convert the usage of dateCreated  everywhere from number to string .Is this expected as a part of this feature?

@rajakash-dev, yes you are correct, that's the change

https://github.com/TBD54566975/dwn-sdk-js/pull/142

@csuwildcat, please update DWN spec accordingly.

Will do


fix: :bug: fixed sample cypress project

Fixes #324

[x] Working Cypress Cucumber project in TypeScript
[x] Working HTML reporter with TypeScript

:rocket: This pull request is included in v3.8.0. See Release 3.8.0 for release notes.


Add support for key_ops.

Codecov Report

Merging #15 (20d73c0) into main (357b4d1) will decrease coverage by 1.89%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main      #15      +/-   ##
==========================================
- Coverage   96.96%   95.07%   -1.90%
==========================================
  Files           6        6
  Lines         330      345      +15
  Branches       44       50       +6
==========================================
+ Hits          320      328       +8
- Misses          7       14       +7
  Partials        3        3

Impacted Files
Coverage Δ

mkkey/cli.py
89.72% <100.00%> (-4.68%)
:arrow_down:

mkkey/jwk.py
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


helper.js:toSymbolKind(): add more universal ctags kinds

First thank you for your ctags companion extension.  It helps me a lot.
Currently only "class", "function", "member", and "variable" kind-tags are mapped to SymbolKind. Universal-ctags support much more kind-tags.
I tried to map more universal-ctags kind-tags to SymbolKind as shown in this table.
By this fix most of kind-tags for program languages will be supported.
Note: "member" was mapped to SymbolKind.Method.  I changed the mapping to SymbolKind.Property.

Great, I will make a release tomorrow.


backendServiceSyncer support for --force.

oops, didn't mean to crate a PR into the real repo yet.


Video Unavailable

The YouTube video (https://www.youtube.com/embed/JbL2-HJ8clE) embedded in this page is not available. Please provide the updated URL if available.

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

ID: 64b2fae9-3356-f90c-8b3c-647aa2ad5f75
Version Independent ID: 5ee251f0-8e8b-47eb-937c-356e15c341ba
Content: Set data alerts in the Power BI service - Power BI
Content Source: powerbi-docs/create-reports/service-set-data-alerts.md
Service: powerbi
Sub-service: pbi-reports-dashboards
GitHub Login: @maggiesMSFT
Microsoft Alias: maggies

Hi, @sayan-mohd -- happy news! We were able to get all the videos back online again.


Update es-ES.coffee

Some lines translated/updated to spanish.
Best Regards!!!

Thank you, @GrecK0


Unbreak master on buildfarm

buildfarm is broken because of checks on llvmlite version is failing during loading of entrypoints.
for example, buildfarm is creating llvmlite version:
>>> import llvmlite
>>> llvmlite.__version__
'0.33.0dev0+17.gc4f5a08'

The version spec comparison thinks the above is greater than 0.33.0dev0 and fails.
To replicate the problem, get a llvmlite from buildfarm and just run
$ python -m numba.runtests numba.tests.test_entrypoints.TestEntrypoints.test_entrypoint_tolerance

smoking at numba_smoketest_cpu_39


carousel stop when i swiper to right, it can't loop

my code:
<Carousel
                    layout={'default'}
                    data={this.state.entries}
                    renderItem={this._renderItem.bind(this)}
                    sliderWidth={viewportWidth}
                    itemWidth={viewportWidth*0.575}
                    loop={true}
                    firstItem={2}
                    loopClonesPerSide={10}
                    //enableMomentum={true}
                    enableSnap={true}
                    inactiveSlideScale={0.95}
                    inactiveSlideOpacity={0.8}
                    onSnapToItem={(index) => this.setState({currentSwiperFilm:index}) }
/>

example when i swiper end of right, slider not loop

i had add gif image demo my issue, please help me :(

i see in docs props , Number of clones to append to each side of the original items, but it not append to end of right

@nguyenvanphuc2203 Ok, so you not only don't care about what's asked of you in order to assist you (e.g. reading and filling the issue template, providing a snack example), you also downvote the very people who are devoting their spare time to maintain/improve the plugin and help others.
This behavior is not appreciated here and is not going to get you anywhere. Good luck figuring things out on your own!

Hi @LuisRodriguezLD,
I'll soon be working on an update that, hopefully, will fix a lot of issues like this one. Fingers crossed though, because it will still rely on ScrollView and FlatList which have a long history of not being that reliable...

Hi @LuisRodriguezLD,
I'll soon be working on an update that, hopefully, will fix a lot of issues like this one. Fingers crossed though, because it will still rely on ScrollView and FlatList which have a long history of not being that reliable...

does it resolve ????

i am having the same problem. Has anyone fixed this issue


Feature - Provide an external endpoint to fetch HA bootstrap script

It would be really helpful to download HA script from an external endpoint (without any authentication) via REST call.
2 step process:

Send HTTP request to some endpoint to get HA script. Request should have following information

RancherServer version
RancherAgent version (not sure if this is needed)

As response, it provides a template bash script which requires  arguments (or as environment variable) needed to setup HA. Eg. cert, registrationURL etc..

Sample REQUEST
GET /rancher-ha/v1?server_version=1.2.0
HOST: api.rancher.io

POST /v1/haconfigs/haconfig?action=createscript
{
  "hostRegistrationUrl":"https://asdf",
  "clusterSize":"3",
  "httpsPort":"443",
  "httpPort":"80",
  "swarmPort":"2376",
  "ppHttpsPort":"444",
  "ppHttpPort":"81",
  "redisPort":"6379",
  "zookeeperClientPort":"2181",
  "zookeeperQuorumPort":"2888",
  "zookeeperLeaderPort":"3888"
}

Hey @vincent99
I was looking for a shared/open URL like https://api.rancher.io/v1/haconfigs/haconfig?action=createscript&server_version=1.1.0 This would help the community to have one source of truth and not rely on custom/local setup.

Closing this issue as it's not required anymore. Bootstrapping rancher server cluster is much simpler now


surface-control: 0.4.2-1 -> 0.4.3-1

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/linux-surface/surface-control/releases.
meta.description for surface-control is: "Control various aspects of Microsoft Surface devices on Linux from the Command-Line"
meta.homepage for surface-control is: "https://github.com/linux-surface/surface-control"
meta.changelog for surface-control is: ""
Updates performed

Rust version update

To inspect upstream changes

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.4.3-1 with grep in /nix/store/6ymn3jzfn7qman3syc1m02bkli6xb2k7-surface-control-0.4.3-1
found 0.4.3-1 in filename of file in /nix/store/6ymn3jzfn7qman3syc1m02bkli6xb2k7-surface-control-0.4.3-1

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
surface-control

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/6ymn3jzfn7qman3syc1m02bkli6xb2k7-surface-control-0.4.3-1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A surface-control https://github.com/r-ryantm/nixpkgs/archive/7b3a66fcf4e704f0a9478b0adec187f5bf6ad4cd.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/6ymn3jzfn7qman3syc1m02bkli6xb2k7-surface-control-0.4.3-1
ls -la /nix/store/6ymn3jzfn7qman3syc1m02bkli6xb2k7-surface-control-0.4.3-1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.


swift: fix build against gcc-13

Without the change swift build fails on bundled llvm on staging-next as:
In file included from /build/src/llvm-project/llvm/lib/Support/Signals.cpp:14:
/build/src/llvm-project/llvm/include/llvm/Support/Signals.h:119:24:
    error: unknown type name 'uintptr_t'; did you mean '__intptr_t'?
  void CleanupOnSignal(uintptr_t Context);
                       ^~~~~~~~~
                       __intptr_t

THe change pulls in upstream fix.
Description of changes

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

@ofBorg eval


Get translation from default value

In some frameworks we can set default Values or fallback values.
It would be nice if there is no translation if we could get the Translation for the selected language from the default value.

Hi @Fibs7000 I am not very sure I have understood your request. Can you provide some examples?


Fail to update a database on Dropbox

Hi, When I want to update a database on dropbox it give me the error shown.
If I delete from dropbox the database before save, it doesn't fail.

I use a KeyFile to encript the database.
Is really helpfull the plugin, thanks

Hi @ewmartinez
Did you solved your trouble?
I have the same problem
Best regards


Add CacheStorage driver as another option for user to do offline storing of data

@thgreasi Can we add this feature in this library.

The Cache API is meant for Request/Response objects, as I understand it, and not for generic storage. See: https://developer.mozilla.org/en-US/docs/Web/API/Cache.
It's in the name; the Cache backend serves as a way for responses to be cached temporarily, but it isn't generic storage. I'm not sure why we'd want to add support for Cache storage—what benefits would it bring over IndexedDB?
(That said, you can write your own custom driver for localForage; see info about custom drivers in the README: https://github.com/localForage/localForage#custom-drivers)

As of iOS 14, CacheStorage is the sole means of sharing data between Safari an an "installed PWA" (added to homescreen). This is important if you don't want the user to re-login, etc.
More reading:

https://firt.dev/ios-14/#storage-shared-with-safari
https://stackoverflow.com/questions/62669966/how-to-maintain-login-status-in-a-pwa-initially-loaded-via-safari-14-ios-14
https://stackoverflow.com/questions/21109615/ios7-safari-saving-to-home-screen-and-persist-token

Not saying localForage should support this, but there now is a valid, unique use case for this driver. 🙂


Update ParameterValue.kt to fix a typo

Fixed the typo 'ColoValue' to 'ColorValue' as mentioned in the #78

Hi @moingshaikh thank you for your contribution, but your build failed because 'ColoValue` is also used in other classes. It would be cool if you could also the change the other occurrences :)

Hi @moingshaikh thank you for your contribution, but your build failed because 'ColoValue` is also used in other classes. It would be cool if you could also the change the other occurrences :)

Thank you for the update, @Foso. I wasn't sure about this but gave it a try since it looked like a one-shot fix to me.
I will try my best to fix this on other places soon :)

I'll close this PR for now. Feel free to reopen it once you have fixed the build issues. :)


Cannot use same field more than once

I would like to use the same field in a view more than once, but aparently field names can be used only one time.
For example. I have a view displaying the field "ImgPath" once for showing a picture (template ) and a second time for displaying the value of that field.

It's not possible for now, and it's a know problem.
But, using an ElementTransformer (as explained here), you can duplicate a value from the API response under two separate keys, and map to the second key in your config:
app.config(function(RestangularProvider) {
    RestangularProvider.addElementTransformer('myElement', function(element) {
        element.key2 = element.key1;
        return element;
    });
});

var myElement = nga.entity('my_element');
bookEntity.editionView()
    .fields([
        nga.field('key1'),
        nga.field('key2')
    ]);


Add darwin-arm64 to supported install.sh archs

What
Fixes macOS on M1 execution of ./install.sh
Why
curl -s https://raw.githubusercontent.com/rancher/k3d/main/install.sh | bash
No prebuilt binary for darwin-arm64.
To build from source, go to https://github.com/rancher/k3d
Failed to install k3d
	For support, go to https://github.com/rancher/k3d.

Implications
Does not affect existing functionality of actual CLI

I tested this in a very rudimentary way by running:
$ curl -s https://raw.githubusercontent.com/rancher/k3d/main/install.sh | sed 's/amd64/arm64/' | bash
Preparing to install k3d into /usr/local/bin
Password:
k3d installed into /usr/local/bin/k3d
Run 'k3d --help' to see what you can do with it.

Hi @colelawrence , thanks for your contribution! Merging right away 👍


Update init.md

this page needs more explanation guys thanks I love u I love your work

There's nothing to add. The init command have no flags or settings. It just creates a package.json file.


ignore bak file on commit

we're no generating this files during the build, why are you adding it?

Bak, swp etc are files tied to the OS/env you are working with, instead of
polute .gitignore with custom matches for each user might be a better
approach to put those ignores on .git/info/exclude which will give you the
same without having to commit .gitignore
On Wednesday, 27 July 2016, fanchuanster<EMAIL_ADDRESS>wrote:

You can view, comment on, or merge this pull request online at:
https://github.com/ging/licode/pull/510
Commit Summary

ignore bak file on commit

File Changes

M .gitignore https://github.com/ging/licode/pull/510/files#diff-0
(1)

Patch Links:

https://github.com/ging/licode/pull/510.patch
https://github.com/ging/licode/pull/510.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ging/licode/pull/510, or mute the thread
https://github.com/notifications/unsubscribe-auth/AACgamyltogHDiHqH5glNTFFIuVaHRg-ks5qZ06ggaJpZM4JWImx
.

--
Sent from Gmail Mobile


gf.path.smooth fails with near-collinear points

Describe the bug
When gf.path.smooth is given a sequence of points with 1e-6 < angle < 360 / npoints, it fails because the bend method returns no points.
To Reproduce
import gdsfactory as gf
p=gf.path.smooth(points=[(0,0), (0,1000), (1, 10000)])
# IndexError: index -1 is out of bounds for axis 0 with size 0

Expected behavior
Angles smaller than the interpolation limit should generate at least one point.
Suggested fix
Add an npoints argument to gf.path.smooth and modify this line:
https://github.com/gdsfactory/gdsfactory/blob/578a0d950b8c6829421f13b5ee5881dc9182733b/gdsfactory/path.py#L1295
so that it passes npoints=max(npoints, int(360 / dt) + 1) to bend. In some adversarial cases this will generate more than one point, but it should always guarantee at least one point is returned.

Thank you Orion for the suggested fix
https://github.com/gdsfactory/gdsfactory/pull/1093
I will release gdsfactory 6.18.4 with the fix
@tvt173 and @flaport  have implemented a non-manhattan router that allows you to route diagonal routes, which may be also useful

@tvt173 and @flaport have implemented a non-manhattan router that allows you to route diagonal routes, which may be also useful

Where can I find this router?

I think they still need to send a PR for this


Figma Design for Coaching Dashboard

Create an initial figma design for the coaching dashboard
https://www.figma.com/file/2rLsjlDrHHVE4YAbP65Mny/Updated-Smart-Clothing-Mobile-Wireframe?type=design&node-id=0-1&mode=design&t=yl5M7jpRUmFmN9Ro-0

First image is in regards of landing page. Welcome touch with a roster of the team, carousel of team highlights, and CSUN moto. Header for greeting the currently logged in user. Settings page and alerts are for editing profile and potential alerts from coaching staff to students. Side navbar is created to depict if it's a student or staff logged in. Nav bar is in the case of athlete login. Only able to see their profiles. Option also includes a link to boracle's website.

Second image is if a student would login for their profile. Would show basic information of student athlete. Currently would display graphs such as Intensity and sprint distance. Possible chart to use to display graphs would be chart.js

This looks good for starting. I would clean up the colors. Try to make them more consistent. Also think about how this would look on mobile screens as well. Although this won't be part of the native mobile app, it should still be adaptive to mobile devices when accessing from the web on a mobile device.

Continued here: https://github.com/CSU-Northridge-ARCS-Dev/coaching-dashboard/issues/1


Unzip stops prematurely in Node 0.10.0

Unzip stops prematurely in Node 0.10.0 without an error when inflating compressed files that are larger than the zlib stream's highWaterMark (16 kb). I believe the issue is the line self._untilStream.pipe(vars.compressedSize, inflater).pipe(entry) - the inflater stream never emits 'end' or 'finish'.
Code:
if (fileSizeKnown) {
  entry.size = vars.uncompressedSize;
  self._untilStream.pipe(vars.compressedSize, inflater).pipe(entry);
}

The error surfaced while I was investigating #19.

Hello I was having an issue with close not being called when these errors were happening for parser.on('error'):
entry:
Error: invalid signature: 0xa
    at /var/www/test/unzip-test/node_modules/unzip/lib/parse.js:59:13
    at processImmediate [as _immediateCallback] (timers.js:345:15)

entry:
Error: invalid code lengths set
    at Zlib._binding.onerror (zlib.js:295:17)

I ended up googling around and found this issue:
https://github.com/EvanOxfeld/node-unzip/issues/47
So i tried cloning this repo:
https://github.com/AnkurMali/node-unzip
And this fixed my problem,.  The errors completely went away and I was able to extract the file (no error) and the close method was being called.

Hi, I installed from npm, used as:
fs
            .createReadStream(req.file.path)
            .pipe(
              unzip.Extract({
                path: webBuildFolder
              }).on('close', function() {
                console.log('NOW!');
              })
            )

And getting error with Mac packed archives:
invalid signature: 0xa


How might we handle adaptive streaming in a video info.json?

This question is a specialization of how we are handling progressive download videos by listing them out as individual sources. You can see an example of listing sources in https://github.com/IIIF/iiif-av/issues/50
With adaptive streaming like HLS and MPEG-DASH what information should we include for a source? Each of these formats basically points to a document which is a manifest (media presentation description) of all the different adaptations that are available for a video. The client can then select which to play based on bandwidth and resolution and switch sources mid-stream based on conditions. In some cases a single file is used for each adaptation (on demand profile which then uses byte-range requests for segments) and in others the source video at different bitrates and resolutions are each pre-segmented (live profile).
The assumption is that for some cases multiple sources are still likely to be listed even with an adaptive version available. This could be because both an HLS and MPEG-DASH stream are made available to reach more devices. (Currently these both use different underlying media formats and so work on different platforms--though the latest HLS allows for fragmented MP4s as MPEG-DASH has been using.) The listed sources could also include a progressive download source to work for clients that don't support the adaptive formats and that can't run a client-side library (e.g. hls.js and dash.js).
I could see this going two ways. In both cases we would list the URL to the media presentation description document as one of the sources. We would list out information relevant to the source at a high level like format. But then we could either stop there, or we could also list out the available adaptations within each adaptive streaming source. Basically the server creating the info.json for a video could look inside the media presentation document and pull out information about each adaptation. This seems duplicative but maybe useful to have this information all with the single request for the info.json? Would it ever change the decision about whether to play an adaptive stream based on which adaptations are available?
Though it isn't required it is also common, recommended practice for the audio adaptation(s) to be separate from the video adaptation(s). This means that if we were going to describe the adaptations for a source we would be describing the technical details of both the audio and video which could either be separate files or multiplexed.
Thoughts on this? Other ways we could handle adaptive bitrate streaming in a video info.json?

Thanks for writing this up, Jason. My view would be not to make things too complicated and to follow your suggestion of just having an entry in the info.json pointing to the adaptive streaming manifest (M3U8 or MPD) along with as many properties as are common to and known about the sources referenced by that manifest. I agree it should be possible to list adaptive sources alongside standalone sources.

Completely agree with Jon -- lets start simple and get traction first.  That would mean simply pointing to the streaming manifest, with the same basic properties as for the other formats.

Sounds good to me. I'll work on adding an example to a my prototype.

(outsourced as Prezi can just refer to HLS, and clients use the format specific info)

Propose close, out of scope / solved by adaptive formats already

Agree with close / out of scope.

This issue came up on 2017-03-07 AV call in the context of a set of streams at different bitrates from Avalon. Agreement on call was that adaptive streaming based on these is out of scope (use a format that supports it instead) and that the use case is really about user selection (where label for each stream indicating difference is adequate).


Long press from longPressAndDrag not being detected until after drag is completed

What happened?
I have tried to integrate it into a test in my app which involves a draggable flatlist from https://www.npmjs.com/package/react-native-draggable-flatlist. This flatlist has its list items wrapped inTouchableHighlight elements with onLongPress={drag}. When running the tests it seems that it tries to press but it isn't detected by the system, then it does the drag (which doesn't accomplish much). After the longPressAndDrag, it looks like a press is then detected.
I removed the dependency of react-native-draggable-flatlist and logged when the onLongPress on the TouchableHighlight is called and it's not called until after the longPressAndDrag action finishes. I tried a normal longPress and that worked as expected and was detected by the system.
Disabling/dabbling around with synchronization produced no results.
What was the expected behaviour?
The Detox test interacts with the UI like a user would. Long press is not detected until after the whole action finishes and therefore the drag doesn't result in anything.
Was it tested on latest Detox?

[X] I have tested this issue on the latest Detox release and it still reproduces.

Did your test throw out a timeout?

[X] I have followed the instructions under Identifying which synchronization mechanism causes us to wait too much.

Help us reproduce this issue!

Clone simplified repo https://github.com/tanakaderoy/detoxIssueRepro/
Checkout branch longPressAndDragRepro
Use a compatible version of node (e.g. 16.10.0)
yarn install and yarn setup to install dependencies
yarn start to run Metro
yarn e2e-build ios.debug to build for Detox
yarn e2e-run ios.debug to run the singular test that does the longPressAndDrag

If you want to run it locally then do:

Steps 1-5 above are completed
Open ios/detoxIssueRepro.xcworkspace in Xcode
Build and run
In app, long press on a list item and then drag -> see it works as expected

In what environment did this happen?
Detox version: 20.1.0
React Native version: 18.0.0
Has Fabric (React Native's new rendering system) enabled: no
Node version: 16.10.0
Device model: iPhone 14 Pro
iOS version: 12.4
macOS version: 12.6.2 on Apple Silicon
Xcode version: 14.1
Test-runner (select one): jest
Detox logs
Github was returning the error There was an error creating your Issue: body is too long (maximum is 65536 characters). when I had the log in here so I put it in pastebin.
https://pastebin.com/WBwYve4U
Device logs
Device logs
arron.ault@HUD040087 detoxIssueRepro % yarn e2e-run ios.debug --record-logs all
yarn run v1.22.19
$ detox test -c ios.debug --record-logs all
17:40:49.876 detox[43451] B jest --config e2e/jest.config.js
watchman warning:  Recrawled this watch 5 times, most recently because:
MustScanSubDirs UserDroppedTo resolve, please review the information on
https://facebook.github.io/watchman/docs/troubleshooting.html#recrawl
To clear this warning, run:
`watchman watch-del '/Users/arron.ault/detoxIssueRepro' ; watchman watch-project '/Users/arron.ault/detoxIssueRepro'`

17:40:54.203 detox[43453] i drag.e2e.ts is assigned to 1B71F80E-EEC3-49A8-A570-B4A8F58A2249 (iPhone 12)
17:40:56.075 detox[43453] i org.reactjs.native.example.detoxIssueRepro launched. To watch simulator logs, run:
        /usr/bin/xcrun simctl spawn 1B71F80E-EEC3-49A8-A570-B4A8F58A2249 log stream --level debug --style compact --predicate 'process == "detoxIssueRepro"'
17:40:57.936 detox[43453] i Drag: should drag and rearrange
17:41:03.602 detox[43453] i Drag: should drag and rearrange [OK]

 PASS  e2e/drag.e2e.ts (13.11 s)
  Drag
    ✓ should drag and rearrange (5601 ms)

✨  Done in 14.38s.
arron.ault@HUD040087 detoxIssueRepro %

More data, please!
https://user-images.githubusercontent.com/84314259/213827704-267c383a-4c63-4b51-95dd-edb23165aa19.mp4

Thanks for providing the repository for the reproduction. I hope @asafkorem will be able to look at it soon.

Hi @asafkorem, is there any update on this please?

Hi @aaulthudl, sorry, I haven't gotten to it yet. I will take a look today or tomorrow.

I was able to reproduce this issue. Investigating.

Hey @aaulthudl, thanks for report. Indeed, it looks like there's some conflict with the gesture handling of this library (and its dependency - RN-Gesture-Handler) and Detox, which will require deeper investigation from my end.
For the meanwhile, I think I found some workaround for you (please confirm).
Add a separate await from.longPress(1000); call right before calling longPressAndDrag. It worked for me with the reproduction test although it shouldn't basically, I will keep this issue open and will update here with any future progress on that matter.

@asafkorem

Hey @aaulthudl, thanks for report. Indeed, it looks like there's some conflict with the gesture handling of this library (and its dependency - RN-Gesture-Handler) and Detox, which will require deeper investigation from my end.
For the meanwhile, I think I found some workaround for you (please confirm). Add a separate await from.longPress(1000); call right before calling longPressAndDrag. It worked for me with the reproduction test although it shouldn't basically, I will keep this issue open and will update here with any future progress on that matter.

It didn't work for me sadly.

This is still required

Is there any update on this issue please?

Bump on this again please

Any update regarding this please?

@asafkorem Any update on this please?

This is also an issue for us. We need to run longPressAndDrag twice in the test, which can cause test errors related to visibility of the pressable item if a ScaleDecorator is used.

Unfortunately, there isn't a straightforward solution for your case I can point on because we rely on Apple's APIs to trigger this interaction rather than using a custom implementation in Detox (see reference).
Currently, there is no priority or ETA from the Detox team to investigate this issue. However, we welcome external contributors who are interested in exploring this further and possibly implementing a better mechanism.


XML Docs are not being generated for DotNet libraries.

Version
Probably all packages released since march 22 2019.
Describe the bug
Xml documentation is not being generated for any of the BotBuilder libraries.
To Reproduce
Try compiling the Release and Docuementation packages and none of the xml files are being generated.
I also checked the latest nuget packages and the XML files are not there.
Expected behavior
Xml docs should be generated.
Additional context
It seems that this PR deleted the settings to generate the XML documentation from Directory.Build.Props.
[bug]

@Kaiqb as an FYI

Solved via #2079


Implement import from csv

Implement import data from csv
Test data stored in test/data/test_data.csv

Codecov Report

Merging #73 (8d8dd69) into master (d003d06) will decrease coverage by 1.74%.
The diff coverage is 0.00%.

@@             Coverage Diff              @@
##             master      #73      +/-   ##
============================================
- Coverage     55.79%   54.05%   -1.75%
  Complexity      441      441
============================================
  Files            94       96       +2
  Lines          1733     1787      +54
  Branches        225      235      +10
============================================
- Hits            967      966       -1
- Misses          694      748      +54
- Partials         72       73       +1

Impacted Files
Coverage Δ

...main/java/seedu/address/commons/util/FileUtil.java
73.91% <0.00%> (-3.36%)
:arrow_down:

...va/seedu/address/logic/commands/ImportCommand.java
0.00% <0.00%> (ø)

.../seedu/address/logic/parser/AddressBookParser.java
88.88% <0.00%> (-11.12%)
:arrow_down:

...eedu/address/logic/parser/ImportCommandParser.java
0.00% <0.00%> (ø)

.../java/seedu/address/model/util/SampleDataUtil.java
0.00% <ø> (ø)

Continue to review full report at Codecov.

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


cannot upload images for no reason

I used your awesome upload module to upload images.
composer.json require
"matriphe/imageupload": "5.*"

form
<input type="file" class="form-control" name="image" accept="image/gif, image/jpeg, image/png">

controller
if ($request->hasFile('image')) {
            Log::debug('Upload images: '.$post->id);
            Imageupload::upload($request->file('image'), $post->id);
        }

config
'newfilename' => 'custom',

However I couldn't upload the following image:
image
I don't know why.
I can upload jpeg, jpg, png, gif files without problems.
weird

I downloaded your image, and uploaded it successfully on my laptop. Is there any error or exception thrown?
Have you set the max upload size in the php.ini?
What version of Laravel or this package do you use?

Do you have enctype="multipart/form-data" on your form?

I think maybe there is an upload size limit on it. Thanks


improve visual design of multiple departments displayed on the front page

This is what it looks like currently:


User/vchintalapat/GitHub actions test

--> Added a github_actions_test workflow and a sample .NET app to this repository
--> The github_actions_test workflow runs every 3 hours, updates a placeholder in the dotnet app with the current UTC time, and deploys the app to Azure App Service.

let's add a test for nodejs too, especially for scenario where app is prebuilt by cx

Looks good!


MoreCollectors.optionals()

A new collector that adapts downstream collector to work with Stream of Optional.
It has all or none semantics: if at least one element is empty the result will be Optional.empty().
IntStreamEx.ints()
            .map(i -> i % 2 == 0 ? null : i)
            .mapToObj(Optional::ofNullable)
            .limit(12)
            .collect(optionals(groupingBy(i -> i % 3)))

>> Optional.empty

IntStreamEx.ints()
            .mapToObj(Optional::ofNullable)
            .limit(12)
            .collect(optionals(groupingBy(i -> i % 3)))

>> Optional[{0=[0, 3, 6, 9], 1=[1, 4, 7, 10], 2=[2, 5, 8, 11]}]

Coverage increased (+0.003%) to 98.548% when pulling 52eabf833c7ff66bfc8d305309f34b26c11d08f1 on nbardiuk:collector-optionals into d021d02b57c8708421d8bbd433c24271215ef5e2 on amaembo:master.

Interesting idea. Seems that it's not very easy to create such collector combining existing ones. However I don't like two things. First, it's too specific: the original stream must be a stream of optionals which is rare thing in practice and somewhat obscure. Second, the name optionals says very little about what collector actually does. I propose something more generic:
    public static <T, A, R> Collector<T, ?, Optional<R>> ifAllMatch(Predicate<T> predicate, Collector<T, A, R> downstream) {
        Predicate<A> finished = finished(downstream);
        Supplier<A> supplier = downstream.supplier();
        BiConsumer<A, T> accumulator = downstream.accumulator();
        BinaryOperator<A> combiner = downstream.combiner();
        return new CancellableCollectorImpl<>(
                () -> new PairBox<>(supplier.get(), Boolean.TRUE),
                (acc, t) -> {
                    if(acc.b && predicate.test(t)) {
                        accumulator.accept(acc.a, t);
                    } else {
                        acc.b = Boolean.FALSE;
                    }
                },
                (acc1, acc2) -> {
                    if(!acc1.b || !acc2.b) acc1.b = Boolean.FALSE;
                    else {
                        acc1.a = combiner.apply(acc1.a, acc2.a);
                    }
                    return acc1;
                },
                acc -> acc.b ? Optional.of(downstream.finisher().apply(acc.a)) : Optional.empty(),
                finished == null ? acc -> !acc.b : acc -> !acc.b && finished.test(acc.a),
                downstream.characteristics().contains(Characteristics.UNORDERED) ? UNORDERED_CHARACTERISTICS : NO_CHARACTERISTICS);
    }

This collector returns result of downstream collector wrapped into optional if all stream elements satisfy the predicate. If at least one does not satisfy the predicate, the empty optional is returned. The downstream collector is guaranteed to be called only on those stream elements which satisfy the predicate.
Now your collector can be expressed simply:
    public static <T, A, R> Collector<Optional<T>, ?, Optional<R>> optionals(Collector<T, A, R> downstream) {
        return MoreCollectors.ifAllMatch(Optional::isPresent, MoreCollectors.mapping(Optional::get, downstream));
    }

On the other hand you example can be simplified without having stream of optionals:
IntStreamEx.range(12).boxed().collect(ifAllMatch(i -> i % 2 != 0, groupingBy(i -> i % 3)));

If you like this, you may provide a new pull request with this collector (along with tests, javadoc, etc.)
Minor issues:
It's better to extract downstream.accumulator(), etc. to variables to reduce single virtual method call per each accumulated element.
If you test short-circuiting collector, it's a good idea to check it with infinite stream as well.

I usually end up with Stream of Optional when mapping function can produce null or throw exception
Stream.of("1,2,3,4,5".split(","))
    .map(this::parseInt) // String -> Optional<Integer>
    .collect(optionals(toList()));

I have very similar collector that composes futures into one that will finish only when all are done:
asList(1, 2, 3, 4, 5).stream()
    .map(this::fetchName) // Integer -> CompletableFuture<String>
    .collect(futures(toList()));

You are right these collectors are very specific and not a common way to use streams.  ifAllMatch is a better collector for library.
I will gladly submit a pull request for ifAllMatch collector

Superceded by #116.


Updated textures to close issue #42 and #10

Changed Tree, wood, and Leaf texters to look more alien like. also Changed plants to look more alien like. Changed the Brick texter to look darker and match the dark moon stone texter. Resolved merge issue from previous request.

Awesome work, thanks for making the changes to the title.


Netlify: select a new build image

Notice from Netlify

After November 15, 2022, builds for this site will fail unless you update the build image.

Thanks for reporting. I don't have permissions to view that page and AFAICT the build image isn't controlled by configuration in this repository. Are you able to help?

@joshuagl as you're a maintainer I'm able to invite you to the Netlify team -- if this is appropriate, let me know which email address you'd like me to use (either here, or in the CNCF slack)

Thanks @joshuagl, invite sent.

Thanks @nate-double-u. I followed the steps here and everything seems OK! 👍


@orta => Registration Flow Improvements

@orta, this view controller looks like it was doing a bunch at one point, but not anymore. So I removed things that didn't appear to be used (like the bid details view that was never being accessed). Please take a look over and see if everything looks good.
Before:

After:

@katarinabatina I had to eyeball the line heights. Could you verify these are correct-ish?
Fixes #436.
Fixes #437.

The https://github.com/artsy/eidolon/commit/73b269f801bf8a70d5617292b7e5dee8adff58c3 commit is work towards fixing a crash I noticed in development. Shouldn't take too much longer, then I'll be on eigen.

:+1:


pytorch 1.11.0 needed - not on anaconda

Tried installing the file requirements.txt after having installed pytorch, but it needs an older version (1.11.0) that is no longer on anaconda - any tips on how to solve this?
Thanks!

Hey cosimadp,
Any recent version of pytroch should work ! I just tested pytorch 12.1.0 which works fine.
I just updated the requirements.txt file to reflect that !
Please let me know if your issue is fixed so I can close this thread.
Wassim
PS: out of curiosity are you on linux or macOS (intel or ARM) ?

Hey Wassim,
Thanks, that worked!
Tried running your unit test to check the installation and there still are some errors:
FAIL: test_tree_rpr (physo.physym.tests.program_display_UnitTest.DisplayTest)
Traceback (most recent call last):
File "/Users/cosima/Documents/GitHub/PhySO/physo/physym/tests/program_display_UnitTest.py", line 153, in test_tree_rpr
tree_latex = my_programs.get_tree_latex(prog_idx=0,)
FileNotFoundError: [Errno 2] No such file or directory: '/var/folders/sf/p4_8lxts6r33flfn1fj9zg0w0000gn/T/dot2tex4ix3jpou/dot2tex.log'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/Users/cosima/Documents/GitHub/PhySO/physo/physym/tests/program_display_UnitTest.py", line 157, in test_tree_rpr
self.fail("Tree generation failed : get_tree_latex")
AssertionError: Tree generation failed : get_tree_latex
Any idea what those might be related to? The program ran for a bit before exiting with this error log.
I’m using macOS.
Thanks so much for your help!

On Mar 15, 2023, at 5:22 PM, Wassim Tenachi @.***> wrote:
Hey cosimadp,
Any recent version of pytroch should work ! I just tested pytorch 12.1.0 which works fine.
I just updated the requirements.txt file to reflect that !
Please let me know if your issue is fixed so I can close this thread.
Wassim
PS: out of curiosity are you on linux or macOS (intel or ARM) ?
—
Reply to this email directly, view it on GitHub https://github.com/WassimTenachi/PhySO/issues/4#issuecomment-1471020785, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARJDM7WE2MWZTQ5OOPLW4ZLW4JMNHANCNFSM6AAAAAAV4QFH6M.
You are receiving this because you authored the thread.

So it sounds like you are not able to pass the tests for the function generating the tree representation of a symbolic function.
This is not a problem as this is a debug feature only intended for advanced users who plan on contributing code.
You wont need that if you are just planning on using this code for SR ! :)
You can even delete the program_display_UnitTest.py or comment its content.
Are you able to pass all other tests except for the ones in program_display_UnitTest.py ?
Do you have a mac M1 ?
Wassim

If you still want to install these optional packages, you can try pulling the latest version from git and run:
conda install --file requirements_display1.txt pip install -r requirements_display2.txt
Which should install those packages smoothly.
Wassim

Hey Wassim!
Installed your new packages, thanks!
What other tests can I try? Like the demos?
Yeah Mac M1 - is that an issue?
Thanks a lot!
Cosima

On Mar 15, 2023, at 6:44 PM, Wassim Tenachi @.***> wrote:
So it sounds like you are not able to pass the tests for the function generating the tree representation of a symbolic function.
This is not a problem as this is a debug feature only intended for advanced users who plan on contributing code.
You wont need that if you are just planning on using this code for SR ! :)
You can even delete the program_display_UnitTest.py or comment its content.
Are you able to pass all other tests except for the ones in program_display_UnitTest.py ?
Do you have a mac M1 ?
Wassim
—
Reply to this email directly, view it on GitHub https://github.com/WassimTenachi/PhySO/issues/4#issuecomment-1471151861, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARJDM7R4S2WBFOA7T5D2FFDW4JWBHANCNFSM6AAAAAAV4QFH6M.
You are receiving this because you authored the thread.

Hi @cosimadp,
It sounds like physo was not installed as a package.
Can you (re)run installation by executing this at the root of the repo ?
pip install -e .
Then can you run:
conda list
And check that physo is listed in the list of installed packages as:
physo                     1.0.dev0                  dev_0    <develop>
Demos should be ran in the same conda environment as the one where physo and its dependencies were installed.
So can you make sure that the environment  in which you are running them is the right one ?

@cosimadp can you confirm that you were able to resolve the problem so I can close this thread ?


Improves testing

Adds more tests and improves self-testing and logging

launch jenkins all

A test was removes. No need to test again.


Revert "Update scheduling-parameters.md"

Reverts sendgrid/docs#4983

Hello @Whatthefoxsays,Thanks again for the PR! We appreciate your contribution and look forward to                                              continued collaboration. Thanks!                                             Team SendGrid DX


[2.6.0] Docs for password change using store

Description:

We have the fature to change the password from the store. But it is not mentioned in the docs.
Appreciate if we could document and add it to the doc space as customers are trying out this.
Suggested Labels:

Suggested Assignees:

Affected Product Version:
OS, DB, other environment details and versions:
Steps to reproduce:
Related Issues:

@dinusha92 , is the UI of the store in 2.6.0 not intuitive enough in this aspect? Does the user need to know anything specific when using this feature?

@dinusha92  any input?

I am closing this Git issue as this is related to API-M 2.6.0, which is a relatively older version of WSO2 API-M.
[1] https://wso2.com/products/support-matrix/


RMT not working while GPIO is

For the DS18B20 library + example, the RMT driver is unable to find any devices. Switching to the GPIO driver makes it work, but I would like to make use of RMT for the stability.
My environment:
Heltec ESP32 LoRa V2
1x DS18B20 on GPIO23
Code from the example repository with owb aee423ca5797472fa6cf7c00ba27070502f9dd59 and ds18b20 4c76db4a34634aa1a2dc67a60345072590375012
Replacing:
owb_rmt_driver_info rmt_driver_info;
owb = owb_rmt_initialize(&rmt_driver_info, GPIO_DS18B20_0, RMT_CHANNEL_0, RMT_CHANNEL_1);

With
owb_gpio_driver_info gpio_driver_info;
owb = owb_gpio_initialize(&gpio_driver_info, GPIO_DS18B20_0);

Is all needed to make it work.
Not sure if it may be related, but I did also notice that the DS18B20 library in both cases thinks there is some parasitic sensor, while there is none. The attached sensor is supplied externally.
I also noticed recent commits, so could it be I should take a older/more stable version?

@Rimco thanks for reporting. Which version of the ESP IDF are you using? There's currently a known issue with recent versions, but it has been tested and shown to work with v3.3 and v4.1beta. v4.2 (unreleased) and master are definitely broken.
Please avoid using the GPIO driver as it is deprecated and will be removed soon. It is unreliable and no longer fully supported.
The root cause is related to initialisation of the RMT peripheral, and the same problem causes mis-detection of the parasite power mode. Once the issue is fixed this symptom should disappear.
Please see: https://github.com/DavidAntliff/esp32-ds18b20-example/issues/19

See also https://github.com/espressif/esp-idf/issues/5237

You can try reverting to an older version if you like - would be interesting to hear back - but if you're using a recent IDF version it will probably have the same issue. A fix (to my code) is in the works.

@Rimco please try the master branch of this component (included by the master branch of the ds18b20 example) - I am hopeful that your issue has been fixed. Please let me know.

Thanks @DavidAntliff,
I overlooked the issue already being open in the ds18b20 repository.
Your fixes seem to match the problems I noticed wrt the uninitialized variables, although I didn't think that was related to the RMT problem. I did get a backtrace due to it, pointing at the parasitic power using an uninitialized GPIO number unless you explicitly enable/disable it. I ran into this because I got rid of the broken parasitic power detection, so I would not enable/disable it at all.
I will try to use the latest versions and report back. I recently started with ESP-IDF and apparently used the master (4.2 alpha let's say) from a few days ago. If your fix does not work I will try 4.1, who knows which other bugs I have gotten for free with this cutting-edge version ;)

Latest version is working with the example code.

Thank you for testing!

pointing at the parasitic power using an uninitialized GPIO number unless you explicitly enable/disable it.

Hmm, this could still be an issue - do you have any more info on this?

The backtrace ended up in owb.c:737:
    if (bus->use_parasitic_power && bus->strong_pullup_gpio != GPIO_NUM_NC)
    {
        gpio_set_level(bus->strong_pullup_gpio, enable ? 1 : 0);

I think the uninitialized variables ended to be:
use_parasitic_power = true;
strong_pullup_gpio = random number >= 0
Because random number wasn't equal to GPIO_NUM_NC, it would try to access an non existent one.
You may want to add strong_pullup_gpio < GPIO_NUM_MAX, but solving the uninitialized variables is of course better.
Btw, I'm using your library in a C++ environment and the compiler started complaining in my C++ wrapper that = {0} would not be sufficient to initialize everything, but = {} was. I'm not that used to plain C structs anymore, but maybe something you want to verify.

Ok, thank you, I'll reopen this issue in the meantime so I don't forget about this.

In C, struct foo f = {0} guarantees that the entire structure will be initialized to zero values, because the standard requires that if one or more fields are initialized, all fields not mentioned must also be initialized to zero. Since a C struct must have at least one field, and all types can be set to zero, this always works.
In C++11, you can use foo f = {} instead, which is called zero initialization. However for foo f = {0} there's also copy initialization (before C++11), list initialization (C++11) and aggregate initialization (before and after C++11). It gets complicated fast.
https://en.cppreference.com/w/cpp/language/aggregate_initialization

If the number of initializer clauses is less than the number of members or initializer list is completely empty, the remaining members are value-initialized.

So the first field will be initialised to zero, and then the rest will be value-initialized, which because no value is specified, will result in zero-initialization.
See Explanation through to Point 4 here: https://en.cppreference.com/w/cpp/language/value_initialization
TL;DR: it should be ok, your C++ compiler might just be warning you that the initialization isn't explicit, so might not do what you expect, if you were expecting something other than zero.
Oddly I can't find any specific discussion online of using that pattern in both C & C++ code.

Ah, this was with the GPIO driver, not the RMT one, is that right?

I've fixed the uninitialised GPIO when using the GPIO driver: https://github.com/DavidAntliff/esp32-ds18b20-example/pull/21
As far as I can tell, the RMT driver is OK.

That one was indeed with the GPIO version, before you did any kind of fixes wrt the uninitialized variables.


Have a separate feature flag for single server diagnostics, that defaults to off

Fixes https://devdiv.visualstudio.com/DevDiv/_workitems/edit/1690006
I could have just reverted the PR, but I like having the code still there for easier fixing later.
It looks like the single server code never calls the diagnostic translator code, which is needed for corrent remapping of diagnotsics (since they don't strictly map) and for some filtering (eg, for edit and continue). Adding in the call seemed like it shouldn't be too hard, but the RazorDiagnosticsEndpoint is hardcoded to only call Roslyn for C# diagnostics, which means even adding that call would mean nothing is filtering or dealing with Html diagnostics, and it wasn't clear to me hiow to fix that, so in the interests of time, I've just turned them off.
FYI @ryanbrandenburg
@allisonchou since I'm away, can you look after getting this in? Its one commit, so if it needs to go in a different branch, it should be easily cherry-pickable
Also FYI @phil-allen-msft for M2/QB/whatevs

This also fixes https://devdiv.visualstudio.com/DevDiv/_queries/edit/1689005


NumSharp.Bitmap and OpenCv

I want to add some common methods to interoperate with OpenCv in NumSharp.Bitmap so that they can be shared. The advantage is that users can easily use NumSharp and OpenCv to process image applications.
For exampe: NdarrayToMat, MatToNdarray.
And we have to rely on this package OpenCvSharp4 which is about 1M size.

static unsafe void Main(string[] args)
{
    Mat src = new Mat("olga.jpg", ImreadModes.AnyColor);
    NDArray nd = WrapWithNDArray(src); //shaped (1, src.Height, src.Width, Channels)
    Bitmap bmp = nd.ToBitmap(); //using NumSharp.Bitmap
    bmp.Save("./olga-reconstructed.jpg");
}

//this method copies Mat to a new NDArray
public static unsafe NDArray ToNDArray(Mat src)
{
    var nd = new NDArray(NPTypeCode.Byte, (1, src.Height, src.Width, src.Type().Channels), fillZeros: false);
    new UnmanagedMemoryBlock<byte>(src.DataPointer, nd.size)
        .CopyTo(nd.Unsafe.Address);

    return nd;
}

//this method wraps without copying Mat.
public static unsafe NDArray WrapWithNDArray(Mat src)
{
    Shape shape = (1, src.Height, src.Width, src.Type().Channels);
    var storage = new UnmanagedStorage(new ArraySlice<byte>(new UnmanagedMemoryBlock<byte>(src.DataPointer, shape.Size, () => Donothing(src))), shape); //we pass donothing as it keeps reference to src preventing its disposal by GC
    return new NDArray(storage);
}

[MethodImpl(MethodImplOptions.NoOptimization)]
private static void Donothing(Mat m)
{
    var a = m;
}

Similar to these? (taken from https://github.com/SciSharp/NumSharp/issues/371)

@Nucs Correct, People use OpenCv a lot. We should make NumSharp and OpenCv work better. We have combined TF.NET and NumSharp. NumSharp with OpenCv is the last piece for Computer Vision.

@Nucs @Oceania2018
It would be better we can make it more generalized (data type, image layout etc. ).
as far as i know, currently there're two image layouts used by mainstream deeplearning frameworks.
cuDNN (Nvidia DNN library) is much more efficient when using NCHW,
but intel GPU would prefer to use NCHW.
tensorflow  ==> NHWC (numl, height, width, channe)
pytorch ==> NCHW (num, channel, height, width)
mxnet ==> NCHW (num, channel, height, width)
caffe ==> NCHW (num, channel, height, width)

during training or inference, sometimes we might decare ndarray with data type uint8 explicitly, sometimes float32 etc.

Our code base is deeply tied to work with tensorflow.
But a simple nd.reshape will do the trick @AvenSun because the data is linear.
With that being, I'll also add an enum parameter allowing to choose between the libraries you mentioned that'll decide the return shape.

@Nucs
yes, I knew there're several ways to transfer NCHW into CHWC and vice versa.
It'll cost extra time if we don't make it at the beginning.
This is more noticeable when the operation lies in loops.
NumSharp should be a common numerical computing library like numpy.
It should not be just for tensorflow.

@Nucs I think NumSharp is not tied to TF.NET sinze v0.20. It's TF.NET tied to NumSharp.

The thing is that all image formats I know about provide their data in a linear way, R1G1B1R2G2B2 ...
So using NHWC is actually the natural way in my opinion to handle files hence why the primary shape order should be NHWC in my opinion.
Nevertheless I'll add support for NCHW


python3Packages.vehicle: 0.2.0 -> 0.2.2

Motivation for this change
Update to latest upstream release 0.2.2
Change log: https://github.com/frenck/python-vehicle/releases/tag/v0.2.2
Things done

Built on platform(s)

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

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

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

2 packages built:

python38Packages.vehicle
python39Packages.vehicle


Support across thread tracing for SOFA-RPC

Now SOFA-PRC plugin only support in thread tracing. It does not support across thread tracing. InvokeCallback class is the key class which does the async callback work. This pr add the ability of across thread tracing by enhancing InvokeCallback class the way like org.apache.skywalking.apm.toolkit.activation.trace.CallableOrRunnableActivation do.

[x] Tests(including UT, IT, E2E) are added to verify the new feature.

[x] If this pull request closes/resolves/fixes an existing issue, replace the issue number. Closes #.

[x] Update the CHANGES log.

Please explain your scenario. When this happens, and what was not working.

I think you should add callback in https://github.com/apache/skywalking-java/tree/main/test/plugin/scenarios/sofarpc-scenario and verify the callback spans through the expected file.

@OrezzerO Is https://github.com/apache/skywalking-java/pull/676 somehow affected this plugin? Is SOFA requiring JDK21? It seems not. Could you change your local JDK to JDK8 or 11 to finish this?

@OrezzerO Is #676 somehow affected this plugin? Is SOFA requiring JDK21? It seems not. Could you change your local JDK to JDK8 or 11 to finish this?

I can change my jdk. I am not familiar with skywalking scenario test, need some time to finish this work.

I think it is not hard to run. The basic workflow is, the test is using a demo app with a compiled latest Java agent up and running. Then there is a mock traffic generator to trigger traces to the mock collector. The last step is to write expected spans to verify.

I have commit some code to verify the callback spans through the expected file. However I have some thing not very sure:

Is expectedData.yaml file strongly depends on the stop order of each span? I am using async invoke ,so the stop order is not fixed. It may affect CI success rate.
I am not sure if "my expect of cross thread tracing" is suitable for skywalking. Please review test/plugin/scenarios/sofarpc-scenario/config/expectedData.yaml carefully.

Generally, this PR is good, just some nits. Please fix them, then it is good to merge.

I tried to apply the change, but it seems not work.

I tried to apply the change, but it seems not work.

Missed import lombok.AccessLevel; statement;  added it.


optional routes support?

I have a route with an optional parameter:
[Route("{categoryId?}")]
public HttpResponseMessage Get(int? categoryId=null)

However, when I don't provide a value for categoryId the call includes {categoryId?} in the request itself...
http://myhost/api/%7BcategoryId%7D

PS: I'm using version 5.0.4

This API structure is not supported by the swagger-spec - https://github.com/swagger-api/swagger-spec/blob/master/versions/2.0.md.
In Swagger, an operation is uniquely identified by a combination of HTTP method and path (excluding query string). So, your action cannot be described as a single operation in Swagger.
Unfortunately, it's quite strict on this constraint. Can I ask what are the semantics of this operation? I'm assuming it might return a collection that can be optionally filtered by categoryId? If this is the case, a more typical URI structure would be as follows
/api/items?categoryId={categoryId}
This would be supported by Swagger because the optional parameter is part of the query string

Thanks for clarifying it.
It's actually a list of categories... so the structure would be like:
/api/categories?id={categoryId}
what looks rather weird in my opinion. Therefore I just split it in two routes:
/api/categories
/api/categories/{categoryId}


Make getter methods

My original comment:
One thing ive been thinking about is it would be nice if I could read either the oracle prices that Solo is looking at or some other way of reading my accounts collateralization.
My understanding is that this is already possible at a lower level but I dont see a way to do it in the python api.

also to piggyback on this issue, it would be great if the collateralization threshold is in https://github.com/dydxprotocol/dydx-python/blob/master/dydx/constants.py#L21 for future-proofing

This isn't blocking me (im using coinbase prices instead which I think is close enough), so this is really just for later clarity:
Getter methods that I would like:
get_oracle_price(currency):
"""
Returns the current oracle price for the currency is question that Solo is using to determine accounts collateralization.
"""

get_my_collateralization()
"""
returns your account's collateralization
"""

get_collateralization(address)
"""
returns some other account's collateralization
"""

And then just the collateralization threshold in constants.py


[BUG]: can't use openai realtime api

How are you running AnythingLLM?
Local development
What happened?
I chose the gpt-4o-realtime model in the workspace.
Then try to use it, but it shows the following error message
Could not respond to message.
404 This is not a chat model and thus not supported in the v1/chat/completions endpoint. Did you mean to use v1/ completions

Are there known steps to reproduce?
No response

Correct, dont use realtime as your model - we dont have support for it currently since it cannot handle chat message pairs

Hello,
Same for me, I just installed AnythingLLM (1.6.9), chose OpenAI and pasted an API Key.
But found why :

In the global settings for AnythingLLM : I chose OpenAI and gpt-4o-realtime-preview-....
Created a workspace in which I configured OpenAI and gpt-4o
When I was trying to chat in that workspace, no matter which model I choose, I got "Could not respond to message.
404 This is not a chat model and thus not supported in the v1/chat/completions endpoint. Did you mean to use v1/completions?"
Then I went back to the global settings for AnythingLLM and chose got-4o
Then chat worked in my workspace
=> it seems that the workspace config for model is not used and it's the global setting that gets used.

Normal ?

PS: other than that, AnythingLLM is awesome!

While realtime is available in the dropdown (we dont filter) support for it needs to still be built out since it works quite differently from the traditional API - that is why it is broken. Realtime is pretty different from the normal API/chunk response.
In the interim, swap to just another model that works in the traditional sense (basically any model that isn't realtime)


Add missing package name

The package name was missing it was installed as "UNKOWN" which clashes with other not named packages.
This PR Adds missing package name information

Thanks for the correction Kursat !


Request custom condor_status plugin to determine how many cores are usable by DE at the moment.

Is your feature request related to a problem? Please describe.
Both in HEPCloud and in DUNE we frequently see the frontend report "idle" cores which are in fact unusable by any
user jobs.  I will attach below a log from the  DUNE global pool which will show a case where we had 32000 idle
jobs all of which matched the group criteria, but no glideins at all were being requested because the frontend saw
idle cores and thought we had enough.  In fact every single one of those "idle" cores was on a glidein where either memory was exhausted or the glidein was retiring or both.  Typical DUNE jobs use 4-6GB of RAM
Describe the solution you'd like
I would like to see a feature added whereby I can add a custom condor_status constraint to show what glideins are
actually usable for my group.  in this case it would be all glideins with free memory greater than the smallest RequestMemory of the job I have in the queue, and have enough execution time to run the jobs with JOB_EXPECTED_MAX_LIFETIME.
Describe alternatives you've considered
The alternative would be to make the whole glide_frontend_element.py more generic and remove the 2GB per core assumption
everywhere it appears.
Info (please complete the following information):
Stakeholders and components can be a comma-separated list or on multiple lines.
If you add a new stakeholder or component, not on the sample list, add it on a line by its own.

Priority:  high
Stakeholders: Concerned stakeholder(s) DUNE, HEPCloud
Components: glidein, documentation, frontend,(and by extension Decision Engine resource_request channel which uses the same logic)

Additional context
Add any other context or supporting files about the feature request here.

@StevenCTimm Would you like a tool that would give you the numbers similar to the ones in the monitoring pages?

No.. what I am trying to go for here is to find the number of real usable slots.
so condor_status -pool  -constraint 'Memory>5GB' for instance.
This is the DUNE use case where 5  5.5GB jobs use up all the memory in a 16-core 32GB glidein
but glideinwms still thinks we have free cores and so it doesn't request more at that entry.
We have to beat this problem, it is resulting in most of our allocation at Fermilab going unused.
The memory level patch that was put in earlier last year helps, but there are still other 1-core 2 GB assumptions
built into the provisioning.


Build and deploy pihole

Have some issues with starting pihole in github action due to port 53.

Closed by #55


TrafficTarget.percent should be REQUIRED

This is to ensure workloads using traffic splits are portable across distributions

cc @knative/trademark-committee
cc @duglin who introduced the change to the spec while it was in serving

/LGTM

/lgtm

/assign @spencerdillard

/LGTM

/approve


Path case-sensitive

According to RFC 3986 the path component is case-sensitive. Do we want to use the camel-case notation from XML or rather mandate all lower case?
I tend to prefer all lower case as it looks more natural in a URL.

Why are we restricting URIs from RFC3986? Why not follow IRIs from RFC3987? we are trying to establish a global standard.
Upper and lower case are really only meaningful for some writing systems. There is no distinction in Cyrillic or Chinese for example. If I wanted to access colleagues' weather services at 中国气象网, why should they have to transliterate into a subset of 1960's ASCII?

I suggest we follow RFC 6570 (URI Templates) since templates are what we are actually defining.  I also like the approach taken by 6570
"Although the URI syntax is used for the result, the template string is allowed to contain the broader set of characters that can be found in Internationalized Resource Identifier (IRI)  references [RFC3987]. Therefore, a URI Template is also an IRI template, and the result of template processing can be transformed to an IRI by following the process defined in Section 3.2 of [RFC3987]."

Sorry -did not mean to close this issue - hit wrong button while rushing for a bus.
@cmheazel happy with your suggestion. We should be permissive rather than proscribing. Even though it is easier to type lower case on a Western Roman keyboard. It is the service providers perogative.
However there is the issue is what is allowed for search terms to the right of the '?' and how these are folded to a canonical form, but again, not really visible or meaningful to the user. As a user, I would be really annoyed if specifying "Data" failed because I should have said "data".

Sorry, I didn't mean to restrict anything. My question was only regarding the parts of the path we define in the spec, e.g., coverages or domainset. Btw. scheme and host are case-insensitive anyways.
Parts defined at runtime by a service like IDs are a different topic. Being based on XML in WCS these have to follow the NCName convention.

Any objection to using lower case in the spec defined path components? Please reopen if there is any.