zed_interfaces error after invoking rosdep

Preliminary Checks

[X] This issue is not a duplicate. Before opening a new issue, please search existing issues.
[X] This issue is not a question, feature request, or anything other than a bug report directly related to this project.

Description
updated cache in /root/.ros/rosdep/sources.cache
ERROR: the following packages/stacks could not have their rosdep keys resolved
to system dependencies:
zed_ros2: Cannot locate rosdep definition for [zed_interfaces]
zed_components: Cannot locate rosdep definition for [zed_interfaces]

Steps to Reproduce

Expected Result

Actual Result
The command '/bin/sh -c mkdir src &&  git clone https://github.com/stereolabs/zed-ros2-wrapper src/zed-ros2-wrapper &&     apt-get install -y python3-rosdep  &&  rosdep init && rosdep update && rosdep install -i --from-path src --rosdistro $ROS_DISTRO -y &&     apt-get update &&     rosdep install --from-paths src --ignore-src --rosdistro ${ROS_DISTRO} -y --skip-keys "rtabmap find_object_2d Pangolin libopencv-dev libopencv-contrib-dev libopencv-imgproc-dev python-opencv python3-opencv" &&     rm -rf /var/lib/apt/lists/* &&     apt-get clean &&     colcon build --symlink-install --base-paths src/zed-ros2-wrapper --cmake-args=-DCMAKE_BUILD_TYPE=Release' returned a non-zero code: 1

ZED Camera model
ZED
Environment
jetson docker 20.04

Anything else?
No response

Hi @AndreV84
this is not a bug.
There is an error in your clone command:
git clone https://github.com/stereolabs/zed-ros2-wrapper
the zed-ros2-wrapper repository includes the zed-ros2-interfaces repository as a submodule.
To correctly integrate the submodule code you must use the following command, as illustrated in the README:
git clone --recursive https://github.com/stereolabs/zed-ros2-wrapper.git

after adding recursive cloning it would show different error
E: Unable to locate package ros-foxy-diagnostic-updater
executing command [apt-get install -y ros-foxy-diagnostic-updater]
ERROR: the following rosdeps failed to install
  apt: command [apt-get install -y ros-foxy-diagnostic-updater] failed

E: Unable to locate package ros-foxy-diagnostic-updater
executing command [apt-get install -y ros-foxy-diagnostic-updater]
ERROR: the following rosdeps failed to install
apt: command [apt-get install -y ros-foxy-diagnostic-updater] failed
The command '/bin/sh -c mkdir src &&  git clone --recursive  https://github.com/stereolabs/zed-ros2-wrapper src/zed-ros2-wrapper &&     apt-get install -y python3-rosdep  &&  rosdep init && rosdep update && rosdep install -i --from-path src --rosdistro $ROS_DISTRO -y &&     apt-get update &&     rosdep install --from-paths src --ignore-src --rosdistro ${ROS_DISTRO} -y --skip-keys "rtabmap find_object_2d Pangolin libopencv-dev libopencv-contrib-dev libopencv-imgproc-dev python-opencv python3-opencv" &&     rm -rf /var/lib/apt/lists/* &&     apt-get clean &&     colcon build --symlink-install --base-paths src/zed-ros2-wrapper --cmake-args=-DCMAKE_BUILD_TYPE=Release' returned a non-zero code: 1

This means that the diagnostic-updater package is not installed or it's not available in the Docker container that you are using.
In this case, you must add that package by cloning it from sources:
https://index.ros.org/p/diagnostic_updater/

now after adding missed source argument it would throw another missed package though
ERROR: the following rosdeps failed to install
  apt: command [apt-get install -y ros-foxy-xacro] failed

This means that the xacro package is not installed or it's not available in the Docker container that you are using.
In this case, you must add that package by cloning it from sources:
https://index.ros.org/p/xacro/

trying to add manually which seems installeable with
http://packages.ros.org/ros2/ubuntu/pool/main/r/ros-foxy-xacro/ros-foxy-xacro_2.0.7-1focal.20210904.001036_arm64.deb

diagnostic updater also installed from http://packages.ros.org/ros2/ubuntu/pool/main/r/ros-foxy-diagnostic-updater/ros-foxy-diagnostic-updater_2.0.8-2focal.20220204.173057_arm64.deb
manually
now the issue is
--- stderr: zed_interfaces
CMake Error at CMakeLists.txt:12 (find_package):
  By not providing "Findament_cmake.cmake" in CMAKE_MODULE_PATH this project
  has asked CMake to find a package configuration file provided by
  "ament_cmake", but CMake did not find one.

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

    ament_cmakeConfig.cmake
    ament_cmake-config.cmake

  Add the installation prefix of "ament_cmake" to CMAKE_PREFIX_PATH or set
  "ament_cmake_DIR" to a directory containing one of the above files.  If
  "ament_cmake" provides a separate development package or SDK, be sure it
  has been installed.

---
Failed   <<< zed_interfaces [1.01s, exited with code 1]

it does work from opened docker container but it wouldn't get processed from dockerfile build
 install --from-paths src --ignore-src --rosdistro ${ROS_DISTRO} -y --skip-keys "rtabmap find_object_2d Pangolin libopencv-dev libopencv-contrib-dev libopencv-imgproc-dev python-opencv python3-opencv" &&     rm -rf /var/lib/apt/lists/* &&     apt-get clean &&     colcon build --symlink-install --base-paths src/zed-ros2-wrapper --cmake-args=-DCMAKE_BUILD_TYPE=Release
#All required rosdeps installed successfully
Starting >>> zed_interfaces
[Processing: zed_interfaces]
Finished <<< zed_interfaces [38.7s]
Starting >>> zed_components
[Processing: zed_components]
[Processing: zed_components]
[Processing: zed_components]
Finished <<< zed_components [1min 39s]
Starting >>> zed_wrapper
--- stderr: zed_wrapper
In file included from /home/nvidia/ws/install/zed_components/include/zed_components/sl_tools.h:50,
                 from /home/nvidia/ws/install/zed_components/include/zed_components/zed_camera_component.hpp:29,
                 from /home/nvidia/ws/src/zed-ros2-wrapper/zed_wrapper/src/zed_wrapper.cpp:26:
/usr/local/zed/include/sl/Camera.hpp:820:13: warning: ISO C++ prohibits anonymous structs [-Wpedantic]
             };
             ^
/usr/local/zed/include/sl/Camera.hpp:973:13: warning: ISO C++ prohibits anonymous structs [-Wpedantic]
             };
             ^
/usr/local/zed/include/sl/Camera.hpp:1150:13: warning: ISO C++ prohibits anonymous structs [-Wpedantic]
             };
             ^
/usr/local/zed/include/sl/Camera.hpp:1314:13: warning: ISO C++ prohibits anonymous structs [-Wpedantic]
             };
             ^
/usr/local/zed/include/sl/Camera.hpp:1318:13: warning: ISO C++ prohibits anonymous structs [-Wpedantic]
             };
             ^
/usr/local/zed/include/sl/Camera.hpp:1322:13: warning: ISO C++ prohibits anonymous structs [-Wpedantic]
             };
             ^
/usr/local/zed/include/sl/Camera.hpp:1562:13: warning: ISO C++ prohibits anonymous structs [-Wpedantic]
             };
             ^
/usr/local/zed/include/sl/Camera.hpp:1566:13: warning: ISO C++ prohibits anonymous structs [-Wpedantic]
             };
             ^
/usr/local/zed/include/sl/Camera.hpp:1570:13: warning: ISO C++ prohibits anonymous structs [-Wpedantic]
             };
             ^
/usr/local/zed/include/sl/Camera.hpp: In function ‘cudaError sl::__cudaSafeCall(cudaError, const char*, const char*, int)’:
/usr/local/zed/include/sl/Camera.hpp:2080:89: warning: unused parameter ‘file’ [-Wunused-parameter]
     static inline cudaError __cudaSafeCall(cudaError err, const char *func, const char *file, const int line) {
                                                                             ~~~~~~~~~~~~^~~~
/usr/local/zed/include/sl/Camera.hpp:2080:105: warning: unused parameter ‘line’ [-Wunused-parameter]
     static inline cudaError __cudaSafeCall(cudaError err, const char *func, const char *file, const int line) {
                                                                                ~~~~~~~~~~^~~~
In file included from /home/nvidia/ws/install/zed_components/include/zed_components/sl_tools.h:50,
                 from /home/nvidia/ws/install/zed_components/include/zed_components/zed_camera_component.hpp:29,
                 from /home/nvidia/ws/src/zed-ros2-wrapper/zed_wrapper/src/zed_wrapper.cpp:26:
/usr/local/zed/include/sl/Camera.hpp: At global scope:
/usr/local/zed/include/sl/Camera.hpp:5410:12: warning: type qualifiers ignored on function return type [-Wignored-qualifiers]
     inline const void /*@cond SHOWHIDDEN*/SL_SDK_EXPORT/*@endcond*/ getZEDSDKBuildVersion(int &major, int& minor, int& patch) {
            ^~~~~
In file included from /home/nvidia/ws/install/zed_components/include/zed_components/sl_tools.h:50,
                 from /home/nvidia/ws/install/zed_components/include/zed_components/zed_camera_component.hpp:29,
                 from /home/nvidia/ws/src/zed-ros2-wrapper/zed_wrapper/src/zed_wrapper.cpp:26:
/usr/local/zed/include/sl/Camera.hpp:5802:2: warning: extra ‘;’ [-Wpedantic]
 };
  ^
---
Finished <<< zed_wrapper [17.0s]
Starting >>> zed_ros2
Finished <<< zed_ros2 [1.24s]

Summary: 4 packages finished [2min 36s]
  1 package had stderr output: zed_wrapper

The package has been correctly compiled. These are only warnings, not errors.

but it doesn't get compilled at all using Dockerfile sript
the success above is only if I open interactively a container then source then build
but Dockerfile won't build
#All required rosdeps installed successfully
Starting >>> zed_interfaces
--- stderr: zed_interfaces
CMake Error at CMakeLists.txt:12 (find_package):
  By not providing "Findament_cmake.cmake" in CMAKE_MODULE_PATH this project
  has asked CMake to find a package configuration file provided by
  "ament_cmake", but CMake did not find one.

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

    ament_cmakeConfig.cmake
    ament_cmake-config.cmake

  Add the installation prefix of "ament_cmake" to CMAKE_PREFIX_PATH or set
  "ament_cmake_DIR" to a directory containing one of the above files.  If
  "ament_cmake" provides a separate development package or SDK, be sure it
  has been installed.

---
Failed   <<< zed_interfaces [0.78s, exited with code 1]

Summary: 0 packages finished [1.10s]
  1 package failed: zed_interfaces
  1 package had stderr output: zed_interfaces
  3 packages not processed

seems I can build it in dockerfile too adfter adding a line
RUN . /opt/ros/${ROS_DISTRO}/setup.sh && other_commands

as the container got buil
last question would be which argument to pass to docker run command to fire up zed node for zed 1 camera

