Registries potential bug and package name collision

Hi, not sure if this is a bug or if I'm using registries incorrectly -- first time user!
Describe the bug
I believe the bug is because of a package I pull in as a registry package that has the same name of a package outside of my registry.
For example, my manifest file specifies "mosquitto", and "pthreads" which is my own version of the "pthreads" vcpkg package which I keep in a private GH enterprise instance. When mosquitto is installing its dependencies, it also lists "pthreads" (the standard one vcpkg has listed in its repository) as a dependency, it pulls in my private package from the registry instead of pulling in from vcpkg's list.
There are no issues with the installation if I don't specify my registry.
Environment

OS: Windows 10
Compiler: MSVC 19.28.29912.0

To Reproduce
Steps to reproduce the behavior:

Create vcpkg.json:

{
    "name": "test",
    "version": "1.0.0",
    "dependencies": [ "mosquitto", { "name": "pthreads", "platform": "windows" } ],
    "overrides": [
        { "name": "mosquitto", "version": "1.6.8", "port-version": 3 }
    ],
    "builtin-baseline": "030cfaa24de9ea1bbf0a4d9c615ce7312ba77af1"
}

Create vcpkg-configuration.json:

{
    "registries": [
        {
            "kind": "git",
            "repository": "https://<URL to private GitHub Enterprise instance>/vcpkg-registry",
            "packages": [ "pthreads" ]
        }
    ]
}

./vcpkg install --feature-flags="manifests,versions,registries"

Expected behavior
When vcpkg packages pull in dependencies, it pulls them in from vcpkg's list.
Failure logs
vcpkg install output:
The following packages will be built and installed:
    c-ares[core]:x86-windows -> 1.17.1 -- C:\Users\acalandra\test\vcpkg\buildtrees\versioning\versions\c-ares\a35b0a23f91ec79cecdcb83c82840f7305dbd709
    libuv[core]:x86-windows -> 1.39.0 -- C:\Users\acalandra\test\vcpkg\buildtrees\versioning\versions\libuv\18afc7f0e81eb4d9c8a9d8d1f4c15a96cb4f2db1
    libwebsockets[core]:x86-windows -> 4.1.6 -- C:\Users\acalandra\test\vcpkg\buildtrees\versioning\versions\libwebsockets\d980cd5098de3cfba2ecd8e63490cf1013545dfd
    mosquitto[core]:x86-windows -> 1.6.8#3 -- C:\Users\acalandra\test\vcpkg\buildtrees\versioning\versions\mosquitto\e50ddad9108597e09097e1853e116a62d650044d
    openssl[core]:x86-windows -> 1.1.1j -- C:\Users\acalandra\test\vcpkg\buildtrees\versioning\versions\openssl\009a7ee95741b939859c77b8e1ddd6c146ffe54e
    pthreads[core]:x86-windows -> 1.0.0 -- C:\Users\acalandra\AppData\Local\vcpkg\registries\git-trees\bb4c600c046c3717bc9fa888844247495eda8a2d
    zlib[core]:x86-windows -> 1.2.11#9 -- C:\Users\acalandra\test\vcpkg\buildtrees\versioning\versions\zlib\827111046e37c98153d9d82bb6fa4183b6d728e4
Could not locate cached archive: C:\Users\acalandra\AppData\Local\vcpkg\archives\df\df65ec229cd0271799a8de9aa8a1e946335c4be9.zip
Using cached binary package: C:\Users\acalandra\AppData\Local\vcpkg\archives\a7\a77c7fbbfbd0204c7b65d03e4066e122be8e69a5.zip
Using cached binary package: C:\Users\acalandra\AppData\Local\vcpkg\archives\6c\6c5020be3e9f566a95250c69a8d661e737c017c4.zip
Using cached binary package: C:\Users\acalandra\AppData\Local\vcpkg\archives\a4\a4a32af0bdf1db916321aed0add13d3d1dacddcb.zip
Could not locate cached archive: C:\Users\acalandra\AppData\Local\vcpkg\archives\9f\9f44457ae1a17fcc69c7133c516c6e33316a7b4d.zip
Using cached binary package: C:\Users\acalandra\AppData\Local\vcpkg\archives\46\46945da58423b348383ae036ff9b25565aed8a0d.zip
Could not locate cached archive: C:\Users\acalandra\AppData\Local\vcpkg\archives\7f\7fa470671d9ebc8bdb3ab5b69e249be4435e7e4c.zip
Starting package 1/7: pthreads:x86-windows
Building package pthreads[core]:x86-windows...
-- Installing port from location: C:\Users\acalandra\AppData\Local\vcpkg\registries\git-trees\bb4c600c046c3717bc9fa888844247495eda8a2d
-- Fetching https://<URL of private GitHub Enterprise server>/pthreads.git...
-- Extracting source C:/Users/acalandra/test/vcpkg/downloads/pthreads-2b27fe212d2ea17203bcf824c13c60b0753b2729.tar.gz
-- Using source at C:/Users/acalandra/test/vcpkg/buildtrees/pthreads/src/b0753b2729-917ff5b6ad.clean
-- Performing post-build validation
-- Performing post-build validation done
Stored binary cache: C:\Users\acalandra\AppData\Local\vcpkg\archives\df\df65ec229cd0271799a8de9aa8a1e946335c4be9.zip
Building package pthreads[core]:x86-windows... done
Installing package pthreads[core]:x86-windows...
Installing package pthreads[core]:x86-windows... done
Elapsed time for package pthreads:x86-windows: 5.342 s
Starting package 2/7: openssl:x86-windows
Building package openssl[core]:x86-windows...
Building package openssl[core]:x86-windows... done
Installing package openssl[core]:x86-windows...
Installing package openssl[core]:x86-windows... done
Elapsed time for package openssl:x86-windows: 225 ms
Starting package 3/7: zlib:x86-windows
Building package zlib[core]:x86-windows...
Building package zlib[core]:x86-windows... done
Installing package zlib[core]:x86-windows...
Installing package zlib[core]:x86-windows... done
Elapsed time for package zlib:x86-windows: 26.89 ms
Starting package 4/7: libuv:x86-windows
Building package libuv[core]:x86-windows...
Building package libuv[core]:x86-windows... done
Installing package libuv[core]:x86-windows...
Installing package libuv[core]:x86-windows... done
Elapsed time for package libuv:x86-windows: 47.07 ms
Starting package 5/7: libwebsockets:x86-windows
Building package libwebsockets[core]:x86-windows...
-- Installing port from location: C:\Users\acalandra\test\vcpkg\buildtrees\versioning\versions\libwebsockets\d980cd5098de3cfba2ecd8e63490cf1013545dfd
-- Downloading https://github.com/warmcat/libwebsockets/archive/736f0739ed8c75db0e29c7678b5a9194e957c347.tar.gz -> warmcat-libwebsockets-736f0739ed8c75db0e29c7678b5a9194e957c347.tar.gz...
-- Extracting source C:/Users/acalandra/test/vcpkg/downloads/warmcat-libwebsockets-736f0739ed8c75db0e29c7678b5a9194e957c347.tar.gz
-- Applying patch CMakeLists.patch
-- Applying patch fix-build-error.patch
-- Using source at C:/Users/acalandra/test/vcpkg/buildtrees/libwebsockets/src/94e957c347-2297ce2a93.clean
-- Found external ninja('1.10.2').
-- Configuring x86-windows
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:105 (message):
    Command failed: ninja -v
    Working Directory: C:/Users/acalandra/test/vcpkg/buildtrees/libwebsockets/x86-windows-rel/vcpkg-parallel-configure
    Error code: 1
    See logs for more information:
      C:\Users\acalandra\test\vcpkg\buildtrees\libwebsockets\config-x86-windows-out.log

Call Stack (most recent call first):
  scripts/cmake/vcpkg_configure_cmake.cmake:324 (vcpkg_execute_required_process)
  buildtrees/versioning/versions/libwebsockets/d980cd5098de3cfba2ecd8e63490cf1013545dfd/portfile.cmake:134 (vcpkg_configure_cmake)
  scripts/ports.cmake:142 (include)

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

