timeout error in build methos in ripple builder

cannot build ripple builder

-- Using src='https://www.sqlite.org/2018/sqlite-amalgamation-3260000.zip'
CMakeFiles/sqlite3.dir/build.make:91: recipe for target '../.nih_c/unix_makefiles/GNU_7.4.0/Release/src/sqlite3-stamp/sqlite3-download' failed
CMakeFiles/Makefile2:321: recipe for target 'CMakeFiles/sqlite3.dir/all' failed
Makefile:129: recipe for target 'all' failed
CMake Error at sqlite3-stamp/download-sqlite3.cmake:159 (message):
  Each download failed!

    error: downloading 'https://www.sqlite.org/2018/sqlite-amalgamation-3260000.zip' failed
         status_code: 1
         status_string: "Unsupported protocol"
         log:
         --- LOG BEGIN ---
         Protocol "https" not supported or disabled in libcurl

  Closing connection -1

         --- LOG END ---
         error: downloading 'https://www.sqlite.org/2018/sqlite-amalgamation-3260000.zip' failed
         status_code: 1
         status_string: "Unsupported protocol"
         log:
         --- LOG BEGIN ---
         Protocol "https" not supported or disabled in libcurl

  Closing connection -1

         --- LOG END ---
         error: downloading 'https://www.sqlite.org/2018/sqlite-amalgamation-3260000.zip' failed
         status_code: 1
         status_string: "Unsupported protocol"
         log:
         --- LOG BEGIN ---
         Protocol "https" not supported or disabled in libcurl

  Closing connection -1

         --- LOG END ---
         error: downloading 'https://www.sqlite.org/2018/sqlite-amalgamation-3260000.zip' failed
         status_code: 1
         status_string: "Unsupported protocol"
         log:
         --- LOG BEGIN ---
         Protocol "https" not supported or disabled in libcurl

  Closing connection -1

         --- LOG END ---
         error: downloading 'https://www.sqlite.org/2018/sqlite-amalgamation-3260000.zip' failed
         status_code: 1
         status_string: "Unsupported protocol"
         log:
         --- LOG BEGIN ---
         Protocol "https" not supported or disabled in libcurl

  Closing connection -1

         --- LOG END ---
         error: downloading 'https://www.sqlite.org/2018/sqlite-amalgamation-3260000.zip' failed
         status_code: 1
         status_string: "Unsupported protocol"
         log:
         --- LOG BEGIN ---
         Protocol "https" not supported or disabled in libcurl

  Closing connection -1

         --- LOG END ---

make[2]: *** [../.nih_c/unix_makefiles/GNU_7.4.0/Release/src/sqlite3-stamp/sqlite3-download] Error 1
make[1]: *** [CMakeFiles/sqlite3.dir/all] Error 2
make: *** [all] Error 2
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/sandbox/lib/jumpscale/Jumpscale/builder/system/BuilderBaseClass.py", line 162, in wrapper_action
    res = self.apply_method(func, kwargs)
  File "/sandbox/lib/jumpscale/Jumpscale/builder/system/BuilderBaseClass.py", line 93, in apply_method
    return func(**kwargs)
  File "/sandbox/lib/jumpscale/Jumpscale/builder/blockchain/BuilderRipple.py", line 60, in build
    self._execute(ripple_build_cmd, timeout=4000)
  File "/sandbox/lib/jumpscale/Jumpscale/builder/system/BuilderBaseClass.py", line 375, in _execute
    showout=showout,
  File "/sandbox/lib/jumpscale/Jumpscale/sal/process/SystemProcess.py", line 103, in execute
    replace=replace,
  File "/sandbox/lib/jumpscale/Jumpscale/core/InstallTools.py", line 1175, in execute
    raise RuntimeError(msg)
RuntimeError:
Could not execute:    bash /tmp/builders/rippled/builder_ripple.sh

