RGB Camera returns No frames received on Jetson Orin

Required Info

Camera Model
D455

Firmware Version
<IP_ADDRESS>

Operating System & Version
Linux (Ubuntu 14/16/17)

Kernel Version (Linux Only)
5.10.65-tegra

Platform
NVIDIA Jetson Orin L4T 34.1.1

SDK Version
2.53.1

Language
python

Segment
others

Issue Description
I installed the Intel RealSense SDK 2.0 using all the methods individually in this on my Jetson Orin, but unfortunately I get the same error, as follows, for all streams except YUYV. I tried playing around with the Resolution and frame rate settings and still got the same error. I also tried hardware reset from the realsense-viewer but of no vain. Only YUYV stream seems to be working, I also have a jetson Nano, and the camera works fine with the Nano, so I guess the camera hardware can be ruled out.
20/04 16:52:05,805 INFO [281472535599360] (sensor.cpp:38) Frame Callback Color #65 overdue. (FPS: 30, max duration: 32.258064 ms)  20/04 16:52:05,837 ERROR [281472535599360] (synthetic-stream.cpp:48) Exception was thrown during callback: _copyI14rs2_extrinsicsEESt10shared_ptrIT_ES3_EUlPS1_E_  20/04 16:52:05,868 ERROR [281472535599360] (synthetic-stream.cpp:48) Exception was thrown during callback: _copyI14rs2_extrinsicsEESt10shared_ptrIT_ES3_EUlPS1_E_  20/04 16:52:05,900 ERROR [281472535599360] (synthetic-stream.cpp:48) Exception was thrown during callback: _copyI14rs2_extrinsicsEESt10shared_ptrIT_ES3_EUlPS1_E_  20/04 16:52:05,932 ERROR [281472535599360] (synthetic-stream.cpp:48) Exception was thrown during callback: _copyI14rs2_extrinsicsEESt10shared_ptrIT_ES3_EUlPS1_E_  20/04 16:52:06,002 ERROR [281472535599360] (synthetic-stream.cpp:48) Exception was thrown during callback: _copyI14rs2_extrinsicsEESt10shared_ptrIT_ES3_EUlPS1_E_  20/04 16:52:06,034 ERROR [281472535599360] (synthetic-stream.cpp:48) Exception was thrown during callback: _copyI14rs2_extrinsicsEESt10shared_ptrIT_ES3_EUlPS1_E_  20/04 16:52:06,066 ERROR [281472535599360] (synthetic-stream.cpp:48) Exception was thrown during callback: _copyI14rs2_extrinsicsEESt10shared_ptrIT_ES3_EUlPS1_E_  20/04 16:52:06,098 ERROR [281472535599360] (synthetic-stream.cpp:48) Exception was thrown during callback: _copyI14rs2_extrinsicsEESt10shared_ptrIT_ES3_EUlPS1_E_  20/04 16:52:06,129 ERROR [281472535599360] (synthetic-stream.cpp:48) Exception was thrown during callback: _copyI14rs2_extrinsicsEESt10shared_ptrIT_ES3_EUlPS1_E_  20/04 16:52:06,199 ERROR [281472535599360] (synthetic-stream.cpp:48) Exception was thrown during callback: _copyI14rs2_extrinsicsEESt10shared_ptrIT_ES3_EUlPS1_E_  20/04 16:52:06,199 INFO [281472535599360] (sensor.cpp:38) Frame Callback Color #78 overdue. (FPS: 30, max duration: 32.258064 ms)  20/04 16:52:06,232 ERROR [281472535599360] (synthetic-stream.cpp:48) Exception was thrown during callback: _copyI14rs2_extrinsicsEESt10shared_ptrIT_ES3_EUlPS1_E_  20/04 16:52:06,264 ERROR [281472535599360] (synthetic-stream.cpp:48) Exception was thrown during callback: _copyI14rs2_extrinsicsEESt10shared_ptrIT_ES3_EUlPS1_E_  20/04 16:52:06,296 ERROR [281472535599360] (synthetic-stream.cpp:48) Exception was thrown during callback: _copyI14rs2_extrinsicsEESt10shared_ptrIT_ES3_EUlPS1_E_  20/04 16:52:06,327 ERROR [281472535599360] (synthetic-stream.cpp:48) Exception was thrown during callback: _copyI14rs2_extrinsicsEESt10shared_ptrIT_ES3_EUlPS1_E_  20/04 16:52:06,359 ERROR [281472535599360] (synthetic-stream.cpp:48) Exception was thrown during callback: _copyI14rs2_extrinsicsEESt10shared_ptrIT_ES3_EUlPS1_E_  20/04 16:52:06,391 ERROR [281472535599360] (synthetic-stream.cpp:48) Exception was thrown during callback: _copyI14rs2_extrinsicsEESt10shared_ptrIT_ES3_EUlPS1_E_  20/04 16:52:06,423 ERROR [281472535599360] (synthetic-stream.cpp:48) Exception was thrown during callback: _copyI14rs2_extrinsicsEESt10shared_ptrIT_ES3_EUlPS1_E_  20/04 16:52:06,455 ERROR [281472535599360] (synthetic-stream.cpp:48) Exception was thrown during callback: _copyI14rs2_extrinsicsEESt10shared_ptrIT_ES3_EUlPS1_E_

Hi @paritoshwale  The methods for a successful installation of the librealsense SDK on Orin are currently to (a) build the SDK from source code but not patch the kernel, or (b) to build from source code with the RSUSB backend installation method so that the kernel is bypassed.  https://github.com/IntelRealSense/librealsense/issues/11628 has information about this.

Hi @MartyG-RealSense, thanks for your quick reply.
I followed the RSUSB backend method and got the above error. Today I tried building the SDK from source without patching the kernel and still could not solve the issue. No RGB frames except YUYV, but a different error this time.
21/04 14:25:00,089 INFO [281472768059648] (rs.cpp:2701) Framebuffer size changed to 1848 x 1016  21/04 14:25:00,089 INFO [281472768059648] (rs.cpp:2701) Window size changed to 1848 x 1016  21/04 14:25:00,089 INFO [281472768059648] (rs.cpp:2701) Scale Factor is now 1  21/04 14:25:00,106 INFO [281472691943680] (backend-v4l2.cpp:656) Enumerating UVC video0 realpath=/sys/devices/platform/3610000.xhci/usb2/2-3/2-3.4/2-3.4:1.0/video4linux/video0  21/04 14:25:00,107 INFO [281472691943680] (backend-v4l2.cpp:656) Enumerating UVC video1 realpath=/sys/devices/platform/3610000.xhci/usb2/2-3/2-3.4/2-3.4:1.0/video4linux/video1  21/04 14:25:00,107 INFO [281472691943680] (backend-v4l2.cpp:656) Enumerating UVC video2 realpath=/sys/devices/platform/3610000.xhci/usb2/2-3/2-3.4/2-3.4:1.0/video4linux/video2  21/04 14:25:00,107 INFO [281472691943680] (backend-v4l2.cpp:656) Enumerating UVC video3 realpath=/sys/devices/platform/3610000.xhci/usb2/2-3/2-3.4/2-3.4:1.0/video4linux/video3  21/04 14:25:00,108 INFO [281472691943680] (backend-v4l2.cpp:656) Enumerating UVC video4 realpath=/sys/devices/platform/3610000.xhci/usb2/2-3/2-3.4/2-3.4:1.3/video4linux/video4  21/04 14:25:00,108 INFO [281472691943680] (backend-v4l2.cpp:656) Enumerating UVC video5 realpath=/sys/devices/platform/3610000.xhci/usb2/2-3/2-3.4/2-3.4:1.3/video4linux/video5  21/04 14:25:00,536 INFO [281472768059648] (backend-v4l2.cpp:656) Enumerating UVC video0 realpath=/sys/devices/platform/3610000.xhci/usb2/2-3/2-3.4/2-3.4:1.0/video4linux/video0  21/04 14:25:00,536 INFO [281472768059648] (backend-v4l2.cpp:656) Enumerating UVC video1 realpath=/sys/devices/platform/3610000.xhci/usb2/2-3/2-3.4/2-3.4:1.0/video4linux/video1  21/04 14:25:00,537 INFO [281472768059648] (backend-v4l2.cpp:656) Enumerating UVC video2 realpath=/sys/devices/platform/3610000.xhci/usb2/2-3/2-3.4/2-3.4:1.0/video4linux/video2  21/04 14:25:00,537 INFO [281472768059648] (backend-v4l2.cpp:656) Enumerating UVC video3 realpath=/sys/devices/platform/3610000.xhci/usb2/2-3/2-3.4/2-3.4:1.0/video4linux/video3  21/04 14:25:00,537 INFO [281472768059648] (backend-v4l2.cpp:656) Enumerating UVC video4 realpath=/sys/devices/platform/3610000.xhci/usb2/2-3/2-3.4/2-3.4:1.3/video4linux/video4  21/04 14:25:00,538 INFO [281472768059648] (backend-v4l2.cpp:656) Enumerating UVC video5 realpath=/sys/devices/platform/3610000.xhci/usb2/2-3/2-3.4/2-3.4:1.3/video4linux/video5  21/04 14:25:00,544 INFO [281472768059648] (context.cpp:382) Found 1 RealSense devices (mask 0xfe)  21/04 14:25:07,370 INFO [281472768059648] (sensor.cpp:1586) Request: RGB8 Color,  Resolved to: YUYV Color,   21/04 14:25:07,377 INFO [281472768059648] (backend-v4l2.cpp:1992) Video node was successfully configured to YUYV format, fd 23  21/04 14:25:07,377 INFO [281472768059648] (backend-v4l2.cpp:1994) Trying to configure fourcc YUYV  21/04 14:25:07,377 INFO [281472768059648] (backend-v4l2.cpp:2195) Metadata node was successfully configured to D4XX format, fd 30  21/04 14:25:07,909 ERROR [281472514619648] (synthetic-stream.cpp:48) Exception was thrown during callback: lS0_E_SaIvELN9__gnu_cxx12_Lock_policyE2EE  21/04 14:25:07,909 INFO [281472514619648] (sensor.cpp:38) Frame Callback Color #0 overdue. (FPS: 30, max duration: 32.258064 ms)  21/04 14:25:07,941 ERROR [281472514619648] (synthetic-stream.cpp:48) Exception was thrown during callback: lS0_E_SaIvELN9__gnu_cxx12_Lock_policyE2EE  21/04 14:25:07,974 ERROR [281472514619648] (synthetic-stream.cpp:48) Exception was thrown during callback: lS0_E_SaIvELN9__gnu_cxx12_Lock_policyE2EE  21/04 14:25:08,006 ERROR [281472514619648] (synthetic-stream.cpp:48) Exception was thrown during callback: lS0_E_SaIvELN9__gnu_cxx12_Lock_policyE2EE  21/04 14:25:08,038 ERROR [281472514619648] (synthetic-stream.cpp:48) Exception was thrown during callback: lS0_E_SaIvELN9__gnu_cxx12_Lock_policyE2EE  21/04 14:25:08,071 ERROR [281472514619648] (synthetic-stream.cpp:48) Exception was thrown during callback: lS0_E_SaIvELN9__gnu_cxx12_Lock_policyE2EE  21/04 14:25:08,103 ERROR [281472514619648] (synthetic-stream.cpp:48) Exception was thrown during callback: lS0_E_SaIvELN9__gnu_cxx12_Lock_policyE2EE  21/04 14:25:08,136 ERROR [281472514619648] (synthetic-stream.cpp:48) Exception was thrown during callback: lS0_E_SaIvELN9__gnu_cxx12_Lock_policyE2EE  21/04 14:25:08,168 ERROR [281472514619648] (synthetic-stream.cpp:48) Exception was thrown during callback: lS0_E_SaIvELN9__gnu_cxx12_Lock_policyE2EE  21/04 14:25:08,200 ERROR [281472514619648] (synthetic-stream.cpp:48) Exception was thrown during callback: lS0_E_SaIvELN9__gnu_cxx12_Lock_policyE2EE  21/04 14:25:08,232 ERROR [281472514619648] (synthetic-stream.cpp:48) Exception was thrown during callback: lS0_E_SaIvELN9__gnu_cxx12_Lock_policyE2EE  21/04 14:25:08,265 ERROR [281472514619648] (synthetic-stream.cpp:48) Exception was thrown during callback: lS0_E_SaIvELN9__gnu_cxx12_Lock_policyE2EE  21/04 14:25:08,297 ERROR [281472514619648] (synthetic-stream.cpp:48) Exception was thrown during callback: lS0_E_SaIvELN9__gnu_cxx12_Lock_policyE2EE  21/04 14:25:08,329 ERROR [281472514619648] (synthetic-stream.cpp:48) Exception was thrown during callback: lS0_E_SaIvELN9__gnu_cxx12_Lock_policyE2EE

