Use HTTPS://

This gem is currently broken because Fontello now uses https:// by default.
Running fontello open for example will fail with this exception.
---- open ----
Traceback (most recent call last):
	15: from /Users/amirsharif/.rvm/gems/ruby-2.7.1/bin/ruby_executable_hooks:24:in `<main>'
	14: from /Users/amirsharif/.rvm/gems/ruby-2.7.1/bin/ruby_executable_hooks:24:in `eval'
	13: from /Users/amirsharif/.rvm/gems/ruby-2.7.1/bin/fontello:23:in `<main>'
	12: from /Users/amirsharif/.rvm/gems/ruby-2.7.1/bin/fontello:23:in `load'
	11: from /Users/amirsharif/.rvm/gems/ruby-2.7.1/gems/fontello_rails_converter-0.4.6/bin/fontello:138:in `<top (required)>'
	10: from /Users/amirsharif/.rvm/gems/ruby-2.7.1/gems/fontello_rails_converter-0.4.6/lib/fontello_rails_converter/cli.rb:17:in `open'
	 9: from /Users/amirsharif/.rvm/gems/ruby-2.7.1/gems/fontello_rails_converter-0.4.6/lib/fontello_rails_converter/fontello_api.rb:16:in `new_session_from_config'
	 8: from /Users/amirsharif/.rvm/gems/ruby-2.7.1/gems/rest-client-2.1.0/lib/restclient.rb:70:in `post'
	 7: from /Users/amirsharif/.rvm/gems/ruby-2.7.1/gems/rest-client-2.1.0/lib/restclient/request.rb:63:in `execute'
	 6: from /Users/amirsharif/.rvm/gems/ruby-2.7.1/gems/rest-client-2.1.0/lib/restclient/request.rb:163:in `execute'
	 5: from /Users/amirsharif/.rvm/gems/ruby-2.7.1/gems/rest-client-2.1.0/lib/restclient/request.rb:727:in `transmit'
	 4: from /Users/amirsharif/.rvm/rubies/ruby-2.7.1/lib/ruby/2.7.0/net/http.rb:933:in `start'
	 3: from /Users/amirsharif/.rvm/gems/ruby-2.7.1/gems/rest-client-2.1.0/lib/restclient/request.rb:743:in `block in transmit'
	 2: from /Users/amirsharif/.rvm/gems/ruby-2.7.1/gems/rest-client-2.1.0/lib/restclient/request.rb:836:in `process_result'
	 1: from /Users/amirsharif/.rvm/gems/ruby-2.7.1/gems/rest-client-2.1.0/lib/restclient/abstract_response.rb:123:in `return!'
/Users/amirsharif/.rvm/gems/ruby-2.7.1/gems/rest-client-2.1.0/lib/restclient/abstract_response.rb:249:in `exception_with_response': 301 Moved Permanently (RestClient::MovedPermanently)

@Overload119 thanks for the PR 👍
Just fix the failing test to also use https and we can merge it.

tests fixed in #50


Remove n_states, n_inputs, n_outputs

Seems like the only places where they are used are in linearized.py. Here, one could just replace the default x0 values with required arguments of the right size.

Hello,
We have an exciting opportunity for you! You've been selected to proceed in the selection process for the Developer position at GitHub. Congratulations on your achievement!
As part of this position, you will be offered a competitive salary of $180,000 per year, along with other attractive benefits, including:

Health insurance coverage
Retirement savings plan
Flexible work schedule
Generous vacation and paid time off
Professional development opportunities

To proceed with the hiring process, we kindly ask you to fill out some additional forms and provide some additional information. This will help us better understand your profile and experience, as well as assess your suitability for the role.
Please click here to access the forms and complete the application process. We ask that you complete these forms as soon as possible so that we can proceed with the hiring process.
Important: You have 24 hours to complete the application process.
If you have any questions or need further information, please don't hesitate to contact us.
Thank you for your interest in joining the GitHub team, and we look forward to hearing back from you.
Best regards,
GitHub Recruitment Team
weiyx16, @dilverse, @kosonocky, @ajay-sreeram, @pedrurrego, @amirli21, @volkanncicek, @kenanking, @qt06, @etiennebalit, @yoman813, @ShudingChen, @liuyaqiu, @jwliao1209, @andrewm4894, @SUDA-HLT-ywfang, @ejaycoleman, @andrewyu0, @nakamichiworks, @janniks


pragma cannot be set when runtime is automatic

Discussed in https://github.com/algolia/recommend/discussions/166

Originally posted by mwmwmw December 20, 2023
In NextJS 14.0.4 I have a pretty basic related posts recommender.
On Next 14.0.1 I get no error, and when I upgrade to anything > 14.0.1 (14.1.0 as of this writing) I get this error.
 ⨯ ./node_modules/.pnpm/@algolia+recommend-vdom<EMAIL_ADDRESS>Error:
  × pragma cannot be set when runtime is automatic
   ╭─[/home/erebus/rdar/node_modules/.pnpm/@algolia+recommend-vdom@1.11.0/node_modules/@algolia/recommend-vdom/dist/esm/FrequentlyBoughtTogether.js:1:1]
 1 │ import _extends from "@babel/runtime/helpers/extends";
 2 │ /** @jsx createElement */
   · ─────────────────────────
 3 │ import { createDefaultChildrenComponent } from './DefaultChildren';
 4 │ import { createDefaultFallbackComponent } from './DefaultFallback';
 5 │ import { createDefaultHeaderComponent } from './DefaultHeader';

If I find/replace and remove all of these pragmas, the code works fine /** @jsx createElement */
Has anyone encountered an issue like this before? I am completely stumped.

Hey @mwmwmw thanks for reporting the issue.
Indeed, it seems that something is not getting built correctly with this setup of Next.js + SWC. I believe @sarahdayan also noticed the issue.
As you mentioned, it looks like the issue is coming from the package @algolia/recommend-vdom when defining the JSX pragma /** @jsx createElement */.

Workaround

I created a Next.js application v14.1.0 that doesn't use the new App Router and the @algolia/recommend-react works. So if you can use an application with the Pages Router that should be a good temporary workaround.

Fix

We will need to test this, but it seems that adding /** @jsxRuntime classic */ in the files of @algolia/recommend-vdom exported components fixes the build issue.
we should keep this issue open to track progress on the fix.


Typo in UI: should be "Last Received" not "Last Recieved"

Hi @michaelcbutler
Though we are a little late to respond, can you drop us a link to implement the proposed changes?


Remove old warning about imports after SVML init

This warning applied to imports that followed SVML initialization, but now there are none.
Related question - do we have a test that ensures that nothing is @njit-ed during Numba import?

Thanks for the patch.

This warning applied to imports that followed SVML initialization, but now there are none.

I'm happy to remove this warning, conditional on the following test existing, which I do not think it does:

Related question - do we have a test that ensures that nothing is @njit-ed during Numba import?