Log from C:\Users\acalandra\test\vcpkg\buildtrees\libwebsockets\config-x86-windows-out.log:
[1/2] cmd /c "cd ../../x86-windows-dbg && "C:/Users/acalandra/test/vcpkg/downloads/tools/cmake-3.19.2-windows/cmake-3.19.2-win32-x86/bin/cmake.exe" "C:/Users/acalandra/test/vcpkg/buildtrees/libwebsockets/src/94e957c347-2297ce2a93.clean" "-DLWS_WITH_STATIC=0" "-DLWS_WITH_SHARED=1" "-DLWS_WITH_GENCRYPTO=ON" "-DLWS_WITH_TLS=ON" "-DLWS_WITH_BUNDLED_ZLIB=OFF" "-DLWS_WITHOUT_TESTAPPS=ON" "-DLWS_IPV6=ON" "-DLWS_WITH_HTTP2=ON" "-DLWS_WITH_HTTP_STREAM_COMPRESSION=ON" "-DLWS_WITH_LIBUV=ON" "-DCMAKE_MAKE_PROGRAM=C:/Program Files (x86)/Microsoft Visual Studio/2019/Professional/Common7/IDE/CommonExtensions/Microsoft/CMake/Ninja/ninja.exe" "-DBUILD_SHARED_LIBS=ON" "-DVCPKG_CHAINLOAD_TOOLCHAIN_FILE=C:/Users/acalandra/test/vcpkg/scripts/toolchains/windows.cmake" "-DVCPKG_TARGET_TRIPLET=x86-windows" "-DVCPKG_SET_CHARSET_FLAG=ON" "-DVCPKG_PLATFORM_TOOLSET=v142" "-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON" "-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON" "-DCMAKE_FIND_PACKAGE_NO_SYSTEM_PACKAGE_REGISTRY=ON" "-DCMAKE_INSTALL_SYSTEM_RUNTIME_LIBS_SKIP=TRUE" "-DCMAKE_VERBOSE_MAKEFILE=ON" "-DVCPKG_APPLOCAL_DEPS=OFF" "-DCMAKE_TOOLCHAIN_FILE=C:/Users/acalandra/test/vcpkg/scripts/buildsystems/vcpkg.cmake" "-DCMAKE_ERROR_ON_ABSOLUTE_INSTALL_DESTINATION=ON" "-DVCPKG_CXX_FLAGS=" "-DVCPKG_CXX_FLAGS_RELEASE=" "-DVCPKG_CXX_FLAGS_DEBUG=" "-DVCPKG_C_FLAGS=" "-DVCPKG_C_FLAGS_RELEASE=" "-DVCPKG_C_FLAGS_DEBUG=" "-DVCPKG_CRT_LINKAGE=dynamic" "-DVCPKG_LINKER_FLAGS=" "-DVCPKG_LINKER_FLAGS_RELEASE=" "-DVCPKG_LINKER_FLAGS_DEBUG=" "-DVCPKG_TARGET_ARCHITECTURE=x86" "-DCMAKE_INSTALL_LIBDIR:STRING=lib" "-DCMAKE_INSTALL_BINDIR:STRING=bin" "-D_VCPKG_ROOT_DIR=C:/Users/acalandra/test/vcpkg" "-D_VCPKG_INSTALLED_DIR=C:/Users/acalandra/test/vcpkg_installed" "-DVCPKG_MANIFEST_INSTALL=OFF" "-G" "Ninja" "-DCMAKE_BUILD_TYPE=Debug" "-DCMAKE_INSTALL_PREFIX=C:/Users/acalandra/test/vcpkg/packages/libwebsockets_x86-windows/debug""
FAILED: ../../x86-windows-dbg/CMakeCache.txt
cmd /c "cd ../../x86-windows-dbg && "C:/Users/acalandra/test/vcpkg/downloads/tools/cmake-3.19.2-windows/cmake-3.19.2-win32-x86/bin/cmake.exe" "C:/Users/acalandra/test/vcpkg/buildtrees/libwebsockets/src/94e957c347-2297ce2a93.clean" "-DLWS_WITH_STATIC=0" "-DLWS_WITH_SHARED=1" "-DLWS_WITH_GENCRYPTO=ON" "-DLWS_WITH_TLS=ON" "-DLWS_WITH_BUNDLED_ZLIB=OFF" "-DLWS_WITHOUT_TESTAPPS=ON" "-DLWS_IPV6=ON" "-DLWS_WITH_HTTP2=ON" "-DLWS_WITH_HTTP_STREAM_COMPRESSION=ON" "-DLWS_WITH_LIBUV=ON" "-DCMAKE_MAKE_PROGRAM=C:/Program Files (x86)/Microsoft Visual Studio/2019/Professional/Common7/IDE/CommonExtensions/Microsoft/CMake/Ninja/ninja.exe" "-DBUILD_SHARED_LIBS=ON" "-DVCPKG_CHAINLOAD_TOOLCHAIN_FILE=C:/Users/acalandra/test/vcpkg/scripts/toolchains/windows.cmake" "-DVCPKG_TARGET_TRIPLET=x86-windows" "-DVCPKG_SET_CHARSET_FLAG=ON" "-DVCPKG_PLATFORM_TOOLSET=v142" "-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON" "-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON" "-DCMAKE_FIND_PACKAGE_NO_SYSTEM_PACKAGE_REGISTRY=ON" "-DCMAKE_INSTALL_SYSTEM_RUNTIME_LIBS_SKIP=TRUE" "-DCMAKE_VERBOSE_MAKEFILE=ON" "-DVCPKG_APPLOCAL_DEPS=OFF" "-DCMAKE_TOOLCHAIN_FILE=C:/Users/acalandra/test/vcpkg/scripts/buildsystems/vcpkg.cmake" "-DCMAKE_ERROR_ON_ABSOLUTE_INSTALL_DESTINATION=ON" "-DVCPKG_CXX_FLAGS=" "-DVCPKG_CXX_FLAGS_RELEASE=" "-DVCPKG_CXX_FLAGS_DEBUG=" "-DVCPKG_C_FLAGS=" "-DVCPKG_C_FLAGS_RELEASE=" "-DVCPKG_C_FLAGS_DEBUG=" "-DVCPKG_CRT_LINKAGE=dynamic" "-DVCPKG_LINKER_FLAGS=" "-DVCPKG_LINKER_FLAGS_RELEASE=" "-DVCPKG_LINKER_FLAGS_DEBUG=" "-DVCPKG_TARGET_ARCHITECTURE=x86" "-DCMAKE_INSTALL_LIBDIR:STRING=lib" "-DCMAKE_INSTALL_BINDIR:STRING=bin" "-D_VCPKG_ROOT_DIR=C:/Users/acalandra/test/vcpkg" "-D_VCPKG_INSTALLED_DIR=C:/Users/acalandra/test/vcpkg_installed" "-DVCPKG_MANIFEST_INSTALL=OFF" "-G" "Ninja" "-DCMAKE_BUILD_TYPE=Debug" "-DCMAKE_INSTALL_PREFIX=C:/Users/acalandra/test/vcpkg/packages/libwebsockets_x86-windows/debug""
-- The C compiler identification is MSVC 19.28.29912.0
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: C:/Program Files (x86)/Microsoft Visual Studio/2019/Professional/VC/Tools/MSVC/14.28.29910/bin/Hostx64/x86/cl.exe - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Compiled with LWS_WITH_DIR and LWS_WITH_LEJP_CONF
SMD requires pthreads
-- Found Git: C:/Program Files/Git/cmd/git.exe (found version "2.28.0.windows.1")
Git commit hash: 2020.11-1-1039-gfe112d830
-- CMAKE_TOOLCHAIN_FILE='C:/Users/acalandra/test/vcpkg/scripts/buildsystems/vcpkg.cmake'
CMake Error at C:/Users/acalandra/test/vcpkg/scripts/buildsystems/vcpkg.cmake:861 (_find_package):
  By not providing "Findpthreads_windows.cmake" in CMAKE_MODULE_PATH this
  project has asked CMake to find a package configuration file provided by
  "pthreads_windows", but CMake did not find one.

  Could not find a package configuration file provided by "pthreads_windows"
  with any of the following names:

    pthreads_windowsConfig.cmake
    pthreads_windows-config.cmake

  Add the installation prefix of "pthreads_windows" to CMAKE_PREFIX_PATH or
  set "pthreads_windows_DIR" to a directory containing one of the above
  files.  If "pthreads_windows" provides a separate development package or
  SDK, be sure it has been installed.
Call Stack (most recent call first):
  CMakeLists.txt:426 (find_package)

-- Configuring incomplete, errors occurred!
See also "C:/Users/acalandra/test/vcpkg/buildtrees/libwebsockets/x86-windows-dbg/CMakeFiles/CMakeOutput.log".
[2/2] cmd /c "cd .. && "C:/Users/acalandra/test/vcpkg/downloads/tools/cmake-3.19.2-windows/cmake-3.19.2-win32-x86/bin/cmake.exe" "C:/Users/acalandra/test/vcpkg/buildtrees/libwebsockets/src/94e957c347-2297ce2a93.clean" "-DLWS_WITH_STATIC=0" "-DLWS_WITH_SHARED=1" "-DLWS_WITH_GENCRYPTO=ON" "-DLWS_WITH_TLS=ON" "-DLWS_WITH_BUNDLED_ZLIB=OFF" "-DLWS_WITHOUT_TESTAPPS=ON" "-DLWS_IPV6=ON" "-DLWS_WITH_HTTP2=ON" "-DLWS_WITH_HTTP_STREAM_COMPRESSION=ON" "-DLWS_WITH_LIBUV=ON" "-DCMAKE_MAKE_PROGRAM=C:/Program Files (x86)/Microsoft Visual Studio/2019/Professional/Common7/IDE/CommonExtensions/Microsoft/CMake/Ninja/ninja.exe" "-DBUILD_SHARED_LIBS=ON" "-DVCPKG_CHAINLOAD_TOOLCHAIN_FILE=C:/Users/acalandra/test/vcpkg/scripts/toolchains/windows.cmake" "-DVCPKG_TARGET_TRIPLET=x86-windows" "-DVCPKG_SET_CHARSET_FLAG=ON" "-DVCPKG_PLATFORM_TOOLSET=v142" "-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON" "-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON" "-DCMAKE_FIND_PACKAGE_NO_SYSTEM_PACKAGE_REGISTRY=ON" "-DCMAKE_INSTALL_SYSTEM_RUNTIME_LIBS_SKIP=TRUE" "-DCMAKE_VERBOSE_MAKEFILE=ON" "-DVCPKG_APPLOCAL_DEPS=OFF" "-DCMAKE_TOOLCHAIN_FILE=C:/Users/acalandra/test/vcpkg/scripts/buildsystems/vcpkg.cmake" "-DCMAKE_ERROR_ON_ABSOLUTE_INSTALL_DESTINATION=ON" "-DVCPKG_CXX_FLAGS=" "-DVCPKG_CXX_FLAGS_RELEASE=" "-DVCPKG_CXX_FLAGS_DEBUG=" "-DVCPKG_C_FLAGS=" "-DVCPKG_C_FLAGS_RELEASE=" "-DVCPKG_C_FLAGS_DEBUG=" "-DVCPKG_CRT_LINKAGE=dynamic" "-DVCPKG_LINKER_FLAGS=" "-DVCPKG_LINKER_FLAGS_RELEASE=" "-DVCPKG_LINKER_FLAGS_DEBUG=" "-DVCPKG_TARGET_ARCHITECTURE=x86" "-DCMAKE_INSTALL_LIBDIR:STRING=lib" "-DCMAKE_INSTALL_BINDIR:STRING=bin" "-D_VCPKG_ROOT_DIR=C:/Users/acalandra/test/vcpkg" "-D_VCPKG_INSTALLED_DIR=C:/Users/acalandra/test/vcpkg_installed" "-DVCPKG_MANIFEST_INSTALL=OFF" "-G" "Ninja" "-DCMAKE_BUILD_TYPE=Release" "-DCMAKE_INSTALL_PREFIX=C:/Users/acalandra/test/vcpkg/packages/libwebsockets_x86-windows""
FAILED: ../CMakeCache.txt
cmd /c "cd .. && "C:/Users/acalandra/test/vcpkg/downloads/tools/cmake-3.19.2-windows/cmake-3.19.2-win32-x86/bin/cmake.exe" "C:/Users/acalandra/test/vcpkg/buildtrees/libwebsockets/src/94e957c347-2297ce2a93.clean" "-DLWS_WITH_STATIC=0" "-DLWS_WITH_SHARED=1" "-DLWS_WITH_GENCRYPTO=ON" "-DLWS_WITH_TLS=ON" "-DLWS_WITH_BUNDLED_ZLIB=OFF" "-DLWS_WITHOUT_TESTAPPS=ON" "-DLWS_IPV6=ON" "-DLWS_WITH_HTTP2=ON" "-DLWS_WITH_HTTP_STREAM_COMPRESSION=ON" "-DLWS_WITH_LIBUV=ON" "-DCMAKE_MAKE_PROGRAM=C:/Program Files (x86)/Microsoft Visual Studio/2019/Professional/Common7/IDE/CommonExtensions/Microsoft/CMake/Ninja/ninja.exe" "-DBUILD_SHARED_LIBS=ON" "-DVCPKG_CHAINLOAD_TOOLCHAIN_FILE=C:/Users/acalandra/test/vcpkg/scripts/toolchains/windows.cmake" "-DVCPKG_TARGET_TRIPLET=x86-windows" "-DVCPKG_SET_CHARSET_FLAG=ON" "-DVCPKG_PLATFORM_TOOLSET=v142" "-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON" "-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON" "-DCMAKE_FIND_PACKAGE_NO_SYSTEM_PACKAGE_REGISTRY=ON" "-DCMAKE_INSTALL_SYSTEM_RUNTIME_LIBS_SKIP=TRUE" "-DCMAKE_VERBOSE_MAKEFILE=ON" "-DVCPKG_APPLOCAL_DEPS=OFF" "-DCMAKE_TOOLCHAIN_FILE=C:/Users/acalandra/test/vcpkg/scripts/buildsystems/vcpkg.cmake" "-DCMAKE_ERROR_ON_ABSOLUTE_INSTALL_DESTINATION=ON" "-DVCPKG_CXX_FLAGS=" "-DVCPKG_CXX_FLAGS_RELEASE=" "-DVCPKG_CXX_FLAGS_DEBUG=" "-DVCPKG_C_FLAGS=" "-DVCPKG_C_FLAGS_RELEASE=" "-DVCPKG_C_FLAGS_DEBUG=" "-DVCPKG_CRT_LINKAGE=dynamic" "-DVCPKG_LINKER_FLAGS=" "-DVCPKG_LINKER_FLAGS_RELEASE=" "-DVCPKG_LINKER_FLAGS_DEBUG=" "-DVCPKG_TARGET_ARCHITECTURE=x86" "-DCMAKE_INSTALL_LIBDIR:STRING=lib" "-DCMAKE_INSTALL_BINDIR:STRING=bin" "-D_VCPKG_ROOT_DIR=C:/Users/acalandra/test/vcpkg" "-D_VCPKG_INSTALLED_DIR=C:/Users/acalandra/test/vcpkg_installed" "-DVCPKG_MANIFEST_INSTALL=OFF" "-G" "Ninja" "-DCMAKE_BUILD_TYPE=Release" "-DCMAKE_INSTALL_PREFIX=C:/Users/acalandra/test/vcpkg/packages/libwebsockets_x86-windows""
-- The C compiler identification is MSVC 19.28.29912.0
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: C:/Program Files (x86)/Microsoft Visual Studio/2019/Professional/VC/Tools/MSVC/14.28.29910/bin/Hostx64/x86/cl.exe - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Compiled with LWS_WITH_DIR and LWS_WITH_LEJP_CONF
SMD requires pthreads
-- Found Git: C:/Program Files/Git/cmd/git.exe (found version "2.28.0.windows.1")
Git commit hash: 2020.11-1-1039-gfe112d830
-- CMAKE_TOOLCHAIN_FILE='C:/Users/acalandra/test/vcpkg/scripts/buildsystems/vcpkg.cmake'
CMake Error at C:/Users/acalandra/test/vcpkg/scripts/buildsystems/vcpkg.cmake:861 (_find_package):
  By not providing "Findpthreads_windows.cmake" in CMAKE_MODULE_PATH this
  project has asked CMake to find a package configuration file provided by
  "pthreads_windows", but CMake did not find one.

  Could not find a package configuration file provided by "pthreads_windows"
  with any of the following names:

    pthreads_windowsConfig.cmake
    pthreads_windows-config.cmake

  Add the installation prefix of "pthreads_windows" to CMAKE_PREFIX_PATH or
  set "pthreads_windows_DIR" to a directory containing one of the above
  files.  If "pthreads_windows" provides a separate development package or
  SDK, be sure it has been installed.
