text:
support use of SealedSecrets

Looking to replace Secret with SealedSecret to help ensure secrets are never leaked by helm. Currently helm's --dry-run and --debug flags cause secrets to be logged. See https://github.com/helm/helm/issues/7275. Perhaps someday helm will provide masking via a --set-secret option but this is not in the current list of options.
The SealedSecret templates would look very similar to the existing Secret templates and a feature flag could enable the SealedSecret templates while disabling the Secret templates.
If there's not currently an appetite to include the SealedSecret templates in the chart, then simply providing a feature flag to disable the Secret templates would allow the chart to be extended by a chart providing the SealedSecret templates.
Below is an example with a sealedSecret.enabled feature flag and a configmap-sealedsecret.yaml template. The feature flag would also be added to configmap-secret.yaml.
values
sealedSecret:
  enabled: true
  annotations:
    sealedsecrets.bitnami.com/namespace-wide: "true"

config:
  secret:
    secret.conf: AgBD1mUgglt5c8Uvu18wHr0ADQF1npS0OMRs1AKwv+8gLOIxn/1ssLin1fCaqc/mdQn6O3X6dpAlBOn+KuUiKTliPGoJmJQE3fS5jSG6P9fkv0RM2Ynr660cql4LUG1zLwqx7uQnt08vXM7eHFxvoHsf5bZJIbO/P1gVIIMtCD/cbXS24sfnYcveHMw4FHlovrkmMvNhMGU2eUBiwgJwQhSHl4E07gJwsi+x4ZuT9gRSNLVL/7vH69jMqeDyF4J4WxHc4ST80qwQKtDwLE62FNJkXzvOb6SwCP9QEzykqVCX3cy0BX26ZRSncImJjS/N+N6K54DJSlu5AlIBCXPr/XHCb1aakrS/jJIO2kiMtnF8Cm1aNX+pnzLGrdFOTVfVctZWTrkkfRaSWOXpq5WXDnzcFCJSn4dF7KSNa6Q2FB6qziEQ51ONTPJI0JfvBDLZ/HNoLBE9ICRv9ItsX1MjVH3kcYJunoK8N4ie4iBm7EvVvw9OdZvNzM4VH5BApOZ5LGSV5qx2Br+k5H73LDuVtfLMcJHdmCBmkLwYBLUGixWyI11lfxsLd5Nkes3odw3sxx7wsaOzX5EOCz2st/dRiXuJK+df3FUXB4lUFaPgvGIlEwCdG7G1lKq9tXmcuP8lZxd/OVPJq7AP67SGvaLyOFnKSdBhjMdiSdMYW/8DEuhP3QsqpcHdKitFfpBgo5E7msyl3jnA2w==

  userProvisioning:
    user.conf: AgBD1mUgglt5c8Uvu18wHr0ADQF1npS0OMRs1AKwv+8gLOIxn/1ssLin1fCaqc/mdQn6O3X6dpAlBOn+KuUiKTliPGoJmJQE3fS5jSG6P9fkv0RM2Ynr660cql4LUG1zLwqx7uQnt08vXM7eHFxvoHsf5bZJIbO/P1gVIIMtCD/cbXS24sfnYcveHMw4FHlovrkmMvNhMGU2eUBiwgJwQhSHl4E07gJwsi+x4ZuT9gRSNLVL/7vH69jMqeDyF4J4WxHc4ST80qwQKtDwLE62FNJkXzvOb6SwCP9QEzykqVCX3cy0BX26ZRSncImJjS/N+N6K54DJSlu5AlIBCXPr/XHCb1aakrS/jJIO2kiMtnF8Cm1aNX+pnzLGrdFOTVfVctZWTrkkfRaSWOXpq5WXDnzcFCJSn4dF7KSNa6Q2FB6qziEQ51ONTPJI0JfvBDLZ/HNoLBE9ICRv9ItsX1MjVH3kcYJunoK8N4ie4iBm7EvVvw9OdZvNzM4VH5BApOZ5LGSV5qx2Br+k5H73LDuVtfLMcJHdmCBmkLwYBLUGixWyI11lfxsLd5Nkes3odw3sxx7wsaOzX5EOCz2st/dRiXuJK+df3FUXB4lUFaPgvGIlEwCdG7G1lKq9tXmcuP8lZxd/OVPJq7AP67SGvaLyOFnKSdBhjMdiSdMYW/8DEuhP3QsqpcHdKitFfpBgo5E7msyl3jnA2w==

global:
  secureCookieKey: AgBD1mUgglt5c8Uvu18wHr0ADQF1npS0OMRs1AKwv+8gLOIxn/1ssLin1fCaqc/mdQn6O3X6dpAlBOn+KuUiKTliPGoJmJQE3fS5jSG6P9fkv0RM2Ynr660cql4LUG1zLwqx7uQnt08vXM7eHFxvoHsf5bZJIbO/P1gVIIMtCD/cbXS24sfnYcveHMw4FHlovrkmMvNhMGU2eUBiwgJwQhSHl4E07gJwsi+x4ZuT9gRSNLVL/7vH69jMqeDyF4J4WxHc4ST80qwQKtDwLE62FNJkXzvOb6SwCP9QEzykqVCX3cy0BX26ZRSncImJjS/N+N6K54DJSlu5AlIBCXPr/XHCb1aakrS/jJIO2kiMtnF8Cm1aNX+pnzLGrdFOTVfVctZWTrkkfRaSWOXpq5WXDnzcFCJSn4dF7KSNa6Q2FB6qziEQ51ONTPJI0JfvBDLZ/HNoLBE9ICRv9ItsX1MjVH3kcYJunoK8N4ie4iBm7EvVvw9OdZvNzM4VH5BApOZ5LGSV5qx2Br+k5H73LDuVtfLMcJHdmCBmkLwYBLUGixWyI11lfxsLd5Nkes3odw3sxx7wsaOzX5EOCz2st/dRiXuJK+df3FUXB4lUFaPgvGIlEwCdG7G1lKq9tXmcuP8lZxd/OVPJq7AP67SGvaLyOFnKSdBhjMdiSdMYW/8DEuhP3QsqpcHdKitFfpBgo5E7msyl3jnA2w==

launcherPem: AgBD1mUgglt5c8Uvu18wHr0ADQF1npS0OMRs1AKwv+8gLOIxn/1ssLin1fCaqc/mdQn6O3X6dpAlBOn+KuUiKTliPGoJmJQE3fS5jSG6P9fkv0RM2Ynr660cql4LUG1zLwqx7uQnt08vXM7eHFxvoHsf5bZJIbO/P1gVIIMtCD/cbXS24sfnYcveHMw4FHlovrkmMvNhMGU2eUBiwgJwQhSHl4E07gJwsi+x4ZuT9gRSNLVL/7vH69jMqeDyF4J4WxHc4ST80qwQKtDwLE62FNJkXzvOb6SwCP9QEzykqVCX3cy0BX26ZRSncImJjS/N+N6K54DJSlu5AlIBCXPr/XHCb1aakrS/jJIO2kiMtnF8Cm1aNX+pnzLGrdFOTVfVctZWTrkkfRaSWOXpq5WXDnzcFCJSn4dF7KSNa6Q2FB6qziEQ51ONTPJI0JfvBDLZ/HNoLBE9ICRv9ItsX1MjVH3kcYJunoK8N4ie4iBm7EvVvw9OdZvNzM4VH5BApOZ5LGSV5qx2Br+k5H73LDuVtfLMcJHdmCBmkLwYBLUGixWyI11lfxsLd5Nkes3odw3sxx7wsaOzX5EOCz2st/dRiXuJK+df3FUXB4lUFaPgvGIlEwCdG7G1lKq9tXmcuP8lZxd/OVPJq7AP67SGvaLyOFnKSdBhjMdiSdMYW/8DEuhP3QsqpcHdKitFfpBgo5E7msyl3jnA2w==

configmap-sealedsecret.yaml
{{- if .Values.sealedSecret.enabled -}}
---
apiVersion: bitnami.com/v1alpha1
kind: SealedSecret
metadata:
  annotations:
    {{- tpl ( toYaml .Values.sealedSecret.annotations ) . | nindent 4 }}
  name: {{ include "rstudio-workbench.fullname" . }}-secret
  namespace: {{ $.Release.Namespace }}
spec:
  encryptedData:
    {{- include "rstudio-library.config.ini" .Values.config.secret | nindent 4 }}
    launcher.pem: |
      {{- include "rstudio-workbench.launcherPem" . | nindent 6 }}
    secure-cookie-key: |
      {{- include "rstudio-workbench.secureCookieKey" . | nindent 6 }}
  template:
    data:
      {{- if .Values.launcherPub }}
      # TODO: would ideally be able to generate launcher.pub as well
      launcher.pub: |
        {{- .Values.launcherPub | nindent 10 }}
      {{- end }}
---
{{- if .Values.config.userProvisioning }}
apiVersion: bitnami.com/v1alpha1
kind: SealedSecret
metadata:
  annotations:
    {{- tpl ( toYaml .Values.sealedSecret.annotations ) . | nindent 4 }}
  name: {{ include "rstudio-workbench.fullname" . }}-user
  namespace: {{ $.Release.Namespace }}
spec:
  encryptedData:
    {{- include "rstudio-library.config.ini" .Values.config.userProvisioning | nindent 4 }}
{{- end }}
{{- end }}

This sounds great! We also discussed:

removing a few default values that are problematic for hybrid typing (i.e. allowing a string or a map)
implementing for Workbench first, and then pivoting to the other charts


text:
reload does not work when launched with option --log-level error

First of all, mega interesting project! Thank you :)
Launch command:
shiny run --reload --log-level error
Result:
When code changes, web page gets greyed out and not responsive.
Possible origin of the problem:
https://github.com/rstudio/py-shiny/blob/f2689a38a97f7e37030efbaf6f6ebb79f13faa8f/shiny/_autoreload.py#L56
is not called when log-level is above info, because of
https://github.com/rstudio/py-shiny/blob/f2689a38a97f7e37030efbaf6f6ebb79f13faa8f/shiny/_main.py#L249

Shoot, that was an oversight on my part. We rely on an INFO-level log message to be emitted from Uvicorn in order to know that Shiny is ready for restart. At the very least we should warn/error if --reload is requested with a log level greater than info.

source: gharchive/issue

repo: rstudio/py-shiny

license: MIT

license_type: permissive

license_source: github-api


text:
Navigationが動かない

不具合の概要

SLAMの動作確認はできたが、Navigationが動かない。
実行環境

リモートPCのOS: Ubuntu 22.04.2 LTS（Docker環境上のUbuntu）
Raspberry Pi MouseのOS: Ubuntu 22.04.2 LTS
ソフトのバージョン: 2023年7月24日現在のfeature/support-humbleブランチを使用（raspimouse.yamlを少しいじっています）

再現方法

ROS_DOMAIN_IDは設定済み
Raspberry Pi Mouse側で 'ros2 launch raspimouse_navigation robot_navigation.launch.py lidar:=lds' を実行
リモートPC側で 'ros2 launch raspimouse_navigation pc_navigation.launch.py map:=MAP_NAME.yaml' を実行
2D Pose Estimateを指定
RViz上でNav2 Goalを指定
Raspberry Pi Mouseが動かない（Navigationが動かない不具合）

期待する動作

Rviz上で指定した目標地点までRaspberry Pi Mouseが動く。
ログ・画像