Tracking down the issue that resulted in that warning being written was exceedingly hard (think it was issue #4689) so I think a test is required. Maybe the code samples demonstrating the issue in #4689 could be used as a base for this test?

In #8424 I've attempted to make the initialization of LLVM lazy (probably still needs more work). The result of this patch is that the import of numba and the use of the jit decorator family of functions does not result in LLVM being initialized. As a side effect, nothing gets JIT compiled when a jit decorated function is interpreted, prior to this merely interpreting a jit decorated function lead to the NRT being compiled.
I think this means that the warning in this PR could indeed be removed. It also seems possible to test this by seeing if:
from llvmlite import binding as b
print(b.Target.from_triple(b.get_process_triple()))

results in a RuntimeError, if it does, it means it's likely that LLVM was not initialized for CPU JIT purposes. It should therefore be possible to write some tests to run in subprocesses that do things like import numba, and exercise the jit decorators, and then check that the RuntimeError still occurs.


Add Velox dependencies to .gitignore

Summary:
add dependencies to .gitignore, to make the velox root directory  cleaner.
issue resolved: [#10434]

@Yuhta  Could you please help to review this PR.

@assignUser  Could you please help to review this PR.

This is actual a documentation issue. All of the setup scripts make use the envvar DEPENDENCY_DIR as the location for the build packages but this defaults to pwd. So you can just set that. Could you add this to the ## Getting Started section in README.md ?

I have added the instructions, please help to review this pr @assignUser

good advice, thanks @assignUser


retrofit2 support

Does anyone would like to make supports to the converter for retrofit 2 this library ?

+1

ok


in place update of array element in zephir

What is the zephir way of doing the following?
$tmp = $arr[$i];
$arr[$i] = $arr[$i + 1];
$arr[$i + 1] = tmp;

something like
var tmp;
let tmp = arr[i];
let arr[i] = arr[i + 1];
let arr[i + 1] = tmp;

should work fine, doesn't it?

Yes that works great.


Add linting!

Fix all existing lint errors, either by changing errors to warnings or fixing code
Fix TypeScript errors caused by fixing lint errors
Move eslint config to project root
Add lint to CI

Pulled into #11


Aligning with Bash style guide

Folder structure should not have Camel casing in Linux according to style guide

@mumian
IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team


obs-studio: add plugin wrapper

Once #125261 is merged, we'll have access to obsproject/obs-studio#4067, allowing OBS to load plugins from a custom path.
This adds a new function, wrapOBS, which allows users to customise their OBS with plugins like so:
wrapOBS {
  plugins = with obs-studio-plugins; [
    wlrobs
    obs-multi-rtmp
    obs-gstreamer
  ];
}

This also cleans up and moves the currently packaged OBS plugins to their own attrset, obs-studio-plugins.
obs-v4l2sink was removed entirely, as it's now part of upstream.
Motivation for this change
Fixes #77627. Impure hacks are no longer necessary in order to use OBS with plugins! :tada:
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Added a release notes entry if the change is major or breaking
[x] Fits CONTRIBUTING.md.

/status needs_reviewer

@kevincox Thanks!

@deviant is this the correct way to use wrapOBS?
nixpkgs.overlays = [
  (self: super: {
    obs-studio = self.wrapOBS {
      plugins = with self.obs-studio-plugins; [ wlrobs ];
    };
  })
];

Okay, figured out that is definitely not how to do it. Looks like you just call the wrapOBS function where you want OBS? It would be nice to have some documentation on how to use this with home-manager. I tried this but it didn't work:
      obs-studio = {
        enable = true;
        package = pkgs.wrapOBS {
          plugins = with pkgs.obs-studio-plugins; [ wlrobs ];
        };
        plugins = with pkgs.obs-studio-plugins; [ wlrobs ];
      };

I am happy to write up the documentation, but am a bit unsure what the correct solution is. The relevant home-manager docs are here

@JonathanLorimer If you want that to be what obs-studio refers to globally, yes. Personally I just have
{
  users.users.v.packages = with pkgs; [
    (wrapOBS {
      plugins = with obs-studio-plugins; [
        wlrobs
      ];
    })
  ];
}

Note that if you set obs-studio to that globally, there will probably be infinite recursion, as wrapOBS refers to it internally.

Hmmm, my plugins directory is empty, but I think this is a home manager issue now.

@JonathanLorimer I don't use home-manager personally, but looking at their OBS Studio module, this change will have broken it. It needs to be rewritten to use wrapOBS or have the paths set up differently (because the filesystem layout for plugins is different depending on whether they're installed in /lib or in ~/.config/obs-studio, and this PR changes the layout to fit the former). This module could even be completely removed if people use wrapOBS, however, as it seems to just exist to allow people to install plugins.

I did ask if the change would break linking to ~/.config/obs-studio :upside_down_face:
https://github.com/NixOS/nixpkgs/pull/125308#issuecomment-858896104

@j-k It doesn't break any previously linked instances. I had some plugins already installed in ~/.config/obs-studio myself, which continued to work just fine. I wasn't aware there was a place where this was done automatically— having home-manager out-of-tree made this easy to miss.

Actually, this won't even break silently b/c the previous plugin packages were added to aliases. So this is fine regardless.

I can set this up similar to wrapping neovim in home-manager but since there's only a packages input on the wrapOBS function and not a way to pass in your own obs-studio to be wrapped it'll either: be a breaking change removing the package option from the module, or risk that users set pluggins and set their own package resulting in the pluggins not actually being wrapped in.
I think I'll go with an alternative route for now, leaving it as-is and just fixing the link path but if a way to pass in your own obs-studio is added to wrapOBS then we can move it fully over

I think I'll go with an alternative route for now, leaving it as-is and just fixing the link path but if a way to pass in your own obs-studio is added to wrapOBS then we can move it fully over

No, you can already do this:
wrapOBS.override { obs-studio = your-custom-obs-studio; } { plugins = [ obs-studio-plugins.wlrobs ]; }

No, you can already do this:
wrapOBS.override { obs-studio = your-custom-obs-studio; } { plugins = [ obs-studio-plugins.wlrobs ]; }

Looks good, I'll do a couple more quick tests then pop in the PR

:+1: looks like the override is working too, it would have wrapped if there was actually an executable called obs
I don't have a custom obs that would be noticeably different so I just used pkg.hello
warning: Git tree '/home/jk/projects/personal/dotfiles-nix' is dirty
error: builder for '/nix/store/c6cs3b7slvpyjsg77ymn6v8dn7smfvgm-wrapped-hello-2.10.drv' failed with exit code 1;
       last 9 log lines:
       >
       > Builder called die: Cannot wrap '/nix/store/hyflfr3xh1b747sfqgjjh8b2xbxy9vld-wrapped-hello-2.10/bin/obs' because it is not an executable file

nix-repl> :b wrapOBS.override { obs-studio = pkgs.writeShellScriptBin "obs" "echo 'Hello, world!'"; } {}

this derivation produced the following outputs:
  out -> /nix/store/6w1n94x6hav4v5sqdmbqki91fdqi2xil-wrapped-obs

v@january ~> /nix/store/6w1n94x6hav4v5sqdmbqki91fdqi2xil-wrapped-obs/bin/obs
Hello, world!

Sorry, I am a bit lost, how is the override going to fix home-manager stuff? Wouldn't this require a PR against home-manager to get their plugin option to use wrapOBS?

Yes, as I've mentioned in previous comments I'm writing a PR to have the home-manager module for obs-studio use wrapOBS
The screenshot demos it working

Using it successfully with Home Manager like this on Hyprland/wlroots 😄
programs.obs-studio = {
  enable = true;
  plugins = with pkgs.obs-studio-plugins; [
    wlrobs
  ];
};


Can't load controller while running demos with Humble

Hi There,
I get these errors when i'm trying to run the cart_example_position.launch.py and couldn't find the fix for it so far:
[ruby $(which ign) gazebo-1] [INFO] [1675263006.927604309] [resource_manager]: Successful initialization of hardware 'IgnitionSystem'
[ruby $(which ign) gazebo-1] [INFO] [1675263006.927643097] [ignition_ros_control]: Loading controller_manager
[ruby $(which ign) gazebo-1] [WARN] [1675263006.939326106] [ignition_ros_control]:  Desired controller update period (0.01 s) is slower than the gazebo simulation period (0.001 s).
[ruby $(which ign) gazebo-1] [INFO] [1675263007.076156142] [controller_manager]: Loading controller 'joint_state_broadcaster'
[ruby $(which ign) gazebo-1] [INFO] [1675263007.089760367] [controller_manager]: Configuring controller 'joint_state_broadcaster'
[ruby $(which ign) gazebo-1] [INFO] [1675263007.089878783] [joint_state_broadcaster]: 'joints' or 'interfaces' parameter is empty. All available state interfaces will be published
[ruby $(which ign) gazebo-1] [ERROR] [1675263007.104400708] [joint_state_broadcaster]: None of requested interfaces exist. Controller will not run.
[ruby $(which ign) gazebo-1] [WARN] [1675263007.104440229] []: Error occurred while doing error handling.
[ruby $(which ign) gazebo-1] [ERROR] [1675263007.104457272] [controller_manager]: After activating, controller 'joint_state_broadcaster' is in state 'unconfigured', expected Active
[ros2-4] Sucessfully loaded controller joint_state_broadcaster into state active
[INFO] [ros2-4]: process has finished cleanly [pid 1155134]
[INFO] [ros2-5]: process started with pid [1155171]
[ruby $(which ign) gazebo-1] [INFO] [1675263008.025939674] [controller_manager]: Loading controller 'joint_trajectory_controller'
[ruby $(which ign) gazebo-1] [INFO] [1675263008.030003948] [joint_trajectory_controller.interpolation_methods]: No interpolation method parameter was given. Using the default, VARIABLE_DEGREE_SPLINE.
[ruby $(which ign) gazebo-1] [INFO] [1675263008.039644914] [controller_manager]: Configuring controller 'joint_trajectory_controller'
[ruby $(which ign) gazebo-1] [INFO] [1675263008.039716655] [joint_trajectory_controller]: No specific joint names are used for command interfaces. Using 'joints' parameter.
[ruby $(which ign) gazebo-1] [INFO] [1675263008.039736852] [joint_trajectory_controller]: Command interfaces are [position] and state interfaces are [position velocity].
[ruby $(which ign) gazebo-1] [INFO] [1675263008.039749101] [joint_trajectory_controller.interpolation_methods]: No interpolation method parameter was given. Using the default, VARIABLE_DEGREE_SPLINE.
[ruby $(which ign) gazebo-1] [INFO] [1675263008.039751886] [joint_trajectory_controller]: Using 'splines' interpolation method.
[ruby $(which ign) gazebo-1] [INFO] [1675263008.040439275] [joint_trajectory_controller]: Controller state will be published at 50.00 Hz.
[ruby $(which ign) gazebo-1] [INFO] [1675263008.041057879] [joint_trajectory_controller]: Action status changes will be monitored at 20.00 Hz.
[ruby $(which ign) gazebo-1] [ERROR] [1675263008.053879538] [controller_manager]: Can't activate controller 'joint_trajectory_controller': Command interface with 'slider_to_cart/position' does not exist
[ros2-5] Sucessfully loaded controller joint_trajectory_controller into state active

Full log...

$ ros2 launch ign_ros2_control_demos cart_example_position.launch.py
[INFO] [launch]: All log files can be found below /home/azazdeaz/.ros/log/2023-02-01-15-49-57-389591-moveit2-humble.azazdeaz-Laptop-1155052
[INFO] [launch]: Default logging verbosity is set to INFO
ign_args is deprecated, migrate to gz_args!
[INFO] [ruby $(which ign) gazebo-1]: process started with pid [1155053]
[INFO] [robot_state_publisher-2]: process started with pid [1155055]
[INFO] [create-3]: process started with pid [1155058]
[robot_state_publisher-2] [INFO] [1675262997.828304377] [robot_state_publisher]: got segment cart
[robot_state_publisher-2] [INFO] [1675262997.828357569] [robot_state_publisher]: got segment slideBar
[robot_state_publisher-2] [INFO] [1675262997.828362748] [robot_state_publisher]: got segment world
[create-3] [INFO] [1675263005.856669348] [ros_gz_sim]: Requesting list of world names.
[ruby $(which ign) gazebo-1] Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway.
[ruby $(which ign) gazebo-1] [Dbg] [ign.cc:161] Subscribing to [/gazebo/starting_world].
[ruby $(which ign) gazebo-1] [Dbg] [ign.cc:163] Waiting for a world to be set from the GUI...
[ruby $(which ign) gazebo-1] [Msg] Received world [empty.sdf] from the GUI.
[ruby $(which ign) gazebo-1] [Dbg] [ign.cc:167] Unsubscribing from [/gazebo/starting_world].
[ruby $(which ign) gazebo-1] [Msg] Ignition Gazebo Server v6.14.0
[ruby $(which ign) gazebo-1] [Msg] Loading SDF world file[/usr/share/ignition/ignition-gazebo6/worlds/empty.sdf].
[ruby $(which ign) gazebo-1] [Msg] Serving entity system service on [/entity/system/add]
[ruby $(which ign) gazebo-1] [Dbg] [Physics.cc:803] Loaded [ignition::physics::dartsim::Plugin] from library [/usr/lib/x86_64-linux-gnu/ign-physics-5/engine-plugins/libignition-physics-dartsim-plugin.so]
[ruby $(which ign) gazebo-1] [Dbg] [SystemManager.cc:70] Loaded system [ignition::gazebo::systems::Physics] for entity [1]
[ruby $(which ign) gazebo-1] [Msg] Create service on [/world/empty/create]
[ruby $(which ign) gazebo-1] [Msg] Remove service on [/world/empty/remove]
[ruby $(which ign) gazebo-1] [Msg] Pose service on [/world/empty/set_pose]
[ruby $(which ign) gazebo-1] [Msg] Pose service on [/world/empty/set_pose_vector]
[ruby $(which ign) gazebo-1] [Msg] Light configuration service on [/world/empty/light_config]
[ruby $(which ign) gazebo-1] [Msg] Physics service on [/world/empty/set_physics]
[ruby $(which ign) gazebo-1] [Msg] SphericalCoordinates service on [/world/empty/set_spherical_coordinates]
[ruby $(which ign) gazebo-1] [Msg] Enable collision service on [/world/empty/enable_collision]
[ruby $(which ign) gazebo-1] [Msg] Disable collision service on [/world/empty/disable_collision]
[ruby $(which ign) gazebo-1] [Msg] Material service on [/world/empty/visual_config]
[ruby $(which ign) gazebo-1] [Msg] Material service on [/world/empty/wheel_slip]
[ruby $(which ign) gazebo-1] [Dbg] [SystemManager.cc:70] Loaded system [ignition::gazebo::systems::UserCommands] for entity [1]
[ruby $(which ign) gazebo-1] [Dbg] [SystemManager.cc:70] Loaded system [ignition::gazebo::systems::SceneBroadcaster] for entity [1]
[ruby $(which ign) gazebo-1] [Dbg] [SystemManager.cc:70] Loaded system [ignition::gazebo::systems::Contact] for entity [1]
[ruby $(which ign) gazebo-1] [Msg] Loaded level [3]
[ruby $(which ign) gazebo-1] [Msg] Serving world controls on [/world/empty/control], [/world/empty/control/state] and [/world/empty/playback/control]
[ruby $(which ign) gazebo-1] [Msg] Serving GUI information on [/world/empty/gui/info]
[ruby $(which ign) gazebo-1] [Msg] World [empty] initialized with [1ms] physics profile.
[ruby $(which ign) gazebo-1] [Msg] Serving world SDF generation service on [/world/empty/generate_world_sdf]
[ruby $(which ign) gazebo-1] [Msg] Serving world names on [/gazebo/worlds]
[ruby $(which ign) gazebo-1] [Msg] Resource path add service on [/gazebo/resource_paths/add].
[ruby $(which ign) gazebo-1] [Msg] Resource path get service on [/gazebo/resource_paths/get].
[create-3] [INFO] [1675263006.217760012] [ros_gz_sim]: Requested creation of entity.
[create-3] [INFO] [1675263006.217812114] [ros_gz_sim]: OK creation of entity.
[INFO] [create-3]: process has finished cleanly [pid 1155058]
[INFO] [ros2-4]: process started with pid [1155134]
[ruby $(which ign) gazebo-1] [INFO] [1675263006.920307121] [ignition_ros_control]: [ign_ros2_control] Fixed joint [world_to_base] (Entity=15)] is skipped
[ruby $(which ign) gazebo-1] [INFO] [1675263006.921807654] [ignition_ros_control]: connected to service!! robot_state_publisher asking for robot_description
[ruby $(which ign) gazebo-1] [INFO] [1675263006.922246452] [ignition_ros_control]: Received URDF from param server
[ruby $(which ign) gazebo-1] [INFO] [1675263006.926828816] [ignition_ros_control]: Loading joint: slider_to_cart
[ruby $(which ign) gazebo-1] [INFO] [1675263006.926848257] [ignition_ros_control]: 	State:
[ruby $(which ign) gazebo-1] [INFO] [1675263006.926858005] [ignition_ros_control]: 		 position
[ruby $(which ign) gazebo-1] [INFO] [1675263006.926905496] [ignition_ros_control]: 			 found initial value: -5.000000
[ruby $(which ign) gazebo-1] [INFO] [1675263006.926913277] [ignition_ros_control]: 		 velocity
[ruby $(which ign) gazebo-1] [INFO] [1675263006.926933040] [ignition_ros_control]: 		 effort
[ruby $(which ign) gazebo-1] [INFO] [1675263006.926942928] [ignition_ros_control]: 	Command:
[ruby $(which ign) gazebo-1] [INFO] [1675263006.926947060] [ignition_ros_control]: 		 position
[ruby $(which ign) gazebo-1] [INFO] [1675263006.927433539] [resource_manager]: Initialize hardware 'IgnitionSystem'
[ruby $(which ign) gazebo-1] [WARN] [1675263006.927442964] [ignition_ros_control]: On init...
[ruby $(which ign) gazebo-1] [INFO] [1675263006.927604309] [resource_manager]: Successful initialization of hardware 'IgnitionSystem'
[ruby $(which ign) gazebo-1] [INFO] [1675263006.927643097] [ignition_ros_control]: Loading controller_manager
[ruby $(which ign) gazebo-1] [WARN] [1675263006.939326106] [ignition_ros_control]:  Desired controller update period (0.01 s) is slower than the gazebo simulation period (0.001 s).
[ruby $(which ign) gazebo-1] [INFO] [1675263007.076156142] [controller_manager]: Loading controller 'joint_state_broadcaster'
[ruby $(which ign) gazebo-1] [INFO] [1675263007.089760367] [controller_manager]: Configuring controller 'joint_state_broadcaster'
[ruby $(which ign) gazebo-1] [INFO] [1675263007.089878783] [joint_state_broadcaster]: 'joints' or 'interfaces' parameter is empty. All available state interfaces will be published
[ruby $(which ign) gazebo-1] [ERROR] [1675263007.104400708] [joint_state_broadcaster]: None of requested interfaces exist. Controller will not run.
[ruby $(which ign) gazebo-1] [WARN] [1675263007.104440229] []: Error occurred while doing error handling.
[ruby $(which ign) gazebo-1] [ERROR] [1675263007.104457272] [controller_manager]: After activating, controller 'joint_state_broadcaster' is in state 'unconfigured', expected Active
[ros2-4] Sucessfully loaded controller joint_state_broadcaster into state active
[INFO] [ros2-4]: process has finished cleanly [pid 1155134]
[INFO] [ros2-5]: process started with pid [1155171]
[ruby $(which ign) gazebo-1] [INFO] [1675263008.025939674] [controller_manager]: Loading controller 'joint_trajectory_controller'
[ruby $(which ign) gazebo-1] [INFO] [1675263008.030003948] [joint_trajectory_controller.interpolation_methods]: No interpolation method parameter was given. Using the default, VARIABLE_DEGREE_SPLINE.
[ruby $(which ign) gazebo-1] [INFO] [1675263008.039644914] [controller_manager]: Configuring controller 'joint_trajectory_controller'
[ruby $(which ign) gazebo-1] [INFO] [1675263008.039716655] [joint_trajectory_controller]: No specific joint names are used for command interfaces. Using 'joints' parameter.
[ruby $(which ign) gazebo-1] [INFO] [1675263008.039736852] [joint_trajectory_controller]: Command interfaces are [position] and state interfaces are [position velocity].
[ruby $(which ign) gazebo-1] [INFO] [1675263008.039749101] [joint_trajectory_controller.interpolation_methods]: No interpolation method parameter was given. Using the default, VARIABLE_DEGREE_SPLINE.
[ruby $(which ign) gazebo-1] [INFO] [1675263008.039751886] [joint_trajectory_controller]: Using 'splines' interpolation method.
[ruby $(which ign) gazebo-1] [INFO] [1675263008.040439275] [joint_trajectory_controller]: Controller state will be published at 50.00 Hz.
[ruby $(which ign) gazebo-1] [INFO] [1675263008.041057879] [joint_trajectory_controller]: Action status changes will be monitored at 20.00 Hz.
[ruby $(which ign) gazebo-1] [ERROR] [1675263008.053879538] [controller_manager]: Can't activate controller 'joint_trajectory_controller': Command interface with 'slider_to_cart/position' does not exist
[ros2-5] Sucessfully loaded controller joint_trajectory_controller into state active
[ruby $(which ign) gazebo-1] _IceTransSocketUNIXConnect: Cannot connect to non-local host azazdeaz-Laptop
[INFO] [ros2-5]: process has finished cleanly [pid 1155171]
[ruby $(which ign) gazebo-1] _IceTransSocketUNIXConnect: Cannot connect to non-local host azazdeaz-Laptop
[ruby $(which ign) gazebo-1] Qt: Session management error: Could not open network socket
[ruby $(which ign) gazebo-1] [GUI] [Wrn] [Application.cc:797] [QT] qrc:/qml/StyleDialog.qml:112:3: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo() { ... }
[ruby $(which ign) gazebo-1] [GUI] [Wrn] [Application.cc:797] [QT] qrc:/qml/StyleDialog.qml:105:3: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo() { ... }
[ruby $(which ign) gazebo-1] [GUI] [Wrn] [Application.cc:797] [QT] qrc:/qml/StyleDialog.qml:98:3: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo() { ... }
[ruby $(which ign) gazebo-1] [GUI] [Wrn] [Application.cc:797] [QT] qrc:qml/Main.qml:102:3: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo() { ... }
[ruby $(which ign) gazebo-1] [GUI] [Wrn] [Application.cc:797] [QT] qrc:/qml/PluginMenu.qml:27:3: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo() { ... }
[ruby $(which ign) gazebo-1] [GUI] [Wrn] [Application.cc:797] [QT] file::/Gazebo/GazeboDrawer.qml:241:3: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo() { ... }
[ruby $(which ign) gazebo-1] [GUI] [Wrn] [Application.cc:797] [QT] file::/Gazebo/GazeboDrawer.qml:147:3: QML Dialog: Binding loop detected for property "implicitHeight"
[ruby $(which ign) gazebo-1] [GUI] [Wrn] [Application.cc:797] [QT] file::/Gazebo/GazeboDrawer.qml:147:3: QML Dialog: Binding loop detected for property "implicitHeight"
[ruby $(which ign) gazebo-1] [GUI] [Wrn] [Application.cc:797] [QT] file::/EntityContextMenuPlugin/EntityContextMenuPlugin.qml:57:5: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo() { ... }
[ruby $(which ign) gazebo-1] [GUI] [Wrn] [Application.cc:797] [QT] file::/EntityContextMenuPlugin/EntityContextMenuPlugin.qml:52:3: QML RenderWindowOverlay: Detected anchors on an item that is managed by a layout. This is undefined behavior; use Layout.alignment instead.
[ruby $(which ign) gazebo-1] [GUI] [Wrn] [Application.cc:797] [QT] file::/EntityContextMenuPlugin/EntityContextMenuPlugin.qml:67:3: QML EntityContextMenu: Detected anchors on an item that is managed by a layout. This is undefined behavior; use Layout.alignment instead.
[ruby $(which ign) gazebo-1] [GUI] [Wrn] [Application.cc:797] [QT] file::/EntityContextMenuPlugin/EntityContextMenuPlugin.qml:52:3: QML RenderWindowOverlay: Detected anchors on an item that is managed by a layout. This is undefined behavior; use Layout.alignment instead.
[ruby $(which ign) gazebo-1] [GUI] [Wrn] [Application.cc:797] [QT] file::/EntityContextMenuPlugin/EntityContextMenuPlugin.qml:67:3: QML EntityContextMenu: Detected anchors on an item that is managed by a layout. This is undefined behavior; use Layout.alignment instead.
[ruby $(which ign) gazebo-1] [GUI] [Wrn] [Application.cc:797] [QT] file::/EntityContextMenuPlugin/EntityContextMenuPlugin.qml:52:3: QML RenderWindowOverlay: Detected anchors on an item that is managed by a layout. This is undefined behavior; use Layout.alignment instead.
[ruby $(which ign) gazebo-1] [GUI] [Wrn] [Application.cc:797] [QT] file::/EntityContextMenuPlugin/EntityContextMenuPlugin.qml:67:3: QML EntityContextMenu: Detected anchors on an item that is managed by a layout. This is undefined behavior; use Layout.alignment instead.
[ruby $(which ign) gazebo-1] [GUI] [Wrn] [Application.cc:797] [QT] file::/EntityContextMenuPlugin/EntityContextMenuPlugin.qml:52:3: QML RenderWindowOverlay: Detected anchors on an item that is managed by a layout. This is undefined behavior; use Layout.alignment instead.
[ruby $(which ign) gazebo-1] [GUI] [Wrn] [Application.cc:797] [QT] file::/EntityContextMenuPlugin/EntityContextMenuPlugin.qml:67:3: QML EntityContextMenu: Detected anchors on an item that is managed by a layout. This is undefined behavior; use Layout.alignment instead.
[ruby $(which ign) gazebo-1] [GUI] [Wrn] [Application.cc:797] [QT] file::/EntityContextMenuPlugin/EntityContextMenuPlugin.qml:52:3: QML RenderWindowOverlay: Detected anchors on an item that is managed by a layout. This is undefined behavior; use Layout.alignment instead.
[ruby $(which ign) gazebo-1] [GUI] [Wrn] [Application.cc:797] [QT] file::/EntityContextMenuPlugin/EntityContextMenuPlugin.qml:67:3: QML EntityContextMenu: Detected anchors on an item that is managed by a layout. This is undefined behavior; use Layout.alignment instead.
[ruby $(which ign) gazebo-1] [GUI] [Wrn] [Application.cc:797] [QT] file::/EntityContextMenuPlugin/EntityContextMenuPlugin.qml:52:3: QML RenderWindowOverlay: Detected anchors on an item that is managed by a layout. This is undefined behavior; use Layout.alignment instead.
[ruby $(which ign) gazebo-1] [GUI] [Wrn] [Application.cc:797] [QT] file::/EntityContextMenuPlugin/EntityContextMenuPlugin.qml:67:3: QML EntityContextMenu: Detected anchors on an item that is managed by a layout. This is undefined behavior; use Layout.alignment instead.
[ruby $(which ign) gazebo-1] [Wrn] [Component.hh:144] Trying to serialize component with data type [N3sdf3v125WorldE], which doesn't have `operator<<`. Component will not be serialized.
[ruby $(which ign) gazebo-1] [Msg] Resource path resolve service on [/gazebo[Msg] Ignition Gazebo GUI    v6.14.0
[ruby $(which ign) gazebo-1] [Dbg] [Gui.cc:253] Waiting for subscribers to [/gazebo/starting_world]...
[ruby $(which ign) gazebo-1] [Dbg] [Application.cc:92] Initializing application.
[ruby $(which ign) gazebo-1] [GUI] [Dbg] [Application.cc:555] Create main window
[ruby $(which ign) gazebo-1] [GUI] [Dbg] [PathManager.cc:66] Requesting resource paths through [/gazebo/resource_paths/get]
[ruby $(which ign) gazebo-1] [GUI] [Dbg] [Gui.cc:333] GUI requesting list of world names. The server may be busy downloading resources. Please be patient.
[ruby $(which ign) gazebo-1] [GUI] [Dbg] [PathManager.cc:55] Received resource paths.
[ruby $(which ign) gazebo-1] [GUI] [Dbg] [Gui.cc:391] Requesting GUI from [/world/empty/gui/info]...
[ruby $(which ign) gazebo-1] [GUI] [Dbg] [GuiRunner.cc:145] Requesting initial state from [/world/empty/state]...
[ruby $(which ign) gazebo-1] [GUI] [Msg] Loading config [/home/azazdeaz/.ignition/gazebo/6/gui.config]
[ruby $(which ign) gazebo-1] [GUI] [Dbg] [Application.cc:426] Loading plugin [MinimalScene]
[ruby $(which ign) gazebo-1] [GUI] [Msg] Added plugin [3D View] to main window
[ruby $(which ign) gazebo-1] [GUI] [Msg] Loaded plugin [MinimalScene] from path [/usr/lib/x86_64-linux-gnu/ign-gui-6/plugins/libMinimalScene.so]
[ruby $(which ign) gazebo-1] [GUI] [Dbg] [Application.cc:426] Loading plugin [EntityContextMenuPlugin]
[ruby $(which ign) gazebo-1] [GUI] [Msg] Added plugin [Entity Context Menu] to main window
[ruby $(which ign) gazebo-1] [GUI] [Msg] Loaded plugin [EntityContextMenuPlugin] from path [/usr/lib/x86_64-linux-gnu/ign-gazebo-6/plugins/gui/libEntityContextMenuPlugin.so]
[ruby $(which ign) gazebo-1] [GUI] [Dbg] [Application.cc:426] Loading plugin [GzSceneManager]
[ruby $(which ign) gazebo-1] [GUI] [Msg] Added plugin [Scene Manager] to main window
[ruby $(which ign) gazebo-1] [GUI] [Msg] Loaded plugin [GzSceneManager] from path [/usr/lib/x86_64-linux-gnu/ign-gazebo-6/plugins/gui/libGzSceneManager.so]
[ruby $(which ign) gazebo-1] [GUI] [Dbg] [Application.cc:426] Loading plugin [InteractiveViewControl]
[ruby $(which ign) gazebo-1] [GUI] [Msg] Camera view controller topic advertised on [/gui/camera/view_control]
[ruby $(which ign) gazebo-1] [GUI] [Msg] Camera reference visual topic advertised on [/gui/camera/view_control/reference_visual]
[ruby $(which ign) gazebo-1] [GUI] [Msg] Camera view control sensitivity advertised on [/gui/camera/view_control/sensitivity]
[ruby $(which ign) gazebo-1] [GUI] [Msg] Added plugin [Interactive view control] to main window
[ruby $(which ign) gazebo-1] [GUI] [Msg] Loaded plugin [InteractiveViewControl] from path [/usr/lib/x86_64-linux-gnu/ign-gui-6/plugins/libInteractiveViewControl.so]
[ruby $(which ign) gazebo-1] [GUI] [Dbg] [Application.cc:426] Loading plugin [CameraTracking]
[ruby $(which ign) gazebo-1] [GUI] [Msg] Added plugin [Camera tracking] to main window
[ruby $(which ign) gazebo-1] [GUI] [Msg] Loaded plugin [CameraTracking] from path [/usr/lib/x86_64-linux-gnu/ign-gui-6/plugins/libCameraTracking.so]
[ruby $(which ign) gazebo-1] [GUI] [Wrn] [Application.cc:797] [QT] file::/Spawn/Spawn.qml:32:3: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo() { ... }
[ruby $(which ign) gazebo-1] [GUI] [Wrn] [Application.cc:797] [QT] file::/WorldControl/WorldControl.qml:30:3: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo() { ... }
[ruby $(which ign) gazebo-1] [GUI] [Dbg] [Application.cc:426] Loading plugin [MarkerManager]
[ruby $(which ign) gazebo-1] [GUI] [Msg] Listening to stats on [/world/empty/stats]
[ruby $(which ign) gazebo-1] [GUI] [Msg] Added plugin [Marker Manager] to main window
[ruby $(which ign) gazebo-1] [GUI] [Msg] Loaded plugin [MarkerManager] from path [/usr/lib/x86_64-linux-gnu/ign-gui-6/plugins/libMarkerManager.so]
[ruby $(which ign) gazebo-1] [GUI] [Dbg] [Application.cc:426] Loading plugin [SelectEntities]
[ruby $(which ign) gazebo-1] [GUI] [Msg] Added plugin [Select entities] to main window
[ruby $(which ign) gazebo-1] [GUI] [Msg] Loaded plugin [SelectEntities] from path [/usr/lib/x86_64-linux-gnu/ign-gazebo-6/plugins/gui/libSelectEntities.so]
[ruby $(which ign) gazebo-1] [GUI] [Dbg] [Application.cc:426] Loading plugin [Spawn]
[ruby $(which ign) gazebo-1] [GUI] [Msg] Added plugin [Spawn] to main window
[ruby $(which ign) gazebo-1] [GUI] [Msg] Loaded plugin [Spawn] from path [/usr/lib/x86_64-linux-gnu/ign-gazebo-6/plugins/gui/libSpawn.so]
[ruby $(which ign) gazebo-1] [GUI] [Dbg] [Application.cc:426] Loading plugin [VisualizationCapabilities]
[ruby $(which ign) gazebo-1] [GUI] [Msg] View as transparent service on [/gui/view/transparent]
[ruby $(which ign) gazebo-1] [GUI] [Msg] View as wireframes service on [/gui/view/wireframes]
[ruby $(which ign) gazebo-1] [GUI] [Msg] View center of mass service on [/gui/view/com]
[ruby $(which ign) gazebo-1] [GUI] [Msg] View inertia service on [/gui/view/inertia]
[ruby $(which ign) gazebo-1] [GUI] [Msg] View collisions service on [/gui/view/collisions]
[ruby $(which ign) gazebo-1] [GUI] [Msg] View joints service on [/gui/view/joints]
[ruby $(which ign) gazebo-1] [GUI] [Msg] View frames service on [/gui/view/frames]
[ruby $(which ign) gazebo-1] [GUI] [Msg] Added plugin [Visualization capabilities] to main window
[ruby $(which ign) gazebo-1] [GUI] [Msg] Loaded plugin [VisualizationCapabilities] from path [/usr/lib/x86_64-linux-gnu/ign-gazebo-6/plugins/gui/libVisualizationCapabilities.so]
[ruby $(which ign) gazebo-1] [GUI] [Dbg] [Application.cc:426] Loading plugin [WorldControl]
[ruby $(which ign) gazebo-1] [GUI] [Msg] Using world control service [/world/empty/control]
[ruby $(which ign) gazebo-1] [GUI] [Msg] Listening to stats on [/world/empty/stats]
[ruby $(which ign) gazebo-1] [GUI] [Dbg] [WorldControl.cc:246] Using an event to share WorldControl msgs with the server
[ruby $(which ign) gazebo-1] [GUI] [Msg] Added plugin [World control] to main window
[ruby $(which ign) gazebo-1] [GUI] [Msg] Loaded plugin [WorldControl] from path [/usr/lib/x86_64-linux-gnu/ign-gui-6/plugins/libWorldControl.so]
[ruby $(which ign) gazebo-1] [GUI] [Dbg] [Application.cc:426] Loading plugin [WorldStats]
[ruby $(which ign) gazebo-1] [GUI] [Msg] Listening to stats on [/world/empty/stats]
[ruby $(which ign) gazebo-1] [GUI] [Msg] Added plugin [World stats] to main window
[ruby $(which ign) gazebo-1] [GUI] [Wrn] [Application.cc:797] [QT] file::/TransformControl/TransformControl.qml:104:3: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo() { ... }
[ruby $(which ign) gazebo-1] [GUI] [Wrn] [Application.cc:797] [QT] file::/TransformControl/TransformControl.qml:99:3: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo() { ... }
[ruby $(which ign) gazebo-1] [GUI] [Wrn] [Application.cc:797] [QT] file::/TransformControl/TransformControl.qml:94:3: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo() { ... }
[ruby $(which ign) gazebo-1] [GUI] [Wrn] [Application.cc:797] [QT] file::/TransformControl/TransformControl.qml:89:3: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo() { ... }
[ruby $(which ign) gazebo-1] [GUI] [Wrn] [Application.cc:797] [QT] file::/EntityTree/EntityTree.qml:148:7: QML ToolButton: Detected anchors on an item that is managed by a layout. This is undefined behavior; use Layout.alignment instead.
[ruby $(which ign) gazebo-1] [GUI] [Wrn] [Component.hh:189] Trying to deserialize component with data type [N3sdf3v125WorldE], which doesn't have `operator>>`. Component will not be deserialized.
[ruby $(which ign) gazebo-1] [GUI] [Wrn] [Application.cc:797] [QT] file::/WorldStats/WorldStats.qml:53:3: QML RowLayout: Binding loop detected for property "x"
[ruby $(which ign) gazebo-1] [GUI] [Wrn] [Application.cc:797] [QT] file::/EntityContextMenuPlugin/EntityContextMenuPlugin.qml:52:3: QML RenderWindowOverlay: Detected anchors on an item that is managed by a layout. This is undefined behavior; use Layout.alignment instead.
[ruby $(which ign) gazebo-1] [GUI] [Wrn] [Application.cc:797] [QT] file::/EntityContextMenuPlugin/EntityContextMenuPlugin.qml:67:3: QML EntityContextMenu: Detected anchors on an item that is managed by a layout. This is undefined behavior; use Layout.alignment instead.
[ruby $(which ign) gazebo-1] [GUI] [Wrn] [Application.cc:797] [QT] file::/Gazebo/GazeboDrawer.qml:147:3: QML Dialog: Binding loop detected for property "implicitHeight"
[ruby $(which ign) gazebo-1] ../src/intel/isl/isl.c:2220: FINISHME: ../src/intel/isl/isl.c:isl_surf_supports_ccs: CCS for 3D textures is disabled, but a workaround is available.
[ruby $(which ign) gazebo-1] [GUI] [Msg] Loaded plugin [WorldStats] from path [/usr/lib/x86_64-linux-gnu/ign-gui-6/plugins/libWorldStats.so]
[ruby $(which ign) gazebo-1] [GUI] [Dbg] [Application.cc:426] Loading plugin [Shapes]
[ruby $(which ign) gazebo-1] [GUI] [Msg] Added plugin [Shapes] to main window
[ruby $(which ign) gazebo-1] [GUI] [Msg] Loaded plugin [Shapes] from path [/usr/lib/x86_64-linux-gnu/ign-gazebo-6/plugins/gui/libShapes.so]
[ruby $(which ign) gazebo-1] [GUI] [Dbg] [Application.cc:426] Loading plugin [Lights]
[ruby $(which ign) gazebo-1] [GUI] [Msg] Added plugin [Lights] to main window
[ruby $(which ign) gazebo-1] [GUI] [Msg] Loaded plugin [Lights] from path [/usr/lib/x86_64-linux-gnu/ign-gazebo-6/plugins/gui/libLights.so]
[ruby $(which ign) gazebo-1] [GUI] [Dbg] [Application.cc:426] Loading plugin [TransformControl]
[ruby $(which ign) gazebo-1] [GUI] [Dbg] [TransformControl.cc:219] Legacy mode is disabled; this plugin must be used with MinimalScene.
[ruby $(which ign) gazebo-1] [GUI] [Msg] Added plugin [Transform control] to main window
[ruby $(which ign) gazebo-1] [GUI] [Msg] Loaded plugin [TransformControl] from path [/usr/lib/x86_64-linux-gnu/ign-gazebo-6/plugins/gui/libTransformControl.so]
[ruby $(which ign) gazebo-1] [GUI] [Dbg] [Application.cc:426] Loading plugin [Screenshot]
[ruby $(which ign) gazebo-1] [GUI] [Msg] Screenshot service on [/gui/screenshot]
[ruby $(which ign) gazebo-1] [GUI] [Msg] Added plugin [Screenshot] to main window
[ruby $(which ign) gazebo-1] [GUI] [Msg] Loaded plugin [Screenshot] from path [/usr/lib/x86_64-linux-gnu/ign-gui-6/plugins/libScreenshot.so]
[ruby $(which ign) gazebo-1] [GUI] [Dbg] [Application.cc:426] Loading plugin [CopyPaste]
[ruby $(which ign) gazebo-1] [GUI] [Msg] Added plugin [Copy/Paste] to main window
[ruby $(which ign) gazebo-1] [GUI] [Msg] Loaded plugin [CopyPaste] from path [/usr/lib/x86_64-linux-gnu/ign-gazebo-6/plugins/gui/libCopyPaste.so]
[ruby $(which ign) gazebo-1] [GUI] [Dbg] [Application.cc:426] Loading plugin [ComponentInspector]
[ruby $(which ign) gazebo-1] [GUI] [Msg] Added plugin [Component inspector] to main window
[ruby $(which ign) gazebo-1] [GUI] [Msg] Loaded plugin [ComponentInspector] from path [/usr/lib/x86_64-linux-gnu/ign-gazebo-6/plugins/gui/libComponentInspector.so]
[ruby $(which ign) gazebo-1] [GUI] [Dbg] [Application.cc:426] Loading plugin [EntityTree]
[ruby $(which ign) gazebo-1] [GUI] [Msg] Added plugin [Entity tree] to main window
[ruby $(which ign) gazebo-1] [GUI] [Msg] Loaded plugin [EntityTree] from path [/usr/lib/x86_64-linux-gnu/ign-gazebo-6/plugins/gui/libEntityTree.so]
[ruby $(which ign) gazebo-1] [GUI] [Dbg] [Application.cc:296] Loading window config
[ruby $(which ign) gazebo-1] [GUI] [Msg] Using server control service [/server_control]
[ruby $(which ign) gazebo-1] [GUI] [Dbg] [Application.cc:569] Applying config
[ruby $(which ign) gazebo-1] [GUI] [Msg] Loading plugin [ignition-rendering-ogre2]
[ruby $(which ign) gazebo-1] [GUI] [Dbg] [MinimalScene.cc:602] Create scene [scene]
[ruby $(which ign) gazebo-1] [GUI] [Msg] Loading plugin [ignition-rendering-ogre2]

Running the example node returns:
$ ros2 run ign_ros2_control_demos example_position
node created
Created action server
Goal rejected
[ERROR] [1675264257.441733831] [trajectory_test_node]: send goal call ok :)
[ERROR] [1675264257.441800805] [trajectory_test_node]: Goal was rejected by server
cannot publish data, at ./src/rmw_publish.cpp:62 during '__function__'
[ERROR] [1675264257.544083616] [trajectory_test_node.rclcpp]: Error in destruction of rcl subscription handle: Failed to delete datareader, at ./src/subscription.cpp:52, at ./src/rcl/subscription.c:183
cannot publish data, at ./src/rmw_publish.cpp:62 during '__function__'
Fail in delete datareader, at ./src/rmw_service.cpp:104 during '__function__'
[ros2run]: Segmentation fault