A synthetic stream error usually does not have a traceable cause and is equivalent to a "something went wrong" message.
At present, using RSUSB or not performing patching are the only two methods of installation for Orin that are confirmed to be successful and there are not alternative suggestions, unfortunately.  The next librealsense version (likely to be numbered 2.54.0) will support JetPack 5.0.2.
Did you remove the original librealsense installation made with the tx2 instructions before attempting a new installation, please?
https://dev.intelrealsense.com/docs/nvidia-jetson-tx2-installation

Yes, I did remove the original installation using sudo make uninstall. I guess I will have to wait until the next version is released.
Thanks!

You are very welcome!
The work-in-progress SDK version that will become the next SDK release is always available on the SDK's development GitHub branch.
https://github.com/IntelRealSense/librealsense/tree/development

Hi @giladosk  I do not have a time estimate for release at this time, unfortunately.
When developing for a production system, using a production firmware driver is likely to be more important than using a non-master SDK branch.  The most recent recommended production firmware is <IP_ADDRESS>.  Using this will mean using an SDK older than version 2.53.1, such as 2.50.0 or 2.51.1.  This is because 2.53.1 requires firmware <IP_ADDRESS>, which is not yet classed as a production firmware.

@MartyG-RealSense We are already using <IP_ADDRESS>, despite the fact the "recommended firmware version" that appears everywhere is 5.14 :)
I tested using both 2.50 and 2.53, with no success. I know how to install (and sometimes patch if needed) it and have done it many times and on many distros. Here I have no success with all the options, so I hope a newer release would be of help.

@giladosk  I have enquired to my Intel RealSense colleagues about whether they have an approximate release time estimate that they can provide.

The new SDK version 2.54.1 is now available - please see https://github.com/IntelRealSense/librealsense/issues/11884

Thank you @MartyG-RealSense, I shall use it and provide an update!

@MartyG-RealSense
Hi, unfortunately, using the newer versions still haven't changed the lack of RGB input.
I have tested the new 2.54.1 both with the older and newer recommended firmware versions.

@giladosk  You said earlier at https://github.com/IntelRealSense/librealsense/issues/11716#issuecomment-1578773313 that certain models of Jetson do not stream RGB even on RSUSB.  As you mentioned 'certain models', does that mean that there are Jetson models that RGB does work on, please?

@giladosk You said earlier at #11716 (comment) that certain models of Jetson do not stream RGB even on RSUSB. As you mentioned 'certain models', does that mean that there are Jetson models that RGB does work on, please?

@MartyG-RealSense Correct. And for them, it works even with the previous librealsense version. I could have suspected it is the vendor to blame, but on previous Jetpack versions they had no issues.

Are all of the boards using the same Ubuntu version?

Are all of the boards using the same Ubuntu version?

The Ubuntu version is the same for all Jetpack 5.0.2, which is 20.04. For this version, the RBG stream does not work for some of the vendors.
For the earlier, Jetpack 4.6, the Ubuntu version is 18.04, and the RGB stream works well for all vendors.

Yes, JetPack 4.6 is the appropriate JetPack to use with Ubuntu 18.04.  Nvidia created JetPack 5 for use with Ubuntu 20.04.
As librealsense does not have Arm64 packages for Ubuntu 20.04, building librealsense from source code with RSUSB backend = true was also an appropriate action.
What was your full CMake buikd instruction on 20.04?  In addition to -DFORCE_RSUSB_BACKEND=TRUE, did you also set -DBUILD_GRAPHICAL_EXAMPLES=true ?  This instruction does not only build example programs and tools but also includes graphics support in the librealsense build.

I did include this flag, as it allows me to fully use the realsense-viewer. I was following the comments you always refer to that include the step-by-step instructions for building on arm:
cmake ../ -DFORCE_RSUSB_BACKEND=ON -DBUILD_PYTHON_BINDINGS:bool=true -DPYTHON_EXECUTABLE=/usr/bin/python3 -DCMAKE_BUILD_TYPE=release -DBUILD_EXAMPLES=true -DBUILD_GRAPHICAL_EXAMPLES=true -DBUILD_WITH_CUDA:bool=true
And it always worked, until this version.

@giladosk  Which Python version are you using, please?  2.54.1, and the earlier development branch that it was based on, added Python 3.11 support but removed support for Python 3.6.

@MartyG-RealSense We are using the 20.04-native python version, 3.8.
Importing the pyrealsense2 works, if that's where you're aiming at.

Thanks, Python 3.8 should be fine as it was 3.6 that had support removed.
It would be helpful to get an update from @paritoshwale the original creator of this issue.
Hi @paritoshwale  Have you had the opportunity to test your Jetson Orin and JetPack 5.0.2 with the new 2.54.1 SDK?  If you have, did you continue to experience No Frames Received on the RGB stream like @giladosk has?


ostree: 2020.8 -> 2021.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/ostreedev/ostree/releases.
meta.description for ostree is: "Git for operating system binaries"
meta.homepage for ostree is: "https://ostree.readthedocs.io/en/latest/"
meta.changelog for ostree is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

Warning: a test defined in passthru.tests did not pass

/nix/store/9y5sf8yi82z1dn120b1v1ijn29yz9c1v-ostree-2021.1/bin/ostree passed the binary check.

/nix/store/9y5sf8yi82z1dn120b1v1ijn29yz9c1v-ostree-2021.1/bin/rofiles-fuse passed the binary check.

2 of 2 passed binary check by having a zero exit code.

2 of 2 passed binary check by having the new version present in output.

found 2021.1 with grep in /nix/store/9y5sf8yi82z1dn120b1v1ijn29yz9c1v-ostree-2021.1

found 2021.1 in filename of file in /nix/store/9y5sf8yi82z1dn120b1v1ijn29yz9c1v-ostree-2021.1

directory tree listing: https://gist.github.com/727d1abf9710247a64b6987342c4e4f9

du listing: https://gist.github.com/def73f376f58c2d41cd9b105ce93a7ed

Rebuild report (if merged into master) (click to expand)

58 total rebuild path(s)

19 package rebuild(s)

19 x86_64-linux rebuild(s)
19 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
19 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
flatpak
flatpak-builder
gnome-builder
gnome3.gnome-software
haskellPackages.gi-ostree
libsForQt5.discover
libsForQt512.discover
libsForQt514.discover
libsForQt515.discover
malcontent-ui
minishift
ostree
pantheon.appcenter
pantheon.sideload
plasma5Packages.discover
rpm-ostree
vala-language-server
xdg-desktop-portal
xdg-desktop-portal-gtk

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/9y5sf8yi82z1dn120b1v1ijn29yz9c1v-ostree-2021.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A ostree https://github.com/r-ryantm/nixpkgs/archive/152b6aeeebec4f257b1692ffd4857415a87933e4.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/9y5sf8yi82z1dn120b1v1ijn29yz9c1v-ostree-2021.1
ls -la /nix/store/9y5sf8yi82z1dn120b1v1ijn29yz9c1v-ostree-2021.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review took longer than 45m and timed out

Maintainer pings
cc @copumpkin for testing.

Result of nixpkgs-review pr 117503 at 152b6aee run on aarch64-linux 1

2 packages marked as broken and skipped:

libsForQt512.discover
libsForQt514.discover

3 packages failed to build:

gnome-builder
pantheon.appcenter
vala-language-server

12 packages built successfully:

flatpak
flatpak-builder
gnome3.gnome-software
haskellPackages.gi-ostree
libsForQt5.discover (libsForQt515.discover ,plasma5Packages.discover)
malcontent-ui
minishift
ostree
pantheon.sideload
rpm-ostree
xdg-desktop-portal
xdg-desktop-portal-gtk

1 suggestion:

warning: unused-argument
Unused argument: fetchpatch.
Near pkgs/tools/misc/ostree/default.nix:3:3:
  |
3 | , fetchpatch
  |   ^

Note that build failures may predate this PR, and could be nondeterministic or hardware dependent.
Please exercise your independent judgement.

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

2 packages marked as broken and skipped:

libsForQt512.discover
libsForQt514.discover

1 package failed to build:

pantheon.appcenter

14 packages built:

flatpak
flatpak-builder
gnome-builder
gnome3.gnome-software
haskellPackages.gi-ostree
libsForQt5.discover (libsForQt515.discover ,plasma5Packages.discover)
malcontent-ui
minishift
ostree
pantheon.sideload
rpm-ostree
vala-language-server
xdg-desktop-portal
xdg-desktop-portal-gtk


How to prevent an entire hierarchy of modules from being imported?

I would like to ensure that my code does not import any module from the Cabal library anywhere (except for my own MyCabal module). How can I configure this without having to list every single Cabal module explicitly? I tried
- modules:
  - { name: Distribution, within: [MyCabal] }

but this doesn't seem to work. Neither will
- modules:
  - { name: Distribution.*, within: [MyCabal] }

Is there an alternative syntx to accomplish this by any chance?

The plan was for Distribution.** to work using the filepattern library. #402 is the work tracking that.

Closing as a duplicate.


Bcdata

Short section that introduces the bcdata package. Fairly superficial as I did not want to delve deeply into the world of geospatial data.

Huh weird, no the requirements.txt shouldn't have been blank! That should be fixed now.


Editing 'Assignment type' doesn't always save

Editing the 'Assignment type' on an assignment is wonky in that it sometimes saves the settings and sometimes doesn't.
Repro:

Make an assignment, leaving 'Students can work in groups' unchecked.
Edit the assignment by checking 'Students can work in groups' as well as 'Automatically generate group names', then save.
Edit the assignment again, this time also allowing students to form groups, then save.
Returning to the edit assignment page, 'Students can work in groups' will be unchecked.

This is a repro that seems to work all of the time. I have encountered the same problem with other cases, though.

This seems to have been fixed.


How to set the runtime environment

Hello! Is this run under linux system? Can you give the flow of how to use it, please.

Hi, thanks for reaching out. You can download and install GNU Radio by following this link: https://wiki.gnuradio.org/index.php/InstallingGR
You can then follow the tutorials to get familiar with it: https://wiki.gnuradio.org/index.php?title=Tutorials

