Not able to connect to datasource

Hi
Running Grafana 10.0.2 in my docker desktop, i try to connect to our OCI tenant.
I've tested with a API key that are oci admin and still the plugin states "Data source is not working"
Better error messages would be nice, but how do i troubleshoot this?

Hi. Can you share logs coming from your container when trying to connect ? Thanks.

Configuration:

Log:
2023-07-13 10:58:55 logger=plugin.oci-metrics-datasource t=2023-07-13T08:58:55.613133057Z level=error msg="Error with config:DEFAULT" 2023-07-13 10:58:55 logger=context userId=1 orgId=1 uname=admin t=2023-07-13T08:58:55.613422132Z level=error msg="Internal server error" error="[plugin.downstreamError] failed to query data: Failed to query data: rpc error: code = Unknown desc = broken environment" remote_addr=<IP_ADDRESS> traceID= 2023-07-13 10:58:55 logger=context userId=1 orgId=1 uname=admin t=2023-07-13T08:58:55.613499302Z level=error msg="Request Completed" method=POST path=/api/ds/query status=500 remote_addr=<IP_ADDRESS> time_ms=1 duration=1.991377ms size=116 referer=http://localhost:3000/connections/datasources/edit/d372cfcb-5c6c-4b94-9109-818a4d039432 handler=/api/ds/query 2023-07-13 10:58:55 logger=plugin.oci-metrics-datasource t=2023-07-13T08:58:55.78661019Z level=error msg="Error with config:DEFAULT" 2023-07-13 10:58:55 logger=context userId=1 orgId=1 uname=admin t=2023-07-13T08:58:55.786711803Z level=error msg="Internal server error" error="[plugin.downstreamError] failed to query data: Failed to query data: rpc error: code = Unknown desc = broken environment" remote_addr=<IP_ADDRESS> traceID= 2023-07-13 10:58:55 logger=context userId=1 orgId=1 uname=admin t=2023-07-13T08:58:55.786747604Z level=error msg="Request Completed" method=POST path=/api/ds/query status=500 remote_addr=<IP_ADDRESS> time_ms=1 duration=1.389796ms size=116 referer=http://localhost:3000/connections/datasources/edit/d372cfcb-5c6c-4b94-9109-818a4d039432 handler=/api/ds/query 2023-07-13 10:58:56 logger=plugin.oci-metrics-datasource t=2023-07-13T08:58:56.1943837Z level=error msg="Error with config:DEFAULT" 2023-07-13 10:58:56 logger=context userId=1 orgId=1 uname=admin t=2023-07-13T08:58:56.194487948Z level=error msg="Internal server error" error="[plugin.downstreamError] failed to query data: Failed to query data: rpc error: code = Unknown desc = broken environment" remote_addr=<IP_ADDRESS> traceID= 2023-07-13 10:58:56 logger=context userId=1 orgId=1 uname=admin t=2023-07-13T08:58:56.194596509Z level=error msg="Request Completed" method=POST path=/api/ds/query status=500 remote_addr=<IP_ADDRESS> time_ms=2 duration=2.879643ms size=116 referer=http://localhost:3000/connections/datasources/edit/d372cfcb-5c6c-4b94-9109-818a4d039432 handler=/api/ds/query 2023-07-13 10:58:56 logger=plugin.oci-metrics-datasource t=2023-07-13T08:58:56.646698757Z level=error msg="Error with config:DEFAULT" 2023-07-13 10:58:56 logger=context userId=1 orgId=1 uname=admin t=2023-07-13T08:58:56.6469136Z level=error msg="Internal server error" error="[plugin.downstreamError] failed to query data: Failed to query data: rpc error: code = Unknown desc = broken environment" remote_addr=<IP_ADDRESS> traceID= 2023-07-13 10:58:56 logger=context userId=1 orgId=1 uname=admin t=2023-07-13T08:58:56.647004795Z level=error msg="Request Completed" method=POST path=/api/ds/query status=500 remote_addr=<IP_ADDRESS> time_ms=3 duration=3.255725ms size=116 referer=http://localhost:3000/connections/datasources/edit/d372cfcb-5c6c-4b94-9109-818a4d039432 handler=/api/ds/query 2023-07-13 10:58:57 logger=plugin.oci-metrics-datasource t=2023-07-13T08:58:57.081793557Z level=error msg="Error with config:DEFAULT" 2023-07-13 10:58:57 logger=context userId=1 orgId=1 uname=admin t=2023-07-13T08:58:57.081926367Z level=error msg="Internal server error" error="[plugin.downstreamError] failed to query data: Failed to query data: rpc error: code = Unknown desc = broken environment" remote_addr=<IP_ADDRESS> traceID= 2023-07-13 10:58:57 logger=context userId=1 orgId=1 uname=admin t=2023-07-13T08:58:57.082023073Z level=error msg="Request Completed" method=POST path=/api/ds/query status=500 remote_addr=<IP_ADDRESS> time_ms=2 duration=2.875247ms size=116 referer=http://localhost:3000/connections/datasources/edit/d372cfcb-5c6c-4b94-9109-818a4d039432 handler=/api/ds/query 2023-07-13 10:58:58 logger=plugin.oci-metrics-datasource t=2023-07-13T08:58:58.063855059Z level=error msg="Error with config:DEFAULT" 2023-07-13 10:58:58 logger=context userId=1 orgId=1 uname=admin t=2023-07-13T08:58:58.064180012Z level=error msg="Internal server error" error="[plugin.downstreamError] failed to query data: Failed to query data: rpc error: code = Unknown desc = broken environment" remote_addr=<IP_ADDRESS> traceID= 2023-07-13 10:58:58 logger=context userId=1 orgId=1 uname=admin t=2023-07-13T08:58:58.064314788Z level=error msg="Request Completed" method=POST path=/api/ds/query status=500 remote_addr=<IP_ADDRESS> time_ms=3 duration=3.24035ms size=116 referer=http://localhost:3000/connections/datasources/edit/d372cfcb-5c6c-4b94-9109-818a4d039432 handler=/api/ds/query 2023-07-13 10:58:58 logger=plugin.oci-metrics-datasource t=2023-07-13T08:58:58.747090823Z level=error msg="Error with config:DEFAULT" 2023-07-13 10:58:58 logger=context userId=1 orgId=1 uname=admin t=2023-07-13T08:58:58.747205665Z level=error msg="Internal server error" error="[plugin.downstreamError] failed to query data: Failed to query data: rpc error: code = Unknown desc = broken environment" remote_addr=<IP_ADDRESS> traceID= 2023-07-13 10:58:58 logger=context userId=1 orgId=1 uname=admin t=2023-07-13T08:58:58.747238466Z level=error msg="Request Completed" method=POST path=/api/ds/query status=500 remote_addr=<IP_ADDRESS> time_ms=2 duration=2.735327ms size=116 referer=http://localhost:3000/connections/datasources/edit/d372cfcb-5c6c-4b94-9109-818a4d039432 handler=/api/ds/query 2023-07-13 10:58:59 logger=plugin.oci-metrics-datasource t=2023-07-13T08:58:59.507688094Z level=error msg="Error with config:DEFAULT" 2023-07-13 10:58:59 logger=context userId=1 orgId=1 uname=admin t=2023-07-13T08:58:59.508015046Z level=error msg="Internal server error" error="[plugin.downstreamError] failed to query data: Failed to query data: rpc error: code = Unknown desc = broken environment" remote_addr=<IP_ADDRESS> traceID= 2023-07-13 10:58:59 logger=context userId=1 orgId=1 uname=admin t=2023-07-13T08:58:59.508090344Z level=error msg="Request Completed" method=POST path=/api/ds/query status=500 remote_addr=<IP_ADDRESS> time_ms=1 duration=1.81637ms size=116 referer=http://localhost:3000/connections/datasources/edit/d372cfcb-5c6c-4b94-9109-818a4d039432 handler=/api/ds/query 2023-07-13 10:59:00 logger=plugin.oci-metrics-datasource t=2023-07-13T08:59:00.087400057Z level=error msg="Error with config:DEFAULT" 2023-07-13 10:59:00 logger=context userId=1 orgId=1 uname=admin t=2023-07-13T08:59:00.087812842Z level=error msg="Internal server error" error="[plugin.downstreamError] failed to query data: Failed to query data: rpc error: code = Unknown desc = broken environment" remote_addr=<IP_ADDRESS> traceID= 2023-07-13 10:59:00 logger=context userId=1 orgId=1 uname=admin t=2023-07-13T08:59:00.087977117Z level=error msg="Request Completed" method=POST path=/api/ds/query status=500 remote_addr=<IP_ADDRESS> time_ms=3 duration=3.413444ms size=116 referer=http://localhost:3000/connections/datasources/edit/d372cfcb-5c6c-4b94-9109-818a4d039432 handler=/api/ds/query 2023-07-13 10:59:01 logger=plugin.oci-metrics-datasource t=2023-07-13T08:59:01.593808136Z level=error msg="Error with config:DEFAULT" 2023-07-13 10:59:01 logger=context userId=1 orgId=1 uname=admin t=2023-07-13T08:59:01.59398384Z level=error msg="Internal server error" error="[plugin.downstreamError] failed to query data: Failed to query data: rpc error: code = Unknown desc = broken environment" remote_addr=<IP_ADDRESS> traceID= 2023-07-13 10:59:01 logger=context userId=1 orgId=1 uname=admin t=2023-07-13T08:59:01.5940463Z level=error msg="Request Completed" method=POST path=/api/ds/query status=500 remote_addr=<IP_ADDRESS> time_ms=11 duration=11.496599ms size=116 referer=http://localhost:3000/connections/datasources/edit/d372cfcb-5c6c-4b94-9109-818a4d039432 handler=/api/ds/query

Hi. Looks like is not able to initiate the communication with the OCI API. This can usually be due to a misconfigured parameter (the "usual" suspect in this case is the API Key, make sure is the one downloaded from OCI console, not modified) or a network communication issue (make sure your container can access the internet and in particular the *oracle.com network)

Hi.
The container is able to access internet. I've downloaded the plugin. Docker host is my pc, so i can sign in to OCI.
Would be nice if the test, could verify access to oracle.com first and return message about that instead of having an errormessage that doesn't give you a glue about whats wrong.
The API key is the "API fingerprint key", in format bf:e9:11:5d:d7:12:xxxxxx, right?
I tried to re-enter everything. still same error

Yes the API key is in that format. Is the pem key you are using containing exactly 27 lines ? and begins with -----BEGIN PRIVATE KEY----- and ends with -----END PRIVATE KEY----- ? can you also verify the newline of the pem is UNIX format (not Windows) ?

Well, i did test it both with and without the begin/end lines.
Without, i get the "Data source is not working" error.
With, i get : "Cannot read properties of undefined (reading 'details')"
I downloaded the PEM file  (private key) from OCI when creating the API token, but it contains 28 lines (including begin/end)

Th file is UTF8, but how do i verify the format. I'm on windows OS

I do not know Windows, sorry. With UNIX/Linux OS you can use the command "file" to determine the line end format. However, you copy/pasted this key in the "Private Key" field, right ?

Hey, I do have the exact same problem:
logger=plugin.oci-metrics-datasource t=2023-07-24T16:24:32.44152414Z level=error msg="Error with config:DEFAULT"

logger=context userId=1 orgId=1 uname=admin t=2023-07-24T16:24:32.441722836Z level=error msg="Internal server error" error="[plugin.downstreamError] failed to query data: Failed to query data: rpc error: code = Unknown desc = broken environment" remote_addr=<IP_ADDRESS> traceID=

