ISTIO 1.1 - ingressgateway not working on a fresh install

Describe the bug
I installed the new version of istio-1.1 using both option 1 and option 2,  I got the same result, I can't access to the bookinfo through the ingressgateway.
 This configuration will be removed from Envoy soon. Please see https://github.com/envoyproxy/envoy/blob/master/DEPRECATED.md for details.
[2019-03-24 10:30:05.701][13][warning][misc] [external/envoy/source/common/protobuf/utility.cc:129] Using deprecated option 'envoy.api.v2.Cluster.hosts'. This configuration will be removed from Envoy soon. Please see https://github.com/envoyproxy/envoy/blob/master/DEPRECATED.md for details.
[2019-03-24 10:30:05.701][13][warning][misc] [external/envoy/source/common/protobuf/utility.cc:129] Using deprecated option 'envoy.api.v2.Cluster.hosts'. This configuration will be removed from Envoy soon. Please see https://github.com/envoyproxy/envoy/blob/master/DEPRECATED.md for details.
[2019-03-24 10:30:05.701][13][warning][misc] [external/envoy/source/common/protobuf/utility.cc:129] Using deprecated option 'envoy.api.v2.Cluster.hosts'. This configuration will be removed from Envoy soon. Please see https://github.com/envoyproxy/envoy/blob/master/DEPRECATED.md for details.
[2019-03-24 10:30:05.701][13][warning][misc] [external/envoy/source/common/protobuf/utility.cc:129] Using deprecated option 'envoy.config.trace.v2.Tracing.Http.config'. This configuration will be removed from Envoy soon. Please see https://github.com/envoyproxy/envoy/blob/master/DEPRECATED.md for details.
[2019-03-24 10:30:05.714][13][warning][config] [bazel-out/k8-opt/bin/external/envoy/source/common/config/_virtual_includes/grpc_stream_lib/common/config/grpc_stream.h:102] gRPC config stream closed: 14, no healthy upstream
[2019-03-24 10:30:05.714][13][warning][config] [bazel-out/k8-opt/bin/external/envoy/source/common/config/_virtual_includes/grpc_stream_lib/common/config/grpc_stream.h:56] Unable to establish new stream
2019-03-24T10:30:08.643346Z     info    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2019-03-24T10:30:30.642532Z     info    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2019-03-24T10:30:32.645420Z     info    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2019-03-24T10:30:34.643814Z     info    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2019-03-24T10:30:36.644777Z     info    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2019-03-24T10:30:38.643351Z     info    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2019-03-24T10:30:40.649722Z     info    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2019-03-24T10:30:42.643485Z     info    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2019-03-24T10:30:44.644455Z     info    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
[2019-03-24 10:30:44.840][13][warning][config] [bazel-out/k8-opt/bin/external/envoy/source/common/config/_virtual_includes/grpc_stream_lib/common/config/grpc_stream.h:102] gRPC config stream closed: 14, upstream connect error or disconnect/reset before headers
2019-03-24T10:30:46.642383Z     info    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2019-03-24T10:30:48.643343Z     info    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2019-03-24T10:30:50.643290Z     info    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
[2019-03-24 10:31:00.276][13][warning][config] [bazel-out/k8-opt/bin/external/envoy/source/common/config/_virtual_includes/grpc_stream_lib/common/config/grpc_stream.h:102] gRPC config stream closed: 14, upstream connect error or disconnect/reset before headers
2019-03-24T10:31:00.647247Z     info    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2019-03-24T10:31:02.642839Z     info    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2019-03-24T10:31:04.650171Z     info    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2019-03-24T10:31:06.643025Z     info    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2019-03-24T10:31:08.642493Z     info    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2019-03-24T10:31:10.653200Z     info    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2019-03-24T10:31:12.642966Z     info    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2019-03-24T10:31:14.644475Z     info    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2019-03-24T10:31:16.644512Z     info    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2019-03-24T10:31:18.645531Z     info    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2019-03-24T10:31:20.648423Z     info    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2019-03-24T10:31:22.645947Z     info    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2019-03-24T10:31:24.650056Z     info    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2019-03-24T10:31:26.644971Z     info    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2019-03-24T10:31:28.652839Z     info    Envoy proxy is ready
2019-03-24T10:31:37.795584Z     info    watchFileEvents: "/etc/certs//..2019_03_24_10_31_37.063241460": CREATE
2019-03-24T10:31:37.795609Z     info    watchFileEvents: "/etc/certs//..2019_03_24_10_31_37.063241460": MODIFY|ATTRIB
2019-03-24T10:31:37.795617Z     info    watchFileEvents: "/etc/certs//root-cert.pem": CREATE
2019-03-24T10:31:37.795643Z     info    watchFileEvents: "/etc/certs//cert-chain.pem": CREATE
2019-03-24T10:31:37.795648Z     info    watchFileEvents: "/etc/certs//key.pem": CREATE
2019-03-24T10:31:37.795654Z     info    watchFileEvents: "/etc/certs//..data_tmp": RENAME
2019-03-24T10:31:37.795681Z     info    watchFileEvents: "/etc/certs//..data": CREATE
2019-03-24T10:31:37.795687Z     info    watchFileEvents: "/etc/certs//..2019_03_24_10_30_04.883745671": DELETE
2019-03-24T10:31:47.796826Z     info    watchFileEvents: notifying
2019-03-24T10:31:47.799288Z     info    Received new config, resetting budget
2019-03-24T10:31:47.799425Z     info    Reconciling retry (budget 10)
2019-03-24T10:31:47.799817Z     info    Epoch 1 starting
2019-03-24T10:31:47.806173Z     info    Envoy command: [-c /etc/istio/proxy/envoy-rev1.json --restart-epoch 1 --drain-time-s 45 --parent-shutdown-time-s 60 --service-cluster istio-ingressgateway --service-node router~<IP_ADDRESS>~istio-ingressgateway-8ccdc79bc-q69fd.istio-system~istio-system.svc.cluster.local --max-obj-name-len 189 --allow-unknown-fields -l warning]
[2019-03-24 10:31:47.908][27][warning][misc] [external/envoy/source/common/protobuf/utility.cc:129] Using deprecated option 'envoy.api.v2.listener.Filter.config'. This configuration will be removed from Envoy soon. Please see https://github.com/envoyproxy/envoy/blob/master/DEPRECATED.md for details.
[2019-03-24 10:31:47.908][27][warning][misc] [external/envoy/source/common/protobuf/utility.cc:129] Using deprecated option 'envoy.api.v2.Cluster.hosts'. This configuration will be removed from Envoy soon. Please see https://github.com/envoyproxy/envoy/blob/master/DEPRECATED.md for details.
[2019-03-24 10:31:47.908][27][warning][misc] [external/envoy/source/common/protobuf/utility.cc:129] Using deprecated option 'envoy.api.v2.Cluster.hosts'. This configuration will be removed from Envoy soon. Please see https://github.com/envoyproxy/envoy/blob/master/DEPRECATED.md for details.
[2019-03-24 10:31:47.908][27][warning][misc] [external/envoy/source/common/protobuf/utility.cc:129] Using deprecated option 'envoy.api.v2.Cluster.hosts'. This configuration will be removed from Envoy soon. Please see https://github.com/envoyproxy/envoy/blob/master/DEPRECATED.md for details.
[2019-03-24 10:31:47.908][27][warning][misc] [external/envoy/source/common/protobuf/utility.cc:129] Using deprecated option 'envoy.config.trace.v2.Tracing.Http.config'. This configuration will be removed from Envoy soon. Please see https://github.com/envoyproxy/envoy/blob/master/DEPRECATED.md for details.
[2019-03-24 10:31:47.914][13][warning][main] [external/envoy/source/server/server.cc:525] shutting down admin due to child startup
[2019-03-24 10:31:47.914][13][warning][main] [external/envoy/source/server/server.cc:533] terminating parent process
[2019-03-24 10:31:47.922][27][warning][config] [bazel-out/k8-opt/bin/external/envoy/source/common/config/_virtual_includes/grpc_stream_lib/common/config/grpc_stream.h:102] gRPC config stream closed: 14, no healthy upstream
[2019-03-24 10:31:47.922][27][warning][config] [bazel-out/k8-opt/bin/external/envoy/source/common/config/_virtual_includes/grpc_stream_lib/common/config/grpc_stream.h:56] Unable to establish new stream
[2019-03-24 10:33:13.041][13][warning][main] [external/envoy/source/server/server.cc:405] caught SIGTERM
2019-03-24T10:33:13.050777Z     info    Epoch 0 exited normally
[2019-03-24 10:38:51.555][27][warning][misc] [external/envoy/source/common/protobuf/utility.cc:129] Using deprecated option 'envoy.api.v2.listener.Filter.config'. This configuration will be removed from Envoy soon. Please see https://github.com/envoyproxy/envoy/blob/master/DEPRECATED.md for details.
[2019-03-24 10:38:51.566][27][warning][misc] [external/envoy/source/common/protobuf/utility.cc:129] Using deprecated option 'envoy.config.filter.network.http_connection_manager.v2.HttpFilter.config'. This configuration will be removed from Envoy soon. Please see https://github.com/envoyproxy/envoy/blob/master/DEPRECATED.md for details.
[2019-03-24 10:38:51.641][27][warning][misc] [external/envoy/source/common/protobuf/utility.cc:129] Using deprecated option 'envoy.api.v2.route.Route.per_filter_config'. This configuration will be removed from Envoy soon. Please see https://github.com/envoyproxy/envoy/blob/master/DEPRECATED.md for details.
[2019-03-24 10:38:51.641][27][warning][misc] [external/envoy/source/common/protobuf/utility.cc:129] Using deprecated option 'envoy.api.v2.route.Route.per_filter_config'. This configuration will be removed from Envoy soon. Please see https://github.com/envoyproxy/envoy/blob/master/DEPRECATED.md for details.
[2019-03-24 10:38:51.641][27][warning][misc] [external/envoy/source/common/protobuf/utility.cc:129] Using deprecated option 'envoy.api.v2.route.Route.per_filter_config'. This configuration will be removed from Envoy soon. Please see https://github.com/envoyproxy/envoy/blob/master/DEPRECATED.md for details.
[2019-03-24 10:38:51.641][27][warning][misc] [external/envoy/source/common/protobuf/utility.cc:129] Using deprecated option 'envoy.api.v2.route.Route.per_filter_config'. This configuration will be removed from Envoy soon. Please see https://github.com/envoyproxy/envoy/blob/master/DEPRECATED.md for details.
[2019-03-24 10:45:49.582][27][warning][misc] [external/envoy/source/common/protobuf/utility.cc:129] Using deprecated option 'envoy.api.v2.listener.Filter.config'. This configuration will be removed from Envoy soon. Please see https://github.com/envoyproxy/envoy/blob/master/DEPRECATED.md for details.
[2019-03-24 10:45:49.582][27][warning][misc] [external/envoy/source/common/protobuf/utility.cc:129] Using deprecated option 'envoy.api.v2.route.Route.per_filter_config'. This configuration will be removed from Envoy soon. Please see https://github.com/envoyproxy/envoy/blob/master/DEPRECATED.md for details.
[2019-03-24 10:45:49.582][27][warning][misc] [external/envoy/source/common/protobuf/utility.cc:129] Using deprecated option 'envoy.api.v2.route.Route.per_filter_config'. This configuration will be removed from Envoy soon. Please see https://github.com/envoyproxy/envoy/blob/master/DEPRECATED.md for details.
[2019-03-24 10:45:49.582][27][warning][misc] [external/envoy/source/common/protobuf/utility.cc:129] Using deprecated option 'envoy.api.v2.route.Route.per_filter_config'. This configuration will be removed from Envoy soon. Please see https://github.com/envoyproxy/envoy/blob/master/DEPRECATED.md for details.
[2019-03-24 10:45:49.582][27][warning][misc] [external/envoy/source/common/protobuf/utility.cc:129] Using deprecated option 'envoy.api.v2.route.Route.per_filter_config'. This configuration will be removed from Envoy soon. Please see https://github.com/envoyproxy/envoy/blob/master/DEPRECATED.md for details.

