ERROR: the following packages/stacks could not have their rosdep keys resolved to system dependencies: dummy_sensors: No definition of [ament_lint_common] for OS version [bionic]

ubuntu 18.04, Foxy
Install dependencies using rosdep have a problem
xiaoyao@xiaoyao-virtual-machine:~/ros2_foxy$ rosdep install --from-paths src --ignore-src --rosdistro foxy -y --skip-keys "fastcdr rti-connext-dds-5.3.1 urdfdom_headers"
ERROR: the following packages/stacks could not have their rosdep keys resolved
to system dependencies:
dummy_sensors: No definition of [ament_lint_common] for OS version [bionic]
bag_recorder_nodes: No definition of [ament_lint_common] for OS version [bionic]
rcl_interfaces: No definition of [ament_lint_common] for OS version [bionic]
sros2_cmake: No definition of [ament_lint_common] for OS version [bionic]
urdf: No definition of [ament_lint_common] for OS version [bionic]
rqt_py_console: No definition of [ament_index_python] for OS version [bionic]
unique_identifier_msgs: No definition of [ament_lint_common] for OS version [bionic]
rqt_graph: No definition of [ament_index_python] for OS version [bionic]
action_tutorials_cpp: No definition of [ament_lint_common] for OS version [bionic]
examples_rclpy_executors: No definition of [ament_pep257] for OS version [bionic]
rmw_implementation: No definition of [ament_lint_common] for OS version [bionic]
common_interfaces: No definition of [ament_lint_common] for OS version [bionic]
tango_icons_vendor: No definition of [ament_lint_common] for OS version [bionic]
uncrustify_vendor: No definition of [ament_cmake] for OS version [bionic]
rosidl_typesupport_connext_cpp: No definition of [ament_cmake] for OS version [bionic]
rttest: No definition of [ament_lint_common] for OS version [bionic]
ros2doctor: No definition of [ament_xmllint] for OS version [bionic]
rviz_ogre_vendor: No definition of [ament_cmake] for OS version [bionic]
rosbag2_transport: No definition of [ament_lint_common] for OS version [bionic]
test_security: No definition of [ament_lint_common] for OS version [bionic]
action_tutorials_interfaces: No definition of [ament_lint_common] for OS version [bionic]
examples_rclpy_minimal_publisher: No definition of [ament_pep257] for OS version [bionic]
rclcpp: No definition of [ament_lint_common] for OS version [bionic]
tf2_eigen_kdl: No definition of [ament_lint_common] for OS version [bionic]
tlsf: No definition of [ament_lint_common] for OS version [bionic]
rmw_cyclonedds_cpp: No definition of [ament_lint_common] for OS version [bionic]
robot_state_publisher: No definition of [ament_lint_common] for OS version [bionic]
resource_retriever: No definition of [ament_lint_common] for OS version [bionic]
tf2_eigen: No definition of [ament_cmake_gtest] for OS version [bionic]
builtin_interfaces: No definition of [ament_lint_common] for OS version [bionic]
dummy_map_server: No definition of [ament_lint_common] for OS version [bionic]
python_cmake_module: No definition of [ament_lint_common] for OS version [bionic]
rosbag2: No definition of [ament_cmake] for OS version [bionic]
diagnostic_msgs: No definition of [ament_lint_common] for OS version [bionic]
intra_process_demo: No definition of [ament_lint_common] for OS version [bionic]
rosgraph_msgs: No definition of [ament_lint_common] for OS version [bionic]
rosidl_typesupport_cpp: No definition of [ament_cmake_core] for OS version [bionic]
ros1_bridge: No definition of [ament_lint_common] for OS version [bionic]
tinyxml2_vendor: No definition of [ament_cmake] for OS version [bionic]
rqt_topic: No definition of [ament_xmllint] for OS version [bionic]
pluginlib: No definition of [ament_cmake_gtest] for OS version [bionic]
rcl_logging_spdlog: No definition of [ament_lint_common] for OS version [bionic]
composition: No definition of [ament_lint_common] for OS version [bionic]
rosbag2_storage: No definition of [ament_lint_common] for OS version [bionic]
examples_rclcpp_minimal_publisher: No definition of [ament_lint_common] for OS version [bionic]
rosbag2_tests: No definition of [ament_lint_common] for OS version [bionic]
rviz2: No definition of [ament_cmake_uncrustify] for OS version [bionic]
demo_nodes_cpp_native: No definition of [ament_lint_common] for OS version [bionic]
mimick_vendor: No definition of [ament_lint_common] for OS version [bionic]
rmw_dds_common: No definition of [ament_lint_common] for OS version [bionic]
qt_gui: No definition of [ament_lint_common] for OS version [bionic]
ros2lifecycle_test_fixtures: No definition of [ament_lint_common] for OS version [bionic]
rmw: No definition of [ament_lint_common] for OS version [bionic]
rpyutils: No definition of [ament_xmllint] for OS version [bionic]
actionlib_msgs: No definition of [ament_lint_common] for OS version [bionic]
launch_ros: No definition of [ament_pep257] for OS version [bionic]
rosidl_typesupport_connext_c: No definition of [ament_cmake] for OS version [bionic]
rqt_console: No definition of [ament_index_python] for OS version [bionic]
launch_yaml: No definition of [ament_pep257] for OS version [bionic]
ros2node: No definition of [ament_xmllint] for OS version [bionic]
ros2topic: No definition of [ament_xmllint] for OS version [bionic]
geometry2: No definition of [ament_cmake] for OS version [bionic]
ros2param: No definition of [ament_xmllint] for OS version [bionic]
tf2_msgs: No definition of [ament_lint_common] for OS version [bionic]
qt_gui_app: No definition of [ament_lint_common] for OS version [bionic]
laser_geometry: No definition of [ament_cmake_uncrustify] for OS version [bionic]
tracetools_launch: No definition of [ament_xmllint] for OS version [bionic]
message_filters: No definition of [ament_cmake_pytest] for OS version [bionic]
pendulum_msgs: No definition of [ament_cmake] for OS version [bionic]
rqt_gui_cpp: No definition of [ament_cmake] for OS version [bionic]
examples_rclpy_minimal_client: No definition of [ament_pep257] for OS version [bionic]
rqt_gui: No definition of [ament_lint_common] for OS version [bionic]
rclpy: No definition of [ament_lint_common] for OS version [bionic]
qt_gui_py_common: No definition of [ament_lint_common] for OS version [bionic]
rcl_lifecycle: No definition of [ament_lint_auto] for OS version [bionic]
rviz_assimp_vendor: No definition of [ament_cmake] for OS version [bionic]
ros2pkg: No definition of [ament_xmllint] for OS version [bionic]
visualization_msgs: No definition of [ament_lint_common] for OS version [bionic]
examples_rclcpp_minimal_action_server: No definition of [ament_lint_common] for OS version [bionic]
tf2: No definition of [ament_cmake_gtest] for OS version [bionic]
rosidl_runtime_py: No definition of [ament_xmllint] for OS version [bionic]
ros_environment: No definition of [ament_cmake_core] for OS version [bionic]
examples_rclcpp_minimal_client: No definition of [ament_lint_common] for OS version [bionic]
ros2cli_common_extensions: No definition of [ament_lint_common] for OS version [bionic]
shared_queues_vendor: No definition of [ament_cmake] for OS version [bionic]
demo_nodes_cpp: No definition of [ament_lint_common] for OS version [bionic]
topic_monitor: No definition of [ament_pep257] for OS version [bionic]
action_msgs: No definition of [ament_lint_common] for OS version [bionic]
example_interfaces: No definition of [ament_cmake] for OS version [bionic]
map_msgs: No definition of [ament_lint_common] for OS version [bionic]
move_base_msgs: No definition of [ament_cmake] for OS version [bionic]
ros2launch: No definition of [ament_pep257] for OS version [bionic]
quality_of_service_demo_py: No definition of [ament_pep257] for OS version [bionic]
sros2: No definition of [ament_pep257] for OS version [bionic]
test_communication: No definition of [ament_lint_common] for OS version [bionic]
rosidl_cmake: No definition of [ament_cmake] for OS version [bionic]
rmw_implementation_cmake: No definition of [ament_cmake] for OS version [bionic]
rosidl_typesupport_introspection_cpp: No definition of [ament_cmake] for OS version [bionic]
tf2_bullet: No definition of [ament_lint_common] for OS version [bionic]
launch: No definition of [ament_pep257] for OS version [bionic]
image_tools: No definition of [ament_lint_common] for OS version [bionic]
rosidl_typesupport_interface: No definition of [ament_cmake_gtest] for OS version [bionic]
ros2bag: No definition of [ament_pep257] for OS version [bionic]
trajectory_msgs: No definition of [ament_lint_common] for OS version [bionic]
tracetools: No definition of [ament_lint_common] for OS version [bionic]
ament_cmake_ros: No definition of [ament_cmake_pytest] for OS version [bionic]
launch_testing: No definition of [ament_pep257] for OS version [bionic]
ros2trace: No definition of [ament_xmllint] for OS version [bionic]
turtlesim: No definition of [ament_cmake] for OS version [bionic]
ros2lifecycle: No definition of [ament_xmllint] for OS version [bionic]
test_msgs: No definition of [ament_cmake_gtest] for OS version [bionic]
sensor_msgs_py: No definition of [ament_pep257] for OS version [bionic]
rviz_visual_testing_framework: No definition of [ament_cmake_uncrustify] for OS version [bionic]
sqlite3_vendor: No definition of [ament_cmake] for OS version [bionic]
examples_rclpy_minimal_service: No definition of [ament_pep257] for OS version [bionic]
examples_rclcpp_minimal_timer: No definition of [ament_lint_common] for OS version [bionic]
stereo_msgs: No definition of [ament_lint_common] for OS version [bionic]
libyaml_vendor: No definition of [ament_lint_common] for OS version [bionic]
rosidl_runtime_cpp: No definition of [ament_cmake] for OS version [bionic]
interactive_markers: No definition of [ament_lint_common] for OS version [bionic]
ros2cli: No definition of [ament_xmllint] for OS version [bionic]
rosidl_default_runtime: No definition of [ament_lint_common] for OS version [bionic]
test_tf2: No definition of [ament_cmake_gtest] for OS version [bionic]
foonathan_memory_vendor: No definition of [ament_cmake_xmllint] for OS version [bionic]
rmw_connext_cpp: No definition of [ament_cmake] for OS version [bionic]
rosbag2_test_common: No definition of [ament_lint_common] for OS version [bionic]
rviz_common: No definition of [ament_cmake_uncrustify] for OS version [bionic]
rcl_action: No definition of [ament_lint_auto] for OS version [bionic]
spdlog_vendor: No definition of [ament_lint_common] for OS version [bionic]
test_quality_of_service: No definition of [ament_lint_common] for OS version [bionic]
connext_cmake_module: No definition of [ament_cmake] for OS version [bionic]
composition_interfaces: No definition of [ament_lint_common] for OS version [bionic]
rosidl_typesupport_introspection_c: No definition of [ament_cmake] for OS version [bionic]
rqt_reconfigure: No definition of [ament_xmllint] for OS version [bionic]
fastrtps_cmake_module: No definition of [ament_lint_common] for OS version [bionic]
rosidl_generator_c: No definition of [ament_cmake_core] for OS version [bionic]
rcl_yaml_param_parser: No definition of [ament_lint_auto] for OS version [bionic]
libcurl_vendor: No definition of [ament_cmake] for OS version [bionic]
examples_rclpy_minimal_action_client: No definition of [ament_pep257] for OS version [bionic]
rcl: No definition of [ament_lint_common] for OS version [bionic]
rviz_rendering: No definition of [ament_cmake_uncrustify] for OS version [bionic]
lifecycle_msgs: No definition of [ament_lint_common] for OS version [bionic]
rqt_py_common: No definition of [ament_cmake_pytest] for OS version [bionic]
rosbag2_storage_default_plugins: No definition of [ament_cmake_gmock] for OS version [bionic]
tinyxml_vendor: No definition of [ament_cmake] for OS version [bionic]
rosidl_default_generators: No definition of [ament_cmake_core] for OS version [bionic]
pendulum_control: No definition of [ament_lint_common] for OS version [bionic]
examples_rclcpp_minimal_composition: No definition of [ament_lint_common] for OS version [bionic]
rmw_connext_shared_cpp: No definition of [ament_cmake] for OS version [bionic]
rclcpp_action: No definition of [ament_lint_common] for OS version [bionic]
tf2_geometry_msgs: No definition of [ament_lint_common] for OS version [bionic]
rosidl_typesupport_fastrtps_c: No definition of [ament_lint_common] for OS version [bionic]
ros2run: No definition of [ament_xmllint] for OS version [bionic]
ros2multicast: No definition of [ament_xmllint] for OS version [bionic]
std_msgs: No definition of [ament_lint_common] for OS version [bionic]
ros_testing: No definition of [ament_cmake] for OS version [bionic]
rmw_fastrtps_cpp: No definition of [ament_cmake] for OS version [bionic]
rviz_rendering_tests: No definition of [ament_index_cpp] for OS version [bionic]
qt_dotgraph: No definition of [ament_lint_common] for OS version [bionic]
libstatistics_collector: No definition of [ament_lint_common] for OS version [bionic]
tracetools_trace: No definition of [ament_xmllint] for OS version [bionic]
launch_testing_ros: No definition of [ament_pep257] for OS version [bionic]
std_srvs: No definition of [ament_lint_common] for OS version [bionic]
test_rclcpp: No definition of [ament_lint_common] for OS version [bionic]
examples_rclcpp_multithreaded_executor: No definition of [ament_lint_common] for OS version [bionic]
ros2interface: No definition of [ament_xmllint] for OS version [bionic]
test_rmw_implementation: No definition of [ament_lint_common] for OS version [bionic]
test_launch_testing: No definition of [ament_lint_common] for OS version [bionic]
examples_rclcpp_minimal_service: No definition of [ament_lint_common] for OS version [bionic]
rcutils: No definition of [ament_lint_auto] for OS version [bionic]
tracetools_read: No definition of [ament_xmllint] for OS version [bionic]
ros2component: No definition of [ament_xmllint] for OS version [bionic]
performance_test_fixture: No definition of [ament_cmake_google_benchmark] for OS version [bionic]
tlsf_cpp: No definition of [ament_cmake_gtest] for OS version [bionic]
logging_demo: No definition of [ament_lint_common] for OS version [bionic]
qt_gui_cpp: No definition of [ament_cmake_pytest] for OS version [bionic]
tf2_kdl: No definition of [ament_cmake_gtest] for OS version [bionic]
examples_rclcpp_minimal_action_client: No definition of [ament_lint_common] for OS version [bionic]
rclcpp_lifecycle: No definition of [ament_lint_common] for OS version [bionic]
rcpputils: No definition of [ament_cmake_gtest] for OS version [bionic]
class_loader: No definition of [ament_lint_common] for OS version [bionic]
tf2_py: No definition of [ament_lint_common] for OS version [bionic]
domain_coordinator: No definition of [ament_pep257] for OS version [bionic]
tf2_sensor_msgs: No definition of [ament_cmake_gtest] for OS version [bionic]
rosidl_generator_py: No definition of [ament_index_python] for OS version [bionic]
ros2action: No definition of [ament_xmllint] for OS version [bionic]
statistics_msgs: No definition of [ament_lint_common] for OS version [bionic]
action_tutorials_py: No definition of [ament_lint_common] for OS version [bionic]
test_cli_remapping: No definition of [ament_lint_common] for OS version [bionic]
qt_gui_core: No definition of [ament_cmake] for OS version [bionic]
demo_nodes_py: No definition of [ament_pep257] for OS version [bionic]
nav_msgs: No definition of [ament_lint_common] for OS version [bionic]
tracetools_test: No definition of [ament_lint_common] for OS version [bionic]
tf2_tools: No definition of [ament_cmake] for OS version [bionic]
launch_testing_ament_cmake: No definition of [ament_cmake_test] for OS version [bionic]
rosidl_adapter: No definition of [ament_lint_auto] for OS version [bionic]
examples_rclpy_minimal_action_server: No definition of [ament_pep257] for OS version [bionic]
test_launch_ros: No definition of [ament_pep257] for OS version [bionic]
rosidl_generator_dds_idl: No definition of [ament_cmake] for OS version [bionic]
tf2_ros: No definition of [ament_cmake_pytest] for OS version [bionic]
geometry_msgs: No definition of [ament_lint_common] for OS version [bionic]
rosidl_typesupport_c: No definition of [ament_cmake_core] for OS version [bionic]
launch_xml: No definition of [ament_pep257] for OS version [bionic]
test_cli: No definition of [ament_lint_common] for OS version [bionic]
rosidl_typesupport_fastrtps_cpp: No definition of [ament_lint_common] for OS version [bionic]
rcl_logging_noop: No definition of [ament_lint_auto] for OS version [bionic]
examples_rclpy_minimal_subscriber: No definition of [ament_pep257] for OS version [bionic]
rosbag2_compression: No definition of [ament_lint_common] for OS version [bionic]
rclcpp_components: No definition of [ament_lint_common] for OS version [bionic]
examples_rclcpp_minimal_subscriber: No definition of [ament_lint_common] for OS version [bionic]
zstd_vendor: No definition of [ament_cmake] for OS version [bionic]
rosbag2_converter_default_plugins: No definition of [ament_lint_common] for OS version [bionic]
console_bridge_vendor: No definition of [ament_lint_common] for OS version [bionic]
test_interface_files: No definition of [ament_cmake_core] for OS version [bionic]
ros2test: No definition of [ament_pep257] for OS version [bionic]
rqt_gui_py: No definition of [ament_lint_common] for OS version [bionic]
rviz_default_plugins: No definition of [ament_index_cpp] for OS version [bionic]
lifecycle: No definition of [ament_lint_common] for OS version [bionic]
rosidl_runtime_c: No definition of [ament_cmake] for OS version [bionic]
yaml_cpp_vendor: No definition of [ament_cmake] for OS version [bionic]
eigen3_cmake_module: No definition of [ament_cmake_lint_cmake] for OS version [bionic]
rosidl_parser: No definition of [ament_lint_common] for OS version [bionic]
quality_of_service_demo_cpp: No definition of [ament_lint_common] for OS version [bionic]
shape_msgs: No definition of [ament_lint_common] for OS version [bionic]
ros2service: No definition of [ament_xmllint] for OS version [bionic]
kdl_parser: No definition of [ament_lint_common] for OS version [bionic]
rcl_logging_log4cxx: No definition of [ament_lint_auto] for OS version [bionic]
examples_tf2_py: No definition of [ament_pep257] for OS version [bionic]
rmw_fastrtps_dynamic_cpp: No definition of [ament_cmake] for OS version [bionic]
python_qt_binding: No definition of [ament_lint_common] for OS version [bionic]
dummy_robot_bringup: No definition of [ament_lint_common] for OS version [bionic]
rosidl_generator_cpp: No definition of [ament_cmake_core] for OS version [bionic]
rmw_fastrtps_shared_cpp: No definition of [ament_cmake] for OS version [bionic]
sensor_msgs: No definition of [ament_lint_common] for OS version [bionic]
rosbag2_cpp: No definition of [ament_lint_common] for OS version [bionic]

