Fix for https://github.com/mattheworiordan/capybara-screenshot/issues/112

This is a fix for https://github.com/mattheworiordan/capybara-screenshot/issues/112 - this adds the option to tell the library to append a "random" value to the end of each screenshot.  This helps mitigate issues where time is frozen and therefore the timestamps are always the same.

Thanks @streetlogics

@streetlogics note I changed your code a little, see https://github.com/mattheworiordan/capybara-screenshot/commit/94fb138379abf943f8e418663758f155f143d9be

@mattheworiordan looks good, thanks!  :+1:


TB4 OAK-D camera launch failed

Please provide the following information:

OS: Ubuntu 22.04 LTS
ROS Distro: ROS2 humble

Expected behaviour
The camera should be launched successfully.
Actual behaviour
ubuntu@ubuntu:~$ ros2 launch turtlebot4_bringup oakd.launch.py
[INFO] [launch]: All log files can be found below /home/ubuntu/.ros/log/2023-06-12-13-27-22-903004-ubuntu-3030
[INFO] [launch]: Default logging verbosity is set to INFO
[ERROR] [launch_ros.actions.node]: Error while expanding or validating node name or namespace for 'package=rclcpp_components, executable=component_container, name=oakd_container, namespace=<launch.substitutions.launch_configuration.LaunchConfiguration object at 0xffffa56e9210>':
[ERROR] [launch]: Caught exception in launch (see debug for traceback): launch configuration 'namespace' does not exist
Other notes
I discovered another problem: the OAKD camera node initially works when the robot starts, but it stops running after a few seconds. I also examined the status of the turtlebot4 bring-up, which is currently running, and it appears that the camera node stops automatically. The log file can be found below.
● turtlebot4.service - "bringup turtlebot4"
Loaded: loaded (/lib/systemd/system/turtlebot4.service; enabled; vendor preset: enabled)
Active: active (running) since Mon 2023-06-12 13:08:19 UTC; 6min ago
Main PID: 2289 (turtlebot4-star)
Tasks: 136 (limit: 4416)
Memory: 252.3M
CPU: 4min 46.496s
CGroup: /system.slice/turtlebot4.service
├─2289 /bin/bash /usr/sbin/turtlebot4-start
├─2376 /usr/bin/python3 /opt/ros/humble/bin/ros2 launch /tmp/turtlebot4.launch.py
├─2401 /opt/ros/humble/lib/turtlebot4_node/turtlebot4_node --ros-args -r __ns:=/ --params-file /tmp/tmpbqcrbeeb --params-file /tmp/launch_params_ftplzws3
├─2403 /opt/ros/humble/lib/joy_linux/joy_linux_node --ros-args -r __node:=joy_linux_node -r __ns:=/ -r /diagnostics:=diagnostics
├─2405 /opt/ros/humble/lib/teleop_twist_joy/teleop_node --ros-args -r __node:=teleop_twist_joy_node -r __ns:=/ --params-file /tmp/tmpi498m703
├─2407 /opt/ros/humble/lib/rplidar_ros/rplidar_composition --ros-args -r __node:=rplidar_composition -r __ns:=/ --params-file /tmp/launch_params_ryfl3mpx
├─2409 /opt/ros/humble/lib/rclcpp_components/component_container --ros-args -r __node:=oakd_container -r __ns:=/
├─2420 /opt/ros/humble/lib/robot_state_publisher/robot_state_publisher --ros-args -r __node:=robot_state_publisher -r __ns:=/ --params-file /tmp/launch_params_h94xpfqr --params-file /tmp/la>
├─2430 /opt/ros/humble/lib/tf2_ros/static_transform_publisher --x 0.0 --y 0.1165 --z 0.0402 --roll -1.5707 --pitch 0.0 --yaw 0.0 --frame-id base_link --child-frame-id wheel_drop_left --ros->
├─2437 /opt/ros/humble/lib/tf2_ros/static_transform_publisher --x 0.0 --y -0.1165 --z 0.0402 --roll -1.5707 --pitch 0.0 --yaw 0.0 --frame-id base_link --child-frame-id wheel_drop_right --ro>
├─2446 /opt/ros/humble/lib/diagnostic_aggregator/aggregator_node --ros-args -r __ns:=/ --params-file /tmp/tmpjlsemtjz -r /diagnostics:=diagnostics -r /diagnostics_agg:=diagnostics_agg -r /d>
└─2454 /usr/bin/python3 /opt/ros/humble/lib/turtlebot4_diagnostics/diagnostics_updater --ros-args -r __ns:=/ -r /diagnostics:=diagnostics -r /diagnostics_agg:=diagnostics_agg -r /diagnostic>
Jun 12 13:08:31 ubuntu turtlebot4-start[2376]: [INFO] [launch_ros.actions.load_composable_nodes]: Loaded node '/oakd' in container '/oakd_container'
Jun 12 13:09:00 ubuntu turtlebot4-start[2376]: [turtlebot4_node-1] [INFO] [1686575340.014893676] [turtlebot4_node]: OAKD stopped
Jun 12 13:09:00 ubuntu turtlebot4-start[2376]: [turtlebot4_node-1] [INFO] [1686575340.015052137] [turtlebot4_node]: RPLIDAR stopped
Jun 12 13:09:01 ubuntu turtlebot4-start[2376]: [turtlebot4_node-1] [INFO] [1686575341.015368789] [turtlebot4_node]: oakd/stop_camera service available, sending request
Jun 12 13:09:01 ubuntu turtlebot4-start[2376]: [turtlebot4_node-1] [INFO] [1686575341.015925172] [turtlebot4_node]: stop_motor service available, sending request
Jun 12 13:09:01 ubuntu turtlebot4-start[2376]: [component_container-5] [INFO] [1686575341.016132503] [oakd]: Stopping camera.
Jun 12 13:09:01 ubuntu turtlebot4-start[2376]: [rplidar_composition-4] [INFO] [1686575341.262744502] [rplidar_composition]: Ingnoring stop_motor request because rplidar_node is in 'auto standby' mode
Jun 12 13:09:01 ubuntu turtlebot4-start[2376]: [turtlebot4_node-1] [INFO] [1686575341.263825712] [turtlebot4_node]: stop_motor service completed.
Jun 12 13:09:03 ubuntu turtlebot4-start[2376]: [turtlebot4_node-1] [INFO] [1686575343.113110689] [turtlebot4_node]: oakd/stop_camera service got results: Success
Jun 12 13:09:03 ubuntu turtlebot4-start[2376]: [turtlebot4_node-1] [INFO] [1686575343.113240558] [turtlebot4_node]:

Apologies for the misunderstanding. It turns out that I made a mistake by connecting the camera's USB port to the USB 2.0 port on the Raspberry Pi, which caused the issue. However, after switching the cable to a USB 3.0 port, everything is now functioning properly.

Hi Hillary,
I would like to express my sincere appreciation for your response.
1.Regarding my first question, I am still curious about the location within the launch file where the namespace is passed. Could you please provide a clearer explanation of where exactly the namespace is defined and passed in? Thank you for your assistance.
2.It appears that you were right about my lack of knowledge regarding the robot's power saver mode when it is docked. I have another question regarding the config code you shared earlier. It seems that both the camera and lidar should be stopped. Should the lidar be mechanically stopped from spinning?
However, I have noticed that the lidar continues rotating even when the robot is in power saver mode. I'm wondering if there is a coding solution that can be implemented to make the lidar stop rotating.
Also I posted the full journalctl logs here for your information.
ubuntu@ubuntu:~$ sudo journalctl -u turtlebot4.service -r
Jun 16 16:03:05 ubuntu turtlebot4-start[961]: [turtlebot4_node-1] [INFO] [1686931385.413754663] [turtlebot4_node]: stop_motor service completed.
Jun 16 16:03:05 ubuntu turtlebot4-start[961]: [rplidar_composition-4] [INFO] [1686931385.412726237] [rplidar_composition]: Ingnoring stop_motor request because rplidar_node is in 'auto standby' mode
Jun 16 16:03:05 ubuntu turtlebot4-start[961]: [turtlebot4_node-1] [INFO] [1686931385.245456700] [turtlebot4_node]:
Jun 16 16:03:05 ubuntu turtlebot4-start[961]: [turtlebot4_node-1] [INFO] [1686931385.245332200] [turtlebot4_node]: oakd/stop_camera service got results: Success
Jun 16 16:03:05 ubuntu turtlebot4-start[961]: [turtlebot4_node-1] [INFO] [1686931385.219758608] [turtlebot4_node]: stop_motor service available, sending request
Jun 16 16:03:05 ubuntu turtlebot4-start[961]: [component_container-5] [INFO] [1686931385.219693682] [oakd]: Stopping camera.

Jun 14 11:56:02 ubuntu turtlebot4-start[4767]: [component_container-5] [INFO] [1686743762.242107267] [oakd]: Starting camera.
Jun 14 11:56:02 ubuntu turtlebot4-start[4767]: [turtlebot4_node-1] [INFO] [1686743762.234822515] [turtlebot4_node]:
Jun 14 11:56:02 ubuntu turtlebot4-start[4767]: [turtlebot4_node-1] [INFO] [1686743762.234654081] [turtlebot4_node]: oakd/start_camera service got results: Success
Jun 14 11:56:02 ubuntu turtlebot4-start[4767]: [component_container-5] [INFO] [1686743762.234058396] [oakd]: Camera ready!
Jun 14 11:56:02 ubuntu turtlebot4-start[4767]: [component_container-5] [INFO] [1686743762.084769702] [oakd]: Finished setting up pipeline.

Jun 14 11:56:00 ubuntu turtlebot4-start[4767]: [turtlebot4_node-1] [INFO] [1686743760.326122592] [turtlebot4_node]: start_motor service completed.
Jun 14 11:56:00 ubuntu turtlebot4-start[4767]: [rplidar_composition-4] [INFO] [1686743760.324502269] [rplidar_composition]: Ingnoring start_motor request because rplidar_node is in 'auto standby' mode
Jun 14 11:56:00 ubuntu turtlebot4-start[4767]: [turtlebot4_node-1] [INFO] [1686743760.143081619] [turtlebot4_node]: start_motor service available, sending request
Jun 14 11:56:00 ubuntu turtlebot4-start[4767]: [component_container-5] [INFO] [1686743760.143206769] [oakd]: No ip/mxid specified, connecting to the next available device.
Jun 14 11:56:00 ubuntu turtlebot4-start[4767]: [component_container-5] [INFO] [1686743760.142900910] [oakd]: Starting camera.
Jun 14 11:56:00 ubuntu turtlebot4-start[4767]: [turtlebot4_node-1] [INFO] [1686743760.141990203] [turtlebot4_node]: oakd/start_camera service available, sending request
Jun 14 11:55:59 ubuntu turtlebot4-start[4767]: [turtlebot4_node-1] [INFO] [1686743759.142104628] [turtlebot4_node]: RPLIDAR started
Jun 14 11:55:59 ubuntu turtlebot4-start[4767]: [turtlebot4_node-1] [INFO] [1686743759.141769518] [turtlebot4_node]: OAKD started
Jun 14 11:51:09 ubuntu turtlebot4-start[4767]: [component_container-5] [INFO] [1686743469.559575810] [oakd]: Camera ready!
Jun 14 11:51:09 ubuntu turtlebot4-start[4767]: [component_container-5] [INFO] [1686743469.400358222] [oakd]: Finished setting up pipeline.