The yaml files for gateway and virtualservice
apiVersion: v1
items:
- apiVersion: networking.istio.io/v1alpha3
  kind: Gateway
  metadata:
    creationTimestamp: "2019-03-24T10:38:50Z"
    generation: 1
    name: gw-bookinfo
    namespace: default
    resourceVersion: "142988"
    selfLink: /apis/networking.istio.io/v1alpha3/namespaces/default/gateways/gw-bookinfo
    uid: 02f901a2-4e21-11e9-bc09-000c2953b5e1
  spec:
    selector:
      istio: ingressgateway
    servers:
    - hosts:
      - '*'
      port:
        name: http
        number: 80
        protocol: HTTP
kind: List
metadata:
  resourceVersion: ""
  selfLink: ""

apiVersion: v1
items:
- apiVersion: networking.istio.io/v1alpha3
  kind: VirtualService
  metadata:
    creationTimestamp: "2019-03-24T10:38:50Z"
    generation: 1
    name: bookinfo-access
    namespace: default
    resourceVersion: "142989"
    selfLink: /apis/networking.istio.io/v1alpha3/namespaces/default/virtualservices/bookinfo-access
    uid: 02fc7837-4e21-11e9-bc09-000c2953b5e1
  spec:
    gateways:
    - gw-bookinfo
    hosts:
    - '*'
    http:
    - match:
      - uri:
          exact: /productpage
      - uri:
          exact: /login
      - uri:
          exact: /logout
      - uri:
          prefix: /api/v1/products
      route:
      - destination:
          host: default/productpage
kind: List
metadata:
  resourceVersion: ""
  selfLink: ""

Version
kubectl version
Client Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.4", GitCommit:"c27b913fddd1a6c480c229191a087698aa92f0b1", GitTreeState:"clean", BuildDate:"2019-02-28T13:37:52Z", GoVersion:"go1.11.5", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.4", GitCommit:"c27b913fddd1a6c480c229191a087698aa92f0b1", GitTreeState:"clean", BuildDate:"2019-02-28T13:30:26Z", GoVersion:"go1.11.5", Compiler:"gc", Platform:"linux/amd64"}

Installation
I used both option 1 and option 2
Environment
kubernetes
Any help for this issue ?
Thanks

This may help you https://istio.io/help/ops/traffic-management/proxy-cmd/#deep-dive-into-envoy-configuration

Find this virtualservice setting is not right
      route:
      - destination:
          host: default/productpage

@hzxuzhonghu  you right I tought that the namespace scoping was for virtualservice too but when I re-check the release notes 1.1, it was only for gateway
Namespace Scoping. When referring to a VirtualService in a Gateway we use DNS based name matching in our configuration model. This can be ambiguous when more than one namespace defines a virtual service for the same host name. To resolve ambiguity it is now possible to explicitly scope these references by namespace using a syntax of the form [{namespace-name}]/{hostname-match} in the hosts field. The equivalent capability is also available in Sidecar for egress.

I'll modify it and let you know
thanks

Fixed by #12804


live transcription doesn't live ???

50% of the time the transcription only comes after stop is pressed
other 50%: error (tensor mismatch stuf) that i cant fix
mayb its only on my pc ??? pls check

fixed 😄


ConfigBean atLeastOne needs to be completed

Right now it is only partially implemented.

This is no longer valid, as helidon-inject will be removed, and helidon-service-inject does not have this issue.


[GUI] "select a hardware wallet" small improvements

1- a spinner showing it's still looking for HW. It's confusing to see "this laptop" there and not my ColdCard that takes 4+ seconds to load.
2- only display the useful signers (or grey out the not useful ones).
By "useful" i mean: having the origin corresponding to a valid key. Preferably only Primary in the spend screen.

an extension of this is to remove "this laptop" when its key isn't part of the descriptor.

I prefer it grey. And i think it's implemented in master: signer whose origin isn't in descriptor will be greyed out in the list.
On Wednesday, January 10th, 2024 at 8:50 PM, Kevin Loaec @.***> wrote:

an extension of this is to remove "this laptop" when its key isn't part of the descriptor.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: @.***>


toBinaryString returns 0s

Code: println((-71777214294589696L).toBinaryString())
Output:<PHONE_NUMBER>000000000000000000000000000000000000000000000000000000

Tried .toUnsignedString(2), toHexString() as well, it's less 0s.
.toUlong().toString() gives a good decimal representation, but I need binary; UTypes don't have toString(radix) methods.
.toUlong().toBigInt().toString(2) gives the right value, but pretty tedious.
.toUBigInt().toString(2) is based on toUnsignedString(10), luckily that's not using toUnsignedString0, so it works.
The bug is in the konversion of formatUnsignedLong from the JDK: when you introduced _this, you forgot to replace the implicit this.toInt() and mask inside digits[], it should be _this.toInt() and mask.

Ok Róbert,
thanks for opening the issue and suggesting the fix, I quickly applied it and it worked.
I'll review all the other call and problems you mentioned with calm.
Btw, push request are welcome for the next time if you want to do it directly.
Shall I publish a release for this fix?

The other issues are not really issues, I was just looking to work around this bug.
I guess the only thing you need to look at is "UTypes don't have toString(radix) methods."
No need to push any quick, I decided to just go with fun Int.toBinaryHashString() = java.lang.Integer.toBinaryString(this) instead of pulling your whole lib in, I'm on desktop and targeting latest Java so have the API I need.


added Filters

issue number = #370
Screenshots:-

Kindly remove the Brick Breaker files from this PR. Also link your PR with the issue it is resolving.

i have linked the issue resolved and the folder of brick breaker is not deleting i have closed a previos PR because of same issue and now it is again the same problem that the folder brick breaker is not removing

@kuldeepjoshi27 Delete the forked repo and clone it again. That should work.

@kuldeepjoshi27 Delete the forked repo and clone it again. That should work.

i done it before with the same project but it is not working


ListItemPicker: DefaultSelectedItems for ListItemPicker not working with Dynamic Data

Bug: defaultSelectedItems for ListItemPicker not working with React dynamic data
I've installed @pnp/spfx-controls-react of version 1.16.0.
I am facing challenge in setting default selected item for ListitemPicker dynamically.
If we set defaultSelectedItems using any static data it is working properly. However if we try to set defaultSelectedItems dynamically using react state variable then it does not set default selected items.
Expected / Desired Behavior / Question
We should be able to set defaultSelectedItems dynamically using react state or any other way.
Observed Behavior
If I set static DefaultSelectedItem for ListItemPicker it works properly.
<ListItemPicker listId='653741e7-84c2-4d78-81a6-ac77dcc6bd24'
                                            columnInternalName='Title'
                                            keyColumnInternalName='Id'
                                            itemLimit={1}
                                            onSelectedItem={this.onSelectedItem}
                                            context={this.props.context}
                                            suggestionsHeaderText = "Please select Location"
                                            defaultSelectedItems={[{key: 12297, name: "A1R1C1S1"}]}

Steps to Reproduce
If we trying to set  DefaultSelectedItem for ListItemPicker dynamically then it does not work.
Please find following example in which I am trying to set default selected items using react state.
  public componentDidMount() {
    sp.setup({
        spfxContext: this.props.context
    });
    this.GetLookupData("Record Location", "Title").then(ChoiceItemCollection => {
        this.setState({
            RecordLocations: ChoiceItemCollection,
            SelectedRecordLocation: ChoiceItemCollection.filter(item => item.key === 12297),
        });
    });

}
  public render(): React.ReactElement < IListPickerProps > {

    return(

                        <ListItemPicker listId='653741e7-84c2-4d78-81a6-ac77dcc6bd24'
                            columnInternalName='Title'
                            keyColumnInternalName='Id'
                            itemLimit={1}
                            onSelectedItem={this.onSelectedItem}
                            context={this.props.context}
                            suggestionsHeaderText="Please select Location"
                            defaultSelectedItems={this.state.SelectedRecordLocation}

                        />

    );
  }

  private GetLookupData(SPListName: string, SPFieldName: string): Promise < any > {
    let spfields = [SPFieldName, "Id"];

    return sp.web.lists.getByTitle(SPListName).items.select(...spfields).top(5000)
        .get()
        .then((data) => {

            if (data && data.length > 0) {
                let ChoicesCollection: any[] = [];
                data.forEach((item, index) => {
                    ChoicesCollection.push({
                        key: parseInt(item.Id),
                        // text: item[SPFieldName],
                        // title:item[SPFieldName],
                        name: item[SPFieldName],
                    });
                });
                return ChoicesCollection;
            }

        }).catch((e) => console.log("Error in GetLookupData() function. " + e));
}

In above example I am getting data from "Record Location" list using async function GetLookupData and trying to set default value using SelectedRecordLocation state variable.
Control re renders when we set state in componentDidMount however it is not setting default value for ListItemPicker control.
Please let me know if this is bug /any solution is there for this issue
Any help will be appreciated.
Thanks!

Hi! I have the same problem.
I solved it with a method and the react state...

Another option here could be to display Spinner until loading the items.
{this.state.defaultItems && <ListItemPicker ... />}
{!this.state.defaultItems && <Spinner ... />}

@AJIXuMuK  and @Macro21  Thank you so much for the reply.
I have tried suggested approach to get default item first and then load the ListItemPicker control. This solution works however here we need to wait to load ListItemPicker control until we don't get the default item. There should be some appropriate fix in this control for this issue.

Hi! I have the same problem.
I solved it with a method and the react state...

Update:
The bug its on Fabric UI TagPicker. ListItemPicker use TagPicker :)

Can I know more code? what's getlistitempicker?
Thanks

@AJIXuMuK and @Macro21 Thank you so much for the reply.
I have tried suggested approach to get default item first and then load the ListItemPicker control. This solution works however here we need to wait to load ListItemPicker control until we don't get the default item. There should be some appropriate fix in this control for this issue.

