does it work with Jetson Jetpack 4.5.1?

Hi, Thank you for your contribution.
Could you advise where to start given we are interested in use of Deepstream integrattion with the most recent Jetpack 4.5.1 release of the Jetson OS , please?

@AndreV84, there is no reason why it should not, due to bandwidth constraints I have not tested personally but would say the odds are highly in your favor that it will "just work" ^TM.  Let us know if you get this up and running and we'll close out the issue.

Hi @toolboc Is there any chance to run the thing without use of the visual code at all?
I installed it both on Jetson / Host x88_64 PC.
It can not execute Select IoT Hub from both devices , as the VSCode is argumenting that it can not find subscription. However there is one that I am using to create IoT hub, device, storage etc.
moreover. Can we not use the visual code  as it fails discovering one of the active subscription at the account? can we use some other deployment approach than the vscode?

failing deployment with this
[Edge] Deployment failed. ArgumentError: Property or Tag name has invalid characters. Error in Property/Tag $LOCAL_STORAGE_ACCOUNT_NAME. Must not contain Control Characters, '.', '$', '#', or ' '.

the .env file has entries:
CONTAINER_REGISTRY_NAME=
LOCAL_STORAGE_ACCOUNT_KEY=3CuWSiDUYNDTT9UeL7OhLQ==
LOCAL_STORAGE_ACCOUNT_NAME=123
DESTINATION_STORAGE_NAME=camerataggingmodulecloud
CLOUD_STORAGE_CONNECTION_STRING=

I will try to do the steps on one more jetson - anothre board also flashed with Jetpack 4.5.1

at nx [ it has no display at all so after first run I disabled the GL sink to fake sink
but the error seems the same as at AGX
 iotedge logs NVIDIADeepStreamSDK
nvbuf_utils: Could not get EGL display connection
No EGL Display
nvbufsurftransform: Could not get EGL display connection
nvbuf_utils: Could not get EGL display connection
No EGL Display
nvbufsurftransform: Could not get EGL display connection
No EGL Display
nvbufsurftransform: Could not get EGL display connection
No EGL Display
nvbufsurftransform: Could not get EGL display connection
No EGL Display
nvbufsurftransform: Could not get EGL display connection
No EGL Display
nvbufsurftransform: Could not get EGL display connection
No EGL Display
nvbufsurftransform: Could not get EGL display connection
No EGL Display
nvbufsurftransform: Could not get EGL display connection
No EGL Display
nvbufsurftransform: Could not get EGL display connection
No EGL Display
nvbufsurftransform: Could not get EGL display connection
No EGL Display
nvbufsurftransform: Could not get EGL display connection
No EGL Display
nvbufsurftransform: Could not get EGL display connection
2021-04-01 11:42:13.554186: I tensorflow/stream_executor/platform/default/dso_loader.cc:48] Successfully opened dynamic library libcudart.so.10.2
No EGL Display
nvbufsurftransform: Could not get EGL display connection
2021-04-01 11:42:14.602195: I tensorflow/stream_executor/platform/default/dso_loader.cc:48] Successfully opened dynamic library libcudart.so.10.2
No EGL Display
nvbufsurftransform: Could not get EGL display connection
No EGL Display
nvbufsurftransform: Could not get EGL display connection
No EGL Display
nvbufsurftransform: Could not get EGL display connection
No EGL Display
nvbufsurftransform: Could not get EGL display connection
No EGL Display
nvbufsurftransform: Could not get EGL display connection
** ERROR: <create_multi_source_bin:1057>: Failed to create element 'src_bin_muxer'
** ERROR: <create_multi_source_bin:1132>: create_multi_source_bin failed
** ERROR: <create_pipeline:1296>: create_pipeline failed
** ERROR: <main:1419>: Failed to create pipeline
Quitting
App run failed
** ERROR: <create_multi_source_bin:1057>: Failed to create element 'src_bin_muxer'
** ERROR: <create_multi_source_bin:1132>: create_multi_source_bin failed
** ERROR: <create_pipeline:1296>: create_pipeline failed
** ERROR: <main:1419>: Failed to create pipeline
Quitting
App run failed
** ERROR: <create_multi_source_bin:1057>: Failed to create element 'src_bin_muxer'
** ERROR: <create_multi_source_bin:1132>: create_multi_source_bin failed
** ERROR: <create_pipeline:1296>: create_pipeline failed
** ERROR: <main:1419>: Failed to create pipeline
Quitting
App run failed
** ERROR: <create_multi_source_bin:1057>: Failed to create element 'src_bin_muxer'
** ERROR: <create_multi_source_bin:1132>: create_multi_source_bin failed
** ERROR: <create_pipeline:1296>: create_pipeline failed
** ERROR: <main:1419>: Failed to create pipeline
Quitting
App run failed
** ERROR: <create_multi_source_bin:1057>: Failed to create element 'src_bin_muxer'
** ERROR: <create_multi_source_bin:1132>: create_multi_source_bin failed
** ERROR: <create_pipeline:1296>: create_pipeline failed
** ERROR: <main:1419>: Failed to create pipeline
Quitting
App run failed
** ERROR: <create_multi_source_bin:1057>: Failed to create element 'src_bin_muxer'
** ERROR: <create_multi_source_bin:1132>: create_multi_source_bin failed
** ERROR: <create_pipeline:1296>: create_pipeline failed
** ERROR: <main:1419>: Failed to create pipeline
Quitting
App run failed

The error indicating "Could not get EGL display connection" implies that you may not be exposing the appropriate v4l device to the container, this is accomplished in the IoT Edge docker create options here: https://github.com/toolboc/Intelligent-Video-Analytics-with-NVIDIA-Jetson-and-Microsoft-Azure/issues/18
Have you exposed the X11 socket and proper V4L path to the container?  See: https://github.com/toolboc/Intelligent-Video-Analytics-with-NVIDIA-Jetson-and-Microsoft-Azure/blob/master/docs/Module 2 - Configure and Deploy Intelligent Video Analytics to IoT Edge Runtime on NVIDIA Jetson.md#module-23--prepare-the-jetson-device-to-use-the-intelligent-video-analytics-sample-configurations

@toolboc
Thank you for following up
I tried running at local jetson with display conncted, but also without display conencted at another Jetson.
In my case with 20 or so attemps to run theapp it did not work at neither of the two devices.
It does't work without display connected at all, doesn't it?
The requirement of the display seems might be due to GLSink in the DeepStream config file. But the display doesn't cause termination of deepstream execution typically. Moreover, I I tried to switch the configuration to Fake sink/ Filesink from GLSink in efforts to troubleshoot it. However, I noticed that log files only reflect entries from first run of the container. From further running or restarting there are no more enrties in the log file added.
How to run the app so that deepstream gets running?
Have you had a chance to implement it with Deepstream 5.1? with Jetpack 4.5.1? With both? With neither of the two?
Is ther any way to get the thing running given I have two jetsons - one with Display also one without a display at all? How to exclude the display error if running the application at device that has the display, but excluding it to avoid the error at all?

@AndreV84,
I have had the chance to implement using DeepStream 5.1 and Jetpack 4.5.1 without issue (although this was using an in-place upgrade of Jetpack which is now possible via Debian based package updates).
One way that you could mitigate the issue possibly being related to a connected display is to only output results to an RTSP sink and connect to that for visual results.

How to make it work?
Does it require to re-deploy from VSCode?
OrI just run the restart docker command for DeepStream container after editing with
 nano /data/misc/storage/Intelligent-Video-Analytics-with-NVIDIA-Jetson-and-Microsoft-Azure/services/DEEPSTREAM/configs/DSConfig-CustomVisionAI.txt

here is sink section I put sink to 5 [rtsp] but I also tried other options
then
docker restart NVIDIADeepStreamSDK

The output is
iotedge logs NVIDIADeepStreamSDK
** ERROR: <create_multi_source_bin:1057>: Failed to create element 'src_bin_muxer'
** ERROR: <create_multi_source_bin:1132>: create_multi_source_bin failed
** ERROR: <create_pipeline:1296>: create_pipeline failed
** ERROR: <main:1419>: Failed to create pipeline
Quitting
App run failed

I do not need visual output at this point but just to get the service running with Azure Iot.
even with Fakesink -sink0=1
 iotedge logs NVIDIADeepStreamSDK
** ERROR: <create_multi_source_bin:1057>: Failed to create element 'src_bin_muxer'
** ERROR: <create_multi_source_bin:1132>: create_multi_source_bin failed
** ERROR: <create_pipeline:1296>: create_pipeline failed
** ERROR: <main:1419>: Failed to create pipeline
Quitting
App run failed
** ERROR: <create_multi_source_bin:1057>: Failed to create element 'src_bin_muxer'
** ERROR: <create_multi_source_bin:1132>: create_multi_source_bin failed
** ERROR: <create_pipeline:1296>: create_pipeline failed
** ERROR: <main:1419>: Failed to create pipeline
Quitting
App run failed

how to overcome this?
iotedge logs NVIDIADeepStreamSDK
** ERROR: <create_multi_source_bin:1057>: Failed to create element 'src_bin_muxer'
** ERROR: <create_multi_source_bin:1132>: create_multi_source_bin failed
** ERROR: <create_pipeline:1296>: create_pipeline failed
** ERROR: <main:1419>: Failed to create pipeline
Quitting
App run failed
** ERROR: <create_multi_source_bin:1057>: Failed to create element 'src_bin_muxer'
** ERROR: <create_multi_source_bin:1132>: create_multi_source_bin failed
** ERROR: <create_pipeline:1296>: create_pipeline failed
** ERROR: <main:1419>: Failed to create pipeline
Quitting
App run failed
** ERROR: <create_multi_source_bin:1057>: Failed to create element 'src_bin_muxer'
** ERROR: <create_multi_source_bin:1132>: create_multi_source_bin failed
** ERROR: <create_pipeline:1296>: create_pipeline failed
** ERROR: <main:1419>: Failed to create pipeline
Quitting
App run failed

@toolboc with sink 0 =1 Fakesink the error is
 iotedge logs NVIDIADeepStreamSDK