stdout:
    Branch 'master' set up to track remote branch 'master' from 'origin'.
    -- The C compiler identification is GNU 7.4.0
    -- The CXX compiler identification is GNU 7.4.0
    -- Check for working C compiler: /usr/bin/cc
    -- Check for working C compiler: /usr/bin/cc -- works
    -- Detecting C compiler ABI info
    -- Detecting C compiler ABI info - done
    -- Detecting C compile features
    -- Detecting C compile features - done
    -- Check for working CXX compiler: /usr/bin/c++
    -- Check for working CXX compiler: /usr/bin/c++ -- works
    -- Detecting CXX compiler ABI info
    -- Detecting CXX compiler ABI info - done
    -- Detecting CXX compile features
    -- Detecting CXX compile features - done
    -- rippled version: 1.2.4
    -- Looking for pthread.h
    -- Looking for pthread.h - found
    -- Performing Test CMAKE_HAVE_LIBC_PTHREAD
    -- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Failed
    -- Check if compiler accepts -pthread
    -- Check if compiler accepts -pthread - yes
    -- Found Threads: TRUE
    -- NIH-EP cache path: /tmp/builders/rippled/rippled/.nih_c/unix_makefiles/GNU_7.4.0/Release
    -- BOOST_ROOT: /tmp/builders/rippled/boost_1_67_0
    -- BOOST_LIBRARYDIR:
    -- Boost version: 1.67.0
    -- Found the following Boost libraries:
    --   chrono
    --   context
    --   coroutine
    --   date_time
    --   filesystem
    --   program_options
    --   regex
    --   serialization
    --   system
    --   thread
    --   atomic
    -- Found OpenSSL: /usr/lib/x86_64-linux-gnu/libcrypto.a (found suitable version "1.1.1", minimum required is "1.0.2")
    -- Found ZLIB: /usr/lib/x86_64-linux-gnu/libz.so (found version "1.2.11")
    -- Pausing to download NuDB...
    -- Found Protobuf: /usr/lib/x86_64-linux-gnu/libprotobuf.a;-pthread (found version "3.0.0")
    -- Could NOT find Doxygen (missing: DOXYGEN_EXECUTABLE)
    -- doxygen executable not found -- skipping docs target
    -- Configuring done
    -- Generating done
    -- Build files have been written to: /tmp/builders/rippled/rippled/my_build
    Scanning dependencies of target snappy
    [  0%] Creating directories for 'snappy'
    [  1%] Performing download step (git clone) for 'snappy'
    [  2%] No patch step for 'snappy'
    [  3%] Performing update step for 'snappy'
    [  4%] Performing configure step for 'snappy'
    -- snappy configure command succeeded.  See also /tmp/builders/rippled/rippled/.nih_c/unix_makefiles/GNU_7.4.0/Release/src/snappy-stamp/snappy-configure-*.log
    [  5%] Performing build step for 'snappy'
    -- snappy build command succeeded.  See also /tmp/builders/rippled/rippled/.nih_c/unix_makefiles/GNU_7.4.0/Release/src/snappy-stamp/snappy-build-*.log
    [  6%] No install step for 'snappy'
    [  7%] No test step for 'snappy'
    [  8%] Completed 'snappy'
    [  8%] Built target snappy
    Scanning dependencies of target rocksdb
    [  9%] Building CXX object CMakeFiles/rocksdb.dir/src/ripple/unity/rocksdb.cpp.o
    [ 10%] Linking CXX static library librocksdb.a
    [ 10%] Built target rocksdb
    Scanning dependencies of target secp256k1
    [ 11%] Building C object CMakeFiles/secp256k1.dir/src/secp256k1/src/secp256k1.c.o
    [ 12%] Linking C static library libsecp256k1.a
    [ 12%] Built target secp256k1
    Scanning dependencies of target lz4
    [ 13%] Creating directories for 'lz4'
    [ 14%] Performing download step (git clone) for 'lz4'
    [ 15%] No patch step for 'lz4'
    [ 16%] Performing update step for 'lz4'
    [ 16%] Performing configure step for 'lz4'
    -- lz4 configure command succeeded.  See also /tmp/builders/rippled/rippled/.nih_c/unix_makefiles/GNU_7.4.0/Release/src/lz4-stamp/lz4-configure-*.log
    [ 17%] Performing build step for 'lz4'
    -- lz4 build command succeeded.  See also /tmp/builders/rippled/rippled/.nih_c/unix_makefiles/GNU_7.4.0/Release/src/lz4-stamp/lz4-build-*.log
    [ 18%] No install step for 'lz4'
    [ 19%] No test step for 'lz4'
    [ 20%] Completed 'lz4'
    [ 20%] Built target lz4
    Scanning dependencies of target libarchive
    [ 21%] Creating directories for 'libarchive'
    [ 22%] Performing download step (git clone) for 'libarchive'
    [ 23%] No patch step for 'libarchive'
    [ 24%] Performing update step for 'libarchive'
    [ 24%] Performing configure step for 'libarchive'
    -- libarchive configure command succeeded.  See also /tmp/builders/rippled/rippled/.nih_c/unix_makefiles/GNU_7.4.0/Release/src/libarchive-stamp/libarchive-configure-*.log
    [ 25%] Performing build step for 'libarchive'
    -- libarchive build command succeeded.  See also /tmp/builders/rippled/rippled/.nih_c/unix_makefiles/GNU_7.4.0/Release/src/libarchive-stamp/libarchive-build-*.log
    [ 26%] No install step for 'libarchive'
    [ 27%] No test step for 'libarchive'
    [ 28%] Completed 'libarchive'
    [ 28%] Built target libarchive
    Scanning dependencies of target ed25519-donna
    [ 28%] Building C object CMakeFiles/ed25519-donna.dir/src/ed25519-donna/ed25519.c.o
    [ 29%] Linking C static library libed25519-donna.a
    [ 29%] Built target ed25519-donna
    Scanning dependencies of target xrpl_core
    [ 30%] Building CXX object CMakeFiles/xrpl_core.dir/src/ripple/beast/core/core.unity.cpp.o
    [ 30%] Building CXX object CMakeFiles/xrpl_core.dir/src/ripple/beast/unity/beast_hash_unity.cpp.o
    [ 31%] Building CXX object CMakeFiles/xrpl_core.dir/src/ripple/beast/unity/beast_insight_unity.cpp.o
    [ 32%] Building CXX object CMakeFiles/xrpl_core.dir/src/ripple/beast/unity/beast_net_unity.cpp.o
    [ 33%] Building CXX object CMakeFiles/xrpl_core.dir/src/ripple/beast/unity/beast_utility_unity.cpp.o
    [ 34%] Building CXX object CMakeFiles/xrpl_core.dir/src/ripple/unity/basics1.cpp.o
    [ 35%] Building CXX object CMakeFiles/xrpl_core.dir/src/ripple/unity/json.cpp.o
    [ 36%] Building CXX object CMakeFiles/xrpl_core.dir/src/ripple/unity/protocol.cpp.o
    [ 37%] Building CXX object CMakeFiles/xrpl_core.dir/src/ripple/unity/crypto.cpp.o
    [ 38%] Linking CXX static library libxrpl_core.a
    [ 38%] Built target xrpl_core
    [ 39%] Running cpp protocol buffer compiler on src/ripple/proto/ripple.proto
    Scanning dependencies of target pbufs
    [ 40%] Building CXX object CMakeFiles/pbufs.dir/proto_gen/ripple.pb.cc.o
    [ 41%] Linking CXX static library libpbufs.a
    [ 41%] Built target pbufs
    Scanning dependencies of target sqlite3
    [ 42%] Creating directories for 'sqlite3'
    [ 43%] Performing download step (download, verify and extract) for 'sqlite3'
    -- Downloading...
       dst='/tmp/builders/rippled/rippled/.nih_c/unix_makefiles/GNU_7.4.0/Release/src/sqlite-amalgamation-3260000.zip'
       timeout='none'
    -- Using src='https://www.sqlite.org/2018/sqlite-amalgamation-3260000.zip'
    -- Retrying...
    -- Using src='https://www.sqlite.org/2018/sqlite-amalgamation-3260000.zip'
    -- Retry after 5 seconds (attempt #2) ...
    -- Using src='https://www.sqlite.org/2018/sqlite-amalgamation-3260000.zip'
    -- Retry after 5 seconds (attempt #3) ...
    -- Using src='https://www.sqlite.org/2018/sqlite-amalgamation-3260000.zip'
    -- Retry after 15 seconds (attempt #4) ...
    -- Using src='https://www.sqlite.org/2018/sqlite-amalgamation-3260000.zip'
    -- Retry after 60 seconds (attempt #5) ...
     -DCMAKE_BUILD_TYPE=Release
    + cmake --build .
    Cloning into 'snappy'...
    Note: checking out '1.1.7'.

    You are in 'detached HEAD' state. You can look around, make experimental
    changes and commit them, and you can discard any commits you make in this
    state without impacting any branches by performing another checkout.

    If you want to create a new branch to retain commits you create, you may
    do so (now or later) by using -b with the checkout command again. Example:

      git checkout -b <new-branch-name>

    HEAD is now at b02bfa7 Tag open source release 1.1.7.
    Cloning into 'lz4'...
    Note: checking out 'v1.8.2'.

    You are in 'detached HEAD' state. You can look around, make experimental
    changes and commit them, and you can discard any commits you make in this
    state without impacting any branches by performing another checkout.

    If you want to create a new branch to retain commits you create, you may
    do so (now or later) by using -b with the checkout command again. Example:

      git checkout -b <new-branch-name>

    HEAD is now at b3692db Merge pull request #531 from lz4/dev
    Cloning into 'libarchive'...
    Note: checking out 'v3.3.3'.

    You are in 'detached HEAD' state. You can look around, make experimental
    changes and commit them, and you can discard any commits you make in this
    state without impacting any branches by performing another checkout.

    If you want to create a new branch to retain commits you create, you may
    do so (now or later) by using -b with the checkout command again. Example:

      git checkout -b <new-branch-name>

    HEAD is now at 5fe69dd0 3.3.3
    CMake Error at sqlite3-stamp/download-sqlite3.cmake:159 (message):
      Each download failed!

        error: downloading 'https://www.sqlite.org/2018/sqlite-amalgamation-3260000.zip' failed
             status_code: 1
             status_string: "Unsupported protocol"
             log:
             --- LOG BEGIN ---
             Protocol "https" not supported or disabled in libcurl

      Closing connection -1

             --- LOG END ---
             error: downloading 'https://www.sqlite.org/2018/sqlite-amalgamation-3260000.zip' failed
             status_code: 1
             status_string: "Unsupported protocol"
             log:
             --- LOG BEGIN ---
             Protocol "https" not supported or disabled in libcurl

      Closing connection -1

             --- LOG END ---
             error: downloading 'https://www.sqlite.org/2018/sqlite-amalgamation-3260000.zip' failed
             status_code: 1
             status_string: "Unsupported protocol"
             log:
             --- LOG BEGIN ---
             Protocol "https" not supported or disabled in libcurl

      Closing connection -1

             --- LOG END ---
             error: downloading 'https://www.sqlite.org/2018/sqlite-amalgamation-3260000.zip' failed
             status_code: 1
             status_string: "Unsupported protocol"
             log:
             --- LOG BEGIN ---
             Protocol "https" not supported or disabled in libcurl

      Closing connection -1

             --- LOG END ---
             error: downloading 'https://www.sqlite.org/2018/sqlite-amalgamation-3260000.zip' failed
             status_code: 1
             status_string: "Unsupported protocol"
             log:
             --- LOG BEGIN ---
             Protocol "https" not supported or disabled in libcurl

      Closing connection -1

             --- LOG END ---
             error: downloading 'https://www.sqlite.org/2018/sqlite-amalgamation-3260000.zip' failed
             status_code: 1
             status_string: "Unsupported protocol"
             log:
             --- LOG BEGIN ---
             Protocol "https" not supported or disabled in libcurl

      Closing connection -1

             --- LOG END ---

    make[2]: *** [../.nih_c/unix_makefiles/GNU_7.4.0/Release/src/sqlite3-stamp/sqlite3-download] Error 1
    make[1]: *** [CMakeFiles/sqlite3.dir/all] Error 2
    make: *** [all] Error 2

Could not execute:    bash /tmp/builders/rippled/builder_ripple.sh

stdout:
    Branch 'master' set up to track remote branch 'master' from 'origin'.
    -- The C compiler identification is GNU 7.4.0
    -- The CXX compiler identification is GNU 7.4.0
    -- Check for working C compiler: /usr/bin/cc
    -- Check for working C compiler: /usr/bin/cc -- works
    -- Detecting C compiler ABI info
    -- Detecting C compiler ABI info - done
    -- Detecting C compile features
    -- Detecting C compile features - done
    -- Check for working CXX compiler: /usr/bin/c++
    -- Check for working CXX compiler: /usr/bin/c++ -- works
    -- Detecting CXX compiler ABI info
    -- Detecting CXX compiler ABI info - done
    -- Detecting CXX compile features
    -- Detecting CXX compile features - done
    -- rippled version: 1.2.4
    -- Looking for pthread.h
    -- Looking for pthread.h - found
    -- Performing Test CMAKE_HAVE_LIBC_PTHREAD
    -- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Failed
    -- Check if compiler accepts -pthread
    -- Check if compiler accepts -pthread - yes
    -- Found Threads: TRUE
    -- NIH-EP cache path: /tmp/builders/rippled/rippled/.nih_c/unix_makefiles/GNU_7.4.0/Release
    -- BOOST_ROOT: /tmp/builders/rippled/boost_1_67_0
    -- BOOST_LIBRARYDIR:
    -- Boost version: 1.67.0
    -- Found the following Boost libraries:
    --   chrono
    --   context
    --   coroutine
    --   date_time
    --   filesystem
    --   program_options
    --   regex
    --   serialization
    --   system
    --   thread
    --   atomic
    -- Found OpenSSL: /usr/lib/x86_64-linux-gnu/libcrypto.a (found suitable version "1.1.1", minimum required is "1.0.2")
    -- Found ZLIB: /usr/lib/x86_64-linux-gnu/libz.so (found version "1.2.11")
    -- Pausing to download NuDB...
    -- Found Protobuf: /usr/lib/x86_64-linux-gnu/libprotobuf.a;-pthread (found version "3.0.0")
    -- Could NOT find Doxygen (missing: DOXYGEN_EXECUTABLE)
    -- doxygen executable not found -- skipping docs target
    -- Configuring done
    -- Generating done
    -- Build files have been written to: /tmp/builders/rippled/rippled/my_build
    Scanning dependencies of target snappy
    [  0%] Creating directories for 'snappy'
    [  1%] Performing download step (git clone) for 'snappy'
    [  2%] No patch step for 'snappy'
    [  3%] Performing update step for 'snappy'
    [  4%] Performing configure step for 'snappy'
    -- snappy configure command succeeded.  See also /tmp/builders/rippled/rippled/.nih_c/unix_makefiles/GNU_7.4.0/Release/src/snappy-stamp/snappy-configure-*.log
    [  5%] Performing build step for 'snappy'
    -- snappy build command succeeded.  See also /tmp/builders/rippled/rippled/.nih_c/unix_makefiles/GNU_7.4.0/Release/src/snappy-stamp/snappy-build-*.log
    [  6%] No install step for 'snappy'
    [  7%] No test step for 'snappy'
    [  8%] Completed 'snappy'
    [  8%] Built target snappy
    Scanning dependencies of target rocksdb
    [  9%] Building CXX object CMakeFiles/rocksdb.dir/src/ripple/unity/rocksdb.cpp.o
    [ 10%] Linking CXX static library librocksdb.a
    [ 10%] Built target rocksdb
    Scanning dependencies of target secp256k1
    [ 11%] Building C object CMakeFiles/secp256k1.dir/src/secp256k1/src/secp256k1.c.o
    [ 12%] Linking C static library libsecp256k1.a
    [ 12%] Built target secp256k1
    Scanning dependencies of target lz4
    [ 13%] Creating directories for 'lz4'
    [ 14%] Performing download step (git clone) for 'lz4'
    [ 15%] No patch step for 'lz4'
    [ 16%] Performing update step for 'lz4'
    [ 16%] Performing configure step for 'lz4'
    -- lz4 configure command succeeded.  See also /tmp/builders/rippled/rippled/.nih_c/unix_makefiles/GNU_7.4.0/Release/src/lz4-stamp/lz4-configure-*.log
    [ 17%] Performing build step for 'lz4'
    -- lz4 build command succeeded.  See also /tmp/builders/rippled/rippled/.nih_c/unix_makefiles/GNU_7.4.0/Release/src/lz4-stamp/lz4-build-*.log
    [ 18%] No install step for 'lz4'
    [ 19%] No test step for 'lz4'
    [ 20%] Completed 'lz4'
    [ 20%] Built target lz4
    Scanning dependencies of target libarchive
    [ 21%] Creating directories for 'libarchive'
    [ 22%] Performing download step (git clone) for 'libarchive'
    [ 23%] No patch step for 'libarchive'
    [ 24%] Performing update step for 'libarchive'
    [ 24%] Performing configure step for 'libarchive'
    -- libarchive configure command succeeded.  See also /tmp/builders/rippled/rippled/.nih_c/unix_makefiles/GNU_7.4.0/Release/src/libarchive-stamp/libarchive-configure-*.log
    [ 25%] Performing build step for 'libarchive'
    -- libarchive build command succeeded.  See also /tmp/builders/rippled/rippled/.nih_c/unix_makefiles/GNU_7.4.0/Release/src/libarchive-stamp/libarchive-build-*.log
    [ 26%] No install step for 'libarchive'
    [ 27%] No test step for 'libarchive'
    [ 28%] Completed 'libarchive'
    [ 28%] Built target libarchive
    Scanning dependencies of target ed25519-donna
    [ 28%] Building C object CMakeFiles/ed25519-donna.dir/src/ed25519-donna/ed25519.c.o
    [ 29%] Linking C static library libed25519-donna.a
    [ 29%] Built target ed25519-donna
    Scanning dependencies of target xrpl_core
    [ 30%] Building CXX object CMakeFiles/xrpl_core.dir/src/ripple/beast/core/core.unity.cpp.o
    [ 30%] Building CXX object CMakeFiles/xrpl_core.dir/src/ripple/beast/unity/beast_hash_unity.cpp.o
    [ 31%] Building CXX object CMakeFiles/xrpl_core.dir/src/ripple/beast/unity/beast_insight_unity.cpp.o
    [ 32%] Building CXX object CMakeFiles/xrpl_core.dir/src/ripple/beast/unity/beast_net_unity.cpp.o
    [ 33%] Building CXX object CMakeFiles/xrpl_core.dir/src/ripple/beast/unity/beast_utility_unity.cpp.o
    [ 34%] Building CXX object CMakeFiles/xrpl_core.dir/src/ripple/unity/basics1.cpp.o
    [ 35%] Building CXX object CMakeFiles/xrpl_core.dir/src/ripple/unity/json.cpp.o
    [ 36%] Building CXX object CMakeFiles/xrpl_core.dir/src/ripple/unity/protocol.cpp.o
    [ 37%] Building CXX object CMakeFiles/xrpl_core.dir/src/ripple/unity/crypto.cpp.o
    [ 38%] Linking CXX static library libxrpl_core.a
    [ 38%] Built target xrpl_core
    [ 39%] Running cpp protocol buffer compiler on src/ripple/proto/ripple.proto
    Scanning dependencies of target pbufs
    [ 40%] Building CXX object CMakeFiles/pbufs.dir/proto_gen/ripple.pb.cc.o
    [ 41%] Linking CXX static library libpbufs.a
    [ 41%] Built target pbufs
    Scanning dependencies of target sqlite3
    [ 42%] Creating directories for 'sqlite3'
    [ 43%] Performing download step (download, verify and extract) for 'sqlite3'
    -- Downloading...
       dst='/tmp/builders/rippled/rippled/.nih_c/unix_makefiles/GNU_7.4.0/Release/src/sqlite-amalgamation-3260000.zip'
       timeout='none'
    -- Using src='https://www.sqlite.org/2018/sqlite-amalgamation-3260000.zip'
    -- Retrying...
    -- Using src='https://www.sqlite.org/2018/sqlite-amalgamation-3260000.zip'
    -- Retry after 5 seconds (attempt #2) ...
    -- Using src='https://www.sqlite.org/2018/sqlite-amalgamation-3260000.zip'
    -- Retry after 5 seconds (attempt #3) ...
    -- Using src='https://www.sqlite.org/2018/sqlite-amalgamation-3260000.zip'
    -- Retry after 15 seconds (attempt #4) ...
    -- Using src='https://www.sqlite.org/2018/sqlite-amalgamation-3260000.zip'
    -- Retry after 60 seconds (attempt #5) ...
     -DCMAKE_BUILD_TYPE=Release
    + cmake --build .
    Cloning into 'snappy'...
    Note: checking out '1.1.7'.

    You are in 'detached HEAD' state. You can look around, make experimental
    changes and commit them, and you can discard any commits you make in this
    state without impacting any branches by performing another checkout.

    If you want to create a new branch to retain commits you create, you may
    do so (now or later) by using -b with the checkout command again. Example:

      git checkout -b <new-branch-name>

    HEAD is now at b02bfa7 Tag open source release 1.1.7.
    Cloning into 'lz4'...
    Note: checking out 'v1.8.2'.

    You are in 'detached HEAD' state. You can look around, make experimental
    changes and commit them, and you can discard any commits you make in this
    state without impacting any branches by performing another checkout.

    If you want to create a new branch to retain commits you create, you may
    do so (now or later) by using -b with the checkout command again. Example:

      git checkout -b <new-branch-name>

    HEAD is now at b3692db Merge pull request #531 from lz4/dev
    Cloning into 'libarchive'...
    Note: checking out 'v3.3.3'.

    You are in 'detached HEAD' state. You can look around, make experimental
    changes and commit them, and you can discard any commits you make in this
    state without impacting any branches by performing another checkout.

    If you want to create a new branch to retain commits you create, you may
    do so (now or later) by using -b with the checkout command again. Example:

      git checkout -b <new-branch-name>

    HEAD is now at 5fe69dd0 3.3.3
    CMake Error at sqlite3-stamp/download-sqlite3.cmake:159 (message):
      Each download failed!

        error: downloading 'https://www.sqlite.org/2018/sqlite-amalgamation-3260000.zip' failed
             status_code: 1
             status_string: "Unsupported protocol"
             log:
             --- LOG BEGIN ---
             Protocol "https" not supported or disabled in libcurl

      Closing connection -1

             --- LOG END ---
             error: downloading 'https://www.sqlite.org/2018/sqlite-amalgamation-3260000.zip' failed
             status_code: 1
             status_string: "Unsupported protocol"
             log:
             --- LOG BEGIN ---
             Protocol "https" not supported or disabled in libcurl

      Closing connection -1

             --- LOG END ---
             error: downloading 'https://www.sqlite.org/2018/sqlite-amalgamation-3260000.zip' failed
             status_code: 1
             status_string: "Unsupported protocol"
             log:
             --- LOG BEGIN ---
             Protocol "https" not supported or disabled in libcurl

      Closing connection -1

             --- LOG END ---
             error: downloading 'https://www.sqlite.org/2018/sqlite-amalgamation-3260000.zip' failed
             status_code: 1
             status_string: "Unsupported protocol"
             log:
             --- LOG BEGIN ---
             Protocol "https" not supported or disabled in libcurl

      Closing connection -1

             --- LOG END ---
             error: downloading 'https://www.sqlite.org/2018/sqlite-amalgamation-3260000.zip' failed
             status_code: 1
             status_string: "Unsupported protocol"
             log:
             --- LOG BEGIN ---
             Protocol "https" not supported or disabled in libcurl

      Closing connection -1

             --- LOG END ---
             error: downloading 'https://www.sqlite.org/2018/sqlite-amalgamation-3260000.zip' failed
             status_code: 1
             status_string: "Unsupported protocol"
             log:
             --- LOG BEGIN ---
             Protocol "https" not supported or disabled in libcurl

      Closing connection -1

             --- LOG END ---

    make[2]: *** [../.nih_c/unix_makefiles/GNU_7.4.0/Release/src/sqlite3-stamp/sqlite3-download] Error 1
make[1]: *** [CMakeFiles/sqlite3.dir/all] Error 2

On branch development_builders working ok

it's working fin now on development_builders branch, tested methods: build, install, start, stop, sandbox.

Commit ID: 94db33b3c33880839f99cf26406a011423ddc57d


feat: add geo subdivision mocking

🎉 Thanks for submitting a pull request! 🎉
Summary
Expands upon the geo country mocking, by adding two libraries, a country file and a subdivision file, mapping codes to names and allowing users to mock subdivisions (states/provinces, etc) as well as countries.
Draft PR, have a few glitchy tests and some issues with importing a json file (eslint doesn't like it?)

For us to review and ship your PR efficiently, please perform the following steps:

[X] Update or add tests (if any source code was changed or added) 🧪
[X] Update or add documentation (if features were changed or added) 📝
[X] Make sure the status checks below are successful ✅

A picture of a cute animal (not mandatory, but encouraged)

Relevant issue: https://github.com/netlify/cli/issues/4498


provide a PDF version of the documentation

@a-siva ???

Can you provide a more detailed description of which documentation should be provided as a PDF

@a-siva,  everything

Hi, @catastrop. We don't produce PDF versions of the docs, but they're open source, so you can download and serve them locally. Or you can produce your own PDFs from the source code.
You can get the generated API docs from the SDK archive page: https://dart.dev/tools/sdk/archive
To get the content of dart.dev, you can clone/download and build the site-www repo: https://github.com/dart-lang/site-www


Remove loader animation to thin out dependencies

This is not worth it, especially since no one is seeing it on CI.

<EMAIL_ADDRESS>


Int, i128, i64, Nat, u128, and u64 are not fully representable in JS

Should be fixed when this is done: https://github.com/boa-dev/boa/issues/1961#issuecomment-1075673692


Add camel-debug automatically in quarkus:dev mode

Would the approach used here to add the camel-debug on classpath automatically https://github.com/apache/camel/pull/7877/files#diff-893d81229b9e254f8dfe5b3b291d713387666add70d56cf8584b95d7a1a6f8d8R114 be possible in Camel Quarkus too?
Or maybe we would need a specific Mojo binding which is wrapping the quarkus:dev?
follow-up on https://github.com/apache/camel-quarkus/issues/3775

Maybe I took the wrong approach in creating a dedicated extension for camel-debug.
Perhaps it would be better if we add camel-debug as a direct dependency to camel-quarkus-core-deployment. Then moved the BuildSteps that are in camel-quarkus-debug into the core. I think that would allow users to not have to explicitly add the debug dependency and also prevent the debug bits leaking outside of dev mode.

Even if, we could move camel-debug and camel-management into core, it would not be enough to make the Camel Debugger works properly as camel-quarkus-xml-jaxb or camel-quarkus-xml-io-dsl are also needed to be able to call dumpModelAsXml which means that one them should also be moved into the core and I guess that it is not wanted.


Orders always auto check for translation

Can you reproduce this issue on default Wordpress theme (eg Storefront)?
Yes
Can you reproduce this issue when all other plugins are disabled except WooCommerce, Polylang and Hyyan WooCommerce Polylang Integration?
Yes
What product versions and settings are you using when this issue occurs?

PHP: 7.1
WordPress: 4.8
WooCommerce: 3.09
Polylang:  2.1.5
Hyyan WooCommerce Polylang Integration: 1.01
Browser: Chrome

Steps to Reproduce

unchecked Language -> Settings -> Custom Post Types -> Orders
refresh WooPoly Setting page
Check back the Language Settings, Order is checked again.

What I Expected
Order remain unchecked.
What Happened Instead
checking on the source code, it seem like keep added the Orders need translation setting back to option table, is that a must ?

Question:

why would you want to turn off Language settings for Orders?
If an Order doesn't have a language, how would it know which language version of the Product to show?

Note that you don't have to translate the Orders, it's just that the Orders are associated with the language the customer selected so that all the emails etc can be sent in that language.
So yes, I guess at the moment Products and Orders would be forced translation on.
Noting your versions, please be aware that there are some issues with 4.8, especially with variations, which require the code from the 1.0.2 branch of this plugin.  Also I haven't tested this plugin with WooCommerce 3.0.9 and won't now 3.1 is out

closing - please open if there is a specific requirement identified


Aerial Life [PCSG01296]

App summary

App name: アエリアル・ライフ
App serial: PCSG01296
App version: 1.00

Vita3K summary

Version: v0.1.6
Build number: 2935
Commit hash: https://github.com/vita3k/vita3k/commit/4a50a4e0
CPU backend: Dynarmic
GPU backend: Vulkan

Test environment summary

Tested by: nishinji
OS: Windows 10
CPU: AMD Ryzen 9 3950X
GPU: RTX3060Ti
RAM: 32 GB

Issues
Screenshots

Log
vita3k.log
Recommended labels

Intro

as of https://github.com/Vita3K/Vita3K/commit/5810acf29cdf0033557c6b2c0c02cdf4bd043464, the game is playable with only the voices are stuttering.
Screenshots

Log
vita3k.log
Recommended Labels

Playable
audio bug

مرحبا


Show upload error when an image fails to upload

Show error text, as well as a red progress bar showing that an error occurred.

Fixed in #65


Error with nested prange+range loop incorporating if statement

Hi,
I am encountering a strange error when incorporating if statements inside nested prange+range loop. Here is a reproducer. The first function uses a simple prange loop while the second function uses a nested prange+range loop (I know there is no point in nesting the loops here, but this is just for demonstration). The second function fails to compile.
It does compile if I remove the if condition (but then the result of the function is of course wrong)
import numpy as np
import numba

N = 1000
x = np.random.rand(N)
is_positive = np.zeros(N)

@numba.njit(parallel=True)
def detect_positive( x, is_positive, N ):
    """Detect positive values in x, and store marker in `is_positive`"""
    for i in numba.prange(N):

        is_positive[i] = 0
        if x[i] > 0:
            is_positive[i] = 1

    return is_positive

@numba.njit(parallel=True)
def detect_positive_split( x, is_positive, N ):
    """Detect positive values in x, and store marker in `is_positive`
    SPLIT WORK ON 2 THREADS"""
    for i in numba.prange(2):

        for j in range( i*N//2, (i+1)*N//2 ):

            is_positive[j] = 0
            if x[j] > 1:
                is_positive[j] = 1

    return is_positive

detect_positive( x, is_positive, N )
assert np.allclose( (x>0).astype(np.float), is_positive )
print('First test passed')

detect_positive_split( x, is_positive, N )
assert np.allclose( (x>0).astype(np.float), is_positive )
print('Second test passed')

Here is the traceback:
Traceback (most recent call last):
  File "test.py", line 38, in <module>
    detect_positive_split( x, is_positive, N )
  File "/Users/rlehe/miniconda3/envs/fbpic/lib/python3.5/site-packages/numba/dispatcher.py", line 307, in _compile_for_args
    return self.compile(tuple(argtypes))
  File "/Users/rlehe/miniconda3/envs/fbpic/lib/python3.5/site-packages/numba/dispatcher.py", line 579, in compile
    cres = self._compiler.compile(args, return_type)
  File "/Users/rlehe/miniconda3/envs/fbpic/lib/python3.5/site-packages/numba/dispatcher.py", line 80, in compile
    flags=flags, locals=self.locals)
  File "/Users/rlehe/miniconda3/envs/fbpic/lib/python3.5/site-packages/numba/compiler.py", line 740, in compile_extra
    return pipeline.compile_extra(func)
  File "/Users/rlehe/miniconda3/envs/fbpic/lib/python3.5/site-packages/numba/compiler.py", line 360, in compile_extra
    return self._compile_bytecode()
  File "/Users/rlehe/miniconda3/envs/fbpic/lib/python3.5/site-packages/numba/compiler.py", line 699, in _compile_bytecode
    return self._compile_core()
  File "/Users/rlehe/miniconda3/envs/fbpic/lib/python3.5/site-packages/numba/compiler.py", line 686, in _compile_core
    res = pm.run(self.status)
  File "/Users/rlehe/miniconda3/envs/fbpic/lib/python3.5/site-packages/numba/compiler.py", line 246, in run
    raise patched_exception
  File "/Users/rlehe/miniconda3/envs/fbpic/lib/python3.5/site-packages/numba/compiler.py", line 238, in run
    stage()
  File "/Users/rlehe/miniconda3/envs/fbpic/lib/python3.5/site-packages/numba/compiler.py", line 494, in stage_parfor_pass
    parfor_pass.run()
  File "/Users/rlehe/miniconda3/envs/fbpic/lib/python3.5/site-packages/numba/parfor.py", line 192, in run
    self._convert_prange(self.func_ir.blocks)
  File "/Users/rlehe/miniconda3/envs/fbpic/lib/python3.5/site-packages/numba/parfor.py", line 352, in _convert_prange
    self._convert_prange(parfor_blocks)
  File "/Users/rlehe/miniconda3/envs/fbpic/lib/python3.5/site-packages/numba/parfor.py", line 269, in _convert_prange
    call_table, _ = get_call_table(blocks)
  File "/Users/rlehe/miniconda3/envs/fbpic/lib/python3.5/site-packages/numba/ir_utils.py", line 783, in get_call_table
    topo_order = find_topo_order(blocks)
  File "/Users/rlehe/miniconda3/envs/fbpic/lib/python3.5/site-packages/numba/ir_utils.py", line 747, in find_topo_order
    cfg = compute_cfg_from_blocks(blocks)
  File "/Users/rlehe/miniconda3/envs/fbpic/lib/python3.5/site-packages/numba/analysis.py", line 211, in compute_cfg_from_blocks
    term = b.terminator
  File "/Users/rlehe/miniconda3/envs/fbpic/lib/python3.5/site-packages/numba/ir.py", line 780, in terminator
    return self.body[-1]
IndexError: Failed at nopython (convert to parfors)

@ehsantn: Can you take a look at this?

Sure @seibert .

There was a minor error in the script above (the if condition in the second function read x[j]>1 instead of x[j]>0), and I just edited the above description to fix it. Sorry about this.
This does not affect the fact that the second function does not compile.

Note: my original test was a bit trivial because
x = np.random.rand(N)

returns only positive numbers. You might want to switch to
x = np.random.rand(N)  - 0.5

in case you are checking the vailidy of the detect_positive function.

Thanks a lot for fixing this issue by the way! ✨

Thank you for reporting this issue @RemiLehe . It led to solving a deep problem.

Thanks for report and fixes. Patched in https://github.com/numba/numba/pull/2478. Closing.


compile error in example packages/fullstack/examples/static-hydrated/src/main.rs error: cannot find attribute component in this scope

https://github.com/DioxusLabs/dioxus/blob/647815fa6f6db2304cda5bd36c78b4f8b0379f39/packages/fullstack/examples/static-hydrated/src/main.rs#L52
when trying to compile as a stand alone package, get a compile error:
error: cannot find attribute component in this scope
--> src/main.rs:52:3
|
52 | #[component]
|   ^^^^^^^^^
error: cannot find attribute component in this scope
--> src/main.rs:70:3
|
70 | #[component]
|   ^^^^^^^^^

The github is checked with the current version of each crate in the workspace. If you want to see what an example looked like at a specific release of dioxus, you can change the tag on github to the tag matching your release. Here is the 0.4 tag: https://github.com/DioxusLabs/dioxus/blob/v0.4.0/packages/fullstack/examples/static-hydrated/src/main.rs

Thank you!


fix: ignore dependencies versions bump when parsing version from commit logs

Builds upon https://github.com/relekang/python-semantic-release/pull/472 from @browniebroke and adds the commit_subject functionality
Fixes: https://github.com/relekang/python-semantic-release/issues/442

Tested in this run: https://github.com/eifinger/here_routing/runs/7449031696?check_suite_focus=true

Fixes #474

Works on one of my projects 👍🏻


Add Ninja build of MAPL

Description

This PR adds a Ninja build of MAPL along with the usual GNU Make.
I think.
We'll find out!
Related Issue

Motivation and Context

Ninja builds can often help show build errors in better ways, see https://github.com/GEOS-ESM/MAPL/pull/1655#issuecomment-1246831128
How Has This Been Tested?

If the CI works, it works!
Types of changes

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

Checklist:

[ ] I have tested this change with a run of GEOSgcm (if non-trivial)
[x] I have added one of the required labels (0 diff, 0 diff trivial, 0 diff structural, non 0-diff)
[x] I have updated the CHANGELOG.md accordingly following the style of Keep a Changelog

Sigh. I actually have to install Ninja in Docker images


Doc: Fix linting issues and rename nomad jobs

What is exactly linting issues in context of this PR?

Should be clearer now.

What is exactly linting issues in context of this PR?

making sure markdown documents follows standards.

I thought that standard applies on only CHANGELOG.md file? Does standard applies on all .md files?

What is exactly linting issues in context of this PR?

making sure markdown documents follows standards.

I thought that standard applies on only CHANGELOG.md file? Does standard applies on all .md files?

Yes. and terraform and ansible etc. See https://github.com/github/super-linter


repos without master branches (develop only) doesn't seem to clone

I've got a few repos with 1 branch called develop (no master).. this seems to be empty until I checkout develop and pull

Oh, I haven't considered a repo without a master branch, let me check that case and complete the script, thanks for contributing ;)

Thanks for the assistance.

bro in which option do you have problems? usning "-e" flag or using "-a" or what is the way that you get your repo not updated? becuase i am using gitRepoUpdater -a and i dont have problems with the repos with only a develop branch, but when i use gitRepoUpdater -e i found a bug when you answer "yes" en the repo


Tiny Syntax Error in sol-status-page/bin/local-sq-stats

The first BEGIN clause needs a closing curly brace in sol-status-page/bin/local-sq-stats I believe. At least I had to add it to get it to run.

Thanks, this is fixed. The issue was a bad merge duplicating the start of the begin block.


Creating a feature group from the Protein Family Sorter with a specific PLF and 66 genomes returns mutliple PLFams and 146 genomes

This is VERY FRUSTRATING!!!!  Everything appears to be broken in the Protein Family sorter and it is making my life miserable.
I have 2 genome groups with private genomes.  As the filter box doesn't work, I had to page through the PFS table until I found PLF_1279_00002629.  I created a feature group of that across my 66 genomes.  But when I went to look at that group, here were the PLFs associated with it:
PLF_1279_00000541
PLF_1279_00002617
PLF_1279_00002629
So now I have to manually go in and manipulate the group....AGAIN!!!!!

I suspect you created went through paging, selected PLF_1279_00000541, created a group, then continued
to next pages until you found PLF_1279_00002617, created another group, and then selected PLF_1279_00002629,
and created third group….without each time without deselecting previous choice. That is why each of your
feature groups contain previous selection as well.
Unless you reload page or manually deselect, the selections you have made are kept, including those you made
on previous page while using pagination in the tables.
Hope this explains.
-Maulik

On Jul 28, 2018, at 12:51 PM, ARWattam<EMAIL_ADDRESS>wrote:
This is VERY FRUSTRATING!!!! Everything appears to be broken in the Protein Family sorter and it is making my life miserable.
I have 2 genome groups with private genomes. As the filter box doesn't work, I had to page through the PFS table until I found PLF_1279_00002629. I created a feature group of that across my 66 genomes. But when I went to look at that group, here were the PLFs associated with it:
PLF_1279_00000541
PLF_1279_00002617
PLF_1279_00002629
So now I have to manually go in and manipulate the group....AGAIN!!!!!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/PATRIC3/patric3_website/issues/2057, or mute the thread https://github.com/notifications/unsubscribe-auth/ABLd76aaU23U5VNWB-r46PoxIspYcdWIks5uLKSygaJpZM4VlIIA.

That makes sense. I believe you are right. Thanks for your help.
Rebecca
Sent from my iPhone

On Jul 28, 2018, at 4:23 PM, Maulik Shukla<EMAIL_ADDRESS>wrote:
I suspect you created went through paging, selected PLF_1279_00000541, created a group, then continued
to next pages until you found PLF_1279_00002617, created another group, and then selected PLF_1279_00002629,
and created third group….without each time without deselecting previous choice. That is why each of your
feature groups contain previous selection as well.
Unless you reload page or manually deselect, the selections you have made are kept, including those you made
on previous page while using pagination in the tables.
Hope this explains.
-Maulik

On Jul 28, 2018, at 12:51 PM, ARWattam<EMAIL_ADDRESS>wrote:
This is VERY FRUSTRATING!!!! Everything appears to be broken in the Protein Family sorter and it is making my life miserable.
I have 2 genome groups with private genomes. As the filter box doesn't work, I had to page through the PFS table until I found PLF_1279_00002629. I created a feature group of that across my 66 genomes. But when I went to look at that group, here were the PLFs associated with it:
PLF_1279_00000541
PLF_1279_00002617
PLF_1279_00002629
So now I have to manually go in and manipulate the group....AGAIN!!!!!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/PATRIC3/patric3_website/issues/2057, or mute the thread https://github.com/notifications/unsubscribe-auth/ABLd76aaU23U5VNWB-r46PoxIspYcdWIks5uLKSygaJpZM4VlIIA.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.


Rename project to Rulebound

It is a better fit, removing a layer of abstraction.

[ ] Repo
[ ] package.json
[ ] Documentation
[ ] External variables
[ ] Internal variables
[ ] Tests


Section Truncation Enhancement

What's preventing us from grabbing all the strings for all the sections and then doing math with their lengths?
Section C is the section that has the filename, and out of all the sections, it's the only one that I wish could be made unshrinkable (which is the polar opposite of the behavior we have in that this is in fact the only section that is squishy) as it is the only section I ever have a reason to copy out of the terminal using the mouse.... i was hoping that we can add some calculations to make section C less squishy.
I mean I guess there are a ton of ways to make this work even a little better, and I understand that what we have now was a quickly-put-together compromise.
But it does leave a bit to be desired. The primary issue I have is that sometimes i open a file in a deep path and the name is quite long but I want it to be visible. This causes me to set section_truncate_width conservatively. However, now when I have Vim open to a file whose path is short, now my extra sections are unnecessarily hidden.
Sooo I can have some scripting that conditionally assigns section_truncate_width values based on the length of the file path string for the buffer. It seems a bit brittle, if it is even possible. I haven't tried it yet.
I was just thinking probably the next level of improvement could be to swap out section_truncate_width for another list of numbers which are meant to represent the maximum expected width of a section... this works for my custom "z" section (you should see it, it's so fancy! I love it), but it sadly does NOT work well for the "warning" section...
So that is just still kind of completely terrible.
So, back to the first sentence, I think we really just need to render the status sections, get their lengths, do math on them. At this point we have the power to prioritize which sections are to be made squishy. In addition, we can implement #686, and in addition there is even freedom to specify how to justify the truncation (left/center/right).

I understand this requirement and I thought it would be pretty. So I committed some changes to the dynamic_width branch. All it does, is it calculates the minimum width for all sections based on some percentages and uses that to shrink the statusline if necessary. Unfortunately, this does not work out so well. For one, it seems like automatic truncation breaks multibyte symbols (this is probably a bug in Vim). and second of all, it does not work very well to calculate the width. I still see sometimes truncated sections, even so the path is very short.
This is clearly not what I had in mind and makes very ugly. I am wondering, if one can calculate the section width before assigning it to the statusline so that truncation could be even more dynamic. However this clearly adds a performance penalty as basically each expression must be evaluated twice, similar to how the g:airline_skip_empty_sections works. Perhaps that would be the better approach.

i find the current truncation method with its hardcoded window sizes opinionated and overly agressive.
one size does not fit all. section_b gets removed if the window width is under 120.  filetype is truncated already at 90... these sizes are huge. they also ignore any customisations the user might have put into place (for example my section_z is tiny and modes are 1 letter) ending up with empty airlines omitting or truncating stuff when actually there is more than enough space to show everything.
the default terminal window width is 80 characters...  and even on a huge display a nerdtree on the side with 2 or 3 vertical splits and i am down to 80-110 columns (which is actually my sweet spot).
i wouldn't mind these arbitrary limits if i could actually override them without changing the code.
would you please consider making these constants configurable?

Have you looked into the help for truncation?

Am 03.04.2019 um 12:15 schrieb minusf<EMAIL_ADDRESS>i find the current truncation method with its hardcoded window sizes opinionated and overly agressive.
one size does not fit all. section_b gets removed if the window width is under 120. filetype is truncated already at 90... these sizes are huge. they also ignore any customisations the user might have put into place (for example my section_z is tiny and modes are 1 letter) ending up with empty airlines omitting or truncating stuff when actually there is more than enough space to show everything.
the default terminal window width is 80 characters... and even on a huge display a nerdtree on the side with 2 or 3 vertical splits and i am down to 80-110 columns (which is actually my sweet spot).
i wouldn't mind these arbitrary limits if i could actually override them without changing the code.
would you please consider making these constants configurable?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

i wouldn't mind these arbitrary limits if i could actually override them without changing the code.

to be more precise, have a look at the help :h airline-default, scroll down a bit and have a look at the variable g:airline#extensions#default#section_truncate_width. Does that do what you want?

Reading the code again more carefully: the 120 minimum window width for branch is overridable using parts:
call airline#parts#define_minwidth('branch', 50)

Now the branch is shown all the way down to winwidth=50.  But this is so burried in the docs,
that reading the code is almost easier...
In my understanding section_truncate_width for b never came into play because it wasn't even shown for winwidth < 120, so I think that's a bug right there.
On a different note: I would prefer never to truncate the branch name (except if it's the hash) to prevent commit apocalypse.
I just fired up a normal 80x24 terminal with my airline and it's clear that these defaults were picked with huge displays in mind:

Call me old fashioned but I think 80 would be a better baseline with prominent documentation examples how to scale this up to hipster sizes :}

Any chance to get the dynamic truncation back alive? I'd be very much in favor of something more dynamic depending on the status line contents. When using a grid window layout, truncation is often happening and the current behavior is somewhat limited.

have you tried the dynamic_width branch? it is still there.

I didn't date because the last commit is three years old ;-)


[Accessibility] [Screen Reader] Fix keyboard navigation using the screen reader in the 'Open a bot' dialog

Describe the issue
Users with visual impairment using a screen reader who relies on assistive technology might get confused and irritated if the focus gets stuck on any element.
Actual behavior:
In scan mode, the narrator's focus gets stuck after pressing the 'down arrow' key on the 'Bot URL' edit field.
Expected behavior:
In scan mode, the narrator's focus should not get stuck after pressing the 'down arrow' key on the 'Bot URL' edit field.
Repro Steps:

Open Bot Framework Emulator installed on the system.
Bot Framework Emulator Application with Welcome screen opens.
Navigate on the welcome screen and select the Open Bot button.
Open A bot Dialog opens, navigate on the dialog and enter inputs in edit fields.
Verify the issue.

Changes included in the PR

Added a conditional aria-hidden value to avoid getting stuck when using a screen reader

Depends on
PR #2300
Screenshots
Test cases executed successfully

Coverage increased (+0.004%) to 67.819% when pulling a68d9b22fb923b609ed1c0377e5aaa87cfcee48b on southworks:external/fix/southworks/fix-open-bot-keys-navigation into 9a794fb17f8d3fe39eeda19c755c96b951c81f40 on microsoft:main.


Transaction list -> Tranasaction detail -> Wrong explorer link

Steps:

Go to transaction list
Open transaction detail
Click explorer link

App redirects you to testnet explorer on main net profile

I know it is a day later, but I want to report a similar  but slightly different issue.
For me when I click on the explorer link, it doesn't take me anywhere.

@cryptoBeliever @jabo38 fixed.

I closed it but opened https://github.com/nemgrouplimited/symbol-mobile-wallet/issues/214


allow external config for cog_validate

Before we were forcing GDAL_DISABLE_READDIR_ON_OPEN=FALSE for validation. With this PR we let the user decide what env to set.
TODO

[ ] add a note about the link between env variable and validation result

cc @JoakimJoensuu

Just tried it on my project. Works like a charm!


Fixed precedence of operators

Also changed some regular expressions in RegexParser + changed the typealias from Regex to R

          1 Message

:book:
Hello, this worked

  Generated by :no_entry_sign: Danger


Reverse 3 finger gestures?

Ref: Conversation #1626 / K. C.

Won't implement.

Can this conversation (or at least the pertinent portions) be replicated here so that users don't have to have a helpscout login to view it?  I think I'm experiencing a similar issue.
Also, (if this is the same issue I'm having) why wasn't it fixed?

The Help Scout link refers to a private email for my own reference. Here is the relevant excerpt:

May I add a request? >> In Firefox: a 3 - finger vertical scroll will send one immediately to the top, or bottom of all webpages (amazingly handy); 3-finger left/right is page back/forward. So, yes, it's opposite with 3 fingers. Actually, I guess this covers 3-finger gestures globally

I can't comment on your issue since i don't know what it is, but here is a relevant excerpt from the FAQ:

Can you make it reverse 3- and 4-finger swipes too? No, this is not possible.

Well, I guess the fact that you can't do it makes my suggestion moot.  But I'll explain anyway.
A two-finger swipe will behave as one would expect from a touch screen, moving the content in the same direction as the swipe.  However, when changing Spaces using a three-finger swipe, the default behavior is opposite: swipe left to view the space to the left (moving the current screen to the right).
This is very confusing and I had hoped you application could resolve it, but it seems that this functionality is out of reach.

Unfortunately, yes it is. Gestures are implemented using a totally different system under the hood.
However, all you need to do is turn on "Scroll Direction: Natural" in trackpad preferences to get the behaviour you want.
You can then use Scroll Reverser to adjust scrolling separately (horizontal and/or vertical) if necessary.

Thinking outside the box!  Nice.  That did the trick!


use facsimile, surface and zone elements to gather information from page XML, follow PH

The transformation from PageXML should follow the PH section (11) of the TEI guidelines.
See https://www.tei-c.org/release/doc/tei-p5-doc/en/html/PH.html

[x] gather information about the facsimile in <facsimile> container element and <surface> and <zone> child elements as described in PHFAX (11.1)
[x] link via @facs from transcription to facsimile as described in PH-transc (11.2)
[x] optionally link via @startfrom facsimile to transcription

marked the checklist item gather information about the facsimile in <facsimile> container element and <surface> and <zone> child elements as described in PHFAX (11.1) as completed

mentioned in commit ad208c069e5293dadfb2bc8b1886c495809b6b9b

mentioned in commit b7c0e73006e9097895cd4b3b4f4f8baee302685b

mentioned in commit 44047aeb4199be66bb36046560efde376044428b

marked the checklist item optionally link via @startfrom facsimile to transcription as completed

added 2h of time spent

added 2h of time spent

mentioned in commit 4f0d845de77b550aae2e8c7008838542817eac18


Function 3 : Filter

I have addressed the following issues #13 #. Thank you!

Reopen issue and move to Milestone 2


fix join heading to prev list

Fix #188
The reason is the joinToPreviousListItem function only handles the cases for paragraph and code block.

@kepta  done


Add Middlesex Community College, please. See long description.

Add Middlesex Community College, please.
Our email domain has changed from middlesex.mass.edu to middlesex.edu. Our college website is still https://middlesex.mass.edu/

@halbeisenp-middlesex-edu Thank you for your patience while waiting for a review and processing your request. Pull request merged. Please start applying for JetBrains educational subscription at https://www.jetbrains.com/shop/eform/students in an hour, to allow the changes to propagate through JetBrains systems.


Missing section about connector and manifest

Hello,
In the page, under the section Post a message to the webhook using PowerShell there are steps on how to do this, very similar to prior section using cURL. However after point 3, some new paragraph/information starts with no context.
The text goes like this:
Include two icons, following the instructions in Icons.
Modify the icons portion of the manifest to refer to the file names of the icons instead of URLs.

For what I gather, following the next few paragraph, this is about something else. This is about creating your own applications and registering them in Teams so you can communicate with them. But this is not clear here that we're talking about something or a whole new concept.

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

ID: 28316a67-22fa-8a05-1ae0-fbe1c5720ef9
Version Independent ID: 8a250e46-2a30-af86-839d-9f83a8b48041
Content: Sending messages to Connectors and Webhooks - Teams
Content Source: msteams-platform/webhooks-and-connectors/how-to/connectors-using.md
Product: msteams
GitHub Login: @laujan
Microsoft Alias: lajanuar

@ngcdev , Thanks for pointing it out. We will update it.

Please provide powerShell example.

@laujan , Just below the PowerShell section, the content shown in the screenshot is from this link


Namadillo: IBC -> List all available tokens for IBC withdrawal

Following on from #1210, we should list all available tokens in a user's account as assets for IBC withdrawal.
Mateusz has updated the indexer to return IBC balances in the usual balance query, with the response being something like:
[
  {
    "tokenAddress": "tnam1qy440ynh9fwrx8aewjvvmu38zxqgukgc259fzp6h",
    "balance": "999000000"
  },
  {
    "tokenAddress": "tnam1p5nnjnasjtfwen2kzg78fumwfs0eycqpecuc2jwz",
    "balance": "18"
  }
]

We just need to display these balances and decode the token addresses. Namada CLI can already decode addresses, so we can just follow whatever it does.

Done


Segmentation Fault (core dumped) in Python 2 and Python 3

I was successfully able to run a customized hotword.py notebook in Ubuntu 16.04 and also in a Raspberry Pi3, where I added:
if event.type == EventType.ON_RECOGNIZING_SPEECH_FINISHED:
    if event.args['text'].lower()=='suspend':
        print('Speech Recognized')
        os.system('systemctl suspend')

However, at home in my other Ubuntu 16.04, I get the following output:
device-model-id home-ABC12345
device_id: ABCDE12345
Fatal Python error: Segmentation fault
Thread 0x00007f6070a63700  (most recent call first):
File "/usr/lib/python2.7/threading.py", line 359 in wait
File "/usr/lib/python2.7/threading.py", line 614 in wait
File "/usr/lib/python2.7/threading.py", line 1071 in run
File "/usr/lib/python2.7/threading.py", line 801 in __bootstrap_inner
File "/usr/lib/python2.7/threading.py", line 774 in __bootstrap
Current thread 0x00007f608053f700  (most recent call first):
File "/home/theone/.local/lib/python2.7/site-packages/google/assistant/library/assistant.py", line 114 in exit
File "hotword.py", line 139 in main
File "hotword.py", line 143 in
Segmentation fault (core dumped)
Previously, I had the same problem - Segmentation fault (core dumped) with Spyder, that would only open with a specific PyQt5 version.
However, it is quite complex to map / try all dependencies of google-assistant and their versions for compatibility. It seems it depends upon the version of libraries installed, for instance, with Anaconda.
Here are my libraries from pip list -l:
Arpeggio (1.9.0)
asn1crypto (0.24.0)
cachetools (3.1.0)
certifi (2018.11.29)
cffi (1.12.1)
chardet (3.0.4)
click (6.7)
cryptography (2.5)
enum34 (1.1.6)
faulthandler (3.1)
futures (3.2.0)
gdb-tools (1.2)
google-assistant-grpc (0.2.1)
google-assistant-library (1.0.0)
google-assistant-sdk (0.5.1)
google-auth (1.6.3)
google-auth-oauthlib (0.2.0)
googleapis-common-protos (1.5.8)
grpcio (1.18.0)
idna (2.8)
ipaddress (1.0.22)
monotonic (1.5)
oauthlib (3.0.1)
pathlib (1.0.1)
pathlib2 (2.3.3)
protobuf (3.6.1)
pyasn1 (0.4.5)
pyasn1-modules (0.2.4)
pycparser (2.19)
pyOpenSSL (19.0.0)
requests (2.21.0)
requests-oauthlib (1.2.0)
rsa (4.0)
scandir (1.9.0)
setuptools (40.8.0)
six (1.12.0)
sounddevice (0.3.12)
tenacity (4.12.0)
urllib3 (1.24.1)
For Python 3 I get:
device-model-id home-ABC12345
device_id: ABCDE12345
Fatal Python error: Segmentation fault
Current thread 0x00007fb35a611700 (most recent call first):
File "/home/theone/.local/lib/python3.5/site-packages/google/assistant/library/assistant.py", line 114 in exit
File "hotword_OK.py", line 139 in main
File "hotword_OK.py", line 143 in
Segmentation fault (core dumped)
Any suggestions ? ulimit adjustment didn't solve the problem. I can run 'systemctl suspend' and 'reboot' using voice, but when I try 'scrot' it aborts.

UPDATE:
I did a fix: instead of running
    if event.args['text'].lower()=='screenshot':
        print(event.args['text'])
        print('Speech Recognized')
        import os
        os.system('scrot')

I created another Python notebook containing:
import os
os.system('scrot')
And then altered hotword.py to:
    if event.args['text'].lower()=='screenshot':
        print(event.args['text'])
        print('Speech Recognized')
        import os
        os.system('python3 scrot.py')

No problem now.


update web and api tests according to the changes on gsm arena

API-Demo-Test: 2 failures due to the
Expected: a JSON array got: a JSON object org.skyscreamer.jsonassert.JSONAssert.assertEquals(JSONAssert.java:256) co....

Web-Demo-Test: 2 failures due to the
Unable to open model: ...

Web-Demo-Test: 2 failures due to the
stale element reference: element is not attached to the page document

new version should be fully passed

fixed. executing api and web tests should be green in carina-demo

Tested on jenkins - 5.1-beta3, qps-infra - develop, pipeline - develop.
Executed api and web tests.
Api tests are green, but web demo tests are red

fixed testdata to validate correctly. also pushed changes to carina-archetype so next archetype release should have100% pass rate for web

Tested on qaprosoft/carina-demo. Web tests are passed. Api tests are failed.

Reverified. Fixed.


Remove deps file from version control

The .deps file is used for Makefile shenanigans to get dependencies to download only once. It should not have been added to version control.

Closing this as it will cause more trouble than its worth; this is being taken care of in #566


Decide if upcoming Temporal.Duration limits should have an impact on DurationFormat

There are plans to limit Temporal.Duration values, details are still TBD. But we still need to decide if these limits should have an impact on Intl.DurationFormat.
The exact same issue was already discussed in #110, but that was before Temporal decided to reduce precision for their Temporal.Duration. Do we need to revisit #110?
For example I'm currently using the following BigInt-based approach to correctly implement PartitionDurationFormatPattern, steps 4.j.iv.1-3:
// Implementation for PartitionDurationFormatPattern 4.j.iv.1, similar functions are needed for 4.j.iv.2-3.
function DurationToFractionalSeconds(duration) {
  // Directly return seconds when no sub-seconds are present.
  if (
    duration.milliseconds === 0 &&
    duration.microseconds === 0 &&
    duration.nanoseconds === 0
  ) {
    return duration.seconds;
  }

  // Otherwise compute the overall amount of nanoseconds using BigInt to avoid
  // loss of precision.
  var ns_sec = NumberToBigInt(duration.seconds) * 1_000_000_000n;
  var ns_ms = NumberToBigInt(duration.milliseconds) * 1_000_000n;
  var ns_us = NumberToBigInt(duration.microseconds) * 1_000n;
  var ns = ns_sec + ns_ms + ns_us + NumberToBigInt(duration.nanoseconds);

  // Split the nanoseconds amount into seconds and sub-seconds.
  var q = ns / 1_000_000_000n;
  var r = ns % 1_000_000_000n;

  // Pad sub-seconds, without any leading negative sign, to nine digits.
  if (r < 0) {
    r = -r;
  }
  r = callFunction(String_pad_start, ToString(r), 9, "0");

  // Return seconds with fractional part as a decimal string.
  return `${q}.${r}`;
}

This approach ensures the precise results are computed for inputs like:
let df = new Intl.DurationFormat("en", {seconds: "numeric", fractionalDigits: 9});

// "10,000,000.000000002" with Number semantics, because
// 10_000_000 + (1 / 1_000_000_000) === 10000000.000000002.
assertEq(
  df.format({seconds: 10_000_000, nanoseconds: 1}),
  "10,000,000.000000001"
);

// "9,007,199,254,740,992.000000000" with Number semantics, because
// Number.MAX_SAFE_INTEGER + 2 ===<PHONE_NUMBER>740992.
assertEq(
  df.format({seconds: Number.MAX_SAFE_INTEGER, milliseconds: 2000}),
  "9,007,199,254,740,993.000000000"
);

Also see #110 and #151.

@ben-allen or @ryzokuken please bring this to the floor in an upcoming TG2 call.

Closed by #173


Phone number banned when testing login flow

I was testing my login flow in the app (using tdlib java), and now I get a message that my phone number is banned.
I sent an email to<EMAIL_ADDRESS>with explanation and my API id. Is there a way to expedite this?
More importantly - is there way to know why the number was banned and how I can prevent it from happening again? I imagine I will be doing a lot of tests while developing the app. Thanks!

The best you can do is to try to log in from an official app and send a recover request from there.

Thanks. That's what I did. How long does it usually take to get unbanned? Is there any other channel I can try?..

Same here with using Gram.js, banned soon after login :\

I found out soon after that we were supposed to use test numbers from different data centers, in order not to get flood restricted or banned. Guess I should have RTFM better :).

@rufatagayev If you still weren't unbanned, make sure that you exactly followed instructions provided at https://tginfo.me/phone-number-is-banned-en/. The article is very detailed and overall looks good to me.

Appreciate it, @levlam , checking it out now. Still not unbanned...

API docs say that logging out and in multiple times on production DCs may trigger a ban. That's why we have to use test DCs. But I believe for development purposes there should be a warning at least.

I'm trying again with new phone number and after login in tdlib it get banned.
I assume new phone number should not login using tdlib , did my assumption make sense ?

I'm trying again with new phone number and after login in tdlib it get banned. I assume new phone number should not login using tdlib , did my assumption make sense ?

not just you, I also feel, not only for old IDs / many users, maybe this is done to reduce spammers but you can contact Telegram to unban. After being unbanned you can use tdlib without being banned as long as it doesn't break the rules and doesn't spam


Bug: kusion workspace create failed on windows

What happened?
Executing kusion workspace create failed on windows, with error "open file failed"
What did you expect to happen?
Executing kusion workspace create succeed on windows.

This is because kusion use the function Join and Dir in package path, which does not support windows, ref: https://pkg.go.dev/path
Should use package path/filepath.
This bug will happen when doing the file-related operation, not only for workspace create.


az storage account create ignores encryption parameters when configuring table/queue encryption key type

Related command

az storage account create \
  --name "test-storage-account" \
  -g "test-rg" \
  --location "westeurope" \
  --sku Standard_GRS \
  --encryption-key-source "Microsoft.Keyvault" \
  --encryption-key-vault "[INSERT_VAULT_URI_HERE]" \
  --encryption-key-name "my-key" \
  --encryption-services blob file queue table \
  --encryption-key-type-for-queue Account \
  --encryption-key-type-for-table Account

Describe the bug

When including the --encryption-key-type-for-queue or --encryption-key-type-for-table properties, other provided encryption parameters are ignored.
I could trace back the section of code that triggers this behavior here: https://github.com/Azure/azure-cli/blob/azure-cli-2.37.0/src/azure-cli/azure/cli/command_modules/storage/operations/account.py#L182-L186
To Reproduce

Configure a key vault and key for storage account encryption (as described on this documentation page)

Either system-managed or user-managed identities reproduces this issue

Create the storage account using above command
Observe that the command completes successfully, and has created a storage account does not have the CMK configured

Expected behavior

To have the storage account created with the CMK
Environment summary

Bash, Azure CLI 2.37.0, MacOS and Linux (Azure DevOps agent)
Additional context

We've just come across this exact issue, and doesn't look like it has been fixed yet.
@jiasli / @evelyn-ys - any update on this? could we get this prioritised to be worked on please?

Hi @chrisking81 , @baaym , here is the private package to test https://zhiyihuangsa.blob.core.windows.net/sharing/cli-private-for-fixing-storage-account-create-with-encryption.zip  Let me know if it fixes the issue.
Instructions to install: ## 1. Prepare and Use a separate virtual environment
Create a python virtual env named testenv with:
python -m venv testenv

Activate the env (if you are using powershell):
.\testenv\Scripts\Activate.ps1

Activate the env (if you are using bash):
source venv/bin/activate

2. Install CLI private package
Unzip the file and install three cli whl packages (azure_cli, azure_cli_core, azure_cli_telemetry):
pip install azure_cli-2.50.0.post20230710052857-py3-none-any.whl azure_cli_core-2.50.0.post20230710052857-py3-none-any.whl azure_cli_telemetry-1.0.8.post20230710052857-py3-none-any.whl


Search Error

System.InvalidOperationException: 'The LINQ expression 'DbSet()
.Where(a => a.TableName.IndexOf(
value: "AmlElement",
comparisonType: OrdinalIgnoreCase) != -1)' could not be translated. Additional information: Translation of method 'string.IndexOf' failed. If this method can be mapped to your custom function

Hi @omar-asfuor
What is your EF version?

@ekondur,
I also get this error using Entity Framework Core 7.0.15. I believe it has something to do with the navigational properties on the entity even though they're not being used on the Datatable. I'm not 100% sure about that, just an assumption. In the past I had to create a SQL view of the entity and use that instead to get by the error. It would be nice to be able to use the entity itself.

I did some more testing on this and found it has something to do with the changes in DatatableJS.Data 3.7.0. I rolled the version back to 3.4.1 in my project and it started working again. Does this have something to do with the case sensitive searching that was added in 3.7.0?

Hi @ItzFender
I will fix it as soon as possible, thank you for your explanation

Fixed with version 3.8.0, thank you for your contributions @ItzFender @omar-asfuor


Automating Agent Creation

Do we have any plans to automate agent creations in DialogFlow using node client?

I have created something similar please go to my get up profile and find bot generator repo, the code is not so good but it is working some level, so please if you find that repository helpful thumbs up and you are improved God and pull request are warm welcome

looking for same


Check various aspects of a certificate

Alg.
SANS list

https://www.monitoring-plugins.org/doc/man/check_http.html

icinga has built-in solution for this: https://www.icinga.com/docs/icinga2/latest/doc/10-icinga-template-library/#http
it should be the same plugin.

Currently we implement icinga plugins that can read the data from a Kubernetes secret or secrets and perform these checks.
We can work towards bringing parity to icinga's built-in plugin but this has to be reimplemented in some way https://github.com/appscode/searchlight/blob/master/plugins/check_cert/lib.go#L203


Add RouteContext::method

Is your feature request related to a problem? Please describe.
Since Route has a method attribute, it would be nice to have a way to use this value inside components.
Describe the solution you'd like
App.rs
<Route
    path="/path"
    methods=&[Method::Get, Method::Post]
    view=Page />

Page.rs
pub fn Page() -> impl IntoView {
    let route = use_route();

    match route.method() { // <----- This feature request
        Method::Get => todo!(),
        Method::Post => todo!(),
        _ => unreachable!(),
    };

    view! {
        // ...
    }
}

I'm actually not sure what you're asking for. Are you asking for access to the methods prop (in which case route.method() would return a &[Method], and your match statement doesn't make sense)? Or are you asking for access to the HTTP method in response to which the page is currently being rendered? (in which case it will be Option<Method>, as sometimes your components are being rendered in the browser and there is no HTTP request involved)

Yeah, it was confusing, and I am having a hard time myself trying to put it in words. Let me try again.

Or are you asking for access to the HTTP method in response to which the page is currently being rendered?

Not necessarily the raw HTTP method. It could some sort of "router method" if that makes sense.
If the route was triggered in the browser and no method was defined there, then the default Method::Get could be returned.
I understand that Route path and HTTP path are not the same, but most of the time we map them 1:1 for better graceful degradation.
In other words, most of the time we want to map:
GET /articles/nature
to:
<Route
    path="/articles/:type"
    view=Articles />

Regardless of it being rendered by the browser or by the server, Articles will use the value of :type during render.
Articles has no idea about HTTP, it only knows Route, as it should be. Yet, for graceful degradation purposes, most of the time we will have Route path and HTTP path being a 1:1 map.
Now lets say we have a POST request:
POST /articles/nature
<Route
    path="/articles/:type"
    methods=&[Method::Get, Method::Post]
    view=Articles />

Articles will be rendered as normal, but there is no way to distinguish between a POST and GET from inside the component.
Today it seems that RouteProps::methods are only used to generate integrations with HTTP frameworks, but Leptos has no concept of Method. I think the absence of this concept makes it harder to create these 1:1 mappings for graceful degradation purposes.
A more concrete example can be found here: https://github.com/leptos-rs/leptos/issues/1120
This simplistic example is trying to demonstrate how to gracefully degrade when JS is not available, but the implementation is incomplete.
It covers the following cases:

JS is not available.
JS is available and FavoriteColors was rendered on the server.

These are covered because when FavoriteColors is rendered on the server, favorite_color_form can differ between GET and POST.
But it does not cover the following:

JS is available and FavoriteColors was rendered on the browser after some routes navigation.

The case above is not covered because when it is rendered on the browser, it will always send a POST request when calling favorite_color_form.

As I understand it the answer is that you are looking for the method the current navigation is being rendered in, always interpreting that as GET for a client-side navigation. Which sounds great. And I believe you that it would make that incomplete demo better. It's unlikely I'll have time to work on this any time soon, but if you'd like to make a PR I'd be happy to look at it.

I'd like to pick this up but I'd like a bit of direction. Would this involve a method on RouteContext that returns the current method? Say a post request on that route should still render that component but the component should be able to query that like in @yokomizor's original comment?

@zoomiti Yes, that's correct: It is solely a question of adding a method that returns the method by which someone was routed to the current page (using GET if it was a client-side navigation).
In effect, this would mean

adapting the server integrations to not only match on different methods, but provide that information via context to the router
returning that provided method, if it's found, otherwise defaulting to GET

@gbj So I have a working implementation of this, should I make an accompanying example? For testing purposes?


json deserialize handle backslashes correctly

the following cmake coded json is problematic : "\"\\\\\\\"\"" which is a backslash backslash backslash json


Support an optional compilation database directory at initialization

This allows the compile_commands.json file to be anywhere, not necessarily at the root of the project. This is specially useful for buck projects, which produce compilation dbs in the buck-out folder, and for projects that, given a certain configuration, use a different compilation db.

You should add the config variable to the vscode extension as well (in package.json and in the clientConfig variable in extension.ts) and then rebuild the vscode extension.

good to know, i just updated it

thanks for the review, i don't know but it's somewhat hard to change my old naming habits lol

I can pick up the lsp-cquery.el changes for Emacs once this has landed, too.

thanks, sadly I know nothing about emacs


HighDPI on Mac is broken

due to a7c95df6a9eb271ddc76686c3f2931199ba24280 (Lime 2.4.3 works fine) lime is broken for High DPI (Retina) Mac. The app gets the High DPI screen, but stageWidth, stageHeight are still the original values, and the window is the non-retina size.
If you specify  the window created will have 100x100 non high-dpi size (i.e., the same size as before this change), while everything inside the app (stage, etc) will be in high DPI, but non-drawable outside the 100x100 area. This means you can only render things on the bottom right corner of the window. It's messy.

I can confirm this issue, experienced on a 13" MacBook Pro. Lime 2.4.3 works fine for me as well.

I'm having the same issue. I verified that it's not just my code by running PiratePig using "lime test neko -Dlegacy". The entire game is squeezed into the bottom-left quadrant of the screen on my retina display.

I tried to mess with this, but didn't get very far:
The first thing I did was to start using SDL_GL_GetDrawableSize instead of SDL_GetWindowSize. This is the correct function to use when going for HighDPI (it returns the actual pixel size). It could also be used to calculate the ratio difference.
If I change that on SDL2Stage, then the whole window area starts getting drawn, except that now Lib.current.stage.stageWidth returns twice the size it should. Example:
Requested on project.xml: 100x100
GetWindowSize: 100x100
GetDrawableSize: 200x200
Lib.current.stage.stageWidth: 400
I'm assuming this means that the stage scaling thing is going insane over this.
I'll keep poking.

Oh. I think I got the problem.
Lib.create() creates a stage that has a "nominal" width of 100x100 (which was passed from the project configuration.
Then the Stage tries to calculate the scale factor, which would be: current width / nominal width, which in this case returns 2, but should be 1.
The it says "well, we need to zoom in everything 2x", which leads to this 400.
It all boils down to the fact that the new SDL window created is actually twice the size it should be. I.e., I'm asking for 100x100 and it's creating a 200x200 screen (the same physical size as a 100x100 low dpi).
I can either:

try to make the default window small (i.e., respect the window size requested on Mac).
make the nominal size to actually factor in the DPI scaling (by surfacing a scale number somewhere that is getdrawablesize/getwindowsize.

Wow, thanks for looking into this. I'm afraid that I tend to be a Lime/OpenFL end user, with basically zero knowledge of the internals (e.g., SDL), so it's hard for me to agree or disagree with your proposed fixes.
I should note that this problem dovetails nicely with a question I asked previously -- in the newer builds of OpenFL, it's no longer possible to query openfl.system.Capabilities.screenDPI (see http://community.openfl.org/t/screendpi-no-longer-valid/1186). If you're thinking about "surfacing a scale number", I'd vote for creating global constants in Lime for the display's horizontal and vertical resolutions and DPI, and perhaps scaling factor as well (is that number independent of the other three?).

I got this problem too.
What are the implications of options 1 and 2?

On retina displays on iOS, my stage starts out at half the size it should be. Then after the first frame, the values are corrected and a RESIZE event is dispatched. It sounds like what you're seeing is different, but it's probably worth double-checking.
(Also, I don't have a retina Mac, so if that's not it, I have nothing to contribute.)

Thanks for the suggestion, but resizing screen doesn't solve the issue.
A possible workaround is mark the .app to open in low resolution on info window.

I can confirm that I experience the same issues with 2.4.4 on a Macbook Pro Retina, and I can confirm that switching to lime 2.4.3 resolves the issue. I did however find that setting the stage alignment to bottom right causes similar calculation errors, even on 2.4.3, maybe related?
Lib.current.stage.align = StageAlign.BOTTOM_RIGHT;
See the following video for an example: http://youtu.be/Ay7hSXXeRY0

Just installed Lime 2.4.5 today, and I'm no longer seeing this problem with -Dlegacy.

Awesome, thank you :smile:

updated lime with version 2.4.7
tried to build using command "lime test mac -Dlegacy -debug"
The window is created and then "Crash Report" window appears.
Building with "neko" works fine.
Building without "-debug" using "mac" also works fine.

Does lime test mac -Dlegacy -debug -clean work differently?

Nope, same result.