Hi, could You share the methods, how You solved this case?


Skip tests when collateral is not present

AB#275
Description
Skip tests that depend on the test collateral submodule to be present. This is in part so that npm run test succeeds on a fresh clone of the repository after a successful build, per the instructions in the main README.
Steps to Reproduce Bug and Validate Solution
Currently, the steps suggested by the main README to build and run tests locally result in some tests failing (assumes the correct version of Node.js is already installed):
git clone https://github.com/microsoft/FluidFramework.git
cd FluidFramework
npm install
npm run build:fast
npm run test

Alternatively, running the tests directly for the @fluid-internal/test-snapshots package if the test collateral submodule is not present also shows its tests failing.
PR Checklist

[ ] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.
[x] My code follows the code style of this project.
[ ] I ran the lint checks which produced no new errors nor warnings for my changes.
[ ] I have checked to ensure there aren't other open Pull Requests for the same update/change.

Does this introduce a breaking change?

[ ] Yes
[x] No

Testing
Follow the steps above. Tests now succeed.

Note: I edited the top line of your description to AB#275 so it will automatically link to the ADO work item.


UWP and Xbox

I have a question.
Have the codes been tested to run on Xbox?

Hi, these Kinect tutorials were written for Kinect for Windows 8.1. That is the platform they were tested on.


BUG: Using a gendered relationship value from a list setting doesn't correctly identify the list setting

Only when using the Name value of the list setting does our code correctly find the list setting.

Included in beta release version 3.48 (Beta 4) and higher

Included in production release version 3.48


NameError /v1/search - name 'q' is not defined

Error from Sentry

NameError: name 'q' is not defined
  File "django/core/handlers/exception.py", line 35, in inner
    response = get_response(request)
  File "django/core/handlers/base.py", line 128, in _get_response
    response = self.process_exception_by_middleware(e, request)
  File "django/core/handlers/base.py", line 126, in _get_response
    response = wrapped_callback(request, *callback_args, **callback_kwargs)
  File "standardsearch/webapp/views.py", line 84, in search_v1
    "query": q,

I Think this is a simple fix:
https://github.com/open-contracting/standard-search/blob/master/standardsearch/webapp/views.py#L84 does have variable q.
Commit https://github.com/open-contracting/standard-search/commit/83b9a019bcbc07f2d0f9ccf245d8d25ade3f8e75 changed this from search to q.
Search is still set in https://github.com/open-contracting/standard-search/blob/master/standardsearch/webapp/views.py#L60 and q is not set?

Confirmed: Here are changes from last deployed version https://github.com/open-contracting/standard-search/compare/open-contracting:41f98ff6ef758d52fb6eea43c8f89d7f16cc755a...master
Am preparing a pull request now

Yes, my error. The assignment should be to q not to search
On Tuesday, September 29, 2020, James (ODSC<EMAIL_ADDRESS>wrote:

I Think this is a simple fix:
https://github.com/open-contracting/standard-search/
blob/master/standardsearch/webapp/views.py#L84 does have variable q.
Commit 83b9a01
https://github.com/open-contracting/standard-search/commit/83b9a019bcbc07f2d0f9ccf245d8d25ade3f8e75
changed this from search to q.
Search is still set in https://github.com/open-
contracting/standard-search/blob/master/standardsearch/webapp/views.py#L60
and q is not set?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/open-contracting/standard-search/issues/10#issuecomment-700801729,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAGOXY6BWDBSN5RM36KO5TSIH7TRANCNFSM4R57IW4Q
.

--
James McKinney
Head of Data Products and Services
+1-514-247-0223 | @mckinneyjames | skype: mckinney.james | timezone: EST
*** An inclusive economy is a stronger economy. Learn about emerging
strategies for empowering women-led businesses through public procurement
https://www.open-contracting.org/resources/empower-women-led-business-procurement/
in
our new report. ***
*** Una economía incluyente es una economía más fuerte. Aprenda sobre cómo
empoderar a empresas lideradas por mujeres y lograr una mayor inclusión en
la contratación pública
https://www.open-contracting.org/es/resources/empresas-lideradas-por-mujeres-contratacion-publica/
en nuestro nuevo reporte***
www.open-contracting.org | follow us @opencontracting

Deployed live


Onering fix

Attempt number 2
I was too eager with reset timers first time. Only touched what's necessary + added -run=none -benchtime=2s to the benchmark line. Tell me if you don't want it. I think it makes it a bit fairer for everyone (too much variation with 1s benchmarks imo)
Unfortunately I can't generate images on my laptop (R seems to need<PHONE_NUMBER>6+=3% libraries to do that).
But I hope the results are sound. Tell me if you see something that's not right

I like the 2s change actually :) What does -run=none do?