** ERROR: <create_multi_source_bin:1057>: Failed to create element 'src_bin_muxer'
** ERROR: <create_multi_source_bin:1132>: create_multi_source_bin failed
** ERROR: <create_pipeline:1296>: create_pipeline failed
** ERROR: <main:1419>: Failed to create pipeline
Quitting
App run failed
** ERROR: <create_multi_source_bin:1057>: Failed to create element 'src_bin_muxer'
** ERROR: <create_multi_source_bin:1132>: create_multi_source_bin failed
** ERROR: <create_pipeline:1296>: create_pipeline failed
** ERROR: <main:1419>: Failed to create pipeline
Quitting
App run failed
** ERROR: <create_multi_source_bin:1057>: Failed to create element 'src_bin_muxer'
** ERROR: <create_multi_source_bin:1132>: create_multi_source_bin failed
** ERROR: <create_pipeline:1296>: create_pipeline failed
** ERROR: <main:1419>: Failed to create pipeline
Quitting
App run failed
** ERROR: <create_multi_source_bin:1057>: Failed to create element 'src_bin_muxer'
** ERROR: <create_multi_source_bin:1132>: create_multi_source_bin failed
** ERROR: <create_pipeline:1296>: create_pipeline failed
** ERROR: <main:1419>: Failed to create pipeline
Quitting
App run failed
** ERROR: <create_multi_source_bin:1057>: Failed to create element 'src_bin_muxer'
** ERROR: <create_multi_source_bin:1132>: create_multi_source_bin failed
** ERROR: <create_pipeline:1296>: create_pipeline failed
** ERROR: <main:1419>: Failed to create pipeline
Quitting
App run failed
** ERROR: <create_multi_source_bin:1057>: Failed to create element 'src_bin_muxer'
** ERROR: <create_multi_source_bin:1132>: create_multi_source_bin failed
** ERROR: <create_pipeline:1296>: create_pipeline failed
** ERROR: <main:1419>: Failed to create pipeline
Quitting
App run failed

with other values for sink in the file errors differ e.g.
with other sink combinations the errors differ but it won't work e.g.
iotedge logs NVIDIADeepStreamSDK
** ERROR: <create_multi_source_bin:1057>: Failed to create element 'src_bin_muxer'
** ERROR: <create_multi_source_bin:1132>: create_multi_source_bin failed
** ERROR: <create_pipeline:1296>: create_pipeline failed
** ERROR: <main:1419>: Failed to create pipeline
Quitting
App run failed
** ERROR: <create_multi_source_bin:1057>: Failed to create element 'src_bin_muxer'
** ERROR: <create_multi_source_bin:1132>: create_multi_source_bin failed
** ERROR: <create_pipeline:1296>: create_pipeline failed
** ERROR: <main:1419>: Failed to create pipeline
Quitting
App run failed
** ERROR: <create_multi_source_bin:1057>: Failed to create element 'src_bin_muxer'
** ERROR: <create_multi_source_bin:1132>: create_multi_source_bin failed
** ERROR: <create_pipeline:1296>: create_pipeline failed
** ERROR: <main:1419>: Failed to create pipeline
Quitting
App run failed
** ERROR: <create_multi_source_bin:1057>: Failed to create element 'src_bin_muxer'
** ERROR: <create_multi_source_bin:1132>: create_multi_source_bin failed
** ERROR: <create_pipeline:1296>: create_pipeline failed
** ERROR: <main:1419>: Failed to create pipeline
Quitting
App run failed
** ERROR: <create_multi_source_bin:1057>: Failed to create element 'src_bin_muxer'
** ERROR: <create_multi_source_bin:1132>: create_multi_source_bin failed
** ERROR: <create_pipeline:1296>: create_pipeline failed
** ERROR: <main:1419>: Failed to create pipeline
Quitting
App run failed
** ERROR: <create_multi_source_bin:1057>: Failed to create element 'src_bin_muxer'
** ERROR: <create_multi_source_bin:1132>: create_multi_source_bin failed
** ERROR: <create_pipeline:1296>: create_pipeline failed
** ERROR: <main:1419>: Failed to create pipeline
Quitting
App run failed
** ERROR: <create_multi_source_bin:1057>: Failed to create element 'src_bin_muxer'
** ERROR: <create_multi_source_bin:1132>: create_multi_source_bin failed
** ERROR: <create_pipeline:1296>: create_pipeline failed
** ERROR: <main:1419>: Failed to create pipeline
Quitting
App run failed
** ERROR: <create_multi_source_bin:1057>: Failed to create element 'src_bin_muxer'
** ERROR: <create_multi_source_bin:1132>: create_multi_source_bin failed
** ERROR: <create_pipeline:1296>: create_pipeline failed
** ERROR: <main:1419>: Failed to create pipeline
Quitting
App run failed
** ERROR: <create_multi_source_bin:1057>: Failed to create element 'src_bin_muxer'
** ERROR: <create_multi_source_bin:1132>: create_multi_source_bin failed
** ERROR: <create_pipeline:1296>: create_pipeline failed
** ERROR: <main:1419>: Failed to create pipeline
Quitting
App run failed

@AndreV84,
Any chance you can post the full contents of your DeepStream configuration file and associated IoT Deployment Manfiest (with any username / passwords redacted)?

@toolboc
DSConfig-CustomVisionAI.txt
deployment.arm64v8_redacted.json.txt
the config file is located at /data/misc/storage/Intelligent-Video-Analytics-with-NVIDIA-Jetson-and-Microsoft-Azure/services/DEEPSTREAM/configs/DSConfig-CustomVisionAI.txt
the deployemnt manifest is generated by Vscode - tried from Jetson, also from x86_64
sometimes the deployment manifest also appears at Azure interface sometimes it doesnt regardless successfull status message at vscode after deploying it to device

@AndreV84,
Take a look at this potential resolution, it is possible that you are setting an incorrect value for DISPLAY (in your deployment template this is set to '1').   This error likely has nothing to do with JetPack version and more likely to do with the X11 configuration on your device.

@toolboc Thank you for your response.
Yes, but I process attempts/ trials in batch like 10-12 configurations one after one after them failing
right after I tried with DISPALY 1. I also tried editing the 1 value in the vscode to 0 then pressed - deploy top sinbgle device. It did not change anything
I also tried disabling / changing every of the three sink\s in the Deepstream Configuration file.
Last day efforts did reflect all statuses OK but for Deepsteam 255 at Azure Web page. Moreover, this time there was no deployment manifest listed at Azure interface that was previously listed there.
Any ideas? But for the Display? How to exclude the Display at all but for editing the Deepstream config file? So that no display would be required for the Deepstream to repurt the OK status in Azure web page?

@toolboc could you confirm if the whole thing does work with disconnected display, please? given in the DeepStream config file eGL sink is disabled in favour of fakesink or just disabled?

You should be able to isolate the issue by modifying the DISPLAY env var name  to something like DISPLAY_PLACEHOLDER, which should force DeepStream to be unable to attempt to connect to any display, in addition to disabling or setting local output to a FakeSink.
I've validated that the workload will work as expected when using FakeSink or disabling Source 0, in either case the output is as expected:
paul@jetson-xaviernx-00:~$ docker logs -f NVIDIADeepStreamSDK
2021-04-07 17:31:01.249303: I tensorflow/stream_executor/platform/default/dso_loader.cc:48] Successfully opened dynamic library libcudart.so.10.2

 *** DeepStream: Launched RTSP Streaming at rtsp://localhost:8554/ds-test ***

(deepstream-test5-app:1): GLib-CRITICAL **: 17:31:01.932: g_strrstr: assertion 'haystack != NULL' failed
0:00:07.132895324     1     0x3bea4d00 INFO                 nvinfer gstnvinfer.cpp:619:gst_nvinfer_logger:<primary_gie> NvDsInferContext[UID 1]: Info from NvDsInferContextImpl::deserializeEngineAndBackend() <nvdsinfer_context_impl.cpp:1701> [UID = 1]: deserialized trt engine from :/data/misc/storage/Intelligent-Video-Analytics-with-NVIDIA-Jetson-and-Microsoft-Azure/services/DEEPSTREAM/configs/../../CUSTOM_VISION_AI/model.onnx_b4_gpu0_fp32.engine
0:00:07.133369029     1     0x3bea4d00 INFO                 nvinfer gstnvinfer.cpp:619:gst_nvinfer_logger:<primary_gie> NvDsInferContext[UID 1]: Info from NvDsInferContextImpl::generateBackendContext() <nvdsinfer_context_impl.cpp:1805> [UID = 1]: Use deserialized engine model: /data/misc/storage/Intelligent-Video-Analytics-with-NVIDIA-Jetson-and-Microsoft-Azure/services/DEEPSTREAM/configs/../../CUSTOM_VISION_AI/model.onnx_b4_gpu0_fp32.engine
0:00:07.325240353     1     0x3bea4d00 INFO                 nvinfer gstnvinfer_impl.cpp:313:notifyLoadModelStatus:<primary_gie> [UID 1]: Load new model:/data/misc/storage/Intelligent-Video-Analytics-with-NVIDIA-Jetson-and-Microsoft-Azure/services/DEEPSTREAM/configs/config_infer_primary_CustomVisionAI.txt sucessfully
nvds_msgapi_connect : connect success
Opening in BLOCKING MODE
WARNING: [TRT]: Using an engine plan file across different models of devices is not recommended and is likely to affect performance or even cause errors.
INFO: [FullDims Engine Info]: layers num: 2
0   INPUT  kFLOAT data            3x416x416       min: 1x3x416x416     opt: 4x3x416x416     Max: 4x3x416x416
1   OUTPUT kFLOAT model_outputs0  45x13x13        min: 0               opt: 0               Max: 0

Runtime commands:
        h: Print this help
        q: Quit

        p: Pause
        r: Resume

NOTE: To expand a source in the 2D tiled display and view object details, left-click on the source.
      To go back to the tiled display, right-click anywhere on the window.

** INFO: <bus_callback:181>: Pipeline ready

@toolboc I put the placeholder
also make sure that there is no GL sink
but the logs still show yesterdays errors not todays errors
how to undeploy/ wipe the whole thing to get the updated todays logs reflected?

