Build error with pip

I tried to use pip install mujoco_mpc/python/  to install it on Ubuntu 20 and the version of Python is 3.8.10 and the version of mujoco-src downloads automatically is 3.0.1. It reports some errors as follow:
Processing ./mujoco_mpc/python
  Preparing metadata (setup.py) ... done
Requirement already satisfied: grpcio in ./venv/lib/python3.8/site-packages (from mujoco-mpc==0.1.0) (1.59.3)
Requirement already satisfied: mujoco>=2.3.3 in ./venv/lib/python3.8/site-packages (from mujoco-mpc==0.1.0) (3.0.1)
Requirement already satisfied: protobuf in ./venv/lib/python3.8/site-packages (from mujoco-mpc==0.1.0) (4.25.1)
Requirement already satisfied: absl-py in ./venv/lib/python3.8/site-packages (from mujoco>=2.3.3->mujoco-mpc==0.1.0) (2.0.0)
Requirement already satisfied: etils[epath] in ./venv/lib/python3.8/site-packages (from mujoco>=2.3.3->mujoco-mpc==0.1.0) (1.3.0)
Requirement already satisfied: glfw in ./venv/lib/python3.8/site-packages (from mujoco>=2.3.3->mujoco-mpc==0.1.0) (2.6.3)
Requirement already satisfied: numpy in ./venv/lib/python3.8/site-packages (from mujoco>=2.3.3->mujoco-mpc==0.1.0) (1.24.4)
Requirement already satisfied: pyopengl in ./venv/lib/python3.8/site-packages (from mujoco>=2.3.3->mujoco-mpc==0.1.0) (3.1.7)
Requirement already satisfied: importlib_resources in ./venv/lib/python3.8/site-packages (from etils[epath]->mujoco>=2.3.3->mujoco-mpc==0.1.0) (6.1.1)
Requirement already satisfied: typing_extensions in ./venv/lib/python3.8/site-packages (from etils[epath]->mujoco>=2.3.3->mujoco-mpc==0.1.0) (4.8.0)
Requirement already satisfied: zipp in ./venv/lib/python3.8/site-packages (from etils[epath]->mujoco>=2.3.3->mujoco-mpc==0.1.0) (3.17.0)
Building wheels for collected packages: mujoco-mpc
  Building wheel for mujoco-mpc (setup.py) ... error
  error: subprocess-exited-with-error

  × python setup.py bdist_wheel did not run successfully.
  │ exit code: 1
  ╰─> [382 lines of output]
      /home/jsun/Mo/venv/lib/python3.8/site-packages/setuptools/__init__.py:80: _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are deprecated.
      !!

              ********************************************************************************
              Requirements should be satisfied by a PEP 517 installer.
              If you are using pip, you can try `pip install --use-pep517`.
              ********************************************************************************

      !!
        dist.fetch_build_eggs(dist.setup_requires)
      running bdist_wheel
      running build
      running build_py
      running generate_proto_grpc
      touch /home/jsun/Mo/mujoco_mpc/python/build/lib.linux-x86_64-cpython-38/mujoco_mpc/proto/__init__.py
      running copy_task_assets
      copying mujoco_mpc/ui_agent_test.py -> build/lib.linux-x86_64-cpython-38/mujoco_mpc
      copying mujoco_mpc/direct.py -> build/lib.linux-x86_64-cpython-38/mujoco_mpc
      copying mujoco_mpc/agent_test.py -> build/lib.linux-x86_64-cpython-38/mujoco_mpc
      copying mujoco_mpc/filter_test.py -> build/lib.linux-x86_64-cpython-38/mujoco_mpc
      copying mujoco_mpc/mjpc_parameters.py -> build/lib.linux-x86_64-cpython-38/mujoco_mpc
      copying mujoco_mpc/filter.py -> build/lib.linux-x86_64-cpython-38/mujoco_mpc
      copying mujoco_mpc/direct_test.py -> build/lib.linux-x86_64-cpython-38/mujoco_mpc
      copying mujoco_mpc/agent.py -> build/lib.linux-x86_64-cpython-38/mujoco_mpc
      copying mujoco_mpc/__init__.py -> build/lib.linux-x86_64-cpython-38/mujoco_mpc
      running build_ext
      Configuring CMake with the following arguments:
        -DCMAKE_EXPORT_COMPILE_COMMANDS:BOOL=TRUE
        -DCMAKE_BUILD_TYPE:STRING=Debug
        -DBUILD_TESTING:BOOL=OFF
        -DMJPC_BUILD_GRPC_SERVICE:BOOL=ON
      CHECK_STARTmujoco::FindOrFetch: checking for targets in package `mujoco`
      CHECK_FAILtarget `mujoco::mujoco` not defined.
      CHECK_STARTmujoco::FindOrFetch: Using FetchContent to retrieve `mujoco`
      CHECK_STARTmujoco::FindOrFetch: checking for targets in package `qhull`
      CHECK_FAILtarget `qhull` not defined.
      CHECK_STARTmujoco::FindOrFetch: Using FetchContent to retrieve `qhull`
      --
      -- ========== qhull Build Information ==========
      -- Build Version:                             8.1-alpha1
      -- Install Prefix (CMAKE_INSTALL_PREFIX):     /usr/local
      -- Binary Directory (BIN_INSTALL_DIR):        bin
      -- Library Directory (LIB_INSTALL_DIR):       lib
      -- Include Directory (INCLUDE_INSTALL_DIR):   include
      -- Documentation Directory (DOC_INSTALL_DIR): share/doc/qhull
      -- Man Pages Directory (MAN_INSTALL_DIR):     share/man/man1
      -- CMake Directory (CMAKE_INSTALL_DIR):       lib/cmake/QHull
      -- PkgConfig Directory (PKGCONFIG_INSTALL_DIR):lib/pkgconfig
      -- Build Type (CMAKE_BUILD_TYPE):             Debug
      -- Build static libraries:                    ON
      -- Build shared library:                      OFF
      -- Use shared library for linking apps:       OFF
      -- Build tests:                                OFF
      -- To override these options, add -D{OPTION_NAME}=... to the cmake command
      --   Build the debug targets                  -DCMAKE_BUILD_TYPE=Debug
      --
      -- To build and install qhull, enter "make" and "make install"
      -- To smoketest qhull, enter "ctest"
      --
      CHECK_PASSDone
      CHECK_STARTmujoco::FindOrFetch: checking for targets in package `tinyxml2`
      CHECK_FAILtarget `tinyxml2` not defined.
      CHECK_STARTmujoco::FindOrFetch: Using FetchContent to retrieve `tinyxml2`
      CHECK_PASSDone
      CHECK_STARTmujoco::FindOrFetch: checking for targets in package `tinyobjloader`
      CHECK_FAILtarget `tinyobjloader` not defined.
      CHECK_STARTmujoco::FindOrFetch: Using FetchContent to retrieve `tinyobjloader`
      CHECK_PASSDone
      CHECK_STARTmujoco::FindOrFetch: checking for targets in package `sdflib`
      CHECK_FAILtarget `SdfLib` not defined.
      CHECK_STARTmujoco::FindOrFetch: Using FetchContent to retrieve `sdflib`
      -- GLM is a header only library, no need to build it. Set the option GLM_TEST_ENABLE with ON to build and run the test bench
      -- Build spdlog: 1.9.2
      -- Build type: Debug
      CHECK_PASSDone
      CHECK_STARTmujoco::FindOrFetch: checking for targets in package `ccd`
      CHECK_FAILtarget `ccd` not defined.
      CHECK_STARTmujoco::FindOrFetch: Using FetchContent to retrieve `ccd`
      CMake Warning (dev) at build/_deps/ccd-src/CMakeLists.txt:9 (project):
        Policy CMP0048 is not set: project() command manages VERSION variables.
        Run "cmake --help-policy CMP0048" for policy details.  Use the cmake_policy
        command to set the policy and suppress this warning.

        The following variable(s) would be set to empty:

          PROJECT_VERSION
          PROJECT_VERSION_MAJOR
          PROJECT_VERSION_MINOR
          PROJECT_VERSION_PATCH
      This warning is for project developers.  Use -Wno-dev to suppress it.

      CHECK_PASSDone
      CHECK_STARTmujoco::FindOrFetch: checking for targets in package `mujoco`
      CHECK_PASSfound
      CHECK_STARTmujoco::FindOrFetch: checking for targets in package `glfw3`
      CHECK_FAILtarget `glfw` not defined.
      CHECK_STARTmujoco::FindOrFetch: Using FetchContent to retrieve `glfw3`
      -- Using X11 for window creation
      CHECK_PASSDone
      CHECK_PASSDone
      CHECK_STARTmujoco::FindOrFetch: checking for targets in package `GTest`
      CHECK_FAILtarget `gtest` not defined.
      CHECK_STARTmujoco::FindOrFetch: Using FetchContent to retrieve `googletest`
      CHECK_PASSDone
      CHECK_STARTmujoco::FindOrFetch: checking for targets in package `absl`
      CHECK_FAILtarget `absl::core_headers` not defined.
      CHECK_STARTmujoco::FindOrFetch: Using FetchContent to retrieve `abseil-cpp`
      CHECK_PASSDone
      CHECK_STARTmujoco::FindOrFetch: checking for targets in package `glfw`
      CHECK_PASSfound
      CHECK_STARTmujoco::FindOrFetch: checking for targets in package `gRPC`
      CHECK_FAILtarget `gRPC` not defined.
      CHECK_STARTmujoco::FindOrFetch: Using FetchContent to retrieve `gRPC`
      CMake Warning at build/_deps/grpc-src/third_party/protobuf/cmake/CMakeLists.txt:3 (message):
        Calling of cmake with source directory set to "cmake" subdirectory of
        Protocol Buffers project is deprecated.  Top-level directory of Protocol
        Buffers project should be used instead.

      --
      -- <IP_ADDRESS>
      -- Checking for module 'libsystemd'
      --   No package 'libsystemd' found
      CHECK_PASSDone
      We need the following for agent/direct_protos:
      _GRPC_CPP_PLUGIN_EXECUTABLE$<TARGET_FILE:grpc_cpp_plugin>
      AGENT_SERVICE_COMPILE_OPTIONS=
      AGENT_SERVICE_COMPILE_OPTIONS=
      DIRECT_SERVICE_COMPILE_OPTIONS=
      FILTER_SERVICE_COMPILE_OPTIONS=
      -- Configuring done
      CMake Warning (dev) at build/_deps/grpc-src/third_party/cares/cares/src/lib/CMakeLists.txt:67 (ADD_LIBRARY):
        Policy CMP0063 is not set: Honor visibility properties for all target
        types.  Run "cmake --help-policy CMP0063" for policy details.  Use the
        cmake_policy command to set the policy and suppress this warning.

        Target "c-ares" of type "STATIC_LIBRARY" has the following visibility
        properties set for C:

          C_VISIBILITY_PRESET

        For compatibility CMake is not honoring them for this target.
      This warning is for project developers.  Use -Wno-dev to suppress it.

      CMake Warning (dev) at build/_deps/grpc-src/third_party/cares/cares/src/tools/CMakeLists.txt:41 (ADD_EXECUTABLE):
        Policy CMP0063 is not set: Honor visibility properties for all target
        types.  Run "cmake --help-policy CMP0063" for policy details.  Use the
        cmake_policy command to set the policy and suppress this warning.

        Target "acountry" of type "EXECUTABLE" has the following visibility
        properties set for C:

          C_VISIBILITY_PRESET

        For compatibility CMake is not honoring them for this target.
      This warning is for project developers.  Use -Wno-dev to suppress it.

      CMake Warning (dev) at build/_deps/grpc-src/third_party/cares/cares/src/tools/CMakeLists.txt:24 (ADD_EXECUTABLE):
        Policy CMP0063 is not set: Honor visibility properties for all target
        types.  Run "cmake --help-policy CMP0063" for policy details.  Use the
        cmake_policy command to set the policy and suppress this warning.

        Target "adig" of type "EXECUTABLE" has the following visibility properties
        set for C:

          C_VISIBILITY_PRESET

        For compatibility CMake is not honoring them for this target.
      This warning is for project developers.  Use -Wno-dev to suppress it.

      CMake Warning (dev) at build/_deps/grpc-src/third_party/cares/cares/src/tools/CMakeLists.txt:7 (ADD_EXECUTABLE):
        Policy CMP0063 is not set: Honor visibility properties for all target
        types.  Run "cmake --help-policy CMP0063" for policy details.  Use the
        cmake_policy command to set the policy and suppress this warning.

        Target "ahost" of type "EXECUTABLE" has the following visibility properties
        set for C:

          C_VISIBILITY_PRESET

        For compatibility CMake is not honoring them for this target.
      This warning is for project developers.  Use -Wno-dev to suppress it.

      -- Generating done
      -- Build files have been written to: /home/jsun/Mo/mujoco_mpc/build
      Building `agent_server` and `ui_agent_server` with CMake
      [  0%] Built target qhullstatic_r
      [  0%] Built target lodepng
      [  0%] Built target ccd
      [ 14%] Built target crypto
      [ 14%] Built target tinyxml2
      [ 14%] Built target tinyobjloader
      [ 15%] Built target glfw
      [ 15%] Built target absl_strerror
      [ 15%] Built target absl_spinlock_wait
      [ 15%] Built target absl_log_severity
      [ 17%] Built target absl_civil_time
      [ 17%] Built target absl_int128
      [ 17%] Built target absl_time_zone
      [ 17%] Built target absl_exponential_biased
      [ 17%] Built target absl_log_internal_nullguard
      [ 17%] Built target absl_flags_commandlineflag_internal
      [ 17%] Built target absl_random_seed_gen_exception
      [ 17%] Built target absl_random_internal_platform
      [ 17%] Built target address_sorting
      [ 19%] Built target upb
      [ 22%] Built target c-ares
      [ 26%] Built target libprotobuf
      [ 26%] Built target re2
      [ 28%] Built target ssl
      [ 28%] Built target absl_random_internal_randen_slow
      [ 31%] Built target mujoco
      [ 31%] Built target absl_raw_logging_internal
      [ 31%] Built target absl_random_internal_randen_hwaes_impl
      [ 33%] Built target platform_ui_adapter
      [ 33%] Built target absl_throw_delegate
      [ 33%] Built target absl_base
      [ 38%] Built target libprotoc
      [ 38%] Built target absl_debugging_internal
      [ 38%] Built target absl_bad_variant_access
      [ 38%] Built target absl_bad_optional_access
      [ 38%] Built target absl_cordz_functions
      [ 39%] Built target absl_crc_cpu_detect
      [ 39%] Built target absl_random_internal_randen_hwaes
      [ 39%] Built target absl_log_internal_conditions
      [ 39%] Built target protoc
      [ 39%] Built target threadpool
      [ 39%] Built target grpc_plugin_support
      [ 41%] Built target absl_malloc_internal
      [ 41%] Built target absl_string_view
      [ 41%] Built target absl_stacktrace
      [ 41%] Built target absl_strings_internal
      [ 41%] Built target absl_demangle_internal
      [ 41%] Built target absl_graphcycles_internal
      [ 41%] Built target absl_city
      [ 41%] Built target absl_low_level_hash
      [ 41%] Built target absl_crc_internal
      [ 41%] Built target absl_random_internal_randen
      [ 42%] Built target absl_strings
      [ 42%] Built target grpc_cpp_plugin
      [ 42%] Built target agent_state_proto_lib
      [ 42%] Built target absl_symbolize
      [ 42%] Built target absl_hash
      [ 42%] Built target absl_time
      [ 42%] Built target absl_str_format_internal
      [ 42%] Built target absl_flags_commandlineflag
      [ 42%] Built target absl_log_internal_proto
      [ 42%] Built target absl_random_distributions
      [ 42%] Built target absl_random_internal_seed_material
      [ 42%] Built target absl_crc32c
      [ 42%] Built target absl_kernel_timeout_internal
      [ 42%] Built target absl_examine_stack
      [ 42%] Built target absl_flags_private_handle_accessor
      [ 44%] Built target absl_flags_marshalling
      [ 44%] Built target absl_log_internal_globals
      [ 46%] Built target absl_log_entry
      [ 46%] Built target absl_log_globals
      [ 46%] Built target absl_random_internal_pool_urbg
      [ 47%] Built target absl_synchronization
      [ 47%] Built target absl_crc_cord_state
      [ 47%] Built target absl_log_internal_format
      [ 47%] Built target absl_log_sink
      [ 47%] Built target absl_random_seed_sequences
      [ 47%] Built target absl_flags_program_name
      [ 47%] Built target absl_hashtablez_sampler
      [ 47%] Built target absl_cord_internal
      [ 47%] Built target absl_cordz_handle
      [ 49%] Built target absl_raw_hash_set
      [ 49%] Built target absl_log_internal_log_sink_set
      [ 49%] Built target absl_flags_config
      [ 49%] Built target absl_cordz_info
      [ 49%] Built target absl_log_internal_message
      [ 49%] Built target absl_flags_internal
      [ 49%] Built target absl_cord
      [ 49%] Built target absl_log_internal_check_op
      [ 49%] Built target absl_status
      [ 49%] Built target absl_flags_reflection
      [ 49%] Built target absl_statusor
      [ 50%] Built target gpr
      [ 50%] Built target absl_flags
      [ 52%] Building CXX object mjpc/CMakeFiles/libmjpc.dir/agent.cc.o
      [ 52%] Building CXX object mjpc/CMakeFiles/libmjpc.dir/tasks/manipulation/common.cc.o
      [ 52%] Built target absl_flags_usage_internal
      [ 52%] Built target absl_flags_usage
      [ 52%] Building CXX object _deps/abseil-cpp-build/absl/flags/CMakeFiles/absl_flags_parse.dir/parse.cc.o
      [ 52%] Building CXX object mjpc/CMakeFiles/libmjpc.dir/tasks/manipulation/manipulation.cc.o
      [ 93%] Built target grpc
      [ 98%] Built target grpc++
      [ 98%] Running gRPC C++ protocol buffer compiler for src/proto/grpc/reflection/v1alpha/reflection.proto
      Scanning dependencies of target grpc++_reflection
      [ 98%] Building CXX object _deps/grpc-build/CMakeFiles/grpc++_reflection.dir/__/__/gens/src/proto/grpc/reflection/v1alpha/reflection.pb.cc.o
      /home/jsun/Mo/mujoco_mpc/mjpc/agent.cc: In member function ‘void mjpc::Agent::GUI(mjUI&)’:
      /home/jsun/Mo/mujoco_mpc/mjpc/agent.cc:597:65: error: no match for ‘operator=’ (operand types are ‘mjuiDef’ {aka ‘mjuiDef_’} and ‘<brace-enclosed initializer list>’)
        597 |                           DataAt(ActiveTask()->weight, i), "0 1"};
            |                                                                 ^
      In file included from /home/jsun/Mo/mujoco_mpc/build/_deps/mujoco-src/include/mujoco/mujoco.h:41,
                       from /home/jsun/Mo/mujoco_mpc/mjpc/../mjpc/agent.h:27,
                       from /home/jsun/Mo/mujoco_mpc/mjpc/agent.cc:15:
      /home/jsun/Mo/mujoco_mpc/build/_deps/mujoco-src/include/mujoco/mjui.h:312:8: note: candidate: ‘constexpr mjuiDef_& mjuiDef_::operator=(const mjuiDef_&)’
        312 | struct mjuiDef_ {                 // table passed to mjui_add()
            |        ^~~~~~~~
      /home/jsun/Mo/mujoco_mpc/build/_deps/mujoco-src/include/mujoco/mjui.h:312:8: note:   no known conversion for argument 1 from ‘<brace-enclosed initializer list>’ to ‘const mjuiDef_&’
      /home/jsun/Mo/mujoco_mpc/build/_deps/mujoco-src/include/mujoco/mjui.h:312:8: note: candidate: ‘constexpr mjuiDef_& mjuiDef_::operator=(mjuiDef_&&)’
      /home/jsun/Mo/mujoco_mpc/build/_deps/mujoco-src/include/mujoco/mjui.h:312:8: note:   no known conversion for argument 1 from ‘<brace-enclosed initializer list>’ to ‘mjuiDef_&&’
      /home/jsun/Mo/mujoco_mpc/mjpc/agent.cc:616:65: error: no match for ‘operator=’ (operand types are ‘mjuiDef’ {aka ‘mjuiDef_’} and ‘<brace-enclosed initializer list>’)
        616 |     defFeatureParameters[0] = {mjITEM_SEPARATOR, "Parameters", 1};
            |                                                                 ^
      In file included from /home/jsun/Mo/mujoco_mpc/build/_deps/mujoco-src/include/mujoco/mujoco.h:41,
                       from /home/jsun/Mo/mujoco_mpc/mjpc/../mjpc/agent.h:27,
                       from /home/jsun/Mo/mujoco_mpc/mjpc/agent.cc:15:
      /home/jsun/Mo/mujoco_mpc/build/_deps/mujoco-src/include/mujoco/mjui.h:312:8: note: candidate: ‘constexpr mjuiDef_& mjuiDef_::operator=(const mjuiDef_&)’
        312 | struct mjuiDef_ {                 // table passed to mjui_add()
            |        ^~~~~~~~
      /home/jsun/Mo/mujoco_mpc/build/_deps/mujoco-src/include/mujoco/mjui.h:312:8: note:   no known conversion for argument 1 from ‘<brace-enclosed initializer list>’ to ‘const mjuiDef_&’
      /home/jsun/Mo/mujoco_mpc/build/_deps/mujoco-src/include/mujoco/mjui.h:312:8: note: candidate: ‘constexpr mjuiDef_& mjuiDef_::operator=(mjuiDef_&&)’
      /home/jsun/Mo/mujoco_mpc/build/_deps/mujoco-src/include/mujoco/mjui.h:312:8: note:   no known conversion for argument 1 from ‘<brace-enclosed initializer list>’ to ‘mjuiDef_&&’
      /home/jsun/Mo/mujoco_mpc/mjpc/agent.cc:621:14: error: no match for ‘operator=’ (operand types are ‘mjuiDef’ {aka ‘mjuiDef_’} and ‘<brace-enclosed initializer list>’)
        621 |         "0 1"};
            |              ^
      In file included from /home/jsun/Mo/mujoco_mpc/build/_deps/mujoco-src/include/mujoco/mujoco.h:41,
                       from /home/jsun/Mo/mujoco_mpc/mjpc/../mjpc/agent.h:27,
                       from /home/jsun/Mo/mujoco_mpc/mjpc/agent.cc:15:
      /home/jsun/Mo/mujoco_mpc/build/_deps/mujoco-src/include/mujoco/mjui.h:312:8: note: candidate: ‘constexpr mjuiDef_& mjuiDef_::operator=(const mjuiDef_&)’
        312 | struct mjuiDef_ {                 // table passed to mjui_add()
            |        ^~~~~~~~
      /home/jsun/Mo/mujoco_mpc/build/_deps/mujoco-src/include/mujoco/mjui.h:312:8: note:   no known conversion for argument 1 from ‘<brace-enclosed initializer list>’ to ‘const mjuiDef_&’
      /home/jsun/Mo/mujoco_mpc/build/_deps/mujoco-src/include/mujoco/mjui.h:312:8: note: candidate: ‘constexpr mjuiDef_& mjuiDef_::operator=(mjuiDef_&&)’
      /home/jsun/Mo/mujoco_mpc/build/_deps/mujoco-src/include/mujoco/mjui.h:312:8: note:   no known conversion for argument 1 from ‘<brace-enclosed initializer list>’ to ‘mjuiDef_&&’
      [ 98%] Building CXX object mjpc/CMakeFiles/libmjpc.dir/tasks/panda/panda.cc.o
      make[3]: *** [mjpc/CMakeFiles/libmjpc.dir/build.make:76：mjpc/CMakeFiles/libmjpc.dir/agent.cc.o] 错误 1
      make[3]: *** 正在等待未完成的任务....
      [ 98%] Building CXX object _deps/grpc-build/CMakeFiles/grpc++_reflection.dir/__/__/gens/src/proto/grpc/reflection/v1alpha/reflection.grpc.pb.cc.o
      [ 98%] Linking CXX static library ../../../../lib/libabsl_flags_parse.a
      [ 98%] Built target absl_flags_parse
      [ 98%] Building CXX object _deps/grpc-build/CMakeFiles/grpc++_reflection.dir/src/cpp/ext/proto_server_reflection.cc.o
      [ 98%] Building CXX object _deps/grpc-build/CMakeFiles/grpc++_reflection.dir/src/cpp/ext/proto_server_reflection_plugin.cc.o
      make[2]: *** [CMakeFiles/Makefile2:6316：mjpc/CMakeFiles/libmjpc.dir/all] 错误 2
      make[2]: *** 正在等待未完成的任务....
      [ 98%] Linking CXX static library ../../lib/libgrpc++_reflection.a
      [ 98%] Built target grpc++_reflection
      make[1]: *** [CMakeFiles/Makefile2:6772：mjpc/grpc/CMakeFiles/agent_server.dir/rule] 错误 2
      make: *** [Makefile:1916：agent_server] 错误 2
      Traceback (most recent call last):
        File "<string>", line 2, in <module>
        File "<pip-setuptools-caller>", line 34, in <module>
        File "/home/jsun/Mo/mujoco_mpc/python/setup.py", line 256, in <module>
          setuptools.setup(
        File "/home/jsun/Mo/venv/lib/python3.8/site-packages/setuptools/__init__.py", line 103, in setup
          return distutils.core.setup(**attrs)
        File "/home/jsun/Mo/venv/lib/python3.8/site-packages/setuptools/_distutils/core.py", line 185, in setup
          return run_commands(dist)
        File "/home/jsun/Mo/venv/lib/python3.8/site-packages/setuptools/_distutils/core.py", line 201, in run_commands
          dist.run_commands()
        File "/home/jsun/Mo/venv/lib/python3.8/site-packages/setuptools/_distutils/dist.py", line 969, in run_commands
          self.run_command(cmd)
        File "/home/jsun/Mo/venv/lib/python3.8/site-packages/setuptools/dist.py", line 963, in run_command
          super().run_command(command)
        File "/home/jsun/Mo/venv/lib/python3.8/site-packages/setuptools/_distutils/dist.py", line 988, in run_command
          cmd_obj.run()
        File "/home/jsun/Mo/venv/lib/python3.8/site-packages/wheel/bdist_wheel.py", line 325, in run
          self.run_command("build")
        File "/home/jsun/Mo/venv/lib/python3.8/site-packages/setuptools/_distutils/cmd.py", line 318, in run_command
          self.distribution.run_command(command)
        File "/home/jsun/Mo/venv/lib/python3.8/site-packages/setuptools/dist.py", line 963, in run_command
          super().run_command(command)
        File "/home/jsun/Mo/venv/lib/python3.8/site-packages/setuptools/_distutils/dist.py", line 988, in run_command
          cmd_obj.run()
        File "/home/jsun/Mo/venv/lib/python3.8/site-packages/setuptools/_distutils/command/build.py", line 131, in run
          self.run_command(cmd_name)
        File "/home/jsun/Mo/venv/lib/python3.8/site-packages/setuptools/_distutils/cmd.py", line 318, in run_command
          self.distribution.run_command(command)
        File "/home/jsun/Mo/venv/lib/python3.8/site-packages/setuptools/dist.py", line 963, in run_command
          super().run_command(command)
        File "/home/jsun/Mo/venv/lib/python3.8/site-packages/setuptools/_distutils/dist.py", line 988, in run_command
          cmd_obj.run()
        File "/home/jsun/Mo/mujoco_mpc/python/setup.py", line 199, in run
          self._configure_and_build_agent_server()
        File "/home/jsun/Mo/mujoco_mpc/python/setup.py", line 240, in _configure_and_build_agent_server
          subprocess.check_call(
        File "/usr/lib/python3.8/subprocess.py", line 364, in check_call
          raise CalledProcessError(retcode, cmd)
      subprocess.CalledProcessError: Command '['cmake', '--build', '/home/jsun/Mo/mujoco_mpc/build', '--target', 'agent_server', 'ui_agent_server', '-j4', '--config', 'Debug']' returned non-zero exit status 2.
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
  ERROR: Failed building wheel for mujoco-mpc
  Running setup.py clean for mujoco-mpc
Failed to build mujoco-mpc
ERROR: Could not build wheels for mujoco-mpc, which is required to install pyproject.toml-based projects

How did you clear this error ????? I got same error. Please help..!

This is probably a problem with the compiler version. Please upgrade the version of gcc g++ to 11 or higher.


Rework Java plugin

My current task had me looking at this class and I saw some places that could use a bit of cleanup and reorganization.

Removed unused method parameters
Reduce usage of configuration name string constants and needless querying of configurations when we already had references elsewhere in class
Make some methods static where possible
Consolidate some short and related methods
Break up generic methods by moving code into relevant locations
Comment and javadoc formatting

@bot-gradle test this

OK, I've already triggered the following builds for you:

PullRequestFeedback build

OK, I've already triggered the following builds for you:

PullRequestFeedback build

@bot-gradle test and merge

The failure seems to be my fault, looking.

@bot-gradle test and merge

OK, I've already triggered a build for you.


How can I use the TimePicker from Material-ui?

This is my code
const MaterialField = createFieldClass({   'TextField': controls.text });
<MaterialField model="week.monday.in">   <TimePicker   format="24hr"   hintText="00:00"   /> </MaterialField>
Also i have performance problems with the TextField :(

Also i have performance problems with the TextField :(

What's the issue?
Also, try to map dispatching actions directly to the component first: https://davidkpiano.gitbooks.io/react-redux-form/content/custom_components.html

Closing this as it is a usage question. Let me know if dispatching actions directly works!


Swiftlint issues

Tried implementing Natalie to my project added xcode integration but storyboards.swift has swiftlint issues. Also I created Storyboards.swift on ProjectName/Common folder but can't seem to find the generated one. Any ideas?

You may want skip the generated file from the SwiftLint rules.

I create a PR #121

thanks! but is there a possibility to specify the path where Storyboards.swift should be created?

@aabanaag that another question!
Generate it, do a cp


fix type checking error

Fixes https://github.com/LostInDarkMath/pedantic-python-decorators/issues/74

Pull Request Test Coverage Report for Build 383

4 of 4 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 382:
0%

Covered Lines:
1614

Relevant Lines:
1614

💛  - Coveralls


PretiMODIT: inverse T-grid instead of Elower

I feel that the inverse T grid should be tried as one of the LBD grids instead of Elower.
tag: Precomputation+T inverse+MODIT
maybe good

less sparse than E-grid (at lower E)
can integrate q(T) and f(T,E)
similar error, according to analytic estimates, not super confident

See also #311 and #318

[ ] max Elower for given Tmax and Pmin (opagird.py)
[ ] 1st derivative correction
[ ] 2nd derivative correction
[ ] residual check
[ ] Opacity Calculator class (opacalc.py)

implemented in  #332


CSV write error Syntax error: Encountered "  "UPDATE "" at line 1, column 1.

System information:

macOS mojave 10.14.6
DBeaver version  DBeaver	<IP_ADDRESS>908191349	org.jkiss.dbeaver.core.product
Java version: java.version=12.0.2

Connection specification:

csv file
Driver name jdbc:relique:csv:/Users/steffen/Downloads
connection settings successful

Describe the problem you're observing:
CSV structure will be successful detected and displayed
After changes in the data tab and pressing the save button at the bottom it will appear an error message. Problem is independently of the structure of the csv files
Error synchronizing data with database
Ursache:
SQL-Fehler: Syntax error: Encountered "  "UPDATE "" at line 1, column 1.
Was expecting:
"SELECT" ...
Error synchronizing data with database
Ursache:
SQL-Fehler: Syntax error: Encountered "  "UPDATE "" at line 1, column 1.
Was expecting:
"SELECT" ...
Steps to reproduce, if exist:
Small csv file test.csv
"Name","Vorname"
"Lehmann","Yvonne"
"Meier","Steffen"
a simple csv connection
Include any warning/errors/backtraces from the logs

CSV driver doesn't support source CSV files modification.
As far as I know most of the CSV drivers doesn't support this.
Workaround: import CSV to some relation table (e.g. SQLite). Edit table data. Export table as CSV.


jib tasks are always executed by lunching quarkusdev task  - fixed

task for building container native image added

Changes look good. Do we need similar changes in pom.xml.ejs or is it already setup? I didn't see jib in there. Would be good to keep the two build systems in sync if we can.

Changes look good. Do we need similar changes in pom.xml.ejs or is it already setup?
No changes needed.
Would be good to keep the two build systems in sync if we can.
In maven we can build image via:
./mvnw clean package -Dquarkus.container-image.push=true
Maybe we can create profile or something else for maven to set properties automatically, but I think this is separate issue


Add a Redis binder implementation

Redis provides all message broker functionnalities (queue, topic, consumer groups, etc...), I was estonished to see that a great project like Spring Cloud Stream does not provide a default support. Its binder was deprecated  in 2016 (https://github.com/spring-cloud/spring-cloud-stream-binder-redis) is it possible to reconsider that decision and provide a default implementation?
I'll be happy to contribute if needed with some helps.
Thanks

@akuma8 Thank you for showing an initiative on this. We've been talking about it internally but never really got around until pretty much now and your issue could not have been more on time.
So, yes we are definitely interested in revisiting it. If you indeed want to contribute, then I'd suggest resurrecting https://github.com/spring-cloud/spring-cloud-stream-binder-redis and issuing PRs there and we can review/merge and get this going.
Please let us know

I think the plan is to implement Spring Integration Channel Adapters for Redis Streams first of all: https://github.com/spring-projects/spring-integration/issues/3226.
With that on board I don't think that old Redis Binder code base would make sense, although we can keep the name and project location...

@akuma8 just to clarify, what Artem is saying the required changes may be significant enough to justify a separate repo but that's fine. The overall goal is the natural evolution and history of project, so reusing the same repo is still better even if you end up completely throwing away the old code.

@olegz what would be the best approach for this?

Hi @lherrera-redislabs
I think resurrecting this implementation based on current s-c-stream 3.1.x - https://github.com/spring-cloud/spring-cloud-stream-binder-redis would probably be the best approach.
We can certainly provide guidance and work with contributors.
We can also discuss the ownership pf the project and see if redislabs are interested to completely take over as some vendors do (e.g., Solace)

Redisson team is adding this feature. Just FYI.
https://github.com/redisson/redisson/issues/3759

@kitkars, @lherrera-redislabs We managed to add Redis Stream support in Spring Integration, see those commits : https://github.com/spring-projects/spring-integration/commits?author=akuma8
The remaining task will be to reuse what we did to add the binder.


Changes are to add icons.

adding icons:
tableRowAdd
tableRowRemove
columnAdd
tableColumnRemove
fragmentExpand

Description
Some icons that were present in CoralUI3 are required by Authoring UI. This change is to add them. They are required only in greyscale mode.
Related Issue

Motivation and Context

How Has This Been Tested?
Testing has been done by adding icons in example html
Screenshots (if appropriate):

Types of changes

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

Checklist:

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ x] I have read the CONTRIBUTING document.

They are different from the ones mentioned here https://github.com/adobe/coral-spectrum/blob/master/coral-compat/data/iconMap.js#L421-L485 right ?

Change looks good, let's figure out if we are not repeating icons that @icaraps linked.

@icaraps : While icons for tableRowRemove and tableColumnRemove look similar to tableRowRemoveCenter and tableColumnRemoveCenter, there is slight difference in placement of minus sign in both icons. Please see if we can have both icons.


Howto: Add label to the edge near the middle

We won't address this beyond what is available for now.


Dungeons:  RFK and RFD may adjusting

I am noticing that the "displayed" dungeons are backwards.  I am being offered the high level dungeon when I am lower level.. and not the lower level dungeon.  Please look at them.

Came to report the same issue so 👍
Razorfen Kraul is 29-38 according to meeting stone.
Razorfen Downs is 37-46.
Razorfen Downs is offered as a search option instead of Razorfen Kraul for a level 30-something character.

Actually.. looking at src\data\dungeons.lua there's a bunch of dungeons with misscharacterized level ranges.

Fixed and phases added


Cb 8 zip code api

Please check if the PR fulfills these requirements

[x] The pull request title contains the ticket number in the title. For example [CB-1]

What kind of change does this PR introduce? (Bug fix, new feature...)
calls zipcode API using a supplied zip code

What is the current behavior?What does the code do before you made the new changes?
Currently, the application does not call the zipcode api.

What is the new behavior?
The application calls the zipcode api and returns a json of the data from localhost8080.

Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR? Run a new command?)
Add the weather api key to the .env file

Other information:

Hey Arushi. I think there are some changes in here that are not part of the zip code api

Thanks so much for the detailed feedback Miguel and Jerry! It really helped me improve my code efficiently and quickly. I've updated this branch so that there are no merge conflicts with main and have changed my hardcoded zipcode and distance values in index.js to query parameters as Jerry suggested. Great job in figuring out that there was no need for the API key for the zipcode API as well! I've removed that as well. I've attempted to remove frontend files from this pr too. Please let me know if there are further changes to be made! Thanks once more for taking the time to give me detailed comments and suggestions :)

Changed distance from kilometers to miles.


Address differences between Go API and Wasm bindings

Summary
This issue lists all known API differences between the Go API and the Wasm bindings. Some of these already have their own issues.
List of Differences

[ ] If no certificates are provided during initialization, GetConfiguration returns the default generated certificate in the Go API but no certificates in the Wasm bindings (See #513).
[x] (Fixed in https://github.com/pions/webrtc/pull/527). Some properties of PeerConnection are implemented as struct fields in the Go API but are methods in the Wasm bindings. Specifically:

CurrentLocalDescription
PendingLocalDescription
CurrentRemoteDescription
PendingRemoteDescription
SignalingState
ICEGatheringState
ConnectionState

[x] (Fixed in https://github.com/pions/webrtc/pull/524). Similarly, some properties of DataChannel are implemented as struct fields in the Go API but are methods in the Wasm bindings:

Label
Ordered
MaxPacketLifeTime
MaxRetransmits
Protocol
Negotiated
ID
ReadyState
BufferedAmount
BufferedAmountLowThreshold

[x] (Fixed in https://github.com/pions/webrtc/pull/546) In the Go API, ICE candidate gathering is synchronous but in the Wasm bindings, ICE candidate gathering happens in the background. The Go API is missing the OnICECandidate and OnNegotiationNeeded methods.
[ ] The Wasm bindings do not support certificates or credentials (See #499). This might not be addressed before the v2 release.
[x] The Wasm bindings do not support tracks, streams, or media (See #500). This might not be addressed before the v2 release.
[ ] The Wasm bindings do not support the BufferedAmount methods (introduced in https://github.com/pions/webrtc/pull/572).
[ ] The Wasm bindings can't properly subscribe to OnOpen callback when creating a DataChannel. This function might return an already opened DataChannel.

Once we have addressed this differences, it should be possible to create a (probably unexported) interface to help enforce homogeneity between the two APIs going forward. This is what @backkem suggested here.

All the subtasks have been resolved.
The API differences between WASM/Go are unfortunate, but surprisingly no user has brought it up!


Read function should not failed when in estimateGas

Read function should not failed when in estimateGas
Description
We try estimateGas() with a simple contract, but it turns out that calling read-only function would failed when the gas limit set beyond the block gas limit.
Your environment

dogechain version: v0.5.0

Steps to reproduce

Deploy contract, codes below:

// SPDX-License-Identifier: MIT
pragma solidity ^0.8.0;

contract Test13 {
    string public name; // call it with gas larger than block-gas-limit
    bool public status;

    constructor() {
        name = 'string';
    }

    function testrevert(string memory _name) public {
        name = _name;
        revert("here!");
    }

    function testrequire(string memory _name) public {
        require(status, "here!");
        name = _name;
    }
}

Set the gas limit to beyond block gas limit.
Try to call name() method.

Expected behaviour
No failure when calling read function even it set the gas limit beyond the block gas limit.
Actual behaviour
It print out something like gas limit reached in the pool.
Proposed solution
Fix it.

@abrahamcruise321 Abra, I don't think it should be marked as a bug.
view transaction does no fee, but running it would consumes CPU and memory, too. So giving the gas limit makes sense.
It wouldn't border the well-behaved users, but give strict limit to those who misbehaves.

The issue is hanging for a long time.
But it could be ignored once we switch client to DBSC.
I'll close this issue, @abrahamcruise321 @0xcb9ff9  you could reopen it if you think it necessary.


choose custom bread controller like the model one

Description:
It would be great if we can choose custom BREAD controller just like we can choose custom model

Currently this can be done by overwriting routes, however what is your ideas here?

That would be handy @hugosvent. I think it might be easy to implement.
Right now, if you need to use a custom controller you can update routes. You know that?

My Ideas are, when creating BREAD, we can choose our custom controller like
Controller Name :
App\Http\Controllers\ProductCoffeeController
btw how can I overwrite routes? Do I just put it on top of Voyager::routes()?

Under Voyager::routes() you can make overwrites like:
Route::get('/login', function () {
    return redirect('my-other-login-page');
});

Now the /admin/voyager will redirect instead.

Pinging some of the good guys for their thoughts on this.
@thedevdojo @tnylea @abdgad @akazorg @handiwijoyo @Frondor @fletch3555

Maybe something like this:
$defaultController = $namespacePrefix.'VoyagerBreadController';

foreach (DataType::all() as $dataType) {
    $breadController = $defaultController;

    // if data type has set a custom bread controller
    if ($dataType->controller) {
         $breadController = $dataType->controller;
    }

    Route::resource($dataType->slug, $breadController);
}

I like that approach @abdgad.

I like that too @abdgad.
I think this feature is a must and most users will love it.
I can create a PR later for that.

Preparing PR for this, in progress...


[Github Action] Clean up space before running backwards compatibility test

Motivation
Backwards compatibility test always failed with
Docker environment should have more than 2GB free disk space.


Compare enums with usingRecursiveComparison

Summary
Hi, I found a very confused limitations, I don't now why this happens bet let's fix it.
I have simple class structure
Example
  static enum A{
        B,
        C
    }
    @AllArgsConstructor
    static class Check{
        public A value;
    }

    public static void main(String[] args) {
        Check actual = new Check(A.B);
        Check expected = new Check(A.C);
        assertThat(actual)
            .usingRecursiveComparison()
            .ignoringAllOverriddenEquals()
            .isEqualTo(expected);

    }

This test passes. I don't understand why
Can you help with it.  I don't want remove usingRecursiveComparison and ignoringAllOverriddenEquals

I've found the solution custom comparator for enum fields
.withComparatorForType(comparator,Enum.class)

We will look into that behavior, does not feel right

@joel-costigliola  thank you for you response. Let me know if you need more information

Git a bit of time to look at it, the reason the test does not fail is that the value field in actual Check is compared recursively against expected. It turns out that enum fields are static and static fields are ignored in the recursive comparison since the point is to compare instances not classes.
I think ignoring static fields is valid, the issue here is that we try to compare enum recursively when they should be compared with equals (or == since it's the same for enum) .

@joel-costigliola Thank you.


Use newer ssl parameter in aiohttp client API

Using ssl= is the preferred way since 3.0 (aio-libs/aiohttp#2626) and ssl_context= goes away in the next version, 4.0 (aio-libs/aiohttp#3548).
This was noticed by @michaelbaamonde in https://github.com/elastic/rally/pull/1510/files/9627d291895ac90f7ae99143f2567f8d8cd1209c#r891133343.

Got the following error but no additional logs:
esrally.exceptions.SystemSetupError: Docker container [esrally-source-builder] failed with status code [1]: Error [None]

@elasticmachine run rally/it-python38 please

@elasticmachine update branch please


Bluetooth: shell: Add missing include path

When building ticker.c from the shell, it requires include access to the
Nordic HAL, so add the relevant folder to the include path.
Signed-off-by: Carles Cufi<EMAIL_ADDRESS>

@asbjornsabo can you please cherry-pick this and verify it fixes your issue?

LGTM, btw is there a reason why this configuration is not built by CI.

It is, but only with CONFIG_FLASH enabled, which also adds this include path. If you build the shell with CONFIG_FLASH=n the issue appears.

Codecov Report

Merging #14910 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master   #14910   +/-   ##
=======================================
  Coverage   52.57%   52.57%
=======================================
  Files         309      309
  Lines       45113    45113
  Branches    10445    10445
=======================================
  Hits        23718    23718
  Misses      16581    16581
  Partials     4814     4814

Continue to review full report at Codecov.

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

Too late to be of importance now - but yes, this fixes the issue.


setup.py "request>=2.28.0" should be "requests>=2.28.0"

setup.py causes an error:
No local packages or working download links found for request>=2.28.0
error: Could not find suitable distribution for Requirement.parse('request>=2.28.0')
Lines 22-23:
install_requires=[
    "request>=2.28.0"

should be:
install_requires=[
    "requests>=2.28.0"

Then it works fine:
Processing dependencies for pyubibot==0.0.4
Searching for requests==2.29.0
Best match: requests 2.29.0
Adding requests 2.29.0 to easy-install.pth file

Finished processing dependencies for pyubibot==0.0.4

Thanks @daemondriver


Travis - Builds are failing, travis sanitizer

https://travis-ci.org/rsocket/rsocket-cpp/jobs/233804282
Seems like .travis.yml should be updated?
[ 53%] Building CXX object test/CMakeFiles/basic_test.dir/basic_test.cc.o
Linking CXX executable examples
/usr/bin/ld: unrecognized option '--push-state'
/usr/bin/ld: use the --help option for usage information
collect2: error: ld returned 1 exit status
make[5]: *** [examples] Error 1
make[4]: *** [CMakeFiles/examples.dir/all] Error 2
make[3]: *** [all] Error 2
make[2]: *** [ReactiveStreams-prefix/src/ReactiveStreams-stamp/ReactiveStreams-build] Error 2
make[1]: *** [CMakeFiles/ReactiveStreams.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....

Fixed: https://github.com/rsocket/rsocket-cpp/pull/468


Update deployment.md

He guys,
my installation on an debian (generic linux) host won't start. Because the server.key file was not accessible from matchbox user.

Can you make this match the line in the same page with user:group ?
sudo chown -R matchbox:matchbox /etc/matchbox

Better now?

Its :, not .

Edited in cac0881206fd6dbf1510a4320974e51d6003ee50


PROPOSAL - Have the @ in the standup report for people who have not submitted.

Is your feature request related to a problem? Please describe.
In the standup report, the people who have not submitted the standups should have the @ against their usernames/handles.

Thanks, @sandipagarwal for the suggestion!
This makes sense as it will act as a further reminder for members who haven't submitted their standups even at the time of report generation.

This has been merged into master. INcluding this in v1.3 milestone.


Add an argument to differentiate between left and right click in ItemList.item_selected

Fix #23465
Added second argument named as 'left' to ItemList.item_selected signal which would tell if the mb is left or not(right)

Hey, idk what should I do now could anyone help me?

Run the compiled binary with --doctool to update the documentation, then amend the changes to this PR.

@YeldhamDev
thanks for the help,since you commented I tried a lot but not able to compile the binary.Whenever I try to create the executable I get an error 'internal compiler error: Segmentation fault',each time in a different file.
I have no idea what should I do now.

That's odd, I compiled a version here with your changes, and everything works fine. Could try doing a clear build following this instructions?

@YeldhamDev I am very sorry for the delay but I am still not able to fix that,thank you for help

Have you successfully compiled Godot before? Did you correctly follow the instructions in one of this pages?

@YeldhamDev I followed the instructions but every time I get  'internal compiler error: Segmentation fault',hence never compiled successfully

This is a generic error message, can you give us more context? In future, you shouldn't create pull requests for changes you hadn't tested yourself, and ensured that they build and work as intended.

Regardless of the build issue, I don't think this a good solution. I think we should either add a new signal for the left mouse button, mirroring item_rmb_selected, and leave item_selected as is. Or at the very least the new argument needs to be a mouse button index from the event instead of a boolean (what if we allow middle mouse button selection, or any mouse button selection?)
 If we go the latter route, it can read "Add a mouse button index to ItemList.item_selected", for example.

@pycbouh I am very sorry for the mistakes(I am a beginner) Thanks for your advice and explaination.I will try to implement the new signal.
Below is the screenshot of the error which occurs in different file every time.

Again

Superseded by https://github.com/godotengine/godot/pull/55381.


User unauthorized to access this resource

Copying the Pivot sample, I changed it to make a call to getBuilds() using the BuildRestClient, supplying only the project id.  Updating the extension, I refreshed and "Loading..." remained visible.  I checked the network messages in debug and saw the error.
After getting the token, the browser makes the request for the project's builds but receives a 401 response.  I have checked the request header and the correct authorization value is being set.  It is strange that getProjects() works but getBuilds() doesn't on the same extension.  I am unsure of where it gets the guid of the user from.
Referencing the same API endpoint works from a JavaScript extension.  Likewise, using the REST clients' getBuilds() in the same JavaScript extension works.
import { BuildRestClient, Build } from "azure-devops-extension-api/Build";
const builds = await getClient(BuildRestClient).getBuilds(projectId);

{"$id":"1","innerException":null,"message":"TF400813: The user '***' is not authorized to access this resource. ","typeName":"Microsoft.TeamFoundation.Framework.Server.InvalidIdentityException, Microsoft.TeamFoundation.Framework.Server","typeKey":"InvalidIdentityException","errorCode":0,"eventId":3000}

I noticed one difference which doesn't have any affect when calling the API directly from the browser: getProjects() is calling api-version=5.1-preview.4 yet getBuilds() is calling api-version=5.1-preview.5.  I've looked within azure-devops-extension-api to see where this is set but cannot find it.

This might be related to a missing scope declaration on your extension json file:
https://docs.microsoft.com/en-us/azure/devops/extend/develop/manifest?view=azure-devops#scopes
I had a similar problem, it was possible to create work items, but for getting a list of them, I had to add the following scope declaration:
"scopes": [
        "vso.work_write"
    ]

In your case, it could be vso.build
That will update your extension and it should be reviewed, instructions are on that link as well.

Once you add the new scope and publish the extension you will also have to go into Azure DevOps organization settings and click a button to grant the new permissions to the extension. It will say something like "Action Required" next to the extension.


Feature: Item, Ability stacks in Telemetry

Certain items "stack" when an Actor deals damage:

Breaking Point increases weapon damage depending on damage dealt
Bonesaw reduces a Target's armor (= defense stat) with each attack
Broken Myth increases crystal damage depending on the time damage has been dealt
Poisoned Shiv deals a mortal wound that reduces healing at the third attack
Tension Bow deals extra weapon damage (currently) every 6 seconds

There are also Abilities that stack:

Krul's auto attacks apply one lifesteal stack each
Fortress' C ability summons wolves, wolves or his B ability + auto attacks apply bleed stacks

It is currently technically difficult to infer the amount of stacks an item/abilties has at a certain point in time, and even with an algorithm that is aware of game mechanics, it could not adapt to item rebalancing or bugs, so Telemetry data should include this information.

Adding to #221

Hey @schneefux If you could provide an example of what you'd like to see the JSON event look like, we'll see what we can do.

{ "time": "2017-05-03T01:26:27+0000", "type": "itemStack", "payload": { "Team": "Left", "Actor": "*Skye*", "Item": "Broken Myth", "currentStacks" : "7" } }

{ "time": "2017-05-03T01:26:27+0000", "type": "abilityStack", "payload": { "Team": "Left", "Actor": "*Saw*", "Ability": "Saw_Perk", "currentStacks" : "12" } }

Issues:

It needs a Target for Bonesaw and Krul.
Maybe they should be *StackGain and *StackLoss events.

After #123, if damage is further split into items this could maybe fit into DealDamage, examples:

Stacks on item - Source is Breaking Point, IsAbility: 0, Stacks: 5
Stacks on ability - Source is SAW perk, IsAbility: 1, Stacks: 3
Stacks on item on target - Source is Bonesaw, IsAbility: 0, Stacks: 2
Stacks on ablilty on target - Source is Krul perk, IsAbility: 1, Stacks 3


Lenses for manipulating Low* state more abstractly

These are a preliminary set of libraries that target verifying Low* programs using more abstract, program-specific memory models.
I would suggest reading them in this order:

LowStar.Lens: Provides a generic framework for an lens-indexed effect LensST, layered on top of Low*'s Stack effect.

examples/lowstar_lenses/TestLowStarLens.Swap.fst: An example making use of LensST illustrating the benefits it can provide, at least in simple setting.

LowStar.Lens.Buffer: Provides an instance of LowStar.Lens for buffers and pointers. One main complication of this library is that it aims to overload the lens with support for both buffers and pointers. Buffers are viewed abstractly as a sequence; whereas pointers, being singleton buffers, are viewed as just a single element. This ad hoc overloading is tricky to support, and the style I used is reminiscent of the style in FStar.Integers.

LowStar.Lens.Tuple2: Provides a product construction for disjoint lenses. It also provides a layer specializing it for what I expect is the typical usage, i.e., products of atomic lenses (buffers or pointers).

I expect we will eventually have LowStar.Lens.Tuple3, 4, 5, ... etc. with perhaps some arity generic programming on top of it to provide a more uniform interface.
In any case, I'm in no hurry to merge this into master. I'm creating this PR to get some early feedback from some folks who I think may be interested, including @aseemr @tahina-pro @zoep @Chris-Hawblitzel @danelahman @mtzguido et al.

This is not really a candidate for merging anymore. It is superseded by all the work on Steel. See https://github.com/FStarLang/FStar/wiki/Abstractions-for-Reasoning-about-Memory-in-F*-Low*


feat: update render call to support all Astro versions

The app.render call deprecates the third argument in favor of an object with the routeData as a property.
See https://github.com/withastro/astro/pull/9199 for more information.

The initial v4 update actually happened as part of #3647, but this PR addresses the scenario where sst is used with older versions of Astro (ex: v3) which don't support the change in the render method argument.

Oh do we need to look into this?

@jayair, yes, @fwang brought up the idea in a thread on the Astro channel. This would preserve functionality for older versions of Astro.


Add command line application to sanitize HTML files

This can be used to test what HTML messages will look like after K-9 Mail's sanitization process.

Note to self: make sure the tests in the new module are executed by the Android CI action


Error with package dependency

Description
JSDOM is one of the dependencies of adobe/acc-js-sdk package which I am using to make connection to Adobe Campaign in a cdk project. While deploying the application using 'cdk deploy' there is a build error for /xhr-sync-worker.js which occurs at the location node_modules/jsdom/lib/jsdom/living/xhr/XMLHttpRequest-impl.js
Expected Behaviour
Application building successfully
Actual Behaviour
An error with JSDOM
ERROR	Uncaught Exception 	{
    "errorType": "Runtime.ImportModuleError",
    "errorMessage": "Error: Cannot find module './xhr-sync-worker.js'\nRequire stack:\n- /var/task/index.js\n- /var/runtime/index.mjs",
    "stack": [
        "Runtime.ImportModuleError: Error: Cannot find module './xhr-sync-worker.js'",
        "Require stack:",
        "- /var/task/index.js",
        "- /var/runtime/index.mjs",
        "    at _loadUserApp (file:///var/runtime/index.mjs:1000:17)",
        "    at async Object.UserFunction.js.module.exports.load (file:///var/runtime/index.mjs:1035:21)",
        "    at async start (file:///var/runtime/index.mjs:1200:23)",
        "    at async file:///var/runtime/index.mjs:1206:1"
    ]
}

Platform and Version
"aws-cdk-lib": "2.35.0"
"@adobe/acc-js-sdk": 1.1.17
Sample Code that illustrates the problem
const adobe = require("@adobe/acc-js-sdk");
Don't really know if the issue is with this package or the JSDOM package
Thanks in advance

Hi @jesney-johny, thanks for the report. It looks indeed to be related to jsdom. I can find the same issue in a different context here: https://stackoverflow.com/questions/44354700/meteor-app-not-finding-xhr-sync-worker-js. Maybe some of the solutions proposed here will work for you.
I'll have a look as soon as possible to make sure this works out of the box.

Thanks for the help. For the temporary fix I have updated the npm dependencies using patch-package


Remove tpn

[x] Pull request represents a single change (i.e. not fixing disparate/unrelated things in a single PR).
[x] Title summarizes what is changing.
[x] ~Has a news entry file (remember to thank yourself!).~
[x] Appropriate comments and documentation strings in the code.
[x] Has sufficient logging.
[x] Has telemetry for enhancements.
[x] Unit tests & system/integration tests are added/updated.
[x] Test plan is updated as appropriate.
[x] package-lock.json has been regenerated by running npm install (if dependencies have changed).
[x] The wiki is updated with any design decisions/details.

Codecov Report

Merging #11765 into master will decrease coverage by 0.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master   #11765      +/-   ##
==========================================
- Coverage   60.64%   60.63%   -0.02%
==========================================
  Files         628      628
  Lines       33953    33954       +1
  Branches     4782     4781       -1
==========================================
- Hits        20592    20588       -4
- Misses      12363    12367       +4
- Partials      998      999       +1

Impacted Files
Coverage Δ

src/datascience-ui/react-common/arePathsSame.ts
75.00% <0.00%> (-12.50%)
:arrow_down:

src/client/common/utils/platform.ts
64.70% <0.00%> (-11.77%)
:arrow_down:

src/client/linters/pydocstyle.ts
86.66% <0.00%> (-2.23%)
:arrow_down:

src/client/datascience/debugLocationTracker.ts
76.56% <0.00%> (-1.57%)
:arrow_down:

src/client/common/process/proc.ts
14.49% <0.00%> (-0.73%)
:arrow_down:

src/client/datascience/types.ts
100.00% <0.00%> (ø)

...datascience/interactive-common/notebookProvider.ts
48.14% <0.00%> (ø)

...active-common/intellisense/intellisenseProvider.ts
37.84% <0.00%> (+0.19%)
:arrow_up:

...ience/interactive-common/notebookServerProvider.ts
56.52% <0.00%> (+1.08%)
:arrow_up:

Continue to review full report at Codecov.

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


Add hacks for BHNT#54

:+1: top speed ;-)
perhaps @stefanmedack can add his project - or I will do a PR for this later

I was about to do a PR, but seems like somebody was faster than me :D

yes - @vog is on fire today ;-)


Fix issue with calculating content inset when scrollview is not constrained to bottom of safe area

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Running Function Tools with HTTPS Fails to Pick Process for Debug

Sometimes we need to run the function apps with HTTPS locally to test OAuth which requires an encrypted URL scheme. However, the extension is hard-coded to look for the status page with the url http://localhost:${funcPort}/admin/host/status which will fail. Since the function core tools do not support both HTTP and HTTPS simultaneously, this causes issues. It would be best if the extension either (a) detected HTTPs via the configs/command line and used it or (b) tried both. This also means supporting self-signed certificates with no chain of trust.
A workaround is to use pickProcess instead of azureFunctions.pickProcess in launch.json, manually restart the function app on changes, and choose the PID from the provided list.
https://github.com/microsoft/vscode-azurefunctions/blob/4e7b9a52b465046e53ab1fa886bf8bf349a6452d/src/commands/pickFuncProcess.ts#L87
Error received when trying with HTTPS:
Failed to detect running Functions host within "60" seconds. You may want to adjust the "azureFunctions.pickProcessTimeout" setting.

Thanks for the detailed bug report, we'll look into it. In the meantime, the workaround you described is the best one I'm aware of


Is it possible to build the resources only for specific platforms?

because I do not need windows, and in some cases I do not need to build splashscreens for iOS by using cordova@10 StoryBoards
for example:

Yes.
As stated in the README.md:

cordova-res accepts a platform for the first argument. If specified, resources are generated only for that platform: $ cordova-res ios

I use $ codova-res android to only have the android resources generated.

Closing per reference to this in the README


allow disabling hipchat

Depends on https://github.com/k8guard/k8guardlibs/pull/21. I will update the glide.yaml/lock once that is merged.

@r0fls currently if you leave the hipchat url empty it will skip hipchat, so I suggest instead of adding a new configuration, add a comment or document to clearify that if you leave hipchat configs empty, hipchat notification is disabled.
@rmb938 What do you think ?

I suggest closing this PR in once this issue is solved https://github.com/k8guard/k8guard-start-from-here/issues/45


Non-async Elasticsearch kwargs sniffer_timeout should be dropped

Hello,
After switching from classic driver to async one I kept the same init kwargs:
self.conn = AsyncElasticsearch(
    hosts=self.hosts,
    # http://elasticsearch-py.readthedocs.io/en/master/api.html?highlight=search#elasticsearch
    sniff_on_start=True,
    sniff_on_connection_fail=True,
    sniffer_timeout=60
)

This setting gives the traceback below. Removing sniffer_timeout make it work again. As the sniffing is probably handled completely different in async driver, I suggest dropping it from calling super.
 File "/usr/lib/python3.5/asyncio/futures.py", line 380, in __iter__
    yield self  # This tells Task to wait for completion.
  File "/usr/lib/python3.5/asyncio/tasks.py", line 304, in _wakeup
    future.result()
  File "/usr/lib/python3.5/asyncio/futures.py", line 293, in result
    raise self._exception
  File "/usr/lib/python3.5/asyncio/tasks.py", line 239, in _step
    result = coro.send(None)
  File "/usr/lib/python3/dist-packages/elasticsearch_async2/transport.py", line 136, in main_loop
    connection = self.get_connection()
  File "/usr/lib/python3/dist-packages/elasticsearch_async2/transport.py", line 53, in get_connection
    self.initiate_sniff()
  File "/usr/lib/python3/dist-packages/elasticsearch_async2/transport.py", line 35, in initiate_sniff
    self.sniffing_task.result()
  File "/usr/lib/python3.5/asyncio/futures.py", line 293, in result
    raise self._exception
  File "/usr/lib/python3.5/asyncio/tasks.py", line 239, in _step
    result = coro.send(None)
  File "/usr/lib/python3/dist-packages/elasticsearch_async2/transport.py", line 116, in sniff_hosts
    node_info = yield from self._get_sniff_data(initial)
  File "/usr/lib/python3/dist-packages/elasticsearch_async2/transport.py", line 86, in _get_sniff_data
    _, headers, node_info = t.result()
  File "/usr/lib/python3.5/asyncio/futures.py", line 293, in result
    raise self._exception
  File "/usr/lib/python3.5/asyncio/tasks.py", line 239, in _step
    result = coro.send(None)
  File "/usr/lib/python3/dist-packages/elasticsearch_async2/connection.py", line 55, in perform_request
    response = yield from self.session.request(method, url, data=body)
  File "/usr/lib/python3/dist-packages/aiohttp/helpers.py", line 91, in __iter__
    ret = yield from self._coro
  File "/usr/lib/python3/dist-packages/aiohttp/client.py", line 168, in _request
    raise RuntimeError('Session is closed')
RuntimeError: Session is closed

This issue has been fixed upstream in elasticsearch[async] 7.8.0. See https://github.com/elastic/elasticsearch-py-async/issues/81 for more information.


Add simple benchmark for append(contentsOf:)

Adding this simple benchmark in preparation for a handful of ABI-related refactoring changes.
There is room for improvement in these tests, as well as the original single-element appends on which they're based, in terms of:

picking the actual number of times/elements to append on a more principled basis (current values are arbitrary)
testing multiple possible types in the array:

1 swift class.
struct with 2 swift class.
enum with single trivial payload
enum with multiple non-trivial payloads
enum with multiple non-trivial payloads
enum with multiple non-trivial payloads
objective-c class
Existential Box.
Unspecialized Generic Type

all of which may have different performance characteristics.
But for now this should serve to indicate if most planned changes have significant perf impact.

@swift-ci please benchmark

Build comment file:
Optimized (O)

Appears benchmarking comparison script can't handle new benchmarks. But aside from that looks to be working correctly.
@swift-ci please smoke test and merge

@swift-ci please smoke test and merge


Printing fixes

Updated printing styling to print the month/year. Minor style adjustments. Fixed Firefox budget printing issues.

Thank you!


Integrate codacy

https://www.codacy.com/
Easy to integrate, and quite useful.. quick win

Codacy doesn't support GO integration :(
https://stackshare.io/stackups/codacy-vs-codecov
@dcaba Shall we consider Codecov as an alternative?

Its not clear for me they are an alternative, but may complement each other. As you have seen, codacy still covers style checks... while i understand codecov focuses in test coverage (that is what is currently missing in codacy). So up to you, but if you did codacy, it may be enough for now :)

I agree, for now it's ok

Related PR #9

Please, move the project to the organization we are now sharing:
https://www.codacy.com/organizations/dachad

done


C# Class-Destructor or Finalize

Expected behaviour
Handle an equivalent process in JavaScript. Not sure if possible.
Actual behaviour
Currently not supported.
Steps to reproduce the behaviour
public class App {
    public static void Main() {
        myClass text = new myClass();
    }
}

public class myClass {
  public myClass() {
    Console.WriteLine("constructor");
  }
  ~myClass() {
    Console.WriteLine("destructor");
  }
}

See Also

http://forums.bridge.net/forum/community/help/1643-class-destructor

A summary of the internal Team's discussion:
So, my summary on the issue would be:

It is not a problem to support the C# destructor syntax like ~myClass in Bridge, but:
There is no such the functionality in JavaScript engines (no finalize/destructor events), so:
It looks like the only thing we could do is to throw a "Not Supported" Exception if a ~myClass syntax detected, and:
Monitor if this functionality appears in JavaScript. If ever.

@DaniilVeriga you could just make it so that at the end of the init/main, you could just call all destructors but only when objects have destructors to stop the code being too messy.

@michaelcheers - Can you mockup a JavaScript sample of your idea? Are you proposing something like the following?
http://live.bridge.net/#e35a5fc2db6819da8deed37afd0e6e0a
public class App
{
    [Ready]
    public static void Main()
    {
        myClass text = new myClass();
        text.Destructor();
    }
}

public class myClass
{
  public myClass()
  {
    Console.Log("constructor");
  }

  //~myClass() {
  public void Destructor()
  {
    Console.Log("destructor");
  }
}

Just for demonstration purposes, I changed the C# destructor declaration with a simple Method, just so the sample would compile.

Yes, basically.

Well, I just don't see that idea working well. If you need to run something at the end of Main, then it would be best to manually call, similar to my last mockup above.
Or manually call a finalizer method when you know you're done with the object.
There are tricks for helping the js garbage collector with freeing up memory, although there's still no event that fires when that happens (if it happens at all).
I just don't know of any way to support this. It's just one of those things in C# that has no functional equivalent in JavaScript, and no way to work around, at least for now. I don't think there's anything in the ES6 or ES7 specs that would help either.
There will be memory management options in WebAssembly, which might be available and might help with this scenario, but that's certainly a ways off at this point.
I think my position at the moment would be to throw an Exception during compilation, with a good description.
If you're porting existing C# code, wrapping with a conditional build statement to exclude the finalizer definition might help.
We're open to other suggestions if anyone has any ideas.

This might help one day: github.com/tc39/proposal-weakrefs
I'm happy that you're currently throwing an exception, I think that it's the least bad of all options. The exception is a tiny bit cryptic ("Language construction DestructorDeclaration is not supported" could say something like "Finalizers are not currently supported by Bridge.NET (see github.com/bridgedotnet/Bridge/issues/994)" and it would be even better if this was identified by an Analyzer, rather than letting the Bridge compiler process start because - if I understand it right - it will fail at the first finalizer that it encounters and not alert you if you have, say, another dozen in your code base).
Also, Deck seems to show a strange error in the C# pane that I don't get when I try the code in VS - see deck.net/61a0ed93f0c819db2c00d522c4494f7d


Connections accross sections

Or ability to skip a section. Could be implemented with ghost boxes in between.
Also mentioned in #6

I've been waiting for this one but cannot work out how to do it. I am currently fudging it with the dirty hack of including an entity twice in different sections and making it a child of itself. If I remove the intermediary entity I now get an orphan entity that is not connected to anything.
Is there something I need to put in between to achieve the "passthrough" I can see in the code? Could you update the docs with an example? Thanks

This is exactly how it works. I just adds child entities in the intermediary sections to connect the curve. The 'passthrough' type enables special rendering for those. Same rules about state apply though. You can try to keep your intermediary entities and just add type: passthrough to them. This would even allow you to position them manually.
I haven't had time to properly explain this in the README.
Here is a screenshot of a weird test I have

Thanks, it is working now. I suspect it may have been a browser cache issue not picking up the new code. I found that keeping the entity, setting type: passthrough and connecting to itself as a child works best as I can control the order and colour of the branches.

Updated README

Is it just me or does the combination of child/parent state not work with passthrough?

@icefest It should. I've used it with passthrough before. Maybe there is some sort of regression. Feel free to open a bug report


Fixes #6, Golang endpoint added

I never used Go, but googled some info as I could.
Open for fixes here.

I see I should make another branch at my fork to make another PR about #29

I see I should make another branch at my fork to make another PR about #29

Indeed, you usually would. But its not a major problem 😄


run many time's then connect will be slow and many client will be reconncet

i write a testcase to stress test.
i run 1000 client to connect server once.
when i run three time's the connect will be slowly and many reconnect event.
[root@localhost]# ulimit
unlimited

i don't know why, in the v0.9 not existed this question.
now,i run about 3300 client connect the server  no response
some debug info
Thu, 12 Feb 2015 07:05:04 GMT engine.io-client:socket socket closing - telling transport to close
Thu, 12 Feb 2015 07:05:04 GMT engine.io-client:socket socket close with reason: "forced close"

//success conncet
Thu, 12 Feb 2015 08:24:25 GMT engine.io-client:socket socket receive: type "open", data "{"sid":"Rf4wpyO0iDMZS8LfAAFQ","upgrades":[],"pingInterval":25000,"pingTimeout":80000}"
Thu, 12 Feb 2015 08:24:25 GMT engine.io-client:socket socket open
Thu, 12 Feb 2015 08:24:25 GMT engine.io-client:socket flushing 1 packets in socket
Thu, 12 Feb 2015 08:24:25 GMT engine.io-client:socket socket receive: type "message", data "0"
Thu, 12 Feb 2015 08:24:25 GMT engine.io-client:socket socket receive: type "message", data "0/wsservices"Thu, 12 Feb 2015 08:24:25 GMT engine.io-client:socket socket receive: type "open", data "{"sid":"Rf4wpyO0iDMZS8LfAAFQ","upgrades":[],"pingInterval":25000,"pingTimeout":80000}"
Thu, 12 Feb 2015 08:24:25 GMT engine.io-client:socket socket open
Thu, 12 Feb 2015 08:24:25 GMT engine.io-client:socket flushing 1 packets in socket
Thu, 12 Feb 2015 08:24:25 GMT engine.io-client:socket socket receive: type "message", data "0"
Thu, 12 Feb 2015 08:24:25 GMT engine.io-client:socket socket receive: type "message", data "0/wsservices"

//error connect
Thu, 12 Feb 2015 08:24:26 GMT engine.io-client:socket writing ping packet - expecting pong within 80000ms
Thu, 12 Feb 2015 08:24:26 GMT engine.io-client:socket flushing 1 packets in socket
Thu, 12 Feb 2015 08:24:26 GMT engine.io-client:socket socket receive: type "pong", data "undefined"
Thu, 12 Feb 2015 08:24:26 GMT engine.io-client:socket writing ping packet - expecting pong within

server debug info
  socket.io:client client close with reason transport close +2ms
  socket.io:socket closing socket - reason transport close +0ms

i think the error must be socket not open.but i don't know why socket not open.
if i deploy server on pc that's will be fine,but when i depoly on the remote server and connect by internet this error must be come out.

https://xkcd.com/979/


Out of Steam - demo link

example link: http://steamcommunity.com/id/ViwuAndYouKnow/

what do we like to do with this professor?

What is the issue, exactly?

I want to write this membership like the game play place (bad english sry)

https://pasteboard.co/GNHbtZ5.png

If you want to get your bot to play a non-Steam game then you can try gamesPlayed with values suggested in https://github.com/seishun/node-steam/tree/master/lib/handlers/user#gamesplayedgamesplayed.

i can not find this page but how can i give me an example

What page can't you find? This might work, didn't test:
steamUser.gamesPlayed({
  games_played: [
    {game_id: '15444025664222527488', game_extra_info: 'whatever'}
  ]
});

bro i live you...


adding indirect CSR access option to clic registers

for issue #349, add option for using indirect CSR access method to control clic registers.  only updated text for smclic.  will update for text other priv modes later. Adding indirect CSR access could close #221 issue as well as it would provide a method to quickly enable/disable sets of interrupt enables.

@dansmathers The PR title and some of the text in this PR seems to suggest that an option is being added. Reading through the PR it however seems that this is not the case because:

The original memory mapped option seems completely removed.
No parameter for this option seems to have been introduced.

There is a statement that "A CSR accessible via one method may or may not be accessible via the other method such as memory-mapped access". This "other method" seems however not specified.
I would really prefer if the memory mapped options stays explicitly specified.
The indirect CSR access option also opens up the discussion again that was closed here: https://github.com/riscv/riscv-fast-interrupt/issues/225. For indirect CSR accesses will there now again be requirements that writes to clicintie or clicintip are evaluated immediately? I think the answer to this question should be made explicit. If the answer is 'yes' then that introduces a weird incompatibility between the two access methods.

Good question on should both indirect and memory mapped access be in this pull.  I've updated the pull title to reflect the current pull status. originally the pull just added indirect CSR access but you are correct that the current pull now replaces memory mapped access with indirect CSR access.   Hopefully we can have a good discussion on adding the memory mapped method back into the spec and how it should be, e.g. if it would be an extension or parameter or something else.
in the 20231205  fast interrupt TG minutes there was this discussion:

Issue #349 – using indirect CSRs for clicintctrl/attr/ip/ie. Hesitate to implement both indirect and CSRs and memory mapped.  choose one or the other.
AIA – one register to implement.  try to be compatible with AIA?  in terms of msi – keep that consistent.  restrict memory map for software interrupts.  just because have msis, don’t open up the whole memory map to everything.
Don’t' have to have indirect csrs.  understanding indirect csr as base.  memory map just opened up enough to do software interrupts.

for your question about issue #225:
I still see this statement under clicintip section:

The conditions for an interrupt trap to occur must be evaluated in a bounded amount of time from when an interrupt becomes, or ceases to be, pending in clicintip, but unlike the MIP/MIE CSRs, there is no requirement that clicintie or clicintip are evaluated immediately following an explicit store to clicintip or clicintie.

in the 20230926 fast interrupt TG minutes, there was this discussion:

#349 - Fixed csr so pipeline can figure out conflicts.  indirect csrs, don’t know select register.  value may not be ready yet.  so things in ind csrs can’t cause pipeline events.  so means ind csrs aren’t critical timing.  so flexible but more constrained on what they can do.  just like AIA, it is a good candidate.  so ind csrs is like a local memory map

So for this question:

For indirect CSR accesses will there now again be requirements that writes to clicintie or clicintip are evaluated immediately?

I would say the answer is no and the answer is explicit in the spec/pull already.  Do you agree?

for your question about issue https://github.com/riscv/riscv-fast-interrupt/issues/225:
I still see this statement under clicintip section:
The conditions for an interrupt trap to occur must be evaluated in a bounded amount of time from when an interrupt becomes, or ceases to be, pending in clicintip, but unlike the MIP/MIE CSRs, there is no requirement that clicintie or clicintip are evaluated immediately following an explicit store to clicintip or clicintie.

This section was added because clicintip and clicintie are/were memory mapped. If you change these to be CSR accessible then I think this should be removed and the reverse should be mandated (i.e. they must be evaluated immediately following the execution of an xRET instruction or an explicit write to these CSRs).
I think furthermore that mandating indirect CSR access just increases the interrupt latency without any real benefit over using a memory mapped strategy. The reason I think interrupt latency is negatively affected is that the mireg CSR adds state that now needs to be saved and restored (which conflicts with the goal of having an extension that improves interrupt latency).
My proposal would be to mark indirect CSR access as a possible post-v1.0 addition as opposed to a pre-v1.0 replacement of a memory mapped strategy.

Interesting point regarding the additional state. In most cases, however, I would argue that ISRs would not need to access indirect CSRs, and then no state needs to be saved.
Given the fact that indirect CSR accesses are a possibility now, I think they are the best choice for CLIC, and we want to have the best possible version of CLIC.
Of course I understand that it might be desired to maintain the memory mapped option in the interest of existing implementations, but from software point of view that would essentially lead to two kinds of CLICs (fueling any concerns regarding fragmentation).
I am travelling on Monday and will not be able to join, so please consider this as my input to the discussion.

I tried to copy comments about moving CLIC memory mapped registers to indirect CSRs to issue #349 for easier issue tracking.  Can we continue the discussion there?


Update Partners New to Use New Theme

Theme update
We're upgrading our bootstrap theme to use a bootstrap 4 template and need to upgrade the various pages in our site.
This issue is the update the app/views/partners/new.html.erb view file to use the new bootstrap theme. When submitting your PR please include a screenshot of the completed page!
If you get stuck please refer to the following pages have been done and can be used as a reference in the new theme:

app/views/requests/index.html.erb
app/views/distributions/index.html.erb
app/views/donation_sites/new.html.erb

As this is a work an progress and we can't go live until all the pages have been converted please submit your PR against the new_theme branch.

Hey there. I'm working on this!

I have a couple questions:

Should I be concerned with anything regarding setting up Bootstrap 4 itself or should I just adapt the code to include Bootstrap features?
I've given the three reference view files a peek after cloning the repository, but they seem to not be updated. Should I find the updated versions elsewhere?

@mflobo hello! Correct, please adapt the code to the newest bootstrap classes. You should be able to see the new ones in the branch (?), so there should be a diff with things like removing section w class "content-header" to a div. Let us know if you still aren't able to find a changed file to reference. Thanks for your help!


API to login user with an unique Id

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

8 of 27 (29.63%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.02%) to 24.09%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/api/api.controller.ts
5
13
38.46%

src/api/api.service.ts
0
11
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.02%

Covered Lines:
617

Relevant Lines:
2291

💛  - Coveralls


dodeltimer

https://github.com/golang/go/blob/81ea89adf38b90c3c3a8c4eed9e6c093a8634d59/src/runtime/time.go#L711
The heap manipulation in the siftupTimer() method of the dodeltimer() method also could cause our loop to skip some other timer. Can this situation cause unexpected mistakes?

Thank you for raising this issue. We don't use the issue tracker for go development questions, I suggest you ask on golang-dev, https://groups.google.com/g/golang-dev, or send a change via the https://golang.org/doc/contribute.html

Thank you for raising this issue. We don't use the issue tracker for go development questions, I suggest you ask on golang-dev, https://groups.google.com/g/golang-dev, or send a change via the https://golang.org/doc/contribute.html

Ok, thanks for your reply.

Ok, thanks for your reply.


Animation direction arrow selector is not keyboard accessible

Bug Description
The animation direction arrow selector (for e.g. fly-in effect) is not keyboard-accessible. Only the currently selected direction is reachable by tab, the other directions are not in the tab-order (probably because they’re disabled). Also, I’d expect arrow keys to be a shortcut for setting the animation direction. The widget should probably be styled as a role=“listbox” with the arrows as role=“option” to follow WCAG. Also, the arrows should have sensible labels.
Currently implemented with a radio group behind the scenes, but it’s not working as such using arrow keys (radio groups can normally be navigated using arrow keys, but we have global listeners preventing that - local listeners will work though).
It can remain a radio group as long as it’s properly announced to screen-readers as such and work as expected for such (including arrow key navigation).
Expected Behaviour

Steps to Reproduce

Screenshots

Additional Context

Plugin Version:
WordPress Version:
Operating System:
Browser:

Do not alter or remove anything below. The following sections will be managed by moderators only.
Acceptance Criteria

Implementation Brief

This is fixed with this: https://github.com/google/web-stories-wp/pull/5574

@csossi for testing - the branch is https://github.com/google/web-stories-wp/pull/5615 and also fixes this issue: https://github.com/google/web-stories-wp/issues/5613

Verified in QA


TLS 1.2 may need to be enabled for the Powershell commands to work

I had issues running the Powershell commands until I enabled TLS 1.2 with:
[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12

It would be handy if this step was mentioned in the docs,

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

ID: 0ddbf28b-7953-3357-55c6-8810d7332767
Version Independent ID: 48e60caf-3261-435b-8946-5b82b573f8a6
Content: Deploy Windows Containers on Windows Server
Content Source: virtualization/windowscontainers/deploy-containers/deploy-containers-on-server.md
Service: windows-containers
Product: windows-containers
GitHub Login: @taylorb-microsoft

Related https://github.com/MicrosoftDocs/Virtualization-Documentation/issues/1387


Auto Close doesn't work for Single / Double quote

When AUTO-CLOSE of Single, Double and brackets is turned on, if I highlight a word and then press a one of those, it will surround it as I expect.
However if what I am attempting to surround has an UNDERSCORE, then it only works for the brackets, not the single or double quote.
I'm currently on 7.0.3, windows 10 postgres db

hi @Moridin11 ,
unfortunately cannot reproduce it. could you try it against 7.0.5?

@uslss  - It appears to be resolved in 7.0.5.  Thanks!!


[api] support CORS and improve docs

#9193

support CORS for cross domain request
improve openapi docs
add a simple lint job to land build

/land


Add support for: gdk_pixbuf_new_from_data, gdk_pixbuf_new_from_bytes

FYI, you can already create a pixbuf from []byte:
pixbufLoader, _ := gdk.PixbufLoaderNew()
iconAsPixbuf, _ := pixbufLoader.WriteAndReturnPixbuf(Icon)

TY. this covers My need.

I was wondering ... don't we already have GdkPixbuf specific code inside of the Gdk package? If so, how'd we separate it without breaking code? Should we just make delegation functions?

I'm afraid it's all jumbled up in just two namespaces. Maybe we really should use some type of delegation function.

yes, we have pixbuf
https://pkg.go.dev/github.com/gotk3/gotk3/gdk?tab=doc#Pixbuf
but exactly these two methods are missing

wrote bindings for the two missing funcs.
@Bios-Marcel, @andre-hub:
we should probably split this like Gtk (as mentioned above) and make a gdk-pixbuf package (on the same level as gtk, gdk, cairo, etc.) and implement it for v0.6.0. If that's fine, I'll open a new issue with the info


Start token - sentence vs coref_chain

Hey,
I was converting now my own dataset to the indiscrim format and I noticed that although the sentence and tokens start from 1 the coref_chains starts from 0.
For example, see coref-data/preco_indiscrim
Where the first word "They" is a singltion cluster and is represented as [0, 0, 0] but is under sentence 1 token 1 ([ { "id": 1, "speaker": null, "text": "They say that sticks and stones may break your bones, but words will never hurt you.", "tokens": [ { "id": 1, "text": "They" },
Is it intential or a "bug"?

That's an interesting point and I agree that this is indeed counterintuitive.
To give some historical context: the sentence/token ids are based on the formatting in the universal dependencies format where sentences/tokens are indexed starting at 1. In universal dependencies token ids can also be of the form e.g. "1-2" for multiword expressions and "1.1" for elided words (such as dropped pronouns that are annotated for syntax but do not correspond to any surface form token).
Meanwhile, the coref_chains indices are based on the format used in conll_transform (https://github.com/boberle/corefconversion) and refer to the literally the index of the sentence or token within the list of tokens.
Probably we should make the "coref_chains" attribute more explicit e.g. something like
"coref_chains": [
    {
        "cluster_id": int,
        "mentions": [
                {
                    "start_index": int,
                    "start_token_id": int,
                    "end_index": int,
                    "end_token_id": int,
                }, ...
        ],
    }, ...
]

Or better yet have a documented Python Dataclass that represents each object.

Yap I am aware about the mismatch in the different formating (I have a code that convert my own data to 4 different ones where indiscrim is the fifth.)
I think that it worth to address this explicitly somewhere
anyhow, thanks on the quick response!


change autotools to install  header files required to build xorgxrdp into /usr

Hello guys
xorgxrdp utilizes some header files from xrdp, what do you think about changing xrdp to install  header files required to build xorgxrdp into /usr ?

Good idea.
Maybe something like /usr/local/include/xrdp/xrdp_client_info.h

jsorg71, do you remember the name of all files used by xorgxrdp ?

@itamarjp
This should be it, just one.

Solved by 1fe368c5b3fa05f287731e57d748afb4556d554f.


PR: Fix snippets completion with a single token with placeholder

Description of Changes

[ ] Wrote at least one-line docstrings (for any new functions)
[ ] Added unit test(s) covering the changes (if testable)

[ ] Included a screenshot or animation (if affecting the UI, see Licecap)

Caused by trying to get a list of a node instead of the tokens of the node
Issue(s) Resolved

Fixes #10971
Affirmation
By submitting this Pull Request or typing my (user)name below,
I affirm the Developer Certificate of Origin
with respect to all commits and content included in this PR,
and understand I am releasing the same under Spyder's MIT (Expat) license.

I certify the above statement is true and correct: dalthviz

@ccordoba12 I will check 👍

Hello @dalthviz! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file spyder/plugins/completion/languageserver/tests/conftest.py:

Line 19:1: E402 module level import not at top of file


add wrapper to serde that allows serializing iterators as sequences

addresses #571

If you prefer I'll refactor everything to Serialize by value and all the impls to impls for references.

I like it and I think RefCell<Option<I>> is fine. My only feedback is IteratorSerializer seems like the wrong name - Serializer means something else and this is not one. How about just serde::ser::Iterator?


Queue Monitor and Control

Idea:

Controlling the queue worker, running or not
Start, Stop (Gracefully, Hard) and Restart the qw

https://github.com/romanzipp/Laravel-Queue-Monitor/

Not a good idea for now


Agenda not getting disabled

Even if you added agenda={false} the agenda is still at the navigation and not being disabled

@senhai-kun - Did you get this to work? I'm having the same issue.

It's still the case
this is a bug I will address soon

@senhai-kun - Did you get this to work? I'm having the same issue.

My only work around was disabling the navigation and create a custom one by navigating through ref but if this issue will be solved then cheers!


is it right to scale microNormalLocal twice in getGGXDir?

in function 'vec3 getGGXDir()' in vratmtl_glsl microNormalLocal was scaled before get reflect dir. Then you pass this scaled microNormalLocal to 'getGGXContribution()', and in this function the microNormalLocal was scaled again to calculate BRDF.
is it right to scale this vector twice?

The generated micro normal is isotropic. The first scale, before the reflection operator, transforms the normal to the stretched anisotropic surface. Before the BRDF evaluation we apply inverse scaling to retrieve the original isotropic micro normal (notice that "*"and "/" operations are swapped). To understand these calculations, please refer to the full derivation which is available in our paper, Sections 4.2 and 5.2 - https://docs.chaos.com/display/RESEARCH/Microsurface+Transformations.


Inform user when target port is not detected

Fixes
Fixes RHTAPBUGS-140
Description
Adds message text when target port cannot be detected.
Type of change

[x] Bugfix

Screen shots / Gifs for design review

/cc @karthikjeeyar @rohitkrai03 @misjohns

@jeff-phillips-18 Consensus was to change the error to "We can't detect your target port. Check if it's correct."

/lgtm
/approve

/retest


Fix extra chars in buffer from leaking into module

*Set InputBuffer length to 1 before entering module
*Fixes extra characters from being sent to module (when menu items >9 or menuoption key that is 2 chars)
*Modules behave strangely when setting to 0

@enusbaum Changed approach -- restricted menu item to 1 character
moved logic from majorbbs.cs to initial module load to avoid duplicating existing module MenuOptionKeys with auto generated ones


LspShowImpl alternative to LspPeekImpl

Would it be possible for a LspShowImpl command be added?
There is a LspPeekImpl command but I prefer how the LspShowReferences command works as compared to the peek commands. Peek is good but showing the list in the quickfix suits my workflow better.

After posting the request I decided to have a closer look. It seems to be as simple as this:
command! -nargs=0 -bar -count LspShowImpl lsp.GotoImplementation(v:false, <q-mods>, <count>)
Is that right? Or does it need anything else?

When you can have multiple locations where a symbol is referenced or defined, then using a quickfix or location list makes sense.  The LspShowImpl command will show only one location where a symbol is implemented.  So the quickfix list will have only one entry?

Hmm. Maybe it depends on the language the LSP is for.
I'm primarily interested in Go and so I'm using gopls. In my case, the proposed LspShowImpl command shows many locations in the quickfix.

I see that we already have the "LspGotoImpl" command which provides the exact same functionality.  Can you use that command?

I see that we already have the "LspGotoImpl" command which provides the exact same functionality. Can you use that command?

Ah. I didn't spot that. I was too busy looking at the Show group of commands.
LspGotoImpl is exactly what I need. Thanks.


disallow names of generic types that are already defined

funny enough, rust actually totally allows this. But rust is smarter than we are about type resolution and properly shadows the primitive type. it seems desirable to just disallow this if possible


add overload tests and tool tests

environment variable currently named azure_ai_projects_connection_string_agents_tests -- may need to update for consistency
still TODO:

streaming tests
more tool tests
testing for tools with functions of different input parameter types

Add to the TODO list: tests for async client

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-ai-projects


Verify Email Link Not Working

The link generated by the email verification is:
http://localhost:3000/#/verify-email/Z3EZ6C1KvuXb_2GNh9X6CXTq2AqVvw_tFtgRXtSy0mE
But when I click that, nothing happens. It just takes me back to the home page. Also, I've checked that 	emails.0.verified = false. I'm not sure how to set up email verification.

Hi @adrianmc,
the # should not be present in the link. Here is where the link it configured.
Have you configured the verifyEmail route with AccountsTemplates.configureRoute?

...in case you don't want to use configureRoute, the other solution is that you set Accounts.urls.verifyEmail by your self with something like this:
Accounts.urls.verifyEmail = function(token){
  return Meteor.absoluteUrl("verify-email/" + token);
};

Ah, I can't believe I missed that. Configuring the route fixed it. My bad for not catching this earlier. Much thanks for helping me out.

I'm glad you solved it ;-)

@splendido I'm a bit confused by "...in case you don't want to use configureRoute" as you stated above. Can you please explain to a beginner what you meant by that? and how I go about using that? I have the issue as OP and having difficulty getting it working :(

@rjayako what I meant is that in case you use AccountsTemplates.configureRoute('verifyEmail') everything will be set up by AccountsTemplates.
While in case you'd like to set up the route on your own (might be for many different reasons...) by using the IR API (or the FR API) you'll have to assign Accounts.urls.verifyEmail the above functions to get things working.
I'd say in first place you'll want to use AccountsTemplates.configureRoute('verifyEmail') ;-)

I think the issue is if you are calling configuration only one the client. At least that was the issue for me.
Maybe that is unclear in the documentation? Or I missed something there.

Confirming with @mitar, I saw this issue when I mistakenly did configureRoute's on my client side router. If you primarily use a client-side routing file its easy to miss the spot in the documentation that says it needs to be defined at the common level. I think the biggest issue is that most things work when you use configureRoute on client only. Could usage of configureRoute anywhere other that at a common level be detected and throw an Error or warning?
Is it possible to catch that configureRoute is not being called at the common level and issue a warning?