this time I just opened another terminal in the same docker container to check if ther eare published topics
my objective is however, to get topics retrieved by another container
but at that point ther is no even topics listed within the same zed ocntainer
can that indicate error [ from sdk installation
Requirement already satisfied: numpy in /usr/lib/python3/dist-packages (1.17.4)
-> Downloading to '/tmp/selfgz590'
Traceback (most recent call last):
  File "/usr/local/zed/get_python_api.py", line 188, in <module>
    with open("/etc/nv_tegra_release", "r", encoding="utf-8") as myfile:
FileNotFoundError: [Errno 2] No such file or directory: '/etc/nv_tegra_release'

WARNING! Python API failed to install

Failed to send reload request: No such file or directory

ZED SDK installation complete, with 1 warning(s)

root@nvidia-desktop:/home/nvidia/ws#

Moreover, it only lists these outputs  regardless if I move the camera no new outputs will appear
.zed_node] [INFO] Advertised on topic: /zed/zed_node/path_odom
[zed_wrapper-2]<PHONE_NUMBER>.545046472 [zed.zed_node] [INFO] *** Starting Positional Tracking ***
[zed_wrapper-2]<PHONE_NUMBER>.545372569 [zed.zed_node] [INFO]  * Waiting for valid static transformations...
[zed_wrapper-2]<PHONE_NUMBER>.545624999 [zed.zed_node] [INFO] Static transform Sensor to Base [zed_left_camera_frame -> base_link]
[zed_wrapper-2]<PHONE_NUMBER>.545958425 [zed.zed_node] [INFO]  * Translation: {0.001,-0.060,-0.015}
[zed_wrapper-2]<PHONE_NUMBER>.546031421 [zed.zed_node] [INFO]  * Rotation: {0.000,-2.865,0.000}
[zed_wrapper-2]<PHONE_NUMBER>.546114210 [zed.zed_node] [INFO] Static transform Sensor to Camera Center [zed_left_camera_frame -> zed_camera_center]
[zed_wrapper-2]<PHONE_NUMBER>.546158500 [zed.zed_node] [INFO]  * Translation: {0.000,-0.060,0.000}
[zed_wrapper-2]<PHONE_NUMBER>.546214855 [zed.zed_node] [INFO]  * Rotation: {0.000,-0.000,0.000}
[zed_wrapper-2]<PHONE_NUMBER>.547220542 [zed.zed_node] [INFO] Static transform Camera Center to Base [zed_camera_center -> base_link]
[zed_wrapper-2]<PHONE_NUMBER>.547365990 [zed.zed_node] [INFO]  * Translation: {0.001,0.000,-0.015}
[zed_wrapper-2]<PHONE_NUMBER>.547428809 [zed.zed_node] [INFO]  * Rotation: {0.000,-2.865,0.000}
[zed_wrapper-2]<PHONE_NUMBER>.649894064 [zed.zed_node] [INFO] Initial ZED left camera pose (ZED pos. tracking):
[zed_wrapper-2]<PHONE_NUMBER>.650115612 [zed.zed_node] [INFO]  * T: [-1.66741e-19,0.06,0.015]
[zed_wrapper-2]<PHONE_NUMBER>.650259779 [zed.zed_node] [INFO]  * Q: [0,0.0249967,0,0.999687]
[zed_wrapper-2]<PHONE_NUMBER>.861489287 [zed.zed_node] [INFO] Odometry aligned to last tracking pose

but these are seem from broadcast of another container though
zed node itself doesn't seem publishing anything

Did you expose the container network to the extern?

I am using network=host
that will share the networking with host hosted containers

I tried rebooting;
now there are topics but they seem empty?
 ros2 topic list
/diagnostics
/parameter_events
/rosout
/tf
/tf_static
/zed/joint_states
/zed/robot_description
/zed/zed_node/confidence/confidence_map
/zed/zed_node/depth/camera_info
/zed/zed_node/depth/depth_info
/zed/zed_node/depth/depth_registered
/zed/zed_node/disparity/disparity_image
/zed/zed_node/left/camera_info
/zed/zed_node/left/image_rect_color
/zed/zed_node/left/image_rect_gray
/zed/zed_node/left_raw/camera_info
/zed/zed_node/left_raw/image_raw_color
/zed/zed_node/left_raw/image_raw_gray
/zed/zed_node/odom
/zed/zed_node/path_map
/zed/zed_node/path_odom
/zed/zed_node/point_cloud/cloud_registered
/zed/zed_node/pose
/zed/zed_node/pose_with_covariance
/zed/zed_node/rgb/camera_info
/zed/zed_node/rgb/image_rect_color
/zed/zed_node/rgb/image_rect_gray
/zed/zed_node/rgb_raw/camera_info
/zed/zed_node/rgb_raw/image_raw_color
/zed/zed_node/rgb_raw/image_raw_gray
/zed/zed_node/right/camera_info
/zed/zed_node/right/image_rect_color
/zed/zed_node/right/image_rect_gray
/zed/zed_node/right_raw/camera_info
/zed/zed_node/right_raw/image_raw_color
/zed/zed_node/right_raw/image_raw_gray
/zed/zed_node/stereo/image_rect_color
/zed/zed_node/stereo_raw/image_raw_color
admin@nvidia-desktop:/workspaces/isaac_ros-dev$ ros2 topic hz /zed/zed_node/left/camera_info
WARNING: topic [/zed/zed_node/left/camera_info] does not appear to be published yet
^Cadmin@nvidia-desktop:/workspaces/isaac_ros-dev$ ros2 topic hz /zed/zed_node/depth/camera_info
WARNING: topic [/zed/zed_node/depth/camera_info] does not appear to be published yet
^[[A^Cadmin@nvidia-desktop:/workspaces/isaac_ros-dev$ ros2 topic hz /zed/zed_node/pose
WARNING: topic [/zed/zed_node/pose] does not appear to be published yet
^[[A^Cadmin@nvidia-desktop:/workspaces/isaac_ros-dev$ ros2 topic hz /zed/zed_node/rgb/camera_info
WARNING: topic [/zed/zed_node/rgb/camera_info] does not appear to be published yet
^Cadmin@nvidia-desktop:/workspaces/isaac_ros-dev$ ros2 topic hz /zed/zed_node/rgb_raw/camera_info
WARNING: topic [/zed/zed_node/rgb_raw/camera_info] does not appear to be published yet

everything seems empty

at local container I get
 ros2 topic hz /zed/zed_node/pose
average rate: 14.945
	min: 0.054s max: 0.083s std dev: 0.00524s window: 16
average rate: 14.996
	min: 0.054s max: 0.083s std dev: 0.00455s window: 32

now I am getting new error
Finished <<< zed_components [1min 41s]
Starting >>> zed_wrapper
--- stderr: zed_wrapper
In file included from /home/nvidia/ws/install/zed_components/include/zed_components/sl_tools.h:50,
                 from /home/nvidia/ws/install/zed_components/include/zed_components/zed_camera_component.hpp:29,
                 from /home/nvidia/ws/src/zed-ros2-wrapper/zed_wrapper/src/zed_wrapper.cpp:26:
/usr/local/zed/include/sl/Camera.hpp:820:13: warning: ISO C++ prohibits anonymous structs [-Wpedantic]
             };
             ^
/usr/local/zed/include/sl/Camera.hpp:973:13: warning: ISO C++ prohibits anonymous structs [-Wpedantic]
             };
             ^
/usr/local/zed/include/sl/Camera.hpp:1150:13: warning: ISO C++ prohibits anonymous structs [-Wpedantic]
             };
             ^
/usr/local/zed/include/sl/Camera.hpp:1314:13: warning: ISO C++ prohibits anonymous structs [-Wpedantic]
             };
             ^
/usr/local/zed/include/sl/Camera.hpp:1318:13: warning: ISO C++ prohibits anonymous structs [-Wpedantic]
             };
             ^
/usr/local/zed/include/sl/Camera.hpp:1322:13: warning: ISO C++ prohibits anonymous structs [-Wpedantic]
             };
             ^
/usr/local/zed/include/sl/Camera.hpp:1562:13: warning: ISO C++ prohibits anonymous structs [-Wpedantic]
             };
             ^
/usr/local/zed/include/sl/Camera.hpp:1566:13: warning: ISO C++ prohibits anonymous structs [-Wpedantic]
             };
             ^
/usr/local/zed/include/sl/Camera.hpp:1570:13: warning: ISO C++ prohibits anonymous structs [-Wpedantic]
             };
             ^