Jun 14 11:51:07 ubuntu turtlebot4-start[4767]: [component_container-5] [INFO] [1686743467.372438709] [oakd]: No ip/mxid specified, connecting to the next available device.
Jun 14 11:51:07 ubuntu turtlebot4-start[4767]: [component_container-5] [WARN] [1686743467.268772517] [rcl.logging_rosout]: Publisher already registered for provided node name. If this is due to multiple>
Jun 14 11:51:07 ubuntu turtlebot4-start[4767]: [component_container-5] [INFO] [1686743467.265845211] [oakd_container]: Instantiate class: rclcpp_components::NodeFactoryTemplate<depthai_ros_driver::Camer>
Jun 14 11:51:07 ubuntu turtlebot4-start[4767]: [component_container-5] [INFO] [1686743467.265694566] [oakd_container]: Found class: rclcpp_components::NodeFactoryTemplate<depthai_ros_driver::Camera>
Jun 14 11:50:11 ubuntu turtlebot4-start[4767]: [turtlebot4_node-1] [INFO] [1686743411.420708224] [turtlebot4_node]: stop_motor service completed.
Jun 14 11:50:11 ubuntu turtlebot4-start[4767]: [rplidar_composition-4] [INFO] [1686743411.419537266] [rplidar_composition]: Ingnoring stop_motor request because rplidar_node is in 'auto standby' mode
Jun 14 11:50:11 ubuntu turtlebot4-start[4767]: [turtlebot4_node-1] [INFO] [1686743411.250742571] [turtlebot4_node]:
Jun 14 11:50:11 ubuntu turtlebot4-start[4767]: [turtlebot4_node-1] [INFO] [1686743411.250618546] [turtlebot4_node]: oakd/stop_camera service got results: Success
Jun 14 11:50:11 ubuntu turtlebot4-start[4767]: [component_container-5] [INFO] [1686743411.222688574] [oakd]: Stopping camera.
Jun 14 11:50:11 ubuntu turtlebot4-start[4767]: [turtlebot4_node-1] [INFO] [1686743411.221374415] [turtlebot4_node]: stop_motor service available, sending request
Jun 14 11:50:11 ubuntu turtlebot4-start[4767]: [turtlebot4_node-1] [INFO] [1686743411.220450563] [turtlebot4_node]: oakd/stop_camera service available, sending request
Jun 14 11:50:10 ubuntu turtlebot4-start[4767]: [turtlebot4_node-1] [INFO] [1686743410.220704511] [turtlebot4_node]: RPLIDAR stopped
Jun 14 11:50:10 ubuntu turtlebot4-start[4767]: [turtlebot4_node-1] [INFO] [1686743410.220367904] [turtlebot4_node]: OAKD stopped
Jun 14 11:49:31 ubuntu turtlebot4-start[4767]: [aggregator_node-9] [INFO] [1686743371.228140022] [AnalyzerGroup]: Group 'Turtlebot4' has a match with my analyzer '/Turtlebot4/Create3'.


Include date and time in graph hover detail.

This is the same solution as applied to PromDash in
https://github.com/prometheus/promdash/pull/72.
Fixes https://github.com/prometheus/prometheus/issues/1569

Screenshot:

@grobie


API Management: added tag for package 2018-06-preview

Automation for azure-sdk-for-go

Automation for azure-sdk-for-js

Automation for azure-sdk-for-ruby

Automation for azure-sdk-for-python

Automation for azure-sdk-for-java

Can one of the admins verify this patch?


can u help me.??

i am new wanna try this out

Hi Taran,
Let us know what you want to know and we will try to help you out.

I just posted the issues #2 . Please help me thanks!


Split the Prombench project

Split the prombench project to solve high and low priority issues.
@krasi-georgiev
Signed-off-by: nikita-mk<EMAIL_ADDRESS>

LGTM


the script for processing the video

Can you share the script for processing the video to get the frame as dataset