# リモートPC側のログ
[INFO] [launch]: All log files can be found below /root/.ros/log/2023-07-24-18-35-10-443445-ubuntu-Dell-G15-5525-1
[INFO] [launch]: Default logging verbosity is set to INFO
[INFO] [component_container_isolated-1]: process started with pid [69]
[INFO] [rviz2-2]: process started with pid [71]
[rviz2-2] QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
[component_container_isolated-1] [INFO] [1690191311.440519308] [nav2_container]: Load Library: /opt/ros/humble/lib/libmap_server_core.so
[component_container_isolated-1] [INFO] [1690191311.478735747] [nav2_container]: Found class: rclcpp_components::NodeFactoryTemplate<nav2_map_server::CostmapFilterInfoServer>
[component_container_isolated-1] [INFO] [1690191311.478772731] [nav2_container]: Found class: rclcpp_components::NodeFactoryTemplate<nav2_map_server::MapSaver>
[component_container_isolated-1] [INFO] [1690191311.478777758] [nav2_container]: Found class: rclcpp_components::NodeFactoryTemplate<nav2_map_server::MapServer>
[component_container_isolated-1] [INFO] [1690191311.478781544] [nav2_container]: Instantiate class: rclcpp_components::NodeFactoryTemplate<nav2_map_server::MapServer>
[component_container_isolated-1] [INFO] [1690191311.497108191] [map_server]:
[component_container_isolated-1] 	map_server lifecycle node launched.
[component_container_isolated-1] 	Waiting on external lifecycle transitions to activate
[component_container_isolated-1] 	See https://design.ros2.org/articles/node_lifecycle.html for more information.
[component_container_isolated-1] [INFO] [1690191311.497171794] [map_server]: Creating
[component_container_isolated-1] [INFO] [1690191311.498067690] [nav2_container]: Load Library: /opt/ros/humble/lib/libcontroller_server_core.so
[INFO] [launch_ros.actions.load_composable_nodes]: Loaded node '/map_server' in container '/nav2_container'
[component_container_isolated-1] [INFO] [1690191311.507957770] [nav2_container]: Found class: rclcpp_components::NodeFactoryTemplate<nav2_controller::ControllerServer>
[component_container_isolated-1] [INFO] [1690191311.507983968] [nav2_container]: Instantiate class: rclcpp_components::NodeFactoryTemplate<nav2_controller::ControllerServer>
[component_container_isolated-1] [INFO] [1690191311.515705475] [controller_server]:
[component_container_isolated-1] 	controller_server lifecycle node launched.
[component_container_isolated-1] 	Waiting on external lifecycle transitions to activate
[component_container_isolated-1] 	See https://design.ros2.org/articles/node_lifecycle.html for more information.
[component_container_isolated-1] [INFO] [1690191311.527340998] [controller_server]: Creating controller server
[component_container_isolated-1] [INFO] [1690191311.542213233] [local_costmap.local_costmap]:
[component_container_isolated-1] 	local_costmap lifecycle node launched.
[component_container_isolated-1] 	Waiting on external lifecycle transitions to activate
[component_container_isolated-1] 	See https://design.ros2.org/articles/node_lifecycle.html for more information.
[component_container_isolated-1] [INFO] [1690191311.544355559] [local_costmap.local_costmap]: Creating Costmap
[component_container_isolated-1] [INFO] [1690191311.545501942] [nav2_container]: Load Library: /opt/ros/humble/lib/libamcl_core.so
[INFO] [launch_ros.actions.load_composable_nodes]: Loaded node '/controller_server' in container '/nav2_container'
[component_container_isolated-1] [INFO] [1690191311.550032333] [nav2_container]: Found class: rclcpp_components::NodeFactoryTemplate<nav2_amcl::AmclNode>
[component_container_isolated-1] [INFO] [1690191311.550056098] [nav2_container]: Instantiate class: rclcpp_components::NodeFactoryTemplate<nav2_amcl::AmclNode>
[component_container_isolated-1] [INFO] [1690191311.564983434] [amcl]:
[component_container_isolated-1] 	amcl lifecycle node launched.
[component_container_isolated-1] 	Waiting on external lifecycle transitions to activate
[component_container_isolated-1] 	See https://design.ros2.org/articles/node_lifecycle.html for more information.
[component_container_isolated-1] [INFO] [1690191311.566020747] [amcl]: Creating
[component_container_isolated-1] [INFO] [1690191311.582248262] [nav2_container]: Load Library: /opt/ros/humble/lib/libsmoother_server_core.so
[INFO] [launch_ros.actions.load_composable_nodes]: Loaded node '/amcl' in container '/nav2_container'
[component_container_isolated-1] [INFO] [1690191311.585990226] [nav2_container]: Found class: rclcpp_components::NodeFactoryTemplate<nav2_smoother::SmootherServer>
[component_container_isolated-1] [INFO] [1690191311.586025218] [nav2_container]: Instantiate class: rclcpp_components::NodeFactoryTemplate<nav2_smoother::SmootherServer>
[component_container_isolated-1] [INFO] [1690191311.610500852] [smoother_server]:
[component_container_isolated-1] 	smoother_server lifecycle node launched.
[component_container_isolated-1] 	Waiting on external lifecycle transitions to activate
[component_container_isolated-1] 	See https://design.ros2.org/articles/node_lifecycle.html for more information.
[component_container_isolated-1] [INFO] [1690191311.612699129] [smoother_server]: Creating smoother server
[component_container_isolated-1] [INFO] [1690191311.613486546] [nav2_container]: Load Library: /opt/ros/humble/lib/libnav2_lifecycle_manager_core.so
[INFO] [launch_ros.actions.load_composable_nodes]: Loaded node '/smoother_server' in container '/nav2_container'
[component_container_isolated-1] [INFO] [1690191311.615305776] [nav2_container]: Found class: rclcpp_components::NodeFactoryTemplate<nav2_lifecycle_manager::LifecycleManager>
[component_container_isolated-1] [INFO] [1690191311.615331955] [nav2_container]: Instantiate class: rclcpp_components::NodeFactoryTemplate<nav2_lifecycle_manager::LifecycleManager>
[component_container_isolated-1] [INFO] [1690191311.637781576] [lifecycle_manager_localization]: Creating
[component_container_isolated-1] [INFO] [1690191311.642849776] [lifecycle_manager_localization]: Creating and initializing lifecycle service clients
[component_container_isolated-1] [INFO] [1690191311.643211347] [nav2_container]: Load Library: /opt/ros/humble/lib/libplanner_server_core.so
[INFO] [launch_ros.actions.load_composable_nodes]: Loaded node '/lifecycle_manager_localization' in container '/nav2_container'
[component_container_isolated-1] [INFO] [1690191311.645274727] [nav2_container]: Found class: rclcpp_components::NodeFactoryTemplate<nav2_planner::PlannerServer>
[component_container_isolated-1] [INFO] [1690191311.645314675] [nav2_container]: Instantiate class: rclcpp_components::NodeFactoryTemplate<nav2_planner::PlannerServer>
[component_container_isolated-1] [INFO] [1690191311.651617609] [lifecycle_manager_localization]: Starting managed nodes bringup...
[component_container_isolated-1] [INFO] [1690191311.651685559] [lifecycle_manager_localization]: Configuring map_server
[component_container_isolated-1] [INFO] [1690191311.651905952] [map_server]: Configuring
[component_container_isolated-1] [INFO] [map_io]: Loading yaml file: MAP_NAME.yaml
[component_container_isolated-1] [DEBUG] [map_io]: resolution: 0.01
[component_container_isolated-1] [DEBUG] [map_io]: origin[0]: -1.91
[component_container_isolated-1] [DEBUG] [map_io]: origin[1]: -1.67
[component_container_isolated-1] [DEBUG] [map_io]: origin[2]: 0
[component_container_isolated-1] [DEBUG] [map_io]: free_thresh: 0.25
[component_container_isolated-1] [DEBUG] [map_io]: occupied_thresh: 0.65
[component_container_isolated-1] [DEBUG] [map_io]: mode: trinary
[component_container_isolated-1] [DEBUG] [map_io]: negate: 0
[component_container_isolated-1] [INFO] [map_io]: Loading image_file: ./MAP_NAME.pgm
[component_container_isolated-1] [DEBUG] [map_io]: Read map ./MAP_NAME.pgm: 335 X 269 map @ 0.01 m/cell
[rviz2-2] [INFO] [1690191311.677059252] [rviz2]: Stereo is NOT SUPPORTED
[rviz2-2] [INFO] [1690191311.677191616] [rviz2]: OpenGl version: 4.6 (GLSL 4.6)
[component_container_isolated-1] [INFO] [1690191311.687912337] [lifecycle_manager_localization]: Configuring amcl
[component_container_isolated-1] [INFO] [1690191311.688063689] [amcl]: Configuring
[component_container_isolated-1] [INFO] [1690191311.688167411] [amcl]: initTransforms
[rviz2-2] [INFO] [1690191311.702354350] [rviz2]: Stereo is NOT SUPPORTED
[component_container_isolated-1] [INFO] [1690191311.706317859] [planner_server]:
[component_container_isolated-1] 	planner_server lifecycle node launched.
[component_container_isolated-1] 	Waiting on external lifecycle transitions to activate
[component_container_isolated-1] 	See https://design.ros2.org/articles/node_lifecycle.html for more information.
[component_container_isolated-1] [INFO] [1690191311.708218560] [planner_server]: Creating
[component_container_isolated-1] [INFO] [1690191311.728657308] [amcl]: initPubSub
[component_container_isolated-1] [INFO] [1690191311.747987508] [amcl]: Subscribed to map topic.
[component_container_isolated-1] [INFO] [1690191311.756160477] [lifecycle_manager_localization]: Activating map_server
[component_container_isolated-1] [INFO] [1690191311.756276448] [map_server]: Activating
[component_container_isolated-1] [INFO] [1690191311.756406639] [map_server]: Creating bond (map_server) to lifecycle manager.
[component_container_isolated-1] [INFO] [1690191311.756463362] [amcl]: Received a 335 X 269 map @ 0.010 m/pix
[component_container_isolated-1] [INFO] [1690191311.813361739] [global_costmap.global_costmap]:
[component_container_isolated-1] 	global_costmap lifecycle node launched.
[component_container_isolated-1] 	Waiting on external lifecycle transitions to activate
[component_container_isolated-1] 	See https://design.ros2.org/articles/node_lifecycle.html for more information.
[component_container_isolated-1] [INFO] [1690191311.813963673] [global_costmap.global_costmap]: Creating Costmap
[INFO] [launch_ros.actions.load_composable_nodes]: Loaded node '/planner_server' in container '/nav2_container'
[component_container_isolated-1] [INFO] [1690191311.817696043] [nav2_container]: Load Library: /opt/ros/humble/lib/libbehavior_server_core.so
[component_container_isolated-1] [INFO] [1690191311.824473133] [nav2_container]: Found class: rclcpp_components::NodeFactoryTemplate<behavior_server::BehaviorServer>
[component_container_isolated-1] [INFO] [1690191311.824488856] [nav2_container]: Instantiate class: rclcpp_components::NodeFactoryTemplate<behavior_server::BehaviorServer>
[component_container_isolated-1] [INFO] [1690191311.865141401] [lifecycle_manager_localization]: Server map_server connected with bond.
[component_container_isolated-1] [INFO] [1690191311.865204864] [lifecycle_manager_localization]: Activating amcl
[component_container_isolated-1] [INFO] [1690191311.865393321] [amcl]: Activating
[component_container_isolated-1] [INFO] [1690191311.865435163] [amcl]: initialPoseReceived
[component_container_isolated-1] [INFO] [1690191311.865612934] [amcl]: Setting pose (1690191311.865613): 0.000 0.000 0.000
[component_container_isolated-1] [INFO] [1690191311.866631148] [amcl]: Creating bond (amcl) to lifecycle manager.
[rviz2-2] [WARN] [1690191311.880372904] [rcl.logging_rosout]: Publisher already registered for provided node name. If this is due to multiple nodes with the same name then all logs for that logger name will go out over the existing publisher. As soon as any node with that name is destructed it will unregister the publisher, preventing any further logs for that name from being published on the rosout topic.
[component_container_isolated-1] [INFO] [1690191311.918293358] [behavior_server]:
[component_container_isolated-1] 	behavior_server lifecycle node launched.
[component_container_isolated-1] 	Waiting on external lifecycle transitions to activate
[component_container_isolated-1] 	See https://design.ros2.org/articles/node_lifecycle.html for more information.
[INFO] [launch_ros.actions.load_composable_nodes]: Loaded node '/behavior_server' in container '/nav2_container'
[component_container_isolated-1] [INFO] [1690191311.924389158] [nav2_container]: Load Library: /opt/ros/humble/lib/libbt_navigator_core.so
[component_container_isolated-1] [INFO] [1690191311.927316907] [nav2_container]: Found class: rclcpp_components::NodeFactoryTemplate<nav2_bt_navigator::BtNavigator>
[component_container_isolated-1] [INFO] [1690191311.927332049] [nav2_container]: Instantiate class: rclcpp_components::NodeFactoryTemplate<nav2_bt_navigator::BtNavigator>
[rviz2-2] [INFO] [1690191311.989725825] [rviz2]: Trying to create a map of size 335 x 269 using 1 swatches
[component_container_isolated-1] [INFO] [1690191311.991157096] [bt_navigator]:
[component_container_isolated-1] 	bt_navigator lifecycle node launched.
[component_container_isolated-1] 	Waiting on external lifecycle transitions to activate
[component_container_isolated-1] 	See https://design.ros2.org/articles/node_lifecycle.html for more information.
[component_container_isolated-1] [INFO] [1690191311.991257223] [bt_navigator]: Creating
[INFO] [launch_ros.actions.load_composable_nodes]: Loaded node '/bt_navigator' in container '/nav2_container'
[component_container_isolated-1] [INFO] [1690191311.993907794] [nav2_container]: Load Library: /opt/ros/humble/lib/libwaypoint_follower_core.so
[rviz2-2] [ERROR] [1690191311.994065706] [rviz2]: Vertex Program:rviz/glsl120/indexed_8bit_image.vert Fragment Program:rviz/glsl120/indexed_8bit_image.frag GLSL link result :
[rviz2-2] active samplers with a different type refer to the same texture image unit
[component_container_isolated-1] [INFO] [1690191311.995586549] [nav2_container]: Found class: rclcpp_components::NodeFactoryTemplate<nav2_waypoint_follower::WaypointFollower>
[component_container_isolated-1] [INFO] [1690191311.995636152] [nav2_container]: Instantiate class: rclcpp_components::NodeFactoryTemplate<nav2_waypoint_follower::WaypointFollower>
[component_container_isolated-1] [INFO] [1690191311.997483023] [lifecycle_manager_localization]: Server amcl connected with bond.
[component_container_isolated-1] [INFO] [1690191311.997508381] [lifecycle_manager_localization]: Managed nodes are active
[component_container_isolated-1] [INFO] [1690191311.997518155] [lifecycle_manager_localization]: Creating bond timer...
[component_container_isolated-1] [INFO] [1690191312.026673323] [amcl]: createLaserObject
[component_container_isolated-1] [INFO] [1690191312.048409556] [waypoint_follower]:
[component_container_isolated-1] 	waypoint_follower lifecycle node launched.
[component_container_isolated-1] 	Waiting on external lifecycle transitions to activate
[component_container_isolated-1] 	See https://design.ros2.org/articles/node_lifecycle.html for more information.
[component_container_isolated-1] [INFO] [1690191312.049873943] [waypoint_follower]: Creating
[INFO] [launch_ros.actions.load_composable_nodes]: Loaded node '/waypoint_follower' in container '/nav2_container'
[component_container_isolated-1] [INFO] [1690191312.052108320] [nav2_container]: Load Library: /opt/ros/humble/lib/libvelocity_smoother_core.so
[component_container_isolated-1] [INFO] [1690191312.053740326] [nav2_container]: Found class: rclcpp_components::NodeFactoryTemplate<nav2_velocity_smoother::VelocitySmoother>
[component_container_isolated-1] [INFO] [1690191312.053765503] [nav2_container]: Instantiate class: rclcpp_components::NodeFactoryTemplate<nav2_velocity_smoother::VelocitySmoother>
[component_container_isolated-1] [INFO] [1690191312.114867254] [velocity_smoother]:
[component_container_isolated-1] 	velocity_smoother lifecycle node launched.
[INFO] [launch_ros.actions.load_composable_nodes]: Loaded node '/velocity_smoother' in container '/nav2_container'
[component_container_isolated-1] 	Waiting on external lifecycle transitions to activate
[component_container_isolated-1] 	See https://design.ros2.org/articles/node_lifecycle.html for more information.
[component_container_isolated-1] [INFO] [1690191312.117291452] [nav2_container]: Found class: rclcpp_components::NodeFactoryTemplate<nav2_lifecycle_manager::LifecycleManager>
[component_container_isolated-1] [INFO] [1690191312.117324852] [nav2_container]: Instantiate class: rclcpp_components::NodeFactoryTemplate<nav2_lifecycle_manager::LifecycleManager>
[component_container_isolated-1] [INFO] [1690191312.155458596] [lifecycle_manager_navigation]: Creating
[INFO] [launch_ros.actions.load_composable_nodes]: Loaded node '/lifecycle_manager_navigation' in container '/nav2_container'
[component_container_isolated-1] [INFO] [1690191312.160485136] [lifecycle_manager_navigation]: Creating and initializing lifecycle service clients
[component_container_isolated-1] [INFO] [1690191312.221902004] [lifecycle_manager_navigation]: Starting managed nodes bringup...
[component_container_isolated-1] [INFO] [1690191312.221954351] [lifecycle_manager_navigation]: Configuring controller_server
[component_container_isolated-1] [INFO] [1690191312.222065686] [controller_server]: Configuring controller interface
[component_container_isolated-1] [INFO] [1690191312.222190040] [controller_server]: getting goal checker plugins..
[component_container_isolated-1] [INFO] [1690191312.222331710] [controller_server]: Controller frequency set to 10.0000Hz
[component_container_isolated-1] [INFO] [1690191312.222372821] [local_costmap.local_costmap]: Configuring
[component_container_isolated-1] [INFO] [1690191312.242745045] [local_costmap.local_costmap]: Using plugin "static_layer"
[component_container_isolated-1] [INFO] [1690191312.248010178] [local_costmap.local_costmap]: Subscribing to the map topic (/map) with transient local durability
[component_container_isolated-1] [INFO] [1690191312.251368960] [local_costmap.local_costmap]: Initialized plugin "static_layer"
[component_container_isolated-1] [INFO] [1690191312.251400957] [local_costmap.local_costmap]: Using plugin "obstacle_layer"
[component_container_isolated-1] [INFO] [1690191312.251987966] [local_costmap.local_costmap]: Subscribed to Topics: scan
[component_container_isolated-1] [INFO] [1690191312.256032672] [local_costmap.local_costmap]: Initialized plugin "obstacle_layer"
[component_container_isolated-1] [INFO] [1690191312.256063017] [local_costmap.local_costmap]: Using plugin "inflation_layer"
[component_container_isolated-1] [INFO] [1690191312.263473386] [local_costmap.local_costmap]: Initialized plugin "inflation_layer"
[component_container_isolated-1] [INFO] [1690191312.300664766] [local_costmap.local_costmap]: StaticLayer: Resizing static layer to 335 X 269 at 0.010000 m/pix
[component_container_isolated-1] [INFO] [1690191312.301446703] [controller_server]: Created progress_checker : progress_checker of type nav2_controller::SimpleProgressChecker
[component_container_isolated-1] [INFO] [1690191312.302722291] [controller_server]: Created goal checker : goal_checker of type nav2_controller::SimpleGoalChecker
[component_container_isolated-1] [INFO] [1690191312.303204715] [controller_server]: Controller Server has goal_checker  goal checkers available.
[component_container_isolated-1] [INFO] [1690191312.308127402] [controller_server]: Created controller : FollowPath of type dwb_core::DWBLocalPlanner
[component_container_isolated-1] [INFO] [1690191312.309278836] [controller_server]: Setting transform_tolerance to 0.200000
[component_container_isolated-1] [INFO] [1690191312.336974120] [controller_server]: Using critic "RotateToGoal" (dwb_critics::RotateToGoalCritic)
[component_container_isolated-1] [INFO] [1690191312.337515321] [controller_server]: Critic plugin initialized
[component_container_isolated-1] [INFO] [1690191312.337731300] [controller_server]: Using critic "Oscillation" (dwb_critics::OscillationCritic)
[component_container_isolated-1] [INFO] [1690191312.338433399] [controller_server]: Critic plugin initialized
[component_container_isolated-1] [INFO] [1690191312.338652514] [controller_server]: Using critic "BaseObstacle" (dwb_critics::BaseObstacleCritic)
[component_container_isolated-1] [INFO] [1690191312.338932668] [controller_server]: Critic plugin initialized
[component_container_isolated-1] [INFO] [1690191312.339082741] [controller_server]: Using critic "GoalAlign" (dwb_critics::GoalAlignCritic)
[component_container_isolated-1] [INFO] [1690191312.339291660] [controller_server]: Critic plugin initialized
[component_container_isolated-1] [INFO] [1690191312.339367001] [controller_server]: Using critic "PathAlign" (dwb_critics::PathAlignCritic)
[component_container_isolated-1] [INFO] [1690191312.339550823] [controller_server]: Critic plugin initialized
[component_container_isolated-1] [INFO] [1690191312.339629390] [controller_server]: Using critic "PathDist" (dwb_critics::PathDistCritic)
[component_container_isolated-1] [INFO] [1690191312.339813292] [controller_server]: Critic plugin initialized
[component_container_isolated-1] [INFO] [1690191312.339886510] [controller_server]: Using critic "GoalDist" (dwb_critics::GoalDistCritic)
[component_container_isolated-1] [INFO] [1690191312.340061660] [controller_server]: Critic plugin initialized
[component_container_isolated-1] [INFO] [1690191312.340080668] [controller_server]: Controller Server has FollowPath  controllers available.
[component_container_isolated-1] [INFO] [1690191312.372793158] [lifecycle_manager_navigation]: Configuring smoother_server
[component_container_isolated-1] [INFO] [1690191312.373036608] [smoother_server]: Configuring smoother server
[component_container_isolated-1] [INFO] [1690191312.405596262] [smoother_server]: Created smoother : simple_smoother of type nav2_smoother::SimpleSmoother
[component_container_isolated-1] [INFO] [1690191312.406436816] [smoother_server]: Smoother Server has simple_smoother  smoothers available.
[component_container_isolated-1] [INFO] [1690191312.436611029] [lifecycle_manager_navigation]: Configuring planner_server
[component_container_isolated-1] [INFO] [1690191312.436804305] [planner_server]: Configuring
[component_container_isolated-1] [INFO] [1690191312.436879446] [global_costmap.global_costmap]: Configuring
[component_container_isolated-1] [INFO] [1690191312.457202508] [global_costmap.global_costmap]: Using plugin "static_layer"
[component_container_isolated-1] [INFO] [1690191312.458547479] [global_costmap.global_costmap]: Subscribing to the map topic (/map) with transient local durability
[component_container_isolated-1] [INFO] [1690191312.465028061] [global_costmap.global_costmap]: Initialized plugin "static_layer"
[component_container_isolated-1] [INFO] [1690191312.465070203] [global_costmap.global_costmap]: Using plugin "obstacle_layer"
[component_container_isolated-1] [INFO] [1690191312.466044886] [global_costmap.global_costmap]: Subscribed to Topics: scan
[component_container_isolated-1] [INFO] [1690191312.473092698] [global_costmap.global_costmap]: Initialized plugin "obstacle_layer"
[component_container_isolated-1] [INFO] [1690191312.473131305] [global_costmap.global_costmap]: Using plugin "inflation_layer"
[component_container_isolated-1] [INFO] [1690191312.473972620] [global_costmap.global_costmap]: Initialized plugin "inflation_layer"
[component_container_isolated-1] [INFO] [1690191312.529070955] [global_costmap.global_costmap]: StaticLayer: Resizing costmap to 335 X 269 at 0.010000 m/pix
[component_container_isolated-1] [INFO] [1690191312.538081302] [planner_server]: Created global planner plugin GridBased of type nav2_navfn_planner/NavfnPlanner
[component_container_isolated-1] [INFO] [1690191312.538147289] [planner_server]: Configuring plugin GridBased of type NavfnPlanner
[component_container_isolated-1] [INFO] [1690191312.538864691] [planner_server]: Planner Server has GridBased  planners available.
[component_container_isolated-1] [INFO] [1690191312.585366842] [lifecycle_manager_navigation]: Configuring behavior_server
[component_container_isolated-1] [INFO] [1690191312.585569332] [behavior_server]: Configuring
[component_container_isolated-1] [INFO] [1690191312.629404505] [behavior_server]: Creating behavior plugin spin of type nav2_behaviors/Spin
[component_container_isolated-1] [INFO] [1690191312.631315924] [behavior_server]: Configuring spin
[component_container_isolated-1] [INFO] [1690191312.658707118] [behavior_server]: Creating behavior plugin backup of type nav2_behaviors/BackUp
[component_container_isolated-1] [INFO] [1690191312.660599780] [behavior_server]: Configuring backup
[component_container_isolated-1] [INFO] [1690191312.690067006] [behavior_server]: Creating behavior plugin drive_on_heading of type nav2_behaviors/DriveOnHeading
[component_container_isolated-1] [INFO] [1690191312.692176789] [behavior_server]: Configuring drive_on_heading
[component_container_isolated-1] [INFO] [1690191312.728802021] [behavior_server]: Creating behavior plugin wait of type nav2_behaviors/Wait
[component_container_isolated-1] [INFO] [1690191312.730758907] [behavior_server]: Configuring wait
[component_container_isolated-1] [INFO] [1690191312.759236448] [lifecycle_manager_navigation]: Configuring bt_navigator
[component_container_isolated-1] [INFO] [1690191312.759408633] [bt_navigator]: Configuring
[component_container_isolated-1] [INFO] [1690191313.045455072] [lifecycle_manager_navigation]: Configuring waypoint_follower
[component_container_isolated-1] [INFO] [1690191313.045627469] [waypoint_follower]: Configuring
[rviz2-2] [ERROR] [1690191313.078930039] [rviz2]: Lookup would require extrapolation into the future.  Requested time 1690191313.224129 but the latest data is at time 1690191313.064812, when looking up transform from frame [laser] to frame [map]
[component_container_isolated-1] [INFO] [1690191313.110786081] [waypoint_follower]: Created waypoint_task_executor : wait_at_waypoint of type nav2_waypoint_follower::WaitAtWaypoint
[component_container_isolated-1] [INFO] [1690191313.111170584] [waypoint_follower]: Waypoint pause duration is set to zero, disabling task executor plugin.
[component_container_isolated-1] [INFO] [1690191313.111639253] [lifecycle_manager_navigation]: Configuring velocity_smoother
[component_container_isolated-1] [INFO] [1690191313.111859933] [velocity_smoother]: Configuring velocity smoother
[component_container_isolated-1] [INFO] [1690191313.131629354] [lifecycle_manager_navigation]: Activating controller_server
[component_container_isolated-1] [INFO] [1690191313.131825717] [controller_server]: Activating
[component_container_isolated-1] [INFO] [1690191313.131888300] [local_costmap.local_costmap]: Activating
[component_container_isolated-1] [INFO] [1690191313.131915872] [local_costmap.local_costmap]: Checking transform
[component_container_isolated-1] [INFO] [1690191313.132059606] [local_costmap.local_costmap]: start
[rviz2-2] [ERROR] [1690191313.337068734] [rviz2]: Lookup would require extrapolation into the future.  Requested time 1690191313.424072 but the latest data is at time 1690191313.344786, when looking up transform from frame [laser] to frame [map]
[component_container_isolated-1] [INFO] [1690191313.382863339] [controller_server]: Creating bond (controller_server) to lifecycle manager.
[rviz2-2] [ERROR] [1690191313.432998369] [rviz2]: Lookup would require extrapolation into the future.  Requested time 1690191313.625349 but the latest data is at time 1690191313.444704, when looking up transform from frame [laser] to frame [map]
[component_container_isolated-1] [INFO] [1690191313.498450829] [lifecycle_manager_navigation]: Server controller_server connected with bond.
[component_container_isolated-1] [INFO] [1690191313.498548655] [lifecycle_manager_navigation]: Activating smoother_server
[component_container_isolated-1] [INFO] [1690191313.498973509] [smoother_server]: Activating
[component_container_isolated-1] [INFO] [1690191313.499049582] [smoother_server]: Creating bond (smoother_server) to lifecycle manager.
[component_container_isolated-1] [INFO] [1690191313.610817805] [lifecycle_manager_navigation]: Server smoother_server connected with bond.
[component_container_isolated-1] [INFO] [1690191313.610885496] [lifecycle_manager_navigation]: Activating planner_server
[component_container_isolated-1] [INFO] [1690191313.611177442] [planner_server]: Activating
[component_container_isolated-1] [INFO] [1690191313.611237551] [global_costmap.global_costmap]: Activating
[component_container_isolated-1] [INFO] [1690191313.611256079] [global_costmap.global_costmap]: Checking transform
[component_container_isolated-1] [INFO] [1690191313.611349428] [global_costmap.global_costmap]: start
[rviz2-2] [ERROR] [1690191313.625739135] [rviz2]: Lookup would require extrapolation into the future.  Requested time 1690191313.825215 but the latest data is at time 1690191313.634815, when looking up transform from frame [laser] to frame [map]
[rviz2-2] [ERROR] [1690191313.821356552] [rviz2]: Lookup would require extrapolation into the future.  Requested time 1690191314.025701 but the latest data is at time 1690191313.834740, when looking up transform from frame [laser] to frame [map]
[rviz2-2] [ERROR] [1690191314.041659158] [rviz2]: Lookup would require extrapolation into the future.  Requested time 1690191314.226259 but the latest data is at time 1690191314.054627, when looking up transform from frame [laser] to frame [map]
[rviz2-2] [ERROR] [1690191314.233006947] [rviz2]: Lookup would require extrapolation into the future.  Requested time 1690191314.426693 but the latest data is at time 1690191314.234779, when looking up transform from frame [laser] to frame [map]
[rviz2-2] [ERROR] [1690191314.425730444] [rviz2]: Lookup would require extrapolation into the future.  Requested time 1690191314.627329 but the latest data is at time 1690191314.434795, when looking up transform from frame [laser] to frame [map]
[rviz2-2] [ERROR] [1690191314.620784424] [rviz2]: Lookup would require extrapolation into the future.  Requested time 1690191314.827804 but the latest data is at time 1690191314.634657, when looking up transform from frame [laser] to frame [map]
[rviz2-2] [INFO] [1690191314.649281816] [rviz2]: Trying to create a map of size 335 x 269 using 1 swatches
[component_container_isolated-1] [INFO] [1690191314.662164449] [planner_server]: Activating plugin GridBased of type NavfnPlanner
[component_container_isolated-1] [INFO] [1690191314.663201097] [planner_server]: Creating bond (planner_server) to lifecycle manager.
[component_container_isolated-1] [INFO] [1690191314.788958502] [lifecycle_manager_navigation]: Server planner_server connected with bond.
[component_container_isolated-1] [INFO] [1690191314.789026855] [lifecycle_manager_navigation]: Activating behavior_server
[component_container_isolated-1] [INFO] [1690191314.789292635] [behavior_server]: Activating
[component_container_isolated-1] [INFO] [1690191314.789328769] [behavior_server]: Activating spin
[component_container_isolated-1] [INFO] [1690191314.789359615] [behavior_server]: Activating backup
[component_container_isolated-1] [INFO] [1690191314.789388959] [behavior_server]: Activating drive_on_heading
[component_container_isolated-1] [INFO] [1690191314.789407097] [behavior_server]: Activating wait
[component_container_isolated-1] [INFO] [1690191314.789441709] [behavior_server]: Creating bond (behavior_server) to lifecycle manager.
[rviz2-2] [ERROR] [1690191314.841467495] [rviz2]: Lookup would require extrapolation into the future.  Requested time 1690191315.028409 but the latest data is at time 1690191314.844689, when looking up transform from frame [laser] to frame [map]
[component_container_isolated-1] [INFO] [1690191314.904935869] [lifecycle_manager_navigation]: Server behavior_server connected with bond.
[component_container_isolated-1] [INFO] [1690191314.905027757] [lifecycle_manager_navigation]: Activating bt_navigator
[component_container_isolated-1] [INFO] [1690191314.905343972] [bt_navigator]: Activating
[component_container_isolated-1] [ERROR] [1690191314.913983498] [bt_navigator]: Exception when loading BT: Error at line 12: -> Node not recognized: RemovePassedGoals
[component_container_isolated-1] [ERROR] [1690191314.914039883] [bt_navigator]: Error loading XML file: /opt/ros/humble/share/nav2_bt_navigator/behavior_trees/navigate_through_poses_w_replanning_and_recovery.xml
[component_container_isolated-1] [ERROR] [1690191314.914285311] [lifecycle_manager_navigation]: Failed to change state for node: bt_navigator
[component_container_isolated-1] [ERROR] [1690191314.914319433] [lifecycle_manager_navigation]: Failed to bring up all requested nodes. Aborting bringup.
[rviz2-2] [ERROR] [1690191315.034018621] [rviz2]: Lookup would require extrapolation into the future.  Requested time 1690191315.229664 but the latest data is at time 1690191315.044649, when looking up transform from frame [laser] to frame [map]
[rviz2-2] [ERROR] [1690191315.225699860] [rviz2]: Lookup would require extrapolation into the future.  Requested time 1690191315.429646 but the latest data is at time 1690191315.234821, when looking up transform from frame [laser] to frame [map]
[rviz2-2] [ERROR] [1690191315.449285899] [rviz2]: Lookup would require extrapolation into the future.  Requested time 1690191315.631042 but the latest data is at time 1690191315.454719, when looking up transform from frame [laser] to frame [map]
[rviz2-2] [ERROR] [1690191315.641193922] [rviz2]: Lookup would require extrapolation into the future.  Requested time 1690191315.831727 but the latest data is at time 1690191315.654622, when looking up transform from frame [laser] to frame [map]
[rviz2-2] [ERROR] [1690191315.833123847] [rviz2]: Lookup would require extrapolation into the future.  Requested time 1690191316.032315 but the latest data is at time 1690191315.844650, when looking up transform from frame [laser] to frame [map]
[rviz2-2] [ERROR] [1690191316.025082209] [rviz2]: Lookup would require extrapolation into the future.  Requested time 1690191316.233120 but the latest data is at time 1690191316.034711, when looking up transform from frame [laser] to frame [map]
[rviz2-2] [ERROR] [1690191316.249902900] [rviz2]: Lookup would require extrapolation into the future.  Requested time 1690191316.433916 but the latest data is at time 1690191316.264642, when looking up transform from frame [laser] to frame [map]
[rviz2-2] [ERROR] [1690191316.441744796] [rviz2]: Lookup would require extrapolation into the future.  Requested time 1690191316.634640 but the latest data is at time 1690191316.454628, when looking up transform from frame [laser] to frame [map]
[rviz2-2] [ERROR] [1690191316.633802662] [rviz2]: Lookup would require extrapolation into the future.  Requested time 1690191316.835461 but the latest data is at time 1690191316.644665, when looking up transform from frame [laser] to frame [map]
[rviz2-2] [ERROR] [1690191316.829746171] [rviz2]: Lookup would require extrapolation into the future.  Requested time 1690191317.036142 but the latest data is at time 1690191316.844694, when looking up transform from frame [laser] to frame [map]
[rviz2-2] [ERROR] [1690191317.049639178] [rviz2]: Lookup would require extrapolation into the future.  Requested time 1690191317.236092 but the latest data is at time 1690191317.064657, when looking up transform from frame [laser] to frame [map]
[rviz2-2] [ERROR] [1690191317.241241788] [rviz2]: Lookup would require extrapolation into the future.  Requested time 1690191317.437564 but the latest data is at time 1690191317.254609, when looking up transform from frame [laser] to frame [map]
[rviz2-2] [ERROR] [1690191317.433290333] [rviz2]: Lookup would require extrapolation into the future.  Requested time 1690191317.638300 but the latest data is at time 1690191317.444693, when looking up transform from frame [laser] to frame [map]
[rviz2-2] [ERROR] [1690191317.631798401] [rviz2]: Lookup would require extrapolation into the future.  Requested time 1690191317.839085 but the latest data is at time 1690191317.644674, when looking up transform from frame [laser] to frame [map]
[rviz2-2] [ERROR] [1690191317.849929855] [rviz2]: Lookup would require extrapolation into the future.  Requested time 1690191318.039816 but the latest data is at time 1690191317.844651, when looking up transform from frame [laser] to frame [map]
[rviz2-2] [ERROR] [1690191318.042559814] [rviz2]: Lookup would require extrapolation into the future.  Requested time 1690191318.240542 but the latest data is at time 1690191318.054618, when looking up transform from frame [laser] to frame [map]
[rviz2-2] [ERROR] [1690191318.233017984] [rviz2]: Lookup would require extrapolation into the future.  Requested time 1690191318.441166 but the latest data is at time 1690191318.244692, when looking up transform from frame [laser] to frame [map]
[rviz2-2] [INFO] [1690191322.009445670] [rviz2]: Message Filter dropping message: frame 'laser' at time 1690191312.020 for reason 'the timestamp on the message is earlier than all the data in the transform cache'
[rviz2-2] [INFO] [1690191322.207491832] [rviz2]: Message Filter dropping message: frame 'laser' at time 1690191312.221 for reason 'the timestamp on the message is earlier than all the data in the transform cache'
[rviz2-2] [INFO] [1690191322.407573140] [rviz2]: Message Filter dropping message: frame 'laser' at time 1690191312.421 for reason 'the timestamp on the message is earlier than all the data in the transform cache'
[rviz2-2] [INFO] [1690191322.607550335] [rviz2]: Message Filter dropping message: frame 'laser' at time 1690191312.622 for reason 'the timestamp on the message is earlier than all the data in the transform cache'
[rviz2-2] [INFO] [1690191322.807649652] [rviz2]: Message Filter dropping message: frame 'laser' at time 1690191312.823 for reason 'the timestamp on the message is earlier than all the data in the transform cache'
[rviz2-2] [INFO] [1690191333.536219810] [rviz2]: Setting estimate pose: Frame:map, Position(0.0717502, -0.137756, 0), Orientation(0, 0, -0.00510166, 0.999987) = Angle: -0.0102034
[component_container_isolated-1] [INFO] [1690191333.536470076] [amcl]: initialPoseReceived
[component_container_isolated-1] [INFO] [1690191333.536571655] [amcl]: Setting pose (1690191333.536572): 0.072 -0.138 -0.010
[rviz2-2] Start navigation
[rviz2-2] [INFO] [1690191341.780735868] [rviz2]: NavigateToPose will be called using the BT Navigator's default behavior tree.
[rviz2-2] [ERROR] [1690191341.781289391] [rviz2]: Goal was rejected by server