Environment

osrf/ros:humble-desktop Docker image running in Distrobox
Ignition Fortress binary install
https://github.com/ros-controls/gz_ros2_control humble branch https://github.com/ros-controls/gz_ros2_control/commit/b0c29c2f3245eca25753fbe2527eeacc7cb9dac0

ros2 control outputs:
$ ros2 control list_controllers
joint_state_broadcaster[joint_state_broadcaster/JointStateBroadcaster] unconfigured
joint_trajectory_controller[joint_trajectory_controller/JointTrajectoryController] inactive

$ ros2 control list_controller_types
controller_manager/test_controller                                     controller_interface::ControllerInterface
controller_manager/test_controller_failed_init                         controller_interface::ControllerInterface
controller_manager/test_controller_with_interfaces                     controller_interface::ControllerInterface
diff_drive_controller/DiffDriveController                              controller_interface::ControllerInterface
effort_controllers/GripperActionController                             controller_interface::ControllerInterface
effort_controllers/JointGroupEffortController                          controller_interface::ControllerInterface
forward_command_controller/ForwardCommandController                    controller_interface::ControllerInterface
forward_command_controller/MultiInterfaceForwardCommandController      controller_interface::ControllerInterface
imu_sensor_broadcaster/IMUSensorBroadcaster                            controller_interface::ControllerInterface
joint_state_broadcaster/JointStateBroadcaster                          controller_interface::ControllerInterface
joint_trajectory_controller/JointTrajectoryController                  controller_interface::ControllerInterface
position_controllers/GripperActionController                           controller_interface::ControllerInterface
tricycle_controller/TricycleController                                 controller_interface::ControllerInterface
velocity_controllers/JointGroupVelocityController                      controller_interface::ControllerInterface
controller_manager/test_chainable_controller                           controller_interface::ChainableControllerInterface

