moveit: 2.10.0-1 in 'jazzy/distribution.yaml' [bloom]

Increasing version of package(s) in repository moveit to 2.10.0-1:

upstream repository: https://github.com/moveit/moveit2.git
release repository: https://github.com/ros2-gbp/moveit2-release.git
distro file: jazzy/distribution.yaml
bloom version: 0.11.2
previous version for package: 2.9.0-1

chomp_motion_planner
* Unify log names (#2720 <https://github.com/moveit/moveit2/issues/2720>)
  Co-authored-by: Abishalini Sivaraman<EMAIL_ADDRESS>* CMake format and lint in pre-commit (#2683 <https://github.com/moveit/moveit2/issues/2683>)
* Contributors: Sebastian Jahr, Tyler Weaver

moveit
* Migrate ros-planning org to moveit (#2847 <https://github.com/moveit/moveit2/issues/2847>)
  * Rename github.com/ros-planning -> github.com/moveit
  * Rename ros-planning.github.io -> moveit.github.io
  * Rename ros-planning organization in docker and CI workflow files
  - ghcr.io/ros-planning -> ghcr.io/moveit
  - github.repository == 'moveit/*''
* CMake format and lint in pre-commit (#2683 <https://github.com/moveit/moveit2/issues/2683>)
* Contributors: Robert Haschke, Tyler Weaver

moveit_common
* Migrate ros-planning org to moveit (#2847 <https://github.com/moveit/moveit2/issues/2847>)
  * Rename github.com/ros-planning -> github.com/moveit
  * Rename ros-planning.github.io -> moveit.github.io
  * Rename ros-planning organization in docker and CI workflow files
  - ghcr.io/ros-planning -> ghcr.io/moveit
  - github.repository == 'moveit/*''
* CMake format and lint in pre-commit (#2683 <https://github.com/moveit/moveit2/issues/2683>)
* Contributors: Robert Haschke, Tyler Weaver

moveit_configs_utils
* Migrate ros-planning org to moveit (#2847 <https://github.com/moveit/moveit2/issues/2847>)
  * Rename github.com/ros-planning -> github.com/moveit
  * Rename ros-planning.github.io -> moveit.github.io
  * Rename ros-planning organization in docker and CI workflow files
  - ghcr.io/ros-planning -> ghcr.io/moveit
  - github.repository == 'moveit/*''
* Fix xacro args loading issue (#2684 <https://github.com/moveit/moveit2/issues/2684>)
  * Fixed xacro args loading issue
  * Formatting fixes with pre-commit action
* Pass along move_group_capabilities parameters (#2587 <https://github.com/moveit/moveit2/issues/2587>)
  * Pass along move_group_capabilities parameters
  * fix lint check
  * Use move_group_capabilities as default launch argument
* CMake format and lint in pre-commit (#2683 <https://github.com/moveit/moveit2/issues/2683>)
* Use different packages for launch and config packages in generate_demo_launch (#2647 <https://github.com/moveit/moveit2/issues/2647>)
* Contributors: Alex Navarro, Forrest Rogers-Marcovitz, Robert Haschke, Tyler Weaver

moveit_core
* Enforce liboctomap-dev by using a cmake version range
* Add utility functions to get limits and trajectory message (#2861 <https://github.com/moveit/moveit2/issues/2861>)
* Migrate ros-planning org to moveit (#2847 <https://github.com/moveit/moveit2/issues/2847>)
  * Rename github.com/ros-planning -> github.com/moveit
  * Rename ros-planning.github.io -> moveit.github.io
  * Rename ros-planning organization in docker and CI workflow files
  - ghcr.io/ros-planning -> ghcr.io/moveit
  - github.repository == 'moveit/*''
* Use std::optional instead of nullptr checking (#2454 <https://github.com/moveit/moveit2/issues/2454>)
* Enable mdof trajectory execution (#2740 <https://github.com/moveit/moveit2/issues/2740>)
  * Add RobotTrajectory conversion from MDOF to joints
  * Convert MDOF trajectories to joint trajectories in planning interfaces
  * Treat mdof joint variables as common joints in
  TrajectoryExecutionManager
  * Convert multi-DOF trajectories to joints in TEM
  * Revert "Convert MDOF trajectories to joint trajectories in planning interfaces"
  This reverts commit 885ee2718594859555b73dc341311a859d31216e.
  * Handle multi-DOF variables in TEM's bound checking
  * Add parameter to optionally enable multi-dof conversion
  * Improve error message about unknown controllers
  * Fix name ordering in JointTrajectory conversion
  * Improve DEBUG output in TEM
  * Comment RobotTrajectory test
  * add acceleration to avoid out of bounds read
* Fix doc reference to non-existent function (#2765 <https://github.com/moveit/moveit2/issues/2765>)
* (core) Remove unused python docs folder (#2746 <https://github.com/moveit/moveit2/issues/2746>)
* Unify log names (#2720 <https://github.com/moveit/moveit2/issues/2720>)
* (core) Install collision_detector_fcl_plugin (#2699 <https://github.com/moveit/moveit2/issues/2699>)
  FCL version of acda563
* Simplify Isometry multiplication benchmarks (#2628 <https://github.com/moveit/moveit2/issues/2628>)
  With the benchmark library, there is no need to specify an iteration count.
  Interestingly, 4x4 matrix multiplication is faster than affine*matrix
* CMake format and lint in pre-commit (#2683 <https://github.com/moveit/moveit2/issues/2683>)
* Merge pull request #2660 <https://github.com/moveit/moveit2/issues/2660> from MarqRazz/pr-fix_model_with_collision
  Fix getLinkModelNamesWithCollisionGeometry to include the base link
* validate link has parent
* pre-commit
* Fix getLinkModelNamesWithCollisionGeometry to include the base link of the planning group
* Acceleration Limited Smoothing Plugin for Servo (#2651 <https://github.com/moveit/moveit2/issues/2651>)
* Contributors: Henning Kayser, Marq Rasmussen, Matthijs van der Burgh, Paul Gesel, Robert Haschke, Sebastian Jahr, Shobuj Paul, Tyler Weaver, marqrazz

moveit_hybrid_planning
* Migrate ros-planning org to moveit (#2847 <https://github.com/moveit/moveit2/issues/2847>)
  * Rename github.com/ros-planning -> github.com/moveit
  * Rename ros-planning.github.io -> moveit.github.io
  * Rename ros-planning organization in docker and CI workflow files
  - ghcr.io/ros-planning -> ghcr.io/moveit
  - github.repository == 'moveit/*''
* Remove HP error codes interface (#2774 <https://github.com/moveit/moveit2/issues/2774>)
* Unify log names (#2720 <https://github.com/moveit/moveit2/issues/2720>)
  Co-authored-by: Abishalini Sivaraman<EMAIL_ADDRESS>* CMake format and lint in pre-commit (#2683 <https://github.com/moveit/moveit2/issues/2683>)
* Clean-up hybrid planning package (#2603 <https://github.com/moveit/moveit2/issues/2603>)
* Contributors: Robert Haschke, Sebastian Jahr, Tyler Weaver

moveit_kinematics
* At least on humble, error is: 'robot_description_kinematics.arm.min_joint_config_distance' has invalid type: expected [double] got [integer]. (#2865 <https://github.com/moveit/moveit2/issues/2865>)
* Migrate ros-planning org to moveit (#2847 <https://github.com/moveit/moveit2/issues/2847>)
  * Rename github.com/ros-planning -> github.com/moveit
  * Rename ros-planning.github.io -> moveit.github.io
  * Rename ros-planning organization in docker and CI workflow files
  - ghcr.io/ros-planning -> ghcr.io/moveit
  - github.repository == 'moveit/*''
* CI: Fix building of ikfast plugins (#2791 <https://github.com/moveit/moveit2/issues/2791>)
  Ignore missing authentication for Indigo packages using --force-yes.
* Unify log names (#2720 <https://github.com/moveit/moveit2/issues/2720>)
* CMake format and lint in pre-commit (#2683 <https://github.com/moveit/moveit2/issues/2683>)
* Contributors: Henning Kayser, Robert Haschke, Sebastian Jahr, Tyler Weaver, s-trinh

moveit_planners
* Migrate ros-planning org to moveit (#2847 <https://github.com/moveit/moveit2/issues/2847>)
  * Rename github.com/ros-planning -> github.com/moveit
  * Rename ros-planning.github.io -> moveit.github.io
  * Rename ros-planning organization in docker and CI workflow files
  - ghcr.io/ros-planning -> ghcr.io/moveit
  - github.repository == 'moveit/*''
* CMake format and lint in pre-commit (#2683 <https://github.com/moveit/moveit2/issues/2683>)
* Contributors: Robert Haschke, Tyler Weaver

moveit_planners_chomp
* Unify log names (#2720 <https://github.com/moveit/moveit2/issues/2720>)
  Co-authored-by: Abishalini Sivaraman<EMAIL_ADDRESS>* CMake format and lint in pre-commit (#2683 <https://github.com/moveit/moveit2/issues/2683>)
* Contributors: Sebastian Jahr, Tyler Weaver

moveit_planners_ompl
* Migrate ros-planning org to moveit (#2847 <https://github.com/moveit/moveit2/issues/2847>)
  * Rename github.com/ros-planning -> github.com/moveit
  * Rename ros-planning.github.io -> moveit.github.io
  * Rename ros-planning organization in docker and CI workflow files
  - ghcr.io/ros-planning -> ghcr.io/moveit
  - github.repository == 'moveit/*''
* Unify log names (#2720 <https://github.com/moveit/moveit2/issues/2720>)
  Co-authored-by: Abishalini Sivaraman<EMAIL_ADDRESS>* Do not overwrite the error code with OMPL interface (#2725 <https://github.com/moveit/moveit2/issues/2725>)
  In case of failure, set the error code to the one returned by the
  planning pipeline's solve method rather than overwriting it with
  PLANNING_FAILED.
* Set planner_id in reponses with OMPL interface (#2724 <https://github.com/moveit/moveit2/issues/2724>)
  This avoids a warning PlanningPipeline::generatePlan().
  Co-authored-by: Gaël Écorchard<EMAIL_ADDRESS>* CMake format and lint in pre-commit (#2683 <https://github.com/moveit/moveit2/issues/2683>)
* Contributors: Gaël Écorchard, Robert Haschke, Sebastian Jahr, Tyler Weaver

moveit_planners_stomp
* Migrate ros-planning org to moveit (#2847 <https://github.com/moveit/moveit2/issues/2847>)
  * Rename github.com/ros-planning -> github.com/moveit
  * Rename ros-planning.github.io -> moveit.github.io
  * Rename ros-planning organization in docker and CI workflow files
  - ghcr.io/ros-planning -> ghcr.io/moveit
  - github.repository == 'moveit/*''
* Unify log names (#2720 <https://github.com/moveit/moveit2/issues/2720>)
  Co-authored-by: Abishalini Sivaraman<EMAIL_ADDRESS>* CMake format and lint in pre-commit (#2683 <https://github.com/moveit/moveit2/issues/2683>)
* missing destination path (#2668 <https://github.com/moveit/moveit2/issues/2668>)
* Fix penalty-based cost function in STOMP (#2625 <https://github.com/moveit/moveit2/issues/2625>)
  * Fix penalty-based cost function in STOMP
  This adds several test cases for STOMP's noise generation and cost
  functions, and provides the following fixes:
  * out-of-bounds vector access when tail states of trajectory are invalid
  * smoothed costs overriding values of previous invalid groups
  * missing validity check of last state in trajectory
  * inability to disable cost function interpolation steps
  * total cost of trajectory not summing up to sum of state penalties
  * bug in Gaussian producing infinite values with invalid start states
  * Improve documentation
  ---------
* Contributors: Henning Kayser, Robert Haschke, Sarvajith Adyanthaya, Sebastian Jahr, Tyler Weaver

moveit_plugins
* CMake format and lint in pre-commit (#2683 <https://github.com/moveit/moveit2/issues/2683>)
* Contributors: Tyler Weaver

moveit_py
* Migrate ros-planning org to moveit (#2847 <https://github.com/moveit/moveit2/issues/2847>)
  * Rename github.com/ros-planning -> github.com/moveit
  * Rename ros-planning.github.io -> moveit.github.io
  * Rename ros-planning organization in docker and CI workflow files
  - ghcr.io/ros-planning -> ghcr.io/moveit
  - github.repository == 'moveit/*''
* Unify log names (#2720 <https://github.com/moveit/moveit2/issues/2720>)
  Co-authored-by: Abishalini Sivaraman<EMAIL_ADDRESS>* Get configuration values of traj_exec_man (#2702 <https://github.com/moveit/moveit2/issues/2702>)
  * (ros_planning) get configuration values of traj_exec_man
  * (py) get configuration values of traj_exec_man
* CMake format and lint in pre-commit (#2683 <https://github.com/moveit/moveit2/issues/2683>)
* log after rclcpp init
* Contributors: Henning Kayser, Matthijs van der Burgh, Robert Haschke, Sebastian Jahr, Tyler Weaver, peterdavidfagan

moveit_resources_prbt_ikfast_manipulator_plugin
* Migrate ros-planning org to moveit (#2847 <https://github.com/moveit/moveit2/issues/2847>)
  * Rename github.com/ros-planning -> github.com/moveit
  * Rename ros-planning.github.io -> moveit.github.io
  * Rename ros-planning organization in docker and CI workflow files
  - ghcr.io/ros-planning -> ghcr.io/moveit
  - github.repository == 'moveit/*''
* CMake format and lint in pre-commit (#2683 <https://github.com/moveit/moveit2/issues/2683>)
* Contributors: Robert Haschke, Tyler Weaver

moveit_resources_prbt_moveit_config
* Migrate ros-planning org to moveit (#2847 <https://github.com/moveit/moveit2/issues/2847>)
  * Rename github.com/ros-planning -> github.com/moveit
  * Rename ros-planning.github.io -> moveit.github.io
  * Rename ros-planning organization in docker and CI workflow files
  - ghcr.io/ros-planning -> ghcr.io/moveit
  - github.repository == 'moveit/*''
* CMake format and lint in pre-commit (#2683 <https://github.com/moveit/moveit2/issues/2683>)
* Contributors: Robert Haschke, Tyler Weaver

moveit_resources_prbt_pg70_support
* Migrate ros-planning org to moveit (#2847 <https://github.com/moveit/moveit2/issues/2847>)
  * Rename github.com/ros-planning -> github.com/moveit
  * Rename ros-planning.github.io -> moveit.github.io
  * Rename ros-planning organization in docker and CI workflow files
  - ghcr.io/ros-planning -> ghcr.io/moveit
  - github.repository == 'moveit/*''
* CMake format and lint in pre-commit (#2683 <https://github.com/moveit/moveit2/issues/2683>)
* Contributors: Robert Haschke, Tyler Weaver

moveit_resources_prbt_support
* Migrate ros-planning org to moveit (#2847 <https://github.com/moveit/moveit2/issues/2847>)
  * Rename github.com/ros-planning -> github.com/moveit
  * Rename ros-planning.github.io -> moveit.github.io
  * Rename ros-planning organization in docker and CI workflow files
  - ghcr.io/ros-planning -> ghcr.io/moveit
  - github.repository == 'moveit/*''
* CMake format and lint in pre-commit (#2683 <https://github.com/moveit/moveit2/issues/2683>)
* Contributors: Robert Haschke, Tyler Weaver

moveit_ros
* Migrate ros-planning org to moveit (#2847 <https://github.com/moveit/moveit2/issues/2847>)
  * Rename github.com/ros-planning -> github.com/moveit
  * Rename ros-planning.github.io -> moveit.github.io
  * Rename ros-planning organization in docker and CI workflow files
  - ghcr.io/ros-planning -> ghcr.io/moveit
  - github.repository == 'moveit/*''
* CMake format and lint in pre-commit (#2683 <https://github.com/moveit/moveit2/issues/2683>)
* Contributors: Robert Haschke, Tyler Weaver

moveit_ros_benchmarks
* Migrate ros-planning org to moveit (#2847 <https://github.com/moveit/moveit2/issues/2847>)
  * Rename github.com/ros-planning -> github.com/moveit
  * Rename ros-planning.github.io -> moveit.github.io
  * Rename ros-planning organization in docker and CI workflow files
  - ghcr.io/ros-planning -> ghcr.io/moveit
  - github.repository == 'moveit/*''
* Fix CI for Rolling / Ubuntu Noble (#2793 <https://github.com/moveit/moveit2/issues/2793>)
  * docker.yaml: Enable caching
  * [TEMP] moveit2_rolling.repos: add not yet released packages
  * Skip broken ci-testing image: osrf/ros2:testing doesn't contain /opt/ros!
  * use boost::timer::progress_display if available
  check for header to stay compatible with ubuntu 20.04.
  Support boost >= 1.83
  Slightly ugly due to the double alias, but boost::timer was a class
  before 1.72, so using boost::timer::progress_display in the code
  breaks with older versions.
  * cherry-pick of #3547 <https://github.com/moveit/moveit2/issues/3547> from MoveIt1
  * Tag ci image as ci-testing as well
  ---------
  Co-authored-by: Michael Görner<EMAIL_ADDRESS>  Co-authored-by: Sebastian Jahr<EMAIL_ADDRESS>  Co-authored-by: Henning Kayser<EMAIL_ADDRESS>* Update deprecated include of boost/progress.hpp to boost/timer/progress_display.hpp (#2811 <https://github.com/moveit/moveit2/issues/2811>)
* Unify log names (#2720 <https://github.com/moveit/moveit2/issues/2720>)
  Co-authored-by: Abishalini Sivaraman<EMAIL_ADDRESS>* CMake format and lint in pre-commit (#2683 <https://github.com/moveit/moveit2/issues/2683>)
* Contributors: Robert Haschke, Sebastian Jahr, Stephanie Eng, Tyler Weaver

moveit_ros_control_interface
* Revert "Simplify controller manager namespacing (#2210 <https://github.com/moveit/moveit2/issues/2210>)"
  This reverts commit 55df0bccd5e884649780b4ceeee80891e563b57b.
  The deprecated constructor was being used in the same file
  for the exact use case of enabling namespaces that are not
  specified by the parameter. There is no replacement for
  supporting a dynamic server lookup, however the parameter
  logic could still use simplification.
* Unify log names (#2720 <https://github.com/moveit/moveit2/issues/2720>)
  Co-authored-by: Abishalini Sivaraman<EMAIL_ADDRESS>* CMake format and lint in pre-commit (#2683 <https://github.com/moveit/moveit2/issues/2683>)
* Contributors: Henning Kayser, Sebastian Jahr, Tyler Weaver

moveit_ros_move_group
* Migrate ros-planning org to moveit (#2847 <https://github.com/moveit/moveit2/issues/2847>)
  * Rename github.com/ros-planning -> github.com/moveit
  * Rename ros-planning.github.io -> moveit.github.io
  * Rename ros-planning organization in docker and CI workflow files
  - ghcr.io/ros-planning -> ghcr.io/moveit
  - github.repository == 'moveit/*''
* Unify log names (#2720 <https://github.com/moveit/moveit2/issues/2720>)
  Co-authored-by: Abishalini Sivaraman<EMAIL_ADDRESS>* Remove extraneous error message from URDF service (#2736 <https://github.com/moveit/moveit2/issues/2736>)
* Add parameter api integration test (#2662 <https://github.com/moveit/moveit2/issues/2662>)
* CMake format and lint in pre-commit (#2683 <https://github.com/moveit/moveit2/issues/2683>)
* Get robot description from topic in GetUrdfService (#2681 <https://github.com/moveit/moveit2/issues/2681>)
* Fix bug in GetUrdfService move_group capability  (#2669 <https://github.com/moveit/moveit2/issues/2669>)
  * Take both possible closings for links into account
  * Make CI happy
* avoid a relative jump threshold of 0.0 (#2654 <https://github.com/moveit/moveit2/issues/2654>)
* Add get group urdf capability (#2649 <https://github.com/moveit/moveit2/issues/2649>)
* Contributors: Abishalini Sivaraman, Ezra Brooks, Mario Prats, Robert Haschke, Sebastian Jahr, Tyler Weaver

moveit_ros_occupancy_map_monitor
* Enforce liboctomap-dev by using a cmake version range
* Migrate ros-planning org to moveit (#2847 <https://github.com/moveit/moveit2/issues/2847>)
  * Rename github.com/ros-planning -> github.com/moveit
  * Rename ros-planning.github.io -> moveit.github.io
  * Rename ros-planning organization in docker and CI workflow files
  - ghcr.io/ros-planning -> ghcr.io/moveit
  - github.repository == 'moveit/*''
* Unify log names (#2720 <https://github.com/moveit/moveit2/issues/2720>)
  Co-authored-by: Abishalini Sivaraman<EMAIL_ADDRESS>* CMake format and lint in pre-commit (#2683 <https://github.com/moveit/moveit2/issues/2683>)
* Contributors: Henning Kayser, Robert Haschke, Sebastian Jahr, Tyler Weaver

moveit_ros_perception
* Fix segmentation fault in mesh_filter/gl_renderer (#2834 <https://github.com/moveit/moveit2/issues/2834>)
* Migrate ros-planning org to moveit (#2847 <https://github.com/moveit/moveit2/issues/2847>)
  * Rename github.com/ros-planning -> github.com/moveit
  * Rename ros-planning.github.io -> moveit.github.io
  * Rename ros-planning organization in docker and CI workflow files
  - ghcr.io/ros-planning -> ghcr.io/moveit
  - github.repository == 'moveit/*''
* Unify log names (#2720 <https://github.com/moveit/moveit2/issues/2720>)
  Co-authored-by: Abishalini Sivaraman<EMAIL_ADDRESS>* CMake format and lint in pre-commit (#2683 <https://github.com/moveit/moveit2/issues/2683>)
* Contributors: CihatAltiparmak, Robert Haschke, Sebastian Jahr, Tyler Weaver

moveit_ros_planning
* Apply clang-tidy fixes
* Migrate ros-planning org to moveit (#2847 <https://github.com/moveit/moveit2/issues/2847>)
  * Rename github.com/ros-planning -> github.com/moveit
  * Rename ros-planning.github.io -> moveit.github.io
  * Rename ros-planning organization in docker and CI workflow files
  - ghcr.io/ros-planning -> ghcr.io/moveit
  - github.repository == 'moveit/*''
* Enable mdof trajectory execution (#2740 <https://github.com/moveit/moveit2/issues/2740>)
  * Add RobotTrajectory conversion from MDOF to joints
  * Convert MDOF trajectories to joint trajectories in planning interfaces
  * Treat mdof joint variables as common joints in
  TrajectoryExecutionManager
  * Convert multi-DOF trajectories to joints in TEM
  * Revert "Convert MDOF trajectories to joint trajectories in planning interfaces"
  This reverts commit 885ee2718594859555b73dc341311a859d31216e.
  * Handle multi-DOF variables in TEM's bound checking
  * Add parameter to optionally enable multi-dof conversion
  * Improve error message about unknown controllers
  * Fix name ordering in JointTrajectory conversion
  * Improve DEBUG output in TEM
  * Comment RobotTrajectory test
  * add acceleration to avoid out of bounds read
  ---------
  Co-authored-by: Paul Gesel<EMAIL_ADDRESS>  Co-authored-by: Abishalini Sivaraman<EMAIL_ADDRESS>  Co-authored-by: Ezra Brooks<EMAIL_ADDRESS>* Skip flaky PSM launch test (#2822 <https://github.com/moveit/moveit2/issues/2822>)
* change default to 1e308 (#2801 <https://github.com/moveit/moveit2/issues/2801>)
* PSM: keep references to scene_ valid upon receiving full scenes (#2745 <https://github.com/moveit/moveit2/issues/2745>)
  plan_execution-related modules rely on plan.planning_scene_ in many places
  to point to the currently monitored scene (or a diff on top of it).
  Before this patch, if the PSM would receive full scenes during execution,
  plan.planning_scene_ would not include later incremental updates anymore
  because the monitor created a new diff scene.
  ---------
  Co-authored-by: v4hn<EMAIL_ADDRESS>* Unify log names (#2720 <https://github.com/moveit/moveit2/issues/2720>)
  Co-authored-by: Abishalini Sivaraman<EMAIL_ADDRESS>* Print links in collision (#2727 <https://github.com/moveit/moveit2/issues/2727>)
* Do not overwrite the error code in planWithSinglePipeline (#2723 <https://github.com/moveit/moveit2/issues/2723>)
  * Do not overwrite the error code in planWithSinglePipeline
  Return the MotionPlanResponse as-is.
  * Do not rely on generatePlan() to set error code
  Do not rely on generatePlan() to set the error code in all cases and
  ensure that the error code is set to FAILURE if generatePlan() returns
  false.
   Before this, break was used to exit the
  current loop of request adapters, planners, or response adapters, but
  the function continued to the next loop. For example, if a planner would
  fail, the response adapters would still be executed.
  Co-authored-by: Gaël Écorchard<EMAIL_ADDRESS>* srdf publisher node (#2682 <https://github.com/moveit/moveit2/issues/2682>)
* CMake format and lint in pre-commit (#2683 <https://github.com/moveit/moveit2/issues/2683>)
* Get robot description from topic in GetUrdfService (#2681 <https://github.com/moveit/moveit2/issues/2681>)
* Shut down PSM publishing before starting to publish on a potentially new topic (#2680 <https://github.com/moveit/moveit2/issues/2680>)
* Contributors: Abishalini Sivaraman, Ezra Brooks, Gaël Écorchard, Henning Kayser, Matthijs van der Burgh, Paul Gesel, Robert Haschke, Sebastian Castro, Sebastian Jahr, Tyler Weaver

moveit_ros_planning_interface
* Apply clang-tidy fixes
* Migrate ros-planning org to moveit (#2847 <https://github.com/moveit/moveit2/issues/2847>)
  * Rename github.com/ros-planning -> github.com/moveit
  * Rename ros-planning.github.io -> moveit.github.io
  * Rename ros-planning organization in docker and CI workflow files
  - ghcr.io/ros-planning -> ghcr.io/moveit
  - github.repository == 'moveit/*''
* Add getNodeHandle impl (#2840 <https://github.com/moveit/moveit2/issues/2840>)
  Co-authored-by: Sebastian Jahr<EMAIL_ADDRESS>* Unify log names (#2720 <https://github.com/moveit/moveit2/issues/2720>)
  Co-authored-by: Abishalini Sivaraman<EMAIL_ADDRESS>* Add parameter api integration test (#2662 <https://github.com/moveit/moveit2/issues/2662>)
* CMake format and lint in pre-commit (#2683 <https://github.com/moveit/moveit2/issues/2683>)
* Remove unused python content from planning interface directory (#2665 <https://github.com/moveit/moveit2/issues/2665>)
  * Remove unused python content from planning interface directory
  * Cleanup test cmake
* Contributors: Robert Haschke, Sebastian Jahr, Tyler Weaver, methylDragon

moveit_ros_robot_interaction
* Migrate ros-planning org to moveit (#2847 <https://github.com/moveit/moveit2/issues/2847>)
  * Rename github.com/ros-planning -> github.com/moveit
  * Rename ros-planning.github.io -> moveit.github.io
  * Rename ros-planning organization in docker and CI workflow files
  - ghcr.io/ros-planning -> ghcr.io/moveit
  - github.repository == 'moveit/*''
* Unify log names (#2720 <https://github.com/moveit/moveit2/issues/2720>)
  Co-authored-by: Abishalini Sivaraman<EMAIL_ADDRESS>* CMake format and lint in pre-commit (#2683 <https://github.com/moveit/moveit2/issues/2683>)
* Contributors: Robert Haschke, Sebastian Jahr, Tyler Weaver

moveit_ros_tests
* Migrate ros-planning org to moveit (#2847 <https://github.com/moveit/moveit2/issues/2847>)
  * Rename github.com/ros-planning -> github.com/moveit
  * Rename ros-planning.github.io -> moveit.github.io
  * Rename ros-planning organization in docker and CI workflow files
  - ghcr.io/ros-planning -> ghcr.io/moveit
  - github.repository == 'moveit/*''
* Add parameter api integration test (#2662 <https://github.com/moveit/moveit2/issues/2662>)
* Contributors: Robert Haschke, Sebastian Jahr
* Migrate ros-planning org to moveit (#2847 <https://github.com/moveit/moveit2/issues/2847>)
  * Rename github.com/ros-planning -> github.com/moveit
  * Rename ros-planning.github.io -> moveit.github.io
  * Rename ros-planning organization in docker and CI workflow files
  - ghcr.io/ros-planning -> ghcr.io/moveit
  - github.repository == 'moveit/*''
* Add parameter api integration test (#2662 <https://github.com/moveit/moveit2/issues/2662>)
* Contributors: Robert Haschke, Sebastian Jahr

moveit_ros_visualization
* Migrate ros-planning org to moveit (#2847 <https://github.com/moveit/moveit2/issues/2847>)
  * Rename github.com/ros-planning -> github.com/moveit
  * Rename ros-planning.github.io -> moveit.github.io
  * Rename ros-planning organization in docker and CI workflow files
  - ghcr.io/ros-planning -> ghcr.io/moveit
  - github.repository == 'moveit/*''
* Unify log names (#2720 <https://github.com/moveit/moveit2/issues/2720>)
  Co-authored-by: Abishalini Sivaraman<EMAIL_ADDRESS>* CMake format and lint in pre-commit (#2683 <https://github.com/moveit/moveit2/issues/2683>)
* Contributors: Henning Kayser, Robert Haschke, Sebastian Jahr, Tyler Weaver

moveit_ros_warehouse
* Migrate ros-planning org to moveit (#2847 <https://github.com/moveit/moveit2/issues/2847>)
  * Rename github.com/ros-planning -> github.com/moveit
  * Rename ros-planning.github.io -> moveit.github.io
  * Rename ros-planning organization in docker and CI workflow files
  - ghcr.io/ros-planning -> ghcr.io/moveit
  - github.repository == 'moveit/*''
* Unify log names (#2720 <https://github.com/moveit/moveit2/issues/2720>)
  Co-authored-by: Abishalini Sivaraman<EMAIL_ADDRESS>* CMake format and lint in pre-commit (#2683 <https://github.com/moveit/moveit2/issues/2683>)
* Contributors: Robert Haschke, Sebastian Jahr, Tyler Weaver

moveit_runtime
* CMake format and lint in pre-commit (#2683 <https://github.com/moveit/moveit2/issues/2683>)
* Contributors: Tyler Weaver

moveit_servo
* Migrate ros-planning org to moveit (#2847 <https://github.com/moveit/moveit2/issues/2847>)
  * Rename github.com/ros-planning -> github.com/moveit
  * Rename ros-planning.github.io -> moveit.github.io
  * Rename ros-planning organization in docker and CI workflow files
  - ghcr.io/ros-planning -> ghcr.io/moveit
  - github.repository == 'moveit/*''
* remove intraprocess comm warning (#2752 <https://github.com/moveit/moveit2/issues/2752>)
* Fix error message text in servo.cpp (#2769 <https://github.com/moveit/moveit2/issues/2769>)
* Fix launch parameters in Servo demos (#2735 <https://github.com/moveit/moveit2/issues/2735>)
  Co-authored-by: Sebastian Jahr<EMAIL_ADDRESS>* [Servo] Fix collision checking with attached objects (#2747 <https://github.com/moveit/moveit2/issues/2747>)
* Unify log names (#2720 <https://github.com/moveit/moveit2/issues/2720>)
  Co-authored-by: Abishalini Sivaraman<EMAIL_ADDRESS>* CMake format and lint in pre-commit (#2683 <https://github.com/moveit/moveit2/issues/2683>)
* Attempt to use SCHED_FIFO for Servo regardless of RT kernel (#2653 <https://github.com/moveit/moveit2/issues/2653>)
  * Attempt to use SCHED_FIFO for Servo regardless of RT kernel
  * Update warning message if Servo fails to use SCHED_FIFO
  Co-authored-by: AndyZe<EMAIL_ADDRESS>  * Update moveit_ros/moveit_servo/src/servo_node.cpp
  Co-authored-by: Sebastian Castro<EMAIL_ADDRESS>  ---------
  Co-authored-by: AndyZe<EMAIL_ADDRESS>  Co-authored-by: Sebastian Castro<EMAIL_ADDRESS>* Acceleration Limited Smoothing Plugin for Servo (#2651 <https://github.com/moveit/moveit2/issues/2651>)
* Contributors: Marc Bestmann, Nathan Brooks, Paul Gesel, Robert Haschke, Sebastian Castro, Sebastian Jahr, Stephanie Eng, Tyler Weaver

moveit_setup_app_plugins
* CMake format and lint in pre-commit (#2683 <https://github.com/moveit/moveit2/issues/2683>)
* Contributors: Tyler Weaver

moveit_setup_assistant
* Migrate ros-planning org to moveit (#2847 <https://github.com/moveit/moveit2/issues/2847>)
  * Rename github.com/ros-planning -> github.com/moveit
  * Rename ros-planning.github.io -> moveit.github.io
  * Rename ros-planning organization in docker and CI workflow files
  - ghcr.io/ros-planning -> ghcr.io/moveit
  - github.repository == 'moveit/*''
* Add dependency on moveit_configs_utils to moveit_setup_assistant (#2832 <https://github.com/moveit/moveit2/issues/2832>)
* CMake format and lint in pre-commit (#2683 <https://github.com/moveit/moveit2/issues/2683>)
* Contributors: Robert Haschke, Tyler Weaver, hacker1024

moveit_setup_controllers
* Add allow_nonzero_velocity_at_trajectory_end parameter to exported ros2_controllers config file (#2751 <https://github.com/moveit/moveit2/issues/2751>)
* CMake format and lint in pre-commit (#2683 <https://github.com/moveit/moveit2/issues/2683>)
* Contributors: Sebastian Castro, Tyler Weaver

moveit_setup_core_plugins
* CMake format and lint in pre-commit (#2683 <https://github.com/moveit/moveit2/issues/2683>)
* Contributors: Tyler Weaver

moveit_setup_framework
* Apply clang-tidy fixes
* Migrate ros-planning org to moveit (#2847 <https://github.com/moveit/moveit2/issues/2847>)
  * Rename github.com/ros-planning -> github.com/moveit
  * Rename ros-planning.github.io -> moveit.github.io
  * Rename ros-planning organization in docker and CI workflow files
  - ghcr.io/ros-planning -> ghcr.io/moveit
  - github.repository == 'moveit/*''
* Unify log names (#2720 <https://github.com/moveit/moveit2/issues/2720>)
  Co-authored-by: Abishalini Sivaraman<EMAIL_ADDRESS>* CMake format and lint in pre-commit (#2683 <https://github.com/moveit/moveit2/issues/2683>)
* Contributors: Robert Haschke, Sebastian Jahr, Tyler Weaver

moveit_setup_srdf_plugins
* Apply clang-tidy fixes
* Unify log names (#2720 <https://github.com/moveit/moveit2/issues/2720>)
  Co-authored-by: Abishalini Sivaraman<EMAIL_ADDRESS>* CMake format and lint in pre-commit (#2683 <https://github.com/moveit/moveit2/issues/2683>)
* Contributors: Robert Haschke, Sebastian Jahr, Tyler Weaver

moveit_simple_controller_manager
* Migrate ros-planning org to moveit (#2847 <https://github.com/moveit/moveit2/issues/2847>)
  * Rename github.com/ros-planning -> github.com/moveit
  * Rename ros-planning.github.io -> moveit.github.io
  * Rename ros-planning organization in docker and CI workflow files
  - ghcr.io/ros-planning -> ghcr.io/moveit
  - github.repository == 'moveit/*''
* Unify log names (#2720 <https://github.com/moveit/moveit2/issues/2720>)
* CMake format and lint in pre-commit (#2683 <https://github.com/moveit/moveit2/issues/2683>)
* Contributors: Robert Haschke, Sebastian Jahr, Tyler Weaver

pilz_industrial_motion_planner
* Apply clang-tidy fixes
* Migrate ros-planning org to moveit (#2847 <https://github.com/moveit/moveit2/issues/2847>)
  * Rename github.com/ros-planning -> github.com/moveit
  * Rename ros-planning.github.io -> moveit.github.io
  * Rename ros-planning organization in docker and CI workflow files
  - ghcr.io/ros-planning -> ghcr.io/moveit
  - github.repository == 'moveit/*''
* Unify log names (#2720 <https://github.com/moveit/moveit2/issues/2720>)
  Co-authored-by: Abishalini Sivaraman<EMAIL_ADDRESS>* Add parameter api integration test (#2662 <https://github.com/moveit/moveit2/issues/2662>)
* CMake format and lint in pre-commit (#2683 <https://github.com/moveit/moveit2/issues/2683>)
* Contributors: Robert Haschke, Sebastian Jahr, Tyler Weaver

pilz_industrial_motion_planner_testutils
* Migrate ros-planning org to moveit (#2847 <https://github.com/moveit/moveit2/issues/2847>)
  * Rename github.com/ros-planning -> github.com/moveit
  * Rename ros-planning.github.io -> moveit.github.io
  * Rename ros-planning organization in docker and CI workflow files
  - ghcr.io/ros-planning -> ghcr.io/moveit
  - github.repository == 'moveit/*''
* CMake format and lint in pre-commit (#2683 <https://github.com/moveit/moveit2/issues/2683>)
* Contributors: Robert Haschke, Tyler Weaver

Holding for Jazzy sync


[ANCHOR-704] Document user_action_required_by

Clean up deprecated amount_fee and update platform transaction schema
Add user_action_required_by to related RPC methods
NotifyInteractiveFlowCompletedRequest
NotifyTransactionOnHoldRequest
NotifyOffchainFundsPendingRequest
NotifyOffchainFundsAvailableRequest
RequestCustomerInfoUpdateRequest
RequestOffchainFundsRequest
RequestOnchainFundsRequest
RequestTrustRequest
Add use instruction in SEP-6 and SEP-24
platforms/anchor-platform/admin-guide/sep6/configuration.mdx
platforms/anchor-platform/admin-guide/sep24/configuration.mdx

Preview is available here:http://developers-pr857.previews.kube001.services.stellar-ops.com

There are 8 actions modified. But the PR has 148 files modified. Is that expected?

I think yarn api regenerated the API docs for SDP and Horizon. Can we remove those from the PR to make it easier to review?

Preview is available here:http://developers-pr857.previews.kube001.services.stellar-ops.com

Preview is available here:http://developers-pr857.previews.kube001.services.stellar-ops.com

There will me more files than just 8 because cleaning up amount_fee  from all existing rpc methos

Preview is available here:http://developers-pr857.previews.kube001.services.stellar-ops.com

We should not merge this PR before https://github.com/stellar/stellar-docs/pull/872
There's going to be a lot of merge conflicts as the result, and I think it's better to resolve conflicts here than there (it's already a huge change in Elliot's PR)

Preview is available here:http://developers-pr857.previews.kube001.services.stellar-ops.com

Closing this one to create a new PR to avoid mass merge


Use xcrun to determine the SDK path

An early change (https://github.com/ganelson/inweb/pull/7/files) had to do with changing the hardwired Xcode path to a hardwired CommandLineTools path. This isn't really better; you're supposed to do
xcrun -show-sdk-path

to determine the path. This allows for installing multiple SDKs on a single Mac, for example. This change does that.
I'm using the GNU Make $(shell) feature, which should be fine on all MacOS. The only hitch is that it's a shell command every time the Makefile is parsed. I don't think this is a big total, but I'm not familiar with what's going on under the hood. (Particularly in the big Inform test suite.)

If there were an inweb {shell} macro, that could run the xcrun command and generate the .mk files with the variable already set. That would avoid the speed problem (however much of a problem it is). I didn't see anything like that, though, and it's probably too fussy a feature to add.

Thanks for this. Yes, that seems exactly right, and gets around the awkward problem that the symlink to the current SDK used to be present on essentially all Macs, but now sometimes isn't - I ran into this on an M1 mini the other day. There's no significant issue with speed here: the speed-critical things in testing are not done by running individual makefiles per test (except for a handful of C project tests). I think it's better to run xcrun each time, in fact, rather than to bake the result into the make files, because then the user might need to remake all the make files every time Xcode is updated.


NotImplementedError: Cannot convert a symbolic Tensor to a numpy array

Please make sure that this is a bug. As per our
GitHub Policy,
we only address code/doc bugs, performance issues, feature requests and
build/installation issues on GitHub. tag:bug_template
System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): stock
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Debian 11
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device:
TensorFlow installed from (source or binary): source and binary
TensorFlow version (use command below): 2.5 and nightly
Python version: 3.9
Bazel version (if compiling from source): 3.7.2
GCC/Compiler version (if compiling from source): gcc11
CUDA/cuDNN version: NA
GPU model and memory: NA

Describe the current behavior
tf.reduce_mean fails on a ragged tensor with NotImplemeted exception (see full error below). It happens in graph (non-eager) mode only. Furthermore, it probably does not happen with order versions of Numpy (1.19.*) but it definitely happens on Numpy 1.20.3
Describe the expected behavior
It must calculate means.
Contributing

Do you want to contribute a PR? (yes/no): yes
Briefly describe your candidate solution(if contributing):

The current code does not catch this type of exception which is probably new in Numpy 1.20

Standalone code to reproduce the issue
Provide a reproducible test case that is the bare minimum necessary to generate
the problem. If possible, please share a link to Colab/Jupyter/any notebook.
Other info / logs Include any logs or source code that would be helpful to
diagnose the problem. If including tracebacks, please include the full
traceback. Large logs and files should be attached.
Following is the full error message.
NotImplementedError: in user code:

    /home/eli/virtenvs/tf_mkl/lib/python3.9/site-packages/tensorflow/python/keras/engine/training.py:869 train_function  *
        return step_function(self, iterator)
    /home/eli/virtenvs/tf_mkl/lib/python3.9/site-packages/tensorflow/python/keras/engine/training.py:859 step_function  **
        outputs = model.distribute_strategy.run(run_step, args=(data,))
    /home/eli/virtenvs/tf_mkl/lib/python3.9/site-packages/tensorflow/python/distribute/distribute_lib.py:1286 run
        return self._extended.call_for_each_replica(fn, args=args, kwargs=kwargs)
    /home/eli/virtenvs/tf_mkl/lib/python3.9/site-packages/tensorflow/python/distribute/distribute_lib.py:2849 call_for_each_replica
        return self._call_for_each_replica(fn, args, kwargs)
    /home/eli/virtenvs/tf_mkl/lib/python3.9/site-packages/tensorflow/python/distribute/distribute_lib.py:3632 _call_for_each_replica
        return fn(*args, **kwargs)
    /home/eli/virtenvs/tf_mkl/lib/python3.9/site-packages/tensorflow/python/keras/engine/training.py:852 run_step  **
        outputs = model.train_step(data)
    /home/eli/virtenvs/tf_mkl/lib/python3.9/site-packages/tensorflow/python/keras/engine/training.py:813 train_step
        self.optimizer.minimize(loss, self.trainable_variables, tape=tape)
    /home/eli/virtenvs/tf_mkl/lib/python3.9/site-packages/tensorflow/python/keras/optimizer_v2/optimizer_v2.py:539 minimize
        grads_and_vars = self._compute_gradients(
    /home/eli/virtenvs/tf_mkl/lib/python3.9/site-packages/tensorflow/python/keras/optimizer_v2/optimizer_v2.py:591 _compute_gradients
        grads_and_vars = self._get_gradients(tape, loss, var_list, grad_loss)
    /home/eli/virtenvs/tf_mkl/lib/python3.9/site-packages/tensorflow/python/keras/optimizer_v2/optimizer_v2.py:473 _get_gradients
        grads = tape.gradient(loss, var_list, grad_loss)
    /home/eli/virtenvs/tf_mkl/lib/python3.9/site-packages/tensorflow/python/eager/backprop.py:1084 gradient
        flat_grad = imperative_grad.imperative_grad(
    /home/eli/virtenvs/tf_mkl/lib/python3.9/site-packages/tensorflow/python/eager/imperative_grad.py:71 imperative_grad
        return pywrap_tfe.TFE_Py_TapeGradient(
    /home/eli/virtenvs/tf_mkl/lib/python3.9/site-packages/tensorflow/python/eager/backprop.py:159 _gradient_function
        return grad_fn(mock_op, *out_grads)
    /home/eli/virtenvs/tf_mkl/lib/python3.9/site-packages/tensorflow/python/ops/math_grad.py:522 _UnsortedSegmentSumGrad
        return _GatherDropNegatives(grad, op.inputs[1])[0], None, None
    /home/eli/virtenvs/tf_mkl/lib/python3.9/site-packages/tensorflow/python/ops/math_grad.py:488 _GatherDropNegatives
        array_ops.ones([array_ops.rank(gathered)
    /home/eli/virtenvs/tf_mkl/lib/python3.9/site-packages/tensorflow/python/util/dispatch.py:206 wrapper
        return target(*args, **kwargs)
    /home/eli/virtenvs/tf_mkl/lib/python3.9/site-packages/tensorflow/python/ops/array_ops.py:3216 ones
        output = _constant_if_small(one, shape, dtype, name)
    /home/eli/virtenvs/tf_mkl/lib/python3.9/site-packages/tensorflow/python/ops/array_ops.py:2900 _constant_if_small
        if np.prod(shape) < 1000:
    <__array_function__ internals>:5 prod

    /home/eli/virtenvs/tf_mkl/lib/python3.9/site-packages/numpy/core/fromnumeric.py:3030 prod
        return _wrapreduction(a, np.multiply, 'prod', axis, dtype, out,
    /home/eli/virtenvs/tf_mkl/lib/python3.9/site-packages/numpy/core/fromnumeric.py:87 _wrapreduction
        return ufunc.reduce(obj, axis, dtype, out, **passkwargs)
    /home/eli/virtenvs/tf_mkl/lib/python3.9/site-packages/tensorflow/python/framework/ops.py:867 __array__
        raise NotImplementedError(

    NotImplementedError: Cannot convert a symbolic Tensor (gradient_tape/tree_model/inner_node/RaggedReduceMean/RaggedReduceSum/sub:0) to a numpy array. This error may indicate that you're trying to pass a Tensor to a NumPy call, which is not supported

Closing this issue because very latest code has the fix already (merged just recently):
https://github.com/tensorflow/tensorflow/blob/b731fef171004dd30ce8fddf9ba24dad9af7dc31/tensorflow/python/ops/array_ops.py#L2902


Hang on standalone application exit

Hello,
thanks for integrating OSC to Unity, it works great. However I have noticed one issue and thought I might report it here. When using OSC in Editor it works as expected, but I am experiencing hang while trying to exit standalone application. In case I disable Event Receiver (and re-compile) I have no issues with app exit - therefore I assume it is related to OscJack. (Tested on Win10 & Unity 2020.1.1f1)

Thanks for reporting it. Could you provide the log file?
https://docs.unity3d.com/Manual/LogFiles.html

Sure, but I guess it doesn't contain any useful information.
Player.log

Hi, I just wanted to let you know (in case it might help you somehow) that I have tried to use OscServer class in order to handle incoming messages and disposing via
private void OnApplicationQuit()
{
    server.Dispose();
}

results in expected behavior.

I can't reproduce this issue on Unity 2020.1.13f1
I'm closing this issue ticket as "not reproducible". Please feel free to reopen it if it still reproduces.


Add privacy link and posts page link to UrlGenerator

Is your feature request related to a problem? Please describe.
It's not easy to remember the functions to get the privacy and blog page links.
Describe the solution you'd like
Methods added to the UrlGenerator class to make acessing these links simple. E.g. url()->privacyPolicy(), url()->postsPage().
There are other links that could be added, such as archives, tag, category pages.
Describe alternatives you've considered
Using the built in functions get_post_type_archive_link, get_privacy_policy_url.
Additional context
The built in functions are difficult to remember and not always consistent. Adding the "special" pages to the UrlGenerator class will solve these issues.

The blog posts page is not always,


Refactor button disabling with Stimulus value attribute

Value attributes are more reliable when button state changed by external Stimulus controller.

Hi @kirillplatonov
I came from the v2.2.2 release note and found the functionality of the disable/enable function seems to have become a purely UI change after this PR. Does this mean that users need to manually change the button's disabled state, rather than continuing to rely on the function in the button controller after this release?

The functionality should be the same. When the button is disabled we ignoring future clicks until it's enabled again: https://github.com/baoagency/polaris_view_components/blob/main/app/assets/javascripts/polaris_view_components/button_controller.js#L8
I updated preview for this feature to better demonstrate how it works. If it's not working for you then it's probably a bug.
https://polarisviewcomponents.org/lookbook/inspect/button/disable_with_actions
Changes in this PR must only improve the internal implementation to better work with external controller (eg when button state is managed by form controller and synchronized with App Bridge save bar).


Certain apps closed in a FancyZone zone open maximized

Microsoft PowerToys version
0.51.1
Running as admin

[X] Yes

Area(s) with issue?
FancyZones
Steps to reproduce
Win10 21H2 19044.1387. Two monitors; on my main monitor, I have three zones: left, center and right.
For inbox apps Microsoft Store, Camera, Calculator, Settings, Mail, Calendar, Alarms and Clock, Photos, and also Store apps OneNote, myTube!, Code Writer, Naturplay Calculator, Home Remote, Adobe Sketchbook, Ink Calendar. Does NOT affect Office, PWA's, Affinity Designer, Zoom, ArcGIS, and many other apps.
Open the app. Use FancyZones to fit the app into a zone or pair of adjacent zones. Close the app.
✔ Expected Behavior
App should open in that FancyZone zone only.
❌ Actual Behavior
[with "Move newly created windows to their last known zone" untoggled] App opens maximized. (Not fullscreen, just maximized.)
[with "Move newly created windows to their last known zone" toggled] App opens in rightmost two zones invariably (even if it was closed in only one zone, or in another pair of adjacent zones).
The issue does not appear if the app is resized in any way, or moved to be outside any FancyZone zone. In that case, closing the app and opening it again results in the app appearing exactly where you closed it as expected.
Other Software
No response

I can't repro this.  The list of apps look to be UWP apps.  I tried calculator and can't repro this on Win11 build 22515
can you do a screenshot of your FZ settings?
What is your OS build number?  (run prompt->WinVer)

Did you mean to close this out?

Apologies, my mistake. Reopening.

@SeraphimaZ i can't repro this.

Thank you again for looking into this. I have updated the original text of the issue with some more specifics. Hopefully that helps.

UWP apps process path sometimes can't be retrieved immediately so FZ doesn't recognize if the zoned window was opened and does nothing with it.
Retry loop helps (https://github.com/microsoft/PowerToys/pull/12284), but it can cause lags on switching with Alt-Tab (https://github.com/microsoft/PowerToys/pull/12860).
I’ll figure out a way to fix it.

This appears to be fixed in the latest release, guys (v0.59.1). Thanks for everything! UWP windows work perfectly now in W10.


[Refactor] Update user short link relation in Usecase

What is frustrating you?
When updating the alias of a short link, the relation of user short link is updated only because they are joint in postgres database but it is not updated in updater usecase
https://github.com/short-d/short/blob/b945aac5192b0f4bb674fd6dfdbdb7d7b1f05fd3/backend/app/usecase/shortlink/updater.go#L80-L81
Your solution
Update user short link relation in Usecase

Huh, good question. Not sure whether we have to manually do this.

A more detailed dissucion in issue #958.


[next branch] Failing migrations: backup/restore full instance?

I got failing migrations:
sqlalchemy.exc.ProgrammingError: (psycopg2.errors.DuplicateColumn) column "optimization_specification_id" of relation "neb_specification" already exists
[SQL: ALTER TABLE neb_specification ADD COLUMN optimization_specification_id INTEGER]

I think it's due to this file: https://github.com/MolSSI/QCFractal/blob/next/qcfractal/qcfractal/alembic/versions/2023-06-05-1638db43303c_enable_different_optimizations_in_neb.py. But to be confirmed cuz I haven't been able to reproduce it locally.
I don't have time to debug this currently, but I was wondering if maybe it would be nice to have an endpoint that allows to back up the full instance (at least records, molecules, dataset and specification).
It seems like a good tradeoff option versus raw SQL backup (that is still sensitive to migration failures).
The tricky part is to restore a record I guess, since those are usually sent by the managers.
Since everything is easily serializable with dict(), maybe it's not that a complex task?
Please let me know what you think @bennybp.

The raw SQL backup should be pretty stable. It uses the postgres standard tools. I wonder if you got caught in a commit with a bug that was later fixed?
You might have created the DB at 9bbb327035041b89096d41d20bec03dde32414dc, with the migration appearing later . So you had the columns already. (If so, apologies for that, that was pretty sloppy of me)

I wonder if you got caught in a commit with a bug that was later fixed?

You might have created the DB at 9bbb327035041b89096d41d20bec03dde32414dc, with the migration appearing later . So you had the columns already. (If so, apologies for that, that was pretty sloppy of me)

Yeah not sure. And no worry, I know it's still WIP, so I understand. For now, it's not an issue since we are still prototyping but I am trying to anticipate when we'll start generating actual data we want to keep.

The raw SQL backup should be pretty stable. It uses the postgres standard tools.

Yes I can always do that but it's still sensitive to db migrations right?

I'm not sure what you mean by sensitive to db migrations. If you upgrade QCFractal after a backup, then you should have to run upgrade-db after you restore from backup. But that would be true of any backup scheme.

Yes, indeed but the migration error I got was when using upgrade-db so as said, I can always backup the raw SQL, but that would not have fixed the original db migration issue.
I don't think it's a blocker right now for me and also probably only a one-time bug. So I will close here!

Oh yes, sorry about that. You are right this is likely just a one time thing (because you are on the bleeding edge).


Add generic-lens

I'm seeing this:
generic-lens-<IP_ADDRESS> (Csongor Kiss<EMAIL_ADDRESS>@kcsongor) is out of bounds for:

[ ] inspection-testing-0.1.1 (==<IP_ADDRESS>). No maintainer. @nomeata. Used by: test-suite

Is there perhaps a cyclic dependency going on here? We may need to skip tests for inspection-testing.

Yes, one of the examples in the inspection-testing package depends on generic-lens, which in turn depends on inspection-testing in the test-suite.
Is there a way to skip the generic-lens test in inspection-testing?

We can skip all tests in inspection-testing by adding it to the skipped-tests section in the build-constraints file. Can you update the PR?
To be clear, the problem isn't the cyclic dependency, but the restrictive upper bound.

Thanks for the explanation, I've updated the PR.

Is there a way to skip the generic-lens test in inspection-testing?

Now the problematic tests in inspection-testing are skipped by default.


View indicator

Is there anyway to add a view indicator to this to see what page you're on?
I can't find any code for it however all other views have them included

@grantwardle Hi
I thought that it was redundant feature, because everybody are able to add it himself
Because there are a lot of types of indicator (circle, square, some image... etc.)
But if you want, I can implement it =) It will be circles only

Circles are perfect, I can’t find any implementation fit them any where.
Grant Wardle
Chief Executive Officer
Newcastle-Under-Lyme • Staffordshire, United Kingdom
AWSCO
+44 78273 44868
+44 74022 77106
<EMAIL_ADDRESS>www.awsco.co.uk

On 21 Feb 2018, at 08:31, Andrei<EMAIL_ADDRESS>wrote:
@grantwardle Hi
I thought that it was redundant feature, because everybody are able to add it himself
Because there are a lot of types of indicator (circle, square, some image... etc.)
But if you want, I can implement it =) It will be circles only
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

@grantwardle Okay) I see
I will implement it soon, i hope. Then I contact you for getting feedback
Thanks for your reaction!

That’s great!
Thank you very much
Grant Wardle
Chief Executive Officer
Newcastle-Under-Lyme • Staffordshire, United Kingdom
AWSCO
+44 78273 44868
+44 74022 77106
<EMAIL_ADDRESS>www.awsco.co.uk

On 21 Feb 2018, at 11:00, Andrei<EMAIL_ADDRESS>wrote:
@grantwardle Okay) I see
I will implement it soon, i hope. Then I contact you for getting feedback
Thanks for your reaction!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

@grantwardle Hi)
I will push new version soon) You can check sample now, there is an update by your issue :)

Thank you very much!
Grant Wardle
Chief Executive Officer
Newcastle-Under-Lyme • Staffordshire, United Kingdom
AWSCO
+44 78273 44868
+44 74022 77106
<EMAIL_ADDRESS>www.awsco.co.uk

On 23 Feb 2018, at 17:06, Andrei<EMAIL_ADDRESS>wrote:
@grantwardle Hi)
I will push new version soon) You can check sample now, there is an update by your issue :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

@grantwardle
I updated package. Check version 1.3.0) Also look through Readme
if you like this package, please, set star on this repository) I will be grateful!


Routing Problem 30 sites visit maximum travel time is 10 hours a day each day vehicle goes back to depot atleast 30 minutes stop at one site.

I am a beginner with or-tools I am trying to solve a rather specific problem whereby I have one vehicle that does delivery to many sites within the month. maximum working day is 10 Hours and a stop at the site is of maximum 30 minutes each day after the 10 hours the vehicle goes back to depot and starts again eliminating the already visited sites from the matrix. please help

Please start reading the examples, the doc and ask for specific questions.


add adopters of autelrobotics

Signed-off-by: wangshulin<EMAIL_ADDRESS>
Ⅰ. Describe what this PR does
add adopters of autelrobotics
Ⅱ. Does this pull request fix one issue?

fixes #XXXX
Ⅲ. List the added test cases (unit test/integration test) if any, please explain if no tests are needed.
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

/lgtm
/approve


Add task counter

Task Counters are added:

total task counter: all tasks stored in database
listed task counter: count the tasks listed in ui
unfinished task counter: count the unfinished tasks stored in database
overdue task counter: count the overdue deadline tasks stored in database
today's remaining task counter: count the remaining deadlines and events for today

@pyokagan Please help me review this pr again, thanks!

@pyokagan Can this pr be merged?

@pyokagan revision done already

Merged as 3e6828bb6ab745503bd3185af801594ef58c0f6a


Raise a runtime error if any supplied priority_countries are not in the main list

Without this, it's easy to end up with messy data if one (ahem) accidentally includes "USA" in priority_countries instead of "United States"...

 Bear with me, I'll re-do this request the old-fashioned way.

There, that's better; the first version of the commit just deleted every line in the file... sigh.

Good idea, thanks for this addition. I'll merge it in and push up an updated gem, hopefully a little later.

Good idea, thanks for this addition. I'll merge it in and push up an updated gem, hopefully a little later.


The "Get started" window opens on system start

It's better to have the application only as a tray icon when it loads with the system starts.

I have been looking into it. Some issue with electron AutoLaunch. You are welcome to find a solution and create a PR.

This Line corresponds to the AutoLaunch option that seems to have the bug. I have tried a workaround here but it's not tested yet.


Vienna 3.8 beta – Applescript: cannot get HTML source

A basic applescript using get documentHTMLSource to open the HTML source of an article in a code editor fails (per the Vienna AS dictionary).
Result: the script opens a blank document. This fails independently of the “new“ browser (WKWebView). It worked fine in 3.7.x.
The following script opens the HTML source in a new BBEdit document (I have a similar one for SubEthaEdit).
tell application "Vienna"
	set this_source to get documentHTMLSource
	tell application "BBEdit"
		activate
		make new text window with properties {text:this_source, source language:"HTML"}
		select insertion point before text of front text document
	end tell
end tell

PS – this is a bit annoying for debugging feeds as the Web inspector cannot be used in WKWebView, unless I miss a magic incantation. The Web inspector still works in the “old” browser.

I am not sure if the issue is due to a mistake in the Article View or due to the WebView behaving differently when a local document is loaded. It is not intentional.

hmm. Hopefully there is some sort of workaround?

For the Web Inspector,[…]Theoretically that could be made into a setting in Viennas Preferences.

Now that would be quite nice, I suspect I am not the only one who uses the inspector tool.

The web inspector within Vienna has never worked for me; it just overlays an opaque view onto the webview. I am not keen on exposing this to release builds.

Didn’t this command work for you ? (quit Vienna beforehand…)
defaults write uk.co.opencommunity.vienna2 WebKitDeveloperExtras -bool true
That has worked for a long time, and still does as long as you have the “old” browser enabled. Right click any element in article view, you’ll see the “Inspect element” entry in the context menu.

I have only tested it in developer builds with the WebKit (“new”) browser enabled. The WebKitDeveloperExtras default makes no difference.

Yes with WKWebView that command does not work (as alluded in my OP), lots of discussions on stackoverflow about that. That is why I turned back to my Old Applescript(s) only that does not work either (In Vienna; I have a AppleScript working with NNW).

I was merely pointing out that exposing the web inspector private API via a toggle in advanced preferences, as suggested by TAKeanice, is not an option. Instead, the AppleScript function documentHTMLSource has to be fixed, so that it also returns the page source of the article, as it does in Vienna 3.7 and older.

For me, access to debugging is possible through Safari's Development menu.
Once this menu is activated (cf. Safari's advanced preferences), a submenu with your machine's name appears into it : Vienna's tab are listed there and can be selected.
You probably also need the defaults write uk.co.opencommunity.vienna2 WebKitDeveloperExtras -bool true command beforehand.

this is still relevant, FWIW

This will be fixed in 3.9.0, at least for recent versions macOS Ventura (commit e0f288b2ed57ec5e486300a2b3555bc57fe2c000 included in PR #1666)


MAINT: special: array API dispatch follow-up

gh-19023 added support for alternative backends to some special functions. We discussed in the PR that a few items would need to be resolved in follow-up work:

The wrapped functions are no longer ufuncs. It is not documented that these functions were ufuncs, but nonetheless, users may be relying on this behavior. What should we do about that?
There is no documentation of the Array API compatibility. Something needs to be added.

Marking with 1.12 milestone because we should consider whether it is ok for gh-19023 should be included in a release before these items have been addressed. (It might be fine, but it should be an explicit decision.)
Once these issues are addressed, we could consider enabling Array API support without the environment variable. (We still might want to require it, but that should be an explicit decision, too.)
Of course, we also want to open an Array API extension proposal and add support for more functions, but those ideas don't need to be tracked here.

@rgommers how do you want the ufunc issue to be addressed? Start with an email to the mailing list?

fyi, I think he may be on vacation for a little bit

There is no documentation of the Array API compatibility. Something needs to be added.

whereabouts would this live? Are you thinking of https://scipy.github.io/devdocs/tutorial/special.html? If so, the same is needed for fft and cluster at some point. Or just an update to https://scipy.github.io/devdocs/dev/api-dev/array_api.html? In any case I think what we have so far is sufficient for 1.12 considering everything is marked as experimental.

The wrapped functions are no longer ufuncs. It is not documented that these functions were ufuncs, but nonetheless, users may be relying on this behavior. What should we do about that?

Mailing list thread for reference
The conclusion from the mailing list seems to be (from Ralf):

We reserve the right to move functions to being ufuncs, and we should also reserve the right to move them away from it

I believe functions in special being ufuncs yes or no is mostly leaking of implementation details - using the ufunc machinery was nice and performant, but quite a few of the methods don't really make sense as Albert points out

I'd be inclined to keep only the few methods that are actually useful, and not the whole API surface of ufuncs. The not so useful methods and attributes can be deprecated first in a wrapper. Finally, a wrapper would also help fix the issues with using inspect.signature, inspect.isroutine & co, and attributes like __module__

There wasn't a clear consensus though so maybe a bit more discussion is needed. If we do go ahead with this, https://scipy.github.io/devdocs/reference/special.html#special-functions-scipy-special needs to be updated to clarify that it is no longer true that they are "technically" ufuncs.
@mdhaber @rgommers should I open a PR to remove the ufuncs line from the docs for 1.12? Then we can open an issue for the deprecation process (unless more discussion is needed first).

whereabouts would this live?

The tutorial, array API documentation, and the special API docs are all good places. Most importantly (I think), if we deprecate the unnecessary ufunc-ness and make these regular functions, then we can add to the function-specific documentation. The decorator approach was working fine except for the ufunc hiccup.

should I open a PR to remove the ufuncs line from the docs for 1.12? Then we can open an issue for the deprecation process (unless more discussion is needed first).

I don't think it's essential for 1.12. After all, the release notes are explicit about array API support being experimental and encouraging testing. If users fine out the hard way that ufuncness is broken, they're more likely to report it. As for deprecation discussion, putting together a way of collecting feedback about which ufunc features should be retained would move that along.

There is no documentation of the Array API compatibility. Something needs to be added.

There is a decent amount of documentation at http://scipy.github.io/devdocs/dev/api-dev/array_api.html. I'd say that that is the right place for now. I would not add it to the tutorials for individual submodules. Once we think it's time, we need one central place in the user-facing docs that explains everything. There should not be differences in behavior between different submodules, so starting to explain in per-submodule docs seems like it will be messy and lead to duplication.

I don't think it's essential for 1.12. After all, the release notes are explicit about array API support being experimental and encouraging testing. If users fine out the hard way that ufuncness is broken, they're more likely to report it. As for deprecation discussion, putting together a way of collecting feedback about which ufunc features should be retained would move that along.

Agreed with this.

Just removing the milestone here - there is relevant discussion about the ufunc changes, but nothing that needs to worry us before we start considering moving out of an experimental env variable


v1.4.3 to v1.5.1 upgrade results in Operations Deployment failure

Describe the bug
After upgrading from LZA v1.4.3 to v1.5.0 and now 1.5.1, the Operations step in the Deploy stage fails while performing sso:UpdatePermissionSet using the arn:aws:sts::012345678901:assumed-role/AWSControlTowerExecution/cdk-assume-role-plugin role.
The assumed AWSControlTowerExecution role within the account that is failing (the Control Tower Audit account)  has the AdministratorAccess policy and no PermissionSets attached.
Log Excerpt
AWSAccelerator-OperationsStack-012345678901-us-east-1 |  5/27 | 5:42:21 PM | UPDATE_COMPLETE      | AWS::Logs::LogGroup          | Custom::SsmGetParameterValueCustomResourceProviderLogGroup (CustomSsmGetParameterValueCustomResourceProviderLogGroup780D220D)
AWSAccelerator-OperationsStack-012345678901-us-east-1 |  6/27 | 5:42:21 PM | UPDATE_COMPLETE      | AWS::IAM::Role               | AssetAccessRole012345678901 (AssetAccessRole0123456789016C7363D4)
AWSAccelerator-OperationsStack-012345678901-us-east-1 |  7/27 | 5:42:22 PM | UPDATE_COMPLETE      | AWS::IAM::Role               | ServiceCatalogPropagationRole (ServiceCatalogPropagationRole17EC5FCF)
AWSAccelerator-OperationsStack-012345678901-us-east-1 |  7/27 | 5:42:22 PM | UPDATE_IN_PROGRESS   | Custom::SsmGetParameterValue | AssetsBucketKms/Lookup/Resource/Default (AssetsBucketKmsLookup24313A2E)
AWSAccelerator-OperationsStack-012345678901-us-east-1 |  8/27 | 5:42:22 PM | UPDATE_COMPLETE      | AWS::IAM::Role               | StackSetExecutionRole (StackSetExecutionRole02DBF677)
AWSAccelerator-OperationsStack-012345678901-us-east-1 |  9/27 | 5:42:23 PM | UPDATE_COMPLETE      | AWS::SSO::PermissionSet      | AdministratorAccessIdentityCenterPermissionSet
AWSAccelerator-OperationsStack-012345678901-us-east-1 |  9/27 | 5:42:24 PM | UPDATE_IN_PROGRESS   | AWS::SSO::PermissionSet      | ReadOnlyAccessIdentityCenterPermissionSet
AWSAccelerator-OperationsStack-012345678901-us-east-1 |  9/27 | 5:42:25 PM | UPDATE_FAILED        | AWS::SSO::PermissionSet      | ReadOnlyAccessIdentityCenterPermissionSet Resource handler returned message: "User: arn:aws:sts::012345678901:assumed-role/AWSControlTowerExecution/cdk-assume-role-plugin is not authorized to perform: sso:UpdatePermissionSet on resource: arn:aws:sso:::permissionSet/ssoins-obfuscatedID563e/ps-obfuscatedID77a4 (Service: SsoAdmin, Status Code: 400, Request ID: b0cd6fb2-37f1-4d20-af94-eda630a76579)" (RequestToken: 9f0a65e6-6664-4d21-9761-89c6ade22341, HandlerErrorCode: GeneralServiceException)
    OperationsStack.createPermissionsSet (/codebuild/output/src1719/src/s3/00/source/packages/@aws-accelerator/accelerator/lib/stacks/operations-stack.ts:993:27)
    \_ OperationsStack.addIdentityCenterPermissionSets (/codebuild/output/src1719/src/s3/00/source/packages/@aws-accelerator/accelerator/lib/stacks/operations-stack.ts:851:34)
    \_ OperationsStack.addIdentityCenterResources (/codebuild/output/src1719/src/s3/00/source/packages/@aws-accelerator/accelerator/lib/stacks/operations-stack.ts:1122:40)
    \_ new OperationsStack (/codebuild/output/src1719/src/s3/00/source/packages/@aws-accelerator/accelerator/lib/stacks/operations-stack.ts:134:12)
    \_ createOperationsStack (/codebuild/output/src1719/src/s3/00/source/packages/@aws-accelerator/accelerator/utils/stack-utils.ts:734:29)
    \_ createMultiAccountMultiRegionStacks (/codebuild/output/src1719/src/s3/00/source/packages/@aws-accelerator/accelerator/bin/app.ts:172:28)
    \_ main (/codebuild/output/src1719/src/s3/00/source/packages/@aws-accelerator/accelerator/bin/app.ts:232:5)
    \_ processTicksAndRejections (node:internal/process/task_queues:96:5)
    \_ async /codebuild/output/src1719/src/s3/00/source/packages/@aws-accelerator/accelerator/bin/app.ts:240:5
AWSAccelerator-OperationsStack-012345678901-us-east-1 |  9/27 | 5:42:25 PM | UPDATE_FAILED        | Custom::SsmGetParameterValue | AssetsBucketKms/Lookup/Resource/Default (AssetsBucketKmsLookup24313A2E) Resource update cancelled
    new CustomResource (/codebuild/output/src1719/src/s3/00/source/node_modules/aws-cdk-lib/core/lib/custom-resource.js:1:823)
    \_ new SsmParameterLookup (/codebuild/output/src1719/src/s3/00/source/packages/@aws-accelerator/constructs/lib/aws-ssm/ssm-parameter-lookup.ts:92:22)
    \_ new KeyLookup (/codebuild/output/src1719/src/s3/00/source/packages/@aws-accelerator/constructs/lib/aws-kms/key-lookup.ts:71:16)
    \_ OperationsStack.lookupAssetBucketKmsKey (/codebuild/output/src1719/src/s3/00/source/packages/@aws-accelerator/accelerator/lib/stacks/operations-stack.ts:1179:14)
    \_ new OperationsStack (/codebuild/output/src1719/src/s3/00/source/packages/@aws-accelerator/accelerator/lib/stacks/operations-stack.ts:120:36)
    \_ createOperationsStack (/codebuild/output/src1719/src/s3/00/source/packages/@aws-accelerator/accelerator/utils/stack-utils.ts:734:29)
    \_ createMultiAccountMultiRegionStacks (/codebuild/output/src1719/src/s3/00/source/packages/@aws-accelerator/accelerator/bin/app.ts:172:28)
    \_ main (/codebuild/output/src1719/src/s3/00/source/packages/@aws-accelerator/accelerator/bin/app.ts:232:5)
    \_ processTicksAndRejections (node:internal/process/task_queues:96:5)
    \_ async /codebuild/output/src1719/src/s3/00/source/packages/@aws-accelerator/accelerator/bin/app.ts:240:5
AWSAccelerator-OperationsStack-012345678901-us-east-1 |  9/27 | 5:42:26 PM | UPDATE_ROLLBACK_IN_P | AWS::CloudFormation::Stack   | AWSAccelerator-OperationsStack-012345678901-us-east-1 The following resource(s) failed to update: [ReadOnlyAccessIdentityCenterPermissionSet, AssetsBucketKmsLookup24313A2E].
AWSAccelerator-OperationsStack-012345678901-us-east-1 |  9/27 | 5:42:29 PM | UPDATE_IN_PROGRESS   | AWS::SSM::Parameter          | SsmParamAcceleratorVersion (SsmParamAcceleratorVersionFF83282D)
AWSAccelerator-OperationsStack-012345678901-us-east-1 |  9/27 | 5:42:29 PM | UPDATE_IN_PROGRESS   | AWS::IAM::Role               | StackSetExecutionRole (StackSetExecutionRole02DBF677)
AWSAccelerator-OperationsStack-012345678901-us-east-1 |  9/27 | 5:42:29 PM | UPDATE_IN_PROGRESS   | AWS::Lambda::Function        | Custom::SsmGetParameterValueCustomResourceProvider/Handler (CustomSsmGetParameterValueCustomResourceProviderHandlerAAD0E7EE)
AWSAccelerator-OperationsStack-012345678901-us-east-1 |  9/27 | 5:42:29 PM | UPDATE_IN_PROGRESS   | AWS::IAM::Role               | AssetAccessRole012345678901 (AssetAccessRole0123456789016C7363D4)
AWSAccelerator-OperationsStack-012345678901-us-east-1 |  9/27 | 5:42:29 PM | UPDATE_IN_PROGRESS   | AWS::IAM::Role               | ServiceCatalogPropagationRole (ServiceCatalogPropagationRole17EC5FCF)
AWSAccelerator-OperationsStack-012345678901-us-east-1 |  9/27 | 5:42:29 PM | UPDATE_IN_PROGRESS   | AWS::SSM::Parameter          | SsmParamStackId (SsmParamStackId521A78D3)
AWSAccelerator-OperationsStack-012345678901-us-east-1 |  8/27 | 5:42:29 PM | UPDATE_COMPLETE      | AWS::SSM::Parameter          | SsmParamAcceleratorVersion (SsmParamAcceleratorVersionFF83282D)
AWSAccelerator-OperationsStack-012345678901-us-east-1 |  7/27 | 5:42:30 PM | UPDATE_COMPLETE      | AWS::SSM::Parameter          | SsmParamStackId (SsmParamStackId521A78D3)
AWSAccelerator-OperationsStack-012345678901-us-east-1 |  8/27 | 5:42:31 PM | UPDATE_COMPLETE      | AWS::SSO::PermissionSet      | ReadOnlyAccessIdentityCenterPermissionSet
AWSAccelerator-OperationsStack-012345678901-us-east-1 |  8/27 | 5:42:31 PM | UPDATE_IN_PROGRESS   | AWS::SSO::PermissionSet      | PortalProjectMerkleTeamIdentityCenterPermissionSet
AWSAccelerator-OperationsStack-012345678901-us-east-1 |  8/27 | 5:42:32 PM | UPDATE_IN_PROGRESS   | AWS::SSO::PermissionSet      | AdministratorAccessIdentityCenterPermissionSet
AWSAccelerator-OperationsStack-012345678901-us-east-1 |  7/27 | 5:42:39 PM | UPDATE_COMPLETE      | AWS::SSO::PermissionSet      | AdministratorAccessIdentityCenterPermissionSet
AWSAccelerator-OperationsStack-012345678901-us-east-1 |  6/27 | 5:42:39 PM | UPDATE_COMPLETE      | AWS::SSO::PermissionSet      | PortalProjectMerkleTeamIdentityCenterPermissionSet
AWSAccelerator-OperationsStack-012345678901-us-east-1 |  5/27 | 5:42:41 PM | UPDATE_COMPLETE      | AWS::Lambda::Function        | Custom::SsmGetParameterValueCustomResourceProvider/Handler (CustomSsmGetParameterValueCustomResourceProviderHandlerAAD0E7EE)
AWSAccelerator-OperationsStack-012345678901-us-east-1 |  5/27 | 5:42:42 PM | UPDATE_IN_PROGRESS   | AWS::Logs::LogGroup          | Custom::SsmGetParameterValueCustomResourceProviderLogGroup (CustomSsmGetParameterValueCustomResourceProviderLogGroup780D220D)
AWSAccelerator-OperationsStack-012345678901-us-east-1 |  4/27 | 5:42:43 PM | UPDATE_COMPLETE      | AWS::Logs::LogGroup          | Custom::SsmGetParameterValueCustomResourceProviderLogGroup (CustomSsmGetParameterValueCustomResourceProviderLogGroup780D220D)
AWSAccelerator-OperationsStack-012345678901-us-east-1 |  4/27 | 5:42:43 PM | UPDATE_IN_PROGRESS   | Custom::SsmGetParameterValue | AssetsBucketKms/Lookup/Resource/Default (AssetsBucketKmsLookup24313A2E)
AWSAccelerator-OperationsStack-012345678901-us-east-1 |  3/27 | 5:42:45 PM | UPDATE_COMPLETE      | AWS::IAM::Role               | AssetAccessRole012345678901 (AssetAccessRole0123456789016C7363D4)
AWSAccelerator-OperationsStack-012345678901-us-east-1 |  2/27 | 5:42:45 PM | UPDATE_COMPLETE      | AWS::IAM::Role               | StackSetExecutionRole (StackSetExecutionRole02DBF677)
AWSAccelerator-OperationsStack-012345678901-us-east-1 |  1/27 | 5:42:45 PM | UPDATE_COMPLETE      | AWS::IAM::Role               | ServiceCatalogPropagationRole (ServiceCatalogPropagationRole17EC5FCF)
AWSAccelerator-OperationsStack-012345678901-us-east-1 |  2/27 | 5:42:50 PM | UPDATE_COMPLETE      | Custom::SsmGetParameterValue | AssetsBucketKms/Lookup/Resource/Default (AssetsBucketKmsLookup24313A2E)
AWSAccelerator-OperationsStack-012345678901-us-east-1 |  3/27 | 5:42:51 PM | UPDATE_ROLLBACK_COMP | AWS::CloudFormation::Stack   | AWSAccelerator-OperationsStack-012345678901-us-east-1
AWSAccelerator-OperationsStack-012345678901-us-east-1 |  4/27 | 5:42:51 PM | UPDATE_ROLLBACK_COMP | AWS::CloudFormation::Stack   | AWSAccelerator-OperationsStack-012345678901-us-east-1

Failed resources:
AWSAccelerator-OperationsStack-012345678901-us-east-1 | 5:42:25 PM | UPDATE_FAILED        | AWS::SSO::PermissionSet      | ReadOnlyAccessIdentityCenterPermissionSet Resource handler returned message: "User: arn:aws:sts::012345678901:assumed-role/AWSControlTowerExecution/cdk-assume-role-plugin is not authorized to perform: sso:UpdatePermissionSet on resource: arn:aws:sso:::permissionSet/ssoins-obfuscatedID563e/ps-obfuscatedID77a4 (Service: SsoAdmin, Status Code: 400, Request ID: b0cd6fb2-37f1-4d20-af94-eda630a76579)" (RequestToken: 9f0a65e6-6664-4d21-9761-89c6ade22341, HandlerErrorCode: GeneralServiceException)
    OperationsStack.createPermissionsSet (/codebuild/output/src1719/src/s3/00/source/packages/@aws-accelerator/accelerator/lib/stacks/operations-stack.ts:993:27)
    \_ OperationsStack.addIdentityCenterPermissionSets (/codebuild/output/src1719/src/s3/00/source/packages/@aws-accelerator/accelerator/lib/stacks/operations-stack.ts:851:34)
    \_ OperationsStack.addIdentityCenterResources (/codebuild/output/src1719/src/s3/00/source/packages/@aws-accelerator/accelerator/lib/stacks/operations-stack.ts:1122:40)
    \_ new OperationsStack (/codebuild/output/src1719/src/s3/00/source/packages/@aws-accelerator/accelerator/lib/stacks/operations-stack.ts:134:12)
    \_ createOperationsStack (/codebuild/output/src1719/src/s3/00/source/packages/@aws-accelerator/accelerator/utils/stack-utils.ts:734:29)
    \_ createMultiAccountMultiRegionStacks (/codebuild/output/src1719/src/s3/00/source/packages/@aws-accelerator/accelerator/bin/app.ts:172:28)
    \_ main (/codebuild/output/src1719/src/s3/00/source/packages/@aws-accelerator/accelerator/bin/app.ts:232:5)
    \_ processTicksAndRejections (node:internal/process/task_queues:96:5)
    \_ async /codebuild/output/src1719/src/s3/00/source/packages/@aws-accelerator/accelerator/bin/app.ts:240:5

 ❌  AWSAccelerator-OperationsStack-012345678901-us-east-1 failed: Error: The stack named AWSAccelerator-OperationsStack-012345678901-us-east-1 failed to deploy: UPDATE_ROLLBACK_COMPLETE: Resource handler returned message: "User: arn:aws:sts::012345678901:assumed-role/AWSControlTowerExecution/cdk-assume-role-plugin is not authorized to perform: sso:UpdatePermissionSet on resource: arn:aws:sso:::permissionSet/ssoins-obfuscatedID563e/ps-obfuscatedID77a4 (Service: SsoAdmin, Status Code: 400, Request ID: b0cd6fb2-37f1-4d20-af94-eda630a76579)" (RequestToken: 9f0a65e6-6664-4d21-9761-89c6ade22341, HandlerErrorCode: GeneralServiceException)
    at FullCloudFormationDeployment.monitorDeployment (/codebuild/output/src1719/src/s3/00/source/node_modules/aws-cdk/lib/api/deploy-stack.ts:512:13)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async Object.deployStack (/codebuild/output/src1719/src/s3/00/source/node_modules/aws-cdk/lib/cdk-toolkit.ts:287:24)
    at async /codebuild/output/src1719/src/s3/00/source/node_modules/aws-cdk/lib/util/work-graph.ts:105:11

 ❌ Deployment failed: Error: The stack named AWSAccelerator-OperationsStack-012345678901-us-east-1 failed to deploy: UPDATE_ROLLBACK_COMPLETE: Resource handler returned message: "User: arn:aws:sts::012345678901:assumed-role/AWSControlTowerExecution/cdk-assume-role-plugin is not authorized to perform: sso:UpdatePermissionSet on resource: arn:aws:sso:::permissionSet/ssoins-obfuscatedID563e/ps-obfuscatedID77a4 (Service: SsoAdmin, Status Code: 400, Request ID: b0cd6fb2-37f1-4d20-af94-eda630a76579)" (RequestToken: 9f0a65e6-6664-4d21-9761-89c6ade22341, HandlerErrorCode: GeneralServiceException)
    at FullCloudFormationDeployment.monitorDeployment (/codebuild/output/src1719/src/s3/00/source/node_modules/aws-cdk/lib/api/deploy-stack.ts:512:13)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async Object.deployStack (/codebuild/output/src1719/src/s3/00/source/node_modules/aws-cdk/lib/cdk-toolkit.ts:287:24)
    at async /codebuild/output/src1719/src/s3/00/source/node_modules/aws-cdk/lib/util/work-graph.ts:105:11
2023-10-20 17:42:52.187 | error | toolkit | The stack named AWSAccelerator-OperationsStack-012345678901-us-east-1 failed to deploy: UPDATE_ROLLBACK_COMPLETE: Resource handler returned message: "User: arn:aws:sts::012345678901:assumed-role/AWSControlTowerExecution/cdk-assume-role-plugin is not authorized to perform: sso:UpdatePermissionSet on resource: arn:aws:sso:::permissionSet/ssoins-obfuscatedID563e/ps-obfuscatedID77a4 (Service: SsoAdmin, Status Code: 400, Request ID: b0cd6fb2-37f1-4d20-af94-eda630a76579)" (RequestToken: 9f0a65e6-6664-4d21-9761-89c6ade22341, HandlerErrorCode: GeneralServiceException)
Deployment failed
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

[Container] 2023/10/20 17:42:52 Command did not exit successfully if [ "diff" != "${CDK_OPTIONS}" ]; then yarn run ts-node --transpile-only cdk.ts --require-approval never $CDK_OPTIONS --config-dir $CODEBUILD_SRC_DIR_Config --partition aws --app cdk.out; fi exit status 1
[Container] 2023/10/20 17:42:52 Phase complete: BUILD State: FAILED
[Container] 2023/10/20 17:42:52 Phase context status code: COMMAND_EXECUTION_ERROR Message: Error while executing command: if [ "diff" != "${CDK_OPTIONS}" ]; then yarn run ts-node --transpile-only cdk.ts --require-approval never $CDK_OPTIONS --config-dir $CODEBUILD_SRC_DIR_Config --partition aws --app cdk.out; fi. Reason: exit status 1

To Reproduce
Run the LZA Core Pipeline after upgrading from v1.4.3 to v1.5.0 or v1.5.1
Expected behavior
I expected the Core Pipeline to complete successfully like it did immediately prior to upgrading LZA.
Please complete the following information about the solution:

[X] Version: [v1.5.1]

To get the version of the solution, you can look at the description of the created AWS CloudFormation stack used to install the LZA (AWSAccelerator-InstallerStack). For example, "(SO0199) Landing Zone Accelerator on AWS. Version 1.5.1.". If the description does not contain the version information, you can look at the Parameters of the stack for the RepositoryBranchName as that should contain the version number.

[X] Region: [us-east-1]
[ ] Was the solution modified from the version published on this repository?
[ ] If the answer to the previous question was yes, are the changes available on GitHub?
[X] Have you checked your service quotas for the services this solution uses?
[ ] Were there any errors in the CloudWatch Logs?

Screenshots
If applicable, add screenshots to help explain your problem (please DO NOT include sensitive information).

Additional context
The Core Pipeline was executed successfully before applying the v1.5.0 LZA upgrade. No other changes to the Configuration core pipeline source were made before or after the upgrade.

@lucashalbert - have you assigned this permission set in the management account?
If so, I believe this is an expected failure

@richardkeit - that was it. Thank you for pointing it out! 🎉

@richardkeit @lucashalbert same error. as @carter-maclennan asked, Could you explain why this is an expected failure?

@devalibvr @carter-maclennan
I had the same problem. It's a limitation of the configuration when using delegated account: https://docs.aws.amazon.com/singlesignon/latest/userguide/troubleshooting.html?icmpid=docs_sso_console#issue15
This message indicates that the [Delegated administration](https://docs.aws.amazon.com/singlesignon/latest/userguide/delegated-admin.html) feature has
been enabled and that the operation you previously attempted
can only be successfully performed by someone who has management account
privileges in AWS Organizations. To resolve this issue, sign in as a user who has
these privileges and try performing the task again or assign this task to someone who has the correct permissions.
For more information, see [Register a member account](https://docs.aws.amazon.com/singlesignon/latest/userguide/delegated-admin.html#delegated-admin-how-to-register).

That probably means someone has manually added this permissionSet to the management account and it needs to be removed for the pipeline to work (somebody with access to the management account must do it).
How to do it:
https://stackoverflow.com/questions/75006646/how-to-remove-a-permission-set-for-a-user-in-iam-identity-center
    Navigate to the IAM Identity Center console and under "Multi-Account Permissions" on the left hand side, select "AWS Accounts"
    Click on the desired account link, rather than the checkbox to the left.
    Once in the individual account, under the "Users and Groups" tabs, you would see the users and groups for this account.
    Select the radial button next to the username or group and click on the "Change Permission Sets" button towards the right side of the screen.
    From this page you can then uncheck the desired permission permission set and click "Save Changes".


Add route to fetch memory dump

Not to be merged now as we already identified a possible source for the leak, but could be useful later

Seems this way of doing it is outdated? https://dev.to/bengl/node-js-heap-dumps-in-2021-5akm

Seems this way of doing it is outdated? https://dev.to/bengl/node-js-heap-dumps-in-2021-5akm

Nice, using v8 seems much faster. Will update the PR if we end up needing doing that.


Synchronize server code with master branch

@DESHRAJ There is a folder called celeryTasks in the app's parent directory. I think we should shift the vqaTask files to celeryTasks.webTasks folder for it to be consistent with other functionalities.

@dexter1691 Sure. I will shift that. :+1:


Loosen absinthe version requirements

actually I dont think this is needed? because ~> 1.5 == >= 1.5 && < 2.0 please ignore lol


Enhancement: ability to reset PXE boot on misconfigured servers

Ever found a bunch of machines that somehow got misconfigured and aren't set to PXE boot, but your IPMI access does appear to work?
Here's a gross hack. Pipe the list of affected asset tags to this abomination.
while read tag; do collins find -c ipmi -t $tag; done  | awk '{print $9,$21}' | sed 's|[,)]||g' | awk '{print "ipmitool -I lanplus -H",$1,"-P",$2,"-U root chassis bootdev pxe"}' | bash -x
Much better would be if collins or consolr could easily issue that IPMI chassis bootdev pxe command to them in a more standard way.
Should be very easy to add to consolr. Having it go via the collins server would of course provide better logging.

Hey, sorry for not answering earlier. That does look like something that could be added to consolr (which now lives in it's own repo here: https://github.com/tumblr/consolr).
As for integration in collins i think the easiest would be to have it trigger on a state transition callback. Maybe have a state called Maintenance:FORCE_PXE and trigger the callback whenever an asset transitions in to that state? More info on callbacks here: http://tumblr.github.io/collins/configuration.html#callbacks
You could posisbly just add your ipmitool command there and not rely on consolr at all.


QuotaExceededError using Ionic Storage with a few strings

Ionic Storage Issue for less memory space
I'm having this issue with Ionic Storage, this is the complete stack trace:

core.es5.js:1084 ERROR Error: Uncaught (in promise): QuotaExceededError:
at c (polyfills.js:3)
at c (polyfills.js:3)
at polyfills.js:3
at t.invokeTask (polyfills.js:3)
at Object.onInvokeTask (core.es5.js:4140)
at t.invokeTask (polyfills.js:3)
at r.runTask (polyfills.js:3)
at o (polyfills.js:3)
at IDBTransaction.invoke (polyfills.js:3)

This happen both in mobile and computer  with low internal storage. If the device storage is below 1GB then this storage module freezes entirely and wont respond until freeing space more than 1GB. We need immediate attention and fix for this problem.

You're using Ionic, but for which platform? Having only 1GB of storage left, especially on a PC, doesn't surprise me that a quota error is encountered. What kind of mobile device are you encountering the error on? What kind of data are you attempting to save when you encounter the error?
This sounds like it's working as intended 🤷♂

Facing this issue on android devices. Tried Samsung J7 and note 5 with 900MB device internal storage. Both of them not working if the device storage is below 1GB. After clearing space out >=1GB then only it works

Any update on how to fix this issue?

First of all let's clarify which storage driver is used. Since you mentioned J7 I would guess that would be IndexedDB (except if you pack your Ionic app as an apk?)

How to identify the storage that the app using in the actual device?

You can run localforage.driver(), ideally inside the error handler of the failed storage method.
Please also clarify whether the error originates from a browser instance of your app or if you are providing it as a store app.

The below screenshot is taken from chrome inspect tool while debugging in my Samsung j7 android device which is currently having 800MB. It shows the storage driver is " asyncStorage" and shows that error. If I clear up some space around more than 1GB then it will work fine. It never really use sqlite or other drivers here. Is that could be the issue?

If you are packaging you ionic app as an apk, then you can use the cordovaSQLiteDriver, which should give more disk space to your app. If you are just providing a web app, then cordiva is obviously not an option.

Is there any other alternative solution to fix within the existing storage plugin?

Wait. Did you mean i have to download and add ionic cordova sqlite on top of the default storage for the sqlite to kick in when deploying apk in the actual device? Is that correct?

Yes that's what I meant but you never answered on whether you are packing an apk or serve as a web app. I thought that ionic storage should add use the Cordova sqlite plugging out of the box. How do you call the storage methods in your code? (Eg localforage.setItem())


Address crash for unmatched server responses

This closes issue #890.

a very good code and test, thanks a lot


TLS for Datawarehouse?

Hi, the document does not clearly mentions if the SSL/TLS applies to Azure SQL Datawarehouse also. Can you please confirm on that. Thanks !

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

ID: 1c2b2800-b8b3-a8f3-a14f-8dc95eb133ba
Version Independent ID: d92ac8c6-7812-9654-6d72-fcb8b61b8423
Content: Security Overview - Azure SQL Database
Content Source: articles/sql-database/sql-database-security-overview.md
Service: sql-database
Sub-service: security
GitHub Login: @jaszymas
Microsoft Alias: jaszymas

Thank you for the feedback.
This is being assigned to the content author to evaluate and update the documentation as appropriate.

Any update on this issue? It's been almost a week.
Thanks

Hi @loboc101! Thanks for submitting this issue. The Encryption in Transit portion should apply to Azure SQL DW as well, but I'll need to check with @julieMSFT on this.
@julieMSFT - Can you confirm?

Hey @julieMSFT - Sorry, I lost track of this. Can you help with this issue?
#reassign:julieMSFT

#assign:nanditavalsan

Hi,
I can confirm that documentation applies to Synapse SQL data warehouse as well. As noted in the documentation, the connection is between the client and the server on which the data warehouse resides. "SQL Database and SQL Managed Instance enforce encryption (SSL/TLS) at all times for all connections. This ensures all data is encrypted "in transit" between the client and server irrespective of the setting of Encrypt or TrustServerCertificate in the connection string."

Thanks, @nanditavalsan! I'll modify the documentation for clarify.


Add steps for rM1 recovery exposing SSH

https://gist.github.com/Eeems/77f6161ad7f33d121bb1071814225f2c

I've opened a PR to add this to remarkable-uuuflash's readme instead.


How do I rebuild a package？Instead of copying DLL file and LIB file from the cache.

How do I rebuild a package？Instead of copying DLL file and LIB file from the cache.

./vcpkg install --no-binarycaching PKG

./vcpkg install --no-binarycaching PKG

Thank you very much.😊
could you please tell me where it is in the document？

I don't know. It is even missing from vcpkg install --help.

Hope to add to the document.
analogous:
Delete the binary cache while deleting the package.


Attachments/Upload a file

Description:
Includes file upload and attachment log

As a (who/ person)

I want (what/ goal)

so that (why/ benefit proposal)

What are the most critical features being built as part of this Epic

Expected Outcome – Justification why this Feature must be built, what is expected value and justification for priority.

Sizing

T-shirt size:

[ ] S
[ ] M
[ ] L
[ ] XL
(S=1-2 Sprints, M=2-3 Sprints, L=4-5 Sprints, XL=not sure, probably more than 5 Sprints).

Risks and Assumptions*

[ ] What are assumptions?
[ ] What are the risks?
[ ] Have we done an RFC on a technical approach?
[ ] Are the dependencies (technical, business, regulatory/policy) known?
[ ] Has work on this Epic been prioritized with key stakeholders?

This Epic is complete.


[Android] None of the available extractors (...) could read the stream

Configuration
$ react-native info
  React Native Environment Info:
    System:
      OS: macOS 10.14.5
      CPU: (8) x64 Intel(R) Core(TM) i7-4770HQ CPU @ 2.20GHz
      Memory: 204.66 MB / 16.00 GB
      Shell: 5.3 - /bin/zsh
    Binaries:
      Node: 12.1.0 - /usr/local/bin/node
      Yarn: 1.16.0 - /usr/local/bin/yarn
      npm: 6.9.0 - /usr/local/bin/npm
      Watchman: 4.9.0 - /usr/local/bin/watchman
    SDKs:
      iOS SDK:
        Platforms: iOS 12.2, macOS 10.14, tvOS 12.2, watchOS 5.2
    IDEs:
      Android Studio: 3.4 AI-183.54<IP_ADDRESS>52501
      Xcode: 10.2.1/10E1001 - /usr/bin/xcodebuild
    npmPackages:
      react: ^16.8.3 => 16.8.3
      react-native: ^0.59.3 => 0.59.3
    npmGlobalPackages:
      react-native-cli: 2.0.1

react-native-track-player version 1.1.4
Issue
When I try to play the following stream URL https://nhks-vh.akamaihd.net/i/news/easy/k10011923001000.mp4/master.m3u8
the player fails on Android with:
{
  code: "playback-source"
  message : "None of the available extractors (MatroskaExtractor, FragmentedMp4Extractor, Mp4Extractor, Mp3Extractor, AdtsExtractor, Ac3Extractor, TsExtractor, FlvExtractor, OggExtractor, PsExtractor, WavExtractor, AmrExtractor) could read the stream."
  type: "playback-error"
}

Strangely an earlier build of my app with version 0.2.3 or react-native-track-player is able to play the stream without issue.
Here's some more detail on the stream:
#EXTM3U
#EXT-X-STREAM-INF:PROGRAM-ID=1,BANDWIDTH=64000,CODECS="mp4a.40.2",CLOSED-CAPTIONS=NONE
https://nhks-vh.akamaihd.net/i/news/easy/k10011923001000.mp4/index_0_a.m3u8?null=0&id=AgAyz4n2FyAuHHC05VxmY81II0nwX6YO6XNjoYkDmlXsFLrySjy6aBUOjV35yRhpL5vB69xqJFhEwQ%3d%3d

Note 1: I've confirmed playback does work for this stream on iOS.
Node 2: I've also tried enabling all extensions through the track-player.json file, unsuccessfully.
{
  "dash": true,
  "hls": true,
  "smoothstreaming": true
}

Hey @javier-artiles I have an inkling about what the issue could be. Do you have a basic demo of this not working?

Hi @dcvz thank for your prompt reply.
I've created a basic demo that illustrates the issue. In the README of the repo I've pasted the log results that I get when running on Android.
Thank you for your help!!

Hi @dcvz by any chance have you been able to look into this issue? If you have any leads I could investigate I may be able to unlock some progress. I’m not familiar with the underlying libraries (or Android native development in general), but I can give it a try if you think that’s where the root cause may be.

@javier-artiles you've forgotten to specify the type of the stream as HLS.. You can specify that in the track object -- there's more info in the documentation
for your specific example, you'd change this:
await TrackPlayer.add({
  id: streamUrl,
  url: streamUrl,
   type: 'hls', // missing this!
   //title: 'Track Title',
  //artist: 'Track Artist',
  //artwork: require('track.png')
});

try it out and let me know if it's working for you :)

as far as I believe we are no longer using the track-player.json to enable modules. /cc @Guichaguri

Thank you so much @dcvz I missed that. I should have reads the docs more thoroughly.
The issue is fixed once I set the track type field to hls.