Call Stack (most recent call first):
  CMakeLists.txt:426 (find_package)

-- Configuring incomplete, errors occurred!
See also "C:/Users/acalandra/test/vcpkg/buildtrees/libwebsockets/x86-windows-rel/CMakeFiles/CMakeOutput.log".
ninja: build stopped: subcommand failed.

@AnthonyCalandra, thanks for reporting this issue!
It's not related to registries features, it could be repro when executing './vcpkg install libwebsockets:x86-windows' locally.

Seems like a port bug on latest changes. I will investigate this issue and try to fix this soon.


NullLogger moved location

https://github.com/aspnet/Testing/pull/69
@NTaylorMullen

:shipit: once testing changes are in.


Write a Rust program to check prime number

Description
Write a Rust program to check prime number
A prime number is a natural number greater than 1 that has no positive divisors other than 1 and itself.
Input  : 5
Output : Prime Number

How to contribute

Save the solution in check_prime_number.rs file
Add check_prime_number.rs file in check-prime-number folder

!assign


Simple commands (such as autocompletion and --version) take a relatively long time

Evaluating the autocomplete takes a very long time (closer to a second).
eval "$(env _PIPENV_COMPLETE=source-bash pipenv)"
Autocompletions also take closer to a second, as does running pretty much any command (no matter how simple).
I had to disable the autocompletion as it adds too much time to my terminals startup (actually I just took the output of the command to my .bashrc for now).
Describe you environment

Linux (Ubuntu 17.04)
Python version: Python 3.5.3
Pipenv version: pipenv, version 8.2.7

Expected result
These simple commands shouldn't take more than a few milliseconds.
Steps to replicate
$ time env _PIPENV_COMPLETE=source-bash pipenv --verbose

_pipenv_completion() {
    local IFS=$'\t'
    COMPREPLY=( $( env COMP_WORDS="${COMP_WORDS[*]}" \
                   COMP_CWORD=$COMP_CWORD \
                   _PIPENV_COMPLETE=complete-bash $1 ) )
    return 0
}

complete -F _pipenv_completion -o default pipenv

real    0m0,763s
user    0m0,708s
sys     0m0,056s

$ time pipenv --version
pipenv, version 8.2.7

real    0m0,646s
user    0m0,600s
sys     0m0,040s

I don't know much about completion but this seems slow. /cc  @erinxocon @nateprewitt

@techalchemy it is slower than it needs to be. I fixed this a few months back and it looks like the big wave of changes in the last month reintroduced it.
It's just that the cli method has become so overloaded it does a lot of checks with every call that aren't necessary in cases like this.
We can fix it again but at best I think we'll be around 400ms just because of click and imports.

@nateprewitt Is there some way we can pare down imports or pre-compile autocompletion or something like that? Maybe that's just a massive refactor though?

@nateprewitt @techalchemy I think the cli might need a bit of a refactor, or at least the options each command can accept needs to be looked at.
@PolarPayne Can I ask what kind of hardware you are running on?

I'm running on a new Lenovo X1 Carbon, it has an SSD and is pretty fast (it's not a potato).

@PolarPayne Just curious.  I'll try and spin up a VM on my computer later with ubuntu and see if I experience any slowdowns.

On a bare metal ubuntu machine running an i7 770k, I'm getting a little under half a second.  A bit long...

I tried changing __main__.py to:
if __name__ == '__main__':
    import os

    pipenv_complete = os.environ.get("_PIPENV_COMPLETE")
    if pipenv_complete:
        import click_completion
        click_completion._shellcomplete(None, "pipenv")
    else:
        from .cli import cli
        cli()

But this only lowered the time by ~100ms.
The problem seems to be that in __init__.py on line 17, cli is getting imported and it's taking long. If that import is just moved inside the if __name__ == '__main__': block in there everything works much faster (when you also have the change above).
If these are fine changes, I can make them into a pull request later today.

I'll gladly also just refactor that autocomplete code to be lightning fast.

I don;t know as much about the autocomplete.  @nateprewitt or @kennethreitz?

Anyways, the main problem is that from .cli import cli takes long (around 500ms on my machine).

I'll put my changes (with a few other ideas related to this) into a pull request as soon as I have some time (next week?).

I think I'm experiencing the same issue.  If there's a clear opportunity to jump in to help, I'd be interested.
Having auto-completion on in my .bashrc makes launching a new shell lag quite a bit.
$ time eval "$(pipenv --completion)"

real	0m1.371s
user	0m1.224s
sys	0m0.134s

For comparison with the above results, here are my results with completion off:
$ time pipenv --version
pipenv, version 8.3.2

real	0m0.619s
user	0m0.535s
sys	0m0.075s

And with completion on:
$ time pipenv --version
pipenv, version 8.3.2

real	0m0.673s
user	0m0.573s
sys	0m0.089s

Versions:
$ python --version
Python 3.6.3

$ pipenv --version
pipenv, version 8.3.2

My hardware is a 2016 15" MBP with 16 GB of RAM running macOS 10.13.1.

I just realized, after creating the pull request, that first of all it doesn't seem to work (I guess it messes up something).
But that there is now the --completion, and it doesn't account for that.
If someone can give me a nudge in the right direction of what might be the correct way to fix this one so I could look into implementing it.

known

Hi! I'm a newcomer. I'm using pipenv shell and/or pipes as replacement of virtualenvwrapper's workon.
I'm facing some lags in my terminal:
a) pipenv autocompletion feels slow
b) exit from shell sometimes take ~2[s] to return to the prompt (or hangs until a keystroke)
Is this related to the second BASH instance or maybe pipes adds some overhead?
Thanks for your time.
OS: ArchLinux; Python 3.6.5; pipenv, version 2018.05.18
Hardware: i5-6300U CPU @ 2.40GHz; 16GB RAM; NVMe SSD

What is pipes?

@tedmiston https://github.com/gtalarico/pipenv-pipes/

For sure the autocomplete is an issue, it's a constant battle. There are some suggestions in https://github.com/pypa/pipenv/issues/497 regarding that.  We are reworking our subshell implementation (in the next release) so that should bring some performance improvements as well.

@dimaqq it is already quite a challenge to stay at this time, but it is something I check regularly. As for alternate approaches, I’m not personally that focused on this beyond what I already do so if someone else has ideas they want to propose and implement I’d be happy do review then

@techalchemy yes I can imagine!
I wish there was a better protocol for shell autocomplete, akin to switch from cgi to fastcgi.
I suppose none stops a dedicated developer from spawning a long-lived background task from at first autocomplete and communicating with said task from then on. Though that sounds like a slippery slope -- what's to stop other tools from doing same, and then if someone has N shells and M tools, would they end up with N*M background processes that do nothing most of the time?
The good news is that this "lag" is cpu-bound, which means it will get twice shorter in 1.5 years or so :D
Or perhaps someone writes an autocomplete-caching-proxy in let's say golang and solves this for us :)

I think this a problem beyond just the autocompletion, the thing is that all commands have this around half a second startup time which is not really acceptable for a CLI tool like pipenv.
I'd love to contribute and help with this, but I'm guessing it's most likely a rather large change.

@PolarPayne I am in 100% agreement and it likely requires some substantial restructuring which I’m happy to review but the smaller the changes the better of course

What is pipes?

@tedmiston  that's one 10-20 repos necessary for pipenv to supposedly do its thing.


Update MHLO .td file to link to StableHLO spec

We should probably directly copy/paste descriptions of already specced StableHLO ops from StableHLO's .td to MHLO's td.

Update: Remain unassigned with low priority in favor of complete Spec work.
Open question: we may address all of these in bulk, or update the corresponding doc when implementing the interpreter op by op.

I think addressing in bulk would be easier because otherwise this becomes a recurring action items that authors and reviewers need to not forget. I definitely felt that when had to update StablehloOps.td in every spec PR in Q4.

Implemented in https://github.com/tensorflow/mlir-hlo/commit/d4f40974fe47f0ce7b5b03ac4ee1d6b1bc77d3ba.


Loading visualization takes too long

Loading the visualization on github.io takes several minutes. This needs to be improved.

More detailed in  #13


Custom table view function: return scalar value?

Hello @CurtHagenlocher and Team,
When using a Table.View OnInvoke handler to handle a custom table view function, is it okay to have the handler directly return a scalar value--or is it expected to follow the typical On* handler pattern, where a new view is returned which later may have its GetRows() handler used for tabular data retrieval?
For example, is something like the below okay?
let
  MyDataSource =
    Table.View(
      null,
      [
	GetType = () => Value.Type(GetRows()),
	GetRows = () =>  #table({"ID", "Name"}, {{ 1, "Joe" }, { 2, "Paul" }}),
	OnInvoke = (func, arguments, index) =>
	  if func = ComputeSpecialValue
	  then 12345 // in real life, make call to external system to fetch correct value
	  else ...
      ]
  ),
  ComputeSpecialValue = Table.ViewFunction(
    (input as table) => ... /* in real life, provide an appropriate non-folding implementation here */
  )
in
  ComputeSpecialValue(MyDataSource)

Thanks,
Ben

The value being returned should be appropriate to the function being invoked. If, for instance, the function was the equivalent of Table.RowCount you would expect it to return a number rather than a table.

Thank you, @CurtHagenlocher!


Add head_vcf.py script

@DailyDreaming I'm going to merge this based on manual testing, but see this issue

@xbrianh Sounds good!


Issue: Desync detected

Product and Version [VS/VSCode]:
VSCode
OS Version [macOS/Windows/Linux]:
macOs
Live Share Extension Version:
Target Platform or Language [e.g. Node.js]:
Node Js, typescript
What were you doing when you encountered the desync?
The code was desync, which caused troubles with the teams and on how to product works
How often have you encountered desyncs?
Just once

Duplicated issue


Check cluster controller for config convergence

All clustercontroller instances are now selected by content node index, so we can now check config convergence for them again

@bratseth please take a look

ping @bratseth


Refactor action for easier updating

Pull requests:

https://github.com/Senzing/github-action-install-senzing-api/pull/40
https://github.com/Senzing/github-action-install-senzing-api/pull/41
https://github.com/Senzing/github-action-install-senzing-api/pull/42
https://github.com/Senzing/github-action-install-senzing-api/pull/43


Demo playground not syncing correctly

The demo-playground nodes are currently producing a single block repeatedly - that is, blocks seem to not being incorporated onto the chain.
This is visible even with a single node - blocks are produced, but each has no awareness of the previous block.

For me it only happens with --real-pbft, it works fine with all other protocols.

Aha, Ouroboros.Consensus.Protocol.PBFT.applyChainState is returningPBftInvalidSignature "Verification failed" for each block. Dives deeper

This also highlighted the issue that the logging here was reporting that we were creating the block, but it was doing it before that block had been actually incorporated into the chain so it was a false success message.
The ChainDB.addBlock does not report any result. Perhaps it should return the tip point once the block was added (and any resulting chain selection is complete). That way the tracing could report if adding the block was successful or not (and it not being successful would be a severe internal error that we should act on).

This also highlighted the issue that the logging here was reporting that we were creating the block, but it was doing it before that block had been actually incorporated into the chain so it was a false success message.

Creating a block and adopting it are two separate things, so I don't see it as a false success message.

The ChainDB.addBlock does not report any result. Perhaps it should return the tip point once the block was added (and any resulting chain selection is complete). That way the tracing could report if adding the block was successful or not (and it not being successful would be a severe internal error that we should act on).