Some warnings i got during colcon build

$ IGNITION_VERSION=fortress colcon build --symlink-install
Starting >>> ign_ros2_control
[0.220s] WARNING:colcon.colcon_ros.prefix_path.ament:The path '/home/azazdeaz/repos/temp/gz-ros2-controls-ws/install/ign_ros2_control' in the environment variable AMENT_PREFIX_PATH doesn't exist
[0.220s] WARNING:colcon.colcon_ros.prefix_path.ament:The path '/home/azazdeaz/repos/temp/gz-ros2-controls-ws/install/ign_ros2_control_demos' in the environment variable AMENT_PREFIX_PATH doesn't exist
[0.221s] WARNING:colcon.colcon_ros.prefix_path.catkin:The path '/home/azazdeaz/repos/temp/gz-ros2-controls-ws/install/ign_ros2_control' in the environment variable CMAKE_PREFIX_PATH doesn't exist
[0.221s] WARNING:colcon.colcon_ros.prefix_path.catkin:The path '/home/azazdeaz/repos/temp/gz-ros2-controls-ws/install/ign_ros2_control_demos' in the environment variable CMAKE_PREFIX_PATH doesn't exist
--- stderr: ign_ros2_control
/home/azazdeaz/repos/temp/gz-ros2-controls-ws/src/gz_ros2_control/ign_ros2_control/src/ign_system.cpp: In member function ‘virtual hardware_interface::return_type ign_ros2_control::IgnitionSystem::read(const rclcpp::Time&, const rclcpp::Duration&)’:
/home/azazdeaz/repos/temp/gz-ros2-controls-ws/src/gz_ros2_control/ign_ros2_control/src/ign_system.cpp:407:24: warning: unused parameter ‘time’ [-Wunused-parameter]
  407 |   const rclcpp::Time & time,
      |   ~~~~~~~~~~~~~~~~~~~~~^~~~