now it shows the status as running in microsoft Azure
but it does also show that there is no deployment configuration [ previously it was listed in deployment cofiguration at azure
previously it would show the entire deployment manifest there
how to wipe then redo correctly?

it seems that it fails more often if just to use vscode on jetson or vscode on x86_64
but when approaching from two vscodes from both devices it gets step further but still some issues

``
(deepstream-test5-app:1): GLib-GObject-CRITICAL **: 18:34:50.124: g_object_get: assertion 'G_IS_OBJECT (object)' failed
(deepstream-test5-app:1): GLib-GObject-CRITICAL **: 18:34:50.164: g_object_get: assertion 'G_IS_OBJECT (object)' failed
(deepstream-test5-app:1): GLib-GObject-CRITICAL **: 18:34:50.205: g_object_get: assertion 'G_IS_OBJECT (object)' failed
(deepstream-test5-app:1): GLib-GObject-CRITICAL **: 18:34:50.245: g_object_get: assertion 'G_IS_OBJECT (object)' failed
Message sent : {
"version" : "4.0",
"id" : 7267,
"@timestamp" : "2021-04-07T18:34:50.178Z",
"sensorId" : "Camera_0",
"objects" : [
"-1|208.269|21.1966|240|54.7009|car"
it shows errors like that
is it fine?

could you extend on how to read events from Azure mqtt interface, please?

(deepstream-test5-app:1): GLib-GObject-CRITICAL **: 18:34:50.124: g_object_get: assertion 'G_IS_OBJECT (object)' failed

(deepstream-test5-app:1): GLib-GObject-CRITICAL **: 18:34:50.164: g_object_get: assertion 'G_IS_OBJECT (object)' failed

(deepstream-test5-app:1): GLib-GObject-CRITICAL **: 18:34:50.205: g_object_get: assertion 'G_IS_OBJECT (object)' failed

(deepstream-test5-app:1): GLib-GObject-CRITICAL **: 18:34:50.245: g_object_get: assertion 'G_IS_OBJECT (object)' failed
Message sent : {
  "version" : "4.0",
  "id" : 7267,
  "@timestamp" : "2021-04-07T18:34:50.178Z",
  "sensorId" : "Camera_0",
  "objects" : [
    "-1|208.269|21.1966|240|54.7009|car"

it shows errors like that
is it fine?

This is fine

could you extend on how to read events from Azure mqtt interface, please?

You can take a look at "Sample test application 5" and the "Azure MQTT test application" that are included in the DeepStream SDK.  Some basic description and the path locations for the source code of these applications can be found in the DeepStream C/C++  Sample Apps documentation.

@toolboc could you direct on how to add message broker GPS information, please?
given there is GPS uinit connected to the jetson sao we would like the messages to come to Azure from it


Implement the rank form view in the game page(which is active in each turn).

6710c8f227d189402e979cd24665ad166c8dae1b

de45cd1f76ec8b763ed06a34b1e1e068845d0b6e


fix(kit): Stepper - add markForCheck on activate step

Co-authored-by: Sviatoslav Zaytsev<EMAIL_ADDRESS>(cherry picked from commit 033fd52c870b339e21f668bb862a67c87d19bb4b)
PR Type
What kind of change does this PR introduce?

[x] Bugfix
[ ] Feature
[ ] Refactoring
[ ] Build or CI related changes
[ ] Documentation content changes

What is the current behavior?
Closes #3629
What is the new behavior?
Does this PR introduce a breaking change?

[ ] Yes
[x] No

still reproduced in 2.82 at https://taiga-ui.dev/v2/navigation/stepper

also scroll to active step not working in V3 (3.22) after component init


Fix: 82 hyp_dictionary not printing childs

Fixes #82

Tests are running fine on Xcode.


ci: update actions/checkout to v3

Looking at https://github.com/actions/checkout/issues shows a couple issues that's happening with docker containers, but our docker containers are a completely separate from tests, so we don't have to worry about it. We don't plan on adding anything docker related to our tests in the foreseeable future right? @austinabell. Otherwise, this looks good to be added

thanks @armujahid !


Infinite loading

Hey i've tried to load a glTF file with your plugin, everything seemed to work properly, but now its been ~ 10 minute and its still stuck on

is it normal ? :c (my glTF is about ~600mb)
(ue4 4.26.1 and your latest plugin version)
(after 20~ minute i've tried with a .gltf instead of .glb, this time, unreal crashed after few seconds)

@Fr0zka  Yes, it's not reasonable.
Can you send the log to me or describe the content of your glTF file? You can find log files in [YourProject]\Saved\Log folder.

I'm uploading the .gltf file right now, but there is the log for now ^^'
Hide.log

@Fr0zka Ok, I got. Give me time to check.

Ok, I know the reason. The glTF file contains about 1600+ objects. For each asset, it will recalculate the md5 value that is generated by the glTF file. The glTF is too big to spend about 1 second to calculate the MD5 value. So it does that about 1600+ times 😵 , it will cost about 20 mins 😢  (also depend on your machine).
And I import it after I fix it and cost about 6 mins 😃  on my laptop.

I will fix it in the next version 2.0.6.

@Fr0zka Does Does the unreal crash when importing the glb file? Can you share the glb file?

Ooohh nice ^^ can't wait for this next update, and i think unreal crashed because i had not enought free ram when i tried.
It never crashed again when trying to load glb/glbf o:
(+ i see that every object have the right position on map o: i'm pretty hyped)

@Fr0zka Ok, now you can download the new version. It was deployed to itch.io.


Setting the weights of combined column not working

It is now impossible to set weights for combined columns - the dialogue only shows the content of the column. Setting the weights by changing the width is also difficult ¨dragable¨ area is too small.

Related to this issue - https://github.com/datavisyn/lineupjs/issues/54

current dev version:


\u2061 inserted in  when it shouldn't

When using an expression like \cos^2 KaTeX inserts the following MathML:
<msup>
  <mi>cos</mi>
  <mo></mo>
  <mn>2</mn>
</msup>

This <mo> tag cause invalid-markup to be displayed in Firefox since an <msup> tag may only contain two elements
KaTeX version: 0.10.0
Browser: Firefox Developer Edition 65.0b1

Sorry, I didn't notice this issue was related to #1800


404 page revision - Alpha

As a user that has reached a dead end or wrong page within the MET platform I would like to be notified so that I know I need to go to the original page I started out on. This way I will know that I have reached a dead end and can't reload the page.
In the style of the alpha site page: https://alpha.gov.bc.ca/gov/content/home/foo
The page you are looking for cannot be found.
The page you’re looking for might have been removed, moved, or is temporarily unavailable.
Suggestions to help you find what you’re looking for:
Check that the web URL has been entered correctly
Go to our homepage (instance homepage) and browse through our past and current engagements
Use the Search function at the top of this page
Telephone Device for the Deaf (TDD ) across B.C.: 711
If you would like to email us, please contact<EMAIL_ADDRESS>https://xd.adobe.com/view/30bd16a9-0635-4ee0-907b-ee3aab727fcc-65ee/screen/30e516f2-2fe2-41b1-8192-bdbffdb5c68a/
Attached SVG asset:

Please fix the below:

Suggestions to help you find what you’re looking for -- you missing in the code
Go to our homepage and browse through our past and current public engagements -- No public in the text provided in the ticket
Need to confirm on the image to be used in the 404 page.

CC: @djnunez-aot


NuGet.exe is missing

The build assumes that Nuget.exe is in path. It would be better to either include it in the repo or use dotnet restore

Run tools\razzle.cmd

I did. but it didn't work.
Now I looked into it again and itshould indeed set the path to the local nuget. but it doesn't work for me

@forki Can you echo %PATH% and validate whether \dep\nuget is in it?
Anyway, the nuget.exe is located in the directory \dep\nuget, you can use it directly.

@forki could you provide any more info as to why it doesn't work for you? As @wujysh said, there's a nuget.exe that's in the repo already, so tools\razzle.cmd should work correctly.

Also gonna drop a link to #489

This appears to have sorted itself out. Closing.


[feature request] matrix to transform and back

It would be nice to have methods that convert between a 4x4 matrix to a transform and back. Currently, there a lot of intermediate steps that need to be done to convert between the two.

Thank you for the suggestion! We will add these functions.

Hi @eric-heiden
I went through this issue and looking to contribute here
I was hoping if this is an priority task and I could take it up as my good-first-issue?
Lmk if there's something else I can work upon, thanks!

Hi @Irene-123,
Thank you for offering to contribute! This is indeed a good first issue you could help with! You can find our contributions guidelines here to get started.
Thanks,
Eric

Hi @eric-heiden Yes, I have joined the discord, will provide more updates over there to you


Synchronize with Franz 5.6.0

Description

This pull request aim at syncing with the upstream (Franz) latest release, v5.6.0-beta.1 (changelog).
Motivation and Context

For https://github.com/getferdi/ferdi/issues/1017.
Checklist:

[x] My pull request is properly named
[x] The changes respect the code style of the project ($ npm run lint)
[x] I tested/previewed my changes locally

I was facing the following issue:
kytwb@kytwbs-MacBook-Pro ferdi % npx lerna run prepare
lerna notice cli v3.19.0
lerna info versioning independent
lerna info Executing command in 3 packages: "npm run prepare"
lerna ERR! npm run prepare exited 2 in '@meetfranz/theme'
lerna ERR! npm run prepare stdout:

><EMAIL_ADDRESS>prepare /Users/kytwb/Projects/Ferdi/ferdi/packages/theme
> tsc

../../node_modules/@types/react-jss/index.d.ts(9,57): error TS7016: Could not find a declaration file for module 'theming'. '/Users/kytwb/Projects/Ferdi/ferdi/node_modules/theming/dist/cjs/index.js' implicitly has an 'any' type.
  Try `npm install @types/theming` if it exists or add a new declaration (.d.ts) file containing `declare module 'theming';`
../../node_modules/@types/react-jss/lib/injectSheet.d.ts(10,8): error TS7016: Could not find a declaration file for module 'theming'. '/Users/kytwb/Projects/Ferdi/ferdi/node_modules/theming/dist/cjs/index.js' implicitly has an 'any' type.
  Try `npm install @types/theming` if it exists or add a new declaration (.d.ts) file containing `declare module 'theming';`

lerna ERR! npm run prepare stderr:
npm ERR! code ELIFECYCLE
npm ERR! errno 2
npm ERR<EMAIL_ADDRESS>prepare: `tsc`
npm ERR! Exit status 2
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>prepare script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!      /Users/kytwb/.npm/_logs/2020-10-18T10_13_54_675Z-debug.log

lerna ERR! npm run prepare exited 2 in '@meetfranz/theme'

This was due to removing the lockfile in hope to regenerate it with npx lerna bootstrap.
Instead, I fixed the conflicts in package.json and re-ran npx lerna bootstrap, which auto-resolved the conflicts in the lockfile and successfully bootstrapped the project again:
kytwb@kytwbs-MacBook-Pro ferdi % npx lerna bootstrap
lerna notice cli v3.19.0
lerna info versioning independent
lerna info bootstrap root only
npm WARN conflict A git conflict was detected in package-lock.json. Attempting to auto-resolve.
npm WARN conflict To make this happen automatically on git rebase/merge, consider using the npm-merge-driver:
npm WARN conflict $ npx npm-merge-driver install -g
...
lerna success run Ran npm script 'prepare' in 3 packages in 18.1s:
lerna success - @meetfranz/forms
lerna success - @meetfranz/theme
lerna success - @meetfranz/ui

added 720 packages from 218 contributors, removed 529 packages, updated 438 packages and moved 49 packages in 145.106s

50 packages are looking for funding
  run `npm fund` for details

Personal checklist:

[ ] Not sure why we added "node-abi": "2.19.1" in package.json
[ ] Not sure why we switched from "cld3-asm" to "cld
"
[ ] Languages don’t all have translations in between parenthesis in language.js
[ ]

Make hibernation work with preferred hibernation timeout set in settings
[ ] Review context menu to add missing Franz entries (save image, go back, go forward, ...)
[ ] Review translations, I think I have lost some in the merge

I went with re-using Franz implementation for hibernation and spellchecking as to avoid double maintenance in the future.
To be continued.

Getting back to this soonish.

Are you still working on it?

Are you still working on it?

@proletarius101 yes.

I'm merging this to make it available to develop and following up in #1017


SSO credentials are not accepted as default

Description
Not clear if this is a bug or a feature request. It seems like a bug. If I defined SSO credentials as the default in my credentials file, the SDK fails to resolve them using the default resolve path. Current workaround is to generate temporary key/secret and add those to the credentials file manually or to re-write the code to explicitly look up the SSO credentials by profile name.
Reproduction Steps
Add your SSO credentials configuration to the [default] section of the credentials file.
Logs
N/A
Environment

SDK Version: <IP_ADDRESS>
OS Info: Windows 10
Build Environment Visual Studio
Targeted .NET Platform:  .NET 5.0

Resolution
Unknown what the resolution is. SSO credentials can be used if you explicitly send them to a service, but this breaks a lot of code that assumes there are default credentials configured. Understood that these calls will fail if you're not logged in. I don't believe it's important to kick off the login step, users who configure this way will be aware that they need to log into SSO in advance.

This is a :bug: bug-report

Hi @ryan-motive,
Thanks for reporting the issue. Could you please share the error message and stack trace, if any? I believe this is related to the existing issue https://github.com/aws/aws-sdk-net/issues/1853 where similar issue is reported. There is a workaround posted in https://github.com/aws/aws-sdk-net/issues/1853#issuecomment-863207180 which might help without requiring you to generate temporary credentials.
Thanks,
Ashish

The error is this, which I understand just means the credentials chain got to the end and wasn't able to find any it could use:
"Unable to get IAM security credentials from EC2 Instance Metadata Service"
Issue 1853 is similar, but the workaround is not viable because it would require me to rewrite all of the current code that expects defaults to take in configured credentials instead.

Default credential resolution fetches credentials which require no callback, for SSO this fails at https://github.com/aws/aws-sdk-net/blob/f33050e58133959457b66b95481257e4f17e67ce/sdk/src/Core/Amazon.Runtime/CredentialManagement/AWSCredentialsFactory.cs#L158. The credential resolution ultimately fails at last EC2 instance credential generator (https://github.com/aws/aws-sdk-net/blob/f33050e58133959457b66b95481257e4f17e67ce/sdk/src/Core/Amazon.Runtime/Credentials/FallbackCredentialsFactory.cs#L58).

Right - is this considered a bug or is this by design? It seems like this should work as long as I'm logged in and have fresh SSO credentials. Otherwise the only workaround is to hand-patch the credentials file every time I run.

@ryan-motive I will discuss this with team and update here accordingly.

Thank you!

Otherwise the only workaround is to hand-patch the credentials file every time I run.

Alternative workaround is using yawsso, it'll help with the hand patching part at least.


SolidJS Array Field Not Working

Describe the bug
I have tried to follow the example given in the docs (link) as closely as possible, but with no luck. Adding a new field works, but typing in it results in the field disappearing. Also, typescript is not happy with type checking of the index prop and when calling the handleChange function.
Your minimal, reproducible example
https://stackblitz.com/edit/solid-vite-fpsaqi?file=src%2Findex.tsx
Steps to reproduce

Click the 'Add name' button
Start typing in the field

Expected behavior
As a user I expected the be able to type into the array field.
How often does this bug happen?
Every time
Screenshots or Videos
No response
Platform

OS: Windows/WSL2
Browser: Chrome
Version: 120

Tanstack Form adapter
solid-form
TanStack Form version
0.13.3
TypeScript version
5.3.3
Additional context
No response

While investigating array bugs in #588, I noticed the same behavior until I switched from For to Index, which seems to also solve your issue:
https://stackblitz.com/edit/solid-vite-zwjafu?file=src%2Findex.tsx

I see, thanks. I checked out the Stackblitz playground you provided and it works for the most part, however, clicking on the X button still doesn't work. i is now just a number, so I changed namesField().removeValue(i()) to namesField().removeValue(i) but even then clicking the X button removes all of the array fields.

Likely a simple fix on our end. Let's open a new issue to track that :)

Created a new issue: https://github.com/TanStack/form/issues/618


add contributing and code of conduct guides

Added contributing and code of conduct pages, keeping it pretty simple
For contributors, should adding tests be a requierment?
Enabled 'Issues' option for repository

@amritagupta Are you able to take a look at these changes and confirm that it makes sense to you? Thanks!

Another addition that would be useful if possible is how specifically contributors can help with the project. Something like a task list for future improvements and we classify each as suitable for either first-timers, intermediate, experts etc. If we don't have clear ideas for future improvements then no problem!

Looks good to me! RE: future improvements task list, that sounds like an awesome addition but could be in a future PR as it becomes clearer what's needed?


Edit track expense

Details

Fixed Issues

$ https://github.com/Expensify/App/issues/38699
Tests

Go to any track expense transaction report.
Try to edit any fields there, which is possible to edit.

[x] Verify that no errors appear in the JS console

Offline tests

Same as Tests
QA Steps

Same as Tests
PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

Android: mWeb Chrome
https://github.com/Expensify/App/assets/58412969/46433726-b38b-409d-bdf6-2be15543b7d2

iOS: Native
https://github.com/Expensify/App/assets/58412969/d8dc88e8-5af4-4ba2-9674-a75701ab8435

iOS: mWeb Safari
https://github.com/Expensify/App/assets/58412969/09003b56-9205-4482-a8c2-63e8ed0b1c37

MacOS: Chrome / Safari
https://github.com/Expensify/App/assets/58412969/dcde2184-4672-45c0-9ce3-e3ffd2572320
https://github.com/Expensify/App/assets/58412969/782c1bf2-0894-43a7-adfe-ea7e517f4d55

MacOS: Desktop
https://github.com/Expensify/App/assets/58412969/8852791a-9fd1-4e3c-85fa-b312313ec517

Are we holding on anything else here? Could we merge main / get this into review?

Reviewer Checklist

[ ] I have verified the author checklist is complete (all boxes are checked off).
[ ] I verified the correct issue is linked in the ### Fixed Issues section above
[ ] I verified testing steps are clear and they cover the changes made in this PR

[ ] I verified the steps for local testing are in the Tests section
[ ] I verified the steps for Staging and/or Production testing are in the QA steps section
[ ] I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[ ] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[ ] I checked that screenshots or videos are included for tests on all platforms
[ ] I included screenshots or videos for tests on all platforms
[ ] I verified tests pass on all platforms & I tested again on:

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

[ ] If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
[ ] I verified proper code patterns were followed (see Reviewing the code)

[ ] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
[ ] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[ ] I verified that comments were added to code that is not self explanatory
[ ] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[ ] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
[ ] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[ ] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[ ] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[ ] I verified the JSDocs style guidelines (in STYLE.md) were followed

[ ] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[ ] I verified that this PR follows the guidelines as stated in the Review Guidelines
[ ] I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
[ ] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[ ] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[ ] If a new component is created I verified that:

[ ] A similar component doesn't exist in the codebase
[ ] All props are defined accurately and each prop has a /** comment above it */
[ ] The file is named correctly
[ ] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[ ] The only data being stored in the state is data necessary for rendering and nothing else
[ ] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[ ] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[ ] All JSX used for rendering exists in the render method
[ ] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[ ] If any new file was added I verified that:

[ ] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[ ] If a new CSS style is added I verified that:

[ ] A similar style doesn't already exist
[ ] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)

[ ] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[ ] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[ ] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[ ] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[ ] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[ ] I verified that all the inputs inside a form are aligned with each other.
[ ] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[ ] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[ ] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[ ] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

BUG There's a reload whenever the description is changed.
https://github.com/Expensify/App/assets/30054992/f4d30512-05c1-4b4d-96fc-8f7504e566e8

@shubham1206agra Can you merge main please if you haven't already?

Notice the position of the Save button. I'm sure we fixed it yesterday.

My bad 🙉

Hm... I have to go out for a couple of hours. I'll check this then if still unresolved.

@shubham1206agra Did the reload issue get fixed?

On it. Should be dine in an hour or so.

@shubham1206agra Can you resolve conflicts?

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by https://github.com/thienlnam in version: 1.4.65-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/mountiny in version: 1.4.65-5 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


InvalidCastException PropertyExpression -> LambdaExpression

I am using the following code:

        public static Func<T1, bool> StatusOffen
        {
            get { return d => d.status < 400; }
        }
        public void Test()
        {
                Expression<Func<T1, bool>> expr1 = a => Item.StatusOffen(a);
                Expression<Func<T1, bool>> expr2 = a => Item.StatusBearbeitbar(a);
                Expression<Func<T1, bool>> expr3 = a => Item.StatusKeinVersand(a);
                var predicate = PredicateBuilder.False<T1>();
                predicate = predicate.Or(expr1);
                predicate = predicate.Or(expr2);
                predicate = predicate.Or(expr3);

                ////predicate = predicate.Or(a => a.status < 400);
                ////predicate = predicate.Or(a => a.status == 850);
                ////predicate = predicate.Or(a => a.status == 400);

                IQueryable<T1> query1 = this.GetByFilterObjectInternal(entities);
                query1 = query1.AsExpandable().Where(predicate);
                ....
        }

On calling the where statement I get the invalid cast Exception. If I use the commented variant instead all runs well.
So what should I do to use the funcs?
Best regards freica

this already has a solution in here
but I don't know why still it's not fixed in the source code.
@scottksmith95 do you have any plan to add support for method and property exressions?

I actually forked this repo to apply fix from that SO thread only to find  that it's actually already fixed and works fine. It doesn't work in OPs scenario because the property invoked should return Expression<Func<...>>, not just Func<...>.

I encountered the same issue.
Has anyone actually filled a pull request to fix this? I'll look around if the issue is actually identical and will file a PR to close this issue.

Seems I cannot reproduce my issue which resembles the provided code.. but with Expression<Func<..>> instead of simply Func<>.


[Feature Request] Checkpoints/expression removal/incremental rewriting

It'd be really nice to support incremental rewrites of some sort, then egg could function as a library underlying a more complex incremental solver
I'm thinking something along these lines
let mut graph = ...;

let expr_id = graph.add(some_expr);
// ...do some things with the egraph

// Undo everything that dealt with the given enode
graph.remove(expr_id);

I know this is much easier said than done given the deduplicating nature of the egraph, but it's a neat idea none the less

What are the semantics of remove? I'm not clear from the givne example.
Would an SMT-style, push and pop meet your needs?
(also, converted from issue to discussion, as this is a ways out)


I want to add a python project which will encode or decode the message.

I want to add a python project(cipher) which will decode or encode the text message by displacing the positions of the alphabets.

Hello, Can you please assign this issue to me?
Thanks in advance :)

Hello sir, please assign this issue to me as i already worked on it in past.

Hey I developed my own algorithm using ceaser cifer technique in python I wanted to add it into this issue please assign me so that I can make contribution. Thanks

Hello, I'm very much interested in it. I have done the same using Huffmann encode and decode.. it even compresses the message. Kindly assign it to me!


is using  infinigen to create complex scene for game development right scenario？

can i use this tool create a game scene and import to unity as asset. and can i use  this scene mesh as base for game development?

that means for now, this project is currently only suitable for generating 3D images and videos, right?


No git link on dockerhub page + no :latest tag

Hey Gary
Good effort with this image :)
Couple of pointers

there is no link to the git on the dockerhub page, had to google it
The latest image doesnt have a :latest tag so docker fails to pull without specifying :1.0.08

Hey James, first off thanks so much for the feedback this is super awesome and useful!

I've thrown my github repo link everywhere :)
I've also added a latest tag

Lovely stuff, cheers my man


Authenticated User Functionality with CafeX LiveAssist

Hey there, I've got CafeX LiveAssist up and running smoothly for Live Chat and co-browse, both working smoothly with XRM Portals. I'm now trying to add the "Contact Pop" functionality (which opens the contact record if the User is logged into the Portal), and am following the instructions on this page: https://www.liveassistfor365.com/en/support/authenticated-visitors-in-the-dynamics-customer-portal/
When I get to the step where I need to retrieve the Public Key using the following instruction, I get a Key Not Found error. Makes sense I haven't done anything to provide a key, though one is configured/provided when using the Cloud-based Dynamics Portals.

To fetch the JWT Public Key, open a separate browser, and navigate to [Customer Portal Base URL]/_services/auth/publickey (e.g. https://cafex02.microsoftcrmportals.com/_services/auth/publickey).

Our portal is hosted as an Azure App Service Web App, and I was hoping to get some clarity on the steps to follow in order to get a Certificate in place and be able to use the Portal's authenticated user in CafeX. Googling has only resulted in scenarios where people are adding certificates in order to use a custom domain name, where we're looking at a different purpose.

I am closing this issue due to inactivity, people may still add comments to the closed issue if they have any assistance to contribute.


onDismissRequest is called twice when bottom sheet is dismissed by swiping down

Hi, I really like you library and I'm trying to integrate it with my own Compose Navigation lib. I've noticed that swiping down causes the current BottomSheetDialog to call onDismissRequest twice, which breaks some logic for me. In all other cases this callback is always called once.
Could you maybe fix this issue and make it be called only once on swipe down? The current behaviour is very much unexpected and error-prone.

@olshevski There was some reason to add it. I'll check it again and resolve issue with #2

@olshevski BottomSheeetDialog (View) has own logic to cancel. I tried to handle animation and cancel logic both, however, it called onDismissRequest twice unintentionally.
I resolved this issue with new feature dismissWithAnimation property 🎉 which is handling animation and cancel logic both properly.

@olshevski  Version 1.0.2 is published(or ongoing). I hope this new version can resolve your issue.

Working great, thank you!


Accesing relationship properties of neo4j

I am building an application using ruby on rails and neo4j as database. I am finding it difficult to access the properties of a ActiveRel class object.
If i query this: p.tagged_creatives.first.rel where p is an object of Project class and tagged_creatives is the relation from Project class to Creative class.
The relationship was created as :
p.tagged_creatives << c

where c is an object of Creative class
Additional information which could be helpful if relevent to your issue:
Code example (inline, gist, or repo)
class HasProjectTag
  include Neo4j::ActiveRel
  from_class :Project
  to_class :any

  type 'TagStatus'

  # property :status, type: Integer
  enum status: [ :tentative, :confirm, :remove, :reject ]
end

 CYPHER 51ms MATCH (n), (n)-[r]-(p) WHERE (ID(n) = {ID_n}) RETURN r as result LIMIT 2 | {:ID_n=>78}
ArgumentError: wrong number of arguments (given 0, expected 2..3)
	from /home/vijeta/.rvm/gems/ruby-2.3.0/gems/neo4j-core-6.1.4/lib/neo4j-server/cypher_node.rb:176:in `match'
	from /home/vijeta/.rvm/gems/ruby-2.3.0/gems/neo4j-core-6.1.4/lib/neo4j-server/cypher_node.rb:211:in `ensure_single_relationship'
	from /home/vijeta/.rvm/gems/ruby-2.3.0/gems/neo4j-core-6.1.4/lib/neo4j-server/cypher_node.rb:156:in `rel'
	from (irb):9
	from /home/vijeta/.rvm/gems/ruby-2.3.0/gems/railties-5.0.0/lib/rails/commands/console.rb:65:in `start'
	from /home/vijeta/.rvm/gems/ruby-2.3.0/gems/railties-5.0.0/lib/rails/commands/console_helper.rb:9:in `start'
	from /home/vijeta/.rvm/gems/ruby-2.3.0/gems/railties-5.0.0/lib/rails/commands/commands_tasks.rb:78:in `console'
	from /home/vijeta/.rvm/gems/ruby-2.3.0/gems/railties-5.0.0/lib/rails/commands/commands_tasks.rb:49:in `run_command!'
	from /home/vijeta/.rvm/gems/ruby-2.3.0/gems/railties-5.0.0/lib/rails/commands.rb:18:in `<top (required)>'
	from bin/rails:4:in `require'
	from bin/rails:4:in `<main>'

Runtime information:
Neo4j database version:
neo4j gem version:
neo4j-core gem version:

I don't think I understand the question, but a few things that might help:
You can create an ActiveRel object by doing:
HasProjectTag.create(project, other, status: :tentative)

Or you could do:
project.tags.create(other, status: :tentative)

Also, I'd suggest that, as much as possible, you make your ActiveRel classes the same as the type.  That way you don't need to specify the type and it's less confusing to figure out how ActiveRel classes match to Neo4j relationships, like:
class TagStatus
  include Neo4j::ActiveRel
  from_class :Project
  to_class :any

  enum status: [ :tentative, :confirm, :remove, :reject ]
end


ubuntu 下 aos make helloworld@linuxhost -c config 出现 recipe for target '.config' failed 编译不过

ubuntu
aos make helloworld@linuxhost -c config
出现很多  ignoring unsupported character
然后就 build/build_rules/aos_kconfig.mk:139: recipe for target '.config' failed
如何解决？是不是我环境有什么东西没有安装？
'est/yunit/Config.in:1:warning: ignoring unsupported character '
'est/yunit/Config.in:2:warning: ignoring unsupported character '
'est/yunit/Config.in:3:warning: ignoring unsupported character '
'est/yunit/Config.in:4:warning: ignoring unsupported character '
'est/yunit/Config.in:4:warning: ignoring unsupported character '
'est/Config.in:6:warning: ignoring unsupported character '
build/build_rules/aos_kconfig.mk:139: recipe for target '.config' failed
make: *** [.config] Error 1
[AliOS-Things] ERROR: "/media/share/AliOS-Things/build/cmd/linux64/make" returned error code 2.
[AliOS-Things] ERROR: Command "/media/share/AliOS-Things/build/cmd/linux64/make HOST_OS=Linux64 TOOLS_ROOT=/media/share/AliOS-Things/build -e -f build/Makefile<EMAIL_ADDRESS>in "/media/share/AliOS-Things"

When using git, you need to set use LFS, because the git automatically changed the line end to CRLF for windows.

When using git, you need to set use LFS, because the git automatically changed the line end to CRLF for windows.
thank

我也出现这个问题了，请问如何处理呢？

我也出现这个问题了，请问如何处理呢？

Depends on which git are you using, delete the repository, clone again with the option "Use Git LFS" selected. Use TortoiseGit, you can see the check box when trying to clone.
Basically you are using Windows and the git default setting will convert all the line ends into CRLF, which causes your problem.


Validation of the annotation service

The submitted service itself needs to be validated.

Get if root is redirected to service endpoint
check if service object is same as this schema: https://github.com/nlpsandbox/nlpsandbox-schemas/blob/develop/json-schema/schemas/service.json
check if POST call works per annotator

This can probably be done in the same way as #32

Yes


Tailnet Keys

Is your feature request related to a problem? Please describe.
The Tailscale API now includes the ability to manage tailnet keys. This should be a resource in the provider
Describe the solution you'd like
A resource like tailscale_tailnet_key with the following fields:
resource "tailscale_tailnet_key" "example_key" {
  capabilities: {
    devices: {
      create: {
        reusable: true,
        ephemeral: false,
      }
    }
  }
}

It should then export the key which can be used with other provides, like vault etc.
Additional context
https://github.com/tailscale/tailscale/blob/main/api.md#keys

Decided to go with this format for now:
resource "tailscale_tailnet_key" "sample_key" {
  reusable = true
  ephemeral = false
}


Added new EdgeKind: ref/file [phab:D1650]

Created by craigbarber at 2017-05-17 22:49:28:
Added new EdgeKind: ref/file to the schema. This is necessary for indexers, such as the bazel indexer, which have anchors referencing files directly.

zarko commented inline (context lost during migration) at 2017-05-17 22:56:21:
Add:
This is distinct from <<refincludes,[ref/includes]>>, which indicates that the anchor causes the contents of `F` to be inserted into the surrounding file. *ref/file* should be used when the anchor refers explicitly to the identity of `F`, as in a hardcoded path in a test or build script.

craigbarber wrote at 2017-05-18 17:25:01:

Incorporated review feedback

zarko accepted this revision at 2017-05-18 19:51:58

craigbarber closed via commit 4b107f7bfd8ebb8334ae6a74a5fcf382f182ef7e at 2017-05-18 20:06:08


Bluetooth: shell: audio: Extend vcs init with opt params

Extend the vcs init command with optional parameters to set the
initial VCS state including volume level, mute state and step size.
This is needed to pass qualification test cases listed below:
VCS/SR/CP/BV-01-C,
VCS/SR/CP/BV-02-C,
VCS/SR/CP/BV-02-C,
VCS/SR/CP/BV-04-C
Signed-off-by: Mariusz Skamra<EMAIL_ADDRESS>

Didn't realize that we are using the shell for PTS tests :)

Why not?

Didn't realize that we are using the shell for PTS tests :)

Why not?

I just didn't know that :D
But it's good to know, since that would also indicate that we need to make sure that the shell modules are complete in terms of what the API offers in the future.
Are we using the shell modules for the GAP and GATT tests too?

I just didn't know that :D
But it's good to know, since that would also indicate that we need to make sure that the shell modules are complete in terms of what the API offers in the future.
Are we using the shell modules for the GAP and GATT tests too?

Shell can be used for GATT/GAP tests as well if one wish, but generally we use bluetooth/tester application instead because it's just faster to use automation

I just didn't know that :D
But it's good to know, since that would also indicate that we need to make sure that the shell modules are complete in terms of what the API offers in the future.
Are we using the shell modules for the GAP and GATT tests too?

Shell can be used for GATT/GAP tests as well if one wish, but generally we use bluetooth/tester application instead because it's just faster to use automation

Alright, so ideally we'd also use a tester application for VCS at some point?

Alright, so ideally we'd also use a tester application for VCS at some point?

That would be nice. It probably requires extending BTP (binary protocol that instructs IUT) with some VCS specific commands, and some work in AutoPTS.

Alright, so ideally we'd also use a tester application for VCS at some point?

That would be nice. It probably requires extending BTP (binary protocol that instructs IUT) with some VCS specific commands, and some work in AutoPTS.

Maybe preparing LE Audio for AutoPTS should be an item on the next F2F :)


fix: Eliminated the possible inclusion of non-ascii characters in the…

Addresses #1934
Summary
The problem arises because HTTP headers cannot include non-ascii characters. convertAjvErrors produces the final error text, which is then passed into sl-violations header.
I removed the ability to view regular expression patterns. (this is exactly what they are complaining about in issue)
Also, I disabled the ability to view allowed values. Our project uses enum with Russian characters, like this:

metering_device_model_execution:
type:        string
description: Исполнение
example:     электронный
enum:
- электронный
- индукционный
- комбинированный
- модульный

If there is a mismatch, the contents of the enum are added to the sl-violations error text.
Enum stores part of the business logic, and getting rid of them is impossible if the base language is not English.
Checklist

The basics

[X] I tested these changes manually in my local or dev environment

Tests

[ ] Added or updated
[X] N/A

Event Tracking

[ ] I added event tracking and followed the event tracking guidelines
[X] N/A

Error Reporting

[ ] I reported errors and followed the error reporting guidelines
[X] N/A

Failed to run tests

It's probably something to do with the system or something else. Because, even without making changes, the tests did not run with this error:
  PS C:\Users\Offlu\OneDrive\Документы\GitHub_Projects\prism> yarn test
yarn run v1.22.19
$ node --expose-gc ./node_modules/.bin/jest
C:\Users\Offlu\OneDrive\Документы\GitHub_Projects\prism\node_modules\.bin\jest:2
basedir=$(dirname "$(echo "$0" | sed -e 's,\\,/,g')")
^^^^^^^
SyntaxError: missing ) after argument list
    at Object.compileFunction (node:vm:360:18)
    at wrapSafe (node:internal/modules/cjs/loader:1055:15)
    at Module._compile (node:internal/modules/cjs/loader:1090:27)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1180:10)
    at Module.load (node:internal/modules/cjs/loader:1004:32)
    at Function.Module._load (node:internal/modules/cjs/loader:839:12)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12)
    at node:internal/main/run_main_module:17:47
error Command failed with exit code 1.

I would be grateful if you could help me figure this out.

@Lingihn thank you for this PR! However, we'd prefer to see this issue solved by MIME encoding, preferably UTF-8, the sl-violations header instead of stripping this from the header altogether. This is in accordance with Http spec.
From that link above:

When it is necessary for a field value to convey non-ASCII content, a Byte Sequence (Section 3.3.5) can be specified, along with a character encoding (preferably UTF-8 [STD63]).

We'd also like to see new or updated tests covering any new changes.

We're going to close this PR since we haven't heard from you in a month. Please re-open if you want to address our PR comments.


Allow candidate exchange via REST+SSE

Closes https://github.com/FAForever/faf-icebreaker/issues/19

How can I help with testing these changes?

@Garanas You cannot yet. There is no matching client implementation so far.


added tags

@exercism/reviewers - Ho!

....but we've got some checks failing (as I am sure you know). Empathy.

Ah, yes. Figured I'd knock out a couple easy ones before braving the actual track setup.


VST3+Cubase 14 mono tracks are not working properly

Tested with Windows 10, Cubase 14, CLAP 1.2.2, latest clap-wrapper, and clap-c99-distortion.
When using a VST3 on mono tracks in Cubase 14, the process() function, which is usually called, is instead replaced by calls to flush(), causing the plugin to malfunction.
As long as the track remains mono, process() is never called, and flush() is called instead. However, when switching the track to stereo, process() is called as expected, and everything works normally.
In Cubase 13, process() was called correctly even on mono tracks, but crashed at const float in_r = process->audio_inputs[0].data32[1][i];. (Can't verify now as Cubase 13 trial expired)

Separate question: The current clap-c99-distortion plugin crashes or throws errors when used on mono tracks in Cubase or Studio One. I’m not sure how to prevent these crashes or errors with minimal changes.
For now, I’m using this method, but it’s clear that something is wrong. Based on my research, I focused on the fact that valid pointers seem to fall within the 0xFFFFFFFFF address range:
@@ clap-c99-distortion.c @@
-	389	const float in_r = process->audio_inputs[0].data32[1][i];
+	389	const float in_r = reinterpret_cast<uintptr_t>(process->audio_inputs[0].data32[1]) <= 0xFFFFFFFFF ? process->audio_inputs[0].data32[1][i] : 0.0f;
-	430	process->audio_outputs[0].data32[1][i] = out_r;
+	430	reinterpret_cast<uintptr_t>(process->audio_outputs[0].data32[1]) <= 0xFFFFFFFFF ? process->audio_outputs[0].data32[1][i] = out_r;

When I tried to test this newly created code in Cubase 14, I found this bug. So, I haven’t been able to run this code yet, but I feel like there’s something wrong with this approach as well:
@@ clap-c99-distortion.c @@
-	389	const float in_r = process->audio_inputs[0].data32[1][i];
+	389	const float in_r = process->audio_inputs_count >= 2 ? process->audio_inputs[0].data32[1][i] : 0.0f;
-	430	process->audio_outputs[0].data32[1][i] = out_r;
+	430	process->audio_inputs_count >= 2 ? process->audio_outputs[0].data32[1][i] = out_r;

I think there’s probably something like process->audio_inputs[0].data32_count somewhere, but I couldn’t find it.
P.S.
I just had a thought and when I looked into it again, I found process->audio_inputs[0].channel_count. This is probably the correct answer, right?:
@@ clap-c99-distortion.c @@
-	389	const float in_r = process->audio_inputs[0].data32[1][i];
+	389	const float in_r = process->audio_inputs[0].channel_count >= 2 ? process->audio_inputs[0].data32[1][i] : 0.0f;
-	430	process->audio_outputs[0].data32[1][i] = out_r;
+	430	process->audio_outputs[0].channel_count >= 2 ? process->audio_outputs[0].data32[1][i] = out_r;

So the c99 distortion advertises a stereo audio port only. It shouldn’t be loadable on a mono track.
I wonder if the wrapper is mis representing the bus configuration in this case.

Cubase allows loading and using plugins regardless of whether tracks or plugins are stereo or mono. When using stereo plugins on mono tracks, most plugins seem to handle this by interpreting only the left channel input (with the right channel being silent), processing internally in stereo as usual, and outputting only the left channel.
When loading clap-c99-distortion through clap-wrapper on mono tracks in Cubase 13, it worked normally except for crashes at const float in_r = process->audio_inputs[0].data32[1][i]; and process->audio_outputs[0].data32[1][i] = out_r;. The crashes were caused by pointers referencing invalid addresses, so I used a custom method to detect valid pointers to prevent crashes. This method was quite tricky but worked fine 99% of the time (false detections only occurred when loading Windows-original CLAP in Bitwig on Linux using yabridge).
Since Cubase and Studio One allow switching between stereo and mono tracks with one click, even if users are notified that certain plugins can't be used on mono tracks, accidental clicks could crash the DAW, so I needed to address this issue. However, yesterday I found process->audio_inputs[0].channel_count and process->audio_outputs[0].channel_count, which seem to have been created to handle this problem, so I feel this issue has been resolved.
However, the situation changed completely with Cubase 14's release. It seems the VST3 specifications or program has changed, and when using clap-c99-distortion through clap-wrapper on mono tracks, the plugin's process() is no longer called at all, and instead flush() is called for each buffer size.
I don't understand why this is happening - whether it's a Cubase 14 bug, if it's because I'm not using the code prepared for mono tracks in clap-c99-distortion (perhaps CLAP_PORT_MONO needs to be set somewhere?), if it's a clap-wrapper bug, or if the apparently normal operation in Cubase 13 itself was due to a bug.
Since I'm not very familiar with C, VST3, or CLAP, I might be missing something critical.

it is probably that way because clap requires you to hand you the format you ask for. And I bet the wrapper just downgrades to not calling process on an mis-configured track. Correctly, I think!
I think the idea of "my plugin requires stereo and you just hand it mono and a null anyway" is a DAW bug indeed. But who knows what's buried in the vst3 spec. I suppose we could make the wrapper on a mono track to a stereo in plugin copy the mono to stereo and return stereo out.
@defiantnerd you have cubase. Any thoughts here?

After various experiments, when I set info->channel_count = 1; and info->port_type = CLAP_PORT_MONO; in c99dist_audio_ports_get, it started working with mono tracks in Cubase 14. This suggests that it wasn't a bug in clap-wrapper, but rather that I hadn't properly configured CLAP's mono compatibility settings, and there was a bug in Cubase 13 that made it work in conditions where it shouldn't have.
It seems the problem could be solved by getting information from the host about whether the track is stereo or mono, and then adding conditional branching in c99dist_audio_ports_get based on the track's state, but I don't know how to receive this information from the host. I think the code would look something like this:
static bool c99dist_audio_ports_get(const clap_plugin_t *plugin, uint32_t index, bool is_input,
                                    clap_audio_port_info_t *info)
{
    clap_c99_distortion_plug *plug = plugin->plugin_data;
    //Branching based on audio port information obtained from another location
    if (plug->is_mono) {
        if (index > 0)
            return false;
        info->id = 0;
        if (is_input)
            snprintf(info->name, sizeof(info->name), "%s", "Mono In");
        else
            snprintf(info->name, sizeof(info->name), "%s", "Distorted Output");
        info->channel_count = 1;
        info->flags = CLAP_AUDIO_PORT_IS_MAIN;
        info->port_type = CLAP_PORT_MONO;
        info->in_place_pair = CLAP_INVALID_ID;
    } else {
        if (index > 0)
            return false;
        info->id = 0;
        if (is_input)
            snprintf(info->name, sizeof(info->name), "%s", "Stereo In");
        else
            snprintf(info->name, sizeof(info->name), "%s", "Distorted Output");
        info->channel_count = 2;
        info->flags = CLAP_AUDIO_PORT_IS_MAIN;
        info->port_type = CLAP_PORT_STEREO;
        info->in_place_pair = CLAP_INVALID_ID;
    }
    return true;
}

The clap protocol doesn’t work that way. If you only advertise one audio port configuration the host has to give you that.
To do what you share here you would need to implement one of the audio multi config options which would allow you to share different shapes. C99distortion doesn’t do that and really shouldn’t be creatabnle on a mono track with correct hosting.

Is audio-ports-config.h needed to implement audio multi config options?
If so, I believe CLAP-wrapper hasn't implemented this feature yet? (I searched the code for CLAP_EXT_AUDIO_PORTS_CONFIG and clap_plugin_audio_ports_config_t but found no matches)
Does this mean the current clap-wrapper cannot simultaneously support both stereo and mono configurations?
I understand this kind of code is probably needed but I'm not sure what's missing...:
uint32_t c99dist_audio_ports_config_count(const clap_plugin_t *plugin) { return 2; }

bool c99dist_audio_ports_config_get(const clap_plugin_t *plugin,
                                    uint32_t index,
                                    clap_audio_ports_config_t *config)
{
    switch (index)
    {
    case 0:
        config->id = 0;
        snprintf(config->name, sizeof(config->name), "%s", "Stereo");
        config->input_port_count = 2;
        config->output_port_count = 2;
        config->has_main_input = true;
        config->main_input_channel_count = 2;
        config->main_input_port_type = CLAP_PORT_STEREO;
        config->has_main_output = true;
        config->main_output_channel_count = 2;
        config->main_output_port_type = CLAP_PORT_STEREO;
        return true;
    case 1:
        config->id = 1;
        snprintf(config->name, sizeof(config->name), "%s", "Mono");
        config->input_port_count = 1;
        config->output_port_count = 1;
        config->has_main_input = true;
        config->main_input_channel_count = 1;
        config->main_input_port_type = CLAP_PORT_MONO;
        config->has_main_output = true;
        config->main_output_channel_count = 1;
        config->main_output_port_type = CLAP_PORT_MONO;
        return true;
    default:
        return false;
    }
}

bool c99dist_audio_ports_config_select(const clap_plugin_t *plugin, clap_id config_id)
{
    switch (config_id)
    {
    case 0:
        return true;
    case 1:
        return true;
    default:
        return false;
    }
}

const clap_plugin_audio_ports_config_t s_c99dist_audio_ports_config = {
    .count  = c99dist_audio_ports_config_count,
    .get = c99dist_audio_ports_config_get,
    .select = c99dist_audio_ports_config_select
};

I know @defiantnerd has done a bunch of work on this. There's audio-ports-config and configurable-audio ports and I am not sure which one is the one.
But yes, something like that would be required.
Timo?
Also: Happy new year!

I see. Happy New Year to you too!


Exception when mixing Attributes and StoreOptions for Schema

Marten v3.13.2, .NET Core v3.1, XUnit v2.4.0
I have most of my Schema Mappings via Attributes on Data Models, but couldn't find a way to define SubClass mapping via attributes. So, as a compromise I tried to define that via MartenRegistry/StoreOptions and got the following error when I did that:
  Error Message:
   System.TypeInitializationException : The type initializer for 'Data.Tests.TestSessionFactory' threw an exception.
---- System.InvalidOperationException : Sequence contains no elements
  Stack Trace:
     at Data.Tests.TestSessionFactory..ctor()
   at Data.Tests.ParentModelTests..ctor() in /Users/zzz/code/yyy/Data.Tests/ParentModelTests.cs:line 17
----- Inner Stack Trace -----
   at System.Linq.ThrowHelper.ThrowNoElementsException()
   at System.Linq.Enumerable.Single[TSource](IEnumerable`1 source)
   at Marten.Schema.UniqueIndexAttribute.Modify(DocumentMapping mapping, MemberInfo member)
   at Marten.Schema.DocumentMapping.<>c__DisplayClass27_0.<applyAnyMartenAttributes>b__9(MartenAttribute att)
   at Baseline.Reflection.ReflectionExtensions.ForAttribute[T](MemberInfo provider, Action`1 action)
   at Marten.Schema.DocumentMapping.<applyAnyMartenAttributes>b__27_2(PropertyInfo prop)
   at Baseline.GenericEnumerableExtensions.Each[T](IEnumerable`1 values, Action`1 eachAction)
   at Marten.Schema.DocumentMapping.applyAnyMartenAttributes(Type documentType)
   at Marten.Schema.DocumentMapping..ctor(Type documentType, StoreOptions storeOptions)
   at Marten.Schema.SubClassMapping..ctor(Type documentType, DocumentMapping parent, StoreOptions storeOptions, String alias)
   at Marten.Schema.DocumentMapping.AddSubClass(Type subclassType, String alias)
   at Marten.MartenRegistry.DocumentMappingExpression`1.<>c__DisplayClass28_0.<AddSubClass>b__0(DocumentMapping`1 mapping)
   at Marten.MartenRegistry.DocumentMappingExpression`1.<>c__DisplayClass26_0.<set_alter>b__0(StoreOptions o)
   at Marten.MartenRegistry.Apply(StoreOptions options)
   at Marten.StoreOptions.ApplyConfiguration()
   at Marten.DocumentStore..ctor(StoreOptions options)
   at Marten.DocumentStore.For(Action`1 configure)
   at Data.Tests.TestSessionFactory..cctor() in /Users/zzz/code/yyy/Data.Tests/TestSessionFactory.cs:line 12