# Raspberry Pi Mouse側のログ
[INFO] [launch]: All log files can be found below /home/ubuntu/.ros/log/2023-07-24-09-19-40-059675-ubuntu-2713
[INFO] [launch]: Default logging verbosity is set to INFO
[INFO] [raspimouse-1]: process started with pid [2724]
[INFO] [hlds_laser_publisher-2]: process started with pid [2726]
[INFO] [robot_state_publisher-3]: process started with pid [2728]
[INFO] [joint_state_publisher-4]: process started with pid [2730]
[hlds_laser_publisher-2] [INFO] [1690190381.603958857] [hlds_laser_publisher]: Init hlds_laser_publisher Node Main
[hlds_laser_publisher-2] [INFO] [1690190381.607696224] [hlds_laser_publisher]: port : /dev/ttyUSB0 frame_id : laser
[robot_state_publisher-3] [INFO] [1690190381.645700547] [robot_state_publisher]: got segment base_footprint
[robot_state_publisher-3] [INFO] [1690190381.648065348] [robot_state_publisher]: got segment base_link
[robot_state_publisher-3] [INFO] [1690190381.649948560] [robot_state_publisher]: got segment laser
[robot_state_publisher-3] [INFO] [1690190381.651835272] [robot_state_publisher]: got segment lds_multi_mount_link
[robot_state_publisher-3] [INFO] [1690190381.652849433] [robot_state_publisher]: got segment left_wheel
[robot_state_publisher-3] [INFO] [1690190381.652901858] [robot_state_publisher]: got segment lf_lightsensor_link
[robot_state_publisher-3] [INFO] [1690190381.652935895] [robot_state_publisher]: got segment lightsensors
[robot_state_publisher-3] [INFO] [1690190381.652971895] [robot_state_publisher]: got segment ls_lightsensor_link
[robot_state_publisher-3] [INFO] [1690190381.653008321] [robot_state_publisher]: got segment rf_lightsensor_link
[robot_state_publisher-3] [INFO] [1690190381.653043746] [robot_state_publisher]: got segment right_wheel
[robot_state_publisher-3] [INFO] [1690190381.653078635] [robot_state_publisher]: got segment rs_lightsensor_link
[raspimouse-1] [INFO] [1690190381.797835763] [raspimouse]: Configuring Raspimouse node
[raspimouse-1] [INFO] [1690190381.827248578] [raspimouse]: Turned motors off
[raspimouse-1] [INFO] [1690190381.829249030] [raspimouse]: Testing counters
[raspimouse-1] [INFO] [1690190381.829505417] [raspimouse]: Using pulse counters for odometry
[raspimouse-1] [INFO] [1690190381.832628937] [raspimouse]: Configuring done
[raspimouse-1] [INFO] [1690190381.841444035] [raspimouse]: Activating Raspimouse node
[raspimouse-1] [INFO] [1690190381.841672256] [raspimouse]: Turned motors on
[raspimouse-1] [INFO] [1690190381.841759626] [raspimouse]: Raspimouse node activated
[joint_state_publisher-4] [INFO] [1690190382.862456256] [joint_state_publisher]: Waiting for robot_description to be published on the robot_description topic...
[raspimouse-1] [INFO] [1690190441.848173264] [raspimouse]: Watchdog timeout; stopping motors
[INFO] [launch]: All log files can be found below /home/ubuntu/.ros/log/2023-07-24-09-19-40-059675-ubuntu-2713
[INFO] [launch]: Default logging verbosity is set to INFO
[INFO] [raspimouse-1]: process started with pid [2724]
[INFO] [hlds_laser_publisher-2]: process started with pid [2726]
[INFO] [robot_state_publisher-3]: process started with pid [2728]
[INFO] [joint_state_publisher-4]: process started with pid [2730]
[hlds_laser_publisher-2] [INFO] [1690190381.603958857] [hlds_laser_publisher]: Init hlds_laser_publisher Node Main
[hlds_laser_publisher-2] [INFO] [1690190381.607696224] [hlds_laser_publisher]: port : /dev/ttyUSB0 frame_id : laser
[robot_state_publisher-3] [INFO] [1690190381.645700547] [robot_state_publisher]: got segment base_footprint
[robot_state_publisher-3] [INFO] [1690190381.648065348] [robot_state_publisher]: got segment base_link
[robot_state_publisher-3] [INFO] [1690190381.649948560] [robot_state_publisher]: got segment laser
[robot_state_publisher-3] [INFO] [1690190381.651835272] [robot_state_publisher]: got segment lds_multi_mount_link
[robot_state_publisher-3] [INFO] [1690190381.652849433] [robot_state_publisher]: got segment left_wheel
[robot_state_publisher-3] [INFO] [1690190381.652901858] [robot_state_publisher]: got segment lf_lightsensor_link
[robot_state_publisher-3] [INFO] [1690190381.652935895] [robot_state_publisher]: got segment lightsensors
[robot_state_publisher-3] [INFO] [1690190381.652971895] [robot_state_publisher]: got segment ls_lightsensor_link
[robot_state_publisher-3] [INFO] [1690190381.653008321] [robot_state_publisher]: got segment rf_lightsensor_link
[robot_state_publisher-3] [INFO] [1690190381.653043746] [robot_state_publisher]: got segment right_wheel
[robot_state_publisher-3] [INFO] [1690190381.653078635] [robot_state_publisher]: got segment rs_lightsensor_link
[raspimouse-1] [INFO] [1690190381.797835763] [raspimouse]: Configuring Raspimouse node
[raspimouse-1] [INFO] [1690190381.827248578] [raspimouse]: Turned motors off
[raspimouse-1] [INFO] [1690190381.829249030] [raspimouse]: Testing counters
[raspimouse-1] [INFO] [1690190381.829505417] [raspimouse]: Using pulse counters for odometry
[raspimouse-1] [INFO] [1690190381.832628937] [raspimouse]: Configuring done
[raspimouse-1] [INFO] [1690190381.841444035] [raspimouse]: Activating Raspimouse node
[raspimouse-1] [INFO] [1690190381.841672256] [raspimouse]: Turned motors on
[raspimouse-1] [INFO] [1690190381.841759626] [raspimouse]: Raspimouse node activated
[joint_state_publisher-4] [INFO] [1690190382.862456256] [joint_state_publisher]: Waiting for robot_description to be published on the robot_description topic...
[raspimouse-1] [INFO] [1690190441.848173264] [raspimouse]: Watchdog timeout; stopping motors

