Service Mesh can't through the dedicated outbound when service port not equal  targetPort

Bug description
We have a situation when service port and targetPort is different, the request in the service mesh goes through the PassthroughCluster instead of the dedicated outbound . But if the request is from the istio gateway, it is normal.
Affected product area
[ ] Docs
[ ] Installation
[X] Networking
[ ] Performance and Scalability
[ ] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
[ ] Upgrade
Affected features
Expected behavior
All requests to "gqc-my-home-crd.crd-test.svc.cluster.local" goes through the mesh.
Steps to reproduce the bug

Start pod&service in a namespace with sidecar injection enabled
service yaml:
apiVersion: v1
kind: Service
metadata:
  labels:
    app.kubernetes.io/instance: gqc-my-home-crd
    app.kubernetes.io/name: gqc-my-home-crd
  name: gqc-my-home-crd
  namespace: crd-test
spec:
  clusterIP: <IP_ADDRESS>
  ports:
    - name: http
      port: 80
      protocol: TCP
      targetPort: http #8220
  selector:
    app.kubernetes.io/instance: gqc-my-home-crd
    app.kubernetes.io/name: gqc-my-home-crd
  sessionAffinity: None
  type: ClusterIP

Config  DestinationRule&VirtualService:
kind: DestinationRule
apiVersion: networking.istio.io/v1alpha3
metadata:
  labels:
    app.kubernetes.io/instance: gqc-my-home-crd
    app.kubernetes.io/name: gqc-my-home-crd
  name: gqc-my-home-crd
  namespace: crd-test
spec:
  host: gqc-my-home-crd
  subsets:
    - labels:
        version: default
      name: default
    - labels:
        version: v2
      name: v2
---
apiVersion: networking.istio.io/v1alpha3
kind: VirtualService
metadata:
  labels:
    app.kubernetes.io/instance: gqc-my-home-crd
    app.kubernetes.io/name: gqc-my-home-crd
  name: gqc-my-home-crd
  namespace: crd-test
spec:
  hosts:
    - gqc-my-home-crd.crd-test.svc.cluster.local
  http:
    - match:
        - headers:
            x-project:
              exact: v2
      route:
        - destination:
            host: gqc-my-home-crd.crd-test.svc.cluster.local
            subset: v2
          headers:
            request:
              add:
                x-project: v2
            response:
              add:
                x-project: v2
    - route:
        - destination:
            host: gqc-my-home-crd.crd-test.svc.cluster.local
            subset: default
          headers:
            request:
              add:
                x-project: default
            response:
              add:
                x-project: default
          weight: 100

Wait until the pod is READY

Verify the istio-proxy container is up and running