To troubleshoot, I removed the UniqueIndex mapping attribute and added it alongside the SubClass mapping on StoreOptions and the exception went away and my tests passed.
Is there anything I am missing? Or is it not advisable to mix and match Schema mapping and I shall pick one approach and stick to it?
Alternatively, can I define SubClass mapping via Attributes? Because that would be my preferred method.
Thanks.

@ParthaBoocha It would help if you could provide us a repro code or add a failing unit test for us to check.

marten.zip
Thanks @mysticmind . The attached zip file has the stripped down code to recreate the exception. Simply run dotnet test Data.Tests/Data.Tests.csproj
To fix exception:

Comment line # 12 in Models/User.cs file
Uncomment line # 23 in Bootstrapper.cs file

@ParthaBoocha Thanks you, will check and keep you posted.

@ParthaBoocha I have identified the issue and it is bug, we will fix it soon. In the interim, use the fluent interface when you want to add unique index on a sub-classed doc.

I don't think this is an issue any longer and there's no recent activity.


Publication date validation should consider month and day, not just year

Publication dates that occur later in the current year are validating when they shouldn't

@amyehodge is this the same as #373?

ran into this while working on #560 and was filing an issue, then realized it was a dupe of this one.
a bit more detail for whoever picks this up:  i noticed that the validation seemed to be happening on the server-side, and an error was sent back when i tried to deposit, it just didn't get presented to me in the UI (per the screenshot in the description).
e.g.:


N1QL support (improved version)

This PR builds on top of what @andrestaht started in #1279
Added required documentation and made the auto-detections tests pass.
Tuned the definition in several ways:

Increase relevance of INFER, UPSERT, MISSING and backquoted identifiers.
Remove support for -- and  $ comments
Highlight backquoted-strings as symbols - they really are identifiers not strings.

Merged. Sorry for the long wait [insert standard busy maintainer apology]. Thanks for the contribution!


Get rid of cacheHash

Description
Symfony usually uses the APP_ENV to construct the cache path like e.g. var/cache/dev/. Shopware added a cacheId, which results in paths like var/cache/dev_h52f02c65f249e550e4ba5c77eb3625ab.
This path is unpredictable, because it's randomly generated.
For most users this may not be a problem, but you can't use e.g.  opcache preload (PHP 7.4) easily with this approach.
https://symfony.com/blog/new-in-symfony-4-4-preloading-symfony-applications-in-php-7-4
; php.ini
opcache.preload=/path/to/project/var/cache/prod/App_KernelProdContainer.preload.php

You can only specify the path to one file. Therefore the path must be predictable.
I'm not quite sure why this additional random cacheId was introduced, but it seems to be only changed during the HTTP-Cache warmup. Therefore I suggest, that separating the HTTP cache from the regular Symfony cache would solve this issue.