Disables non benchmark tests (which you don't have there, so it's rather cosmetic in this instance, but usually it's a good idea to have it as those can sometimes leave a state behind that affects benchmarks)

Ah okay, that makes sense 😄

@kellabyte I changed all queues to send pointers, which actually made Diode benchmark more correct + removed additional check that's not present in other benchmarks from onering

Awesome! Thanks so much for the changes!


Support vue-cli unit:test

Codecov Report

Merging #43 (386d539) into master (2bf481b) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##            master       #43    +/-   ##
==========================================
  Coverage   100.00%   100.00%
==========================================
  Files           56        60     +4
  Lines         1302      1423   +121
  Branches       300       324    +24
==========================================
+ Hits          1302      1423   +121

Flag
Coverage Δ

root
100.00% <100.00%> (ø)

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

Impacted Files
Coverage Δ

packages/cli/src/bin/wuzzle/wuzzle.ts
100.00% <ø> (ø)

packages/cli/src/apply-config.ts
100.00% <100.00%> (ø)

...s/cli/src/bin/wuzzle-transpile/wuzzle-transpile.ts
100.00% <100.00%> (ø)

...cli/src/bin/wuzzle-unregister/wuzzle-unregister.ts
100.00% <100.00%> (ø)

packages/cli/src/constants.ts
100.00% <100.00%> (ø)

packages/cli/src/launches/index.ts
100.00% <100.00%> (ø)

packages/cli/src/launches/vue-cli-service.ts
100.00% <100.00%> (ø)

packages/cli/src/registers/node/transform.ts
100.00% <100.00%> (ø)

...ckages/cli/src/registers/razzle__3.x/pre-config.ts
100.00% <100.00%> (ø)

...cli/src/registers/react-scripts__3.x/pre-config.ts
100.00% <100.00%> (ø)

... and 6 more

Continue to review full report at Codecov.

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


Send UserLeft callback to the leaving user

If a new client logs into a user from an existing room, the existing user leaves the room as their connection is "cleaned up". They should receive a UserLeft callback to notify them that this is the case so that they can leave the room.
Note: The above scenario will throw an assert on older clients without the changes in https://github.com/ppy/osu/pull/17663.
Manually-tested scenarios:

User leaves room.
User is kicked.
User is logged into by another client.

Looks sensible aside from the above.

Hmm, the thinking was that a UserLeft is always triggered by the user, so sending this to the user is meaningless (and potential added complexity). What would you say to changing the server to send a UserKicked in the scenario this is being used for instead of UserLeft?

Sure, using UserKicked would work.

It should also be explicitly commented that UserLeft is only sent for other users and not the local user.


AMQP-521: LocalizedQueueConnectionFactory

JIRA: https://jira.spring.io/browse/AMQP-521
Connect to the broker where an HA mirrored queue is mastered.
ported from XD with some polishing

Travis says that there is something wrong with the code:

/home/travis/build/spring-projects/spring-amqp/spring-rabbit/src/test/java/org/springframework/amqp/rabbit/connection/LocalizedQueueConnectionFactoryTests.java:108: error: method does not override or implement a method from a supertype

  	@Override

		^

But if it is only an issue, I'll address on merge.

Hmmm - something was lost with me switching computers; I changed that test yesterday. Let me look

Oh, I see, I just failed to remove it.

Pushed

Rebased, pushed.

That's fine merging, if that CAUTION looks good in the final Manual :smile:

Merged as https://github.com/spring-projects/spring-amqp/commit/62cf949e78704c7e376ca6c268da550c9f684c25


MAINT: stats: move shortcut calculation of mu3 where it belongs

Reference issue
scipy/scipy#15140
What does this implement/fix?
There is a shortcut for calculating mu3 in rv_continuous.stats that is out of place. The value isn't used until calculating kurtosis, so move it down there so that:

It is only calculated if needed
All other calculations it relies on have already been performed

This also makes some of the other fixes discussed in scipy/scipy#15140

Thanks a lot! @mdhaber. Merging.


Support for Background Functions in async_mainloop

Support for Background Update Functions in async_mainloop
First of all, thank you for sharing this library! It has been a big help in my project, and I truly appreciate you've shared this lib.
Need
In my project, I encountered a scenario where I didn’t need an async function triggered by an element like a button press.  Instead, I needed a background update function that would run continuously and regularly perform updates.
Solution
Thanks to your work, I was able to achieve this fairly easy by a small tweak to your code. Specifically, by modifying the following section:
https://github.com/insolor/async-tkinter-loop/blob/7dd8f02033de3d9060e2be22d160294b5844edbc/async_tkinter_loop/async_tkinter_loop.py#L46-L55
Modified Code:
def async_mainloop(root: tkinter.Tk, custom_coroutine) -> None:
    """
    A function, which is a substitute to the standard `root.mainloop()`.

    Args:
        root: tkinter root object
    """
    coroutines = [custom_coroutine, main_loop(root)]
    get_event_loop().run_until_complete(asyncio.gather(*coroutines))

This change allows me to pass a custom update function to async_mainloop. Here's an example of how I used it in my project:
Example Usage:
async def update():
    """
    Demonstration update function
    """
    while True:
        print("Some task")
        await asyncio.sleep(1)

async_mainloop(root, update())

With this approach, I can easily run an asynchronous background task while using the async_mainloop. This is particularly useful for dynmic updates of the UI or performing other background tasks like webscraping.
Request
Would you consider adding support for this use case to the library? I believe this feature would be a valuable addition for users who need to run background tasks alongside their Tkinter applications.
Thank you again for sharing your work, i hope i can give something back to the community with this! Let me know if you'd like further clarification or a pull request for this suggestion.
Best regards,
Mo-to

There is no need in such modifications. Just use loop.create_task() to create background tasks. See https://github.com/insolor/async-tkinter-loop/blob/main/examples/start_stop_counter.py example. Just replace start/stop logic in this example with your infinite loop, and it will work.

Closing, because background tasks are already supported (through loop.create_task())


add storage for velocity controls to please TAF

What changes does this PR introduce?
(Bug fix, feature, docs update, ...)
This is really a small fix. When initial uvel/vvel fields are in the control vector, i.e.
defined ALLOW_UVEL0_CONTROL && defined ALLOW_VVEL0_CONTROL
TAF complains that it needs to recompute these fields within packages_init_variables. This probably isn't a big savings in compute time, but since this likely applies to all the ECCO, SOSE, ASTE, et al folks (at least), I thought I'd introduce the PR...
What is the current behaviour?
(You can also link to an open issue here)
TAF gives a warning about some extra recomputations.
What is the new behaviour
(if this is a feature change)?
This is fixed.
Does this PR introduce a breaking change?
(What changes might users need to make in their application due to this PR?)
Other information:
Suggested addition to tag-index
(To avoid unnecessary merge conflicts, please don't update tag-index. One of the admins will do that when merging your pull request.)

@timothyas I took a quick look, and it seems it's the first time these 2 CPP options appear in main
model/src code. I seach for them in current verification exp. (as well as in verification_other) but did not find any example that defines any of these 2 options. They don't appear anywhere neither in any
pkg/${PKG}_OPTIONS.h file.

I would suggest to add/document these 2 options (set to #undef + 1 line of comment in
one of the 2 files, either in:
https://github.com/MITgcm/MITgcm/blob/master/pkg/ctrl/CTRL_OPTIONS.h
(where we already have option for initial Theta & Salt controls)
or in:
https://github.com/MITgcm/MITgcm/blob/master/pkg/ecco/ECCO_OPTIONS.h
although it seems less natural there.
not clear to me why you added these 2 storage dir only when both UVEL0 and VVEL0 options
are defined. I would have thought that it would be safer to add these storage dir any time one of
the 2 is defined.

Thanks for the review @jm-c!

Done, I added these to CTRL_OPTIONS.h since I agree, it seems more natural than ECCO_OPTIONS.h. I also added these to the documentation since it seems they aren't listed there either.

I borrowed the same logic as what is in ctrl_map_ini_genarr since this seems to be what is causing the TAF recomputation warning. I would guess that this is for LLC type grids, where the model uvel/vvel is not the usual definition.

The second issue brings up the fact that even if someone uses generic controls, they additionally have to define these macros to use initial velocity as a control variable. The same is true for bottom drag and geothermal flux (see ctrl_map_ini_genarr). Should I add a note about this in the documentation and/or CTRL_OPTIONS.h?

LGTM +1
Will try to merge this PR tomorrow.

Thanks @jm-c!


README.md: fix specification links

I am now using the older links, but for some reason I'm still sometimes redirected to the new versions when I click on them. This happens when I show the rich diff in files changed and just click on the links like a user would. Can you see if this also happens for you @s-heppner?


remove requestauthentication resource

Summary

The RequestAuthentication reosource in the kubeflow namespace is obsolete. It caused IRSA to modify the jwt issuer, leading to the observed exceptions.
This PR is related to issue #146 .
I tested the change by accessing kubeflow pipelines as described in the linked issue.
Test Plan

Checklist

[ ] My change requires a change to the documentation and I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.

@ncbkr Can you bump the chart version?


[Bug]: Prism Launcher 6.0 not automatically updated

Prerequisites

[X] I have written a descriptive issue title.
[X] I have searched all issues/PRs to ensure it has not already been reported or fixed.
[X] I have verified that I am using the latest version of Scoop and corresponding bucket.

Package Name
Prism Launcher
Expected/Current Behaviour
scoop update should show the  latest Prism Launcher release, wich is 6.0, but doesn't update
Steps to Reproduce
scoop update

Possible Solution
Change autoupdate to https://github.com/PrismLauncher/PrismLauncher/releases/download/$version/PrismLauncher-Windows-MSVC-Portable-$version.zip possibly?
Scoop and Buckets Version
❯ scoop --version
Current Scoop version:
v0.3.1 - Released at 2022-11-15

'404NetworkError' bucket:
13a127f (HEAD -> main, origin/main, origin/HEAD) jazz2-resurrection: Update to version 1.3.0

'extras' bucket:
72a18b50a (HEAD -> master, origin/master, origin/HEAD) mobaxterm: Update to version 22.3

'games' bucket:
89167f92 (HEAD -> master, origin/master, origin/HEAD) ryujinx: Update to version 1.1.468

'java' bucket:
93dd38f8 (HEAD -> master, origin/master, origin/HEAD) graalvm-nightly: Update to version 23.0.0-dev-20221212_0450

'main' bucket:
c75ad152a (HEAD -> master, origin/master, origin/HEAD) sourcegraph-cli: Update to version 4.3.0

'nerd-fonts' bucket:
39e48e8 (HEAD -> master, origin/master, origin/HEAD) SarasaGothic: Update to version 0.38.0

'nonportable' bucket:
293da1b (HEAD -> master, origin/master, origin/HEAD) parsec-np: Update to version 150-86g

'versions' bucket:
9d23b43e (HEAD -> master, origin/master, origin/HEAD) ipfilter-nightly: Update to version<PHONE_NUMBER>

Scoop Config
❯ scoop config

last_update         scoop_branch scoop_repo
-----------         ------------ ----------
12/12/2022 19:36:06 master       https://github.com/ScoopInstaller/Scoop

PowerShell Version
❯ $PSVersionTable

Name                           Value
----                           -----
PSVersion                      7.3.0
PSEdition                      Core
GitCommitId                    7.3.0
OS                             Microsoft Windows 10.0.22000
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

Additional Softwares
No response

c951bef has been pushed that updates Prism Launcher to v6.0


Update ERC-7631: Update ERC-7631

This updates the ERC-7631 proposal to address:

Choice of boolean return value for getSkipNFT.
Optionality of explicitly implementing getSkipNFT and setSkipNFT.
Rare NFT sniping concerns.

LGTM

LGTM

LGTM


Improve error for incompatible generic arguments for WeakRef

Closes #11833

I'd prob also add something to the docs to make this more clear before you go to do it. E.g. via the WARNING admonition

The proper check is probably T <= Reference?. A similar one is used by Box(T).

I believe standard library specs are only allowed to use compile_file, not assert_error.


[REQUEST] New Pencil function

Shift+left-click on a block with a Pencil should spawn "Building Unit Template" of all similar connected blocks. (Not work with Blueprint blocks, for a reason)
Example:
You see statue made of diamond and gold blocks you would like to copy, you take pencil, select color, Shift+left-click diamond block and get template of all diamond blocks that touch each other. With color you selected.
You change color and Shift+left-click gold block, get template with other color blocks.
Then you can use Building Unit to spawn different parts of statue, and then "build" it using blocks you like.

And another Pencil function:
Shift+right-clicking on Bluepring block will adopt it's color.

I got change of idea.
Pencil:
Left-click will add overlay to a blocks (some form of highlight), with color, of course.
Shift+Left-click will add overlay to all similar and touching blocks.
Eraser:
will remove highlight
Then you can use Building Unit to make a Template of all highlighted blocks and blueprint blocks.

I like this idea but couldn't we just:

Add button that toggles between reading Blueprints and Blocks
When in block mode, the Unit will read anything in the area.
Blocks will be converted into Blueprints (Example: the first block it sees is black, then the next different block is gray etc) Allowing 16 different blocks to read in one single action.

This allows players to copy their creations that are already built. Also the Markers can be used to determine it's size so players can control what they want read.


Change log timestamp to ISO8601 w/ timezone

This prevents ambiguity when, say, running falco in a container, which
may have a different /etc/localtime than the host system.

Fix #527

@lorenzo-david can you review for @mstemm

Actually, this still requires some work before it's ready to review.


kie-server tests: refactored kie client

backport of #327 to 6.4.x
(cherry picked from commit 42b0e34e91d0f04a0152ae7c49ae7c63afc80d1f)

merged into 6.4.x


A solution for Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'attempt to insert row 2 into section 1, but there are only 0 rows in section 1 after the update'

I would like to share a solution I developed for those experiencing issues with #3384 but I am unable to comment on the issue since it's locked. This is my solution:
/// Used to group change notifications that occur within the same table view.
class SectionedNotificationTokenBlock {
    struct Changes {
        var deletions = [IndexPath]()
        var insertions = [IndexPath]()
        var modifications = [IndexPath]()
    }
    private var queuedChanges = Changes()
    /// Called with all queued changes.
    private var updateBlock: (Changes) -> Void
    /// Groups change notifications that occur within the same table view.
    ///
    /// - Parameter updateBlock: The block to be called whenever an update occurs.
    init(_ updateBlock: @escaping (Changes) -> Void) {
        self.updateBlock = updateBlock
    }
    /// Returns a closure you can provide as the handler for `observe`.
    ///
    /// - Parameter section: The section of the content in your table view.
    func block<CollectionType>(forSection section: Int, initialBlock: (() -> Void)? = nil, errorBlock: ((Error) -> Void)? = nil) -> ((RealmCollectionChange<CollectionType>) -> Void) {
        return { change in
            switch change {
            case .error(let error):
                errorBlock?(error)
            case .update(_, let deletions, let insertions, let modifications):
                self.queuedChanges.deletions.append(contentsOf: deletions.map { IndexPath(row: $0, section: section) })
                self.queuedChanges.insertions.append(contentsOf: insertions.map { IndexPath(row: $0, section: section) })
                self.queuedChanges.modifications.append(contentsOf: modifications.map { IndexPath(row: $0, section: section) })
                OperationQueue.current?.underlyingQueue?.async(execute: self.drainQueue)
            case .initial(_):
                initialBlock?()
            }
        }
    }
    /// Calls the sectioned notification token block with all changes.
    private func drainQueue() {
        guard queuedChanges.deletions.count > 0 || queuedChanges.insertions.count > 0 || queuedChanges.modifications.count > 0 else { return }
        self.updateBlock(queuedChanges)
        self.queuedChanges = Changes()
    }
}

And to use it:
let sectionedNotificationTokenBlock = SectionedNotificationTokenBlock { (changes) in
    self.tableView.performBatchUpdates({
        self.tableView.insertRows(at: changes.insertions, with: .automatic)
        self.tableView.reloadRows(at: changes.modifications, with: .automatic)
        self.tableView.deleteRows(at: changes.deletions, with: .automatic)
    })
}
rows1NotificationToken = rows1.observe(sectionedNotificationTokenBlock.block(forSection: 0, initialBlock: {
    self.tableView.reloadSections([0], with: .automatic)
}, errorBlock: { (error) in
    print("Realm error reloading rows", error)
}))
rows2NotificationToken = rows2.observe(sectionedNotificationTokenBlock.block(forSection: 1, initialBlock: {
    self.tableView.reloadSections([1], with: .automatic)
}, errorBlock: { (error) in
    print("Realm error reloading rows", error)
}))

This should work well for anyone having trouble with errors like this:

*** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'attempt to insert row 2 into section 1, but there are only 0 rows in section 1 after the update'

It works by combining updates from multiple notification tokens together and then processing them at the end of the current dispatch queue. There may be bugs/memory leaks but overall this solution has been working quite well for me.
I've made a demo project here: https://github.com/IsaiahJTurner/realm-bug-report
The project has two commits. In the first commit you will see a simple reproduction of this issue. In the second commit, you will see how this solution is used to solve the problem.

If a collaborator can link to this ticket on #3384 I think it would be very helpful for others.

Oh, important note! This won't work if you do multiple writes sequentially because the operation queue will group multiple updates for the same section together.
Ideally, I wanted to call drainQueue after all callbacks were called (basically at the end of the void CollectionNotifier::after_advance() implementation) but that code is in C++ so it's not possible to swizzle.
The easiest way to prevent multiple writes from being stacked on the operation queue is to call them async. I use this since I also wanted to use promises but anything that wraps .write in OperationQueue.current?.underlyingQueue?.async will work.
func write<T>(_ block: @escaping (() throws -> T)) -> Promise<T> {
    return Promise { seal in
        OperationQueue.current?.underlyingQueue?.async {
            self.realm.beginWrite()
            do {
                let result = try block()
                if self.realm.isInWriteTransaction { try self.realm.commitWrite() }
                OperationQueue.current?.underlyingQueue?.async {
                    seal.fulfill(result)
                }
            } catch let error {
                if self.realm.isInWriteTransaction { self.realm.cancelWrite() }
                seal.reject(error)
            }
        }
    }
}

When applying updates to the UI, can you try avoiding using a custom OperationQueue?

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.

This solution never fully worked for us and we've finally worked our our perfect solution:
func set(activityItemIds newIds: [String]) {
		guard let oldIds = self.activityItemIds, oldIds.count > 0 else {
			self.activityItemIds = newIds
			self.tableView.reloadData()
			return
		}
		var deletedRows = [Int]()
		var movedRows = [(fromRow: Int, toRow: Int)]()
		var insertedRows = [Int]()

		for (oldRow, id) in oldIds.enumerated() {
			if let newRow = newIds.firstIndex(of: id) {
				if newRow != oldRow {
					movedRows.append((fromRow: oldRow, toRow: newRow))
				}
			} else {
				deletedRows.append(oldRow)
			}
		}

		for (newRow, id) in newIds.enumerated() {
			if !oldIds.contains(id) {
				insertedRows.append(newRow)
			}
		}

		tableView.performBatchUpdates({
			self.activityItemIds = newIds
			tableView.deleteRows(at: deletedRows.map { IndexPath(row: $0, section: 0) }, with: .automatic)
			movedRows.forEach { tableView.moveRow(at: IndexPath(row: $0.fromRow, section: 0), to: IndexPath(row: $0.toRow, section: 0)) }
			tableView.insertRows(at: insertedRows.map { IndexPath(row: $0, section: 0) }, with: .automatic)
		}) { (completed) in
			print("Updated feed with result:", completed)
		}
	}

You will need to tweak this substantially to work for your exact use case but essentially, we compare the new array of ids with the old array of ids and manually create the move/delete/inserted rows. This abstracts our table view away from the results collection and prevents crashing.


Upgrade to .48 missing node list entity's in 'Z-Wave Node Management'

Home Assistant release (hass --version):
0.48.0
Python release (python3 --version):
Python 3.4.2
Component/platform:
Zwave
Description of problem:
Z-wave node list menu is empty after upgrading to .48

^ shows nothing when opening.
Expected:
To show z-wave devices.
I do see z-wave devices, and i can still manage them and turn them on/off so the stack seems fine. Just the menu shows nothing anymore.
Using opt-out on the new z-wave entity id's didn't change anything. Same issue. Rebooted rpi and restarted browser too.

I have the exact same issue. Running dev.

On Firefox mine randomly showed up just fine after a few hours and a few restarts of hass.

On Chrome mine randomly showed up too, took some hours too. Restarted hass to be sure, seems to populate now straight away. @happyleavesaoc are you still having this issue?

Yep, I am. Just checked in Chrome and FF

(i did opt out on the new id's, perhaps it restored somehow) or it needed to wake up every device before it went 'ok' on my end. I just did a full restart with the new id's and i can still see the list. Presume it has something to do with how the zwave stack saves data in the zwcfg config? That after some time the culprit was overwritte/fixed and the drop down list worked again.
Leaving the ticket open for you @happyleavesaoc ;-)

Same problem here, using Chrome and FF. Upgraded to 0.48.1 and the issue still exists. Restated HA, restarted browsers, cleared browser caches, issue persists.

Had to wait almost a full day before it showed normal again, really think it has something to do with updates to the zwcfg file. Have not been able to reproduce the issue after it was "ok" again, if you made no changes to zwave renames you can always remove your file (make a backup ofcourse) restart and see if the issue persists. If it does, it could be something in that file.

I have my zwcfg_0x*.xml file symlinked to the OZWCP file, so mine is always up to date. I am always experiencing this issue on 0.48.1. Unfortunate timing as well, seeing as how this was the release where the new Z Wave entity ids were made default.

I have it hidden too. That must be why. But I have it hidden for a reason! I don't want to see all those ...

Maybe you can hide them individually instead?

@ddykhoff Thank you for sharing, this immediately resolved it for me. Which makes me sad... I really did not want to see all of those entities in my front-end. This is what I had in my configuration.yaml:
customize_domain:
  zwave:
  hidden: true

I only had a few zwave entities hidden but not all. Still it showed up after some time. But the end result here is that the node list might not be populated in certain conditions when zwave devices are hidden in customize. Is this something you could check @turbokongen ? (assuming you worked on it)

I would've expected the Z-Wave configuration to show all nodes that are part of the Z-Wave network regardless of nodes hidden by using "customize". I don't want to see all the "zwave.*" nodes on the states page, but I still want to be able to edit them in the Z-wave configuration.

Just ran into this bug. The zwave configuration certainly shouldn't be hiding any nodes regardless of the customize settings.

I think we can all agree that we are so many updates further along the line that this issue is no longer a problem.


Fix value annotation in isValid method for Regex validator.

Changed annotation for parameter value in isValid method for Regex validator, from string to string|numerical as long as this method accepts also integer and float parameters.

Thanks for your work here @h3nnry - #280 has been merged into 3.0.x, so I think this PR is no longer relevant.


Add update checker

Closes #222 by adding the Alteryx open-source update checker. The update checker will automatically check if there's a newer release of Compose available.

There are breaking changes in the doc tutorials. Also, there seems to be an issue with the Codecov upload -- possibly related to the same issue encountered here. I'll open new issues to track these.


Vagrant support

Local development is much easier if you can get the environment preconfigured.

Closing this as we already have support for Docker.


Update to 1.21.4

This is just a quick patch for Minecraft 1.21.4.
I implemented the fix for RealmsUploadScreenMixin.java a little differently compared to #56  since adding injecting at <init> didn't seem quite right to me. It should be closer to the original intention of the injection now. If you need further explanation I'm happy to elaborate.
I've put a compiled release on my forked repo under releases so it's a bit easier for someone who doesn't know how to compile a mod to get their hands on it. If that's not cool with you just let me know, and I can take it down.
P.S. I've never updated a mod before, so if I did anything incorrectly, please let me know!

I wont be able to review this update until sometime in january, but Im completely fine with the build on your repo, thank you very much! :)

Sounds good! Thanks for the quick reply!


Reorganize and update info about customizing KLT in Helm chart and manifest

Goal
Make installation instructions more complete and easier to follow
Problem
The current Installing KLT section has some deficits:

Info about modifying the Helm chart follows the information about installing from the Helm chart whereas it must be done before installation
We do not document how to modify the manifest before installation.  We do say that the manifest does not allow for customizations but that is not exactly true
The Use your own cert-manager (optional) page is free-standing and before the page about installing from the Helm chart.  Currently it only includes info for modifying the manifest and it should also show how to modify the Helm chart
We do not document how to use Helm chart to update an installation done with a manifest

Technical Details
To discuss: When will we drop support for installing from manifests?  Can we live with the unhappy mix of Helm and manifest info we have until then?
DoD

Add "Modifying Helm charts and manifests before installation (optional)" page before "Install and Enable KLT"

Move what is currently the Modify Helm configuration options to the top of this section
Add sub-section "Modify manifest configuration options" section
Move Use your own cert-manager (optional) page as a sub-section
Add sub-section with example of how to modify the Helm chart or manifest to only install metrics-operator rather than all of KLT
Add sub-section that discusses how to resize the resource footprint by modifying the Helm chart or manifest

Add information about configuring your own cert-manager in the Helm chart
Add information to Upgrade about how to use the Helm chart to update an installation that was done with a manifest

### Tasks
- [ ] https://github.com/keptn/lifecycle-toolkit/issues/1176
- [ ] https://github.com/keptn/lifecycle-toolkit/issues/1547
- [ ] https://github.com/keptn/lifecycle-toolkit/issues/1622

I suggest waiting 'till https://github.com/keptn/lifecycle-toolkit/issues/1588 is completed since it will impact the Helm Charts.

This ticket is outdated, it can be closed


Add missing parameters to the nan<x> functions

Rel. #6198.
NumPy 1.22 added missing parameters for some nan<x> functions.

A number of the nan functions previously lacked parameters that were present in their -based counterpart, e.g. the where parameter was present in numpy.mean but absent from numpy.nanmean.

https://numpy.org/devdocs/release/1.22.0-notes.html#missing-parameters-have-been-added-to-the-nan-x-functions

[ ] nanmin: initial & where
[ ] nanmax: initial & where
[ ] nanargmin: keepdims & out
[ ] nanargmax: keepdims & out
[ ] nansum: initial & where
[ ] nanprod: initial & where
[ ] nanmean: where
[ ] nanvar: where
[ ] nanstd: where

Hey @takagi
I am interested in this issue.
But a bit confused.
How should I get started?

Thanks for your interest, @Alt-Shivam! Can I have the points you get confused?

"Steps to Contribute" section in #6078 would be a good starting point. Please begin with trying to build CuPy and run some test on your local.

@takagi @pri1311 is someone working on this ? or is it up for the grab ? I looked into numpy's nan functions and I am also checking how the functions are implemented in cupy. If no one is working on this I can check further and work on it.

Please go ahead as no progress for months, @praburocking!

@takagi I will start looking into this and will post here  if there is any roadblock.

Hi, please excuse my negligence, but I am confused about how would you pass the identity variable to the create_reduction_func. For all previous implementations, I have seen, it only has hardcoded values of None, 1, or 0.
Also, keepdims is already a supported argument, just undocumented.
As for where, is it just a simple change of using cupy.where as I believe create_reduction_func does not support where argument just yet?

how would you pass the identity variable to the create_reduction_func

We have two options:

Change the reduction kernel to take identity at runtime
Create another reduction kernel instance when it takes initial other than the default

Also, keepdims is already a supported argument, just undocumented.

👍

As for where, is it just a simple change of using cupy.where as I believe create_reduction_func does not support where argument just yet?

It currently doesn't support it. We may use cupy.where together, but it needs extra memory to have the result of where. cupy.ufunc internally supports _where keyword parameter, and its code may help you.
https://github.com/cupy/cupy/blob/9395dbe22ddb591df6e3d044c8b6877fcbbf7b99/cupy/_core/_kernel.pyx#L973-L978

Change the reduction kernel to take identity at runtime

I was already working on this, however, if you suggest the second option, I will go with that.

cupy.ufunc internally supports _where keyword parameter, and its code may help you.

Alright, got it. 👍


Questions about PascalVOC-SP and COCO-SP

I found that the feature vector of these two datasets is 14-dimension, but when I read your paper ,  the description in this paper is " The initial feature of each superpixel node is 12 dimensional RGB feature value (mean, std, max, min) ".
So I don't particularly understand why the features are actually fourteen-dimensional. Could you please explain to me? Thanks for your kindness.

Hi @HB-pencil-zero, thank you for pointing this out.
The node feature vector is indeed 14-dimensional (12 dim RGB features + 2 dim coordinates) as mentioned in Table 1.
The sentence that you refer to (in Section 3.1) misses to include the phrase about the 2 dimensional coordinate. We will correct this sentence and update the paper.

Thanks for your nice explaination and your kindness，and now I can understand the dataset.
@.***
@.***
---- Replied Message ----
From Vijay Prakash @.>Date 10/28/2022 21:41To @.>Cc Huang<EMAIL_ADDRESS>Re: [vijaydwivedi75/lrgb] Questions about PascalVOC-SP and COCO-SP (Issue #7)
Hi @HB-pencil-zero, thank you for pointing this out.
The node feature vector is indeed 14-dimensional (12 dim RGB features + 2 dim coordinates) as mentioned in Table 1.
The sentence that you refer to (in Section 3.1) misses to include the phrase about the 2 dimensional coordinate. We will correct this sentence and update the paper.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>


fixed some escpaing issues, removed dead code, eslint

Note: Need to adjust to 3.4.5 and merge then to 3.4


Relax tolerance of im2col test

Fixes #8035

Before this PR: 2 failures in 180,824 trials
With this PR: No failure in 1,000,000 trials

Jenkins, test this please.

Jenkins CI test (for commit 2ba4afa4ecaed6bdef57582b9a228b6d3090e3be, target branch master) succeeded!

LGTM.

Jenkins CI test (for commit 2ba4afa4ecaed6bdef57582b9a228b6d3090e3be, target branch master) failed with status FAILURE.


Ignore empty directories for source task

Follow up of #15147 to see what will fail.

@bot-gradle test this

OK, I've already triggered ReadyForMerge build for you.

Closing since this was only to try out if any tests fail.


Source generator tweaks

Various source generator tweaks and improvements:

The comment field is now immutable (we were already refusing to parse any classes/enums/properties that didn't have one so it made sense to do)
Optimizing the parsing of various properties depending on the type (eg. only parsing schema:domainIncludes for properties only)
Deserializing the HTTP stream for the JSON rather than a string buffer (note the HttpCompletionOption which helps this) which can improve performance and allocations
Removes the additional Task.Run in the generator's initializer
Caches schema object data between different runs of the source generator for the different targets

Other plans:

~Investigate whether the source generator is triggered for every target (if so, see if we can cache the JSON)~
Any other performance improvements in processing the JSON

Other notes:

Found a weird quirk with #261 that it compiles with dotnet build but not msbuild or via Visual Studio. See dotnet/roslyn#52017 - the CI isn't affected as far as I can tell.

Investigate whether the source generator is triggered for every target (if so, see if we can cache the JSON)

Confirmed - initialization and executing occur multiple times. Next check will be if they use the same instance of the generator and if they do, we can skip the initialization if the SchemaObjects property is not null.
Example Log

Initialize: 21/03/2021 5:21:30 AM
Execute: 21/03/2021 5:21:30 AM
Initialize: 21/03/2021 5:21:39 AM
Execute: 21/03/2021 5:21:39 AM
Initialize: 21/03/2021 5:21:40 AM
Execute: 21/03/2021 5:21:40 AM
Initialize: 21/03/2021 5:21:40 AM
Execute: 21/03/2021 5:21:40 AM
Initialize: 21/03/2021 5:21:40 AM
Execute: 21/03/2021 5:21:40 AM

Next check will be if they use the same instance of the generator and if they do, we can skip the initialization if the SchemaObjects property is not null.

Unfortunately they use different instances however as a static property, we can share data between them. The multi-target builds seem to overlap so adding some locking to it seems like a good idea.

Nice nice improvements. Do you think we can release a major version after this?

We can, yeah. I do want to try and get pending types but that may be better after.

LGTM


[Security] Babel vulnerable to arbitrary code execution when compiling specifically crafted malicious code

Please see https://github.com/advisories/GHSA-67hx-6x53-jw92
Thanks

Thanks for updating the yarn.lock @pyramation, I can now remove the resolution in our package.json.

In fact still not fixed.
<EMAIL_ADDRESS>uses "@cosmwasm/ts-codegen" "0.35.7" which uses "@babel/traverse" "7.18.11"


Firmware failing to start?

Problem

See the code here: https://www.bittysoftware.com/temp/touchpad_control.js

Build and install that project that and you'll see a message scroll across the screen on start-up.

Uncomment the last line:

// control.onEvent(TOUCHPAD_CONTROL, 0, touchpadControl)
Build again and reinstall and you'll find that the start message does not appear and there's no Bluetooth advertising, suggesting the code has not started at all or crashed somewhere.
Expected behavior
With the stated line uncommented, the device should still start up with the same message scroll across the screen and Bluetooth advertising started.
Desktop (please complete the following information):

OS: Windows 10
Browser Chrome
Version 70

Smartphone (please complete the following information):

N/A

Additional context

Most likely running out of memory https://github.com/lancaster-university/microbit-dal/issues/390
Get Outlook for iOShttps://aka.ms/o0ukef

From: Martin Woolley<EMAIL_ADDRESS>Sent: Monday, November 12, 2018 8:48 AM
To: Microsoft/pxt
Cc: Subscribed
Subject: [Microsoft/pxt] Firmware failing to start? (#4995)
Problem

See the code here: https://www.bittysoftware.com/temp/touchpad_control.jshttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.bittysoftware.com%2Ftemp%2Ftouchpad_control.js&data=02|01|jhalleux%40microsoft.com|d40e3bd916c8402ab6c708d648beb540|72f988bf86f141af91ab2d7cd011db47|1|0|636776381255245906&sdata=dKyWFaUh0nD4kfa8PvcC16VQm1qvtrL71neEKpmbfJw%3D&reserved=0

Build and install that project that and you'll see a message scroll across the screen on start-up.

Uncomment the last line:

// control.onEvent(TOUCHPAD_CONTROL, 0, touchpadControl)
Build again and reinstall and you'll find that the start message does not appear and there's no Bluetooth advertising, suggesting the code has not started at all or crashed somewhere.
Expected behavior
With the stated line uncommented, the device should still start up with the same message scroll across the screen and Bluetooth advertising started.
Desktop (please complete the following information):

OS: Windows 10
Browser Chrome
Version 70

Smartphone (please complete the following information):

N/A

Additional context
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoft%2Fpxt%2Fissues%2F4995&data=02|01|jhalleux%40microsoft.com|d40e3bd916c8402ab6c708d648beb540|72f988bf86f141af91ab2d7cd011db47|1|0|636776381255255910&sdata=CT%2BT%2FRAe18Dd7uwTruWOx9mW1mi4sstE%2BEDP7x8P4IM%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAD-4KbyLrwcqvXj8iEy6xNfcJKsD_DgIks5uuaZegaJpZM4YaCYE&data=02|01|jhalleux%40microsoft.com|d40e3bd916c8402ab6c708d648beb540|72f988bf86f141af91ab2d7cd011db47|1|0|636776381255265923&sdata=Tl5tulus36FYW%2FRL%2Bdfh2ZOziXtOMZTmMpKPhT5enoI%3D&reserved=0.

Write a C++ sample to see if the same issue happens

I already have. I'm essentially converting some working C/C++:
http://www.bittysoftware.com/tutorials/solutions/controller/bc_4tronix.cpp


Get headers

I'm missing functionality to get header names

Is the header event what you want?
https://github.com/Keyang/node-csvtojson#header


mj-column does not align in the center on Outlook where is a background image

Hi
When using the following MJML the column is not centered on Outlook
<mjml>

  <!-- Head -->
  <mj-head>
    <mj-attributes>
      <mj-text padding="5px 0px 10px 0px" />
      <mj-section padding="0px" />
      <mj-image padding="0px" />
      <mj-all font-family="Arial" font-size="14px" />
    </mj-attributes>
  </mj-head>

  <mj-body background-color="#EAEAEA">
    <mj-section padding="20px 40px 0px 40px" background-color="#ffffff" background-url="https://via.placeholder.com/1400" background-size="300px">

      <mj-column background-color="#ffffff" width="80%" padding="0px 0px 0px 0px">

        <mj-text padding="20px 10px 20px 10px" align="left" font-size="24px" font-weight="600" line-height="26px" color="#1a2746">
          This column is not centered on Outlook
        </mj-text>

      </mj-column>

    </mj-section>

  </mj-body>
</mjml>

Potentially related to this:
https://github.com/mjmlio/mjml/issues/1867
But could not see a way to resolve.
Thanks

Note, removing the padding from  does seem to resolve the issue for Outlook on desktop, but does not help with what I'm trying to achieve which is retaining some of the background image on mobile.

ok, so have worked around it by using some additional CSS to add the padding on mobile. MJML is:
<mjml>

  <!-- Head -->
  <mj-head>
    <mj-attributes>
      <mj-text padding="5px 0px 10px 0px" />
      <mj-section padding="0px" />
      <mj-image padding="0px" />
      <mj-all font-family="Arial" font-size="14px" />
    </mj-attributes>

    <mj-style>
      @media (max-width:480px) {
        .mobile-section-padding {
          padding:0px 40px !important;
        }
      }
    </mj-style>

  </mj-head>

  <mj-body background-color="#EAEAEA">
    <mj-section css-class="mobile-section-padding" padding="0px 0px" background-color="#ffffff" background-url="https://via.placeholder.com/1400" background-size="300px">

      <mj-column background-color="#ffffff" width="80%" padding-left="0px" padding-right="0px">

        <mj-text padding="20px 0px 20px 0px" align="left" font-size="24px" font-weight="600" line-height="26px" color="#1a2746">
          This column is not centered on Outlook
        </mj-text>

      </mj-column>

    </mj-section>

  </mj-body>
</mjml>

But maybe let me know if there's a better way.

We have a discussion about this to replace padding by margin when applying background image within a section/hero as padding left/right are both applied to the left ( and appears off-centered).
There's not really a better way to handle that for now


stats: Reindex documents after the statistics have been calculated

:heart: Thank you for your contribution!
Description
Addresses https://github.com/zenodo/rdm-project/issues/203
List of changes:

Retrieves the statistics that have already been generated, and skips entries that are not modified
Puts the parents of the entries that are updated in a new index as a buffer
Consumes the entries from that buffer and does a Reindex, current_rdm_records_service.reindex_latest_first (THIS PART DOES NOT WORK YET!)

Checklist
Ticks in all boxes and 🟢 on all GitHub actions status checks are required to merge:

[x] I'm aware of the code of conduct.
[ ] I've created logical separate commits and followed the commit message format.
[ ] I've added relevant test cases.
[ ] I've added relevant documentation.
[x] I've marked translation strings (for relevant code).
[x] I've followed the CSS/JS and React guidelines (for relevant code).
[x] I've followed the web accessibility guidelines (for relevant code).
[x] I've followed the user interface guidelines (for relevant code).
[x] I've identified the copyright holder(s) and updated copyright headers for touched files (>15 lines contributions).
[x] I've NOT included third-party code (copy/pasted source code or new dependencies).

Third-party code
If you've added third-party code (copy/pasted or new dependencies), please reach out to an architect.
Reminder
By using GitHub, you have already agreed to the GitHub’s Terms of Service including that:

You license your contribution under the same terms as the current repository’s license.
You agree that you have the right to license your contribution under the current repository’s license.

I'm opening a new PR from this one. It will require changes in three modules


Update sacreBLEU and improve how it is called

New versions of sacreBLEU newer than 1.4 do not work with OCELoT because sacreBLEU API has changed. We should update it and improve the way how it is called in OCELoT to make potential updates in the future easier. For example, we can write a simple wrapper for computing BLEU and ChrF outside Django models.

Would be great to update sacreBLEU for WMT22.

Agreed. Will look into it.
On Thu, Jun 30, 2022, 6:59 PM Roman Grundkiewicz @.***>
wrote:

Would be great to update sacreBLEU for WMT22.
—
Reply to this email directly, view it on GitHub
https://github.com/AppraiseDev/OCELoT/issues/23#issuecomment-1171465504,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACSH2E6WYGGTNSKCAZYAE3VRXG7FANCNFSM4YHCIBPA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

I have updated to sacrebleu v2.2, using the compat methods supporting v1.4.10 API calls. Also moved process_to_text() into our own utils as this has been changed in v2.2.

When we get to adding Score objects for various metrics, we can tackle this better. We will also need to switch to proper sacrebleu v2.2 API use when adding signature support.
On the radar for wmt22 release...


JSON completion introduces unexpected character

Description
Using the vscode-json-languageserver-bin server for auto-completion in JSON introduces unexpected characters.
Note: Following https://github.com/jupyterlab/jupyterlab/issues/16129
Reproduce

1/ Create environment
conda create -n lsp install python=3.8 jupyterlab jupyterlab-lsp json-lsp

2/ Create an empty json based on a schema
{
    "$schema": "https://json.schemastore.org/tsconfig",
}

Add a line, type ", then press Tab to see the suggestions,  select one options and press Enter

After pressing Enter , an object {} is inserted with an unexpected character $1

Expected behavior
The equivalent behavior in vscode, no unexpected character introduced

Context

Operating System and version: Windows 10
Browser and version: Chrome 123.0.6312.105 (Build officiel) (64 bits)
JupyterLab version: Version 4.1.5
Language server and version: jupyter-lsp-jupyterlab-lsp 5.1.0 & json (vscode-json-languageserver-bin)

Required: installed server extensions

(lsp) C:\Users\***>jupyter server extension list
Config dir: C:\Users\***\.jupyter
Config dir: C:\Users***\miniconda3\envs\lsp\etc\jupyter
jupyter_lsp enabled
- Validating jupyter_lsp...
jupyter_lsp 2.2.4 ok
jupyter_server_terminals enabled
- Validating jupyter_server_terminals...
jupyter_server_terminals 0.5.3 ok
jupyterlab enabled
- Validating jupyterlab...
Extension package jupyterlab took 0.2171s to import
jupyterlab 4.1.5 ok
notebook_shim enabled
- Validating notebook_shim...
notebook_shim  ok
Config dir: C:\ProgramData\jupyter

Required: installed lab extensions

JupyterLab v4.1.5
C:\Users\***\miniconda3\envs\lsp\share\jupyter\labextensions
        jupyterlab_pygments v0.3.0 enabled ok (python, jupyterlab_pygments)
        @jupyter-lsp/jupyterlab-lsp v5.1.0 enabled ok (python, jupyterlab-lsp)
Disabled extensions:
@jupyterlab/completer-extension:base-service
@jupyterlab/fileeditor-extension:language-server
@jupyterlab/lsp-extension:settings
@jupyterlab/notebook-extension:language-server

Troubleshoot Output

$PATH:
        C:\Users\***\miniconda3\envs\lsp
        C:\Users\***\miniconda3\envs\lsp\Library\mingw-w64\bin
        C:\Users\***\miniconda3\envs\lsp\Library\usr\bin
        C:\Users\***\miniconda3\envs\lsp\Library\bin
        C:\Users\***\miniconda3\envs\lsp\Scripts
        C:\Users\***\miniconda3\envs\lsp\bin
        C:\Users\***\miniconda3\condabin
        C:\Windows\system32
        C:\Windows
        C:\Windows\System32\Wbem
        C:\Windows\System32\WindowsPowerShell\v1.0
        C:\Windows\System32\OpenSSH
        C:\Program Files\Git\cmd
        C:\Program Files (x86)\Microsoft SQL Server\160\DTS\Binn
        C:\Program Files\Azure Data Studio\bin
        C:\Program Files (x86)\Microsoft SQL Server\160\Tools\Binn
        C:\Program Files\Microsoft SQL Server\160\Tools\Binn
        C:\Program Files\Microsoft SQL Server\Client SDK\ODBC\170\Tools\Binn
        C:\Program Files\Microsoft SQL Server\160\DTS\Binn
        C:\Users\***\AppData\Local\Programs\Python\Python38\Scripts
        C:\Users\***\AppData\Local\Programs\Python\Python38
        C:\Users\***\AppData\Local\Programs\Python\Python37\Scripts
        C:\Users\***\AppData\Local\Programs\Python\Python37
        C:\Users\***\AppData\Local\Microsoft\WindowsApps
        .

[I 2024-04-07 16:52:45.921 ServerApp] jupyter_server_terminals | extension was successfully linked.
[I 2024-04-07 16:52:45.945 ServerApp] jupyterlab | extension was successfully linked.
[I 2024-04-07 16:52:46.751 ServerApp] notebook_shim | extension was successfully linked.
[I 2024-04-07 16:52:46.820 ServerApp] notebook_shim | extension was successfully loaded.
[I 2024-04-07 16:52:46.828 ServerApp] jupyter_lsp | extension was successfully loaded.
[I 2024-04-07 16:52:46.834 ServerApp] jupyter_server_terminals | extension was successfully loaded.
[I 2024-04-07 16:52:46.843 LabApp] JupyterLab extension loaded from C:\Users\***\miniconda3\envs\lsp\lib\site-packages\jupyterlab
[I 2024-04-07 16:52:46.864 LabApp] JupyterLab application directory is C:\Users\***\miniconda3\envs\lsp\share\jupyter\lab
[I 2024-04-07 16:52:46.875 LabApp] Extension Manager is 'pypi'.
[I 2024-04-07 16:52:47.360 ServerApp] jupyterlab | extension was successfully loaded.
[I 2024-04-07 16:52:47.360 ServerApp] The port 8888 is already in use, trying another port.
[I 2024-04-07 16:52:47.370 ServerApp] Serving notebooks from local directory: C:\Users\***\Documents\DEV\LSP
[I 2024-04-07 16:52:47.374 ServerApp] Jupyter Server 2.13.0 is running at:
[I 2024-04-07 16:52:47.375 ServerApp] http://localhost:8889/lab?token=238a6c705333adf5ef18de2a75e907da1e6567aca215393f
[I 2024-04-07 16:52:47.375 ServerApp]     http://<IP_ADDRESS>:8889/lab?token=238a6c705333adf5ef18de2a75e907da1e6567aca215393f
[I 2024-04-07 16:52:47.376 ServerApp] Use Control-C to stop this server and shut down all kernels (twice to skip confirmation).
[C 2024-04-07 16:52:47.475 ServerApp]
To access the server, open this file in a browser:
    file:///C:/Users/***/AppData/Roaming/jupyter/runtime/jpserver-7088-open.html
Or copy and paste one of these URLs:
    http://localhost:8889/lab?token=238a6c705333adf5ef18de2a75e907da1e6567aca215393f
    http://<IP_ADDRESS>:8889/lab?token=238a6c705333adf5ef18de2a75e907da1e6567aca215393f

[I 2024-04-07 16:52:50.853 ServerApp] Skipped non-installed server(s): bash-language-server, dockerfile-language-server-nodejs, javascript-typescript-langserver, jedi-language-server, julia-language-server, pyright, python-language-server, python-lsp-server, r-languageserver, sql-language-server, texlab, typescript-language-server, unified-language-server, vscode-css-languageserver-bin, vscode-html-languageserver-bin
[I 2024-04-07 16:52:54.241 LabApp] Build is up to date
[I 2024-04-07 16:53:02.235 ServerApp] Saving file at /untitled.json
[I 2024-04-07 16:53:06.811 ServerApp] Saving file at /untitled.json
[I 2024-04-07 16:53:13.176 ServerApp] Saving file at /untitled.json

Browser Output (recommended for all interface issues)

Paste the output from your browser JavaScript console replacing the text in here.
To learn how to open the developer tools in your browser:
https://developer.mozilla.org/en-US/docs/Learn/Common_questions/What_are_browser_developer_tools#How_to_open_the_devtools_in_your_browser
If too many messages accumulated after many hours of working in JupyterLab,
consider refreshing the window and then reproducing the bug to reduce the noise in the logs.

This is a snippet completion. Apparently vscode-json-languageserver-bin is violating the LSP spec - it should not return snippet completions when client does not advertise support for these. I guess we should implement snippet support (https://github.com/jupyter-lsp/jupyterlab-lsp/issues/208) now that CodeMirror 6 migration headaches are over.


Fix for #8.  Pad percentage outputs

This resolves issue#8

Please discard this PR. See #17 instead.


Allow protobuf export to idiomatic Go

Thanks for making this library, it's a really good initiative and I would like to contribute by adding some support for exporting to Go.
Currently I only added support to the compile_single.py script as it is already reading the contents of the files and modifying the temporary intermediary. If we want to add support for the recursive compilation, we would also have to create temporary files that can be interpreted and modified before running through protoc.
I hope at least these few changes are alright!

Cloned and ran with different params, got no errors while testing, so it's good to go i think :-)
Thank's for your work + contribution!

hey sorry for pulling this up after it's closed. is there a reason why the proto are compiled to separate packages? @zeeraw
it's screwing with my build and vendoring

Hey @pxue, I couldn't get protoc to compile if they were all combined in one package. I would get conflicts. If you have any ideas of how it could all be compiled to one package, that would be cool. Personally I would also like to get the recursive compilation working to have a 1:1 mapping between the proto & go packages.

ah okay. Yes, the Go work around is to pass all proto files as to the protoc command. ie,
protoc --proto_path=tmp --go_out=out tmp/*.proto
that'll allow you to compile all proto files under the package specified with option go_package


Connection string is invalid

I have submitted a secret using function app publish profile in repository.
name for secret is AZURE_FUNCTIONAPP_PUBLISH_PROFILE
and value is data given in Publish profile.
Here is the script: Please help
on:
#workflow_dispatch:
push:
branches:
- developer
paths:
- 'appsettings.json'
jobs:
syncconfig:
runs-on: ubuntu-latest
steps:
# checkout done so that files in the repo can be read by the sync
- uses: actions/checkout@v1
- uses: azure/appconfiguration-sync@v1
with:
configurationFile: 'appsettings.json'
format: 'json'
# Replace  with the name of the secret in your
# repository
#publish-profile: ${{ secrets.AZURE_FUNCTIONAPP_PUBLISH_PROFILE }}
connectionString: ${{ secrets.AZURE_FUNCTIONAPP_PUBLISH_PROFILE }}
separator: ':'

@arpitmishra-eaton you should obtain the connection string from your Azure App Configuration store. From the Azure Portal, navigate to your App Configuration store -> Access keys -> copy one of Read-write keys.

with this, Can i update app setting of function app, please?

This GitHub action is to update settings in Azure App Configuration. It's not to update settings in Function App. You can, however, load settings in Azure App Configuration from your Function App.
https://docs.microsoft.com/en-us/azure/azure-app-configuration/quickstart-azure-functions-csharp

oh, Thanks! is there a way we can update app setting of function app using Github Action or the pipeline, please

That's a question you may like to reach out to the Azure Functions team https://github.com/Azure/azure-functions-host.

Thanks Much @zhenlan


Sprint 4 Closure and Plan

Sprint 4 Exiting Level Plans
For exiting the level we planned on having the player collect all coins/shells/diamonds (whatever) until they can leave the level. Some things we have to do to achieve this:

Adding more coins/shells, because collecting only 3 of them would most likely be a bit too easy, so we agreed on for starters having 5 of them.
Removing the chest/exit until player has collected all the coins. This is something that could be done with if statements in the game logic so that is something we will work on.
making sure there are no other ways that allow the player to leave the level unless completing the task
Bonus: Stating the task somewhere, like for example adding a text bubble so that it is clear for the player what to do.
Note: I've had an issue with changing the sprite for the diamonds/coins in the water level even after asking multiple sources including teachers, classmates, teammates and ChatGPT. (I'll send you the code over Slack so that you can take a closer look at it)

For Me so far It has been like a failure so far I tried working on changing the end level as I am trying to collect the whole coin to the exit level however I have wanted to do it with GameSetetrWater.JS but, It failed miserably because the code either crash or didn't work but I am striving towards success here what I mean. I tried using gamesetetrwater.js  but it failed I am determine to solve the problem but the changes so far are the sprites change asThey t matches the team


iPhone 13 Pro Max Splash screen

Add please a new splash screen for new iPhones like iPhone 13 Pro Max.

You should try and do a pull request for this as it seems like a minor update.


BlobLeaseCLient updates itself

BlobLeaseClient will always update its internal leaseId field to match
the value from the last service response it received. This makes it
possible to use changeLease without needing to discard a lease client in
favor of a new one.
Existing tests updated to check internal values of client.

The variable field 'leaseId' of class 'BlobLeaseAsyncClient' should be final. Classes annotated with @ServiceClient are supposed to be immutable. [ServiceClient]
@alzimmermsft is there a way to disable this check for the single property?

The variable field 'leaseId' of class 'BlobLeaseAsyncClient' should be final. Classes annotated with @ServiceClient are supposed to be immutable. [ServiceClient]
@alzimmermsft Alan Zimmer FTE is there a way to disable this check for the single property?

Maybe wrapping this could help. I.e. keep wrapper reference final and update the wrapper.

The variable field 'leaseId' of class 'BlobLeaseAsyncClient' should be final. Classes annotated with @ServiceClient are supposed to be immutable. [ServiceClient]
@alzimmermsft is there a way to disable this check for the single property?

Yes, this single value should be excludable. Here is an example of suppressing a Checkstyle rule for a specific line, or set of lines, of code.

/check-enforcer evaluate


Fix false negative for Rails/LinkToBlank when _blank is a symbol

when using target: :_blank, the Rails/LinkToBlank cop does not register an offence when it should.

Thanks!


not enough arguments in call to kinesis.NewAuth

and 4. line of code is what I had before and it worked. Now I wanted to implement Godep but it looks like that I am a little bit too late.

First four lines below are what I had before and it worked. Now I am trying to implement it like you implemented it in example.go ... but keep getting errors...

not enough arguments in call to kinesis.NewAuth
undefined: kinesis.Region (even if i pass kinesis.Region{} as second parameter to kinesis.New function
cannot use &auth (type **kinesis.AuthCredentials) as type kinesis.Auth in argument to kinesis.New:
**kinesis.AuthCredentials does not implement kinesis.Auth (missing GetAccessKey method)

I would really appreciate some help here... since code don't work for me the way it is in example.go.
Best,
Tomaz
// KINESIS AUTHENTIACTION
// set env variables AWS_ACCESS_KEY and AWS_SECRET_KEY AWS_REGION_NAME
//auth := kinesis.NewAuth()
//ksis := kinesis.New(&auth, kinesis.Region{})

var (
	err  error
	auth kinesis.Auth
)

auth, err = kinesis.NewAuthFromEnv()
if err != nil {
	fmt.Printf("unable to retrieve authentication credentials from the environment: %v", err)
	os.Exit(1)
}

ksis := kinesis.New(auth, "")

Hello, @ulutomaz Did you looks in kinesis_test.go? Maybe this will help?

Did you get a fix on this as I have the same issue.

After working through the code I found the issue.
ksis := kinesis.New(auth, "")
should actually be
ksis := kinesis.New(auth, REGION)
where REGION is the aws region to communicate with. i.e. us-east-1


Fixes issue #31

jQuery handles events from .trigger a bit interesting in that it checks if there's a matching method and runs it instead. Since .remove is a jQuery and a dom method, that took priority.
I've namespaced all events we trigger which will break any code that relies on it. It's the only way to make sure anything else funky doesn't happen.

should'nt events be named tokens.remove instead of remove.tokens ? I think i'm seeing a lot more of tokens.remove name style out there... just to be consistent...

Just keeping it standard with jquery: http://api.jquery.com/event.namespace/

You are right. Jquery seems to suggest using "click.tokens" instead of "tokens.click". Good to know. Thanks for pointing that out!

I'm wish you though, I'd prefer it if it was .event to be more in line with everything else out there.


Add my first file

I have created a branch, created a file, and made a commit!

I think this is the end


Update metro wiki

Quarto + Dokuwiki might be useful:
https://quarto.org/docs/reference/formats/wiki/dokuwiki.html

@hancush has created documentation for scrapers here.
Next steps:

clean out parts of the existing LA Metro wiki that are superseded by info in the scrapers repo
add app-specific info

Related to scraper docs issues: https://github.com/Metro-Records/la-metro-councilmatic/issues/451

@xmedr will start moving the Metro wiki to quarto now that the scrapers one is up and running.

@camachoo @neilarellano Do you know if you folks have any internal documentation for the app that you use to help in your day-to-day? If that exists, it would be great to include that in our existing documentation. No worries if it doesn't!


Inconsistent LineHeight Desktop JVM Linux / Windows vs. Mac OS X

In a (Basic)Textfield or TextField or Text, the Lineheight specification results in inconsistent behavior on different Platforms (JVM on Linux/Windows vs. Mac OS X):
@Composable
BasicTextField(
            value = lines.value,
            textStyle = TextStyle(
                fontSize = AppTheme.fontSize,
//                lineHeight =AppTheme.fontSize*2.5f, // Needed on Mac to get correct line size that is too large for Linux.
                ),
            onValueChange = { lines.value = it  }
)

On MAC:

empty (or only space) lines get rendered with very small line height, unless lineHeight is explicitly set fo 2.5f * fontSize

On Linux/Windows:

empty (or only space) lines get rendered in the above case with much higher lineHeigt that seems to be more the intuitive expected behavior of the spec "LineHeigt".

Unclear if unclear spec, issue in above code (but: what is correct rendering, then? ), or inconsistency in Implementation on Mac vs. Linux/Win platforms.

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.


No file descriptors available Error

Hi,
After a few hours of running wstunnel as below, I got this error.
wstunnel server wss://[::]:8443

This is my limits info:

This is not related to wstunnel but to your system/workload, file descriptors are not infinite.
Either spread the load on another machine, or if you have too many idle connections, use a reverse proxy to force close inactive connections after a timeout

Hi,
If I run wstunnel like this on the client side, will the problem be solved?
wstunnel client -L 'tcp://<IP_ADDRESS>:80:localhost:80?timeout_sec=60' -L 'tcp://<IP_ADDRESS>:443:localhost:443?timeout_sec=60' wss://sub.domain.ir:8443
Thanks for your answer

It would indeed, but the timeout is only implemented for udp. As for Tcp we already know when to terminate the connection.
I strongly recommend you installing nginx/haproxy in front of wstunnel to handle those cases.


[NEW][10.0] pos_cashbox module

[NEW][10.0] pos_cashbox module

issue for unitest #662

@GabbasovDinar 2 remaining lints to be fixed

@ilmir-k DONE (I sent the PR to your branch)

@yelizariev I think it can be merged. It's ready for publication

We need to fix pos_invoice_pay and check are there other errors or not

@yelizariev We have one lint error about test only. I think we can merge it


Use H- ID as the uuid when dealing with marketplace instances

For historical reasons we use H- as the uuid for marketplace instances. So registering containers needs to be done using H-, not A- for marketplace instances. It should not be done for custom compose apps, only for marketplace.

@AdheipSingh did we deal with this ?


read all language files from theme stream

Currently when inheriting a theme and creating language files in the child theme, they will override the language files of the base theme. There is no chance to extend from the base theme language files other than copying them. This leads to a lot of manual syncing effort when updating the base theme.
themes
- child-theme
-- languages.yaml

- base-theme
-- languages.yaml <- content never loaded

I changed the language file loading to read language files from all themes in theme://.
This might be interesting for @lazybadger.

Do you really want to load all themes? Wouldnt it make more sense to only load the base theme?

Do you really want to load all themes? Wouldnt it make more sense to only load the base theme?

I am only loading all themes in inheritance chain (so this will be usually two themes, if using inheritance)! What do you do if you want to create additional language variables in child theme?

Alright, that makes sense to me.

Looks good to me too


Update README.md

I just updated the readme section for the issue

@PiyushKalyanpy please approve it

@vedprakashnautiyal, I kindly request you to review the README file.

@vedprakashnautiyal, I kindly request you to review the README file.

is someone updated the readme file previously whiy it was conflicting and also there is some change which is currently visible