in other namespace pod (sidecar injection enabled),use curl to send rquest[GET]
CURL LOG
[root@gqc-log-85b477456b-nsfvk Log]# curl -v http://gqc-my-home-crd.crd-test/faq
* About to connect() to gqc-my-home-crd.crd-test port 80 (#0)
*   Trying <IP_ADDRESS>...
* Connected to gqc-my-home-crd.crd-test (<IP_ADDRESS>) port 80 (#0)
> GET /faq HTTP/1.1
> User-Agent: curl/7.29.0
> Host: gqc-my-home-crd.crd-test
> Accept: */*
>
< HTTP/1.1 200 OK
< x-server-id: GQC-Server
< x-faq-servicehost: http://<IP_ADDRESS>:3000
< date: Fri, 16 Apr 2021 08:38:35 GMT
< content-length: 4
< x-envoy-upstream-service-time: 35
< server: envoy
<
* Connection #0 to host gqc-my-home-crd.crd-test left intact
true

ISTIO-PROXY ACCESS LOG
[2021-04-16T08:38:35.729Z] "GET /faq HTTP/1.1" 200 - via_upstream - "-" 0 4 37 35 "-" "curl/7.29.0" "ddab2953-9d64-98c4-958c-5b910e6c8e3a" "gqc-my-home-crd.crd-test" "<IP_ADDRESS>:8220" PassthroughCluster <IP_ADDRESS>:59668 <IP_ADDRESS>:8220 <IP_ADDRESS>:59666 - allow_any

Highlights:

Header is not added
Mesh goes through the PassthroughCluster

If i change k8s service port to 8220

  ports:
      - name: http
        port: 8220
        protocol: TCP
        targetPort: http  #8220

Use curl to send rquest[GET]
CURL LOG
[root@gqc-logx-85b477456b-nsfvk Log]# curl -v http://gqc-my-home-crd.crd-test:8220/faq
* About to connect() to gqc-my-home-crd.crd-test port 8220 (#0)
*   Trying <IP_ADDRESS>...
* Connected to gqc-my-home-crd.crd-test (<IP_ADDRESS>) port 8220 (#0)
> GET /faq HTTP/1.1
> User-Agent: curl/7.29.0
> Host: gqc-my-home-crd.crd-test:8220
> Accept: */*
>
< HTTP/1.1 200 OK
< x-server-id: GQC-Server
< x-faq-servicehost: http://<IP_ADDRESS>:3000
< date: Fri, 16 Apr 2021 08:46:32 GMT
< content-length: 4
< x-envoy-upstream-service-time: 47
< server: envoy
< x-project: default
<
* Connection #0 to host gqc-my-home-crd.crd-test left intact
true

ISTIO-PROXY ACCESS LOG
[2021-04-16T08:46:32.701Z] "GET /faq HTTP/1.1" 200 - via_upstream - "-" 0 4 49 47 "-" "curl/7.29.0" "6ed948f6-0d15-944f-8820-0785766ceeba" "gqc-my-home-crd.crd-test:8220" "<IP_ADDRESS>:8220" outbound|8220|default|gqc-my-home-crd.crd-test.svc.cluster.local <IP_ADDRESS>:48176 <IP_ADDRESS>:8220 <IP_ADDRESS>:41816 - -

Highlights:

Header "x-project" is added
mesh goes through the outbound

It works (only port = targetPort can work )

Check Envoy Config
This is the config of Port 80, and there is no difference in the config of Port 8220.
{
"name": "gqc-my-home-crd.crd-test.svc.cluster.local:80",
"domains": [
  "gqc-my-home-crd.crd-test.svc.cluster.local",
  "gqc-my-home-crd.crd-test.svc.cluster.local:80",
  "gqc-my-home-crd",
  "gqc-my-home-crd:80",
  "gqc-my-home-crd.crd-test.svc.cluster",
  "gqc-my-home-crd.crd-test.svc.cluster:80",
  "gqc-my-home-crd.crd-test.svc",
  "gqc-my-home-crd.crd-test.svc:80",
  "gqc-my-home-crd.crd-test",
  "gqc-my-home-crd.crd-test:80",
  "<IP_ADDRESS>",
  "<IP_ADDRESS>:80"
],
"routes": [
  {
   "match": {
    "prefix": "/",
    "case_sensitive": true,
    "headers": [
     {
      "name": "x-project",
      "exact_match": "v2"
     }
    ]
   },
   "route": {
    "cluster": "outbound|80|v2|gqc-my-home-crd.crd-test.svc.cluster.local",
    "timeout": "0s",
    "retry_policy": {
     "retry_on": "connect-failure,refused-stream,unavailable,cancelled,retriable-status-codes",
     "num_retries": 2,
     "retry_host_predicate": [
      {
       "name": "envoy.retry_host_predicates.previous_hosts"
      }
     ],
     "host_selection_retry_max_attempts": "5",
     "retriable_status_codes": [
      503
     ]
    },
    "max_stream_duration": {
     "max_stream_duration": "0s"
    }
   },
   "metadata": {
    "filter_metadata": {
     "istio": {
      "config": "/apis/networking.istio.io/v1alpha3/namespaces/crd-test/virtual-service/gqc-my-home-crd"
     }
    }
   },
   "decorator": {
    "operation": "gqc-my-home-crd.crd-test.svc.cluster.local:80/*"
   },
   "request_headers_to_add": [
    {
     "header": {
      "key": "x-project",
      "value": "v2"
     },
     "append": true
    }
   ],
   "response_headers_to_add": [
    {
     "header": {
      "key": "x-project",
      "value": "v2"
     },
     "append": true
    }
   ]
  },
  {
   "match": {
    "prefix": "/"
   },
   "route": {
    "cluster": "outbound|80|default|gqc-my-home-crd.crd-test.svc.cluster.local",
    "timeout": "0s",
    "retry_policy": {
     "retry_on": "connect-failure,refused-stream,unavailable,cancelled,retriable-status-codes",
     "num_retries": 2,
     "retry_host_predicate": [
      {
       "name": "envoy.retry_host_predicates.previous_hosts"
      }
     ],
     "host_selection_retry_max_attempts": "5",
     "retriable_status_codes": [
      503
     ]
    },
    "max_stream_duration": {
     "max_stream_duration": "0s"
    }
   },
   "metadata": {
    "filter_metadata": {
     "istio": {
      "config": "/apis/networking.istio.io/v1alpha3/namespaces/crd-test/virtual-service/gqc-my-home-crd"
     }
    }
   },
   "decorator": {
    "operation": "gqc-my-home-crd.crd-test.svc.cluster.local:80/*"
   },
   "request_headers_to_add": [
    {
     "header": {
      "key": "x-project",
      "value": "default"
     },
     "append": true
    }
   ],
   "response_headers_to_add": [
    {
     "header": {
      "key": "x-project",
      "value": "default"
     },
     "append": true
    }
   ]
  }
],
"include_request_attempt_count": true
},

Version
$ bin/istioctl version --remote
client version: 1.9.2
control plane version: 1.9.2
data plane version: 1.9.2 (24 proxies)

$ kubectl version --short
Client Version: v1.20.0
Server Version: v1.19.8

cilium version: 1.9.5
    loadBalancer.mode=hybrid
    hostServices.enabled=true
    kubeProxyReplacement=strict
    ...

How was Istio installed?
IstioOperator
kind: IstioOperator
apiVersion: install.istio.io/v1alpha1
metadata:
  name: installed-state
  namespace: istio-system
spec:
  components:
    base:
      enabled: true
    cni:
      enabled: true
    egressGateways:
      - enabled: false
        name: istio-egressgateway
    ingressGateways:
      - enabled: true
        name: istio-ingressgateway
    istiodRemote:
      enabled: false
    pilot:
      enabled: true
  hub: docker.io/istio
  meshConfig:
    accessLogFile: /dev/stdout
    defaultConfig:
      proxyMetadata: {}
      tracing:
        sampling: 100
        zipkin:
          address: 'jaeger-collector.kube-event:9411'
    enablePrometheusMerge: true
  profile: default
  tag: 1.9.2
  values:
    base:
      enableCRDTemplates: false
      validationURL: ''
    gateways:
      istio-egressgateway:
        autoscaleEnabled: true
        env: {}
        name: istio-egressgateway
        secretVolumes:
          - mountPath: /etc/istio/egressgateway-certs
            name: egressgateway-certs
            secretName: istio-egressgateway-certs
          - mountPath: /etc/istio/egressgateway-ca-certs
            name: egressgateway-ca-certs
            secretName: istio-egressgateway-ca-certs
        type: ClusterIP
        zvpn: {}
      istio-ingressgateway:
        autoscaleEnabled: true
        env: {}
        name: istio-ingressgateway
        secretVolumes:
          - mountPath: /etc/istio/ingressgateway-certs
            name: ingressgateway-certs
            secretName: istio-ingressgateway-certs
          - mountPath: /etc/istio/ingressgateway-ca-certs
            name: ingressgateway-ca-certs
            secretName: istio-ingressgateway-ca-certs
        type: LoadBalancer
        zvpn: {}
    global:
      arch:
        amd64: 2
        ppc64le: 2
        s390x: 2
      configValidation: true
      defaultNodeSelector: {}
      defaultPodDisruptionBudget:
        enabled: true
      defaultResources:
        requests:
          cpu: 10m
      imagePullPolicy: ''
      imagePullSecrets: []
      istioNamespace: istio-system
      istiod:
        enableAnalysis: false
      jwtPolicy: third-party-jwt
      logAsJson: false
      logging:
        level: 'default:info'
      meshNetworks: {}
      mountMtlsCerts: false
      multiCluster:
        clusterName: ''
        enabled: false
      network: ''
      omitSidecarInjectorConfigMap: false
      oneNamespace: false
      operatorManageWebhooks: false
      pilotCertProvider: istiod
      priorityClassName: ''
      proxy:
        autoInject: enabled
        clusterDomain: cluster.local
        componentLogLevel: 'misc:error'
        enableCoreDump: false
        excludeIPRanges: ''
        excludeInboundPorts: ''
        excludeOutboundPorts: ''
        image: proxyv2
        includeIPRanges: '*'
        logLevel: warning
        privileged: true
        readinessFailureThreshold: 30
        readinessInitialDelaySeconds: 1
        readinessPeriodSeconds: 2
        resources:
          limits:
            cpu: 2000m
            memory: 1024Mi
          requests:
            cpu: 100m
            memory: 128Mi
        statusPort: 15020
        tracer: zipkin
      proxy_init:
        image: proxyv2
        resources:
          limits:
            cpu: 2000m
            memory: 1024Mi
          requests:
            cpu: 10m
            memory: 10Mi
      sds:
        token:
          aud: istio-ca
      sts:
        servicePort: 0
      tracer:
        datadog: {}
        lightstep: {}
        stackdriver: {}
        zipkin: {}
      useMCP: false
    istiodRemote:
      injectionURL: ''
    pilot:
      autoscaleEnabled: true
      autoscaleMax: 5
      autoscaleMin: 1
      configMap: true
      cpu:
        targetAverageUtilization: 80
      enableProtocolSniffingForInbound: true
      enableProtocolSniffingForOutbound: true
      env:
        ENABLE_LEGACY_FSGROUP_INJECTION: false
      image: pilot
      keepaliveMaxServerConnectionAge: 30m
      nodeSelector: {}
      replicaCount: 1
      traceSampling: 1
    telemetry:
      enabled: true
      v2:
        enabled: true
        metadataExchange:
          wasmEnabled: false
        prometheus:
          enabled: true
          wasmEnabled: false
        stackdriver:
          configOverride: {}
          enabled: false
          logging: false
          monitoring: false
          topology: false

Environment where the bug was observed (cloud vendor, OS, etc)
Private kubernetes cluster
I got this issue after using cilium& upgrade istio, VirtualService was normal before,so I don’t know if it is caused by a configuration error or a bug .

I use tcpdump to capture packets in two cases:
Success through by dedicated outbound :
07:07:30.332382 IP gqc-log-5cbd659f9b-khq55.34918 > 10-216-12-126.gqc-my-home-crd.crd-test.svc.cluster.local.8220: Flags [P.], seq<PHONE_NUMBER>:2048147439, ack<PHONE_NUMBER>, win 502, options [nop,nop,TS val<PHONE_NUMBER> ecr<PHONE_NUMBER>], length 1529
07:07:30.333705 IP 10-216-12-126.gqc-my-home-crd.crd-test.svc.cluster.local.8220 > gqc-log-5cbd659f9b-khq55.34918: Flags [.], ack 1529, win 494, options [nop,nop,TS val<PHONE_NUMBER> ecr<PHONE_NUMBER>], length 0
07:07:30.360278 IP 10-216-12-126.gqc-my-home-crd.crd-test.svc.cluster.local.8220 > gqc-log-5cbd659f9b-khq55.34918: Flags [P.], seq 1:1436, ack 1529, win 501, options [nop,nop,TS val<PHONE_NUMBER> ecr<PHONE_NUMBER>], length 1435
07:07:30.360334 IP gqc-log-5cbd659f9b-khq55.34918 > 10-216-12-126.gqc-my-home-crd.crd-test.svc.cluster.local.8220: Flags [.], ack 1436, win 494, options [nop,nop,TS val<PHONE_NUMBER> ecr<PHONE_NUMBER>], length 0

Fail through by PassthroughCluster:
07:22:08.238366 IP gqc-log-5cbd659f9b-khq55.43572 > 10-216-12-117.gqc-my-home-crd.crd-test.svc.cluster.local.8220: Flags [S], seq 456758148, win 64860, options [mss 1410,sackOK,TS val 44191485 ecr 0,nop,wscale 7], length 0
07:22:08.239340 IP 10-216-12-117.gqc-my-home-crd.crd-test.svc.cluster.local.8220 > gqc-log-5cbd659f9b-khq55.43572: Flags [S.], seq<PHONE_NUMBER>, ack 456758149, win 64308, options [mss 1410,sackOK,TS val<PHONE_NUMBER> ecr 44191485,nop,wscale 7], length 0
07:22:08.239379 IP gqc-log-5cbd659f9b-khq55.43572 > 10-216-12-117.gqc-my-home-crd.crd-test.svc.cluster.local.8220: Flags [.], ack 1, win 507, options [nop,nop,TS val 44191486 ecr<PHONE_NUMBER>], length 0
07:22:08.239738 IP gqc-log-5cbd659f9b-khq55.43572 > 10-216-12-117.gqc-my-home-crd.crd-test.svc.cluster.local.8220: Flags [P.], seq 1:1391, ack 1, win 507, options [nop,nop,TS val 44191487 ecr<PHONE_NUMBER>], length 1390
07:22:08.240183 IP 10-216-12-117.gqc-my-home-crd.crd-test.svc.cluster.local.8220 > gqc-log-5cbd659f9b-khq55.43572: Flags [.], ack 1391, win 501, options [nop,nop,TS val<PHONE_NUMBER> ecr 44191487], length 0
07:22:08.264709 IP 10-216-12-117.gqc-my-home-crd.crd-test.svc.cluster.local.8220 > gqc-log-5cbd659f9b-khq55.43572: Flags [P.], seq 1:1497, ack 1391, win 501, options [nop,nop,TS val<PHONE_NUMBER> ecr 44191487], length 1496
07:22:08.264742 IP gqc-log-5cbd659f9b-khq55.43572 > 10-216-12-117.gqc-my-home-crd.crd-test.svc.cluster.local.8220: Flags [.], ack 1497, win 496, options [nop,nop,TS val 44191512 ecr<PHONE_NUMBER>], length 0

The ip here may be different from the issue , because the pod has been rebuilt.

Same issue as https://github.com/istio/istio/issues/27619

@bianpengyuan Thanks for the quick reply! I agree that this is very similar, but why does this work when the service port equal  targetPort?
According to the issue  #27619 ,if I want istio + cilium to work well, Cilium must be configured ：
kubeProxyReplacement=partial
hostServices.enabled=false

Is this understanding correct?

@EugeneCI the problem is that cilium is translating the Service -> endpoint before it reaches Istio. So it messes with Istio's understanding, since expect requests to Service IP/port

Thanks again! What is the future plan? It's by design the cannot change factor ?

It is by design and at this point seems unlikely it will change in the near
future as there are no current plans
On Sat, Apr 17, 2021, 4:36 AM Eugene @.***> wrote:

Thanks again! What is the future plan? It's by design the cannot change
factor ?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/32231#issuecomment-821809400, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYGXK5HGT3RHBVMRFUZB3TJFXFTANCNFSM43BWMHEQ
.

For all who have troubles with cilium in strict mode without kube-proxy.
From my point of view, the root cause for the issues was our cilium version < 12.x and linux kernel < 5.7 due to the usage of ubuntu 20.04 as kubernetes node image.
There were the same issues as described in http(s) communication across namespaces using services with port mappings to different destination ports. Using the same ports mitigated the problem for some pods, but not for all.
e.g. Java based service worked well, but python services with async lib had troubles.....
After updating to cilium 1.12.6 we still faced the issues, but after looking into the logs of the cilium pods, I found in the startup section warnings about possible problems with istio using a kernel lower than 5.7.
We updated the cluster nodes to a current ubuntu 22.04 with kernel 5.15.x and voilà, all our issues were gone. We even don't need the port mapping change to use the same destination ports.
The for us working command line to render the cilium chart is:
   helm template cilium cilium/cilium --version 1.12.6 --namespace` kube-system --set cni.exclusive=false --set operator.replicas=1 \
     --set hubble.tls.auto.method=cronJob --set hubble.relay.enabled=true --set hubble.ui.enabled=true \
     --set socketLB.hostNamespaceOnly=true --set nodePort.enabled=true --set hostPort.enabled=true \
     --set externalIPs.enabled=true --set bpf.masquerade=false \
     --set kubeProxyReplacement=strict --set k8sServiceHost=CHANGEME --set k8sServicePort=CHANGEME

kubernetes node:
System Info:
  Kernel Version:             5.15.0-60-generic
  OS Image:                   Ubuntu 22.04.1 LTS
  Operating System:           linux
  Architecture:               amd64
  Container Runtime Version:  containerd://1.6.16
  Kubelet Version:            v1.22.16


fix: dropped idp lark err

This fixes a dropped err in the idp package.

Replaced by: https://github.com/casbin/casdoor/commit/66aca3124ca31f4a83cc50d433044331828c7f16


Capture errors running tag-track on GitHub action

Current method only works if is tag-track the one that reports the error, but if the program panics or there is an issue in the bash script that runs tag-track, the error is not processed.

The stderr and exit code is now stored and used to check if there was a unexpected error. If there was an error, it will be printed using echo "error::Raw Tag Track output: <OUTPUT>" .


Update HNC CLI to matching naming doc

Implement bit.ly/hnc-cli-naming
/assign @adrianludwin

Hi @adrianludwin
If you are okay. I can pick this up and update kubectl hnc plugin as mentioned in hnc-cli-naming doc.

Thanks @VineethReddy02 but there's a fair amount of context that was needed to implement this stuff, so it was easier to do it myself.


Zoom instructions to show

I put these here because I wanted to link to them in the https://coderefinery.github.io/manuals/workshop-playbook/
These instructions are meant to be posted in zoom chat or as screenshare during exercise sessions:
- If you have a team name -> find room named accordingly
- If you want to join ad hoc team -> join room
- If you need help join a helper room or write in HackMD
    - If two or more EHs then other one could be in room and others could circle where requested
- Open rooms are for ad hoc teams or private EH help
- Quiet room is for staying in Zoom but having a moment of silence for focused work

I recommend to keep this in the manual close to the role responsible for this.

I recommend to keep this in the manual close to the role responsible for this.


Show Header and Footer on Error

Describe the Feature Request
Currently, if there's an uncaught error, the whole page goes blank. We should have a way to catch such errors and display the header and footer with an error message. The error message could include a link to our Discord to encourage reporting the error.

Implemented in #439


add int validation to rest api

Addresses #987

should be fixed now with this commit https://github.com/agentejo/cockpit/commit/eaf8a22f2bd98e48b260bad96c61c636c264cdd2


When Fields in Selectable comes from type alias of named tuple. the fields are not selectable

Compiler version
3.6.4-RC1-bin-20241122-64411b6-NIGHTLY and earlier
Minimized code
import scala.language.experimental.namedTuples

class SelectableNT[A <: NamedTuple.AnyNamedTuple](val nt: A) extends Selectable:
  type Fields = A
  def selectDynamic(x: String) = ???

object Test:

  val a = (name = "foo", age = 1)

  val sa = SelectableNT(a)
  sa.name   // ok

  type B = a.type
  val b: B = a

  val sb = SelectableNT(b)
  sb.name   // fails

Output
value name is not a member of bug.SelectableNT[(bug.Test.a : (name : String, age : Int))]

Expectation
Successful compilation

The problem came actually not from the fact that B is an alias, but that it is an alias of a singleton type.


Add Kopia SFTP support

Is your feature request related to a problem? Please describe.
I'm currently using Kopia with SFTP backend to store snapshots, I see Kanister only supports S3, Azure and GCP.
Describe the solution you'd like
It would be great if Kanister would support SFTP as a storage location for Kopia: https://kopia.io/docs/repositories/#sftp
I believe this would require adding some parameters to the Kanister Profile.
I'm not good enough at Go yet to be able to make a PR that wouldn't break anything else.
Describe alternatives you've considered
Using S3 as a storage, but less convenient for me as I have a big SFTP backup storage available.
Environment
Kubernetes Version/Provider: RKE2 1.25.3
Storage Provider: Rook CEPH / SFTP server for Kopia backups
Cluster Size (#nodes): 3 master + 3 workers
Data Size: variable, depends on the PVC to backup - couple of MB to ~250GB
Additional context
N/A

Hey @fastlorenzo - thanks for the request!
We are working on improving the integration of Kopia in Kanister and will consider adding SFTP support with the other planned changes.

Hi team, will this be considered and implemented? I would suggest to not close it to keep track. Thanks

Reopening

not stale


Fix badge for high resolutions

Take provided line height into consideration

For demo code on NativeBase docs, it causes the badges to look like this

Please modify the PR, and an explanation for what it fixes for which use case would help :)


Not work for private torrents

try submitting the link of the torrent to the web interface of transmission but this doesnt work for private sites that need a session for the torrent file to be downloaded.

Yes, this is not supported in Transmission, I can't do anything about this. You have to click to open the web interface and upload the torrent file to Transmission.

Hm. How works other extension? https://addons.mozilla.org/ru/firefox/addon/torrent-to-web/

Oh, they download the torrent in the browser and reupload to Transmission…

Can you do this in your extension?

Please test the current git master version (Clone or download → Download ZIP, extract, go to about:debugging in Firefox, click Load Temporary Addon, select manifest.json in the extracted folder), should work now

Work. Please upload to addons.mozilla.org

Uploaded (and approved already, wow that was fast!)


AssetOrArchive shouldn't be in the schema

Before this exclusion, the schemas of providers using AssetOrArchive would have its type definition in their schema. Besides being wrong anyway, it would also generate invalid Go code because the signatures fields start with numbers.

Let's make sure we have a schema test here before merging. I would add the test in infer/tests and have it call the GetSchema method on a provider that has an resource.Asset, resource.Archive and types.AssetOrArchive.

Done.


Permission denied for  python binary in .pybuilder path

Hi,
I'm getting the following error when I run pyb in Win7:
PyBuilder version 0.12.0.dev20200402011033
Build started at 2020-04-03 13:40:49
------------------------------------------------------------
------------------------------------------------------------
BUILD FAILED - [Errno 13] Permission denied: 'c:\\code\\projectname\\.pybuilder\\plugins\\cpython-3.7.3.final.0\\Scripts\\python.exe'
------------------------------------------------------------
Build finished at 2020-04-03 13:40:50
Build took 1 seconds (1041 ms)

If I wait for a few minutes then it allows me to re-run the build.
Is this something you've seen or is it because of my setup? Not seen this in the previous 0.12 pre-releases I've been using just with the most recent ones.
Thank you,
Christos

Could you please post a larger log excerpt from the log, quote it as I did above and run the build with -X -v (debug verbose)?
And the answer is no, we don't see it, as you can see full build on Windows and latest PyB completes fine: https://travis-ci.org/github/pybuilder/pybuilder/jobs/669949295
I would also recommend upgrading to latest Python 3.7, i.e. 3.7.7 and see if it changes things.

@cmdel any news?

Upgrading to 3.7.7 python seems to stop this issue for me. Thanks @arcivanov


Monitor deployments again

A few months ago we migrated our deployment solution Anaconda Workbench from Digital Ocean to AWS. This came with some difficulties that are still being worked out, leading to the deployments being currently unstable. At the moment, we have pretty much no monitoring in place. We need to re-enable monitoring when the deployments become more stable.

[x] Re-enable the lambda checking deployments
The static site now hosts a JSON file that lists the expected deployments, it could be used to feed the lamba: https://examples.holoviz.org/_static/deployments.json
[x] Document the lambda, for now I suggest in a file on the repo that is not part of the website
[x] Add a doit task that reports the state of all the deployments (same code as the lambda basically)
[ ] I'd love it if we could host a static page / tiny Panel app that reports the status of each deployment when visited.

(I chose not to comment in https://github.com/holoviz-topics/examples/issues/184 that has a similar goal but is a bit outdated)

https://github.com/holoviz-topics/examples/pull/426


Enhance publisher

Currently the publisher only supports setting a message. It would be nice to have support for setting message key and headers.
Something like err = ctx.GetPublisher().Publish(ctx, pubsub.PublishRequest{ Topic: "products", Message: msg, Key: "a key"}).
I hacked breaking code changes on my fork this weekend and wanted to discuss:

if this is something you would like to support ?
how should be approach it so that we still support the old api ?

@PapePathe gofr's publisher that you get from ctx.GetPublisher() is a generic implementation for publishing to different pub-sub backends like kafka, mqtt, gcp etc. Setting up of message key and headers is something relavant to kafka only not to other pub-sub backends.
if this is something you would like to support ? : Yes, we are not bounded by any datasource.
how should be approach it so that we still support the old api ?
To have a functionality specific to kafka or any other backend, user can extend the functionality, similar to how we have extended for mongo.
we have defined it interface and methods in gofr : https://github.com/gofr-dev/gofr/blob/development/pkg/gofr/datasource/mongo.go
and its implementation exists in a different repo : https://github.com/vipul-rawat/gofr-mongo
Such that those who don't want it, will not have to get it as a dependency.

Thanks for the quick reply. I will study the mongo example and go from there

I am just curious how the mongo example can be integrated on an existing app

@PapePathe sure here is the mongo example : https://github.com/vipul-rawat/using-mongo


[WIP] Change application id format

Pull Request Test Coverage Report for Build 642

0 of 0   changed or added relevant lines in 0 files are covered.
7 unchanged lines in 3 files lost coverage.
Overall coverage increased (+0.4%) to 69.467%

Files with Coverage Reduction
New Missed Lines
%

dist/plugins/Log.js
1
81.9%

dist/plugins/PluginContext.js
2
76.92%

dist/index.js
4
80.58%

Totals

Change from base Build 638:
0.4%

Covered Lines:
2309

Relevant Lines:
3083

💛  - Coveralls


Instruction to get repository URL for helm's requirements.yaml

While az acr helm implements by calling the helm command, the documentation here didn't reflect how to develop helm charts that depends on an acr chart, using requirements.yaml, by not providing a way to get the repo URL. (it should be helm repo list I assume)

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

ID: 59c4be11-ec02-7160-e65b-2218bfd70f68
Version Independent ID: 19e08339-390f-ccfa-885c-2643722bd186
Content: Use Helm repositories in Azure Container Registry
Content Source: articles/container-registry/container-registry-helm-repos.md
Service: container-registry
GitHub Login: @iainfoulds
Microsoft Alias: iainfou

@tdihp Thanks for the feedback! We are currently investigating and will update you shortly.

@iainfoulds Please provide your comments

Sorry, not sure I understand the doc feedback, @tdihp. What is it that you're trying to do so we can make sure we address your needs.
CC: @SteveLas and @sajayantony as there's active work around the Helm integration and ACR.

@tdihp - sorry about not documenting the repo URL scenario a bit more. The overall direction has been to unify helm and the registry and priority has been around landing a proper model for helm3 which is natively integrated into the registry.

@iainfoulds Helm requirements.yml will need a repo URL for dependency tracking. The documentation didn't cover how we can retrieve this information for our repository.
@sajayantony Thanks for pointing out! I've checked helm3. I think the need is still there, as you can fetch dependency charts across registry I think?

@tdihp i do believe the helm team is working on this.
One of the many reasons we inverted the registry & helm support to be natively integrated into helm was just for this reason.
Please log Helm questions in the helm/helm repo so @jdolitski and others can see and respond

@iainfoulds I am assigning this issue to you so that you can act on this if doc update is required.

closing as this is a helm 3 requirement.

@jakaruna-MSFT As @SteveLasker notes, this is an upcoming Helm 3 requirement, so there's no current action on the existing doc #please-close

@tdihp We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.

@BryanTrach-MSFT Any updates on this? I have a chart that depends on subcharts in a ACR repo. I can't seem to find a URL for the chart that works when calling helm dep update. I'm using Helm v3.1.2.

@aaronwjha I would suggest opening a new issue under this doc to bring fresh eyes to your request. Thank you for your understanding.


Fix paper.md

Need to update paper.md with better and comprehensive instructions(some were lost during repo transfer).
Maybe an example paper might be useful and then move the instructions to README.md.

Seems like a good idea! :)


Fix defaults for mt_rand

I was about to submit this exact same PR, along with the better description and all! Thanks :)

:) glad to help!

Just checking - shouldn't these be @param int $min and @param int max with type definitions?

Nice catch! Thanks


Is there other ways to contact developers besides Telegram that is more active?

I've been noticing that once in a while, multiple users in Telegram will simply ask questions that only the developers will respond to.
Annoyingly, there's no other public developer besides Kui that is there to respond, and even then he doesn't respond at all to other questions when people come in to ask something different.

By yourself.

By yourself.

what?

Leave your question here. We'll try to answer them. The other two developers are not so good at English. So if the question needs a lot of words to answer, I am the better one.

你们用中文回答， 没关系的
我们会尽力翻译成英文， 不用担心

Leave your question here. We'll try to answer them. The other two developers are not so good at English. So if the question needs a lot of words to answer, I am the better one.

Alright, good to know.


Disable Java kernel autoselection test

It's been failing for the last half dozen runs. https://github.com/microsoft/vscode-jupyter/runs/1690934132

Codecov Report

Merging #4371 (ae07b7e) into main (e41d7fb) will increase coverage by 0%.
The diff coverage is n/a.

@@          Coverage Diff          @@
##            main   #4371   +/-   ##
=====================================
  Coverage     75%     75%
=====================================
  Files        390     390
  Lines      25510   25510
  Branches    3647    3647
=====================================
+ Hits       19261   19263    +2
- Misses      4753    4759    +6
+ Partials    1496    1488    -8

Impacted Files
Coverage Δ

...client/datascience/editor-integration/decorator.ts
59% <0%> (-14%)
:arrow_down:

src/client/common/application/debugService.ts
46% <0%> (-7%)
:arrow_down:

...datascience/editor-integration/codelensprovider.ts
84% <0%> (-3%)
:arrow_down:

.../datascience/editor-integration/codeLensFactory.ts
85% <0%> (-2%)
:arrow_down:

...ient/datascience/editor-integration/codewatcher.ts
68% <0%> (-1%)
:arrow_down:

.../client/datascience/notebook/kernelWithMetadata.ts
85% <0%> (ø)

.../datascience/interactive-common/interactiveBase.ts
71% <0%> (+<1%)
:arrow_up:

src/client/datascience/jupyter/kernels/helpers.ts
60% <0%> (+<1%)
:arrow_up:

...ient/datascience/raw-kernel/rawNotebookProvider.ts
90% <0%> (+1%)
:arrow_up:

...ient/datascience/jupyter/kernels/kernelSelector.ts
85% <0%> (+1%)
:arrow_up:

... and 5 more

Codecov Report

Merging #4371 (ae07b7e) into main (e41d7fb) will increase coverage by 0%.
The diff coverage is n/a.

@@          Coverage Diff          @@
##            main   #4371   +/-   ##
=====================================
  Coverage     75%     75%
=====================================
  Files        390     390
  Lines      25510   25510
  Branches    3647    3647
=====================================
+ Hits       19261   19263    +2
- Misses      4753    4759    +6
+ Partials    1496    1488    -8

Impacted Files
Coverage Δ

...client/datascience/editor-integration/decorator.ts
59% <0%> (-14%)
:arrow_down:

src/client/common/application/debugService.ts
46% <0%> (-7%)
:arrow_down:

...datascience/editor-integration/codelensprovider.ts
84% <0%> (-3%)
:arrow_down:

.../datascience/editor-integration/codeLensFactory.ts
85% <0%> (-2%)
:arrow_down:

...ient/datascience/editor-integration/codewatcher.ts
68% <0%> (-1%)
:arrow_down:

.../client/datascience/notebook/kernelWithMetadata.ts
85% <0%> (ø)

.../datascience/interactive-common/interactiveBase.ts
71% <0%> (+<1%)
:arrow_up:

src/client/datascience/jupyter/kernels/helpers.ts
60% <0%> (+<1%)
:arrow_up:

...ient/datascience/raw-kernel/rawNotebookProvider.ts
90% <0%> (+1%)
:arrow_up:

...ient/datascience/jupyter/kernels/kernelSelector.ts
85% <0%> (+1%)
:arrow_up:

... and 5 more


sidebar - fix for some problems with sticky sub-submenu

@fichtner - sidebar - fix for some problems with sticky sub-submenu

#2873


Referenced track not found

After 62 chapters, I get:
Referenced QT chapter track not found
Stops processing m4bs correctly at that point.
Also the m4a cuts off at around 6 hours.

That error is from the file converter. Take a look here jostyee/AAXtoM4B .
Since i'm not maintaining the converters i will close this issue and recommend that you open it on jostyee's repo.

It could however been nice to be independent from the converter binaries and just use ffmpeg. If you want to give it at shot and implement it, that would be much appreciated.


python37Packages.qiskit-ibmq-provider: 0.6.1 -> 0.7.0

Semi-automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/python3.7-qiskit-ibmq-provider/versions.
meta.description for python37Packages.qiskit-ibmq-provider is: "Qiskit provider for accessing the quantum devices and simulators at IBMQ"
meta.homepage for python37Packages.qiskit-ibmq-provider is: "https://github.com/Qiskit/qiskit-ibmq-provider"
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

Warning: a test defined in passthru.tests did not pass

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

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

found 0.7.0 with grep in /nix/store/hjbnp9iawqn6dkiwixgz2zxl3hcqjxyg-python3.7-qiskit-ibmq-provider-0.7.0

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

du listing: https://gist.github.com/a5edea4d2f69c6e016ccdcc2e40eb134

Rebuild report (if merged into master) (click to expand)

10 total rebuild path(s)

3 package rebuild(s)

3 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
3 x86_64-darwin rebuild(s)
3 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
python37Packages.qasm2image
python37Packages.qiskit
python37Packages.qiskit-ibmq-provider

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/hjbnp9iawqn6dkiwixgz2zxl3hcqjxyg-python3.7-qiskit-ibmq-provider-0.7.0 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python37Packages.qiskit-ibmq-provider https://github.com/r-ryantm/nixpkgs/archive/aedacfbb00150d5fa6ad31b1d8702f29326f5380.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/hjbnp9iawqn6dkiwixgz2zxl3hcqjxyg-python3.7-qiskit-ibmq-provider-0.7.0
ls -la /nix/store/hjbnp9iawqn6dkiwixgz2zxl3hcqjxyg-python3.7-qiskit-ibmq-provider-0.7.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review 1

2 packages failed to build:
- python37Packages.qasm2image
- python37Packages.qiskit

1 package built:
- python37Packages.qiskit-ibmq-provider

Maintainer pings
cc @drewrisinger for testing.

Qiskit requires a specific version of this package, so it won't build yet.
I will post an update soon to the latest version of the Qiskit packages.
On Sat, May 9, 2020, 5:26 PM ofborg[bot]<EMAIL_ADDRESS>wrote:

@ofborg https://github.com/ofborg[bot] requested your review on: #87432
https://github.com/NixOS/nixpkgs/pull/87432
python37Packages.qiskit-ibmq-provider: 0.6.1 -> 0.7.0.
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/NixOS/nixpkgs/pull/87432#event-3319761062, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ACNZYI6WAUS3W42IRKSO6GTRQXDBHANCNFSM4M46VWZA
.


Add Toggle for SSH GitHub Fetch

Is your feature request related to a problem? Please describe.
Proper OpSec requires expiring OAuth tokens -> Expiring OAuth tokens means needing to update CMake toolchains entirely too often. Luckily, every GH Repo can be accessed via SSH (https://github.com/REPO -> git@github.com:REPO) which allows us to use our super-secret-ssh-key to access private repositories without the headache!
Seems that you've thought about this based on the comments, but no solution other than manual specification of the URL as an SSH URL is possible at this time. As there's a one-to-one with (default) HTTPS/SSH access to GH, it might make sense to enable this with a simple toggle
Describe the solution you'd like
Having an option (e.g. CMAIZE_GITHUB_USE_SSH) to switch to SSH GH access would be desireable. I've done this locally via addition of the following to CMaize/cmake/cmaize/package_managers/cmake/dependency/github.cmake after URL discovery:
if ( _bd_private AND CMAIZE_GITHUB_USE_SSH )
  string(REPLACE "github.com/" "${CMAIZE_GITHUB_SSH_PREFIX}:" _bd_url "${_bd_url}")
endif( )

where CMAIZE_GITHUB_SSH_PREFIX defaults to<EMAIL_ADDRESS>If this is a sufficient fix, I'll PR it, if there's more that would need to be done infrastructurally, this is meant to start the discussion.

Is the idea that you would be able to enable this CMAIZE_GITHUB_USE_SSH toggle from the command line (-DCMAIZE_GITHUB_USE_SSH=ON) or the toolchain file? I like that idea, since you don't have to modify every CMakeLists.txt file to use the SSH versions of the repo URLs anymore.
It would be awesome if you would get a PR started! As for the PR, CMAIZE_GITHUB_USE_SSH and CMAIZE_GITHUB_SSH_PREFIX should be defined and documented in cmake/cmaize/globals.cmake, which is in alphabetical order aside from the two project variables that are grouped together.

CLI vs Toolchain

I would expect these to have the same behaviour

PR + globals

Sounds good, I'll do that now


Implement SqlServer driver

Should be in the same setup as MySqlConnector example - separate NUNIT project

Currently blocked - not supported in SQLC itself.


Support koa2

Coverage remained the same at 80.392% when pulling ca9d3ee284394c95f001c655134490a020444707 on hopeness:patch-1 into 06bd0e9f20a8813143389b6e2896322e64513db9 on xtemplate:master.


streamlit issue

installed requirements

still stream lit is giving error.
I have used streamlit in my projects on my pc and it works.
@nithishr

Hi @aryanraj2713 ,
The issue from what you posted above seems to be that Tensorflow pinned version could not be found for your version of Python. And therefore the pip installation failed & streamlit could not be installed.
One option would be to install a newer version of tensorflow that works with your system & then update it in your requirements.txt file.

@nithishr

tensorflow is already present in my system and I have tried updating it

@nithishr heyy!!

@aryanraj2713
Could you share the output of pip freeze? The error that you posted initially is pointing to missing streamlit?
$pip freeze
Also what happens when you run one of the streamlit demos like this one for example in the same environment?
$streamlit hello

@aryanraj2713 Is your problem solved? Let me know if you still are facing issues.

@nithishr Still facing issues.
Result of pip freeze

Streamlit is also satisfied-

@aryanraj2713
Why is streamlit not shown in the output of pip freeze?
I believe that you have an issue where you have streamlit installed in some other environment not the one where you are running the demo.


Port aws-sdk-cpp has a non relocatable rpath, which becomes problematic when used with (remote) vcpkg binary caching

Describe the bug
aws-sdk-cpp sets CMAKE_INSTALL_RPATH_USE_LINK_PATH to true in its CMakeLists.txt file. The consequence is that when we install it with vcpkg (with a triplet that uses dynamic libraries, like the triplet x64-linux-dynamic described in the documentation), the RPATH of the installed libraries contains the full path where it was installed. This becomes problematic when the binary caching feature of vcpkg is used.
For instance, assume that I install aws-sdk-cpp with vcpkg in /home/klalumiere/Projects/vcpkg/. The library /home/klalumiere/Projects/vcpkg/installed/x64-linux-dynamic/lib/libaws-cpp-sdk-core.so now contains the RPATH /home/klalumiere/Projects/vcpkg/installed/x64-linux-dynamic/lib. If VCPKG_BINARY_SOURCES contains a Nuget server, vcpkg uploads the library on this server.
Now, my colleague, which use exactly the same "toolchain" as I do, also installs the library with vcpkg. vcpkg downloads the library from the Nuget server since it (correctly) determines that the "toolchains" (the hash) are the same. However, my colleague now has a library with a RPATH that doesn't exist on its machine. Moreover, the library is unlikely to work because it won't found its dependencies (e.g. libcurl.so).
Environment

OS: Ubuntu 20.04.1 LTS
Compiler: clang version 10.0.0-4ubuntu1

To Reproduce
Steps to reproduce the behavior:

./vcpkg install aws-sdk-cpp:x64-linux-dynamic --overlay-triplets=../vcpkg-overlays/triplets
objdump -x installed/x64-linux-dynamic/lib/libaws-cpp-sdk-core.so | grep PATH
A RUNPATH particular to your machine is observed.

Expected behavior
RUNPATH should be $ORIGIN, which is relocatable. I'll submit a pull request in a few minutes that fix the issue.

@klalumiere, thanks for reporting this issue! and very appreciate for your contribution!


Apply #195 + suggested fixes

This PR applies #195 and applies the suggested fixes.

@charleskawczynski is this PR still planned?

Ah, yes, we should revive this if insolation hasn’t been updated yet. I’ll see if I can rebase tomorrow

Ah, yes, we should revive this if insolation hasn’t been updated yet. I’ll see if I can rebase tomorrow

no rush! just doing a little housekeeping over here :)

@charleskawczynski Is it okay to close this PR? I'm not sure what the suggested fixes in addition to #195 are

@charleskawczynski is this something you would like me to finish (do we still need it?)

superseded by #407


Support Cash Game Option

Idea is to have a cash game option where:

Players can sit down and stand up whenever they want
Includes a rake
Includes a timeout option where the current player has to fold if no action is given
Register AIs

Idea: Have a Table Class in furtherance of this abstraction

Hello, I'd like to potentially work on this.
If you could give me a high level pointer to where the abstraction fits amongst the others I can take it from there.
Cheers!

Hey @logicdotpy! Yeah that would be great if you could take a look at this! Here's my thoughts:
The main idea I think is that the Table class can wrap around the TexasHoldEm class and provide "thread-safe" access to the methods and attributes. For instance, we can call Table.unregister(player_id) at any time but the Table class will handle that smartly by first, making the next action of the player to be FOLD and then there's probably some logic here to make the TexasHoldEm class not put that seat back in. Similarly, for Table.register.
I put "thread-safe" in quotes here first because it's a lot like a locking mechanism but also second we should be able to pass in a time limit in the constructor. If there's a time-limit, there's probably a need for threading, but otherwise we should not be making new threads.
We can also keep a players dictionary that maps agents to player_ids so that the actions are taken automatically when it's a player's turn.
Let me know what you think! We can worry about integrating with the History and the TextGUI later and I can share more about the testing setup if you have questions.

In fact, I think we can split off the timeout option as a second phase for this. That probably makes this a bit better to work with

Let me ask actually... do you think it makes sense to have the register / unregister functionality in the TexasHoldEm class or this new Table class? I can see the point where we have a flag in the constructor cash_game=True which enables that functionality.


Add prisma-markdown and change typia

New library prisma-markdown, and change typia content to announce protobuf features.

Wow, prisma-markdown with mermaid diagrams is so cool.
Thank you for sharing @samchon


FIX: Eyelink not able to get position for right eye

We have not been able to use the right eye for any tracking until I found what looks to be missing parentheses.
Is this just a fix for us?

@rkmaddox @drammock @larsoner
I'm so confused but having changed this we can use el.get_eye_position() when tracking the right eye (whereas we couldn't before and spent a decent amount of time trying to figure out why).

Yep, that should fix it. The problem is that without the parentheses, sample.isLeftSample is a function, not the returned value of the function. A function != 0, and anything that is non-zero evaluates to true. So it always tried to get the left eye position.

Ouch, I think that was my bad from way back when


Projectcounter

Need entry for the cron in the config.yml and also need the corresponding item/trigger in openshift-ansible.
4-6 hours for the cron seems sufficient for our needs at the moment.  Trigger should be informational and report if there are no projects.


for Unauthorized send 401 and for wrong authentication send 403

Fix for TJWS embedded server.

Currently for wrong authentication  returns 401 and for no Basic auth details returns 405. Which is not correct.

This fix will return 403 for wrong authentication and 401 for no Basic auth details on request.

Hi Jeeva,

I don't see why it would be incorrect to send 401. RFC2616 (https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html) says:

If the request already included Authorization credentials, then the 401 response indicates that authorization has been refused for those credentials.

whereas for 403 it says

Authorization will not help and the request SHOULD NOT be repeated.

So I think 401 makes sense here.

I think you're right that, in the absence of an Authorization header, or in the presence of an Authorization header that is not a request for BASIC authorization, 401 should be returned.

Have you looked at the test failures in the resteasy-jaxrs module:

Failed tests:
BasicAuthTest.testProxyFailure:200 expected:<401> but was:<403>
BasicAuthTest.testSecurity:246 expected:<403> but was:<401>
BasicAuthTest.testSecurityFailure:286 expected:<403> but was:<401>
These need to be dealt with.
Thanks,
Ron

Given Ron's comment above (and no response to him) and considering we're working on actually removing the TJWS embedded server from RESTEasy, I'm closing this PR:


Binder link is broken

sigh I'm not sure what's going on here and I don't have time to fix!
Any help very welcome!

I think it is a nice place to discuss Binder :smiley:
Building the environment needed to run the repository failed. So my 1st guess was that smth was wrong with dependencies or its versions. I manually tried to build Binder repository, and according to logs - Failed building wheel for numpy; Failed to build numpy;
Then I tried to indicate the numpy version (numpy==1.16.2) in setup.py and requirements.txt files, but building process still failed :disappointed:
I asked the question in Binder community chat, and...well I will just paste the answer from @minrk:
"It's the pinning of pandas that's the problem.
Pandas is pinned to <=0.22, which doesn't have a wheel for Python 3.7. Pandas then requires an old numpy as a build dependency, so to build pandas from source, it needs an old numpy. This, in turn, builds an old numpy from source, which doesn't work because the chosen version of numpy doesn't work with Python 3.7.
General guideline if you want an environment to last, especially if it involves compiled packages: if you pin down (i.e. ==or <=), also pin the Python version.
If you want to follow latest Python, make sure to let packages also float so they can keep up with the changes they need to work with Python upgrades.
This approach isn't so much a "reproducible environment" as a "living environment""
As suggested in the answer, I unpinned pandas (made just "pandas" in setup.py and "pandas" in requirements.txt ), pinned the Python version (python-3.6) in runtime.txt and building Binder repo failed again :disappointed:  with the error message "No module named 'sklearn'"
So I added module scikit-learn to setup.py and requirements.txt files, and voila!!! it works :rocket: :sparkles:
@KirstieJane do you want me to make a PR with all these changes I made to my forked repo?

Woooo! Fantastic! Yes - please do open a PR!
The only other addition is to add seaborn because we're going to need that for the figures 😸
Are you sure we need to pin to python-3.6 if we have unpinned pandas?
Thank you @wingedRuslan!! Great sleuthing 🔎

:relaxed:  Sure, I will open a PR

Are you sure we need to pin to python-3.6 if we have unpinned pandas?

Well, I will try to build Binder repo without pinning to python-3.6, and then tell you whether or not it is needed to indicate python version or not :smile:

The only other addition is to add seaborn because we're going to need that for the figures

seaborn is already included in setup.py and requirements.txt files

I have made my PR!
@KirstieJane you were right, pinning to python-3.6 was unnecessary(successfully built Binder without it). So I did not include this change in PR


Add podTemplate Volume to allow to persist .m2/repository for maven build

The existing template which is used to generate the podTemplate from an imagestream
# convert_is_to_slave converts the OpenShift imagestream to a Jenkins Kubernetes
# Plugin slave configuration.
function convert_is_to_slave() {
  [ -z "$oc_cmd" ] && return
  local name=$1
  local template_file=$(mktemp)
  local template="
  <org.csanchez.jenkins.plugins.kubernetes.PodTemplate>
    <inheritFrom></inheritFrom>
    <name>{{.metadata.name}}</name>
    <instanceCap>5</instanceCap>
    <idleMinutes>0</idleMinutes>
    <label>{{if not .metadata.annotations}}${name}{{else}}{{if index .metadata.annotations \"slave-label\"}}{{index .metadata.annotations \"slave-label\"}}{{else}}${name}{{end}}{{end}}</label>
    <serviceAccount>${oc_serviceaccount_name}</serviceAccount>
    <nodeSelector></nodeSelector>
    <volumes/>
    <containers>
      <org.csanchez.jenkins.plugins.kubernetes.ContainerTemplate>
        <name>jnlp</name>
        <image>{{.status.dockerImageRepository}}</image>
        <privileged>false</privileged>
        <alwaysPullImage>false</alwaysPullImage>
        <workingDir>/tmp</workingDir>
        <command></command>
        <args>\${computer.jnlpmac} \${computer.name}</args>
        <ttyEnabled>false</ttyEnabled>
        <resourceRequestCpu></resourceRequestCpu>
        <resourceRequestMemory></resourceRequestMemory>
        <resourceLimitCpu></resourceLimitCpu>
        <resourceLimitMemory></resourceLimitMemory>
        <envVars/>
      </org.csanchez.jenkins.plugins.kubernetes.ContainerTemplate>
    </containers>
    <envVars/>
    <annotations/>
    <imagePullSecrets/>
    <nodeProperties/>
  </org.csanchez.jenkins.plugins.kubernetes.PodTemplate>
  "
  echo "${template}" > ${template_file}
  $oc_cmd get -n "${PROJECT_NAME}" is/${name} -o templatefile --template ${template_file}
  rm -f ${template_file} &>/dev/null
}

doesn't allow to mount a volume to by example persist the .m2/repository used by the pod to build a maven project
Proposition is to add a PersistentVolumeClaim using as parameter the claimName and mounthPath
 <volumes>
            <org.csanchez.jenkins.plugins.kubernetes.volumes.PersistentVolumeClaim>
              <mountPath>/home/jenkins/.m2</mountPath>
              <claimName>jenkins-maven</claimName>
              <readOnly>false</readOnly>
            </org.csanchez.jenkins.plugins.kubernetes.volumes.PersistentVolumeClaim>
 </volumes>

I don't think we want to make that change since it would require users have a free PV available to claim.
For now users are free to modify the slave configuration in their jenkins server after standing it up (or providing their own configuration via an s2i build of a new jenkins image, and run that jenkins image instead).
We are also working on a new feature this sprint to allow users to provide slave configuration via a ConfigMap object, so you could define your "PVC-enabled" maven slave definition via that mechanism.
But i don't think we want to hardcode the behavior in this way.  Sound reasonable?
@oatmealraisin fyi

Also this change would require the user define a PVC w/ that name in their project, right?  that is also likely to trip people up.

Sound reasonable?

This is reasonable

PVC w/ that name in their project,

I agree with you that this approach will bring more complexity.

Thanks, closing this issue, the feature for better configuration of slaves is being tracked here:
https://trello.com/c/hS9lzo1v

better configuration

Is there something already available that we could use as for the moment we are stuck to fork the jenkins 2 centos image and override the PodTemplate to pass the volume definition
<volumes>
            <org.csanchez.jenkins.plugins.kubernetes.volumes.PersistentVolumeClaim>
              <mountPath>/home/jenkins/.m2</mountPath>
              <claimName>jenkins-maven</claimName>
              <readOnly>false</readOnly>
            </org.csanchez.jenkins.plugins.kubernetes.volumes.PersistentVolumeClaim>
 </volumes>

As, since OCP 1.6 we can pass ENV vars from the BuildConfig, we could override the existing script to pass 2 keys that we could test within the shell script to include a volume -- make sense ?
env:
  - name: mountPath
    value: /home/jenkins/.m2
  - name: claimName
     value: jenkins-maven

Is there something already available that we could use as for the moment we are stuck to fork the jenkins 2 centos image and override the PodTemplate to pass the volume definition

i'm not sure i'd call that a fork, it's more like extending the existing image w/ a new layer that contains your customized slave-config script (or just provide your hardcoded jenkins config files w/ the right slave definitions in your customized image).
another option would be to mount your config into the jenkins pod from a PV.
But otherwise no, there's nothing at the moment that you can do to use the existing jenkins image, as is, but get the pod template configuration you want.

As, since OCP 1.6 we can pass ENV vars from the BuildConfig, we could override the existing script to pass 2 keys that we could test within the shell script to include a volume -- make sense ?

no i'm afraid i don't understand the suggestion.  The shell script that generates the slave pod template configuration is independent of (and has no access to) your buildconfig definitions.  When you provide env variables in your buildconfig, they are made available to the associated pipeline in general, not to a slave pod specifically.


[Question] How to config with dynamic routes?

I have a website with regular routes and dynamic routes also. I was able to generate the sitemap file successfully, however, for the dynamic routes I got the following output:
</url><url><loc>https://mydomain/route/[id]</loc>

Expected
</url><url><loc>https://mydomain/route/param</loc>

An example of how to dynamically generate this would be great.

You should use getStaticPaths for this to work, then the pages will be there after building and nextjs-sitemap-generator will know about it.


Broken link in documentation

Link to "DC/OS Usage docs" in https://github.com/dcos/dcos-vagrant/README.md leads to a 404 error (The page you're looking for can't be found.).
I guess the correct link is https://dcos.io/docs/1.7/usage/

Not sure what you mean...
The link to https://dcos.io/docs/latest/usage/ is redirected to https://dcos.io/docs/1.7/usage/
Are you looking at docs for an old version of dcos-vagrant?

yep.
Checked again and now it works. Thanks for support


*: add torcx download root

This adds the necessary variables for uploading and downloading torcx
packages at various points, as well as for setting the download root
users will be able to access packages at.
i've attempted to include correct configurations for nightlies and all
channels.
This change should have no effect until https://github.com/coreos/scripts/pull/737 is merged

@dm0- updated; most of those were on the branch I was actually doing trial runs with, but forgot to re-push here


"Import is already running."

Describe the bug
I followed the deployment guide on the web, and all seemed ok, but about 24 hours ago discovery abruptly began failing on all my target accounts. The error message is cryptic but reasonably descriptive:
{
"message": "Stopping import as import is already running.",
"level": "info",
"timestamp": "2021-09-23T15:16:25.503Z"
}
Deleting and re-importing the accounts and regions did not help.
This seems to stop the discovery process cold. I don't know what caused it, so I'm not sure how to reproduce it.
This happens across multiple browsers; I don't believe it's browser-related.
aws-perspective-error-log.txt
I'm just getting started with Perspective, so if the answer is "tear it down and do it again," that's ok.

When you go into ECS console is there a task still running? The discovery process does a check at the start and won't run if another one is still in progress. Also, can you give me a rough idea how many resources are in these accounts? Did any resources get discovered?

When I look at the cluster in the ECS console, there is one fargate task running, but it started this morning at 8:30.
I was successful in discovering maybe 1500 resources. I only tried to discover resources from a couple of target accounts.
I'm sure I interrupted some running process, I'm just not sure what.

Did you add any new accounts just before it stopped working? The reason I ask is that we have seen issues with rate limiting from AWS Config if you add multiple accounts at the same time. It seems to be that if Perspective tries to add around ~3000 resources all at once, the rate limiting kicks in.

I may have; I added one new account but am not sure of the exact time.

I am almost sure it's this issue, can you remove the last account you added and kill the ECS task and then see if it runs again. Don't uninstall any of the CloudFormation you installed, i.e., global-resources.template and regional-resources.template, just remove the account from the UI in Perspective.

OK, I removed the account and stopped the task. It's moved to "pending" now.

Same error message.

Are there errors in the logs for the ECS task that is running or has it just hung?

The ecs task is running, but the only log entry is identical to the one I originally supplied above. I'm not sure which check for something already running is failing.

Ah sorry, I thought there was a task that was running that was working and other ones were failing with that error. So are you saying that the task has that error but continues to run? I've not seen this before, the discovery process makes a call to the ECS listTasks to see if any other tasks are running and fails if there's already a copy running. I don't understand how this check is getting trigger if the task producing the error is the only one running. What outputdo you get if you run the follwoing cli command:
aws ecs list-tasks --cluster aws-perspective-<acoount-number>-cluster

$ aws ecs list-tasks --cluster aws-perspective-300128025978-cluster
{
"taskArns": [
"arn:aws:ecs:us-east-1:300128025978:task/aws-perspective-300128025978-cluster/4c15c0cd0e2845f7831041450ad0842f",
"arn:aws:ecs:us-east-1:300128025978:task/aws-perspective-300128025978-cluster/760ea23e97054676ae8dd79067f32a5f"
]
}
So there do appear to be two tasks running.

Maybe just go into the ECS console and click Stop All, that should get any.

Also, if you alter the task definition to add an environment variable called LOG_LEVEL and set it to DEBUG we can get more info the next time it runs.

I stopped all, but it only reported on stopping the second one.

So is the other one still running? Maybe try to kill them using the cli?

So both tasks ended up getting stopped. The restarted task ran successfully (as far as I can tell; the "last scanned" column in the web UI region list remains "N/A") at 11:45 and 12:00.
However, the 12:15 run reverted to the same error message, though there is only one task running according to the cli.
I was not at the computer then, so I know I didn't change any of the parameters. :-)

This is very strange, what region are you running Perspective in?

us-east-1

OK. I deleted the entire stack (which left the ecs task provisioned, just so you know -- you have to deregister the old one after you reinstall and a new task is defined), reinstalled it, and tried to add discovery for resources from three AWS accounts. That failed after a few discovery cycles; it seems that the throttling phenomenon you suspected was on the mark.
I killed all the running ECS tasks, removed the regions from all but one AWS account, and the next discovery ran without reporting errors in cloudwatch.
It was our sandbox account, without that many resources (337). If that runs successfully the rest of today, I'll add one more account and see what happens there.

Yeah, ~300 resources is fine, I normally test in an account with ~2k, it's when you get to the double that that this throttlling stuff seems to happen.

If that number of resources is fine, then there is some problem with state management or error handling.
This just happened this morning. I cleaned things up, killed running tasks, etc. The first discovery after I did that interrogated one account for two regions. The region with (many) fewer resources finished successfully after about three minutes:
{
"level": "info",
"message": "<<<<<<<<<< import of config complete for account:<PHONE_NUMBER>88 region: us-east-2 finished!",
"timestamp": "2021-09-28T13:48:55.060Z"
}
The region with the bulk of the resources threw a few errors like this:
"(node:1) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 7)"
"(node:1) UnhandledPromiseRejectionWarning: TypeError [ERR_INVALID_ARG_TYPE]: The first argument must be of type string or an instance of Buffer, ArrayBuffer, or Array or an Array-like Object. Received undefined"
resulting in
{
"level": "error",
"message": "Error Message: You have specified a resource that is either unknown or has not been discovered.",
"timestamp": "2021-09-28T13:48:51.890Z"
}
and then goes off into never-never land.
That task is still running, and nothing else runs while it is.

After some time, you just get a stream of error messages:
{
"level": "error",
"message": "Error Message: The security token included in the request is expired",
"timestamp": "2021-09-28T15:13:37.497Z"
}
maybe once every 45 seconds to a minute.

Finally, after about two hours, the first region completes:
{
"level": "info",
"message": "<<<<<<<<<< import of config complete for account:<PHONE_NUMBER>88 region: us-east-1 finished!",
"timestamp": "2021-09-28T15:46:55.303Z"
}
It then attempts to go off and process data from other accounts -- even though I removed them from the discovered regions using the Web UI -- removes them from the ElasticSearch store, and finishes about 15 minutes later.
The discovery process eventually recovers, in the sense that another task starts running. I guess it's working, in that the lengthy discovery processes eventually complete with (at this moment) 854 unique resources -- including resources that don't belong to the account being discovered. I guess the discovery process didn't remove them from the database?

There's still something weird going on here, it shouldn't take 2 hours to discover 850 resources. Regarding the other accounts that have been removed in the UI, I wonder are there still resources hanging around in the Config Aggregator (it will be called aws-perspective-<region>-<account-no>-aggregator). Can you check in the Config console and see if it still has the other accounts, maybe the call to Config to remove them failed.

Yes, the aggregator "knows" about three accounts and it's going off and trying to update resources in a ton of regions: me-south-1, eu-west-3, us-west-1, etc. I have no idea why it's trying those regions.

So, looking at the cfn that sets up the aggregator in the account where Perspective lives(https://github.com/awslabs/aws-perspective/blob/8a75b2e5314f57a22556df51b5dd9191574e68b3/source/cfn/templates/zoom-import-and-aggregator.yaml#L18), it looks like the AllRegions option is enabled but that doesn't explain why it's enabled for the other accounts. It should only affect the Perspective account.

If you edit the aggregator to remove the extra regions that should definitely help with the throttling, especially if you've a bunch of resources in those other regions you don't care about. Also, we can look at changing that cfn template to only use the region Perspective is installed in initially.

I rebuilt with only one account, two regions, removed the rest of the unused regions from the aggregator, and a discovery import now takes about 30-45 minutes to discover approximately 350 resources.
I get a ton of error messages from the task that look like
{
"level": "error",
"message": "Error linking 9b140fac7eab812d19be7a6b312938ee to e045b5fa500e03bbc628012018710c2e with label AWS::TAGS::TAG",
"timestamp": "2021-09-29T16:38:03.723Z"
}
so that might be extending the time it takes.

Can you grab the whole logs for that discovery task that took 30-45 mins and attach them here, maybe something might jump out at me. You'll probably have to get them direct from the CloudWatch Logs console rather than the ECS one.

It ran from 12:01:16 to 12:38:07. Is there an easy way to download all events from that one log stream?
There are 3900 events in less than a minute of elapsed time, and I got tired of hitting "load newer events".

Might be easier to just use the cli, that will give you 10k events in one go:
https://docs.aws.amazon.com/cli/latest/reference/logs/get-log-events.html

OK, I'll look at that.

Here's pretty much all of the log output for that task run.
log-output.txt

Thank you! I'll get digging.

I appreciate your help with this. Believe me that I understand the difficulty with this kind of remote debugging.

@svozza we have exactly same issue like @JamesWilson19947 I opened ticket https://github.com/awslabs/aws-perspective/issues/285 for it

This issue is a scaling limitation with v1.1.0 as the discovery process made an API call to AWS Config for every resource it found. For regions with ~2500 resources, this meant Config would start applying rate limiting to these calls and eventually the whole discovery process would hang and not complete. We have addressed this issue in version v2.0.0 and now make far fewer calls to Config when discovering resources. This new version was released today, and the 2500 resource limit no longer applies.


Database days hot fix

Add/read day and date to/from database.
Adapt UI to accommodate slots increase.

@all-contributors add @Thesmader for Code, Project Management, Maintenance


BVAL-502

Supersedes https://github.com/beanvalidation/beanvalidation-spec/pull/96 by @Sanne, @Davide and @Gunnar.
Fixed a few conversion errors and did a global proofreading of the spec while I was at it.

@gsmet Your changes are good, I've added only some few remarks. Once you've addressed those, it's good to merge. Yippie :)

Merged \o/. Thanks to all!


Zone support

Does ASE V3 support availability zones, and if so is is it zonal or zone redundant?

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

ID: 39980d7c-2702-a924-6412-a0ec40d719c8
Version Independent ID: 613452e8-c5b8-37e7-a8b6-2f5284f208c8
Content: Create an App Service Environment - Azure App Service Environment
Content Source: articles/app-service/environment/creation.md
Service: app-service
GitHub Login: @ccompy
Microsoft Alias: ccompy

Thanks for the feedback! We are currently investigating and will update you shortly.

Hi @hbuckle , ASE V3 will have availability zone support at GA. The ASE has to be provisioned to be zone redundant. There are more details around this feature which will be covered in this doc in the near future.
We will close this out, but if you feel you need more information please just let us know.


rule idea: detect DES constants

Add detection for DES constants: https://en.wikipedia.org/wiki/DES_supplementary_material#Initial_permutation_.28IP.29
Source example: https://github.com/mimoo/DES/blob/master/src/DES.c#L17

closed via https://github.com/fireeye/capa-rules/pull/56


task: regenerate mocks

Proposed changes
While generating a new mock a mock for live migration as also generated, this means we had a fake livemigration not generated by the tooling, regenerating all mocks just in case
Checklist

[x] I have added tests that prove my fix is effective or that my feature works
[x] I have added any necessary documentation (if appropriate)
[x] I have addressed the @mongodb/docs-cloud-team comments (if appropriate)
[x] I have updated e2e/E2E-TESTS.md (if an e2e test has been added)
[x] I have run make fmt and formatted my code

what causes the incorrect mock to be generated in the first place (how can we avoid it happening again in the future?)

We add something like this (actual culprit here) to interfaces we want to mock
//go:generate mockgen -destination=../mocks/mock_live_migration_validations.go -package=mocks github.com/mongodb/mongocli/internal/store LiveMigrationValidationsCreator,LiveMigrationCutoverCreator,LiveMigrationValidationsDescriber

My guess, somebody changed the output file on that command and forgot to regenerate the mocks since no test will fail as long as the mocks are the same
to not happen again maybe add a CI check to generate mocks and fail if any diff


Outputs: Site labour/time on site and windshield time

Should we include another output in LDAR-Sim that breaks down total LDAR time into two components? The first would be windshield time/travel time between sites and the second would be labour time/actual time spent on site doing screenings and surveys. While cost wouldn't be included here, this is related to economics in LDAR-Sim, as some firms may want to use this information to optimize scheduling or improve on-site times if there are inefficiencies. Health and safety managers may also want to see the ratio that their employees are subject to and use the information in hazard assessments.
@tarcadius @tbarchyn @KeeganShaw-GIS @AkaMrmuffin @tybob-gough

Both Travel times, and onsite time are now calculated in the plan_visit function of mobile crews.  It would be a matter of moving them into either state or timeseries variables.


Package phpoffice/phpexcel is abandoned,

I got this error When I am trying to install this package on Yii 2.0.15
Package phpoffice/phpexcel is abandoned, you should avoid using it. Use phpoffice/phpspreadsheet instead.

Thank you
Khadijah Shtayat  http://people.bayt.com/khadijah-shtayat/
Location
Dir
Profile Amman, Jordan
+962.7.906.77436
jo.linkedin.com/pub/khadijah-shtayat/b/79b/b6/
One ton of office paper uses 24 trees. Please don't print this email
unless you need to.
On Fri, Oct 26, 2018 at 11:26 PM Moh Khoirul Anam<EMAIL_ADDRESS>wrote:

sorry for long time i am not resolve this issue, but i don't have time
before.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/moonlandsoft/yii2-phpexcel/issues/29#issuecomment-433547985,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACPlD4EY1SRwxUtE3BinYIRs5AV5JQ7sks5uo335gaJpZM4WN4KQ
.

Thank you for this update. Will there be a release with this change? The current stable version, 1.1.0, doesn't reflect the change.


MKLDNN int8 support

MKLDNN 0.17 release states that it supports int8 quantization (https://github.com/intel/mkl-dnn/releases). However, we run into the following issue when we comment out this line
mxnet.base.MXNetError: [15:57:38] src/operator/nn/mkldnn/mkldnn_convolution.cc:140: Check failed: conv_pd.next_impl() No implementation

To reach this, I had to comment out this line of code:
(https://github.com/apache/incubator-mxnet/blob/5111b187e3d8917d45a2482ceaf44b42588eff51/src/operator/subgraph/mkldnn/mkldnn_conv.cc#L346).
For Q & A and discussion, please start a discussion thread at https://discuss.mxnet.io
Description
(Brief description of the problem in no more than 2 sentences.)
Environment info (Required)
What to do:
1. Download the diagnosis script from https://raw.githubusercontent.com/apache/incubator-mxnet/master/tools/diagnose.py
2. Run the script using `python diagnose.py` and paste its output here.

Package used (Python/R/Scala/Julia):
(I'm using ...)
For Scala user, please provide:

Java version: (java -version)
Maven version: (mvn -version)
Scala runtime if applicable: (scala -version)

For R user, please provide R sessionInfo():
Build info (Required if built from source)
Compiler (gcc/clang/mingw/visual studio):
MXNet commit hash:
(Paste the output of git rev-parse HEAD here.)
Build config:
(Paste the content of config.mk, or the build command.)
Error Message:
(Paste the complete error message, including stack trace.)
Minimum reproducible example
(If you are using your own code, please provide a short script that reproduces the error. Otherwise, please provide link to the existing example.)
Steps to reproduce
(Paste the commands you ran that produced the error.)

Pending

@azai91 Thanks for raising the issues.
We already have the implementations in local and will PR soon (just wait a moment for r1.4 cut before).
@ZhennanQin

@azai91 we need more validation with the real workload since the int8 network is not too much in the hand.

Corresponding PR is filed at: https://github.com/apache/incubator-mxnet/pull/13697

#13697 is merged. Closing this issue now.


Is it possible to do iterative training? Load the weight and retrain on new data.

Instead of loading entire training data, can I train the model on part of it, load the weights and retrain the data?

@vinay-k12, I am closing this as inactive. If you've managed to make the iterative training work for you, I'd love to learn more! Thank you. :)


Cannot inspect any strings

OS: Debian 11 (bullseye)
VSCode version:  1.54.1
Extension version: 1.6.1
Compiler: Clang 11.0
Build target: x86_64  gnu++14 (clang11.0 default)
When trying to inspect a string, it reports "error: summary string parsing error".  I get the same from hover tips, the watch window, and doing p <variableName> in the debugger window.
If I issue the command type summary delete std::string --category cplusplus in the debugger window, then strings start displaying correctly again.

Which stdlib are you using?   (GNU libstdc++ or LLVM libc++)

GNU libstdc++
ldd a.out|grep -F c++
        libstdc++.so.6 => /lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007f98b37db000)

$ apt search "libstdc++"|grep installed

libstdc++-10-dev/testing,now 10.2.1-6 amd64 [installed,automatic]
libstdc++6/testing,now 10.2.1-6 amd64 [installed]

Hit the same problem myself after switching to clang.  This seems to be relevant: https://bugzilla.redhat.com/show_bug.cgi?id=1740927.  Basically, you need to either install a debug version of libstdc++, or compile with -fstandalone-debug flag.  The latter worked for me.

I think that is a different bug.  The error when inspecting a string in that bug report is...
error: incomplete type 'std::string' (aka 'std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >') where a complete type is required
forward declaration of 'std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >'

Whereas the error I am getting is...
error: summary string parsing error
It seems in my case the summary parser that is installed by default is not working correctly.  By removing the string summary parser using the command "type summary delete std::string --category cplusplus" I can view strings again.

This is now even more broken in 1.6.2.  I used to be able to issue the command "type summary delete std::string --category cplusplus" which would allow me to see strings again.  However in 1.6.2 when I do this, all the strings get reported as blank.
With 1.6.1...
p test1
(std::string) $0 = error: summary string parsing error
p test2
(std::string) $1 = error: summary string parsing error
type summary delete std::string --category cplusplus
p test1
(std::string) $2 = "short"
p test2
(std::string) $3 = "reallyreallyreallyreallyreallyreallylongstring"

With 1.6.2...
p test1
(std::string) $0 = error: summary string parsing error
p test2
(std::string) $1 = error: summary string parsing error
type summary delete std::string --category cplusplus
p test1
(std::string) $2 = {}
p test2
(std::string) $3 = {}

I think that is a different bug.

I believe the cause is the same.  Have you tried compiling with -fstandalone-debug?

Compile what? My program or libstdc++ ?

Your program.

I can confirm that compiling with -fstandalone-debug fixes the issue.  Thanks.

Unfortunately, this is still happening on Windows with cl or clang-cl, -fstandalone-debug doesn't work.


High Availibility Mode (Issue 13)

issue 13.
This is a start. I may have missed edge cases and when/if the Shutdown work I did gets pushed to the main repo it will need updated aligned with this code.
Also I would have preferred to use Google's Service but the out of date guava jars that hadoop is using was getting in the way.

May be I missed something, but my impression was that the main idea of issue #13 was to recover state.
Usually full HA consists of 3 parts:

Failover
Discoverability
State recovery

I would imagine that Failover of MyriadDriver (not sure though) as well as RM (pretty sure) will/should be done by Mesos. Discoverability again should be done by Mesos.
"State Recovery" needs to be addressed and it is what issue #13 is about.

As I said this is only a start, in general I agree, but a few questions.
How will the MyriadDriver know to recover its state if it does not know
that it should? That it is now the leader?
Reconciliation is being worked and when its complete, or ready, it can be
added to the mix. Shutdown will have to added as well.
On Tue, Apr 28, 2015 at 8:10 PM, Yuliya Feldman<EMAIL_ADDRESS>wrote:

May be I missed something, but my impression was that the main idea of
issue #13 https://github.com/mesos/myriad/issues/13 was to recover
state.
Usually full HA consists of 3 parts:

Failover
Discoverability
State recovery

I would imagine that Failover of MyriadDriver (not sure though) as well as
RM (pretty sure) will/should be done by Mesos. Discoverability again should
be done by Mesos.
"State Recovery" needs to be addressed and it is what issue #13
https://github.com/mesos/myriad/issues/13 is about.
—
Reply to this email directly or view it on GitHub
https://github.com/mesos/myriad/pull/94#issuecomment-97269793.

Closing for now, adding state recovery and reconciliation. [PR #94] (https://github.com/mesos/myriad/pull/94), [issue #13] (https://github.com/mesos/myriad/issues/13)


V support

Check for existing issues

[X] Completed

Language
V
Tree Sitter parser link
https://github.com/vlang/vls/tree/master/tree_sitter_v
Language server link
https://github.com/vlang/vls
Misc notes
No response

This would be very easy to add, since I assume you are using tree sitter. It would be great to see V support


The data isn't all there

On the website link provided, most of the information is not there to load.

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

ID: 7bf2015c-41fe-8234-dd4d-698e589b6fc7
Version Independent ID: bc0deeb1-04c7-abc3-b26c-10ea6d75c57f
Content: Getting started with Power BI Desktop - Power BI
Content Source: powerbi-docs/desktop-getting-started.md
Service: powerbi
Sub-service: powerbi-desktop
GitHub Login: @davidiseminger
Microsoft Alias: davidi

Thanks for your comment, @rebecca-aaas . I've assigned your issue to the doc author for review. In the meantime, can you tell us specifically which website link you are referring to that page? Thanks.

https://www.bankrate.com/finance/retirement/best-places-retire-how-state-ranks.aspx

We've updated the doc to reflect changes in that table. Sorry for the inconvenience.


Dht bit manipulation improvment

We now use go's math/bits lib to calculate the leading zeros of the id's in the dht.
The new function is faster and more readable.
added some tests to make sure everything works well.

thanks, travis is happy you can merge now :)


Possible bug: Datageneration from custom function inspects function signature.

When playing around with this example in the documentation: https://f3dasm.readthedocs.io/en/latest/auto_examples/003_datageneration/001_own_datagenerator.html#car-stopping-distance-problem
If you change the custom function to
def y(x2):
    z = norm.rvs(1.5, 0.5, size=1)
    y = z*x2 + 0.1*x2**2
    return y

You get that the experiment samples not have the status of error after executing experiment_data.evaluate(data_generator=y, output_names=['y']), getting
File "/Users/eaguerov/mambaforge/envs/3dasm/lib/python3.10/site-packages/f3dasm/_src/experimentdata/experimentsample.py", line 161, in get
    value, from_disk = self._load_from_experimentdata(item)
TypeError: cannot unpack non-iterable NoneType object

This is because we changed the signature of y(x) to y(x2), which does not coincide with the input name on the domain of the experimentdata object.
I personally could understand why this behavior might be desirable, but I believe that the consequences of the current implementation are that you cannot generate basically anything that was not typed out manually by the user.
If you train a model, and want to test the predictions of the model on some input data, you simply cannot do data_generator=my_model, unless the my_model variable has the exact signature of the input features that the experimentData Domain has. This is cumbersome for problems with 10+ input features.
I do not have an explicit solution in mind, I just wanted to share my thoughts with the developers so that a scalable solution is devised.

Just for the record, I noticed that this is also discussed in #268. I will keep this issue because I believe I believe this topic needs more discussion


Migrate current integration tests to pytest

Describe the feature
In order to mirror the approach of dbt core as well as the rest of the package ecosystem, we should consider moving our test suite to pytest. This also gives us more flexibility to add test scenarios without having to maintain multiple dbt projects with specific characteristics of interest (i.e. integration_tests vs integration_tests_2)
Describe alternatives you've considered
Continuing to use nested dbt projects
Who will this benefit?
Developers and maintainers!
Are you interested in contributing this feature?
Certainly part of it!

@dave-connors-3 , do you have a list of repos that use pytest today instead of an integration_tests project? dbt-core is doing it but I checked quickly dbt-utils and it looks like it hasn't moved to pytest yet (and personally that would be the one I would try to replicate from)

utils should have some, but these may just be ported over from core as they migrated the cross db utils.
Metrics also has pytest based testing

We should still do this!