This is indeed what should happen and  does happen in the real (as opposed to the mock) implementation of ChainDB.addBlock. I use the following type for that:
-- | Trace type for the various events that occur when adding a block.
data TraceAddBlockEvent blk
  = AddedBlockToVolDB    (Point blk)
    -- ^ A block was added to the Volatile DB
  | TryAddToCurrentChain (Point blk)
    -- ^ The block fits onto the current chain, we'll try to use it to extend
    -- our chain.
  | TrySwitchToAFork     (Point blk) (NonEmpty (HeaderHash blk))
    -- ^ The block fits onto some fork, we'll try to switch to that fork (if
    -- it is preferable to our chain).
  | StoreButDontChange   (Point blk)
    -- ^ The block doesn't fit onto any other block, so we store it and ignore
    -- it.
  | SwitchedToChain
    { _prevChain :: AnchoredFragment (Header blk)
    , _newChain  :: AnchoredFragment (Header blk)
    }
    -- ^ We successfully installed a new chain.
  | ChainChangedInBg
    { _prevChain :: AnchoredFragment (Header blk)
    , _newChain  :: AnchoredFragment (Header blk)
    }
    -- ^ We have found a new chain, but the current chain has changed in the
    -- background such that our new chain is no longer preferable to the
    -- current chain.
  | AddBlockValidation (TraceValidationEvent blk)
    -- ^ An event traced during validating performed while adding a block.

data TraceValidationEvent blk
  = InvalidBlock
    { _validationErr :: ExtValidationError blk
    , _invalidPoint  :: Point blk
    }
    -- ^ A point was found to be invalid.
  | InvalidCandidate
    { _candidate     :: AnchoredFragment (Header blk)
    , _reasonInvalid :: ReasonInvalid
    }
    -- ^ A candidate chain was invalid.
  | ValidCandidate (AnchoredFragment (Header blk))
    -- ^ A candidate chain was valid.

Creating a block and adopting it are two separate things, so I don't see it as a false success message.

Working notes: looks like the SignTag isn't the same between the two cases, probably due to the genesis key being wrong. Diving deeper...


Dark helmet nightvision doesn't work properly in creative flying

Using:
EnderCore-1.7.10-<IP_ADDRESS>_beta
EnderIO-1.7.10-<IP_ADDRESS>5_beta
Whenever player enter "creative flying" (double tap jump to enter flying in creative mode), dark helmet nightvision  stops working properly. Screen starts flashing as if nightvision potion was running out. Timer starts running out and as soon timer runs out, screen will rapidly flash between nightvision on and off. Also, during creative flying, player is "unable" to turn it on. It will make the noise, but won't turn on. As soon as player exit creative flying, it will kick in. Otherwise, it works normally during walking, standing or falling.
For comparison: this doesn't happen in older version of Ender IO (EnderIO-1.7.10-<IP_ADDRESS>1). There it works even if player is flying in creative.

Tested the newest version and the issue is gone.
So, I guess this issue can be closed now.


Add support for internal version checks in HTEX

Is your feature request related to a problem? Please describe.
As Globus compute moves to using Parsl's HTEX managers often run different python and parsl versions than the interchange. Currently, this raises a VersionMismatch exception since HTEX requires a version match to avoid the several different errors that could creep in from version mismatch. In the GC context, this is less of a concern and an option to disable this check is preferrable.
Describe the solution you'd like
A kwarg option for the HighThroughputExecutor(disable_internal_version_checks: bool = False) which defaults to the current behavior.

I think disabling that check, rather than putting some effort into protocol work, is an approach that will come back to haunt you :ghost:
"disable/enable" features look nicer (to me) with fewer negatives, and phrased about whether the check should be made or not, rather than phrased as a change against soon-forgotten built-in behaviour: eg. instead of "disable_internal_version_checks: bool = False", have "check_version_mismatches: bool = True".

I was going to recommend Messagepack. I agree that doing this properly now is the right way to go.

I don't think it brings in any additional requirements, but it's also interesting maybe to think about this happening inside Parsl: any of the places where we're interested in multiple environments existing - which is cloud stuff, not so interesting any more, but also WQ and radical which have the ability to build their own environments, and places where people are using containers.  I think that is broadly the same situation as with Globus Compute and doesn't change anything here, but I'm noting it on this issue anyway.


support option to tell people to head to github

Add a --support option that prints a message indicating folks should open issues on our repository. Fixes #95

after a code tour from dave
:+1:


When copying an alert record dont copy id of the record.

Presence of id in @alert was causing UI to think that existing record is being edited instead a new copied record being added. Due to this incorrect cell title and form buttons were displayed on screen.
https://bugzilla.redhat.com/show_bug.cgi?id=1312961
before:

after:

@dclarizio @martinpovolny please review

Hmm, #clone should not copy id -- see http://apidock.com/rails/ActiveRecord/Base/clone

@martinpovolny i tried that in console see output below:
``
2.2.3 :001 > a = MiqAlert.first
MiqAlert Load (0.3ms)  SELECT  "miq_alerts".* FROM "miq_alerts" ORDER BY "miq_alerts"."id" ASC LIMIT $1  [["LIMIT", 1]]
MiqAlert Inst Including Associations (6.9ms - 1rows)
=> #<MiqAlert id:<PHONE_NUMBER>001, guid: "9bc0d572-40bd-11de-bd12-005056a170fa", description: "Host Datastore < 5% of Free Space", created_on: "2014-01-30 15:52:29", updated_on: "2014-10-23 09:42:26", options: {:notifications=>{:email=>{:from=>"", :to=>[]}}}, db: "Host", expression: #<MiqExpression:0x000000092e6388 @exp={"FIND"=>{"search"=>{"IS NOT NULL"=>{"field"=>"Host.storages-name"}}, "checkany"=>{">"=>{"field"=>"Host.storages-v_used_space_percent_of_total", "value"=>95}}}}>, responds_to_events: nil, enabled: nil>
2.2.3 :002 > b = a.clone
=> #<MiqAlert id:<PHONE_NUMBER>001, guid: "9bc0d572-40bd-11de-bd12-005056a170fa", description: "Host Datastore < 5% of Free Space", created_on: "2014-01-30 15:52:29", updated_on: "2014-10-23 09:42:26", options: {:notifications=>{:email=>{:from=>"", :to=>[]}}}, db: "Host", expression: #<MiqExpression:0x000000092e6388 @exp={"FIND"=>{"search"=>{"IS NOT NULL"=>{"field"=>"Host.storages-name"}}, "checkany"=>{">"=>{"field"=>"Host.storages-v_used_space_percent_of_total", "value"=>95}}}}>, responds_to_events: nil, enabled: nil>
``

Sorry, sent you to the wrong method. Here is the correct one: http://apidock.com/rails/ActiveRecord/Core/dup

@martinpovolny addressed your comment, please re-review

@h-kataria : cool, can be merged, once travis gets green


Implement persistent awaitable constraint.

Add a new constraint that allows saving time stamps to an external destination. E.g. to allow using RateLimiter after application relaunch with previously created timestamps.

Hello @FireNero , I understand the need and like the proposal.
I will review the code later on.
Meanwhile, the test you provided is failing, could take a look and correct it?

@David-Desmaisons sure, actually I've run tests locally before creating a PR and everything was fine. But I will double check it asap.

Hey, @David-Desmaisons. Can you give me an estimation about reviewing this PR, please? I need this changes in my work and prefer to get it from NuGet instead of managing dll.

It should be ready (inclusing nuget) by the end of this week.

@FireNero , new version published: same API you designed, small tweaks in the implementation


Fetching full data for TG

Note that TG provides this data as CSV here: https://opendata.swiss/de/dataset/covid_19-fallzahlen-kanton-thurgau
The only reason this is not yet implemented is, that TG keeps the CSV in this repo updated themselves, so there was not really a need for a proper scraper.

closing in favor of #859


Support other Idris 2 code generators

Support more Idris 2 code generators. For starters:

JVM: https://github.com/mmhelloworld/idris-jvm
Python: https://github.com/madman-bob/idris2-python

Split into #13 and #14.


DataStore Temporal cannot persist precision of micro seconds and nano seconds

Describe the bug
Using schema
type Blog @model {
  name: String!
  awsDateTime: AWSDateTime
}

Run below sample code
let models = [
    try Blog(name: "1", awsDateTime: Temporal.DateTime.init(iso8601String: "2020-01-01T19:30:45.000000000Z")),
    try Blog(name: "2", awsDateTime: Temporal.DateTime.init(iso8601String: "2020-01-01T19:30:45.100000000Z")),
    try Blog(name: "3", awsDateTime: Temporal.DateTime.init(iso8601String: "2020-01-01T19:30:45.100250000Z")),
    try Blog(name: "4", awsDateTime: Temporal.DateTime.init(iso8601String: "2020-01-01T19:30:45.1000Z")),
    try Blog(name: "5", awsDateTime: Temporal.DateTime.init(iso8601String: "2020-01-01T19:30:45.111Z")),
    try Blog(name: "6", awsDateTime: Temporal.DateTime.init(iso8601String: "2020-01-01T19:30:45.111+00:00")),
    try Blog(name: "7", awsDateTime: Temporal.DateTime.init(iso8601String: "2020-01-01T19:30:45.111+01:00")),
    try Blog(name: "7", awsDateTime: Temporal.DateTime.init(iso8601String: "2020-01-01T19:30:45.111222333Z")),
]

for model in models {
    Amplify.DataStore.save(model) { result in
        switch(result) {
        case .success(let savedItem):
            print("Saved item: \(savedItem.name)")
        case .failure(let error):
            print("Could not save item to DataStore: \(error)")
        }
    }
}

The awsDateTime values stored in local SQLite DB drops the micro seconds and nano seconds specified in the input.

The fractional seconds dropping seems to be done by this format string:
https://github.com/aws-amplify/amplify-ios/blob/2c57ccce43d60789183f3737e44226a453eae969/Amplify/Categories/DataStore/Model/Temporal/TemporalFormat%2BDateTime.swift#L21
Steps To Reproduce
Steps to reproduce the behavior:
1. Run the sample code
2. Observe the records inserted in SQLite DB

Expected behavior
When records are inserted into SQLite, the DateTime column should persist micro seconds and nano seconds following user input.
Amplify Framework Version
1.18.1
Amplify Categories
DataStore
Dependency manager
Swift PM
Swift version
5
CLI version
7.6.5
Xcode version
13.2.1
Relevant log output
No response
Is this a regression?
No
Regression additional context
No response
Device
iPhone 13 simulators
iOS Version
15.2
Specific to simulators
No response
Additional context
No response

Thanks for opening this issue @HuiSF.
This is an OS limitation that we unfortunately can't work around. Temporal.Date and Temporal.DateTime are backed by Foundation.Date, which only supports down to millisecond granularity.
For example:
let dateString = "2020-01-01T19:30:45.111222333Z"
let formatter = DateFormatter()
formatter.dateFormat = "yyyy-MM-dd'T'HH:mm:ss.SSSSSSSSZZZZZ"

let date = formatter.date(from: dateString)
date // "Jan 1, 2020 at 2:30 PM"
date?.debugDescription // "2020-01-01 19:30:45 +0000"

let backToString = date.map(formatter.string(from:))
backToString // "2020-01-01T14:30:45.11100000-05:00"

This means we lose micro and nanosecond precision once the iso string gets converted to a Foundation.Date, which happens in the Temporal.DateTime implementation.

Thanks for the explanation @atierian .
This causes platform discrepancy though between AppSync, and amplify-android.
Use case 1:
A customer wants to use data from AppSync produced by other Apps, AppSync is capable to persist micro and nanosecond. In this case, amplify-ios may mutate existing data unexpectedly.
Use case 2:
A customer wants to create an Android App and an iOS App which can communicate each other real time via DataStore, if two devices modify the same model, the way ampliy-ios handling DateTime may cause data inconsistency between the two platforms.
Considering above use cases, is that possible to extract micro and nanosecond from the original input initiating Temporal.DateTime, and merge the info back after getting the ISO8601 string before writing the value into local DB?

Thanks for the explanation of use cases, that's helpful. This is something that should have platform parity.
I'll take this on as a feature request; considering this is an expected limitation on iOS, I don't believe it should be classified a bug, unless there's a standard or API contract we're violating.
I'll dig into this and update here.

Due to the system constraints mentioned above - Temporal.DateTime is backed byFoundation.Date, which doesn't support micro- or nanoseconds - we'll have to revisit this feature request at a later time. The Swift Clock, Instant, and Duration Proposal that is currently under review may open up the possibility for us to support micro- and nanoseconds. We'll revisit this feature request when/if these changes make it possible to do so.


