CI Failure: Missing command interfaces

Our humble CI currently fails. During execution tests, the hardware interface dies due to the following exception:
[ur_ros2_control_node-3] [INFO] [1680755341.288273949] [resource_manager]: Loading hardware 'ur5e'
[ur_ros2_control_node-3] [INFO] [1680755341.295206915] [resource_manager]: Initialize hardware 'ur5e'
[ur_ros2_control_node-3] [INFO] [1680755341.295287715] [resource_manager]: Successful initialization of hardware 'ur5e'
[ur_ros2_control_node-3] terminate called after throwing an instance of 'std::runtime_error'
[ur_ros2_control_node-3]   what():  Wrong state or command interface configuration.
[ur_ros2_control_node-3] missing state interfaces:
[ur_ros2_control_node-3]
[ur_ros2_control_node-3] missing command interfaces:
[ur_ros2_control_node-3] ' gpio/tool_voltage_cmd '	' zero_ftsensor/zero_ftsensor_cmd '	' zero_ftsensor/zero_ftsensor_async_success '
[dashboard_client-4] [INFO] [1680755341.260516185] [UR_Client_Library]: Connected: Universal Robots Dashboard Server
[dashboard_client-4]
[controller_stopper_node-5] [INFO] [1680755341.303615095] [Controller stopper]: Waiting for switch controller service to come up on controller_manager/switch_controller
[ERROR] [ur_ros2_control_node-3]: process has died [pid 18199, exit code -6, cmd '/root/target_ws/install/ur_robot_driver/lib/ur_robot_driver/ur_ros2_control_node --ros-args --params-file /tmp/launch_params_djvvmchi --params-file /root/target_ws/install/ur_robot_driver/share/ur_robot_driver/config/ur5e_update_rate.yaml --params-file /root/target_ws/install/ur_robot_driver/share/ur_robot_driver/config/ur_controllers.yaml'].

This only occurs on testing, not on main. This seems related to https://github.com/ros-controls/ros2_control/pull/953, which is now part of ros2_control 2.0.25.

See https://github.com/UniversalRobots/Universal_Robots_ROS2_Driver/pull/582

This should be fixed now. The README doesn't reflect this, yet, since we show scheduled builds there, only. However, head of the humble branch seems to build (and test) fine atm, hence closing this.


[SVE] Support splitting by vscale in tir::split and te::split

This commit adds support for splitting via the compile-time unknown constant vscale. Two main changes are introduced; they are described below.
The split scheduling primitive has a new parameter disable_predication that allows the user to avoid introducing a block-level predicate when splitting with a factor of vscale. This feature is useful when schedule writers know that the loop they're splitting is a factor of the scalable vector length for their target. Otherwise, a predicate must be introduced due to the nature of vscale.
CanProve has been extended to prove expressions that use multiple instances of vscale. Known possible scalar values of the vscale intrinsic are iterated over and substituted into the expression. If the expression holds true for each possible value, we can conclude the expression true. Currently only support for an SVE target has been added, but it is possible to extend to other targets as/when needed. If the analyzer becomes more powerful in the future and is able to deal with multiple instances of a symbolic value in an expression, this feature can be removed.
Co-authored-by: Elen Kalda<EMAIL_ADDRESS>Co-authored-by: Neil Hickey<EMAIL_ADDRESS>

cc @ekalda @Lunderberg @cbalint13 @Anndrey24 @tqchen

Thanks @lhutton1 :)


Prepare attachments viewer: Add MXKAttachment class.

I consider this default value may be useful in the future...

ok. LGTM


Release 3.0.0 into main

stellar-disbursement-platform-frontend-preview is available here:http://sdp-frontend-pr192.previews.kube001.services.stellar-ops.com/


"UNAVAILABLE:upstream request timeout" when trying Helloworld sample app

Issue description
I followed the tutorial almost exactly (the only divergence is discussed below). After installing the Apigee adapter I got UNAVAILABLE:upstream request timeout error when curling helloworld with the API Key.
I looked into the logs of the adapter and the mixers. The apigee-adapter log has entries like this

2019-06-01T22:39:15.061388Z debug   adapters    Authenticate success: …

It also shows the correct API product and app names from Apigee.
The mixer container in the istio-policy pod logs:

Environment and Versions
Google Cloud GKE version: 1.12.7-gke.10
Istio version: Tried on both 1.1.5 and 1.1.7, installed through helm and found the same timeout error. The above logs were from 1.1.5
Apigee-adapter version: 1.1.3
Steps to reproduce
Follow the tutorial.
Divergence: When creating the API product, I couldn't find Custom resources as described in the tutorial. There is only API resources, where I added the istio-auth proxy and the / path as the tutorial says.

Thanks for the report. Have you taken a look through the debugging information here? https://github.com/apigee/istio-mixer-adapter/wiki/Debug-Authorization-check-in-Istio-1.1.x

I ran through these checks and here are the results:

$ kubectl get pod
NAME                             READY   STATUS    RESTARTS   AGE
helloworld-v1-7b984f4489-9w5fj   2/2     Running   0          9d

$ kubectl -n istio-system get pods -l chart=mixer
NAME                               READY   STATUS    RESTARTS   AGE
istio-policy-77785c98c5-xbgzw      2/2     Running   0          28h
istio-telemetry-844f4f6dc9-57gqs   2/2     Running   0          28h

$ kubectl -n istio-system get cm istio -o<EMAIL_ADDRESS>| grep disablePolicyChecks
disablePolicyChecks: false

$ kubectl -n istio-system logs kubectl -n istio-system get po -l istio-mixer-type=policy -o 'jsonpath={.items[0].metadata.name}'; mixer | grep error
2019-06-02T15:15:38.287042Z     info    transport: loopyWriter.run returning. connection error: desc = "transport is closing"
2019-06-02T15:15:38.289055Z     info    grpc: addrConn.createTransport failed to connect to {apigee-adapter:5000 0  }. Err :connection error: desc = "transport: Error while dialing dial tcp <IP_ADDRESS>:5000: connect: connection refused". Reconnecting...
2019-06-02T15:15:59.287816Z     info    grpc: addrConn.createTransport failed to connect to {apigee-adapter:5000 0  }. Err :connection error: desc = "transport: Error while dialing dial tcp <IP_ADDRESS>:5000: i/o timeout". Reconnecting...
2019-06-02T15:17:28.415094Z     info    transport: loopyWriter.run returning. connection error: desc = "transport is closing"
2019-06-02T15:17:38.416981Z     error   adapters        adapter did not close all the scheduled daemons {"adapter": "prometheus.istio-system"}
2019-06-02T15:18:59.521247Z     error   api     Check failed: performing check operation failed: 1 error occurred:
* rpc error: code = Canceled desc = context canceled
2019-06-02T15:19:04.589133Z     error   api     Check failed: performing check operation failed: 1 error occurred:
* rpc error: code = DeadlineExceeded desc = context deadline exceeded
2019-06-02T15:21:36.121447Z     error   api     Check failed: performing check operation failed: 1 error occurred:
* rpc error: code = Canceled desc = context canceled
2019-06-02T15:21:41.127010Z     error   api     Check failed: performing check operation failed: 1 error occurred:
* rpc error: code = DeadlineExceeded desc = context deadline exceeded
2019-06-02T15:21:46.182563Z     error   api     Check failed: performing check operation failed: 1 error occurred:
* rpc error: code = DeadlineExceeded desc = context deadline exceeded
2019-06-02T15:24:26.417795Z     info    transport: loopyWriter.run returning. connection error: desc = "transport is closing"
2019-06-03T13:20:30.517511Z     info    transport: loopyWriter.run returning. connection error: desc = "transport is closing"
2019-06-03T13:21:58.458724Z     error   api     Check failed: performing check operation failed: 1 error occurred:
* rpc error: code = DeadlineExceeded desc = context deadline exceeded
2019-06-03T20:21:21.106668Z     error   api     Check failed: performing check operation failed: 1 error occurred:
* rpc error: code = DeadlineExceeded desc = context deadline exceeded
2019-06-03T20:21:26.111773Z     error   api     Check failed: performing check operation failed: 1 error occurred:
* rpc error: code = DeadlineExceeded desc = context deadline exceeded
2019-06-03T20:21:31.181124Z     error   api     Check failed: performing check operation failed: 1 error occurred:
* rpc error: code = DeadlineExceeded desc = context deadline exceeded

Note here the last 6 lines starting at 2019-06-03T20:21:21 are from a recent curl I made.

$ kubectl -n istio-system get svc -l app=apigee-adapter
NAME             TYPE        CLUSTER-IP     EXTERNAL-IP   PORT(S)    AGE
apigee-adapter   ClusterIP   <IP_ADDRESS>           5000/TCP   9d

$ kubectl -n istio-system get po -l app=apigee-adapter
NAME                              READY   STATUS    RESTARTS   AGE
apigee-adapter-7b4f47f6db-5kchl   1/1     Running   0          29h

$ kubectl -n istio-system get handler apigee-handler -o custom-columns=KIND:.kind,NAME:.metadata.name,ADAPTER:.spec.adapter
KIND      NAME             ADAPTER
handler   apigee-handler   apigee

$ kubectl -n istio-system get rule apigee-rule -o custom-columns=MATCH:.spec.match
MATCH
context.reporter.kind == "inbound" && destination.namespace == "default"

A few other things I tried from Debug 404 error:

Accessing from pod's sidecar:

$ kubectl exec $WORKLOAD_POD -c istio-proxy -- curl localhost:5000/hello
% Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
Dload  Upload   Total   Spent    Left  Speed
0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0Hello version: v1, instance: helloworld-v1-7b984f4489-9w5fj
100    60  100    60    0     0    429      0 --:--:-- --:--:-- --:--:--   431

Accessging from backend sidecar