How to resolve it?
Thanks

I have a solution:
xiaoyao@xiaoyao-virtual-machine:~/ros2_foxy$ rosdep install --from-paths src --ignore-src --rosdistro foxy -y --os=ubuntu:focal --skip-keys "fastcdr rti-connext-dds-5.3.1 urdfdom_headers"


Then plug-in sync dialog causes obsidian crashes

Then plug-in sync dialog causes obsidian crashes
I’ve experienced this problem on my multiple devices
(Screen recording will be uploaded soon)

Thank you for letting me know! I am looking forward to seeing the video.
but if you are troubled about recording or reproducing, I’d love to ask a few things in advance.

When did it happen?
always or sometimes?
Was any message shown?

I think that obsidian takes a bit long startup time now if this plugin is enabled. because of the rough handling of file changes.

Thank you for letting me know! I am looking forward to seeing the video. but if you are troubled about recording or reproducing, I’d love to ask a few things in advance.

When did it happen?
always or sometimes?
Was any message shown?

I think that obsidian takes a bit long startup time now if this plugin is enabled. because of the rough handling of file changes. But I think it just takes time.

Thanks for replying such fast .this is the screenshot
Screen record
It happens every time on my ipad
And most times on my other phones.
But I haven't experienced any problem on PCs
Thanks for your hard working 😘

Thank you for the information and screen record!
But I am wondering what makes crashes.
How many plugins are shown in here on the desktop device?
And may I ask what will be likely to be the obstacle if you move to the 'hidden file sync' feature? (Do you want to sync plugins manually?)

Thank you for the information and screen record! But I am wondering what makes crashes. How many plugins are shown in here on the desktop device?
And may I ask what will be likely to be the obstacle if you move to the 'hidden file sync' feature? (Do you want to sync plugins manually?)

Hello dear author
I have 23 plugins shown in the desktop plugin sync dialog.
and Ive double checked , this only happen to my ipad (constantly) and my iphone(not each time )
but no any problem on my PCs/Mac/Androids
Any way I could provide the crash log to you ?

Hi! It has been a long time, but I have refined this feature completely!
Now iOS devices will not crash again (for the same reason).
I hope that this feature helps us!


Call send_event rather than Object#send

Currently, the Chef handler fails to report errors to Sentry. The call toRaven#send should be to Raven#send_event, instead of Object#send.
The PR also has some small changes to the README.md examples.

@johnbellone  @coderanger would you like to release this version to supermarket?


fixes #74, wrong handling of oneway=-1

thanks to @DrVanScott for suggesting a fix.
see for discussion https://github.com/DennisOSRM/Project-OSRM/issues/74