Firstly, thank you for your reply.
According to Gunadio's instruction manual,I downloaded and installed in the windows,But when I run this .grc file, It's error;
So,I I want to ask you for a few questions.
1.Is the operating system under Windows?If not, what is his operating system and version.
2.Gunradio  and Python What is the corresponding version number?
I would appreciate it very much if I could help me with deal with questions.
Yours
Best


Error reading default credentials file using Newtonsoft.Json v8

The call to Google.Storage.V1.StorageClient.FromApplicationCredentials() works using Newtonsoft.Json 7.x, but fails when upgrading to 8.x.
This behavior happens when debugging this sample: https://github.com/csells/GoogleStorageProvider/tree/e4f2436cbf951c0d522f8c73ac72beae54d76a38
Enter the PowerShell command "dir gcs:" to see the problem.
Following the error's recommendation to "Please rerun 'gcloud auth login' to regenerate credentials file" does not fix the problem.

This is actually not possible to fix.
You get that error message (rerun gcloud auth login) because in the bowels of the Apiary client library, an exception is thrown when trying to parse the credentials JSON file. That exception is "could not find Newtonsoft.Json 7.x.
Why is it looking for Newtonsoft.Json 7.x? Because the Apiary client libraries (Google.Apis.dll) has a dependency on it. Normally users don't run into these problems because an assembly redirect is put in app.config by NuGet. However, PowerShell doesn't honor your project's app.config file because of the way cmdlets are loaded. (There is no notion of an assembly-specific config file, to my knowledge.)
So you could work around this by putting the assembly redirect in your machine.config file. Or just downgrade to Newtonsoft 7.x when using PowerShell until the Apiary client libraries upgrade to 8.0. As for upgrading the Apiary client libraries to use Newtonsoft 8.0, there is nothing stopping us from doing that. I think it is just a matter of thinking harder about it and confirming it won't break anybody.

To reiterate, this should only be blocking scenarios where the consumer of the gcloud-dotnet project is an assembly, and not a stand-alone executable. Since the stand-alone executable path will use an app.config file.

How do I tell that this is a “would need an app.config” file bug (as it was before) vs. a “we’ve got a build process stamping the wrong version on things” bug or a “Newtonsoft.JSON has tighten the JSON that they read and our mostly-by-not-completely-correct JSON credentials file is no longer correct” bug (which is what I thought it was)? Does any entry in the app.config signal trouble? Do we know the algorithm to detect this kind of problem in the future? Given the algorithm, I’m happy to write a tool to avoid this problem in the future.
On Apr 11, 2016, at 8:25 AM, Chris Smith <notifications<EMAIL_ADDRESS>wrote:
This is actually not possible to fix.
You get that error message (rerun gcloud auth login) because in the bowels of the Apiary client library, an exception is thrown when trying to parse the credentials JSON file. That exception is "could not find Newtonsoft.Json 7.x.
Why is it looking for Newtonsoft.Json 7.x? Because the Apiary client libraries (Google.Apis.dll) has a dependency on it. Normally users don't run into these problems because an assembly redirect is put in app.config by NuGet. However, PowerShell doesn't honor your project's app.config file because of the way cmdlets are loaded. (There is no notion of an assembly-specific config file, to my knowledge.)
So you could work around this by putting the assembly redirect in your machine.config file. Or just downgrade to Newtonsoft 7.x when using PowerShell until the Apiary client libraries upgrade to 8.0. As for upgrading the Apiary client libraries to use Newtonsoft 8.0, there is nothing stopping us from doing that. I think it is just a matter of thinking harder about it and confirming it won't break anybody.
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHubhttps://github.com/GoogleCloudPlatform/gcloud-dotnet/issues/102#issuecomment-208400487

One option would be to stop being quite so liberal with the exceptions we catch in https://github.com/google/google-api-dotnet-client/blob/master/Src/Support/GoogleApis.Auth.DotNet4/OAuth2/DefaultCredentialProvider.cs
If we had a specific set of error scenarios in mind, tested what exception is thrown in each of them, and then caught only those exceptions (and gave great error messages) this would be much cleaner.
Perhaps we should move this bug over to https://github.com/google/google-api-dotnet-client now?

I’m wary of us catching a “bug” that’s by design as far as Microsoft is concerned. I was thinking more along the lines of a post-build tool that would perhaps check for a non-empty app.config? Or check the entries in the app.config against the dependent versions? I’m not sure what the right think to check for, actually.
On Apr 11, 2016, at 9:17 AM, Jon Skeet <notifications<EMAIL_ADDRESS>wrote:
One option would be to stop being quite so liberal with the exceptions we catch in https://github.com/google/google-api-dotnet-client/blob/master/Src/Support/GoogleApis.Auth.DotNet4/OAuth2/DefaultCredentialProvider.cs
If we had a specific set of error scenarios in mind, tested what exception is thrown in each of them, and then caught only those exceptions (and gave great error messages) this would be much cleaner.
Perhaps we should move this bug over to https://github.com/google/google-api-dotnet-client now?
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHubhttps://github.com/GoogleCloudPlatform/gcloud-dotnet/issues/102#issuecomment-208431910