$ kubectl exec $WORKLOAD_POD -c istio-proxy -- curl -v http://helloworld.default.svc.cluster.local:5000/hello -H "x-api-key: $API_KEY" --resolve
"helloworld.default.svc.cluster.local:5000:$POD_IP"
* Added helloworld.default.svc.cluster.local:5000:<IP_ADDRESS> to DNS cache
* Hostname helloworld.default.svc.cluster.local was found in DNS cache
*   Trying <IP_ADDRESS>...
% Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
Dload  Upload   Total   Spent    Left  Speed
0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0* Connected to helloworld.default.svc.cluster.local (<IP_ADDRESS>) port 5000 (#0)
> GET /hello HTTP/1.1
> Host: helloworld.default.svc.cluster.local:5000
> User-Agent: curl/7.47.0
> Accept: */*
> x-api-key: THE_API_KEY
>
0     0    0     0    0     0      0      0 --:--:--  0:00:04 --:--:--     0< UNAVAILABLE:upstream request timeoutHTTP/1.1 503 Service Unavailable
< content-length: 36
< content-type: text/plain
< date: Mon, 03 Jun 2019 20:59:33 GMT
< server: istio-envoy
< x-envoy-decorator-operation: helloworld.default.svc.cluster.local:5000/*
<
{ [36 bytes data]
100    36  100    36    0     0      7      0  0:00:05  0:00:05 --:--:--     7
* Connection #0 to host helloworld.default.svc.cluster.local left intact

Do you see anything in the apigee-adapter logs?
kubectl -n istio-system log $(kubectl -n istio-system get po -l app=apigee-adapter -o 'jsonpath={.items[0].metadata.name}')

It has this log associated with the curl.
2019-06-03T23:24:59.708351Z	debug	adapters	HandleAuthorization: &InstanceMsg{Subject:&SubjectMsg{User:,Groups:,Properties:map[string]*istio_policy_v1beta11.Value{api_key: &Value{Value:&Value_StringValue{StringValue:<THE_API_KEY>,},},json_claims: &Value{Value:&Value_StringValue{StringValue:,},},},},Action:&ActionMsg{Namespace:default,Service:helloworld.default.svc.cluster.local,Method:GET,Path:/hello,Properties:map[string]*istio_policy_v1beta11.Value{},},Name:apigee-authorization.instance.istio-system,}	{"adapter": "ncrlabs~dev"}
2019-06-03T23:24:59.708450Z	debug	adapters	HandleAuthorization: Subject: authorization.Subject{User:"", Groups:"", Properties:map[string]interface {}{"api_key":"FWzF2...", "json_claims":""}}, Action: authorization.Action{Namespace:"default", Service:"helloworld.default.svc.cluster.local", Method:"GET", Path:"/hello", Properties:map[string]interface {}{}}	{"adapter": "ncrlabs~dev"}
2019-06-03T23:24:59.708462Z	debug	adapters	Authenticate: key: FWzF2..., claims: map[string]interface {}{}	{"adapter": "ncrlabs~dev"}
2019-06-03T23:24:59.708801Z	debug	adapters	using api key from request	{"adapter": "ncrlabs~dev"}
2019-06-03T23:24:59.708887Z	debug	adapters	Authenticate success: &{0xc0001f9a40 FWzF2...  hello-istio-app [hello-istio-product] 2019-06-03 23:36:33 +0000 UTC  [] FWzF2...}	{"adapter": "ncrlabs~dev"}
2019-06-03T23:25:04.731803Z	debug	adapters	HandleAuthorization: &InstanceMsg{Subject:&SubjectMsg{User:,Groups:,Properties:map[string]*istio_policy_v1beta11.Value{api_key: &Value{Value:&Value_StringValue{StringValue:<THE_API_KEY>,},},json_claims: &Value{Value:&Value_StringValue{StringValue:,},},},},Action:&ActionMsg{Namespace:default,Service:helloworld.default.svc.cluster.local,Method:GET,Path:/hello,Properties:map[string]*istio_policy_v1beta11.Value{},},Name:apigee-authorization.instance.istio-system,}	{"adapter": "ncrlabs~dev"}
2019-06-03T23:25:04.732029Z	debug	adapters	HandleAuthorization: Subject: authorization.Subject{User:"", Groups:"", Properties:map[string]interface {}{"json_claims":"", "api_key":"FWzF2..."}}, Action: authorization.Action{Namespace:"default", Service:"helloworld.default.svc.cluster.local", Method:"GET", Path:"/hello", Properties:map[string]interface {}{}}	{"adapter": "ncrlabs~dev"}
2019-06-03T23:25:04.732059Z	debug	adapters	Authenticate: key: FWzF2..., claims: map[string]interface {}{}	{"adapter": "ncrlabs~dev"}
2019-06-03T23:25:04.732329Z	debug	adapters	using api key from request	{"adapter": "ncrlabs~dev"}
2019-06-03T23:25:04.732505Z	debug	adapters	Authenticate success: &{0xc0001f9a40 FWzF2...  hello-istio-app [hello-istio-product] 2019-06-03 23:36:33 +0000 UTC  [] FWzF2...}	{"adapter": "ncrlabs~dev"}
2019-06-03T23:25:05.709623Z	debug	adapters	HandleAnalytics: [&InstanceMsg{ApiProxy:helloworld.default.svc.cluster.local,ResponseStatusCode:503,ClientIp:&v1beta1.IPAddress{Value:[0 0 0 0 0 0 0 0 0 0 255 255 10 32 2 123],},RequestVerb:GET,RequestUri:/hello,RequestPath:,Useragent:curl/7.58.0,ClientReceivedStartTimestamp:&v1beta1.TimeStamp{Value:2019-06-03T23:24:59.705691415Z,},ClientReceivedEndTimestamp:&v1beta1.TimeStamp{Value:2019-06-03T23:24:59.705691415Z,},ClientSentStartTimestamp:&v1beta1.TimeStamp{Value:2019-06-03T23:25:04.706293766Z,},ClientSentEndTimestamp:&v1beta1.TimeStamp{Value:2019-06-03T23:25:04.706293766Z,},TargetSentStartTimestamp:&v1beta1.TimeStamp{Value:2019-06-03T23:24:59.705691415Z,},TargetSentEndTimestamp:&v1beta1.TimeStamp{Value:2019-06-03T23:24:59.705691415Z,},TargetReceivedStartTimestamp:&v1beta1.TimeStamp{Value:2019-06-03T23:25:04.706293766Z,},TargetReceivedEndTimestamp:&v1beta1.TimeStamp{Value:2019-06-03T23:25:04.706293766Z,},ApiClaims:map[string]string{json_claims: ,},ApiKey:<THE_API_KEY>,Name:apigee-analytics.instance.istio-system,}]	{"adapter": "ncrlabs~dev"}
2019-06-03T23:25:05.709717Z	debug	adapters	HandleAnalytics: 1 instances	{"adapter": "ncrlabs~dev"}
2019-06-03T23:25:05.709766Z	debug	adapters	Authenticate: key: FWzF2..., claims: map[string]interface {}{}	{"adapter": "ncrlabs~dev"}
2019-06-03T23:25:05.710456Z	debug	adapters	using api key from request	{"adapter": "ncrlabs~dev"}
2019-06-03T23:25:05.710536Z	debug	adapters	Authenticate success: &{0xc0001f9a40 FWzF2...  hello-istio-app [hello-istio-product] 2019-06-03 23:36:33 +0000 UTC  [] FWzF2...}	{"adapter": "ncrlabs~dev"}
2019-06-03T23:25:05.710996Z	debug	adapters	new bucket created: /tmp/apigee-istio/analytics/ncrlabs/dev/temp/ncrlabs~dev/1559604305-749020971	{"adapter": "ncrlabs~dev"}
2019-06-03T23:25:05.711795Z	debug	adapters	1 records written to /tmp/apigee-istio/analytics/ncrlabs/dev/temp/ncrlabs~dev/1559604305-749020971	{"adapter": "ncrlabs~dev"}
2019-06-03T23:25:09.748680Z	debug	adapters	HandleAuthorization: &InstanceMsg{Subject:&SubjectMsg{User:,Groups:,Properties:map[string]*istio_policy_v1beta11.Value{api_key: &Value{Value:&Value_StringValue{StringValue:<THE_API_KEY>,},},json_claims: &Value{Value:&Value_StringValue{StringValue:,},},},},Action:&ActionMsg{Namespace:default,Service:helloworld.default.svc.cluster.local,Method:GET,Path:/hello,Properties:map[string]*istio_policy_v1beta11.Value{},},Name:apigee-authorization.instance.istio-system,}	{"adapter": "ncrlabs~dev"}
2019-06-03T23:25:09.748884Z	debug	adapters	HandleAuthorization: Subject: authorization.Subject{User:"", Groups:"", Properties:map[string]interface {}{"api_key":"FWzF2...", "json_claims":""}}, Action: authorization.Action{Namespace:"default", Service:"helloworld.default.svc.cluster.local", Method:"GET", Path:"/hello", Properties:map[string]interface {}{}}	{"adapter": "ncrlabs~dev"}
2019-06-03T23:25:09.748923Z	debug	adapters	Authenticate: key: FWzF2..., claims: map[string]interface {}{}	{"adapter": "ncrlabs~dev"}
2019-06-03T23:25:09.749212Z	debug	adapters	using api key from request	{"adapter": "ncrlabs~dev"}
2019-06-03T23:25:09.749350Z	debug	adapters	Authenticate success: &{0xc0001f9a40 FWzF2...  hello-istio-app [hello-istio-product] 2019-06-03 23:36:33 +0000 UTC  [] FWzF2...}	{"adapter": "ncrlabs~dev"}
2019-06-03T23:25:10.732370Z	debug	adapters	HandleAnalytics: [&InstanceMsg{ApiProxy:helloworld.default.svc.cluster.local,ResponseStatusCode:503,ClientIp:&v1beta1.IPAddress{Value:[0 0 0 0 0 0 0 0 0 0 255 255 10 32 2 123],},RequestVerb:GET,RequestUri:/hello,RequestPath:,Useragent:curl/7.58.0,ClientReceivedStartTimestamp:&v1beta1.TimeStamp{Value:2019-06-03T23:25:04.729572118Z,},ClientReceivedEndTimestamp:&v1beta1.TimeStamp{Value:2019-06-03T23:25:04.729572118Z,},ClientSentStartTimestamp:&v1beta1.TimeStamp{Value:2019-06-03T23:25:09.729405666Z,},ClientSentEndTimestamp:&v1beta1.TimeStamp{Value:2019-06-03T23:25:09.729405666Z,},TargetSentStartTimestamp:&v1beta1.TimeStamp{Value:2019-06-03T23:25:04.729572118Z,},TargetSentEndTimestamp:&v1beta1.TimeStamp{Value:2019-06-03T23:25:04.729572118Z,},TargetReceivedStartTimestamp:&v1beta1.TimeStamp{Value:2019-06-03T23:25:09.729405666Z,},TargetReceivedEndTimestamp:&v1beta1.TimeStamp{Value:2019-06-03T23:25:09.729405666Z,},ApiClaims:map[string]string{json_claims: ,},ApiKey:<THE_API_KEY>,Name:apigee-analytics.instance.istio-system,}]	{"adapter": "ncrlabs~dev"}
2019-06-03T23:25:10.732529Z	debug	adapters	HandleAnalytics: 1 instances	{"adapter": "ncrlabs~dev"}
2019-06-03T23:25:10.732557Z	debug	adapters	Authenticate: key: FWzF2..., claims: map[string]interface {}{}	{"adapter": "ncrlabs~dev"}
2019-06-03T23:25:10.732742Z	debug	adapters	using api key from request	{"adapter": "ncrlabs~dev"}
2019-06-03T23:25:10.732850Z	debug	adapters	Authenticate success: &{0xc0001f9a40 FWzF2...  hello-istio-app [hello-istio-product] 2019-06-03 23:36:33 +0000 UTC  [] FWzF2...}	{"adapter": "ncrlabs~dev"}
2019-06-03T23:25:10.733521Z	debug	adapters	1 records written to /tmp/apigee-istio/analytics/ncrlabs/dev/temp/ncrlabs~dev/1559604305-749020971	{"adapter": "ncrlabs~dev"}
2019-06-03T23:25:15.746881Z	debug	adapters	HandleAnalytics: [&InstanceMsg{ApiProxy:helloworld.default.svc.cluster.local,ResponseStatusCode:503,ClientIp:&v1beta1.IPAddress{Value:[0 0 0 0 0 0 0 0 0 0 255 255 10 32 2 123],},RequestVerb:GET,RequestUri:/hello,RequestPath:,Useragent:curl/7.58.0,ClientReceivedStartTimestamp:&v1beta1.TimeStamp{Value:2019-06-03T23:25:09.742385115Z,},ClientReceivedEndTimestamp:&v1beta1.TimeStamp{Value:2019-06-03T23:25:09.742385115Z,},ClientSentStartTimestamp:&v1beta1.TimeStamp{Value:2019-06-03T23:25:14.743136165Z,},ClientSentEndTimestamp:&v1beta1.TimeStamp{Value:2019-06-03T23:25:14.743136165Z,},TargetSentStartTimestamp:&v1beta1.TimeStamp{Value:2019-06-03T23:25:09.742385115Z,},TargetSentEndTimestamp:&v1beta1.TimeStamp{Value:2019-06-03T23:25:09.742385115Z,},TargetReceivedStartTimestamp:&v1beta1.TimeStamp{Value:2019-06-03T23:25:14.743136165Z,},TargetReceivedEndTimestamp:&v1beta1.TimeStamp{Value:2019-06-03T23:25:14.743136165Z,},ApiClaims:map[string]string{json_claims: ,},ApiKey:<THE_API_KEY>,Name:apigee-analytics.instance.istio-system,}]	{"adapter": "ncrlabs~dev"}
2019-06-03T23:25:15.747816Z	debug	adapters	HandleAnalytics: 1 instances	{"adapter": "ncrlabs~dev"}
2019-06-03T23:25:15.747910Z	debug	adapters	Authenticate: key: FWzF2..., claims: map[string]interface {}{}	{"adapter": "ncrlabs~dev"}
2019-06-03T23:25:15.748425Z	debug	adapters	using api key from request	{"adapter": "ncrlabs~dev"}
2019-06-03T23:25:15.748549Z	debug	adapters	Authenticate success: &{0xc0001f9a40 FWzF2...  hello-istio-app [hello-istio-product] 2019-06-03 23:36:33 +0000 UTC  [] FWzF2...}	{"adapter": "ncrlabs~dev"}
2019-06-03T23:25:15.748981Z	debug	adapters	1 records written to /tmp/apigee-istio/analytics/ncrlabs/dev/temp/ncrlabs~dev/1559604305-749020971	{"adapter": "ncrlabs~dev"}

(I have replace the API key with <THE_API_KEY> placeholder.)
It also generates this message every 2 min, independent of what I'm doing:
2019-06-03T23:24:34.327067Z	debug	adapters	Looper work running	{"adapter": "ncrlabs~dev"}
2019-06-03T23:24:34.327258Z	debug	adapters	retrieving products from: https://ncrlabs-dev.apigee.net/istio-auth/products	{"adapter": "ncrlabs~dev"}
2019-06-03T23:24:34.824506Z	error	adapters	unable to unmarshal JSON response '{… <followed by a super long json string>
2019-06-03T23:24:34.827157Z	error	adapters	Error retrieving products: invalid character '"' after array element	{"adapter": "ncrlabs~dev"}
2019-06-03T23:24:34.827192Z	debug	adapters	Looper work scheduled to run in 2m0s	{"adapter": "ncrlabs~dev"}

The third line here is followed by a super long json string which looks like a log of Apigee API product creation (who created what when).

Some updates:
In the istio-policy mixer log, right before the rpc error, there is a warning:
2019-06-01T22:39:19.659072Z	warn	grpcAdapter	unable to connect to:/authorization.HandleAuthorizationService/HandleAuthorization, apigee-adapter:5000
2019-06-01T22:39:19.659464Z	error	api	Check failed: performing check operation failed: 1 error occurred:

* rpc error: code = Canceled desc = context canceled

Hmm. The unable to unmarshal JSON response is concerning. It appears that an error in the JSON that you are receiving from https://ncrlabs-dev.apigee.net/istio-auth/products may be causing the issue. Can you check the JSON and/or share it with me?

Specifically, the JSON file has '"displayName": """"' in it that messed up the parsing.

Hmm. That's a bug of some kind. A product's displayName is required... What is yours? Is it just quotes? (Or do you have any idea how this might have gotten munged?)

Thanks! We start to work on that now.


Backstage Working Group - DevOps Automation - Feb 15, 2024

Date
Thursday, Feb 15, 2024 - 11am ET; 3pm UK
Untracked attendees

Name
Firm
Comment

Meeting notices

FINOS Project leads are responsible for observing the FINOS guidelines for running project meetings. Project maintainers can find additional resources in the FINOS Maintainers Cheatsheet.

All participants in FINOS project meetings are subject to the LF Antitrust Policy, the FINOS Community Code of Conduct and all other FINOS policies.

FINOS meetings involve participation by industry competitors, and it is the intention of FINOS and the Linux Foundation to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of, and not participate in, any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws. Please contact<EMAIL_ADDRESS>with any questions.

FINOS project meetings may be recorded for use solely by the FINOS team for administration purposes. In very limited instances, and with explicit approval, recordings may be made more widely available.

Agenda

[ ] Convene, roll call, welcome new people
[ ] Approve previous meeting minutes
[ ] Review DevOps SIG project board
[ ]
[ ] AOB, Q&A & Adjourn (5mins)

Decisions Made

[ ] Decision 1
[ ] Decision 2
[ ] ...

Action Items

[ ] Action 1
[ ] Action 2
[ ] ...

Zoom info
Join Zoom Meeting

https://zoom.us/j/94904595244
Meeting ID: 949 0459 5244
Passcode: 545224
Find your local number: https://zoom.us/u/aesEqmNODb

Github Repo: https://github.com/finos/devops-automation/
Project Board: https://github.com/orgs/finos/projects/33
Mailing List: Email<EMAIL_ADDRESS>to subscribe to our mailing list

Hello

Karl Moll / FINOS

Hi !
Mark Jorgensen - Morgan Stanley

Juan Flores / Fidelity Investments

Kris Borchers - GM Financial

Testing Templates with Dry-run
https://github.com/backstage/backstage/tree/master/contrib/scaffolder


Attempt to start services when required ring file exists

Attemp to start services only when service ring file exists. The error was hidden until following PR #1868 was merged.

@j2sol Updated PR per our discussion yesterday...


Adding typecasts, write(buf, len) and write(const char* buf)

I needed some typecases, write(const char*) and write(buf, len) to make it work for me. Could not get my code compiled without this.

Bugfix: Removed the matchBanner from read(). As it passed a &ch to a matchBanner (const char *buf, int len).
Also rewrote read and available in same style...


Including Boxed enums in "Literals" Section?

Was hoping to add the following convention for boxed enums (described here). I figure trying to create a dictionary with enums would require the use of numberWithInt: or numberWithInteger:, so this would align with the current conventions.
typedef NS_ENUM(NSInteger, NYTDaysOfTheWeek){
     NYTMonday = 0,
     NYTTuesday,
     NYTWednesday
};

NSDictionary * daysOfTheWeek = @{ @"monday" : @(NYTMonday),
                                 @"tuesday" : @(NYTTuesday),
                               @"wednesday" : @(NYTWednesday) };

I’m not sure I totally understand what you’re suggesting here @spacedrabbit. Mind making a PR to clarify?

Sure @mattbischoff, just added: https://github.com/NYTimes/objective-c-style-guide/pull/116


Any guidance on environment separation?

In a typical enterprise scenario, do you have separate gateway(s) for each environment?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 20c772b2-ccb1-a6dc-5bf6-a94e5cadc4d8
Version Independent ID: 8dd056db-f148-b0db-0ee9-044ab5c0dbbd
Content: Guidance for deploying a data gateway for Power BI - Power BI
Content Source: powerbi-docs/service-gateway-deployment-guidance.md
Service: powerbi
GitHub Login: @mgblythe
Microsoft Alias: mblythe

@cmeyertons - closing this out with answer from @arthiriyer. Feel free to reopen if necessary.


Consider removing the setting of PATH_DIRS from the completion module

Description
PATH_DIRS can make completion very slow depending on your PATH (>10s). It is instant without it, and the PATH_DIRS feature doesn't seem so great.
I observed this for a while in executable completions, and eventually I just did a commenting-out bisection on the completion module and tracked it down to PATH_DIRS. It seems there is some limited discussion of this on the zsh list.
Expected behavior
Executable completions are fast!
Actual behavior

Steps to Reproduce
I'm not entirely sure what about my PATH triggers this. Removing entries speeds it up, but it might also be something to do with the size of the parent directories, I'm not totally sure what PATH_DIRS does.
Versions

Prezto commit: e915c34507d3e47b8de320475f55c066d414ada2
ZSH version: 5.8
OS information:

Hi @michaelpj,
Does it help if you set the completion style accept-exact-dirs as mentioned here?
You can apply it as so:
zstyle ':completion:*:default' accept-exact-dirs true

I can't reproduce this any more! I accidentally wiped out my change to not set PATH_DIRS and I didn't even notice! So I really have not idea what's going on. Maybe one of the other people who thumbs-up-ed this can still reproduce?

I have this issue running in WSL2, it seems the expansion of Windows paths is taking forever. Setting the above option does not work. I wouldn't expect it to, because I am doing a very basic command completion, e.g. pyth<TAB> so there's no exact path here.
On the other hand, unsetopt PATH_DIRS fixes the issue, so yeah it would be great to have an option to disable it. I wouldn't remove it outright, I assume those that don't find it slow prefer for expanded search options for better results.
Weirdly enough, it seems to be the test whether a result is a directory (/ glob qualifier) that causes the slowness for me, but that's a discussion for zsh, not this repo.


ResourceLfTags clears all tags when running code twice

What happened?
I am using ResourceLfTags. I got strange behavior for it, when I run it at the first time all our tags created correctly but when this code run again, pulumi sees the difference (but we use the same tags without changes, pulumi must ignore this step) and remove all tags but are not create anyone (but in logs pulumi shows it like replacement), just clean up all tags.
My function looks like that:
const databaseLFTags = new aws.lakeformation.ResourceLfTags("databaseLfTags", {
            database: { name: databaseName },
            lfTags: lfTags
        }, { parent: this });

lfTags always the same something like that [{key: "foo", value: "123"}, {key: "env", value: "test"}]
Expected Behavior
When I run the code again and don't change the tags, pulumi should ignore this step. Or if new tags are added, then delete the existing ones and add only those that are present in lfTags.
Steps to reproduce
Run twice
const databaseLFTags = new aws.lakeformation.ResourceLfTags("databaseLfTags", {
            database: { name: databaseName },
            lfTags:  [{key: "foo", value: "123"}, {key: "env", value: "test"}]
        }, { parent: this });

Output of pulumi about

Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

Hi @sdostanko - thank you for filing this issue.
In order to help us root cause this, can you please provide us with a program containing a minimum reproduction that we can run on our end?
In addition, can you tell us:

what version of pulumi you are using?
what version of the AWS provider you are using?

A general note: it may be that you're running into something related to this upstream bug - even though that particular bug was closed, it is possible that there are unintended side effects on our end.

I am using 3.75.0 pulumi version and aws-cli 2.4.18, Ubuntu 20.04 LTS.

@sdostanko would you be able to provide us a complete, minimal program to run which demonstrates your issue?
This could either be pasted in a comment or be a link to a repo. Thanks!

Closing as stale.


how to open the csv data it extracts?

Please tell me how to use the csv file after extracting it

You can open it in Notepad or import it into Excel.

Right click
Open with
Microsoft Excel

Cheers!

Thanks for the reply but i guess i addressed my issue in an incorrect way
,actually what i meant was that when i open it in excel it shows name
,status and [Object] in place of other data.
On Sun, Feb 3, 2019 at 11:40 AM AdamSmith1020<EMAIL_ADDRESS>wrote:

Right click
Open with
Microsoft Excel

Cheers!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/LoranKloeze/WhatsAllApp/issues/59#issuecomment-460026303,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AZR4L0xIlvGMHuzMcsiklghk6MHA6ExUks5vJn1VgaJpZM4afiz3
.

Can you post a few rows from the csv?

Here is an example
On Sun, Feb 3, 2019 at 7:48 PM Loran Kloeze<EMAIL_ADDRESS>wrote:

Can you post a few rows from the csv?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/LoranKloeze/WhatsAllApp/issues/59#issuecomment-460055550,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AZR4L0Xa_HT76Zb2hD54tfzOXMnnOyMWks5vJu-mgaJpZM4afiz3
.

I don't see anything?


Feature Request: Tab close functionalities

This issue pertains to the following package(s):

[x] GraphQL Playground - Electron App
[x] GraphQL Playground HTML
[x] GraphQL Playground

Feature Request
Would be awesome to have a little context menu on a tab with the following functionalities:

Close Others
Close to the Right

Yep, when there are lots of tabs (and there are always lots of tabs) it will be really handy, I was going to create same issue

Is that possible to send request after close the window tab.
I want to implement after close tab and send graphql request for change user status.
Please help for this.
Thanks,


fix readthedocs errors

Fixed by import sphinx.util.logging to log info and warnings
Error:
Traceback (most recent call last):
  File "/home/docs/checkouts/readthedocs.org/user_builds/cloudlib4zvm/envs/latest/lib/python3.6/site-packages/sphinx/cmd/build.py", line 281, in build_main
    app.build(args.force_all, args.filenames)
  File "/home/docs/checkouts/readthedocs.org/user_builds/cloudlib4zvm/envs/latest/lib/python3.6/site-packages/sphinx/application.py", line 347, in build
    self.builder.build_update()
  File "/home/docs/checkouts/readthedocs.org/user_builds/cloudlib4zvm/envs/latest/lib/python3.6/site-packages/sphinx/builders/__init__.py", line 312, in build_update
    len(to_build))
  File "/home/docs/checkouts/readthedocs.org/user_builds/cloudlib4zvm/envs/latest/lib/python3.6/site-packages/sphinx/builders/__init__.py", line 326, in build
    updated_docnames = set(self.read())
  File "/home/docs/checkouts/readthedocs.org/user_builds/cloudlib4zvm/envs/latest/lib/python3.6/site-packages/sphinx/builders/__init__.py", line 433, in read
    self._read_serial(docnames)
  File "/home/docs/checkouts/readthedocs.org/user_builds/cloudlib4zvm/envs/latest/lib/python3.6/site-packages/sphinx/builders/__init__.py", line 454, in _read_serial
    self.read_doc(docname)
  File "/home/docs/checkouts/readthedocs.org/user_builds/cloudlib4zvm/envs/latest/lib/python3.6/site-packages/sphinx/builders/__init__.py", line 510, in read_doc
    publisher.publish()
  File "/home/docs/checkouts/readthedocs.org/user_builds/cloudlib4zvm/envs/latest/lib/python3.6/site-packages/docutils/core.py", line 218, in publish
    self.settings)
  File "/home/docs/checkouts/readthedocs.org/user_builds/cloudlib4zvm/envs/latest/lib/python3.6/site-packages/sphinx/io.py", line 104, in read
    self.parse()
  File "/home/docs/checkouts/readthedocs.org/user_builds/cloudlib4zvm/envs/latest/lib/python3.6/site-packages/docutils/readers/__init__.py", line 78, in parse
    self.parser.parse(self.input, document)
  File "/home/docs/checkouts/readthedocs.org/user_builds/cloudlib4zvm/envs/latest/lib/python3.6/site-packages/sphinx/parsers.py", line 78, in parse
    self.statemachine.run(inputlines, document, inliner=self.inliner)
  File "/home/docs/checkouts/readthedocs.org/user_builds/cloudlib4zvm/envs/latest/lib/python3.6/site-packages/docutils/parsers/rst/states.py", line 171, in run
    input_source=document['source'])
  File "/home/docs/checkouts/readthedocs.org/user_builds/cloudlib4zvm/envs/latest/lib/python3.6/site-packages/docutils/statemachine.py", line 241, in run
    context, state, transitions)
  File "/home/docs/checkouts/readthedocs.org/user_builds/cloudlib4zvm/envs/latest/lib/python3.6/site-packages/docutils/statemachine.py", line 452, in check_line
    return method(match, context, next_state)
  File "/home/docs/checkouts/readthedocs.org/user_builds/cloudlib4zvm/envs/latest/lib/python3.6/site-packages/docutils/parsers/rst/states.py", line 2779, in underline
    self.section(title, source, style, lineno - 1, messages)
  File "/home/docs/checkouts/readthedocs.org/user_builds/cloudlib4zvm/envs/latest/lib/python3.6/site-packages/docutils/parsers/rst/states.py", line 327, in section
    self.new_subsection(title, lineno, messages)
  File "/home/docs/checkouts/readthedocs.org/user_builds/cloudlib4zvm/envs/latest/lib/python3.6/site-packages/docutils/parsers/rst/states.py", line 395, in new_subsection
    node=section_node, match_titles=True)
  File "/home/docs/checkouts/readthedocs.org/user_builds/cloudlib4zvm/envs/latest/lib/python3.6/site-packages/docutils/parsers/rst/states.py", line 282, in nested_parse
    node=node, match_titles=match_titles)
  File "/home/docs/checkouts/readthedocs.org/user_builds/cloudlib4zvm/envs/latest/lib/python3.6/site-packages/docutils/parsers/rst/states.py", line 196, in run
    results = StateMachineWS.run(self, input_lines, input_offset)
  File "/home/docs/checkouts/readthedocs.org/user_builds/cloudlib4zvm/envs/latest/lib/python3.6/site-packages/docutils/statemachine.py", line 241, in run
    context, state, transitions)
  File "/home/docs/checkouts/readthedocs.org/user_builds/cloudlib4zvm/envs/latest/lib/python3.6/site-packages/docutils/statemachine.py", line 452, in check_line
    return method(match, context, next_state)
  File "/home/docs/checkouts/readthedocs.org/user_builds/cloudlib4zvm/envs/latest/lib/python3.6/site-packages/docutils/parsers/rst/states.py", line 2779, in underline
    self.section(title, source, style, lineno - 1, messages)
  File "/home/docs/checkouts/readthedocs.org/user_builds/cloudlib4zvm/envs/latest/lib/python3.6/site-packages/docutils/parsers/rst/states.py", line 327, in section
    self.new_subsection(title, lineno, messages)
  File "/home/docs/checkouts/readthedocs.org/user_builds/cloudlib4zvm/envs/latest/lib/python3.6/site-packages/docutils/parsers/rst/states.py", line 395, in new_subsection
    node=section_node, match_titles=True)
  File "/home/docs/checkouts/readthedocs.org/user_builds/cloudlib4zvm/envs/latest/lib/python3.6/site-packages/docutils/parsers/rst/states.py", line 282, in nested_parse
    node=node, match_titles=match_titles)
  File "/home/docs/checkouts/readthedocs.org/user_builds/cloudlib4zvm/envs/latest/lib/python3.6/site-packages/docutils/parsers/rst/states.py", line 196, in run
    results = StateMachineWS.run(self, input_lines, input_offset)
  File "/home/docs/checkouts/readthedocs.org/user_builds/cloudlib4zvm/envs/latest/lib/python3.6/site-packages/docutils/statemachine.py", line 241, in run
    context, state, transitions)
  File "/home/docs/checkouts/readthedocs.org/user_builds/cloudlib4zvm/envs/latest/lib/python3.6/site-packages/docutils/statemachine.py", line 452, in check_line
    return method(match, context, next_state)
  File "/home/docs/checkouts/readthedocs.org/user_builds/cloudlib4zvm/envs/latest/lib/python3.6/site-packages/docutils/parsers/rst/states.py", line 2779, in underline
    self.section(title, source, style, lineno - 1, messages)
  File "/home/docs/checkouts/readthedocs.org/user_builds/cloudlib4zvm/envs/latest/lib/python3.6/site-packages/docutils/parsers/rst/states.py", line 327, in section
    self.new_subsection(title, lineno, messages)
  File "/home/docs/checkouts/readthedocs.org/user_builds/cloudlib4zvm/envs/latest/lib/python3.6/site-packages/docutils/parsers/rst/states.py", line 395, in new_subsection
    node=section_node, match_titles=True)
  File "/home/docs/checkouts/readthedocs.org/user_builds/cloudlib4zvm/envs/latest/lib/python3.6/site-packages/docutils/parsers/rst/states.py", line 282, in nested_parse
    node=node, match_titles=match_titles)
  File "/home/docs/checkouts/readthedocs.org/user_builds/cloudlib4zvm/envs/latest/lib/python3.6/site-packages/docutils/parsers/rst/states.py", line 196, in run
    results = StateMachineWS.run(self, input_lines, input_offset)
  File "/home/docs/checkouts/readthedocs.org/user_builds/cloudlib4zvm/envs/latest/lib/python3.6/site-packages/docutils/statemachine.py", line 241, in run
    context, state, transitions)
  File "/home/docs/checkouts/readthedocs.org/user_builds/cloudlib4zvm/envs/latest/lib/python3.6/site-packages/docutils/statemachine.py", line 452, in check_line
    return method(match, context, next_state)
  File "/home/docs/checkouts/readthedocs.org/user_builds/cloudlib4zvm/envs/latest/lib/python3.6/site-packages/docutils/parsers/rst/states.py", line 2352, in explicit_markup
    nodelist, blank_finish = self.explicit_construct(match)
  File "/home/docs/checkouts/readthedocs.org/user_builds/cloudlib4zvm/envs/latest/lib/python3.6/site-packages/docutils/parsers/rst/states.py", line 2364, in explicit_construct
    return method(self, expmatch)
  File "/home/docs/checkouts/readthedocs.org/user_builds/cloudlib4zvm/envs/latest/lib/python3.6/site-packages/docutils/parsers/rst/states.py", line 2102, in directive
    directive_class, match, type_name, option_presets)
  File "/home/docs/checkouts/readthedocs.org/user_builds/cloudlib4zvm/envs/latest/lib/python3.6/site-packages/docutils/parsers/rst/states.py", line 2151, in run_directive
    result = directive_instance.run()
  File "/home/docs/checkouts/readthedocs.org/user_builds/cloudlib4zvm/checkouts/latest/doc/ext/restapi_parameters.py", line 145, in run
    self.yaml_from_file(self.yaml_file)
  File "/home/docs/checkouts/readthedocs.org/user_builds/cloudlib4zvm/checkouts/latest/doc/ext/restapi_parameters.py", line 107, in yaml_from_file
    self.app.warn(
AttributeError: 'Sphinx' object has no attribute 'warn'

Exception occurred:
  File "/home/docs/checkouts/readthedocs.org/user_builds/cloudlib4zvm/checkouts/latest/doc/ext/restapi_parameters.py", line 107, in yaml_from_file
    self.app.warn(
AttributeError: 'Sphinx' object has no attribute 'warn'

Also fixed get vswitch info by portid rest api doc


Not able to disable guest checkout

Terms

[X] Before you openning this issue, i have checked if the issue has already been reported.

Bagisto Version(s) affected
2.x
Issue Description
Not able to disable guest checkout in product configuration
Preconditions
Local environment
Steps to reproduce

Go to 'Configuration'
Click on 'product'
Disable guest checkout
Save the configuration
See an error

Expected Result
Configuration should be update
Actual Result
Not able to disable guest checkout
Screenshots
No response
Additional context
No response

Now, this issue is fixed. so I am closing this issue.
And I have attached a screenshot Here, for future reference.


Add servo / PWM block to calliope

Currently using Roberta Labs it is not possible to configure an output as PWM to control a servo.
Add a block to control a servo to the calliope mini.
"set servo at  to Hz <1000>"
The functionality already exist in Microsoft MakeCode.

checked, but the following remarks:

i don't understand the text set servo at to Hz <1000> from the description
i don't understand the first comment

I believe, that the servo block here is using PWM to set a servo motor to a well-defined degree.
I don't close this issue, because:

the english tooltip is completely wrong
the help block (on the right side) is missing

B.T.W: this will be deployed today IN THIS BAD state.

The block is designed to
use PWM to set a servo motor to a well-defined degree
the english tooptip is correct now


Can't login to the App

Hi there
I've successfully installed the app and running the python webserver on port 8888 but when I try to update the IP address in the Preference area but gets automagically updated with its default IP which is <IP_ADDRESS>.
I am attaching the screenshots. Please tell guide me what's wrong here.

https://github.com/dineshshetty/Android-InsecureBankv2/issues/12


export timedMap

Hi, I wonder why timedMap type is unexportable
https://github.com/firasdarwish/temap/blob/d915b30f10222a8b4e696434535f45072c3062a9/map.go#L29
so I can't extend it like this, would you mind to make it exportable?
type Foo temap.TimedMap

Hi, huahuayu
you got it, now it's exportable


Add HTTPS egress safelist

Allow provided FQDNs out via the istio egressgateway.

I'm guessing there will be a corresponding verify-cluster-config PR to stuff values in?

@philandstuff Yes. See https://github.com/alphagov/verify-cluster-config/pull/11.
There will also be corresponding changes to the proxy node chart.


[Feature Request] Possibility to give table name as parameter/config

Hi,
I need to write a pretty advanced merge operation so I do that manually but I would still like to use this extension for the Bulk insert that the merge need. So I would like to be able to provide the BulkInsert operation my temporary table name instead of directly inserting to the Entity table. Eg:
new BulkConfig { DestinationTable = "dbo.MyTempTable" }
or
context.BulkInsert("dbo.MyTempTable", entities)
Regards Daniel

Oh and if you think this would be a good fit for this extension then I would be happy to try and add it my self and do a Pull-Request with it.

You can try to implement it and do PullRequest

In Config there is now CustomDestinationTableName that can be set with 'TableName' only or with 'Schema.TableName'.


context key "atEndOfWord" is always false

Type: Bug
When I open a code editor in VSCode and place the text cursor at the end of any word, the context key atEndOfWord remains false, it stays false at every cursor position. I use this context key in the "when" keys of the "keybindings.json" and it has always worked without any problems.
I think that the state of atEndOfWord is always false since version 1.85 or 1.85.1.
VS Code version: Code 1.86.2 (903b1e9d8990623e3d7da1df3d33db3e42d80eda, 2024-02-13T19:40:56.878Z)
OS version: Windows 10 x64 10.0.19045
Modes:

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-5200U CPU @ 2.20GHz (4 x 2195)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: enabled_ondirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_graphite: disabled_offvideo_decode: enabledvideo_encode: unavailable_offvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabled

Load (avg)
undefined

Memory (System)
7.92GB (3.01GB free)

Process Argv
--log info

Screen Reader
no

VM
0%

Extensions (23)

Extension
Author (truncated)
Version

json-viewer
Dut
0.1.0

vscode-commands
fab
1.4.3

thefoldingstuff
geo
0.2.1

vscode-menu-builder
kyl
1.0.2

vscode-plugin-keyboard-shortcut-eval-custom-javascript-codes
Lia
1.0.13

vscode-language-pack-de
MS-
1.85.2024021409

csharp
ms-
2.15.30

vscode-dotnet-runtime
ms-
2.0.1

debugpy
ms-
2024.0.0

python
ms-
2024.0.1

vscode-pylance
ms-
2024.2.2

jupyter
ms-
2024.1.1

jupyter-keymap
ms-
1.1.2

jupyter-renderers
ms-
1.0.17

vscode-jupyter-cell-tags
ms-
0.1.8

vscode-jupyter-slideshow
ms-
0.1.5

powershell
ms-
2024.0.0

multi-command
ryu
1.6.0

vbsvscode
Ser
1.2.1

memento-inputs
spa
1.0.0

vscode-autohotkey2-lsp
thq
2.3.2

vscode-inline-values-powershell
Tyl
0.0.7

vscode-autohotkey-debug
zer
1.11.0

It is a possible enhancement request to make atEndOfWord context key always available, independent of editor.tabCompletion setting?

This a q quite expensive context key and we have no plans to make it generally available. It comes from a time that predates ghost text and it is more likely that we will eventually onboard tab completions to that and get rid of this context key all together.


Added Animation On Few Static Buttons

Few Buttons Were Very Static So Added Hover Animations:

On Button One Saying "Get No Of Clicks" On First Page
2} On Button Two Saying "Search" On 2nd Page

Here Is A Video Showing The Changes👇
https://github.com/ShivaBhattacharjee/Trim/assets/146619192/cbce525f-abff-43b1-b606-1b7dc16129d2

Approved thanks

Approved thanks

Thanks Mate Very Cool🙌


Unit Tests for User Docker Images

We should have tests to detect when public docker images stop working. At least basic functionality should work.

@Lukas113 What's the current status? I think the images are tested nightly, no?

No the docker images are not tested at all. The tests failed. I'm not entirely sure if it was because the tests are flaky or if something else was the problem.
The initial setup was a layer during the docker build. This was the easiest way to test the image. I don't think testing nightly is better than testing on build because once an image is build everything is installed and nothing can really change.


Irreversible block height stop growing

I have a test network,  for some reason,  some BP stop running. when I restarted them, the irreversible block height stop growing but the block height still growing ,this means my network is in an unavailable state, how should I solve this problem?

The jungle test net has some problem. All push does not take effect.

irreversible block number grows only if there're more than 2/3 of producers who are actually producing. You need fix those problematic BPs if this happens.


Add evergreen_fn buildpacks to heroku/buildpacks:20

Bumped versions of evergreen_fn metabuildpack to versions compatible with heroku-20 and heroku-18 stacks.
Added canary tests to workflow for publishling heroku/buildpacks:20 in CircleCI

Signed-off-by: Jesse Brown<EMAIL_ADDRESS>

I ran a container diff of the current heroku/buildpacks:18 and the version that is produced by this PR. There were no differences. I did this mostly because the version changes look scary, but are not a result of actual changes to the resulting images.
» container-diff diff daemon://testfn18-live daemon://testfn18-vnext --type=layer

-----FileLayer-----

Diff for Layer 0:
These entries have been added to testfn18-live: None

These entries have been deleted from testfn18-live: None

These entries have been changed between testfn18-live and testfn18-vnext: None

Diff for Layer 1:
These entries have been added to testfn18-live: None

These entries have been deleted from testfn18-live: None

These entries have been changed between testfn18-live and testfn18-vnext: None

Diff for Layer 2:
These entries have been added to testfn18-live: None

These entries have been deleted from testfn18-live: None

These entries have been changed between testfn18-live and testfn18-vnext: None

Diff for Layer 3:
These entries have been added to testfn18-live: None

These entries have been deleted from testfn18-live: None

These entries have been changed between testfn18-live and testfn18-vnext: None

Diff for Layer 4:
These entries have been added to testfn18-live: None

These entries have been deleted from testfn18-live: None

These entries have been changed between testfn18-live and testfn18-vnext: None

Diff for Layer 5:
These entries have been added to testfn18-live: None

These entries have been deleted from testfn18-live: None

These entries have been changed between testfn18-live and testfn18-vnext: None

Diff for Layer 6:
These entries have been added to testfn18-live: None

These entries have been deleted from testfn18-live: None

These entries have been changed between testfn18-live and testfn18-vnext: None

Diff for Layer 7:
These entries have been added to testfn18-live: None

These entries have been deleted from testfn18-live: None

These entries have been changed between testfn18-live and testfn18-vnext: None

Diff for Layer 8:
These entries have been added to testfn18-live: None

These entries have been deleted from testfn18-live: None

These entries have been changed between testfn18-live and testfn18-vnext: None

Diff for Layer 9:
These entries have been added to testfn18-live: None

These entries have been deleted from testfn18-live: None

These entries have been changed between testfn18-live and testfn18-vnext: None

Diff for Layer 10:
These entries have been added to testfn18-live: None

These entries have been deleted from testfn18-live: None

These entries have been changed between testfn18-live and testfn18-vnext: None

Diff for Layer 11:
These entries have been added to testfn18-live: None

These entries have been deleted from testfn18-live: None

These entries have been changed between testfn18-live and testfn18-vnext: None

Diff for Layer 12:
These entries have been added to testfn18-live: None

These entries have been deleted from testfn18-live: None

These entries have been changed between testfn18-live and testfn18-vnext: None

Diff for Layer 13:
These entries have been added to testfn18-live: None

These entries have been deleted from testfn18-live: None

These entries have been changed between testfn18-live and testfn18-vnext: None

Diff for Layer 14:
These entries have been added to testfn18-live: None

These entries have been deleted from testfn18-live: None

These entries have been changed between testfn18-live and testfn18-vnext: None

Diff for Layer 15:
These entries have been added to testfn18-live: None

These entries have been deleted from testfn18-live: None

These entries have been changed between testfn18-live and testfn18-vnext: None

I ran a container diff of the current heroku/buildpacks:18 and the version that is produced by this PR. There were no differences. I did this mostly because the version changes look scary, but are not a result of actual changes to the resulting images.
» container-diff diff daemon://testfn18-live daemon://testfn18-vnext --type=layer

-----FileLayer-----

Diff for Layer 0:
These entries have been added to testfn18-live: None

These entries have been deleted from testfn18-live: None

These entries have been changed between testfn18-live and testfn18-vnext: None

Diff for Layer 1:
These entries have been added to testfn18-live: None

These entries have been deleted from testfn18-live: None

These entries have been changed between testfn18-live and testfn18-vnext: None

Diff for Layer 2:
These entries have been added to testfn18-live: None

These entries have been deleted from testfn18-live: None

These entries have been changed between testfn18-live and testfn18-vnext: None

Diff for Layer 3:
These entries have been added to testfn18-live: None

These entries have been deleted from testfn18-live: None

These entries have been changed between testfn18-live and testfn18-vnext: None

Diff for Layer 4:
These entries have been added to testfn18-live: None

These entries have been deleted from testfn18-live: None

These entries have been changed between testfn18-live and testfn18-vnext: None

Diff for Layer 5:
These entries have been added to testfn18-live: None

These entries have been deleted from testfn18-live: None

These entries have been changed between testfn18-live and testfn18-vnext: None

Diff for Layer 6:
These entries have been added to testfn18-live: None

These entries have been deleted from testfn18-live: None

These entries have been changed between testfn18-live and testfn18-vnext: None

Diff for Layer 7:
These entries have been added to testfn18-live: None

These entries have been deleted from testfn18-live: None

These entries have been changed between testfn18-live and testfn18-vnext: None

Diff for Layer 8:
These entries have been added to testfn18-live: None

These entries have been deleted from testfn18-live: None

These entries have been changed between testfn18-live and testfn18-vnext: None

Diff for Layer 9:
These entries have been added to testfn18-live: None

These entries have been deleted from testfn18-live: None

These entries have been changed between testfn18-live and testfn18-vnext: None

Diff for Layer 10:
These entries have been added to testfn18-live: None

These entries have been deleted from testfn18-live: None

These entries have been changed between testfn18-live and testfn18-vnext: None

Diff for Layer 11:
These entries have been added to testfn18-live: None

These entries have been deleted from testfn18-live: None

These entries have been changed between testfn18-live and testfn18-vnext: None

Diff for Layer 12:
These entries have been added to testfn18-live: None

These entries have been deleted from testfn18-live: None

These entries have been changed between testfn18-live and testfn18-vnext: None

Diff for Layer 13:
These entries have been added to testfn18-live: None

These entries have been deleted from testfn18-live: None

These entries have been changed between testfn18-live and testfn18-vnext: None

Diff for Layer 14:
These entries have been added to testfn18-live: None

These entries have been deleted from testfn18-live: None

These entries have been changed between testfn18-live and testfn18-vnext: None

Diff for Layer 15:
These entries have been added to testfn18-live: None

These entries have been deleted from testfn18-live: None

These entries have been changed between testfn18-live and testfn18-vnext: None


[FEATURE] Only show global repos if they meet a criteria

What would you like to share?

This space is meant for exploration of good projects and contribute to them. For that, We have to set some criteria for listing and accepting projects on the repos page.
Criteria for Listing Projects:

Projects should be developed to a certain level and be ready for launch.
Projects with at least 12 stars.
Projects with 100 or more commits.
Complete documentation is a must.
Projects should be in active development, and owners should be actively engaging with issues.

However, there are some repositories that might not meet these criteria and could potentially waste people's time.

It's worth noting that some individuals are even using this space for their GitHub READMEs.

Additional information
No response

This is an interesting idea, I will comment on each of your points

Projects should be developed to a certain level and be ready for launch.

This is not possible to judge

Projects with at least 12 stars.

Maybe 100

Projects with 100 or more commits.

Good idea, although we don't get this information

Complete documentation is a must.

This is difficult to gauge

Projects should be in active development, and owners should be actively engaging with issues.

We have the last pushed date
My thoughts on the filters with info we already have:

100+ stars
10+ forks
Recent commit in the last 30 days

This is an interesting idea, I will comment on each of your points

Projects should be developed to a certain level and be ready for launch.

This is not possible to judge

Projects with at least 12 stars.

Maybe 100

Projects with 100 or more commits.

Good idea, although we don't get this information

Complete documentation is a must.

This is difficult to gauge

Projects should be in active development, and owners should be actively engaging with issues.

We have the last pushed date
My thoughts on the filters with info we already have and the mongo query could be updated:

100+ stars
10+ forks
Recent commit in the last 30 days

We can then see how this goes and build on it later

I think it's possible with the the github api, the stars limit I mean🤔

I think we have the functionality and info we need already...
https://github.com/EddieHubCommunity/BioDrop/blob/5d4eb0be1cb7527726e5c36e13e2c3f14bcbb258/models/Profile/Repo.js#L34-L40

I think we have the functionality and info we need already...
https://github.com/EddieHubCommunity/BioDrop/blob/5d4eb0be1cb7527726e5c36e13e2c3f14bcbb258/models/Profile/Repo.js#L34-L40

that's actually good then

I can work on this issue.

This is an interesting idea, I will comment on each of your points

Projects should be developed to a certain level and be ready for launch.

This is not possible to judge

Projects with at least 12 stars.

Maybe 100

Projects with 100 or more commits.

Good idea, although we don't get this information

Complete documentation is a must.

This is difficult to gauge

Projects should be in active development, and owners should be actively engaging with issues.

We have the last pushed date
My thoughts on the filters with info we already have and the mongo query could be updated:

100+ stars
10+ forks
Recent commit in the last 30 days

We can then see how this goes and build on it later

Should we update Mongo Query for this ?
we can simply apply a filter like this in the pages/repos.js
export async function getServerSideProps() {
  let repos = await getRepos();
  return {
    props: { repos: repos.filter(repo=>repo.stats.stars>=100 && repo.stats.forks>=10) },
  };
}

And for Recent Commit in 30 days filter, should we consider the pushedAt variable for finding out the last commit ?
dates: {
      createdAt: '2023-05-27T12:56:31.000Z',
      updatedAt: '2023-08-30T20:10:57.000Z',
      pushedAt: '2023-08-30T20:08:43.000Z'
    },
    updatedAt: '2023-08-30T20:30:06.820Z',

@dhruvilmehta this should be done in a mongo query not in javascript code, otherwise it will not be efficient. Do you still want it to be assigned?

Yes you can assign this to me.
Can you tell me how to find out the last commit date. is it the same as pushedAt key in the dates object of the repository as shown in the above comment ?

Personally, I feel stars shouldn't be a metric for this. Newer projects can also be good if maintainers seriously want to contribute to the community. What do you think @eddiejaoude
Other metrics such as commits and all are fine.

Yes you can assign this to me.
Can you tell me how to find out the last commit date. is it the same as pushedAt key in the dates object of the repository as shown in the above comment ?

I have assigned it to you. Yes use pushedAt 👍

Personally, I feel stars shouldn't be a metric for this. Newer projects can also be good if maintainers seriously want to contribute to the community. What do you think @eddiejaoude
Other metrics such as commits and all are fine.

I agree, but also many projects are dropped early, I think the star metric also demonstrates a bit of commitment to their  project


Required parameter missing: pricing_type

I tried to create charge
ApiClient::init(CryptoAPI::first()->apikey);
        $chargeObj = new Charge();

        $chargeObj->name = 'The Sovereign Individual';
        $chargeObj->description = 'Mastering the Transition to the Information Age';
        $chargeObj->local_price = [
            'amount' => '100.00',
            'currency' => 'USD'
        ];
        $chargeObj->pricing_type = 'fixed_price';
        $chargeObj->save();
        return redirect($chargeObj->hosted_url);

And got error Required parameter missing: pricing_type
PHP 7.2
Shared Hosting

Hey @arifnurdiansyah92 I just tried your code with my own API key, seemed to work fine. Are you still having this issue?

I’m closing this issue because it has been inactive for a while now. However, please feel free to reopen it if you still encounter this issue with the latest stable version, or please submit a PR if you've managed to fix it. Thanks!


fix(DataStore): log metrics for ReconcileAndLocalSaveOperation

Issue #, if available:
Description of changes:
The goal of this PR is to add the ability to gather metrics on ReconcileAndLocalSaveOperation which performs a number of read and writes to the the local SQL DB.
The debug logs produced look like this
2021-05-11 14:44:50.677372-0700 DataStoreLoadTest[77234:1618471] [ReconcileAndLocalSaveOperation] query local metadata: 0.000369192s
2021-05-11 14:44:50.677901-0700 DataStoreLoadTest[77234:1618471] [ReconcileAndLocalSaveOperation] query pending mutations: 0.000528688s
2021-05-11 14:44:50.679721-0700 DataStoreLoadTest[77234:1618471] [ReconcileAndLocalSaveOperation] save model: 0.001818936s
2021-05-11 14:44:50.681961-0700 DataStoreLoadTest[77234:1618471] [ReconcileAndLocalSaveOperation] save metadata: 0.002241446s
2021-05-11 14:44:50.682496-0700 DataStoreLoadTest[77234:1618471] [ReconcileAndLocalSaveOperation] total time: 0.005473928s

Testing done based on these metrics:

records to sync 10k
page size to sync 1k
item size (~250B)
a single model
IPhone 12 Pro simulator

Results:

query local metadata is a read from SQL for local metadata for the remote model's id: 7.37s
query pending mutations is a read from SQL for pending mutations not in process: 10.27s
save model is a read (check if exists) and write (insert/update) to SQL: 39.87s
save metadata is a read for local metadata, read (check if exists), and a write (insert/update) to SQL: 41.49s
total 5 SQL reads and 2 writes, 99s
sync query API call has been tested before and takes around <1s (around 0.8s on average). there are 10 API calls (10k records/1k page)
total elapsed time from the sample app DataStore.start, to ModelSynced event: 114s

Check points:

[ ] Added new tests to cover change, if needed
[ ] All unit tests pass
[ ] All integration tests pass
[ ] Documentation update for the change if required
[ ] PR title conforms to conventional commit style

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

Merging #1215 (a8dc78f) into main (00521a5) will increase coverage by 0.03%.
The diff coverage is 80.00%.

@@            Coverage Diff             @@
##             main    #1215      +/-   ##
==========================================
+ Coverage   59.92%   59.96%   +0.03%
==========================================
  Files         652      653       +1
  Lines       19293    19336      +43
==========================================
+ Hits        11562    11595      +33
- Misses       7731     7741      +10

Flag
Coverage Δ

API_plugin_unit_test
63.50% <ø> (-0.11%)
:arrow_down:

AWSPluginsCore
76.74% <ø> (ø)

Amplify
48.59% <ø> (ø)

Analytics_plugin_unit_test
73.41% <ø> (ø)

Auth_plugin_unit_test
82.31% <ø> (ø)

DataStore_plugin_unit_test
73.92% <80.00%> (+0.07%)
:arrow_up:

Predictions_plugin_unit_test
33.51% <ø> (ø)

Storage_plugin_unit_test
57.72% <ø> (ø)

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

Impacted Files
Coverage Δ

...eAndLocalSave/ReconcileAndLocalSaveOperation.swift
80.18% <57.14%> (-1.28%)
:arrow_down:

...taStoreCategoryPlugin/Sync/Support/Stopwatch.swift
90.32% <90.32%> (ø)

...s/AWSHubPlugin/Internal/HubChannelDispatcher.swift
94.11% <0.00%> (-2.95%)
:arrow_down:

...CategoryPlugin/Operation/AWSGraphQLOperation.swift
60.75% <0.00%> (-2.54%)
:arrow_down:

...n/Operation/AWSGraphQLOperation+APIOperation.swift
47.27% <0.00%> (ø)

Amplify/Categories/Hub/HubFilter.swift
57.89% <0.00%> (+5.26%)
:arrow_up:

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 00521a5...a8dc78f. Read the comment docs.


rewrite for brigade2 compatibility

Complete rewrite of this GW for Brigade2 compatibility.

@vdice all suggested changes applied.


Contact Us Page: Added Responsive Contact Us Page

Added Responsive Contact Us Page:
• Created a fully responsive "Contact Us" page using HTML, CSS, and JS.
• Implemented a responsive layout to ensure proper display on both desktop and mobile devices.
• Added form validation using JavaScript to improve user experience and error handling.
• Styled the page using CSS Flexbox for a clean and modern design.
• Optimized the page for faster loading and better performance across various screen sizes.

Added Responsive Contact Us Page:
• Created a fully responsive "Contact Us" page using HTML, CSS, and JS. • Implemented a responsive layout to ensure proper display on both desktop and mobile devices. • Added form validation using JavaScript to improve user experience and error handling. • Styled the page using CSS Flexbox for a clean and modern design. • Optimized the page for faster loading and better performance across various screen sizes.

Request for Changes Before Merging
Thank you for your contribution! The work you've done is great, but we kindly request a couple of modifications before we can proceed with merging:

Please rename the "conatct" page to contact.html for clarity.
Bring all the related files into the main folder to keep the structure organized not in different folder.

Once these changes are made, feel free to submit again, and we’ll be happy to review and merge your PR!

Added Responsive Contact Us Page:
• Created a fully responsive "Contact Us" page using HTML, CSS, and JS. • Implemented a responsive layout to ensure proper display on both desktop and mobile devices. • Added form validation using JavaScript to improve user experience and error handling. • Styled the page using CSS Flexbox for a clean and modern design. • Optimized the page for faster loading and better performance across various screen sizes.

Request for Changes Before Merging
Thank you for your contribution! The work you've done is great, but we kindly request a couple of modifications before we can proceed with merging:

Please rename the "contact" page to contact.html for clarity.
Bring all the related files into the main folder to keep the structure organized not in different folder.

Once these changes are made, feel free to submit again, and we’ll be happy to review and merge your PR!

Thank you for the feedback.
I have made the requested changes:

Renamed the "contact" page to contact.html, along with the corresponding CSS and JavaScript files (contact.css and contact.js), for clarity and consistency.

Moved all related files (HTML, CSS, JS, and images) into the main folder to ensure the project structure remains organized and free of unnecessary subfolders.


Syntax highlighting does not initialize on new C# scripts

Godot version
v4.0.rc2.mono.official [d2699dc7a]
System information
Manjaro Linux, kernel 6.0.19-4
Issue description
The syntax highlighting for C# does not function on newly-created C# source code files.  However, after closing and reopening the newly-created file, the syntax highlighting begins to function after a short delay (1-3 seconds on my system).
Steps to reproduce

Create a new C# file.  Its syntax highlighting does not function.
Close the new C# file.
Reopen the C# file.  Its syntax highlighting begins to function after a short delay

Minimal reproduction project
N/A

This bug is still occurring with Godot 4.1

This bug occured at Godot 4.1.1, Windows x64. Actions with reopen helped

Still an issue with Godot 4.2.1

Updated the original post with a more accurate description

In addition, on existing C# files (such as copied directly from an addon folder like YarnSpinner for Godot), there is some syntax highlighting but it's not great (comments are not gray, some keywords in blue, using and var is not colored, etc.

To force syntax highlight I had to save the file (despite no change), close the file, reopen it and wait 3 seconds. In other words, saving the file seems to make it as if it was our own new file, then we can use the same workaround as with our own files.

I have no idea what this intermediate syntax highlighting means, but I'd expect both new and existing files to just open with the complete highlighting, possibly after a short delay if that's really about finding if a class exists in the project (but things like comments should be immediately identified).

Tested on: v4.2.2.stable.mono.official [https://github.com/godotengine/godot/commit/15073afe3856abd2aa1622492fe50026c7d63dc1]

This bug is still present in Godot 4.2.2
I used to code a lot in Python IDLE without syntax highlighting, but with C# it's much harder.
Saving and re-opening the file doesn't help.
I had to restart the entire engine to fix it.

First time trying to edit C# within the editor personally, saving and reopening seems to work for me on 4.3rc3.
Not sure if it's supported but I'm not getting any intellisense either.

I'm also experiencing this on Godot 4.3 mono on windows 11 x64. Steps to reproduce as listed by the OP worked for me.

screenshots show the same file before saving, closing, and re-opening


Centralize RunService connections

This solves #55, looking for a bit of feedback on how this is structured and whether we want to make any changes before I go around centralizing all of the code. The inclusion of the pause and resume functions also solves #5.
Possible changes include:

not using a metatable and instead just directly writing the Singleton as a class, while still using the method : operator instead of the function/property . operator, even though stylistically it is frowned upon. The formatting updates addressed this change
changing how the thread works to force us to use RunService.Stepped or RunService.RenderStepped instead of being able to manually change it The formatting change forces this change
creating a very simple Signal class which gets built into the Updater class, so that we aren't using sleitnick/signal, though this doesn't make much sense.
changing :pause() and :play() to :throttle(throttle: boolean) This idea has been discarded
and so on

Also not sure where exactly we want the source file Updater.lua to be located, I temp threw it into src/Utility, but I'm not sure that's the best place for it. Also, perhaps we want it to have a different name?

I don't like that this change is introducing dependencies to the Fusion project without warning.
It's been an intentional design choice to keep Fusion dependency-free up until this point because it avoids a lot of problems.
When we release a build of Fusion, it would now be dependent on code not part of Fusion to run. This breaks our works-out-of-the-box philosophy that a substantial number of users have appreciated thus far. If you don't use a package manager (which I would bet is over 95% of our user base right now), the burden is now on you to find this stuff yourself. For this reason alone Fusion does not focus on serving the Wally audience primarily - we only push there as a convenience to those people, but otherwise have no further plans to integrate.
On the other hand, we could bundle Fusion up with these dependencies at release time, but this now becomes extra work for us. Now we have to deal with licenses and making sure we don't breach terms - and what if we do breach terms and can't include something? Furthermore, we now have to remember to attribute everything we use, as per the terms of most licenses. This is an overhead I do not want to deal with.
Then there's the runaway dependency issue. We meme about this already with node_modules, but I think it's a serious issue when we're constantly outsourcing small features to libraries and inflating file sizes by fragmenting features in that fashion. Fusion, being a library itself, is meant to be light and small in implementation. Making our library depend on pulling in other libraries would go against that philosophy.
Furthermore, this introduces issues of code control. The entire Fusion codebase, in my own opinion, should be understandable from end to end without having to learn how other libraries work, and any version of Fusion should be built to run at any time into the future. Dependencies break both of these things - the moment we start outsourcing features to external code is the moment we lose that understanding and reliability. All of a sudden you're now dealing with versioning and making sure that all lines up - and then what if that version of the code becomes unavailable or lost?
For these reasons I request that you remove all dependencies you've added, and keep everything in-house for this pull request. We can discuss this in an issue later if you disagree with this policy :)

For these reasons I request that you remove all dependencies you've added, and keep everything in-house for this pull request. We can discuss this in an issue later if you disagree with this policy :)

Thanks for the response, I fully agree with you!
After looking through the Fusion codebase and reading through the existing issues/PR's more I understand what we're going for. Also the existence of the Signal now seems a bit redundant since the code doesn't actually support the ability to override the update method, and just directly connects to RunService.Stepped or RunService.RenderStepped. For now, the existence of .pause(), and .play() should fit the needs of plugin authors and anyone who needs to pause updating for any reason.

Also not sure where exactly we want the source file Updater.lua to be located, I temp threw it into src/Utility, but I'm not sure that's the best place for it. Also, perhaps we want it to have a different name?

You're right that both of these need a bit more consideration. In general, that seems to be a trend in this PR, it all feels a bit rushed, with some obvious errors as a result.

This still needs more design. There are too many questions posed when trying to build this.


feat: added the logo of modelina

Description

Added the logo of modelina in its website.

Related issue(s)

Resolves #1152

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 92.428%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
4793

Relevant Lines:
5053

💛  - Coveralls

@jonaslagoni did the revert of package-lock.json but still there is deploy error

The preview does not work at the moment for what ever reason... Has something to do with netlify. Lets just ignore it.
@sambhavgupta0705 don't think it makes sense we have an icon called AsyncAPILogo, but it's the logo of Modelina monocle_face What do you think?

yeahh Jonas I also thought that.
Making the changes according to that.

/rtm


major: upgrade to fastify v5

Reverted ava: with 20+ plugins I can't use n different things because upgrading them will waste my free time. I want to spend at most 15 minutes to run a simple bump like this
Waiting for Fastify v5 before merging

It's always great when you want to upgrade something to the next major version and see something fail just to come to a PR like this one that has been prepared months in advance! Thank you :)


LED #1 is bright purple?

Any idea why LED #1 is bright (brighter than LIFR) purple and can't be nulled off? I thought it might be the string but it does the same on multiple strings.

Any idea why LED #1 is bright (brighter than LIFR) purple and can't be nulled off? I thought it might be the string but it does the same on multiple strings.

I was having the same issue, it appears there is an issue with the ESP8266 package past ver 3.0.0. Go into boards manager and remove the current ESP8266 should be ver 3.0.2 and reinstall selecting 2.7.4. The issue was resolved for me after that.
Cheers.

Thank you for figuring that out! I was actively troubleshooting and
starting to think I had some sort of hardware design issue.
On Mon, Sep 27, 2021 at 10:05 AM mrkoopa1 @.***> wrote:

Any idea why LED #1 https://github.com/WKHarmon/led-sectional/pull/1 is
bright (brighter than LIFR) purple and can't be nulled off? I thought it
might be the string but it does the same on multiple strings.
I was having the same issue, it appears there is an issue with the ESP8266
package past ver 3.0.0. Go into boards manager and remove the current
ESP8266 should be ver 3.0.2 and reinstall selecting 2.7.4. The issue was
resolved for me after that.
Cheers.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/WKHarmon/led-sectional/issues/12#issuecomment-928077172,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAB322776BQCU72GYJC6OFDUECP6NANCNFSM5EM3M2JA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

--
Kyle Harmon
@.***

Thanks @mrkoopa1, that fixed it!
@WKHarmon did you get the METAR spreadsheet that I sent a few weeks ago?


chore: add ts errors checking by VTI

Interesting feature to use: VTI (Vetur teminal interface) for pre-push hook
Pros:

type checking in templates, to prevent errors

Cons:

it is unstable, yet
runnig takes a lot of time (on my device ~2 minutes)

@mutoe, what do you think. Is it worth to use this tool?

You can, that looks good :D


Bugfix/errors in logs after session expiry

#1071
Checklist

[x] the [contributor license agreement][] is signed
[x] commit message follows [commit guidelines][]

Description of change
The error we saw from the Resource-centre logs actually refers to an issue about LegacyContent not properly handling ajax requests. At the moment we can log this error in a better way and fix it in the future.

Looks good to me. I note that this fix doesn't display an error on the user side, but it at least stops the resource centre logs from filling up.

Cool, let's await a clean build, and if it happens before the release branch for 2020.1 is created we'll discuss whether to merge.


Consensus within the team was to ignore the issue for now. It's a safe place (CLI command) and the code has been in master like that for quite a while.


Add speed-trial infrastructure

This PR is the test script I wrote in support of #1009.  I thought I'd submit it in case it's useful to others.

util/benchmark.py tests the same Wren code between different commits.
With this PR, you can test different Wren code within one commit.

What this PR does:

util/test.py: Exclude directory test/speedtrials.  This gives us a place to hold speed tests that aren't part of the test or benchmark suites.
New util/speedtrial.pl to run speed trials

For example:

Build Wren
Create test/speedtrials/foo-1.wren, test/speedtrials/foo-2.wren, and test/speedtrials/foo-3.wren.
Run ./util/speedtrial.pl test/speedtrials/foo.  It will run test/speedtrials/foo*.wren and output a performance comparison.

Could we stick with Python for this? Adding a Perl script seems out of the norm.

Feel free!

in case it's useful to others.

@cxw42 Thanks for thinking of everyone.  I feel like we should either have a policy that says we accept random helpful scripts (written in a variety of languages) or perhaps we need another repository or Wiki page to collect these instead (rather than living in PRs that will never be merged).
I think I'd be against such a policy for utils but if we had a contrib folder that we more open I think that might be fine. But then of course one might worry how you prevent that from becoming a "junk drawer" of things no one uses (other than the original author).


FILEPERMISSIONS_UID: unbound variable when running the image

Trying to deploy openebs/nfs-server-alpine:0.10.0 to kube but:
Writing SHARED_DIRECTORY to /etc/exports file
The PERMITTED environment variable is unset or null, defaulting to '*'.
This means any client can mount.
The READ_ONLY environment variable is unset or null, defaulting to 'rw'.
Clients have read/write access.
The SYNC environment variable is unset or null, defaulting to 'async' mode.
Writes will not be immediately written to disk.
/usr/bin/nfsd.sh: line 127: FILEPERMISSIONS_UID: unbound variable

Hi @bianchi2. Could you share more details about your environment:

Kubernetes version
dynamic-nfs-provisioner version
OS and version

Also the complete logs would be useful:

provisioner logs
server logs
PVC yaml
StorageClass yaml
kubelet logs for node where the application pod is scheduled
Provisioner yaml (need to see the env values for the FILEPERMISSIONS)

The same issue.

System: Linux XXXX 5.15.0-76-generic #83~20.04.1-Ubuntu SMP Wed Jun 21 20:23:31 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Logs:
Writing SHARED_DIRECTORY to /etc/exports file The PERMITTED environment variable is unset or null, defaulting to '*'. This means any client can mount. The READ_ONLY environment variable is unset or null, defaulting to 'rw'. Clients have read/write access. The SYNC environment variable is unset or null, defaulting to 'async' mode. Writes will not be immediately written to disk. /usr/bin/nfsd.sh: line 127: FILEPERMISSIONS_UID: unbound variable

docker compose:
i deployed by docker compose.
`version: "2.1"
services:
nfs:
image: openebs/nfs-server-alpine:0.10.x-ci
container_name: nfs
restart: unless-stopped
privileged: true
environment:

SHARED_DIRECTORY=/data
volumes:
/ssd1/nfs-data:/data
ports:
2049:2049`

I am not able to picture your configuration @kingmorning. Could you share your storageClass yaml? If you're trying to use FILEPERMISSIONS, could you check if you're following this doc: https://github.com/openebs/dynamic-nfs-provisioner/blob/develop/docs/tutorial/file-permissions.md?

The intro doc needs an update on the FILEPERMISSIONS options.


Use stable icon in release/1.18 branch

Workaround for https://github.com/microsoft/azuredatastudio/issues/10508.  Hard-code official icon into release branch.

Hopefully Anthony's fix works - but do we know that this is the only one affected? There's a number of other product icons we replace in various places.

@Charles-Gagnon I looked through the product and didn't see anywhere else, so certainly no where else nearly as prominent.  The build is here if you'd like to look for other cases https://azuredatastudiobuilds.blob.core.windows.net/releases/1.18.0/azuredatastudio-windows-user-setup-1.18.0.exe.

Coverage increased (+0.1%) to 33.739% when pulling 81f11a156322198ccb66e17399919385b48ed2fe on defect/stableIcon into acd6257bae68d59c9f8b42db1443faddb1504410 on release/1.18.

Alrighty, yeah I ran through it as well and didn't see any other issues on Windows. Just those two.


#19 Fix the missing data from Push Notification payload

closes #19

Codecov Report

Merging #20 into master will increase coverage by -0.48%.

@@            Coverage Diff             @@
##           master      #20      +/-   ##
==========================================
- Coverage      50%   49.52%   -0.48%
==========================================
  Files          15       15
  Lines         104      105       +1
==========================================
  Hits           52       52
- Misses         52       53       +1

Impacted Files
Coverage Δ

src/api/token-api.js
60% <ø> (ø)
:white_check_mark:

src/sw.js
19.04% <ø> (-0.96%)
:x:

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 99e77da...065f3a3. Read the comment docs.


WIP: Represent step dependency as dag in backend

depends on #2183
address  backend to be prepared for #1860

well it was still WIP - and we do NOT in the backend.
but I guess I'll create an issue to track this first

#3381


[HUDI-1781] Fix Flink streaming reader throws ClassCastException

Tips

Thank you very much for contributing to Apache Hudi.
Please review https://hudi.apache.org/contributing.html before opening a pull request.

What is the purpose of the pull request
Fix Flink streaming reader throws ClassCastException when reading from empty table path
Brief change log

Change force cast to if clause

Verify this pull request
This pull request is already covered by existing tests*.
Committer checklist

[ ] Has a corresponding JIRA in PR title & commit

[ ] Commit message is descriptive of the change

[ ] CI is green

[ ] Necessary doc changes done or have another open PR

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

jira url is https://issues.apache.org/jira/browse/HUDI-1781

Codecov Report

Merging #2900 (d388df1) into master (c9bcb5e) will decrease coverage by 38.53%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master   #2900       +/-   ##
============================================
- Coverage     47.90%   9.36%   -38.54%
+ Complexity     3421      48     -3373
============================================
  Files           488      54      -434
  Lines         23529    1997    -21532
  Branches       2501     236     -2265
============================================
- Hits          11271     187    -11084
+ Misses        11277    1797     -9480
+ Partials        981      13      -968

Flag
Coverage Δ
Complexity Δ

hudicli
?
?

hudiclient
?
?

hudicommon
?
?

hudiflink
?
?

hudihadoopmr
?
?

hudisparkdatasource
?
?

hudisync
?
?

huditimelineservice
?
?

hudiutilities
9.36% <ø> (ø)
48.00 <ø> (ø)

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

Impacted Files
Coverage Δ
Complexity Δ

...ache/hudi/source/StreamReadMonitoringFunction.java

...pache/hudi/cli/commands/FileSystemViewCommand.java

...in/java/org/apache/hudi/hive/SchemaDifference.java

...ache/hudi/sink/compact/CompactionPlanOperator.java

...til/jvm/HotSpotMemoryLayoutSpecification64bit.java

...e/hudi/exception/HoodieFlinkStreamerException.java

...i/hadoop/utils/HoodieRealtimeInputFormatUtils.java

...in/java/org/apache/hudi/common/model/BaseFile.java

...e/hudi/common/table/log/HoodieFileSliceReader.java

...ava/org/apache/hudi/common/model/HoodieRecord.java

... and 423 more

It seems not because of my commit, what should I do


"Build" in dependency groups example

I thought I'd try out dependency groups, and copying the example in the docs I added a group called "build". This installed the packages into /packages/build. However my .gitignore has the seemingly standard line:
!packages/*/build/```

And hence everything in the build group shows up as a change for git. Is using "Build" as the name of a group a bad idea, or have I missed something?

just remove that line from gitignore and just ignore completete packages folder.

That is what I have done, but if everyone following the example will face the same issue is it a good example?

the question is what strange thing added that gitignore line. ;-)

I copied that line from the .gitignore in F# project scaffold, the line was added in this commit:
https://github.com/fsprojects/ProjectScaffold/commit/261e11e28a087568728b52fc1542ee133eaba11f

please send PR to ProjectScaffold that removes that line. thx


Feature Request: Add AMDGPU fan control for newer GPUs as optional package

Newer AMD (RX 6000 series for sure and probably others) GPUs don't have a fan curve configurable by vbios and often it only ramps up the fans to about 30% when it hits 90° by default. It makes a great egg fryer and maybe some people be concerned about the thermals.
As per the ArchWiki he simple and working solution is to install and enable the fan curve script by installing the amdgpu-fancontrol-git package. It can be enabled optionally by systemd it the users so desires and need to have a sensible default configuration (provided by the /etc/amdgpu-fancontrol.cfg) so I don't see a problem in installing it by default and leave it disabled by default.

On second thought and a bit of digging, the same effect can be achieved by a sensible use of fancontrol included in lm-sensors package and already installed, so no need for a new package.


Torchrec sharding plan setting

I'm using torchrec to make model parallelization. Is that possible to manually setting up a group of sparse features to be sharded in the same machine? For example, I have 3 sparse features A, B and C. They are interact frequently in my model so I'd like them to be in the same GPU to reduce the communication between machines. Is there any way to make it in torchrec?
Thanks very much!

Hi @shan-jiang-faire, I'm assuming these 3 features will be in separate embedding tables? afaik, if you're using the TorchRec planner to generate a sharding plan, there isn't an easy way to enforce all 3 tables will be on the same GPU/rank. However, you can use the construct_module_sharding_plan API [source] to manually define a sharding plan such that the 3 tables are table-wise sharded on the same rank.
Example:
plan = construct_module_sharding_plan(
  ebc,
  {
     "table_1": table_wise(rank=0),
     "table_2": table_wise(rank=0),
     "table_3": table_wise(rank=0),
  },
)

Would that work for your use case?

@shan-jiang-faire closing this issue for now. Feel free to re-open if your issue isn't resolved.


LaravelDatabaseDesigner support for Laravel Generator

hi, im working on integrate laravel generator with
https://github.com/BioDesignRealWorld/LaravelDatabaseDesigner
ps im the author of laravel database designer.
cheers

@badgeek great. let me know once its ready.


Fix typo adress -> address

Proposed changes

Unreleased project version (optional)

Related issues (optional)

Deploy preview for docsdocker ready!
Built with commit 69094f30429563a6e5e4fdaef5e873e4127590e7
https://deploy-preview-9068--docsdocker.netlify.com

Good catch, thanks!


Preferences menu selection causes no visible UI change with no open windows

Operation System: macOS 10.14.2
Beaker version: 0.8.2
Many macOS application, inclusive of Beaker Browser, stay open when the last window is closed. In Beaker Browser's case, this may be useful for continually seedings sites (I would imagine, I'm new to it).
When I have closed the last Beaker Browser window, it remains in my macOS Dock and the Beaker Browser menus (Beaker Browser, File, Edit, etc.) remain accessible. Selecting the Beaker Browser menu then Preferences causes nothing to be visually shown in the user interface.
This only seems to be the case when there is no visible Beaker Browser window being displayed. If one is visible, a new tab is created to show the Preferences. However, if no window is shown, it seems that no new tab/window is created.

On further inspection, this same behavior is exhibited for other menu items as well. For example, in the same scenario with no Beaker windows open, selecting View>Toggle Dev Tools does not cause anything to display on the screen.

Fixed! Huge thanks to @lvivier. I didn't even have time to triage this before it was fixed


Program aborts if you scroll while moused over a widget

Output of abort:
listener function for opcode 6 of wl_pointer is NULL
fish: Job 1, '/usr/local/bin/zenway' terminated by signal SIGABRT (Abort)

Steps to reproduce:

Hold modifier key to show zenway
Mouse over any widget
Scroll

Thanks! Fixed in PR #6


Add TessBaseApi::GetTessDataDir

Trivial patch to expose the used tessdata_prefix in the public API.

https://github.com/tesseract-ocr/tesseract/blob/master/api/baseapi.cpp#L954

const char *  TessBaseAPI::GetDatapath() {
return tesseract_->datadir.c_str();
}

Oh, not sure how I managed to miss that one. Thanks!


As a pigeon, I want the minimum balance check to be 0.05ETH and subject to governance

Background
Pigeons are using up their valset updates of 0.1 ETH and being jailed. As such, we want to lower the threshold for jailing while still refunding pigeons. We would like to lower the default threshold for pigeon to be active from 0.1 ETH to LESS THAN 0.05 ETH.
Done when

[ ] Update minimum ETH required to be in the validator set  0.05 ETH or MORE.

@Vizualni is this okay to ship in th enext release?

@Vizualni is this okay to ship in th enext release?

Yep! We will ship it.

This is done. Closing


Emmet override the key binding for atom sniplets

When I enable emmet, I can not do sniplets with tab.
When I disable emeet, tab start working for sniplets
Atom - 1.7.3

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/34071616-emmet-override-the-key-binding-for-atom-sniplets?utm_campaign=plugin&utm_content=tracker%2F535900&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F535900&utm_medium=issues&utm_source=github).

Yeah, for some reason using "tab" to accept auto-complete suggestions is broken for me too, but only in CSS/SCSS files...

I have the same problem. This is with emmet 2.4.3 and atom 1.9.9. If there is any additional info I can provide I'm happy to do so.


[SMALLFIX] Implement isDirectory in Swift UFS

Valid prefixes ending in a path separator will be counted as "existing" paths.

High-level question: is this for a performance improvement?

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/10072/
Test PASSed.

Merged build finished. Test PASSed.

LGTM

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/10073/
Test PASSed.

Merged build finished. Test PASSed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/10099/
Test FAILed.

LGTM


ocamlPackages.vg: 0.9.1 -> 0.9.3

Motivation for this change
Compatibility with recent Js-of-OCaml.
Things done

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

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

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Notify maintainers
cc @jirkamarsik

@GrahamcOfBorg build ocamlPackages.vg


Simulation is very slow

I am running CARLA 0.8.4 on Windows 10
I am running the manual_control python client, however the simulation is very very slow, it is like performing maybe 2 frames per second or something like that
Is there any way to speed up the simulation, or maybe is there a way to use the GPU, if this can help ?
Note: I already reduced the size of the server
.\CarlaUE4.exe -carla-server -windowed -ResX=1 -ResY=1
but it seems it is not also helping, the pygame itself is very slow
Any tips/ideas ?

Hi, I have the same issue. (maybe slower). I tried it ubuntu 16.04, with two GPUs. I compiled, ran "CarlaUE4.sh -windowed" and ran "manual_control.py". As I press WSAD keys, I can see the car moving in the big window. But the small window (from inside the car) is updated so slowly and catches up some seconds later. What is wrong?

u should change the drive of your video card.use the independent one.