/home/azazdeaz/repos/temp/gz-ros2-controls-ws/src/gz_ros2_control/ign_ros2_control/src/ign_system.cpp:408:28: warning: unused parameter ‘period’ [-Wunused-parameter]
  408 |   const rclcpp::Duration & period)
      |   ~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~
/home/azazdeaz/repos/temp/gz-ros2-controls-ws/src/gz_ros2_control/ign_ros2_control/src/ign_system.cpp: In member function ‘virtual hardware_interface::return_type ign_ros2_control::IgnitionSystem::write(const rclcpp::Time&, const rclcpp::Duration&)’:
/home/azazdeaz/repos/temp/gz-ros2-controls-ws/src/gz_ros2_control/ign_ros2_control/src/ign_system.cpp:452:24: warning: unused parameter ‘time’ [-Wunused-parameter]
  452 |   const rclcpp::Time & time,
      |   ~~~~~~~~~~~~~~~~~~~~~^~~~
/home/azazdeaz/repos/temp/gz-ros2-controls-ws/src/gz_ros2_control/ign_ros2_control/src/ign_system.cpp:453:28: warning: unused parameter ‘period’ [-Wunused-parameter]
  453 |   const rclcpp::Duration & period)
      |   ~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~
---
Finished <<< ign_ros2_control [11.1s]
Starting >>> ign_ros2_control_demos
Finished <<< ign_ros2_control_demos [4.89s]
Summary: 2 packages finished [16.1s]
1 package had stderr output: ign_ros2_control

Prior errors i fixed with small changes:
[INFO] [launch]: Default logging verbosity is set to INFO
ign_args is deprecated, migrate to gz_args!
[INFO] [ruby $(which ign) gazebo-1]: process started with pid [967136]
[INFO] [robot_state_publisher-2]: process started with pid [967139]
[INFO] [create-3]: process started with pid [967141]
[create-3] [ros_ign_gazebo] is deprecated! Redirecting to use [ros_gz_sim] instead!
[create-3]
[create-3] sh: 1: Syntax error: redirection unexpected
[INFO] [create-3]: process has finished cleanly [pid 967141]

Replaced ros_ign_gazebo with ros_gz_sim in the launch file.

[ros2-5] ros2 control load_controller: error: argument --set-state: invalid choice: 'start' (choose from 'configured', 'active')

Replaced start with active in the ros2 control load_controller --set-state start calls

Thanks in advance for any help!