logger=context userId=1 orgId=1 uname=admin t=2023-07-24T16:24:32.44179929Z level=error msg="Request Completed" method=POST path=/api/ds/query status=500 remote_addr=<IP_ADDRESS> time_ms=2 duration=2.252837ms size=116 referer=http://<IP_ADDRESS>:3000/connections/datasources/edit/b6c07fc9-5c3f-4e6c-95a5-4e8012075760/ handler=/api/ds/query

logger=plugin.oci-metrics-datasource t=2023-07-24T16:24:32.956951635Z level=error msg="Error with config:DEFAULT"

logger=context userId=1 orgId=1 uname=admin t=2023-07-24T16:24:32.957136678Z level=error msg="Internal server error" error="[plugin.downstreamError] failed to query data: Failed to query data: rpc error: code = Unknown desc = broken environment" remote_addr=<IP_ADDRESS> traceID=

logger=context userId=1 orgId=1 uname=admin t=2023-07-24T16:24:32.957210387Z level=error msg="Request Completed" method=POST path=/api/ds/query status=500 remote_addr=<IP_ADDRESS> time_ms=2 duration=2.102871ms size=116 referer=http://<IP_ADDRESS>:3000/connections/datasources/edit/b6c07fc9-5c3f-4e6c-95a5-4e8012075760/ handler=/api/ds/query

logger=plugin.oci-metrics-datasource t=2023-07-24T16:24:33.510568401Z level=error msg="Error with config:DEFAULT"

logger=context userId=1 orgId=1 uname=admin t=2023-07-24T16:24:33.510732939Z level=error msg="Internal server error" error="[plugin.downstreamError] failed to query data: Failed to query data: rpc error: code = Unknown desc = broken environment" remote_addr=<IP_ADDRESS> traceID=

logger=context userId=1 orgId=1 uname=admin t=2023-07-24T16:24:33.510804324Z level=error msg="Request Completed" method=POST path=/api/ds/query status=500 remote_addr=<IP_ADDRESS> time_ms=2 duration=2.115372ms size=116 referer=http://<IP_ADDRESS>:3000/connections/datasources/edit/b6c07fc9-5c3f-4e6c-95a5-4e8012075760/ handler=/api/ds/query

logger=plugin.oci-metrics-datasource t=2023-07-24T16:24:33.990380103Z level=error msg="Error with config:DEFAULT"

logger=context userId=1 orgId=1 uname=admin t=2023-07-24T16:24:33.990560274Z level=error msg="Internal server error" error="[plugin.downstreamError] failed to query data: Failed to query data: rpc error: code = Unknown desc = broken environment" remote_addr=<IP_ADDRESS> traceID=

logger=context userId=1 orgId=1 uname=admin t=2023-07-24T16:24:33.990634649Z level=error msg="Request Completed" method=POST path=/api/ds/query status=500 remote_addr=<IP_ADDRESS> time_ms=2 duration=2.08875ms size=116 referer=http://<IP_ADDRESS>:3000/connections/datasources/edit/b6c07fc9-5c3f-4e6c-95a5-4e8012075760/ handler=/api/ds/query

logger=plugin.oci-metrics-datasource t=2023-07-24T16:24:35.695729409Z level=error msg="Error with config:DEFAULT"

logger=context userId=1 orgId=1 uname=admin t=2023-07-24T16:24:35.695928192Z level=error msg="Internal server error" error="[plugin.downstreamError] failed to query data: Failed to query data: rpc error: code = Unknown desc = broken environment" remote_addr=<IP_ADDRESS> traceID=

logger=context userId=1 orgId=1 uname=admin t=2023-07-24T16:24:35.696001731Z level=error msg="Request Completed" method=POST path=/api/ds/query status=500 remote_addr=<IP_ADDRESS> time_ms=2 duration=2.178451ms size=116 referer=http://<IP_ADDRESS>:3000/connections/datasources/edit/b6c07fc9-5c3f-4e6c-95a5-4e8012075760/ handler=/api/ds/query

logger=plugin.oci-metrics-datasource t=2023-07-24T16:24:36.734521685Z level=error msg="Error with config:DEFAULT"

logger=context userId=1 orgId=1 uname=admin t=2023-07-24T16:24:36.734702349Z level=error msg="Internal server error" error="[plugin.downstreamError] failed to query data: Failed to query data: rpc error: code = Unknown desc = broken environment" remote_addr=<IP_ADDRESS> traceID=

logger=context userId=1 orgId=1 uname=admin t=2023-07-24T16:24:36.734777698Z level=error msg="Request Completed" method=POST path=/api/ds/query status=500 remote_addr=<IP_ADDRESS> time_ms=16 duration=16.204181ms size=116 referer=http://<IP_ADDRESS>:3000/connections/datasources/edit/b6c07fc9-5c3f-4e6c-95a5-4e8012075760/ handler=/api/ds/query

logger=plugin.oci-metrics-datasource t=2023-07-24T16:24:37.726303653Z level=error msg="Error with config:DEFAULT"

logger=context userId=1 orgId=1 uname=admin t=2023-07-24T16:24:37.726510591Z level=error msg="Internal server error" error="[plugin.downstreamError] failed to query data: Failed to query data: rpc error: code = Unknown desc = broken environment" remote_addr=<IP_ADDRESS> traceID=

logger=context userId=1 orgId=1 uname=admin t=2023-07-24T16:24:37.726583205Z level=error msg="Request Completed" method=POST path=/api/ds/query status=500 remote_addr=<IP_ADDRESS> time_ms=2 duration=2.197841ms size=116 referer=http://<IP_ADDRESS>:3000/connections/datasources/edit/b6c07fc9-5c3f-4e6c-95a5-4e8012075760/ handler=/api/ds/query

logger=plugin.oci-metrics-datasource t=2023-07-24T16:24:38.734039676Z level=error msg="Error with config:DEFAULT"

logger=context userId=1 orgId=1 uname=admin t=2023-07-24T16:24:38.734441619Z level=error msg="Internal server error" error="[plugin.downstreamError] failed to query data: Failed to query data: rpc error: code = Unknown desc = broken environment" remote_addr=<IP_ADDRESS> traceID=

logger=context userId=1 orgId=1 uname=admin t=2023-07-24T16:24:38.734522622Z level=error msg="Request Completed" method=POST path=/api/ds/query status=500 remote_addr=<IP_ADDRESS> time_ms=2 duration=2.856838ms size=116 referer=http://<IP_ADDRESS>:3000/connections/datasources/edit/b6c07fc9-5c3f-4e6c-95a5-4e8012075760/ handler=/api/ds/query

logger=plugin.oci-metrics-datasource t=2023-07-24T16:24:39.740146688Z level=error msg="Error with config:DEFAULT"

logger=context userId=1 orgId=1 uname=admin t=2023-07-24T16:24:39.740311168Z level=error msg="Internal server error" error="[plugin.downstreamError] failed to query data: Failed to query data: rpc error: code = Unknown desc = broken environment" remote_addr=<IP_ADDRESS> traceID=

logger=context userId=1 orgId=1 uname=admin t=2023-07-24T16:24:39.740377028Z level=error msg="Request Completed" method=POST path=/api/ds/query status=500 remote_addr=<IP_ADDRESS> time_ms=2 duration=2.118898ms size=116 referer=http://<IP_ADDRESS>:3000/connections/datasources/edit/b6c07fc9-5c3f-4e6c-95a5-4e8012075760/ handler=/api/ds/query

logger=cleanup t=2023-07-24T16:27:58.60708791Z level=info msg="Completed cleanup jobs" duration=1.804088ms

Did configure it exactly as the guide said. But Grafana just states "Data Source not working"
I am also running Grafana locally but on my NAS.

Also, can you confirm you are using the very latest version (4.0.1) of the plugin ? thanks.

Yes, I am using OCI 4.0.1. Grafana version 10.0.2
Probably should also add Grafana runs in a Docker container on my QNAP NAS (linux based). It can access the internet, verified by pinging different adresses from inside the container.

Hi guys. I was able to reproduce the issue. This is due to recent changes in Grafana 10 and limited support for AngularJS. A couple of things here. you should put in your grafana.ini config file this statement: " angular_support_enabled = true". With that I still got errors while configuring the datasource, however the datasource seems to work (I can create dashboards, etc). I will open a bug and we will start to work for a bugfix. Meanwhile you can try as suggested to set the angular support and try to create a sample dashboard ignoring the error in datasource configuration. If this will not work I think, for now, you can use a different version of Grafana (v9 or v8). I will update on progresses on the bugfix.

I think in my case the problem is something else. I set up a new container wit Grafana v9.5.6 and still get the same error and log output. Could it be a new limitation to the Oracle free tier? But then again it did work in the past.

I tried with Grafana 9.5.6 and it works without errors. and yeah, I tested using a free account too.

Any word on when a fix for this will be released? We have been seeing the same issue with our Grafana 10.0.2 instance, and had to downgrade to 9.5.8 to get OCI metrics to work.

Hi all. "Datasource not working" is driving to some misconfiguration in your parameter (as said, the usual suspect is the API key). Current version of the plugin should work till version 9.x, if something is not working till this version then I would recommend to double check the parameters and eventually the policies in your tenancy. It can be useful to try to check on the same host where your Grafana is installed, also to check access using the OCI CLI to test if the service accountis working as expected. User who are using Grafana 10.x may have different problem ("Cannot read properties of undefined") while configuring the datasource. This is due to the deprecation of AngularJS in Grafana 10 and will be fixed in the next plugin release. However if you encounter that exact error, you can ignore for now and try to create a dashboard. As said this is due to AngularJS but does not prevent the current version of the plugin to work with Grafana 10.x too.

Hi. Yes, it can. There can be two potential issues. First, if your API key is working but the service account or user owner of that key does not have the policies to access metrics. Then you would run into that error. Or if you copy/pasted the API key skipping some characters, or with Windows newlines. Then the key is stored but is somewhat corrupted in the plugin.

Well, I can only speak to our experiences. The plugin did not work for us in version 10.0.2 - we have existing dashboard and the data source would not configure, and we got no data into the dashboards. Downgrade to 9.5.8, and it works fine (same API keys and everything).

Strange, I tested everything which was mentioned in this thread, but everything without succes

Downgrade to Grafana 8, Grafana 9.5.8,
Tried another user (which is definately able to read the metrics, because we use it on Linux prompts to read the output).

But none of them helped me out.
Any suggestions? I am currently running Grafana 9.5.8 and still receiving the same warning ( Datasource not working )

Can you try to upgrade to the latest plugin version (5.0.0) and double check your connection parameters and see if it fixed the issue ?

We will try to upgrade this as soon as possible.

Late, sorry. Can confirm this works now.


Add filenames to warnings for new syntax

Thanks Shane, I hadn't found the documentation for the options variable.


updated hook is triggered but data not change

Version
2.5.16
Reproduction link
https://codepen.io/greenhandTan/pen/NzRYZR
Steps to reproduce
waitting 1s and then show a alert dialog
What is expected?
updated hook should not be triggered
What is actually happening?
updated hook is triggered

I believe this is intended as it wouldn't be beneficial enough to check everything that has been set before updating.
In the other hand, if you have something expensive at every update, you can prevent it by setting the variable message only if it really changed.


Add native spinners from Android-Spinkit

Added an Android project that uses Android-Spinkit so that spinners can have native performance just like iOS ones !
Spinners :
Bounce
Wave
RotatingPlane
WanderingCubes
9CubeGrid
FadingCircleAlt
Pulse
ChasingDots
ThreeBounce
Circle
FoldingCube
also make it possible to link iOS and Android libraries simply use rnpm
$ rpm link