hey @hhoechtl
we are aware of that. There is also a ticket for that issue: https://issues.shopware.com/issues/NEXT-6104
The reason for the "random" string is that the DI container must be build new, once a plugin is activated/deactivated

In between you can override the getCacheHash method:
https://github.com/shopware/core/blob/master/Kernel.php#L274

Still open? disappointing...

The preload file is now outside of the cache folder


Error: Could not find Chromium (rev. 1095492)

We installed Puppeteer 19 and we are getting the following error on Heroku Stack 22. It may be that some dependencies are missing...
Error: Could not find Chromium (rev. 1095492). This can occur if either
 1. you did not perform an installation before running the script (e.g. `npm install`) or
 2. your cache path is incorrectly configured (which is: /app/.cache/puppeteer).
For (2), check out our guide on configuring puppeteer at https://pptr.dev/guides/configuration.
    at ChromeLauncher.resolveExecutablePath (/app/node_modules/puppeteer-core/lib/cjs/puppeteer/node/ProductLauncher.js:127:27)
    at ChromeLauncher.executablePath (/app/node_modules/puppeteer-core/lib/cjs/puppeteer/node/ChromeLauncher.js:206:25)
    at ChromeLauncher.launch (/app/node_modules/puppeteer-core/lib/cjs/puppeteer/node/ChromeLauncher.js:93:37)
    at async module.exports (/app/pdf.js:11:21)
    at async Promise.all (index 0)

