fs.createReadStream throws unhandled exception

In googleauth.ts, nothing handles errors thrown by fs.createReadStream  (for example, when the file doesn't exist), so applications that call getClient have to use an unhandled exception handler.

Interesting!  If I may ask - how did you get into a situation where this happened?  We're actually pretty careful about checking for the file first:
https://github.com/google/google-auth-library-nodejs/blob/master/src/auth/googleauth.ts#L361
Can you share a repro?

I think @eyqs is saying that there is no way callers of fs.createReadStream can handle errors other than by installing global unhandled rejections handlers.

Makes sense :) What I'm asking is - how would I even test something like this?  I could add the few lines of code to attach an .on('error') handler, and make sure to throw. But...  I actually don't know what situation (short of an invalid file path) would trigger an error in this way since we're checking for the existence of the file first.
@ofrobots what do you think?

@eyqs would it be possible for you to put together a test that demonstrates the problem?

Sorry for the delay, and thanks for covering for me, Ali.
Here's a repro:
const {google} = require('googleapis');
google.auth.getClient({keyFilename: "invalid_file"});

The reason is because getClient doesn't call lstat. I can add a pull request that resolves this, if you'd like.


Problem with 320x240@60 FPS

Required Info

Camera Model
R200, F200 or SR300

Firmware Version
<IP_ADDRESS>

Operating System & Version
Ubuntu 15.04

Kernel Version (Linux Only)
3.19.0-66-generic

Build System
Qtcreator

I am currently working with SR300 model and I am facing problem with getting depth and color stream at 320x240@60 fps. I get the following error
terminate called after throwing an instance of 'rs::error'
what():  uvc subdevice 1 cannot provide 320x240:Z16@60Hz DEPTH
I don't find any problem getting 640x480@60fps but I didn't understand why I am not getting it work at 320x240 frame size.

Both F200 and SR300 do not support 320X240 for depth stream.
You can choose between 640X480 or 640X240 modes only.

Hi,
Please check out supported_video_formats for up-to-date list of supported formats.


Add ability to specify pattern using KP's built-in placeholders

The ability to "Add Character Set" is nice, but I think it would be even better if it were possible to define placeholder patterns using the same syntax as the built-in password generator profiles.

https://keepass.info/help/base/pwgenerator.html#pattern

That way you could have excellent compatibility with existing functionality, and could move patterns out of profiles and into the rules attached to entries themselves.
Here's a quick mock-up of what I'm suggesting:

Keep the ability to define simple characters, but also add the ability to do custom placeholder patterns.

Do you have a specific case in mind where this would be helpful? I think the predefined character classes that I have, along with custom character sets, should be enough for just about any password rule. I haven’t seen any services whose password rules would be made easier if KeePass’s placeholder patterns were available here in addition to what the plugin already provides.
The goal of this user interface is not to replace KeePass’s profiles entirely, but to make it so that in most cases users don’t have to think like a programmer in order to use the password generator. Allowing KeePass’s placeholder syntax does not advance this goal.


feat(planning_launch): add new remap to behavior velocity planner

Signed-off-by: TakumiKozaka-T4<EMAIL_ADDRESS>PR Type

Improvement

Related Links

Add detailed stop reason
[New message type for detailed stop reason] (https://github.com/tier4/tier4_autoware_msgs/pull/24)
Description

Add new remapping to /planning_launch/launch/scenario_planning/lane_driving/behavior_planning/behavior_planning.launch.py
This is needed to remap additional stop reason topic in the linked PR.
Review Procedure

Run planning simulator.
Put initial pose and goal.
Run the command : ros2 topic list | grep reason

The following topic should be published :
/planning/scenario_planning/status/stop_reason2
Remarks

Pre-Review Checklist for the PR Author
PR Author should check the checkboxes below when creating the PR.

[x] Code follows coding guidelines
[x] Assign PR to reviewer

Checklist for the PR Reviewer
Reviewers should check the checkboxes below before approval.

[ ] Commits are properly organized and messages are according to the guideline
[ ] Code follows coding guidelines
[ ] (Optional) Unit tests have been written for new behavior
[ ] PR title describes the changes

Post-Review Checklist for the PR Author
PR Author should check the checkboxes below before merging.

[ ] All open points are addressed and tracked via issues or tickets
[ ] Write release notes

CI Checks

Build and test for PR: Required to pass before the merge.
Check spelling: NOT required to pass before the merge. It is up to the reviewer(s). See here if you want to add some words to the spell check dictionary.

@isamu-takagi i forgot this PR. Is this PR need yet?

@yabuta Remapping in launch file is no longer needed because AD API defines the topic name in universe repository. So close this PR.


data structure

how is my database structured?

Hi @vuhungtvt142
I don't understand what you mean exactly.


After ng add @nativescript/schematics, Angular web-project structure/code changed and dont work with ng serve -o

I am new to nativescript but an experienced developer. I have created an angular 9 workspace project and contain some projects and libraries with architecture as:-
projects
   -- library 1
   -- library 2
   -- project 1
   -- project 2
src
   -- app
   -- index.html

I was migrating my project to nativescript and followed this link. After,
ng add @nativescript/schematics
when i do,
ng serve -o

My project only show the content which is placed in app.component.html like some divs only.
However, I have also defined my <router-outlet></router-outlet> in app.component.html but this is not working. As of surprise, while compiling and browsing not showing/throwing any errors/warnings.
Each component has its own routing and module. Used lazy-load in app.module.ts

Apart from this, i created a small dummy project with the same structure but still no luck and i dont want to proceed if this will still persist. Have anyone came across this situation???
package.json
"dependencies": {
    "@nativescript/angular": "~9.0.0",
    "@nativescript/core": "~6.5.5",
    "@nativescript/theme": "~2.2.1",
    "reflect-metadata": "~0.1.12",
    "tslib": "^1.10.0",
    "@angular/animations": "~9.1.11",
    "@angular/common": "~9.1.11",
    "@angular/compiler": "~9.1.11",
    "@angular/core": "~9.1.11",
    "@angular/forms": "~9.1.11",
    "@angular/platform-browser": "~9.1.11",
    "@angular/platform-browser-dynamic": "~9.1.11",
    "@angular/router": "~9.1.11",
    "@nativescript/schematics": "^9.0.0"
    "rxjs": "~6.5.4",
    "zone.js": "~0.10.2"
  }

Still waiting for the answers on this link from other helpful open-source community users too :)

Fixed in latest release, please see here for instructions of use.


Document setup for running vida through pycharm debugger

Being able to properly debug vida is an important step for getting new developers 1) more familiar with the project and 2) debug issues in the web application. We are using pycharm with django integration which with the proper configuration can help us debug the application in the deployed VM.

added a section with a link to a doc with screen shots to the vida-ansible [readme] (https://github.com/ROGUE-JCTD/vida-ansible/blob/master/README.md) file


SAK-42366 - use Base64.getUrlDecoder and error check better

Travis passed but somehow it was not communicated back.


CI for Node

✕ Initializes with two players (3 ms)
✕ Starts the game with a random player (1 ms)

Initializes with two players
Starts the game with a random player
Sets the current player to be whoever it is not


Bring back update notification

The current framework update service is broken. The proposed solution retrieves the last 5 releases from Github and checks the version of the first non-prerelease/RC version against the installed version. The result is cached and is shown to host users as a clear blue button prompting to upgrade. The button opens a new window with the release on Github visible.

For the API rate limits, would a solution for this issue be a service created on a hosted site that caches hourly this information that is needed to connect to the link information provided by GitHub for the update?

@thabaum We have a solution ;)

@donker this looks good to me but I think we need to sync up with the changes in the service itself right? Let's discuss this in next meeting if you are available...

@donker this looks good to me but I think we need to sync up with the changes in the service itself right? Let's discuss this in next meeting if you are available...

Yes, but I'm assuming that is the easy part given we control everything

The UPdate Service changes have been deployed, this is good to go


⚠ Bofrost.be has degraded performance

In 695a07b, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 3744 ms

Resolved: Bofrost.be performance has improved in ccb32c5.


Suppress the excessive information log

Hi,
First of all I would like to thank the author and contributors to this amazing plugin.
As it is at the moment ,I am getting a full screen of information log every 30 seconds or so. Is there a way to suppress it?

Regards,
uswong

@uswong I swear I am not stalking you, but pretty sure this is due to one I brought up a long time ago and can be solved by adding the following to you config (can be found on the README):

You want to set that to true.

Lol.....Mitch, certainly feel like someone is stalking me....
Thanks for that simple solution!  Haha...it is obvious that I did not read the README properly!    Sorted now and finally I have some space on my homebridge screen to look at messages from other plugins!

It drives me nuts when my logs are spammed with information I do not need!

Thanks @mitch7391 for answering this question.
@uswong do you think that we can close this issue?


7 render readme demo reproducibility