F5_Recommended_Tunneling_delete_objects - flagged in every ucs

There was a change in version 3.3.1. It looks like the Journeys tool is not discerning whether the config is using a tunnel, only that the default (unused?) http-tunnel and socks-tunnel config snippets exist. These config snippets exist on every BIG-IP by default.
net tunnels tunnel /Common/http-tunnel {
description "Tunnel for http-explicit profile"
profile /Common/tcp-forward
}net tunnels tunnel /Common/socks-tunnel {
description "Tunnel for socks profile"
profile /Common/tcp-forward
}

Everyone running Journeys will see the alert related to the socks-tunnel and http-tunnel. Maybe this is deliberate, maybe it’s not, so just be aware.
Additionally, it's not obvious how you would follow the recommendation to delete these tunnels or corresponding default profiles easily from the Configuration Utility (Web UI).

Hello @tmarfil , thank you for reaching out.
We will double check the possible improvements.

Filed internal Jira SOLUTIONS-6312.

Fixed in 3.3.3


Upload (and possibly resize) image as its own thumbnail

Feature request
When uploading an image it would be nice to allow the same image to be used as the thumbnail for the image.  If the image is over x size (>5 mb? >500 pixels wide or tall) then the client should automatically resize the image and upload it to spee.ch as the thumbnail.

The compression would be handled by https://github.com/lbryio/spee.ch/issues/599
For this to work inside the app, we'd need to give users who are uploading images an option to use the same image as a thumbnail. This would then call the spee.ch upload functionality, but at least they wouldn't have to re-select the file again. I don't think this should happen automatically...what if they want to use a different thumb, or if the image being uploaded doesn't "work" as a thumb because of aspect ratio, etc.

There was also discussion in the forum that many (most?) images wouldn't be good to use as the thumbnail since they would be too large (would slow down the pages), so the client should resize the image dynamically (maybe even offer cropping, etc. to make it more reasonable).
So, the feature might be broken into versions:

Upload as thumbnail, no resizing
Auto resize and upload, no editing
Auto resize and allow cropping/subset selection


SOCKS proxy settings are not respected

Describe the bug
Nosey Parker doesn't observe proxy settings as expected.
To Reproduce

Set a SOCKS proxy like export ALL_PROXY=socks5h://<proxy_host>:<proxy_port>
Scan a GitHub organization, e.g., noseyparker scan --github-org praetorian-inc

Expected behavior
Nosey Parker enumerates the repositories in the praetorian-inc organization on GitHub, clones them all, and scans them successfully.
Actual behavior
Nosey Parker fails to successfully clone the enumerated repositories, even though regular command-line git succeeds.
Output of noseyparker --version
noseyparker 0.21.0-dev

Build Configuration:

    Build Timestamp:    2024-11-06T15:27:31.263704000Z

    Commit Timestamp:   2024-11-05T16:32:04.000000000-05:00
    Commit Branch:      main
    Commit SHA:         d006eb0d2288e71b8a4121d70f5bf3a1fc0d6195

    Cargo Features:     color_backtrace,default,disable_trace,github,log,mimalloc,release
    Debug:              true
    Optimization:       3
    Target Triple:      aarch64-apple-darwin

Build System:

    OS:                 Darwin
    OS Version:         MacOS 14.7

    CPU Vendor:         Apple
    CPU Brand:          Apple M3 Max
    CPU Cores:          14

    rustc Version:      1.82.0
    rustc Channel:      stable
    rustc Host Triple:  aarch64-apple-darwin
    rustc Commit Date:  2024-10-15
    rustc Commit SHA:   f6e511eec7342f59a25f7c0534f1dbea00d01b14
    rustc LLVM Version: 19.1

Additional context
I'm reporting this issue second-hand, and have not actually reproduced it myself yet.
An open question: Are SOCKS proxy settings observed as expected for Nosey Parker's github enumeration phase? Or are things broken there too?

Two kinds of network traffic occur when using Nosey Parker's --git-organization=ORG option:

HTTPS traffic against GitHub's REST API to list the repositories to clone and scan
HTTPS traffic from command-line git to actually clone the repositories.

Nosey Parker shells out to git to actually clone repositories. Nosey Parker goes out of its way to explicitly use a very vanilla git configuration for this process. In particular, proxy-relevant Git configuration environment variables (all_proxy, http_proxy, and https_proxy) are not propagated to the git process. This is very likely related to this bug.
See git's documentation for a bit more information on proxy-relevant settings.
(Why does Nosey Parker use command-line git instead of a library? When I last tried a couple years ago, neither libgit2 nor gix could reliably do bare or mirror clones with behavior matching CLI git.)

Maybe relevant — a list of the various ways to configure proxies: https://gist.github.com/yougg/5d2b3353fc5e197a0917aae0b3287d64


Fixes #2969 Tabbing to "Search PyPI" text box does not give it focus

Fixes #2969 Tabbing to "Search PyPI" text box does not give it focus
Changes style back into an actual text box to avoid multiple nested text boxes.

👍


Tests for Existing Endpoints

Issue: There might be insufficient unit tests for the current server endpoints, such as creating rooms, joining rooms, and sending messages.

elaborate please


https://www.google.com/maps/ -> https://www.google.com/maps/?authuser=1

[x] I believe this to be a bug, not a question about using URL Auto Redirector.
[ ] This is a feature request.

My OS

[x] I am on (or have tested on) macOS 10+
[ ] I am on (or have tested on) Ubuntu GNU/Linux
[ ] I am on (or have tested on) Other GNU/Linux
[ ] I am on (or have tested on) Windows 10+

My Chrome Version

[ ] I cannot install URL Auto Redirector.
[x] The rules do not work.

My Reproduction Steps

Step 1:  Source ^https://www.google.com/maps/(.*)$ Dest https://www.google.com/maps/$1?authuser=1
Step 2 visit https://www.google.com/maps/ or https://maps.google.com/
Step 3 it doesn't add suffix ?authuser=1 to the url.

@kaovilai I think Google Maps actually changed URL after loading by adding a pair of coordinates. Does it happen to you?

@kaovilai I think Google Maps actually changed URL after loading by adding a pair of coordinates. Does it happen to you?

Sure and? The regex still valid right?

@kaovilai I think Google Maps actually changed URL after loading by adding a pair of coordinates. Does it happen to you?

Sure and? The regex still valid right?

I think so.


MDV & Emailing service

Will add the daily verse to the email once MDH is migrated to AWS

@mohdels the first two tasks were not pushed or done i think, the underlined verse is still small compared to the title.
could we move the circled colored section to the left?

just unticked them


Unnecessary "confirm query execution" dialog in some queries

Description
The following query triggers a "Confirm query execution" dialog, which is unnecessary since it's a read-only query (simplified):
select bool_or(true = true); -- triggers confirmation dialog

The following related queries work fine, i.e. they do not trigger the confirmation dialog:
select true = true; -- ok
select bool_or(true); -- ok

DBeaver Version
Community Edition 23.0.1
Operating System
Windows 11
Database and driver
PostgreSQL 14.5
Driver Version 42.5.0
Steps to reproduce
No response
Additional context
No response

Hello @ewoerner,
DBeaver doesn't know whether a particular query might or not have side effects. Therefore, it always assumes there can be one.
I think the current behavior should be kept.

@ShadelessFox that is not correct, DBeaver seems to have some logic (SQLSemanticProcessor.isSelectQuery) that decides whether a query might have side effects. See the two related queries in my original comment which do not trigger the confirm query execution dialog.

Perhaps the existing semantics of the SQLSemanticProcessor#isSelectQuery function are invalid, actually.
In your example, the bool_or functions can have side effects, but DBeaver doesn't complain about it for some reason.
There's room for improvement. I'm sorry for sweeping the issue right away without a proper investigation.

Could you please try to update DBeaver and check this in the last version?

Still reproducible in 23.0.4

I can reproduce using 23.1.0 (EA)

Thanks.

https://github.com/dbeaver/dbeaver/assets/31996417/81fb3c0b-8817-4c2b-9de6-7d7457e7c798
Reproducible only if "Confirm SQL Execution" is enabled for connection type

@ewoerner Thank you for your request.
We need to enhance our parser to improve this behavior.


Incorrect "feedlist-title-format" expansion (%t)

IMHO %t must show total number of feeds in the "urls" file:
diff -up newsboat-2.19-git/src/feedlistformaction.cpp.orig newsboat-2.19-git/src/feedlistformaction.cpp
--- newsboat-2.19-git/src/feedlistformaction.cpp.orig   2020-05-19 09:37:30.803802297 +0300
+++ newsboat-2.19-git/src/feedlistformaction.cpp        2020-05-19 09:38:09.442451704 +0300
@@ -626,7 +626,7 @@ void FeedListFormAction::set_feedlist(
        fmt.register_fmt('N', PROGRAM_NAME);
        fmt.register_fmt('V', utils::program_version());
        fmt.register_fmt('u', std::to_string(unread_feeds));
-       fmt.register_fmt('t', std::to_string(i));
+       fmt.register_fmt('t', std::to_string(v->get_ctrl()->get_feedcontainer()->feeds_size()));

        f.set("head", fmt.do_format(title_format, width));
 }

I'm not so sure. Users can apply filters to feedlist, e.g. show just the unread feeds, or the ones with a particular tag. The title is automatically updated to match the feeds that are currently displayed. If I apply this patch, two things happen:

the title might become confusing, since unread_feeds change depending on what's in the list, and total number of feeds doesn't change;
the title becomes less useful, since it's no longer content-sensitive.

Is there a particular problem that you tried to solve with this patch? Tagging as question for now.

I think an option like this might be useful, maybe I will start using it as well with a format like:
showing %t feeds out of %a total (kept original %t, introduced %a == total_number_of_feeds)
However, the current usage of %t is still useful for people who prefer to have a context-sensitive title.
I've opened PR https://github.com/newsboat/newsboat/pull/963 which introduces new format specifiers for "total feeds" and "total unread feeds".
That PR also clarifies in documentation that the existing %t and %u show the count of currently visible feeds.

I still don't quite get the purpose of this. What's the point of showing the total number of feeds if the user is looking at a subset of them? The only one that comes to my mind is to distinguish filtered views from non-filtered ones. Is that it?

The only one that comes to my mind is to distinguish filtered views from non-filtered ones. Is that it?

For me, that is it.
It makes it easier to notice that you are not looking at the full list of feeds.
I think it is a nice feature but It is definitely not essential.

Got it! How about a new attribute that contains the filter itself? So the title is like this for non-filtered view:
newsboat 2.19 - Your feeds (0 unread, 100 total)

And like this for a filtered one:
newsboat 2.19 - Feeds (0 unread, 42 total) matching filter `feedtitle =~ ".*the.*"`

