cadl, multi-client on different api-version or different server

Plan is move version / url / host param to client level (avoid global level).
Version could be a problem, need to determine whether different client shared a same version (or @versioned list). So this would be likely the last to solve.

server done in https://github.com/Azure/autorest.java/pull/1982


User should have an easy way to check a list of all template params without reading docs

Reason/Context
Many templates have very different parameters that they support. Template params are always described in template configuration, to which we have access, so dropping them into the logs should not be a big deal
Description

add some meaningful flag that user can use to log params
logs that talk about warnings and errors while using template params should always have a hint about how to log all available params

Still valid. We need the such a feature (for generator) in our cli.

still valid


Accept a validation schema as a GET param

Pass it on to libhxl as a parsed JSON object (?)

@davidmegginson we think this is going to help us if we want to use some customizations from user.

@davidmegginson I think should be high priority. We need the option to send via POST and GET the content of the validation schema

OK, moved back to the 4.7 (30 April) release.

Realised that this issue belongs to the HXL Proxy, not libhxl. Closing here, and replacing with
HXLStandard/hxl-proxy#212


Enhancement [spring-cloud-config-server]: Add endpoint for .json similar to .properties, .yml, and .yaml endpoints

.yml, .yaml, and .properties require 3rd party libraries to parse whereas a json can be parsed natively by JavaScript interfacing with the config server api.
The outputs coming from {name}/{profiles} is verbose (great for debugging) but does not resolve the property that is to be used. If you want to use JSON, the logic of selecting the correct property is delegated to the client.
Suggestion: Add an endpoint for {name}-{profiles}.json and for /{label}/{name}-{profiles}.json
Mentioned in Issue #112

The method you removed explicitly removes spring.profiles though as well. Can we have that back?

That logic is still in place. Method was renamed to getPropertiesString since sortLines no longer seemed appropriate.
However, this did bring to my attention that spring.profiles is present in the .json endpoint since this method is not utilized. I will move this logic to the method generating the properties Map.
After adding another commit, do I need to close and open another pull request in order to get it included?

do I need to close and open another pull request in order to get it included?

No, just push to the same branch as you did before (and squash the commits if you are feeling helpful).

Okay. I have completed this task, ran tests, squashed commits (I think, first time using rebase here as my company only uses merge in their development cycle so for sure double check me on this), and pushed to master branch on my forked repo.
Thanks,
Chris Manning

Thanks. Final task for you: did you complete the contributor's agreement (link in README)?

I have now :+1:


Protobuf encoder improvement

Hi
I found it convenient and intuitive to subscribe with empty interface{} in case when you don't need arguments to reply with encoded response. Also it's convenient to request with nil argument.
I used this modified proto encoder for our application.
I create failed test cases in commit: https://github.com/AnatoliiPrylutskyi/nats/commit/a3c60694003763933585705ca6f89b18599a8367
Thanks

Strange error message on build, please inform me if I can fix this error.

For example:
Service "A" hold currency rates info and do not need arguments to return rates, it return currency rates on request in protobuf on topic "currencyRates".
Service "B" need to load all currency rate, so Service "B" need to request Service "A" on "currencyRates" topic with no arguments.
In current implementation I can't pass nil to Request function with protobuf encoder, cause I will receive error, but it's convenient to use proto-encoded connection to auto-unmarshall response from protobuf. Also I can't subscribe with empty interface{} with proto-encoded connection.

natsResp := new(f9_proto.CurrencyResponse)
Nats.ProtoConn().Request(currencyRatesTopic, nil, natsResp, timeout)


[Feature] Add spacing tokens and style-dictionary configs

Description of Change

Adds 12 new spacing tokens in packages/tokens/spacing/spacing.json from figma export
Add style-dictionary filters, formats, and configs for spacing

Filters spacing category
Creates TS declarations
Adds spacing to index.js export

Testing Packages

<EMAIL_ADDRESS><EMAIL_ADDRESS>
Screenshots/Video

Tested vadsSpaceLg token for 20 padding in Alert
iOS

Android

Web

Testing

[x] Tested on iOS
[x] Tested on Android
[x] Tested on Web

PR Checklist
Code reviewer validation:

General

[x] PR is linked to ticket(s)
[x] PR has changelog label applied if it's to be included in the changelog
[x] Acceptance criteria:

All satisfied or
Documented reason for not being performed or
Split to separate ticket and ticket is linked by relevant AC(s)

[x] Above PR sections adequately filled out
[x] If any breaking changes, in accordance with the pre-1.0.0 versioning guidelines: a CU ticket has been created for the VA Mobile App detailing necessary adjustments with the package version that will be published by this ticket

Code

[x] Tests are included if appropriate (or split to separate ticket)
[x] New functions have proper TSDoc annotations

Publish

If changes warrant a new version per the versioning guidelines and the PR is approved and ready to merge:

[ ] Merge main into branch
[ ] Merge branch to main
[ ] Verify that Check Component Integrations workflow ran successfully
[ ] Publish new version after merging

Added figma export for spacing tokens


Dragging Functionality Not working in Windows 10: Chrome

Facts about my Drag N Drop implementation:

I did this:

const touchDevice = ('ontouchstart' in document.documentElement)
let ConnectedRoot
if(touchDevice){
  ConnectedRoot = DragDropContext(TouchBackend)(Root)
}
else{
  ConnectedRoot = DragDropContext(HTML5Backend)(Root)
}
export default ConnectedRoot

This did work in allowing drag n drop to work on iPad, iPhone, MacBook Pro (Chrome, Safari, Firefox) on various versions.
Even on Windows 7 Chrome, Firefox, etc: Drag N'Drop worked... and windows 8 touchscreen--it worked in all browsers with fingers but not with mouse.

Problem is with a specific Windows 10 laptop (we'll call Win10) without Touchscreen in Chrome. Particular problem is with the initial Grab functionality where onDragStart never fires.

Win10's Firefox: DragN'Drop works fine with custom drag layer and canDrag etc.
Win 10 is not touchscreen--its a lenovo that looks like a thinkpad with a glossy screen.

After seeing this post: on super user: google chrome drag-drop
Assumed that may just be a chrome settings/flags issue.
However, this did not appear to be the case:

Win10 was able to use Drag N Drop on Chrome within Gmail--needed no flag changes etc.
Tried to follow instructions provided in above article => But...

did not seem to be the case that chrome was being run as an administrator because I tried to re-run using Window key+R and it worked)
Doesn't look like a flag issue because it worked in Gmail.