i'm sorry i guess this pull request now includes heaps of other changes because i pushed more changes to the branch afterwards.
the relevant commit is https://github.com/emiltin/Project-OSRM/commit/f34d58fc7ec9e7218ac5c0f719a0e477d8c117bc


fix(workflow): match discovery burst and qps for kubectl with upstream kubectl binary

May fix or alleviate issues like https://github.com/argoproj/argo-workflows/issues/11156 and https://github.com/argoproj/argo-workflows/issues/9934
Motivation
We migrated to using kubectl as a package starting v3.4.7:

v3.4.7: https://github.com/argoproj/argo-workflows/blob/v3.4.7/go.mod#L71
v3.4.8: https://github.com/argoproj/argo-workflows/blob/v3.4.8/go.mod#L71
master: https://github.com/argoproj/argo-workflows/blob/master/go.mod#L71

Before v3.4.7 we used kubectl binary (ref1, ref2)
kubectl binary uses uses higher values for discovery burst and QPS since v1.24. kubectl passes the new QPS and burst through NewDefaultKubectlCommand while in argo workflows we use NewKubectlCommand instead which uses default burst of 100 (we are using v.0.24.3 version of kubectl pkg at the time of writing this)
If there are 100 or more CRDs in the cluster, discovery can take time. This leaves less time for pod to run because of which pod can exceed activeDeadlineSeconds (check https://github.com/argoproj/argo-workflows/issues/11156 and https://github.com/argoproj/argo-workflows/issues/9934). Related: https://github.com/kubernetes/kubectl/issues/1126
Modifications
This PR matches the the new discovery burst and QPS set in the upstream.
Related:

https://github.com/kubernetes/kubernetes/pull/120024 is merged

Note that in 1.26 version (v0.26.x for kubectl package), default burst across all client-go clients was bumped up to 300 (no increase in the default QPS though) but we can't use this since we are on v0.24.3. Upgrading the kubectl package is an option but I am not sure about the consequences of doing that. We might want to re-visit this PR again in the future and remove lines which are already set in the upstream.
Verification

300/50 seems too high, I raised https://github.com/argoproj/argo-helm/issues/2195 but 100/50 is only recommended from k8s 1.27, under k8s 1.27 its 20/10

300/50 seems too high, I raised argoproj/argo-helm#2195 but 100/50 is only recommended from k8s 1.27, under k8s 1.27 its 20/10

I think you are talking about rest client burst/qps. This PR is about discovery client burst/qps. 300/50 is the default upstream value since v1.24 version of Kubernetes. All of the details are in the description of the PR.

CI / E2E Tests (test-executor, minimal) seems flaky. Similar test is failing in other open PRs as well:

https://github.com/argoproj/argo-workflows/pull/11628
https://github.com/argoproj/argo-workflows/pull/11641
https://github.com/argoproj/argo-workflows/pull/11638
https://github.com/argoproj/argo-workflows/pull/11644

Makes me think the test failure is not related to this PR.

I think the PR is ready for review. I don't think the test failure is related to the changes in this PR. Happy to take another look if the reviewers think the failure is related to changes in this PR.

May fix or alleviate issues like #11156 and #9934

If there are 100 or more CRDs in the cluster, discovery can take time. This leaves less time for pod to run because of which pod can exceed activeDeadlineSeconds (check #11156 and #9934)

This specific change would only help those issues if they were using many resource templates with many CRDs. They don't give reproducible Workflows unfortunately, but those are typically a small subset of Workflows.


tf.GradientTape() can't train custom subclassing model.

System information

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

You can collect some of this information using our environment capture
script
You can also obtain the TensorFlow version with: 1. TF 1.0: python -c "import tensorflow as tf; print(tf.GIT_VERSION, tf.VERSION)" 2. TF 2.0: python -c "import tensorflow as tf; print(tf.version.GIT_VERSION, tf.version.VERSION)"
Describe the current behavior
I tried to make my custom model inherited from tf.keras.Model and I want to training this model by using tf.GradienTape().
But it can't train my model. Loss keeps same values for training and isn't reduced.
However, model.complie() and model.fit() with same criterion and optimizer work well for my custom model.
I don't understand why does this situation happen. Which part is problem?
Code to reproduce the issue
import tensorflow as tf
cfg_imagenet = [64, (128,2), 128, (256,2), 256, (512,2), 512, 512, 512, 512, 512, (1024,2), 1024]
cfg_cifar = [64, 128, 128, 256, 256, 512, 512, 512, 512, 512, 512, 1024, 1024]

class MobileNet(tf.keras.Model):
    def __init__(self, data_format='channels_last'):
        super(MobileNet, self).__init__()
        self.channel_axis = 1 if data_format == 'channels_last' else -1
        self.initializer = tf.keras.initializers.he_normal()

        self.features = self._make_layers()
        self.classifier = tf.keras.layers.Dense(10, kernel_initializer='he_normal')

    def _make_layers(self):
        layers = []
        layers.append(tf.keras.layers.Conv2D(32, kernel_size=3, strides=2, padding='same', name='conv1',
                      kernel_initializer=self.initializer))
        layers.append(tf.keras.layers.BatchNormalization(axis=self.channel_axis, name='conv1_bn'))
        layers.append(tf.keras.layers.ReLU(name='conv1_relu'))
        for idx, x in enumerate(cfg_imagenet):
            i = idx + 1
            filters = x if isinstance(x, int) else x[0]
            strides = 1 if isinstance(x, int) else x[1]
            layers.append(tf.keras.layers.DepthwiseConv2D((3, 3), strides, padding='same', kernel_initializer=self.initializer, name='block{}_dw'.format(i)))
            layers.append(tf.keras.layers.BatchNormalization(axis=self.channel_axis, name='block{}_bn1'.format(i)))
            layers.append((tf.keras.layers.ReLU(name='block{}_relu1'.format(i))))
            layers.append(tf.keras.layers.Conv2D(filters, 1, padding='same', activation='relu', kernel_initializer=self.initializer, name='block{}_pw'.format(i)))
            layers.append(tf.keras.layers.BatchNormalization(axis=self.channel_axis, name='block{}_bn2'.format(i)))
            layers.append((tf.keras.layers.ReLU(name='block{}_relu2'.format(i))))
        layers.append(tf.keras.layers.GlobalAveragePooling2D())
        return layers

    def call(self, input_tensor):
        x = input_tensor
        for layer in self.features:
            x = layer(x)
        x = self.classifier(x)
        return x

criterion = tf.keras.losses.SparseCategoricalCrossentropy(from_logits=True)
optimizer = tf.keras.optimizers.Adam(learning_rate=0.001)

def loss_func(model, x, y):
    y_ = model(x)
    return criterion(y, y_)

def grad(model, inputs, targets):
    with tf.GradientTape() as tape:
        loss_value = loss_func(model, inputs, targets)
    return loss_value, tape.gradient(loss_value, model.trainable_variables)

train_dataset = tf.data.Dataset.from_tensor_slices((train_data, train_labels))
test_dataset = tf.data.Dataset.from_tensor_slices((test_data, test_labels))
for epoch in range(10):
    train_acc = tf.keras.metrics.SparseCategoricalAccuracy(name='train_acc')
    for x, y in train_dataset:
        loss_value, grads = grad(model, x, y)
        optimizer.apply_gradients(grads_and_vars=zip(grads, model.trainable_variables))
        train_acc(y, model(x))
        print(loss_value)
        print(train_acc.result())
    print(epoch, "complete")

@jyh2378 ,
When i tried running the given code, i got the output , kindly find the gist of colab. Can you provide complete code to reproduce the issue mentioned here?Thanks!

@oanush
I've got the answer of this problem. I didn't give the the parameter "training=True" to the BatchNorm layers. So, My model can't be reduced the loss. When I fix this part, model can be trained well.

@oanush
I've got the answer of this problem. I didn't give the parameter "training=True" to BatchNorm layers.
So the model trained except parameter of BatchNorm layers. When I fixed this part, the model was trained well.


Alignment Component

I'll post my thoughts on how this might work in a subsequent comment.

Goals and Assumptions
Goal: maximize re-usability of alignment component by minimizing its dependencies on its environment.
Assumptions:

In the description below, I assume that the alignment component (AC) lives in its own page in gateway-translate which is a NextJs application.  Being in its own page makes it easier to reason about.
Let's also assume that the way to route to the aligner page is by selecting it in the sidebar navigation.

Workflow
After user logs in, opens a file, and (perhaps) edits it. Then they wish to align it.

In side navigation, click the alignment button
The app routes to the alignment page
The page shows a list of files that have been opened.
The user selects a book
The app retrieves the original language text for the selected book (if hasn't been retrieved already) and loads it into the PK cache (converting it to PERF along the way)
The app accesses the original language PERF for the selected book from the PK cache
The app accesses the edited PERF for the selected book from the PK cache
The app instantiates the alignment component with the two PERF files, plus a save function, the bookId, and the versification for the book.
Thus the component would look something like this:<Aligner
    originalLanguage={olPerf}
    content={editedPerf}
    bookid={bookId}
    onSave={onSave}
    versification={vrs}
 />

10. The AC would then show, defaulting to chapter 1 verse 1.
11. In addition to the alignment area, the follow UI elements are needed:
   - chapter and verse navigation
   - a Cancel button: routes to main workspace without saving
   - a Save button: save the updated PERF to the PK cache
   - a Close button (which saves and routes to the main workspace)
12. Possibly, the cancel and close may need to fire functions provided by the app. In that case, they would be passed in similar to the "onSave" above.
13. Possibly, instead of passing in PERF, it may be desirable to pass in Epitelete instances

Ok, so chapter/verse (or whatever) navigation would be an aligner RC concern? I had imagined that the aligner RC would be given the chapter/verse context of the text editor. If not, it feels to me like the aligner is working in its own context and, in that case, it probably shouldn't be in the same page as the text editor.
It's really a question of workflow. I was imagining that people are editing a verse and then want to do a quick bit of aligning. (Or, they are aligning and realise that they need to make a change to the text, which is the tCore workflow.) In that case I think we should have shared bcv navigation for both text editor and alignment, and the user effectively swaps between two views of the bcv context.
Alternatively, if alignment is primarily a separate activity, it might make sense to do it somewhere far from the text editor. But even in that case, I think we'd want a way to jump from the text editor to align the thing that was being edited, or vice versa.

To

maximize re-usability of alignment component
the bcv context could potentially be more than a verse, eg a verse range, a chapter, a book...

@mvahowe thanks... I had never imagined that a translator would want to flip back and forth between translating and aligning. But then I'm not a translator... need some expert user input on that point. Keeping it separate has a lot advantages on the development side and for the robustness (way less complicated and prone to bugs). But I may have to concede the point.
In the workflow I described, the context would always be a verse or a verse range... i.e., it would be driven from how the target text was structured. And the Original Language side would need to show all the verses represented in the target range.

I could imagine both approaches here above to be useful - depending on use cases, I guess...
So maybe the question to @birchamp might be: Which approach has first priority for gT right now?

Alignment by verse, or verse range as per @mvahowe here above
or more of a full navigation (by book) aligner as per @mandolyte
And from my point of view, I actually do not really think that keeping it separate has much development side advantage (if any).


updated and added

Renamed few file names and also added Calloc (dynamic memory allocation) program.

@Pavan-Kamthane Could you please check my PR for adding new program to the C language


Incorrect mock generated for composed protocol

If I define the following protocols in the same file:
/// @mockable
protocol First {
    var first: String { get }
}

/// @mockable
protocol Second {
    var second: String { get }
}

/// @mockable
protocol Both: First & Second { }

Then the resulting generated mocks are:
class FirstMock: First {
    init() { }
    init(first: String = "") {
        self.first = first
    }

    private(set) var firstSetCallCount = 0
    var first: String = "" { didSet { firstSetCallCount += 1 } }
}

class SecondMock: Second {
    init() { }
    init(second: String = "") {
        self.second = second
    }

    private(set) var secondSetCallCount = 0
    var second: String = "" { didSet { secondSetCallCount += 1 } }
}

class BothMock: Both {
    init() { }
    init(first: String = "") {
        self.first = first
    }

    private(set) var firstSetCallCount = 0
    var first: String = "" { didSet { firstSetCallCount += 1 } }
}

Looking at the BothMock class above, it only conforms to First and doesn't include conformance to Second. This then results in a compilation error since BothMock doesn't ultimately conform to the Both protocol.

Thanks for the report. I would be happy to create a PR for you as I can't fix it right away.

Close as it appears to be a similar issue to #170.


rsn leak (npc)

@ThatGamerBlue this plugin leaks your rsn when talking to a npc. Can you fix that please?

fixed in f24579adbf007038a561e73f23ed21a536e229e0


Remove $(DEVICE_HOST) from build command.

This makes it possible to build with different versions of Xcode and it wasn't really needed, anyways.

OK, this makes sense, so this means it will build with anything, but our tests can still be on a specific sim. :+1:


Show key hash collisions in the profile

Two interesting things. 1) Simon Peyton Jones remarks that the Hashable instance for Value could hash only the value, not the type as well. 2) how often do we get collisions in the map? Would be an interesting statistic in diagnostic mode. Could also check all keys are equal to themselves in lint.

Johan says taking hashes from multiple types and combining them directly is a bad idea, so I won't do (1).

Probably the easiest thing is to add the info to the profile output, and then analyse it there.

So plan is to write the hash for each key in the JSON, then in the viewer have a collision percentage and a max hash collisions, so people can drill down if there is an issue.

It's unclear if duplicate hash collisions would actually have a meaningful impact on the database. Most of the time I'm using an array and indexing by Id so these things don't crop up much.
At the same time, I thought it worth confirming that Hadrian doesn't have too many duplicate keys. Out of 15,810 keys, it has no duplicates at all. This really isn't worth bubbling up to the profiling.


What distro of linux does this really work on?

I tried Ubuntu 22.04 and got demo to work one time.  After that, it never could connect to the switch again.  I tried rebooting and nothing seems to fix it.
Tried running nxbt test, and it successfully creates remote controller, but then times out trying to connect to the switch while I'm sitting at the "Change Grip/Order" screen.
To get it to run the first time, I had to manually install bluez and libdbus-glib-1-dev.
Are there actual directions to make this work somewhere that I'm missing?

I ended up getting it to work with Raspberry PI Desktop.
https://www.raspberrypi.com/software/raspberry-pi-desktop/
Thank you for a great program!!!!


templates using templateRef are broken in >=v3.0

These were removed in
f31e0c6f9 chore!: Remove deprecated fields (#5035)
This field has been deprecated for some time and was removed in v3.0. I'm not sure that this was clearly communicated, otherwise we'd have published a clear migration path for users, and would have followed this ourselves.

@sarabala1979 @whynowy @wanghong230


Broken beaglebone.

We plugged in a beaglebone incorrectly (it recieved -7V on the DC jack instead of the recommended 5V), and it's completely unresponsive now. It's kind of surprising that this happened, because it's supposed to have built in protection from being plugged in
USB power, DC jack power, and pin reset/ pwr button do nothing.
There is no obvious visible damage on the board, but we think it might be salvageable if we figure out exactly what was burned on it.
It's possible that it's U4 the voltage regulator TL5209, is what's broken, and fortunately free samples are available.
I've gone ahead and ordered one, but won't actually get to attempting to fix it until after competition.

Actually, after glancing at the datasheet again it's almost definitely not the TL5209, the datasheet clearly reads:

Reverse-Battery Protection

So that's probably not it.
(This is still a low priority, Just thought I should warn someone before someone tries to yank it out.)
Looking at the schematic more closely, on sheet 2 it looks like TPS65217C is directly connected to the DC jack, so my guess is that this would be the first thing to break.)


Increase frequency of automatic deduplication jobs

Originally we thought that we'd include a deduplication step in the new open access deposit workflow (previously described in https://github.com/psu-libraries/researcher-metadata/issues/630), but we've determined that it won't really be necessary if we simply increase the frequency with which we're already running automated deduplication tasks.
Since possible duplicate publications are already being grouped as they're being imported, and since the first step in this workflow is to find and confirm a DOI for each incoming publication, merging with other duplicate publications that have matching DOIs can happen automatically in the background. It should be fine if automatic merging occurs when the publication is at any given stage in the workflow, but ideally we'd want merging to happen as soon as possible. So we should run the automatic deduplication tasks as frequently as is practical. At least for now we aren't going to worry about possible duplicates that don't match well enough to be automatically merged.
One of our main concerns regarding duplicate metadata in this workflow is the duplication of effort resulting from two coauthors of the same publication each entering the publication into Activity Insight and uploading a file. When that happens, both publications will enter into this workflow, but if auto-merging occurs frequently enough, then any duplicates that enter after the original should either quickly drop out (that is, be auto-merged into the original and deleted) after their DOIs have been confirmed, or the original and its metadata (and thus its stage in the workflow) will be merged into the incoming duplicate.

@EricDurante You may not be able to see the pull request for this: https://github.com/psu-libraries/researcher-metadata/issues/681 .  I increased the frequency of the auto mergers to run daily, since that's about the frequency of our most frequent importers.


Possible improvements with the view transition API

Hello :slightly_smiling_face:
I started using Turn with the view transition API and I noticed a few things that could maybe be integrated into the library, let me know what you think (I am still learning how the API works and its best practices, but I think I have a pretty good understanding of it already).
1. Add an attribute helper to add view-transition-name on elements during transitions
I think one of the best features of the view transition API is the ability to let the browser automatically translate elements from one place to another using view-transition-name. From what I understand (and what I've tested so far), it's important to have this attribute added only during the transition and then removed if the DOM elements are not the same (which will be the case 99% of the time during visits). This is explained here.
With that, I think it's in the scope of this library to add an attribute like data-turn-transition-name that would only get added to its respective element during a view transition, and then automatically removed (by setting the view-transition-name property to an empty string or none).
It would also maybe be interesting to have it "scoped" to its current element, so it does not add the view-transition-name property on every element on the page? I don't know what the best practises for names are. e.g. I have a list of products, do I just add view-transition-name: product-title; to the product I clicked on during the transition, or add view-transition-name: product-title-1;, etc... On each product currently visible on my page?
I did a quick implementation with the current events dispatched by Turn, I have no idea if this is the best way to do it and it could probably get some improvement, but it worked pretty well during my testing.
let pendingTransitions: HTMLElement[] = [];

// Add transition name to elements with data-turn-transition-name attribute (only those inside the initiator)
window.addEventListener('turn:before-transition', (({ detail }: CustomEvent<{ initiator: HTMLElement }>) => {
  if (getPrefersReducedMotion()) {
    return;
  }

  const { initiator } = detail;
  const transitions = initiator.querySelectorAll('[data-turn-transition-name]');

  transitions.forEach((transition) => {
    if (!(transition instanceof HTMLElement)) {
      return;
    }

    // @ts-expect-error Experimental API
    transition.style.viewTransitionName = transition.dataset.turnTransitionName;

    pendingTransitions.push(transition);
  });
}) as EventListener);

// Remove the transition names we added before
window.addEventListener('turn:before-enter', (() => {
  pendingTransitions.forEach((transition) => {
    // @ts-expect-error Experimental API
    transition.style.viewTransitionName = 'none';
  });

  pendingTransitions = [];
}) as EventListener);

With that, my details page would have the transition names set

Some news

News description

And my results on my search page would have the data- attribute with the same name

Some news

News desc...

The title and description now nicely translate when clicking on the link or going back to the search page.
2. Allow hybrid configuration for Firefox/Safari
I found myself in a situation where I had to make a choice : either support only view transition browsers and hope Firefox/Safari implement it soon enough, or give up on it and use data-turn-enter & data-turn-exit only.
This happened because on a page with a navbar header, a footer and a sidebar (lots of navigation), I wanted these elements to not animate during a visit, so I would add data-turn-enter & data-turn-exit to the container with the current view. It works well but breaks the view transition API completely. It seems that as soon as I add these attributes, the view transitions are not taken into account at all (most likely because they conflict with each other as Turn is animating the whole view with a fade). It would be interesting to be able to add these attributes, but only use them if the view transition API is not available.
I know what I want to achieve would most likely be achievable by using CSS only rather than the data- attributes, but it would require more work than simply adding my Tailwind animation to the attribute.

Add an attribute helper to add view-transition-name on elements during transitions

This has been a consideration during the design of the events system. Here's how I have implemented this in a proof-of-concept:
;(function () {
  window.addEventListener('turn:before-transition', function ({ detail }) {
    let { referrer, action, initiator, newBody } = detail

    if (action === 'restore') {
      const selector = 'a[data-transition]'
      initiator = [...newBody.querySelectorAll(selector)].find(
        a => a.href === referrer
      ) || document.documentElement
    } else {
      reset()
    }

    applyNames(initiator)
    applyNames(initiator, newBody)
  })

  function applyNames (initiator, body = document.body) {
    if (!initiator.dataset.transition) return

    // …
    const viewTransitionIds = initiator.dataset.transition.split(' ')

    viewTransitionIds.forEach(function (id) {
      const element = body.querySelector(`[id='${id}']`)
      if (element) {
        // <video id="video_0" data-view-transition-name="video" …>
        element.style.viewTransitionName = element.dataset.viewTransitionName
      }
    })
  }

  function reset () {
    document.querySelectorAll('[data-view-transition-name]').forEach(function (e) {
      e.style.viewTransitionName = ''
    })
  }
})()

To use, give each transitioning element an id and data-view-transition-name attributes:
<video id="video_0" data-view-transition-name="video" …>

Then give links that might trigger a transition, a data-transition attribute that references any IDs of elements that will transition (space separated):
View video 0

On the turn:before-transition event, query the elements that match the initiator's data-transition, and apply their data-view-transition-name.
There is a few parts to this, and the initiator is only a best guess, so until it's a bit more reliable, I'm probably not going to make it a feature.

Allow hybrid configuration for Firefox/Safari

Checkout the hybrid demos: https://domchristie.github.io/turn/examples/hybrid-basic/, https://domchristie.github.io/turn/examples/hybrid-advanced/
I'd recommend creating custom variants to scope the transitions by the html.turn-view-transitions and html.turn-no-view-transitions classes.

@domchristie Thank you for the detailed process. By saying that initiator is not reliable enough, you're talking about an issue with Turbo?
As for the hybrid transitions, I think my situation is a bit more complicated because what I want to achieve is : use view transition only (if available), else use enter/leave animations. As an example of what I am trying to achieve :

  Header

      Some long navigation...

Title

Desc

  Footer

Here, I would like to let the view transition translate the different elements of the page using view-transition-name, I can then edit the animations very easily with CSS. But if the view transition API is not available, then I would like Turn to animate enter/leave on the section (give it a fade out/in). It works well in theory, but in practise, the view transition API stops working because of the CSS to prevent the "flash of content" issue. The CSS is as simple as :
html.turn-no-view-transitions.turn-advance.turn-exit [data-turn-exit] {
    @apply animate-fade-out;
}

html.turn-no-view-transitions.turn-advance.turn-enter [data-turn-enter] {
    @apply animate-fade-in;
}

html.turn-before-exit [data-turn-exit],
html.turn-exit [data-turn-exit] {
    will-change: transform, opacity;
}

.turn-view-transitions.turn-transition [data-turn-enter],
.turn-view-transitions.turn-before-transition [data-turn-enter] {
    opacity: 0;
}

If I remove the last lines, then this specific scenario will work as intended, but other pages will suffer from the "flash of content" issue. I feel like I'm missing something simple, but I can't get my hand on it.

By saying that initiator is not reliable enough, you're talking about an issue with Turbo?

Kind of! Turbo doesn't provide any details as to which element triggered the visit, so Turn makes a best guess.

If I remove the last lines, then this specific scenario will work as intended, but other pages will suffer from the "flash of content" issue. I feel like I'm missing something simple, but I can't get my hand on it.

Would you be able to provide a live demonstration of this?

I do! I tried my best to reproduce the current situation I'm having here.
If you comment
.turn-view-transitions.turn-transition [data-turn-enter],
.turn-view-transitions.turn-before-transition [data-turn-enter] {
    opacity: 0;
}

Then the "flash of new content" issue does not appear on other pages any more, but the hybrid configuration gets broken (the view transition API is basically hidden?).
I also tried your implementation for the transition names, it seems to work just fine for now (although the text zooms a bit too much lol).
Note : The "flash of new content" issue does not seem to appear on this codesandbox, but it definitely does in a real application. Also, your browser will hang for some time after the first visit, I have no idea why, sorry (if you wait it out then it's fine)


Updated LVGL to v8.2 & Added Windows Build Support

Added support for Windows x64 build via Cygwin.
Updated VS Code launch.json & task.json for selecting the diffrent targets.
Updated main.c for LVGL v8.2 which now includes demo code, removed lv_demo repo dependancy.
Updated Makefile to support both Linux & Windows builds.
Updated README.md for Windows build instructions.

I tried but it was not able to compile.
lv_port_pc_vscode/main/src/main.c:141: undefined reference to `lv_theme_mono_init'
collect2: error: ld returned 1 exit status
make: *** [Makefile:57: default] Error 1


Update troubleshoot-nat-connectivity.md

This is line for this document: "If you're still having trouble, open a support case for further troubleshooting:. The link is not taking to open a support case or else you can do similar like another line: "our investigation is inconclusive, open a support case to further troubleshoot".
Use the same line: * If your investigation is inconclusive, open a support case to further troubleshoot.
Removed this line: * If you're still having trouble, open a support case for further troubleshooting.

#sign-off


What else should a scenario contain? Desired speed, lane chage, etc. and how is it defined?

Will be defined in the scenario/generation. Goal definition could be to adhere to the speed limit
Extend GoalDefinitionStateLimits

I think this can be closed: ConfigurableScenarioGeneration allows goal specification based on abstract keywords, left change, right change, but also more customized goals
Speed limits are parameterizable in GoalDefinitionStateLimitsFrenet


Can not create a Push Credential

Yesterday, I create a push credential.
Today, I delete it, and want create a new one.
when I have filled the blanks, and clicked the save button.
I just redirect to the previous page. nothing add.
P.S. My account is a trial account.

And it seems no mater what i fill with all three blanks,
It just redirect me to this page:
https://www.twilio.com/console/voice/sdks/credentials
and did nothing, because nothing added.

Hi @allenming123
Sorry that you are experiencing some technical issue with the developer console, but without your account credential I am afraid we can't help much here. If you are still seeing the same problem, please go to Twilio Support and file a ticket with you account SID so we can use the credential to see if we can find out anything unusual. You may as well mention "Bobie from the Voice SDK team" so our support engineers know to forward the issue directly to the team.
One thing I am curious is that are you seeing any error message popping out in the console when you clicked the save button?
Thanks
-bobie

ACCOUNT SID: AC0305d404dd2af5ca883cc1d8de7ce1bc
no error at all, when i clicked save button, it just redirect me to the following page:
https://www.twilio.com/console/voice/sdks/credentials
原始邮件
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>发送时间:2018年3月7日(周三) 07:12
主题:Re: [twilio/voice-quickstart-objc] Can not create a Push Credential(#93)
Hi @allenming123
Sorry that you are experiencing some technical issue with the developer console, but without your account credential I am afraid we can't help much here. If you are still seeing the same problem, please go to Twilio Support and file a ticket with you account SID so we can use the credential to see if we can find out anything unusual. You may as well mention "Bobie from the Voice SDK team" so our support engineers know to forward the issue directly to the team.
One thing I am curious is that are you seeing any error message popping out in the console when you clicked the save button?
Thanks
-bobie
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Hi @allenming123
I've passed the info to the Notify team and am waiting for their help to see if they can find any anomaly regarding your attempt to create the push credential.
Please stay tuned.
Thanks
-bobie

Hi @allenming123
It appeared to be a bug in https://www.twilio.com/console/voice/sdks/credentials. The console team has identified the issue and updated. Could you please try again and let us know if you are able to create Push Credentials again.
Thanks and sorry for the inconvenience.
-bobie

@bchen-twilio The problem is settled, thanks!


Adjacent tags with whitespace between them are stripped

Description
Thanks for maintaining this library! I wanted to flag an issue where adjacent tags that have only whitespace between them are being stripped, even when keep_typographic_whitespace is set to true, resulting in the whitespace being removed and distinct words being jumbled together.
Steps to Reproduce

Install the html-sanitizer library in a Python environment.
Use the following code snippet to sanitize an HTML string containing adjacent tags with whitespace:

from html_sanitizer import Sanitizer

html = 'This is some text with adjacent tags.'

sanitizer = Sanitizer({
        "whitespace": set(),
        "keep_typographic_whitespace": True,
})
sanitized_html = sanitizer.sanitize(html)

print(sanitized_html)

Observe the output. The expected output should maintain the whitespace between the adjacent tags, like this:
This is some text with adjacent tags.
However, the actual output removes the whitespace and merges the adjacent tags:
This is sometext with adjacent tags.
Expected Behavior
When sanitizing HTML content, the whitespace between adjacent tags should be preserved. The adjacent tags should not be merged together, and the whitespace should remain intact.
Actual Behavior:
The html-sanitizer library removes the whitespace between adjacent tags and merges the tags together, resulting in the loss of whitespace and potentially altering the intended formatting of the HTML content.
Additional Information:
Python version: 3.8.15
html-sanitizer version: 2.4.2

Thanks for the excellent bug report!


Refactor GovspeakContent and GovspeakContentWorker

This PR moves all of the govspeak -> html rendering logic into the GovspeakContent class. This will allow it to be called elsewhere e.g. when the HtmlAttachment is being presented for the Publishing API. When that is done we may be able to get rid of the GovspeakContentWorker altogether which I'll do in a further PR if possible.
This is related to https://github.com/alphagov/whitehall/pull/2543 and is mentioned there.

👍


Not save old data of previous apk when update apk.

Please try to fill all questions below before submitting an issue.

[ ] On which android versions do you have this issue? :
[ ] On which phones do you have this issue? :
[ ] Which hawk version are you using? :
[ ] Does this issue happen always or is it flaky? :
[ ] Can you write failing test? :
[ ] If it is Hawk.put and Hawk.get issue, can you write down which data you were trying to save and get it back?
[ ] Is the data you are trying to save it huge or small?

On which android versions do you have this issue?
After OS update from android 6 to 7
On which phones do you have this issue?

Galaxy S6 Edge (zerolte)
Galaxy A5(2016) (a5xelte)
Galaxy Note5 (noblelte)
Galaxy S6 Edge (zerolte)
Galaxy A3(2016) (a3xelte)

Which hawk version are you using?
1.23
Does this issue happen always or is it flaky?
always after OS update
Can you write failing test?
no
if it is Hawk.put and Hawk.get
Hawk.put("SOME_KEY", 0L) return false and if i reed this property Hawk.get("SOME_KEY", 0L) I receive old value
Is the data you are trying to save it huge or small?
small
How can I fix that?

Sorry @harm, Just a mistake in my code. sorry for raise this bug. And i confirm, HAWK have no this issues. :) Many Thanks


Resnet

@ShamieCC I am unable to review until next weekend. can you assign new members ? @emre570 for example

Some rephrasing is needed. I suggest to use Grammarly to rephrase. Free version is okay.

@ShamieCC  I checked with Grammarly and proposed these changes. Still, it's better if you check it yourself!

Some rephrasing is needed. I suggest to use Grammarly to rephrase. Free version is okay.

I have installed Grammarly now and will use it going forward thank you.

Some rephrasing is needed. I suggest to use Grammarly to rephrase. Free version is okay.

@ShamieCC I checked with Grammarly and proposed these changes. Still, it's better if you check it yourself!

Thank you for the proposed changes, I have committed some of them. I will use Grammarly from now on.


List All Work Items and Commits/Changesets Associated with an Entire Development Branch in the Release Notes

VSTS Extension you are using
Generate Release Notes Build Task
Where are you running it?
TFS Version 16.122.27102.1

I have used the extension to get the lists of work items and commits/changesets for a particular build. However, I am working in a CI environment where pull requests and subsequent merge commits are done frequently by various team members, which, in return triggers its associated CI build. In that build definition, we have included the 'Generate Release Notes Build Task'.
 Thus, we lose all of the earlier commits. What I want is a collective release note document including all the builds (and their associated workitems & changesets) triggered from a specific branch. Is such a thing even possible?Any sort of suggestion will be highly appreciated. Thanks in advance.
The following is the current output of my 'Generate Release Notes' build task:
#Release notes for build DexmoMiddleware-Build
Build Number  : 20171214.4
Build started : 14/12/17 14:24:09
Source Branch : refs/heads/0.2.0
Associated work items

Product Backlog Item 154 [Assigned by: Onur Leblebici <UNIVERA\onur.leblebici>] complete missing dexmo core tests

Associated change sets/commits

ID d8e2f155ceaae8f6b2169cc02f6ad82761f0c36c log level tests added
ID 8d8ed64d5948734d00afef5196689538798567bc test code coverage improvements
ID 958c30199cbe0326fde3816fdc6ff86c3d17c248 generic type class constraint added
ID 6d8544d9c013e22a769b8bd79b9edbaa7480dce2 dexmo core test coverage improvements
ID c3462ee78955e74cbf881a187fb9cc6c02fd3e47 Merged PR 22: test coverage ratio improvements

test coverage ratio improvements
Related work items: #154

I have same problem.

A couple of quick fixes sprint to mind without a code change

The releasenores.md file is configurable. You could make the release notes output file name something line releasenote-($buildbuildnumber).md
The contents of the release notes file are also provided as a build output variable. You could use this as an input into a bit of inline PowerShell that appended the contents into a file.

Would either of these work?

Those could both be somewhat a workaround, though what I want in the end of the day would a collective ReleaseNotes.md file which includes all the builds triggered from their respective branch.
More specifically, say, I have a repository named MyRepo, and in that I have a master branch, into which I regulary commit and push my source code. In our CI environment, every commit to master triggers a build, and in that build definition, we include the task 'Generate Release Notes'. I want this task to list exacly each and every build that is triggered, as well as the workitems&changesets associated with it. However, as in the original post where I have attached the output of my build task, the Powershell script fetches only that particular build's associated workitems, and commit/changesets.

Exactly!

That's do'able. I will try to get it done ASAP, probably be into the New Year

Actually, you probably do not have to rush it. I have investigated into the powershell source files .ps1 and .psm1 and found that you had used TFS API to perform REST calls to retrieve data related to work items based on build IDs. Would it be possible to modify this REST call similarly to get work items not based on their build IDs, but based on their branch/iteration path? That way I could list the work items associated with a given branch/iteration path in their entirety. That, indeed would be COMPLETE solution to my case, rather than a workaround.

Actually, you probably do not have to rush it. I have investigated into the powershell source files .ps1 and .psm1 and found that you had used TFS API to perform REST calls to retrieve data related to work items based on build IDs. Would it be possible to modify this REST call similarly to get work items not based on their build IDs, but based on their branches/iteration paths? That way I could list the work items associated with a given branch/iteration path in their entirety. That, indeed would be a COMPLETE solution to my case, rather than a workaround.

Is there any update on this?

I see no reason why that could not work and it might actual provide a solution. However, it is a good deal of work. Not sure when I will have enough time to undertake the work.
Also how do you see the branches/iteration path being passed in?

as parameters
autodetched from the builds

I suppose it would be better if was automatically fetched from the build, since this is an all-automated CI workflow we are talking about.

Hello again @rfennell,
As I've mentioned in earlier comments, I'm trying to consume TFS RESTful API using WIQL to get workitems based on their iteration paths. To that end, I need to get the source branch whether from the build definition, or as a reference from TFS build environment variable.
To provide some context, I am doing an Invoke-RestMethod request (its method being 'POST') within the powershell script and passing the query as application/json to the request as follows:
{
    "query": "Select [System.Id], [System.Title]
	       From WorkItems
	       Where ([System.WorkItemType] = 'Bug'
	              OR [System.WorkItemType] = 'Product Backlog Item')
	              AND [State] <> 'Done'
	              AND [System.IterationPath] = <source_branch>"
}

In our build environment, our iteration paths and source branch names are the same. Like I said, I need to replace the <source_branch> with an actual reference to the source branch that the build is triggered from.
In short, I've found that you have gotten some of the build details in GenerateReleaseNotes.ps1 using the environment variables:
# Get the build and release details
$collectionUrl = $env:SYSTEM_TEAMFOUNDATIONCOLLECTIONURI
$teamproject = $env:SYSTEM_TEAMPROJECT
$releaseid = $env:RELEASE_RELEASEID
$releasedefid = $env:RELEASE_DEFINITIONID
$buildid = $env:BUILD_BUILDID
$builddefname = $env:BUILD_DEFINITIONNAME
$releasedefname = $env:RELEASE_DEFINITIONNAME
$buildnumber = $env:BUILD_BUILDNUMBER
$currentStageName = $env:RELEASE_ENVIRONMENTNAME

Is there such a way that I can get the source branch from which the build is triggered as an environment variable, say, something like  $sourcebranch = $env:BUILD_SOURCEBRANCH? Any help on this will save my day. Thanks in advance!

Will give it a try and get back to you, @ChrisLGardner! Thanks.


Only delete default backend when there are no loadbalancers

Previously we were deleting the IG(s) when there were no more backend services (i.e the backend pool had no Services to sync). This mirrors how they are created.
However, in the case where we have an Ingress with 0 nodeports (i.e user sticks type=ClusterIP Services into the Ingress), we would still like the lb to get an IP, and requests sent to this IP to get a 404 from the default backend.  For this we need to keep the default backend around till there are no more lbs, and by extension, we also need to keep the IG around for the default backend.
Also adds some better events in the case where the default backend has no nodeport.

This change is

Coverage decreased (-0.2%) to 41.054% when pulling a6b0405480d1e7541d9c60cf5ee52fd6051f9088 on bprashanth:default_backend_ig_delete into f90e9eeb7c64b7679038e99d5719a69fab270c8e on kubernetes:master.

LGTM


Problem when build: export { removeConsole as default }

"typescript": "^4.6.4",
"vite": "^3.2.0",

Removing this line hels:

BTW: Useful plugin, thanks ; )

Hey, is it convenient to provide a reproduction warehouse, so that I can easily debug

Use export default removeConsole; instead of export { removeConsole as default };, maybe it will be fine. welcome pr 😊

Please upgrade to the latest version, it should be fixed


properties with double hypen at beginning break cli linting

What version of Sass Lint are you using?
1.12.1
Please include any relevant parts of your configuration
none
What did you do? Please include the actual source code causing the issue.
installed sass-lint globally, ran "sass-lint file.scss" in command line
file.scss contents:
.thing {
--mdc-layout-grid-gutter-phone: 16px;
}
What did you expect to happen?
results of linting file.scss
What actually happened? Please include any error messages given to you by Sass Lint.
/usr/local/lib/node_modules/sass-lint/lib/rules/property-sort-order.js:108
name = prop.first('ident');
^
TypeError: Cannot read property 'first' of null
at /usr/local/lib/node_modules/sass-lint/lib/rules/property-sort-order.js:108:26
at Node.forEach (/usr/local/lib/node_modules/sass-lint/node_modules/gonzales-pe-sl/lib/gonzales.js:179:83)
at Node. (/usr/local/lib/node_modules/sass-lint/lib/rules/property-sort-order.js:106:15)
at /usr/local/lib/node_modules/sass-lint/node_modules/gonzales-pe-sl/lib/gonzales.js:308:41
at Node.traverse (/usr/local/lib/node_modules/sass-lint/node_modules/gonzales-pe-sl/lib/gonzales.js:288:6)
at Node.traverse (/usr/local/lib/node_modules/sass-lint/node_modules/gonzales-pe-sl/lib/gonzales.js:293:36)
at Node.traverse (/usr/local/lib/node_modules/sass-lint/node_modules/gonzales-pe-sl/lib/gonzales.js:293:36)
at Node.traverseByType (/usr/local/lib/node_modules/sass-lint/node_modules/gonzales-pe-sl/lib/gonzales.js:307:11)
at Object.detect (/usr/local/lib/node_modules/sass-lint/lib/rules/property-sort-order.js:99:9)
at /usr/local/lib/node_modules/sass-lint/index.js:134:27
If you're using a IDE plugin have you tried the CLI too?
N/A

For anyone wanting to get around this for now, use the following:
Mixin
@mixin root-prop($prop: null, $value: null) {
	@if ($prop and $value) {
		#{$prop}: $value;
	}
}

Usage
:root {
	@include root-prop(--root-prop, #000000);
}

Thank you Noah Mason for coming up with a workaround.  It would be nice -- maybe it should be a feature request -- if sass-lint supported CSS custom properties (variables) in Sass.

This issue is currently blocking me.
Looks like there are two separate PRs aimed at fixing this, #1225 and #1207.
Is there something I can do to help move this toward the light?

@altearius The mixin provided by Noah is what I've been using in my projects (two comments up from yours).

@NetOperatorWibby  Currently, I find it preferable to disable the property-sort-order rule rather than introduce workarounds.  My sass is correct without the mixin.  I do not choose to change correct code into confusing code because there is bad code in a third-party tool, unless there is no other choice.

@altearius To each their own. Personally, I didn't feel like waiting on this to get fixed and I didn't find alternatives that suited my needs. I also wanted to continue on with my work.

I am getting this issue too. i am using 1.4.0

I am getting this issue too. i am using 1.4.0


feat: add after hook method on session

feat: add after hook method on session
refactor: don't trigger hooks in goroutine

Codecov Report

Merging #43 (9cd9f90) into master (626cc2c) will increase coverage by 0.07%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #43      +/-   ##
==========================================
+ Coverage   95.12%   95.20%   +0.07%
==========================================
  Files          11       11
  Lines         369      375       +6
==========================================
+ Hits          351      357       +6
  Misses         12       12
  Partials        6        6

Impacted Files
Coverage Δ

server.go
83.33% <100.00%> (+0.37%)
:arrow_up:

session.go
98.83% <100.00%> (+0.05%)
:arrow_up:

Continue to review full report at Codecov.

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


chore(deps-dev): bump dependencies in the rollup project

WIP not working, there are dependency conflicts
Bump rollup dependencies
Don't update @types/node, prevent to have type errors as we are using an old typescript version (4.5)

Intermediate errors when not overriding the glob version
With some intermediate (releases available at a time that have received new updates afterwards) versions that were used during the developments of this PR, the glob dependency generated type errors.
At that time, an attempt to set/override the glob version as been tested, but it failed as well.
The usage of newer versions of some dependencies on 2024-10-04 fixed the issue: there is now no need to override the glob version.
Past errors, see https://github.com/process-analytics/bpmn-visualization-examples/actions/runs/10795028440/job/29940770804?pr=604
Error: node_modules/@types/glob/index.d.ts(29,42): error TS2694: Namespace '"/home/runner/work/bpmn-visualization-examples/bpmn-visualization-examples/projects/typescript-vanilla-with-rollup/node_modules/minimatch/dist/commonjs/index"' has no exported member 'IOptions'.
Error: node_modules/@types/glob/index.d.ts(74,30): error TS2724: '"/home/runner/work/bpmn-visualization-examples/bpmn-visualization-examples/projects/typescript-vanilla-with-rollup/node_modules/minimatch/dist/commonjs/index"' has no exported member named 'IMinimatch'. Did you mean 'Minimatch'?
Error: Process completed with exit code 2.


Node.js bindings: Add infrastructure and start binding platform functions (v2)

This PR replaces #1233

Ummm, what is __asan_unregister_globals and why is soletta using it :)

https://www.google.fi/search?q=__asan_unregister_globals brings up some interesting pages ...

https://github.com/google/sanitizers/issues/380 is interesting. Perhaps this is issue arises from the fact that soletta.node is built with g++ whereas soletta.so is built with gcc.

It's libasan thing. You can enable/disable this address sanitizer in the menuconfig
basic -> compiler options -> compiler sanitize
It's useful to detect uninitialized reads and memory leaks

@ceolin so, does this mean it needs to be apt-get install-ed on the semaphore?

@ceolin is libasan getting loaded dynamically? If so, it may be running into the same issue as https://github.com/solettaproject/soletta/issues/1331

i think it's dynamic. I am seeing what can be happening

Maybe we should have a test where we load soletta with RTLD_LOCAL | RTLD_NOW - which is what happens when soletta is loaded from another library, to make sure that chaining works. Of course, this still wouldn't catch issues like #1331 ... hmmm ...

What if we make use of libasan only when building in debug mode?

On Fri, 29 Jan 2016 08:29:28 -0800, gabrielschulhof wrote:

What if we make use of libasan only when building in debug mode?

That's already the case, IIRC.

Reply to this email directly or view it on GitHub:
https://github.com/solettaproject/soletta/pull/1369#issuecomment-176848164

i've made a pull request passing -z,defs to linker. This should check if there are undefined symbols.

OK, I'll wait for that to land, then I'll rebase onto it and hopefully this issue will no longer be present.

@gabrielschulhof Could you please rebase with the master branch and try again?
Thank you

@gabrielschulhof You need to add to depedency check if the user have npm installed. I tried to run your branch and the build broke because I did not have npm.

@cabelitos you have node but you don't have npm? I have a check for node, and node always comes with npm.

+1


Use Incognito in visual regressions to avoid visited link styling

🛠 Summary of changes
Attempts to fix some test flakiness in visual regression specs, where links may sometimes be "visited" and appear in a purple color depending on test parallelism, since pages are now run concurrently across multiple tabs as of #389.
The solution is to use a Chrome Incognito (private browsing) context, where history will not be remembered. In my brief testing of a live Incognito tab, links will never show with visited styling.
📜 Testing Plan
Build should pass.
Test locally:
ONLY_VISUAL_REGRESSION_TEST=1 make test

Reverting to draft since this did not resolve the test failures.

I think the initial changes make sense, but the bigger issue is that usa-link--visited doesn't exist, and there's no real way to "force" a link to be styled as visited. The way this is done in USWDS documentation is with a custom CSS class .usa-color-text-visited which is specific to their documentation site (source). We don't really have a good way to replicate that, so I opted to just remove it for now, and add a cache busting query parameter on other links which may be considered "visited".
The build will fail since the content of the page is being changed from the live site, but it should pass moving forward I hope.


Reference to Stat Modifier Formulas

I need the stat modifier formulas for the Character UI Page. If we have them made, or if they are straight from a DND handbook, could someone post a link here.

https://roll20.net/compendium/dnd5e/Ability Scores#content
From what I see: subtract 10 from the ability score and then divide by 2, and that's the ability modifier.

Strength, Constitution, Wisdom, Dexterity, Charisma, and Intellect:  (x-10)/2
Proficiency: (Math.ceil((level) / 4) + 1)
Level is based on XP points that I have to calculate. https://roll20.net/compendium/dnd5e/Character Advancement#content
I don't know if we can derive hit points from hit points max. We may need to track this as I don't know damage taken.
Does our Ability_Points refer to Ability Check (I'm pretty sure it does)
Initiative may not make sense for our DB: https://www.d20srd.org/srd/combat/initiative.htm

@drowsell Is this closable?


fix(cos): optimize error message

:tada: This PR is included in version 2.5.6 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Clarify landing strip docs

It's not clear that the specified value for REPORTER has to be exactly landing, not landingstrip or something.

@APerson241 thanks!


Update NativeTests.exe to use TestHooks, add UnicodeText tests from #4905

@aileronajay did the original work for this PR, but adding TestHooks to NativeTests.exe was required and a bit too involved for a first-time contributor. Hopefully this will allow more direct native unit testing in the future.

@jackhorton nit: ideally the original commit will be in the history, or the author(original)/committer(you) of the commit we merge here should be set so that the original author gets credit in our history.

At this point its much easier for me to just --amend @aileronajay as the author than to try to rebuild the history.

@jackhorton that's perfect


Lag spike on server due to Elder Guardian

Hello hello 👋
Describe the bug
I encounter lag spikes coming from Progressive Bosses on my modpack, I used spark to detect the lag spike and it says that it has something to do with the elder guardian.
Versions:

Minecraft: 1.16.5
Forge: 36.2.34
Progressive Bosses: ProgressiveBosses-3.4.3-mc1.16.5
InsaneLib: InsaneLib-1.4.2-mc1.16.5

Steps to reproduce

Fly fast on a heavy modded server
Use spark to find out the lag spike
(I wouldn't recommend doing all this tbh, I'm just here to talk, maybe you'll have an idea if that ever happened with someone else here...)

Expected behavior
No lag spike ? :D
Screenshots
Here is the spark link explaining the lag spike : https://spark.lucko.me/5x7jyKXlMz
Logs
latest.log
Can the issue be reproduced with a mininal set of mods? (E.g. Progressive Bosses + InsaneLib + Tinkers' Construct)
Probably not
Thank you for your mod also, I'm really enjoying it. If you have any idea on why this would happen, that would help me a lot. Thanks again :)

That's pretty strange. I even check for nearby Ender Guardians every 20 ticks instead of every tick

The spark link has expired and got no other people with same problem. Just reopen the issue if still persists


devcontainer: simplify and remove Dockerfile

Signed-off-by: Sven Anderson<EMAIL_ADDRESS>

Looks OK to me. As like last time it might be nice to have another vscode user take it for a spin before merging but it isn't required.

There's just @rajatsing, so he can try it out until tomorrow I would say. Otherwise I will just merge it.

I'll take a look at it

So I tested it but I am not sure what am I suppose to test here?. Is it for the caching of the downloads somewhere locally in the machine or something else that I might have missed?.
IF it was the caching f the downloaded packages, the no, it just downloads all the needed packages every time I run the test, the command that I am using to run the test is, here I was running the TestGetMirrorUUID test.
make test-multi-container ENTRYPOINT_ARGS="--test-pkg rbd --test-run ^TestGetMirrorUUID$"

The output snippet below will be common for all the test, after downloading all these files, the actual test is executed
go: downloading golang.org/x/sys v0.0.0-20200501145240-bc7a7d42d5c3
go: downloading github.com/aws/aws-sdk-go v1.35.24
go: downloading github.com/jmespath/go-jmespath v0.4.0
go: downloading github.com/stretchr/testify v1.4.0
go: downloading github.com/gofrs/uuid v3.2.0+incompatible
go: downloading github.com/pmezard/go-difflib v1.0.0
go: downloading github.com/davecgh/go-spew v1.1.0
go: downloading gopkg.in/yaml.v2 v2.2.8
github.com/ceph/go-ceph
github.com/ceph/go-ceph/internal/retry
golang.org/x/sys/internal/unsafeheader
github.com/ceph/go-ceph/rgw
github.com/ceph/go-ceph/common/commands
github.com/aws/aws-sdk-go/aws/client/metadata
github.com/ceph/go-ceph/internal/errutil
github.com/ceph/go-ceph/internal/cutil
golang.org/x/sys/unix
.
.
.
.
.
.

@rajatsing

So I tested it but I am not sure what am I suppose to test here?. Is it for the caching of the downloads somewhere locally in the machine or something else that I might have missed?.

Sorry, I probably should have given more context. See updated description.

IF it was the caching f the downloaded packages, the no, it just downloads all the needed packages every time I run the test, the command below is what I am using to run the test, here I was running the TestGetMirrorUUID unit test.

No, it's not about the caching of the packages required for the tests. This you have to enable with USE_CACHE=1 like described in #513.

@mergifyio rebase

I merged this, because it was bothering me not having it in the master branch. If there are any issues coming up for you @rajatsing, I will fix short term. But I think at the moment I'm the only one actively using this.

My bad @ansiwen and yes to worked!.
I forgot to mention it in here.


DataArray.to_masked_array always returns array

Should fix https://github.com/xray/xray/issues/684

It also would be great to have a quick note in "what's new"

Looks great to me, thanks!

cool, thanks for this @femtotrader


Add a "zen/reading/distraction free" mode

Just an idea, press a keyboard shortcut to hide all menus/pagination, display only the article content.
Examples:

Safari with the "Reader View"
Sublime Text with the "Distraction free mode"
...

I've moved towards the zen route in my fork of your default theme. It's basically slightly different fonts/spacing, removal of the border lines, and most importantly, a few max-width statements that maintain a line width that is easy to read.
It seems to me that a "full screen mode" could be an interesting way to do this. In this way, branding, menus and pagination could be hidden under the CSS :fullscreen/:moz-full-screen/:webkit-full-screen pseudoclass. We would utilize the key shortcut that's a standard part of the browser/window manager -  for example.


Fix rails 5.x ORDER BY change

ActiveRecord recently made a small change that causes the following
error in master:
 ActiveRecord::StatementInvalid:
   PG::InvalidColumnReference: ERROR:  for SELECT DISTINCT, ORDER BY expressions must appear in select list
   LINE 1: ...L AND "spree_variants"."product_id" = $1 ORDER BY "spree_var...
                                                                ^
   : SELECT COUNT(*) FROM (SELECT DISTINCT "spree_assets_variants".*
This should fix the current travis fails for solidus 2.3-master.

Travis is all green! :tada:

Hi, I'm getting the same error described here. Any chance this could get merged?
Something else to consider: removing the default_scope from https://github.com/solidusio/solidus_asset_variant_options/blob/master/app/models/spree/variant_image.rb#L8
default_scope does nothing but cause pain and it's recommended to not use it.


Feature 'cvt with .bf16' requires .target sm_80 or higher Error

An error message stating that "Feature 'cvt with.bf16' requires.target sm_80 or higher Error" appears when I try to fine-tune Mamba. I looked up this repo . I'm fine-tuning in the Tesla T4 card it uses Turning Architecture and only supports SM_75, although SM_80 or above is needed from error. Thus, support for SM_80 in Ampere Architecture, such as A100, the error is being caused by ineffective hardware or if there is another cause. I would appreciate clarification. Is there another option to fine-tune in T4?
Thanks in advance

I know I'm very late to this but you can change the datatype to float32, this should help


hotstar 1.1.1 login issue

This has to be fixed by @iMro0t , He is only one who can fix this issue.!!!


Implement  to Character detail table

Description
Currently character detail table still uses old hard coded implementation of DataTable, we need to migrate it to use the re-usable DataTable

Hey team! Please add your planning poker estimate with ZenHub @AnnieTran13 @luigibesani @pascwhale


Need Subscribe (UnSubscribe) Topics by Server site request.

Environment

VerneMQ Version:1.3.0
OS: centos 6
Erlang/OTP version (if building from source): 20.1

Expected behavior

Use php to Subscribe to topics instead of clients

Actual behaviour

php use clients 's id to subscribe topics may kickout client
maybe we can add a function Subscribe() and UnSubscribe()  in veremq_dev api

Hi, if I understand it correctly you'd like to subscribe or unsubscribe topics on behalf of a client using some other API than connecting with an MQTT client. This is currently not directly supported. One way to achieve this (changing the subscriptions of a client) would be to change the ACL rules for the client and then disconnect it using vmq-admin session disconnect command which would force the client to reconnect and reload the ACLs.

@larshesel i want to  use vmq_reg:subscribe/3 and vmq_reg:unsubscribe/3
but return:
vmq_reg:subscribe(true, {[],<<"c_65275750">>} , {[<<"User">>,<<"65275750">>,<<"Inbox">>],2}).
** exception error: undefined function vmq_reg:subscribe/3
vmq_reg:module_info().
[{module,vmq_reg},
{exports,[{subscribe,4},
{unsubscribe,4},
the source https://github.com/erlio/vernemq/blob/c66e5463f2ebe67b40267a0031e9a71574801d64/apps/vmq_server/src/vmq_reg.erl#L21


feat: add support for debian based repos

What CDN does this PR relate to

Popular Debian based repos

Debian
Ubuntu
Kali
Mint
Pop_OS!
Deepin
ppa launchpad

Does this require running via sniproxy

untested
Capture method

repo list is available in distro sources.list
Testing Scenario

home. Added the records and ran apt update; apt upgrade and watched lancache logs to ensure caching happened.
I confirmed that caching happened
Testing Configuration
<!-- Paste either your docker run command from the DNS container OR explain how you have setup DNS zone files etc to test this issue -->

Sniproxy output
Please paste the output from docker logs <sniproxy container name/id> | sed 's/.*\:443 \[//;s/\].*//' | sort | uniq -c below
<!-- If you are running sniproxy paste the output to the following command
docker logs <sniproxy container name/id> | sed 's/.*\:443 \[//;s/\].*//' | sort | uniq -c
-->

We are unlikely to add Linux repos as upgrading Linux is not a core feature required by LAN. I would look at apt-cacher-ng, which is a proxy designed to do this which understands the shap of Linux repos.

I would suggest otherwise. Linux gaming is growing with the addition of proton. Windows has WSL now that supports Ubuntu and Debian. SteamDeck is a Linux-based game console (adding support would be useful (I think its arch based?). Game servers (using SteamCMD) that run on Linux etc.
To me, this is no different that supporting Windows Updates which is currently supported by LAN cache.

For my personal use case, I am developing a new docker container for my game server project LinuxGSM (That was first developed at a Multiplay LAN event) which requires repeated access to update Ubuntu. Adding this is greatly speeding up the development of the docker containers.  Debian-based distros are also by far the most popular distros for hosting game servers. So to me from a game server perspective this is very useful.
I hope I have highlighted how useful this is for gamers and game server hosters. 😃

Windows support is really a side consequence of supporting game purchase through the Microsoft store. While I accept that more people have access to Linux. It's still an overwhelming large windows market at LAN.

I'd also love to see this added. Perhaps it doesn't make so much sense in a LAN-party setting, but it certainly does for the "home setup with multiple gamers." And seeing that LANCache runs in docker, anyone using this is sure to have at LEAST one Linux host.

I am in support of adding this. We use lancache at our lan party which is a sub event of the SouthEast Linux Fest. It is not uncommon to have 300-400 linux based computers using the network at an given time.

I’d also add to the pile. That with two steam decks in the house now that
caching Linux would be useful.
On Fri 11 Nov 2022 at 17:38, zunder1990 @.***> wrote:

I am in support of adding this. We use lancache at our lan party which is
a sub event of the SouthEast Linux Fest. It is not uncommon to have 300-400
linux based computers using the network at an given time.
—
Reply to this email directly, view it on GitHub
https://github.com/uklans/cache-domains/pull/208#issuecomment-1311982022,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAVOY6KVNNBUS2Q4R2YNN2TWH2ACZANCNFSM6AAAAAARL2AU7E
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

@DuzAwe SteamDeck updates would be a good addition. I believe it is arch-based and I have no experience in that distro. Hopefully it is possible to cache updates like Debian based distros

Looks like it's possible to cache packages using Squid. So I am assuming it wouldn't be a stretch to support pacman
Squid
https://wiki.archlinux.org/title/Package_Proxy_Cache
Nginx
https://fernandobarillas.com/blog/2017/caching-pacman-packages-with-nginx/

We are unlikely to add Linux repos as upgrading Linux is not a core feature required by LAN. I would look at apt-cacher-ng, which is a proxy designed to do this which understands the shap of Linux repos.

If someone wants to maintain a fork that includes them it should work. However the current thinking our side is that we are not going to include them in the main list.

I will setup an action to check the main repo to make sure it gets updates.

Oh, I didn't see this: https://github.com/uklans/cache-domains/pull/208/commits/54ee3311bc111779a4a0b10b709b8a61352fe44b.
I've changed my fork to only include http domains, I can revert my changes and close my PR if you want (I wasn't sure if uklans/repo wanted both https and http, or just the http domains).

It could also be worth adding the kernel to the Linux kernel to the list.
I think these should be the correct domains:
mirrors.kernel.org
git.kernel.org
cdn.kernel.org

I could be wrong though, and/or it might not be a good idea to add these, lmk what you think.

We are unlikely to add Linux repos as upgrading Linux is not a core feature required by LAN. I would look at apt-cacher-ng, which is a proxy designed to do this which understands the shap of Linux repos.

Is there a downside to adding more domains to this repo?

Yes, unfortunately debian does not follow the immutability rule which lancache is built on, so adding these to a cache can result in broken package files.
There's is nothing to stop you maintaining your own list with this in however and still using the lancache toolset or others.


Run script sh with data passing

Summary
Being able to run script sh.
Motivation
By creating apps for Macos, it would be nice to be able to run sh scripts.
Basic Example
Example having some input fields to put the data, when the send button is pressed, the sh script is executed, passing the input data.

File Sh:
git clone --progress $project
open ~/$path/$name

Open Questions
I thought I was using child_process, but it seems to only work on node.

The best bet is to write a native module to add support for this. It's unlikely we take something like this in to core any time soon.


merge all fixes into master

Would you please merge all fixes into the "master" branch? We have two branches in GitHub currently:

master
csi-v1.0

I would expect the default branch (remote HEAD) to point to master, but it currently points to csi-v1.0.
This makes me think csi-v1.0 must be some kind of long-lived feature branch, moving ahead of master in some ways, and behind master in other ways?
It's not clear to me which branch we should distribute downstream. It would make it easier for newcomers if "master" was the very latest, since this matches other repositories (like ceph.git) and rook.git).

I'd think rename the branches so that:

csi-v1.0 (current default) becomes the "new" master
current master (i.e. csi v0.3 support) becomes new csi-v0.3 branch.

@rootfs i thought csi-v1.0 will stay in alpha until we sort out all the metadata-related issues?

As this has come up in a couple of other conversations posting my thoughts as well,

Although we state v1.0 branch is alpha, the images from these branches are available for use by users, is there a definitive statement we can make regarding v1.0's alpha status?

The kubernetes driver list carries ceph drivers as v1.0, does this mean anything more than, these drivers are available for testing, and not for production/serious use?

If v1.0 is still in alpha, can we get breaking changes into the same, so that certain aspects need not be supported in the future (assuming we have a fair discussion about the same)

Not attempting to hijack the original thread, but some questions that crop up as we decide if v1.0 is still alpha.
My opinion is it (v1.0) should be alpha, till we can get a few things sorted out and also some CI or testing ironed out, to get to a required and sustainable quality as we add more code in the future.

@ktdreyer merging all the changes from CSI v1.0 branch to master is not possible because of the spec it maintains. ie master is on v0.3 and csiv1.0 is v1.0.0.  I think the best bet would be what @rootfs suggested. however, I doubt it can have some impact on the users who already cloned these repos and using it .

Ok. Can we make master the mainline for development at least?

@rootfs ^^

Ok. Can we make master the mainline for development at least?

Sure, the only concern here is, how is it going to effect the existing customers if we do branch flip/switch..  @rootfs @gman0 can you share your thoughts?

@ktdreyer @humblec let's cut a v0.3 branch from master, then reset master to replicate v1.0 branch, and then make master the dev branch.

@rootfs sounds good to me. Just to make sure, we are in same page, if some users already have the image from current master and if their CO is on a version which is compatible with 0.3 spec, after our update of master branch, do you foresee any issues ?

There will be some CI work for 0.3 branch here
@Madhu-1 can you take all these? thanks

@rootfs, sure let me check what changes i need to make.

proposal here #266

@Madhu-1 @humblec Sorry I started a discussion on this topic at #266 not realizing you had this going here.  I set what I was thinking in terms of a task-list, let me know what you think; if we get a branch csi-v0.3 branch I'm happy to help out with the remaining tasks.

@ktdreyer @j-griffith can we close this one or #266 so that we can continue our discussion on one place so that we don't need to track the same issue in different places.

I would rather keep this open and close #266 considering this came first. @ktdreyer @j-griffith @Madhu-1 .

anything would be fine for me. let  @ktdreyer and @j-griffith decide.

closing this one as a master is the default brach


[Extension Feature Request] Toggle "Low Power Mode" of Battery Preferences ("System" Extension)

Extension – System (built-in extension)
Author: Raycast authors
Describe the feature and the current behavior/state.
The System extension already provides actions to e.g. restart or set the volume. It would be nice to be able to set/toggle the "Low Power Mode" of MacOS using Raycast. It is part of the Battery preference pane.
Currently, no "toggle MacOS Low Power Mode" command is available in Raycast.

Who will benefit with this feature?
Users who want to extend battery life of their laptops, but don't want to dig deep in the preferences.

Seems that there are already some ideas on how to trigger LPM programmatically: https://www.reddit.com/r/shortcuts/comments/qi3nz1/turn_low_power_mode_onoff_on_mac/
In particular the following returns the current LPM state (requires `sudo, unfortunately):
pmset -g | grep lowpowermode | awk -F' ' '{ print$2 }'

Hey @chrisma! I think this can be done better by creating a separate extension for this, like "Battery Controls" where it would be possible to do.
Probably now is the perfect time to build one 😉

I think this can be done better by creating a separate extension for this, like "Battery Controls"

Thanks for the reply! Important to know whether additional "system commands" should be integrated into the built-in Raycast System extension, or be supplemented by additional separate extensions by the community.
The scope of extensions could be the individual screens of the MacOS System Preferences, i.e. Battery, Bluetooth, Displays.