RVizのスクリーンショット

その他

bt_navigatorが上手く起動できていないみたいですね
[component_container_isolated-1] [INFO] [1690191314.905343972] [bt_navigator]: Activating
[component_container_isolated-1] [ERROR] [1690191314.913983498] [bt_navigator]: Exception when loading BT: Error at line 12: -> Node not recognized: RemovePassedGoals
[component_container_isolated-1] [ERROR] [1690191314.914039883] [bt_navigator]: Error loading XML file: /opt/ros/humble/share/nav2_bt_navigator/behavior_trees/navigate_through_poses_w_replanning_and_recovery.xml
[component_container_isolated-1] [ERROR] [1690191314.914285311] [lifecycle_manager_navigation]: Failed to change state for node: bt_navigator
[component_container_isolated-1] [ERROR] [1690191314.914319433] [lifecycle_manager_navigation]: Failed to bring up all requested nodes. Aborting bringup.

2点確認してほしいことが有ります

以下のファイルがあって、中身が書かれていそうなこと

XML file: /opt/ros/humble/share/nav2_bt_navigator/behavior_trees/navigate_through_poses_w_replanning_and_recovery.xml

Error at line 12: -> Node not recognized: RemovePassedGoalsとのことなので、RemovePassedGoalsに関する情報が上記ファイルに書かれていること