Instead of Drag N Drop it selects text... (only in Win10's chrome and in all other devices listed it just grabs something).

Any help or work around would be appreciated.

Does it work in Windows 10 Chrome if you force it to use HTML5Backend? This seems like it might be a problem with your feature sniffing.

Yes, unfortunately you were correct... Firefox was not picking up that Windows 10 considers itself to have 'ontouchstart' even when no touchscreen device is connected (ie. a windows touchscreen monitor) or if a laptop its built in touchscreen... it makes no distinction and thus my app would allow drag but only on a touch connected device. This is sad, but I'll figure out a way to make both work eventually.

How did you manage to solve this?

@zargold @Ronnyrr I'm seeing the same issue. Any insights on how to solve it?

After fighting with react-dnd on the Surface (and other all-in-one devices), I ended up writing a react drag and drop library specifically to handle the touch-and-also-mouse case. It's not as mature or as well-supported as react-dnd, but if touch-and-mouse support is a major blocker,  https://github.com/diiq/esdragon might help.


Title with number couldn't be parsed correctly

The.Legend.of.1900.1998.1080p.BluRay.H264.AAC-RARBG
2001.A.Space.Odyssey.1968.iNTERNAL.1080p.BluRay.x264-MANNEKEPiS

Another example 1983.S01E02.720p.WEBRip.X264-DEFLATE[eztv].mkv

I fix this in my fork of this project, together with other additions I had to make - I'd open a pull request here, but the original author has had no GitHub activity for years, and no recent pull requests have actually been merged.


Downloads stopped working?

Yes, suddenly the rate limit is over: https://api.soundcloud.com/tracks/256347798/stream?client_id=11a37feb6ccc034d5975f3f803928a32

I will try to fix it

Soundcloud provides 15k downloads in 24-hour window: https://developers.soundcloud.com/docs/api/rate-limits#play-requests, so I can't handle that and expand rate limits. The only thing I can do is to show the appropriate error message.

Ideal solution: register more apps and if rate limit is exceeded on one client_id then use another client_id.


Cannot login

Please ask the following questions, Thanks!

My system:

Arch Linux

My pidgin version is:

2.13.0-7

My pidgin-wechat version is:

0.1.1-1

standard output:

get: "https://login.web.wechat.com/jslogin?appid=wx782c26e4c19acffb&redirect_uri=https://web.wechat.com/cgi-bin/mmwebwx-bin/webwxnewloginpage&fun=new&lang=zh_CN"
thread '<unnamed>' panicked at 'called `Option::unwrap()` on a `None` value', src/libcore/option.rs:347:21
stack backtrace:
   0: <unknown>
   1: <unknown>
   2: <unknown>
   3: <unknown>
   4: std::panicking::rust_panic_with_hook
   5: <unknown>
   6: rust_begin_unwind
   7: core::panicking::panic_fmt
   8: core::panicking::panic
   9: <unknown>
  10: openssl::ssl::connector::SslConnectorBuilder::new
  11: native_tls::TlsConnector::builder
  12: hyper_native_tls::NativeTlsClient::new
  13: <unknown>
  14: std::sync::once::Once::call_inner
  15: <unknown>
  16: __rust_maybe_catch_panic
  17: <unknown>
  18: <unknown>
  19: <unknown>
  20: start_thread
  21: __clone

Installed directly from aur, and login window just does not appear.

I had the same problem.
Repeated login failure

我也遇到了同样的问题。


Update pagination

Code redesigned
Components changed from function component to class component
Updated pagination
Pagination done using MUI Outlined pagination

Great Work 👌


Generate Project Scrum/Kanban Board

https://github.com/users/jubaan/projects/1/views/1?visibleFields=["Title"%2C"Status"%2C"Milestone"%2C1488678%2C1488695%2C1488891%2C"Assignees"%2C"Labels"]

Project Scrum board:
https://github.com/users/jubaan/projects/1/views/1?visibleFields=["Title"%2C"Status"%2C"Milestone"%2C1488678%2C1488695%2C1488891%2C"Assignees"%2C"Labels"]


Could not build wheels for selective_scan, which is required to install pyproject.toml-based projects

Hello author, I've encountered a bit of trouble here. I've also downloaded the pyproject.toml library mentioned. Could the issue lie in my CUDA configuration? I'm using CUDA 11.7, cuDNN 8.5.0, and Torch 2.0.0.

Hello, before you execute main.py, you should first execute the command (cd kernels/selective_scan: Python setup. py install) to install selective_scan, which may solve your problem

Hello, before you execute main.py, you should first execute the command (cd kernels/selective_scan: Python setup. py install) to install selective_scan, which may solve your problem您好，在执行 main.py 之前，您应该先执行命令（cd kernels/selective_scan：Python setup. py安装）来安装selective_scan，这可能会解决您的问题

I encountered an error while executing {cd kernels/selective_scan && pip install .}, and I still couldn't resolve it. I wonder if anyone else has encountered the same problem as me.

Hello, before you execute main.py, you should first execute the command (cd kernels/selective_scan: Python setup. py install) to install selective_scan, which may solve your problem

I encountered an error while executing {cd kernels/selective_scan && pip install .}, and I still couldn't resolve it. I wonder if anyone else has encountered the same problem as me.

Hello, before you execute main.py, you should first execute the command (cd kernels/selective_scan: Python setup. py install) to install selective_scan, which may solve your problem

 I encountered an error while executing {cd kernels/selective_scan && pip install .}, and I still couldn't resolve it. I wonder if anyone else has encountered the same problem as me.

same here

 Hello author, I've encountered a bit of trouble here. I've also downloaded the pyproject.toml library mentioned. Could the issue lie in my CUDA configuration? I'm using CUDA 11.7, cuDNN 8.5.0, and Torch 2.0.0.

same

Have you ever checked the #95 ? Is that works for you?

It seems that you haven't installed g++?

Mar 16, 2024

Did you solve it? I had the same problem T^T SOS！！！

have you resovled this issue, i also faced this problem.

same here. Did anyone solved it?

Mar 16, 2024

Did you solve it? I had the same problem T^T SOS！！！

I solved the problem.It looks like just the problem of cuda version.I used the cuda11.6 and now I use cuda11.8.Cuda11.8 will be OK.

The same to me， I always failed to install it.

The same to me， I always failed to install it.

I fix it.You need a new environment, then do it again

The same to me， I always failed to install it.

I fix it.You need a new environment, then do it again

我也遇到这个问题了，请问可以详细说说吗，环境怎么设置的，

The same to me， I always failed to install it.

I fix it.You need a new environment, then do it again

我也遇到这个问题了，请问可以详细说说吗，环境怎么设置的，

和cuda版本有关，版本太低就会报类似的错，可以尝试升级cuda版本

我用的cuda版本已经是11.8的了 ，还是不行

The same to me， I always failed to install it.

I fix it.You need a new environment, then do it again

我也遇到这个问题了，请问可以详细说说吗，环境怎么设置的，

和cuda版本有关，版本太低就会报类似的错，可以尝试升级cuda版本

我用的cuda版本已经是11.8的了 ，还是不行

降低 一下cython版本试试，
1. pip install cython==0.29.36

2. 再执行cd kernels/selective_scan && pip install .

I tried it,but it did not work.

I also had this problem, and finally found out that the version of gcc was too low (4.x.x), and after upgrading the version (11.x.x) the installation was successful

Mar 16, 2024

Did you solve it? I had the same problem T^T SOS！！！

I solved the problem.It looks like just the problem of cuda version.I used the cuda11.6 and now I use cuda11.8.Cuda11.8 will be OK.


Create an AWS commons extension

Fixes #566

ok to test

updated

I think the right place for this kind of ancillary extension would be extensions/support/aws and the artifactId should match the existing conventions - something like camel-quarkus-support-aws

Is there any reason not to move the extesion to extensions/support/aws?

This was the first idea. It could be moved for sure.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/camel-quarkus-pr/496/

Btw I'll move the extension when I can.

ok to test

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/camel-quarkus-pr/498/Failed Tests: 1camel-quarkus-pr/org.apache.camel.quarkus:camel-quarkus-integration-test-tagsoup: 1org.apache.camel.quarkus.component.tagsoup.it.TagSoupIT.htmlParse

ok to test

Ok to test

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/camel-quarkus-pr/501/

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/camel-quarkus-pr/503/


The gateways is installed by Helm chart (https://istio.io/latest/docs/setup/additional-setup/gateway/)
The istiod has an option global.proxy.autoInject=disabled and istio-ingress namespace has a label istio-injection=enabled.
Pods with ingress gateways have correct image value.
I think this warning should be removed as far as is missleading and harmless.
Version
$  istioctl version
client version: 1.11.1
control plane version: 1.11.1
data plane version: 1.11.1 (18 proxies)
$  kubectl version --short
Client Version: v1.21.0
Server Version: v1.19.12-gke.2100

Additional Information
No response
Affected product area

[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Extensions and Telemetry
[ ] Security
[X] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
[ ] Upgrade
[ ] Multi Cluster
[ ] Virtual Machine
[ ] Control Plane Revisions

Is this the right place to submit this?

[X] This is not a security vulnerability
[X] This is not a question about how to use Istio

Running with the same configuration (1.11.1 deployed with Helm and global.proxy.autoInject=disabled doesn't give the IST0146 analyzer issue when running locally for me.
Can you show a dump of the mutating webhook active in your cluster, anything non-standard there?

More info:
$ kubectl get mutatingwebhookconfigurations/istio-sidecar-injector -o yaml|
apiVersion: admissionregistration.k8s.io/v1
kind: MutatingWebhookConfiguration
metadata:
  annotations:
    meta.helm.sh/release-name: istio-discovery
    meta.helm.sh/release-namespace: istio-system
  creationTimestamp: "2021-03-22T21:04:46Z"
  generation: 15
  labels:
    app: sidecar-injector
    app.kubernetes.io/managed-by: Helm
    install.operator.istio.io/owning-resource: unknown
    istio.io/rev: default
    operator.istio.io/component: Pilot
    release: istio-discovery
  name: istio-sidecar-injector
  resourceVersion: "370242012"
  selfLink: /apis/admissionregistration.k8s.io/v1/mutatingwebhookconfigurations/istio-sidecar-injector
  uid: 82bf8a77-6a38-438f-bed9-f18a02950d4a
webhooks:
- admissionReviewVersions:
  - v1beta1
  - v1
  clientConfig:
    caBundle: XXX
    service:
      name: istiod
      namespace: istio-system
      path: /inject
      port: 443
  failurePolicy: Fail
  matchPolicy: Equivalent
  name: rev.namespace.sidecar-injector.istio.io
  namespaceSelector:
    matchExpressions:
    - key: istio.io/rev
      operator: In
      values:
      - default
    - key: istio-injection
      operator: DoesNotExist
  objectSelector:
    matchExpressions:
    - key: sidecar.istio.io/inject
      operator: NotIn
      values:
      - "false"
  reinvocationPolicy: Never
  rules:
  - apiGroups:
    - ""
    apiVersions:
    - v1
    operations:
    - CREATE
    resources:
    - pods
    scope: '*'
  sideEffects: None
  timeoutSeconds: 10
- admissionReviewVersions:
  - v1beta1
  - v1
  clientConfig:
    caBundle: XXX
    service:
      name: istiod
      namespace: istio-system
      path: /inject
      port: 443
  failurePolicy: Fail
  matchPolicy: Equivalent
  name: rev.object.sidecar-injector.istio.io
  namespaceSelector:
    matchExpressions:
    - key: istio.io/rev
      operator: DoesNotExist
    - key: istio-injection
      operator: DoesNotExist
  objectSelector:
    matchExpressions:
    - key: sidecar.istio.io/inject
      operator: NotIn
      values:
      - "false"
    - key: istio.io/rev
      operator: In
      values:
      - default
  reinvocationPolicy: Never
  rules:
  - apiGroups:
    - ""
    apiVersions:
    - v1
    operations:
    - CREATE
    resources:
    - pods
    scope: '*'
  sideEffects: None
  timeoutSeconds: 10
- admissionReviewVersions:
  - v1beta1
  - v1
  clientConfig:
    caBundle: XXX
    service:
      name: istiod
      namespace: istio-system
      path: /inject
      port: 443
  failurePolicy: Fail
  matchPolicy: Equivalent
  name: namespace.sidecar-injector.istio.io
  namespaceSelector:
    matchExpressions:
    - key: istio-injection
      operator: In
      values:
      - enabled
  objectSelector:
    matchExpressions:
    - key: sidecar.istio.io/inject
      operator: NotIn
      values:
      - "false"
  reinvocationPolicy: Never
  rules:
  - apiGroups:
    - ""
    apiVersions:
    - v1
    operations:
    - CREATE
    resources:
    - pods
    scope: '*'
  sideEffects: None
  timeoutSeconds: 10
- admissionReviewVersions:
  - v1beta1
  - v1
  clientConfig:
    caBundle: XXX
    service:
      name: istiod
      namespace: istio-system
      path: /inject
      port: 443
  failurePolicy: Fail
  matchPolicy: Equivalent
  name: object.sidecar-injector.istio.io
  namespaceSelector:
    matchExpressions:
    - key: istio-injection
      operator: DoesNotExist
    - key: istio.io/rev
      operator: DoesNotExist
  objectSelector:
    matchExpressions:
    - key: sidecar.istio.io/inject
      operator: In
      values:
      - "true"
    - key: istio.io/rev
      operator: DoesNotExist
  reinvocationPolicy: Never
  rules:
  - apiGroups:
    - ""
    apiVersions:
    - v1
    operations:
    - CREATE
    resources:
    - pods
    scope: '*'
  sideEffects: None
  timeoutSeconds: 10

$ kubectl get deploy -n istio-ingress istio-ingressgateway-external -o yaml | kubectl neat
apiVersion: apps/v1
kind: Deployment
metadata:
  annotations:
    deployment.kubernetes.io/revision: "1"
    meta.helm.sh/release-name: istio-ingress
    meta.helm.sh/release-namespace: istio-ingress
  labels:
    app: istio-ingressgateway
    app.kubernetes.io/managed-by: Helm
    install.operator.istio.io/owning-resource: unknown
    istio: ingressgateway-external
    istio.io/rev: default
    operator.istio.io/component: IngressGateways
    release: istio-ingress-external
  name: istio-ingressgateway-external
  namespace: istio-ingress
spec:
  progressDeadlineSeconds: 600
  replicas: 1
  revisionHistoryLimit: 10
  selector:
    matchLabels:
      app: istio-ingressgateway
      istio: ingressgateway-external
  strategy:
    rollingUpdate:
      maxSurge: 100%
      maxUnavailable: 25%
    type: RollingUpdate
  template:
    metadata:
      annotations:
        inject.istio.io/templates: gateway
        prometheus.io/path: /stats/prometheus
        prometheus.io/port: "15020"
        prometheus.io/scrape: "true"
        sidecar.istio.io/inject: "true"
      creationTimestamp: null
      labels:
        app: istio-ingressgateway
        install.operator.istio.io/owning-resource: unknown
        istio: ingressgateway-external
        operator.istio.io/component: IngressGateways
        sidecar.istio.io/inject: "true"
    spec:
      affinity:
        nodeAffinity:
          preferredDuringSchedulingIgnoredDuringExecution:
          - preference:
              matchExpressions:
              - key: kubernetes.io/arch
                operator: In
                values:
                - amd64
            weight: 2
          - preference:
              matchExpressions:
              - key: kubernetes.io/arch
                operator: In
                values:
                - ppc64le
            weight: 2
          - preference:
              matchExpressions:
              - key: kubernetes.io/arch
                operator: In
                values:
                - s390x
            weight: 2
          requiredDuringSchedulingIgnoredDuringExecution:
            nodeSelectorTerms:
            - matchExpressions:
              - key: kubernetes.io/arch
                operator: In
                values:
                - amd64
                - ppc64le
                - s390x
      containers:
      - env:
        - name: ISTIO_META_UNPRIVILEGED_POD
          value: "true"
        - name: ISTIO_META_ROUTER_MODE
          value: standard
        image: auto
        imagePullPolicy: Always
        name: istio-proxy
        ports:
        - containerPort: 15021
          protocol: TCP
        - containerPort: 8080
          protocol: TCP
        - containerPort: 8443
          protocol: TCP
        - containerPort: 15090
          name: http-envoy-prom
          protocol: TCP
        resources:
          limits:
            cpu: "1"
            memory: 250Mi
          requests:
            cpu: "1"
            memory: 250Mi
        securityContext:
          allowPrivilegeEscalation: false
          capabilities:
            drop:
            - ALL
          privileged: false
          readOnlyRootFilesystem: true
        terminationMessagePath: /dev/termination-log
        terminationMessagePolicy: File
        volumeMounts:
        - mountPath: /etc/istio/ingressgateway-certs
          name: ingressgateway-certs
          readOnly: true
        - mountPath: /etc/istio/ingressgateway-ca-certs
          name: ingressgateway-ca-certs
          readOnly: true
      dnsPolicy: ClusterFirst
      restartPolicy: Always
      schedulerName: default-scheduler
      securityContext:
        fsGroup: 1337
        runAsGroup: 1337
        runAsNonRoot: true
        runAsUser: 1337
      serviceAccount: istio-ingressgateway-external-service-account
      serviceAccountName: istio-ingressgateway-external-service-account
      terminationGracePeriodSeconds: 30
      volumes:
      - name: ingressgateway-certs
        secret:
          defaultMode: 420
          optional: true
          secretName: istio-ingressgateway-certs
      - name: ingressgateway-ca-certs
        secret:
          defaultMode: 420
          optional: true
          secretName: istio-ingressgateway-ca-certs

$ kubectl get pod -n istio-ingress  istio-ingressgateway-external-59cb6c6985-2n5mn -o yaml | kubectl neat
apiVersion: v1
kind: Pod
metadata:
  annotations:
    inject.istio.io/templates: gateway
    prometheus.io/path: /stats/prometheus
    prometheus.io/port: "15020"
    prometheus.io/scrape: "true"
    proxy.istio.io/overrides: '{"containers":[{"name":"istio-proxy","ports":[{"containerPort":15021,"protocol":"TCP"},{"containerPort":8080,"protocol":"TCP"},{"containerPort":8443,"protocol":"TCP"},{"name":"http-envoy-prom","containerPort":15090,"protocol":"TCP"}],"env":[{"name":"ISTIO_META_UNPRIVILEGED_POD","value":"true"},{"name":"ISTIO_META_ROUTER_MODE","value":"standard"}],"resources":{"limits":{"cpu":"1","memory":"250Mi"},"requests":{"cpu":"1","memory":"250Mi"}},"volumeMounts":[{"name":"ingressgateway-certs","readOnly":true,"mountPath":"/etc/istio/ingressgateway-certs"},{"name":"ingressgateway-ca-certs","readOnly":true,"mountPath":"/etc/istio/ingressgateway-ca-certs"},{"name":"istio-ingressgateway-external-service-account-token-t9rsd","readOnly":true,"mountPath":"/var/run/secrets/kubernetes.io/serviceaccount"}],"terminationMessagePath":"/dev/termination-log","terminationMessagePolicy":"File","imagePullPolicy":"Always","securityContext":{"capabilities":{"drop":["ALL"]},"privileged":false,"readOnlyRootFilesystem":true,"allowPrivilegeEscalation":false}}]}'
    sidecar.istio.io/inject: "true"
    sidecar.istio.io/status: '{"initContainers":null,"containers":["istio-proxy"],"volumes":["istio-envoy","istio-data","istio-podinfo","istio-token","istiod-ca-cert"],"imagePullSecrets":null,"revision":"default"}'
  labels:
    app: istio-ingressgateway
    install.operator.istio.io/owning-resource: unknown
    istio: ingressgateway-external
    istio.io/rev: default
    operator.istio.io/component: IngressGateways
    pod-template-hash: 59cb6c6985
    service.istio.io/canonical-name: istio-ingressgateway
    service.istio.io/canonical-revision: latest
    sidecar.istio.io/inject: "true"
  name: istio-ingressgateway-external-59cb6c6985-2n5mn
  namespace: istio-ingress
spec:
  affinity:
    nodeAffinity:
      preferredDuringSchedulingIgnoredDuringExecution:
      - preference:
          matchExpressions:
          - key: kubernetes.io/arch
            operator: In
            values:
            - amd64
        weight: 2
      - preference:
          matchExpressions:
          - key: kubernetes.io/arch
            operator: In
            values:
            - ppc64le
        weight: 2
      - preference:
          matchExpressions:
          - key: kubernetes.io/arch
            operator: In
            values:
            - s390x
        weight: 2
      requiredDuringSchedulingIgnoredDuringExecution:
        nodeSelectorTerms:
        - matchExpressions:
          - key: kubernetes.io/arch
            operator: In
            values:
            - amd64
            - ppc64le
            - s390x
  containers:
  - args:
    - proxy
    - router
    - --domain
    - $(POD_NAMESPACE).svc.cluster.local
    - --proxyLogLevel=warning
    - --proxyComponentLogLevel=misc:error
    - --log_output_level=default:info
    - --log_as_json
    env:
    - name: JWT_POLICY
      value: third-party-jwt
    - name: PILOT_CERT_PROVIDER
      value: istiod
    - name: CA_ADDR
      value: istiod.istio-system.svc:15012
    - name: POD_NAME
      valueFrom:
        fieldRef:
          fieldPath: metadata.name
    - name: POD_NAMESPACE
      valueFrom:
        fieldRef:
          fieldPath: metadata.namespace
    - name: INSTANCE_IP
      valueFrom:
        fieldRef:
          fieldPath: status.podIP
    - name: SERVICE_ACCOUNT
      valueFrom:
        fieldRef:
          fieldPath: spec.serviceAccountName
    - name: HOST_IP
      valueFrom:
        fieldRef:
          fieldPath: status.hostIP
    - name: PROXY_CONFIG
      value: |
        {}
    - name: ISTIO_META_POD_PORTS
      value: |-
        [
            {"containerPort":15021,"protocol":"TCP"}
            ,{"containerPort":8080,"protocol":"TCP"}
            ,{"containerPort":8443,"protocol":"TCP"}
            ,{"name":"http-envoy-prom","containerPort":15090,"protocol":"TCP"}
        ]
    - name: ISTIO_META_APP_CONTAINERS
    - name: ISTIO_META_CLUSTER_ID
      value: Kubernetes
    - name: ISTIO_META_INTERCEPTION_MODE
      value: REDIRECT
    - name: ISTIO_META_WORKLOAD_NAME
      value: istio-ingressgateway-external
    - name: ISTIO_META_OWNER
      value: kubernetes://apis/apps/v1/namespaces/istio-ingress/deployments/istio-ingressgateway-external
    - name: ISTIO_META_MESH_ID
      value: cluster.local
    - name: TRUST_DOMAIN
      value: cluster.local
    - name: ISTIO_META_UNPRIVILEGED_POD
      value: "true"
    - name: ISTIO_META_ROUTER_MODE
      value: standard
    image: istio/proxyv2:1.11.1
    imagePullPolicy: Always
    lifecycle:
      preStop:
        exec:
          command:
          - /bin/sleep
          - 8m
    name: istio-proxy
    ports:
    - containerPort: 15021
    - containerPort: 8080
    - containerPort: 8443
    - containerPort: 15090
      name: http-envoy-prom
    readinessProbe:
      failureThreshold: 30
      httpGet:
        path: /healthz/ready
        port: 15021
      initialDelaySeconds: 1
      periodSeconds: 2
      timeoutSeconds: 3
    resources:
      limits:
        cpu: "1"
        memory: 250Mi
    securityContext:
      allowPrivilegeEscalation: false
      capabilities:
        drop:
        - ALL
      privileged: false
      readOnlyRootFilesystem: true
    volumeMounts:
    - mountPath: /var/run/secrets/istio
      name: istiod-ca-cert
    - mountPath: /var/lib/istio/data
      name: istio-data
    - mountPath: /etc/istio/proxy
      name: istio-envoy
    - mountPath: /var/run/secrets/tokens
      name: istio-token
    - mountPath: /etc/istio/pod
      name: istio-podinfo
    - mountPath: /etc/istio/ingressgateway-certs
      name: ingressgateway-certs
      readOnly: true
    - mountPath: /etc/istio/ingressgateway-ca-certs
      name: ingressgateway-ca-certs
      readOnly: true
    - mountPath: /var/run/secrets/kubernetes.io/serviceaccount
      name: istio-ingressgateway-external-service-account-token-t9rsd
      readOnly: true
  preemptionPolicy: PreemptLowerPriority
  priority: 0
  schedulerName: gke.io/optimize-utilization-scheduler
  securityContext:
    fsGroup: 1337
    runAsGroup: 1337
    runAsNonRoot: true
    runAsUser: 1337
  serviceAccountName: istio-ingressgateway-external-service-account
  tolerations:
  - effect: NoExecute
    key: node.kubernetes.io/not-ready
    operator: Exists
    tolerationSeconds: 300
  - effect: NoExecute
    key: node.kubernetes.io/unreachable
    operator: Exists
    tolerationSeconds: 300
  volumes:
  - emptyDir:
      medium: Memory
    name: istio-envoy
  - name: istio-data
  - downwardAPI:
      items:
      - fieldRef:
          fieldPath: metadata.labels
        path: labels
      - fieldRef:
          fieldPath: metadata.annotations
        path: annotations
    name: istio-podinfo
  - name: istio-token
    projected:
      sources:
      - serviceAccountToken:
          audience: istio-ca
          expirationSeconds: 43200
          path: istio-token
  - configMap:
      name: istio-ca-root-cert
    name: istiod-ca-cert
  - name: ingressgateway-certs
    secret:
      optional: true
      secretName: istio-ingressgateway-certs
  - name: ingressgateway-ca-certs
    secret:
      optional: true
      secretName: istio-ingressgateway-ca-certs
  - name: istio-ingressgateway-external-service-account-token-t9rsd
    secret:
      secretName: istio-ingressgateway-external-service-account-token-t9rsd

$  kubectl get namespace -L istio-injection
NAME              STATUS   AGE    ISTIO-INJECTION
default           Active   643d   disabled
istio-ingress     Active   177m   enabled
istio-system      Active   161d   disabled
kube-node-lease   Active   643d
kube-public       Active   643d
kube-system       Active   643d

$ kubectl -n istio-system get configmap istio-sidecar-injector -o jsonpath='{.data.config}' | grep policy:
policy: disabled

I think this webhook can't work for Deployments: it has resources: ["pods"] so verification of Deployments by istioctl analyze looks useless to me.

Right while the webhook will only modify pods, the analyzer is meant to check whether the pods created by the deployment will be injected. There was discussion about this potentially giving false positives in the original PR, though can remove the deployment part of the analyzer for now.

Just reproduced, the problem seems to be that the analyzer thinks the pod will be created in the default namespace rather than the istio-ingress, and since default NS is labeled istio-injection=disabled it thinks injection won't happen. Looking more into it.

Hello,
I am not sure if there is a regression here, but we have the same behaviour in istio 1.16.0
Warning [IST0146] (Deployment istio-gateways/istio-ingressgateway) Deployment istio-ingressgateway contains image: autobut does not match any Istio injection webhook selectors.

We do have the same behavior with istioctl 1.14.6 and Istio 1.13.7.

/reopen please, this also happens with 1.15.6

Still there in 1.17.0

and 1.17.2

This might be related to using revisions.
We do, and since we started using the revision flag for istioctl analyze, this message is gone.

Hi folks, I have the same issue for 1.17.5 and 1.18.1 versions of Istio.


Add interactive webviz + static png viz

this merge request adds a webserver that supports interactive visualizations. at the moment, it is somewhat bare, but it allows for query exploration. there is a README.md file in viz/ and the majority of the interfacing with existing histwords code is in viz/common.py.
the one main pip requirement to run this code is pylru, the rest of the requirements.txt file is from the existing requirements for histwords repo that we've run into.
some screenshots are here: http://imgur.com/a/XrhFj
i'm happy to get code review (but i know it takes time) and i'm more interested in getting feedback / ideas on how to expand on the usefulness of the program. i'm also not in any rush to get it merged, so don't worry about that.

Wow, this is fantastic!!! After I quick read through the code, I am very impressed, and I will try to do a longer code review on Monday (I have another deadline I am swamped with at the moment).
I actually really like the table view. It is simple, but quite nice.
In terms of expanding the usefulness, the most immediate thing that comes to my mind is easy support for loading/using different datasets. I could be wrong, but it seems like the current code can only load from the default location "embeddings/eng-all_sgns". This seems like the biggest way to make it more useful. There would need to be a consistent naming format etc for the embedding files, but I think researchers would love to be able to visualize changes in their datasets with this tool.
A much more minor point on the visualizations: For the cloud view, would it be possible to toggle on/off the drift for the background words? E.g., it might be useful to only show the background words for the most recent context, and show the target word shifting in that space, if that makes sense. I'll need to look at the code in some more detail to see if this is really reasonable though.
Thanks again! This is awesome.

will work on it more next week, also have some stuff this weekend.
re: embeddings: that is fine - the main problem is how much RAM they take up (4GB or so for one set), so it is hard to load multiple corpuses at once. a simple solution is that the webserver can start up and ask which embeddings to use on first load (and generate the candidate list by scanning the embeddings/ dir)
re: cloud view: that's possible. it would be easiest to accomplish by just turning all words off not from the most recent decade (but the invisible words would still have influenced the tSNE layout). to do so, we'll add some simple toggle controls to the frontend

Okay, so I have tinkered around more, and it is a substantial amount of code, but so far I haven't found anything problematic, and the interactive visualization is working great for me.
A couple minor things:

vis/web/config.py is blank/empty
running python scripts/closest_over_time_with_anns.py awful throws an error because the directory vis/web/output doesn't exist. This directory could be made if necessary using ioutils.make_dir command from the main branch. Also, README should also be updated to run the command as python scripts/closest_over_time_with_anns.py awful or the output path should be changed to scripts/output/... instead of viz/scripts/output.
on MacOS I need to "run python as a framework" by running pythonw instead of python. Maybe worth mentioning this in the README.

I looked at the get_time_sims code in some detail and it looks great!
After playing with it for some time, I am really starting to like the table view (especially compared to the cloud view). Not sure if you feel the same way, but it is a lot easier to work with, and I really like the automatic shading.
Overall, I am very impressed, and nothing has broken yet in my tinkering/playing around. I would be very happy to merge this into master sooner rather than later, but I'll defer to you because I know you have other things you want to potentially add before merging.
Oh, and in reply to you response to my comments:

re embeddings: The proposed solution of letting them choose the embeddings upon spinning up the server does make the most sense.
re the cloudview: this sort of toggle functionality would perfectly satisfy what I had in mind.

thanks for the patience - this next set of diffs addresses the feedback from earlier (blank config.py file, selectable embeddings, control for cloudview to toggle visibility of words,etc) and adds a new view: "timeline view" for browsing through the embeddings. from here, we are ready to merge (after cleaning up any last things you want us to take care of).
stepping back, i'd like to highlight what each view can tell us. below, i use 'query term' for the search word and 'neighbor word' for the nearest neighbors words that are returned by the API.
table view

see which neighbor word is most similar to query term in each decade
compare similarity of two neighbors to each other
see the similarity of a neighbor over time to the query term
locate common neighboring words between multiple query terms

cloud view

see neighboring word drift over time
see how the nearest neighbor words relate to each other
spatially see changes in meaning of the original query term (when the timeline significantly moves, we can guess that the query term changed in meaning)
locate common neighbors between query terms

timeline view

see when neighbor words enter and exit the meaning of the query term (i.e. what was first and last year that the neighbor word appeared)
find words that have stable meanings vs. unstable meanings (f.e. "sure" is stabler than "burglar")

No worries at all! This is really great work, and well worth waiting a few days for the new timeline view etc :)
I've played around with it some more, and it works amazing! And the new capabilities are fantastic. Again, I gave the code a skim, but I haven't ran into any issues or problems.
I would be very happy to merge this into the repo if you think that it's ready. Let me know.
I can also make you an official collaborator on the main repo. You put a lot of work into this visualization code, so I think it is fair and reasonable to make you an official collaborator. (You can also tinker with and maintain the code more easily then).
Does that all sound reasonable to you?

thanks! that sounds reasonable. there's actually two of us, @juniferd and myself, but i'll take contributor rights (and be responsible for on-going maintenance of the viz).
the code is ready to be merged, but there is still some stuff to be added (eventually) around controls for selecting which decades to search and how many nearest neighbors to show.

Awesome! The merge is done and you should have contributor rights. Thanks again @okayzed and @juniferd!


Install libmount-dev

Part of https://github.com/gtk-rs/examples/pull/229

CI almost passed (apveyour32 test fails again)

It doesn't change anything on appveyor so doesn't matter in here.


add support of getting resolved body in async client

At first I wasn't sure what this gave that the other body methods didn't, but then I saw that it specifically returns a Concat and then handles gzip.
I kind of think that gzip should be handled regardless of using this new method. There's work to try to do this in #161...

I'm going to close this, #161 will be merged soon.


LSTM train() callback/log is not working

I'm not exactly sure if I'm doing something wrong here, but at a glance it looks like my code is following the examples accurately. Here, I'm doing a simple LSTM train() but the logs/callbacks are not working.
Example 1 – Callback
const net = new Brain.recurrent.LSTM({
      hiddenLayers: [20, 20]
});
const trainRes = net.train(trainingData, {
    iterations: 1000,
    errorThresh: 0.05,
    callback: step => console.log(step)
});

Example 2 – Log = true
const net = new Brain.recurrent.LSTM({
      hiddenLayers: [20, 20]
});
const trainRes = net.train(trainingData, {
    iterations: 1000,
    errorThresh: 0.05,
    log: true // also fails with a function
});

Both examples fail to log. I also tried using both at the same time, which did not work either.
Funny thing however, is that after some (normal amounts of) time, the training finishes and everything works. It's just the logging that doesn't work.

I found out that if you give your neural network an impossible problem to solve, it will literally never log because it doesn't make a progress. That's what I get for being a noob.
Closing issue now.


OSDEV-914: Updating the approved claim auto-reply message

OSDEV-914: Updating the body of the approved claim email auto-reply messaging. Adding details to inform claimant that two fields cannot be edited. The "Facility name (English language)" & "Address" fields cannot be edited. Doing so will result in the claim being revoked.
OSDEV-913: Updating the body of the submitted claim email auto-reply messaging. Adding details to inform claimant of the expected processing time for the initial review & details of the required documentation for verification of a claim.

Hi @vrwOAR,
Could we close this PR in favor of the new one?


How to consider composing RootResolvers

This is a feature request/inquiry  -- Is there a way to compose the root-resolvers?

please give me some example what do you mean.

rootResolverOne :: GQLRootResolver AppObs () Query Mutation Undefined
rootResolverOne =
    GQLRootResolver
        { queryResolver =
              Query
                  { qa = resolverQa
                  , qb = resolverQb
                  }
        , mutationResolver = Mutation {ma = resolverMa}
        , subscriptionResolver = Undefined
        }

rootResolverTwo :: GQLRootResolver AppObs () Query Mutation Undefined
rootResolverTwo =
    GQLRootResolver
        { queryResolver =
              Query
                  { qc = resolverQc
                  , gd = resolverGd
                  }
        , mutationResolver = Mutation {mb = resolverMb}
        , subscriptionResolver = Undefined
        }

The goal would be to compose the two definitions.
The use case...
Each module would have my resolvers, types and root resolver for the module.  Each module would only export the rootResolver.
I would have a separate module "Root" that would compose all of my Roots.

oooh. you mean merge this root types. it's possible but not yet implemented.

Great!  Is there an outline of the syntax required? Perhaps I could move it along for you.  I ask for a started because I'm not yet up to speed on how to compose with type-level operations in the mix.

#425
no you can do it with:
api :: a -> m b
api = runApp (deriveApp rootResolverOne <> deriveApp rootResolverTwo)

@EdmundsEcho I think we can close it


sync loss keep getting bigger

Hello, I am using hq_wav2lip_train.py for training, and the expert loss has dropped to 0.2 before. At the beginning, the sync loss was always 0, and the percep loss was around 0.69. After training for a period of time, the sync loss began to gradually increase, and the percep loss also increased, but the fake and real loss continued to decrease. Now sync loss has been increased to 20, percep loss is 1.99 .I don't know what went wrong, what should the correct loss curve look like?

I'm having the same problem as you, have you solved it?

Hi, thanks for interesting. The most importance thing is dataset, do you check the dataset is preprocessed in the correct way?


max_workers

Is there a posibility to set the max_workers?
Best regards

i've found a solution
--close--

I think see #19 for reference

Exactky thank you.
Are any updates planned for the library?


Door State not shown in datapoints

Hello my lovely Developer of the Bambulab adapter,
i use hass io to get the state of the door of my x1c printer. Is it possible to get this state in iob as well? If yes i can delete hass.

If yes i can delete hass.

have fun with 0.3.4 and decommissioning :)

Kisses 💋💋

It doesn't work like that. HomeFlag is not always the same when the door is open or closed. HomeFlag always has a difference of 8388608 between open and closed. I have made a pull request with the necessary changes to make it work
https://github.com/DrozmotiX/ioBroker.bambulab/pull/132


KW Protocol

Hi.
Is it possible to integrate the KW protocol?

Eine mögliche Anlage zum Test steht in 94099 😉

Hi @Wurzelfuchs,
the open-source idea works, someone else extended my code with KW protocol. I fetched those code snippets, but I am not able to test it. Please report back if it is not working.


git.stage command bug

Does this issue occur when all extensions are disabled?: No (although probably need built in git extension)

Version: 1.74.3 (user setup)
Commit: 97dec172d3256f8ca4bfb2143f3f76b503ca0534
Date: 2023-01-09T16:59:02.252Z
Electron: 19.1.8
Chromium: 102.0.5005.167
Node.js: 16.14.2
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.22621
Sandboxed: No
Steps to Reproduce:

Create folder C:\repo, open it in vscode, run git init
Create a file test.txt, write some text, save file, close file
Ctrl+P - Preferences: Open Keyboard Shortcuts (JSON)
Add this item to json and save file:

	{
		"key": "ctrl+k ctrl+z",
		"command": "git.stage",
		"args": [
			"C:\\repo\\test.txt"
		]
	}

Press ctrl+k ctrl+z, notice that test.txt is not staged
Open test.txt
Press ctrl+k ctrl+z, notice that test.txt is staged

The bug: the file doesn't need to be open to become staged.

Never mind, the issue is wrong, but I still think there's some issue, I'll open another one after some testing...


auth: simplify merging range perm

No need of separate function to filter duplicates.
Just merge ranges in-place
go test -v -run=xxx -bench=BenchmarkMergeOld -benchmem
BenchmarkMergeOld-8   	  100000	     13524 ns/op	    1104 B/op	       8 allocs/op

go test -v -run=xxx -bench=BenchmarkMergeNew -benchmem
BenchmarkMergeNew-8   	  100000	     13432 ns/op	     936 B/op	       3 allocs/op

Not much performance boost, but less memory allocation
and simpler

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@9f8e82e). Click here to learn what that means.
The diff coverage is 100%.

@@            Coverage Diff            @@
##             master    #7313   +/-   ##
=========================================
  Coverage          ?   64.77%
=========================================
  Files             ?      230
  Lines             ?    20716
  Branches          ?        0
=========================================
  Hits              ?    13418
  Misses            ?     6306
  Partials          ?      992

Impacted Files
Coverage Δ

auth/range_perm_cache.go
42.26% <100%> (ø)

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 9f8e82e...ee8edbb. Read the comment docs.

lgtm defer to @mitake


Red OmniSharp flame icon in status bar with "OmniSharp process errored:" tooltip (1.16.1)

Environment data
dotnet --info output:
.NET Core SDK (reflecting any global.json):
 Version:   2.1.402
 Commit:    3599f217f4

Runtime Environment:
 OS Name:     Mac OS X
 OS Version:  10.13
 OS Platform: Darwin
 RID:         osx.10.13-x64
 Base Path:   /usr/local/share/dotnet/sdk/2.1.402/

Host (useful for support):
  Version: 2.1.4
  Commit:  85255dde3e

.NET Core SDKs installed:
  2.1.402 [/usr/local/share/dotnet/sdk]

.NET Core runtimes installed:
  Microsoft.AspNetCore.All 2.1.4 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.App 2.1.4 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 2.1.4 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]