@IonicaBizau There's a few closed issues related to this. It's due to a change in how Pupeteer works - not anything related to this buildpack.
I finally got things working by downgrading to Pupeteer 18.1.0 (anything higher didn't work) and clearing the build cache, following the instructions in the README of this repository.

Clearing the build cache should work, but I've seen before where it seems like Heroku doesn't clear the full cache, or there is some other cache that causes things to stick around. I've fixed that by just creating a new Heroku app with the same code. Perhaps you can try clearing the cache, and if that doesn't work, either downgrade Puppeteer versions or create a new Heroku app if you'd like to use the latest.


Move list of sources to separate file, outside of Makefile

Either that, or use a wildcard make function to avoid listing sources altogether

done via https://github.com/LexouDuck/libccc/pull/27


Install STIX Math font

STIX2Math:
https://github.com/stipub/stixfonts/blob/master/OTF/STIX2Math.otf
related to https://github.com/metanorma/mn-native-pdf/issues/133#issuecomment-619208997

Done in https://github.com/fontist/formulas/commit/1bacc61497c0d69059604a5ce560e1fad7ccf652


unable to show confetti on click of button

`int[] confettiColors = new int[]{R.color.red, R.color.blue, R.color.green, R.color.black, R.color.orange, R.color.darkergray};
ConfettiSource confettiSource = new ConfettiSource(linearLayout.getWidth(),
linearLayout.getHeight());
CommonConfetti.rainingConfetti(linearLayout, confettiSource, confettiColors ).infinite();`
i have done this code ....is that sufficient for showing confetti?

it depends on when you do this, debug and check what's your linearLayout.getWidth(). my theory is that you are calling this before the linearlayout gets measured.


Run SAP Fiori Application With SAP Business Application Studio

Tutorial URL: https://developers.sap.com/tutorials/abap-environment-deploy-cf-production.html
In step 4 - sub step 4 ---> In screenshot its showing "List Report Object Page V2" but while executing we are getting only "List Report Object Page" tile. Please refer below screenshots.
In Tutorial

While executing

Hi @shivakumar-p-sap ,
I already created following pull request: #5743
It still needs to be merged. @MichaelCzcz  can you merge my changes?
Best regards,
Merve

Hi @MichaelCzcz ,
we can close this ticket.
Best regards,
Merve


Track in discovery.yml whether loaders append or upsert (or both)

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/2507
Originally created by @DouweM on 2021-01-12 22:27:27

Going beyond https://gitlab.com/meltano/meltano/-/issues/2505 to enable https://gitlab.com/meltano/meltano/-/issues/2506.

View 9 previous comments from the original issue on GitLab


Switch to new trivy-operator and trivy-server

This needs to be verified in AWS before merging

Fixes #941

Support for EKS has been deprecated. Furthermore, we are already running the trivy-operator. Closing this.


About the return values of  xgboostModel.transformLeaf function ?

About the return values of  xgboostModel.transformLeaf(trainRDD) ?   the value is  the value of leaf nodes or  the index of leaf nodes ?
Solving the CTR issue with XGboost4j-spark and sparkml lr , does it need to do one hot encoder with the leaves' values of  xgboostModel.transformLeaf(trainRDD) , then take it as input of logistic regression algorithm ??
请原谅我，需要用中文表述一下我的两个问题，通过 Xgboost4j-spark 和 sparkml 中的 LR 算法，做 CTR 预估，是否需要对xgboost模型输出的叶子节点进行 Onehot,然后将 Onehot 后的结果作为 LR 算法的输入？？
xgboost model 输出的transformLeaf 输出的是叶子节点的值，还是叶子节点的索引呢？

transformLeaf returns index of leaf nodes. Yes, you will want to perform one hot encoding if you are using output of transformLeaf as input to logistic regression


Node-waf replaced by node-gyp

Node-waf is not available anymore. I know that this package is quite old and you don't maintain it anymore but I hope it will work for me. Thanks for that.

@hlogeon sorry for the slow response. Thanks!


Cleanup multi-arch tests

Changes
Use common lachlanevenson/k8s-kubectl image instead of different ones for amd64 and s390x/ppc64le
architectures
/kind cleanup
Submitter Checklist
As the author of this PR, please check off the items in this checklist:

[ ] Docs included if any changes are user facing
[ ] Tests included if any functionality added or changed
[x] Follows the commit message standard
[x] Meets the Tekton contributor standards (including
functionality, content, code)
[x] Release notes block below has been filled in or deleted (only if no user facing changes)

Release Notes
NONE

/test pull-tekton-pipeline-build-tests

/test pull-tekton-pipeline-alpha-integration-tests

/lgtm


Remove redundant UI tests from cos-api

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)
[ X] 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)
https://tools.hmcts.net/jira/browse/FPET-819
Change description
Evidence of tests passing locally
Smoke test  : -

