Unable to load the video in Ubuntu 22.04

When I load a dataset on Ubuntu 22.04 commit: https://github.com/ami-iit/robot-log-visualizer/commit/dc5e8fdba199743aa9358f26150a9478b69a0442
I got the following error while trying to play the video that's remain black.
You can open the visualizer by visiting the following URL:
http://<IP_ADDRESS>:7000/static/
qt.svg: Invalid path data; path truncated.
qt.svg: Invalid path data; path truncated.
qt.svg: Invalid path data; path truncated.
qt.svg: Invalid path data; path truncated.
qt.svg: Invalid path data; path truncated.
qt.svg: Invalid path data; path truncated.
qt.svg: Invalid path data; path truncated.
../src/intel/isl/isl.c:2216: FINISHME: ../src/intel/isl/isl.c:isl_surf_supports_ccs: CCS for 3D textures is disabled, but a workaround is available.
qt.svg: Invalid path data; path truncated.
qt.svg: Invalid path data; path truncated.
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
Error: "Internal error: could not render surface"
Error: "Internal error: could not render surface"

That's pretty similar to: https://ubuntuforums.org/showthread.php?t=2481167

in iRonCub we encountered the same problem on the robot laptop, which is Ubuntu 22.04.
 Use QT_QPA_PLATFORM=wayland to run on Wayland anyway.