Set to render README (#7)
Update README, close #7

Heads-up @stholder3 going to merge this now to keep the ball rolling.


TileMap Placement preview is innacurate if the TileMap has rotation or negative scale

Godot version:

v3.2.2.stable.official
OS/device including version:

Windows 10 v2004 (build 19041.388)
Ryzen 5 3600
R9 290 4GB, Radeon software v20.7.2 (release: 7/11/2020)
Issue description:

When placing tiles on a tile map with rotation or a negative scale, the placement preview (translucent image of the tile to be placed) is inaccurate.
When placed, tiles display as expected. The expected behavior is for the placement preview to match the transform of the tile when placed.
If the tile map is rotated, the preview will not be rotated to match.

A placed tile can be seen under the un-rotated preview
If the tile map is scaled, the preview will be scaled to match, but will not be positioned correctly.

The placed tile is again correct, but the preview is displayed on the top of the tile below the one currently selected
Steps to reproduce:

Create a tile map in a 2D scene
Assign it any tileset
Apply a transform to the tile map that has either:

a negative x and/or y value in its scale
any rotation

Go into edit mode on the tile map, select a tile to add, and move the mouse into the viewport
The tile placement indicator will now be incorrect

Minimal reproduction project:

TileMapError.zip

Seems like draw_texture_rect/draw_texture_rect_region() is used, which will not take into account the transform:
https://github.com/godotengine/godot/blob/ec678c5e94ac1c91c099c15fabc398e80ede7bfe/editor/plugins/tile_map_editor_plugin.cpp#L895-L899
Will make a PR soon to take that into account.


[global_costmap.global_costmap]: Can't update static costmap layer, no map received

Hi,
I try to run the robot.launch.py. The rviz and robot pops up fine but I don't recieve any map from my unitree. Do you know what is wrong with it?
[INFO] [launch]: All log files can be found below /home/uchiwuwu/.ros/log/2024-11-08-09-41-53-364221-uchiwuwu-Inspiron-5593-16788
[INFO] [launch]: Default logging verbosity is set to INFO
IP list: ['<IP_ADDRESS>']
[INFO] [robot_state_publisher-1]: process started with pid [16789]
[INFO] [pointcloud_to_laserscan_node-2]: process started with pid [16791]
[INFO] [go2_driver_node-3]: process started with pid [16793]
[INFO] [lidar_to_pointcloud-4]: process started with pid [16795]
[INFO] [rviz2-5]: process started with pid [16797]
[INFO] [joy_node-6]: process started with pid [16799]
[INFO] [teleop_node-7]: process started with pid [16801]
[INFO] [twist_mux-8]: process started with pid [16803]
[INFO] [joint_state_publisher_gui-9]: process started with pid [16833]
[INFO] [foxglove_bridge-10]: process started with pid [16847]
[INFO] [async_slam_toolbox_node-11]: process started with pid [16849]
[INFO] [controller_server-12]: process started with pid [16859]
[INFO] [smoother_server-13]: process started with pid [16870]
[INFO] [planner_server-14]: process started with pid [16899]
[INFO] [behavior_server-15]: process started with pid [16913]
[INFO] [bt_navigator-16]: process started with pid [16933]
[INFO] [waypoint_follower-17]: process started with pid [16944]
[INFO] [velocity_smoother-18]: process started with pid [16946]
[INFO] [lifecycle_manager-19]: process started with pid [16969]
[robot_state_publisher-1] [INFO] [1731076914.211033696] [robot_state_publisher]: got segment FL_calf
[robot_state_publisher-1] [INFO] [1731076914.211151615] [robot_state_publisher]: got segment FL_calflower
[robot_state_publisher-1] [INFO] [1731076914.211164472] [robot_state_publisher]: got segment FL_calflower1
[robot_state_publisher-1] [INFO] [1731076914.211172185] [robot_state_publisher]: got segment FL_foot
[robot_state_publisher-1] [INFO] [1731076914.211179098] [robot_state_publisher]: got segment FL_hip
[robot_state_publisher-1] [INFO] [1731076914.211185830] [robot_state_publisher]: got segment FL_thigh
[robot_state_publisher-1] [INFO] [1731076914.211192532] [robot_state_publisher]: got segment FR_calf
[robot_state_publisher-1] [INFO] [1731076914.211199412] [robot_state_publisher]: got segment FR_calflower
[robot_state_publisher-1] [INFO] [1731076914.211206664] [robot_state_publisher]: got segment FR_calflower1
[robot_state_publisher-1] [INFO] [1731076914.211213981] [robot_state_publisher]: got segment FR_foot
[robot_state_publisher-1] [INFO] [1731076914.211220617] [robot_state_publisher]: got segment FR_hip
[robot_state_publisher-1] [INFO] [1731076914.211227307] [robot_state_publisher]: got segment FR_thigh
[robot_state_publisher-1] [INFO] [1731076914.211234271] [robot_state_publisher]: got segment Head_lower
[robot_state_publisher-1] [INFO] [1731076914.211241544] [robot_state_publisher]: got segment Head_upper
[robot_state_publisher-1] [INFO] [1731076914.211248059] [robot_state_publisher]: got segment RL_calf
[robot_state_publisher-1] [INFO] [1731076914.211254892] [robot_state_publisher]: got segment RL_calflower
[robot_state_publisher-1] [INFO] [1731076914.211262074] [robot_state_publisher]: got segment RL_calflower1
[robot_state_publisher-1] [INFO] [1731076914.211269456] [robot_state_publisher]: got segment RL_foot
[robot_state_publisher-1] [INFO] [1731076914.211276554] [robot_state_publisher]: got segment RL_hip
[robot_state_publisher-1] [INFO] [1731076914.211283891] [robot_state_publisher]: got segment RL_thigh
[robot_state_publisher-1] [INFO] [1731076914.211290861] [robot_state_publisher]: got segment RR_calf
[robot_state_publisher-1] [INFO] [1731076914.211297587] [robot_state_publisher]: got segment RR_calflower
[robot_state_publisher-1] [INFO] [1731076914.211305318] [robot_state_publisher]: got segment RR_calflower1
[robot_state_publisher-1] [INFO] [1731076914.211312207] [robot_state_publisher]: got segment RR_foot
[robot_state_publisher-1] [INFO] [1731076914.211319173] [robot_state_publisher]: got segment RR_hip
[robot_state_publisher-1] [INFO] [1731076914.211326564] [robot_state_publisher]: got segment RR_thigh
[robot_state_publisher-1] [INFO] [1731076914.211333649] [robot_state_publisher]: got segment base_footprint
[robot_state_publisher-1] [INFO] [1731076914.211340604] [robot_state_publisher]: got segment base_link
[robot_state_publisher-1] [INFO] [1731076914.211347381] [robot_state_publisher]: got segment front_camera
[robot_state_publisher-1] [INFO] [1731076914.211354610] [robot_state_publisher]: got segment imu
[robot_state_publisher-1] [INFO] [1731076914.211362539] [robot_state_publisher]: got segment map
[robot_state_publisher-1] [INFO] [1731076914.211369966] [robot_state_publisher]: got segment odom
[robot_state_publisher-1] [INFO] [1731076914.211377553] [robot_state_publisher]: got segment radar
[teleop_node-7] [INFO] [1731076914.204477662] [TeleopTwistJoy]: Linear axis x on 1 at scale 0.200000.
[teleop_node-7] [INFO] [1731076914.204534225] [TeleopTwistJoy]: Linear axis y on 3 at scale 0.200000.
[teleop_node-7] [INFO] [1731076914.204542006] [TeleopTwistJoy]: Angular axis yaw on 6 at scale 0.200000.
[twist_mux-8] [INFO] [1731076914.204574538] [twist_mux]: Topic handler 'topics.joy' subscribed to topic 'cmd_vel_joy': timeout = 0.500000s , priority = 10.
[twist_mux-8] [INFO] [1731076914.205104184] [twist_mux]: Topic handler 'topics.navigation' subscribed to topic 'cmd_vel': timeout = 0.500000s , priority = 5.
[foxglove_bridge-10] [INFO] [1731076914.232253058] [foxglove_bridge_component_manager]: Load Library: /opt/ros/humble/lib/libfoxglove_bridge_component.so
[foxglove_bridge-10] [INFO] [1731076914.240946380] [foxglove_bridge_component_manager]: Found class: rclcpp_components::NodeFactoryTemplate<foxglove_bridge::FoxgloveBridge>
[foxglove_bridge-10] [INFO] [1731076914.241009218] [foxglove_bridge_component_manager]: Instantiate class: rclcpp_components::NodeFactoryTemplate<foxglove_bridge::FoxgloveBridge>
[foxglove_bridge-10] [INFO] [1731076914.243158489] [foxglove_bridge]: Starting foxglove_bridge (humble, 0.8.0@) with WebSocket++/0.8.2
[foxglove_bridge-10] [INFO] [1731076914.243684146] [foxglove_bridge]: [WS] Server running without TLS
[foxglove_bridge-10] [INFO] [1731076914.243940106] [foxglove_bridge]: [WS] WebSocket server listening at ws://<IP_ADDRESS>:8765
[foxglove_bridge-10] [INFO] [1731076914.244451954] [foxglove_bridge]: [WS] WebSocket server run loop started
[async_slam_toolbox_node-11] [INFO] [1731076914.233874406] [slam_toolbox]: Node using stack size 40000000
[controller_server-12] [INFO] [1731076914.235268562] [controller_server]:
[controller_server-12] 	controller_server lifecycle node launched.
[controller_server-12] 	Waiting on external lifecycle transitions to activate
[controller_server-12] 	See https://design.ros2.org/articles/node_lifecycle.html for more information.
[controller_server-12] [INFO] [1731076914.243952117] [controller_server]: Creating controller server
[controller_server-12] [INFO] [1731076914.264904640] [local_costmap.local_costmap]:
[controller_server-12] 	local_costmap lifecycle node launched.
[controller_server-12] 	Waiting on external lifecycle transitions to activate
[controller_server-12] 	See https://design.ros2.org/articles/node_lifecycle.html for more information.
[controller_server-12] [INFO] [1731076914.265648762] [local_costmap.local_costmap]: Creating Costmap
[smoother_server-13] [INFO] [1731076914.254673421] [smoother_server]:
[smoother_server-13] 	smoother_server lifecycle node launched.
[smoother_server-13] 	Waiting on external lifecycle transitions to activate
[smoother_server-13] 	See https://design.ros2.org/articles/node_lifecycle.html for more information.
[smoother_server-13] [INFO] [1731076914.257947790] [smoother_server]: Creating smoother server
[planner_server-14] [INFO] [1731076914.261474600] [planner_server]:
[planner_server-14] 	planner_server lifecycle node launched.
[planner_server-14] 	Waiting on external lifecycle transitions to activate
[planner_server-14] 	See https://design.ros2.org/articles/node_lifecycle.html for more information.
[planner_server-14] [INFO] [1731076914.266391084] [planner_server]: Creating
[planner_server-14] [INFO] [1731076914.271482258] [global_costmap.global_costmap]:
[planner_server-14] 	global_costmap lifecycle node launched.
[planner_server-14] 	Waiting on external lifecycle transitions to activate
[planner_server-14] 	See https://design.ros2.org/articles/node_lifecycle.html for more information.
[planner_server-14] [INFO] [1731076914.272315651] [global_costmap.global_costmap]: Creating Costmap
[behavior_server-15] [INFO] [1731076914.277607338] [behavior_server]:
[behavior_server-15] 	behavior_server lifecycle node launched.
[behavior_server-15] 	Waiting on external lifecycle transitions to activate
[behavior_server-15] 	See https://design.ros2.org/articles/node_lifecycle.html for more information.
[bt_navigator-16] [INFO] [1731076914.292232639] [bt_navigator]:
[bt_navigator-16] 	bt_navigator lifecycle node launched.
[bt_navigator-16] 	Waiting on external lifecycle transitions to activate
[bt_navigator-16] 	See https://design.ros2.org/articles/node_lifecycle.html for more information.
[bt_navigator-16] [INFO] [1731076914.292329643] [bt_navigator]: Creating
[waypoint_follower-17] [INFO] [1731076914.306554370] [waypoint_follower]:
[waypoint_follower-17] 	waypoint_follower lifecycle node launched.
[waypoint_follower-17] 	Waiting on external lifecycle transitions to activate
[waypoint_follower-17] 	See https://design.ros2.org/articles/node_lifecycle.html for more information.
[velocity_smoother-18] [INFO] [1731076914.306643414] [velocity_smoother]:
[velocity_smoother-18] 	velocity_smoother lifecycle node launched.
[velocity_smoother-18] 	Waiting on external lifecycle transitions to activate
[velocity_smoother-18] 	See https://design.ros2.org/articles/node_lifecycle.html for more information.
[waypoint_follower-17] [INFO] [1731076914.310143613] [waypoint_follower]: Creating
[lifecycle_manager-19] [INFO] [1731076914.329667483] [lifecycle_manager_navigation]: Creating
[lifecycle_manager-19] [INFO] [1731076914.340506942] [lifecycle_manager_navigation]: Creating and initializing lifecycle service clients
[async_slam_toolbox_node-11] [INFO] [1731076914.408377336] [slam_toolbox]: Using solver plugin solver_plugins::CeresSolver
[async_slam_toolbox_node-11] [INFO] [1731076914.408563341] [slam_toolbox]: CeresSolver: Using SCHUR_JACOBI preconditioner.
[pointcloud_to_laserscan_node-2] [INFO] [1731076914.427011347] [pointcloud_to_laserscan]: Got a subscriber to laserscan, starting pointcloud subscriber
[lifecycle_manager-19] [INFO] [1731076914.459587737] [lifecycle_manager_navigation]: Starting managed nodes bringup...
[lifecycle_manager-19] [INFO] [1731076914.459638869] [lifecycle_manager_navigation]: Configuring controller_server
[controller_server-12] [INFO] [1731076914.460797000] [controller_server]: Configuring controller interface
[controller_server-12] [INFO] [1731076914.460947491] [controller_server]: getting goal checker plugins..
[controller_server-12] [INFO] [1731076914.461027935] [controller_server]: Controller frequency set to 3.0000Hz
[controller_server-12] [INFO] [1731076914.461063615] [local_costmap.local_costmap]: Configuring
[controller_server-12] [INFO] [1731076914.464688488] [local_costmap.local_costmap]: Using plugin "static_layer"
[controller_server-12] [INFO] [1731076914.471016445] [local_costmap.local_costmap]: Subscribing to the map topic (/map) with transient local durability
[controller_server-12] [INFO] [1731076914.472145038] [local_costmap.local_costmap]: Initialized plugin "static_layer"
[controller_server-12] [INFO] [1731076914.472182939] [local_costmap.local_costmap]: Using plugin "voxel_layer"
[controller_server-12] [INFO] [1731076914.473411876] [local_costmap.local_costmap]: Subscribed to Topics: scan
[controller_server-12] [INFO] [1731076914.480746975] [local_costmap.local_costmap]: Initialized plugin "voxel_layer"
[controller_server-12] [INFO] [1731076914.480788272] [local_costmap.local_costmap]: Using plugin "inflation_layer"
[controller_server-12] [INFO] [1731076914.481948222] [local_costmap.local_costmap]: Initialized plugin "inflation_layer"
[controller_server-12] [INFO] [1731076914.489277362] [controller_server]: Created progress_checker : progress_checker of type nav2_controller::SimpleProgressChecker
[controller_server-12] [INFO] [1731076914.490886301] [controller_server]: Created goal checker : general_goal_checker of type nav2_controller::SimpleGoalChecker
[controller_server-12] [INFO] [1731076914.492167836] [controller_server]: Controller Server has general_goal_checker  goal checkers available.
[controller_server-12] [INFO] [1731076914.495315917] [controller_server]: Created controller : FollowPath of type dwb_core::DWBLocalPlanner
[controller_server-12] [INFO] [1731076914.501060618] [controller_server]: Setting transform_tolerance to 0.200000
[controller_server-12] [INFO] [1731076914.514793641] [controller_server]: Using critic "RotateToGoal" (dwb_critics::RotateToGoalCritic)
[controller_server-12] [INFO] [1731076914.515474494] [controller_server]: Critic plugin initialized
[controller_server-12] [INFO] [1731076914.515632953] [controller_server]: Using critic "Oscillation" (dwb_critics::OscillationCritic)
[controller_server-12] [INFO] [1731076914.516149117] [controller_server]: Critic plugin initialized
[controller_server-12] [INFO] [1731076914.516288923] [controller_server]: Using critic "BaseObstacle" (dwb_critics::BaseObstacleCritic)
[controller_server-12] [INFO] [1731076914.516503948] [controller_server]: Critic plugin initialized
[controller_server-12] [INFO] [1731076914.516638323] [controller_server]: Using critic "GoalAlign" (dwb_critics::GoalAlignCritic)
[controller_server-12] [INFO] [1731076914.517076015] [controller_server]: Critic plugin initialized
[controller_server-12] [INFO] [1731076914.517219002] [controller_server]: Using critic "PathAlign" (dwb_critics::PathAlignCritic)
[controller_server-12] [INFO] [1731076914.517545379] [controller_server]: Critic plugin initialized
[controller_server-12] [INFO] [1731076914.517775214] [controller_server]: Using critic "PathDist" (dwb_critics::PathDistCritic)
[controller_server-12] [INFO] [1731076914.518018181] [controller_server]: Critic plugin initialized
[controller_server-12] [INFO] [1731076914.518110757] [controller_server]: Using critic "GoalDist" (dwb_critics::GoalDistCritic)
[controller_server-12] [INFO] [1731076914.518320755] [controller_server]: Critic plugin initialized
[controller_server-12] [INFO] [1731076914.518343118] [controller_server]: Controller Server has FollowPath  controllers available.
[lifecycle_manager-19] [INFO] [1731076914.523826126] [lifecycle_manager_navigation]: Configuring smoother_server
[smoother_server-13] [INFO] [1731076914.524709481] [smoother_server]: Configuring smoother server
[smoother_server-13] [INFO] [1731076914.529215350] [smoother_server]: Created smoother : simple_smoother of type nav2_smoother::SimpleSmoother
[smoother_server-13] [INFO] [1731076914.530182087] [smoother_server]: Smoother Server has simple_smoother  smoothers available.
[lifecycle_manager-19] [INFO] [1731076914.534665700] [lifecycle_manager_navigation]: Configuring planner_server
[planner_server-14] [INFO] [1731076914.535079899] [planner_server]: Configuring
[planner_server-14] [INFO] [1731076914.535127017] [global_costmap.global_costmap]: Configuring
[planner_server-14] [INFO] [1731076914.601037835] [global_costmap.global_costmap]: Using plugin "static_layer"
[planner_server-14] [INFO] [1731076914.607294215] [global_costmap.global_costmap]: Subscribing to the map topic (/map) with transient local durability
[planner_server-14] [INFO] [1731076914.608168671] [global_costmap.global_costmap]: Initialized plugin "static_layer"
[planner_server-14] [INFO] [1731076914.608216411] [global_costmap.global_costmap]: Using plugin "voxel_layer"
[planner_server-14] [INFO] [1731076914.609561498] [global_costmap.global_costmap]: Subscribed to Topics: scan
[rviz2-5] [INFO] [1731076914.647416540] [rviz2]: Stereo is NOT SUPPORTED
[rviz2-5] [INFO] [1731076914.647650951] [rviz2]: OpenGl version: 4.6 (GLSL 4.6)
[rviz2-5] [INFO] [1731076914.684991599] [rviz2]: Stereo is NOT SUPPORTED
[pointcloud_to_laserscan_node-2] [WARN] [1731076914.837151790] [pointcloud_to_laserscan]: New subscription discovered on topic '/scan', requesting incompatible QoS. No messages will be sent to it. Last incompatible policy: RELIABILITY_QOS_POLICY
[rviz2-5] [WARN] [1731076914.917979844] [rcl.logging_rosout]: Publisher already registered for provided node name. If this is due to multiple nodes with the same name then all logs for that logger name will go out over the existing publisher. As soon as any node with that name is destructed it will unregister the publisher, preventing any further logs for that name from being published on the rosout topic.
[rviz2-5] [WARN] [1731076914.931270383] [rcl.logging_rosout]: Publisher already registered for provided node name. If this is due to multiple nodes with the same name then all logs for that logger name will go out over the existing publisher. As soon as any node with that name is destructed it will unregister the publisher, preventing any further logs for that name from being published on the rosout topic.
[planner_server-14] [INFO] [1731076915.002088723] [global_costmap.global_costmap]: Initialized plugin "voxel_layer"
[planner_server-14] [INFO] [1731076915.002830768] [global_costmap.global_costmap]: Using plugin "inflation_layer"
[planner_server-14] [INFO] [1731076915.007832624] [global_costmap.global_costmap]: Initialized plugin "inflation_layer"
[planner_server-14] [INFO] [1731076915.013439826] [planner_server]: Created global planner plugin GridBased of type nav2_navfn_planner/NavfnPlanner
[planner_server-14] [INFO] [1731076915.013489064] [planner_server]: Configuring plugin GridBased of type NavfnPlanner
[joint_state_publisher_gui-9] [INFO] [1731076915.021922595] [joint_state_publisher_gui]: Waiting for robot_description to be published on the robot_description topic...
[joint_state_publisher_gui-9] [INFO] [1731076915.031210572] [joint_state_publisher_gui]: Centering
[planner_server-14] [INFO] [1731076915.092118687] [planner_server]: Planner Server has GridBased  planners available.
[lifecycle_manager-19] [INFO] [1731076915.101354542] [lifecycle_manager_navigation]: Configuring behavior_server
[behavior_server-15] [INFO] [1731076915.101625624] [behavior_server]: Configuring
[behavior_server-15] [INFO] [1731076915.105783966] [behavior_server]: Creating behavior plugin spin of type nav2_behaviors/Spin
[behavior_server-15] [INFO] [1731076915.106646384] [behavior_server]: Configuring spin
[behavior_server-15] [INFO] [1731076915.111273495] [behavior_server]: Creating behavior plugin backup of type nav2_behaviors/BackUp
[behavior_server-15] [INFO] [1731076915.111980885] [behavior_server]: Configuring backup
[behavior_server-15] [INFO] [1731076915.114520407] [behavior_server]: Creating behavior plugin drive_on_heading of type nav2_behaviors/DriveOnHeading
[behavior_server-15] [INFO] [1731076915.115341016] [behavior_server]: Configuring drive_on_heading
[behavior_server-15] [INFO] [1731076915.117750996] [behavior_server]: Creating behavior plugin assisted_teleop of type nav2_behaviors/AssistedTeleop
[behavior_server-15] [INFO] [1731076915.119365489] [behavior_server]: Configuring assisted_teleop
[behavior_server-15] [INFO] [1731076915.123258179] [behavior_server]: Creating behavior plugin wait of type nav2_behaviors/Wait
[behavior_server-15] [INFO] [1731076915.123923226] [behavior_server]: Configuring wait
[lifecycle_manager-19] [INFO] [1731076915.126866556] [lifecycle_manager_navigation]: Configuring bt_navigator
[bt_navigator-16] [INFO] [1731076915.127071680] [bt_navigator]: Configuring
[lifecycle_manager-19] [INFO] [1731076915.196356990] [lifecycle_manager_navigation]: Configuring waypoint_follower
[waypoint_follower-17] [INFO] [1731076915.196580136] [waypoint_follower]: Configuring
[waypoint_follower-17] [INFO] [1731076915.201432521] [waypoint_follower]: Created waypoint_task_executor : wait_at_waypoint of type nav2_waypoint_follower::WaitAtWaypoint
[lifecycle_manager-19] [INFO] [1731076915.202728487] [lifecycle_manager_navigation]: Configuring velocity_smoother
[velocity_smoother-18] [INFO] [1731076915.203442084] [velocity_smoother]: Configuring velocity smoother
[lifecycle_manager-19] [INFO] [1731076915.206875035] [lifecycle_manager_navigation]: Activating controller_server
[controller_server-12] [INFO] [1731076915.207120260] [controller_server]: Activating
[controller_server-12] [INFO] [1731076915.207167093] [local_costmap.local_costmap]: Activating
[controller_server-12] [INFO] [1731076915.207183552] [local_costmap.local_costmap]: Checking transform
[controller_server-12] [INFO] [1731076915.207301640] [local_costmap.local_costmap]: start
[joint_state_publisher_gui-9] [INFO] [1731076915.220498164] [joint_state_publisher_gui]: Centering
[rviz2-5] [ERROR] [1731076915.566706957] [rviz2]: The link is static or has unrealistic inertia, so the equivalent inertia box will not be shown.
[rviz2-5]
[rviz2-5] [ERROR] [1731076915.566862786] [rviz2]: The link is static or has unrealistic inertia, so the equivalent inertia box will not be shown.
[rviz2-5]
[go2_driver_node-3] [INFO] [1731076915.609083730] [go2_driver_node]: Received ip list: ['<IP_ADDRESS>']
[go2_driver_node-3] [INFO] [1731076915.609612264] [go2_driver_node]: Connection type is webrtc
[go2_driver_node-3] [INFO] [1731076915.610075918] [go2_driver_node]: Connection mode is single
[rviz2-5] [INFO] [1731076915.630834227] [rviz2]: Stereo is NOT SUPPORTED
[go2_driver_node-3] INFO:scripts.go2_camerainfo:Loading camera info from file: /home/uchiwuwu/ros2_ws/install/go2_robot_sdk/share/go2_robot_sdk/calibration/front_camera.yaml
[go2_driver_node-3] INFO:root:Trying to send SDP using a NEW method...
[controller_server-12] [INFO] [1731076916.257714397] [controller_server]: Creating bond (controller_server) to lifecycle manager.
[lifecycle_manager-19] [INFO] [1731076916.359847132] [lifecycle_manager_navigation]: Server controller_server connected with bond.
[lifecycle_manager-19] [INFO] [1731076916.359895579] [lifecycle_manager_navigation]: Activating smoother_server
[smoother_server-13] [INFO] [1731076916.360083279] [smoother_server]: Activating
[smoother_server-13] [INFO] [1731076916.360114977] [smoother_server]: Creating bond (smoother_server) to lifecycle manager.
[lifecycle_manager-19] [INFO] [1731076916.461791920] [lifecycle_manager_navigation]: Server smoother_server connected with bond.
[lifecycle_manager-19] [INFO] [1731076916.461849088] [lifecycle_manager_navigation]: Activating planner_server
[planner_server-14] [INFO] [1731076916.462080746] [planner_server]: Activating
[planner_server-14] [INFO] [1731076916.462116952] [global_costmap.global_costmap]: Activating
[planner_server-14] [INFO] [1731076916.462128406] [global_costmap.global_costmap]: Checking transform
[planner_server-14] [INFO] [1731076916.462212533] [global_costmap.global_costmap]: start
[lidar_to_pointcloud-4] /opt/ros/humble/local/lib/python3.10/dist-packages/rclpy/node.py:441: UserWarning: when declaring parameter named 'robot_ip_lst', declaring a parameter only providing its name is deprecated. You have to either:
[lidar_to_pointcloud-4] 	- Pass a name and a default value different to "PARAMETER NOT SET" (and optionally a descriptor).
[lidar_to_pointcloud-4] 	- Pass a name and a parameter type.
[lidar_to_pointcloud-4] 	- Pass a name and a descriptor with `dynamic_typing=True
[lidar_to_pointcloud-4]   warnings.warn(
[lidar_to_pointcloud-4] /opt/ros/humble/local/lib/python3.10/dist-packages/rclpy/node.py:441: UserWarning: when declaring parameter named 'map_name', declaring a parameter only providing its name is deprecated. You have to either:
[lidar_to_pointcloud-4] 	- Pass a name and a default value different to "PARAMETER NOT SET" (and optionally a descriptor).
[lidar_to_pointcloud-4] 	- Pass a name and a parameter type.
[lidar_to_pointcloud-4] 	- Pass a name and a descriptor with `dynamic_typing=True
[lidar_to_pointcloud-4]   warnings.warn(
[lidar_to_pointcloud-4] /opt/ros/humble/local/lib/python3.10/dist-packages/rclpy/node.py:441: UserWarning: when declaring parameter named 'map_save', declaring a parameter only providing its name is deprecated. You have to either:
[lidar_to_pointcloud-4] 	- Pass a name and a default value different to "PARAMETER NOT SET" (and optionally a descriptor).
[lidar_to_pointcloud-4] 	- Pass a name and a parameter type.
[lidar_to_pointcloud-4] 	- Pass a name and a descriptor with `dynamic_typing=True
[lidar_to_pointcloud-4]   warnings.warn(
[lidar_to_pointcloud-4] [INFO] [1731076916.990920883] [lidar_to_pointcloud]: Map will be saved
[lidar_to_pointcloud-4] [INFO] [1731076916.991239895] [lidar_to_pointcloud]: Map name is 3d_map.ply
[planner_server-14] [INFO] [1731076917.962586075] [planner_server]: Activating plugin GridBased of type NavfnPlanner
[planner_server-14] [INFO] [1731076917.963083619] [planner_server]: Creating bond (planner_server) to lifecycle manager.
[lifecycle_manager-19] [INFO] [1731076918.065106198] [lifecycle_manager_navigation]: Server planner_server connected with bond.
[lifecycle_manager-19] [INFO] [1731076918.065157341] [lifecycle_manager_navigation]: Activating behavior_server
[behavior_server-15] [INFO] [1731076918.065417037] [behavior_server]: Activating
[behavior_server-15] [INFO] [1731076918.065444627] [behavior_server]: Activating spin
[behavior_server-15] [INFO] [1731076918.065457063] [behavior_server]: Activating backup
[behavior_server-15] [INFO] [1731076918.065465377] [behavior_server]: Activating drive_on_heading
[behavior_server-15] [INFO] [1731076918.065474871] [behavior_server]: Activating assisted_teleop
[behavior_server-15] [INFO] [1731076918.065484604] [behavior_server]: Activating wait
[behavior_server-15] [INFO] [1731076918.065496893] [behavior_server]: Creating bond (behavior_server) to lifecycle manager.
[lifecycle_manager-19] [INFO] [1731076918.168148078] [lifecycle_manager_navigation]: Server behavior_server connected with bond.
[lifecycle_manager-19] [INFO] [1731076918.168197230] [lifecycle_manager_navigation]: Activating bt_navigator
[bt_navigator-16] [INFO] [1731076918.168406997] [bt_navigator]: Activating
[bt_navigator-16] [INFO] [1731076918.192791387] [bt_navigator]: Creating bond (bt_navigator) to lifecycle manager.
[lifecycle_manager-19] [INFO] [1731076918.295165847] [lifecycle_manager_navigation]: Server bt_navigator connected with bond.
[lifecycle_manager-19] [INFO] [1731076918.295208922] [lifecycle_manager_navigation]: Activating waypoint_follower
[waypoint_follower-17] [INFO] [1731076918.295445034] [waypoint_follower]: Activating
[waypoint_follower-17] [INFO] [1731076918.295476096] [waypoint_follower]: Creating bond (waypoint_follower) to lifecycle manager.
[lifecycle_manager-19] [INFO] [1731076918.397287181] [lifecycle_manager_navigation]: Server waypoint_follower connected with bond.
[lifecycle_manager-19] [INFO] [1731076918.397335633] [lifecycle_manager_navigation]: Activating velocity_smoother
[velocity_smoother-18] [INFO] [1731076918.397644359] [velocity_smoother]: Activating
[velocity_smoother-18] [INFO] [1731076918.397714559] [velocity_smoother]: Creating bond (velocity_smoother) to lifecycle manager.
[lifecycle_manager-19] [INFO] [1731076918.499855386] [lifecycle_manager_navigation]: Server velocity_smoother connected with bond.
[lifecycle_manager-19] [INFO] [1731076918.499901802] [lifecycle_manager_navigation]: Managed nodes are active
[lifecycle_manager-19] [INFO] [1731076918.499916378] [lifecycle_manager_navigation]: Creating bond timer...
[controller_server-12] [WARN] [1731076925.207578088] [local_costmap.local_costmap]: Can't update static costmap layer, no map received
[planner_server-14] [WARN] [1731076926.775827512] [global_costmap.global_costmap]: Can't update static costmap layer, no map received
[controller_server-12] [WARN] [1731076935.207575289] [local_costmap.local_costmap]: Can't update static costmap layer, no map received
[planner_server-14] [WARN] [1731076936.786239909] [global_costmap.global_costmap]: Can't update static costmap layer, no map received
[controller_server-12] [WARN] [1731076945.207514536] [local_costmap.local_costmap]: Can't update static costmap layer, no map received
[planner_server-14] [WARN] [1731076946.785546319] [global_costmap.global_costmap]: Can't update static costmap layer, no map received

I'm also experiencing this issue time to time. Refer to issue #87 for related questions. It might be helpful to handle the issue.
First, type "ros2 topic list" and validate topics. If the connection is good, topics are similar to issue #87 and image from front camera should appear. If topics and camera image are valid, it is usually caused by inappropriate dependencies. Please do properly install the dependencies.


[feature] Pytest Conversion: Application (detail, list, reset) [OSF-8018]

Purpose

Conversion of API tests to Pytest
Increase in performance
Changes

Pytest conversion of test_application_detail.py, test_application_list.py, test_application_reset.py
Grouping of tests within test_application_detail.py
Added assert_dict_contains_subset to api_tests/utils.py
Side effects

None known.
Ticket

https://openscience.atlassian.net/browse/OSF-8018
QA Considerations
None known.
Test Validation
Change: api_tests/applications/test_application_detail.py
Modification: assert res.status_code == 404
Modification Rational: Shows that the test is testing the right thing by verifying that it returns the right 4** error message
Expected Result: returned 409 not 404
Result: E   assert 409 == 404
Test(s) Broken:
test_update_application_incorrect_type(self)
Change: api_tests/applications/test_application_list.py
Modification: assert len(res.json['data']) == len(self.user_one_apps) + len(self.user_two_apps)
Modification Rational: Shows that the test is testing the right thing by making sure a user can't see more than their number of apps.
Expected Result: # != # + #
Result: E   assert 3 == (3 + 2)
Test(s) Broken:
test_user_one_should_see_only_their_applications
Change: api_tests/applications/test_application_reset.py
Modification: assert res.status_code == 404
Modification Rational: Shows that the test is testing the right thing by verifying that it returns the right 4** error message
Expected Result: returned 403 not 404
Result: E   assert 403 == 404
Test(s) Broken:
test_other_user_cannot_reset

Looks good! The test failure is unrelated to these changes.


Fix slides continuing during blackout

When triggering blackout the content would be hidden. Autoplay, however, would not be paused because the util variable was null. This happened because immediately after assigning to the correct util variable, a new one was defined using the var keyword. I don't know a lot about javascript, but, as I understand it,this somehow overwrote the original variable, as its value was null afterwards. This second variable was never used anywhere, so I believe it is safe to remove it. I don't understand why the util variable is necessary at all as substituting api.lib.util everywhere seems to work just fine and makes it clear what util refers to.

Thanks for the fix!


usb: USB device stack should track and check the state of control transfers

USB spec. Chapter "8.5.3" describes the  Control Transfers.
The USB stack does not track the state and does not check the correctness of the stages.
Although the real drawbacks of this are minor, it makes troubleshooting and
validation of the drivers more difficult.

Fixed in the new USB stack, use CONFIG_USB_DEVICE_STACK_NEXT to enable it.


Develop and Run SAP Fiori Application With SAP Business Application Studio

Tutorials: https://developers.sap.com/tutorials/abap-environment-deploy-cf-production.html
Step 6: Deploy your application
4.Go back to SAP Business Application Studio and open the terminal again. To add deploy config details, enter npx fiori add deploy-config.
Add following information...
Before adding following information, we need to choose target as ABAP.
This step should be added and screenshot should be updated.
Expected result:

Actual Result:

Labels :
Landscape Labels: trail1, trail2
SCPTest-fabap : Develop a Fiori App Using ABAP
Label: SCPTest-2102A
Priority label : 'Low'
Thanks and regards,
Farozan

Hi @FarozanFarman ,
thank you for your e-mail. We will address this issue as soon as possible.
Best regards,
Merve

Hi @MichaelCzcz ,
I created following pull request for this issue: #6552.
Can you merge?
Thank you.
Best regards,
Merve


Azure.Search.Documents tests slow in playback

BufferedSender takes > 2 min.

This issue is no longer valid. BufferedSender tests are running in < 6 seconds in playback mode.


cannot open settings

VSCode Version: 1.9.x
OS Version: macOS

Trying to open Settings now always results in this error:

Before that I was able to open settings, searched for "update" in user settings, then switched to workspace settings where the problem occurred first.

Duplicates #18557


Error calling ToString function

I found that not only calling this function, but even some of the basic BNM functions don't work, such as setting the value of the array

I'm not sure if there's enough information here to help you?
But are there any errors or warnings logged from BNM when you run it?
And have you added the hooking software and selected the correct Unity version in [GlobalSettings.hpp](https://github.com/ByNameModding/BNM-Android/blob/master/include/BNM/UserSettings/GlobalSettings.hpp)?

I don't think that's the problem.

have you added the hooking software in GlobalSettings.hpp?

without doubt

have you Initialized it?

has been initialised, and although the code is a bit abstract, there is no problem testing the Hook functionality so far!

Can you provide full crash log?

vivo-V2166A-Android-12_2024-10-25_212433.log
If source code is required
https://github.com/2079541547/TEFModLoader/blob/main/core/src/main/cpp/TEFModLoader/src/TEFModLoader.cpp

Is it because of the shaodwhook error, so can I get the instance manually?

I don't know exactly what is going wrong (not enough information), so try to do sth, like add more logs to see if all found, hooked correctly.

哥们有实力啊，解决了


Support ? operator

The question mark operator is not supported.

    Ok(())
}

generates the following C code.
core_result_Result_55 eurydice_tests_call_it(void)
{
  KRML_HOST_EPRINTF("KaRaMeL abort at %s:%d\n%s\n",
    __FILE__,
    __LINE__,
    "Eurydice error: Failure(\"TODO: TraitTypes core::result::{core::ops::try_trait::Try for core::result::Result<T, E>[TraitClause@0, TraitClause@1]}#26<T@0, T@1>[TraitClause@0, TraitClause@1]::Residual\")\n");
  KRML_HOST_EXIT(255U);
}

This boils down to support for associated types, which would require a little bit of feature work, to encode the associated types in trait parameters as type arguments to pre-monomorphized functions.

You should get this for free once we solve https://github.com/AeneasVerif/charon/issues/127, which is at the top of my priority queue.


Implement np.where in nopython mode

Hi, I am using Numba as much as I can,
Is it possible to implement np.where in nopython mode?
This would be great as I frequently need to find all the argmax indices of an array. e.g.
indmax = np.where((X == X.max())))[0]

Perhaps this could help:
https://github.com/numba/numba/issues/1359

We have implemented np.where (and np.nonzero) in the PR (#1432) that was just merged to master.  Updated dev packages for numba with this feature should be appearing in our anaconda.org "numba" channel in a few hours.


Add sFUEL Section

Add sFUEL Overview
Add it to onboarding
Links to Proof of Work
Update Faucet Links (Testnet)
Deep Dive into sFUEL for developers
Deep dive into philosphy of sFUEL Distribution
Invisible Distribution

Resolved in #108


Only set seen flag on read SMS and MMS

Hi @jberkel can you comment on this? Should I change anything to get it merged?

i am a bit worried this will annoy existing users, since this is a behavioral change, and also conflicts with the documentation / settings

And if I give it a New option, like syc read flags?

yes that would be right the way to do this. but on the other hand nobody has asked for the feature (as far  as i remember), so i'm not sure if it's worth adding. and there are already too many options, so i'm very hesitant to add even more.

I've successfully used it for a month now and I really like it, bekause I only get notifications for unread messages on my desktop that way. Will add the option later today and update the request.

I've update the pull request, can you have a look?

Just pushed the new version. Any comments?

getting there. but you still need migrate the user pref to the new one, otherwise user settings will get lost.

... and it would also be great if you could add a test for the new code (i think the code wasn't tested at all before, so might be a good chance to cover the basics)

I've tried to add a migration path, but it doesn't seem to work, do you have an idea, or an example somewhere how to do it?

on startup i would just explicitly convert it:

app starts
is mark_as_read key present ?
if yes, convert  to mark_as_read_types and delete key

Migration is working now. I would propose to have the testing code in a separate pull request, as there is none for it right now. Anything else to do before merging it?

Done, thanks for the comments!

would be great if you could some tests for code you added, shouldn't be too difficult.


Start with front camera

Dear all,
I try to search how to init Camera Kit or props for "front camera"
I want to start the camera with front camera first
Best regards,

Hi,
For a temporary solution, you can use this right after your screen mount (maybe with some delay):
const success = await this.camera.changeCamera();
A better solution will be added soon.

Dear @gran33
I couldn't be the temporary solution right now because we cannot change the camera to the side we want
For ex: the first time we open screen, after mount, we call "changeCamera" as you suggested, the camera turn to "front camera". OK, it right
However, the next time, we open screen again, after mount, the "changeCamera" will be call again and it turn the "remembered front camera" to the rear camera. We could not control how to open the front camera whenever we open camera screen

Store in your app state the camera shown, and if it's already front so don't perform the action.

I'd also like this as a proper solution. In the mean time I'll use the hack.

Hi,
For a temporary solution, you can use this right after your screen mount (maybe with some delay):
const success = await this.camera.changeCamera();
A better solution will be added soon.

How do I use this
const success = await this.camera.changeCamera(); and where. can anyone please help i am new in react native


Implementation of 'sro'-instruction

@M-ximus @kkorolev
Find 10 differences: https://godbolt.org/z/NNY2_w
Reporting to MS right now.

Reported: https://developercommunity.visualstudio.com/content/problem/833637/wrong-compilation-for-ones-right-shift.html


PWN-4393 New Home toolbar fix

Jira Ticket
https://p2pvalidator.atlassian.net/browse/PWN-4393
Description of Work
Fix home toolbar icons shadow and address width
Screenshots

Incorrect branch name


I2C bug fix.

I2C had bug.

test MBED_A19 did not work. It is because delay should be added.
If I2C writes same data, W7500 uses GPIO instead of I2C, but there is bug in stop function so we change I2c as GPIO.

We choose to change I2c as GPIO.


closeOnBlur={false} doesn't work

Steps

add closeOnBlur={false} to dropdown
blur dropdown by outside click or esc

Expected Result
popup will not be closed
Version
0.68.5
Testcase
try it out in your documentation: https://react.semantic-ui.com/modules/dropdown#dropdown-example-close-on-blur

Fixed with https://github.com/Semantic-Org/Semantic-UI-React/pull/1998

We'll check it soon, thank you so much for fast reaction!


Is it possible to ignore some filenames

For example I need to different css files 1) for all browsers 2) for IE
PIPELINE_CSS = {
    'all': {
        'source_filenames': (
            'blocks/*/*.css',
        ),
        'ignore_filenames': (
            'blocks/*/*.ie.css',
        ),
        'output_filename': '_all.css',
    },
    'all_ie': {
        'source_filenames': (
            'blocks/*/*.ie.css',
        ),
        'output_filename': '_all.ie.css',
    },
}

Is it possible to ignore "*.ie?.css" ?
I think 'ignore_filenames' or regexp matching should be good solution.

I created a pull request for this
https://github.com/cyberdelia/django-pipeline/pull/436


Launcher 2.0

The current iteration of the launcher has been in action for some time now, what do we like about it? What don't we like?
I figure we could take a moment to reflect on what its strengths are, along with its weaknesses. I've come across a few launchers since I first put this one together, and have a few ideas on what could be improved from a UX perspective.

There's too little information on-screen at once
There isn't any room for more information, like
Animations are distracting
It's QML, a separate beast from the rest of Avalon, both to maintain and to get PRs from others

On the upside.

It's uncomplicated and intuitive
It looks nice
It performs well

What could this critical, first line of defense that is the Launcher do to improve?

Sifting through issues, here's one I would like to unpack. :) I want our Launcher to be preferable to anything else, what is it about ftrack that the user prefers?

One of the things I'd like to support is information about the user, his tasks and history. E.g. Ben is logged in and sees tasks related to Ben, along with his last few launched applications - and possibly which files those applications were launched with, e.g. my_model_v035.ma. I'd also like to support images; such as of the user, of the project, or the asset and of the task.
We'd need a document in the DB to hold that kind of data, which could be ingested via a Python API but won't need a GUI, since it would normally come from e.g. CGWire/ftrack/Shotgun or the like.

what is it about ftrack that the user prefers?

When using a production tracker like Ftrack, the users starts off there reading comments etc.
The launcher could maybe facilitate all the data from the production tracker, but that seem like a lot of data syncing for little gain.

So far none of our current and potential clients are interested in launcher other than as backup option when ftrack is down. It's too much hassle for artist to click through it considering they always first need to find ftrack task for comments and overall context. In Kredenc for example it wasn't launched a single time in past 4 months.
Second thing is that we found that users prefer launching global actions (the ones in launcher visible without a project), from tray icon menu directly. it's quicker. We have a good version of tray, that we're happy to share and push to core if there is interested. Looks like this

That's just a really quick one from me. I think it could me made much more useful fairly easily. So I'll comment more in a bit.

The launcher could maybe facilitate all the data from the production tracker, but that seem like a lot of data syncing for little gain.

I was thinking about this and think you're right; the amount of data that would effectively need to be duplicated isn't a good way forwards.
So then it got me thinking that maybe the answer isn't to:

Duplicate the data
Use the duplicated, now internal, data in Launcher

But instead to:

Read from optionally implemented "hooks" in Launcher

A hook could be e.g. external.find_icon({"type": "icon", "project": "Spiderverse", "asset": "ab1002"}) which doesn't actually read from the Avalon DB, but rather calls on find_icon which may or may not be implemented in a config. A vanilla config could then, e.g. take this query and always return the same generic icon. A studio could implement a studio-specific, but still generic icon for all assets. And finally, a studio could implement the function to take into account their internal projects, which in turn may call on cgwire or ftrack or what have you.
So long as the function always returns the same type, perhaps given the type key, then it'd be entrely polymorphic; i.e. it's a duch if it quacks like a duck.
This way, we could support arbitrary external data, without duplicating anything.
One immediate consequence is that queries could take longer than normal queries to the Avalon DB, e.g. if they physically connect to an ftrack db somewhere. But for that we could quite easily implement a caching mechanism under the hood of such calls to remedy that, and/or make any calls to external sources asynchronous and take a callback for the result.

Think "hooks" sounds like a very interesting idea!
I guess they aren't just going to be for fetching but also pushing data back to the trackers?
For example updating a status or adding a comment is still needed in the production tracker, because coordinators aren't going to be using Avalon.
One issue I could foresee is accommodating the workflows of the production trackers. For example CGWire and Ftrack may not have the same idea how commenting works. One could work with a flat commenting, and the other could enable users to reply to comments. Think Slack, where you can both comment in the channel as reply or reply directly to a post.

I guess they aren't just going to be for fetching but also pushing data back to the trackers?

Exactly, they wouldn't need to as Avalon isn't the place for authoring such things. I think we can leverage that property to make the interface that much simpler.

One could work with a flat commenting, and the other could enable users to reply to comments.

True, each hook would need to translate the data to something that make sense for how things are drawn in Avalon.

Exactly, they wouldn't need to as Avalon isn't the place for authoring such things. I think we can leverage that property to make the interface that much simpler.

I was saying that Avalon would need to be able to push data back to the tracker.
For example comments. If we are wanting users to not spend time in Ftrack, we would need to facilitate all the needs of the user from the Ftrack interface, like replying to comments.

If we are wanting users to not spend time in Ftrack

No, that not what anyone wants. Avalon and ftrack serve complementary purposes. Also this issue isn't specifically about ftrack, but about making Avalon better, especially for those that don't use ftrack or want/need an alternative.
What I've got in mind is for production data - including but not limited to comments - to appear throughout Avalon, such as in the Library and Launcher, when relevant to what the user is doing.

In the context of the launcher, getting an icon for a shot can help guide the user towards making the right selection (e.g. finding that big yellow asset is easier than finding one called exactly supremeOverlord_SK15_lol5).
For a library, comments can help the user understand what the latest change of a particular version was, if comments are used to reflect those kinds of things.

Both of these are things a user shouldn't have to go someplace else for, they should happen in-context. Likewise, if they are already in ftrack, then it would make sense to also launch an application from there, and it's good we're able to facilitate both.
Lowering the amount of context switching is key here.

Some work has been done on trying to test an integration with allzpark as a launcher for Avalon. and for future reference I also wanted to link the gitter discussion about Avalon + Allzpark too.


Cannot find protocol declaration for 'G8TesseractDelegate'

I installed package with required steps such as installing pods and linking but still getting this error. I have no idea how to solve it.
This error occurs in RNTesseractOcr.xcodeproj/RNTesseractOcr.h/RNTesseractOcr
#import "RCTBridgeModule.h"
#import "RNTesseractOcr.h"
@interface RNTesseractOcr : NSObject <RCTBridgeModule, G8TesseractDelegate>
@end
any ideas how to solve it?

Please respect guidelines for posting issue: we do not provide support for 3rd party projects.
(this is not tesseract header files)

Sorry I think I posted it in wrong place.


Vue pagination not working

API Platform version(s) affected: 2.6.2
Description
The pagination in the generated Vue list components is not working.
The API pagination URLs returned as hydra:* are used as router links which does not make sense since router links point to components.
How to reproduce
Generate the components for an arbitary API resource, create enough entries for the pagination to show up or reduce the items_per_page in the api_platform.yaml.
The first page of the list loads just fine but clicking a pagination link switches from the regular frontend view to /api/<api-resource/?page=N.
Possible Solution
Instead the API URL must be passed via the mapped getPage() method to the getItems() action of the store to fetch the desired page and replace the mapped items.

have you found anything ? im facing the same error

my url is getting the ?page=2
but its not showing page2 in the list

Works fine here as described in Possible Solution. However, we don't use the generated client code anymore.
Instead we have a custom pagination component like this:
<template>
    <ul class="pagination">
        <li
            class="page-item"
            :class="{
                disabled: !view['hydra:previous'],
            }"
        >
            <button
                @click="$emit('previous', view['hydra:previous'])"
                :disabled="!view['hydra:previous']"
                type="button"
                class="btn-link page-link action-previous"
            >
                Previous
            </button>
        </li>

        <li
            class="page-item"
            :class="{
                disabled: !view['hydra:next'],
            }"
        >
            <button
                @click="$emit('next', view['hydra:next'])"
                :disabled="!view['hydra:next']"
                type="button"
                class="btn-link page-link action-next"
            >
                Next
            </button>
        </li>
    </ul>
</template>

<script>
export default {
    props: {
        view: {
            type: Object,
            default: () => {},
        },
    },

    emits: [
        'previous',
        'next',
    ],
};
</script>

This can be embedded anywhere:
<my-pagination
    v-if="view"
    :view="view"
    @previous="getPage"
    @next="getPage"
/>

Here view is based on the hydra:view returned from the API and exposed in the Vuex store module. And getPage is the Vuex store action to trigger fetching items. This already has a page argument by default which will be triggered with an URL like /api/resource?page=N and thus passed through.

Thanks !!! this worked


When I drop all files, and add one I have traceback and aider exits.

Traceback (most recent call last):
  File "C:\Users\Coder\AppData\Local\Programs\Python\Python310\lib\runpy.py", line 196, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "C:\Users\Coder\AppData\Local\Programs\Python\Python310\lib\runpy.py", line 86, in _run_code
    exec(code, run_globals)
  File "C:\Users\Coder\AppData\Local\Programs\Python\Python310\Scripts\aider.exe\__main__.py", line 7, in <module>
  File "C:\Users\Coder\AppData\Local\Programs\Python\Python310\lib\site-packages\aider\main.py", line 293, in main
    coder.run()
  File "C:\Users\Coder\AppData\Local\Programs\Python\Python310\lib\site-packages\aider\coders\base_coder.py", line 328, in run
    new_user_message = self.run_loop()
  File "C:\Users\Coder\AppData\Local\Programs\Python\Python310\lib\site-packages\aider\coders\base_coder.py", line 392, in run_loop
    return self.commands.run(inp)
  File "C:\Users\Coder\AppData\Local\Programs\Python\Python310\lib\site-packages\aider\commands.py", line 58, in run
    return self.do_run(matching_commands[0][1:], rest_inp)
  File "C:\Users\Coder\AppData\Local\Programs\Python\Python310\lib\site-packages\aider\commands.py", line 43, in do_run
    return cmd_method(args)
  File "C:\Users\Coder\AppData\Local\Programs\Python\Python310\lib\site-packages\aider\commands.py", line 254, in cmd_add
    self.coder.abs_fnames.add(abs_file_path)
AttributeError: 'list' object has no attribute 'add'

Good find, and thanks for reporting this issue. I just pushed a fix.
You'll need to install the latest from github to pick it up. Please let me know if you have any more problems.
pip install git+https://github.com/paul-gauthier/aider.git

It actually works!!!


implement doSelfUpdate() but working

Apparently the self-update package I was using relies on an old go-github version, which may not be compatible with the GitHub API anymore. Need to either search for a replacement, or chase down the specifics of what's wrong with it.

Implemented. Maybe I'll change the flow of update/setup/run later, but that's a relatively minor detail and not part of this issue :)


Elastic server is publicly accessible, without authentication

As part of our integration with API Umbrella, we are making calls directly to the API Umbrella Elastic analytics server. The calls we make do not use authentication, meaning we can access the full analytics data for the server in an insecure manner (similarly for anyone else with the proper knowledge).
How can we secure the API Umbrella Elastic analytics server?

Ah, I guess we've assumed API Umbrella is behind some other type of load balancer or firewall that would prevent access on non-HTTP/HTTPS ports, but that's probably not a good assumption to make. Thanks for bringing this to our attention. We'll look to get this fixed in the next release (although, it will probably be next week before we can get to it).
What we'll probably do is bind elasticsearch to localhost-only (which Elasticsearch has also made the default behavior in v2). If you want to make that change now, you can do so with the following additions to your /etc/api-umbrella/api-umbrella.yml:
elasticsearch:
  embedded_server_config:
    network:
      host: <IP_ADDRESS>

This will mean you'll have to tweak that setting if you need any other servers to access Elasticsearch directly. For a default API Umbrella installation, that would mean that the servers running the web-app component would need access somehow. So you could go back to binding to <IP_ADDRESS> as long as you have other network rules in place that would disallow public access to elasticsearch's port, but it does seem safer to make this configuration a bit more explicit.
If you're calling Elasticsearch directly in the apinf dashboard, though, I'm not quite sure if there's a simple alternative. I think you'd need some sort of server-side layer in-between to deal with access control, which is what the analytics APIs that are part of the web-app admin do. Those APIs ensure that the admin is authorized, has permission to the specific queries they're trying to perform, and then calls Elasticsearch internally (so isn't exposed publicly). Can you use those admin analytics APIs, or are you doing more custom things that aren't possible with those?

Ping @shaliko @frenchbread. Please read the above changes related to Elastic analytics, as it will probably affect our packaging and dashboard integration.

@GUI we can start using the API Umbrella API to fetch analytics data. Are there endpoint(s) where we can get custom aggregations, such as binning results by response time or status code?

Sorry it took so long for us to get this out in a packaged release, but this has finally landed in v0.14.0. Thanks again for the report!
This also affected our embedded Mongo instances, so if you can't upgrade immediately and you're on an unprotected network, you should probably check that setup.
Here's a documentation page we've added covering network binds: https://api-umbrella.readthedocs.io/en/latest/server/multi-server.html#bind-address

cc: @shaliko this might affect our packaging.

@brylie thank for notice, will do few tests.


command to toggle a script on and off

if its already enabled, then disable, otherwise rename and make it executable

added in ba60ed19a46be18b2877db1f366e658fa3b61ebb


bench:  allow explicit limiting of max-slot for analysis

This allows locli, and the workbench to limit the max-slot for the machine timeline analysis:
wb analyse --end-slot 37000 machine-timeline 2021-10-24-<IP_ADDRESS>-rc1-rts.k51-10ep-3000kU-750kD-64kbs-10tps-cli

bors r+


remove some double trait bounds

Signed-off-by: TennyZhuang<EMAIL_ADDRESS>Make the code clear.
I guess it's better to be a clippy rule, but at least we can make it cleaner manually.

I have no idea why the CI failed.

CI failure should be fixed in the latest master (https://github.com/rust-lang/futures-rs/pull/2644). Could you rebase?

rebased


Added php support

i added support for php files

Hi!
This package already supports PHP, as it's a C based language. Did you have any problem commenting PHP code?

Hi, i didn't see c entry in the languages.js file, so i add it, but if this works without this code you can ignore the PR


CI: Cilium Pre flight checks

Added  a new helper on cmd.Filter
Add two pre-checks on the ExpectCiliumReady.
Dump controller failure count in the json file.

This change is

test-me-please

test-me-please

test-me-please

test-me-please

test-me-please


Question: How to use extra input variables from data in the pinn that do not occur in the equations

The objective
I was wondering if and how I can use my input_variables from my input_tensor in the pinn. Or does it already do this?
class Heat2D(TimeDependentProblem, SpatialProblem):

    # Define these yourself
    LENGTH_X = 82
    LENGTH_Y = 70
    DURATION = 2284

    output_variables = ['u']
    spatial_domain = Span({'x': [0, LENGTH_X], 'y': [0, LENGTH_Y]})
    temporal_domain = Span({'t': [0, DURATION]})

    def heat_equation_2D(input_, output_):
        '''1'''
        # c is thermal diffusivity, variates for different materials so google
        c = (0.01/torch.pi) ** 0.5

        du = grad(output_, input_)
        ddu = grad(du, input_, components=['dudx','dudy'])
        return (
            du.extract(['dudt']) -
            (c**2)*(ddu.extract(['ddudxdx']) + ddu.extract(['ddudydy']))
        )

    def nil_dirichlet_x(input_, output_):
        '''2 and 3'''
        du = grad(output_, input_)
        u_expected_boundary = 0.0
        return du.extract(['dudx']) - u_expected_boundary

    def nil_dirichlet_yL(input_, output_):
        '''4'''
        du = grad(output_, input_)
        u_expected_boundary = 0.0
        return du.extract(['dudy']) - u_expected_boundary

    def nil_dirichlet_y0(input_, output_):
        '''5'''
        # TODO: make this conditionally on if door is open
        du = grad(output_, input_)
        u_expected_boundary = 0.0
        return du.extract(['dudy']) - u_expected_boundary

    def initial_condition(input_, output_):
        u_expected_initial = torch.sin(torch.pi*input_.extract(['x']))
        return output_.extract(['u']) - u_expected_initial

    conditions = {
        'boundx0': Condition(location=Span({'x': 0, 'y': [0, LENGTH_Y], 't': [0, DURATION]}), function=nil_dirichlet_x),
        'boundxL': Condition(location=Span({'x': LENGTH_X, 'y': [0, LENGTH_Y], 't': [0, DURATION]}), function=nil_dirichlet_x),
        'boundy0': Condition(location=Span({'x': [0, LENGTH_X], 'y': 0, 't': [0, DURATION]}), function=nil_dirichlet_y0),
        'boundyL': Condition(location=Span({'x': [0, LENGTH_X], 'y': LENGTH_Y, 't': [0, DURATION]}), function=nil_dirichlet_yL),
        'initial': Condition(location=Span({'x': [0, LENGTH_X], 'y': [0, LENGTH_Y], 't': 0}), function=initial_condition),
        'heat_eq': Condition(location=Span({'x': [0, LENGTH_X], 'y': [0, LENGTH_Y], 't': [0, DURATION]}), function=heat_equation_2D),
        'data': Condition(input_points=input_tensor , output_points=output_tensor),
        }

I was wondering all this since
heat_problem = Heat2D()
print(heat_problem.input_variables)

gives
['x', 'y', 't']

instead of
['Hot gas pipe', 'Liquid pipe', 'Suction pipe',
       'Energie meter (kwh / pulse) Watt', 'Door', 'Fridge', 'Water-1',
       'Water-2', 'Water-3', 'x', 'y', 't']

The input variables refer to the problem, and they are extracted directly from the problem spatial/temporal variables. Hence it is ok that you obtain [x,y,t]
The input tensors and output tensors are evaluated directly by pina in the loss. For each condition, PINA checks if it corresponds to a function or to output_points. In the latter case, we evaluate directly the residual between output points and model(input points).
Hope it helps ;)

We also plan to insert a simple tutorial about the possibility to pass input/ output points to PINA in version 0.1 (see #83). If you are interested in collaborating, let us know 💪🏼

Thank you! This clears things up.

Hi @Bovhasselt, have you re-open the issue by mistake? In that case, close it as it is complete. Otherwise, what is the problem?

Hi, sorry I was still running into some things but decided to give it another try on my own.
I strongly get the feeling that only the variables listed in the problem definition are evaluated by the model this way since
class EmptyProblem(TimeDependentProblem, SpatialProblem):
    output_variables = ['u']

    conditions = {'data': Condition(input_points=X_input_tensor , output_points=X_output_tensor),}
empty_problem = EmptyProblem()

model = FeedForward(
    layers=[30, 20, 10, 5],
    output_variables=list(X_output.columns),
    input_variables=list(X_input.columns),
    func=Softplus,
)

pinn_empty = PINN(
    empty_problem,
    model,
    lr=0.01,
    error_norm='mse',
    regularizer=0)

pinn_empty.train(1000,100)

results in
              sum          data
[epoch 00000] 2.245686e+02 2.245686e+02
              sum          data
[epoch 00001] 7.516103e+01 7.516103e+01
              sum          data
[epoch 00100] 2.235714e-01 2.235714e-01
              sum          data
[epoch 00200] 7.226005e-02 7.226005e-02
              sum          data
[epoch 00300] 9.989784e-02 9.989784e-02
              sum          data
[epoch 00400] 4.041366e-02 4.041366e-02
              sum          data
[epoch 00500] 2.071431e-02 2.071431e-02
              sum          data
[epoch 00600] 1.661560e-02 1.661560e-02
              sum          data
[epoch 00700] 6.244321e-02 6.244321e-02
              sum          data
[epoch 00800] 4.118864e-02 4.118864e-02
              sum          data
[epoch 00900] 1.691275e-02 1.691275e-02
[epoch 01000] 9.447230e-03 9.447230e-03
0.009447230026125908

but
class EmptyProblem(TimeDependentProblem, SpatialProblem):
    LENGTH_X = 82
    LENGTH_Y = 70
    DURATION = 2284

    output_variables = ['u']
    spatial_domain = Span({'x': [0, LENGTH_X], 'y': [0, LENGTH_Y]})
    temporal_domain = Span({'t': [0, DURATION]})

    conditions = {'data': Condition(input_points=X_input_tensor , output_points=X_output_tensor),}
empty_problem = EmptyProblem()

model = FeedForward(
    layers=[30, 20, 10, 5],
    output_variables=empty_problem.output_variables,
    input_variables=empty_problem.input_variables,
    func=Softplus,
)

pinn_empty = PINN(
    empty_problem,
    model,
    lr=0.01,
    error_norm='mse',
    regularizer=0)

pinn_empty.train(1000,100)

results in
              sum          data
[epoch 00000] 8.389169e+01 8.389169e+01
              sum          data
[epoch 00001] 1.952116e+01 1.952116e+01
              sum          data
[epoch 00100] 9.829848e+00 9.829848e+00
              sum          data
[epoch 00200] 7.163562e+00 7.163562e+00
              sum          data
[epoch 00300] 5.870559e+00 5.870559e+00
              sum          data
[epoch 00400] 5.345792e+00 5.345792e+00
              sum          data
[epoch 00500] 5.173698e+00 5.173698e+00
              sum          data
[epoch 00600] 5.122586e+00 5.122586e+00
              sum          data
[epoch 00700] 5.111149e+00 5.111149e+00
              sum          data
[epoch 00800] 5.109069e+00 5.109069e+00
              sum          data
[epoch 00900] 5.108763e+00 5.108763e+00
[epoch 01000] 5.108727e+00 5.108727e+00
5.108726501464844

The reason this is a problem for me is that in my 2D heat problem I do need to span points for optimising my equations and then simply entering    output_variables=list(X_output.columns),     input_variables=list(X_input.columns), does not work anymore.
Is there any way to get the model to train on all input_variables instead of just the ones listed in the problem?

👋🏻 @Bovhasselt Do you still need help? In case not, please close the issue. Let me know ;)

@dario-coscia Yes, I still haven't figured it out yet. Is there any way to get the model to train on all data points?

Hi @Bovhasselt sorry for the late reply, we have been busy working on the new beta version. It seems you are right, and indeed we have taken the issue in serious consideration. The bug was related with the sampling point mechanism.
In the beta version this will be solved. In https://github.com/mathLab/PINA/pull/104 I implemented the solution to the problem, here you can find a new PINA version which (is still under development but) works. I now tested the code and it correctly works for all the combinations of the Condition class. So if you clone at https://github.com/mathLab/PINA/pull/104 stage, you can solve your problem.
Notice that, since the beta version will be released shortly, we are not planning to make these changes in the current version of PINA due to code maintenance and compatibility.
Finally, something you could be interesting... In the new version we will enable pytorch lightning as backhand, meaning that you will be able to use advance deep learning techniques for training basically for free.
Hope this help 😄

Hi @Bovhasselt just checking if you managed or need extra help. Let us know 😄

👋🏻 @Bovhasselt do you need extra help still? I will close the issue, if more help is needed fee free to reopen it.


Add Kumho Electric SmartMesh Gateway PnP Model

Thank you for contributing to the IoT Plug and Play Models repository
:memo: Please review this checklist before submission

[ ] :eyes: The models submitted in this PR follow the DTDL Naming Guidelines for contributing to this repository.
[ ] 🕵I have validated the models locally using the dmr-client command line tool.
[ ] ❗ I understand once the PR is approved, the models are considered immutable: any edits will require to submit new files.
[ ] ✨ When creating a new top level dtmi:namespace, I have completed the PR Info Template below.

:zap: PR validation steps are described in the tools Wiki.
PR Info Template
When submitting models to the repository we ask that you provide as much of the following meta information around your models and related devices as possible. This info will be used to improve the IoT Plug and Play ecosystem.
👇: Please replace the markdown comment examples with your own values.
Company Info

Company name : Kumho Electric
Company website : https://www.khe.co.kr/en/

IoT Plug and Play Device Info

Product website : https://www.khe.co.kr/en/
OS & Arch : Azure Sphere
SDK used for model implementation : Azure SDK

Model Submission Goals

Device certification
Presence in the Certified Device catalog

Code Owners & Reserved Names
If no alias is specified then we assume the PR submitter is responsible for the namespace.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact<EMAIL_ADDRESS>with any additional questions or comments.

When will it be merged?


Azure function tools version 3.0 doesn't show java worker runtime

[Enter feedback here]
Hi ,
I was using Azure function tools 3.0.2245. func init command allows me to choose the worker runtime.
This version is not of Azure function tool, is not showing Java as a worker runtime. version 2.x was showing Java worker.
$ func version
3.0.2245
$ func init
Select a number for worker runtime:

dotnet
node
python
powershell

is Java no longer supported on Azure function tools?

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

ID: 5e85de04-2f8b-68ea-eeb9-dcc65f216332
Version Independent ID: db26953c-f234-3828-4c38-493ad410e25a
Content: Java developer reference for Azure Functions
Content Source: articles/azure-functions/functions-reference-java.md
Service: azure-functions
GitHub Login: @ggailey777
Microsoft Alias: glenga

@arbarik Thank you for your feedback! We will review and update as appropriate.

Hello @arbarik I don't recall the "java" option ever being on that list. You can use func init --java or func init --worker-runtime java to initialize an empty Function App but you'll still need to use Maven (or the alternatives discussed in this documentation) to scaffold an actual Java project with POM etc..
Since this channel is for driving improvements towards MS Docs and we haven't determined any changes upon reviewing your feedback, we will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.


Add FailNow() if config marshal fails

build-depends: 26624
build-depends: https://github.com/dci-labs/dallas-pipelines/pull/570
Similar to the line 159 we probably want to fail out gracefully if there's a failure to marshal the JSON correctly.

/dci-rerun


Minor offset fix for highlight in docs

Thanks! I think I probably fixed it at some point, it seems to be right: https://fastapi.tiangolo.com/tutorial/sql-databases/

Yes, looks like it.

Cool, thanks.


Same Metered Registry with multiple impl block.

Hey,
So in my rust project, there is struct called Shard and there multiple impl blocks exists that too in different files.
So how can I use metered-rs with same registry for this use case?
I tried putting this macro #[metered(registry = ShardMetricRegistry , registry_expr = self.metric_registry.metric, visibility = pub(self))]  on multiple impl blocks like this.
file : src/shard.rs
#[metered(registry = ShardMetricRegistry , registry_expr = self.metric_registry.metric, visibility = pub(self))]
impl Shard {
    #[measure(HitCount)]
    pub fn metered_test(&self) {
        println!("this function do nothing");
    }
}

file : src/shard_var.rs
pub struct Shard {
    pub metric_registry : ShardMetric
}

#[derive(Debug,Default,serde::Serialize)]
pub struct ShardMetric {
    pub metric : ShardMetricRegistry
}

#[metered(registry = ShardMetricRegistry , registry_expr = self.metric_registry.metric, visibility = pub(self))]
impl Shard {
    #[measure(HitCount)]
    #[measure(ErrorCount)]
    #[measure(ResponseTime)]
    pub fn put_data(&self, dara: Data) -> Result<(),()> {
       //doing nothing
      Some(())
    }
}

In this case I am getting this compilation error.
"no field metered_test on type shard::shard_var::ShardMetricRegistry
pub fn metered_test(&self) {
^^^^^^^^^^^^ unknown field"
Error is indicating that metered-rs didn't encounter second impl block from src/shard_var.rs file.
Does metered-rs capable of handling such case? if yes then plz suggest how.
Thanks.

Unfortunately, this is a limitation in Rust macros -- each syntactic item is independent, and we cannot know in advance of the existence of another impl block (or read it). Registries are generated at the same time as we process impl blocks.
Something you can do is bundle all your measured methods in the same impl block, and forward them to their implementation in different impl blocks

Cool. Thanks for such a quick response.

You're welcome.  For the record, it is also possible to generate one metric registry per impl block that you encapsulate in your own registry struct.


fix(example): add dns resolve for http_proxy

see #2103

is there any reason not to use to_socket_addr which comes with std library?
https://github.com/shirshak55/http-to-socks/blob/master/src/main.rs#L74

Is this pr going to be merged?

I'd rather not make some of these functions part of the public API. The example includes in its comments what it can and cannot do, and even with DNS resolution, it won't work over HTTPS. I think for that reason it's better to show it in a limited capacity, and imply that making a full proxy is more involved.


feat: scene emotes & animator support to sdk7

What does this PR change?
Fixes #1078
Fixes #1237
In order to solve the problem, all the animations of the scenes need to be converted to Animator leaving behind the legacy Animation system. This is directly related to: https://github.com/decentraland/asset-bundle-converter/pull/94
The animations that are meant to be played in the avatar (scene emotes) cannot be differentiated from any other animation in the scene in the conversion process, so we have to convert everything, since legacy animations cannot be played on the player's avatar.
A new system has been implemented to support Animator for the SDKAnimatorComponent, but we will keep supporting legacy animations in case there is any.
Also, a new system has been implemented to download the asset bundles of the scene emote required by triggerSceneEmote, so it can be later played by the existing systems.
How to test the changes?

Clean asset bundle cache
Follow issue steps
Go to goerli plaza and go through all scenes that has animations. For example: (76,-3), (74,-9), (72,-8)
Check that animations are working as expected
Check that the player emotes are working as expected

Our Code Review Standards
https://github.com/decentraland/unity-renderer/blob/master/docs/code-review-standards.md

All evidences and cases are being consolidated on the following document

Worth checking if this one closes #1266 and #1262 as well

QA checked
Check all videos as evidences here
Comments: the scenes with the cubes and the snow still needs some work. The user needs to clicks twice each cube to get the action triggered. This was said to be expected

The animations may not play instantly, as it is necessary to first download the animation file before playing it. This is why the first time there should be a delay, but once it is cached, it should be instant. This could be improved in the future by attempting to download the animation file when loading the scene, although we would need to figure out how to identify which animations require pre-downloading.


fix: Document delta dependency

Changelog: None
Signed-off-by: Alan<EMAIL_ADDRESS>

@mender-test-bot cherry-pick to:

3.4.x
3.3.x


Fix Border of Login Button

Fixes Issue
#4514
Changes proposed

Check List (Check all the applicable boxes)

[ ] My code follows the code style of this project.
[ ] My change requires changes to the documentation.
[ ] I have updated the documentation accordingly.
[ ] All new and existing tests passed.
[ ] This PR does not contain plagiarized content.
[ ] The title of my pull request is a short description of the requested changes.

Screenshots

Note to reviewers

Hi Could you please share a screenshot of the changes


fails with most recent game version

amon@c18:~/CelestiaSunrise$ CelestiaSunrise.py -s -d mlp_save_prime.dat <>
Loading save...
Done !
Parsing XML tree...
Something went wrong, error message:
duplicate attribute: line 1, column 633
Traceback (most recent call last):
File "/usr/local/lib/python3.4/dist-packages/xmltodict-0.9.0-py3.4.egg/xmltodict.py", line 246, in parse
parser.ParseFile(xml_input)
TypeError: argument must have 'read' attribute
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/lib/python3.4/dist-packages/CelestiaSunrise-1.0.0_rc4-py3.4.egg/EGG-INFO/scripts/CelestiaSunrise.py", line 64, in
File "/usr/local/lib/python3.4/dist-packages/CelestiaSunrise-1.0.0_rc4-py3.4.egg/src/shell/ponyshell.py", line 54, in init
self._xml_handle = XmlHandler(data.decode('utf-8', 'ignore'))
File "/usr/local/lib/python3.4/dist-packages/CelestiaSunrise-1.0.0_rc4-py3.4.egg/src/xmlhandler.py", line 217, in init
self.xmlobj = xmltodict.parse(clean_string(remove_parent(xml_data)))
File "/usr/local/lib/python3.4/dist-packages/xmltodict-0.9.0-py3.4.egg/xmltodict.py", line 248, in parse
parser.Parse(xml_input, True)
xml.parsers.expat.ExpatError: duplicate attribute: line 1, column 633
Exiting...

I am aware of it, which is present since the 2.2.0n update. The thing is the xml used in the savegame is misformatted (as reported by Expat), and python lacks permissive XML parsing library.
Anyway, I'm working on it, by creating python bindings for the XML parsing library used by the game itself (which is rapidxml), to prevent problems in the future. I'll update this issue when I'm done.

oh, i see.
sorry to have bothered you ^^;

No problem at all, at least I know someone is using what I've done, and that makes me working even faster :)

should be ok now.


Change artefact kind when we change edition format

Tangentially for: https://trello.com/c/RRJOTFQo/252-remove-business-support-code-that-still-exist-in-publisher
While exploring how best to remove and properly redirect business finance support editions from publisher I noticed that artefacts did not always have the a kind that matched up with the format of their latest_edition.  Since #428 we've allowed users to create a new edition of a published document with a new type, but we never made sure the artefact kind and edition format synced up.
It's unlikely to cause any real problems, but it felt strange to me so I thought I'd attempt to fix it.  There are notes on each commit, so worth reading them one-by-one.

Nice! 👌  I remember coming across this back on Custom team, and I can't remember why we didn't just fix it back then... 😐
Because you mentioned CompletedTransactions in your commits, I'm now wondering what happens with the slug of an artefact that gets changed from eg an Answer to a CompletedTransaction and if the '/done' gets appended to it... but that's probably not related to this particular PR.

@davidbasalla good point about converting things into CompletedTransactions. I don't really know how important the done/ prefix is on the slug, so I did some tests (on a local db replicated a couple of days ago on this branch):
Artefact.where(kind: 'completed_transaction').count
#=> 150
werent_always_done_pages = Artefact.where(kind: 'completed_transaction').select { |x| Edition.where(panopticon_id: x.id).map(&:kind_for_artefact).uniq != ['completed_transaction'] }
# => [#<Artefact _id: 5072de35a4254a58fa00003c, slug: "driving-transaction-finished",  ... >, #<Artefact _id: 5076dd61e5274a66de000002, slug: "transaction-finished", ... >]
werent_always_done_pages.map &:state
# => ["archived", "archived"]
werent_always_done_pages.map &:redirect_url
# => ["/done/driving-transaction-finished", "/done/transaction-finished"]
werent_always_done_pages.map &:valid?
# => [false, false]

Looks like we think the done/ prefix is important as the two examples we have of artefacts that were turned into done pages were ultimately archived and redirected to new done/ prefixed versions.  You can't change the slug of a document in publisher (can you?) so this makes sense.  I think in a different PR we probably want to remove done pages from the list of things you can convert things into.

@h-lame that sounds sensible to disable the conversion of formats into a CompletedTransaction (in a potential future PR)! 👍 Looks good to merge


Create KEYS

a sample KEYS file
part of releasing and signing releases
I have used the key in this file to do ASF releases before
Whenever anyone else does releases, they should add the public part of their key to this file
We will link to this file from our download page

FYI on this note, I am going to get my Apache key in the web of trust next week as well as adding it to Apache KEYS file so I can participate in releases

Hi,
Having it in the web of trust is a nice to have but not a requirement.
Justin

@mdedetrich @He-Pin Can this be merged? It's useful to have a file to link to in the release docs.


[#111760326] use custom s3 and semver resources with iam support

#111760326 Use custom resources for S3 & Semver using IAM profiles
What
We'd like to use custom resources for S3 and Semver because this will allow us to use IAM profiles for provisioning. We will use the images generated automatically in docker hub: https://hub.docker.com/r/governmentpaas/s3-resource/builds/ and https://hub.docker.com/r/governmentpaas/semver-resource/builds/, which where setup in https://github.com/alphagov/paas-s3-resource/pull/2 and https://github.com/alphagov/paas-semver-resource/pull/3
We will also stop using static AWS credentials in the pipelines for these resources.
Context
This PR should be reviewed in this context:

I want to add the new resources in concourse lite, using a shell provisioner to change the required configuration. Before that, we refactor how post-deployment scripts are executed in vagrant to make it easier to add/remove steps.
I want to configure the new resources in the "deployer" concourse, by changing the manifest to include the required configuration.
I want to remove the credentials used by this resources in all the pipelines, and not even pass it as variables. The only exception is the deploy-cloudfoundry pipeline, which needs the credentials to setup S3 access for the cloud-controller.

How to test this PR
Follow the steps described in the README.md deploying from scratch (at least, destroy and recreate vagrant, as concourse deployer will be redeployed).
Remember to specifying the current branch by exporting or passing the $BRANCH variable:
export BRANCH=$(git rev-parse --abbrev-ref HEAD)

It is not required to wait until the cloudfoundry deploy job finish, as the CF deployment has not being changed.
Who?
Anyone but @dcarley or @keymon

Rebased after #51


Edit schedule names not working as intended

Unintuitive design
Need to be reflected everywhere

Closing this issue since it is no longer relevant for the rewrite.


Add contribution guidelines

If this is going to be open to public contributors, we need a CONTRIBUTING.md.
Take a look at the examples listed here:
https://help.github.com/en/articles/setting-guidelines-for-repository-contributors#examples-of-contribution-guidelines

Added a skeleton doc for this in c4f687a.


Remove i18next from predictions.js

It would be ideal if predictions.js was once again purely the math behind all of the turnip calculations and not FoS code with libraries to import. When decoupled, the calculations can be used for other branching scripts when this project is abandoned - otherwise the calculations are tied to this library.

This wouldn't be too difficult to accomplish. We could hoist the pattern_description out of the pattern results in js/predictions.js and insteaad do that mapping in js/scripts.js.
That side effect to that is anyone who's using the this prediction code will no longer have a friendly name as part of the prediction result - they'll need to solve for that on their own.

It would be ideal if predictions.js was once again purely the math behind all of the turnip calculations and not FoS code with libraries to import.

@h2v4c I'm sorry, I don't know the acronym FoS, could you expand that for me?

I took it as the Urban Dictionary top result of "Full of Shit".

My apologies, FoS="Front of site"


Add a unified command handler to make use of both slash and prefix

…commands.

Add option to use either slash commands or prefix commands.
Replace std::format() for cross-compatibility.

Pain.


fix: dashboard improvement.

Description

fixes the issue where the script removes already downloaded information in case it has issues parsing it.
adds a button for the contribution guide at the top.

@KhudaDad414 logs are not happy with your change:
11:00:32 AM: ./dashboard.json
11:00:32 AM: Module parse failed: Unexpected token "}" (0x7D) in JSON at position 4346 while parsing near "...     }\n      ],\n    },\n    {\n      \"id\":..."

@derberg Oh my log, a sneaky comma 🤦

/rtm


Coverage.py misses lines in Python 3.11

Describe the bug
We recently found that coverage.py misses lines after Sanic test client calls in Python 3.11, and it's resolved after upgrading to Python 3.12.
To Reproduce
requirements.txt
coverage==7.6.10
pytest==8.3.4
sanic==24.6.0
sanic-testing==24.6.0

test_app.py
def test_app():
    from sanic import Sanic

    app = Sanic(__name__)

    app.config.TOUCHUP = False

    client = app.test_client
    _, response = client.get("/")
    assert response is not None
    assert response.status == 500

Run in Python 3.11.9
$ python3.11 -m coverage run -m pytest
python3.11 -m coverage run -m pytest
===================================== test session starts ======================================
platform linux -- Python 3.11.9, pytest-8.3.4, pluggy-1.5.0
rootdir: /workspaces/sanic-coverage-issue
plugins: anyio-4.7.0
collected 1 item

test_app.py .                                                                            [100%]

================================ 1 passed, 3 warnings in 0.38s =================================

$ python3.11 -m coverage report -m
Name          Stmts   Miss  Cover   Missing
-------------------------------------------
test_app.py       8      2    75%   10-11
-------------------------------------------
TOTAL             8      2    75%

Run in Python 3.12.1
$ python3.12 -m coverage run -m pytest
===================================== test session starts ======================================
platform linux -- Python 3.12.1, pytest-8.3.4, pluggy-1.5.0
rootdir: /workspaces/sanic-coverage-issue
plugins: anyio-4.7.0
collected 1 item

test_app.py .                                                                            [100%]
================================ 1 passed, 3 warnings in 0.84s =================================

$ python3.12 -m coverage report -m
Name          Stmts   Miss  Cover   Missing
-------------------------------------------
test_app.py       8      0   100%
-------------------------------------------
TOTAL             8      0   100%

Expected behavior
All lines are supposed to be covered even in Python 3.11
Additional context
I will try more python versions when I get some more time.

3.11.11 bad
3.12.0 good

This seems like a duplicate of #1595.  There's something about some kind of async operations that aren't properly traced in 3.11, but are in 3.12.


Set warning color to brown

The previous orange color was almost unreadable against the default gray
background, this is better.

+1

Darkened the color to match the OS styles a bit. Not as contrasty as suggested, but better than it was. Thanks for the nudge.