Functional test : -

Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[ ] No

@suresh-sharada Only one e2e test exists after this PR in src/e2e/tests/caseSearch_test.js. It checks that a user can find a case, and that these tabs show on the case screen:
[this.fields.historyTab, this.fields.summaryTab, this.fields.applicantsTab, this.fields.opTab, this.fields.docsTab, this.fields.ordersTab, this.fields.hearingsTab]
I wondered, if these should also remain (at least).
src/e2e/tests/summaryTab_test.js
"Verify details of sibling and other placement orders are displayed in the summary page"
src/e2e/tests/paymentTab_test.js
"Verify Payment details of a case"

Hi @gokul-sol.  Suresh agrees that we should keep the two tests below.  Can they be put back?  Thanks.

@suresh-sharada Only one e2e test exists after this PR in src/e2e/tests/caseSearch_test.js. It checks that a user can find a case, and that these tabs show on the case screen:
[this.fields.historyTab, this.fields.summaryTab, this.fields.applicantsTab, this.fields.opTab, this.fields.docsTab, this.fields.ordersTab, this.fields.hearingsTab]
I wondered, if these e2e tests should also remain (at least).
src/e2e/tests/summaryTab_test.js
"Verify details of sibling and other placement orders are displayed in the summary page"
src/e2e/tests/paymentTab_test.js
"Verify Payment details of a case"


rs485 support

Hi
any possibility of RS485 support in the future?
https://github.com/cbrake/linux-serial-test/blob/aed2a6e78160b63295368d70dbdbc19fe3a38225/linux-serial-test.c#L460
Thanks
Nick

Indeed it would be nice.
Maybe you can propose a pull request to help to add this feature.

rs485 is  not supported now?

I use 'apt-get install ros-kinetic-serial' to install the package. I find it supports rs485!

Confirmation on whether or not this is working and/or a pull request to enable this would be good. Closing for now though.


[BUG] [AIO] Unhealthy DNS pod

What happened:
Following instructions on microshift.io for AIO on Linux:
https://microshift.io/docs/getting-started/#using-microshift-for-application-development
All infra pods get scheduled and running except the default DNS pod (1/2):
openshift-dns                   dns-default-lkjwg                      1/2     Running   5          27m   <IP_ADDRESS>   a92cc98eb64a   <none>           <none>

Logs:
WARN[0000] Error validating CNI config file /etc/cni/net.d/10-flannel.conflist: [failed to find plugin "flannel" in path [/usr/local/libexec/cni /usr/libexec/cni /usr/local/lib/cni /usr/lib/cni /opt/cni/bin]]
.:5353
[INFO] plugin/reload: Running configuration MD5 = eb791f1fb4e1f964e4a7377f6b122c87
CoreDNS-1.8.1
linux/amd64, go1.16.1,
W0228 17:14:27.051185       1 reflector.go:436] github.com/coredns/coredns/plugin/kubernetes/controller.go:399: watch of *v1.EndpointSlice ended with: an error on the server ("unable to decode an event from the watch stream: http2: client connection lost") has prevented the request from succeeding
W0228 17:14:27.051214       1 reflector.go:436] github.com/coredns/coredns/plugin/kubernetes/controller.go:406: watch of *v1.Namespace ended with: an error on the server ("unable to decode an event from the watch stream: http2: client connection lost") has prevented the request from succeeding
W0228 17:14:27.051225       1 reflector.go:436] github.com/coredns/coredns/plugin/kubernetes/controller.go:395: watch of *v1.Service ended with: an error on the server ("unable to decode an event from the watch stream: http2: client connection lost") has prevented the request from succeeding

What you expected to happen:
All infra services must be up and running.
How to reproduce it (as minimally and precisely as possible):

Follow https://microshift.io/docs/getting-started/#using-microshift-for-application-development

Anything else we need to know?:
Environment:

Microshift version (use microshift version):
MicroShift Version: 4.8.0-0.microshift-unknown
Base OKD Version: 4.8.0-0.okd-2021-10-10-030117

Hardware configuration:
Lenovo X1 Carbon

OS (e.g: cat /etc/os-release):
Fedora 35

Kernel (e.g. uname -a):
Linux fedora.oglok.net 5.16.8-200.fc35.x86_64 #1 SMP PREEMPT Tue Feb 8 20:58:59 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Others:

Relevant Logs

I also ran into this (DNS not working at all)


everytime hit transfer button wallet goes white screen and nothing happens

every time hit transfer button wallet goes white screen and nothing happens

nevermind.  have to have eos in acct before that window will open...so if you create new acct transfer some funds to it before opening transfer tab

I am not sure, but may look like a UI bug. Was you able initiate transfer without specified amount of tokens?

yes i did !  once i put some more eos in there it was fine.  i commented on
my own issue in case someone else runs into same issue.  thanks for
responding though !!  wallet is awesome w/ ledger !!
On Sun, Sep 16, 2018 at 2:36 PM tarassh<EMAIL_ADDRESS>wrote:

I am not sure, but may look like a UI bug. Was you able initiate transfer
without specified amount of tokens?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/tarassh/fairy-wallet/issues/30#issuecomment-421819324,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ApT0jfRFc1TztOk1bnSekLrMkbU30QLcks5ubqgmgaJpZM4Wq5Ek
.

I confirm the same bug...

I have the same issue, but I have 0 balance. If i send some tokens to account should it fix that bug? does anyone know?

Exact !
I had 0.20 only on my account when i note that problem.
Now I have more than that and it works !
So it's a minor bug that disapear beyond a threshold...

cool, thanks! i hope they will fix that adding return button with describing how to fix that

Fixed in 0.9.4


Co-Sponsor Chips list has no Placeholder or Label text

The .chips list that holds the co-sponsors in the general data section has to placeholder text or label. A Lable would be better than a placeholder text because it would look more like the other fields then. In the past, only one of the placeholder options has worked though. This may have to do something with how the init event is triggered for this field. The placeholder text is in the init script but isn't being displayed. Only the secondaryPlaceholder seemed to have worked before though.

As with #6 this seems to have gotten better with the restructuring of event handling.

It doesn't seem like normal labels are supported on the chips object. will ask the materialize.css devs though.

I'm updating materialize first though, that may solve some things!

Nope: still doesn't work after the update. But, this does work: Idk why it doesn't work in the editor though.

See #82 for updating


Breaks pure-render checks

This module generates new a11y id's every render, meaning that pure render mixin doesn't work.

Why is this important for testing accessibility?

It's an issue because during development performance of the application is extremely poor with react-a11y enabled. Ideally we'd like to keep react-a11y enabled always so that new warnings are immediately visible to developers.

Yeah it's important because it slows iteration speed in development and makes it hard to identify similar performance regressions not caused by react-a11y.


Call univ_rhs_store # reset after each run_infer_one_pass

Also fix https://github.com/zhengqunkoo/hipsleek/issues/1#issuecomment-659909756.