To install additional .NET Core runtimes or SDKs:
  https://aka.ms/dotnet-download

VS Code version: 1.27.1
C# Extension version: 1.16.1
Steps to reproduce

Create a new project: dotnet new console
Open containing folder with Visual Studio Code
Observe that the OmniSharp Log appears in the OUTPUT pane and focuses itself automatically (happens every time I open a C# project since 1.16.0)
Observe that the OmniSharp flame icon in the taskbar is red instead of green
Mouse over the icon and observe "OmniSharp process errored:" tooltip
Observe that there are no errors in the output from step 3

Expected  behavior
The extension should load normally without opening the OUTPUT pane in VS Code. The OmniSharp flame icon should be green as it was prior to version 1.16.0.
Actual behavior

Upon loading a C# project, the OUTPUT pane opens up with the message (this is with log level set to "debug"; usually I have it set to "critical" and it still focuses itself upon opening a project):
Starting OmniSharp server at 9/12/2018, 9:19:49 PM
    Target: /Users/zach/Desktop/OmniTest

OmniSharp server started with Mono 5.14.0.
    Path: /Users/zach/.vscode/extensions/ms-vscode.csharp-1.16.1/.omnisharp/1.32.5/omnisharp/OmniSharp.exe
    PID: 62698

[info]: OmniSharp.Stdio.Host
        Starting OmniSharp on MacOS 10.13.6 (x64)
[info]: OmniSharp.Services.DotNetCliService
        DotNetPath set to dotnet
[info]: OmniSharp.MSBuild.Discovery.MSBuildLocator
        Located 2 MSBuild instance(s)
            1: Mono 15.0 - "/usr/local/Cellar/mono/<IP_ADDRESS>/lib/mono/msbuild/15.0/bin"
            2: StandAlone 15.0 - "/Users/zach/.vscode/extensions/ms-vscode.csharp-1.16.1/.omnisharp/1.32.5/omnisharp/msbuild/15.0/Bin"
[info]: OmniSharp.MSBuild.Discovery.MSBuildLocator
        Registered MSBuild instance: Mono 15.0 - "/usr/local/Cellar/mono/<IP_ADDRESS>/lib/mono/msbuild/15.0/bin"
            CscToolPath = /Users/zach/.vscode/extensions/ms-vscode.csharp-1.16.1/.omnisharp/1.32.5/omnisharp/msbuild/15.0/Bin/Roslyn
            CscToolExe = csc.exe
[info]: OmniSharp.Cake.CakeProjectSystem
        Detecting Cake files in '/Users/zach/Desktop/OmniTest'.
[info]: OmniSharp.Cake.CakeProjectSystem
        Could not find any Cake files
[info]: OmniSharp.WorkspaceInitializer
        Project system 'OmniSharp.DotNet.DotNetProjectSystem' is disabled in the configuration.
[info]: OmniSharp.MSBuild.ProjectSystem
        No solution files found in '/Users/zach/Desktop/OmniTest'
[info]: OmniSharp.MSBuild.ProjectManager
        Queue project update for '/Users/zach/Desktop/OmniTest/OmniTest.csproj'
[info]: OmniSharp.Script.ScriptProjectSystem
        Detecting CSX files in '/Users/zach/Desktop/OmniTest'.
[info]: OmniSharp.Script.ScriptProjectSystem
        Could not find any CSX files
[info]: OmniSharp.WorkspaceInitializer
        Invoking Workspace Options Provider: OmniSharp.Roslyn.CSharp.Services.CSharpWorkspaceOptionsProvider
[info]: OmniSharp.WorkspaceInitializer
        Configuration finished.
[info]: OmniSharp.Stdio.Host
        Omnisharp server running using Stdio at location '/Users/zach/Desktop/OmniTest' on host 62678.
[info]: OmniSharp.MSBuild.ProjectManager
        Loading project: /Users/zach/Desktop/OmniTest/OmniTest.csproj
[info]: OmniSharp.MSBuild.ProjectManager
        Successfully loaded project file '/Users/zach/Desktop/OmniTest/OmniTest.csproj'.
[info]: OmniSharp.MSBuild.ProjectManager
        Adding project '/Users/zach/Desktop/OmniTest/OmniTest.csproj'
[info]: OmniSharp.MSBuild.ProjectManager
        Update project: OmniTest

and the OmniSharp flame icon in the status bar is red. The plugin features generally seem to work fine, though.

@zvinless @ru-ace Thanks for filing this--we believe this is caused by our omnisharp error detector spuriously detecting an error. I suspect omnisharp features are still working for you despite the red flame?
cc @akshita31

@rchande, yeah, the plugin features are all good!

@zvinless, yes - plugin works fine.

Yep same to me. I see it under Unity project.

Yep same for me.  The plugin still works as expected though.

I have this same issue however, in my case it seems to break omnisharp, it doesn't want to build my project anymore, this is my log:
Starting OmniSharp server at 9/18/2018, 1:35:29 AM
    Target: /home/monyarm/Documents/Amicitia/Source/Amicitia.sln

OmniSharp server started with Mono 5.14.0.
    Path: /home/monyarm/.vscode/extensions/ms-vscode.csharp-1.16.1/.omnisharp/1.32.5/omnisharp/OmniSharp.exe
    PID: 32579

[info]: OmniSharp.Stdio.Host
        Starting OmniSharp on ubuntu 17.10 (x64)
[info]: OmniSharp.Services.DotNetCliService
        DotNetPath set to dotnet
[info]: OmniSharp.MSBuild.Discovery.MSBuildLocator
        Located 2 MSBuild instance(s)
            1: Mono 15.0 - "/usr/lib/mono/msbuild/15.0/bin"
            2: StandAlone 15.0 - "/home/monyarm/.vscode/extensions/ms-vscode.csharp-1.16.1/.omnisharp/1.32.5/omnisharp/msbuild/15.0/Bin"
[info]: OmniSharp.MSBuild.Discovery.MSBuildLocator
        Registered MSBuild instance: Mono 15.0 - "/usr/lib/mono/msbuild/15.0/bin"
            CscToolPath = /home/monyarm/.vscode/extensions/ms-vscode.csharp-1.16.1/.omnisharp/1.32.5/omnisharp/msbuild/15.0/Bin/Roslyn
            CscToolExe = csc.exe
[info]: OmniSharp.Cake.CakeProjectSystem
        Detecting Cake files in '/home/monyarm/Documents/Amicitia/Source'.
[info]: OmniSharp.Cake.CakeProjectSystem
        Could not find any Cake files
[info]: OmniSharp.WorkspaceInitializer
        Project system 'OmniSharp.DotNet.DotNetProjectSystem' is disabled in the configuration.
[info]: OmniSharp.MSBuild.ProjectSystem
        Detecting projects in '/home/monyarm/Documents/Amicitia/Source/Amicitia.sln'.
[info]: OmniSharp.MSBuild.ProjectManager
        Queue project update for '/home/monyarm/Documents/Amicitia/Source/AmicitiaLibrary/AmicitiaLibrary.csproj'
[info]: OmniSharp.MSBuild.ProjectManager
        Queue project update for '/home/monyarm/Documents/Amicitia/Source/Amicitia/Amicitia.csproj'
[info]: OmniSharp.MSBuild.ProjectManager
        Queue project update for '/home/monyarm/Documents/Amicitia/Source/Commandline tools/bvptool/bvptool.csproj'
[info]: OmniSharp.MSBuild.ProjectManager
        Queue project update for '/home/monyarm/Documents/Amicitia/Dependencies/AtlusFileSystemLibrary/Source/AtlusFileSystemLibrary/AtlusFileSystemLibrary.csproj'
[info]: OmniSharp.Script.ScriptProjectSystem
        Detecting CSX files in '/home/monyarm/Documents/Amicitia/Source'.
[info]: OmniSharp.Script.ScriptProjectSystem
        Could not find any CSX files
[info]: OmniSharp.WorkspaceInitializer
        Invoking Workspace Options Provider: OmniSharp.Roslyn.CSharp.Services.CSharpWorkspaceOptionsProvider
[info]: OmniSharp.WorkspaceInitializer
        Configuration finished.
[info]: OmniSharp.Stdio.Host
        Omnisharp server running using Stdio at location '/home/monyarm/Documents/Amicitia/Source' on host 29054.
[info]: OmniSharp.MSBuild.ProjectManager
        Loading project: /home/monyarm/Documents/Amicitia/Source/AmicitiaLibrary/AmicitiaLibrary.csproj
[info]: OmniSharp.MSBuild.ProjectManager
        Successfully loaded project file '/home/monyarm/Documents/Amicitia/Source/AmicitiaLibrary/AmicitiaLibrary.csproj'.
[info]: OmniSharp.MSBuild.ProjectManager
        Adding project '/home/monyarm/Documents/Amicitia/Source/AmicitiaLibrary/AmicitiaLibrary.csproj'
[info]: OmniSharp.MSBuild.ProjectManager
        Loading project: /home/monyarm/Documents/Amicitia/Source/Amicitia/Amicitia.csproj
[info]: OmniSharp.MSBuild.ProjectManager
        Successfully loaded project file '/home/monyarm/Documents/Amicitia/Source/Amicitia/Amicitia.csproj'.
[info]: OmniSharp.MSBuild.ProjectManager
        Adding project '/home/monyarm/Documents/Amicitia/Source/Amicitia/Amicitia.csproj'
[info]: OmniSharp.MSBuild.ProjectManager
        Loading project: /home/monyarm/Documents/Amicitia/Source/Commandline tools/bvptool/bvptool.csproj
[info]: OmniSharp.MSBuild.ProjectManager
        Successfully loaded project file '/home/monyarm/Documents/Amicitia/Source/Commandline tools/bvptool/bvptool.csproj'.
[info]: OmniSharp.MSBuild.ProjectManager
        Adding project '/home/monyarm/Documents/Amicitia/Source/Commandline tools/bvptool/bvptool.csproj'
[info]: OmniSharp.MSBuild.ProjectManager
        Loading project: /home/monyarm/Documents/Amicitia/Dependencies/AtlusFileSystemLibrary/Source/AtlusFileSystemLibrary/AtlusFileSystemLibrary.csproj
[info]: OmniSharp.MSBuild.ProjectManager
        Successfully loaded project file '/home/monyarm/Documents/Amicitia/Dependencies/AtlusFileSystemLibrary/Source/AtlusFileSystemLibrary/AtlusFileSystemLibrary.csproj'.
[info]: OmniSharp.MSBuild.ProjectManager
        Adding project '/home/monyarm/Documents/Amicitia/Dependencies/AtlusFileSystemLibrary/Source/AtlusFileSystemLibrary/AtlusFileSystemLibrary.csproj'
[info]: OmniSharp.MSBuild.ProjectManager
        Update project: AmicitiaLibrary
[info]: OmniSharp.MSBuild.ProjectManager
        Update project: Amicitia
[info]: OmniSharp.MSBuild.ProjectManager
        Update project: bvptool
[info]: OmniSharp.MSBuild.ProjectManager
        Update project: AtlusFileSystemLibrary

While if i delete my build folder and try again, then i get it:
Starting OmniSharp server at 9/18/2018, 1:38:53 AM
    Target: /home/monyarm/Documents/Amicitia/Source/Amicitia.sln

OmniSharp server started with Mono 5.14.0.
    Path: /home/monyarm/.vscode/extensions/ms-vscode.csharp-1.16.1/.omnisharp/1.32.5/omnisharp/OmniSharp.exe
    PID: 1095

[info]: OmniSharp.Stdio.Host
        Starting OmniSharp on ubuntu 17.10 (x64)
[info]: OmniSharp.Services.DotNetCliService
        DotNetPath set to dotnet
[info]: OmniSharp.MSBuild.Discovery.MSBuildLocator
        Located 2 MSBuild instance(s)
            1: Mono 15.0 - "/usr/lib/mono/msbuild/15.0/bin"
            2: StandAlone 15.0 - "/home/monyarm/.vscode/extensions/ms-vscode.csharp-1.16.1/.omnisharp/1.32.5/omnisharp/msbuild/15.0/Bin"
[info]: OmniSharp.MSBuild.Discovery.MSBuildLocator
        Registered MSBuild instance: Mono 15.0 - "/usr/lib/mono/msbuild/15.0/bin"
            CscToolPath = /home/monyarm/.vscode/extensions/ms-vscode.csharp-1.16.1/.omnisharp/1.32.5/omnisharp/msbuild/15.0/Bin/Roslyn
            CscToolExe = csc.exe
[info]: OmniSharp.Cake.CakeProjectSystem
        Detecting Cake files in '/home/monyarm/Documents/Amicitia/Source'.
[info]: OmniSharp.Cake.CakeProjectSystem
        Could not find any Cake files
[info]: OmniSharp.WorkspaceInitializer
        Project system 'OmniSharp.DotNet.DotNetProjectSystem' is disabled in the configuration.
[info]: OmniSharp.MSBuild.ProjectSystem
        Detecting projects in '/home/monyarm/Documents/Amicitia/Source/Amicitia.sln'.
[info]: OmniSharp.MSBuild.ProjectManager
        Queue project update for '/home/monyarm/Documents/Amicitia/Source/AmicitiaLibrary/AmicitiaLibrary.csproj'
[info]: OmniSharp.MSBuild.ProjectManager
        Queue project update for '/home/monyarm/Documents/Amicitia/Source/Amicitia/Amicitia.csproj'
[info]: OmniSharp.MSBuild.ProjectManager
        Queue project update for '/home/monyarm/Documents/Amicitia/Source/Commandline tools/bvptool/bvptool.csproj'
[info]: OmniSharp.MSBuild.ProjectManager
        Queue project update for '/home/monyarm/Documents/Amicitia/Dependencies/AtlusFileSystemLibrary/Source/AtlusFileSystemLibrary/AtlusFileSystemLibrary.csproj'
[info]: OmniSharp.Script.ScriptProjectSystem
        Detecting CSX files in '/home/monyarm/Documents/Amicitia/Source'.
[info]: OmniSharp.Script.ScriptProjectSystem
        Could not find any CSX files
[info]: OmniSharp.WorkspaceInitializer
        Invoking Workspace Options Provider: OmniSharp.Roslyn.CSharp.Services.CSharpWorkspaceOptionsProvider
[info]: OmniSharp.WorkspaceInitializer
        Configuration finished.
[info]: OmniSharp.Stdio.Host
        Omnisharp server running using Stdio at location '/home/monyarm/Documents/Amicitia/Source' on host 29054.
[info]: OmniSharp.MSBuild.ProjectManager
        Loading project: /home/monyarm/Documents/Amicitia/Source/AmicitiaLibrary/AmicitiaLibrary.csproj
[info]: OmniSharp.MSBuild.ProjectManager
        Successfully loaded project file '/home/monyarm/Documents/Amicitia/Source/AmicitiaLibrary/AmicitiaLibrary.csproj'.
[info]: OmniSharp.MSBuild.ProjectManager
        Adding project '/home/monyarm/Documents/Amicitia/Source/AmicitiaLibrary/AmicitiaLibrary.csproj'
[info]: OmniSharp.MSBuild.ProjectManager
        Loading project: /home/monyarm/Documents/Amicitia/Source/Amicitia/Amicitia.csproj
[info]: OmniSharp.MSBuild.ProjectManager
        Successfully loaded project file '/home/monyarm/Documents/Amicitia/Source/Amicitia/Amicitia.csproj'.
[info]: OmniSharp.MSBuild.ProjectManager
        Adding project '/home/monyarm/Documents/Amicitia/Source/Amicitia/Amicitia.csproj'
[info]: OmniSharp.MSBuild.ProjectManager
        Loading project: /home/monyarm/Documents/Amicitia/Source/Commandline tools/bvptool/bvptool.csproj
[info]: OmniSharp.MSBuild.ProjectManager
        Successfully loaded project file '/home/monyarm/Documents/Amicitia/Source/Commandline tools/bvptool/bvptool.csproj'.
[info]: OmniSharp.MSBuild.ProjectManager
        Adding project '/home/monyarm/Documents/Amicitia/Source/Commandline tools/bvptool/bvptool.csproj'
[info]: OmniSharp.MSBuild.ProjectManager
        Loading project: /home/monyarm/Documents/Amicitia/Dependencies/AtlusFileSystemLibrary/Source/AtlusFileSystemLibrary/AtlusFileSystemLibrary.csproj
[info]: OmniSharp.MSBuild.ProjectManager
        Successfully loaded project file '/home/monyarm/Documents/Amicitia/Dependencies/AtlusFileSystemLibrary/Source/AtlusFileSystemLibrary/AtlusFileSystemLibrary.csproj'.
[info]: OmniSharp.MSBuild.ProjectManager
        Adding project '/home/monyarm/Documents/Amicitia/Dependencies/AtlusFileSystemLibrary/Source/AtlusFileSystemLibrary/AtlusFileSystemLibrary.csproj'
[info]: OmniSharp.MSBuild.ProjectManager
        Update project: AmicitiaLibrary
[info]: OmniSharp.MSBuild.ProjectManager
        Update project: Amicitia
[warn]: OmniSharp.MSBuild.ProjectManager
        Unable to resolve assembly '/home/monyarm/Documents/Amicitia/Build/Debug/AmicitiaLibrary.dll'
[info]: OmniSharp.MSBuild.ProjectManager
        Update project: bvptool
[warn]: OmniSharp.MSBuild.ProjectManager
        Unable to resolve assembly '/home/monyarm/Documents/Amicitia/Build/Debug/AmicitiaLibrary.dll'
[info]: OmniSharp.MSBuild.ProjectManager
        Update project: AtlusFileSystemLibrary

Right now i'm forced to delete my build folder, then run monodevelop, and have it build my project

I'm seeing the red flame also, but I Cannot launch apps with the VS Code debugger: https://github.com/Microsoft/vscode/issues/58847
Not sure if it's related.

Same problem
.NET Core SDK (reflecting any global.json):
 Version:   2.1.402
 Commit:    3599f217f4

Runtime Environment:
 OS Name:     linuxmint
 OS Version:  19
 OS Platform: Linux
 RID:         linuxmint.19-x64
 Base Path:   /usr/share/dotnet/sdk/2.1.402/

Host (useful for support):
  Version: 2.1.4
  Commit:  85255dde3e

.NET Core SDKs installed:
  2.1.402 [/usr/share/dotnet/sdk]

.NET Core runtimes installed:
  Microsoft.AspNetCore.All 2.1.4 [/usr/share/dotnet/shared/Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.App 2.1.4 [/usr/share/dotnet/shared/Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 2.1.4 [/usr/share/dotnet/shared/Microsoft.NETCore.App]

@monyarm  The issue here is just that the OmniSharp flame is red despite of the fact that all IDE features work. Can you file a new issue with specific repro steps ?

@zvinless @ru-ace Thanks for filing this--we believe this is caused by our omnisharp error detector spuriously detecting an error. I suspect omnisharp features are still working for you despite the red flame?
cc @akshita31

Not for me. On macOS Mojave I get the red flame as well but my Console app project won't debug any more. It starts to run the app and locks up, truncating the console output. I can't pause it but I can stop it. When I run the project on Visual Studio Code for Windows (same version) I get the green flame icon and a functional debugging session. So I think this is more than simply an erroneous alert.

The beta with the fix for the red OmniSharp flame is out: https://github.com/OmniSharp/omnisharp-vscode/releases/tag/v1.17.0-beta1. Please give it a try.

Yeah, that made things worse. The C# extension isn't loading at all now:
/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:281 [Extension Host] Activating extension 'ms-vscode.csharp' failed: Cannot find module 'strip-bom'. (at Object.showMessage (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:614:509))
t.log @ /Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:281
/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:281 [Extension Host] Activating extension `ms-vscode.csharp` failed:  Cannot find module 'strip-bom' (at /Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:291:583)
t.log @ /Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:281
/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:281 [Extension Host] Here is the error stack:  Error: Cannot find module 'strip-bom'
	at Function.Module._resolveFilename (module.js:543:15)
	at Function.Module._load (module.js:473:25)
	at Function.t._load (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:648:268)
	at Function.o._load (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:592:300)
	at Module.require (module.js:586:17)
	at Module.require (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/extensions/git/dist/main.js:1:113692)
	at require (internal/module.js:11:18)
	at Object.<anonymous> (/Users/johntsombakos/.vscode-insiders/extensions/ms-vscode.csharp-1.16.1/out/src/utils/removeBOM.js:8:25)
	at Object.<anonymous> (/Users/johntsombakos/.vscode-insiders/extensions/ms-vscode.csharp-1.16.1/out/src/utils/removeBOM.js:18:3)
	at Module._compile (module.js:642:30)
	at Object.Module._extensions..js (module.js:653:10)
	at Module.load (module.js:561:32)
	at tryModuleLoad (module.js:504:12)
	at Function.Module._load (module.js:496:3)
	at Function.t._load (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:648:268)
	at Function.o._load (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:592:300)
	at Module.require (module.js:586:17)
	at Module.require (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/extensions/git/dist/main.js:1:113692)
	at require (internal/module.js:11:18)
	at Object.<anonymous> (/Users/johntsombakos/.vscode-insiders/extensions/ms-vscode.csharp-1.16.1/out/src/omnisharp/server.js:33:21)
	at Object.<anonymous> (/Users/johntsombakos/.vscode-insiders/extensions/ms-vscode.csharp-1.16.1/out/src/omnisharp/server.js:519:3)
	at Module._compile (module.js:642:30)
	at Object.Module._extensions..js (module.js:653:10)
	at Module.load (module.js:561:32)
	at tryModuleLoad (module.js:504:12)
	at Function.Module._load (module.js:496:3)
	at Function.t._load (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:648:268)
	at Function.o._load (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:592:300)
	at Module.require (module.js:586:17)
	at Module.require (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/extensions/git/dist/main.js:1:113692)
	at require (internal/module.js:11:18)
	at Object.<anonymous> (/Users/johntsombakos/.vscode-insiders/extensions/ms-vscode.csharp-1.16.1/out/src/omnisharp/extension.js:31:18)
	at Object.<anonymous> (/Users/johntsombakos/.vscode-insiders/extensions/ms-vscode.csharp-1.16.1/out/src/omnisharp/extension.js:164:3)
	at Module._compile (module.js:642:30)
	at Object.Module._extensions..js (module.js:653:10)
	at Module.load (module.js:561:32)
	at tryModuleLoad (module.js:504:12)
	at Function.Module._load (module.js:496:3)
	at Function.t._load (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:648:268)
	at Function.o._load (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:592:300)
	at Module.require (module.js:586:17)
	at Module.require (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/extensions/git/dist/main.js:1:113692)
	at require (internal/module.js:11:18)
	at Object.<anonymous> (/Users/johntsombakos/.vscode-insiders/extensions/ms-vscode.csharp-1.16.1/out/src/main.js:15:19)
	at Object.<anonymous> (/Users/johntsombakos/.vscode-insiders/extensions/ms-vscode.csharp-1.16.1/out/src/main.js:147:3)
	at Module._compile (module.js:642:30)
	at Object.Module._extensions..js (module.js:653:10)
	at Module.load (module.js:561:32)
	at tryModuleLoad (module.js:504:12)
	at Function.Module._load (module.js:496:3)
	at Function.t._load (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:648:268)
	at Function.o._load (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:592:300)
	at Module.require (module.js:586:17)
	at Module.require (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/extensions/git/dist/main.js:1:113692)
	at require (internal/module.js:11:18)
	at Function.i [as __$__nodeRequire] (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/loader.js:31:146)
	at /Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:617:969
	at t._doActivateExtension (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:618:84)
	at t._activateExtension (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:616:854)
	at Object.actualActivateExtension (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:614:641)
	at e._activateExtension (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:291:446)
	at /Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:291:65
	at Array.map (<anonymous>)
	at e._activateExtensions (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:291:40)
	at e.activateByEvent (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:289:321)
	at /Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:615:126
	at Object.g [as _notify] (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:78:971)
	at Object.enter (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:82:277)
	at n.Class.derive._oncancel._run (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:84:100)
	at n.Class.derive._oncancel._completed (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:83:559)
	at e.open (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:110:637)
	at /Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:614:679
	at Object.g [as _notify] (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:78:971)
	at Object.enter (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:82:277)
	at n.Class.derive._oncancel._run (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:84:100)
	at n.Class.derive._oncancel._completed (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:83:559)
	at c (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:86:1011)
	at K.then.o.(anonymous function) (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:87:205)
	at Object.g [as _notify] (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:78:971)
	at Object.enter (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:82:277)
	at n.Class.derive._oncancel._run (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:84:100)
	at n.Class.derive._oncancel._completed (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:83:559)
	at /Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:114:1006
	at /Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:141:73
	at LOOP (original-fs.js:1757:14)
	at _combinedTickCallback (internal/process/next_tick.js:131:7)
	at process._tickCallback (internal/process/next_tick.js:180:9) (at /Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:291:651)
/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:3322 Activating extension 'ms-vscode.csharp' failed: Cannot find module 'strip-bom'.

@akshita31, the asset on the 1.17.0-beta1 release is https://github.com/OmniSharp/omnisharp-vscode/releases/download/v1.17.0-beta1/csharp-1.16.1.vsix - that doesn't seem right?

@jtsom @bjornharrtell Apologies that didn't work. Seems there is an issue wth missing dependency. I am investigating further.

<3

The flame is indeed green, but I still can't debug my console app any more. It runs and freezes. Cannot pause debugger. When I stop it I can't debug again because the pdb files are in-use and can't be overwritten during the build. This happens in macOS High Sierra and Mojave.

@argentini Can you file a new issue with the relevant information about your system and the project you are working with ?


[dashboard v2] add tests

This PR adds a ton of tests for the new dashboard app. I have a few more todo (enumerated below) and will rebase it once #4962 is merged (this has commits from that branch on it), but wanted to make a PR to start getting an idea of coverage.
@graceguo-supercat
TODO

[ ] fix old Dashboard tests
[ ] add reducer tests
[ ] add action tests

actually, going to abandon this and create a new one once #4962 has merged.


Host api at api subdomain api.medperf.org

We are finishing the website, which going to be hosted on the main domain webperf.org
and so need to move api for CLI to the api subdomain -> api.medperf.org

@hasan7n  as discussed let's make changes on code to reflect the domain changes


Simple Logic plugin

One really good thing about Kong is the plugin architecture it has and I think it would be nice able to add simple logic plugin to check the user/consumer status without delegating this task to upstream services.
For example, Account Confirmation plugin will check every request that the user / consumer status is verified

Can you provide a more detailed description of your use case?

Sure, I'm building a new system where I have to ensure every users/consumers of my microservices has verified his account during registration.
Am thinking if there is a simple plugin for this, I don't have to do an extra check in all my services.

Thx. How would you envision this to work? What interaction between the application and kong would be required? Can you describe this flow?

I haven't looked into how the plugin works but on a high level, I would imagine when you create a consumer in Kong, you can specify extra fields just like you would for a normal user (verified, dob, etc. ) as json.
After that, you  add the SimpleLogic plugin that adds one or two multiple conditions.
user.verified = true
user.age > 18
...

On each request, the plugin evaluates the conditions and can deny or allow the request.


Deep Link for Standalone

Does this plugin support Windows standalone build?

I have the same problem. Can anyone solve this?

Same here


Mention Capelin in the main README.md

It's still too early to fully credit Capelin and point to papers, since those are still under WIP/submission, but we should definitely already mention it, for the case that people read the thesis (especially after the Best Graduate ceremony in november) and want to have a look. To make this a bit more visible, I added an emoji and also one for the line above for consistency.

@gandreadis Can I also add your thesis to the wiki? See https://github.com/atlarge-research/opendc/wiki/Publications

@fabianishere Absolutely, very good idea!


Ignore flake8 warning W504

Currently breaking tests with the latest flake8, which added a pair of competing rules, W503 and W504, for whether line breaks should be before or after a binary operator. ignore needs to ignore at least one of them, otherwise flake8 can never be pleased.

I don't care very much which warning is ignored but black recommends ignoring W503 https://github.com/ambv/black#line-breaks--binary-operators -- do you have a preference?

I did this to avoid having to change any code, will switch to W503 to copy black/pep8.

Don't worry, it's fine for me as it is -- I was just asking :)
(Maybe we should just switch to black completely instead?)

Maybe we should just switch to black completely instead?

I'm in favor of this. :+1: I've found it very helpful to just let black handle formatting.

Already changed

Thanks!


Integrate Nonin OEM III into firmware

This PR:

Integrates SpO2 sensing into the main loop of the firmware
Slightly renames some types in the Nonin OEM III driver
Slightly refactors/adapts the driver into the uniform low-level Device and higher-level Sensor interface pattern which we have started using with the SFM3019 driver.
Solves a new problem in Github Actions firmware checks (missing public key for installing LLVM and clang from LLVM's website rather than Github's custom distribution which is unable to install clang-tools)

This PR is in the critical path of development, passes clang-tidy and clang-format checks, is needed for me to make progress on the milestone 8 (v0.5), is of at least comparable quality to the rest of the firmware codebase, and probably would not be able to find someone to review it very quickly. We will need to go back and review everything in this PR and refactor and add another layer to the Nonin OEM III driver code, which may induce some refactoring of code from this PR. I will merge in this PR now.
For records-keeping:

This project is licensed under Apache License v2.0 for any software, and Solderpad Hardware License v2.1 for any hardware - do you agree that your contributions to this project will be under these licenses, too? Yes
Were any of these contributions also part of work you did for an employer or a client? No
Does this work include, or is it based on, any third-party work which you did not create? No


check if libzip is available

The configure/make system should check if libzip is available. and then compile the parts that relies on libzip only when it is available. But, please, no GNU automake/autoconf and stuff!

Consider using pkg-config. It is probably installed.

Work in progress in branch check_for_libzip

This is closed by PR #22


[WIP] security : add more tests

Add a few more security test, overall :

check if kernel module signing is enabled.
check if there are any unconfined processes running on the system.
check if the umask is set to 077.
check if there are any hidden executables on the system.
check if core dumps are disabled.
check if there are any processes running as root.
check if AppArmor is enabled.
check if the mount options for proc and tmpfs types are secure.
check if the tmpfs mounts are secure.

@uncleDecart a bunch of these tests are going to fail until we fix eve, should we disable sec test suit or it is OK if the fail?

@uncleDecart a bunch of these tests are going to fail until we fix eve, should we disable sec test suit or it is OK if the fail?

@shjala I think it's better to fix tests on EVE. We can rebase EVE test version after that.


custom parameter in resource

Expected Behavior
Adding a custom parameter on a docker resource i would expect to be able to read it in a task where the resource is used.
Actual Behavior
I can't read it.
Steps to Reproduce the Problem

Create a docker resource with a custom parameter "deployment":

apiVersion: tekton.dev/v1alpha1
kind: PipelineResource
metadata:
  name: docker-image
spec:
  type: image
  params:
    - name: url
      value: issue/pipeline-test
    - name: deployment
      value: dev

Create a task and access the parameters of the resource:

apiVersion: tekton.dev/v1alpha1
kind: Task
metadata:
  name: env-test
spec:
  inputs:
    resources:
    - name: builtImage
      type: image
  steps:
  - name: set
    image: node:12-alpine
    command: ["sh"]
    args: ["-c","echo $(inputs.resources.builtImage.url) ; echo '---' ; echo $(inputs.resources.builtImage.deployment) "]

run the task with a taskrun:

kind: TaskRun
metadata:
  name: env-test-run-resource
spec:
  serviceAccountName: build-bot2
  taskRef:
    name: env-test
  inputs:
    resources:
    - name: builtImage
      resourceRef:
        name: docker-image

read the output:

issue/pipeline-test --- sh: inputs.resources.builtImage.deployment: not found
Additional Info

/kind feature

Would adding an input param to the Task be suitable here?
apiVersion: tekton.dev/v1alpha1
kind: Task
metadata:
  name: env-test
spec:
  inputs:
    params:
    - name: deployment
      type: string
    resources:
    - name: builtImage
      type: image
  steps:
  - name: set
    image: node:12-alpine
    command: ["sh"]
    args: ["-c","echo $(inputs.resources.builtImage.url) ; echo '---' ; echo $(inputs.params.deployment) "]

If that's not suitable for your use case could you go in to a little detail about why not? It strikes me as a little counterintuitive that you could bundle additional arbitrary fields in a PipelineResource since the params it expects are specific to the work that it does.

The problem for me is where I could save additional information regarding the application i'm working with.
On my actual system the docker-resources are the only object with the same cardinality as the application I'm working with so for me it has been quite natural to try to store some information there.
Getting that information as a parameter (as you suggested) force me to write a triggerTemplate for every app i have to put in pipeline.
Of course there are many other solutions I could adopt but reading this paragraph of the documentation made me (wrongly) think my solution would work.

@vas-dev-ops yeah that's the problem with the current design of PipelineResource, it gives the feeling that you can pass any number of parameters, but those parameters are ignored.
We should try to take this into account for the new design of PipelineResource.

@vdemeester Can i take a look at the document you linked (i've required the access with my email<EMAIL_ADDRESS>?
You need to be in the tekton-users@ google group (and/or tekton-dev@ google group), see here

If the relation " reource (n)< --->(1) project" is correct i have thought that even a "config" resource would have solved mine problem.

Depends on what you mean by project (as there is no such notion in tekton) ? the relation is more n -> n : Task define what pipelineresource they need (and it can be many), and you can "bind" the actual resource to any number of task (or taskrun, aka execution of task).


Unreal Engine support

Are there any plans to support Unreal Engine?

Hi @Besjan - thanks for raising this.
We are very interested in Unreal support but we don't have anything planned in the near future. It is technically possible as our native server plugin can work with any buffers and we are more than happy to review any community contribution around this!


fix(deps): update terraform-module

This PR contains the following updates:

Package
Type
Update
Change

github.com/terraform-ibm-modules/terraform-ibm-watsonx-saas-da
module
patch
v1.6.5 -> v1.6.6

terraform-ibm-modules/cos/ibm (source)
module
patch
8.11.13 -> 8.11.14

Release Notes

terraform-ibm-modules/terraform-ibm-watsonx-saas-da (github.com/terraform-ibm-modules/terraform-ibm-watsonx-saas-da)
v1.6.6
Compare Source
Bug Fixes

deps: update terraform terraform-ibm-modules/cos/ibm to v8.11.14 (#175) (e548f1a)

terraform-ibm-modules/terraform-ibm-cos (terraform-ibm-modules/cos/ibm)
v8.11.14
Compare Source
Bug Fixes

deps: update terraform terraform-ibm-modules/secrets-manager/ibm to v1.18.6 (#731) (af80c37)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

/run pipeline

:tada: This PR is included in version 2.5.1 :tada:
The release is available on:

GitHub release
v2.5.1

Your semantic-release bot :package::rocket:


Travis' bundler is too old to install Guard

Changes Unknown when pulling 4b0ca42b38e928658f04a5d34d2e19b191af20dd on bugfix/ci into ** on develop**.

Changes Unknown when pulling f2c660c127da2c40c81e93ac391aa682b8d4679a on bugfix/ci into ** on develop**.

Changes Unknown when pulling 25b4e5bd0c8edb99013b5f18c8c229e654aeb789 on bugfix/ci into ** on develop**.

Changes Unknown when pulling 077f56dd2b0a30fcb1cfe17ae6cfeb5e2831145c on bugfix/ci into ** on develop**.

Changes Unknown when pulling 89dea302fd819645685349007e54d1d96ca35e34 on bugfix/ci into ** on develop**.

Changes Unknown when pulling 89dea302fd819645685349007e54d1d96ca35e34 on bugfix/ci into ** on develop**.

Failures are now JRuby-only, with hanging in the middle of the suite.

Changes Unknown when pulling 515b209085a7d762a1dd356b27b712a52b3eb266 on bugfix/ci into ** on develop**.


lastest plugin not supported for Jellyfin 10.8.8

Information:

Plugin Version: <IP_ADDRESS>
Jellyfin Version:10.8.8

Issue:

Plugin Status: NotSupported

It worked for version <IP_ADDRESS> before. Due to domain changed, not working anymore.

update jellyfin

What is the lowest version of jellyfin that this plugin supports?

update jellyfin

What is the lowest version of jellyfin that this plugin supports?

https://github.com/ThePornDatabase/Jellyfin.Plugin.ThePornDB/blob/main/Jellyfin.Plugin.ThePornDB/ThePornDB.csproj#L44

🌹🌹Could you please kindly keep an baseline version for 10.8.x  (for mine x = 8)?  It's kind of tough for my NAS(latest version not supported for  current NAS OS) to update the Jellyfin version.

should be away to update that version exist more that year

🌹🌹Could you please kindly keep an baseline version for 10.8.x (for mine x = 8)? It's kind of tough for my NAS(latest version not supported for current NAS OS) to update the Jellyfin version.

Same as you, the latest version of Jellyfin I can install on my NAS is 10.8.9

🌹🌹Could you please kindly keep an baseline version for 10.8.x (for mine x = 8)? It's kind of tough for my NAS(latest version not supported for current NAS OS) to update the Jellyfin version.

Same as you, the latest version of Jellyfin I can install on my NAS is 10.8.9

I'm really not understand what's problem to update jelly, where is even multiple docker images
You could build with version you need, change this line, https://github.com/ThePornDatabase/Jellyfin.Plugin.ThePornDB/blob/main/Jellyfin.Plugin.ThePornDB/ThePornDB.csproj#L44


wasm: CppProxyCacheEntry.count required?

Hey,
I am wrapping my head whether the mechanics around CppProxyCacheEntry.count are ready required.
So, for referential integrity (and reuse), we have cppProxyCache that caches the JS-side proxy of the CPP-object.
Is CppProxyCacheEntry.count used for the sole purpose of shielding against a race condition between finalising the JS-side proxy -- WeakRef is dead, but not yet removed from cache -- and getting a proxy for the very same CPP-object?
Wouldn't it be enough to check during removal if the JS-side proxy is still the one stored in the cache?

Hi Daniel,  the reason for adding this count can be found here https://github.com/Snapchat/djinni/pull/41
There are probably other ways to solve this problem, but it was the solution that I came up with at that point.
"Wouldn't it be enough to check during removal if the JS-side proxy is still the one stored in the cache?"  I'm not entirely sure what do you mean.  the JS-side proxy is already gone,  we don't have it any more, when we reach the finalizer.  (note that the nativeRef is not the same as the JS-side proxy object.


Homebrew recipe not updated on release

Expected behavior
brew upgrade ship installs the latest version, (0.19.0 currently)
Actual behavior
brew upgrade ship thinks the latest version of ship is 0.16.0
$  brew upgrade ship
Error: replicatedhq/ship/ship 2200e0dd8365a4b02f47d1536f5a6c4a5f3f3563 already installed
$ ship version
{
    "version": "0.16.0",
    "git": "1dc2578",
    "buildTime": "2018-10-03T21:07:09Z"
}

That's not the behavior I've experienced:
~$ brew upgrade ship
Error: replicatedhq/ship/ship 0.19.0 already installed
~$ ship version
{
    "version": "0.19.0",
    "git": "bebf32f",
    "buildTime": "2018-10-18T21:04:40Z"
}

I think you added the tap before I did, that might explain the issues

Strange. Okay. Got it to work via
brew uninstall --force ship

and then reinstalling. Will close this for now, and reopen if it fails again on the next release.


Use Unicode mode parsing rules

I'm proposing to remove Annex B parsing from this engine's rules. Because I'm also allowing an AST to be passed as an argument to parse it should still be possible to evaluate expressions parsed according to Annex B rules, you'd just have to add your own dependency on regexpp.
Some of that Annex B stuff is madness, most specifically being able to parse expressions with invalid escape codes!

For reference this is the madness I'm talking about: https://hackernoon.com/the-madness-of-parsing-real-world-javascript-regexps-d9ee336df983#.2l8qu3l76
Right now regexpp is handling it all for us, but I really don't want to bring that kind of syntax weirdness forward into a higher-levels of my streaming parser design. Compatibility brings me little benefit.

My resolution to this issue is not to touch this module, but instead to fork it in the bablr org. Each organization has different needs, history, conventions, and audience.


Release on LuaRocks

Could you please release this module on https://luarocks.org (de facto standard repository for Lua modules)?

+1, this integration with ulua is just "meh" imho.
Why? In order to run scilua code I need to run scilua binary from ~/ulua/bin because it does not work otherwise. So, you need to keep both packages, in my case, torch and ulua when you could get everything under luarocks umbrella and thus wonderful itorch.

Seconded - it will be great to see sci-lua work side-by-side with Torch.

@tastyminerals: you don't need to invoke /ulua/bin/scilua to use the scilua library unless you want to the sci syntax extensions (i.e. everything []), in which case you would need to run the scilua script even with luarocks.
That aside, I would be happy to submit scilua to luarocks as well in case someone provides a working rockspec for the package. Keep in mind there is the dependency on OpenBLAS.

What's the best way to have SciLua + OpenBLAS working on ZeroBrane IDE?
I'm a newbie and want to try working on LuaJit + SciLua.

This seems to have already been done: https://luarocks.org/modules/stepelu/sci

Yes, this should be fixed, please re-open if the provided rock doesn't work.

Could the luarocks sci be updated for lua v. 5.4.4?

The sci library requires LuaJIT.

@stepelu Understood.


No manifest file

In svektekit example there is not generated manifest.webmanifest
error:
Generating PWA...
PWA v0.12.0
mode      generateSW
precache  1 entries (0.00 KiB)
files generated
.svelte-kit\output\client\sw.js
.svelte-kit\output\client\workbox-0b852b48.js
warnings
One of the glob patterns doesn't match any files. Please remove or fix the following: {
"globDirectory": "./build/",
"globPattern": "/*.{js,css,html,ico,png,svg,webmanifest}",
"globIgnores": [
"/sw*",
"**/workbox-",
"../.svelte-kit/output/client/sw.js",
"../.svelte-kit/output/client/workbox-.js"
]
}
node:fs:2817
handleErrorFromBinding(ctx);
^
Error: ENOENT: no such file or directory, copyfile './.svelte-kit/output/client/_app/manifest.webmanifest' -> './.svelte-kit/output/client//manifest.webmanifest'
at copyFileSync (node:fs:2817:3)
at file:///F:/WebProjects/sveltekit-pwa/pwa.js:39:4
at Array.forEach ()
at buildPwa (file:///F:/WebProjects/sveltekit-pwa/pwa.js:38:27)

@zpovsic are you using the same code with the @sveltejs/adapter-static adapter? Maybe a new version of SvelteKit changing the output layout? Check the build folder and adjust the paths on pwa.js module

@userquin  - correct
copyFileSync('./.svelte-kit/output/client/_app/manifest.webmanifest', ${d}/manifest.webmanifest)
should become
copyFileSync('./.svelte-kit/output/client/manifest.webmanifest', ${d}/manifest.webmanifest)
in pwa.js

I have been working with Ben to align kit and vite, but we have a problem with a race condition in kit and pwa plugin in the write and close bundle hooks.
You can check this PR https://github.com/antfu/vite-plugin-pwa/pull/327
The folks at Vite and Rollup have gotten involved and an RFC is open to fix the existing problem, you can see it here:
https://github.com/vitejs/vite/discussions/9442
I have been trying to correct the problem by brute force, but for the solution we have to wait for the RFC:

https://github.com/sveltejs/kit/issues/5709
https://github.com/sveltejs/kit/pull/5694
https://github.com/vitejs/vite/pull/9326

Thx for this - I am not sure I fully understand all the details.
But for now - until I see otherwise in the documentation or I get errors -  I changed pwa.js to reflect the new path.
And manually added in index.html <link rel="manifest" href="/manifest.webmanifest">
And in pwa.js search for a workbox*.js file and copy this into build
Then the build process runs nicely and I get an installable PWA.

@Tommertom if you're using SvelteKit 358+ you need to copy sw stuff manually.
The example in this repo is wrong with the new Kit version and may or may not work.
The problem is the following:

writeBundle in Kit plugin will generate the prerendered folder with the SSG
then, we have the closeBundle hook on Kit and pwa plugin: since this 2 hooks are async, both will run in parallel, so the adapter can finish before the pwa plugin finish building the sw and the workbox-xxx modules

You need to copy manually, ofc if you configure the output folder on the pwa plugin to be the adapter output folder the problem disappear.
Since we'll remove both scripts from the SvelteKit example (pwa.js and pwa-configuration.js), I think we don't need to change the docs...
With new SvelteKit version, Vite will be configured properly, and so we don't need any of the scripts: Vite's outDir and publicDirconfigured properly, the webmanifest will be on the client output folder (and copied by the adapter process).

Got it! Thx

Released initial version of custom kit plugin: https://vite-pwa-org.netlify.app/frameworks/sveltekit.html
The example in this repo Will be removed, check the New repo for new custom kit plugin here https://github.com/vite-pwa/sveltekit