We only need a non-empty app.config in cases where assembly binding redirects are actually required. I think the fact that the error message suggested the wrong course of action is the first thing to fix - if it were obvious that this is a type load failure, what bug would you have filed? (Not saying it wouldn't have been worth filing one, but I think it would have been different.)
I'd also be interested in thinking about how this would be caught by testing of the customer's code - if it's always caught in any tests that exercise the API at all, I'm not sure that a post-build tool gives much more benefit...

@csells: Any thoughts on whether we can close this as basically infeasible? We're basically in the same situation as all other projects that take other dependencies.

Closing as "won't fix" until anyone comes up with a better idea.


Cannot open WebChat or Channel View in Azure

Bot Info

SDK Platform: .NET
SDK Version: v3.0 and v4(preview)
Active Channels: None
Deployment Environment: Azure Bot Service

Issue Description
When I create a new Bot Channel Registration, I cannot open the following views:

Test in Web Chat
Analytics
Channels
Speech

Reproduction Steps

Follow this tutorial (https://docs.microsoft.com/en-us/azure/bot-service/bot-service-quickstart?view=azure-bot-service-4.0)
Go to the bot service
Click webchat

I have also tried to create a v3.0 bot, with the same results.
I started by first creating a (v4) bot locally and then uploading it to a web app and then register the bot, which had the same result.
Expected Behavior
It would show me an Web Chat:

Actual Results

It shows me one of these images. When looking in the dev tools, I can see that it tries to connect to bot framework, but fails:

When going to that url in my browser, I do get a valid result.

@mgbennet Are you able to look into this one too?

Update:
The problem is the Firefox Browser. I can access all features on Chrome. Even if I use Firefox incognito mode, I am not able to use Web Chat.

Could you still let us know what language you are using in the Azure portal?  It will help us see if this is related to a similar issue we are tracking at this time.

Of course! I am using the English.

Shall I also send the Har file to you?


help: Document dark-theme mobile feature.

Documents "Night mode" option.
Adds Related articles section.

Screenshots and screen captures:

https://zulip.com/help/dark-theme

Self-review checklist

[x] Self-reviewed the changes for clarity and maintainability

Communicate decisions, questions, and potential concerns.

[x] Automated tests.

Individual commits are ready for review (see commit discipline).

[x] Each commit is a coherent idea.
[x] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[x] Visual appearance of the changes.
[x] Links.

@alya This PR is ready for you. I changed the related articles section and updated the screenshot in the description.

Looks good to me, thanks!

Merged, thanks @drrosa!


Add PSP support, but better integrated into the codebase

This adds PSP support in a way which keeps the PC and Vita builds in tact.

Short todo list:

[ ] Use separate sprite for pause menu background
[ ] Make pause menu show in the middle of the screen
[ ] Use separate sprite for points in multiplayer
[ ] Make points show in correct position
[ ] Make upcoming garbage blocks show in correct position
[ ] Make sure the code starts on the PSP
[ ] Fix the options menu being completely black
[ ] Fix input on PSP
[ ] Move xcf files out of assets directory
[ ] Remove sprites.png

There might be more. I don't remember all of them off the top of my head.

The implementation for the garbage queue for the psp needs work. SDL is rescaling it to half size in real time, which might be on the slow side.


sklearn-intelex integration?

Hi, I've seen this work by Intel: https://github.com/intel/scikit-learn-intelex and curious if anyone has looked into how it may compare / if it can be used as a speed up in nndescent / associated tools (UMAP/etc)? There is an example notebook here showing the speedup on a toy example: https://www.kaggle.com/kppetrov/fast-knn-using-scikit-learn-intelex-for-mnist - i believe there are also additional hooks for GPU methods: https://intel.github.io/scikit-learn-intelex/gpu.html

I haven't looked in depth, but it seems like it is a nice wrapper that provides sklearn-alike classes for many common sklearn tasks (so you catch essentially just use them in place of the sklearn versions, or even just override the sklearn versions). The wrapper is actually calling their DAAL library, which seems to be a Java and C++ library for basic/core ML tasks. I don't think this library can really make use of that, so that just leaves comparisons. If someone wants to run a benchmark I would be interested to see results, but I don't have enough spare time to do it myself at this point. Thanks for pointing me to the library though, it definitely looks useful.


AND-7105: The customView in Invite Collaborators activity should get updated

Fixed the bug, to update the custom view on invite collaborators activity if
collaborators are added or removed.
Changed the order of attaching listener to the custom view based on views lifecycle.

Verified that @nyjalusc has signed the CLA. Thanks for the pull request!

+1


What's left for a beta/stable version?

Hey,
I would like to offer some help with hyperion.ng to bring it at least to a beta version and release some binary packages so the users don't have to compile it.
I'm not a full-time c++ developer, but I'm sure I can help fix some bugs and/or test things.
I've seen some forum posts with checklists and ToDos, but all seems very old (2016,2017) and I don't know what has been implemented or not.
Do we have an accurate checklist? Should I open new issues for packaging release and work on them?
What about bi-monthly (I know everyone is busy) release tag so we can have a proper changelog?
Thx

Hi,
help is always very welcome.
From my perspective ng would be ready Dir Beta.
We have one big thing to do:
We have to define and implement automatic Build and deploy process. I think you already saw the process with Travis. We need to complete this.
Would be great if you can contribute there.
Thanks!

Cool. I'll be happy to take a look on that.

Is there anything still blocking? I saw the working Azure Pipelines which look very promising!


[feat] Add kotlin -> rust bindings for creating an account

Basically we will need to create a java class to pass the private key, which will call the rust code to create an account with that private key
References

I would like to try this one.

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
I have a strong background in both Java and Rust, which positions me well for tasks involving cross-language integration.
How I plan on tackling this issue
I will implement the issue with the following steps!
I will create a Rust function to accept a private key and perform account creation.
Use #[no_mangle] and extern "C" to make the function callable from Java then compile the Rust code into a shared library (.so, .dll, or .dylib).
Define a native method in Java to interface with the Rust function.
Load the shared library and call the native method with the private key.
Ensure the shared library is accessible in the Java library path and execute the Java program

Hello @trbutler4! ,If it is still available I'd like to take it and work on it. Also, I am part of Dojo Coding if this helps me.
Thank you!

I would like to try this one.

assigned to @Gerson2102. @Gerson2102 the outline @ScottyDavies put down is spot on. LMK if you have any other questions.


colortool.exe does not exit after executing

This bug-tracker is monitored by Windows Console development team and other technical types.  We like detail!
If you have a feature request, please post to the UserVoice.

Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues. Instead, send dumps/traces to<EMAIL_ADDRESS>referencing this GitHub issue.

Please use this form and describe your issue, concisely but precisely, with as much detail as possible

Your Windows build number:  (Type ver at a Windows Command Prompt)

Microsoft Windows [Version 10.0.17134.48]

What you're doing and what's happening: (Copy & paste specific commands and their output, or include screen shots)

I'm trying to use the color tool to change the color scheme. Whenever I execute it within cmd.exe, it does not exit. Also the effects (even with --both) don't seem to persist when I close the hung window and open a new one.

What's wrong / what should be happening instead:

Color tool does not exit and freezes cmd

To repro:
cd Downloads
colortool.exe --both OneHalfDark

Please see attached screenshot:

Can you right click on the title bar of the "hung" window and click on the "Properties" option? What does the "Colors" Tab look like?
I'd guess that conhost isn't actually hung, it's just rendering white-on-white text for some reason. It might be possible that we're not restoring the fg/bg colors at the end of printing the table.
Does adding the --quiet argument fix it?

It does look like it's correctly setting everything in the properties window:

It also does correctly exit and change the current prompt. However the changes do not persist when I open a new window (--both --quiet)

How are you launching cmd?

Via the run box (eg. win+r, "cmd")
Via the start menu
Via the "Start Menu Shortcut" (the one that's brought up when you right click on the start button, also "Win+X, C"
Another shortcut
some other way?

This actually makes a great deal of difference to how the settings are stored (unfortunately). Most likely, you'll have to actually hit OK in the prop sheet for the changes to persist.
I'd try changing your Text Foreground to something other than white to check if that's it.

When launched via ctrl+r cmd: the color scheme is applied, but the colors are not right. For example, here is what OneHalfDark looks like:

However you can see that --quiet is not required in this case. I get these results both with and without --quiet.
Same result with launching via start menu.
The initial problem manifested itself via taskbar shortcut right click:

And here I am not seeing any theming applied at all

When launched via ctrl+r + cmd, I get the view in the previous screenshot. When launched via right click on taskbar, I see:


🐛 persistent error notifications

There is an issue where an improperly set up camply config in a constantly restarting docker container sends notifications all day. In the case of pushover, a process sent ~4,500 notifications today (and I believe they're error messages). This PR only emits the "last gasp" error notification if the search has run at least once.
It also replaces the built-in Pushover token - which resolves an issue for the month of May where the token limit is reached.

Relates to #348

:tada: This PR is included in version 0.32.7 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


backend agnostic hooks

I'd like to have a generic way to hook after some events, e.g. send an email after the user receive a message in the inbox. I think this can be implemented using django signals, not sure where to add them if on each backend or in the api.

I think i'm gonna move tests on another file so they are not duplicated please don't apply yet.


Transformers.js

The models are not tagged with the transformers.js category. Should they?

No, not necessarily


Date is not a constructor

I'm using jsdom with Jest + Enzyme + React.
When I mount a component with Enzyme mount after I properly defined global.window and global.document, I get an error:
TypeError: Date is not a constructor

      at DocumentImpl (node_modules/jsdom/lib/jsdom/living/nodes/Document-impl.js:269:83)
      at Object.setup (node_modules/jsdom/lib/jsdom/living/generated/Document.js:702:17)
      at Object.create (node_modules/jsdom/lib/jsdom/living/generated/Document.js:672:10)
      at new Window (node_modules/jsdom/lib/jsdom/browser/Window.js:67:29)
      at Object.<anonymous>.exports.jsdom (node_modules/jsdom/lib/jsdom.js:109:18)

I narrowed down the problem to this line of code:
https://github.com/tmpvar/jsdom/blob/master/lib/jsdom/living/nodes/Document-impl.js#L269
Seems like Date is undefiend... How is it possible?

Can you share a minimal example that triggers this problem, without using external libraries like Jest or Enzyme or React?

I don't know how to reproduce this problem sorry, I hoped that someone encountered the same problem previously...

So, I was using Sinon and I forgot to mention it. By the way, removing Sinon everything works perfectly... So maybe it's something related to Jest + Sinon since they are the only constants in all the discussions I found on the web.

Unrelated to jsdom entirely, but leaving breadcrumbs people running into this issue.
This has been resolved with a v1.5.2 of sinonjs/lolex.
If you're using one of the the Sinon 2.0.0-pre releases, you just need to re-install the lolex dependecy.


tensorflow or theano?

How to make choice to get best results? Why?

Try both?
I have nothing better here. I don't really care what the underlying tensor library is.
My specific experience for this specific network on my servers for a specific set of library revisions:
Theano takes a longer time to "compile" - to start the script,  which is annoying.
But TensorFlow is slower to train.

thx


OSC controls for position and rotation added for all agents

The output addresses must have this format:

/agent/{id}/pos [f32, f32, f32] (x, y, z)
/agent/{id}/rot [f32, f32, f32] (roll, pitch, yaw)


Multithreading in Node.js： Using Atomics for Safe Shared Memory Operations

The original blog info

subject
content

title
Multithreading in Node.js： Using Atomics for Safe Shared Memory Operations

url
blog url

author
Pavel Romanov

Node.js developers got too comfortable with a single thread where JavaScript is executed. Even with the introduction of multiple threads via worker_threads, you can feel pretty safe.
However, things change when you add shared resources to multiple threads. In fact, it is one of the most challenging topics in all software engineering. I'm talking about multithreading programming.
Thankfully, JavaScript provides a built-in abstraction to mitigate the problem of shared resources across multiple threads. This mechanism is called Atomics.
In this article, you'll learn what shared resources look like in Node.js and how Atomics API helps us to prevent wild race conditions.
Shared memory between multiple threads
Let's start with understanding what transferable objects are.
Transferable objects are the objects that can be transferred from one execution context to another without holding to resources from the original context.
An execution context is a place where JavaScript code can be executed. To make it easier to understand, let's assume that an execution context is equal to a worker thread because each thread is indeed a separate execution context.

For example, ArrayBuffer is a transferable object. It consists of 2 parts: raw allocated memory and JavaScript handle to this memory. You can read the article about Buffers in JavaScript to learn more about this topic.
Whenever we transfer ArrayBuffer from the main thread to a worker thread, both components, the raw memory and JavaScript objects are recreated in the worker thread. There is no way you can access the same object reference or underlying memory of ArrayBuffer inside of the worker thread.
The only way to share resources between different threads is to use SharedArrayBuffer.
As the name suggests, it is designed to be shared. We consider this buffer to be a non-transferable object. If you try to pass SharedArrayBuffer from the main thread to a worker thread, only the JavaScript object gets recreated, but the memory region that it refers to is the same

While SharedArrayBuffer is a unique and powerful API it comes with a cost.
As Uncle Ben told us:

When we share resources between multiple threads, we expose ourselves to a whole new world of nasty race conditions.
Race conditions for shared resources
It would be easier to understand what I'm talking about with a particular example.
import { Worker, isMainThread } from 'node:worker_threads';

if (isMainThread) {
  new Worker(import.meta.filename);
  new Worker(import.meta.filename);
} else {
  // worker code
}

We're using the same file to run the main thread and worker threads. The block under isMainThread condition is executed only for the main thread. You might also notice import.meta.filename, it is ES6 alternative to __filename variable available since Node 20.11.0. Next, we introduce a shared resource and an operation over the shared resource.
import { Worker, isMainThread, workerData, threadId } from 'node:worker_threads';

if (isMainThread) {
  const buffer = new SharedArrayBuffer(1);
  new Worker(import.meta.filename, { workerData: buffer });
  new Worker(import.meta.filename, { workerData: buffer });
} else {
  const typedArray = new Int8Array(workerData);
  typedArray[0] = threadId;
  console.dir({ threadId, value: typedArray[0] });
}

We pass SharedArrayBuffer to each of the workers as workerData. Both workers change the first element of the buffer to its ID. Then, we log the first buffer element.
One of the workers will have ID equals to 1 and the other one to 2. Without reading any further, what are you expecting to see in the output when this code runs?
Here is the result.
# 1 type of results
{ threadId: 1, value: 2 }
{ threadId: 2: value: 2 }

# 2 type of results
{ threadId: 1, value: 1 }
{ threadId: 2: value: 1 }

# 3 type of results
{ threadId: 1, value: 1 }
{ threadId: 2: value: 2 }

Did you notice it? Why on earth do we have cases where the value is the same for both threads? If you think about it from the standpoint of a single-threaded program, we should see different values printed every time.
Even if we run this code asynchronously in a single thread, the only thing that could be possibly different is the order in which a result is printed, but not such a drastic difference in the final value.
What happens here is one of the threads assigns value right between these two lines:
  typedArray[0] = threadId;

  // one of the threads sneaks right in here and assign value

  console.dir({ threadId, value: typedArray[0] });

It goes like this:

The First thread assigns a value to the shared buffer

The second thread assigns a value to the shared buffer

The first thread prints the result to the console

The second thread prints the result to the console.

As you can see, it is easy to run into a race condition with as little as 10 lines of code when we have shared resources and multiple threads. That's why we need a mechanism that can make sure that one worker is not interrupting the workflow of another worker. The Atomics API was created exactly for this purpose.
Atomics
I want to emphasize that using Atomics is the only possible way to be 100% sure that you're not running into race conditions when dealing with multiple threads and shared resources between them.
The main purpose of Atomics is to make sure that a single operation is performed as a single, uninterruptible unit. In other words, it ensures that no other workers can get in the middle of currently executable operation and do their stuff, like we've seen before.
Let's rewrite the example with race conditions using Atomics.
import { Worker, isMainThread, workerData, threadId } from 'node:worker_threads';

if (isMainThread) {
  const buffer = new SharedArrayBuffer(1);
  new Worker(import.meta.filename, { workerData: buffer });
  new Worker(import.meta.filename, { workerData: buffer });
} else {
  const typedArray = new Int8Array(workerData);
  const value = Atomics.store(typedArray, 0, threadId);
  console.dir({ threadId, value });
}

We changed two things: how we save the value and how we read the saved value. Using Atomics, we can do both operations at the same time using the store function.
When you run this code, you won't see a case where both threads have the same value. They are always different.
[1, 1]
[2, 2]

[2, 2]
[1, 1]

We could use 2 operations instead of 1: store and load.
const typedArray = new Int8Array(workerData);
Atomics.store(typedArray, 0, threadId);
const value = Atomics.load(typedArray, 0);
console.dir({ threadId, value });

However, this approach is still prone to race conditions. The whole point of using Atomics is to make our operations atomic.
In this case, we want 2 operations to be executed as a single atomic operation: to save a value and to read this value. When we use store and load functions, we're actually doing 2 separate atomics operations, not 1.
That's why it is still possible to run into a race condition where code from one worker gets in between store and load calls from the other threads.
There are more than just 2 functions to Atomics, in the following article, we'll cover how to use more of its functions to build our own semaphore and mutex to make the work with shared resources even more convenient.
Conclusion
Node.js is all fun and good when there is only a single thread. If you introduce multiple threads and shared resources on top of it, you get an environment where race conditions are inevitable.
There is only one mechanism in JavaScript that allows you to mitigate these problems and avoid race conditions, it is called Atomics.
The idea of Atomics is to have operations that execute as a single unit that cannot be interrupted from the outside.
Thanks to such a design, we can be sure that whenever we use Atomics functions, there is no way for other threads to get somewhere inside of such operations.
Node.jsJavaScriptWeb Development
Share this


Support glEGLImageTargetTexture2DOES for Android GLES

After RenderDoc began to strictly check extensions, android developers were faced with the fact that due to the unsupported glEGLImageTargetTexture2DOES extension, they lost the ability to use the RenderDoc. Most modern android games use this extension to display videos or ads.
Here is support of this extension for Android platform.
Functionality can be tested in this sample: http://l1f.ru/contributing/renderdoc/external_texture/external_texture_debug.apk
Also in the serialiser.cpp there is a small fix of chunks processing when loading from xml+zip.

@Squareys do not leave reviews on pull requests from repositories that you are not authorised to. I'm amazed that github even allows this, apparently this is enabled by default and I have now changed that.
It is rude and arrogant to write a review on a repository you have absolutely no relation to nor had any interaction with, leave that to the repository maintainers or anyone they ask to review the code otherwise you will only cause confusion - people submitting PRs do not know if you are one of the maintainers or a complete stranger.

@baldurk Sorry for that, but @Squareys was very helpful in finding corner cases with this implementations, and these suggestions were quite useful. I've already fix them.
@baldurk Sure, I also wait for your review, it seems there is something to improve here.

btw as a minor point of clarification, glEGLImageTargetTexture2DOES is not an extension it's an extension function, the extension itself is OES_EGL_image or OES_EGL_image_external. This is important because not all extensions have only one function, and within your changes you have not added either extension to the list of allowed extensions.
Implementing this function alone will do nothing for a correctly written program since it will still see the extension reported as unavailable. If you are seeing a difference in behaviour with this PR that means the program you're testing with is broken and not functioning correctly.

@baldurk I got your point about the texture type. I'll try to make these updates.
About implementing ony one function from extenstion: As I understand it will works correctly if application does not check ext availability with RenderDoc. It's on developer side. Will you approve PR if it implement only glEGLImageTargetTexture2DOES in this case (if other stuff is OK)?

RenderDoc does not intend to handle broken applications and we don't write code assuming applications will misbehave and then work by coincidence. Any application that tries to use functionality without checking if the extension is supported is not correct.
You must implement the entire extension that you are intending to support and report it, to ensure that valid applications will work correctly. As long as everything in the extension is working that shouldn't be an issue, and I only mentioned it to make sure that you remembered to allow the extension itself as there are no other functions to implement. If you have not looked at the entire extension to make sure you are implementing it correctly you should do that, as it will be reported as supported and the entirety of it is expected to work.

From email discussion this extension is extremely badly designed to an extent that I had not fully appreciated, in particular that external textures are considered an entirely separate fundamental type of texture of the degree that they are accessed via a different type in shaders. As opposed to every other graphics API and several other supported GL extensions where they are normal textures, but created/initialised in a different way to perform the import operation.
This forces an implementation as this PR begins to do that must add support for this fake texture type throughout the GL backend and possibly further into the API abstraction (either with unknown real type or N different new fake types of texture to account for the actual types), as well as using external platform-specific APIs (which are likely unreliable on Android) for creating the textures on replay. The only other alternative that would be to somehow transform the captured commands and patch the use of external textures in shaders into normal textures, which can likely never be done robustly.
The conclusion I've come to is that this means a significant amount of implementation cost and maintenance burden which I do not feel is justified by the value of supporting this extension. While this is not a final written-in-stone decision that can never be reconsidered, I do not see a path forward where there would be an implementation of this extension that I would consider acceptable given the current situation. Since I also do not see that situation significantly changing, for now I consider this feature not something I ever plan to implement or support. Of course since RenderDoc is open source anyone is welcome to make whatever changes they wish locally, but this is not something I will accept upstream.
This is not a unique circumstance, there are a number of GL extensions which are not supported due to the cost of implementation and maintenance not being outweighed by the value of supporting them, and indeed there are a handful of things that are legal in core GL which are simply not supported and never will be due to them being extremely bad design decisions in GL and being far too costly or problematic to be worth supporting.


Raw Text of Node Labels and Corresponding Mappings

Excellent work! It is greatly insightful and beneficial to the community.
To further my understanding, I would be grateful if you could share the raw text of the node labels and their corresponding mappings for the Goodreads-NC and Ele-Fashion datasets?
Thank you very much for considering my request.

Thanks for the comments. You can find raw data here: https://huggingface.co/datasets/mm-graph-org/mm-graph/tree/main/raw-data
You can find mapping here in each corresponding data folder called 'node_mapping.pt', see an example here: https://huggingface.co/datasets/mm-graph-org/mm-graph/tree/main/ele-fashion


Markdown code style and Jekyll files

The following line:

A file MUST start with a first level header on the first line.

conflicts with markdown files used with Jekyll (which is what Github Pages uses to host markdown content).

Closing due to lack of activity.


League object fails to instantiate when not all teams of league have managers

Sport
Basketball
Summary
We had a member of our league drop all his players during playoffs so I removed his access to the league by removing his email from the league members page. When I went to run our power rankings program this morning, it suddenly stopped working. Adding in a dummy email for the team got everything to run smoothly again. If this is intended, then please close this, but I'm not sure why every team needs to have a team owner for the API to work. See attached image below for the error:
Logs/Data

That is a bug, thanks for reporting. The get and default to single object in array was suppose to prevent that but I am guessing the owners field is present just an empty array. I will look into fixing this.


Binance - Error Trading on Binance Perpetual Due to New Binance Credits Requirement

Describe the bug
Hi all,
starting June 26th, Binance Futures traders in the European Economic Area (EEA) must switch to using Binance Credits (BNFCR) for trading. Direct assets for USD-M or COIN-M markets are no longer usable. In the Binance Futures Credits Trading Mode, all USDT or USDC contracts' PNL, margin, and fees will be displayed as Credits labeled BNFCR.
https://www.binance.com/en-BH/support/faq/how-to-use-binance-futures-credits-trading-mode-0e857c392a2d47cebde0af762d9255ae
The error message I encounter in my Hummingbot scripts when trading on binance_perpetual, even though I have enough BNFCR.
Affected countries:
Austria, Bulgaria, Cyprus, Czech Republic, Denmark, Estonia, Finland, Greece, Hungary, Iceland, Ireland, Latvia, Liechtenstein, Lithuania, Luxembourg, Malta, Norway, Poland, Portugal, Romania, Slovakia, and Slovenia.
Thanks for your help!
Steps to reproduce
When running any HB script, an error occurs, see log
Release version
Dashboard (hummingbot/deploy), HB source 1.28.0
Type of installation
Source
Attach required files
log.txt

Hello. I just installed hummingbot and i have the same problem Do you have any news about this? I want to modify code to use BNFCR instead USDT for balance, do you have any hints for this?


Uninformative unauthorized error in API client

In some cases when using Casdoor Api client, you can find uninformative errors, like these:

The error says, that issue is json parsing, but if you log http message request/response, you'll see that the main reason why code failed, is "Unauthorized operation":

This happens, if you forget about setting up token in client or you have invalid configuration file (for example, organization-owner does not exists with this name, invalid url, etc), and error does nothing to address that.

@MadL1me hi, can you make a PR to fix it?

@MadL1me hi, can you make a PR to fix it?

Yep


Full monorepo

With /api and /www directories with own package.json files. Is it worth?

Done. Almost, web deploy does not work but it's up to Now 2 to be fixed.


[EASY] [PDF] Define D as a distinct language for the listings package

The listings LaTeX package allows code formatting and highlighting in various languages. Previously we hacked the D language keywords on top of listings' C++ definition. This PR defines D as a distinct language.

Is the circleci failure expected?

Is the circleci failure expected?

Yes, no one has merged the script yet -> https://github.com/dlang/dlang.org/pull/1948

FWIW I always use this lstlangd.tex file, it's a bit more complete than the one used here.

Btw it seems like you have included https://github.com/dlang/dlang.org/pull/1951 in this PR too. And we usually use git rebase instead of git merge to avoid polluting the git history.

@wilzbach good pointer. So should I just have issued git rebase fix-listings?

@wilzbach good pointer. So should I just have issued git rebase fix-listings?

I just tried to improve our contribution guides, hence I am linking to https://wiki.dlang.org/Starting_as_a_Contributor#Working_on_an_pull_request
tl;dr: I prefer keeping a separate upstream remote node:
git fetch upstream
git rebase upstream/master
``

FWIW I always use this lstlangd.tex file, it's a bit more complete than the one used here.

Feel free to integrate it later. Thanks!

@CyberShadow DAutoTest is failing with:
Package keyval Error: breakatwhitespace undefined.

I've googled around a bit and found this discussion, which suggests running:
sudo apt-get remove fp-utils-3.0.0

Indeed it seems from the logs that the listings-related files are loaded from /usr/share/texmf/tex/latex/fpc-3.0.0/, suggesting fp as the culprit.

which suggests running:
sudo apt-get remove fp-utils-3.0.0

Um, done.

@CyberShadow thanks, that worked!


Compile Errors on collection _RO fields when using -Ximmutable and -Xfluent-builder together

When I try to compile code generated using both -Ximmutable and -Xfluent-builder I get compile errors from the Builder inner static class trying to access private _RO collection fields in the parent class:
private transient List<AppType> app_RO = null;

Then in the Builder.init method there is code like:
product.app_RO = ((app == null)?null:Collections.unmodifiableList(product.app));

Which causes:
[error] ACES.java:240: error: app_RO has private access in ACES
[error]     product.app_RO = ((app == null)?null:Collections.unmodifiableList(product.app));
[error]            ^

I changed the _RO fields to be protected instead of private to avoid the error but I'm not sure if that's the best solution or not:  https://github.com/tpunder/jaxb2-rich-contract-plugin/commit/5020fe446eb279ec1fa9be3c0ad3f0dd45714521

Hi tpunder,
Actually, I think the best solution would be to leave the "_RO" fields completely uninitialized by the builder, since they are lazily initialized anyway. I'm currently implementing this fix in version 1.5.2

Thanks, your pull request has been integrated...


Migrate from stretch to taffy

https://github.com/DioxusLabs/taffy is the revival of the flexbox stretch crate we use currently. Should be fairly straightforward to cutover https://github.com/a-b-street/abstreet/tree/master/widgetry/src/widgets to it. An advantage down the line could be using taffy's planned table support

Let us know if there are features you need or bugs that you encounter :)

If no one's picked this up, could I be assigned? 👀
I have work done locally, just need to figure out how to test if/that widgetry acts as expected.

@inFocus7, that would be amazing, thank you for picking this up!
The easiest way to test is the widgetry_demo crate. You should be able to just cd widgetry_demo; cargo run and compare to http://play.abstreet.org/0.3.24/widgetry_demo.html. The "Show timeseries" at the top creates a scrollable popup that should check a few related things. You can also run the main A/B Street apps by following https://a-b-street.github.io/docs//tech/dev/index.html#getting-started, but I don't think this is necessary before PR review. I'll think about a list of cases that really stretch stretch today, so we can check things like the table layout:

Hey @dabreegster!
I just put a PR up for review here. I manually tested through the widgetry_demo to make sure it acts like the one you linked. Also ran random A/B Street apps to make sure nothing is broken.
It would be a good idea to test out that table layout to feel safer with this migration. Is that a custom layout you made? Or is it part of one of the existing apps in A/B Street?

Not sure if this is a new issue (maybe with my changes), but I tried running a tests locally in url.rs and saw this error:
error[E0432]: unresolved import `crate::backend::Drawable`
  --> widgetry/src/lib.rs:36:9
   |
36 | pub use crate::backend::Drawable;
   |         ^^^^^^^^^^^^^^^^^^^^^^^^ no `Drawable` in `backend`

Thank you for the PR! Migration is done, so I'll close this issue. I'll keep an eye on taffy and see if there's any opportunity to reduce some of the code in widgetry in the future.

Not sure if this is a new issue (maybe with my changes), but I tried running a tests locally in url.rs and saw this error:

It's not related to your changes. There's some cargo features that have to be enabled for this crate to compile, and it looks like the default one somehow got ignored by cargo test. If I run cargo test at the workspace level, things are fine. If I run inside the widgetry crate, I get the same problem. I'll have a look, thanks for the heads up!


make new indexes instead of replacing old ones

Before creating a pull request make sure that:

[ ] commit messages are meaningful and follow good commit message guidelines
[ ] README and other documentation has been updated / added (if needed)
[ ] tests have been updated / new tests has been added (if needed)

Please remove this line and everything above and fill the following sections:
JIRA link (if applicable)
Change description
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[ ] No

Is it ok for there to have multiple indexes on the same column? How does the DB know which one to pick?

yeah, you can put more than 1. DB seems to work it out what it needs


[FEATURE] Custom tool for Conversational Retrieval QA Chain?

I have just ask langchainjs for making external request in Conversational Retrieval QA Chain like custom tool.
They said that: They already support RemoteLangChainRetriever
Could flowiseai support custom tool for Conversational Retrieval QA Chain
Do Conversational Retrieval QA Chain support custom tool? #2747

Something like this? https://www.youtube.com/watch?v=m0nr1_pnAxc&t=1s

Something like this? https://www.youtube.com/watch?v=m0nr1_pnAxc&t=1s

Yep, but how to this chatflow both answer from the documents and allow custom tool like (calculator, call api, serp api, add user to hubspot ...)

I (better) understand your question. Theoretically you should be able to create an agent with acces to all these tools, in one hit). I have not tried it yet in Flowwise. But when you read last weeks developments on RAG, you can imagine you create 4 or 5 agents (each for a specific domain), and then combine them towards a LLM. What is your use case?

Hi @kientv,
I believe you can use Conversational Retrieval Agent to achieve that.

Hi @kientv,
I believe you can use Conversational Retrieval Agent to achieve that.

But Conversational Retrieval Agent don't have VectorStoreRetriever

Hi @kientv ,
I have the same question as you. Did you an answer yet?

Hi @kientv , I have the same question as you. Did you already find a solution?

My solution is using Retrieval tool. But it's not smooth:


Showing :i and other output inline (by choice?)

I think an important use case for IHaskell is to create demos/demonstrations, and for that, it is sometimes useful to include the output of :i, :k etc inline. Currently that's only shown in a popup, which is not part of the generated report. (An example is trying to create a demo of Frames, where showing the autogenerated types is really key).
I made a quick change to the rendering of :i, and actually quite like it inline.

I was first thinking we could have a separate command :infoinline or something, however we could also have some kind of a switch :set IHaskell-inline, which would affect all commands. I'm happy to hack on something like this, but would like some direction about how you'd like it implemented, and if you think it's desirable.

Want to back this issue? Place a bounty on it! We accept bounties via Bountysource.

Try out
:option no-pager

followed by
:i Num

Is this what you were looking for?
...for some reason that option is not in :help. Oops. That's an error.

Indeed, exactly what I was looking for!
Maybe include this in the demo notebook as well, right now the text "The
same goes for the :info command. However, unlike GHCi, which simply prints
info, the IHaskell notebook brings up a separate pane.", and the pasted
image, makes it seem like this is the only way. (See separate pull request)
On Thu, Feb 19, 2015 at 12:48 PM, Andrew Gibiansky<EMAIL_ADDRESS>
wrote:

Try out
:option no-pager
followed by
:i Num
Is this what you were looking for?
...for some reason that option is not in :help. Oops. That's an error.
—
Reply to this email directly or view it on GitHub
https://github.com/gibiansky/IHaskell/issues/363#issuecomment-75100211.

--
http://reganmian.net/blog -- Random Stuff that Matters

I will regenerate the HTML and add info to the help text as well, at some point.


Fix documentation

The documentation isn't correctly generated. For instance, this page is missing.
The version and copyright information is also not updated.

Fixed by #141


Not an issue, but help on how to exactly use this

Hi, I've been trying to understand how to use texconv to convert from tex to dds and vice-versa (don't even know if this is possible at all). Sorry if this sounds like a dumb question, but I'm a beginner and need help with this, if possible!

Hello, afaik Tex is a proprietary Nintendo format and it's not supported by Texconv.
Maybe check out [BrawlCrate](https://github.com/soopercool101/BrawlCrate.

Thanks for your reply!
Oh, and I forgot to mention it was actually from Capcom's MT Framework. Sorry!
But yeah, it's from a Switch game and I did manage to use Texconv GUI to export a while ago, to batch convert from tex to dds. It was a BC7 lot, if I'm not mistaken.
Also, I have a tool (a .bat file, actually) that uses Texconv to convert from dds to this tex format, but not the other way around. I was hoping TexConvGui could help me to automate the batch conversion of tex to dds.
But thanks for the clarification!

Can you share some test tex textures and that bat file? Can't promise anything but will take a look.

Can you share some test tex textures and that bat file? Can't promise anything but will take a look.

Sure! Thank you very much for helping!
Test textures:
https://www.mediafire.com/file/28ivcuxac1p8arp/RE5_TEX.7z/file
.Bat file with the tools I use to convert from dds to tex:
https://www.mediafire.com/file/umtmomqy805be96/RE0+and+RE+HD+Texture+Tools.7z/file
The workflow I use is the following:
1- Since I don't have a tool to convert from tex to dds, I bruteforce my way in with Rawtex. For this, I must open a hexadecimal editor, and find the offset of the beginning of the image, discover the compression format used and the size of the  image. Then Rawtex will give me a dds file.
2- With the dds extracted by Rawtex, I start editing it.
3- When I'm done, I place my edit in the 'dds' folder of the tool I sent to you.
4- Now, I place the vanilla tex which I used in Rawtex to give me the dds, in the 'original_tex' folder of the tool I sent to you.
5- Next step is make sure my 'convert_textures.bat' file has the decimal value  of the offset of the dds image I got on step 1.
6- Now I only have to run the bat and it'll generate the working edited tex, inside the 'new_tex' folder of the toolset I sent you.
7- And that's it. Now I have to repeat the step 1 hundreds of times for every texture I have to edit because I don't have a batch conversion tool 😩
Here's hoping you can figure this out 😁

Ok this is defnitely outside the scope of this tool. But I found this post and tried the attached MegaMan11Switch_TEX script with QuickBMS and your test textures and it works.

Ok this is defnitely outside the scope of this tool. But I found this post and tried the attached MegaMan11Switch_TEX script with QuickBMS and your test textures and it works.

Oh, cool! I'll check it out!


Align with davidtheclark/focus-trap master

Specifically this commit: https://github.com/basecrm/focus-trap/pull/1/commits/b3147b2dbe69851adfcca379e701064a25da5c65 fixes https://sentry.io/base-crm/frontend/issues/149938244/


Update sbt-ci-release to 1.2.6

Updates com.geirsson:sbt-ci-release from 1.2.2 to 1.2.6.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention @scala-steward in the comments below.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [{ groupId = "com.geirsson", artifactId = "sbt-ci-release" }]

labels: semver-patch

I have no idea where the errors come from in these PRs... I'll try to take a look when I have more bandwidth

Looks like #8 worked, and now we're building with openjdk11...


Discussion about project ideas

Hey,
I created this issue to discuss possible extensions to this project. Feel free to comment here your ideas, for new features and changes to this project.

@gshukov98 can you share here your vison about this project? What would you like to add or change?

At the moment we will fix if we find existing bugs. In future we can extend functionalities.


Fix linear normalization preprocess bug

This is a quick fix to make 'linear' work
We should investigate why I needed to comment
The lines out that were a problem

Interesting. I agree, I will need to take a closer look at those lines. Did you make sure commenting them out does not affect circle preprocessing? @nmaterise

Got it.


Add example app to Aries Askar for react native

Because we can not have tests right now for the React Native wrapper, we can add an example app with some buttons to execute the code and make sure it works.
It MUST be an Expo app to keep the repo a lot smaller and should work with the latest version of RN and Expo.

Just so I don't forget the requirements of this application I will write them down here.

Expo application to reduce repository size
(only) be able to use locally-built libraries

Can do with libraries from Github release as well, but locally-built are preferred.

Should include some pages with buttons to mock the tests as is done in Node.JS

Far future:

Integrate the application into the CI, Maestro might be a good fit for this, but it is not required.

Feel free to leave suggestions here as well.


UIStoryboard  crashes on iOS

The ios build running on an iphone  Probability crashes with the crashlog shown below. Any help would be greatly appreciated.

Crash log
Incident Identifier: 8DADABE8-C4C6-4074-98E5-E24242B63ABD
CrashReporter Key:   7cef8ca5ad8229f5f350e4998c74b0bc1c0b4db5
Hardware Model:      iPad11,3
Process:             Runner [27942]
Path:                /private/var/containers/Bundle/Application/54C78347-FED5-4786-9A29-A6894BEC3D13/Runner.app/Runner
Identifier:          com.qmmx.kit
Version:             1.2.4 (38)
AppStoreTools:       14C17
Code Type:           ARM-64 (Native)
Role:                Foreground
Parent Process:      launchd [1]
Coalition:           com.qmmx.kit [1938]

Date/Time:           2023-01-10 00:50:16.2024 +0800
Launch Time:         2023-01-10 00:50:15.9579 +0800
OS Version:          iPhone OS 16.2 (20C65)
Release Type:        User
Report Version:      104

Exception Type:  EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Triggered by Thread:  0

Application Specific Information:
abort() called

Last Exception Backtrace:
0   CoreFoundation                	       0x1a4fc1e48 __exceptionPreprocess + 164
1   libobjc.A.dylib               	       0x19e30b8d8 objc_exception_throw + 60
2   UIKitCore                     	       0x1a759c838 -[UIStoryboard initWithBundle:storyboardFileName:identifierToNibNameMap:identifierToExternalStoryboardReferenceMap:designatedEntryPointIdentifier:designatedMenuIdentifier:] + 0
3   UIKitCore                     	       0x1a7433234 -[UIApplication _loadMainStoryboardFileNamed:bundle:] + 80
4   UIKitCore                     	       0x1a756e4a4 -[UIApplication _loadMainInterfaceFile] + 156
5   UIKitCore                     	       0x1a74e52ac -[UIApplication _runWithMainScene:transitionContext:completion:] + 688
6   UIKitCore                     	       0x1a74e4fa0 -[_UISceneLifecycleMultiplexer completeApplicationLaunchWithFBSScene:transitionContext:] + 132
7   UIKitCore                     	       0x1a722b20c _UIScenePerformActionsWithLifecycleActionMask + 108
8   UIKitCore                     	       0x1a756ce98 __101-[_UISceneLifecycleMultiplexer _evalTransitionToSettings:fromSettings:forceExit:withTransitionStore:]_block_invoke + 216
9   UIKitCore                     	       0x1a741dce0 -[_UISceneLifecycleMultiplexer _performBlock:withApplicationOfDeactivationReasons:fromReasons:] + 220
10  UIKitCore                     	       0x1a741db08 -[_UISceneLifecycleMultiplexer _evalTransitionToSettings:fromSettings:forceExit:withTransitionStore:] + 620
11  UIKitCore                     	       0x1a741d6b8 -[_UISceneLifecycleMultiplexer uiScene:transitionedFromState:withTransitionContext:] + 252
12  UIKitCore                     	       0x1a741d584 __186-[_UIWindowSceneFBSSceneTransitionContextDrivenLifecycleSettingsDiffAction _performActionsForUIScene:withUpdatedFBSScene:settingsDiff:fromSettings:transitionContext:lifecycleActionType:]_block_invoke + 148
13  UIKitCore                     	       0x1a7b012b8 +[BSAnimationSettings(UIKit) tryAnimatingWithSettings:fromCurrentState:actions:completion:] + 736
14  UIKitCore                     	       0x1a7b9aa8c _UISceneSettingsDiffActionPerformChangesWithTransitionContextAndCompletion + 224
15  UIKitCore                     	       0x1a72c958c -[_UIWindowSceneFBSSceneTransitionContextDrivenLifecycleSettingsDiffAction _performActionsForUIScene:withUpdatedFBSScene:settingsDiff:fromSettings:transitionContext:lifecycleActionType:] + 316
16  UIKitCore                     	       0x1a773c184 __64-[UIScene scene:didUpdateWithDiff:transitionContext:completion:]_block_invoke.214 + 556
17  UIKitCore                     	       0x1a739bbb8 -[UIScene _emitSceneSettingsUpdateResponseForCompletion:afterSceneUpdateWork:] + 216
18  UIKitCore                     	       0x1a739ba28 -[UIScene scene:didUpdateWithDiff:transitionContext:completion:] + 244
19  UIKitCore                     	       0x1a739af7c -[UIApplication workspace:didCreateScene:withTransitionContext:completion:] + 520
20  UIKitCore                     	       0x1a739ad08 -[UIApplicationSceneClientAgent scene:didInitializeWithEvent:completion:] + 288
21  FrontBoardServices            	       0x1bacdce90 -[FBSScene _callOutQueue_agent_didCreateWithTransitionContext:completion:] + 344
22  FrontBoardServices            	       0x1bad1c8f8 __92-[FBSWorkspaceScenesClient createSceneWithIdentity:parameters:transitionContext:completion:]_block_invoke.78 + 120
23  FrontBoardServices            	       0x1bace0c24 -[FBSWorkspace _calloutQueue_executeCalloutFromSource:withBlock:] + 168
24  FrontBoardServices            	       0x1bad1c530 __92-[FBSWorkspaceScenesClient createSceneWithIdentity:parameters:transitionContext:completion:]_block_invoke + 360
25  libdispatch.dylib             	       0x1ac5d0fdc _dispatch_client_callout + 20
26  libdispatch.dylib             	       0x1ac5d4a5c _dispatch_block_invoke_direct + 264
27  FrontBoardServices            	       0x1bacead40 __FBSSERIALQUEUE_IS_CALLING_OUT_TO_A_BLOCK__ + 52
28  FrontBoardServices            	       0x1bacea8dc -[FBSSerialQueue _targetQueue_performNextIfPossible] + 220
29  FrontBoardServices            	       0x1baced184 -[FBSSerialQueue _performNextFromRunLoopSource] + 28
30  CoreFoundation                	       0x1a508df34 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 28
31  CoreFoundation                	       0x1a509a30c __CFRunLoopDoSource0 + 176
32  CoreFoundation                	       0x1a501e1d0 __CFRunLoopDoSources0 + 244
33  CoreFoundation                	       0x1a5033b8c __CFRunLoopRun + 836
34  CoreFoundation                	       0x1a5038ec0 CFRunLoopRunSpecific + 612
35  GraphicsServices              	       0x1de7e3368 GSEventRunModal + 164
36  UIKitCore                     	       0x1a752e86c -[UIApplication _run] + 888
37  UIKitCore                     	       0x1a752e4d0 UIApplicationMain + 340
38  Runner                        	       0x1000650a8 main + 20648 (AppDelegate.swift:5)
39  dyld                          	       0x1c384a960 start + 2528

Thread 0 name:   Dispatch queue: com.apple.main-thread
Thread 0 Crashed:
0   libsystem_kernel.dylib        	       0x1e2081160 __pthread_kill + 8
1   libsystem_pthread.dylib       	       0x1f26dc1ac pthread_kill + 268
2   libsystem_c.dylib             	       0x1ac634c8c abort + 180
3   libc++abi.dylib               	       0x1f261bb8c abort_message + 132
4   libc++abi.dylib               	       0x1f260ba80 demangling_terminate_handler() + 336
5   libobjc.A.dylib               	       0x19e311d3c _objc_terminate() + 144
6   libc++abi.dylib               	       0x1f261af28 std::__terminate(void (*)()) + 20
7   libc++abi.dylib               	       0x1f261aec4 std::terminate() + 56
8   libdispatch.dylib             	       0x1ac5d0ff0 _dispatch_client_callout + 40
9   libdispatch.dylib             	       0x1ac5d4a5c _dispatch_block_invoke_direct + 264
10  FrontBoardServices            	       0x1bacead40 __FBSSERIALQUEUE_IS_CALLING_OUT_TO_A_BLOCK__ + 52
11  FrontBoardServices            	       0x1bacea8dc -[FBSSerialQueue _targetQueue_performNextIfPossible] + 220
12  FrontBoardServices            	       0x1baced184 -[FBSSerialQueue _performNextFromRunLoopSource] + 28
13  CoreFoundation                	       0x1a508df34 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 28
14  CoreFoundation                	       0x1a509a30c __CFRunLoopDoSource0 + 176
15  CoreFoundation                	       0x1a501e1d0 __CFRunLoopDoSources0 + 244
16  CoreFoundation                	       0x1a5033b8c __CFRunLoopRun + 836
17  CoreFoundation                	       0x1a5038ec0 CFRunLoopRunSpecific + 612
18  GraphicsServices              	       0x1de7e3368 GSEventRunModal + 164
19  UIKitCore                     	       0x1a752e86c -[UIApplication _run] + 888
20  UIKitCore                     	       0x1a752e4d0 UIApplicationMain + 340
21  Runner                        	       0x1000650a8 main + 20648 (AppDelegate.swift:5)
22  dyld                          	       0x1c384a960 start + 2528

Thread 1 name:   Dispatch queue: com.apple.UIKit.KeyboardManagement
Thread 1:
0   libsystem_kernel.dylib        	       0x1e207b5e0 __ulock_wait + 8
1   libdispatch.dylib             	       0x1ac5d19cc _dlock_wait + 56
2   libdispatch.dylib             	       0x1ac5d1780 _dispatch_thread_event_wait_slow + 56
3   libdispatch.dylib             	       0x1ac5e0860 __DISPATCH_WAIT_FOR_QUEUE__ + 368
4   libdispatch.dylib             	       0x1ac5e040c _dispatch_sync_f_slow + 144
5   UIKitCore                     	       0x1a752eb40 __37-[_UIRemoteKeyboards startConnection]_block_invoke_3 + 156
6   CoreFoundation                	       0x1a502c6c4 __invoking___ + 148
7   CoreFoundation                	       0x1a4fd8b2c -[NSInvocation invoke] + 428
8   Foundation                    	       0x19f456908 __NSXPCCONNECTION_IS_CALLING_OUT_TO_REPLY_BLOCK__ + 16
9   Foundation                    	       0x19f427c90 -[NSXPCConnection _decodeAndInvokeReplyBlockWithEvent:sequence:replyInfo:] + 520
10  Foundation                    	       0x19fa01244 __88-[NSXPCConnection _sendInvocation:orArguments:count:methodSignature:selector:withProxy:]_block_invoke_5 + 188
11  libxpc.dylib                  	       0x1f2736d48 _xpc_connection_reply_callout + 124
12  libxpc.dylib                  	       0x1f2729b90 _xpc_connection_call_reply_async + 88
13  libdispatch.dylib             	       0x1ac5d105c _dispatch_client_callout3 + 20
14  libdispatch.dylib             	       0x1ac5eef58 _dispatch_mach_msg_async_reply_invoke + 344
15  libdispatch.dylib             	       0x1ac5d856c _dispatch_lane_serial_drain + 376
16  libdispatch.dylib             	       0x1ac5d9214 _dispatch_lane_invoke + 436
17  libdispatch.dylib             	       0x1ac5e3e10 _dispatch_workloop_worker_thread + 652
18  libsystem_pthread.dylib       	       0x1f26d5df8 _pthread_wqthread + 288
19  libsystem_pthread.dylib       	       0x1f26d5b98 start_wqthread + 8

Thread 2:
0   libsystem_pthread.dylib       	       0x1f26d5b90 start_wqthread + 0

Thread 3:
0   libsystem_pthread.dylib       	       0x1f26d5b90 start_wqthread + 0

Thread 4 name:  com.apple.uikit.eventfetch-thread
Thread 4:
0   libsystem_kernel.dylib        	       0x1e207aaa8 mach_msg2_trap + 8
1   libsystem_kernel.dylib        	       0x1e208cfc4 mach_msg2_internal + 80
2   libsystem_kernel.dylib        	       0x1e208d204 mach_msg_overwrite + 388
3   libsystem_kernel.dylib        	       0x1e207afec mach_msg + 24
4   CoreFoundation                	       0x1a5032ad4 __CFRunLoopServiceMachPort + 160
5   CoreFoundation                	       0x1a5033d18 __CFRunLoopRun + 1232
6   CoreFoundation                	       0x1a5038ec0 CFRunLoopRunSpecific + 612
7   Foundation                    	       0x19f3f70d4 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 212
8   Foundation                    	       0x19f3f6fbc -[NSRunLoop(NSRunLoop) runUntilDate:] + 64
9   UIKitCore                     	       0x1a766372c -[UIEventFetcher threadMain] + 436
10  Foundation                    	       0x19f4105a8 __NSThread__start__ + 716
11  libsystem_pthread.dylib       	       0x1f26d66cc _pthread_start + 148
12  libsystem_pthread.dylib       	       0x1f26d5ba4 thread_start + 8

Thread 5:
0   libsystem_pthread.dylib       	       0x1f26d5b90 start_wqthread + 0

Thread 6 name:   Dispatch queue: com.apple.root.default-qos
Thread 6:
0   libsystem_kernel.dylib        	       0x1e207b5e0 __ulock_wait + 8
1   libdispatch.dylib             	       0x1ac5d19cc _dlock_wait + 56
2   libdispatch.dylib             	       0x1ac5d1780 _dispatch_thread_event_wait_slow + 56
3   libdispatch.dylib             	       0x1ac5e0860 __DISPATCH_WAIT_FOR_QUEUE__ + 368
4   libdispatch.dylib             	       0x1ac5e040c _dispatch_sync_f_slow + 144
5   AXCoreUtilities               	       0x1b0190208 AXPerformBlockSynchronouslyOnMainThread + 108
6   AccessibilityUtilities        	       0x1ae6a4b14 ___AXSharedDisplayManager_block_invoke_2 + 40
7   libdispatch.dylib             	       0x1ac5cf4b4 _dispatch_call_block_and_release + 32
8   libdispatch.dylib             	       0x1ac5d0fdc _dispatch_client_callout + 20
9   libdispatch.dylib             	       0x1ac5d40c8 _dispatch_queue_override_invoke + 788
10  libdispatch.dylib             	       0x1ac5e2a6c _dispatch_root_queue_drain + 396
11  libdispatch.dylib             	       0x1ac5e3284 _dispatch_worker_thread2 + 164
12  libsystem_pthread.dylib       	       0x1f26d5dbc _pthread_wqthread + 228
13  libsystem_pthread.dylib       	       0x1f26d5b98 start_wqthread + 8

Thread 7 name:   Dispatch queue: AXCodeLoader
Thread 7:
0   libobjc.A.dylib               	       0x19e2fd0b8 objc_storeStrong + 8
1   AccessibilityUtilities        	       0x1ae71e26c -[_AXCodeItemDecoder decodedCodeItemsFromURL:decodingErrors:] + 3568
2   AccessibilityUtilities        	       0x1ae68c660 -[AXCodeLoader _createAccessibilityCodeItemsFromBundleMapURLs:] + 356
3   AccessibilityUtilities        	       0x1ae68b430 -[AXCodeLoader _updateAccessibilityCodeItemDefinitionsIfNeeded] + 280
4   AccessibilityUtilities        	       0x1ae689778 __76-[AXCodeLoader beginTrackingLoadedCodeItemsWithMode:completion:targetQueue:]_block_invoke + 164
5   libdispatch.dylib             	       0x1ac5cf4b4 _dispatch_call_block_and_release + 32
6   libdispatch.dylib             	       0x1ac5d0fdc _dispatch_client_callout + 20
7   libdispatch.dylib             	       0x1ac5d8694 _dispatch_lane_serial_drain + 672
8   libdispatch.dylib             	       0x1ac5d91e0 _dispatch_lane_invoke + 384
9   libdispatch.dylib             	       0x1ac5e3e10 _dispatch_workloop_worker_thread + 652
10  libsystem_pthread.dylib       	       0x1f26d5df8 _pthread_wqthread + 288
11  libsystem_pthread.dylib       	       0x1f26d5b98 start_wqthread + 8

Thread 0 crashed with ARM Thread State (64-bit):
    x0: 0x0000000000000000   x1: 0x0000000000000000   x2: 0x0000000000000000   x3: 0x0000000000000000
    x4: 0x00000001f261f0f5   x5: 0x000000016fd9e180   x6: 0x000000000000006e   x7: 0xffffffff00000300
    x8: 0x988830f86c04f916   x9: 0x988830f997220ed6  x10: 0x0000000000000200  x11: 0x000000000000000b
   x12: 0x000000000000000b  x13: 0x00000000001ff800  x14: 0x00000000000007fb  x15: 0x00000000cc80e860
   x16: 0x0000000000000148  x17: 0x00000001fb26f7c0  x18: 0x0000000000000000  x19: 0x0000000000000006
   x20: 0x0000000000000103  x21: 0x00000001fb26f8a0  x22: 0x0000000000000000  x23: 0x00000001fb26f8a0
   x24: 0x00000002838dc310  x25: 0x00000001fbbdcb58  x26: 0x0000000000000000  x27: 0x00000000211200d5
   x28: 0x00000001c616d880   fp: 0x000000016fd9e0f0   lr: 0x00000001f26dc1ac
    sp: 0x000000016fd9e0d0   pc: 0x00000001e2081160 cpsr: 0x40000000
   far: 0x00000001f8758480  esr: 0x56000080  Address size fault

Binary Images:
       0x1e2076000 -        0x1e20b0fe3 libsystem_kernel.dylib arm64e  <9daa5c2993e03768a3e1e139995dc4af> /usr/lib/system/libsystem_kernel.dylib
       0x1f26d5000 -        0x1f26e0fff libsystem_pthread.dylib arm64e  <f2ba7ec0f75a3345b4f6f7da4979b902> /usr/lib/system/libsystem_pthread.dylib
       0x1ac614000 -        0x1ac693ff7 libsystem_c.dylib arm64e  <f088d98df2a13452996f9e6bb5139f52> /usr/lib/system/libsystem_c.dylib
       0x1f260a000 -        0x1f2621ffb libc++abi.dylib arm64e  <a0028fdf20f43a76a43df0fa725bee9f> /usr/lib/libc++abi.dylib
       0x19e2f4000 -        0x19e337e1f libobjc.A.dylib arm64e  <d6ecfb730ca23a21a3a919e450d3b49c> /usr/lib/libobjc.A.dylib
       0x1ac5cd000 -        0x1ac613fff libdispatch.dylib arm64e  <24db930d870b31ceac69534d7896b4a8> /usr/lib/system/libdispatch.dylib
       0x1bacda000 -        0x1bad80fff FrontBoardServices arm64e  <2cec922bdd383ca7b826f3de9118f37a> /System/Library/PrivateFrameworks/FrontBoardServices.framework/FrontBoardServices
       0x1a4fb8000 -        0x1a539dfff CoreFoundation arm64e  <725e49f4653b39bf9a7a8a3250911ecb> /System/Library/Frameworks/CoreFoundation.framework/CoreFoundation
       0x1de7e2000 -        0x1de7eafff GraphicsServices arm64e  <5adda888f38735f787a7e01fcb9bb928> /System/Library/PrivateFrameworks/GraphicsServices.framework/GraphicsServices
       0x1a718d000 -        0x1a8978fff UIKitCore arm64e  <59cbc9b530ae396ea269a986640001bc> /System/Library/PrivateFrameworks/UIKitCore.framework/UIKitCore
       0x100060000 -        0x10011ffff Runner arm64  <cf0d37bf60473d7385ca71217e258748> /private/var/containers/Bundle/Application/54C78347-FED5-4786-9A29-A6894BEC3D13/Runner.app/Runner
       0x1c3835000 -        0x1c38b808f dyld arm64e  <7b63c57361613b33a3a29944ba59722f> /usr/lib/dyld
       0x19f3b5000 -        0x19fcfefff Foundation arm64e  <07a92f05d8ec327eab3341db9f77ba16> /System/Library/Frameworks/Foundation.framework/Foundation
       0x1f2719000 -        0x1f2759fff libxpc.dylib arm64e  <9826b3aa0ca03ca4b664d86869fb33f2> /usr/lib/system/libxpc.dylib
       0x1b018e000 -        0x1b01b0fff AXCoreUtilities arm64e  <44bf5b5d880d35fcb8986f444a801172> /System/Library/PrivateFrameworks/AXCoreUtilities.framework/AXCoreUtilities
       0x1ae5f7000 -        0x1ae7b2fff AccessibilityUtilities arm64e  <bfe59883f5103fb3a0bcde1e95a7ae6b> /System/Library/PrivateFrameworks/AccessibilityUtilities.framework/AccessibilityUtilities

EOF

flutter doctor -v
[✓] Flutter (Channel stable, 3.0.5, on macOS 13.1 22C65 darwin-x64, locale zh-Hans-CN)
    • Flutter version 3.0.5 at /Users/os/Documents/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision f1875d570e (6 months ago), 2022-07-13 11:24:16 -0700
    • Engine revision e85ea0e79c
    • Dart version 2.17.6
    • DevTools version 2.12.2
    • Pub download mirror https://pub.flutter-io.cn
    • Flutter download mirror https://storage.flutter-io.cn

[!] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
    • Android SDK at /Users/os/Library/Android/sdk
    ✗ cmdline-tools component is missing
      Run `path/to/sdkmanager --install "cmdline-tools;latest"`
      See https://developer.android.com/studio/command-line for more details.
    ✗ Android license status unknown.
      Run `flutter doctor --android-licenses` to accept the SDK licenses.
      See https://flutter.dev/docs/get-started/install/macos#android-setup for more details.

[✓] Xcode - develop for iOS and macOS (Xcode 14.2)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2021.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)

[✓] VS Code (version 1.74.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.56.0

[✓] Connected device (3 available)
    • iPhone (3) (mobile) • 00008110-000A0D3A0103801E • ios            • iOS 16.2 20C65
    • macOS (desktop)     • macos                     • darwin-x64     • macOS 13.1 22C65 darwin-x64
    • Chrome (web)        • chrome                    • web-javascript • Google Chrome 105.0.5195.125

[✓] HTTP Host Availability
    • All required HTTP hosts are available
! Doctor found issues in 1 category.

Hi @WangLao100, are you able to reproduce this crash locally?
If you can, please provide a complete minimal reproducible code sample so that we can investigate.
If you cannot, can you tell us the device(s) that are experiencing the crash along with the frequency of the crashes?
Also, is your app a regular flutter app or is it a native app with flutter embedded?
Thank you

This crash will be reproduced locally, and this could happen with ios 15 versions or later. You could start the application and then close it，but after restart the application, the application may also crash 1-2 times out of 20 times. As for the code samples, I will take the time to reprocess them.

From duplicate https://github.com/flutter/flutter/issues/118303

Flutter isn't in that stack trace and it's not even loaded in the Binary Images section, and just an abort with no exception information from UIKit is extremely unhelpful...

This crash will be reproduced locally, and this could happen with ios 15 versions or later.

Are you able to catch it in the debugger if you run from Xcode ios/Runner.xcworkspace?

FlutterViewController, which is heavily used in engineering. The FlutterViewController was generated using the UIStoryboard. I will provide you with a complete minimal reproducible code sample .

Just figured out what caused #118303 - see https://github.com/flutter/flutter/issues/118303#issuecomment-1385390375


Replace once_cell usage with std::sync::OnceLock

Closes #30
Closes #1141
See also https://github.com/gtk-rs/gir/pull/1532
This change does not fully remove once_cell. Full removal will break a contract of glib::Properties macro.

I guess, this PR should be merged first.

before landing this, someone should do the same for gstreamer as they use the re-exported once_cell crate from glib iirc

But we have a Cargo.lock so I'll take care of that once this is merged :) I'll shortly go over this again and then merge it.


Add Pub/Sub example

Description
Adding example for Pub/Sub pattern.
Issue reference
#32
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list:

[x] Code compiles correctly
[ ] Created/updated tests
[x] Extended the documentation

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: letmerecall sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

Hi, tried to add a simple pub/sub example. I hope it will be helpful for other.
Let me know if any changes needed :)

Thanks @letmerecall  for the contribution

Thanks @letmerecall  for the contribution


[AKS] TOC entry for AKS

:warning: Validation status: warnings

File
Status
Preview URL
Details

docs-ref-autogen/overview/azure/AKS.yml
:warning:Warning

Details

docs-ref-mapping/reference.yml
:white_check_mark:Succeeded

docs-ref-autogen/overview/azure/AKS.yml

[Warning] Uid(azure.python.sdk.landingPage.services.Container.Service) has already been defined in docs-ref-autogen/overview/azure/ContainerService.yml.

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

:warning: Validation status: warnings

File
Status
Preview URL
Details

docs-ref-autogen/overview/azure/AKS.yml
:warning:Warning

Details

docs-ref-conceptual/python-azure-tools.md
:white_check_mark:Succeeded

docs-ref-mapping/reference.yml
:white_check_mark:Succeeded

docs-ref-autogen/overview/azure/AKS.yml

[Warning] Uid(azure.python.sdk.landingPage.services.Container.Service) has already been defined in docs-ref-autogen/overview/azure/ContainerService.yml.

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


Fix sample code in Consumer API Docs

I found a compilation error in the sample code of Consumer API Docs and fixed it.

Thanks!