but on Android, after rnpm link you still need to add JitPack repository to your android app's build.gradle
allprojects {
        repositories {
            ...
            maven { url "https://jitpack.io" }
        }
    }

Add index.android.js in Example

This is awesome @wkh237 !!!! :)
The only missing piece we needed  🎉
I just have a few questions:

Can you confirm me that all the files you committed are necessary (.idea folder, gradle folder ...)? Maybe only necessary for your IDE ?
Why did you develop another Example instead of using the one we already have ? (It would be easier to manage one cross-platform example instead of 2)

@maxs15 No problem, I'll clean up the android project :D
As for the Android example, because index.android.js was empty, I thought that means the android part will not use the same one in index.ios.js ( after all android still missing Arcs and WordPress spinners ), so I put my test app instead.
I think it's good to use the same example, I 'll replace index.android.js with the iOS example :)

Perfect 👍
Well index.android.js was requiring index.ios.js, kind of stupid I admit (we could rename it index.js) but everything should work without modifying the example.
Thanks again for the good work !

@maxs15 I've updated my master branch for the changes :D

Awesome, I'm going to check that.
I'm getting an error when running the Example app, seems like I can't fetch the Android-SpinKit dependency.
Still trying to figure out why
FAILURE: Build failed with an exception.

What went wrong:
A problem occurred configuring project ':app'.

Could not resolve all dependencies for configuration ':app:_debugCompile'.
Could not find com.github.ybq:Android-SpinKit:1.0.4.
Searched in the following locations:
https://jcenter.bintray.com/com/github/ybq/Android-SpinKit/1.0.4/Android-SpinKit-1.0.4.pom
https://jcenter.bintray.com/com/github/ybq/Android-SpinKit/1.0.4/Android-SpinKit-1.0.4.jar
file:/Users/maxs/Documents/Perso/Github/personal/react-native-spinkit/Example/node_modules/react-native/android/com/github/ybq/Android-SpinKit/1.0.4/Android-SpinKit-1.0.4.pom
file:/Users/maxs/Documents/Perso/Github/personal/react-native-spinkit/Example/node_modules/react-native/android/com/github/ybq/Android-SpinKit/1.0.4/Android-SpinKit-1.0.4.jar
file:/Users/maxs/Documents/SDK/ANDROID/extras/android/m2repository/com/github/ybq/Android-SpinKit/1.0.4/Android-SpinKit-1.0.4.pom
file:/Users/maxs/Documents/SDK/ANDROID/extras/android/m2repository/com/github/ybq/Android-SpinKit/1.0.4/Android-SpinKit-1.0.4.jar
file:/Users/maxs/Documents/SDK/ANDROID/extras/google/m2repository/com/github/ybq/Android-SpinKit/1.0.4/Android-SpinKit-1.0.4.pom
file:/Users/maxs/Documents/SDK/ANDROID/extras/google/m2repository/com/github/ybq/Android-SpinKit/1.0.4/Android-SpinKit-1.0.4.jar
Required by:
Example:app:unspecified > Example:react-native-spinkit:unspecified

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

BUILD FAILED

@maxs15 because Android-Spinkit uses jitpack not default repository, after rnpm link you still have to manually add
'maven { url "https://jitpack.io" }'
to app's android build.gradle just like what I described in the first comment.
(because I don't know how to make this automatic :/ )
I 've tested this on different machines several times, and I think it should work properly, I'll try it again later :D

I've finally succeeded to build the app, the problem was maven { url "https://jitpack.io" } in Example/android/build.gradle was defined in the buildscriptproperty instead of allprojects.
Now I'm gonna have to find why the app quit unexpectedly (I'm getting an alert "Unfortunately, Example has stopped") when I'm running the app on my phone with the library.
If I unlink the library the app is working again

Could you send me your build.gradle ?
I want to make sure everything is right

@maxs15 I think you're right, I should move maven { url "https://jitpack.io" } into allprojects  block.
As for the app crash problem, does it happens when you click change color button several times? Android color attribute only accepts  six-digit hexadecimal representation, perhaps this is the reason ?

No it's on the app start, I don't even see anything..
It should something missing in my configuration if you're able to start your app properly without any issue

Hi @maxs15 , I'm locating the issue, are you running the app with release configuration ? I could only reproduce this issue when I change Build Variant to release in Android Studio.

After the app crashes (on the app start just like you described),
I find last logs before it crashes by command adb logcat
E/        (30771): Unable to load script from assets: index.android.bundle
E/AndroidRuntime(30771): FATAL EXCEPTION: mqt_js
E/AndroidRuntime(30771): Process: com.example, PID: 30771
E/AndroidRuntime(30771): java.lang.RuntimeException: Couldn't get the native call queue: bridge configuration isn't available. This shouldn't be possible. Congratulations.
E/AndroidRuntime(30771): 	at com.facebook.react.bridge.queue.NativeRunnable.run(Native Method)
E/AndroidRuntime(30771): 	at android.os.Handler.handleCallback(Handler.java:739)
E/AndroidRuntime(30771): 	at android.os.Handler.dispatchMessage(Handler.java:95)
E/AndroidRuntime(30771): 	at com.facebook.react.bridge.queue.MessageQueueThreadHandler.dispatchMessage(MessageQueueThreadHandler.java:31)
E/AndroidRuntime(30771): 	at android.os.Looper.loop(Looper.java:135)
E/AndroidRuntime(30771): 	at com.facebook.react.bridge.queue.MessageQueueThreadImpl$3.run(MessageQueueThreadImpl.java:187)
E/AndroidRuntime(30771): 	at java.lang.Thread.run(Thread.java:818)
W/ActivityManager(  728):   Force finishing activity com.example/.MainActivity
E/EGL_emulation(  713): tid 713: eglCreateSyncKHR(1181): error 0x3004 (EGL_BAD_ATTRIBUTE)

I think this is the reason, because there's no assets folder in Example project, not to mention the bundle file index.android.bundle
E/        (30771): Unable to load script from assets: index.android.bundle

If we're using debug mode, the app fetches bundle from react-native packager server instead of assets folder inside itself, so it won't crash.
In order to generate offline bundles, I followed procedure in official document
Go to the root folder of Example app and run this command
# do execute ./gradlew installRelease in android folder, that will use an incorrect CWD
cd android && ./gradlew installRelease

And the app starts without any problem.

Thanks for looking @wkh237.
Unfortunately this is not the issue, I'm running the app in debug mode using react-native run-android
I'm getting that error using adb logcat
E/AndroidRuntime( 3416): FATAL EXCEPTION: AsyncTask #1
E/AndroidRuntime( 3416): Process: com.example, PID: 3416
E/AndroidRuntime( 3416): java.lang.RuntimeException: An error occured while executing doInBackground()
E/AndroidRuntime( 3416): 	at android.os.AsyncTask$3.done(AsyncTask.java:304)
E/AndroidRuntime( 3416): 	at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:355)
E/AndroidRuntime( 3416): 	at java.util.concurrent.FutureTask.setException(FutureTask.java:222)
E/AndroidRuntime( 3416): 	at java.util.concurrent.FutureTask.run(FutureTask.java:242)
E/AndroidRuntime( 3416): 	at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:231)
E/AndroidRuntime( 3416): 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
E/AndroidRuntime( 3416): 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
E/AndroidRuntime( 3416): 	at java.lang.Thread.run(Thread.java:818)
E/AndroidRuntime( 3416): Caused by: java.lang.IllegalAccessError: Method 'void android.support.v4.net.ConnectivityManagerCompat.<init>()' is inaccessible to class 'com.facebook.react.modules.netinfo.NetInfoModule' (declaration of 'com.facebook.react.modules.netinfo.NetInfoModule' appears in /data/app/com.example-2/base.apk)
E/AndroidRuntime( 3416): 	at com.facebook.react.modules.netinfo.NetInfoModule.<init>(NetInfoModule.java:55)
E/AndroidRuntime( 3416): 	at com.facebook.react.shell.MainReactPackage.createNativeModules(MainReactPackage.java:67)
E/AndroidRuntime( 3416): 	at com.facebook.react.ReactInstanceManagerImpl.processPackage(ReactInstanceManagerImpl.java:793)
E/AndroidRuntime( 3416): 	at com.facebook.react.ReactInstanceManagerImpl.createReactContext(ReactInstanceManagerImpl.java:730)
E/AndroidRuntime( 3416): 	at com.facebook.react.ReactInstanceManagerImpl.access$600(ReactInstanceManagerImpl.java:91)
E/AndroidRuntime( 3416): 	at com.facebook.react.ReactInstanceManagerImpl$ReactContextInitAsyncTask.doInBackground(ReactInstanceManagerImpl.java:184)
E/AndroidRuntime( 3416): 	at com.facebook.react.ReactInstanceManagerImpl$ReactContextInitAsyncTask.doInBackground(ReactInstanceManagerImpl.java:169)
E/AndroidRuntime( 3416): 	at android.os.AsyncTask$2.call(AsyncTask.java:292)
E/AndroidRuntime( 3416): 	at java.util.concurrent.FutureTask.run(FutureTask.java:237)
E/AndroidRuntime( 3416): 	... 4 more