Of course, we have uploaded the corresponding script (chaizhen_gt.py, chaizhen_blur.py）.

By the way, the result of my current inference enhancement is a separate frame. Are you using a separate script to evaluate it?


Switch from Shiba to Random Dog API

Description of Your Pull Request
While the doggo/Shiba random pictures were great, there was a bit of diversity desired from the dog command. This switches to the dog.ceo API to add more variety to the dog command.
Changes Proposed and or Files Changed
Update the request URL to use the dog.ceo API, more specifically this endpoint. This endpoint returns an object with a status property and a message property. The message property is the URL for the image.
Label Your Pull Request

[x] This PR modifies existing code to enhance the bot
[ ] This PR fixes a bug within the bot
[ ] This PR removes/renames methods or properties
[ ] This PR adds methods, features, commands or properties

Snekfetch is discontinued so I'd advise using superagent or node-fetch instead.

Discontinued !== Broken, just like RethinkDB not being updated doesn't mean it can't be used. It'll still work but just won't have any future updates.


Update image urls to github source

Submission Checklist
Required

[x] The pull request title clearly contains the name of the sheet I am editing.
[x] The pull request title clearly states the type of change I am submitting (New Sheet/New Feature/Bugfix/etc.).
[x] The pull request makes changes to files in only one sub-folder.
[x] The pull request does not contain changes to any json files in the translations folder (translation.json is permitted)

New Sheet Details

The name of this game is: <   >  (i.e. Dungeons & Dragons 5th Edition, The Dresden Files RPG)

The publisher of this game is: <   > (i.e. Wizards of the Coast, Evil Hat)

The name of this game system/family is: <   > (i.e. Dungeons & Dragons, FATE)

[ ] I have followed the Character Sheets Standards when building this sheet.

[ ] This sheet has been made on behalf of, or by, the game's publisher.
[ ] This game is not a traditionally published game, but a copy of the game rules can be purchased/downloaded/found at: <   >
[ ] This sheet is for an unofficial fan game, modification to an existing game, or a homebrew system.

Changes / Description

Updated image sources to reference github instead of personal roll20 image library.

Character Sheet Info Roll20 Internal Use only.

@Kurohyou Can you make sure you're labeling these PRs with the sheet name in future, please? Thanks!


how to reproduce meep simulations from the examples?

file meep-sim-norm-res20.dat seems empty, how can we check the MPB and meep compatibility?

I was able to reproduce this issue on a system without parallel meep.  If the parallel argument is set to True, it will attempt to run with mpirun.  However, it will crash silently if you are just using serial meep.
If you'd like to run with parallel meep, you can create a fresh conda env with the corresponding package:
conda create -n pmp -c conda-forge pymeep=*=mpi_mpich_*
or install into another existing environment:
conda install -c condo-forge pymeep=*=mpi_mpich_*
Otherwise, just setting the parallel argument to False should let it run.  I also changed the documentation (abcf2ce) so the example uses regular meep by default.

I was able to reproduce this issue on a system without parallel meep.  If the parallel argument is set to True, it will attempt to run with mpirun.  However, it will crash silently if you are just using serial meep.
If you'd like to run with parallel meep, you can create a fresh conda env with the corresponding package:
conda create -n pmp -c conda-forge pymeep=*=mpi_mpich_*
or install into another existing environment:
conda install -c condo-forge pymeep=*=mpi_mpich_*
Otherwise, just setting the parallel argument to False should let it run.  I also changed the documentation (abcf2ce) so the example uses regular meep by default.

I was able to reproduce this issue on a system without parallel meep.  If the parallel argument is set to True, it will attempt to run with mpirun.  However, it will crash silently if you are just using serial meep.
If you'd like to run with parallel meep, you can create a fresh conda env with the corresponding package:
conda create -n pmp -c conda-forge pymeep=*=mpi_mpich_*
or install into another existing environment:
conda install -c condo-forge pymeep=*=mpi_mpich_*
Otherwise, just setting the parallel argument to False should let it run.  I also changed the documentation (abcf2ce) so the example uses regular meep by default.

I was able to reproduce this issue on a system without parallel meep.  If the parallel argument is set to True, it will attempt to run with mpirun.  However, it will crash silently if you are just using serial meep.
If you'd like to run with parallel meep, you can create a fresh conda env with the corresponding package:
conda create -n pmp -c conda-forge pymeep=*=mpi_mpich_*
or install into another existing environment:
conda install -c condo-forge pymeep=*=mpi_mpich_*
Otherwise, just setting the parallel argument to False should let it run.  I also changed the documentation (abcf2ce) so the example uses regular meep by default.


Fixes map crash

Fixes error with safeAreaInsets, other code included will be merged in another PR but wont hurt this file.
#trivial

Fails

:no_entry_sign:

No CHANGELOG added.

:no_entry_sign:

[danger-plugin-jest] Could not read test results. Danger cannot pass or fail the build.

  Generated by :no_entry_sign: dangerJS

This should be fixed already by https://github.com/artsy/emission/pull/1443 , right?

Yeah, I think this can be closed


Data checks: attach list of feature name(s) to message

This will make it easy to programmatically identify which feature or features have a particular error or warning.

Slight expansion: to enable other programmatic formatting & internationalization, it would be nice if EvalML returned the un-formatted information in addition to the message that it returns right now. Something like:
{
  "message": "Warning: too many null values present in column 'foobar'",
  "code": "TOO_MANY_NULLS",
  "detail": {
    "level": "warning",
    "columns": ["foobar"]
  }
}

This would make it possible to perform language independent formatting on the results, by tying the code back to internationalization strings. And having metadata available in the detail allows that information to be optionally formatted back into the messages that are presented in a structured fashion.

@BoopBoopBeepBoop thanks. I like that proposal.
Would you expect "code" to be an enum, or just a string defined somewhere inside the data check?
One tweak I may suggest is to keep the structure flat:
{
  "message": "Warning: too many null values present in column 'foobar'",
  "code": "TOO_MANY_NULLS",
  "level": "warning",
  "columns": ["foobar"]
}

Here we're talking in terms of JSON, but setting that aside I think each of these fields should be attached to the DataCheckWarning/DataCheckError object.

That's fair - I had added those elements there as in my head detail was "essentially a map". However, those aren't great examples, because they're probably present for all checks ...
Would there be any situations where our messages should include additional metadata that is essentially present on a "per-message" basis? Examples I've seen on this before would be calling out specific values as examples, formatting dynamic lower/upper bounds in messages, or similar. That is usually where you benefit from having a detail (or pick a different name) map

Would you expect "code" to be an enum, or just a string defined somewhere inside the data check?

I would just expect it to be stable - where it lives is 🤷

Would you expect "code" to be an enum, or just a string defined somewhere inside the data check?

I would just expect it to be stable - where it lives is 🤷

If it's all the same I think I'd prefer an enum. We're currently defining our own strings to determine which checks to run as part of the job, and it would be nice to have an enum consistent to EvalML to leverage there in stead of creating our own.
Alongside this and maybe toward what @BoopBoopBeepBoop was mentioning with the detail, it might be helpful to know which type of error was thrown. For example, in the ID column check, EvalML does a check on whether the column name has "id" in it or if the values are N% unique. We may want to filter out the former or represent them differently, so this level of granularity may be useful, either through more granular enums or in something similar to a detail structure described above.

Just discussed with @dsherry @freddyaboulton: I had put up https://github.com/alteryx/evalml/pull/1444 to update our data checks API to return a dictionary instead of a list of warnings and errors. With this issue in mind, I'll update my PR to return a DataCheckResults where errors and warnings are attributes, as well as add a to_json method for the class which will return the JSON formatted messages as @BoopBoopBeepBoop has suggested here, with minimal information--for now, just the message and level.
This issue will remain open to track adding more fields (such as the "code") to the JSON output, and other fields that PS may need/want.

Thanks @angela97lin !
So here's the latest proposal:

Update DataCheck.validate and DataChecks.validate to both return the following format:

{'errors': [...], 'warnings': [...]}

where each entry in the above is of the format
{
  "message": "Warning: too many null values present in column 'foobar'",
  "code": "TOO_MANY_NULLS",
  "level": "warning",
  "columns": ["foobar"]
}

Define a DataCheckMessageCode enum for populating the code field above.

Any objections / comments before we build this? @tyler3991 @Cmancuso @BoopBoopBeepBoop @angela97lin @freddyaboulton
(@angela97lin @freddyaboulton I started typing out a version of this proposal with a DataCheckResults class, and then decided we should simply return the JSON-ified dict from above, rather than defining another class. Functionally equivalent, but not using the class is simpler. All the results class would be doing is holding the same info, not adding other functionality to it. LMK if you think that's a bad idea.)

Talked to @angela97lin about this RE PR #1444. The above plan is unchanged, except she may choose to keep the DataCheckMessage classes around internally for convenience / to make it harder for people to define invalid message entries. But validate will return a JSON-able dict of dicts as defined above.
(@angela97lin if that doesn't match what we just discussed please correct me!)

Tweaking this with @angela97lin . Latest:
{
  "message": "Warning: too many null values present in column 'foobar'",
  "code": "TOO_MANY_NULLS",
  "level": "warning",
  "details": {
    "columns": ["foobar"]
  }
}

where the "details" key can hold any info the data check wants to return. And it'll be omitted if there's nothing to be included.
We need to update the following data checks to include the column(s) which failed the check: highly null, ID, and target leakage. Bonus if we also update the other data checks :)
This is basically what @BoopBoopBeepBoop proposed! ✨ @Cmancuso FYI


Load driver configuration from file

Description
Add a Config struct to NJointBlmcRobotDriver that contains all
configurable parameters.  Actual driver implementations should provide a
method get_default_config which returns the default configuration.
A method load_config is provided which gets the default configuration
from the driver as well as path to a config file provided by the user.
Loads the config from the file and uses the default values where no
value is given in the file.
Add a print function for easy debugging.
Set C++ standard to 14 as otherwise aggregate initialization is not
possible for a struct that has default values (this is supported by
default GCC on Ubuntu 16.04, so should be no problem).
Add default config files for all current robots in blmc_robots/config.
In all the Python demos, use rospack to automatically find the default
config files from the blmc_robots package.
Some refactoring:

Use a generic, templated create_backend function to avoid code
duplication.

How I Tested
By running the demos without actual robots and printing the loaded configuration.
I cannot test on the real robots right now because they are in use at the moment but I will do this before merging.
Do not merge before
~https://github.com/open-dynamic-robot-initiative/robot_interfaces/pull/14~

@MaximilienNaveau This PR changes blmc_robots to use C++14 and CMake >= 3.1.  Would this cause any issues on your side?  Both is available on Ubuntu 16.04 but I did not check for earlier versions.

@mwuethri Default values are removed so all comments are addressed now.

It would be nice to not use too advanced C++ version so people do have to reinstall gcc.
For CMAKE or C++ we use the default Ubuntu one. We support Ubuntu 16.04 yet.
So the code using CMAKE/C++ must at least compatible with the ubuntu 16.04 version of these.


Improving integration tests with SAML2 artifact binding test cases

Is your suggestion related to an experience ? Please describe.
Currently for product-is there are no integration tests available in order to cover the SAML2 artifact binding scenarios. Because of that some issues can be occurred when updating third party classes and releasing them to live. Such case is occurred in [1]
[1] https://github.com/wso2/product-is/issues/13026

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!


Missing PLATFORM_SPECIFIC_HAL_LIB

Jacobs-Air:BLE_HeartRate jacobrosenthal$ rm -rf yotta*
Jacobs-Air:BLE_HeartRate jacobrosenthal$ yt target nordic-nrf51822-16k-gcc
info: get versions for nordic-nrf51822-16k-gcc
info: download<EMAIL_ADDRESS>from the public module registry
info: get versions for mbed-gcc
info: download<EMAIL_ADDRESS>from the public module registry
Jacobs-Air:BLE_HeartRate jacobrosenthal$ yt install
info: get versions for ble
info: download<EMAIL_ADDRESS>from the public module registry
info: get versions for ble-nrf51822
info: download<EMAIL_ADDRESS>from the public module registry
info: get versions for mbed-drivers
info: download<EMAIL_ADDRESS>from the public module registry
info: get versions for mbed-hal
info: download<EMAIL_ADDRESS>from the public module registry
info: get versions for cmsis-core
info: download<EMAIL_ADDRESS>from the public module registry
info: get versions for ualloc
info: download<EMAIL_ADDRESS>from the public module registry
info: get versions for minar
info: download<EMAIL_ADDRESS>from the public module registry
info: get versions for core-util
info: download<EMAIL_ADDRESS>from the public module registry
info: get versions for compiler-polyfill
info: download<EMAIL_ADDRESS>from the public module registry
info: get versions for mbed-hal-nordic
info: download<EMAIL_ADDRESS>from the public module registry
info: get versions for mbed-hal-nrf51822-mcu
info: download<EMAIL_ADDRESS>from the public module registry
info: get versions for cmsis-core-nordic
^[[Ainfo: download<EMAIL_ADDRESS>from the public module registry
info: get versions for cmsis-core-nrf51822
info: download<EMAIL_ADDRESS>from the public module registry
info: get versions for dlmalloc
info: download<EMAIL_ADDRESS>from the public module registry
info: get versions for minar-platform
info: download<EMAIL_ADDRESS>from the public module registry
info: get versions for minar-platform-mbed
info: download<EMAIL_ADDRESS>from the public module registry
Jacobs-Air:BLE_HeartRate jacobrosenthal$ yt build
info: generate for target: nordic-nrf51822-16k-gcc 0.1.2 at /Users/jacobrosenthal/Downloads/ble-examples/BLE_HeartRate/yotta_targets/nordic-nrf51822-16k-gcc
GCC version is: 4.8.4
suppressing warnings from ble-nrf51822
CMake Error at /Users/jacobrosenthal/Downloads/ble-examples/BLE_HeartRate/yotta_modules/mbed-hal-nrf51822-mcu/CMakeLists.txt:94 (message):
  Missing PLATFORM_SPECIFIC_HAL_LIB

-- Configuring incomplete, errors occurred!
See also "/Users/jacobrosenthal/Downloads/ble-examples/BLE_HeartRate/build/nordic-nrf51822-16k-gcc/CMakeFiles/CMakeOutput.log".
error: command ['cmake', '-D', 'CMAKE_BUILD_TYPE=RelWithDebInfo', '-G', 'Ninja', '.'] failed
Jacobs-Air:BLE_HeartRate jacobrosenthal$

Hi, can you move this issue to the mbed-hal-nrf51822-mcu module: https://github.com/ARMmbed/mbed-hal-nrf51822-mcu
The error you are getting, https://github.com/ARMmbed/mbed-hal-nrf51822-mcu/blob/master/CMakeLists.txt#L91 because the target (nordic-nrf51822-16k-gcc) should be considered as generic, which is currently not published, plus the target might not set the correct target like macro.

ARM Internal Ref: IOTSFW-1248

Hi @jacobrosenthal, thank you for your post. This is a possible explanation of what is happening:
The targets nordic-nrf51822-16k-gcc, nordic-nrf51822-16k-armcc, nordic-nrf51822-32k-gcc and nordic-nrf51822-32k-armcc are the "family" targets, which means that they contain common information for all the nrf51-based end targets (i.e. nrf51dk-gcc, nrf51dk-armcc, mkit-gcc, mkit-armcc, bbc-microbit-gcc and bbc-microbit-armcc). However the family targets are not meant to be used directly to build applications because they lack target specific information such as target specific pin names. Furthermore, other macro definitions made by other modules pulled in by end targets are needed. For instance, if I attempt the same sequence of commands you did I get the following dependencies by running yt ls:
ble-eddystonebeaconexperimental 0.0.1
┗─ ble 2.0.3
  ┣─ ble-nrf51822 2.0.3 yotta_modules/ble-nrf51822
  ┗─ mbed-drivers 0.11.2 yotta_modules/mbed-drivers
    ┣─ mbed-hal 1.1.0 yotta_modules/mbed-hal
    ┃ ┗─ mbed-hal-nordic 2.0.0 yotta_modules/mbed-hal-nordic
    ┃   ┗─ mbed-hal-nrf51822-mcu 2.0.3 yotta_modules/mbed-hal-nrf51822-mcu
    ┣─ cmsis-core 1.0.2 yotta_modules/cmsis-core
    ┃ ┗─ cmsis-core-nordic 1.0.1 yotta_modules/cmsis-core-nordic
    ┃   ┗─ cmsis-core-nrf51822 1.1.0 yotta_modules/cmsis-core-nrf51822
    ┣─ ualloc 1.0.2 yotta_modules/ualloc
    ┃ ┗─ dlmalloc 1.0.0 yotta_modules/dlmalloc
    ┣─ minar 1.0.1 yotta_modules/minar
    ┃ ┗─ minar-platform 1.0.0 yotta_modules/minar-platform
    ┃   ┗─ minar-platform-mbed 1.0.0 yotta_modules/minar-platform-mbed
    ┣─ core-util 1.0.1 yotta_modules/core-util
    ┗─ compiler-polyfill 1.1.1 yotta_modules/compiler-polyfill

But if I use an end target such as mkit-gcc then I get the following dependencies:
ble-eddystonebeaconexperimental 0.0.1
┗─ ble 2.0.3
  ┣─ ble-nrf51822 2.0.3 yotta_modules/ble-nrf51822
  ┗─ mbed-drivers 0.11.2 yotta_modules/mbed-drivers
    ┣─ mbed-hal 1.1.0 yotta_modules/mbed-hal
    ┃ ┗─ mbed-hal-nordic 2.0.0 yotta_modules/mbed-hal-nordic
    ┃   ┗─ mbed-hal-nrf51822-mcu 2.0.3 yotta_modules/mbed-hal-nrf51822-mcu
    ┃     ┗─ mbed-hal-mkit 1.0.2 yotta_modules/mbed-hal-mkit
    ┣─ cmsis-core 1.0.2 yotta_modules/cmsis-core
    ┃ ┗─ cmsis-core-nordic 1.0.1 yotta_modules/cmsis-core-nordic
    ┃   ┗─ cmsis-core-nrf51822 1.1.0 yotta_modules/cmsis-core-nrf51822
    ┣─ ualloc 1.0.2 yotta_modules/ualloc
    ┃ ┗─ dlmalloc 1.0.0 yotta_modules/dlmalloc
    ┣─ minar 1.0.1 yotta_modules/minar
    ┃ ┗─ minar-platform 1.0.0 yotta_modules/minar-platform
    ┃   ┗─ minar-platform-mbed 1.0.0 yotta_modules/minar-platform-mbed
    ┣─ core-util 1.0.1 yotta_modules/core-util
    ┗─ compiler-polyfill 1.1.1 yotta_modules/compiler-polyfill

The important thing to note here is that the module mbed-hal-mkit is not included when you using nordic-nrf51822-16k-gcc, hence we start missing a few things there. I hope that clarifies a little the problem. Perhaps if you could give me a bit more information of what you are trying to achieve I can have a closer look.

I have a custom target that inherits from nordic-nrf51822-16k-gcc which started erroring, so I just grabbed the one I was inheriting from to 'prove' it was an upstream problem.
Oddly enough this error went away over night. I assume there was some dependency mismatch or something that was cleared up in todays updates.


NO-JIRA: Update OCP max supported version for HO

Updated the max supported version to 4.19
/hold until branch cut

/area hypershift-operator

/close in favor of https://github.com/openshift/hypershift/pull/5146

/close


cart rule for free delivery applying on all cart items instead of condition based items

Bug report
Issue Description
cart rule for free delivery applying on all cart items instead of condition based items
Bagisto version

[X] master branch
[ ] 1.3.1
[ ] 1.3.0
[ ] 1.2.0

Steps to reproduce

create cart rule for free shipping based on product condition
add multiple item in cart, one should be match with condition and other shouldn't
go to checkout and select shipping

Expected result
While selecting Flat Rate shipping amount should be deducted only for one item
Actual result
While selecting Flat Rate, both product shipping gets $0

waiting for the solution for this issue.

any progress on this task?


Version change from 5.0.4 to 5.0.5

Changes

[X] Changed package version to 5.0.5.

Pending release references

Fix recursion in canonicalSignatureType() (#54)

Regards.

Codecov Report

Merging #55 (ea0700e) into master (d692288) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #55   +/-   ##
=======================================
  Coverage   91.97%   91.97%
=======================================
  Files         239      239
  Lines        4749     4749
  Branches      728      728
=======================================
  Hits         4368     4368
  Misses        233      233
  Partials      148      148

Continue to review full report at Codecov.

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


Target Framework

If there's no specific reason, I suggest we bump this down to .net standard 2.0/2.1 so it's more widely usable. This would make it usable in both Xamarin and MAUI.
Otherwise, we should target multiple frameworks.

If there's no specific reason, I suggest we bump this down to .net standard 2.0/2.1 so it's more widely usable. This would make it usable in both Xamarin and MAUI.
Otherwise, we should target multiple frameworks.

It seems that the recent improvements have used new methods which arent available in netstandard, such as Convert.FromHex and DecryptCbc/EncryptCbc

How about net7?

Sure, but do you mind if I set up multi-target (netstandard2.0, net6.0, net7.0) for the lib? It makes sense if you want to use some newer features, but it would be nice to support the minimum as well.

netstandard to open it as wide as possible
net6 for LTS
net7 for STS

Sure, let's do that
On Thu, Feb 16, 2023, 10:29 PM Kori Francis @.***>
wrote:

Sure, but do you mind if I set up multi-target (netstandard2.0, net6.0,
net7.0) for the lib? It makes sense if you want to use some newer features,
but it would be nice to support the minimum as well.

netstandard to open it as wide as possible
net6 for LTS
net7 for STS

—
Reply to this email directly, view it on GitHub
https://github.com/Kukks/NNostr/issues/12#issuecomment-1433737970, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAN357VUFZY3BLKM52PNKV3WX2L3TANCNFSM6AAAAAAU2RE3AA
.
You are receiving this because you commented.Message ID:
@.***>


destroy command show no error when port 9000 is used

Which version of kubefirst are you using?
v2.1.1
Which cloud provider?
k3d (local)
Which installation type?
CLI
Which distributed Git provider?
None specific
What is the issue?
When running kubefirst k3d destroy (I assume it will be the same issue with other cloud providers), if the port 9000 is already used, the destroy command won't work, but the CLI doesn't display anything except the usual "here's how you can check the logs for that command" output.
You need to check the logs to see that an error happened.
023-06-14T15:33 INF pkg/helpers.go:78 > Using config file: /Users/fharper/.kubefirst
2023-06-14T15:33 FTL cmd/k3d/destroy.go:41 > port 9000 is in use - this port is required to tear down your kubefirst environment - please close any existing port forwards before continuing

A new user could think that the command ran successfully, not knowing that we usually display information on the process, and confirm it was successful or show error if not.
Code of Conduct

[X] I agree to follow this project's Code of Conduct

That's weird though, I just got it again, and nothing was returned with sudo lsof -i tcp:9000 🤯


JenkinsQueueJobV2 - added handling of code 302 to JenkinsQueueJobV2 task

Task name: JenkinsQueueJobV2
Description: reworked changes from https://github.com/microsoft/azure-pipelines-tasks/pull/16058 - fixed tests
Documentation changes required: Y
Added unit tests: added tests (302 code returned - considerCode302AsSuccess is on/off, simple successful scenario for task)
Attached related issue: N
Checklist:

[x] Task version was bumped - please check instruction how to do it
[x] Checked that applied changes work as expected - made sanity check with simple jenkins job run

/azp run

/azp run

/azp run

Is this still being worked on? Seeing similar issues to the original poster here


implement Clone for RwLockReadGuard

Currently RwLock::read_recursive() can be used to achieve the same effect, but clone is easier to use and doesn't require a reference to the underlying lock.

I've added this in lock_api v0.1.2, which parking_lot uses.

One thing I'm not sure about: Is this technically a breaking change because guard.clone() used to clone the target and now clones the guard?

You're right, it was indeed a breaking change. I added a test and yanked the version with clone.

I think for now the best workaround is a static RwLockReadGuard::clone(guard:&Self) method, which has the nice property that it shouldn't break if it's later turned into an instance method.
But I'm still in favour of implementing Clone, following the precedent set by other smart-pointers like Arc, the next time you introduce other breaking changes.


Feature Request: Allow cookies and logins to be saved

Please add an option per app to save cookies and password logins. I want to use WebAppss for many forums and do not want to have to login all the time. Also for YouTube I perfer to have autoplay disabled and would like it if the browser will save it and not clear it when I exit the webapp.

Duplicate of #98


CLI: pwsh -Command - and pwsh -File - unexpectedly exhibit pseudo-interactive behavior, lack support for argument passing

Related: #9497
While pwsh -Command - and pwsh -File - both accept command input from the pipeline / from stdin:

they exhibit undesirable pseudo-interactive behavior:

they execute each line one by one, in separate pipelines.

additionally, -File - prints the prompt string and each input line before the output

they require pipelines that are spread across multiple lines  for readability to be terminated with two newlines (see below) - as would be necessary interactively, if PSReadLine weren't loaded.

they do not support combining - input with  passing arguments:

While that limitation is documented for -Command - (-File - is undocumented altogether), there's no good reason for this limitation, and it limits the usefulness of the construct.

While you could (but in my mind shouldn't) argue that -Command - should be limited to providing a self-contained source-code snippet that doesn't expect arguments, at the least -File - should support passing arguments by placing them after the - - after all, you want to be able to pass arguments to a script - whether that script is specified as a a file or as a script's content via stdin.

Thus, the following command, which spreads pipeline "hi" |  % { "$_ there" }  across two lines -  does not work:
@'
"in"
"hi" |
  % { "$_ there" }
"out"
'@ | powershell -noprofile -command -

The above yields only in, because the end of the multi-line command is never detected, causing it to be quietly ignored.
As evidence that this happens in the real world, see this Stack Overflow question, whose accepted answer provides more detail.
Inserting an empty line after the multi-line command fixes the problem:
@'
"in"
"hi" |
  % { "$_ there" }

"out"
'@ | powershell -noprofile -command -

The above now yields in, hi there and out - that is, the multi-line pipeline was correctly submitted due to the extra newline, as was the single-line statement afterwards.

Summary:

Both File - and -Command - should be fixed; and, on Unix /dev/stdin should be the same as passing -.

If -File - worked properly, there'd really be no need for -Command -.

Update: Except perhaps for emulating an interactive REPL via stdin - see https://github.com/PowerShell/PowerShell/issues/15331#issuecomment-830652350

-File - should optionally also accepted arguments.

At first look I'd expect that "-Command -" accept only one line command but how input multi-line one? And it is not clear that is semantic of "-File script.ps1 -"
Also I'd expect that we read console input if there is not explicit redirection.

At first look I'd expect that -Command - accept only one line command but how input multi-line one?

As argued in https://github.com/PowerShell/PowerShell/issues/9494#issuecomment-487621948, there's really no point in supporting -Command - altogether, if -File - worked properly.
Given that we cannot remove it: Just like you can already pass a multi-line argument to -Command, the entirety of stdin input should be executed as a snippet of source code.
(Line-by-line interactive execution doesn't really make sense - just start a PowerShell session normally to do that.)

it is not clear that is semantic of -File script.ps1 -

As stated in the linked comment, the - is not special at all in this case: since it follows a -File argument - script.ps1 - it is just a (positional) argument to pass to script.ps1; - is only special in lieu of a script-file argument.

Given that we cannot remove it: Just like you can already pass a multi-line argument to -Command, the entirety of stdin input should be executed as a snippet of source code.

We have API Powershell.AddCommand() and Powershell.AddScript() - I believe "-Command" behavior must fit first and "-File" - second.

It is the other way around:
.AddScript() is the one that behaves like -Command - you can pass it an arbitrary snippet of PowerShell code - the method is poorly named, .AddScriptBlock() would have made more sense.
.AddCommand() is for adding a command name or path, with the need to specify arguments separately; as such it is akin to -File.
Aside from that, there's no requirement of one-to-one mapping to SDK methods here.

Aside from that, there's no requirement of one-to-one mapping to SDK methods here.

My comment was about expected behavior. Both methods is often used in our tests and I'd expect such behavior in CLI too.

As shown, the names of the SDK methods not only do not align with the CLI parameters, but suggest the opposite mapping.
It is the CLI parameters that are sensibly named, and their fundamental semantics must not and cannot change (-File is self-describing (the fact that the argument must be a script file is implied), and -Command / -c aligns with the long-established -c command in POSIX-like shells (and is akin to /c in cmd.exe).
What should change, however, is how they deal with stdin input, as (now) suggested in the OP and argued in https://github.com/PowerShell/PowerShell/issues/9494#issuecomment-487648892

P.S., @iSazonov: You could open a separate issue suggesting more sensible alias names for the SDK methods (obviously, the old names cannot be removed); especially .AddScript() keeps causing confusion.

@mklement0 I think this is a dead proposal (add aliases) because it is a public API.
-File - is not documented so we could change its behavior as we need.

-File - is not documented so we could change its behavior as we need.

That's a good point.
We can then deprecate -Command - (and leave it as is) to support the following idioms, all based on -File, in conjunction with fixing #9497:
# Execute *code* piped from stdin.
... | pwsh   # same as: ... | pwsh -File -

# Execute *code* piped from stdin *with arguments*
# (`File -` is then required for disambiguation)
... | pwsh -File - args...

# Provide *input data* vis stdin - to a script file
... | pwsh -File someScript.ps1 [args...]

# Provide *input data* vis stdin - to a string containing commands
... | pwsh -Command $snippetOfPsCode

The unfortunate thing - which we cannot change - is that -Command doesn't accept arguments to pass to $snippetOfPsCode - it simply considers the remaining arguments to be part of the command string.

I think this is a dead proposal (add aliases) because it is a public API.

I don't think it's a pressing issue, and the downside is that it bloats the SDK, but why couldn't we add new, more descriptive method names that effectively call their less descriptively named predecessors? Of course, you'd then need to know what version of the SDK you're targeting.

I'd expect that AddScriptBlock() accept a parameter of ScriptBlock type, AddScript() - string parameter.

AddScript() adds a script block that just happens to be constructed from a string argument.
It's better to name methods for _what they do-, not the - somewhat incidental, possibly varying by overload - type of their arguments.

Just to add another voice here, we've just stumbled on this behaviour as part of a generic "monitoring solution". The plan was to feed generic scripts through to powershell as a script interpreter; we don't really have a workaround for this at the moment short of requiring that all scripts fed in are terminated with two blank lines (which seems to work but is definitely suboptimal).

So since 2017 if you write a script like this
# dbg.ps1
Write-Output "before try"
try {
    Write-Output "inside try"
} finally {
    Write-Output "inside finally"
}

without the two blank lines at the end and then run it with
Get-Content .\dbg.ps1 | powershell -command -

You won't see any logs from inside of the try or finally?

If you are here, and you didn't spend an hour debugging this, you are the luckiest person on the planet

This issue has not had any activity in 6 months, if there is no further activity in 7 days, the issue will be closed automatically.

Nice joke. It is still relevant

This issue has not had any activity in 6 months, if there is no further activity in 7 days, the issue will be closed automatically.

Activity in this case refers only to comments on the issue. If the issue is closed and you are the author, you can re-open the issue using the button below. Please add more information to be considered during retriage. If you are not the author but the issue is impacting you after it has been closed, please submit a new issue with updated details and a link to this issue and the original.

Bruh


Hebrew Translation

Checklist

[X] I am able to reproduce the bug with the latest version.
[X] I made sure that there are no existing issues - open or closed - which I could contribute my information to.
[X] I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
[X] This issue contains only one bug, that only occurs in Squawker

Affected version
3.8.0
Steps to reproduce the bug

Go to 'a Hebrew written post'
Press on 'the translation symbol'

Expected behavior
No response
Actual behavior
"language iw is not supported from host translate.fedilab.app"
Screenshots/Screen recordings

Logs
No response
Affected Android/Custom ROM version
Android 14/One UI 6.0
Affected device model
Samsung S22 Ultra
Additional information
No response

The error says:
"language iw is not supported from..."
I googled to know what is the language code iw.
It's the old standard for the language code of Hebrew.
The official current standard is the language code he (since 1989).
So Twitter/X (or @kann_news) uses the old standard for the language code of Hebrew, but the translation site translate.fedilab.app do not recognize that old language code for Hebrew, hence the error.
Squawker will simply replace iw by he before sending the text to be translated by the translation site.

Version v3.8.1 should fix it.


Parity with gl-matrix?

Thinking about doing the same for gl-mat4. How close are we matching gl-matrix? Couple issues I've noticed:

no GL_ARRAY_TYPE, only works on typed arrays
no 'aliases' like idt or mul

Some other questions...

any tests planned?
it would be nice if we had some automated way of knowing when this is falling behind gl-matrix in terms of patches, features or bug fixes ..  hmm

EDIT:
For the most part, the original gl-matrix files can be split pretty easily and automatically with regexes.. maybe worth considering.

Toji has converted to a more modular format which uses webpack for the workflow.
Wouldn't it be best for us to simply use his refactored code driectly?  We could more easily keep up with releases.
Check out https://github.com/toji/gl-matrix/tree/master/src which has the master gl-matrix simply be several imports of the refactored source.

Some thoughts on that:

the goals of this module (and others like gl-quat, gl-vec3) are to fully modularize the source down to each function

this allows it to be used in places like this where there is no need for a "matrix library" -- just some individual vector functions

modularization down to each function also means that versioning becomes less problematic for front-end uses

for example, if gl-mat3 is bumped to 2.0.0 due to a change in a single function, bundlers (browserify/webpack) can still de-duplicate the rest of the functions since they are separate modules

depending directly on gl-matrix/src/foobar is fragile; if Toji decides to change his build step (for e.g. use ES6) or re-factor internal sources, it could break this module and all other dependents using it
the strict focus on modularization leads to some different design decisions for a library like this, see https://github.com/stackgl/gl-mat4/pull/6
gl-matrix does not have a clear scope or "end in sight" - see recent merges: [1], [2], [3]

I would rather encourage new functions to be added independently to npm, even if that means breaking feature parity with gl-matrix

/cc @hughsk @mikolalysenko

@mattdesl those are all great points but I'm curious what @toji's thoughts are.
I'm just getting into webgl and it's confusing to have such similar and well maintained / well adopted packages as a newcomer.  Plus, if I want to use gl-matrix for the SIMD support then I can't use most of the stackgl packages without having duplicate vec/mat libraries.

I think @mattdesl points are very valid. It's valuable to adhere to the core goals of the libray: gl-matrix goes out of it's way to avoid introducing explicit classes for the various types, even when that would make some things easier (like SIMD). Similarly this library goes out of it's way to maintain strict modularity. I don't think introducing a formal dependency on my library serves that goal.
That said, if there's any sort of code or style tweaks that I could make to gl-matrix that would improve the workflow for migrating new features to this library I'm happy to discuss them!

@toji for me the restructuring you've done eases any modularity concerns.  Between webpack's dead code elimination and the ability to import individual components I don't have any issues there. :+1: for the restructuring though import vec2 from "gl-matrix/vec2" would be a great shift for v3 over import vec2 from "gl-matrix/src/gl-matrix/vec2".
I'm also a big fan of the simplified imports you get by having these components in a single package.
import { vec3, mat4 } from "gl-matrix";

Although they're not identical concerns, they are related. It's also nice to have a single github project to go to for issues related to vec/mat math.
Personally I'm just bummed I can't use some of the drop-in stackgl components without adding duplicate code. Especially when the libraries are functionally equivalent.

I'm just getting into webgl and it's confusing to have such similar and well maintained / well adopted packages as a newcomer.

I think more documentation in these repos would help, and clearer explanation about the philosophical differences to gl-matrix. It should be noted that this is currently a subset of gl-matrix, implementing the core functionality, and not much more. New features are already being added in their own modules.

Between webpack's dead code elimination and the ability to import individual components I don't have any issues there.

Unless I'm mistaken, you will still end up importing the entire vec2.js module even if you just need, say, vec2.add.

Personally I'm just bummed I can't use some of the drop-in stackgl components without adding duplicate code. Especially when the libraries are functionally equivalent.

Yes, it's a bummer. But it would be more of a bummer if all the current dependents on gl-* modules used gl-matrix. Instead of a few duplicate functions, you'd be dealing with hundreds of kilobytes of duplicate/dead code and potentially several copies of gl-matrix in your final bundle. :laughing:
One solution would be to refactor gl-matrix to use the same architecture as here to keep it modular. However, there's some obvious pitfalls:

that is a huge overhaul and a lot of work that @toji and many of the gl-matrix users would not benefit from
gl-matrix and gl-* have different philosophies in regard to new features and scope
configuration is not easy to solve with modules https://github.com/stackgl/gl-mat4/pull/6#issuecomment-100523121

Even SIMD is a lot of extra code for (currently) little gain. Only works in FF nightly, only works on typed arrays, introduces a new avenue for bugs, and the extra performance may be negligible given your use case.
Ultimately I think it's OK to keep things separate for now. Once ES6 and tree-shaking becomes common place in Node/npm/browser, maybe it will be easier to merge the projects.

Hopefully not OT, but have we considered es6 modules, both syntax and
module loaders via SPDY and HTTP/2?
I've used es6/JSPM for a recent webgl mooc by Ed Angel and loved it. I used
it both in dynamic mode (recompiles each page load, good for development)
and bundled (good for deployment, much faster).
The biggest problem is that there are multiple systems for module loading.
I used JSPM due to being standards oriented. It handled the latest glMatrix
with no problems as a "global" module type. But there are others like
webpack and babel/browserify and the es6-module-loader which JSPM builds
upon.
On Thu, Oct 8, 2015 at 2:56 PM, Matt DesLauriers<EMAIL_ADDRESS>wrote:

I'm just getting into webgl and it's confusing to have such similar and
well maintained / well adopted packages as a newcomer.
I think more documentation in these repos would help, and clearer
explanation about the philosophical differences to gl-matrix. It should
be noted that this is currently a subset of gl-matrix, implementing the
core functionality, and not much more. New features are already being added in
their own modules
https://github.com/Jam3/quat-from-unit-vec3/blob/master/index.js.
Between webpack's dead code elimination and the ability to import
individual components I don't have any issues there.
Unless I'm mistaken, you will still end up importing the entire vec2.js
module even if you just need, say, vec2.add.
Personally I'm just bummed I can't use some of the drop-in stackgl
components without adding duplicate code. Especially when the libraries are
functionally equivalent.
Yes, it's a bummer. But it would be more of a bummer if all the current
dependents on gl-* modules used gl-matrix. Instead of a few duplicate
functions, you'd be dealing with hundreds of kilobytes of duplicate/dead
code and potentially several copies of gl-matrix in your final bundle. [image:
:laughing:]
One solution would be to refactor gl-matrix to use the same architecture
as here to keep it modular. However, there's some obvious pitfalls:

that is a huge overhaul and a lot of work that @toji
https://github.com/toji and many of the gl-matrix users would not
benefit from
gl-matrix and gl-* have different philosophies in regard to new
features and scope
configuration is not easy to solve with modules stackgl/gl-mat4#6
(comment)
https://github.com/stackgl/gl-mat4/pull/6#issuecomment-100523121

Even SIMD is a lot of extra code for (currently) little gain. Only works
in FF nightly, only works on typed arrays, introduces a new avenue for
bugs, and the extra performance may be negligible given your use case.
Ultimately I think it's OK to keep things separate for now. Once ES6 and
tree-shaking becomes common place in Node/npm/browser, maybe it will be
easier to merge the projects.
—
Reply to this email directly or view it on GitHub
https://github.com/stackgl/gl-mat3/issues/1#issuecomment-146682608.

ES6 would be great for gl-matrix - a tool like rollup might produce a slimmer UMD build than webpack. Those using rollup would also get dead code elimination down to each function, as long as jsnext:main is specified in package.json.
However, gl-matrix would still have to pre-publish ES5 to npm for those not using rollup. This means Node/webpack/browserify users consuming the module via npm would not get the benefits of ES6. JSPM might also have the same issue - I'm not sure whether JSPM resolves jsnext:main or main.
Even with all this, there's no point in moving all the gl-vec2 files to a single ES6 file. I'm not aware of any tool that can output multiple ES5 files per function from a single ES6 source.


Local pull request success status testing

Docs Build status updates of commit 04e9213:
:clock10: Pending: waiting for processors (7 builds ahead of you)
:warning: Docs Build is busy, currently there are 7 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit 04e9213:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

E2E_DocsBranch_Dynamic/index.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Delete Resources

Need to delete VM

Ran Plan for dir: . workspace: default
google_compute_instance.default: Refreshing state... [id=projects/terraformprojects-365816/zones/us-central1-a/instances/atlantis-vm-dev]

No changes. Your infrastructure matches the configuration.

Terraform has compared your real infrastructure against your configuration
and found no differences, so no changes are needed.

:arrow_forward: To apply this plan, comment:

atlantis apply -d .

:put_litter_in_its_place: To delete this plan click here
:repeat: To plan this project again, comment:

atlantis plan -d .

:fast_forward: To apply all unapplied plans from this pull request, comment:

atlantis apply

:put_litter_in_its_place: To delete all plans and locks for the PR, comment:

atlantis unlock

atlantis destroy

Error: unknown command "destroy".
Run 'atlantis --help' for usage.
Available commands(--allow-commands): version, plan, apply, unlock, approve_policies

atlantis --help

atlantis
Terraform Pull Request Automation

Usage:
  atlantis <command> [options] -- [terraform options]

Examples:
  # show atlantis help
  atlantis help

  # run plan in the root directory passing the -target flag to terraform
  atlantis plan -d . -- -target=resource

  # apply all unapplied plans from this pull request
  atlantis apply

  # apply the plan for the root directory and staging workspace
  atlantis apply -d . -w staging

Commands:
  plan     Runs 'terraform plan' for the changes in this pull request.
           To plan a specific project, use the -d, -w and -p flags.
  apply    Runs 'terraform apply' on all unapplied plans from this pull request.
           To only apply a specific plan, use the -d, -w and -p flags.
  unlock   Removes all atlantis locks and discards all plans for this PR.
           To unlock a specific plan you can use the Atlantis UI.
  approve_policies
           Approves all current policy checking failures for the PR.
  version  Print the output of 'terraform version'
  help     View help.

Flags:
  -h, --help   help for atlantis

Use "atlantis [command] --help" for more information about a command.

atlantis plan -destroy

Ran Plan for dir: estroy workspace: default
Plan Error
dir "estroy" does not exist

atlantis plan -- -destroy

Ran Plan for dir: . workspace: default
Show Output
google_compute_instance.default: Refreshing state... [id=projects/terraformprojects-365816/zones/us-central1-a/instances/atlantis-vm-dev]

Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
- destroy

Terraform will perform the following actions:

  # google_compute_instance.default will be destroyed
- resource "google_compute_instance" "default" {
      - can_ip_forward       = false -> null
      - cpu_platform         = "Intel Broadwell" -> null
      - current_status       = "RUNNING" -> null
      - deletion_protection  = false -> null
      - enable_display       = false -> null
      - guest_accelerator    = [] -> null
      - id                   = "projects/terraformprojects-365816/zones/us-central1-a/instances/atlantis-vm-dev" -> null
      - instance_id          = "4661442100994193029" -> null
      - label_fingerprint    = "42WmSpB8rSM=" -> null
      - labels               = {} -> null
      - machine_type         = "e2-micro" -> null
      - metadata             = {} -> null
      - metadata_fingerprint = "OunhsVn_J1I=" -> null
      - name                 = "atlantis-vm-dev" -> null
      - project              = "terraformprojects-365816" -> null
      - resource_policies    = [] -> null
      - self_link            = "https://www.googleapis.com/compute/v1/projects/terraformprojects-365816/zones/us-central1-a/instances/atlantis-vm-dev" -> null
      - tags                 = [
          - "dev",
          - "engineering",
        ] -> null
      - tags_fingerprint     = "x7YZUfmdF48=" -> null
      - zone                 = "us-central1-a" -> null

      - boot_disk {
          - auto_delete = true -> null
          - device_name = "persistent-disk-0" -> null
          - mode        = "READ_WRITE" -> null
          - source      = "https://www.googleapis.com/compute/v1/projects/terraformprojects-365816/zones/us-central1-a/disks/atlantis-vm-dev" -> null

          - initialize_params {
              - image  = "https://www.googleapis.com/compute/v1/projects/ubuntu-os-cloud/global/images/ubuntu-2204-jammy-v20221014" -> null
              - labels = {
                  - "env" = "dev"
                } -> null
              - size   = 10 -> null
              - type   = "pd-standard" -> null
            }
        }

      - network_interface {
          - name               = "nic0" -> null
          - network            = "https://www.googleapis.com/compute/v1/projects/terraformprojects-365816/global/networks/default" -> null
          - network_ip         = "<IP_ADDRESS>" -> null
          - queue_count        = 0 -> null
          - stack_type         = "IPV4_ONLY" -> null
          - subnetwork         = "https://www.googleapis.com/compute/v1/projects/terraformprojects-365816/regions/us-central1/subnetworks/default" -> null
          - subnetwork_project = "terraformprojects-365816" -> null

          - access_config {
              - nat_ip       = "<IP_ADDRESS>" -> null
              - network_tier = "PREMIUM" -> null
            }
        }

      - scheduling {
          - automatic_restart   = true -> null
          - min_node_cpus       = 0 -> null
          - on_host_maintenance = "MIGRATE" -> null
          - preemptible         = false -> null
          - provisioning_model  = "STANDARD" -> null
        }

      - shielded_instance_config {
          - enable_integrity_monitoring = true -> null
          - enable_secure_boot          = false -> null
          - enable_vtpm                 = true -> null
        }
    }

Plan: 0 to add, 0 to change, 1 to destroy.

:arrow_forward: To apply this plan, comment:

atlantis apply -d .

:put_litter_in_its_place: To delete this plan click here
:repeat: To plan this project again, comment:

atlantis plan -d . -- -destroy

Plan: 0 to add, 0 to change, 1 to destroy.

:fast_forward: To apply all unapplied plans from this pull request, comment:

atlantis apply

:put_litter_in_its_place: To delete all plans and locks for the PR, comment:

atlantis unlock

atlantis plan -destroy

Ran Plan for dir: estroy workspace: default
Plan Error
dir "estroy" does not exist


200 rewrites and custom headers not working

I have 2 Amplify Apps (both in us-east-2)
Parent appId is d8l7t3188xrku
Child appId is d2odpmx6x4fi0k
Both are using master branch
Child deploys a JS file to https://master.d2odpmx6x4fi0k.amplifyapp.com/header.js
Parent has a 200 rewrite rule for to send requests for /header.js to the child app's JS file referenced above
JSON for the rewrite rule in parent:
[
    {
        "source": "/header.js",
        "target": "https://master.d2odpmx6x4fi0k.amplifyapp.com/header.js",
        "status": "200",
        "condition": null
    }
]

So I would expect a request to parent/header.js to result in me seeing the same JS file from the link above, however I instead get redirected to index.html
Link for testing https://master.d8l7t3188xrku.amplifyapp.com/header.js
This poses an issue, because I need to use that JS file in parent app. So in the meantime, I have attempted to setup custom headers on child so I can access the JS file without violating cors. My build settings look like the following for child
version: 0.1
frontend:
  phases:
    preBuild:
      commands:
        - npm ci
    build:
      commands:
        - npm run build
  artifacts:
    baseDirectory: /dist/
    files:
      - '**/*'
  customHeaders:
    - pattern: '*'
      headers:
      - key: 'Access-Control-Allow-Origin'
        value: '*'
  cache:
    paths:
      - node_modules/**/*

My build logs for child include this towards the end
2020-02-17T17:51:38.806Z [INFO]: customHeaders section is found in amplify.yml, applying custom headers...

And I updated the contents to make sure it deployed a new copy during the deploy phase
2020-02-17T17:51:41 [INFO]: Starting Deployment
2020-02-17T17:51:41 [INFO]: Uploading header.js
2020-02-17T17:51:41 [INFO]: Updating Edge config
2020-02-17T17:51:42 [INFO]: Deployment finished.

However if you click the link at the top of the post, the header isn't present, so I'm still stuck.

@anatonie, thanks for reporting this. We're investigating.

Got same issue

This issue has been resolved and I am closing this out.  Please feel free to open another issue if anyone continues to see this behavior.


Two-stage IPO for NVHPC

See #569, fixes #328. I cleaned up the code and the git history from that PR.

Would it be possible to move most or all macros in https://github.com/MFlowCode/MFC/blob/master/src/simulation/include/inline_riemann.fpp to subroutines, now?

@sbryngelson I tried doing the others yesterday but got some issues on Frontier. For now, I think we should just merge this PR and remove the other macros with the other frontier hacks.

@sbryngelson I tried doing the others yesterday but got some issues on Frontier. For now, I think we should just merge this PR and remove the other macros with the other frontier hacks.

Yes this is fine with me. Just waiting on it to be 'working'. That is, passing CI with good benchmark results.


perlPackages.TextBibTeX: always install libbtparse.so to /lib instead of /lib64

Fixes the build of biber: https://hydra.nixos.org/build/222252165
The root cause should be the same as in https://github.com/NixOS/nixpkgs/pull/122567
Description of changes

Things done

Built on platform(s)

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

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

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

13 packages built:

biber
biber.devdoc
blahtexml
blahtexml.doc
bluespec
bluespec.doc
perl534Packages.TextBibTeX
perl534Packages.TextBibTeX.devdoc
perl536Packages.TextBibTeX
perl536Packages.TextBibTeX.devdoc
tectonic
texlive.combined.scheme-full
yosys-bluespec

Works for me. Thanks!


[WIP] windows compatability

Hello I am trying to make this library compatible on the Windows platform through React Native Windows.
Currently I am looking at the android implementation as a guide.
Also looking at the docs:

Native Module Windows
React Native Share library that has windows compatibility

Any feedback or help would be appreciated. Thank you.

@AlexanderZaytsev I have tested this and it works

Thank you @josephan :+1:

@mmazzarolo You're welcome!


[Bulk Pusub] Add Negative Scenarios for Bulk Publish

In what area(s)?

/area test-and-release
Describe the proposal

Add Negative test scenarios for Bulk Publish eg: wrong message structure

/keep-alive

/assign


Ability to display country in language switcher

Add ability to display country for language codes like fr_FR or fr_BE for example.

looks sane to me.

@jtraulle Can you add some tests for this behavior. Thanks!

@ikwattro Sorry but I do not have time at the moment :wink:
Feel free to close this PR if you want.


Module timing source selection window is messed up on the engine configuration panel

When I set the Timing source Type to module timing source, the timing source window is badly overlapped with other items on the panel

making other controls\indicators hard to see and modify

This is a duplicate of this issue and has already been closed.
https://github.com/LabVIEW-DCAF/StandardEngine/issues/55


Correct certificate and key names for explicit ec param test

Just a fix for leftover old certificate names.

This pull request is ready to merge

Merged to master. Thank you for the review.


Allow use of url or slug page variable

Other static site generators tend to support the use of a url or a slug variable, which is the route the final page is served at.
Currently, I wish to have a filename called 00-intro.md and have the url be introduction-to-julia or introduction-to-julia.html, if inside 00-intro.md there is a page variable that contains a valid url.

Minor improvement suggestion: it would be nice if the slug meta variable that is returned by pagevar always contained the final url. Currently, it contains the final url if it is set by the user or it is nothing / an empty variable, and the user has to check that and then parse the filename to figure out the final url.

Yes that makes sense, I'll add another issue for that


⚠ ClamAV has degraded performance

In c653e31, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 83 ms

Resolved: ClamAV performance has improved in 9c8a9f5.


[Input] disableUnderline changes component height

[x] I have searched the issues of this repository and believe that this is not a duplicate.

Normal inputs have 32px in height. disableUnderline removes the 2 px at the bottom, resulting in a component of 30px height. This has a few issues:

A disableUnderline component doesn't align well alongside a row of underlined components
30px breaks vertical rhythm, as it's not a multiple of the theme unit.

I'm willing to submit a PR to add the missing 2px if this change is ok.
Expected Behavior

Current Behavior

Steps to Reproduce (for bugs)
Just use disableUnderline components alongside normal underlined components.
https://codesandbox.io/s/l9xryo62x7
Context
I'm trying to use a <Select disableUnderline> alongside a list of underlined components and they don't align.
Your Environment

Tech
Version

Material-UI
v1-beta11

React
15

browser
Chrome latest

etc

I do think that the current behavior is the expected one. We have to make a call between keeping the underline height or not. I think that reducing the height of the input when the underline is not present it the best call to make given using two input that looks different side by side isn't consistent to start with.
Also, you can fix your example by removing alignItems: 'flex-start',.

I understand that a call must be made. Yet, I argue that even using the component without placing it next to other underlined components breaks the page's vertical rhythm without the user being aware of/having intended it. "All components have heights divisible by 8px" is a reasonable mental assumption users of this library might be making and having a prop break the assumption without warning might not be ideal.

All components have heights divisible by 8px

This is something I have never been taking into account so far. At least, I haven't noticed this pattern in the spec. But, yeah, this sounds like a good pattern!

Vertical rhythm is a pretty wide-spread concept in design and apparently there's a mention of it in the spec as well (albeit not explicitly as "component heights must be multiples of 8px"):
https://material.io/guidelines/layout/metrics-keylines.html
If one component doesn't have divisible heights, then all the components after it are shifted and don't align to the 8px grid the spec mentions.

@dapetcu21 This is something I wanted to enforce for the Typography component at some point but lost this priority. I have never considered applying it to the other components. While I do think that enforcing it for the typography is something that doesn't require too much effort with a good outcome. I'm less convinced with the other component. At least, it won't harm trying 👍 .

So, in that case, would it be ok to make a PR out of this?
https://github.com/dapetcu21/material-ui/tree/input-fix-disable-underline

@dapetcu21 Yes, we can try. Let's see how the visual regression tool catch :).


Cosmos DB Input SQL Query requires values as String - Javascript

I'm not sure if this is the intended behavior, but I spent a better part of the day trying to send an Azure Storage Queue Message to an Azure Function using a Cosmos DB input, utilizing the SQL Query option, to get specific documents, and I think I have found an issue.
When I tried to query documents in the form {"String": Number} where the database's document match that form, the query was unsuccessful and returned an empty array. However, when querying the data directly in the Cosmos DB section of the Azure Portal, a similar query (I.E. Select * from c where c.mrnum = 157739 ) would succeed. This lead me to believe that a query with just a number should work when the form of the data is the same.
Here are examples that did and did not work.
Azure Function - Cosmos DB Input - SQL Query:
SELECT * FROM d where d.mrnum = {mrnum}

Azure Storage Queue - Message:
/* Did not work */
{"mrnum": 157739}

/* Did work (when documents matched)*/
{"mrnum": "157739"}

Documents:
/* Did not allow query */
{
    "mrnum": 157739,
    "etc": "..."
},
{
    "mrnum": 163358,
    "etc": "..."
}

/* Did allow query (when queue message matched) */
{
    "mrnum": "157739",
    "etc": "..."
},
{
    "mrnum": "163358",
    "etc": "..."
}

Function:
module.exports = function (context, message, docs) {
    context.log(docs);
    context.done();
}

If this is the intended behavior, then I believe this should be clearly stated in the documentation so that people don't run into this same issue.

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

ID: fa5bcb79-2af8-3b0e-c78c-0c89a2535e15
Version Independent ID: 31b87687-7841-f46f-8c97-38898e7b97db
Content: Azure Cosmos DB bindings for Functions 2.x
Content Source: articles/azure-functions/functions-bindings-cosmosdb-v2.md
Service: azure-functions; cosmos-db
GitHub Login: @craigshoemaker
Microsoft Alias: cshoe

@itsknob Thanks for the feedback! We are currently investigating and will update you shortly.

@itsknob Thanks for reporting this! This seems to be a problem when dealing with numbers specifically.
I have created an issue - Azure/azure-webjobs-sdk-extensions#533 to further investigate.

@itsknob With respect to this document and the issue at hand, there is no doc update required at the moment.
We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.

@itsknob While we investigate this issue further, here is a workaround you can try out

Create a User Defined Function in Cosmos DB with this code

function ConvertToNumber(str){
    return Number(str);
}

And use it in your function.json like this

{
  "bindings": [
    {
      "name": "myQueueItem",
      "type": "queueTrigger",
      "direction": "in",
      "queueName": "js-queue-items",
      "connection": "<connection-string-setting-name>"
    },
    {
      "type": "cosmosDB",
      "name": "inputDocument",
      "databaseName": "inDatabase",
      "collectionName": "d",
      "connectionStringSetting": "<connection-string-setting-name>",
      "sqlQuery": "select * from c where c.num = udf.ConvertToNumber({num})",
      "direction": "in"
    }
  ]
}

This workaround was shared initially on StackOverflow by Amor.

Thank you for investigating this issue and the workaround.


Question

Hey guys - new to the channel here. I had an idea for the RuneLite client and wanted to gauge the feasibility of it. I'm a software engineer and my work primarily focuses on frontend web development in Chrome with TypeScript + Angular 2. I've played around with the RuneLite client code a bit and have noticed that developing interfaces in Swing is... a little difficult compared to the wonderful world of the web :-). With the growing popularity of desktop application frameworks like Electron, I was wondering if it would be possible and worth the time to integrate the runescape-client + runelite apis with a desktop application framework like Electron so that we can build a rich web based UIs for the RuneLite client. This would allow a greater audience of developers to contribute to the UI since web development is generally easier to pick up and more broadly known than Swing. It would also give us all of the powerful rendering features of CSS. All of that being said, I've never created an Electron application, but I do have experience using java WebViews to pass data back and forth between Java and JavaScript. One of my main concerns would be the performance overhead doing this as it may be too slow for mid to low tier computers. I wanted to get the communities thoughts on this and see if anyone else would be interested in exploring this with me.
-Chris

Swing works fine for us atm. If we have any opening, we will let you know.

Okay man, thanks.


Docs release/week of 9 12

Gimbal assembly

Thermal
laser
FPV

Gimbal testing
Prop guard assembly

I'll make a separate PR later to fix that
On Fri, Sep 23, 2022, 09:01 noelified @.***> wrote:

@.**** commented on this pull request.
In .gitignore
https://github.com/bellflight/AVR-2022/pull/249#discussion_r978707208:

\ No newline at end of file
+.DS_Store

idk, I did not manually create that.
—
Reply to this email directly, view it on GitHub
https://github.com/bellflight/AVR-2022/pull/249#discussion_r978707208,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACB4QK56OVDYHBOQKXTZFILV7WZ5BANCNFSM6AAAAAAQTQAETE
.
You are receiving this because you commented.Message ID:
@.***>


Change linked guide to the same as .guide

considering switching the guide over until wiiu.guide gets certain important updates.


Submission to add Yeti to the ShowcaseList

Thanks for submitting a PR! Please read these instructions carefully:
Motivation (required)
Hello, I would like to put back Yeti Smart Home on the Showcase list as it is an application to control smart home devices fully built using react-native technology
Thank you

We're not currently accepting PRs for the Showcase. Thanks for your understanding.


Add missed image folder from full version

In the head, there are links to favicon images but folder was missed

Thank you :+1:


Prefabs gone?

I extracted a game, and I get thousands of prefabs, but since the game got updated to U2019.1.8 I had to update UtinyRipper, and now I get like 10 prefabs. The rest are missing and are in the levels as separeate objects without prefabs, which I can't reuse in other levels, since the levels are all one combined mesh.
I also noticed that a lot of file paths now get lower cased, which is especially a problem with physics materials.
What happened?

Prefabs gone in this particular game. It is developer's decision use or not to use prefabs.
I don't understand why there is a problem with physics material because of lower case. Anyway, there is no way to export assets in other way.

Developer's decision to remove a thousand prefabs? That makes no sense. He's obviously still using prefabs, but Utiny no longer exports them, and each level that uses them have no association with the prefab. It's only exporting prefabs that are in the resources folder now, and they're all lower cased.

Yea, I just checked with a completely new Unity project.
It has none of my prefabs, and in each scene the objects are not instances of the prefab.

Unity always has been exporting prefabs only for resources and references. Combined mesh mean that developer decided to get rid of dynamic resources (prefabs) and made them static.
All resources are lower case because that is how unity store them. I'll improve naming a bit sometime later.

But with previous versions of UtinyRipper I got non-resource prefabs, etc. and all names were proper casings.

Do you say that with previous version of ripper you could extract prefabs from previous version of the game but with latest version of ripper you can't get prefabs from the same version of the game?

Apparently not. I guess the game just had practically all prefabs in resources.
But why are names now lower case for resources? Previous versions of uTinyripper got the casing right.
The actual casings are in resources.asset. Eg. uTinyripper exports a file as 'referencepose_bindpose.asset', and to correct it, I can just open up resources.assets and search for 'referencepose_bindpose' to see that the correct casings is 'ReferencePose_BindPose'.

Unity handle its resources in a case insensitive way. So there is no much difference between 'referencepose_bindpose' and 'ReferencePose_BindPose' since directory path will be in lower case anyway.

Fixed resource asset names in 0479bab4f9e4113f048afa35402e26dab29bc78d


WIP: rely on knative/pkg to update TaskRuns

This removes the Update call from the TaskRun ReconcileKind method,
instead relying on knative/pkg's mechanics to update the resource if it
changed.
This refactors away the method to apply the version annotation to the
resource, instead doing it at the top of ReconcileKind, and all update
error handling.
What's left is a method to emit Cloud Events, which is just deferred
at the top of ReconcileKind so it always gets called -- if the before
and after conditions are equivalent, emitEvents is a no-op.
Proof of concept for https://github.com/tektoncd/pipeline/issues/5146
/kind cleanup
Submitter Checklist
As the author of this PR, please check off the items in this checklist:

[x] Has Docs included if any changes are user facing
[x] Has Tests included if any functionality added or changed
[x] Follows the commit message standard
[x] Meets the Tekton contributor standards (including
functionality, content, code)
[x] Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
[x] Release notes block below has been updated with any user facing changes (API changes, bug fixes, changes requiring upgrade notices or deprecation warnings)
[x] Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes
NONE

/test all
(Just realized it was skipping CI.. 🙃 )

It seems something somewhere was depending on this to persist the task labels or something; this fails on the only test that checks that the task label is persisted on the taskrun.
    taskrun_test.go:1983: Labels were not added to task run
    taskrun_test.go:1986: Did not get expected label (-want, +got):   string(
        -       "test-task",
        +       "",
          )

Anyway, I'll keep plugging away later.

/test check-pr-has-kind-label

PR friction log:

the kind label wasn't set when I created the PR with /kind cleanup, causing CI ❌
manually adding the label didn't cause the label check to run, so still ❌

Thank you for tracking these. They should be fixed now.

/retest

@imjasonh what's the status ? 🙃 (it's red right now because of the rebase required I guess ?)

Aside from needing to rebase, I need to figure out why label propagation is broken by this.
I think we're relying on there being two updates of the object in etcd during the initial reconcile, so that cloudevent receivers can see the TaskRun has started, then also see it become Pending (I think). The model knative/pkg expects is that each time through ReconcileKind is zero-or-one etcd update, which conflicts with our usage. I think their model is simpler to understand than ours, and I'd like to get to it, without breaking cloudevents consumers.
...Then I got distracted with other stuff and haven't made it back to work on this. I'll rebase at least so it's not so red, but any help untangling this or better understanding of how this works would be helpful.

Aside from needing to rebase, I need to figure out why label propagation is broken by this.
I think we're relying on there being two updates of the object in etcd during the initial reconcile, so that cloudevent receivers can see the TaskRun has started, then also see it become Pending (I think). The model knative/pkg expects is that each time through ReconcileKind is zero-or-one etcd update, which conflicts with our usage. I think their model is simpler to understand than ours, and I'd like to get to it, without breaking cloudevents consumers.

The started event and running events are sent during the same reconcile cycle, because I didn't want to rely on two reconcile cycles for that. Not sure why labels would not work... I wonder if it's something about how tests are designed?

Let me try to tackle this for TaskRun and PipelineRun 🤔


SyntaxError: Unexpected token (

Hi, I have a Syntax Error when i'm trying to run the script. Can you look at it or do I something wrong? First of all thanks for the solution and as second thanks for the feedback. For more info look attachment.
Attachment: https://1drv.ms/i/s!Ap-6dK_njayli2Mdgi7WwxQ6Xwxk

Hello.
mcdetect requires node 7.6.0 or later. What is your node version?

Thanks for your reply. Indeed I had node version 6.1. I have upgraded now and its works fine.

Nice, closing this.


Fix mapem explode

Fix #96
No more NaNs

I guess this needs to be rebased

Whoops, I guess I was in a rush. Fixed

thanks. It could be useful to draw some attention to this in a doc-cell. I don't think that the original paper has this "epsilon". I believe it is necessary because of OSEM.

I'm not 100% sure why subsets would impact this update, which is in image space (that's in no way to say I doubt it!). But logically, if locally x_reg = 1 and x_em = 0 then you'd get the denominator = 0, so it seems pretty reasonable that that could occur and that the eps is a good idea. I've added a fairly generic explanation - do you think it's adequate?

sure.
I believe that if you initialise the algo with non-zero, and you use 1 subset, it can never get to this case, but it's ages ago I've checked that or indeed read the paper. Happy with your modification.


:bug: Fixing callContract when block id is a number or a tag

Describe your changes
GatewayProvider.callContract fails when using blockTag or blockNumber. It always sends blockHash even if the block id is a number or a tag.
Linked issues
Closes --> https://github.com/software-mansion/starknet-jvm/issues/154

Thank you for creating a PR for us, we always appreciate users who want to contribute ❤
Unfortunately @cptartur was working on fix in the same time as you. We decided to merge his PR (https://github.com/software-mansion/starknet-jvm/pull/159/files) as it fixes this problem in other places as well in GatewayProvider.
To avoid doing unnecessary work please make sure no one is assigned to the issue that you want to fix. If there is someone there is a chance someone is already working on it.


Exception when executing task graph with HighLevelGraph after a shuffle

Describe the issue:
In https://github.com/geopandas/dask-geopandas/issues/303, dask-geopandas has a report that its custom sjoin method fails with a TypeError under some conditions. Internally, that method constructs a HighLevelGraph.
The observed failure is a TypeError raised by geopandas because dask fails to substitute the concrete (geo)DataFrame for the key (name, partition_number) when executing the task graph.
I've managed to produce a dask / dask-expr only version:
Minimal Complete Verifiable Example:
import dask.dataframe as dd
import pandas as pd
import dask
import dask_expr

dask.config.set(scheduler="single-threaded")

l1 = dd.from_pandas(pd.DataFrame({"a": [1, 2], "b": [0, 0]}), npartitions=1).shuffle("a")
r1 = dd.from_pandas(pd.DataFrame({"a": [1, 3], "c": [1, 1]}), npartitions=1).shuffle("a")

def func(left, right):
    assert isinstance(left, pd.DataFrame), f"Wrong type {left}"
    return pd.merge(left, right, how="inner")

dsk = {}
name = "myjoin-" + dask.base.tokenize(l1, r1, ensure_deterministic=True)
for i in range(1):
    dsk[(name, i)] = (
        func,
        (l1._name, i),
        (r1._name, i),
    )

divisions = [None] * (len(dsk) + 1)
g1 = dask.highlevelgraph.HighLevelGraph.from_collections(name, dsk, dependencies=[l1, r1])
x1 = dask_expr.from_graph(g1, func(l1._meta, r1._meta), divisions, dsk.keys(), "myjoin")
x1.compute()

That fails with
---------------------------------------------------------------------------
AssertionError                            Traceback (most recent call last)
Cell In[3], line 30
     28 g1 = dask.highlevelgraph.HighLevelGraph.from_collections(name, dsk, dependencies=[l1, r1])
     29 x1 = dask_expr.from_graph(g1, func(l1._meta, r1._meta), divisions, dsk.keys(), "myjoin")
---> 30 x1.compute()

File [~/gh/geopandas/dask-geopandas/.direnv/python-3.10/lib/python3.10/site-packages/dask_expr/_collection.py:477](http://<IP_ADDRESS>:8889/~/gh/geopandas/dask-geopandas/.direnv/python-3.10/lib/python3.10/site-packages/dask_expr/_collection.py#line=476), in FrameBase.compute(self, fuse, **kwargs)
    475     out = out.repartition(npartitions=1)
    476 out = out.optimize(fuse=fuse)
--> 477 return DaskMethodsMixin.compute(out, **kwargs)

File [~/gh/geopandas/dask-geopandas/.direnv/python-3.10/lib/python3.10/site-packages/dask/base.py:376](http://<IP_ADDRESS>:8889/~/gh/geopandas/dask-geopandas/.direnv/python-3.10/lib/python3.10/site-packages/dask/base.py#line=375), in DaskMethodsMixin.compute(self, **kwargs)
    352 def compute(self, **kwargs):
    353     """Compute this dask collection
    354
    355     This turns a lazy Dask collection into its in-memory equivalent.
   (...)
    374     dask.compute
    375     """
--> 376     (result,) = compute(self, traverse=False, **kwargs)
    377     return result

File [~/gh/geopandas/dask-geopandas/.direnv/python-3.10/lib/python3.10/site-packages/dask/base.py:662](http://<IP_ADDRESS>:8889/~/gh/geopandas/dask-geopandas/.direnv/python-3.10/lib/python3.10/site-packages/dask/base.py#line=661), in compute(traverse, optimize_graph, scheduler, get, *args, **kwargs)
    659     postcomputes.append(x.__dask_postcompute__())
    661 with shorten_traceback():
--> 662     results = schedule(dsk, keys, **kwargs)
    664 return repack([f(r, *a) for r, (f, a) in zip(results, postcomputes)])

Cell In[3], line 14, in func(left, right)
     13 def func(left, right):
---> 14     assert isinstance(left, pd.DataFrame), f"Wrong type {left}"
     15     return pd.merge(left, right, how="inner")

AssertionError: Wrong type ('rearrangebycolumn-8e5135a4ed46029cf9bb3c4bc7eff32e', 0)

As I mentioned, the shuffle there is important. Without that shuffle, things work fine.
Anything else we need to know?:
I'll take a look at this today.
Environment:

Dask version: '2024.8.1'
dask-expr version: '1.1.11'

Thanks for the report. This is not unexpected, the optimiser will most likely change l1._name and r1._name because we are changing the backing expression.
You can simulate this if you need the output keys by
r1 = r1.optimize()
l1 = l1.optimize()

This is roughly what happens internally in dask-expr (we are not calling optimise but .lower() to create an expression that we can execute (you can see this in the __dask_graph__ method), optimise is preferable though

Gotcha, make sense.
Do you have any initial guesses on a good path forward? I was thinking to try to rewrite that dask-geopandas method as a new dask_expr.Expr, with the hope that it would integrate into the whole optimization.
A potential workaround in dask-geopandas is to call optimize() on the inputs before constructing the HLG. It fixes the reported error, but I'm not sure how robust this will be.

A potential workaround in dask-geopandas is to call optimize() on the inputs before constructing the HLG. It fixes the reported error, but I'm not sure how robust this will be.

This is definitely what I would recommend as long as you are using HLGs for this. Otherwise optimisation won't be triggered at all, which might leave stuff on the table.

Do you have any initial guesses on a good path forward? I was thinking to try to rewrite that dask-geopandas method as a new dask_expr.Expr, with the hope that it would integrate into the whole optimization.

When you create an expression for this, then you basically pass in left and right expressions and the expression tree will keep the references to the correct changed expression. The graph is only constructed after everything else was done (meaning optimisations), so if you implement the layer method on the expression, keys won't change anymore. Does this help? Happy to help you through the process of creating the expression


refactor: move merge cell and set cell height and weight to worksheet

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 94.18%. Comparing base (590a3c4) to head (0b7de61).

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #43      +/-   ##
==========================================
- Coverage   98.97%   94.18%   -4.79%
==========================================
  Files           8        1       -7
  Lines         781       86     -695
==========================================
- Hits          773       81     -692
+ Misses          6        3       -3
  Partials        2        2

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


As soon as you open it, it will always flash

Windows Terminal version
No response
Windows build number
No response
Other Software
No response
Steps to reproduce

Expected Behavior
No response
Actual Behavior
always flash

@freedomspiritJohn Did you set elevate:true in the profiles.defaults part of your settings/? This might be #13928

@freedomspiritJohn Did you set elevate:true in the profiles.defaults part of your settings/? This might be #13928

I don't know，i cant open it。I reset this application in the settings，It's normal now。But I hope this can be avoided in the future

Welp. Since you can't repro this anymore, I'm just gonna assume it was that. #14946 which is the fix for #13928 should be coming out soon enough in a servicing release for 1.16 and 1.17.


[Python] Dividing by zeros in standardize_accros_features function

(neuroCombat migrated here for maintainability)
From @RocaVincent:
Hi,
Thanks for this code,
Line 170 of neuroCombat.py file, I got a problem when it divides using the following term : np.dot(np.sqrt(var_pooled), np.ones((1, n_sample))). In this term, almost half of the coefficients are zeros so I got a RuntimeWarning and Nan values create problems later. Have you any idea why I got zeros and how I can fix this problem ?
Thanks

@Figsandcitrus Yes this problem has occurred for both Matlab and R implementations (which I just fixed a few minutes ago). I'll fix this for Python today

Should be fixed in https://github.com/Jfortin1/ComBatHarmonization/commit/3b6f16a060618c022983005d3a521909993a9e49


Missing doc about snapshots in CSI-v1.0 branch

Missing doc and snapshotter yaml files in CSI-v1.0 branch in examples directory.

@rollandf we have yaml files for snapshot https://github.com/ceph/ceph-csi/blob/csi-v1.0/examples/rbd/snapshot.yaml

I can do it if you want

@rollandf sure PR's are most welcome :)

Fixed by #170
@rootfs can we close this one?