また、コマンドを書くときは、'(シングルくオーテーション)じゃなくて`(アポストロフィ)で囲うと上手く表示ができますよ。
'not this' but this

ありがとうございます！
/opt/ros/humble/share/nav2_bt_navigator/behavior_trees/navigate_through_poses_w_replanning_and_recovery.xmlが存在していることを確認しました。こちらのファイルの中身を添付します。
<!--
  This Behavior Tree replans the global path periodically at 1 Hz through an array of poses continuously
   and it also has recovery actions specific to planning / control as well as general system issues.
-->
<root main_tree_to_execute="MainTree">
  <BehaviorTree ID="MainTree">
    <RecoveryNode number_of_retries="6" name="NavigateRecovery">
      <PipelineSequence name="NavigateWithReplanning">
        <RateController hz="0.333">
          <RecoveryNode number_of_retries="1" name="ComputePathThroughPoses">
            <ReactiveSequence>
              <RemovePassedGoals input_goals="{goals}" output_goals="{goals}" radius="0.7"/>
              <ComputePathThroughPoses goals="{goals}" path="{path}" planner_id="GridBased"/>
            </ReactiveSequence>
            <ClearEntireCostmap name="ClearGlobalCostmap-Context" service_name="global_costmap/clear_entirely_global_costmap"/>
          </RecoveryNode>
        </RateController>
        <RecoveryNode number_of_retries="1" name="FollowPath">
          <FollowPath path="{path}" controller_id="FollowPath"/>
          <ClearEntireCostmap name="ClearLocalCostmap-Context" service_name="local_costmap/clear_entirely_local_costmap"/>
        </RecoveryNode>
      </PipelineSequence>
      <ReactiveFallback name="RecoveryFallback">
        <GoalUpdated/>
        <RoundRobin name="RecoveryActions">
          <Sequence name="ClearingActions">
            <ClearEntireCostmap name="ClearLocalCostmap-Subtree" service_name="local_costmap/clear_entirely_local_costmap"/>
            <ClearEntireCostmap name="ClearGlobalCostmap-Subtree" service_name="global_costmap/clear_entirely_global_costmap"/>
          </Sequence>
          <Spin spin_dist="1.57"/>
          <Wait wait_duration="5"/>
          <BackUp backup_dist="0.30" backup_speed="0.05"/>
        </RoundRobin>
      </ReactiveFallback>
    </RecoveryNode>
  </BehaviorTree>
</root>

ありがとうございます。いますねぇ、RemovePassedGoals.......

/opt/ros/humble/share/nav2_bt_navigator/behavior_trees/navigate_through_poses_w_replanning_and_recovery.xmlの以下の行を削除（コメントアウト）するとNavigationが動くことを確認しました。解決策になるかは分かりませんが、とりあえず動きはします。
<RemovePassedGoals input_goals="{goals}" output_goals="{goals}" radius="0.7"/>
<ComputePathThroughPoses goals="{goals}" path="{path}" planner_id="GridBased"/>

また、以下の2点も確認しました。

Turtlebot3のGazeboシミュレータではNavigationが動くことを確認
CycloneDDSに切り替えてもRaspberry Pi MouseのNavigationは動かない

Navigationが動かない問題についてのメモ

Navigation2のbt_navigatorが下記のxmlファイルを正常に読み込めなくてエラーを吐いている
/opt/ros/humble/share/nav2_bt_navigator/behavior_trees/navigate_through_poses_w_replanning_and_recovery.xml
このxmlファイルはインストールしてからそのままの状態、何が悪いのか分からない
params/raspimouse.yamlがHumbleに対応していないかも？（この問題に影響しているかは不明）

params/raspimouse.yamlのbt_navigatorの項目に下記の行を追加するとNavigationが動きました。
Behavior Treeのノードが足りていなかったことが原因のようです。
- nav2_compute_path_through_poses_action_bt_node
- nav2_remove_passed_goals_action_bt_node

下記のように追加しました。
bt_navigator:
  ros__parameters:
    use_sim_time: False
    global_frame: map
    robot_base_frame: base_link
    odom_topic: /odom
    default_bt_xml_filename: "navigate_w_replanning_and_recovery.xml"
    plugin_lib_names:
    - nav2_compute_path_to_pose_action_bt_node
    - nav2_follow_path_action_bt_node
    - nav2_back_up_action_bt_node
    - nav2_spin_action_bt_node
    - nav2_wait_action_bt_node
    - nav2_clear_costmap_service_bt_node
    - nav2_is_stuck_condition_bt_node
    - nav2_goal_reached_condition_bt_node
    - nav2_goal_updated_condition_bt_node
    - nav2_initial_pose_received_condition_bt_node
    - nav2_reinitialize_global_localization_service_bt_node
    - nav2_rate_controller_bt_node
    - nav2_distance_controller_bt_node
    - nav2_speed_controller_bt_node
    - nav2_recovery_node_bt_node
    - nav2_pipeline_sequence_bt_node
    - nav2_round_robin_node_bt_node
    - nav2_transform_available_condition_bt_node
    - nav2_time_expired_condition_bt_node
    - nav2_distance_traveled_condition_bt_node
    - nav2_compute_path_through_poses_action_bt_node
    - nav2_remove_passed_goals_action_bt_node

上記の対応で、僕も手元のラズパイマウスが無事ナビゲーションできたことを確認しました〜

#6 で解決済みです。

authors: ShotaAk YusukeKato shu-rt


text:
Update change log and bump up version for Foxy release

What does this implement/fix?

Foxy リリースに向けてChangelog と バージョンを更新しました。
Checklists

[x]  I have read the CONTRIBUTING guidelines.
[x]  I have checked to ensure there aren't other open Pull Requests for the same change.

余計なファイルが入ったのでやり直します。

source: gharchive/pull-request

license_source: bigquery


text:
List View issue list

Bug 1

In frontend of list view the excerpt is not visible. The excerpt option is by default enabled, and the excerpt is also visible in backend but when checked the preview it is not visible in frontend. ( Note: When I first selected the List block excerpt was on and the excerpt was not visible in backend/frotnend both. This happened only once )

Steps to Reproduce

Select the List view block
Check the settings, excerpt option is by default enabled
Check the backend, excerpt is visible
Check the frontend, excerpt is not visible