That clearly disambiguates between filtered and non-filtered views, and also reminds the user which filter is currently in use. The only downside to this (that I can think of) is that the user can't at a glance tell which percentage of feeds were filtered out.
In the example above, I put filter at the end because it might be longer than the screen is wide. Also, this new attribute could be added to the articlelist too (I don't think we have any other dialogs that can be filtered?).

I think it is a nice feature but It is definitely not essential.

Sorry for taking an antagonistic stance here. I'm not against the feature per se — I just want to understand what problem it's solving. With a use-case in hand, I can mentally fit it into the existing puzzle of features, and see if it can be done differently/better or rejected if it doesn't fit/requires more support than it's worth. I feel that without this sort of analysis, the program will just become a pile of assorted features, i.e. incomprehensible, practically unusable, and unmainteinable.

@SchweinDeBurg, @dennisschagt: will my suggestion above serve your use-cases, or is there something that's better served by a "total number of feeds" count?

@Minoru : Yes, exactly!

How about a new attribute that contains the filter itself?

Sounds good to me.

Cool!
Now that I thought about it a bit more, one interesting consequence of implementing my proposal is that show-read-feeds/show-read-articles will affect the title, because they're implemented with filters. I think it's okay, because it gives the user a clear indication of what they're looking at.
I also think this attribute is useful enough to be included in the title-format by default.
I'm not committing to implementing it myself, because I've blocked enough issues already. @dennisschagt's #963 can be used as a guide in implementing this, though; you just have to pick a letter and get the filter as a string. (And change the default. And update docs. And mention this in the CHANGELOG. :)

Now that I thought about it a bit more, one interesting consequence of implementing my proposal is that show-read-feeds/show-read-articles will affect the title, because they're implemented with filters.

That doesn't seem to be the case.
There are several ways in which a feed can be hidden irrespective of filters:
https://github.com/newsboat/newsboat/blob/6ca32a883fc0fdec8386cb8e49281371e1464afe/src/feedlistformaction.cpp#L578-L583

Hmm, I distinctly remember being surprised that a feature unrelated to filters is implemented via them. Perhaps it was rewritten since, or maybe I'm dreaming all this up =\ Thanks for investigating, @dennisschagt, and for the PR too!


Missing "Download all attachments as ZIP"

Rainloop <IP_ADDRESS>, Ubuntu 16.04.2 Server
Hi, i somehow lost the "Download all attachments as ZIP" functionality in my (premium) RainLoop installation.
I upgraded the server from Ubuntu 14.04 to 16.04 and at the same time Rainloop to <IP_ADDRESS> and lost it.
Can you please remind me, is it application.ini setting or separate module?

RainLoop uses php zip extension to do this stuff.
Perhaps you updated php and the zip extension disappeared after that.

That was it, php7.0-zip was not installed.
Thank you!


Raise if given different type to strictly typed models or entities

Raising when noticing the wrongly given @type is more explicit error behaviour than just ignoring the input.

Current coverage is 93.40% (diff: 100%)

Merging #35 into master will increase coverage by 0.33%

@@             master        #35   diff @@
==========================================
  Files            11         11
  Lines           375        379     +4
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits            349        354     +5
+ Misses           26         25     -1
  Partials          0          0

Powered by Codecov. Last update 93d2eaf...d04450f


resize support for WASM mode

It would be good if we could support having a resizable terminal widget -- right now the sizes are fixed, or set programmatically - whereas we'd like the text widget to be responsive to resizing performed by a mouse action.

@gdamore Hey, I was actually just thinking about polishing off what I have been working on, and and pushing it up.
I have tried to find a WASM build or runtime that would properly operate with xterm, without some backend server, rather then all self-contained in the browser's client runtime.
Forgive the lack of couth in my choice of test strings... However the TDFDraw fonts look great in a xterm.js vtty :grinning: It also does a great job to show off your library inside of it.
This adds another screen impl with the wasm/js GOOS/GOARCH build tags to produce js bindings, and init hooks/callbacks for being able to share the input/output buffers, and I then built an xterm addon specifically to handle your library with Go so that I could try and optimize as much as possible due to the lack of proper threading.
I am not sure when I would have time to polish it up... but I can push what I have if anyone wants to deal with my mess.
It supports all of xterm.js features (not that much needed to be done to handle). You may have to provide decent fonts for some things.
Transparency works, resize events are fired, things are quite snappy as long as you dont try and do lots of screen updates while also doing input.
https://github.com/gdamore/tcell/assets/1828125/781d588b-e439-4e21-bc11-359335d1a134

This looks interesting.  I would be interested in seeing this followed up.


Transactions

[ ] Allow players to donate.
[ ] Allow admin to send money to players.
[ ] Provide easy to use helper.
[ ] save all transactions for future statistics.

See commit #e4a6a77 & #f586724

I am closing this donations should be in another issue.


Unit testing of all possible (sensibly) testable parts of nape

Mainly to avoid regression whenever the source is changed. The unit tests i've so far added already picked out some bugs in AABB which must have existed for months without anyone noticing them! Not a good thing by any means.

unit tests (compiling to c++ as neko fails!) performed in release script before accepting a build for public release.


Setting up products on home page

I'm using bootstrap with shoppe so i did this in my home's index.html.erb
<% @products.each do |category, products| %>

<%= category.name %>

    <% products.each do |product| %>

                         <%= image_tag product.default_image.path, :width => '320px', :height => '150px' %>

<%= number_to_currency product.price %>

<%= link_to product.name, product_path(product.permalink)%>

15 reviews

              <% end %>

              <% end %>

and now i get an action error
NoMethodError in Home#index
Showing c:/Sites/shoppe/app/views/home/index.html.erb where line #48 raised:
undefined method `each' for nil:NilClass
Rails.root: c:/Sites/shoppe
I'm not sure what i should do because the models were not made in the newb friendly way i remember since i am using shoppe. HALP
P.S line 48 is  <% @products.each do |category, products| %>

What code is in the controller index method?
Just a heads up, Shoppe hasn't been tested on Windows.

@deanperry
  def index
@products = Shoppe::Product.root.ordered.includes(:product_category, :variants)
@products = @products.group_by(&:product_category)
  end

That is an issue here. I'm making an ecommerce website for a technical project in my college. I gotta pass it to graduate and i decided to use shoppe. But if i keep running into errors like this because of compatibility issues, i might be fkd :U

Alright i fixed the issue. After taking a long break and clearing my mind. (jk i was flipping going crazy)
i forgot to add the above index method into my home controller as well ;_:
#CLOSED


[HELP]Cant download ep image

Describe the issue:
I try to use escape pod from normal pc before 1 years ago. Now I find wire-pod.
When try to install ep image from this, An error occurred when I select Vector. When next day I tried, loading icon with circle showed and didn't go to next screen. I think it because My vector is too old. My vector OS version from CSIS screen is 0.9.0(V4)
What are you running wire-pod on?

[OS]: Linux(But trying to install ep image from windows)
[Hardware]: Synology NAS with x64 cpu

Are you setting up a prod (regular) bot or a dev/OSKR (unlocked) bot?
Prod
What steps have you tried?

I tried to install few times.
Tried from another devices like android.
I try clear user data.
Turn on experimental web platform
I try on incognito mode
(note: I will delete any issues which fit under this category but don't follow this template. I will not accept an "It's just not working!")

edit: I fixed link.

That site is outdated. Use https://wpsetup.keriganc.com
Web Bluetooth is finnicky. You'll just have to keep trying again and again. I have had the best experience with an incognito tab on Android. 0.9.0(V4) is the normal recovery firmware version, and is what he is supposed to be running for this step.

The setup link in the wiki was updated a couple weeks ago.
wpsetup.keriganc.com has essentially the same content as keriganc.com/vector-epod-setup, but it does not redirect. It is just hosted on a different server and has some more error-handling code.

https://github.com/kercre123/wire-pod/issues/334#issuecomment-2259507380

Clearing the bot's user data first finally got it to install from 0.9.0


Sanitizing a dashboard JSON breaks the possibility to import a dashboard JSON using NR UI

Description
Sanitizing a dashboard JSON with a command like yarn sanitize-dashboard snyk will get rid of all account IDs, etc. and make it more generic. However, it also removes the "permissions": "PUBLIC_READ_WRITE", attribute from the JSON. This then leads to the issue that I cannot import the sanitized dashboard JSON anymore using the NR UI.
Steps to Reproduce

export dashboard JSON
sanitize dashboard
import using NR UI

Expected Behavior
dashboard can be imported without any issues

not an issue when used in the context of the quickstarts


[BenchmarkService] class cast exception in step 9

Describe your question
I'm testing my code with 85d216f. There are error messages like these

Please update ur data

Please update ur data

thank u! the problem is fixed now


test

What is your Scenario?
url : https://adminsec2.nike.net/admin-app/#/users
EmailAddress<EMAIL_ADDRESS>Password:Ankit@314
manually page loading correctly

when we run test cafe

same issue in testcafe studio
please help me to resolve this issue..i tried wait await ..still no luck...
What is the Current behavior?
Page not lodaing when we enter user name and pass word
What is the Expected behavior?
page should load with all the content ...
What is your public website URL? (or attach your complete example)
url : https://adminsec2.nike.net/admin-app/#/users
EmailAddress<EMAIL_ADDRESS>Password:Ankit@314
manually page loading correctly

when we run test cafe

same issue in testcafe studio
please help me to resolve this issue..i tried wait await ..still no luck...
What is your TestCafe test code?
import { Selector } from 'testcafe';
import { ClientFunction } from 'testcafe';
//import { AngularSelector, waitForAngular } from 'testcafe-angular-selectors';

const cancelLoading = ClientFunction(() => window.stop());

const elementByXPath = Selector(xpath => {
    const iterator = document.evaluate(xpath, document, null, XPathResult.UNORDERED_NODE_ITERATOR_TYPE, null )
    const items = [];

    let item = iterator.iterateNext();

    while (item) {
        items.push(item);
        item = iterator.iterateNext();
    }

    return items;
});

const logIn = Selector('#okta-signin-submit');
const EmailAddress = Selector(elementByXPath('//*[@id="okta-signin-username"]'));
const Password = Selector(elementByXPath('//*[@id="okta-signin-password"]'));
const dropdown = Selector(elementByXPath('//*[@id="search_dropdown_chosen"]/a'));
const searchtextBox = Selector(elementByXPath('//input[@id="search_input"]'));
const searchButton = Selector(elementByXPath('//*[@id="search_mgfy_glass"]'));
const pageheader = Selector(elementByXPath('//*[@id="page_header"]/h2/translate'));
const option = Selector(elementByXPath('//*[@id="search_dropdown_chosen"]/div/ul/li[7]'));
const user = Selector(elementByXPath('/html[1]/body[1]/div[4]/div[1]/table[1]/tbody[1]/tr[2]/td[1]/a[1]'));
const HeaderUserName = Selector(elementByXPath('//translate[normalize-space()="Username"]'));
const ImpersonateUser = Selector(elementByXPath('//translate[normalize-space()="Impersonate User"]'));
const changepartner = Selector(elementByXPath('//a[@id="change_customer"]'));
const Partner = Selector(elementByXPath('//td[@class="input-radio"]//label[@for="account_0005025475"]'));
const SetPartnerButton = Selector(elementByXPath('//translate[normalize-space()="Set Partner"]'));
const ChooseActivity = Selector(elementByXPath('//translate[normalize-space()="Choose Activity"]'));
const Manage = Selector(elementByXPath('//a[@id="PRTL_LNK_MNGE"]'));
fixture`MyFixture`
     .page `https://adminsec2.nike.net/admin-app/#/users`;
      //beforeEach(async t => await failOnJsErrors());
     /*.beforeEach(async t => {
        await waitForAngular();
      });*/

      test('Navigate to the Docs', async t => {
        await t

            //t.maximizeWindow()
            t.resizeWindow(200, 100)
            t.typeText (EmailAddress<EMAIL_ADDRESS>
            await t.typeText (Password , 'Ankit@314')
            await t.click(logIn)
            await t.wait(10000)
            //----------------stop page load-------------------------------
            //const inputField = Selector('#PRTL_LNK_HOME2 > span');
            //await t
           //.expect(inputField.visible).ok()
           // await cancelLoading();
            await t.wait(120000)
           // t.navigateTo('https://adminsec2.nike.net/admin-app/#/users');
            //t.wait(120000)

            //await t.click(pageheader)

            await t.click(dropdown)
            .wait(10000)

            await t.click(Selector(option))
            await  t.typeText (searchtextBox , '5025475')
            .wait(8000)
            await t.click(searchButton)
            .wait(30000)
            await t.click(user)
            await t.click(HeaderUserName)
            .wait(10000)
            await t.click(ImpersonateUser)
            .wait(120000)
            await t.click(changepartner)
            await t.click(Partner)
            await t.click(SetPartnerButton)
            await t.click(ChooseActivity)
            await t.click(Manage)
            .debug()
            //.click(userSelect);
    })

Your complete configuration file
No response
Your complete test report
No response
Screenshots
No response
Steps to Reproduce
url : https://adminsec2.nike.net/admin-app/#/users
EmailAddress<EMAIL_ADDRESS>Password:Ankit@314
login using above credential
TestCafe version
1.18.4
Node.js version
No response
Command-line arguments
"test": "testcafe chrome test.js --ports 54321,34546"
Browser name(s) and version(s)
No response
Platform(s) and version(s)
No response
Other
No response

Thank you for your inquiry.
I have managed to reproduce this behavior on my side: the page is rendered incorrectly with TestCafe after logging into the site.
Please note that despite the fact that the page works properly without TestCafe, there are several errors in the DevTools Console.

These errors can cause the problems with testing in TestCafe.
For the team.
The minimal test to reproduce the problem
import { Selector } from 'testcafe';

const elementByXPath = Selector(xpath => {
    const iterator = document.evaluate(xpath, document, null, XPathResult.UNORDERED_NODE_ITERATOR_TYPE, null )
    const items = [];

    let item = iterator.iterateNext();

    while (item) {
        items.push(item);
        item = iterator.iterateNext();
    }

    return items;
});

const logIn = Selector('#okta-signin-submit');
const EmailAddress = Selector(elementByXPath('//*[@id="okta-signin-username"]'));
const Password = Selector(elementByXPath('//*[@id="okta-signin-password"]'));

fixture`MyFixture`
    .page `https://adminsec2.nike.net/admin-app/#/users`;

test('Navigate to the Docs', async t => {
    await t.typeText (EmailAddress , 'shefali.gulati@nike.com');
    await t.typeText (Password , 'Ankit@314');
    await t.click(logIn);

    await t.debug(); // the page looks incorrect
});

Test run result

I also have got this result in the hammerhead-playground on the commit.

How to resolve or any alternative to resolve or I need to inform dev team to fix the issues

There are some critical errors after logging, which can cause the problems with testing. Please inform the dev team about the issues. If this doesn't help, reopen the issue again.

tesg

hh

please delete the details

please delete details

Thank you for your inquiry. I have managed to reproduce this behavior on my side: the page is rendered incorrectly with TestCafe after logging into the site.
Please note that despite the fact that the page works properly without TestCafe, there are several errors in the DevTools Console.  These errors can cause the problems with testing in TestCafe.
For the team. The minimal test to reproduce the problem
import { Selector } from 'testcafe';

const elementByXPath = Selector(xpath => {
    const iterator = document.evaluate(xpath, document, null, XPathResult.UNORDERED_NODE_ITERATOR_TYPE, null )
    const items = [];

    let item = iterator.iterateNext();

    while (item) {
        items.push(item);
        item = iterator.iterateNext();
    }

    return items;
});

const logIn = Selector('#okta-signin-submit');
const EmailAddress = Selector(elementByXPath('//*[@id="okta-signin-username"]'));
const Password = Selector(elementByXPath('//*[@id="okta-signin-password"]'));

fixture`MyFixture`
    .page `https://adminsec2.nike.net/admin-app/#/users`;

test('Navigate to the Docs', async t => {
    await t.typeText (EmailAddress , 'shefali.gulati@nike.com');
    await t.typeText (Password , 'Ankit@314');
    await t.click(logIn);

    await t.debug(); // the page looks incorrect
});

Test run result  I also have got this result in the hammerhead-playground on the commit.

Can you please delete this comment on urgent basis please...

please delete this sensitive information like as provided above

@helen-dikareva
Please delete all the details mentioned in ticket u replied ..it have have sensitive information about client ..thanks
in advance

@Aleksey28  do u have access to delete the content replied by @helen-dikareva it’s sensitive information.please help me to delete the details available in the replied details by @helen-dikareva

Please delete  content u replied

Done. Check this, please. Feel free to contact us if I missed something else.

@Aleksey28  still I am able to see the details.. please strike out or remove the details like code as URL  and screenshot...u r help always apricated


bug(dev host binding @next.321): Unable to bind to <IP_ADDRESS>

Describe the bug
I am running SvelteKit in a docker container.
After upgrading to @next.321, I am unable to bind to <IP_ADDRESS> using npm run dev , which prevents access to SvelteKit inside the container
There appears to be a breaking change around npm run preview and host #4729 on 321. Perhaps there are some side effects to dev mode binding to '<IP_ADDRESS>' or the best practices have changed?
https://github.com/sveltejs/kit/pull/4729
SvelteKit  has been working with npm run dev --host to bind to <IP_ADDRESS> since version ~100.
Reproduction
Attempt 1:
package.json
"scripts": {
    "dev": "svelte-kit dev"
    ...
}

npm run dev -- --host <IP_ADDRESS>

><EMAIL_ADDRESS>dev
> svelte-kit dev "--host" "<IP_ADDRESS>"

  SvelteKit v1.0.0-next.321

  local:   http://localhost:3000
  network: http://<IP_ADDRESS>:3000

  Note that all files in the following directories will be accessible to anyone on your network: src/lib, src/routes, .svelte-kit, src, node_modules
  network: http://<IP_ADDRESS>:3000

  Note that all files in the following directories will be accessible to anyone on your network: src/lib, src/routes, .svelte-kit, src, node_modules
  network: http://<IP_ADDRESS>:3000

  Note that all files in the following directories will be accessible to anyone on your network: src/lib, src/routes, .svelte-kit, src, node_modules

Attempt 2:
package.json
"scripts": {
    "dev": "svelte-kit dev --host <IP_ADDRESS>",
    ...
}

npm run dev

><EMAIL_ADDRESS>dev
> svelte-kit dev --host <IP_ADDRESS>

  SvelteKit v1.0.0-next.321

  local:   http://localhost:3000
  network: http://<IP_ADDRESS>:3000

  Note that all files in the following directories will be accessible to anyone on your network: src/lib, src/routes, .svelte-kit, src, node_modules
  network: http://<IP_ADDRESS>:3000

  Note that all files in the following directories will be accessible to anyone on your network: src/lib, src/routes, .svelte-kit, src, node_modules
  network: http://<IP_ADDRESS>:3000

  Note that all files in the following directories will be accessible to anyone on your network: src/lib, src/routes, .svelte-kit, src, node_modules

Notice the slightly different rendering of
# Attempt 1 stdout
> svelte-kit dev "--host" "<IP_ADDRESS>"
...

# Attempt 2 stdout
> svelte-kit dev --host <IP_ADDRESS>

Logs
In Reproduction.

System Info
lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 20.04.4 LTS
Release:	20.04
Codename:	focal

node --version
v14.17.0

npm --version
8.3.2

Severity
serious, but I can work around it
Additional Information
This may be isolated to the dev mode
node build/index.js

Still seems to work and bind to <IP_ADDRESS> from within docker.

As discussed in Discord, this is likely an issue with their Docker network configuration since the bindings appeared to be correct when passing --host, --host <IP_ADDRESS>, and a missing --host (as seen on the screenshots on the Discord thread).
@ryanrussell will attempt to get to the bottom of it and provide a minimal reproduction if an issue is found in SvelteKit.

For me npm run dev --host doesn't work,
but when I add this new command to package.json it does:
"dev-host": "svelte-kit dev --host <IP_ADDRESS>",


Incomplete STEP

Not sure if it's intentional but the step only contains the RPi mount. Would be great to see the full model.

Sorry, fixing that now

OK, should be good now


error loading dynamically imported module

Seeing this error in staging. The trace doesn't have any spans in honeycomb so there's nothing else

In the console there was this error: Loading module from “https://staging.languagedepot.org/” was blocked because of a disallowed MIME type (“text/html”).

I believe https://stackoverflow.com/a/74057337 may explain the cause of this issue. Summary: when Vite compiles bundles, it includes a hash in the filename. When you deploy a new version of the bundle, the hash is different, which forces browser caches to reload it. But what can happen is the following sequence:

User loads a page where /project/sena-3 points to projectPage.123abc.js
Deployment runs, uploading a new projectPage.456def.js file and deleting projectPage.123abc.js
User does not reload the browser page, then clicks the /project/sena-3 link.
Router tries to load the non-existent 123abc.js page, gets 404 (which might be rendered in text/html), produces this error

https://stackoverflow.com/a/74861436 (another answer on the same SO question) has a suggested answer that works with the Vue router. Don't know yet if a similar approach could be taken in Svelte-Kit.

Yeah, I also think this it's the problem @rmunn suggests. Meaning it's a pretty normal problem. Somehow you have to get an outdated version of a loaded page up to date.
The docs suggest that SK tries to detect and fix this automatically automatically when a relevant error occurs:

If SvelteKit encounters an error while loading the page and detects that a new version has been deployed (using the name specified here, which defaults to a timestamp of the build) it will fall back to traditional full-page navigation.

I think that's what I've generally observed: that this error message sort of just flashes and the page is automatically reloaded, but that might have to do with dev and hmr. The screenshot from the OP suggests the browser stayed on the error page.
I see 2 sort of dumb, but potentially worth trying option (maybe in combination):

We detect these errors too and reload the page (it's hard to know what that will actually do to users. Did they just click a submit button? Where should we send them? etc.)
We use import { updated } from '$app/stores' in combination with the version poll config and show an appropriate message and refresh button

The hope is that we can reproduce this locally to same extent by doing something like:

turn off HMR in Vite
turn off optimistic loading on hover (just so there's less magic and confusion)
Load a page
Restart the server
Try to click a link

It sounds like we

sometimes catch this error: then we could use the updated store to see if it's due to an update and at the very least make that visible to the user so they know that we know what happened.
and sometime don't 🤷 catch the error: it which case we might always want to listen to updated and show a toast when it emits

Here's the single recorded occurence in staging. (this link isn't quite as good, but might be more reliable 🤔)
It's surrounded by "Function called outside component initialization" errors, which are thrown (for example) when onMount is called too late. I assume they're similar to the page subscribe error log and that neither is really a bug, they just get triggered when the svelte-app is broken.
Interestingly we actually only had those errors on staging for a few days. In dev there's a corresponding patch, but also sporadic occurences before and after.

This doesn't actually appear to have anything to do with an update.
The error was triggered at 8:52 (my time) with a version from 3 days prior and the app was only updated at 9:07.
Here's an overview of the requests by version.
So, my working theory is that...I don't know 😉. Or the server just failed to serve the module, because it was tripping over the "Function called outside component initialization" errors.

I'm able to produce 3 different behaviours.
I use a prod build, so that version checking is active and the script files get hashed.
1. Trigger the error without killing the server
This is done by making the script files invalid when/before the server starts = doesn't really make sense.

Build and run with pnpm vite build & pnpm vite preview
Load the home or admin dashboard page
Delete or rename frontend\.svelte-kit\output\client\_app\immutable\nodes\7.******.js (script file for the project page)
Restart the app pnpm vite preview
Hover over a project link and click on it
The desired error 🐛

2. SvelteKit automatically recovers (probably the most realistic scenario)
This is done by properly updating the app while a user has a (now outdated) loaded page.

Build and run with pnpm vite build & pnpm vite preview
Load the home or admin dashboard page
Make a change in [project_code]/+page.ts (e.g. add a comment)
Rebuild and restart the app pnpm vite build & pnpm vite preview
Hover over a project link
A 307 (404 after this PR) gets returned for a script
SvelteKit does a full refresh and recovers (also automatically navigating to the url behind a hovered link, which is weird, but whatever), successfully landing on the new version of the app 🪄

3. The server dies (not super interesting)
This is done by making the script files invalid while the server is running = doesn't really make sense.

Build and run with pnpm vite build & pnpm vite preview
Load the home or admin dashboard page
Make a change in [project_code]/+page.ts (e.g. add a comment)
Rebuild pnpm vite build
Hover over a project link
The server is dead 💥 with the "desired" error message 🐛

I just ran into this in staging again:
(Including a toast: A new version of the application was detected. You may need to reload the page.")

Trace: https://ui.honeycomb.io/sil-language-forge/environments/staging/trace/iQC4TrKRxFK?fields[]=c_name&fields[]=c_service.name&span=ec384c7c42f922b5
Service version in trace: v2023-10-19-f3cf95cc
Service version in app after a page reload: v2023-10-20-27ca67bf
Today is the 24th, so both versions were published several days ago. Also, it wasn't the first time I accessed the application today. WEIRD!!
So, somehow my browser loaded the version from the 19th, which wasn't functional, because the server was running the version from the 20th.
Reopening, because one way or another we have to decide if we want to deal with this more thoroughly.

This happened when I opened the application in a new tab.
I propose that we automatically reload the page if we land on the error page and detect a new version.

This hasn't been reported in staging or prod since the trace linked aboue (or since I merged my PR), so I'd say it's not very important and I'm moving to done. We'll be monitoring errors in prod anyway.
We could consider ignoring these errors in dev, where it happens frequently, almost certainly due to files being regenerated while the app is in use.
Prod:

Staging:

Dev:


Choose WFD survey field center

For DC1 this was done by @humnaawan, @egawiser and the LSS group.  As far as I know we do not yet have a DC2 field location.
A separate question is where if at all the DDF sits inside of the WFD survey.

I'd suggest we choose a DDF field position from the OpSim database, and
then select WFD visits around it. Why not the Twinkles field? (Extended
Chandra Deep Field South, RA: 03h 32m 30s Dec: -28d 06m 00s)
There are risks associated with DDF field placement:

If the over-density of time-variable objects is a problem for the
analysis of the WFD visits, we need to be able to recover from that.

If the time-variable objects or DDF/enhanced visit list are delayed, we
don't want to delay processing the main survey images.

I think we can mitigate both of these by putting the uDDF in the corner of
the main survey area rather than the center. Then, worst case scenario is
that we lose a corner of the main survey while a) the uDDF is simulated, or
b) ignored during main survey analysis.  Thoughts?

@drphilmarshall I think that putting the uDDF is a good idea and it looks like that field is far from the galactic plane so for WL and LSS the stellar contamination and extinction should be low and I guess that for DC2 is fine to have those conditions. @slosar showed interest in having some sort of higher-than-average extinction to play with it while we were preparing DC1. Is this something that you are still interested in? (I think that if we want to study magnification maybe it is not a great idea to have high extinction/stellar contamination but maybe you want to make some tests in high-extinction conditions?)

I second the suggestion of the TWINKLES field as a location for the uddf.
I also agree that the over density of time dependent objects is a risk for the main survey, though I think this worry is perhaps overestimated (at least for SN). I think we need to be careful that this is not the case.
I don't know the latest dither plan, but one of the advantages of having it at the center is that SN will not care, and others can implement their best dithers without it affecting us. Moving the uDDF to the corner affects us.

What if we put the uDDF region as close to a corner as we can without
losing any WFD image coverage? That shoudl still make the affected region
small compared to the main survey area, if we need to excise it.
On Thu, Dec 14, 2017 at 7:14 PM, rbiswas4<EMAIL_ADDRESS>wrote:

I second the suggestion of the TWINKLES field as a location for the uddf.
I also agree that the over density of time dependent objects is a risk for
the main survey, though I think this worry is perhaps overestimated (at
least for SN). I think we need to be careful that this is not the case.
I don't know the latest dither plan, but one of the advantages of having
it at the center is that SN will not care, and others can implement their
best dithers without it affecting us. Moving the uDDF to the corner affects
us.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/LSSTDESC/DC2_Repo/issues/54#issuecomment-351902043,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AArY9yRa8gGRpNfvCMRm_cs1Fimxj2cHks5tAeQsgaJpZM4RBFwt
.

That was the only worry, so if we ensure that this is true, I would not care about the uDDF being in the centre. If such a configuration exists (have not checked), we can all go home happy!

@drphilmarshall @cwwalter @rbiswas4 Since we have a new planning document for DC2 now, can we close this issue? Thanks!

I think so: the Run 2 main survey region field center will appear in the Run 2 specs note, ready to be applied in the extragalactic catalog when it is made.


Documentation v3

Hey @Dishie2498, please find below some improvements for the v3 of the doc :
1. Bug fixing

[x] Add the line autosummary_generate = True in the conf.py like here
[x] References are not listed because none are used in the code. You need to add a References section for the OinfoZeroLag and InfoTopo and cite the refences like here

2. Improvements

[x] The documentation of classes and functions generated using autosummary should follow those templates
[x] Can you create a banner that goes at the bottom of each page of the documentation? The banner should contains the logo of the INT, Aix-Marseille university and gsoc
[x] In the Overview tab, can you create a file called ovw_theory.rst with the title Theoretical background. Later, @Mattehub will write some of the mathematical background about information-theory and HOI. You'll also have to create a overview/index.rst file

Done in #13


Create File with URL

Match Overlap report with an additional column for Hathi URL.

Fixed by #668


Checking whether the bot is online before showing chat window

From a UX perspective, it is necessary to check if the bot is online & responding to messages before showing the actual webchat to the user. To achieve this, I am proposing the following:

Create a directline object and subscribe to the activity$ (using the botframework-directlinejs client library)
Monitor the connection status and check if it goes into ConnectionStatus.Online
If it does, then initialize BotChat.App

Can someone confirm that this is a sound approach, or point me into a better direction? Thanks!

That makes sense to me. Please report back here if this works out for you.
A question: what if WebChat had a visually distinct "connecting" mode? Would you still need to do this?

Great, thanks Bill - will do. A visually distinct "connecting" mode is even better from a UX standpoint in my opinion... especially in cases where the bot is not set to "Always on" and may take a while to start up. If the connection succeeds, then the user can start the conversation with the bot, otherwise, the chat window could show some sort of "offline" or "unavailable" mode.

@billba I did a quick test and it works: https://github.com/alyssaong1/WebchatStatus
Basically checked for a successful direct line connection, and also check that the bot doesn't respond with any errors before showing the webchat view. Main logic is in public/js/index.js.
Any suggestions/improvements welcome! Am thinking of doing an implementation of what you suggested re the visually distinct "connecting" mode... or is this already currently in the works for webchat?

Glad to hear it works. I'm going to close this issue.
I wouldn't hold your breath on the "connecting" mode...


Jeremyfyke/clausius clapeyron precipitation scaling

Added real-life test. Tweaked the docs.

I suggest we remove the constraint pr ( len(time) ==1 ) so this can be applied for example to a time series of annual maxima.

Hi @huard - I added another commit on my branch, related to the great comment you provided above.  Perhaps we can chat sometime about this -  how we structure this tool may guide how folks use it, which gets to the underlying philosophy behind CC temperature scaling.  Would love to download your thoughts before proceeding.

Good for me. Available next Monday anytime.


Unnecessary element in sorting

In sorting panel there is unnecessary element "Action" which does nothing

Need to delete line #61
Action
 in templates / views / products / components / sorting.tpl

Fixed by https://github.com/cscart/cscart-boilerplate/commit/88a5046628d8fba528654fc94da25f4979979ba1


Article about tracking presents only small information about the topic.

This article present very little info about tracking. It does answer following questions:

How does tracking affect future queries that query the same entity?
What will happen if I execute for example context.Entities.Where(e => e.Name.StartsWith("zix") twice in the row
How tracking works with TransactionScope and overall with transactions.
Does IsolationLevel of transaction impacts tracking?
What are criteria for LINQ query to return tracking entity and skip SQL query?
Why my query inside RepeatableRead transaction returns cached data from queries outside transaction when I just changed data manually from db side? Why afterwards I have read lock when I am using old tracked entity? It does not make sense - did I make some kind of SQL Query then but it is not updating my entity?
What is lifespan of tracked entities? Do they even have lifespan?
Is there a limit of how many tracked entities EF can have?
Are there any performance considerations we should think about when using tracking?
How can I disable tracking for whole DbContext? Is it possible?

Therefore this article is a stub and it explains nothing of importance.

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

ID: f3ffc114-df51-0be7-8972-6fcead14e011
Version Independent ID: 94c34571-7314-aab1-7898-93ac6d0f3430
Content: Tracking vs. No-Tracking Queries - EF Core
Content Source: entity-framework/core/querying/tracking.md
Product: entity-framework
Technology: entity-framework-core
GitHub Login: @smitpatel
Microsoft Alias: avickers

Questions for @dotnet/efteam
#2803 clarifies 1,2,5
9,10 is already answered by existing article.
I am not sure how/where/what we should document for rest.

[x] 1. How does tracking affect future queries that query the same entity?
[x] 2. What will happen if I execute for example context.Entities.Where(e => e.Name.StartsWith("zix") twice in the row
[ ] 3. How tracking works with TransactionScope and overall with transactions.
[ ] 4. Does IsolationLevel of transaction impacts tracking?
[x] 5. What are criteria for LINQ query to return tracking entity and skip SQL query?
[ ] 7. Why my query inside RepeatableRead transaction returns cached data from queries outside transaction when I just changed data manually from db side? Why afterwards I have read lock when I am using old tracked entity? It does not make sense - did I make some kind of SQL Query then but it is not updating my entity?
[ ] 8. What is lifespan of tracked entities? Do they even have lifespan?
[x] 9. Is there a limit of how many tracked entities EF can have?
[x] 10. Are there any performance considerations we should think about when using tracking?
[ ] 11. How can I disable tracking for whole DbContext? Is it possible?


Cache terminal output

It seems a script cached by wireit does not show previous terminal outputs, so if I cache a unit test (with coverage folder as output, src as input files), I won't see the test results and coverage table again.
Klarwind :: ~/Develop/template-lib-ts ‹master*› » WIREIT_LOGGER=metrics npm run test

><EMAIL_ADDRESS>test
> wireit

🏃 [test] Running command "vitest run"

 RUN  v2.1.5 /Users/otakustay/Develop/template-lib-ts
      Coverage enabled with v8

 ✓ src/__tests__/index.test.ts (1 test) 2ms

 Test Files  1 passed (1)
      Tests  1 passed (1)
   Start at  16:21:31
   Duration  243ms (transform 14ms, setup 0ms, collect 10ms, tests 2ms, environment 0ms, prepare 33ms)

 % Coverage report from v8
----------|---------|----------|---------|---------|-------------------
File      | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s
----------|---------|----------|---------|---------|-------------------
All files |     100 |      100 |     100 |     100 |
 index.ts |     100 |      100 |     100 |     100 |
----------|---------|----------|---------|---------|-------------------
✅ [test] Executed successfully
🏁 [metrics] Executed 1 script(s) in 0.49 seconds
	Ran                 : 1 (100%)
	Skipped (fresh)     : 0 (0%)
	Restored from cache : 0 (0%)
Klarwind :: ~/Develop/template-lib-ts ‹master*› » WIREIT_LOGGER=metrics npm run test

><EMAIL_ADDRESS>test
> wireit

✅ [test] Already fresh
🏁 [metrics] Executed 1 script(s) in 0.01 seconds
	Ran                 : 0 (0%)
	Skipped (fresh)     : 1 (100%)
	Restored from cache : 0 (0%)

This is by design. We actually used to cache stdout/err and replay it, but most of the time it was noisy. This could be a good option to have, though.

I believe output like unit test coverage, build asset size, are very helpful for developers, would it be possible that we add an option in wireit section like keepOutput to specify whether each command should silent previous output or just pipe it to stdout


Updated sfinae-ed call to partialPacket in gemm_pack_rhs

This function is responsible for speedups in standard packet loads for certain cases. The change is required to compensate for a recent CXX-03 compatibility fix in Eigen (Bitbucket commit id ff59d33). The change works whether the CXX-03 compatibility fix is there or not.

I've done this change as a part of Eigen version bump: https://github.com/tensorflow/tensorflow/commit/c9e93a1bbfb7041e9f86c6c73ec617afc5bbcb51

Thank you @ezhulenev
And sorry for breaking the Eigen C++03 compatibility.


[Checkbox][Radio] Alignment breaks on Safari and iOS

On Safari and iOS we found a bug that the labels are not aligned anymore to the rectangle (checkbox) or the ellipse (radio). Please compare to the screenshot.
Steps to reproduce the issue

Open the Checkbox or Radio on Safari (I am using Safari in Version 15.3 (176<IP_ADDRESS>.8))

wont do


win 7 use the app have some wrong...

windows 7 64bit use 32bit app it should show kb but it shows TB。

windows 7 64bit use 64bit app out of memory

When I add or remove hard driver,appear memory address or nil pointer dereference

说点人话就是
32位单位错误
64位热拔插硬盘会崩


devtron-graphana-test status shows error

devtron-graphana-test showing error in GCP and Linode while installing

Should be resolved now


Fix the snippet loading with Babel ES6 JavaScript

When using Babel ES6 JavaScript as syntax, the source is considered as source.js.jsx and with current definition, the snippet is not loaded/used. This change set fixes the issue.

Can you update https://github.com/sindresorhus/atom-ava/blob/master/snippets/assertions.json#L2 too?

Ah, of course. PR updated.

Thank you :)


Enable multiplex tests

Updates aegir to 9.3.2 and also enables the libp2p-multiplex tests.

\o/ awesome! :D thank you!