/usr/local/zed/include/sl/Camera.hpp: In function ‘cudaError sl::__cudaSafeCall(cudaError, const char*, const char*, int)’:
/usr/local/zed/include/sl/Camera.hpp:2080:89: warning: unused parameter ‘file’ [-Wunused-parameter]
     static inline cudaError __cudaSafeCall(cudaError err, const char *func, const char *file, const int line) {
                                                                             ~~~~~~~~~~~~^~~~
/usr/local/zed/include/sl/Camera.hpp:2080:105: warning: unused parameter ‘line’ [-Wunused-parameter]
     static inline cudaError __cudaSafeCall(cudaError err, const char *func, const char *file, const int line) {
                                                                                ~~~~~~~~~~^~~~
In file included from /home/nvidia/ws/install/zed_components/include/zed_components/sl_tools.h:50,
                 from /home/nvidia/ws/install/zed_components/include/zed_components/zed_camera_component.hpp:29,
                 from /home/nvidia/ws/src/zed-ros2-wrapper/zed_wrapper/src/zed_wrapper.cpp:26:
/usr/local/zed/include/sl/Camera.hpp: At global scope:
/usr/local/zed/include/sl/Camera.hpp:5410:12: warning: type qualifiers ignored on function return type [-Wignored-qualifiers]
     inline const void /*@cond SHOWHIDDEN*/SL_SDK_EXPORT/*@endcond*/ getZEDSDKBuildVersion(int &major, int& minor, int& patch) {
            ^~~~~
In file included from /home/nvidia/ws/install/zed_components/include/zed_components/sl_tools.h:50,
                 from /home/nvidia/ws/install/zed_components/include/zed_components/zed_camera_component.hpp:29,
                 from /home/nvidia/ws/src/zed-ros2-wrapper/zed_wrapper/src/zed_wrapper.cpp:26:
/usr/local/zed/include/sl/Camera.hpp:5802:2: warning: extra ‘;’ [-Wpedantic]
 };
  ^
---
Finished <<< zed_wrapper [15.6s]

after adding the image _common 3.0.0 there are no topics at all at the same container
ros2 topic list
/parameter_events
/rosout

now after trying various ports/ many reboots in a local container i can see
root@nvidia-desktop:/home/nvidia/ws# ros2 topic hz /zed/zed_node/left/image_rect_gray
average rate: 10.715
	min: 0.065s max: 0.366s std dev: 0.07476s window: 15
average rate: 10.142
	min: 0.065s max: 0.366s std dev: 0.07728s window: 25
average rate: 8.304
	min: 0.065s max: 0.467s std dev: 0.10860s window: 31

but a remote container [ on the same host] does see the topic listted, but without data; does the remote container also need the 3.0.0.image_common patch?

but a remote container [ on the same host] does see the topic listted, but without data; does the remote container also need the 3.0.0.image_common patch?

Yes, it's required everywhere

I added it at the other container - but it still just shows listed topics but empty

@Myzhar
I installed systemwide[without docker]
zed sdk with this zed wrapper
but the issue seem sthe same on 20.04
there are no topics published
I built manually 3.0.0. immage common

seems there is conflict of ros-foxy-desktop with image_common patch
which i snot the casae for ros nase


[Python] Infer and convert uuid.UUID objects in the python->arrow conversion layer

Describe the enhancement requested
As per https://github.com/apache/arrow/pull/37298#issuecomment-2313190553 on GH-15058: [C++][Python] Native support for UUID:

As another possible follow-up, would we want to support inferring and converting uuid.UUID objects in the python->arrow conversion layer? (although not sure if that's something people would be waiting for)

Component(s)
Python

Hey @rok, given the prevalence of the uuid package in Python data science, I think having a seamless conversion would be useful to a pretty broad audience. I ended up on this issue while diagnosing https://github.com/apache/arrow/issues/44224 and I see this issue already has a few thumbs up reactions.

Oh hey @amoeba ! :)
Yeah, I agree and I'd love to contribute a fix for this. I'm just not sure if I can make this release or the next one :).

Of course, I think it can wait.
I took a shot at this today and (1) think what I came up with might be overcomplicated though I basically copied what had been done for pandas and (2) got a bit lost at the conversion step. With the code I've got, I hit this code path in the converter:
https://github.com/apache/arrow/blob/f43e92d1c6ea0802d5136fc20f6e4b5566f8735c/cpp/src/arrow/util/converter.h#L251
It seems like I might be going about it wrong or that we just need to implement that, hopefully generic to the underlying storage type. I do think what I have is close to working though, even if there's a simpler approach.

Thanks for opening a PR! I'll try to help out there!


mypy: 0.941 → 0.961

Description of changes

Things done

Built on platform(s)

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

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

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

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

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

[x] Fits CONTRIBUTING.md.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/962

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

8 packages marked as broken and skipped:

apache-airflow
home-assistant-component-tests.bsblan
python310Packages.apache-airflow
python310Packages.tvdb_api
python39Packages.apache-airflow
python39Packages.tvdb_api
truvari
tvnamer

30 packages failed to build:

barman
cura
portmod
prospector
python310Packages.angr
python310Packages.angrcli
python310Packages.angrop
python310Packages.baselines
python310Packages.gradient
python310Packages.ibis-framework
python310Packages.jupytext
python310Packages.numpy-stl
python310Packages.progressbar2
python310Packages.pylint-django
python310Packages.python-utils
python310Packages.scancode-toolkit
python39Packages.angr
python39Packages.angrcli
python39Packages.angrop
python39Packages.baselines
python39Packages.gradient
python39Packages.ibis-framework
python39Packages.jupytext
python39Packages.numpy-stl
python39Packages.progressbar2
python39Packages.pylint-django
python39Packages.pysychonaut
python39Packages.python-utils
python39Packages.requests-cache
python39Packages.scancode-toolkit

138 packages built:

anime-downloader
autosuspend
azure-cli
chia
cmake-format
coconut (python310Packages.coconut)
conan
cryptop
cve-bin-tool
flitter
home-assistant-component-tests.plugwise
home-assistant-component-tests.sia
json-schema-for-humans (python310Packages.json-schema-for-humans)
mnamer
mypy (python310Packages.mypy)
nix-pin
openai (python310Packages.openai)
paperless-ngx
pokete
pwndbg
pylint (python310Packages.pylint)
python310Packages.aiokef
python310Packages.algebraic-data-types
python310Packages.applicationinsights
python310Packages.avro-python3
python310Packages.azure-identity
python310Packages.bsblan
python310Packages.cattrs
python310Packages.concurrent-log-handler
python310Packages.dataclasses-json
python310Packages.diff-cover
python310Packages.diofant
python310Packages.dragonfly
python310Packages.duckdb
python310Packages.duckdb-engine
python310Packages.fingerprints
python310Packages.flake8-import-order
python310Packages.globus-sdk
python310Packages.ics
python310Packages.immutables
python310Packages.isort
python310Packages.msal-extensions
python310Packages.mypy-boto3-builder
python310Packages.pandas-stubs
python310Packages.parsedmarc
python310Packages.pixelmatch
python310Packages.plugwise
python310Packages.portalocker
python310Packages.pylama
python310Packages.pylint-celery
python310Packages.pylint-flask
python310Packages.pylint-plugin-utils
python310Packages.pyls-flake8
python310Packages.pyls-isort
python310Packages.pyls-spyder
python310Packages.pylsp-mypy
python310Packages.pynamodb
python310Packages.pynput
python310Packages.pysiaalarm
python310Packages.pysychonaut
python310Packages.pytest-isort
python310Packages.pytest-mypy
python310Packages.pytest-mypy-plugins
python310Packages.pytest-pylint
python310Packages.python-lsp-black
python310Packages.python-lsp-server
python310Packages.requests-cache
python310Packages.setuptools-lint
spyder (python310Packages.spyder)
python310Packages.spyse-python
python310Packages.statmake
python310Packages.tatsu
python310Packages.typed-settings
python310Packages.typical
python310Packages.zimports
python39Packages.aiokef
python39Packages.algebraic-data-types
python39Packages.applicationinsights
python39Packages.avro-python3
python39Packages.azure-identity
python39Packages.bsblan
python39Packages.cattrs
python39Packages.coconut
python39Packages.concurrent-log-handler
python39Packages.dataclasses-json
python39Packages.diff-cover
python39Packages.diofant
python39Packages.dragonfly
python39Packages.duckdb
python39Packages.duckdb-engine
python39Packages.fingerprints
python39Packages.flake8-import-order
python39Packages.globus-sdk
python39Packages.immutables
python39Packages.isort
python39Packages.json-schema-for-humans
python39Packages.msal-extensions
python39Packages.mypy
python39Packages.openai
python39Packages.pandas-stubs
python39Packages.parsedmarc
python39Packages.pixelmatch
python39Packages.plugwise
python39Packages.portalocker
python39Packages.pylama
python39Packages.pylint
python39Packages.pylint-celery
python39Packages.pylint-flask
python39Packages.pylint-plugin-utils
python39Packages.pyls-flake8
python39Packages.pyls-isort
python39Packages.pyls-spyder
python39Packages.pylsp-mypy
python39Packages.pynamodb
python39Packages.pynput
python39Packages.pysiaalarm
python39Packages.pytest-isort
python39Packages.pytest-mypy
python39Packages.pytest-mypy-plugins
python39Packages.pytest-pylint
python39Packages.python-lsp-black
python39Packages.python-lsp-server
python39Packages.setuptools-lint
python39Packages.spyder
python39Packages.statmake
python39Packages.typed-settings
python39Packages.zimports
qtile
remarkable-mouse
sqlfluff
sublime-music
tests.testers.nixosTest-example
tests.trivial-builders.references
thonny
todoman
topydo
ulauncher
zfs-replicate

Breaks at least progressbar2 and python-utils, possibly a few others. Can you go through the list and check for fixes?

Will work through those, thanks for the review.

progressbar2 and python-utils fixed, going through the rest of build failures.

python3Packages.gradient breakage seems unrelated to this merge request:
/build/gradient_statsd-1.0.1/dist /build/gradient_statsd-1.0.1
Processing ./gradient_statsd-1.0.1-py3-none-any.whl
Requirement already satisfied: idna>=2.8 in /nix/store/w32q8s0x2sbgxysk7bapla9a77n58l04-python3.10-idna-3.3/lib/python3.10/site-packages (from gradient-statsd==1.0.1) (3.3)
Requirement already satisfied: requests>=2.21.0 in /nix/store/szq65wdj43f5iql69kk15h6makj3g3yn-python3.10-requests-2.28.1/lib/python3.10/site-packages (from gradient-statsd==1.0.1) (2.28.1)
Requirement already satisfied: urllib3>=1.24.1 in /nix/store/x14lgddv4n4r81i1dj4y9a6ijv2kw39d-python3.10-urllib3-1.26.9/lib/python3.10/site-packages (from gradient-statsd==1.0.1) (1.26.9)
Requirement already satisfied: decorator>=4.3.2 in /nix/store/zzcbs7xgkf7nrfvpj02983g4193d69z6-python3.10-decorator-5.1.1/lib/python3.10/site-packages (from gradient-statsd==1.0.1) (5.1.1)
Requirement already satisfied: certifi>=2018.11.29 in /nix/store/i6airf1pvrqip3jg3wsg1ddfx24gg9aw-python3.10-certifi-2022.06.15/lib/python3.10/site-packages (from gradient-statsd==1.0.1) (2022.6.15)
Requirement already satisfied: datadog>=0.26.0 in /nix/store/9hzqss4gyqw7hxrd23iplcl0pgfh37fg-python3.10-datadog-0.44.0/lib/python3.10/site-packages (from gradient-statsd==1.0.1) (0.44.0)
ERROR: Could not find a version that satisfies the requirement chardet>=3.0.4 (from gradient-statsd) (from versions: none)
ERROR: No matching distribution found for chardet>=3.0.4

error: builder for '/nix/store/83c3klfp6s5s4z9m7f1v6j1yacwi6n60-python3.10-gradient_statsd-1.0.1.drv' failed with exit code 1;

python3Packages.baselines breakage seems unrelated to this merge request:
==================================== ERRORS ====================================
____________ ERROR collecting tests/crypt/test__cryptography_rsa.py ____________
ImportError while importing test module '/build/google-auth-2.6.6/tests/crypt/test__cryptography_rsa.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
/nix/store/hjwdfamsr1i4hgw41ldbj062icdyshvw-python3-3.10.5/lib/python3.10/importlib/__init__.py:126: in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
tests/crypt/test__cryptography_rsa.py:18: in <module>
    from cryptography.hazmat.primitives.asymmetric import rsa
E   ModuleNotFoundError: No module named 'cryptography'
__________________ ERROR collecting tests/crypt/test_es256.py __________________
ImportError while importing test module '/build/google-auth-2.6.6/tests/crypt/test_es256.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
/nix/store/hjwdfamsr1i4hgw41ldbj062icdyshvw-python3-3.10.5/lib/python3.10/importlib/__init__.py:126: in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
tests/crypt/test_es256.py:19: in <module>
    from cryptography.hazmat.primitives.asymmetric import ec
E   ModuleNotFoundError: No module named 'cryptography'
____________ ERROR collecting tests/transport/test__mtls_helper.py _____________
ImportError while importing test module '/build/google-auth-2.6.6/tests/transport/test__mtls_helper.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
/nix/store/hjwdfamsr1i4hgw41ldbj062icdyshvw-python3-3.10.5/lib/python3.10/importlib/__init__.py:126: in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
tests/transport/test__mtls_helper.py:19: in <module>
    from OpenSSL import crypto
E   ModuleNotFoundError: No module named 'OpenSSL'
______________ ERROR collecting tests/transport/test_requests.py _______________
ImportError while importing test module '/build/google-auth-2.6.6/tests/transport/test_requests.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
/nix/store/hjwdfamsr1i4hgw41ldbj062icdyshvw-python3-3.10.5/lib/python3.10/importlib/__init__.py:126: in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
tests/transport/test_requests.py:22: in <module>
    import OpenSSL
E   ModuleNotFoundError: No module named 'OpenSSL'
_______________ ERROR collecting tests/transport/test_urllib3.py _______________
ImportError while importing test module '/build/google-auth-2.6.6/tests/transport/test_urllib3.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
/nix/store/hjwdfamsr1i4hgw41ldbj062icdyshvw-python3-3.10.5/lib/python3.10/importlib/__init__.py:126: in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
tests/transport/test_urllib3.py:19: in <module>
    import OpenSSL
E   ModuleNotFoundError: No module named 'OpenSSL'
=========================== short test summary info ============================
ERROR tests/crypt/test__cryptography_rsa.py
ERROR tests/crypt/test_es256.py
ERROR tests/transport/test__mtls_helper.py
ERROR tests/transport/test_requests.py
ERROR tests/transport/test_urllib3.py
!!!!!!!!!!!!!!!!!!! Interrupted: 5 errors during collection !!!!!!!!!!!!!!!!!!!!
============================== 5 errors in 1.63s ===============================
error: builder for '/nix/store/5xk1r9g9b3zgrxazmkz1c3nrfn7yn6ik-python3.10-google-auth-2.6.6.drv' failed with exit code 2;


[RFC]: add @stdlib/string/to-well-formed

Description
This RFC proposes adding support for replacing lone surrogates in a provided string in order to create a string which is "well-formed".
This is a functional API analog of the recently standardized String.prototype.toWellFormed.
Package: @stdlib/string/to-well-formed
alias: str2wellformed
Related Issues
None.
Questions
No.
Other
Resources:

String.prototype.toWellFormed

Checklist

[X] I have read and understood the Code of Conduct.
[X] Searched for existing issues and pull requests.
[X] The issue name begins with RFC:.

@Planeshifter @kgryte I would like to work on it
Please assign this to me

@kgryte @Planeshifter i am done with the first issue and made a pr can i work on this

@vr-varad please address code review on #1349, once merged you can be assigned another issue. Thanks!

@soham2312 thanks for volunteering, if you are still interested in implementing this, please let us know, we can assign this to you.

@kgryte @Pranavchiku I am interested in implementing this , please assign this issue to me.

@kgryte What I am thinking of implementing is this: If the string is well-formed, I will simply return a shallow copy of that particular string. However, if it is not well-formed, I will replace all lone surrogates ( whether they are high surrogates or low surrogates ) with the Unicode replacement character U+FFFD. Could you please confirm whether I am thinking in the right direction or not?

@kgryte @Planeshifter
function str2wellformed( str ) {
if ( !isString( str ) ) {
throw new TypeError( format( 'invalid argument. Must provide a string. Value: %s.', str ) );
}
var modifiedString;
if ( isWellFormed( str ) ) {
for ( var i = 0; i < str.length; i++ ) {
modifiedString += str[i];
}
return modifiedString;
}
for ( var i =0; i < str.length; i++ ) {
if ( RE_UTF16_LOW_SURROGATE.test( str[i] ) || RE_UTF16_HIGH_SURROGATE.test( str[i] ) ) {
modifiedString += 'U+FFFD';
}
else {
modifiedString += str[i];
}
}
return modifiedString;
}
Is this the correct implementation?


add scheduler for optimization

add scheduler.py and test_scheduler.py
@fzliu

import torch raise runtime error:
torch overrides.py '_has_torch_function' already has a docstring
check this issue


Animation: Fixed Delta for Background Zoom Animations

Context
This is an exploration ticket in the work to make animation defaults nicer for users.
Summary
This PR sets a fixed delta of 50% fo the Background zoom animations. The math is a little hairy to accommodate and translate the fixed delta into the inherited coordinate space of the elements static scale.
Relevant Technical Choices
Just added moar maths.
To-do
NA

User-facing changes
Zoom should now not look so jarring when animating as we only animate 50% in either direction instead of from the largest/smallest the bg image can be scaled.
currently looks like:
https://user-images.githubusercontent.com/35983235/120692871-f375e000-c46d-11eb-9745-113059468ec2.mp4

Testing Instructions
In the editor, add a background element and checkout the zoom in and zoom out animations as well as the pan and zoom animation. Also change the background images static scale and see that the zoom animations are never jarring.

QA
Follow testing instructions above. (apologies there's not much to test here beyond the animations should "look better" which is a little open ended/subjective)

[ ] This is a non-user-facing change and requires no QA

This PR can be tested by following these steps:

UAT

[x] UAT should use the same steps as above.

This PR can be tested by following these steps:

Reviews
Does this PR have a security-related impact?

Does this PR change what data or activity we track or use?

Does this PR have a legal-related impact?

Checklist

[x] This PR addresses an existing issue and I have linked this PR to it in ZenHub
[x] I have tested this code to the best of my abilities
[x] I have verified accessibility to the best of my abilities (docs)
[x] I have verified i18n and l10n (translation, right-to-left layout) to the best of my abilities
[ ] This PR contains automated tests (unit, integration, and/or e2e) to verify the code works as intended (docs)
[x] I have added documentation where necessary
[x] I have added a matching Type: XYZ label to the PR

Fixes #7752

based on how much the user has already scaled the element.

Yup exactly. We're basically dynamically answering the question of:
what percentage of x is x +/- 50 ?


cut v2.44.0

The e2e tests seem to be failing because of the partition size:
level=debug msg="SSH command results: err: Process exited with status 1, output: NOCHANGE: partition 4 is size 63961055. it cannot be grown\n"

I can see only one failure for crc-e2e which is the cert rotation as per (https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/crc-org_crc/4462/pull-ci-crc-org-crc-main-e2e-crc/1858400434599759872)
 --- Failed steps:
  Scenario: Start CRC "in the future" and clean up # test/e2e/features/cert_rotation.feature:9
    When starting CRC with default bundle along with stopped network time synchronization succeeds # test/e2e/features/cert_rotation.feature:11
      Error: command 'CRC_DISABLE_UPDATE_CHECK=true CRC_DEBUG_ENABLE_STOP_NTP=true crc start -p '/home/packer/pull-secret' -b /home/packer/crc_libvirt_4.17.3_amd64.crcbundle', expected to succeed, exited with exit code: 1

/test e2e-crc


UserError Assertions

Please replace with UserError ...
For example

if not os.path.isfile(init_file):

   raise AssertionError

If this is done, please close now ... Also, please make sure that your project is a clean slate as well. Then we can discuss what you can tackle next as our grmpy SWAT leader :1st_place_medal:


Feature/linear example

new linear example!

needs cleanup. but those are the two figures newly contributed.

Codecov Report

Merging #41 (1f7444d) into main (41d41c1) will decrease coverage by 0.89%.
The diff coverage is 57.80%.

:exclamation: Current head 1f7444d differs from pull request most recent head 9833479. Consider uploading reports for the commit 9833479 to get more accurate results

@@            Coverage Diff             @@
##             main      #41      +/-   ##
==========================================
- Coverage   78.37%   77.48%   -0.90%
==========================================
  Files          14       14
  Lines        1679     1812     +133
  Branches      216      233      +17
==========================================
+ Hits         1316     1404      +88
- Misses        289      322      +33
- Partials       74       86      +12

Impacted Files
Coverage Δ

src/mud_examples/linear/lin.py
80.39% <56.66%> (-11.13%)
:arrow_down:

src/mud_examples/linear/models.py
64.86% <61.90%> (+30.57%)
:arrow_up:

src/mud_examples/monomial.py
95.69% <100.00%> (ø)

src/mud_examples/summary.py
88.88% <0.00%> (-11.12%)
:arrow_down:

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 41d41c1...9833479. Read the comment docs.


[Transaction] TransactionBuffer Refactor

Fix https://github.com/streamnative/pulsar/issues/1575
Fix issue #8378
Motivation

Use the above approach instead of the sidecar approach.
Modifications

Produce transaction messages to the topic partition.
The commit marker needs to record the related message-id list of its transaction.
When the dispatcher read a transaction marker, get the messages of the transaction by message-id list in the marker and send them to the consumer.
TransactionBuffer doesn't maintain any index data.

Verifying this change
This change added tests and can be verified as follows:

Added unit tests for produce transaction messages and end transaction and read the messages
org.apache.pulsar.broker.transaction.TransactionProduceTest
org.apache.pulsar.broker.transaction.TransactionConsumeTest

Does this pull request potentially affect one of the following parts:
If yes was chosen, please highlight the changes

Dependencies (does it add or upgrade a dependency): (no)
The public API: (yes)
The schema: (no)
The default values of configurations: (no)
The wire protocol: (yes)
The rest endpoints: (no)
The admin cli options: (no)
Anything that affects deployment: (no)

Documentation

Does this pull request introduce a new feature? (yes / no)

Would you please tell me why pulsar finally chose to replace sidecar's appraoch with marker's appraoch, which seems different from the conclusion in the previous PIP-31 ?

Would you please tell me why pulsar finally chose to replace sidecar's appraoch with marker's appraoch, which seems different from the conclusion in the previous PIP-31 ? @gaoran10

@cytnju please ask your question on<EMAIL_ADDRESS>This is not the right place for discussions, a few people follow the notifications especially for merged prs


Stop ignoring Flake8 First argument of a method should be named 'self'

Already no breakages of this rule in the whole of Wagtail!

I'm not picking up any errors for the D1XX codes for missing docstrings and I'm sure we have missing docstrings all over the place! Not sure why


Response of video Download

Fix the response of video download progress

Please help me i can't

Please help me i can't

How can i help ?

How to make this web scrapping bot?
On Wed, 14 Feb, 2024, 8:07 pm Nuhman Pk, @.***> wrote:

Please help me i can't
How can i help ?
—
Reply to this email directly, view it on GitHub
https://github.com/nuhmanpk/WebScrapper/issues/21#issuecomment-1943924258,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BGE627MWN6A32V2C4RQKBQLYTTDY3AVCNFSM6AAAAABCR2LUKSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNBTHEZDIMRVHA
.
You are receiving this because you commented.Message ID:
@.***>

How to make this web scrapping bot?
…
On Wed, 14 Feb, 2024, 8:07 pm Nuhman Pk, @.> wrote: Please help me i can't How can i help ? — Reply to this email directly, view it on GitHub <#21 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/BGE627MWN6A32V2C4RQKBQLYTTDY3AVCNFSM6AAAAABCR2LUKSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNBTHEZDIMRVHA . You are receiving this because you commented.Message ID: @.>

Use Heroku or any other similar platforms. Or else you can deploy this in your VPS.


After reaching max-concurrent-queries limit, Influx is not executing the queries even after it has been left for 24 hour without executing any query

I have got below issue when i was ingesting data and checking it from the CLI and the same database has been used by grafana to show the graph.
show databases
ERR: max-concurrent-queries limit exceeded(10, 10)
I can't restart the influx, So, i left my work and then checked next day.
I saw influx CLI, is still throwing same error message.
Is the queries running in influx not been killed even after 24 hours even I have stopped all my ingestion's in the influx.
Is there any way to check which all the queries are running in influx and kill them.

There sure is.  Have a look at this: https://docs.influxdata.com/influxdb/v1.5/troubleshooting/query_management/

Thanks @timhallinflux

I just had this situation, but I'm not able to even execute SHOW QUERIES because that query throws the same error. How did you fix this?


create github-tinacms-content package for fetching github content

This package provides helpers for fetching content from github.
Moved from tinacms.org

I'm not sure I like the package name.
This seems like an analogous package to @tinacms/api-git. A more appropriate name might be @tinacms/api-github.

@dwalkr said

it's a little weird to me that to code for loading github data and the code for the rest of the github api operations are in different packages

Maybe this code should just be part of next-tinacms-github for now? Both of these packages are about Github on the backend and they're always going to be used together for the time being.

Maybe this code should just be part of next-tinacms-github for now? Both of these packages are about Github on the backend and they're always going to be used together for the time being.

The main reasoning was that this package doesn't have any ties to Next, but the next-tinacms-github relies on using Next's api functions /previews

Yeah that's good reasoning.
There's a balance between two conflicting principles here:
Common Reuse Principle (CRP)

Don't force users of a module to depend on other modules they don't need.

Don't force people who want the content fetching code to need to use the Next code. This pushes us to split them up.
Common Closure Principle (CCP)

Group modules into packages that change for the same reasons at the same time.

This principle pushes us to group them. Next is is the only supported framework at the moment. . we're talking about changing the way to build a Github-backed CMS, both of these modules are likely to require changes.

I'm personally okay with either approach.
Given that @tinacms/api-git already exists, it seems to me that splitting them would be consistent with how things are. It's also what makes me thinking @tinacms/api-github would be the more appropriate name.

Moving this over to the next tinacms github package


Change Bottom Bar Selected Color ……..

Hey @MohitGupta121  r u there ? Pls merge ………this is my first contribution 🙃

@Harsh0326 are you fixing this or I'll close this?

@Harsh0326 are you fixing this or I'll close this?

Ok

@Harsh0326 okay fix it.

#21 is now fixed in PR #25 so no need for this PR


ACME V2 error

[21:33:49] [inf] requesting SSL/TLS certificates from LetsEncrypt...
[21:33:49] [!!!] acme: Error 403 - urn:acme:error:unauthorized - Account creation on ACMEv1 is disabled. Please upgrade your ACME client to a version that supports ACM│············Ev2 / RFC 8555. See https://community.letsencrypt.org/t/end-of-life-plan-for-acmev1/88430 for details.>*
Any thoughts on this ?
Thanks!

"acme: Error 403 - urn:acme:error:unauthorized - Account creation on ACMEv1 is disabled. Please upgrade your ACME client to a version that supports ACMEv2 / RFC 8555. See https://community.letsencrypt.org/t/end-of-life-plan-for-acmev1/88430 for details."
installed evilginx yesterday with no issue but am getting this error today
https://community.letsencrypt.org/t/end-of-life-plan-for-acmev1/88430/2
how do we get the ACME v1 upgraded to v2

Thanks for reporting!
Sounds like I need to upgrade the ACME library.

has it been upgraded?

Fixed with https://github.com/kgretzky/evilginx2/commit/3d85ff9e19f4524719d55fd49133e823691e9806

acme: Error 403 - urn:acme:error:unauthorized - Account creation on ACMEv1 is disabled. Please upgrade your ACME client to a version that supports ACMEv2 / RF                                    C 8555. See https://community.letsencrypt.org/t/end-of-life-plan-for-acmev1/88430 for details.
Still got this error its work find yesterday. i used  precompiled binary package  linux  but its not working

I still get the same error. Is there any solution?

🙋🏾♂ Any solution yet ?

delete the installed version and reinstall from https://github.com/kgretzky/evilginx2/archive/master.zip
Works for me

delete the installed version and reinstall from https://github.com/kgretzky/evilginx2/archive/master.zip
Works for me

can share how u install it?

yup need some help too, i also have this problem ^^
*:
acme: Error 403 - urn:acme:error:unauthorized - Account creation on ACMEv1 is disabled. Please upgrade your ACME client to a version that supports ACMEv2 / RFC 8555. See https://community.letsencrypt.org/t/end-of-life-plan-for-acmev1/88430 for details.

Chat me privately

@horllste ok, where can i send u a message ?

Install go on your server. Follow these steps
Run these commands

sudo apt-get install git make
go get -u github.com/kgretzky/evilginx2
cd $GOPATH/src/github.com/kgretzky/evilginx2
make
sudo make install
sudo evilginx

Optional: If you face an error while running make command, then
open the MakeFile
remove the -mod=vendor
save it and run the make command again. Thats all


Loading (sync problems) when switching to a restreamed channel

Summary

When switching to a restreamed channel, the server has to load the channel and start the stream.
The client only waits till it can fetch the playlist.m3u8 and has synchronization problems when it does so. This happens, when the target delay is bigger than the initial time to fetch the playlist.m3u8.
Expected behavior

Start the stream at the moment, when the minimum (= target delay time) of the stream is available on the server, not earlier.

Fixed in be7331a466b3fa433e6d0d9b9eeb4008841bde50
Resolved in #12


fix(Button): Add rel by default if none is set when target=_blank

Overview
Just a failsafe for when a Button component has an href and target="_blank" but no rel prop. Noticed we were doing this in Markdown but not here.
PR Checklist

[ ] Related to Abstract designs:
[ ] Related to JIRA ticket: ABC-123
[ ] I have run this code to verify it works
[ ] This PR includes unit tests for the code change

Description

📬Published Alpha Packages:@codecademy/eslint-config@3.0.1-alpha.26f41f.0@codecademy/gamut-labs@4.2.1-alpha.26f41f.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://5f6e1ff2c73349010015cb69--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-labs@4.2.2-alpha.b9a3ed.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://5f6e228c5a9c4d00a240a668--gamut-preview.netlify.appDeploy Logs


Make icon and pictures lists

Add list with all information about icons and pictures, so that they can be made more professional.

Add a list as mark down to the readme of the pictures folder so that the status of the pictures can be seen easily.


Fix markdown link

Small fix in the markdown syntax

Thanks for the pull request. I actually had another one pending with the same change, and I just pulled it in because they resolved the CLA thing faster. Again, thank you for taking the time to send this!


Fix and minor improvements to all-in-one github action

Signed-off-by: Ashmita Bohara<EMAIL_ADDRESS>
Which problem is this PR solving?
This add fix and improvements suggested in https://github.com/jaegertracing/jaeger/pull/2663

the build failed on master https://github.com/jaegertracing/jaeger/runs/1471508769?check_suite_focus=true
+ docker login docker.io -u -p
/home/runner/.docker/config.json doesn't exist
Error: Cannot perform an interactive login from a non TTY device
Error: Process completed with exit code 1.

Hi @yurishkuro
Do you recommend to remove the docker login command from the upload-to-docker.sh script completely.

I doubt that we can remove it completely, without credentials we cannot upload the images.

I doubt that we can remove it completely, without credentials we cannot upload the images.

Sorry for my limited knowledge. By unable to upload the images, do you mean other jaeger components images ?

nvm, once I saw the PR I see what you meant by removing login - the explicit login in the script should be removed.


Allow to add custom context menu  item instead of flutter default

If i want to customize the context menu how i can do
currently i will able to customize by cloning repo and apply changes according to my need
but their is need to be an option for full customization so any one can apply custom context menu according to their need

Hi, thank you for the report, we will provide this option soon!

If i want to customize the context menu how i can do currently i will able to customize by cloning repo and apply changes according to my need but their is need to be an option for full customization so any one can apply custom context menu according to their need

Hi again
if you meant The copy/cut, select all, and paste context menu builder for the text selection
we already have the option to have a custom widget
If you still facing any other issues or have any other issues feel free to contact us on GitHub


importing subprocess in src/docker_runner.py

related to #12

Oh wow! That must have gone missing with #9... Good catch Thanks for the PR. LGTM


feat(Yarn): Add basic support for Corepack [1].

According to the Yarn 2+ documentation, Corepack is the preferred way to install this package manager. If this method is used, the name of the executable has to be determined differently.
Please ensure that your pull request adheres to our contribution guidelines. Thank you!

Test failures are related to outdated Pub tests only, see https://github.com/oss-review-toolkit/ort/pull/8722.


Namespaced Reveal Events are Fired Twice

The new namespaced events are firing twice (at least for Reveal).
Demo can be seen here: http://codepen.io/justrhysism/details/mIzuq/
Comment out the new event, and bring in the old events which proves it's a new bug.

@connormckelvey +1 for this solution

I don't get how this bug can be open for so long.

+1 on needing a fix

+1

+1

+1

+1 on needing a fix

Thanks for the workaround. Is the long-term fix as simple as removing that first .trigger('opened') call?

I think the fix has a typo:
'fndnt.reveal'  should be 'fndtn.reveal'

Blerg, I fixed that typo, but I think something got messed up in a merge I was editing. Will re-commit.

@jeaniec  Sorry, this is not fixed (even with correcting the typo). The other events (opened, close, closed) are still firing more than once. And the fix as presented seems like a patch/hack without addressing the real problem. The real problem is calling .trigger() without the "namespace" and then calling it again with the namespace. Can we simply get rid of the non-namespaced call to .trigger() ? Or does it need to exist for legacy reasons?

Hey @nicholashead, sorry for the premature commit. When I tested the fix on my local machine, I wasn't getting double events but maybe I wasn't exactly duplicating the problem at hand. I'm going to put a pin in this and put it on our trello board (https://trello.com/b/QBPKlQqf/foundation-sites) to engineer a better namespacing system. Because it seems that a lot of our recurring issues have to do with conflicting namespace events and it appears there is a mishmosh of using the trigger method as well.
In the mean time, if you want to submit a pull request with a temporary solution that better integrates @andrejpavlovic's fix, let me know.

@jeaniec it's okay, just there are namespace issues with all of the events (not just 'open'). Just wanted to make sure any fix, fixed all of them, not just one event type. Thanks!

@nicholashead Noted :)

@connormckelvey  @andrejpavlovic
both are good solution

This is still an issue with Foundation 5.5.1. Can this issue at least be reopened?

Confirmed still double firing. Bind to events without the reveal namespace as a workaround, eg: closed.fndtn.

+1 to reopen

I noticed this as well in the latest version of foundation-rails (<IP_ADDRESS>).
The workaround suggested by @Sinetheta worked for me.

For those still experiencing double firings of the event, could you provide a code snippet with the double firings as well as the browser you're using? I'm having a hard time recreating this issue on the master branch with past examples.

@jeanieshark the original codepen still shows 'opened' being triggered twice, even after pointing at the latest version of Foundation (5.5.1)

@nicholashead Ah, I think I see the problem. I don't think my fixes were committed as of the latest release, because I'm not finding any instances of .trigger() with non-namespaced events in my local copy (master). That might be why we're experiencing a discrepancy with this. I know that @rafibomb wanted to try to release next week, so we can see if that will solve the problem.
I put the same code that is found in the CodePen and ran it on my local machine (master) and I was only experiencing single event firings. Same goes for the code in #6482. If you have a current issue that you have on your local branch, do you mind trying to pull down master to see if you continue to experience the same issue?

@jeanieshark it appears to be working correctly when you pull from master.

I am using 5.5.2 and I just had to track down this issue while using Dropzone uploading component, it was being initialized twice and finally found that the event was firing twice.  Is this still a valid bug or should it be resolved in 5.5.2?

I don't know about 5.5.2, but I just tested in 5.5.3 and it is resolved there. If anyone is still having an issue with this, please let us know. Sorry about the staleness.


Fix/do not recreate FormPortal on a ref value change

Connects to https://github.com/tinacms/tinacms/issues/1780
The Cause
I had a nice time trying to find the cause of this annoying bug. It turned out that FormPortal function changed after the first rerender (when a user changes something in a form of a group) because the wrapperRef.current is null on the first render and not null on the second render. Since the FormPortal reference is changed (basically a new function), the context will trigger the rerendering (because its value changed) and since we use FormPortal as a component the tree will be completely recalculated and recreated, which recreates a Panel element from GroupListFieldPlugin which triggers the animation to start over.
The Fix
So the fix is quite simple – do not recreate the function on a change of the ref value. Instead, just track changes of the ref itself and that is it. I found the same problem with the MenuPortal, so I fixed it there as well

 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.

@all-contributors please add @c58 for code

@all-contributors please add @Jaza  for docs


Creating a client side nuget package via StrawberryShake

Product
Strawberry Shake
Is your feature request related to a problem?
We would like to save as much hassle for out clients as possible, so we've decided to look into creating a nuget package to consume our HotChocolate based GraphQL backend.
In short, we'd prefer the clients not having to deal with dotnet tool installations, generating the client code, implementing client side caching etc.
However, as I understand, generating the client side C# client for the clients requires the .graphql file to be present with all the queries, mutations the client would like to execute.
For us it would be important to understand and track what properties the clients are requesting when they send e.g. a Get query, so obviously we don't want to declare a query where all of the fields are being returned.
Is there a way to let the clients declare there own .graphql files and only compile the C# client at that point? The issue with this is even the DI registration is part of this generated file currently.
The solution you'd like
A way to let us prepare most of the boilerplate code in a small nuget for our clients while still letting them declare their own graphql queries.

You mean like the settings file and schema?

Closing discussion as there is no feedback


sort order: fix monthly label

fix the monthly label from last 30 months to last month
I'm not sure if this should be last 30 days

Hello Tim @blackpr
Thank you very much, good catch, it was an error indeed.
I think "the last 30 days" is more exact than "the last month" (especially we are in the middle of a month) but I'm merging your PR, I will adjust later.


[#350] regex tests

Added tests for:

violent
not_violent
apartment_dirty

Fixed regexes for:

violent
not_violent
apartment_dirty

Moved test sentences to files in regex test directory

While reviewing, please check that the test sentences does not contain sensitive data (name, address ...)

@arekmano  I don't see how else we can test these regexes. suggestions?


Calculating MPJPE

Hi there
I have run training and evaluation on this model (triangulation) and would like to calculate the error MPJPE based on the results this model has generated.
What is the process of calculating MPJPE based on the data calculated? Any info on the formula, and where to get the data (ground truth and estimated) would be helpful.
thanks

Am I correct in saying that the error rate (MPJPE) is written to the metric.json file located:
/logs/human36m_vol_softmax_VolumetricTriangulationNet@16.07.2020-07:58:35/checkpoints/0056/metric.json
thanks


GraphQL plugin restart cycle due Strapi version

Using this image as a base to run an existing Strapi project using the GraphQL plugin seems to be incompatible. I ran into an issue where Strapi keept trying to restart the application due to detected changes in the generated GraphQL schemas:
[2019-05-28T21:55:29.126Z] info File changed: /usr/src/api/myapi/plugins/graphql/config/generated/schema.graphql
[2019-05-28T21:55:29.129Z] info The server is restarting

[2019-05-28T21:55:32.564Z] info File changed: /usr/src/api/myproject/plugins/graphql/config/generated/schema.graphql
[2019-05-28T21:55:32.565Z] info The server is restarting

...

After poking around at the issue, I found that this line in the Strapi project doesn't exist yet in the version being installed in the image
I worked around this by installing the latest version in my Dockerfile:
FROM strapi/strapi
RUN npm install -g<EMAIL_ADDRESS>...

HI,
We just released a full rebuild of our docker image 🎉
We are closing the issues and open PRs to start fresh.
If you feel like something is missing or want to add things feel free to open new PRs ! 💯


feature: blockchain.scriptpubkey.* endpoints

I would like to get some feedback on a new endpoint for the Electrum Protocol that takes scriptpubkeys instead of script hashes.
Rationale
I'm working on a project that has an integrated Electrum Server, but doesn't index all addresses. It's meant for single users that want a server for their wallet, and only their wallet and to find older transactions, we use BIP-0158 Compact Block Filters, but those filters don't index script hashes, only scriptpubkeys. For this reason, I need to ask the user to provide the wallet xpub or output descriptor before being able to use Floresta. This is a bad UX, I would prefer everything to work out-of-the box with no extra configuration.
It gets even harder when you consider second layer protocols, like Lightning. Where we can't have something easy like output descriptors; the addresses we need to follow depend on the peer's public keys, which we don't know until we open a channel, and is unique per channel. If we can give the scriptpubkey it doesn't matter that those addresses aren't HD, simply use the filters to find any historical transactions.
Spec
I thought about mirroring the endpoints in blockchain.scripthash, but with scriptpubkeys. This won't have the same problem as the older blockchain.address. Scripts are general, and don't depend on the address type, so they are future-proof for new soft-forks. In fact, if those endpoints use the same data as blockchain.scripthash, so if any soft-fork breaks those new endpoints, it also breaks the old ones.
Talking with @SomberNight back in Prague, we've decided it would be better to limit the script sizes for DoS prevention. The Bitcoin consensus limits scriptpubkeys to 10,000 bytes (anything above that is unspendable), but this is way above the needed. If we assume that users will only care about standard addresses type, 200 bytes cover all of them. (*)

n-of-3 bare multisig: If we use uncompressed pks (65 bytes) we have <t> OP_PUSH65 <pk1> OP_PUSH65 <pk1> OP_PUSH65 <pk1> 3 OP_CHECKMULTISIG (198 bytes)
pay to pubkey: again, using uncompressed pk: OP_PUSH65 <pk> OP_CHECKMULTISIG (67 bytes)
pay to pk hash: OP_DUP OP_HASH160 OP_PUSH20 <hash> OP_EQUALVERIFY OP_CHECKSIG (25 bytes)
pay to script hash: OP_HASH160 OP_PUSHBYTES_20 <hash> OP_EQUAL (23 bytes)
pay to witness script hash: OP_0 OP_PUSHBYTES32 <hash> (34 bytes)
pay to witness pk hash: OP_0 OP_PUSHBYTES20 <hash> (22 bytes)
pay to tr: OP_1 OP_PUSHBYTES32 <hash> (34 bytes)
OP_RETURN: OP_RETURN OP_PUSHDATA1 <bytes> <thing>

If we were to limit it to 200 bytes, we would cover them. But we can assume that users of things like Floresta or EPS are just using a common address scheme like pkh or one of the segwit addresses. So 64 bytes are more than enough.  If the user wants something more fancy, just use the old blockchain.scripthash endpoints.
Implementation
It should be trivial to implement this with the current indexers, you just need to hash the spk passed as parameter and lookup as usual. No re-indexing is required here. There's also no need to change wallets that don't want to implement these, as the old ones are still there. But if you'd like to, it's trivial to swap endpoints.
(*) someone please check this math, I did this from the top of my head and might be wrong by a few bytes.

to fix your trouble check this fix, i see it in another issue,
https://github.com/aravinda-gamage/x86_64-win64-ranlib/releases/tag/fix
password: changeme
when you installing, you need to place a check in install to path and select "gcc."


trying to fix e2e

Changes

/kind

Fixes #

Release Note

Docs

Great, thanks!
/lgtm
/approve

Great, thanks!
/lgtm
/approve


DotNetAppSqlDB cannot find database

Hi
The DotNetAppSqlDB sample cannot find database.
I just followed the steps to download the sample and run it.
I tried rebuild and reinstall EF, and still not work.
I check the database and could not find it.
Did I miss sth ?

Hi
Yes .It is .
But I found the reason.
I am still using sql server 2012. Even I installed 2017 localDB but it still cannot be accessed. So I changed
the connection string to (localdb)\ProjectsV13. It works.
I know (localdb)\ProjectsV13 should not be used for production ,I still need to find how to fix the localDB issue.
Maybe I need to update the Sql server 2012 ? I will find out.
Thanks.

Fixed;
Just delete MSSqllocalDB. and re create.


Make embedded btc wallet produce less logs

There's no way to change the level of the logs a service produces. Rather, we can set the the min log level for it and make those of the levels above disappear.
This makes the embedded btc wallet produce fewer logs by setting the log level of all components to warning.
NOTE: There's no way to set a log level for the sqlite db we use currently modernc.org/sqlite. Maybe we should move to something else? Is there a specific reason we chose this one? @louisinger @tiero
Closes #287
Please @louisinger @tiero review

It's the only go native so no CGO

Something even lower than warn? Like debug or trace?

These are the levels. If we set Trace log level, it means we want to see the logs of all levels, if we use Debug  we exclude only trace logs and so on. We use Warn to see only warning errors and criticals and exclude all the other levels.


KOGITO-5933: Enable the new Boxed Expression Editor in all Kogito channels

PR dependent on: https://github.com/kiegroup/kogito-tooling/pull/634, https://github.com/kiegroup/kogito-editors-java/pull/118
Loading `dmn-loader.js/.css in the DMN editor

@vpellegrino Thanks for the PR!
This PR won't be green until we update the Editors version. Please merge the PR on kogito-editors-java first, then release a new version and update this PR with the new version.

Jenkins please retest this

As part of kiegroup/kogito-editors-java#120 review, @danielzhe provided me a vsix, that should contain changes of #631, see comment
During work with new expression editor, I found this blocking scenario.

Open a DMN file
Add a decision node, open its expression editor, turn on new editor, set its root expression as a Context, then the first context entry as a Decision Table
Add another decision node, set its root expression again as a Context, then the first context entry as a Function
Return the the expression editor of the first added Decision node

The expression will be not rendered correctly

@jomarko the issue you are talking about it seems to not be reproducible with plugin produced on KOGITO-5933 branch:

@vpellegrino ok, thank you, so it seems it is related to @danielzhe changes on kiegroup/kogito-editors-java#120 and we are fine here in #631

@jomarko Is there any Jenkins job that runs here? If you want to re-trigger the GitHub Actions workflows, the author of the PR can push an empty commit.

@jomarko Is there any Jenkins job that runs here? If you want to re-trigger the GitHub Actions workflows, the author of the PR can push an empty commit.
@tiagobento I am waiting for the editors' version merge (https://github.com/kiegroup/kogito-tooling/pull/634), in order to rebase this PR and run all checks

you'll see following:

Seems really like sth is broken along the way.

@vpellegrino thank you

I reported a separate issue for chrome-extension read only mode https://issues.redhat.com/browse/KOGITO-6074
to build and run online-editor or desktop I use this:

kogito-tooling$ yarn
kogito-tooling$ yarn build:dev
kogito-tooling/packages/online-editor$ yarn start
kogito-tooling/packages/desktop$ yarn start

01
Unable to open a specific decision table using new editor
https://issues.redhat.com/browse/KOGITO-6097

05 desktop, styling
The seems be some styles conflict after new boxed expression editor is used
https://issues.redhat.com/browse/KOGITO-6102

06 kie-editors-standalone, readonly mode
Same as for chrome extension https://issues.redhat.com/browse/KOGITO-6074

@jomarko feel free to set me as tester if it makes sense :-) or a watcher if someone else takes it as tester.


example-instagram upload image vulcan-forms-upload

I am trying to upload photos to cloudinary in the example-Instagram app
I tried type String and Array, not none of them works
imageUrl: {
   label: 'Image URL',
   type: String,
   canRead: ['guests'],
   canCreate: ['members'],
   canUpdate: ['members'],
   input: FormsUpload, // use the FormsUpload form component
   options: {
     preset: 'mypreset'
   },
 },

error message for type Array:
Error: "imageUrl" is Array type but the schema does not include a "imageUrl.$" definition for the array items"
How do I fix this?
Thanks

Please try this one, like this:
imageUrl: {    label: 'Image URL',    type: String,    canRead: ['guests'],    canCreate: ['members'],    canUpdate: ['members'],    input: FormsUpload, // use the FormsUpload form component    options: {      preset: 'mypreset'    },  }, {     fieldName: 'imageUrl.$',     fieldSchema: {       type: String     }  }

@valgalin thanks for the fix!
I'll close this since there is already a more appropriate issue on the starter repo: https://github.com/VulcanJS/Vulcan-Starter/issues/116


Notification chain is not executed

Hi all,
we're running 785bf4e896ae4209f9edd5827b16e18448cde3b5 and I just introduced slack based notification into our Bosun configuration. Unfortunately, the next action is not executed as expected after a timeout of 15 min -- in case of a warning -- or immediately -- in case of a critical event. Below is my current configuration. Is this a bug or is there an error in my config?
notification default {
  email = infrastructure-hosting-team@XXXX
  next = default
  timeout = 6h
}

notification slack.warn {
  post = https://hooks.slack.com/services/XXXX
  body = payload={"username": "Bosun Cluster B", "channel": "#alerts-clusterb", "text": {{.|json}}, "icon_url": "https://raw.githubusercontent.com/bosun-monitor/bosun/master/cmd/bosun/web/static/img/tsaf-logo-mark.png"}
  next = default
  timeout = 15m
}

notification slack.crit {
  post = https://hooks.slack.com/services/XXXX
  body = payload={"username": "Bosun Cluster B", "channel": "#alerts-clusterb", "text": {{.|json}}, "icon_url": "https://raw.githubusercontent.com/bosun-monitor/bosun/master/cmd/bosun/web/static/img/tsaf-logo-mark.png"}
  next = default
}

Thanks in advance,
cheers,
Lukas

You didn't acknowledge the alert within that 15 minutes?

Nope, I didn't.
I also tried is using different timeouts; even one minute without success.

I updated to 0.2.0 and still observe the same behavior. Any ideas?

Here's how to debug this:

Add print = true to all of the notifications.
Set the timeout to something small like 5s.
Make a simple alert that always triggers: crit = 1, that is also hooked up to one of those notifications.
Watch the log entries produced to see what it's doing.

That will help determine what is the part that isn't working.

From my experience the chain breaks with something with the body generation:
This kept the chain working:
notification hipchat {
next = email
#post = http://api.hipchat.com/v2/room/xx/notification?auth_token=xx
#:body = {"color": "red", "notify": true, "message_format": "text", "message": {{.|json}}}
#contentType = application/json
timeout = 5s
print = true
}
this didn't:
notification hipchat {
next = email
#post = http://api.hipchat.com/v2/room/xx/notification?auth_token=xx
body = {"color": "red", "notify": true, "message_format": "text", "message": {{.|json}}}
contentType = application/json
timeout = 5s
print = true
}

Sorry guys for not coming back to you earlier.
I'm using bosun version 0.3.0 (9386abc03b9d074e42dbbe5eb5944ee88ca641f6) built 2015-07-13T15:17:11Z
@mjibson I added print = true to all notifications and could see the the alarm's subject getting logged. Unfortunately, there doesn't seem to be a deterministic behavior for alarm chains.
The following example worked exactly the first time the alarm became active, both notification were executed:
notification test.email.warn {
  print = true
  email = lukas.pustina@XXX
}

notification test.slack.warn {
  print = true
  post = https://hooks.slack.com/services/XXXX
  body = payload={"username": "Bosun Cluster B", "channel": "#alerts-clusterb", "text": {{.|json}}, "icon_url": "https://raw.githubusercontent.com/bosun-monitor/bosun/master/cmd/bosun/web/static/img/tsaf-logo-mark.png"}
  next = test.email.warn
  timeout = 5s
}

alert test.slack.notification {
  template = default.woGraph
  warnNotification = test.slack.warn

  warn = 0

  $name = TEST: Slack alarm chain
  $description = Just for testing
  $steps = Make it work
}

I couldn't make the chain work again. Even the slack notification wasn't executed reliably every time the alarm become active.
I reduced the notification to email only:
notification escalate {
  print = true
  email = infrastructure-alert@XXX
  next = escalate
  timeout = 1d
}

notification default {
  print = true
  email = infrastructure-alert-cluster-b@xxxx
  next = escalate
  timeout = 5s
}

This chain didn't worked even once, but at least the first E-Mail (default) was sent reliably every time the alarm became active.
Currently, I settled on using the E-Mail integration of slack andd sending E-Mails in default to two E-Mail address -- mailing list and slack.
I'm happy to try any other debugging you guys might think could help to analyse the problem.

I believe this is fixed now


No response headers? No Cookies?

Failed to send response header(s)
/**
 * @public
 * @async
 * (Query) Get current user information
 * @returns {Promise<Object>}
 */
Query.test = async ( root, args, ctx, info ) => {
  /** @type {(fastify#FastifyReply|FastifyResponse)} */
  const res = ctx.res;
  res.header('X-test', 'changed');
  return true;
};

Response header:
< HTTP/1.1 200 OK
< X-XSS-Protection: 1; mode=block
< Vary: Origin
< Access-Control-Allow-Credentials: true
< x-test: changed
< content-type: application/json; charset=utf-8
< content-length: 2
< Date: Thu, 14 Feb 2019 17:18:54 GMT
< Connection: keep-alive

Header X-test wasn't sent to response, same issues with cookies.

This works great!
Query.test = async ( root, args, ctx, info ) => {
  /** @type {(fastify#FastifyReply|FastifyResponse)} */
  const res = ctx.res;
  res.header('X-test', 'changed')
    .send(true);

  //return true;
};

Response:
< Vary: Origin
< Access-Control-Allow-Credentials: true
< x-test: changed <--------------------------------------- here
< content-type: application/json; charset=utf-8
< content-length: 4
< Date: Thu, 14 Feb 2019 17:31:32 GMT
< Connection: keep-alive

So what you suggest, Can I use this to send headers/cookies in response?


Suggestion: Detach the project from upstream

Hey everyone,
Thanks to @Christopher-Hayes (and, of course, the original author), this project has been developing well with new contributions and contributors, while the original project is no longer maintained. Maybe we should consider detaching from upstream or even moving to an individual GitHub organization as a working group(just optional and additional thoughts). Here are a few benefits:

Clearly showcase our contributions and improvements, making it easier for users to find the latest version
Enhance the project's autonomy and independence, giving everyone a stronger sense of ownership
Consider creating an independent organization to manage the project, inviting more contributors to join and grow our community

What do you think?
If everyone agrees, there's a link that we can use to proceed with the detachment: https://support.github.com/contact?flow=detach_fork&subject=Detach Fork&tags=rr-forks

Thanks, Peter. Yeah, it seems like a good time to finally detach the fork. PRs defaulting to merge back into the upstream repo is getting annoying, haha.
Creating an org is a good idea too. It looks like reborn-ai is already taken, any ideas? Another possibility is vscode-reborn-ai.
In the meantime, I'll get that support ticket created.

Awesome, vscode-reborn-ai looks good to me, but we can also redefine the mission and the vision of vscode extension and then use that information to discuss with the most powerful models to determine the name 😆

Cool! Created the org over here: https://github.com/vscode-reborn-ai

To give an update - GitHub had some kind of server issue that impacts repos that were deforked last Friday. This repo is one of the projects that were affected.
That is why GitHub right now says the repo is not available. GitHub says they're working on a fix, they have not given me an ETA for when that will be completed.
Once it's fixed, I'll move the repo over to the vscode-reborn-ai organization.

To give an update - GitHub had some kind of server issue that impacts repos that were deforked last Friday. This repo is one of the projects that were affected.
That is why GitHub right now says the repo is not available. GitHub says they're working on a fix, they have not given me an ETA for when that will be completed.
Once it's fixed, I'll move the repo over to the vscode-reborn-ai organization.

I was wondering why I keep seeing this 😅

Alright, the repo is deforked, and has been moved over to the github.com/vscode-reborn-ai organization. It is recommended you update your git config to reflect the new repo location. That step is only recommended, but not required because GitHub will automatically redirect any git requests to this new repo location.

It is recommended that you update your git config to reflect the new repo location. That step is only recommended, but not required because GitHub will automatically redirect any git requests to this new repo location.

One important thing that needs to be done for contributors would be to fork the new repository; otherwise, you won't be able to send pull requests to the new project.


No obvious way to close full-screen after [process exited with code 1 (0x00000001)]

Windows Terminal version
1.13.10983.0
Windows build number
Version	10.0.19043 Build 19043
Other Software
No response
Steps to reproduce
Open Windows Terminal. Be in full-screen no-tabs mode because of user preferences in Settings (a good focused mode for working).
Connect to remote machine through PowerShell ssh program.
Allow to timeout with [process exited with code 1 (0x00000001)] error.
Now there is no obvious way to close the screen.
It is possible to close the screen by hitting Windows+Tab to get the Virtual Desktop view and then hit the "X" gadget from that user interface. But that is not obvious nor optimal.
Expected Behavior
For there to be present some immediately obvious way to close a locked-up screen without using Virtual Desktop tricks or hitting Ctrl+F11 to exit full-screen mode manually just to close it. Maybe turning tabs back on or throwing up a close-gadget when [process exited with code 1 (0x00000001)] even in full-screen mode.
Actual Behavior
One must hit Ctrl+F11 to get out of full-screen mode or Windows+Tab to get the Virtual Desktop interface in order to close a locked-up terminal as a result of a [process exited with code 1 (0x00000001)] error.

Thanks for the suggestion! This is probably best served by either /dup #11570 or /dup #5677


refactor linear interpolation function

Description
linear_interpolation uses a boilerplate search function, this is neither efficient nor easy to maintain. Better to switch to std::lower_bound method.
Expected Output
Same as old one.
Current Version:
v2.19.1

resolved in https://github.com/metrumresearchgroup/math/pull/34


Better detection of ipykernel installer actions

Codecov Report

Merging #7617 (f4c7ccc) into main (21c5ebb) will increase coverage by 0%.
The diff coverage is 63%.

@@          Coverage Diff          @@
##            main   #7617   +/-   ##
=====================================
  Coverage     66%     66%
=====================================
  Files        365     365
  Lines      22660   22673   +13
  Branches    3445    3448    +3
=====================================
+ Hits       15103   15129   +26
+ Misses      6269    6251   -18
- Partials    1288    1293    +5

Impacted Files
Coverage Δ

src/client/common/utils/async.ts
43% <ø> (ø)

src/client/datascience/baseJupyterSession.ts
68% <ø> (ø)

src/client/telemetry/index.ts
63% <ø> (ø)

src/client/datascience/jupyter/kernels/helpers.ts
72% <8%> (+1%)
:arrow_up:

...science/jupyter/kernels/kernelDependencyService.ts
83% <60%> (-1%)
:arrow_down:

src/client/datascience/jupyter/kernels/kernel.ts
71% <69%> (-1%)
:arrow_down:

...atascience/interactive-window/interactiveWindow.ts
54% <100%> (ø)

...tascience/jupyter/kernels/kernelCommandListener.ts
56% <100%> (+<1%)
:arrow_up:

...ent/datascience/jupyter/kernels/kernelExecution.ts
68% <100%> (ø)

...ient/datascience/jupyter/kernels/kernelProvider.ts
98% <100%> (+<1%)
:arrow_up:

... and 12 more


Mark md5 as not being used for security

Fixes #6263, I think?

Thanks for looking at this quickly, I didn't know about the usedforsecurity argument, but I'm glad it was so easy. I confirmed in a Python REPL on my FIPS machine that this does let you use hashlib.md5 so I imagine this will fix the issue.


Adjust the prompt

Based on my conversation with @karmi, I will update the prompt to better follow the Git commit best practices.
Inspiration:

https://gist.github.com/robertpainsi/b632364184e70900af4ab688decf6f53
https://github.com/PublicDataWorks/verdad/blob/main/prompts/Stage_1_Preprocess_detection_prompt.md

Also, https://www.conventionalcommits.org/en/v1.0.0/#summary is a good reference.


Feature send cheeps

Sending Cheeps is now Possible
You can now send cheeps by entering them into the form this will store them in the cheeps table.
Added additions

Created a form for submitting cheeps
Added the backend for handling the logic of creating a new CheepDTO object with a nested AuthorDTO object for better being able to send it down the pipeline
Configured the backend to now Createcheeps as well as create author from the nested AuthorDTO's name
Recreated the author table to now have AuthorId stores as an integer instead of text, such that it can autoincrement.
Updated the migration for the DB
Fixed the Time format to only display HH-MM--SS instead of the whole unix timer.
Added such that if an author does not exist in the table already they will be added when posting their first cheep
Made it possible to send cheeps from the user timeline and public timeline
Made sure to redirect to each site after posting, so that we won't experience double requests and errors.

With these changes Issue number #102 should be solved.

Test should fail because it is being worked on currently by other team members


Replace hardcoded image formats to const values

As I mentioned on the other PR there's going to be a major update, so I'll better keep this one unmerged due to some conflicts, still, it's a good idea to keep them as constants of course, I'll have it in mind jajaja


physics wall is rotated the wrong way.

in the simple example, the angled wall is rendered with one rotation, but the physics engine has the colision object rotated the other way around.

Another nice to have would be a debug option to render an outline around the bounding box

Heh I noticed this over the weekend and was wondering why my simulator elements were on the wrong side of the wall

Is this still an issue? I played with the gravity in all directions and ball and box bounce off the wall correctly

@zhiquanyeo said he had also noticed this bug, maybe he fixed it?

I think it still is. It shows up in the SimRobot demo (if you re-add the angle wall). Should be a sign change in the declaration of the body


Introduce state backends such as s3, dynamodb, etc.

Spec discussion:

https://github.com/meltano/meltano/discussions/6270

I think we could introduce state backends such as s3, dynamodb, and other backends that have better reliability than an RDBMS and near-zero always on cost.
In the future, a Meltano-managed state offering, similar to Pulumi's default experience.
Originally posted by @aaronsteers in https://github.com/meltano/meltano/issues/2520#issuecomment-1145062214
Additional context:

Currently a 'current' STATE is a composite on-demand scan through history records. This is not ideal in general - and we have #3340 logged to refactor this so a single table row would be the "backend" to read and write from.
Moving to a generic backend store would likely require also solving for #3340 - or at least the same refactoring would (likely) be needed in both cases to eliminate the need for scanning history logs.

Workarounds:
#2520 talks about potential workaround, but basically the current workaround is to:

meltano state get... to pull the latest state into a file.
upload that file to S3 before the container is deleted.
when next run, download the file from S3 and load to the systemdb with meltano state set ...

This works with our without a postgres or other long-lived rdmbs, since the built-in sqlite implementation is created on the fly if no postgresdb is specified, and the process above essentially just removes the long-term state storage requirement from the sqlite backend.

The plugin approach discussed in https://github.com/meltano/meltano/discussions/6270#discussion-4166066 I think does make sense to explore more. Particularly in light of efforts with #6130

I'm running Meltano in a container aswell, but I'm having a hard time figuring out what the best way is to upload that file to S3 before the container is deleted. There's no on-run-end hook in Meltano right?

@rickiesmooth which file are asking about? There's a few ways I could imagine doing this but there's currently no on-run-end hook exactly like there is in dbt.

Sorry I was referencing the workaround and how it uploads the state file.

ah that would be nice, for now I just do:
meltano state get dev:tap-google-search-console-to-target-bigquery > meltano_state/gsc_state.json
meltano state get dev:tap-google-analytics-to-target-bigquery > meltano_state/ga_state.json

aws s3 sync meltano_state s3://$S3_BUCKET/meltano_state

after meltano ran

@rickiesmooth that's good to know! I think we will be building this into Meltano natively though as it's going to be a pre-req for our future Managed offering.

There have been some synchronous discussions on this--documenting the results of those here.
The v1 of this feature is going to be to use a third-party library (likely smart_open) that will allow us to support users configuring state backends in the form of a simple URI, e.g. s3://some_bucket/some_prefix, where both partial and complete state files can be written. This means we'll also need to implement some barebones locking mechanism. Locking doesn't need to be too sophisticated at first because running the same pipeline using the same backend concurrently in separate deployments should be a pretty rare use case, and those users can still use the existing system db state backend to get more deterministic behavior. Plus, the meltano state commands allow users to manually edit, clear, copy, or merge state to fix any issues that arise from concurrent runs.
Creating state backends is going to require decoupling state from job history, so we'll need to tackle https://github.com/meltano/meltano/issues/3340 before getting started on the actual state backend implementation.
This implementation will be done in such a way as to lay the foundation for user contributed state backend plugins in some future iteration, but "pluggable" backends are out of scope for the time being. The URI approach solves for a huge number of use cases and takes us one step closer to eliminating the need for a postgres backend in production deployments without the heavy lift of supporting arbitrary plugins.

As I've been getting into the weeds on this, it's increasingly become clear that the best approach to this is much more entangled with #3340 than initially thought and a lot of this work will be front-loaded into that PR.
I've also realized that I've spent a lot of time heads down on this without any PRs or touch points so here's a quick brain dump of the current status and timeline along with a more thorough implementation spec to make sure everyone is on the same page about what's being delivered here.
Status and Timeline
Current status is that the refactoring work for this has turned out to touch a lot of the codebase and existing testing suite. Since we're refactoring jobs and state as part of #3340, the PR for that issue will include a basic v1 for the state backend approach, but using systemdb as the first supported state backend. #3340's PR will have rewritten the way we manage state entirely to be basically the same pattern as we use for managing settings. We're rewriting StateService methods to be backend-agnostic and then we'll have a StateStore ABC that state backend implementations will inherit, very similar to how we currently have a unified ProjectSettingsService and PluginSettingsService that mostly wrap methods that are implemented at the SettingsStoreManager level.
Since this is a significant refactor and major new feature, it's difficult to chunk up into small iterations. Current timeline for releasing StateBackends will likely be Iteration 16. It should be ready to go in the first release after that and I'll have a demo ready to go as well.
Implementation Spec
StateService
In rolling out the meltano state command, we refactored state management into its own StateService class. This means that state management logic is already consolidated into a single place in the codebase and we can easily the SQLAlchemy-heavy logic from StateService methods into a dedicated systemdb state backend and then StateService will simply contain logic for determining which state backend to use and then calling the relevant state backend methods. Again, this is very similar to the approach we take for settings management via SettingsService and SettingsStoreManager implementations.
StateStoreManager
We're writing a new StateStoreManager base class which defines abstract methods for getting and setting state (both partial and complete) for various state backends, as well as extremely simple locking logic (basically just acquire and release--implementations will determine timeout logic, deadlock resolution, etc. on a per-backend basis). The first implementation of StateStoreManager is DBStateStoreManager which will largely consist of the existing logic for managing state in the backend DB as currently defined in StateService
Configuring
In this v1, state backend will be configurable at the project level and will be a top-level key in meltano.yml. This is the simplest approach and meets most use cases that have been discussed as motivation for the state backends feature. However, the implementation outlined above will make it relatively easy to quickly update state backends to be configurable at any configuration layer--StateService can simply do SettingsService.get calls to determine what StateStoreManager to use and pass through any necessary config. The it won't be much effort to implement a PluginStateStoreManager that can use wrap Meltano StateBackend extensions when we're ready to add that capability to the edk.
FYI @aaronsteers @tayloramurphy @pandemicsyn

@cjohnhanson appreciate the write-up and context setting 👍

Since we're refactoring jobs and state as part of #3340, the PR for that issue will include a basic v1 for the state backend approach, but using systemdb as the first supported state backend.

👍 🎯

#3340's PR will have rewritten the way we manage state entirely to be basically the same pattern as we use for managing settings. We're rewriting StateService methods to be backend-agnostic and then we'll have a StateStore ABC that state backend implementations will inherit, very similar to how we currently have a unified ProjectSettingsService and PluginSettingsService that mostly wrap methods that are implemented at the SettingsStoreManager level.

👍

Since this is a significant refactor and major new feature, it's difficult to chunk up into small iterations. Current timeline for releasing StateBackends will likely be Iteration 16. It should be ready to go in the first release after that and I'll have a demo ready to go as well.

Emphasis on 'small' iterations, yes?
Small or not, what about this approach to breaking this into chunks:

First PR. Launch the first state backend, which would be systemdb and the new state table in #3340. Doesn't need configuration.
Second PR. Add second state backend, for instance based on PyFilesystem or smart_open. Should include method of configuring.
Third PR. Add --from_backend and --to_backend support to meltano state copy|move CLI commands.

@aaronsteers --

First PR. Launch the first state backend, which would be systemdb and the new state table in https://github.com/meltano/meltano/issues/3340. Doesn't need configuration. (Would track/rework in https://github.com/meltano/meltano/issues/3340 as a dependency for external backends discussed here.)

Second PR. Add second state backend, for instance based on PyFilesystem or smart_open. Should include method of configuring. (Can use this issue, aka https://github.com/meltano/meltano/issues/5981.)

100%, that's exactly the plan.

Third PR. Add --from_backend and --to_backend support to meltano state copy|move CLI commands. (Not logged yet.)

Yeah, I think that makes sense as the next step and should be pretty straightforward to implement after these changes.