/home/ironcub/code/robotology-superbuild/build/install/lib/python3/dist-packages/robot_log_visualizer/plotter/matplotlib_viewer_canvas.py:47: UserWarning: frames=None which we can infer the length of, did not pass an explicit *save_count* and passed cache_frame_data=True.  To avoid a possibly unbounded cache, frame data caching has been disabled. To suppress this warning either pass `cache_frame_data=False` or `save_count=MAX_FRAMES`.
  self.vertical_line_anim = animation.FuncAnimation(
GStreamer; Unable to pause - "file:///home/ironcub/robot_logger_device_2023_10_06_12_35_58_logitech2_rgb.mp4"
GStreamer; Unable to pause - "file:///home/ironcub/robot_logger_device_2023_10_06_12_35_58_logitech2_rgb_old.mp4"
GStreamer; Unable to pause - "file:///home/ironcub/robot_logger_device_2023_10_06_12_35_58_logitech_rgb.mp4"
Warning: "No decoder available for type 'video/quicktime, variant=(string)iso'."
Warning: "No decoder available for type 'video/quicktime, variant=(string)iso'."
Warning: "No decoder available for type 'video/quicktime, variant=(string)iso'."
Error: "Your GStreamer installation is missing a plug-in."
Error: "Your GStreamer installation is missing a plug-in."
Error: "Your GStreamer installation is missing a plug-in."

For conda, I think this is the problem in https://github.com/ami-iit/robot-log-visualizer/issues/67 . For Ubuntu 22.04, can you try if it improves to run:
sudo apt install gstreamer1.0-plugins-good gstreamer1.0-plugins-ugly

Thank you @traversaro ❤

That solved the problem?

if testing o the solution is still required, we can test also this solution tomorrow on the experiment PC.

I don't know what changed, but yesterday the robot-log-visualizer was continuously crashing when loading .mp4 videos. Loading only the .mat file without videos was working correctly.
After a lot of debugging I have managed to restore the original behavior of the visualizer on Ubuntu 22.04 (the one described in the front comment). The reason seems related to this warning message about the graphics protocol I was using:
Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway.
/home/ironcub/code/robotology-superbuild/build/install/lib/python3/dist-packages/robot_log_visualizer/plotter/matplotlib_viewer_canvas.py:47: UserWarning: frames=None which we can infer the length of, did not pass an explicit *save_count* and passed cache_frame_data=True.  To avoid a possibly unbounded cache, frame data caching has been disabled. To suppress this warning either pass `cache_frame_data=False` or `save_count=MAX_FRAMES`.

I fixed the warning following the instructions in https://stackoverflow.com/questions/69828508/warning-ignoring-xdg-session-type-wayland-on-gnome-use-qt-qpa-platform-wayland:

1.Disabled Wayland by uncommenting WaylandEnable=false in the /etc/gdm3/custom.conf
Check whether you are on Wayland or Xorg using:
echo $XDG_SESSION_TYPE

this did NOT fixed the problem, but at least now the interface does not crash anymore when I try to load a .mp4 file.

Thank you @traversaro ❤

That solved the problem?

Unfortunately no.
The strange thing is that this is happening only the robot pc.

The strange thing is that this is happening only the robot pc.

If you have two Ubuntu 22.04 machines, one in which it is working, and one in which it is not working, it would be interesting to collect:

How robot-log-visualizer is installed
https://github.com/ami-iit/log-installed-software output
output of env (sanified from possible confidential info)

here I am. So the visualizer is installed with the superbuild + apt
this is the trace of gdb when it crashes
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
--Type <RET> for more, q to quit, c to continue without paging--
Core was generated by `/usr/bin/python3.10 /usr/local/src/robot/robotology-superbuild/build/install/li'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x00007fbb99445571 in wl_proxy_marshal_array_flags () from /lib/x86_64-linux-gnu/libwayland-client.so.0
[Current thread is 1 (Thread 0x7fba03fef640 (LWP 49247))]
(gdb) where
#0  0x00007fbb99445571 in wl_proxy_marshal_array_flags () at /lib/x86_64-linux-gnu/libwayland-client.so.0
#1  0x00007fbb99445c7f in wl_proxy_marshal_flags () at /lib/x86_64-linux-gnu/libwayland-client.so.0
#2  0x00007fba4a097181 in  () at /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so
#3  0x00007fba4a06e879 in  () at /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so
#4  0x00007fba4a0328c4 in  () at /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so
#5  0x00007fbb6471423d in  () at /lib/x86_64-linux-gnu/libQt5MultimediaGstTools.so.5
#6  0x00007fbb647144ef in  () at /lib/x86_64-linux-gnu/libQt5MultimediaGstTools.so.5
#7  0x00007fbb64703777 in  () at /lib/x86_64-linux-gnu/libQt5MultimediaGstTools.so.5
#8  0x00007fbb40300862 in gst_bus_post () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
#9  0x00007fbb403165ea in  () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
#10 0x00007fbb402f1d20 in  () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
#11 0x00007fbb403163b2 in gst_element_post_message () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
#12 0x00007fbb402e7cbc in  () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
#13 0x00007fbb40300862 in gst_bus_post () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
#14 0x00007fbb403165ea in  () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
#15 0x00007fbb402f1d20 in  () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
#16 0x00007fbb403163b2 in gst_element_post_message () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
#17 0x00007fbb402e7cbc in  () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
#18 0x00007fbb40300862 in gst_bus_post () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
#19 0x00007fbb403165ea in  () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
#20 0x00007fbb402f1d20 in  () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
#21 0x00007fbb403163b2 in gst_element_post_message () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
#22 0x00007fbb402e7cbc in  () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
#23 0x00007fbb40300862 in gst_bus_post () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
#24 0x00007fbb403165ea in  () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
#25 0x00007fbb402f1d20 in  () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
#26 0x00007fbb403163b2 in gst_element_post_message () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
#27 0x00007fbb402e7cbc in  () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
#28 0x00007fbb40300862 in gst_bus_post () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
#29 0x00007fbb403165ea in  () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
#30 0x00007fbb403163b2 in gst_element_post_message () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
#31 0x00007fba4a03d51e in  () at /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so
#32 0x00007fba683b82c2 in  () at /lib/x86_64-linux-gnu/libgstbase-1.0.so.0
#33 0x00007fba4a03b619 in  () at /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so
#34 0x00007fba683b3432 in  () at /lib/x86_64-linux-gnu/libgstbase-1.0.so.0
#35 0x00007fbb40338dcc in  () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
#36 0x00007fbb4033944e in  () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
#37 0x00007fbb40339908 in  () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
#38 0x00007fbb4032f7b0 in  () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
#39 0x00007fbb4033c9da in gst_pad_push_event () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
#40 0x00007fba683cbb18 in  () at /lib/x86_64-linux-gnu/libgstbase-1.0.so.0
#41 0x00007fba683cbe1a in  () at /lib/x86_64-linux-gnu/libgstbase-1.0.so.0
#42 0x00007fbb40338dcc in  () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
#43 0x00007fbb4033944e in  () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
#44 0x00007fbb40339908 in  () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
#45 0x00007fbb4032f7b0 in  () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
#46 0x00007fbb4033c9da in gst_pad_push_event () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
#47 0x00007fbb4033cf81 in  () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
#48 0x00007fbb403369fe in gst_pad_forward () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
#49 0x00007fbb40336b45 in gst_pad_event_default () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
#50 0x00007fbb40338dcc in  () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
#51 0x00007fbb4033944e in  () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
--Type <RET> for more, q to quit, c to continue without paging--
#52 0x00007fbb40339908 in  () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
#53 0x00007fbb4032f7b0 in  () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
#54 0x00007fbb4033c9da in gst_pad_push_event () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
#55 0x00007fbb4033cf81 in  () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
#56 0x00007fbb403369fe in gst_pad_forward () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
#57 0x00007fbb40336b45 in gst_pad_event_default () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
#58 0x00007fbb40338dcc in  () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
#59 0x00007fbb4033944e in  () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
#60 0x00007fbb40339908 in  () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
#61 0x00007fbb4032f7b0 in  () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
#62 0x00007fbb4033c9da in gst_pad_push_event () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
#63 0x00007fba683cbb18 in  () at /lib/x86_64-linux-gnu/libgstbase-1.0.so.0
#64 0x00007fba683cbe1a in  () at /lib/x86_64-linux-gnu/libgstbase-1.0.so.0
#65 0x00007fbb40338dcc in  () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
#66 0x00007fbb4033944e in  () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
#67 0x00007fbb40339908 in  () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
#68 0x00007fbb4032f7b0 in  () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
#69 0x00007fbb4033c9da in gst_pad_push_event () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
#70 0x00007fba683cbb18 in  () at /lib/x86_64-linux-gnu/libgstbase-1.0.so.0
#71 0x00007fba683cbe1a in  () at /lib/x86_64-linux-gnu/libgstbase-1.0.so.0
#72 0x00007fbb40338dcc in  () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
#73 0x00007fbb4033944e in  () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
#74 0x00007fbb40339908 in  () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
#75 0x00007fbb4032f7b0 in  () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
#76 0x00007fbb4033c9da in gst_pad_push_event () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
#77 0x00007fbb4033cf81 in  () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
#78 0x00007fbb403369fe in gst_pad_forward () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
#79 0x00007fbb40336b45 in gst_pad_event_default () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
#80 0x00007fba4a1b6c6a in  () at /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstplayback.so
#81 0x00007fbb40338dcc in  () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
#82 0x00007fbb4033944e in  () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
#83 0x00007fbb40339908 in  () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
#84 0x00007fbb4032f7b0 in  () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
#85 0x00007fbb4033c9da in gst_pad_push_event () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
#86 0x00007fba4a127c5c in  () at /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstcoreelements.so
#87 0x00007fbb40362127 in  () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
#88 0x00007fbbb574d6b4 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#89 0x00007fbbb574aa51 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#90 0x00007fbbb7c94ac3 in start_thread (arg=<optimized out>) at ./nptl/pthread_create.c:442
#91 0x00007fbbb7d26a40 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Following https://askubuntu.com/questions/1441953/ubuntu-22-04-1-lts-totem-video-player-crashes-on-launch we removed gstreamer1.0-vaapi with
sudo apt purge gstreamer1.0-vaapi

Now everything is working

Cool, if he problem was vaapi it is possible that the route cause was a graphic card driver problem or similar.

cool, we'll test it also on the iRonCub PC during the next experimental campaign!

I am facing the same issue. I can load the robot and the data but the video window remains black,
UserWarning: frames=None which we can infer the leng
th of, did not pass an explicit *save_count* and passed cache_frame_data=True.  To avoid a possibly unbounded cache, frame data caching has been disabled. To suppress this warni
ng either pass `cache_frame_data=False` or `save_count=MAX_FRAMES`.
  self.vertical_line_anim = animation.FuncAnimation(
GStreamer; Unable to pause - "file:///home/laniakea/git/research/element_codesign-for-walking-and-jumping/src/ergoCub_sim/drake_sim/data/cartesian_tracking/robot_logger_device_2
023_08_29_12_35_39_jabra.mp4"
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
Warning: "Could not open audio device for playback."
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
Warning: "No decoder available for type 'video/mpeg, mpegversion=(int)4, systemstream=(boolean)false, profile=(string)simple, level=(string)1, codec_data=(buffer)000001b001000001b58913000001000000012000c48d8800f528045a1463000001b24c61766335382e35342e313030, width=(int)1280, height=(int)720, framerate=(fraction)30/1, pixel-aspect-ratio=(fraction)1/1'."
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
Error: "Your GStreamer installation is missing a plug-in."
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material
js: _meshfile is deprecated. Please use _meshfile_geometry for geometries and _meshfile_object for objects with geometry and material

I have all the everything installed (https://github.com/ami-iit/robot-log-visualizer/issues/56#issuecomment-1752109790). Also, https://github.com/ami-iit/robot-log-visualizer/issues/56#issuecomment-1792189063 does not help.
Im on Ubuntu 22.04, installed the library via mamba. I will look into, https://github.com/ami-iit/robot-log-visualizer/issues/56#issuecomment-1792373795, if possible.

@akhilsathuluri if you are using mamba, you should try in your environment:
mamba install gst-plugins-good gst-plugins-bad

as the relevant errors in your log is:
GStreamer; Unable to pause - "file:///home/git/element_codesign-for-walking-and-jumping/src/ergoCub_sim/drake_sim/data/cartesian_tracking/robot_logger_device_2
023_08_29_12_35_39_jabra.mp4"
Warning: "Could not open audio device for playback."
Warning: "No decoder available for type 'video/mpeg, mpegversion=(int)4, systemstream=(boolean)false, profile=(string)simple, level=(string)1, codec_data=(buffer)000001b001000001b58913000001000000012000c48d8800f528045a1463000001b24c61766335382e35342e313030, width=(int)1280, height=(int)720, framerate=(fraction)30/1, pixel-aspect-ratio=(fraction)1/1'."
Error: "Your GStreamer installation is missing a plug-in."

See https://github.com/ami-iit/robot-log-visualizer/issues/67#issuecomment-1752102250 .

mamba install gst-plugins-good gst-plugins-bad

Thanks, I can confirm that this works now!
Installing via apt was not helpful then.

Perhaps an alternative if you wont or can't uninstall gstreamer vaapi could be to set the LIBVA_DRIVER_NAME to fakedriver ? See https://fhackts.wordpress.com/2018/04/16/temporarily-skipping-vaapi-decoders-in-decodebin/ .

@giotherobot did an extensive investigation on a similar problem on its computer, and for him the video player started to work (on Ubuntu 22.04 with conda) after he installed sudo apt install ubuntu-restricted-extras . Probably some libvaapi driver was missing or something similar. For debug, a useful command he used is:
GST_DEBUG=4 gst-play-1.0 '/home/giovannif/Documents/dataset/2024_05_29-01/robot_logger_device_2024_05_29_16_09_18_jabra_rgb.mp4'

If anyone is still experiencing this problem, please report the output of https://github.com/ami-iit/log-installed-software and the output of GST_DEBUG=4 gst-play-1.0, thanks!


ARROW-13557: [Packaging][Python] Skip test_cancellation test case on M1

@github-actions crossbow submit wheel-macos-*

@github-actions crossbow submit wheel-macos-big-sur-*

@github-actions crossbow submit wheel-macos-big-sur-*


⚠ ClamAV has degraded performance

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

HTTP code: 200
Response time: 107 ms

Resolved: ClamAV performance has improved in 13f6e1c.


completed!

Did you complete this after David showed you the answers? Instead of the verbose get '/guitars'... you can do something like resources :guitars, only: [:index, :show]

I didn't. I used the documentation and trial and error.
On Jan 22, 2015 11:45 AM, "Json Wharff"<EMAIL_ADDRESS>wrote:

Did you complete this after David showed you the answers? Instead of the
verbose get '/guitars'... you can do something like resources :guitars,
only: [:index, :show]
—
Reply to this email directly or view it on GitHub
https://github.com/ga-wdi-boston/wdi_2_assessment_rails_routes/pull/5#issuecomment-71052126
.


ReactPlay misspelled in the CLI

ReactPlay is misspelled as rectplay during installation in CLI

Hi @frankiefab100, thanks for noticing it. Will fix it ASAP.

Hi @frankiefab100, thanks for noticing it. Will fix it ASAP.

Alright👍🏼

This issue has been fixed with this PR on the create-react-play repo


Mathematical induction calculator

Is your feature request related to a problem? Please describe.
Add mathematical induction calculator to the algebra section. The definition shouldn't be plagiarized.

Hello, I am a GSSOC'22 participant and I have knowledge about mathematical induction and i would like to contribute in this issue, can you Please assign it to me.

@ROUSHNI1 u can work


Git branch segment

Hi Dom,
I have both:
  (spaceline-toggle-all-the-icons-vc-status-on)
  (spaceline-toggle-all-the-icons-git-status-on)
  (spaceline-toggle-all-the-icons-vc-icon-on)

But there is no way for me to get the current branch name as a segment, even though additions and deletions show up just fine.

What version control are you using? Git?
Could you please print the value of vc-mode?

Yes, git, mostly. Evaluating vc-mode does not provide pertinent information.

That's odd... vc-mode is a native variable and Emacs should detect this for you... Did the original spaceline theme contain information for the branch? I can't see anything in spaceline-segments.el that uses/displays it. 🤔
I also don't think I have to do anything to set vc-mode up in my init.
Here's some docs on vc-mode and Emacs, but I'm not sure if they're useful.

Again, my bad. Some snippets of my previous modeline setup were messing things around. By removing it it works just fine. Sorry for the noise :-(

Ah, well glad it's working for you!

Thanks and congratulations for the awesome job !


Make da Playground Project name unique with timestamp

Our test implementation is on a dev branch/release, but is mixed in with some other experimental changes.
X of the problem: We're finding we're having some caching issues with @CaroRob's tests - tests on the same branch will use previous yml code, not updating to the newly pulled code. When a branch's code is updated in relevant ways, its tests will continue to behave as they previously had. A new branch checked out of that branch with no code changes will behave properly. Also, after a few days, the problem will disappear and the tests will behave appropriately again.
Possibly, through the API the Project's name gets deleted, but the Project itself doesn't get fully deleted, and pulling new code doesn't actually pull new code. That seems strange, but we don't have other guesses right now.
Y of the problem (and the purpose of this issue): We think making sure the Project name is unique will solve this. We implemented it on a dev branch/release and the problem hasn't showed up again yet. We hope that if this is indeed the problem, lingering Projects will clean themselves up - after all, the problem does disappear after a few days.

GitHub ticket
In case GitHub stuff is involved with this as well.

Product
GitHub
Description
Actions don't seem to be updating based on code updates - test output for a branch doesn't change even when the code changes until the user makes a new branch with the same code. Not blocking, but our users are getting frustrated working around this. We don't mind that the tests are failing - the new branch's tests are failing in expected ways - we just mind that the action output doesn't change when the code changes.
What we saw a few weeks ago on a different repo too:
Branch 1 starts failing specific end-to-end tests (e.g. #20, #21, #22). Rerunning results in the same consistently failing tests 5 times in a row.
Checkout a new branch from Branch 1 (Branch 2a). Make no changes.
Branch 2a (correctly) fails only one test, e.g. #22, consistently.
Checkout another new branch from Branch 1 (Branch 2b). Make no changes.
Branch 2b (correctly) fails only one test, e.g. #22, consistently, same as Branch 2a.
Branch 1 continues to fail all its same own tests consistently (e.g. #20, #21, #22)
We're now having this issue again:
Branch 1: https://github.com/A2JatAKCourts/docassemble-ChangingChildCustody/actions/runs/4318924770
Branch 2: https://github.com/A2JatAKCourts/docassemble-ChangingChildCustody/actions/runs/4318784095
Branch 3: https://github.com/A2JatAKCourts/docassemble-ChangingChildCustody/actions/runs/4319050758
I'm not sure GitHub is the only culprit. I think the site being tested could potentially have something to do with it. Maybe it thinks the action is a returning user. Does the GitHub branch keep the same IP address for all its actions however many times they're run? Does it keep some other information around? Is there a way to clear that information?
When we had this issue for a few days a few weeks ago, there was a post in GitHub about caching issue with something else. We hoped it was related, but maybe it's not.
Reproduction Steps
We can't reproduce this consistently, but this is what we have seen sometimes:
Branch 1 starts failing specific end-to-end tests (e.g. #20, #21, #22). Rerunning results in the same consistently failing tests 5 times in a row.
Checkout a new branch from Branch 1 (Branch 2a). Make no changes.
Branch 2a (correctly) fails only one test, e.g. #22, consistently.
Checkout another new branch from Branch 1 (Branch 2b). Make no changes.
Branch 2b (correctly) fails only one test, e.g. #22, consistently, same as Branch 2a.
Branch 1 continues to fail all its same own tests consistently (e.g. #20, #21, #22)
Fault Type
Intermittent - Occurring irregularly
Blocking?
No
Last working date
16 February
Logs
These are the actions that are providing the same output, even when rerun. Note that each branch contains the same code during these actions.
"Branch 1" is failing the wrong way: https://github.com/A2JatAKCourts/docassemble-ChangingChildCustody/actions/runs/4318924770
20 scenarios (5 failed, 15 passed)
150 steps (5 failed, 25 skipped, 120 passed)
"Branch 2" is failing the right way: https://github.com/A2JatAKCourts/docassemble-ChangingChildCustody/actions/runs/4318784095
20 scenarios (1 failed, 19 passed)
150 steps (1 failed, 5 skipped, 144 passed)
"Branch 3" is failing the right way: https://github.com/A2JatAKCourts/docassemble-ChangingChildCustody/actions/runs/4319050758
20 scenarios (1 failed, 19 passed)
150 steps (1 failed, 5 skipped, 144 passed)
I'm not sure what info would be useful for you to see.
Clarifying note
The other repo eventually fixed itself after a couple days or so - suddenly re-running the tests on the branch updated to the new code and everything was fine. This repo hasn't done that yet.

Response

Hello plocket,
Thank you for reaching out to GitHub Support! I apologize for the delayed response here.

Actions don't seem to be updating based on code updates - test output for a branch doesn't change even when the code changes until the user makes a new branch with the same code.

With checking out code in Actions, actions/checkout will by default check out the repository on the commit SHA of the triggering event. Re-running the job will have it execute in the same context of when it first triggered with the same commit SHA, whereas triggering another workflow run will bring a fresh triggering event with perhaps an updated commit SHA if changes were made.
In the logs for a workflow run, the last log line of the actions/checkout step will be this commit SHA (example). If the same SHA or code is being checked out, I'm not certain what the difference would be here with making a new branch - as that shouldn't have an impact on what is getting pulled and executed in the workflow run.

Does the GitHub branch keep the same IP address for all its actions however many times they're run? Does it keep some other information around? Is there a way to clear that information?

GitHub-hosted runners execute on hosts provisioned from a shared pool of VMs that each have their own IPs. It's possible that two separate jobs may execute from the same VM by chance since they come from the same pool, but that would be pretty rare given the large size of the pool. Altogether, no information like that is maintained exclusively for a branch or repository that would cause it to persist and affect workflow runs.
As long as you can verify that the same code is being used to execute the tests, I believe the cause of the differences in results would come from the test execution itself, as you mentioned. I see from your examples that a third-party action SuffolkLITLab/ALKiln is being used to do the testing - is this the same for the instances you're still seeing of this issue? Are you aware of any cases where differences in results could stem from non-code related differences?


fix(1478): fix deformed style of number indicator when empty

By creating this pull request you agree to the terms in CONTRIBUTING.md.
https://github.com/Infineon/.github/blob/master/CONTRIBUTING.md
--- DO NOT DELETE ANYTHING ABOVE THIS LINE ---
CONTRIBUTING.md also tells you what to expect in the PR process.
Description
Changed property height >>> max-height .
Related Issue
Closes #1478

📦 Published PR as canary version: 25.5.0--canary.1481.221e1268c91b80a5c6dfc0ebf9cb8440028300d6.0

:sparkles: Test out this PR locally via:
npm install<EMAIL_ADDRESS># or
yarn add<EMAIL_ADDRESS>

When number-indicator is empty, NaN is rendered.
number-indicator=""

Also, this condition is very unclear.
!this.numberIndicator !== undefined

Also, even when number-indicator is not set, its wrapper is still rendered in the DOM.

@akashyeole

every sidebar-item instance throws an error
sidebar__nav-item-indicator wrapper still occupies space even when number-indicator is not present.


:sparkles: Use a separate namespace for each e2e test

Fixes #1307
Create and use a new namespace for every e2e test. This means that extension resources are placed in their own namespace. The tests deletes the namespace, and then waits until completion. This ensures that most of an extension's resources are deleted.
It does guarantee that global resources (e.g. CRDs, CRs, CRBs) are deleted.
And would eventually allow the tests to be run in parallel (assuming the installed extensions allow for that).

Description

Reviewer Checklist

[ ] API Go Documentation
[ ] Tests: Unit Tests (and E2E Tests, if appropriate)
[ ] Comprehensive Commit Messages
[ ] Links to related GitHub Issue(s)

I have encountered one failure over the course of several dozen; so this is not perfect, but it does reduce the likelyhood

Of course, it failed e2e... but it failed because the bundle's CRDs were still present... not much we can do here except chase a timeout, which is never a good idea.

Managed to get this to run 35 times in a row without a failure...


python3Packages.sphinx-autodoc-typehints: 1.18.3 -> 1.19.0; python3Packages.psycopg: 3.0.15 -> 3.0.16

With psycopg 3.0.16 we can drop all patches that we required with 3.0.15 to make the package build in a sandboxed environment and with Sphinx 5.0.
Description of changes

Things done

Built on platform(s)

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

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

pgcli broken on target branch, since it requires an older pgspecial version.

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

2 packages failed to build:

pgcli (python310Packages.pgcli)
python39Packages.pgcli

6 packages built:

python310Packages.pgspecial
python310Packages.psycopg
python310Packages.sphinx-autodoc-typehints
python39Packages.pgspecial
python39Packages.psycopg
python39Packages.sphinx-autodoc-typehints


v0.4.1 discussion

Milestone
Remaining items

[x] https://github.com/Quansight/qhub/pull/1219

Partially dependent on  https://github.com/Quansight/qhub/pull/1234

[x] https://github.com/Quansight/qhub/pull/1271

PR to fix the region issue https://github.com/Quansight/qhub/pull/1271

@iameskild @tonyfast @magsol should we let this open for a release postmortem?

That sounds good to me!

Results after upgrading quansight-beta:

[x] GPUs enabled and working (GCP)

the gpu node group also scaled down to 0 appropriately

[x] panel dashboard working after upgrade to >0.12.4
[x] dask cluster + dashboard tested (not the labextention)
[ ] Theme display_version displaying wrong version (v0.0.1)

Results after upgrading quansight:

[x] GPUs enabled and working (GCP)

the gpu node group also scaled down to 0 appropriately

[ ] panel dashboard not working after upgrade to >0.12.4
[x] dask cluster + dashboard tested (not the labextention)
[ ] Theme display_version displaying wrong version (v0.0.1)

The display_version is also seems to be layered on top of the "Help" button during creating dashboards:

Thanks, @iameskild, I think I already know why the version is incorrect, but I didn't take into consideration the help button when adding the theme config.

Could you check the output from 'qhub --version' of the installed one?


[BUG] Device/entity does not show up in climate service

Describe the bug
Thanks for this integration, my Ariston LydosHibrid shows up and works fine over the webui (device profile page), I'm able to set the target temperature and the mode of operation (e.g. BOOST or GREEN). Inspecting the websocket events, I see the following corresponding messages:
{"type":"call_service","domain":"water_heater","service":"set_operation_mode","service_data":{"operation_mode":"BOOST","entity_id":"water_heater.ariston"},"id":49}

{"type":"call_service","domain":"water_heater","service":"set_temperature","service_data":{"entity_id":"water_heater.ariston","temperature":52},"id":51}

However, I'm unable to call the climate services (e.g. set target temperature) in my automations: the equipment is missing both among the entities and the devices.
If I configure the YAML manually, e.g. like this:
service: climate.set_temperature
data:
  entity_id: water_heater.ariston
  temperature: 51

According to the feedback of the webui the call succeeds, but nothing actually happens, and the following message is emitted in the system logs:
2024-04-13 17:48:00.109 WARNING (MainThread) [homeassistant.helpers.service] Referenced entities water_heater.ariston are missing or not currently available

Expected behavior
I expect to the climate service to work from automations as well.
Environment (please complete the following information):

HA version: 2024.4.3
Version of the integration: most recent stable (just installed today via HACS)
Ariston device type (check the integration Device info): "VELIS LydosHybrid by ariston "

User error, sorry :) TIL: there is a water_heater integration in HA and that works just fine:
service: water_heater.set_temperature
data:
  entity_id: water_heater.ariston
  temperature: 51


Cleanup plotting

Staged on top of #39.
(not really needed for v1.0.0)

I haven't had time to visually verify the the output images are the same. This PR can wait after v1.0.0 release I think.

After a somewhat painful rebase on master this is now ready for review.

@JanosJiri I've pushed a small change according to your suggestions. Please apply your formatter to the file and feel free to merge.


Could not find mnist/train6k-array in Multiclass Classification example

Hi
I am trying to execute the code referred in this page:  link
The code breaks when I execute with below error:

Traceback (most recent call last):
  File "multiclass_classification.py", line 4, in <module>
    data = tc.SFrame('mnist/train6k-array')
  File "/Users/ganapathiram/Documents/Ram/runtimes/turicreate/venv_turicreate/lib/python2.7/site-packages/turicreate/data_structures/sframe.py", line 812, in __init__
    raise ValueError('Unknown input type: ' + format)
  File "/Users/ganapathiram/Documents/Ram/runtimes/turicreate/venv_turicreate/lib/python2.7/site-packages/turicreate/cython/context.py", line 49, in __exit__
    raise exc_type(exc_value)
IOError: /Users/ganapathiram/Documents/Ram/runtimes/turicreate/mnist/train6k-array not found.

I have browsed to see if I can download but could not find an easy way. The python is the default one available in Mac OS.
I am executing this inside virtualenv.
Please let me know how to fix this.
Thanks
Ram

dup of #97


Fix playing video on iPhone

Fixes https://github.com/hugomyb/filament-media-action/issues/12
After reading a dozen articles and trying all the different solutions to this weird issue, I found out two things are necessary for this to work properly.

Calling load on the video element to trigger canplaythrough manually on iPhones.
Adding playsinline to prevent unwanted fullscreen video.

There were other suggestions like adding loop autoplay muted preload="none" controls="true" to the video element, tinkering with mimes, configuring the server for range requests, etc.
But these two changes seemed to be the only absolutely necessary ones.

Hi !
Thanks for your pull request, I merged your modifications in the latest version v<IP_ADDRESS>


ValidationData::initializeAndGatherData returns duplicates

Laravel Version: 8.59.0
PHP Version: 7.4.21
Database Driver & Version:

Description:
I am creating a custom validation rule that checks if max one value is true in an array. Because it works on arrays I tried reusing some of the same logic as the Laravel validator. The ValidationData::initializeAndGatherData returns duplicate data if attribute is "*".
Steps To Reproduce:
Illuminate\Validation\ValidationData::initializeAndGatherData("*", ["a", "b", "c"]);
expected: ["a", "b", "c"]
returns ["a", "b", "c", "a", "b", "c"]

Hey there,
Can you first please try one of the support channels below? If you can actually identify this as a bug, feel free to open up a new issue with a link to the original one and we'll gladly help you out.

Laracasts Forums
Laravel.io Forums
StackOverflow
Discord
Larachat
IRC

Thanks!


how to add channel constriction  in the pruning config

Hi, I've look through the docs and could not find how to set in the pruning config(suppose we use l1-norm-pruner) so that remained convs have channel number that is divisible by a certain number, say 8.
Thanks.

hello @RunningLeon , sorry we don't have this feature right now, but it's on our to-do list, which stage you want to apply the channel constriction, in pruner simulated pruning or in pruning speedup or both?
And could you explain why this feature is important to you so that we can re-evaluate this feature's priority?
For now, there is a workaround can make the remained channel number can be divisible by 8, you could set the sparsity to a certain value, here is an example:
    import math
    config_list = []
    target_remained = 0.3
    div_num = 8
    for name, module in model.named_modules():
        if isinstance(module, torch.nn.Conv2d):
            if module.out_channels < div_num:
                continue
            remained_num = math.ceil((module.out_channels // div_num) * target_remained) * div_num
            config_list.append({'op_names': [name], 'sparsity': (module.out_channels - remained_num) / module.out_channels})

hello @RunningLeon , sorry we don't have this feature right now, but it's on our to-do list, which stage you want to apply the channel constriction, in pruner simulated pruning or in pruning speedup or both? And could you explain why this feature is important to you so that we can re-evaluate this feature's priority?
For now, there is a workaround can make the remained channel number can be divisible by 8, you could set the sparsity to a certain value, here is an example:
    import math
    config_list = []
    target_remained = 0.3
    div_num = 8
    for name, module in model.named_modules():
        if isinstance(module, torch.nn.Conv2d):
            if module.out_channels < div_num:
                continue
            remained_num = math.ceil((module.out_channels // div_num) * target_remained) * div_num
            config_list.append({'op_names': [name], 'sparsity': (module.out_channels - remained_num) / module.out_channels})

@J-shang Hi, thanks for your reply. I'd prefer both.
The motivation is that for backends like TensorRT, if the channel number meets some requirements, the performance would be better. For instance, for structured sparsity for TensorRT, the channel number should be 128 * x, see this doc.
The workaround does not work for pruner which automatically decides different sparsity for different layers or convs.

@J-shang Hi, thanks for your reply.

I'd prefer both.
The motivation is that for backends like TensorRT, if the channel number meets some requirements, the performance would be better. For instance, for structured sparsity for TensorRT, the channel number should be 128 * x, see this doc.
The workaround does not work for pruner which automatically decides different sparsity for different layers or convs.

@RunningLeon , hello, thanks for your information. I believe this is a reasonable motivation for us to make this feature a higher priority, we will discuss about this feature and let you know if this is done.

Thanks a lot. Looking forward to this feature.


Can not run the example in quickstart

Describe the bug
Hi, I did cargo install<EMAIL_ADDRESS>&&     flutter_rust_bridge_codegen create doc && cd doc && flutter run on my terminal but error says:

Connected devices:
Linux (desktop) • linux  • linux-x64      • Ubuntu 22.04.3 LTS 6.2.0-39-generic
Chrome (web)    • chrome • web-javascript • Google Chrome 120.0.6099.129
[1]: Linux (linux)
[2]: Chrome (chrome)
Please choose one (or "q" to quit): 1
Launching lib/main.dart on Linux in debug mode...
SEVERE: error: linking with cc failed: exit status: 1
SEVERE:           collect2: error: ld returned 1 exit status
SEVERE: error: could not compile proc-macro2 (build script) due to 1 previous error
SEVERE: warning: build failed, waiting for other jobs to finish...
SEVERE: error: linking with cc failed: exit status: 1
SEVERE:           collect2: error: ld returned 1 exit status
SEVERE: error: could not compile libc (build script) due to 1 previous error
Building Linux application...
Error: Build process failed

Steps to reproduce
Hint: A simple way to reproduce is to clone and modify the https://github.com/fzyzcjy/flutter_rust_bridge/tree/master/frb_example/dart_minimal example package according to your needs.

cargo install<EMAIL_ADDRESS>&&     flutter_rust_bridge_codegen create doc && cd doc && flutter run

Logs
Connected devices:
Linux (desktop) • linux  • linux-x64      • Ubuntu 22.04.3 LTS 6.2.0-39-generic
Chrome (web)    • chrome • web-javascript • Google Chrome 120.0.6099.129
[1]: Linux (linux)
[2]: Chrome (chrome)
Please choose one (or "q" to quit): 1
Launching lib/main.dart on Linux in debug mode...
SEVERE: error: linking with `cc` failed: exit status: 1
SEVERE:           collect2: error: ld returned 1 exit status
SEVERE: error: could not compile `proc-macro2` (build script) due to 1 previous error
SEVERE: warning: build failed, waiting for other jobs to finish...
SEVERE: error: linking with `cc` failed: exit status: 1
SEVERE:           collect2: error: ld returned 1 exit status
SEVERE: error: could not compile `libc` (build script) due to 1 previous error
Building Linux application...
Error: Build process failed

Expected behavior
No response
Generated binding code
No response
OS
Ubuntu 22
Version of flutter_rust_bridge_codegen
2.0
Flutter info
No response
Version of clang++
No response
Additional context
No response

Hi, could you please flutter run --verbose and paste the logs?

[  +45 ms] executing: uname -m
[  +15 ms] Exit code 0 from: uname -m
[        ] x86_64
[ +245 ms] Artifact Instance of 'AndroidGenSnapshotArtifacts' is not required,
skipping update.
[   +6 ms] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required,
skipping update.
[   +1 ms] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping
update.
[   +1 ms] Artifact Instance of 'FlutterWebSdk' is not required, skipping
update.
[   +1 ms] Artifact Instance of 'LegacyCanvasKitRemover' is not required,
skipping update.
[   +7 ms] Artifact Instance of 'WindowsEngineArtifacts' is not required,
skipping update.
[   +1 ms] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping
update.
[   +1 ms] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping
update.
[   +1 ms] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required,
skipping update.
[   +1 ms] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required,
skipping update.
[   +1 ms] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required,
skipping update.
[   +1 ms] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required,
skipping update.
[ +124 ms] executing: /home/point/Android/Sdk/platform-tools/adb devices -l
[  +75 ms] List of devices attached
[  +13 ms] Artifact Instance of 'AndroidGenSnapshotArtifacts' is not required,
skipping update.
[        ] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required,
skipping update.
[        ] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping
update.
[  +18 ms] Artifact Instance of 'WindowsEngineArtifacts' is not required,
skipping update.
[        ] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping
update.
[   +2 ms] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required,
skipping update.
[   +1 ms] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required,
skipping update.
[        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required,
skipping update.
[        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required,
skipping update.
[ +143 ms] Connected devices:
[  +69 ms] Linux (desktop) • linux  • linux-x64      • Ubuntu 22.04.3 LTS
6.2.0-39-generic
[   +3 ms] Chrome (web)    • chrome • web-javascript • Google Chrome
120.0.6099.129
[   +1 ms] [1]: Linux (linux)
[        ] [2]: Chrome (chrome)
[   +2 ms] Please choose one (or "q" to quit)
[        ] :
[+2478 ms] 1
[  +33 ms] Skipping pub get: version match.
[ +183 ms] Found plugin rust_lib_doc at /home/point/flutter/doc/rust_builder/
[  +59 ms] Found plugin integration_test at
/home/point/snap/flutter/common/flutter/packages/integration_test/
[ +131 ms] Found plugin rust_lib_doc at /home/point/flutter/doc/rust_builder/
[  +30 ms] Found plugin integration_test at
/home/point/snap/flutter/common/flutter/packages/integration_test/
[  +97 ms] Found plugin rust_lib_doc at /home/point/flutter/doc/rust_builder/
[  +23 ms] Found plugin integration_test at
/home/point/snap/flutter/common/flutter/packages/integration_test/
[ +133 ms] Generating
/home/point/flutter/doc/android/app/src/main/java/io/flutter/plugins/GeneratedPl
uginRegistrant.java
[ +186 ms] No packages with native assets. Skipping native assets compilation.
[   +5 ms] Initializing file store
[  +15 ms] Skipping target: gen_localizations
[   +6 ms] gen_dart_plugin_registrant: Starting due to
{InvalidatedReasonKind.inputChanged: The following inputs have updated contents:
/home/point/flutter/doc/.dart_tool/package_config_subset}
[  +96 ms] Found plugin rust_lib_doc at /home/point/flutter/doc/rust_builder/
[  +16 ms] Found plugin integration_test at
/home/point/snap/flutter/common/flutter/packages/integration_test/
[  +32 ms] gen_dart_plugin_registrant: Complete
[   +1 ms] Skipping target: _composite
[   +3 ms] complete
[  +12 ms] Launching lib/main.dart on Linux in debug mode...
[   +8 ms]
/home/point/snap/flutter/common/flutter/bin/cache/dart-sdk/bin/dartaotruntime
--disable-dart-dev
/home/point/snap/flutter/common/flutter/bin/cache/dart-sdk/bin/snapshots/fronten
d_server_aot.dart.snapshot --sdk-root
/home/point/snap/flutter/common/flutter/bin/cache/artifacts/engine/common/flutte
r_patched_sdk/ --incremental --target=flutter --experimental-emit-debug-metadata
-DFLUTTER_WEB_AUTO_DETECT=true
-DFLUTTER_WEB_CANVASKIT_URL=https://www.gstatic.com/flutter-canvaskit/2e4ba9c6fb
499ccd4e81420543783cc7267ae406/ --output-dill
/tmp/flutter_tools.HNBGUS/flutter_tool.YWXXFC/app.dill --packages
/home/point/flutter/doc/.dart_tool/package_config.json -Ddart.vm.profile=false
-Ddart.vm.product=false --enable-asserts --track-widget-creation
--filesystem-scheme org-dartlang-root --initialize-from-dill
build/26c1224f28ba1925f2521c2679048535.cache.dill.track.dill --verbosity=error
--enable-experiment=alternative-invalidation-strategy
[  +55 ms] Building Linux application...
[  +33 ms] <- compile package:doc/main.dart
[  +24 ms] executing: [build/linux/x64/debug/] cmake -G Ninja
-DCMAKE_BUILD_TYPE=Debug -DFLUTTER_TARGET_PLATFORM=linux-x64
/home/point/flutter/doc/linux
[ +128 ms] -- Configuring done
[   +3 ms] -- Generating done
[   +6 ms] -- Build files have been written to:
/home/point/flutter/doc/build/linux/x64/debug
[  +32 ms] executing: ninja -C build/linux/x64/debug install
[ +128 ms] ninja: Entering directory `build/linux/x64/debug'
[+2895 ms] [1/6] Generating librust_lib_doc.so, phony
[   +7 ms] FAILED: plugins/rust_lib_doc/librust_lib_doc.so
plugins/rust_lib_doc/phony
[ +149 ms] cd /home/point/flutter/doc/build/linux/x64/debug/plugins/rust_lib_doc
&& /snap/flutter/145/usr/bin/cmake -E env
CARGOKIT_CMAKE=/snap/flutter/145/usr/bin/cmake CARGOKIT_CONFIGURATION=Debug
CARGOKIT_MANIFEST_DIR=/home/point/flutter/doc/linux/flutter/ephemeral/.plugin_sy
mlinks/rust_lib_doc/linux/../../rust
CARGOKIT_TARGET_TEMP_DIR=/home/point/flutter/doc/build/linux/x64/debug/plugins/r
ust_lib_doc/cargokit_build
CARGOKIT_OUTPUT_DIR=/home/point/flutter/doc/build/linux/x64/debug/plugins/rust_l
ib_doc CARGOKIT_TARGET_PLATFORM=linux-x64
CARGOKIT_TOOL_TEMP_DIR=/home/point/flutter/doc/build/linux/x64/debug/plugins/rus
t_lib_doc/cargokit_build/tool
CARGOKIT_ROOT_PROJECT_DIR=/home/point/flutter/doc/linux
/home/point/flutter/doc/rust_builder/cargokit/run_build_tool.sh build-cmake
[  +19 ms] INFO: Precompiled binaries are disabled
[   +7 ms] INFO: Building rust_lib_doc for x86_64-unknown-linux-gnu
[        ] SEVERE:
================================================================================
[        ] SEVERE: Cargokit BuildTool failed with error:
[        ] SEVERE:

[        ] SEVERE: External Command: rustup "run" "stable" "cargo" "build"
"--manifest-path" "/home/point/flutter/doc/rust/Cargo.toml" "-p" "rust_lib_doc"
"--target" "x86_64-unknown-linux-gnu" "--target-dir"
"/home/point/flutter/doc/build/linux/x64/debug/plugins/rust_lib_doc/cargokit_bui
ld"
[   +4 ms] SEVERE: Returned Exit Code: 101
[        ] SEVERE:
[   +4 ms] SEVERE: STDOUT:
[        ] SEVERE:
[        ] SEVERE: STDERR:
[   +2 ms] SEVERE: Compiling libc v0.2.150
[        ] SEVERE:    Compiling proc-macro2 v1.0.70
[   +1 ms] SEVERE: error: linking with cc failed: exit status: 1
[  +25 ms] SEVERE:   |
[ +105 ms] SEVERE:   = note: LC_ALL="C"
PATH="/home/point/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib
/x86_64-unknown-linux-gnu/bin:/snap/flutter/current/usr/bin:/snap/flutter/curren
t/bin:/home/point/snap/flutter/common/flutter/bin:/snap/flutter/current/usr/bin:
/snap/flutter/current/bin:/home/point/snap/flutter/common/flutter/bin:/home/poin
t/vcpkg:/home/point/.cargo/bin:/home/point/.nvm/versions/node/v20.11.0/bin:/home
/point/.local/bin:/home/point/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/
bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/snap/bin:/home/point/.loca
l/share/JetBrains/Toolbox/scripts:/home/point/cling_2020-11-05_ROOT-ubuntu2004/b
in" VSLANG="1033" "cc" "-m64" "/tmp/rustcDGhsdv/symbols.o"
"/home/point/flutter/doc/build/linux/x64/debug/plugins/rust_lib_doc/cargokit_bui
ld/debug/build/proc-macro2-2257f79b3cc59fd9/build_script_build-2257f79b3cc59fd9.
build_script_build.2f144325cdd186e2-cgu.0.rcgu.o"
"/home/point/flutter/doc/build/linux/x64/debug/plugins/rust_lib_doc/cargokit_bui
ld/debug/build/proc-macro2-2257f79b3cc59fd9/build_script_build-2257f79b3cc59fd9.
build_script_build.2f144325cdd186e2-cgu.1.rcgu.o"
"/home/point/flutter/doc/build/linux/x64/debug/plugins/rust_lib_doc/cargokit_bui
ld/debug/build/proc-macro2-2257f79b3cc59fd9/build_script_build-2257f79b3cc59fd9.
build_script_build.2f144325cdd186e2-cgu.2.rcgu.o"
"/home/point/flutter/doc/build/linux/x64/debug/plugins/rust_lib_doc/cargokit_bui
ld/debug/build/proc-macro2-2257f79b3cc59fd9/build_script_build-2257f79b3cc59fd9.
4n4yopk1y2c8z15f.rcgu.o" "-Wl,--as-needed" "-L"
"/home/point/flutter/doc/build/linux/x64/debug/plugins/rust_lib_doc/cargokit_bui
ld/debug/deps" "-L"
"/home/point/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_
64-unknown-linux-gnu/lib" "-Wl,-Bstatic"
"/home/point/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_
64-unknown-linux-gnu/lib/libstd-66d8041607d2929b.rlib"
"/home/point/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_
64-unknown-linux-gnu/lib/libpanic_unwind-a57e2388c0aea9b1.rlib"
"/home/point/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_
64-unknown-linux-gnu/lib/libobject-dcd9be90ae2cb505.rlib"
"/home/point/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_
64-unknown-linux-gnu/lib/libmemchr-516789932d161b4e.rlib"
"/home/point/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_
64-unknown-linux-gnu/lib/libaddr2line-1ff34b0cf871cb60.rlib"
"/home/point/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_
64-unknown-linux-gnu/lib/libgimli-0c110dd0650d6cb7.rlib"
"/home/point/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_
64-unknown-linux-gnu/lib/librustc_demangle-a6e97aae2681ad8f.rlib"
"/home/point/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_
64-unknown-linux-gnu/lib/libstd_detect-b93dac2525ec4d1e.rlib"
"/home/point/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_
64-unknown-linux-gnu/lib/libhashbrown-ce1d65fb391ae98b.rlib"
"/home/point/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_
64-unknown-linux-gnu/lib/librustc_std_workspace_alloc-8933a2fb54d88492.rlib"
"/home/point/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_
64-unknown-linux-gnu/lib/libminiz_oxide-306712ebb1ee1a3f.rlib"
"/home/point/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_
64-unknown-linux-gnu/lib/libadler-349c574f342b0d30.rlib"
"/home/point/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_
64-unknown-linux-gnu/lib/libunwind-65c422a3ad95273d.rlib"
"/home/point/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_
64-unknown-linux-gnu/lib/libcfg_if-7e6330a6c0cb9441.rlib"
"/home/point/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_
64-unknown-linux-gnu/lib/liblibc-39c59240bfdfab27.rlib"
"/home/point/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_
64-unknown-linux-gnu/lib/liballoc-e9d126c51bb8b2bb.rlib"
"/home/point/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_
64-unknown-linux-gnu/lib/librustc_std_workspace_core-5af394d9b1f07bdc.rlib"
"/home/point/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_
64-unknown-linux-gnu/lib/libcore-693a8f23970c5917.rlib"
"/home/point/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_
64-unknown-linux-gnu/lib/libcompiler_builtins-13fc9d1ed9c7a2bc.rlib"
"-Wl,-Bdynamic" "-lgcc_s" "-lutil" "-lrt" "-lpthread" "-lm" "-ldl" "-lc"
"-Wl,--eh-frame-hdr" "-Wl,-z,noexecstack" "-L"
"/home/point/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_
64-unknown-linux-gnu/lib" "-o"
"/home/point/flutter/doc/build/linux/x64/debug/plugins/rust_lib_doc/cargokit_bui
ld/debug/build/proc-macro2-2257f79b3cc59fd9/build_script_build-2257f79b3cc59fd9"
"-Wl,--gc-sections" "-pie" "-Wl,-z,relro,-z,now" "-nodefaultlibs"
[  +27 ms] SEVERE:   = note: /snap/flutter/current/usr/bin/ld:
/usr/lib/gcc/x86_64-linux-gnu/11/liblto_plugin.so: error loading plugin:
/snap/flutter/145/usr/bin/../../lib/x86_64-linux-gnu/libc.so.6: version
GLIBC_2.33' not found (required by /usr/lib/gcc/x86_64-linux-gnu/11/liblto_plugin.so) [  +10 ms] SEVERE:           collect2: error: ld returned 1 exit status [        ] SEVERE:            [        ] SEVERE:  [        ] SEVERE: error: could not compile proc-macro2(build script) due to 1 previous error [        ] SEVERE: warning: build failed, waiting for other jobs to finish... [        ] SEVERE: error: linking withccfailed: exit status: 1 [        ] SEVERE:   | [ +122 ms] SEVERE:   = note: LC_ALL="C" PATH="/home/point/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib /x86_64-unknown-linux-gnu/bin:/snap/flutter/current/usr/bin:/snap/flutter/curren t/bin:/home/point/snap/flutter/common/flutter/bin:/snap/flutter/current/usr/bin: /snap/flutter/current/bin:/home/point/snap/flutter/common/flutter/bin:/home/poin t/vcpkg:/home/point/.cargo/bin:/home/point/.nvm/versions/node/v20.11.0/bin:/home /point/.local/bin:/home/point/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/ bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/snap/bin:/home/point/.loca l/share/JetBrains/Toolbox/scripts:/home/point/cling_2020-11-05_ROOT-ubuntu2004/b in" VSLANG="1033" "cc" "-m64" "/tmp/rustcFmCIGg/symbols.o" "/home/point/flutter/doc/build/linux/x64/debug/plugins/rust_lib_doc/cargokit_bui ld/debug/build/libc-3d6003ca1f7bafc7/build_script_build-3d6003ca1f7bafc7.build_s cript_build.6d0b1aae691defa6-cgu.0.rcgu.o" "/home/point/flutter/doc/build/linux/x64/debug/plugins/rust_lib_doc/cargokit_bui ld/debug/build/libc-3d6003ca1f7bafc7/build_script_build-3d6003ca1f7bafc7.build_s cript_build.6d0b1aae691defa6-cgu.1.rcgu.o" "/home/point/flutter/doc/build/linux/x64/debug/plugins/rust_lib_doc/cargokit_bui ld/debug/build/libc-3d6003ca1f7bafc7/build_script_build-3d6003ca1f7bafc7.build_s cript_build.6d0b1aae691defa6-cgu.2.rcgu.o" "/home/point/flutter/doc/build/linux/x64/debug/plugins/rust_lib_doc/cargokit_bui ld/debug/build/libc-3d6003ca1f7bafc7/build_script_build-3d6003ca1f7bafc7.build_s cript_build.6d0b1aae691defa6-cgu.3.rcgu.o" "/home/point/flutter/doc/build/linux/x64/debug/plugins/rust_lib_doc/cargokit_bui ld/debug/build/libc-3d6003ca1f7bafc7/build_script_build-3d6003ca1f7bafc7.5anfc1b 3rpvnaiu7.rcgu.o" "-Wl,--as-needed" "-L" "/home/point/flutter/doc/build/linux/x64/debug/plugins/rust_lib_doc/cargokit_bui ld/debug/deps" "-L" "/home/point/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_ 64-unknown-linux-gnu/lib" "-Wl,-Bstatic" "/home/point/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_ 64-unknown-linux-gnu/lib/libstd-66d8041607d2929b.rlib" "/home/point/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_ 64-unknown-linux-gnu/lib/libpanic_unwind-a57e2388c0aea9b1.rlib" "/home/point/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_ 64-unknown-linux-gnu/lib/libobject-dcd9be90ae2cb505.rlib" "/home/point/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_ 64-unknown-linux-gnu/lib/libmemchr-516789932d161b4e.rlib" "/home/point/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_ 64-unknown-linux-gnu/lib/libaddr2line-1ff34b0cf871cb60.rlib" "/home/point/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_ 64-unknown-linux-gnu/lib/libgimli-0c110dd0650d6cb7.rlib" "/home/point/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_ 64-unknown-linux-gnu/lib/librustc_demangle-a6e97aae2681ad8f.rlib" "/home/point/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_ 64-unknown-linux-gnu/lib/libstd_detect-b93dac2525ec4d1e.rlib" "/home/point/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_ 64-unknown-linux-gnu/lib/libhashbrown-ce1d65fb391ae98b.rlib" "/home/point/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_ 64-unknown-linux-gnu/lib/librustc_std_workspace_alloc-8933a2fb54d88492.rlib" "/home/point/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_ 64-unknown-linux-gnu/lib/libminiz_oxide-306712ebb1ee1a3f.rlib" "/home/point/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_ 64-unknown-linux-gnu/lib/libadler-349c574f342b0d30.rlib" "/home/point/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_ 64-unknown-linux-gnu/lib/libunwind-65c422a3ad95273d.rlib" "/home/point/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_ 64-unknown-linux-gnu/lib/libcfg_if-7e6330a6c0cb9441.rlib" "/home/point/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_ 64-unknown-linux-gnu/lib/liblibc-39c59240bfdfab27.rlib" "/home/point/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_ 64-unknown-linux-gnu/lib/liballoc-e9d126c51bb8b2bb.rlib" "/home/point/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_ 64-unknown-linux-gnu/lib/librustc_std_workspace_core-5af394d9b1f07bdc.rlib" "/home/point/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_ 64-unknown-linux-gnu/lib/libcore-693a8f23970c5917.rlib" "/home/point/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_ 64-unknown-linux-gnu/lib/libcompiler_builtins-13fc9d1ed9c7a2bc.rlib" "-Wl,-Bdynamic" "-lgcc_s" "-lutil" "-lrt" "-lpthread" "-lm" "-ldl" "-lc" "-Wl,--eh-frame-hdr" "-Wl,-z,noexecstack" "-L" "/home/point/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_ 64-unknown-linux-gnu/lib" "-o" "/home/point/flutter/doc/build/linux/x64/debug/plugins/rust_lib_doc/cargokit_bui ld/debug/build/libc-3d6003ca1f7bafc7/build_script_build-3d6003ca1f7bafc7" "-Wl,--gc-sections" "-pie" "-Wl,-z,relro,-z,now" "-nodefaultlibs" [  +15 ms] SEVERE:   = note: /snap/flutter/current/usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/11/liblto_plugin.so: error loading plugin: /snap/flutter/145/usr/bin/../../lib/x86_64-linux-gnu/libc.so.6: versionGLIBC_2.33' not found (required by
/usr/lib/gcc/x86_64-linux-gnu/11/liblto_plugin.so)
[        ] SEVERE:           collect2: error: ld returned 1 exit status
[        ] SEVERE:
[        ] SEVERE:
[        ] SEVERE: error: could not compile libc (build script) due to 1
previous error
[        ] SEVERE:
[        ] SEVERE: #0      runCommand (package:build_tool/src/util.dart:121:5)
[        ] SEVERE: #1      RustBuilder.build
(package:build_tool/src/builder.dart:142:5)
[        ] SEVERE:
[        ] SEVERE: #2      ArtifactProvider.getArtifacts
(package:build_tool/src/artifacts_provider.dart:71:25)
[        ] SEVERE:
[   +6 ms] SEVERE: #3      BuildCMake.build
(package:build_tool/src/build_cmake.dart:29:23)
[        ] SEVERE:
[        ] SEVERE: #4      BuildCMakeCommand.runBuildCommand
(package:build_tool/src/build_tool.dart:79:5)
[        ] SEVERE:
[        ] SEVERE: #5      BuildCommand.run
(package:build_tool/src/build_tool.dart:37:5)
[   +1 ms] SEVERE:
[        ] SEVERE: #6      CommandRunner.runCommand
(package:args/command_runner.dart:212:13)
[        ] SEVERE:
[        ] SEVERE: #7      runMain
(package:build_tool/src/build_tool.dart:251:5)
[        ] SEVERE:
[        ] SEVERE:
[        ] SEVERE: BuildTool arguments: [build-cmake]
[        ] SEVERE:
[+2741 ms] [2/6] Generating
/home/point/flutter/doc/linux/flutter/ephemeral/libflutter_linux_gtk.so,
/home/point/flutter/doc/linux/flutter/ephemeral/flutter_linux/fl_basic_message_c
hannel.h,
/home/point/flutter/doc/linux/flutter/ephemeral/flutter_linux/fl_binary_codec.h,
/home/point/flutter/doc/linux/flutter/ephemeral/flutter_linux/fl_binary_messenge
r.h,
/home/point/flutter/doc/linux/flutter/ephemeral/flutter_linux/fl_dart_project.h,
/home/point/flutter/doc/linux/flutter/ephemeral/flutter_linux/fl_engine.h,
/home/point/flutter/doc/linux/flutter/ephemeral/flutter_linux/fl_json_message_co
dec.h,
/home/point/flutter/doc/linux/flutter/ephemeral/flutter_linux/fl_json_method_cod
ec.h,
/home/point/flutter/doc/linux/flutter/ephemeral/flutter_linux/fl_message_codec.h
,
/home/point/flutter/doc/linux/flutter/ephemeral/flutter_linux/fl_method_call.h,
/home/point/flutter/doc/linux/flutter/ephemeral/flutter_linux/fl_method_channel.
h,
/home/point/flutter/doc/linux/flutter/ephemeral/flutter_linux/fl_method_codec.h,
/home/point/flutter/doc/linux/flutter/ephemeral/flutter_linux/fl_method_response
.h,
/home/point/flutter/doc/linux/flutter/ephemeral/flutter_linux/fl_plugin_registra
r.h,
/home/point/flutter/doc/linux/flutter/ephemeral/flutter_linux/fl_plugin_registry
.h,
/home/point/flutter/doc/linux/flutter/ephemeral/flutter_linux/fl_standard_messag
e_codec.h,
/home/point/flutter/doc/linux/flutter/ephemeral/flutter_linux/fl_standard_method
_codec.h,
/home/point/flutter/doc/linux/flutter/ephemeral/flutter_linux/fl_string_codec.h,
/home/point/flutter/doc/linux/flutter/ephemeral/flutter_linux/fl_value.h,
/home/point/flutter/doc/linux/flutter/ephemeral/flutter_linux/fl_view.h,
/home/point/flutter/doc/linux/flutter/ephemeral/flutter_linux/flutter_linux.h,
phony
[   +4 ms] [ +109 ms] executing: uname -m
[   +1 ms] [  +73 ms] Exit code 0 from: uname -m
[        ] [        ] x86_64
[        ] [ +132 ms] Artifact Instance of 'AndroidGenSnapshotArtifacts' is not
required, skipping update.
[   +7 ms] [   +5 ms] Artifact Instance of 'AndroidInternalBuildArtifacts' is
not required, skipping update.
[        ] [        ] Artifact Instance of 'IOSEngineArtifacts' is not required,
skipping update.
[        ] [        ] Artifact Instance of 'FlutterWebSdk' is not required,
skipping update.
[        ] [        ] Artifact Instance of 'LegacyCanvasKitRemover' is not
required, skipping update.
[        ] [  +10 ms] Artifact Instance of 'WindowsEngineArtifacts' is not
required, skipping update.
[        ] [   +3 ms] Artifact Instance of 'MacOSEngineArtifacts' is not
required, skipping update.
[        ] [        ] Artifact Instance of 'LinuxEngineArtifacts' is not
required, skipping update.
[        ] [        ] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not
required, skipping update.
[        ] [        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not
required, skipping update.
[        ] [        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not
required, skipping update.
[        ] [   +6 ms] Artifact Instance of 'FlutterRunnerDebugSymbols' is not
required, skipping update.
[        ] [ +649 ms] Artifact Instance of 'MaterialFonts' is not required,
skipping update.
[        ] [   +3 ms] Artifact Instance of 'GradleWrapper' is not required,
skipping update.
[   +2 ms] [        ] Artifact Instance of 'AndroidGenSnapshotArtifacts' is not
required, skipping update.
[   +2 ms] [        ] Artifact Instance of 'AndroidInternalBuildArtifacts' is
not required, skipping update.
[        ] [        ] Artifact Instance of 'IOSEngineArtifacts' is not required,
skipping update.
[        ] [   +2 ms] Artifact Instance of 'FlutterWebSdk' is not required,
skipping update.
[        ] [        ] Artifact Instance of 'LegacyCanvasKitRemover' is not
required, skipping update.
[   +5 ms] [        ] Artifact Instance of 'FlutterSdk' is not required,
skipping update.
[        ] [   +5 ms] Artifact Instance of 'WindowsEngineArtifacts' is not
required, skipping update.
[        ] [        ] Artifact Instance of 'MacOSEngineArtifacts' is not
required, skipping update.
[   +2 ms] [   +2 ms] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not
required, skipping update.
[        ] [        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not
required, skipping update.
[   +1 ms] [        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not
required, skipping update.
[        ] [        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not
required, skipping update.
[        ] [        ] Artifact Instance of 'IosUsbArtifacts' is not required,
skipping update.
[        ] [        ] Artifact Instance of 'IosUsbArtifacts' is not required,
skipping update.
[        ] [   +3 ms] Artifact Instance of 'IosUsbArtifacts' is not required,
skipping update.
[        ] [        ] Artifact Instance of 'IosUsbArtifacts' is not required,
skipping update.
[        ] [        ] Artifact Instance of 'IosUsbArtifacts' is not required,
skipping update.
[        ] [        ] Artifact Instance of 'FontSubsetArtifacts' is not
required, skipping update.
[        ] [        ] Artifact Instance of 'PubDependencies' is not required,
skipping update.
[        ] [ +125 ms] Initializing file store
[        ] [  +15 ms] Done initializing file store
[        ] [ +212 ms] Skipping target: native_assets
[        ] [   +5 ms] Skipping target: gen_localizations
[        ] [   +3 ms] Skipping target: gen_dart_plugin_registrant
[        ] [ +903 ms] Skipping target: unpack_linux
[        ] [ +675 ms] Skipping target: kernel_snapshot
[        ] [ +455 ms] Skipping target: debug_bundle_linux-x64_assets
[        ] [   +8 ms] Persisting file store
[        ] [  +32 ms] Done persisting file store
[        ] [  +29 ms] build succeeded.
[        ] [  +32 ms] "flutter assemble" took 3,237ms.
[        ] [ +274 ms] ensureAnalyticsSent: 251ms
[        ] [        ] Running 0 shutdown hooks
[        ] [        ] Shutdown hooks complete
[        ] [   +7 ms] exiting with code 0
[   +5 ms] ninja: build stopped: subcommand failed.
[  +30 ms] Building Linux application... (completed in 6.6s)
[+9580 ms] Error: Build process failed
[   +2 ms] "flutter run" took 20,473ms.
[  +12 ms]
#0      throwToolExit
(package:flutter_tools/src/base/common.dart:10:3)
#1      RunCommand.runCommand
(package:flutter_tools/src/commands/run.dart:815:9)

#2      FlutterCommand.run.
(package:flutter_tools/src/runner/flutter_command.dart:1389:27)

#3      AppContext.run.
(package:flutter_tools/src/base/context.dart:153:19)

#4      CommandRunner.runCommand
(package:args/command_runner.dart:212:13)

#5      FlutterCommandRunner.runCommand.
(package:flutter_tools/src/runner/flutter_command_runner.dart:355:9)

#6      AppContext.run.
(package:flutter_tools/src/base/context.dart:153:19)

#7      FlutterCommandRunner.runCommand
(package:flutter_tools/src/runner/flutter_command_runner.dart:295:5)

#8      run..
(package:flutter_tools/runner.dart:119:9)

#9      AppContext.run.
(package:flutter_tools/src/base/context.dart:153:19)

#10     main (package:flutter_tools/executable.dart:90:3)

[ +279 ms] ensureAnalyticsSent: 251ms
[        ] Running 1 shutdown hook
[  +12 ms] Shutdown hooks complete
[   +6 ms] exiting with code 1

/usr/lib/gcc/x86_64-linux-gnu/11/liblto_plugin.so: error loading plugin:
/snap/flutter/145/usr/bin/../../lib/x86_64-linux-gnu/libc.so.6: version
`GLIBC_2.33' not found (required by
/usr/lib/gcc/x86_64-linux-gnu/11/liblto_plugin.so)

The error message: version `GLIBC_2.33' not found
Maybe have a look at  https://cjycode.com/flutter_rust_bridge/manual/troubleshooting#issues-with-glibc-eg-version-glibc_233-not-found

How can I install the flutter without snap?

I guess googling or looking at Flutter official website may show some approaches.

Thanks it works.

(Close since it was solved)


A few questions...

Good job!!!
I am a security researcher and would be interested in asking you some questions:
Would this script work exclusively in a corporate LAN?
Could this script be an exploit in the wild?
Could this vulnerability apply in a Server scenario and not just a client scenario?
What degree of dangerousness would you give to this vulnerbaility? (LOW,MEDIUM;HIGH,CRITICAL)
Thank you very much and congratulations on your research.
Gianluca.

Hi,
this PoC just demonstrates another (among many others) way of getting around UAC and it further demonstrates how broken its design is.
Sysadmins should never trust this boundary due to the fact neither MS trusts their own design.
The PoC works on default Windows installations (without any network requirements) and also on Servers.
But on servers, UAC doesn't make that much sense as a concept in general.


Remove non_float webgl env from all_env, but have all tests use all_env

This change is

Reviewed 4 of 18 files at r1.
Review status: 4 of 18 files reviewed at latest revision, all discussions resolved, some commit checks failed.

src/kernels/backend_webgl.ts, line 1010 at r1 (raw file):

  // TODO(smilkov): Remove these two methods (used only in tests), and make
  // engine.backend private.
  getGPGPUContext(): GPGPUContext {

I think this will break demos. Can you run build_and_lint_all?

Comments from Reviewable

Review status: 4 of 18 files reviewed at latest revision, 1 unresolved discussion, some commit checks failed.

src/kernels/backend_webgl.ts, line 1010 at r1 (raw file):
Previously, nsthorat (Nikhil Thorat) wrote…
I think this will break demos. Can you run build_and_lint_all?

No demos broken.

Comments from Reviewable


Fix wicg_scheduler.js externs

Due to commit 876761b33479c1cade1e37e648d6afc4693d9ba6 I'm no longer able to compile my project using --language_in ECMASCRIPT5_STRICT because compilation fails with externs.zip//wicg_scheduler.js:56:50: ERROR - [JSC_LANGUAGE_FEATURE] This language feature is only supported for ECMASCRIPT_2015 mode or better: default parameter. error.

bug scrub: The change that caused this problem is now rolledback


GCC-6 cannot link cblas on travis.

The problem was that gcc was trying to link it statically, so the order of the arguments matter.
It was solved in commit 29e9a20


Vulcanized file doesn't work in Firefox "ReferenceError: Polymer is not defined"

Got trouble to get a vulcanized polymer project running in firefox.
The page is total empty in Firefox and i get these error:
"ReferenceError: Polymer is not defined"
I striped it down to these examples:
Test element ff-test.html:
<dom-module id="ff-test">
    <template>
        Test FF.
    </template>
</dom-module>
<script>
    Polymer({
        is: "ff-test"
    });
</script>

Not Vulcanized test file (works in Chrome and Firefox)
<!doctype html>
<html>
    <head>
        <title>FF Test</title>
        <meta charset="utf-8">
        <meta name="viewport" content="width=device-width, minimum-scale=1.0, initial-scale=1.0, user-scalable=yes">
        <script src="bower_components/webcomponentsjs/webcomponents-lite.min.js"></script>
        <link rel="import" href="bower_components/polymer/polymer.html">
        <link rel="import" href="ff-test.html">
    </head>
    <body>
        <ff-test></ff-test>
    </body>
</html>

Vulcanized test file (works only in Chrome, not in Firefox)
<!doctype html>
<html>
    <head>
        <title>FF Test</title>
        <meta charset="utf-8">
        <meta name="viewport" content="width=device-width, minimum-scale=1.0, initial-scale=1.0, user-scalable=yes">
        <script src="bower_components/webcomponentsjs/webcomponents-lite.min.js"></script>
        <link rel="import" href="bower_components/polymer/polymer.html">
    </head>
    <body class="fullbleed">
        <div hidden="" by-vulcanize="">
            <dom-module id="ff-test" assetpath="/">
                <template>
                    Test FF.
                </template>
            </dom-module>
            <script>
                Polymer({
                    is: "ff-test"
                });
            </script>
        </div>
        <ff-test></ff-test>
    </body>
</html>

I get the same problem when webcomponents-lite.min.js and polymer.html are also inline.

Tested with:
polymer: 1.1.1
webcomponentsjs: 0.7.12
vulcanize: 1.10.3

Tried the same example in Firefox and IE11, it's a bug indeed.

Workaround seems to be wrapping the code in "WebComponentsReady" listener
            <script>
                window.addEventListener("WebComponentsReady", function(){
                    console.log("ready");
                    Polymer({
                        is: "ff-test"
                    });
                });
            </script>

I can confirm this, see #231

The example works with the "WebComponentsReady" listener, thanks :).
Is there a way to get vulcanize to build the html in this way?
Correcting a big project with lots of imports manual after each vulcanize would be pretty time consuming...

Found out that using crisper avoids this problem.

Looks like a polymer change. Bisected to Polymer/polymer@051e1bffc3c2dd8104a4a48a53211027d41aa1ed

This also breaks safari, and I image every browser that isn't chrome.

I'm still getting this issue in FireFox version 47.0 and Polymer 1.6.1. Was the fix incorporated into Polymer? Or are we supposed to just wrap our code in a WebComponentsReady listener?

Still same issue in FIrefox 49.0.2 with Polymer 1.7.0, as well as the same issue happens in Microsoft Edge.

Same issue in FIrefox 51.0.1 with Polymer 1.7.0. Really thinking to abandon Polymer and passing to Angular 2 It is a too unpredictable library...
Any really useful workaround?


HasOneRelation though another using the wrong key

// In class Message

fromAddress: {
  relation: Model.HasOneRelation,
  modelClass: require.resolve('./emailAddress'),
  join: {
    from: 'messages.id',
    through: {
      from: 'message_from_addresses.message_id',
      to: 'message_from_addresses.email_address_id'
    },
    to: 'email_addresses.id',
  },
},

When I do:
await message.$relatedQuery('fromAddress')

It seems to be simply be querying email_addresses.id = messages.id and ignoring the join table.

Through can only be used with ManyToManyRelation and HasOneThroughRelation.

Total user error. I was just coming here to post that and close this, thanks.


[release blocker] Fix user popup positioning.

This issue is about the placement of the user popover menu.
If you have a small screen (or just make your browser window short) and click on a message near the center of the page, the user menu will be cropped.  If somebody's screen height is less than about 550 pixels, we just make the vertical position exactly in the center of the screen (regardless of the click point).
If you have a thin screen (i.e. mobile web), then open the user menu using the buddy list chevron, it will fall off the left side of the screen.  If the screen width is less than about 600 pixels, we should just center it horizontally, and it's fine if it's over the buddy list.  (The same applies for clicking on the avatar in the message feed, although you might tweak the cutoff width there).
It's best to do this just in JS, not CSS.
More context here:
https://chat.zulip.org/#narrow/stream/9-issues/topic/user.20menus.20cropped/near/695185

@zulipbot claim

@zulipbot claim

Is this issue resolved? or can I still work on it?

@phoenikx I am actually working on this already. @showell assigned this to me. More here: https://chat.zulip.org/#narrow/stream/9-issues/topic/user.20menus.20cropped/near/696247


TrafficLightsBuzzerTuple unused?

TrafficLightsBuzzerTuple is declared in boards.py but is not used.

Fixed in #138


🐛  Uplift to gopkg.in/yaml to v3.0.0

Current gopkg.in/yaml.v3 has vulnerabilities. See https://github.com/advisories/GHSA-hp87-p4gw-j4gq for details. Uplifting
the package to v3.0.0 should solve this.

/test-v1b1-ubuntu-integration

/assign @Xenwar

/cherry-pick release-0.5

/cherrypick release-0.5


Copy As GitHub Permalink not working for enterprise GitHub

Type: Bug
This is a variation on #4245, which took me awhile to figure out.
I have github-enterprise.uri set to the correct enterprise host, call it https://git.foobar.com. However my repo was cloned without the FQDN, so my remote looked like git@git:org/repo.git. Github permalinks were pointing to github.com rather than git.foobar.com. It took me quite awhile to figure out what the problem was, but editing the remote URL in .git/config fixed the issue.
I think it would be ideal if the permalinks were correctly generated regardless of the domain name used to clone the repo, but if that's not possible, it would be great if there were some way to provide a hint of what the problem is.
Regardless, I absolutely love this feature! :heart_eyes:
Extension version: 0.62.0
VS Code version: Code 1.77.0 (7f329fe6c66b0f86ae1574c2911b681ad5a45d63, 2023-03-29T10:05:35.165Z)
OS version: Linux x64 4.15.0-208-generic
Modes:
Sandboxed: Yes

System Info

Item
Value

CPUs
Intel(R) Xeon(R) CPU E5-2620 v3 @ 2.40GHz (24 x 1680)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: disabled_softwarevideo_encode: disabled_softwarevulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_off

Load (avg)
1, 1, 1

Memory (System)
125.82GB (118.17GB free)

Process Argv
--crash-reporter-id 8d88996b-5509-4503-a902-c9771ae124cb

Screen Reader
no

VM
0%

DESKTOP_SESSION
xsession

XDG_CURRENT_DESKTOP
GNOME-Flashback:GNOME

XDG_SESSION_DESKTOP
xsession

XDG_SESSION_TYPE
x11

A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492cf:30256860
vslsvsres303:30308271
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscorecescf:30445987
pythondataviewer:30285071
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593:30376534
pythonvs932:30410667
cppdebug:30492333
vsclangdf:30486550
c4g48928:30535728
dsvsc012cf:30540253
pynewext54:30695312
azure-dev_surveyone:30548225
nodejswelcome1cf:30587006
2e4cg342:30602488
pyind779:30671433
f6dab269:30613381
pythonsymbol12:30671437
2i9eh265:30646982
vsctsb:30677850
pythonb192:30669360
azdwalk:30687957
pythonms35:30701012

@hellige are you using url aliasing like in https://github.com/microsoft/vscode-pull-request-github/issues/4551?

@alexr00 no, I don't think the situation in that issue applies to me. I've never used insteadOf or pushInsteadOf, and have no [url] sections in my config. It's only that I access GHE from my office workstation where we have DNS search domains configured, so the host git automatically resolves to git.foobar.com.

Verified with code review


Does not show up in Eve, Home+, or VIZ Designer apps

The controls for WLED show up fine in Home App, but do not show in any other control apps.  Is this able to be done?

This plugin is currently only designed to be used in the Home App. Due it is a Homebridge Plugin I do not think so that it is possible to be shown at other apps.

This plugin is currently only designed to be used in the Home App. Due it is a Homebridge Plugin I do not think so that it is possible to be shown at other apps.

It should be able to show in companion apps since data is pulled from the Home app.  All my other accessories that I run through Homebridge (and I have a ton across about 12 plug-ins) will show in Eve, Home+, etc.  The accessories from this app and my Denon/Marantz app are the only ones that will not show in others.
I am a noob at how this stuff works on a programming side so I am not saying it can be done, just saying it does work on others.
Great app though.  I thank you for the time it takes to build something like this for the benefit of others!
Thanks,
Shaun

+1
I have no other plugins behaves like this.
As it's in the home app it should be shown in other apps (i.e. elegato eve in my case) that use Apple's HomeKit infrastructure.
As mentioned before: great plugin. Really! - with only this quirk.
Is there any way to get around this behaviour?


useDebugValue order changing on component, throwing warning.

Environment
System:

OS: Windows 10 10.0.18363
CPU: (8) x64 Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz
Memory: 19.00 GB / 31.90 GB

Binaries:

Node: 10.18.0 - C:\Program Files\nodejs\node.EXE
Yarn: 1.22.5 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
npm: 6.13.4 - C:\Program Files\nodejs\npm.CMD

npmPackages:

babel-plugin-styled-components: ^1.10.6 => 1.10.6
styled-components: ^5.2.1 => 5.2.1

Reproduction
We have a component that is being restyled I will post the error log.
Expected Behavior
useDebugValue shouldn't be changing run order between rerenders.
Actual Behavior
react-dom.development.js:88 Warning: React has detected a change in the order of Hooks called by Styled(Interactable). This will lead to bugs and errors if not fixed. For more information, read the Rules of Hooks: https://fb.me/rules-of-hooks

   Previous render            Next render
   ------------------------------------------------------
1. useDebugValue              useDebugValue
2. useContext                 useContext
3. useContext                 useContext
4. useContext                 useContext
5. useContext                 useContext
6. useContext                 useContext
7. useContext                 useContext
8. useDebugValue              useContext
   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

    in Styled(Interactable) (created by Button)
    in Button (created by IconButton)
    in IconButton (created by StyledIconButton)
    in StyledIconButton (created by SvgIcon)
    in SvgIcon (created by NavigationItem)
    in ErrorBoundary (created by NavigationItem)
    in NavigationItem (created by ThemedNavigationItem)
    in ThemedNavigationItem (created by Navigation)
    in a (created by Link)
    in Link (created by Navigation)
    in li (created by MenuItem)
    in MenuItem (created by Navigation)
    in ul (created by Menu)
    in Menu (created by Navigation)
    in div (created by MenuDiv)
    in MenuDiv (created by Navigation)
    in nav (created by StyledNav)
    in StyledNav (created by Navigation)
    in Ge (created by ThemeProvider)
    in ThemeProvider (created by Navigation)

I know the debug value isn't within our codebase as i have done a global search for it and i get 0 results.

Without a reproduction I cannot unfortunately pin this down. The fact that I haven't seen this however, and this hasn't been reported again is a good indication that there may be something funky going on in your codebase. However, it isn't that easy for me to tell what that may be. So, if it's a usage question, I do have the following advice though:
Please refer with usage questions to Stack Overflow, as you're more likely to get quicker and helpful answers there ❤ Repository issues on GitHub are great for that, issues, things that need to be resolved in the library itself, or can't be resolved by anyone but the maintainers. While I (and many others on other repos) are happy to eventually answer usage questions, styled-components is a busy repo and mostly stable and slow moving towards new releases, so you're not likely to get fast responses here