Screenshots
https://user-images.githubusercontent.com/41000648/103737012-5ece9980-5017-11eb-83d3-0cc99c4f4420.mp4

Bug 2

When only title, author and date option is enabled, there is space issue between the author name and the date. In backend the space is less ( which is looking fine ), but in frontend the space is more. Both backend and frontend should have equal spacing between author and date paramters.

Note: Applies to both view when images are displayed left as well as when images are displayed right.
Screenshot of backend

Screenshot of frontend

8th Feb 2021 QA status on the changes done as per the client requirements
Cross-checked the above listed issues with the latest changes on https://google-webstories.rt.gw/ and these issues are not valid now.
Hence, closing this issue.
cc: @maitreyie-chavan

repo: rtCamp/web-stories-wp


text:
favicon

Please provide favicon in .ico format, which is to be expected for https://readthedocs.org/favicon.ico or content-type 'image/x-icon', instead PNG.
Or just use PNG image and provide right content-type:
<link rel="icon" type="image/png" href="https://readthedocs.org/favicon.png" />

Thanks

Hm... you do provide right icon in HTML source code as:
<link rel="icon" type="image/png" href="https://media.readthedocs.org/images/favicon.png">

but anyways https://readthedocs.org/favicon.ico exists as PNG image.
Offending file is at https://github.com/rtfd/readthedocs.org/blob/master/media/images/favicon.ico which has wrong extension and the same file exists also as https://github.com/rtfd/readthedocs.org/blob/master/media/images/favicon.png.
Gimp can convert png to ico, or imagemagick, or else.

I would like to pick this up. As right icon is provided in HTML source code, and the related file exist at https://github.com/rtfd/readthedocs.org/blob/master/media/images/favicon.png, should  https://github.com/rtfd/readthedocs.org/blob/master/media/images/favicon.ico be removed to fix this?
What is the right way to fix this issue?

Hello @tapasweni-pathak, sorry, this has already been resolved in #2334. I'd suggest to look the list at https://github.com/rtfd/readthedocs.org/issues?q=is%3Aissue+is%3Aopen+label%3A"Good+First+Bug" if you have time to work on other issues.
Thanks!

Cool. Sure.

authors: berkerpeksag klonuo tapasweni-pathak


text:
cleanup, add collectstatic, and blurb about builds

This commit aims to solve the problems encountered in issue #1867 revolving around frustrations with getting an on-premises server started and working.
I've done the following:

cleaned up the "step flow"...This now reads a lot more sane
added the step around collectstatic to ensure static assets are copied
inserted stanza warning about port assignment for builds to work successfully.

Thanks for the update here, looks great! :+1:

authors: InAnimaTe agjohnson


text:
Notify the user when deleting a superproject

Closes #3742

@stsewd
Here is the screenshot.

Also, I have updated the code.

OK. I tried to do a change suggestion and I did it wrong and a proper commit was created. I updated the copy on the test as well.
I think this is ready to be merged. @stsewd do you agree?

authors: dojutsu-user humitos


text:
Feature Request: array mutations within an object