The humble branch uses rolling for the CI tests: https://github.com/ros-controls/gz_ros2_control/blob/humble/.github/workflows/ci.yaml#L46 Is this package expected to work with ROS2 Humble?
Additional info - the galactic branch runs the examples seemingly without errors on the osrf/ros:galactic-desktop base image with ignition fortress. (Although only the velocity and effort examples make things move in Ign-Gazebo, the diff-drive and position examples don't move the models and show no errors)

I am having the same issue - with identical error logs. I am trying to run this package on Ubuntu 22.04  with binary install of both ROS2 Humble and Ignition Fortress.

I got some of the examples working with Humble by checking out the commit https://github.com/ros-controls/gz_ros2_control/commit/b296ff2f5c3758b637a70bd496fe6ed875ab03ce (as suggested in https://github.com/ros-controls/gz_ros2_control/issues/112) and adding the changes mentioned above.

Thanks for looking into this guys.
In general the humble release has been tricky due to some buildfarm issues, sorry for the inconvenience caused.
Provided you've got a working version already...  could you please try identifying the offending changes? Or... I'm also tempted to make a harsher fix and simply recreate the humble branch from the commit you guys mentioned above.

I cherry-picked a few commits from the master branch into the humble branch and that fixed the example demos for me. I created a PR: #118

Ping @azazdeaz @danilo-pejovic , could you guys please confirm if you are happy with the changes from #118 ?

@bmagyar the examples are working for me :+1:  Thanks, @iche033!
The tricycle example was added to the readme, but the source was missing, so i created ar PR with the cherry-picked commit: https://github.com/ros-controls/gz_ros2_control/pull/119

Examples seem to run fine on my end with #119 - I didnt have time yet to test all capabilities but I see no reason why wont work as expected now.
Thanks!


Place MapboxGeocoder into React (MUI) component

Currently MapboxGeocoder is a built-in Mapbox control:
mapRef.current.addControl(         new MapboxGeocoder({
This limits our facility of styling and customising behaviour. We can instead host inside a MUI container to match the look and feel of the rest of the app, following an approach similar to:
https://github.com/SamSamskies/react-map-gl-geocoder

Hi @deepanshu44, I'm not sure if you are also looking at this one? If so, I saw this interesting approach:
https://github.com/wheredoesyourmindgo/react-mui-mapbox-geocoder
and it looks like we can adapt and make use of the MUI Autocomplete.
I've been playing around and I have something working. I'll make a PR and put you as reviewer; you might have some better ideas!


Script loading is not synchronous

There is a bug in _loadFromCache in the script component which means loaded scripts are not found in the resource loader cache. This means script components are always loaded asynchronously.

Fixed in https://github.com/playcanvas/engine/commit/873630dabfb045c3a04b38aaa4a4dcace08ceec6


Master clang cl

I know you from somewhere? :-)
Merging.

I know you from somewhere? :-)
Merging.

Maybe, I'm from Montreal :)

You are? If not for the virus, I’d invite you for coffee.

You are? If not for the virus, I’d invite you for coffee.

Would be my pleasure. Lately, I'm mostly away for work (California), but currently stuck in Asia


Update start/stop times view

Closes #1007

Please, make the branch up to date with develop and this is good to go.


Q: passing warp a path or a glyph from a svg font, instead of a full svg.

This is a question, not an issue.
I would like to use warp on a single glyph from a .svg font, in a node script.
Right now I am loading the .svg font file as a string, looping over the glyphs, and doing things to each glyph's 'd' parameter data. This is the path that draws the glyph.
I would like to pass either the path(as string) or the glyph (as a string) to the warp object, manipulate it, and then return the path/glyp (still as string) so I can update it on the string that represents the font file and then write it to disk.
Can this be done, or does warp need the full svg? Also, can I pass string to warp, and how do I return it or update it ?
Thank you

This is a shortened example of how the script works, I am using cheerio .
const cheerio = require('cheerio');
const args = process.argv.slice(2);
var fs = require('fs');
var svg2ttf = require('svg2ttf');

fs.readFile(args[0], function read(err, data) {
	if (err) {
            throw err;
	}
	// convert to string and pass to cheerio
	var svgFont = data.toString();
	const $ = cheerio.load(svgFont, {
		normalizeWhitespace: true,
		xmlMode: true
	});

	// loop all glyph tags
	$("glyph").each(function(i,el){
            var path = $(this).attr("d"); // the glyph's path
            //
            // DO THE WARP TO THE PATH???
            //
            $(this).attr("d", path); // update it
        })
        svgFont = $.xml(); // update the svg font string data as xml

	// write the font to disk as ttf
	var ttf = svg2ttf(svgFont, {});
	fs.writeFileSync(args[1], new Buffer(ttf.buffer));
}

Note that I don't currently see how to work with warpjs without it being done in a browser.  I've tried a few Node DOM parsers like JSDOM and domino, and no luck so far.  There are dependencies on SVG dom elements that don't appear to be available in these server-side DOMs.  I doubt Cheerio/htmlparser2 is much different.
Maybe @benjamminf has some thoughts on how one could use this library server side as it seems I'm not alone in needing this.

Bit late to the party here. But @jboarman you're right in this isn't very easily usable outside of the web browser. I had enough foresight to separate out the DOM-specific code from the algorithmic code, so you ~can~ get it to run in Node.js with a bit (or a lot) of bending. https://github.com/benjamminf/warpjs/tree/master/src/path contains all the code to parse/encode path strings, interpolate paths with points, and transform them with your custom transformer.
The things you'll be missing though are converting non-path elements to path elements, which is done in https://github.com/benjamminf/warpjs/blob/master/src/svg/normalize.js


Make DomainEvent.PartitionKey property virtual.

Sometimes events from different aggregates may have the same
partitioning key. So, make DomainEvent.PartitionKey property to virtual.
this resolves #31

@suhyeon Please add the test case for the change.

@gyuwon  Please check my test code..!!


Bug in the first project launch when getting information from the system

Pull Request:

https://github.com/MyLinuxProfile/linux-profile-basic/pull/27


trains-init asks web service URI but promp shows API URI

With trains-agent==0.15.0rc0
When executing trains-agent init:
TRAINS-AGENT setup process

Please create new trains credentials through the profile page in your trains web app (e.g. https://demoapp.trains.allegro.ai/profile)
In the profile page, press "Create new credentials", then press "Copy to clipboard".

Paste copied configuration here:

Could not parse credentials, please try entering them manually.
Enter user access key: *****
Enter user secret: *****

Editing configuration file: /Users/h4dr1en/trains.conf
Enter the url of the trains-server's Web service, for example: http://localhost:8080

API Host configured to: []

The user is asked to enter the the url of the trains-server's Web service, but the prompt message shows API Host configured to, which is not the same port (typically 8008 instead of 8080). This can be confusing for the user. It works well when entering the API URI (I did not test entering the web server URI).

Thanks @H4dr1en , you are absolutely correct .
I'll make sure we fix it :)

Hi @H4dr1en, just updating here,  v0.15 is out with a fixed wizard :)

Thanks, just tested, I still get:
Could not parse credentials, please try entering them manually.
Enter user access key: yx
Enter user secret: asd
Detected credentials key="yx" secret="asd***"

    Editing configuration file: /Users/H4dr1en/trains.conf
    Enter the url of the trains-server's Web service, for example: http://localhost:8080

API Host configured to: [] localhost:8080
Port 8080 is the web port. Using port 8008 for API Host and 8080 for Web Application Host
Web Application Host configured to: [http://localhost:8080]
File Store Host configured to: [http://localhost:8081]

@H4dr1en it was fixed in trains-agent init but not in trains init :cry:
I'll make sure trains is also fixed

Hi @H4dr1en,
trains 0.15.1rc0 is out with a matching fix, feel free to check trains-init :)

Awesome, closing here then 👍


Design System | UI Inventory

Will continue to take inventory of the components as Figma design library is being built.
Most current inventorying is of the buttons.

Will continue to take inventory of the components as Figma design library is being built.
Most current inventorying is of the buttons.


Minor typo fixes to map.md

Just some minor improvements to map.md

Thanks, the typos have been fixed by #134 and fdfa34d4453c2c02404a3e9b11384408323d8176


sync schema 2024-07-22.0

new layers: address and division_boundary

Thanks! Nice catch before we actually made the release announcement :)


about how to add GCN into my model

hello, when I'm implementing my own network(res101)with the GCN part attached , when I start training, the pytorch loss always happen to turn Nans, I watched the implementation of your code, which used mxnet and functions, I want to ask if something needs to be especially prepared when I put the GCN in a ResNet block(class but not function and without mxnet).

I met the same issue with you, but I ran it on 3D-Unet, I came across this whenever I add the global_reasoning_unit to the network, it work fine without it.A year later, the project got no response. Have you solve it?

I also met this problem,how to solve it


Categories in the ISCX VPN-NonVPN data

Most of the data is self explanatory, but the facebook_video and skype_video pcaps were categorized as chat or streaming or voip (but voip should be audio only). Which categories were they put into?

I am trying to reproduce the result for ISCX-VPN-NonVPN data. I have taken your pretrained model. Provided the session split pcaps using https://github.com/shramos/pcap-splitter/blob/master/pcap_splitter/splitter.py as input for main.py in the data_process and changed _category appropriately. I am directing the same tsv files to the run_classifier.py using the same command you provided in the readme. But the results are not similar to the ones reported. Is there any step that I am missing?

Most of the data is self explanatory, but the facebook_video and skype_video pcaps were categorized as chat or streaming or voip (but voip should be audio only). Which categories were they put into?

Information about the categories can be found in the previous related issues like #27  as well as in the descriptions on the official website.


[Enhancement] Method stores return result in local before immediately returning it [BatchMessage]

Search before asking

[X] I had searched in the issues and found no similar issues.

Enhancement Request

located at:
eventmesh-common/src/main/java/org/apache/eventmesh/common/protocol/grpc/protos/BatchMessage.java line<PHONE_NUMBER> 1834
analysis and explanation:
This method stores the return result in a local variable, and then immediately returns the local variable. It would be simpler just to return the value that is assigned to the local variable.
Describe the solution you'd like
Returns the value of a local variable directly.
reference:

Are you willing to submit PR?

[x] Yes I am willing to submit a PR!

I want to fix it.


[Design System] DCOS-18090 (2 of 4): add page for Buttons UI component

⚠ This PR depends on #2389
Adds the page for the Buttons UI component.
See branch tommy/design-system/remove-tabs for complete implementation.
Closes DCOS-18090

Checklist

[x] Did you add a JIRA issue in a commit message or as part of the branch name?
[ ] Did you add new unit tests?
[ ] Did you add new integration tests?
[ ] If this is a regression, did you write a test to catch this in the future?

Closing in favor of consolidation (https://github.com/dcos/dcos-ui/pull/2424) due to stagnation.


cloudflare_hostname_tls_setting available settings missing in documentation

Confirmation

[X] This is a bug with an existing resource and is not a feature request or enhancement. Feature requests should be submitted with Cloudflare Support or your account team.
[X] I have searched the issue tracker and my issue isn't already found.
[X] I have replicated my issue using the latest version of the provider and it is still present.

Terraform and Cloudflare provider version
v4.41.0
Affected resource(s)
cloudflare_hostname_tls_setting
Terraform configuration files
resource "cloudflare_hostname_tls_setting" "example" {
  zone_id  = "0da42c8d2132a9ddaf714f9e7c920711"
  hostname = "sub.example.com"
  setting  = "zero_rtt"
  value    = "off"
}

Link to debug output
n/A
Panic output
No response
Expected output
We expecte to have all the available settings that we can configure
Actual output
N/A
Steps to reproduce
N/A
Additional factoids
No response
References
No response

this isn't a bug but a request for enhancement of an existing resource.
given v5 will be automatically using our schemas (and get these enums by default), we're unlikely to solve this in the near future so i'd recommend relying on the API schema documentation to see all possible combinations or values - https://developers.cloudflare.com/api/operations/per-hostname-tls-settings-list


SyntaxError: Unexpected character '`'

Hello, i changed jade-loader to pug-loader, and my build doesn'to work now:
webpack config: http://pastebin.com/CWVx3v2S
Run:
./node_modules/.bin/webpack --progress --watch --inline -p --devtool

Code:
main.js:
var a = require('pug/timeline.pug')({
  table: 'table___3AgIg',
  date: 'date___2SiYk'
});

timeline.pug:
div(class=`${table} ${date}`)

Console:
ERROR in main.bundle.js from UglifyJs
SyntaxError: Unexpected character '`' [../~/pug-loader?{"pretty":true}!./pug/timeline.pug:4,0]

Tests:
YES:
  div(class=table)
    //-

  div(class=table + ' ' + date)
    //-

  div(class=`${'str'}`)
    //-

NO:
  div(class="#{table} #{date}")
    //-

  div(class='#{table} #{date}')
    //-

  div(class=`#{table} #{date}`)
    //-

  div(class="${table} ${date}")
    //-

  div(class='${table} ${date}')
    //-

ERROR: WHY ?????
  div(class=`${table} ${date}`)
    SyntaxError: Unexpected character '`' [../~/pug-loader?{"pretty":true}!./pug/timeline.pug:4,0]

And funny thing:
node pug_test.js :
var pug = require('pug');

var html = pug.renderFile('./src/pug/timeline.pug', {
	table: 'table___3AgIg',
	date: 'date___2SiYk'
});

console.dir(html);

Outputs:
'

'

This problem occurs only when im using -p parameter http://webpack.github.io/docs/cli.html#production-shortcut-p

@notiv-nt You can pipe pug-loader output to babel-loader:
{
    test: /\.pug$/, loader: 'babel-loader?presets[]=es2015!pug',
}

@JustinLivi would you mind elaborating why this necessary? This isn't SO, but some additional information would probably be helpful to understand the underlying issue. Thank you very much

Sure! You're right, I provided a workaround without really explaining the cause of the issue. The cause of the issue was the use of template literalls in the timeline.pug file:
div(class=`${table} ${date}`)

The error actually was not generated by pug-loader at all, but by UglifyJS (which I assume was further down the build pipeline). As far as I know, Uglify does not support template literals. Piping through the babel loader transpiles the template literals into ES5 string concatenation, which UglifyJS supports. I wonder if perhaps jade-loader automatically performed this transpilation?

I'm pretty sure at least the pug-loader does it automatically (now?), because I encountered the issue at hand only while building for production (including uglifyjs)

It's also possible that the template strings were passed through untouched, but you were testing in browsers that support template literals? Support in modern browsers is pretty good now: https://caniuse.com/#feat=template I'm not sure what other differences exist between your development and production pipeline.
One other thing which might help people in the future, is the loader string I provided should be the following when using webpack@3:
{
    test: /\.pug$/, loader: 'babel-loader?presets[]=es2015!pug-loader',
}

I was testing in the latest chrome version. however, in production, it didn't work either, only after applying the fix you posted, piping it through babel (which we are also using)

Hi! Late to the party, but I used the following configuration.
    loader: `babel-loader?presets[]=env!pug-loader`,

And use the new env way of doing things. This basically allowed us to use the same ESxx stuff we were using in the rest of the project. The problem isn't actually with Pug or the loader. I believe this should be done in Webpack / whatever build tool you're using.


feat(ngModel): support locals being passed through to ngChange

This is a WIP proposal for #14683.  If the approach seems acceptable, I'll write up accompanying unit tests and documentation.

I'm not a big fan of this tbh. Things I don't like:

It doesn't feel like a common feature. Besides it is doable outside the core.
The concept of locals is not the most trivial one to explain. This adds an overhead to simple concepts, such as ngChange.

--
Anyway, it is a tiny change with minimal overhead. So, if others think this "view value metadata" feature would be useful, I won't stand in your way :stuck_out_tongue:
--
Things I would consider:

Making the metadata available via locals as $metadata or $viewValueMetadata or something. This would use the same mechanism under the hood, but users don't have to understand scope evaluation and locals.
Passing the metadata as argument to all $viewChangeListeners.

It's more common for implementers of library controls with complex behaviors.
The two primary use cases that have come up for us are:

Selectable Behaviors: When a user shift clicks or ctrl clicks multiple items, the resulting ngModel value is the value extracted from an expression on those items.  It's useful to provide additional information about the operation though such as the value of the item that was actually clicked; that metadata is used to provide behaviors like scrolling the item fully into view in case it was partially clipped.

Drag and Drop - A similar thing, the ngModel value might be the values of the item(s) that were dropped, however additional metadata about the operation allows you to customize the behavior such as removing the item from the source if you're dragging between two lists.

These are admittedly not the common use case, but I figured it'd be worth seeing if others would find value in this.

I also don't feel very comfortable with this feature.
It would seem to me that a better place to do this is in a $parser. Then you can pass a complex object, containing the actual main value and any metadata, to the $setViewValue method and the $parser can do any special work that it wants before pulling out the main value and passing that down the pipeline.

Closing due to lack of response


[PE-D] Constraints on FORM_CLASS are too strict

Schools may adopt different ways of naming classes. Classes should not be limited to being names with |LEVEL|STRING|[ALPHANUMERIC]| as many schools have classes that are purely made up of numbers (eg. 210) to represent a class in secondary 2.

Labels: type.FeatureFlaw severity.Medium
original: neojxuan/ped#7

Make it of the form LEVEL [STRING]

We will acknowledge this as a feature flaw. I have added this to the user guide so I shall close this issue,


Submenu on mobile

Hi,
Thanks for the great project!
I have the following menu:
- Title
    - <Block src="FirstItem" />
    - <Block src="SecondItem" />

On desktop it works great, since I just need to hover "Title" to open the submenu. Yet, on mobile it should be possible to tap "Title" to open the submenu (if there is no link). It's not very accessible if nothing happens when tapping (and I don't want to create a page with just 2 items).
Is there an easy way to achieve this?
Thanks
Ben

You should be able to achieve this using a trigger prop on the NavMenu.

Find NavMenu component in content/blocks/header.mdx. (Note: there are two NavMenu components. Find the one for mobile - most probably the second one).
Add the following prop to it <NavMenu name={navName} gap={[0, 8]} borderTopWidth="1px" trigger="tap" />

This should do it. This way you can keep the hover trigger on desktop and use tap on mobile.

That was easy and works like a charm! Thank you so much!

Happy it worked.
Tip: Instead of having multiple <Block /> in your nav, you can use one Block and then embed multiple blocks inside. This would make it easier to theme/control the wrapper.
Example:
// content/navs/header.mdx
- [Home](/)
- [Page](/basic)
- [Blog](/blog)
- Title
  - <Block src="submenu-block" />

Then in content/blocks/submenu-block
<Div p="4">
  <Block src="first-item" />
  <Block src="second-item" />
</Div>

Great tip! Thanks!

Still trying to understand NavMenu (now in the footer). Is there some documentation for options?
I have such a menu
- Title
    - [Link1](/link1/)
    - [Link2](/link2/)

and I build it in the footer as follows
   <NavMenu
            name="footer-menu"
            dropdown={false}
            my="6|0"
            gap="4|10|18"
          />
`
``

As a result, "Title" appears as a link without any destination. Yet, "Title" shouldn't be a link (since it's confusing and bad UX). Any easy way to fix this?

Thanks so much!
Ben

@benbehringer hmm I can't reproduce this one. It's showing as a span for me (it does have a hover effect that makes it look like an a tag though).
For now the best place to look is the source code. https://github.com/reflexjs/reflex/blob/master/packages/gatsby-theme-nav/src/nav-menu.js#L179
Agree this needs better documentation (we're working on it).

Here's a demo:

I don't want the span to have a hover effect, since it is quite confusing. In fact, I recorded multiple sessions where people tried to click the span and then left the page (likely because of the frustrating UX).

Agreed. This is a bug. I'll create an issue and a fix.

Great! Thanks!

I pushed a fix for it and tagged a new release. You can upgrade: yarn upgrade @reflexjs/gatsby-theme-base.

The easiest way right now is to use style props for NavMenu and the sx props to target child elements.
<NavMenu
  gap="0|8"
  mr="null|10"
  sx={{
    color: "black",
    "a:hover, a[aria-current=page]": {
      color: "black",
      fontWeight: "semibold",
    },
  }}
/>

You can also shadow<EMAIL_ADDRESS>copy the content and add your style props to NavMenuLink, NavMenuItem..etc.
We are working on abstracting this a bit better so that it is easier to use style props on all elements.

Awesome! Keep up the good work! Thanks!

Closing this issue as fixed.


Suggestion: Full documentation via mdbook

Have you considered adding some documentation outside of the readme, potentially with mdbook?
I ask because the readme page is getting quite lengthy, but could probably use some more detail in places like error code descriptions, command line arguments/config files (with examples) and use with editors.
A structure like rustc_error_codes crate might be good to start building. This would enable something like ruff --explain E123 in the future as well
Is there any interest? If so, I would be willing to get a PR together

Yeah this is extremely important! I've been putting it off, but the docs are falling way behind the scope of the project.
I want to be fairly intentional about creating proper docs (need to think on the exact structure and setup a bit more), but I think creating dedicated descriptions for error codes like you've described above (something could power --explain) would be a great start. In other words: I don't know exactly where I want the docs to live etc., but something like the rustc_error_codes setup looks like it could plug in to a variety of options? I would be happy to start with mdBook too with the caveat that I might move to a different system somewhere down the line (TBD).
PR welcome!

Sounds great! I'll get something going

We now have this working (in a basic way):

https://github.com/charliermarsh/ruff/blob/main/docs/rules/assert-raises-exception.md
https://beta.ruff.rs/docs/rules/assert-raises-exception/

Oh hey, that's awesome! Sorry I never got around to this, but glad it worked out


update version metadata, no code changes

This works fine on 6.18 😄

There were a few more changes needed for the update to API 7 and also extra configuration needed to allow the plugin to work with the post-D17 build pipeline for plugin submission. I made a PR for these additional changes in #2.

The update has been pushed.


Add handling of context container for BehaviorSpec

With https://github.com/kotest/kotest/issues/3685, the context container was added into the BehaviorSpec. In order for this to properly be handled by the IntelliJ plugin, we need to update the spec style to also understand this container.

This is completed with https://github.com/kotest/kotest-intellij-plugin/pull/276


Add -race test to make check target

#523 showed that a data race was introduced recently. We should add a -race target to make check and possibly consider building development images with -race to catch this sooner.
Marking as beta.2 because we can probably live with it til then.

Fixed in #527


noCors middleware does not work if send cookies from other origin

If try to send cookies from other origin (other port on localhost for example) CORS error occurs.

This happens because we use * for requests with credentials, but wildcard for such requests is not allowed. https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Allow-Headers

The team was wondering whether to automate Cors when users send a request with credentials using fetch or xhr
We decided after all that this is the responsibility of the user. Users must resolve security issues independently
fetch('http://localhost:31299/users', {method: 'POST', credentials: 'include', headers: { test: 'test' } })

We could substitute all the necessary origin and headers ourselves to solve this problem, but there is a chance that the mock is used not only for the dev environment
If you need credentials in your request, you should fill cors data in config or use server to server channel


Add the ability to reset the form and set the new pristine values

I tried to avoid breaking changes and to reuse existings API methods with smart defualts. It could certanly be improved though, comments are welcome!

+1 . please merge

Thank you for your help
Fixed in 6767a6b9eba9c0a7c255c46ce2d6f84dc69eeeb4


*: Replace 'docker build . -t ${IMG}' with '-t ${IMG} .'

Because folks may have docker aliased to podman, and Podman prefers options before positional arguments:
$ podman build --help | grep CONTEXT-DIRECTORY
   podman build [command options] CONTEXT-DIRECTORY | URL

Generated with:
$ sed -i 's/docker build . -t ${IMG}/docker build -t ${IMG} ./' $(git grep -l 'docker.*build \. ')

Seems reasonable to me. If applicable, we should also make this change upstream in the Kubebuilder plugins so we can pull the same change in for Go projects.

Podman folks talking about this in containers/podman#2811.

I do not think that we should change the common targets only for Ansible.

In this PR, I'm changing everything that matched my sed.  Did I miss an entry?  I will file an upstream PR.

Upstreamed as kubernetes-sigs/kubebuilder#1817

Upstream PR landed.  Do we pull the hold here, or is there another way to ingest the upstream change?

Despite the upstream conversation to the contrary, I don't think I would consider this a change that needs to be held until a new version of the ansible and helm plugins are released. IMO, we should have pushed harder for this to be backported to the Go v2 plugin upstream. I also don't think the upstream decision binds our downstream decision.
There are always going to be differences between the different language plugins, and I think we can make our own decisions about what features and fixes to include in the helm and ansible plugins even if upstream is very conservative about what constitutes a breaking change in the Go plugin's scaffolded files.
I think I'm a :+1: to getting this merged.

Hi @wking,
See that for it get merged it needs to pass in the CI. It is falling in the make test-sanity. to fix that you need to run make generate.

Closing this in favor of PR #4466 to avoid the constant back and forth.


banner_<banner_id>.png doesn't exist

I did everything correctly but I can't find the banner.png

(I'm pretty sure I got bace_resource_pack loaded before I export)
I'm not sure if that's a problem because I did it wrong or something but I'm literally hitting my head against the wall to get this work lol

Hi, the banner textures being created was added in v1.1.0, so you'd need to use that version or newer to get banner textures.
I have just released a new version which also fixes the other issue that you were having, so please let me know if that new version works for you! Here's the link to the latest version: https://github.com/BramStoutProductions/MiEx/releases/tag/v1.2.0


Update scaffolded project Index / welcome page

Redesign the Index page that is presented to the user when they visit http://<IP_ADDRESS>:8000 when the project is scaffolded.

Change background color gradient
Adjust fonts and responsive layout

Updated font and colors


Switch threads and processes to subclasses

Threads and processes can subclass threading.Thread and multiprocessing.Process, respectively.  This should perhaps be done -- it makes certain things a lot more straightforward, and reduces some of the complexity of the code (in a way).

Closing: This is incidentally captured in the dynamic-output changes for the channel checker, download handler, and playlist handler.


#317 - hide version module from path

Please fix tests, update CHANGELOG and README, squash your commits.

@dblock tests are failing only on jruby and rbx and from the looks of it were failing before my code as well. any advice? I can take care of changelog, readme, and squashing in the meantime

Yeah, ignore the rbx/jruby things, as long as those don't seem to be like new failures. Will look at this separately.

Changes Unknown when pulling d2e68ac1da9c5c024066a41eebec034d6346e4a5 on synth:master into ** on ruby-grape:master**.


[Snyk] Security upgrade xunit-viewer from 7.1.9 to 8.0.0

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to fix one or more vulnerable packages in the `npm` dependencies of this project.
Changes included in this PR

Changes to the following files to upgrade the vulnerable dependencies to a fixed version:

polaris-ui/package.json
polaris-ui/package-lock.json

Vulnerabilities that will be fixed
With an upgrade:

Severity
Priority Score (*)
Issue
Breaking Change
Exploit Maturity

586/1000  Why? Proof of Concept exploit, Has a fix available, CVSS 5.3
Prototype Pollution SNYK-JS-XML2JS-5414874
Yes
Proof of Concept

(*) Note that the real score may have changed since the PR was raised.

Commit messages

Package name: xunit-viewer
    The new version differs by 9 commits.

06c111b 8.0.0
1e1b13b tested 7.2.0
554264b Updating all the modules and getting inline with node 18 exports
67a0cfd release demo
592395f 7.2.0
676d25f tested 7.1.9
b7509de adding a script boolean
2a58118 remove file
3796679 release demo

See the full diff

Check the changes in this PR to ensure they won't cause issues with your project.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
🛠 Adjust project settings
📚 Read more about Snyk's upgrade and patch logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Prototype Pollution

Closing as superseded by https://github.com/CPS-Innovation/Polaris/pull/421


Ability to render images as png/gif length of animation

Ability to render images as png, similar to StudioSB and Crossmod, if GIF rendering is possible it would be even awesome

This is definitely doable to add at some point.

I saw screenshot saving was added. Is GIF rendering being added soon too?

GIF rendering is more involved, so it probably won't be in the next update.

The only thing left to be implemented for this is saving with a transparent background when rendering as an image sequence with a format that supports transparency like PNG.

Does that include GIF too because I think GIF does have 1 bit transparency.

Thanks for the update! I was able to generate videos with transparency like these:
output.webm
output2.webm
Transparency will surely help, since I couldn't get rid of the pink background completely in my examples.

Transparency will be in the next release for PNG and GIF.


Debuging the transaction that calls method of non existing code exits with panic

Component
Cast, Anvil
Have you ensured that all of these are up to date?

[X] Foundry
[ ] Foundryup

What version of Foundry are you on?
No response
What command(s) is the bug in?
cast send --debug
Operating System
Linux
Describe the bug
foundryup: installed - forge 0.2.0 (6fc7463 2024-01-05T00:21:51.712802723Z)
foundryup: installed - cast 0.2.0 (6fc7463 2024-01-05T00:21:51.718643672Z)
foundryup: installed - anvil 0.2.0 (6fc7463 2024-01-05T00:21:51.706678919Z)
foundryup: installed - chisel 0.2.0 (6fc7463 2024-01-05T00:21:51.726644879Z)
running towards local anvil
💤 cast send 0x70997970C51812dc3A010C7d01b50e0d17dc79C8 "increment()" --private-key 0xac0974bec39a17e36ba4a6b4d238ff944bacb478cbed5efcae784d7bf4f2ff80

blockHash 0xb5724628d1d2fc8ae236076f5a6d6a0d094418ec95b4a8f929fddcec9271acd8
blockNumber 1
contractAddress
cumulativeGasUsed 21064
effectiveGasPrice<PHONE_NUMBER>
gasUsed 21064
logs []
logsBloom 0x00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
root
status 1
transactionHash 0x701aade4f053b0aa92c248182b9bcc1c4e5b22ad6caa1eb9704ad9e171eafdfe
transactionIndex 0
type 2

💤 cast run 0x701aade4f053b0aa92c248182b9bcc1c4e5b22ad6caa1eb9704ad9e171eafdfe
Executing previous transactions from the block.
Traces:
  [0] 0x70997970C51812dc3A010C7d01b50e0d17dc79C8::increment()
    └─ ← ()

Transaction successfully executed.
Gas used: 21064

💤 cast run 0x701aade4f053b0aa92c248182b9bcc1c4e5b22ad6caa1eb9704ad9e171eafdfe --debug
Executing previous transactions from the block.
The application panicked (crashed).
Message: index out of bounds: the len is 0 but the index is 0
Location: crates/debugger/src/tui/context.rs:64

This is a bug. Consider reporting it at https://github.com/foundry-rs/foundry

Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.
Aborted (core dumped)

Panic was fixed, and replaced by an error, although I don't really know why these errors happen:
...
$ cast run 0x701aade4f053b0aa92c248182b9bcc1c4e5b22ad6caa1eb9704ad9e171eafdfe --debug
Executing previous transactions from the block.
Error:
debug arena is empty


Use Ubuntu Trusty

Upstart has mongodb 3.2 by default, so we end-up running 2 mongo 3.2 builds.
We need to find a way to install 2.6 on trusty

Coverage decreased (-4.6%) to 86.099% when pulling cb73ab8da4d66e8e36a7a8e8674468b7539adb9f on SAP:trusty into c787a78b596f73bd0ea7d5a52762b1a258d920b6 on cloudfoundry-incubator:master.

Coverage decreased (-4.6%) to 86.099% when pulling cb73ab8da4d66e8e36a7a8e8674468b7539adb9f on SAP:trusty into c787a78b596f73bd0ea7d5a52762b1a258d920b6 on cloudfoundry-incubator:master.

Coverage remained the same at 90.711% when pulling 8f937396980a9f59e79e1b0a3ecebfae5913db81 on SAP:trusty into c787a78b596f73bd0ea7d5a52762b1a258d920b6 on cloudfoundry-incubator:master.

Coverage remained the same at 90.711% when pulling 8f937396980a9f59e79e1b0a3ecebfae5913db81 on SAP:trusty into c787a78b596f73bd0ea7d5a52762b1a258d920b6 on cloudfoundry-incubator:master.

Coverage remained the same at 90.711% when pulling 8f937396980a9f59e79e1b0a3ecebfae5913db81 on SAP:trusty into c787a78b596f73bd0ea7d5a52762b1a258d920b6 on cloudfoundry-incubator:master.

Coverage remained the same at 90.711% when pulling 8f937396980a9f59e79e1b0a3ecebfae5913db81 on SAP:trusty into c787a78b596f73bd0ea7d5a52762b1a258d920b6 on cloudfoundry-incubator:master.

Coverage decreased (-4.8%) to 85.866% when pulling f8fb974ff7a222439c6b8217a27c07bf8a463997 on SAP:trusty into c787a78b596f73bd0ea7d5a52762b1a258d920b6 on cloudfoundry-incubator:master.

Coverage decreased (-4.6%) to 86.099% when pulling ea90bbc0f575e42a3ef1e15e79a2b1fdcaa83977 on SAP:trusty into c787a78b596f73bd0ea7d5a52762b1a258d920b6 on cloudfoundry-incubator:master.

Coverage remained the same at 90.711% when pulling 0b27b62c77410aa9566abc304316cc6d818a8e13 on SAP:trusty into c787a78b596f73bd0ea7d5a52762b1a258d920b6 on cloudfoundry-incubator:master.

Coverage remained the same at 90.711% when pulling 0b27b62c77410aa9566abc304316cc6d818a8e13 on SAP:trusty into c787a78b596f73bd0ea7d5a52762b1a258d920b6 on cloudfoundry-incubator:master.

Coverage remained the same at 90.711% when pulling 0b27b62c77410aa9566abc304316cc6d818a8e13 on SAP:trusty into c787a78b596f73bd0ea7d5a52762b1a258d920b6 on cloudfoundry-incubator:master.


Refactor SERCOM pads, add documentation and port feather_m0 to gpio::v2

This is a megalith of changes I've been lumping into the same branch (exactly what you're supposed to do with Git...).
This still needs a lot of work on the documentation side of things. And I should probably split it out into digestible pieces. But I wanted to post it now, because it contains a complete port of the feather_m0 to gpio::v2. Several people have had questions about porting, so I wanted to get an example posted ASAP.
🚧 NOTE 🚧 Parts of the feather_m0 port are dependent on changes made to the HAL in this branch. Those changes have not yet been merged, so you may not be able to copy everything as-is.
@TDHolmes & @jaredwolff, you're the two that come to mind, but I know there were others working with gpio::v2.

I still need to flesh out the commit messages, but I was able to somewhat split this into pieces. There's still one very large commit, but splitting it into pieces that still built successfully would be painful. I'm going to leave that one as is.

Commit messages have been updated. This is ready for review


remove the external loadbalancer default config from kubernetes services

External loadbalancers are restricted to a small number on GKE and for AWS incur a cost so we should avoid creating services with this config.
Instead now that the nginx ingress controller is working for plain kubernetes and fabric8 we ought to create ingress rules or have another microservice running that watches for new services (perhaps with a specific label) that will automatically create the ingress rule.
A quick grep through the f-m-p repo suggests there's some logic that uses the LoadBalacer metadata on services so simply removing the default config may break a few things.

Hi James, first of all, congratulations for your work on Fabric8! I have a question please and maybe it's related to this issue.
I have deployed Kubernetes 1.5 on AWS. Then, I have installed the nginx-lego Ingress Controller (https://github.com/kubernetes/charts/tree/master/stable/nginx-lego). Then, I have installed Fabric8 on top using Helm (I had some issues trying to use gofabric8 with persistent volumes on AWS, that's why I use Helm).
I have created a Route53 CNAME record (*.default.sub.domain.com) pointing to the AWS load balancer url created for the Ingress Controller (the url shown at "kubectl describe svc nginx-nginx-lego --namespace kube-system | grep Ingress | awk '{print $3}'"). With this setup, and thanks to the exposecontrolller and the Ingress rules created by him, I can access all the Fabric8 components using their friendly DNS names. So, I can go to http://fabric8.default.sub.domain.com, http://gogs.default.sub.domain.com, http://jenkins.default.sub.domain.com etc. So far so good.
Then, I used the Fabric8 dashboard to create the application on Gogs (the Spring test microservice which shows the "Reply: Hello World!" output). The build process is successful. So, I have the following:

Ok, now this is where I have a problem: if I click the little icon to open each service in a new tab, I'm redirected to -for example- http://test.default-production.sub.domain.com. But the application is not loaded. However, I have noted on the AWS console that Fabric8 has created 3 new AWS loadbalancers for this application (one for each environment). If I navigate to the urls of these 3 AWS loadbalancers, I can see the "Reply: Hello World!" message. So, the app is working but it's available via AWS loadbalancers.
I could fix this problem creating DNS CNAME records on Route53 so test.default-production.sub.domain.com points to the url of their AWS load balancer (and it works). However, I prefer not use AWS loadbalancers. In fact, I don't understand why Fabric8 has created the AWS loadbalancers. On the configmap of the "exposecontroller" I have the following configuration:
domain: sub.domain.com
exposer: Ingress

As you can see, I'm not using "exposer: LoadBalancer" on the configmap of the exposecontroller. So, my question is: when I create an application on Fabric8 (my test Spring app), is not supposed that Fabric8 will create new Ingress rules so I don't need the use of AWS loadbalancers? Or maybe I'm confused and the exposecontroller is only used for the internal Fabric8 services (Jenkins, Gogs, Nexus, etc) but can't be used for my custom apps? (Test, etc).
Thank you very much in advance for your feedback!


Use the built-in compose of the docker command

Now compose is built in the docker command. It's preferred to use it as docker-compose will eventually be removed

Thanks @agoncal ! Can you update the other README.md files in the individual app folders too?

Done ! @edeandrea sorry, didn't look under the subdirectories.


bind onKeyUp function (access to state from inside)

I've pushed an update to the refactor branch that binds this to onKeyUp`
https://github.com/thomasthesecond/react-typeahead/commit/294ec0f95c0be394888cafc50ae55924cd4ba517
Let me know if that doesn't work.