There is some issue related to this error on the RN github (like this one: https://github.com/facebook/react-native/issues/7373)
Could you confirm me the version of react-native you're running?
I'm running the example using the RN 0.25.1
Thanks

@wkh237 found the issue.
If I'm removing compile 'com.android.support:appcompat-v7:23.3.0 it's working !
Do you know if we need this library ? Looks like some component like react-native-dialogs (https://github.com/aakashns/react-native-dialogs/blob/master/android/build.gradle) doesn't include it

Hi, @maxs15, it's great to hear that! The RN version I'm using should be the same as yours, I just clone the master branch and install my spinkit from my local repo when testing.
$ git clone https://github.com/maxs15/react-native-spinkit.git
$ cd react-native-spinkit/Example
$ npm install
$ npm install --save path-to-local-repo
$ rnpm link
$ vim android/build.gradle # open build.gradle and add jitpack repo manually

It works fine on my devices (Android 4.4 and 5.0 devices).
The adb log looks like something is changing UI in a non-UI thread, but I can't figure out why android support library make this happen.
I think this line :
compile 'com.android.support:appcompat-v7:23.3.0

is unnecessary, it's automatically generated when I create the android library project, and it seems that Android-Spinkit does not use it at all, and neither do I.

Ok, let's figure it out later and merge the PR.

The native android spinners are now available in the release 0.1.0 !
@wkh237 could you check if everything is working on your side using the last version ? Thanks


Pub server port should be configurable

Please make the pub serve port configurable from within the dart editor. When pub serve tries to start on my machine it fails because I already have a server running on port 8080. I don't want pub serve to run on 8080.
////////////////////////////////////////////////////////////////////////////////////
Editor: 1.5.0.dev_01_01 (2014-05-23)
OS: Linux - amd64 (3.13.0-24-generic)
JVM: 1.7.0_55
projects: 16
open dart files: 5
auto-run pub: true
localhost resolves to: <IP_ADDRESS>
mem max/total/free: 1778 / 470 / 71 MB
thread count: 30
index: 480658 relationships in 84913 keys in 391 sources
SDK installed: true
Dartium installed: true

how can we change port number instead of default port number 8080
in (webdev) instead of (pug server).


If credential.issuanceDate is not passed in, set it to now()

When using issue(), if the credential passed in does not contain an issuanceDate, create one and set it to now().
(This frees up developers from having to deal with RFC-formatting the date, etc, if they don't actually care about a specific date.)

Addressed by #106.


Update coverage from MAVSDK tests

This enables updating coverage information successfully from MAVSDK tests.

Rebased on master.


SIGPIPE unavailable on Windows10/11 : catch exception ?

Hi,
EDIT: not seen previous open issue related to it: https://github.com/chris-ritsen/network-audio-controller/issues/9
netaudio device list
gives me error on Windows 11:
site-packages\netaudio\console\application.py", line 1, in <module>     from signal import signal, SIGPIPE, SIG_DFL ImportError: cannot import name 'SIGPIPE' from 'signal' (C:\Program Files\Python312\Lib\signal.py). Did you mean: 'SIGFPE'?
Seen there: https://stackoverflow.com/questions/58718659/cannot-import-name-sigpipe-from-signal-in-windows-10
Replacing this solved in https://github.com/chris-ritsen/network-audio-controller/blob/master/netaudio/console/application.py the problem for me:
try:
    from signal import signal, SIGPIPE, SIG_DFL
    signal(SIGPIPE, SIG_DFL)
except ImportError:  # If SIGPIPE is not available (win32),
    pass             # we don't have to do anything to ignore it.

But don't know if it's the best solution.

@rem5 Could you test the PR on your end please?

@muzicman82 If using the master branch, this should already be fixed: https://github.com/chris-ritsen/network-audio-controller/pull/23

@muzicman82 If using the master branch, this should already be fixed: #23

I just did pip install netaudio.


Fail to set custom verification callback on macOS/iOS/...

The following MWE fails with an assertion error when trying to use a customVerificationCallback in NIOSSLClientHandler on an Apple platform.
let tlsConfiguration = TLSConfiguration.forClient()
let sslContext = try! NIOSSLContext(configuration: tlsConfiguration)

let eventLoopGroup = MultiThreadedEventLoopGroup(numberOfThreads: 1)

ClientBootstrap(group: eventLoopGroup)
    .channelInitializer { channel in
        let sslHandler = try! NIOSSLClientHandler(context: sslContext, serverHostname: nil, customVerificationCallback: {_, _ in
        })
        return channel.pipeline.addHandler(sslHandler)
    }.connect(host: "localhost", port: 443)

When initializing NIOSSLClientHandler, SSLConnection.customVerificationManager is set twice which triggers the assertion.
First time:
https://github.com/apple/swift-nio-ssl/blob/e14f8ebd6a919c5cf9bbbacaf5245e38ecdb8352/Sources/NIOSSL/SSLContext.swift#L252-L260
Second time:
https://github.com/apple/swift-nio-ssl/blob/e14f8ebd6a919c5cf9bbbacaf5245e38ecdb8352/Sources/NIOSSL/NIOSSLClientHandler.swift#L71-L73

Yeah, I think that assertion is overly fussy. I will double-check this, but I’m pretty sure the code behaves entirely reasonably in the face of setting this callback twice.


⚠ Cioos Pacific CKAN Sitemap has degraded performance

In 3625e6a, Cioos Pacific CKAN Sitemap (https://catalogue.cioospacific.ca/sitemap/sitemap-1.xml) experienced degraded performance:

HTTP code: 200
Response time: 11982 ms

Resolved: Cioos Pacific CKAN Sitemap performance has improved in 0340c28 after 18 minutes.


Sink Analyser: Pretty print callpath result

Signed-off-by: Arthur Chan<EMAIL_ADDRESS>

Currently, the callpath for each parent function of the sink function will be sorted and only top 20 of the callpath link is displayed. The link will direct the user to another new webpage showing the callpath and some related information.
The sorting is based on the length of the callpath, the 20 shallowest callpath will be displayed, indicate possible API calls that are closest to the target sink function.

Awesome! Moving the sink details page into individual pages is nice and I think we can use this for additional features in the future.


Fix artifacts being worth 0 spacebucks

Fixes #16737
Also fixes sussy =+ operator, which is not a real operator and just does assign instead of increment.
Changelog
:cl:

tweak: Artifacts now retain their monetary value after extracting points.

famous =+ operator from c


why can't intents wtih i18n by async?

I'm currently researching how to internationalize my Action and most of the info seems pretty clear.
However, according to the fulfillments section of the localization docs, intents that use the i18n node package must not be async.
Can someone please explain why? My welcome intent relies on async/await, but I'd like to use i18n middleware to handle locales. Has anyone tried this with i18next (used in Alexa examples)?

The current i18n library we mention in the docs only has a shared global instance for setting the locale so it needs to not be async in order to ensure that there are no race conditions with multiple conversations setting conflicting locales.
You should be able to apply the same concepts described in the docs for another i18n library that is able to have multiple concurrent instances with different locales so you can avoid the race condition.
Thank you for bringing up the i18next library though! We been wanting to update our localization docs so we'll take a look again at libraries like 18next to evaluate the best i18n solution for Actions Node.js developers.

Thanks @Canain! My fulfillment is built as an express app hosted on AWS lambda - so the lifetime of the process is only as long as request => response. In this case, do you still think I'd run up against the race condition?

I'm not super familiar with how AWS Lambda runtimes work exactly, but if you can guarantee that only one conversation request will be invoked at a time for a Node.js instance, then you should be able to avoid the race condition as the locale won't be set multiple times during a single request.

@nealrs Would you mind sharing some code showing how your welcome intent uses async/await

Closing this since the original question was answered.


tokenizer.py

Due to meta-ai lama-3-8b not using sentencePiece, but litgpt/tokenizer. py still uses sentencePiece. When I use the litgpt chat -- checkpoint_dir E: \ checkpoint \ meta llama \ Meta-Llama-3-8B Instrument
RuntimeError: Internal: could not part ModelProto from E: \ checkpoint \ meta llama \ Meta Llama-3-8B Instrument \ tokenizer. model
How to solve it

Hi there,
thanks for reporting this. If the Hub does not provide a tokenizer.model file, it should use the tokenizers library instead:
https://github.com/Lightning-AI/litgpt/blob/63a0a10f30a92b317cbd3ea40fc61e15af2b0858/litgpt/tokenizer.py#L21-L33
In the case of Llama 3, only the tokenizer.json is provided, so it should not use sentencepiece:

I was trying this in a fresh environment
git clone https://github.com/Lightning-AI/litgpt.git
cd litgpt

pip install -e ".[all]"
litgpt download --repo_id meta-llama/Meta-Llama-3-8B-Instruct --access_token ...

pip uninstall sentencepiece
litgpt chat --checkpoint_dir checkpoints/meta-llama/Meta-Llama-3-8B-Instruct

and it worked without problem.

I was using tokenizers version '0.19.1', perhaps you have an older version installed? Could you try to upgrade it via
pip install tokenizers -U and give it another try?

Let us know if you still have problems here, happy to reopen and revisit!


Auto Assign SLOs

Ability to scan services and auto assign SLOs for latency, availability, throughput and error budget.
Using historical data, take a running average to define the "99.5 percentile" and auto assign those numbers as targets. In this way, large organizations can quickly ramp up to speed and only adjust as necessary, rather than manually set up each process.

@bharathraj10 @tangollama @ricegi could you guys pls provide more description of this idea? How should this work from UI/user perspective?

@norbertsuski - the idea behind this one was to just auto-assign SLOs. So imagine an experience on a the launcher that listed all the entities that don't have SLOs and have an action that would auto-assign a very generic SLO.
I think we could just look at 500 errors per transactions as the most basic and set the SLA to a standard. 99.4 - that is 6000 defects per million.


"Could not locate the configuration file" prints on every run

This seems to be have been introduced between versions 5.0.5 and 6.0.1.
./result/bin/macchina
Error: Custom { kind: NotFound, error: "Could not locate the configuration file" }

        a8888b.           Host        -  owen@nixos
       d888888b.          Machine     -  Dell Inc. XPS 13 9370
 ...

I personally didn't plan on writing a macchina config file, but I don't want that to print on every run.
It's not strictly a bug, but I'm not a fan of this default behavior. It says there's an error, yet it continues running just fine. Maybe this should only be printed when running the doctor (-d)?
Found this change while reviewing the nixpkgs upgrade pr

We're tackling this in v6.0.2.
I'm closing this as it's a duplicate of #242

@414owen Is this still an issue with v6.0.2?


Redirect URI validation is too restrictive

The field says allows any valid URIs but validator restricts scheme to http and https only. Need to support custom protocol handler URIs such as secure-image://client.

Thanks @f-w we are going to address this in our current sprint. and we have a meeting scheduled the week  of august 11 to get your feedback. thanks!


[SPARK-14306][ML][PySpark] PySpark ml.classification OneVsRest support export/import

What changes were proposed in this pull request?
https://issues.apache.org/jira/browse/SPARK-14306
Add PySpark OneVsRest save/load supports.
How was this patch tested?
Test with Python unit test.

test it please

Test build #55993 has started for PR 12439 at commit 55bd6d1.

Test build #55993 has finished for PR 12439 at commit 55bd6d1.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class OneVsRestParam(HasFeaturesCol, HasLabelCol, HasPredictionCol):
class OneVsRest(Estimator, OneVsRestParam, MLReadable, MLWritable):
class OneVsRestModel(Model, OneVsRestParam, MLReadable, MLWritable):

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/55993/
Test PASSed.

Merged build finished. Test PASSed.

ping @jkbradley

Thanks!  I'll take a look now

Nice PR, this looks good except for the 1 nit I commented on.
After this PR, I believe we will have full Python coverage for persistence!  I'd like to do something of an integration test for persistence in ml/tests.py in the "PersistenceTest" suite.  I just made a JIRA: [https://issues.apache.org/jira/browse/SPARK-14706].  Would you be interested in working on that one?

@jkbradley Sure, I can do that. I'll fix this one first.

test it please

Test build #56079 has started for PR 12439 at commit 69357ec.

LGTM pending tests

Test build #56079 has finished for PR 12439 at commit 69357ec.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class OneVsRestParams(HasFeaturesCol, HasLabelCol, HasPredictionCol):
class OneVsRest(Estimator, OneVsRestParams, MLReadable, MLWritable):
class OneVsRestModel(Model, OneVsRestParams, MLReadable, MLWritable):

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/56079/
Test PASSed.

Merging with master.  Thanks for the PR!


TS - kiota abstractions must be a peer dependency in auth and fetch library

When should you use peer dependencies?
When you are building a library to be used by other projects, and
This library is using some other library, and
You expect/need the user to work with that other library as well

https://stackoverflow.com/a/34645112/10760931

Thanks for raising this.
Assuming the abstraction lib is a peer dep for http, serialization and authentication packages, what would be the dependency story in msgraph-core? and in msgraph service libs?
Would you have them + abstractions being a peer dep in msgraph-core and then being a direct dep in the service libs to lock down the versions?

Would you have them + abstractions being a peer dep in msgraph-core and then being a direct dep in the service libs to lock down the versions?

We will have abstractions as a dependency in graph core and service library.
the graph core depends on the interfaces for middleware and authentication which are needed for a core only user as well.

but then following that logic, http/serialization/authentication which all depend on and expose abstractions interfaces should also have a dependency, not a peer dep.


Fixed makefile parameter.  build output directly into target folder i…

build output directly into target folder instead of moving files

use NDK_OUT and NDK_LIBS_OUT parameters
remove clearNativeArtifacts because no longer needed. as artifacts aren't placed under base directory.

makefile parameter works now as correct APP_BUILD_SCRIPT parameter is passed to ndk-build

Added unit test to verify
old code used make style -f makefile which doesn't work for ndk-build

This actually fails if you build the samples. At least for me.
Can you try and fix that
mvn clean install -P it
with an attached device.
I get -------------------------------------------------------
T E S T S
Running com.simpligility.maven.plugins.androidndk.projects.NativeSampleIT
Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 8.713 sec <<< FAILURE! - in com.simpligility.maven.plugins.androidndk.projects.NativeSampleIT
buildDeployAndRun3.2.3  Time elapsed: 8.58 sec  <<< FAILURE!
java.lang.AssertionError: [[ERROR] No native compiled library found, did the native compile complete successfully?, [ERROR] Error while executing: No native compiled library found, did the native compile complete successfully?, [ERROR] Failed to execute goal com.simpligility.maven.plugins:android-ndk-maven-plugin:1.0.1-SNAPSHOT:ndk-build (default-ndk-build) on project native-code: No native compiled library found, did the native compile complete successfully? -> [Help 1], [ERROR] , [ERROR] , [ERROR] For more information about the errors and possible solutions, please read the following articles:, [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException, [ERROR] , [ERROR] After correcting the problems, you can resume the build with the command, [ERROR]   mvn  -rf :native-code]
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.assertTrue(Assert.java:41)
at io.takari.maven.testing.executor.MavenExecutionResult.assertErrorFreeLog(MavenExecutionResult.java:44)
at com.simpligility.maven.plugins.androidndk.projects.NativeSampleIT.buildDeployAndRun(NativeSampleIT.java:51)
Results :
Failed tests:
NativeSampleIT.buildDeployAndRun:51 [[ERROR] No native compiled library found, did the native compile complete successfully?, [ERROR] Error while executing: No native compiled library found, did the native compile complete successfully?, [ERROR] Failed to execute goal com.simpligility.maven.plugins:android-ndk-maven-plugin:1.0.1-SNAPSHOT:ndk-build (default-ndk-build) on project native-code: No native compiled library found, did the native compile complete successfully? -> [Help 1], [ERROR] , [ERROR] , [ERROR] For more information about the errors and possible solutions, please read the following articles:, [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException, [ERROR] , [ERROR] After correcting the problems, you can resume the build with the command, [ERROR]   mvn  -rf :native-code]
Tests run: 1, Failures: 1, Errors: 0, Skipped: 0
[WARNING] File encoding has not been set, using platform encoding UTF-8, i.e. build is platform dependent! The file encoding for reports output files should be provided by the POM property ${project.reporting.outputEncoding}.
[INFO]

So did we merge this with the failing test?  sorry I didn't respond quicker..

I will look into this and make sure it is all working properly.. that the output .so's are being found and attached as artifacts..  I know that since the plugin builds each ABI separately, instead of all at once like the ndk-build wants to do... it will do a clean before building.. which would mean already built ABI artifacts  are deleted, which would be bad.  But I thought I got around this..  Why does the plugin build each ABI separately?

Not sure.. I have not had a closer look. I just merged it forgetting that the ITs are not run on travis..

It builds them separately because we dont have the support for attaching multiple .so for different architectures just yet.  Instead of relying on the Application.mk we specify the target architectures in the pom.xm.  This should probably be looked at at some point.

Ok, it seems this commit is indeed breaking things in the end - I get errors while building the samples as well.  Will see if I can make the plugin build all ABIs in a single invoke of the ndk-build.  There are some concerns about regressions, mainly concerning the selection of toolchains for the ABI being built (e.g. to select toolchain, you most likely will need to compile in separate steps ...)


remove  Response's Status magic var

remove  Response's Status magic var

remove  Response's Status magic var

remove  Response's Status magic var

remove  Response's Status magic var

Seems reasonable, but can you please split into 2 PRs? The changes seems unrelated right now.


completion-less spawn is deprecated.

The stackful coroutine examples need to be updated to handle the case where the spawned function exits via exception. This needs to be commented so the user understands. And we need to define the Asio macro which turns use of deprecated functions into a compile error.

The stackful coroutine examples need to be updated to handle the case where the spawned function exits via exception. This needs to be commented so the user understands. And we need to define the Asio macro which turns use of deprecated functions into a compile error.

This will need a bit more work, since it'll also change the signatures in the tests & the way stack are allocated with boost.context. boost::coroutine::attributes is deprecated as well.

derp


Data Insertion API returns invalid XML

When an error occurs with the data insertion API invalid XML is returned, multiple root nodes.
<?xml version="1.0" encoding="UTF-8"?>
<status>FAILURE</status>
<reason>NO account</reason>

While fixing this would obviously be difficult given it would likely be a breaking change it definitely something that should be noted in the documentation. Furthermore the documentation is wrong and states multiple xml declarations are returned in a single response, that does not match what I'm seeing.
https://github.com/AdobeDocs/analytics-1.4-apis/blob/master/docs/data-insertion-api/reference/r_post_response_codes.md
This invalid XML is making parsing problematic.
https://github.com/Leonidas-from-XIV/node-xml2js/issues/197#issuecomment-628488459

Thank you for reporting this! I've removed the multiple declarations, improved the formatting, and added a note that failure responses can contain multiple root nodes.


Programming parser produces too many false positives

Find a way to limit the false positives that the programming parser produces.

Rewrote the confidence calculation and using upgrades to simplebayes to give better results.


remove Adapter and tableName parameter at Writer/Db::prepareInsert()

and uses $this->db and $this->tableName directly as they are accessible in prepareInsert() and we use it.

Thanks, @samsonasik


logging to /dev/null?

as far asI see nothing gets logged permanently right now, which is good for my purposes. but would it be possible to explicitely send the vpn connection logs to /dev/null?

What do you mean by "vpn connection logs"? Are you referring to the Wireguard daemon logs? If so, it is not managed by wireguard-ui actually.


Update 3-Longest-Substring-Without-Repeating-Characters.js

Refactor 3 Longest Substring Without Repeating Characters

File(s) Modified:3-Longest-Substring-Without-Repeating-Characters.js
Language(s) Used:  javascript
Submission URL: https://leetcode.com/submissions/detail/769028712/

Refactored solution to match neetcode's video solution

Thanks, @maryums!


Segmentation fault: 11 when running model = load_codec_model(use_gpu=True if device == 'cuda' else False)

When I run the clone_voice.ipynb (on a mac), specially this code:
import os
os.environ['KMP_DUPLICATE_LIB_OK']='True'
from bark.generation import load_codec_model, generate_text_semantic
from encodec.utils import convert_audio
import torchaudio
import torch
from hubert.hubert_manager import HuBERTManager
hubert_manager = HuBERTManager()
hubert_manager.make_sure_hubert_installed()
hubert_manager.make_sure_tokenizer_installed()
device = 'cuda' #'cuda' # or 'cpu'
model = load_codec_model(use_gpu=True if device == 'cuda' else False)
I get the following error:
Segmentation fault: 11
Do you know how to deal with this?

Hi @artificialnouveau , I am pretty sure you are using a fork. You should re-post your question in the forked repo discussions.
But, the segmentation fault feels like some models aren't downloaded properly. Or, you down' have cuda on your mac -- device shouldn't be cuda if you are using a mac. Change it to cpu or mps instead.


[GreencityUBS] Order payment by points return order id

UBSClientServiceImpl.class, saveFullOrderToDB()

pull request #457


Add Windows tests for the container commands

Added more unit tests for 'nerdctl container' command on Windows. Also added the 'HyperVContainer' helper to check with hcsshim if the container is a hyperv container.
Restart and stop tests are skipped since they fail atm on WS 2019.

Docker test seems to be flaky, and it's a linux test it's failing on. Can this be merged?


Clarify Linux/Windows Security scan inconsistencies

File: docker-hub/official_images.md
Windows images do not show scan results - but Linux images do.  Please update the docs to make this more clear
Navigate to the repository of the Official Image whose security scan you want to view.
Click the Tags tab to see a list of tags and their security scan summaries.

This is correct for Linux images:  https://hub.docker.com/r/library/alpine/tags/
Microsoft Images are very different, there is no security scan information
https://hub.docker.com/r/microsoft/nanoserver/tags/
https://hub.docker.com/r/microsoft/dotnet/tags/

Thanks for sharing this issue. As the issue is old, a lot has changed. The information is no longer applicable.


Pixi global inject

Problem description
When installing tools using pixi global install it is sometimes necessary to install additional packages in the same environment as the tool. For example pixi global install visidata will install visidata, but if we want to be able to inspect yaml files then we need pyyaml in the visidata environment too. With pipx, this is achieved using pipx inject visidata pyyaml. It would be great to have a similar command for pixi global.
Is there a current method to manually install a package inside a global tool environment? I tried manually activating the environment in ~/.pixi/envs/visidata but when I try using mamba install pyyaml I get the following error:
DirectoryNotACondaEnvironmentError: The target directory exists, but it is not a conda environment.

This is a good idea!

I'd be willing to work on this, would it be right to say if we want to have inject, then we essentially want pixi global to be a wrapper for project-type pixi?
That is, it'll find the project or init a project in ~/.pixi/envs as a bare pixi project repo (I mean bare as in the content of envs/my-package will be the contents of project level .pixi/ directory, env and prefix)
... then behave exactly as if using project-type pixi for that project? With some new mappings for subcommands like

global install package => init --p $(uname -m), add package , setup ~/.pixi/bin with needed .sh scripts`
global inject package depends => add depends, update project for package if needed

Does that make sense? I imagine once pixi global manages packages as if they were projects, it'll not diverge from the rest of pixi. The only question would be whether to follow pipx's approach of, don't global install things that don't have user entry points - I think it's a good approach. Thoughts?

Mm, from my point of view global environments are indeed slimmed down pixi projects, but without a lot of the complexity of tasks, multiplatform, host/build dependencies and lock files. If you want that you're better of with a project. You can most likely reuse a lot of code but I would not quite treat them the same.

I think implementing global install as an ordinary pixi project with added magic of exposing the binaries/entry-points is a good concept that should allow reusing existing functionality.
Things I'd like:

Allow adding pypi-dependencies and exposing entry-points from those packages as well
Allow configuring which binaries / entry-points to expose - i.e. allow specifying entry-points that shouldn't be exposed.

Another question on a use case is related to sharing the same tools. I haven't had the need to do this, but for example,
Someone in my collaboration asks me how I use some tool that I've installed with pipx (that has dependencies I've got via pipx inject), I'd give them code to run pipx from their shell.
Is this what we want for pixi? I think it helps keep the scope down since usage of globals are typically less context-sensitive,
BUT it's not as similar to project TOML's that only support [dev] dependencies and perhaps someone has a need for a more complex globally used tool. Writing it makes me realize I don't think I'd want that. Running from cli seems best I think.

Okay, thanks @ruben-arts, I think that's better too. @dhirschfeld maybe postponing exposing binaries from dependencies installed vua inject.
For now, scope is to only expose binaries that are already exposed with global install but adding an inject command for dependencies in those envs. I can do that.

I think implementing global install as an ordinary pixi project with added magic of exposing the binaries/entry-points is a good concept that should allow reusing existing functionality.
Things I'd like:
* Allow adding `pypi-dependencies` and exposing entry-points from those packages as well

* Allow configuring which binaries / entry-points to expose - i.e. allow specifying entry-points that shouldn't be exposed.

I was pondering this today and had the thought, why make it so that only global can expose binaries?
I'm taking some inspiration of the pixi run install task of developing pixi itself, but if ordinary pixi projects could expose entry-points globally, it would be really nice for developing tools locally in addition for installing downloaded ones.
pixi global install <package> then could become a wrapper around pixi init ~/.pixi/envs/<package> and something like pixi add --manifest-path ~/.pixi/envs/<package> --expose-bins <package>.
Then pixi global inject <parent_package> <new_package> would also wrap pixi add --manifest-path ~/.pixi/envs/<parent_package> and could have --expose-bins argument as well.
# ~/xpublish-dev/pixi.toml
[pypi-dependencies]
xpublish_cli = {path = "./xpublish-cli", editable = true, expose_bins = true}

Something like this would also help #1017 for where related subpackages also need to have their entry-points accessible.
# ~/.pixi/envs/ansible/pixi.toml
[dependencies]
ansible = {version = "something", expose_bins = true}
ansible-core = {version = "something", expose_bins = true}

I feel that auto expose into your global space from a project wouldn't fit the pixi project vision. Possibly with a command line addition to allow a user to do it themselves could make sense.

I feel that auto expose into your global space from a project wouldn't fit the pixi project vision. Possibly with a command line addition to allow a user to do it themselves could make sense.

I was thinking along those lines, but I wanted to avoid the what-ifs in that comment to not confuse the idea too much.
A technique that I've seen to deal with this that I've liked is having a .local version of a config that acts as an override of the regular config file.

Say an pixi.toml has a dependency that exposes bins.
# ~/xpublish-dev/pixi.toml
[pypi-dependencies]
xpublish_cli = {path = "./xpublish-cli", editable = true, expose_bins = true}

Say, if you run pixi install (or any other commands that would trigger installation), then it would give a warning, but not expose them automatically.
WARN pixi::project: pixi.toml suggested exposing binaries and/or entry points from
`xpublish_cli` to your global environment.
Run `pixi install -expose-bins xpublish_cli` to add to your global environment.

If the user decides to run pixi install -expose-bins xpublish_cli, then they are linked in ~/.pixi/bin/, and a local config file is created (and added to .gitignore) to record the users choice.
# ~/xpublish-dev/pixi.local.toml
[pypi-dependencies]
xpublish_cli = {expose_bins = true}

To avoid nagging the user, there could be an --ignore-bins option as well that would also create a local config file.
# ~/xpublish-dev/pixi.local.toml
[pypi-dependencies]
xpublish_cli = {expose_bins = false}

Do binaries from a project need to be exposed globally?
Wouldn't pixi run <bibary-name> work just fine?

Just a data point - I tried to use copier as a pixi global app but it didn't work as I also need copier_templates_extensions installed in the same environment.

Thanks @dhirschfeld good one! I think you might be able to do pixi exec -s copier -s copier_template_extensions copier, (haven't tried it 👼, so ymmv) to work around this for now.

We are currently finishing up a minimal version of the new pixi global. The details are in this proposal, but the main advantages are:

Shareable global environments.
Managing complex environments with multiple packages as dependencies
Flexible exposure of executables

Before we release it, we would appreciate it if a couple of users could try it out to make sure we are not missing glaring bugs or UX problems.
You can use it locally like this:
# Clone the repository
git clone https://github.com/prefix-dev/pixi.git

# Navigate into the repository
cd pixi

# Checkout a specific branch
git switch feature/pixi-global

# Install the Rust project with a custom binary name
pixi run install-as pixid

# Run commands
pixid global install nushell

This should work on all operating systems and only requires git and pixi to be installed locally.

Tried this on windows and got the following error:
 You don't have a global manifest yet.
Do you want to create one based on your existing installation?
 You don't have a global manifest yet.
Do you want to create one based on your existing installation?
Your existing installation will be removed if you decide against it. yes
  × Failed to create global manifest from existing installation
  ├─▶ failed to write to file `C:\Users\<username>\.pixi\manifests\pixi-
  │   global.toml`
  ╰─▶ The system cannot find the path specified. (os error 3)

The .pixi folder does exist, and creating the manifests folder in it before running the last command resolves the problem. I'll try it on my linux machine sometime today if I have the time

Hey Sam 👋🏻 !
Nice find, I opened a PR that should fix this. Could you please check if it solves the problem?
https://github.com/prefix-dev/pixi/pull/2163

I get a warning about add_channel being dead code, but otherwise works a treat :) not sure if I was supposed to test anything beyond that but the subcommand inject or global add isn't added yet to the version I tested. So I haven't tested that bit, but the installation works great. Not sure if it's supposed to but figured I'd mention it.

Also not sure if this is exactly the right place for it, but I just saw the open question in the proposal for "Should we version the manifest?" and I'm just gonna add my 2 cents unprompted: I highly recommend that you do. As someone that has worked a year on things that used to be un-versioned and had to make it versioned, please do your future selves a favor and do it, with a compatibility check if possible. Even a very lightweight versioning like a single number, can save you so much head ache in the future if you ever have to make changes to your format. Of course, it's still all of your decision, but from where I stand the potential benefits outweigh the cost

oh one other thing that is about this specific PR, the installation and running of tools via this version of pixi go very smoothly but after the command I run exits the terminal immediately closes. I tested this with several versions of hydromt (versions 0.10.0 and 0.9.4 specifically) as well as grayskull which was the first conda installable binary that came to mind.
Not sure if it is a pixi problem, but I don't remember it happening before, so it might be worth investigating on this side as well.

Thanks for the feedback Sam ❤


CI cannot run JUnit Tests

Currently, the Travis-CI can not run unit tests for the IVCT_Framework.
For example, we get stuck on running tests for the Command subproject:

It requires IVCT_CONF to be set. Aka we need a valid IVCT Runtime folder.
It requires the HelloWorld TestSuite, which is a different repository alltogether.

I am wondering whether these tests are actually unit tests, or should rather be considered as integration tests? For now I am running the CI build without running tests.
The question is now: do we want to automatically run unit/integration tests with the Travis-CI builds? I am inclined to say yes. If so:

Can we remove the dependency of the unit tests on specific Test Suites and an IVCT Runtime configuration?
If not: we have a chicken and egg problem: if we have the required docker images for the HelloWorld Test Suite, and the volume containers for making a valid IVCT Runtime, we could set up a valid environment by using docker.

Please let me know what would be possible.

check is this is still an open issue

It still is. You can try it yourself with a gradle test on the development branch. Gives an error at:
> Task :Command:test

Unexpected exception thrown.
org.gradle.internal.remote.internal.MessageIOException: Could not write '/<IP_ADDRESS>:63103'.
        at org.gradle.internal.remote.internal.inet.SocketConnection.flush(SocketConnection.java:134)
        at org.gradle.internal.remote.internal.hub.MessageHub$ConnectionDispatch.run(MessageHub.java:325)
        at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:63)
        at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:46)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:55)
        at java.lang.Thread.run(Thread.java:748)
Caused by: java.io.IOException: An existing connection was forcibly closed by the remote host
        at sun.nio.ch.SocketDispatcher.write0(Native Method)
        at sun.nio.ch.SocketDispatcher.write(SocketDispatcher.java:51)
        at sun.nio.ch.IOUtil.writeFromNativeBuffer(IOUtil.java:93)
        at sun.nio.ch.IOUtil.write(IOUtil.java:51)
        at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:471)
        at org.gradle.internal.remote.internal.inet.SocketConnection$SocketOutputStream.writeWithNonBlockingRetry(SocketConnection.java:272)
        at org.gradle.internal.remote.internal.inet.SocketConnection$SocketOutputStream.writeBufferToChannel(SocketConnection.java:260)
        at org.gradle.internal.remote.internal.inet.SocketConnection$SocketOutputStream.flush(SocketConnection.java:254)
        at org.gradle.internal.remote.internal.inet.SocketConnection.flush(SocketConnection.java:132)
        ... 7 more

> Task :Command:test FAILED

has been fixed by adding the activemq task into the gradle test build environment


Questions about xxxStorageLocation syntax

Why is this writing method used in the new version of the contract? What are the benefits of this writing method? Is there any document that I can refer to?
struct ERC2981Storage {         RoyaltyInfo _defaultRoyaltyInfo;         mapping(uint256 tokenId => RoyaltyInfo) _tokenRoyaltyInfo;     }     // keccak256(abi.encode(uint256(keccak256("openzeppelin.storage.ERC2981")) - 1)) & ~bytes32(uint256(0xff))     bytes32 private constant ERC2981StorageLocation = 0xdaedc9ab023613a7caf35e703657e986ccfad7e3eb0af93a2853f8d65dd86b00;

That is using the ERC-7201: Namespaced Storage Layout pattern, which was introduced starting from version 5.0.0 of the upgradeable variant of OpenZeppelin Contracts.  This blog post outlines its benefits.
If you have further questions on this pattern, feel free to post on our forum at https://forum.openzeppelin.com/


Oops: need to quote back reference introducer

Unfortunately this bug was not spotted earlier.

Very strange: the diff shows that the original change did use a second backslash:
https://github.com/sebbASF/infrastructure-puppet/commit/7c49ec23a1976449f18759a9181bf584d5d8abc4#diff-938c82e29af80dc3f834d0985642368c
See lines 83-84


Missing dependencies for nd4j-native-platform

Issue Description
Below dependency is failing to find some jars
 <repository>
            <id>snapshots-repo</id>
            <url>https://oss.sonatype.org/content/repositories/snapshots</url>
            <releases>
                <enabled>false</enabled>
            </releases>
            <snapshots>
                <enabled>true</enabled>
                <updatePolicy>daily</updatePolicy>
            </snapshots>
        </repository>
    <deeplearning4j>0.9.2-SNAPSHOT</deeplearning4j>
    <dependency>
            <groupId>org.nd4j</groupId>
            <artifactId>nd4j-native-platform</artifactId>
            <version>${deeplearning4j}</version>
        </dependency>

Could not resolve dependencies for project  The following artifacts could not be resolved: org.nd4j:nd4j-native:jar:android-arm:0.9.2-SNAPSHOT, org.nd4j:nd4j-native:jar:android-arm64:0.9.2-SNAPSHOT, org.nd4j:nd4j-native:jar:android-x86:0.9.2-SNAPSHOT, org.nd4j:nd4j-native:jar:android-x86_64:0.9.2-SNAPSHOT, org.nd4j:nd4j-native:jar:ios-arm64:0.9.2-SNAPSHOT, org.nd4j:nd4j-native:jar:windows-x86_64:0.9.2-SNAPSHOT, org.nd4j:nd4j-native:jar:linux-ppc64le:0.9.2-SNAPSHOT: Failure to find org.nd4j:nd4j-native:jar:android-arm:0.9.2-SNAPSHOT

Looking at the maven repository https://oss.sonatype.org/content/repositories/snapshots/org/nd4j/nd4j-native-platform/0.9.2-SNAPSHOT/ those dependencies are indeed missing...

0.9.2-SNAPSHOT is obsolete.
The last release was 1.0.0-alpha - use that instead (it's what 0.9.2-SNAPSHOT became).
If you really need snapshots (you very likely don't) you can use 1.0.0-SNAPSHOT.


Different Results from ks cluster ls when --output Specified

We have a number of clusters and all but one are Classic.  The one exception is vpc-gen2.
Using ibmcloud ks cluster ls to list them shows all clusters.
However, ibmcloud ks cluster ls --output json is one short and doesn't list the one cluster that's vpc-gen2.
Is it possible to get all clusters in json format with a single call?  I tried using multiple --provider arguments but it only accepts the last one.

Is this not the right place to ask these questions?

@JohnStarich could you address this question?


Prepare release PM 1.0

This is a list of what should be done for 1.0 PM release:

[X] Close all issues of Milestone 1.0: https://github.com/PolyMathOrg/PolyMath/milestone/1
[x] Discuss how to manage code and branches after 1.0 release: https://github.com/PolyMathOrg/PolyMath/issues/118
[x] Prepare list of changes
[x] Update README.md
[x] Update CONTRIBUTING.md
[x] Clean branches
[x] Do the release with the 1.0 tag
[x] Do announcement on Twitter
[x] Do announcements on Pharo mailing-lists

Everything is done.


created doc Mendix Cloud v4

needed more information about this topic

Can be language-reviewed and merged.


Investigate Bamboo maven plugin used in Artemis

Check if it's still not possible to generate build plans from yaml

It's also still impossible to POST yaml specs to a bamboo server. [1] And it also looks like it will not be implemented. Additionally, yaml specs are not fully documented, like its run in docker feature and maybe generating the builds using the Java Specs with the maven plugin is the way to go here.


Header styling

I made some styling changes to the header

I'll review this after https://github.com/OpenCovenant/quill/issues/445 has been merged

I'm liking the red color, but maybe we can add it later after discussing it more.
Please change red to black and white respectively (to white and dark mode).


chore: update codecov.yaml

Signed-off-by: saintube<EMAIL_ADDRESS>Ⅰ. Describe what this PR does

update codecov.yaml, change PR blocking for project-level coverage into -2% (before: -5%)
add unit tests for meminfo.go

Ⅱ. Does this pull request fix one issue?

Ⅲ. Describe how to verify it
Ⅳ. Special notes for reviews
test CI blocking for coverage

Codecov Report

Merging #208 (2272d69) into main (49850ce) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head 2272d69 differs from pull request most recent head 78d918a. Consider uploading reports for the commit 78d918a to get more accurate results

@@           Coverage Diff           @@
##             main     #208   +/-   ##
=======================================
  Coverage   58.52%   58.52%
=======================================
  Files         100      100
  Lines        9222     9222
=======================================
  Hits         5397     5397
  Misses       3374     3374
  Partials      451      451

Flag
Coverage Δ

unittests
58.52% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Continue to review full report at Codecov.

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

/approve


Update issue templates to redirect to the notebook repo

Part of https://github.com/jupyterlab/retrolab/issues/356

This is what it looks like now:


feat(popover): add missing accessibility attributes, cypress/storybook tests and documentation.

What is it?

[x] Feature / enhancement
[ ] Bug
[x] Docs / tests

Description
Finalize headless popover component.
Add missing cypress and storybook tests.
Add docs.
Checklist:

[x] My code follows the developer guidelines of this project
[x] I have performed a self-review of my own code
[x] I have made corresponding changes to the documentation
[x] Added new tests to cover the fix / functionality

I have read the CLA Document and I hereby sign the CLA


Fix Docker tagging issue with upper case

Build is broken on main branch due to tags in upper case: https://github.com/OpenDevin/OpenDevin/actions/runs/9569731256/job/26384552101
This was introduced by #2456

Running the workflow on my fork now: https://github.com/li-boxuan/OpenDevin


Upload code

The following is a to-do list for the first release:

[ ] upload code
[ ] pass tests
[ ] improve test coverage
[ ] python3 compatibility

#2 works towards uploading the code

#4 Adds the code and the tests

#7 fixes Python3 compatibility


Sync.pull returns (_, pull_error) result, but there is no pp_pull_error

thanks for #684, I finally found the time to attempt to upgrade to a more recent irmin-master.
while doing so, the signature of Sync.pull changed:
-     (unit, [ fetch_error | Merge.conflict ]) result Lwt.t
+    (status, pull_error) result Lwt.t

now in #683 (not merged) a pp_pull_error was briefly introduced, but the current API does not have a pp_pull_error (but it has a pp_push_error). It would be great to supply potential users with such a functionality?

and while at it, a pp_status may be beneficial as well ;)

turns out there's S.Store.Status which defines t and pp, but the S.SYNC_STORE.status is slightly different... (and the pp doesn't contain any variance annotations)...

in addition, your src/irmin-git/irmin_git.ml contains some debug messages which are not very useful:
    let result refs =
      (* FIXME: need pp_result *)
      Log.debug (fun f ->
          f "fetch result: XXX" (* Git.Sync.Result.pp_fetch r *) );
      let key =
        try Some (G.Reference.Map.find reference refs) with Not_found -> None
      in

Thanks for the reports. Looks like there already was a pp_pull_error, but it just wasn't being exposed.
This is partly resolved by https://github.com/mirage/irmin/pull/789 (which doesn't do anything about the incomplete debug message, yet); please let me know if it's missing something.

@CraigFe thanks, that looks like a good solution to me! :)

Fixed by #789


initial addition of apps client

This adds a client for handling interactions with apps (backed by serving.Services). The client automatically adds a label for new apps created by kf and injects VCAP style variables when they are upserted automatically.
It includes a KfApp we can use as the basis for accessing deeply nested parts of serving.Service.
It will replace the following in subsequent small PRs:

[ ] Environment client
[ ] App Lister
[ ] Part of deployer
[ ] Part of push

@poy can you remind me how to run the integration tests again?

@josephlewis42 scripts/integration_tests.sh

@poy looking deeper into these errors, I was able to get them to run by updating the buildpacks on the cluster and increasing the timeouts. It looks like there might be some slowness in GKE/Knative/gcr right now.


Message Additions

Allow Apps to provide message attachments/uploads.

Issue moved to RocketChat/Rocket.Chat.Apps-engine #55 via ZenHub


Requeue finalizer if resource is in use

Type of change

Bugfix

Description
This ensures that reconciler is called again to recheck finalization of
the resource.
@kornys I've not tested if this fixes your issue, but I could see from the operator logs that it failed to remove first because address was still present, but it didn't attempt to reconcile the endpoint again, so this should ensure that it tries again after 10 seconds. Usually it tries again on errors, but maybe that is not guaranteed by framework, so explicit scheduling is probably better.
Checklist

[ ] Update/write design documentation in ./documentation/design
[ ] Write tests and make sure they pass
[ ] Update documentation
[ ] Check RBAC rights for Kubernetes / OpenShift roles
[ ] Try your changes from Pod inside your Kubernetes and OpenShift cluster, not just locally
[ ] Reference relevant issue(s) and close them after merging
[ ] Update CHANGELOG.md

@lulf so from code I see, if it is requeue, that means if will try again after 10 seconds and if it fails again it requeue it again? Like a infinite recursion?

@kornys Correct, it will attempt indefinitely. IMO it shouldn't try to be clever and give up and go ahead with deletion, because it can lead to an inconsistent state.

@lulf makes sense :-)


Hibernate bootstrapping agreement

✅ commit has been signed off by @gavinking

Alright, so I believe we have a consensus on this! 🎉🎉🎉


[ISSUE] global.labels Used in Both matchLabels and metadata.labels

Describe the issue:
related to: https://jira.camunda.com/browse/SUPPORT-24909
The global.labels field in the Camunda Platform Helm chart is being applied to both metadata.labels and matchLabels (selectors). This behavior is problematic because matchLabels are immutable, and dynamic or environment-specific labels cannot be safely updated in subsequent deployments.

Actual behavior:
When labels are defined in global.labels, they are applied to:

metadata.labels (which is expected and allowed to change).
matchLabels (used for Kubernetes selectors, which are immutable).

Expected behavior:

How to reproduce:

Logs:

Environment:
Please note: Without the following info, it's hard to resolve the issue and probably it will be closed.

Platform:
Helm CLI version:
Chart version:
Values file:

@hamza-m-masood adding your comment here.
I can reproduce this.
Helm upgrading with a changed global.labels produces an error saying that matchLabels can't be changed in each component.
I'm fine with you opening a bug report on this. We could probably just take out this section in the function:
https://github.com/camunda/camunda-platform-helm/blob/36fc7f60e4aa2dc00288e91ad222[…]55b8/charts/camunda-platform-8.6/templates/camunda/_helpers.tpl
I'm fine with that part being taken out because the other labels still exist in the function.
I checked other bitnami charts hoping to see something along the lines of global.matchLabels but most charts only provide matchLabels for either ingress or networkPolicies. I did find a common function which seems useful: https://github.com/bitnami/charts/blob/b41a51d1bd04841fc108b78d3b8357a5292771c8/bitnami/common/templates/_labels.tpl#L34
This is used by the grafana chart which can be seen here:
https://github.com/bitnami/charts/blob/b41a51d1bd04841fc108b78d3b8357a5292771c8/bitnami/grafana/templates/deployment.yaml#L16C1-L21C43
it would be better to implement what the grafana chart does already. It keeps the matchLabels immutable

We are also facing this issue.


origin table is reversed

Excuse me, I have a tableview to show all things, after I install your framework, and use in my target page, until here is fine, but when I back the last page the tableview is reverse.

Do you access tableView.re in 車行列表ViewController?

I've fixed this issue. Please try v0.4.6!

it works!!! Thank you so much.

Great!! Thank you for your reporting.


nanoflann: 1.2.3 -> 1.3.0

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/nanoflann/versions.
meta.description for nanoflann is: '"Header only C++ library for approximate nearest neighbor search"'.
Release on GitHub
Compare changes on GitHub

Checks done (click to expand)

built on NixOS

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

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

found 1.3.0 with grep in /nix/store/44kyifad9yj3m198p8hrsvbq92402wk2-nanoflann-1.3.0

directory tree listing: https://gist.github.com/c7fd9e5648491852526e406463d8e677

du listing: https://gist.github.com/92c8cb81bb8101fc1b9c99ffaa93b72a

Instructions to test this update (click to expand)

One-time optional setup to skip building using Cachix:
nix-shell -p cachix --run 'cachix use r-ryantm'

Test this update by entering a nix shell, seeing what is inside the
result, and if applicable, running some binaries:
nix-shell --pure -I nixpkgs=https://github.com/r-ryantm/nixpkgs/archive/f750f8ea0214d87d1c65eaa752006dfe2f40600d.tar.gz -p nanoflann
ls -la /nix/store/44kyifad9yj3m198p8hrsvbq92402wk2-nanoflann-1.3.0

Success on x86_64-linux (full log)
Attempted: nanoflann
Partial log (click to expand)
-- Installing: /nix/store/44kyifad9yj3m198p8hrsvbq92402wk2-nanoflann-1.3.0/lib/cmake/nanoflann/nanoflannConfig.cmake
-- Installing: /nix/store/44kyifad9yj3m198p8hrsvbq92402wk2-nanoflann-1.3.0/lib/cmake/nanoflann/nanoflannConfigVersion.cmake
-- Installing: /nix/store/44kyifad9yj3m198p8hrsvbq92402wk2-nanoflann-1.3.0/include/nanoflann.hpp
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/44kyifad9yj3m198p8hrsvbq92402wk2-nanoflann-1.3.0
strip is /nix/store/vcc4svb8gy29g4pam2zja6llkbcwsyiq-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/44kyifad9yj3m198p8hrsvbq92402wk2-nanoflann-1.3.0/lib
patching script interpreter paths in /nix/store/44kyifad9yj3m198p8hrsvbq92402wk2-nanoflann-1.3.0
checking for references to /build in /nix/store/44kyifad9yj3m198p8hrsvbq92402wk2-nanoflann-1.3.0...
/nix/store/44kyifad9yj3m198p8hrsvbq92402wk2-nanoflann-1.3.0

Success on x86_64-darwin (full log)
Attempted: nanoflann
Partial log (click to expand)
-- Installing: /nix/store/rqqph2rs530vl2n4s4jx0j4kszxp8wcf-nanoflann-1.3.0/lib/cmake/nanoflann/nanoflannTargets.cmake
-- Installing: /nix/store/rqqph2rs530vl2n4s4jx0j4kszxp8wcf-nanoflann-1.3.0/lib/pkgconfig/nanoflann.pc
-- Installing: /nix/store/rqqph2rs530vl2n4s4jx0j4kszxp8wcf-nanoflann-1.3.0/lib/cmake/nanoflann/nanoflannConfig.cmake
-- Installing: /nix/store/rqqph2rs530vl2n4s4jx0j4kszxp8wcf-nanoflann-1.3.0/lib/cmake/nanoflann/nanoflannConfigVersion.cmake
-- Installing: /nix/store/rqqph2rs530vl2n4s4jx0j4kszxp8wcf-nanoflann-1.3.0/include/nanoflann.hpp
post-installation fixup
strip is /nix/store/53nysl8bqwxihwzs1pgwka20nf8mbvlp-cctools-binutils-darwin/bin/strip
stripping (with command strip and flags -S) in /nix/store/rqqph2rs530vl2n4s4jx0j4kszxp8wcf-nanoflann-1.3.0/lib
patching script interpreter paths in /nix/store/rqqph2rs530vl2n4s4jx0j4kszxp8wcf-nanoflann-1.3.0
/nix/store/rqqph2rs530vl2n4s4jx0j4kszxp8wcf-nanoflann-1.3.0

Success on aarch64-linux (full log)
Attempted: nanoflann
Partial log (click to expand)
-- Installing: /nix/store/lf3k3hbx35rjlcwnz4vcdpm4xv7lxi7l-nanoflann-1.3.0/lib/cmake/nanoflann/nanoflannConfig.cmake
-- Installing: /nix/store/lf3k3hbx35rjlcwnz4vcdpm4xv7lxi7l-nanoflann-1.3.0/lib/cmake/nanoflann/nanoflannConfigVersion.cmake
-- Installing: /nix/store/lf3k3hbx35rjlcwnz4vcdpm4xv7lxi7l-nanoflann-1.3.0/include/nanoflann.hpp
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/lf3k3hbx35rjlcwnz4vcdpm4xv7lxi7l-nanoflann-1.3.0
strip is /nix/store/p9akxn2sfy4wkhqdqa3li97pc6jaz3r1-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/lf3k3hbx35rjlcwnz4vcdpm4xv7lxi7l-nanoflann-1.3.0/lib
patching script interpreter paths in /nix/store/lf3k3hbx35rjlcwnz4vcdpm4xv7lxi7l-nanoflann-1.3.0
checking for references to /build in /nix/store/lf3k3hbx35rjlcwnz4vcdpm4xv7lxi7l-nanoflann-1.3.0...
/nix/store/lf3k3hbx35rjlcwnz4vcdpm4xv7lxi7l-nanoflann-1.3.0


Added hyperscale billing self-service API.

ARM (Control Plane) API Specification Update Pull Request

[!TIP]
Overwhelmed by all this guidance? See the Getting help section at the bottom of this PR description.

[!NOTE]
As of January 2024 there is no PR assignee. This is expected. See https://aka.ms/azsdk/pr-arm-review.

PR review workflow diagram
Please understand this diagram before proceeding. It explains how to get your PR approved & merged.

 Click here to see the details of Step 1
Breaking changes review (Diagram Step 1)
If the automation determines you have breaking changes, i.e. Step 1 from the diagram applies to you,
you must follow the breaking changes process.
IMPORTANT This applies even if:

The tool fails while it shouldn't, e.g. due to runtime exception, or incorrect detection of breaking changes.
You believe there is no need for you to request breaking change approval, for any reason.
Such claims must be reviewed, and the process is the same.

 Click here to see the details of Step 2
ARM API changes review (Diagram Step 2)

For help with Step 2 / "ARM review", see https://aka.ms/azsdk/pr-arm-review.

 Click here to see the diagram footnotes
Diagram footnotes
[1] See ARM review queue (for PR merge queues, see [2]).
[2] public repo merge queue, private repo merge queue (for ARM review queue, [1])
The ARM reviewer on-call engineer visits the merge queue twice a day, so the approximate ETA for merges is 12 - 24 hours.

Purpose of this PR
What's the purpose of this PR? Check the specific option that applies. This is mandatory!

[ ] New resource provider.
[ ] New API version for an existing resource provider. (If API spec is not defined in TypeSpec, the PR should have been generated using OpenAPI Hub).
[x] Update existing version for a new feature. (This is applicable only when you are revising a private preview API version.)
[ ] Update existing version to fix OpenAPI spec quality issues in S360.
[ ] Other, please clarify:

edit this with your clarification

Due diligence checklist
To merge this PR, you must go through the following checklist and confirm you understood
and followed the instructions by checking all the boxes:

[x] I confirm this PR is modifying Azure Resource Manager (ARM) related specifications, and not data plane related specifications.
[x] I have reviewed following Resource Provider guidelines, including
ARM resource provider contract and
REST guidelines (estimated time: 4 hours).
I understand this is required before I can proceed to the diagram Step 2, "ARM API changes review", for this PR.

Additional information

 Viewing API changes
For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the Generated ApiView comment added to this PR. You can use ApiView to show API versions diff.

Suppressing failures
If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
suppressions guide to get approval.

Getting help

First, please carefully read through this PR description, from top to bottom. Please fill out the Purpose of this PR and Due diligence checklist.
To understand what you must do next to merge this PR, see the Next Steps to Merge comment. It will appear within few minutes of submitting this PR and will continue to be up-to-date with current PR state.
For guidance on fixing this PR CI check failures, see the hyperlinks provided in given failure
and https://aka.ms/ci-fix.
For help with PR workflow diagram Step 2 (ARM review), see https://aka.ms/azsdk/pr-arm-review.
If the PR CI checks appear to be stuck in queued state, please add a comment with contents /azp run.
This should result in a new comment denoting a PR validation pipeline has started and the checks should be updated after few minutes.
If the help provided by the previous points is not enough, post to https://aka.ms/azsdk/support/specreview-channel and link to this PR.

/azp run

/azp run

/azp run

/azp run

Looks like this possibly breaking change could have impact on old versions, do you need to have this breaking change? Did you previously document that new enum values may be added in the future?

The new version is adding enum value(s) 'Standby' from the old version.
New: Microsoft.Sql/preview/2024-02-01-preview/Databases.json#L1747:9
Old: Microsoft.Sql/stable/2021-11-01/Databases.json#L1518:9

Please can you address ModelValidation and SemanticValidation errors

Looks like this possibly breaking change could have impact on old versions, do you need to have this breaking change? Did you previously document that new enum values may be added in the future?

The new version is adding enum value(s) 'Standby' from the old version.
New: Microsoft.Sql/preview/2024-02-01-preview/Databases.json#L1747:9
Old: Microsoft.Sql/stable/2021-11-01/Databases.json#L1518:9

I'm a bit confused by this, my diff doesn't change the 'secondaryType' enum or deal with geosecondaries at all. Our control plane folks mentioned that changes in this file often create breaking changes for us, is it possible this is a mistake in the automation?

Looks like this possibly breaking change could have impact on old versions, do you need to have this breaking change? Did you previously document that new enum values may be added in the future?

The new version is adding enum value(s) 'Standby' from the old version.
New: Microsoft.Sql/preview/2024-02-01-preview/Databases.json#L1747:9
Old: Microsoft.Sql/stable/2021-11-01/Databases.json#L1518:9

I'm a bit confused by this, my diff doesn't change the 'secondaryType' enum or deal with geosecondaries at all. Our control plane folks mentioned that changes in this file often create breaking changes for us, is it possible this is a mistake in the automation?

It looks like this breaking change has already been approved in this PR: https://github.com/Azure/azure-rest-api-specs/pull/27828/checks?check_run_id=21749239385


snapshot validate does not validate snapshots independently

Describe the bug
The forest-tool snapshot validate [FILES]... does not seem to validate the snapshots independently. It may be by design, but it's a pretty unexpected behaviour and should be either mitigated functionally (by validating each snapshot independently and failing the command if one of them is corrupted) or by having a separate subcommand for validating a union of snapshots.
To Reproduce Steps to reproduce the behavior:

Download a snapshot that is missing a genesis block. You can find one here
Download any valid snapshot.
Run forest-tool snapshot validate --check-network calibnet forest_snapshot_calibnet_2023-08-21_height_842289.forest.car.zst. You should see:

  Checking IPLD integrity:       ✅ verified!
  Identifying genesis block:     ❌ No valid genesis block!                                                                                Error: Snapshot does not contain a genesis block

Run `forest-tool snapshot validate --check-network calibnet

❯ forest-tool snapshot validate --check-network calibnet forest_snapshot_calibnet_2023-08-21_height_842529.forest.car.zst
  Checking IPLD integrity:       ✅ verified!
  Identifying genesis block:     ✅ found!                                                                                Verifying network identity:    ✅ verified!
  Running tipset transactions:   ✅ verified!                                                                                Snapshot is valid

Run the same with both snapshots as positional arguments:

❯ forest-tool snapshot validate --check-network calibnet forest_snapshot_calibnet_2023-08-21_height_842289.forest.car.zst forest_snapshot_calibnet_2023-08-21_height_842529.forest.car.zst
  Checking IPLD integrity:       ✅ verified!
  Identifying genesis block:     ✅ found!                                                                                Verifying network identity:    ✅ verified!
  Running tipset transactions:   ✅ verified!                                                                                Snapshot is valid

Expected behaviour
This snapshot validate <multiple files>... should fail if any file is corrupt. If we want to validate a union, there should be a separate subcommand, e.g., snapshot validate-union.
Screenshots

Environment (please complete the following information):

OS: Linux Fedora 38
Branch/commit a2a800e

Other information and links

The reason for the above is that we are using ManyCar::open for the validate command, which is loading all the files as a union.
Perhaps it's best to convert this command to something that either:

Takes exactly one snapshot as an argument.
Allows for validating each snapshot independently in some sort of loop.
Does 2 and has a union argument for union validation.

Having a separate command for union would probably be more obvious, even if it points
to the same code under the hood, just a different branch of it.

Solution: Rename the validate command to validate-diffs and add a new validate command that checks each file separately.


Add managementpartner/resource-manager/readme.typescript.md

Autogenerated

Automation for azure-sdk-for-python

Automation for azure-sdk-for-node

Automation for azure-sdk-for-go


VideoBaseTexture fixes and changes

https://github.com/pixijs/pixi.js/commit/8d39e810c595b0afc48e542b2d4cad9c204cc7d2 didn't fully solve the video loading issues; the examples page for videos still doesn't work. I've tracked that down to the static 'fromUrl' function, which called video.play(). This was a tad early, resulting in width and height being 0. Removing the .play here doesn't matter, as it is still automatically called within _onCanPlay()

autoUpdate changed to a getter/setter. It's doc states that it could be used to control when auto updating happened, but this wasn't true, it was actually just an internal variable to check whether it was currently auto updating or not. I've create a couple of private tracking variable for this state, whilst the public getter / setting now truly controls autoUpdate as per docs, and can be changed on the fly.

moved this class to use the ticker. My expectation as a dev is that if I stop the shared ticker, PIXI would stop anything internal requiring timing, but VideoBaseTexture was an exception as it used rAF directly.

autoUpdate changed to a getter/setter. It's doc states that it could be used to control when auto updating happened, but this wasn't true

It checked the flag in the update loop. If you set it to false, the update loop would stop (since it was using requestAnimationFrame from within the flag check. Having the getter/setter now is important that you use shared ticker.

But the original flag couldn't be used to control the autoPlay functionality. You could only use it to control autoPlay after canplay from the video was emitted, as that would turn on then autoplaying flag no matter what. The change in the pr means you can control that functionality straight after the base texture creation.