I'm trying to use seamless-immutable as my data option in redux and I'm trying to add a demo "add-post" action which would push a new post into the post array which is within the state object (also an immutable object created with const initialState = Immutable({ posts: [], post: {} });. Using the following, which I would assume would work:
case ActionTypes.ADD_POST :
      return state.update('posts', list => list.push(
        {
          name: action.name,
          title: action.title,
          content: action.content,
          slug: action.slug,
          id: action.id,
          dateadded: action.dateadded,
          updateddate: action.updateddate,
        },
      ));

, causes an error. I could do something like this:
return Immutable({
        posts: [{
          name: action.name,
          title: action.title,
          content: action.content,
          slug: action.slug,
          id: action.id,
          dateadded: action.dateadded,
          updateddate: action.updateddate,
        }].concat(state.posts),
        post: state.post });

but I was hoping for a more elegant, functional programming-y solution 😝. However, I realize that a feature that would allow this sort of nested mutation might go against the philosophy of this module, but I thought I'd suggest it anyway :smile:.

I realize that a feature that would allow this sort of nested mutation might go against the philosophy of this module, but I thought I'd suggest it anyway :smile:.

As you predicted, I'm not open to introducing mutations. 😉  Appreciate the thoughtful post though!

authors: gigavinyl rtfeldman

repo: rtfeldman/seamless-immutable


text:
unexpected argument mutation

I observe some unexpected behavior with argument and variant. They seem more like a bug than a feature.
Here are my code snippets. It compiles with GCC on a Linux box.
#include <iostream>
#include <vector>
#include "rttr/registration.h"
#include "rttr/type.h"

using namespace std;
using namespace rttr;

int sum4(int x1, int x2, int x3, int x4) {
    return (x1+x2+x3+x4);
}

RTTR_REGISTRATION { registration::method("sum4", &sum4); }

int main() {
    vector<argument> args;
    for (int i = 1; i<=4; ++i) {
        variant v = i;
        args.push_back(v);
    }
    for (auto arg : args) {
        cout << arg.get_value<int>() << endl;
    }
    variant ret = type::invoke("sum4", args);
    if (ret.is_valid()) {
        cout << ret.to_int() << endl;
    }
    for (auto arg: args) {
        cout << arg.get_value<int>() << endl;
    }
}

My expected output is
1
2
3
4
10
1
2
3
4

The actual output is
4
4
4
4
16
16
16
16
16

This seems rather weird to me. Does it have something to do with perfect forwarding or global reference?
If I add this line variant tmp = -1; right below  variant ret = type::invoke("sum4", args);, then the output will be
4
4
4
4
16
-1
-1
-1
-1

It seems that all values in the vector of arguments args refer to the closest (most recent) value of variant type.
Is this desired behavior?
How can I use invoke if I want to pass in multiple arguments that are only known at runtime? I know type::invoke("sum", {1, 2, 3, 4}) will always work.

In your code, you expect that argument can store data. However, argument acts like a void * with type information so that all elements in the args point to the same variant v. You can use vector<variant> to store data and convert it to vector<argument> when you need to invoke the function.

Thank you! I will close the issue then.

repo: rttrorg/rttr

license: mit


text:
Merge pull request #1 from rubensrsjunior13/07-Google2

ok

ok


text:
Strings are not extracted from es6 modules

import angular from 'angular';

angular.controller('GreetingController', function(gettextCatalog) {
    this.message = gettextCatalog.getString("Hello");
});

Seems angular-gettext does not support ES6, but you can transform into ES5 with babel, and then extract strings.
For example, I use gulp to do that:
var babel = require('gulp-babel');
var plumber = require('gulp-plumber');
var gettext = require('gulp-angular-gettext');
gulp.task('extract-strings', function (done) {
  gulp.src(['src/**/*.js'])
    .pipe(plumber())
    .pipe(babel({ presets: ['es2015'] }))
    .pipe(gulp.src(['src/components/**/*.html']))
    .pipe(gettext.extract('template.pot', { attributes: ['placeholder'] }))
    .pipe(gulp.dest('po/'))
    .on('end', done);
});

This fixed in gettext-tools v2.2.2 https://github.com/rubenv/angular-gettext-tools/blob/v2.2.2/lib/extract.js#L175

authors: ekaragodin ramonsan

repo: rubenv/angular-gettext


text:
portal chart icon visibility

Describe the bug
Using the portal in dark mode, the Active chart Icons for "filter on the selected points" (funnel with plus sign) and "select the enclosed points" (checkmark) are not very visible due to their outline color (black).
To Reproduce
Steps to reproduce the behavior:

Go to 'active chart in the portal'
Click on 'select'
Select a subset of data points
Icons for "filter on the selected points" (funnel with plus sign) and "select the enclosed points" (checkmark) appear but I couldn't see them until I hovered over them.

Expected behavior
All of the icons to be easy to see while in dark mode
Screenshots
If applicable, add screenshots to help explain your problem.

URL
If applicable, cut and paste the URL from your browser at which the issue occurred
Desktop (please complete the following information):

OS: macOS ventura 13.4.1
Browser: Safari
Version: 16.5.1

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

Thank you very much for this report.  I've verified this and passed it on to the development team as a bug.  We are still working through a few residual items from the recent introduction of dark mode.

authors: GloriaFA gpdf


text:
Cop idea: detect .none()

Actual behavior
I have the code:
module ApplicationHelper
  def my_method
    User.where(id: nil)
    User.where(id: 0)
    User.where(id: [])
    User.where(id: {})
    User.limit(nil)
    User.limit(0)
  end
end

I run rubocop and don't get any offences:
ydakuka@yauhenid:~/Work/project$ bin/rails_docker rubocop app/helpers/application_helper.rb
Inspecting 1 file
.

1 file inspected, no offenses detected

Expected behavior
I expected to receive the following code:
module ApplicationHelper
  def my_method
    User.none # for all cases
  end
end

https://github.com/rubocop/rails-style-guide/issues/337

repo: rubocop/rubocop-rails


text:
Ship a config for InternalAffairs

InternalAffairs/CopDescription and InternalAffairs/UselessMessageAssertion want to only look at a specific subset of files. To do that, they override the relevant_file? method.
Instead, just treat InternalAffairs like a RuboCop extension and inject the config so it goes through the usual processes.
There are more cops that could be added here (many only concern themselves with either specs or library code) but I'll leave that for a subsequent PR.
This removes the tests from https://github.com/rubocop/rubocop/pull/13209, the process of config inheritance is already well-tested and there nothing special here anymore. I've manually verified that this change works correctly in rubocop-rails and here as well of course (i.e. there are still offenses when there should be).
@splattael, do you want to give this a try and see if this works for you?

Before submitting the PR make sure the following are checked:

[x] The PR relates to only one subject with a clear title and description in grammatically correct, complete sentences.
[x] Wrote good commit messages.
[ ] Commit message starts with [Fix #issue-number] (if the related issue exists).
[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[ ] Added tests.
[x] Ran bundle exec rake default. It executes all tests and runs RuboCop on its own code.
[ ] Added an entry (file) to the changelog folder named {change_type}_{change_description}.md if the new code introduces user-observable changes. See changelog entry format for details.

@Earlopain Thanks for the quick PR :bow:
This looks good to me and my local testing worked! :tada: Great work :nerd_face:
I left two observations - nothing blocking - just my thoughts during testing :grin:

Good improvement!

authors: Earlopain bbatsov splattael

repo: rubocop/rubocop


text:
Retained Grape::Http::Headers in memory instead of new ones created.

I ran a memory profiling (memory_profiler gem) on my app by hitting our Grape api first. I found it odd that it retains a bunch of http verbs when they are defined as const in Grape::Http::Headers :
       354  "HEAD"
       353  /Users/eproulx/.rbenv/versions/2.4.9/lib/ruby/gems/2.4.0/gems/grape-1.2.6/lib/grape/router/route.rb:67
         1  /Users/eproulx/.rbenv/versions/2.4.9/lib/ruby/gems/2.4.0/gems/grape-1.2.6/lib/grape/router.rb:30

       352  "GET"
       351  /Users/eproulx/.rbenv/versions/2.4.9/lib/ruby/gems/2.4.0/gems/grape-1.2.6/lib/grape/router/route.rb:67
         1  /Users/eproulx/.rbenv/versions/2.4.9/lib/ruby/gems/2.4.0/gems/grape-1.2.6/lib/grape/router.rb:30

       168  "POST"
       107  /Users/eproulx/.rbenv/versions/2.4.9/lib/ruby/gems/2.4.0/gems/grape-1.2.6/lib/grape/router/route.rb:67
        60  /Users/eproulx/.rbenv/versions/2.4.9/lib/ruby/gems/2.4.0/gems/grape-1.2.6/lib/grape/api/instance.rb:230
         1  /Users/eproulx/.rbenv/versions/2.4.9/lib/ruby/gems/2.4.0/gems/grape-1.2.6/lib/grape/router.rb:30

       113  "PATCH"
        82  /Users/eproulx/.rbenv/versions/2.4.9/lib/ruby/gems/2.4.0/gems/grape-1.2.6/lib/grape/router/route.rb:67
        30  /Users/eproulx/.rbenv/versions/2.4.9/lib/ruby/gems/2.4.0/gems/grape-1.2.6/lib/grape/api/instance.rb:230
         1  /Users/eproulx/.rbenv/versions/2.4.9/lib/ruby/gems/2.4.0/gems/grape-1.2.6/lib/grape/router.rb:30

        50  "DELETE"
        46  /Users/eproulx/.rbenv/versions/2.4.9/lib/ruby/gems/2.4.0/gems/grape-1.2.6/lib/grape/router/route.rb:67
         3  /Users/eproulx/.rbenv/versions/2.4.9/lib/ruby/gems/2.4.0/gems/grape-1.2.6/lib/grape/api/instance.rb:230
         1  /Users/eproulx/.rbenv/versions/2.4.9/lib/ruby/gems/2.4.0/gems/grape-1.2.6/lib/grape/router.rb:30

        43  "PUT"
        34  /Users/eproulx/.rbenv/versions/2.4.9/lib/ruby/gems/2.4.0/gems/grape-1.2.6/lib/grape/router/route.rb:67
         8  /Users/eproulx/.rbenv/versions/2.4.9/lib/ruby/gems/2.4.0/gems/grape-1.2.6/lib/grape/api/instance.rb:230
         1  /Users/eproulx/.rbenv/versions/2.4.9/lib/ruby/gems/2.4.0/gems/grape-1.2.6/lib/grape/router.rb:30

I looked at the code and made a fix by detecting supported_methods instead of retaining the route method received.
Actual memory footprint on first call
Total allocated: 50532358 bytes (526479 objects)
Total retained:  6386850 bytes (17587 objects)

And with the improvement
Total allocated: 50453158 bytes (524521 objects)
Total retained:  6346610 bytes (16603 objects)

1958 less objects allocated (79 200 bytes)
984 less objects retained (40 240 bytes)

So for your example it's 80K. How much slower is endpoint mounting?

A lot of endpoints .. Is there an easyway to count them ? Like Grape::Api.endpoints.count ?
For the endpoint mounting, i'll benchmark my app boot time.

A lot of endpoints .. Is there an easyway to count them ? Like Grape::Api.endpoints.count ?

I am not sure, but I think .routes will get you started :)

For the endpoint mounting, i'll benchmark my app boot time.

Let us know when you're ready/happy with this PR! Looking forward to merge.

I dont know why but now I'm just 2x slower instead of almost 6
Warming up --------------------------------------
Hash with case insensitive
                       309.328k i/100ms
              detect   173.918k i/100ms
Calculating -------------------------------------
Hash with case insensitive
                          7.785M (± 4.9%) i/s -     38.975M in   5.021621s
              detect      2.699M (± 1.0%) i/s -     13.566M in   5.026560s

Comparison:
Hash with case insensitive:  7785176.2 i/s
              detect:  2699078.6 i/s - 2.88x  slower

Anyway, the reality is having a case-insensitive hash is really hard (no easy way). I mean we would upcase everything like before but we wont have a substantial gain (less memory usage) anymore. Also, since its a static array, worst case scenario is O(7). So, I'm not sure the 2x slower is a big issue here.

I don't think it's a big issue, I was just trying to make this code simpler. Your call.

I merged this, thanks.

authors: dblock ericproulx

repo: ruby-grape/grape


text:
Handle =" as a designator for Excel 'formulas'

We have a .CSV from a vendor that quotes numeric fields that should be treated as strings with =" -- for example (excerpt from a real file)
USD,="6161015399000000",54585234
I'm going to experiment with a custom converter. If that works, I'll close this issue.

I agree that a custom converter would be the right approach to solving this problem.
That being the case, should we close this issue?

authors: bmo stevendaniels

repo: ruby/csv


text:
build: Use bundler-cache in CI

This PR:

uses the bundler-cache feature of the Ruby-maintained Action setup-ruby. See ruby/setup-ruby for more information.
Avoids duplicate CI Jobs for Pull Requests by only running tests on the push event for "master" branch.

@nobu 👋 I hope this merge was not premature. (I guess you have a lot to review, and took a chance merging this.)

To run the tests, pushing to master or PRs are needed?

@nobu One of those two, is the idea.

If we need to refine the configuration somehow, let's do that. Or return to what it was before. Avoiding duplicates was my only goal, here.

I would like to add, there's another way to skip double-builds. Inspiration: https://github.com/thoughtbot/factory_bot/pull/1491

authors: nobu olleolleolle

repo: ruby/drb


text:
add ericgpks as a reviewer to some rails dependency gems

By reading this issue https://github.com/ruby/gem_rbs_collection/issues/558, I would like to join as a reviewer in some gems.
I add me as a reviewer in this PR.

@ericgpks
Thank you for expressing your intention.
However, I am sorry, but I am considering removing the aws-sdk gem from gem_rbs_collection. (I haven't deleted it yet because I haven't been able to verify what will happen if it's removed.)
Even if you are added as a reviewer, your first task will likely be to review the removal.
ref: https://github.com/ruby/gem_rbs_collection/issues/511

@ksss
Thank you for sharing the situation. I got it.

authors: ericgpks ksss


text:
Improve backtrace location specs

Improve specs for backtrace location labels' behaviors.

Hey @eregon, anything I can do to improve this, or did you just go off on some amazing vacation while us poor souls are still stuck on GitHub? ;)

@ivoanjo The later, I just returned from vacation, should have written that here :)
Merging now, thank you for the PR!

authors: eregon ivoanjo

repo: ruby/spec


text:
Apply refactor to DistributionDestroyService similar to the Create/Update services

Summary
DistributionDestroyService (app/services/distribution_destroy_service.rb) is still using the older paradigm that cannot yet have a superclass extracted. It also has incomplete testing. In #1557, both app/services/distribution_create_service.rb and app/services/distribution_update_service.rb are refactored. We want to get parity with the Destroy Service so that we can do some additional refactoring.
Things to Consider

The end goal here is to extract a superclass, so look closely at both the Create and Update services for possible elements that could be promoted to a Superclass, as well as behaviors that can be made universal across all three service classes.
There is test coverage for DistributionDestroyService but it is minimal and does not cover the error cases. Let's get that up to :100:

Criteria for Completion

[ ] Tests pass
[ ] Class is refactored to be similar to the Create / Update services
[ ] Destroy Service has 100% coverage (currently at 80%, CreateService is at :100:)

I'll take a swing at this :)

authors: armahillo edwinthinks

repo: rubyforgood/diaper


text:
Update BarcodeItem Edit to Use New Theme

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

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

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

Hey, I'm going to update this one :)

authors: elainemattos maebeale


text:
As a Bank Admin I am seeing items in triplicate in the Dashboard

Summary
Items on the bank admin dashboard are being repeated in triplicate. Please view the below image to see the issue:

Things to Consider
This started happening late last year and causes issues for bank admins when they are trying to get a snapshot of Distributions, Donations and Diaper Drives.
Criteria for Completion

[ ] There should only be one line item for each distribution, donation, diaper drive.

Thanks @AngeVeza I can take a look at this

@AngeVeza actually this was fixed and was going to ship out with the latest release of human essentials. It was fixed in https://github.com/rubyforgood/human-essentials/pull/2638. I've gone ahead and released that code into production.
Please let the submitter that it should be fixed now.

authors: AngeVeza edwinthinks

repo: rubyforgood/human-essentials


text:
Update the email that partners get when they are approved to be more informative.

Summary
Update the email that partners get when they are approved.
Why
The current text is confusing if the banks are using the "Invite and Approve".  It also doesn't tell the partner what they are approved to do.
Details
##To see the email:
On local, sign in as org_admin1@example.com
Click on "Partner Agencies", then "All Partners" in the left hand menu
Click on "Review Applicant's Profile"
Click on "Approve Partner"
It will take a moment or two, but once the mail job runs, you should get a tab in your browser containing the email that is sent to the partner on approval.
It currently contains the text "[bank name] has approved your application."
What we should have
Change the text to "You have been approved to make requests for essentials to [bank name]."
Criteria for completion

[ ] text in email updated
[ ] any tests that refer to that text updated

Hey, I would like to work on this

Please do.

authors: cielf slusy


text:
Show all active partners on distributions page unrestricted by filter

Resolves #4834
Description
See #4834 for the issue and reproduction steps.
Type of change

Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?
Added a new request spec.
Screenshots
Before:
Filtering by date filter for day with no distributions => No partner dropdown box at all.

After:
No distributions after filtering but all active partners still selectable in dropdown.

Fixed the merge conflict, so this is ready for review again.


text:
not able to verify via SMS

Something wrong with twilio client

Actually this does not influence the operation of the exchange. It is just for customer data capture. But it is not necessary to import the openware key in new version.

authors: Guillerbr UbuntuEvangelist

repo: rubykube/microkube


text:
App: Added features for RSE Page

this also included changing the components and the table fixtures to reflect the fact that we have static gets and no streams here.

closes #302

repo: rucio/webui


text:
Compatibility issue: Does it work on Mac M1?

Hi @ruggi,
Thank you for creating this amazing tool! I was wondering if it is compatible with Mac M1. I encountered an error as below while typing "cal" in alfred:

Hi @ruggi,
Thank you for creating this amazing tool! I was wondering if it is compatible with Mac M1. I encountered an error as below while typing "cal" in alfred:

@heroc0111, @Budaa, @T0rukMakt0, @wolfkarl, @svenko99, @timmb, @volleysolutions, @Avivbens, @NouamaneTazi, @Budaa
I've created a pr fix this waiting for @ruggi to review and publish new release. In the mean time you can check out the fixed release from my fork!

Hi @ruggi,

Thank you for creating this amazing tool! I was wondering if it is compatible with Mac M1. I encountered an error as below while typing "cal" in alfred:

@heroc0111, @Budaa, @T0rukMakt0, @wolfkarl, @svenko99, @timmb, @volleysolutions, @Avivbens, @NouamaneTazi, @Budaa
I've created a pr fix this waiting for @ruggi to review and publish new release. In the mean time you can check out the fixed release from my fork!

Thanks a lot 🙏
Can you put a link to the PR?

Hi @ruggi,

Thank you for creating this amazing tool! I was wondering if it is compatible with Mac M1. I encountered an error as below while typing "cal" in alfred:

@heroc0111, @Budaa, @T0rukMakt0, @wolfkarl, @svenko99, @timmb, @volleysolutions, @Avivbens, @NouamaneTazi, @Budaa
I've created a pr fix this waiting for @ruggi to review and publish new release. In the mean time you can check out the fixed release from my fork!

Thanks a lot 🙏
Can you put a link to the PR?

It's here

authors: AaronHeee Avivbens viethung0823

repo: ruggi/calfred


text:
OpenInferenceCallbackHandler uses node IDs rather than hashes

Description
Change the OpenInferenceCallbackHandler to use node IDs rather than node hashes. Node hashes were originally chosen because of an issue reading in legacy LlamaIndex persisted indexes, but the node IDs work with newer versions.
This issue was initially investigated here, where we found that the issue disppear after re-indexing with a newer version of LlamaIndex.
Type of Change
Please delete options that are not relevant.

[x] New feature (non-breaking change which adds functionality)

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[x] I stared at the code and made sure it makes sense

Suggested Checklist:

[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes

@logan-markewich Please wait to merge this one in until I am able to make corresponding changes to the tutorial notebooks on our side 😄

Hey @axiomofjoy is this safe to merge yet?

@logan-markewich Thanks for the reminder. Not yet, I still need to update the notebook on our side.

Hi, @axiomofjoy
I had an issue with using Arize/Phoenix since OpenInferenceCallback returns the Node hash as an ID.
It seems similar to this issue: https://github.com/run-llama/llama_index/issues/7101
I assume NodeData should be created with the Node ID instead of the hash, same with the changes made in this PR. Are there any plans to reopen this PR?
I temporarily forked Llama-index and made changes to OpenInferenceCallback when using it with Phoenix. I hope this can be fixed in the future.

authors: axiomofjoy logan-markewich pRivAte12


text:
Smooth Animation Glitches out at zulrah

Particularly the melee phase and the spawn deaths. Zul will spazz out and won't look right.
Forgot to post last night so dont have anything to show but its quite obvious when you look at it

This is probably fixed with 62dec90d42f565ca49471f5d42d110db55ee7884

authors: Adam- Stickaplex

repo: runelite/runelite


text:
World map location for Vannaka easy cryptic clue is incorrect

Type
Incorrect behavior
Operating System
Windows
OS Version
Windows 11
Bug description
While doing an easy clue I found out that the location of a map marker for the vannaka step is way off. it's located north-east of where it should be.
Screenshots or videos

RuneLite version
Runelite Version: 1.8.24.3
Launcher Version: 2.4.0
Logs
No response

fix: https://github.com/runelite/runelite/pull/15211
It seems there is two cryptic clues that have you seek out Vannaka. One has the correct coordinate and the other has an incorrect 'x' coordinate.

authors: MrRickroll SpencerSKane


text:
Add Moonlight Potions to ItemStats plugin

Add Moonlight Potions (from Perilous oons) to ItemStats Plugin.
Working properly with the Wiki-stated formulas, and showing boost in stats in the correct colors/amounts.

#17607

authors: DominickCobb-rs mbtissot


text:
Not working with Docker per example

Running this per the documentation does not seem to work.
$ apf redis

*  ==> : Forwarding local listening ports to (==>) remote ports
*  <== : Forwarding to local ports from (<==) remote listening ports (use -r option)

No ports are opened.
I have tried builds from commit 38558a1 and b8059ea. I've tried the -d option, but the log file is empty
Docker version 20.10.12, build e91ed5707e
Linux archlinux 5.15.10-arch1-1 #1 SMP PREEMPT Fri, 17 Dec 2021 11:17:37 +0000 x86_64 GNU/Linux
Let me know if you need any other information

can you log into the container (docker -it exec redis bash) and run some commands while apf is running with -d?
# in the container
ps aux
cat /tmp/autoportforward.log

I don't have an Archlinux. but it does work on my CentOS vm and Mac.

Thanks for the quick response.
There is no ps available in the redis image (621ceef7494a), and no files in /tmp in the container. Another image had ps, but running it showed only the original process, the sh I was using, and ps itself (and again no files in /tmp).
I tried with a few other images and I got this error about half the time
2022/01/05 11:46:24 [ERR] yamux: Invalid protocol version: 79

Let me know what else I should try

Interesting. the way apf works is apf will copy a small agent binary to the container, and that binary will use its stdio to multiplex tcp streams. I am suspecting the binary can't be executed in your containers，maybe because the kernel or the libc loader or the arch doesn't match.
Those errors you got, and with no log file in the container might be caused by that binary failing to run. The next step to assist me debugging would be:

run an ubuntu container or others that has ps/busybox installed
run apf -d
in other terminal window, log in the container, check if there's a /apf-agent file in the / dir
if so, see if you can manually run it. let me known if it runs, prints some garbage characters and exits.

Thanks!

aha!
./apf-agent: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by ./apf-agent)

@codebling mind help me checking if the latest main works? before I tag a new release.

works!

Thank you for your help!

Does not exit after forwarding ports, however

apf should stay running so it can keep the listeners alive. if you close it, forwarding stops.

Confirmed. I was expecting the port to show up as forwarded under Docker after running apf but it makes sense that it doesn't. Definitely forwards the port, and forwarding stops when the program is closed. Works great! Thanks for the quick fix!
By the way, I've made autoportforward available as a package on arch. It's just in the user repository and builds from the main branch, for now.
Great idea thanks for the great creation!

authors: codebling ruoshan

repo: ruoshan/autoportforward


text:
[Practice Website], FreeCodeCamp etc

Category Name
Practice Website
Subcategory Name
Freecodecamp
Additional Context
There are lots of useful websites that let you code with in-browser IDEs such as FreecodeCamp and many more!! which can help beginners with industrial practices.
And can you suggest any good category name for this?
Thank You
Checklist

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[X] I have checked that this category does not exist
[X] I have checked that this subcategory does not exist
[X] I am willing to work on this issue (optional)
[X] I am participating in Hacktoberfest 2023

It's already there.

Do you want to add a new resource here.
I may be getting the wrong idea, so do correct me.

Ohh! What I meant is that FreeCodeCamp has project-based learning, and Codedamn, Exercism is also similar to it.

@Amanmawar17
As you can see these already exists for various subcategories.

What do you suggest, making a new subcategory?
It might be a good idea, let me know the subcategory name and which type of platforms will be there.

Can I add a certification sub-category as project-based learning in resources, and I also saw that certification in placement prep is empty.
We can also moves online code editor from frontend to resources.

@rupali-codes @CBID2
What do you think? I'm kinda confused. But the options like codecademy, exercism, freecodecamp can be in 1 category due to learning by solving step wise questions from instructions.

@rupali-codes @CBID2
What do you think? I'm kinda confused. But the options like codecademy, exercism, freecodecamp can be in 1 category due to learning by solving step wise questions from instructions.

Self-paced courses maybe @Anmol-Baranwal?

So, should I add self-paced courses as a sub-category in resources?

Self-paced courses maybe @Anmol-Baranwal?

Yeah, great suggestion.

So, should I add self-paced courses as a sub-category in resources?

@Amanmawar17
I have assigned you the issue. Please proceed with it, and don't hesitate to tag me @Anmol-Baranwal or @CBID2 if you require any assistance.

@Amanmawar17
Please update the description of this issue to reflect what you need to add. It will be in resources as you suggested.

Is it look good? @Anmol-Baranwal

Is it look good? @Anmol-Baranwal

Looks great. Please raise a PR 😄

repo: rupali-codes/LinksHub


text:
automake config files for x11 related packages do not support arm64

I've read Brief overview section and do understand basic concepts. [Yes]
I've read F.A.Q. section and there is no solution to my problem there. [Yes]
I've read Code of Conduct, I promise to be polite and will do my best at being constructive. [Yes]
I've read Reporting bugs section carefully. [Yes]
I've checked that all the hunter_add_package/find_package API used by me in the example is the same as in documentation. [Yes]
I'm using latest Hunter URL/SHA1. [Yes]

I've created SSCCE reproducing the issue:

# CMakeLists.txt

cmake_minimum_required(VERSION 3.2)

include("cmake/HunterGate.cmake")
HunterGate(
    URL "..."
    SHA1 "..."
)

project(foo)

hunter_add_package(xproto)
find_package(xproto CONFIG REQUIRED)

Here is the log until first error reported by Hunter, option HUNTER_STATUS_DEBUG is ON:

I've checked that the first error in logs IS NOT external.build.failed. [Yes]

I'm building on [Linux amd64].
[I've built CMake from sources myself]
CMake version: <3.14.3>

I'm using my toolchain:

set(CMAKE_INSTALL_RPATH "\$ORIGIN/../lib")

I'm using the next command line on generate step:
cmake -H. -B_builds "-GUnix Makefiles"

When building X libraries on arm64, config.guess and config.sub are too old in the official releases to properly support amd64. I get the following error on all of the various X libraries that are built with autotools:
[ 62%] Performing configure step for 'x11'
cd /home/user/.hunter/_Base/7bcf092/5d27811/ec05bef/Build/x11/Source && . /home/user/.hunter/_Base/Download/Hunter/0.23.164/7bcf092/Unpacked/scripts/clear-all.sh && PATH=/home/user/.hunter/_Base/7bcf092/5d27811/ec05bef/Install/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin PKG_CONFIG_LIBDIR=/home/user/.hunter/_Base/7bcf092/5d27811/ec05bef/Install/lib/pkgconfig:/home/user/.hunter/_Base/7bcf092/5d27811/ec05bef/Install/share/pkgconfig LD_LIBRARY_PATH=/home/user/.hunter/_Base/7bcf092/5d27811/ec05bef/Install/lib: ./configure AR=/usr/bin/ar LD=/usr/bin/ld NM=/usr/bin/nm OBJCOPY=/usr/bin/objcopy OBJDUMP=/usr/bin/objdump RANLIB=/usr/bin/ranlib STRIP=/usr/bin/strip CC=/usr/bin/cc CXX=/usr/bin/c++ CPPFLAGS=-I/home/user/.hunter/_Base/7bcf092/5d27811/ec05bef/Install/include "CFLAGS=-O3 -DNDEBUG" "CXXFLAGS=-O3 -DNDEBUG" LDFLAGS=-L/home/user/.hunter/_Base/7bcf092/5d27811/ec05bef/Install/lib --enable-shared --disable-static --prefix=/home/user/.hunter/_Base/7bcf092/5d27811/ec05bef/Build/x11/Install
checking build system type... ./config.guess: unable to guess system type

This script, last modified 2011-11-11, has failed to recognize
the operating system you are using. It is advised that you
download the most up to date version of the config scripts from

  http://git.savannah.gnu.org/gitweb/?p=config.git;a=blob_plain;f=config.guess;hb=HEAD
and
  http://git.savannah.gnu.org/gitweb/?p=config.git;a=blob_plain;f=config.sub;hb=HEAD

If the version you run (./config.guess) is already up to date, please
send the following data and any information you think might be
pertinent to <config-patches@gnu.org> in order to provide the needed
information to handle your system.

config.guess timestamp = 2011-11-11

uname -m = aarch64
uname -r = 4.4.38-tegra
uname -s = Linux
uname -v = #1 SMP PREEMPT Thu May 17 00:15:19 PDT 2018

When I download the newest config.guess and config.sub from the urls mentioned in the error, this fixes the issue. However this is quite annoying to fork the sources for all these projects just to update these two files. Would it be possible to have hunter detect this issue, and replace these files in place?

Here is the log until first error reported by Hunter, option HUNTER_STATUS_DEBUG is ON

I don't see logs. What version of X11 you have there? It should be 1.6.7:

https://github.com/ruslo/hunter/blob/v0.23.166/cmake/projects/x11/hunter.cmake#L26-L35

It's not 2011 release: libX11-1.6.7.tar.bz2 | 2018-10-09 14:30 | 2.2M

Will upload logs later today.
x11 package contains more recent config files from 2017-01-01 (which is still outdated compared to its release date)
For example: https://www.x.org/releases/individual/proto/xproto-7.0.31.tar.bz2
xproto-7.0.31.tar.bz2	2016-09-23 06:50	293K
If you download this file and extract its contents, you will find that config.guess and config.sub are outdated.
grep 'timestamp' config.guess | head -1
timestamp='2006-02-23'

https://gist.github.com/sjdrc/b38e2820039dafadf3bc8d4112ce539e
@ruslo You can see the issue occurring here with the latest renderproto.

@ruslo Any ideas on how best to fix this?

Any ideas on how best to fix this?

Fix upstream, use upstream URL
Patch upstream, use patched URL

https://github.com/ruslo/hunter/blob/v0.23.214/README.rst

authors: ruslo sjdrc

repo: ruslo/hunter


text:
Fix the issue that libxml2 failed to build with NDK r18.

This commit fixes the issue that libxml2 failed to build with NDK r18 because GCC has been removed since this revision. This issue is reported at https://github.com/hunter-packages/libxml2/issues/3

Thanks for your advise. Just updated. :)

Just updated. Should I undo PACKAGE_INTERNAL_DEPS_ID for OpenSSL and odb-boost, too?

Just updated. Should I undo PACKAGE_INTERNAL_DEPS_ID for OpenSSL and odb-boost, too?

Please undo the OpenSSL change. You can leave odb-boost since it's affected in fact too, additional test will not hurt :)

Got it. It's done. :)

Testing.
xau:

https://travis-ci.org/ingenue/hunter/builds/412324059?utm_source=github_status&utm_medium=notification
https://ci.appveyor.com/project/ingenue/hunter/build/1.0.4307

gstreamer:

https://travis-ci.org/ingenue/hunter/builds/412324273?utm_source=github_status&utm_medium=notification
https://ci.appveyor.com/project/ingenue/hunter/build/1.0.4308

libxml2:

https://travis-ci.org/ingenue/hunter/builds/412324328?utm_source=github_status&utm_medium=notification
https://ci.appveyor.com/project/ingenue/hunter/build/1.0.4309

odb-boost:

https://travis-ci.org/ingenue/hunter/builds/412324543?utm_source=github_status&utm_medium=notification
https://ci.appveyor.com/project/ingenue/hunter/build/1.0.4310

Uploading.
xau:

https://travis-ci.org/ingenue/hunter/builds/412329105?utm_source=github_status&utm_medium=notification
https://ci.appveyor.com/project/ingenue/hunter/build/1.0.4311

gstreamer:

https://travis-ci.org/ingenue/hunter/builds/412329184?utm_source=github_status&utm_medium=notification
https://ci.appveyor.com/project/ingenue/hunter/build/1.0.4312

libxml2:

https://travis-ci.org/ingenue/hunter/builds/412329256?utm_source=github_status&utm_medium=notification
https://ci.appveyor.com/project/ingenue/hunter/build/1.0.4313

odb-boost:

https://travis-ci.org/ingenue/hunter/builds/412329351?utm_source=github_status&utm_medium=notification
https://ci.appveyor.com/project/ingenue/hunter/build/1.0.4314

I've checked Android Studio build - both NDK r17 and NDK r18 works fine, @olliwang great job!
Released: https://github.com/ruslo/hunter/releases/tag/v0.23.11

@ruslo Thank you for guiding me through the libxml2 issues. Really appreciated. 👍

authors: olliwang ruslo


text:
Access/modify attributes of principal

It would be cool if I could use this library to modify the "Attributes" field of principals; for instance, to set +needchange on user principals to expire passwords rather than hard-expiring them with a date.
Interface could look something like
>>> princ.attributes
['REQUIRES_PRE_AUTH']
>>> princ.attributes.append('REQUIRES_PWCHANGE')
>>> princ.attributes
['REQUIRES_PRE_AUTH', 'REQUIRES_PWCHANGE']

corresponding to
kadmin: getprinc foobar
Principal: foobar@REALM.CORP
...
Attributes: REQUIRES_PRE_AUTH REQUIRES_PWCHANGE
kadmin: modprinc +needchange foobar
Principal "foobar@REALM.CORP" modified.

in kadmin.
I could write a pull request if someone were to point me in the right direction re: docs, etc.

This functionality exists, it's just not documented...
princ.set_flags(kadmin.REQUIRES_PWCHANGE)
princ.commit()
(Also princ.unset_flags)

It exists, but the code hasn't been fleshed out (there are still comments floating around) and the interface could be more user-friendly. If I have time I plan on fixing this up and writing some docs.

authors: ehashman moonpatrol

repo: russjancewicz/python-kadmin