Using fonts with a more freedomrespecting license

Hi there,
thanks for asciidoctor-fopub.
Im running Debian and there the following asciidoc source sample.adoc
= Document Title

== Testing

* item 1
** item 2
*** item 3
**** item 4
***** item 5

when run through
asciidoctor -b docbook -d book -a data-uri! sample.adoc
fopub sample.xml

gives the following warnings:
WARNING: Glyph "◦" (0x25e6, openbullet) not available in font "Helvetica".
[...]
WARNING: Glyph "▪" (0x25aa, H18543) not available in font "Helvetica".

and renders characters ◦ and ▪ with a # in the pdf... more-or-less like this:
  • item 1
     # item 2
        # item 3
           • item 4
              # item 5

Solution using (somewhat restrictive) Microsoft fonts
I've figure out a way of solving this, but it involves using some Microsoft fonts from here http://sourceforge.net/projects/corefonts/
These somewhat restrictive fonts can be used in Debian, by installing ttf-mscorefonts-installer, like this:
edit /etc/apt/sources.list to include contrib archive area:
deb http://http.debian.net/debian wheezy main contrib
deb-src http://http.debian.net/debian wheezy main contrig

then get the fonts like this:
apt-get update
apt-get install ttf-mscorefonts-installer

This pulls down fonts from here http://sourceforge.net/projects/corefonts/
Would these fonts have been included directly in Debian, they'd have been banished to the non-free archive area, since they are restrictive.
Preferred solution
Now the question... does anybody know:

Is there a way of getting asciidoctor-fopub to work without the microsoft fonts?

I'd like to use fonts with a free open source license, such as the fonts in debians main archive area (as opposed to contrib)
...maby by font substitution or some other means?
Thanks

Just an update since the links in the previous messages are now outdated. If using newer versions of FOP, see https://xmlgraphics.apache.org/fop/2.1/fonts.html for including custom fonts. It's now a much simpler process.


[not a flake] K8sServicesTest Checks ClusterIP Connectivity Checks service on same node

This is unlikely a CI flake but a real problem
Symptom:
/home/jenkins/workspace/Cilium-PR-Ginkgo-Tests-Validated/src/github.com/cilium/cilium/test/ginkgo-ext/scopes.go:410
cannot curl to service IP from host
Expected command: curl --path-as-is -s -D /dev/stderr --fail --connect-timeout 5 --max-time 8 http://<IP_ADDRESS>/ -w "time-> DNS: '%{time_namelookup}(%{remote_ip})', Connect: '%{time_connect}',Transfer '%{time_starttransfer}', total '%{time_total}'"
To succeed, but it failed:
Exitcode: 7
Stdout:
      time-> DNS: '0.000022()', Connect: '0.000000',Transfer '0.000000', total '3.205344'
Stderr:

/home/jenkins/workspace/Cilium-PR-Ginkgo-Tests-Validated/src/github.com/cilium/cilium/test/k8sT/Services.go:136

The services are plumbed correctly:
cmd: kubectl exec -n kube-system cilium-8dvs9 -- cilium service list
Exitcode: 0
Stdout:
 	 ID   Frontend              Backend
	 1    <IP_ADDRESS>:2379   1 => <IP_ADDRESS>:2379
	                            2 => <IP_ADDRESS>:2379
	                            3 => <IP_ADDRESS>:2379
	 2    <IP_ADDRESS>:53         1 => <IP_ADDRESS>:53
	 3    <IP_ADDRESS>:443         1 => <IP_ADDRESS>:6443
	 6    <IP_ADDRESS>:80     1 => <IP_ADDRESS>:80
	                            2 => <IP_ADDRESS>:80

I've noticed that the demo app deployments do not define a readiness probe so maybe the pdo is not up and listening yet.

Seen again:
https://jenkins.cilium.io/job/Ginkgo-CI-Tests-Pipeline/6868/testReport/Suite-k8s-1/10/K8sServicesTest_Checks_ClusterIP_Connectivity_Checks_service_on_same_node/
/home/jenkins/workspace/Ginkgo-CI-Tests-Pipeline/k8s-1.10-gopath/src/github.com/cilium/cilium/test/ginkgo-ext/scopes.go:410
cannot curl to service IP from host
Expected command: curl --path-as-is -s -D /dev/stderr --fail --connect-timeout 5 --max-time 8 http://<IP_ADDRESS>/ -w "time-> DNS: '%{time_namelookup}(%{remote_ip})', Connect: '%{time_connect}',Transfer '%{time_starttransfer}', total '%{time_total}'"
To succeed, but it failed:
Exitcode: 7
Stdout:
 	 time-> DNS: '0.000022()', Connect: '0.000000',Transfer '0.000000', total '3.205023'
Stderr:

/home/jenkins/workspace/Ginkgo-CI-Tests-Pipeline/k8s-1.10-gopath/src/github.com/cilium/cilium/test/k8sT/Services.go:136

5f1470eb_K8sServicesTest_Checks_ClusterIP_Connectivity_Checks_service_on_same_node.zip

Would benefit from having access to cilium monitor logs as well.

 After going through logs and comparing the raw hex dumps via bpftool and CT table entries, the services for DNS do not show any oddities. The test has legacy services enabled. I also went through the code paths and compared it with the data in the CT table and looks reasonable to me. cilium_lb4_backends, cilium_lb4_services_v2, cilium_lb4_reverse_nat and cilium_lb4_services looked okay to me.
Running the test itself in a separate instance in a loop over night did not trigger the issue for me. I was only able to trigger from CI so far (for the cases where I didn't hit other flakes or timeouts).
From CI it triggers on old and on net-next kernel. Latter is good since dump can be reliably done via bpftool.
Checking curl directly with ip:port, it's not issuing DNS requests, so I proceeded looking into the service which was exposed over port 80 and its backends:

cmd: "curl --path-as-is -s -D /dev/stderr --fail --connect-timeout 5 --max-time 8 http://<IP_ADDRESS>/ -w \"time-> DNS: '%{time_namelookup}(%{remote_ip})', Connect: '%{time_connect}',Transfer '%{time_starttransfer}', total '%{time_total}'\"" exitCode: 7 duration: 4.211108994s stdout:
time-> DNS: '0.000036()', Connect: '0.000000',Transfer '0.000000', total '3.205025'

Service/LB table (bugtool-cilium-js4wq):
SERVICE ADDRESS      BACKEND ADDRESS
<IP_ADDRESS>:443        <IP_ADDRESS>:0 (4)
                     <IP_ADDRESS>:6443 (4)
<IP_ADDRESS>:2379   <IP_ADDRESS>:2379 (1)
                     <IP_ADDRESS>:2379 (1)
                     <IP_ADDRESS>:0 (1)
                     <IP_ADDRESS>:2379 (1)
<IP_ADDRESS>:80       <IP_ADDRESS>:80 (10)           <---
                     <IP_ADDRESS>:80 (10)
                     <IP_ADDRESS>:0 (10)
<IP_ADDRESS>:53        <IP_ADDRESS>:0 (2)
                     <IP_ADDRESS>:53 (2)
<IP_ADDRESS>:9153      <IP_ADDRESS>:9153 (3)
                     <IP_ADDRESS>:0 (3)

The endpoint list has the backends as well:
<IP_ADDRESS>:0          id=3422  flags=0x0000 ifindex=111 mac=86:B7:F2:A2:2C:12 nodemac=C6:F2:C6:99:7C:0A
<IP_ADDRESS>:0           id=3378  flags=0x0000 ifindex=107 mac=02:24:0E:A0:CD:4B nodemac=DA:4C:19:95:98:8C

BUT: there are zero entries for service or both of the backend IPs in the global TCP CT table.
Note that curl command is executed out of hostns since we're testing cluster IP.
iptables-save output looks okay, both backends are present ...
-A KUBE-SEP-4Y35VQSXWDNOZSET -s <IP_ADDRESS>/32 -j KUBE-MARK-MASQ
-A KUBE-SEP-4Y35VQSXWDNOZSET -p tcp -m tcp -j DNAT --to-destination <IP_ADDRESS>:80
[...]
-A KUBE-SEP-C2TE2QT3F5HYJVTY -s <IP_ADDRESS>/32 -j KUBE-MARK-MASQ
-A KUBE-SEP-C2TE2QT3F5HYJVTY -p tcp -m tcp -j DNAT --to-destination <IP_ADDRESS>:80
[...]
-A KUBE-SERVICES ! -s <IP_ADDRESS>/16 -d <IP_ADDRESS>/32 -p tcp -m comment --comment "default/app1-service: cluster IP" -m tcp --dport 80 -j KUBE-MARK-MASQ
-A KUBE-SERVICES -d <IP_ADDRESS>/32 -p tcp -m comment --comment "default/app1-service: cluster IP" -m tcp --dport 80 -j KUBE-SVC-VV2BFTTEFL2JBH3L
[...]
-A KUBE-SVC-VV2BFTTEFL2JBH3L -m statistic --mode random --probability 0.50000000000 -j KUBE-SEP-4Y35VQSXWDNOZSET
-A KUBE-SVC-VV2BFTTEFL2JBH3L -j KUBE-SEP-C2TE2QT3F5HYJVTY
[...]

... given the endpoints must be on the same node, we would expect the packet path to go via cilium_host (bpf_netdev) and enter BPF context from there. So a CT entry should have been present.
Routing table from bugtool looks okay, both backends are under <IP_ADDRESS>/24  so we should hit that one to get back to cilium_host with src IP <IP_ADDRESS>:
default via <IP_ADDRESS> dev enp0s3 proto dhcp src <IP_ADDRESS> metric 100
<IP_ADDRESS>/24 dev enp0s3 proto kernel scope link src <IP_ADDRESS>
<IP_ADDRESS> dev enp0s3 proto dhcp scope link src <IP_ADDRESS> metric 100
<IP_ADDRESS>/24 via <IP_ADDRESS> dev cilium_host src <IP_ADDRESS>                   <---
<IP_ADDRESS> dev cilium_host scope link
<IP_ADDRESS>/24 via <IP_ADDRESS> dev cilium_host src <IP_ADDRESS>
<IP_ADDRESS>/16 dev docker0 proto kernel scope link src <IP_ADDRESS>
<IP_ADDRESS>/24 dev enp0s9 proto kernel scope link src <IP_ADDRESS>
<IP_ADDRESS>/24 dev br-bf20ae55382c proto kernel scope link src <IP_ADDRESS>
<IP_ADDRESS>/24 dev enp0s8 proto kernel scope link src <IP_ADDRESS>

In the daemon log, I can also see that <IP_ADDRESS> is added to endpoint map:
2019-05-23T14:38:30.658466743Z level=debug msg="Added local ip to endpoint map" ipAddr=<IP_ADDRESS> subsys=daemon
2019-05-23T14:38:30.658572945Z level=debug msg="Added local ip to endpoint map" ipAddr=<IP_ADDRESS> subsys=daemon

And is the IP of cilium_host:
[...]
53: cilium_host@cilium_net: <BROADCAST,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether be:d2:2e:1a:82:87 brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/32 scope link cilium_host
       valid_lft forever preferred_lft forever
[...]

Question then became whether we even reach bpf_netdev. For that cilium monitor output was needed. For k8s, it's not available, so after hacking it up and passing through the CI again, here's what I've seen:
 ------------------------------------------------------------------------------
 CPU 01: MARK 0x998b23c1 FROM 0 from-host: 74 bytes (74 captured), state new, identity 1->0
 Ethernet        {Contents=[..14..] Payload=[..62..] SrcMAC=be:d2:2e:1a:82:87 DstMAC=be:d2:2e:1a:82:87 EthernetType=IPv4 Length=0}
 IPv4    {Contents=[..20..] Payload=[..40..] Version=4 IHL=5 TOS=0 Length=60 Id=1316 Flags=DF FragOffset=0 TTL=64 Protocol=TCP Checksum=7863 SrcIP=<IP_ADDRESS> DstIP=<IP_ADDRESS> Options=[] Padding=[]}
 TCP     {Contents=[..40..] Payload=[] SrcPort=38704 DstPort=80(http) Seq=3357937382 Ack=0 DataOffset=10 FIN=false SYN=true RST=false PSH=false ACK=false URG=false ECE=false CWR=false NS=false Window=64240 Checksum=5904 Urgent=0 Options=[..5..]  Payload=[..62..] SrcMAC=c6:f2:c6:99:7c:0a DstMAC=86:b7:f2:a2:2c:12 EthernetType=IPv4 Length=0}
 IPv4    {Contents=[..20..] Payload=[..40..] Version=4 IHL=5 TOS=0 Length=60 Id=1316 Flags=DF FragOffset=0 TTL=63 Protocol=TCP Checksum=8119 SrcIP=<IP_ADDRESS> DstIP=<IP_ADDRESS> Options=[] Padding=[]}
 TCP     {Contents=[..40..] Payload=[] SrcPort=38704 DstPort=80(http) Seq=3357937382 Ack=0 DataOffset=10 FIN=false SYN=true RST=false PSH=false ACK=false URG=false ECE=false CWR=false NS=false Window=64240 Checksum=5904 Urgent=0 Options=[..5..] Padding=[]}
 ------------------------------------------------------------------------------

Thus we've hit the Policy denied (L3) one from the metrics:
[...]
cilium_drop_bytes_total                               direction="INGRESS" reason="Policy denied (L3)"                <--                                    2960.000000
[...]

So this means, packet comes in  from-host and it therefore reaches bpf_netdev program. The iptables rules did select the backend <IP_ADDRESS>. identity 1-> 0 was seen initially. In bpf_netdev.c, this points to the trace entry in do_netdev():
                send_trace_notify(skb, trace, identity, 0, 0,
                                  skb->ingress_ifindex, 0, TRACE_PAYLOAD_LEN);

Thus in there, identity was initially 0. In handle_identity_from_host() we found that the skb has HOST identity based on skb mark. This seems good.
In CILIUM_CALL_IPV4_FROM_LXC tail call aka handle_ipv4(). In there we do a ipcache_lookup4() since we have reserved identity. Based on the monitor output in Successfully mapped daddr=<IP_ADDRESS> to identity=2, it remapped the identity to 2 (WORLD) instead of 1 (HOST), so it must have found an entry for <IP_ADDRESS> in the ipcache.
Looking into the dump, I can see the following (cilium-map-list---verbose.md):
## Map: cilium_ipcache
Key                        Value                 State   Error
<IP_ADDRESS>/32              105 0 <IP_ADDRESS>   sync
<IP_ADDRESS>/32              4 0 <IP_ADDRESS>           sync
f00d::a0a:0:0:83ce/128     4 0 <IP_ADDRESS>           sync
f00d::a0a:100:0:77a6/128   100 0 <IP_ADDRESS>   sync
<IP_ADDRESS>/32               1 0 <IP_ADDRESS>     sync
<IP_ADDRESS>/32             4 0 <IP_ADDRESS>     sync
f00d::a0a:100:0:5ca1/128   101 0 <IP_ADDRESS>   sync
f00d::a0a:100:0:a048/128   4 0 <IP_ADDRESS>     sync
<IP_ADDRESS>/32           1 0 <IP_ADDRESS>           sync
f00d::a0a:0:0:49c5/128     53897 0 <IP_ADDRESS>       sync
<IP_ADDRESS>/32             101 0 <IP_ADDRESS>   sync
<IP_ADDRESS>/32              101 0 <IP_ADDRESS>         sync
<IP_ADDRESS>/32             4 0 <IP_ADDRESS>     sync
f00d::a0a:100:0:3c6/128    105 0 <IP_ADDRESS>   sync
<IP_ADDRESS>/32             20272 0 <IP_ADDRESS>       sync
f00d::a0a:0:0:8a38/128     65224 0 <IP_ADDRESS>       sync
<IP_ADDRESS>/0                  2 0 <IP_ADDRESS>           sync
<IP_ADDRESS>/32              4 0 <IP_ADDRESS>     sync
<IP_ADDRESS>/32             101 0 <IP_ADDRESS>   sync
f00d::a0a:100:0:82a5/128   4 0 <IP_ADDRESS>     sync
f00d::a0a:0:0:a5bc/128     20272 0 <IP_ADDRESS>       sync
::/0                       2 0 <IP_ADDRESS>           sync
<IP_ADDRESS>/32             105 0 <IP_ADDRESS>   sync
<IP_ADDRESS>/32             65224 0 <IP_ADDRESS>       sync
f00d::a0a:100:0:3c8/128    104 0 <IP_ADDRESS>   sync
<IP_ADDRESS>/32               53897 0 <IP_ADDRESS>       sync
<IP_ADDRESS>/32             104 0 <IP_ADDRESS>   sync
f00d::a0a:100:0:9e36/128   105 0 <IP_ADDRESS>   sync
f00d::a0a:100:0:f761/128   4 0 <IP_ADDRESS>     sync
f00d::a0a:0:0:65f7/128     4 0 <IP_ADDRESS>           sync
<IP_ADDRESS>/32              100 0 <IP_ADDRESS>   sync
<IP_ADDRESS>/32             100 0 <IP_ADDRESS>   sync
f00d::a0a:0:0:df3c/128     101 0 <IP_ADDRESS>         sync
f00d::a0a:100:0:45c4/128   105 0 <IP_ADDRESS>   sync
f00d::a0a:100:0:1/128      1 0 <IP_ADDRESS>           sync
f00d::a0a:0:0:1/128        1 0 <IP_ADDRESS>           sync
fd04::11/128               1 0 <IP_ADDRESS>           sync
<IP_ADDRESS>/32             4 0 <IP_ADDRESS>     sync
f00d::a0a:100:0:490e/128   100 0 <IP_ADDRESS>   sync
f00d::a0a:0:0:73a6/128     20272 0 <IP_ADDRESS>       sync
f00d::a0a:0:0:3fc3/128     4 0 <IP_ADDRESS>           sync
f00d::a0a:100:0:453c/128   101 0 <IP_ADDRESS>   sync
f00d::a0a:100:0:25aa/128   4 0 <IP_ADDRESS>     sync
<IP_ADDRESS>/32             4 0 <IP_ADDRESS>           sync
<IP_ADDRESS>/32             105 0 <IP_ADDRESS>   sync
<IP_ADDRESS>/32               1 0 <IP_ADDRESS>           sync
f00d::a0a:100:0:bdb4/128   105 0 <IP_ADDRESS>   sync
f00d::a0a:0:0:64bc/128     4 0 <IP_ADDRESS>           sync
<IP_ADDRESS>/32              105 0 <IP_ADDRESS>   sync
<IP_ADDRESS>/32              20272 0 <IP_ADDRESS>       sync

But the issue is that an entry for <IP_ADDRESS> is missing there. If our source IP would have been <IP_ADDRESS>, then we would have seen HOST identity.
The address stems form and is a dynamic one; it's not known to cilium in the sense it's neither ipv4 internal nor external:
2: enp0s3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 08:00:27:f8:ea:e5 brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/24 brd <IP_ADDRESS> scope global dynamic enp0s3
       valid_lft 84528sec preferred_lft 84528sec

The source IP being <IP_ADDRESS> instead of expected <IP_ADDRESS> could have come from the fact that packet first went to L7 proxy ... which would also explain from the skb->mark that HOST was derived from there.
The cilium-js4wq_policy_get.txt shows that we actually have a L7 policy:
[
  {
    "endpointSelector": {
      "matchLabels": {
        "any:id": "app1",
        "k8s:io.kubernetes.pod.namespace": "default"
      }
    },
    "ingress": [
      {
        "fromEndpoints": [
          {
            "matchLabels": {
              "k8s:io.kubernetes.pod.namespace": "second"
            }
          }
        ],
        "toPorts": [
          {
            "ports": [
              {
                "port": "80",
                "protocol": "TCP"
              }
            ],
            "rules": {
              "http": [
                {
                  "path": "/public",
                  "method": "GET"
                }
              ]
            }
          }
        ]
      }
    ],
    "labels": [
      {
        "key": "io.cilium.k8s.policy.name",
        "value": "cnp-second-namespace",
        "source": "k8s"
      },
      {
        "key": "io.cilium.k8s.policy.uid",
        "value": "81f002c0-7d69-11e9-a08d-080027f8eae5",
        "source": "k8s"
      },
      {
        "key": "io.cilium.k8s.policy.namespace",
        "value": "default",
        "source": "k8s"
      },
      {
        "key": "io.cilium.k8s.policy.derived-from",
        "value": "CiliumNetworkPolicy",
        "source": "k8s"
      }
    ]
  }
]
Revision: 76

What is still unclear and currently under investigation: 1) why was the IP <IP_ADDRESS> to 2 ipcache mapping missing in the dump (double checking in CI via bpftool), and 2) whether the L7 policy was a even stale leftover from prior CI tests and is not even supposed to be in there. E.g. did policy removal in prior tests fail? Error handling is being ignored for it ...

ci-dump.zip

@borkmann We could work around this by applying SNAT from the proxy if the address is not the cilium_host IP

That extra policy left behind looks a lot like test pollution. I'm going to see if there's a test pollution problem locally in relation to this issue.

That extra policy left behind looks a lot like test pollution. I'm going to see if there's a test pollution problem locally in relation to this issue.

Yes, agree. It should be cnp-second-namespaces.yaml as I've stated above in my updated analysis. I still think there is another bug with either source address selection and/or stale ipcache mapping. Specifically, the <IP_ADDRESS>/24 via <IP_ADDRESS> dev cilium_host src <IP_ADDRESS> should select <IP_ADDRESS> as source address if I'm not mistaken which is not the case.

@borkmann the test pollution problem appears to be the source of some of the problems!
This has to be done while running with NETNEXT=true on your local setup.
To reproduce, I did  the following:

Boot the VMs with K8S_VERSION=1.10 and NETNEXT=true:

$ K8S_VERSION=1.10 NETNEXT=true vagrant up k8s1-1.10 ; K8S_VERSION=1.10 NETNEXT=true vagrant up k8s2-1.10

Run the test which leaves the extra policy around:

$ K8S_VERSION=1.10 NETNEXT=true ginkgo --focus="Namespaces policies" -v -- -cilium.provision=false -cilium.holdEnvironment=true -cilium.skipLogs=true -cilium.testScope="K8s"

Run the service on same node test:

$ K8S_VERSION=1.10 NETNEXT=true ginkgo --focus="Checks ClusterIP Connectivity" -v -- -cilium.provision=false -cilium.holdEnvironment=true -cilium.skipLogs=true -cilium.testScope="K8s"

The test will fail:

K8sServicesTest Checks ClusterIP Connectivity Checks service on same node
at /Users/ianvernon/go/src/github.com/cilium/cilium/test/ginkgo-ext/scopes.go:410

[cannot curl to service IP from host
Expected command: curl --path-as-is -s -D /dev/stderr --fail --connect-timeout 5 --max-time 8 http://<IP_ADDRESS>/ -w "time-> DNS: '%{time_namelookup}(%{remote_ip})', Connect: '%{time_connect}',Transfer '%{time_starttransfer}', total '%{time_total}'"
To succeed, but it failed:
Exitcode: 7
Stdout:
 	 time-> DNS: '0.000039()', Connect: '0.000000',Transfer '0.000000', total '3.203264'
Stderr:

]

Pausing test for debug, use vagrant to access test setup.
Run "kill -SIGCONT 74434" to continue.

You will see the extra CNP by checking for CNPs:

$ kubectl get cnp cnp-second-namespace -o yaml
apiVersion: cilium.io/v2
kind: CiliumNetworkPolicy
metadata:
  annotations:
    kubectl.kubernetes.io/last-applied-configuration: |
      {"apiVersion":"cilium.io/v2","description":"Policy to stress test L7 proxy","kind":"CiliumNetworkPolicy","metadata":{"annotations":{},"name":"cnp-second-namespace","namespace":"default"},"spec":{"endpointSelector":{"matchLabels":{"id":"app1"}},"ingress":[{"fromEndpoints":[{"matchLabels":{"k8s:io.kubernetes.pod.namespace":"second"}}],"toPorts":[{"ports":[{"port":"80","protocol":"TCP"}],"rules":{"http":[{"method":"GET","path":"/public"}]}}]}]}}
  clusterName: ""
  creationTimestamp: 2019-05-24T23:26:41Z
  generation: 1
  name: cnp-second-namespace
  namespace: default
  resourceVersion: "2312"
  selfLink: /apis/cilium.io/v2/namespaces/default/ciliumnetworkpolicies/cnp-second-namespace
  uid: 62ad7dec-7e7b-11e9-8107-080027f8eae5
spec:
  endpointSelector:
    matchLabels:
      any:id: app1
  ingress:
  - fromEndpoints:
    - matchLabels:
        k8s:io.kubernetes.pod.namespace: second
    toPorts:
    - ports:
      - port: "80"
        protocol: TCP
      rules:
        http:
        - method: GET
          path: /public
status:
  nodes:
    k8s1:
      enforcing: true
      lastUpdated: 2019-05-24T23:26:41.430684992Z
      localPolicyRevision: 20
      ok: true
    k8s2:
      enforcing: true
      lastUpdated: 2019-05-24T23:26:41.307851007Z
      localPolicyRevision: 14
      ok: true

Delete the CNP:

$ kubectl delete cnp cnp-second-namespace
ciliumnetworkpolicy.cilium.io "cnp-second-namespace" deleted

The command ran by the test will now succeed:

$ curl --path-as-is -s -D /dev/stderr --fail --connect-timeout 5 --max-time 8 http://<IP_ADDRESS>/ -w " '%{time_starttransfer}', total '%{time_total}'" onnect: '%{time_connect}',Transfer
HTTP/1.1 200 OK
Date: Fri, 24 May 2019 23:33:56 GMT
Server: Apache/2.4.25 (Unix)
Last-Modified: Mon, 11 Jun 2007 18:53:14 GMT
ETag: "2d-432a5e4a73a80"
Accept-Ranges: bytes
Content-Length: 45
Content-Type: text/html

<html><body><h1>It works!</h1></body></html>
time-> DNS: '0.000027(<IP_ADDRESS>)', Connect: '0.000173',Transfer '0.001082', total '0.001185'

For a simpler reproducer, do the following:

Boot the VMs per the above:
Apply the following policy:

kubectl apply -f test/k8sT/manifests/cnp-second-namespaces.yaml

Run the service on same node test:

$ K8S_VERSION=1.10 NETNEXT=true ginkgo --focus="Checks ClusterIP Connectivity" -v -- -cilium.provision=false -cilium.holdEnvironment=true -cilium.skipLogs=true -cilium.testScope="K8s"

The test will fail:

K8sServicesTest Checks ClusterIP Connectivity Checks service on same node
at /Users/ianvernon/go/src/github.com/cilium/cilium/test/ginkgo-ext/scopes.go:410

[cannot curl to service IP from host
Expected command: curl --path-as-is -s -D /dev/stderr --fail --connect-timeout 5 --max-time 8 http://<IP_ADDRESS>/ -w "time-> DNS: '%{time_namelookup}(%{remote_ip})', Connect: '%{time_connect}',Transfer '%{time_starttransfer}', total '%{time_total}'"
To succeed, but it failed:
Exitcode: 7
Stdout:
 	 time-> DNS: '0.000039()', Connect: '0.000000',Transfer '0.000000', total '3.203264'
Stderr:

]

Pausing test for debug, use vagrant to access test setup.
Run "kill -SIGCONT 74434" to continue.

The thing here though, is that with K8s, we should allow ingress from the host even though the above policy which is errantly left behind only allows ingress from a separate namespace. We need to allow ingress from the host for healthchecks from K8s.
Also one thing to note - I initially ran this without NETNEXT=true with K8s 1.14, and the test pollution did not affect the test. So I think something involving ingress from host when L7 policy applies to a pod is messed up in newer kernels.

This appears to be highly related to https://github.com/cilium/cilium/issues/8018

# curl --path-as-is -s -D /dev/stderr --fail --connect-timeout 5 --max-time 8 http://<IP_ADDRESS>/ -w "time-> DNS: '%{time_namelookup}(%{remote_ip})', Connect: '%{time_connect}',Transfer '%{time_starttransfer}', total '%{time_total}'"
time-> DNS: '0.000038()', Connect: '0.000000',Transfer '0.000000', total '3.203689'

# docker exec -ti 6d5465170bf4 bash
# cilium bpf lb list
SERVICE ADDRESS      BACKEND ADDRESS
<IP_ADDRESS>:80    <IP_ADDRESS>:0 (6)                                      <---
                     <IP_ADDRESS>:80 (6)
                     <IP_ADDRESS>:80 (6)
<IP_ADDRESS>:2379   <IP_ADDRESS>:2379 (3)
                     <IP_ADDRESS>:0 (3)
                     <IP_ADDRESS>:2379 (3)
                     <IP_ADDRESS>:2379 (3)
<IP_ADDRESS>:53        <IP_ADDRESS>:0 (2)
                     <IP_ADDRESS>:53 (2)
<IP_ADDRESS>:443        <IP_ADDRESS>:6443 (1)
                     <IP_ADDRESS>:0 (1)
# exit

root@k8s1:/home/vagrant# ip route get <IP_ADDRESS>
<IP_ADDRESS> via <IP_ADDRESS> dev enp0s3 src <IP_ADDRESS> uid 0
    cache
root@k8s1:/home/vagrant# ip route get <IP_ADDRESS>
<IP_ADDRESS> via <IP_ADDRESS> dev cilium_host src <IP_ADDRESS> uid 0
    cache
root@k8s1:/home/vagrant# ip route get <IP_ADDRESS>
<IP_ADDRESS> via <IP_ADDRESS> dev cilium_host src <IP_ADDRESS> uid 0
    cache
root@k8s1:/home/vagrant# ip r
default via <IP_ADDRESS> dev enp0s3 proto dhcp src <IP_ADDRESS> metric 100
<IP_ADDRESS>/24 dev enp0s3 proto kernel scope link src <IP_ADDRESS>
<IP_ADDRESS> dev enp0s3 proto dhcp scope link src <IP_ADDRESS> metric 100
<IP_ADDRESS>/24 via <IP_ADDRESS> dev cilium_host src <IP_ADDRESS>
<IP_ADDRESS> dev cilium_host scope link
<IP_ADDRESS>/24 via <IP_ADDRESS> dev cilium_host src <IP_ADDRESS>
<IP_ADDRESS>/16 dev docker0 proto kernel scope link src <IP_ADDRESS>
<IP_ADDRESS>/24 dev enp0s9 proto kernel scope link src <IP_ADDRESS>
<IP_ADDRESS>/24 dev br-e6fcdf93b490 proto kernel scope link src <IP_ADDRESS>
<IP_ADDRESS>/24 dev enp0s8 proto kernel scope link src <IP_ADDRESS>

This means that source address selection is wrong. Look like this is done on the service address and when we rewrite to one of the backends, this is still the same and not updated to <IP_ADDRESS>. This should be done after we selected a backend.


[Proposal] when variant

Mix already has a long set of built-in variants. Yet, there isn't a variant to check if a value is true or false: there's where the when variant would come in. It'd be similar to the if keyword in dart, taking a bool as a parameter.
Basic usage
// in a stateful widget

bool hasError = false;

void fetch() {
  try {
    // perform the fetch
    setState(() => hasError = false);
  } catch (e) {
    // handle the error
    setState(() => hasError = true);
  }
}

final mix = Mix(
  when(hasError)(
    bgColor(theme<MyColors>((colors) => colors.errorBackgroundColor)),
  )(
    // this would be the `else` case
    bgColor(theme<MyColors>((colors) => colors.surfaceBackgroundColor)),
  ),
);

Why?
Currently, it's very verbose to check if a value is true or false in a Mix. We must either ¹create a variant and use mix.withVariant or ²create inline conditional checks hasError ? bgColor(...) : bgColor(...)

@bdlukaa I really like that, we do have another conditional which is in the Mix factory Mix.chooser, also there is the variantSwitcher, The good thing about this approach is that you could nest variant conditionals...

From #99 and #93, I also thought of a callback function that may work as a chooser as well:
Mix(
  bgColor(chooser(hasError)
    (theme<MyColors>((colors) => colors.errorBackgroundColor))
    (theme<MyColors>((colors) => colors.surfaceBackgroundColor)),
  ),
),

It'd be used inside the attributes themselves. Of course, would only be possible if #93's model is approved
What are you thoughts on this?


Document process / compile FAQ for creating BIDS Apps

Working together with Daniele, Asier and Madhur to document the process of creating a BIDS app.
This will most likely be a page on the wiki!

Excited to see this documented ! Just to add one helpful resource: there's example BIDS App repository

Thanks for the helpful link!
Check out the new wiki page and let me know what you think:
https://github.com/INCF/BIDS-Starter-Kit/wiki/BIDS-Apps-Help

This looks great @Park-Patrick! I made a few changes (a little bit of formatting and a couple of new links) but definitely looks awesome ✨


Uncaught TypeError for clang

Hey! I've tried to run a script and this error popped up. Unfortunately I can't give any more context since the script is not publicly available.
/Users/oli/.tea/go.dev/v1.20.5/pkg/tool/darwin_arm64/link: running clang failed: exit status 1
tea: installing go.dev, llvm.org
error: Uncaught TypeError: argv._.push is not a function
                argv._.push(flags.strings["_"] ?? !isNumber(arg) ? arg : Number(arg));
                       ^
    at parse (https://deno.land/std@0.177.0/flags/mod.ts:303:24)
    at getOptions (https://deno.land/std@0.177.0/node/internal_binding/node_options.ts:30:18)
    at getOptionsFromBinding (https://deno.land/std@0.177.0/node/internal/options.ts:26:37)
    at getOptionValue (https://deno.land/std@0.177.0/node/internal/options.ts:31:21)
    at https://deno.land/std@0.177.0/node/crypto.ts:21:20
clang-16: error: linker command failed with exit code 1 (use -v to see invocation)

hmm do you know what command is running here?
The output is confusing. go is running it's link, which seems to cause go to be installed…? finally clang-16 errors out…!

also super weird backtrace, none of our code and it starts in node/crypto…!

I ran a script that essentially does go run . --start. Inside of main.go it starts by checking if certain cli tools are installed on the machine. Perhaps this confuses tea?

it starts by checking if certain cli tools are installed on the machine. Perhaps this confuses tea?

scripts don’t get tea’s magic unless you manually source it. So probs not.
try setting export DEBUG=1 and set -x in the script

The check for installed cli tools is already part of the main.go so that won't work. The function in the script responsible to call main.go is this:
    pushd $DIR
    go run . -start
    popd

so there's not a lot to debug on that side. The go script exec.Command("the-command-to-check", "version").Run() to check if it exists. Maybe this part triggers tea somehow due to the underlying implementation?

export DEBUG=1 and running the script will still give us more data as tea itself will output more.

export DEBUG=1 and running the script will still give us more data as tea itself will output more.

I did that and I didn't get any extra output. However I deleted ~/.tea and reinstalled it before doing this as the issue prevented me from working.

I just wanted to see if I can reproduce the issue and ran tea git but I got this stacktrace instead:
{
  exit: [Object: null prototype] { success: false, code: 1, signal: null }
}
Error: cmd failed: 1:
    at useRun (file:///private/var/folders/y3/yr3bxsy95c3gfwwj61ytbp000000gq/T/45bf702e/src/hooks/useRun.ts:29:34)
    at eventLoopTick (ext:core/01_core.js:182:11)
    at async default (file:///private/var/folders/y3/yr3bxsy95c3gfwwj61ytbp000000gq/T/45bf702e/src/app.exec.ts:13:9)
    at async run (file:///private/var/folders/y3/yr3bxsy95c3gfwwj61ytbp000000gq/T/45bf702e/src/app.main.ts:59:25)
    at async file:///private/var/folders/y3/yr3bxsy95c3gfwwj61ytbp000000gq/T/45bf702e/src/app.ts:12:5 {
  code: 1,
  cmd: []
}

this is expected git by itself returns exit code 1.

is the reported error still happening after your reinstall?

Doesn't seem like it.

hmm… I hope this means we fixed it. We release a lot of point releases with fixes. Closing. Reopen if it happens again.

I've seen this when clang is invoked via symlink.
Possibly too many args are passed for deno to handle or something.

Might be it, I'm using ccache which creates symlinks to itself for tools like clang.

Did some experimenting:

I removed the symlinks from ~/.local/bin and invoked ~/.tea/.local/bin/clang hello.c, it worked fine.
After that, I added ~/.tea/.local/bin to PATH and invoked clang hello.c, it crashed:

% DEBUG=1 tea -vvv clang hello.c
resolving package graph
{
  hydrating: [
    {
      project: "llvm.org",
      path: ~/.tea/tea.xyz/var/pantry/projects/llvm.org/package.yml,
      constraint: *,
      shebang: [ "clang" ]
    }
  ]
{
  cmd: [ "clang", "hello.c" ],
  env: {
    PATH: "/Users/zahaaar/.tea/llvm.org/v16.0.5/bin:/Users/zahaaar/.local/share/go/bin:/Users/zahaaar/.cargo/bi"... 149 more characters,
    MANPATH: "/Users/zahaaar/.tea/zlib.net/v1.2.13/share/man:/Users/zahaaar/.tea/llvm.org/v16.0.5/share/man:/usr/s"... 8 more characters,
    PKG_CONFIG_PATH: "/Users/zahaaar/.tea/zlib.net/v1.2.13/lib/pkgconfig",
    LIBRARY_PATH: "/Users/zahaaar/.tea/zlib.net/v1.2.13/lib:/Users/zahaaar/.tea/llvm.org/v16.0.5/lib",
    LD_LIBRARY_PATH: "/Users/zahaaar/.tea/zlib.net/v1.2.13/lib:/Users/zahaaar/.tea/llvm.org/v16.0.5/lib",
    CPATH: "/Users/zahaaar/.tea/zlib.net/v1.2.13/include:/Users/zahaaar/.tea/llvm.org/v16.0.5/include",
    XDG_DATA_DIRS: "/Users/zahaaar/.tea/zlib.net/v1.2.13/share:/Users/zahaaar/.tea/llvm.org/v16.0.5/share",
    DYLD_FALLBACK_LIBRARY_PATH: "/Users/zahaaar/.tea/zlib.net/v1.2.13/lib:/Users/zahaaar/.tea/llvm.org/v16.0.5/lib",
    LDFLAGS: "-Wl,-rpath,/Users/zahaaar/.tea",
    TEA_PREFIX: "/Users/zahaaar/.tea",
    TEA_FORK_BOMB_PROTECTOR: "1"
  }
}
error: Uncaught TypeError: argv._.push is not a function
                argv._.push(flags.strings["_"] ?? !isNumber(arg) ? arg : Number(arg));
                       ^
    at parse (https://deno.land/std@0.177.0/flags/mod.ts:303:24)
    at getOptions (https://deno.land/std@0.177.0/node/internal_binding/node_options.ts:30:18)
    at getOptionsFromBinding (https://deno.land/std@0.177.0/node/internal/options.ts:26:37)
    at getOptionValue (https://deno.land/std@0.177.0/node/internal/options.ts:31:21)
    at https://deno.land/std@0.177.0/node/crypto.ts:21:20
clang-16: error: linker command failed with exit code 1 (use -v to see invocation)
{
  exit: [Object: null prototype] { success: false, code: 1, signal: null }
}
Error: cmd failed: 1: hello.c
    at useRun (file:///private/var/folders/y3/yr3bxsy95c3gfwwj61ytbp000000gq/T/f0a0633b/src/hooks/useRun.ts:29:34)
    at eventLoopTick (ext:core/01_core.js:182:11)
    at async default (file:///private/var/folders/y3/yr3bxsy95c3gfwwj61ytbp000000gq/T/f0a0633b/src/app.exec.ts:13:9)
    at async run (file:///private/var/folders/y3/yr3bxsy95c3gfwwj61ytbp000000gq/T/f0a0633b/src/app.main.ts:59:25)
    at async file:///private/var/folders/y3/yr3bxsy95c3gfwwj61ytbp000000gq/T/f0a0633b/src/app.ts:12:5 {
  code: 1,
  cmd: [ "hello.c" ]
}
% ls -la $(which clang)
lrwxr-xr-x  1 zahaaar  staff  3 Jun  9 12:48 /Users/zahaaar/.tea/.local/bin/clang -> tea
% ls -la $(which tea)
lrwxr-xr-x  1 zahaaar  staff  24 Jun  9 11:24 /Users/zahaaar/.tea/.local/bin/tea -> ../../tea.xyz/v*/bin/tea

Closing with the hope is fixed in the latest release. reopen if not. i will also reopen if I find the same issue.

Confirming that clang toolchain now works fine for me, thanks!


Can't get to work at all

I am unsure what else to try. Here is my vimrc. Notably I have
filetype plugin indent on
and
set rtp+=~/.vim/bundle/vim-colorschemes/
set t_Co=256
" note: using Atom terminal color scheme for iTerm2
" (https://github.com/mbadolato/iTerm2-Color-Schemes/blob/master/schemes/Atom.itermcolors)
colorscheme herald
if has("syntax")
  syntax enable
endif

I have verified that the Vundle installation executed successfully
jamis@Jamiss-MBP:~/src/dotfiles$ tree ~/.vim/bundle/vim-solidity/
/Users/jamis/.vim/bundle/vim-solidity/
├── LICENSE
├── README.md
├── ftdetect
│   └── solidity.vim
├── ftplugin
│   └── solidity.vim
├── indent
│   └── solidity.vim
└── syntax
    └── solidity.vim

4 directories, 6 files](url)

Am I missing something major? Something conflicting in my vimrc? Maybe a conflicting Vundle plugin?

I have no problem installing through Pathogen.

Also can't make it work with Vundle.
But with Pathogen it works fine.

add this line in file ~/.vim/bundles.vim before the last line "filetype plugin indent on"
filetype off

something in my .vimrc was screwing it up. I use Vundle. anyway this is what fixed it at the very end of my .vimrc shrug
filetype off filetype plugin indent on


Add a slideshow of games to the landing page

I'm not sure it's a good idea to feature games like that without asking for permission from their creators. Also, you can see in the diff that that section actually had two backgrounds, one of them was adding black gradients at the top and at the bottom, you removed it.

Black gradient has been returned
https://redot-landing-page.vercel.app/

I made same mistake when I did mine. I think it needs black gradient at the bottom as well.

Oh, sharp eyes!

Looks pretty good. In MainPageHero.vue page, can you please replace the "Game Name" with your game's name?

They don't have a name (nor release anywhere), they are simply prototypes I've been trying out.
They serve as temporary images for showcasing the hero until something more fancy is submitted🙂, so no attribution is required

Ah alright. I guess the "Game name" pill can be hidden for now. After that, I'll approve and merge


Create a design doc specifying decomposition and updates to the result object

Hey team! Please add your planning poker estimate with ZenHub @cjao @Emmanuel289 @kessler-frost


Add NVAccess.NVDA. It's a screen reader.

NVAccess.NVDA
Version: 2020.1
website: https://www.nvaccess.org
NonVisual Desktop Access (NVDA) is a free and open source screen reader for the Microsoft Windows operating system. Providing feedback via synthetic speech and Braille, it enables blind or vision impaired people to access computers running Windows for no more cost than a sighted person. NVDA is developed by NV Access, with contributions from the community.
Microsoft Reviewers: Open in CodeFlow

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: abitglow sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.


JedisCluster support choosing database.

[Motivation]
JedisCluster should support choosing database instead of default 0.
[Modifications]
(1) add private member: database in JedisClusterInfoCache;
(2) add new constructor with database for JedisCluster;
[Result]
JedisCluster support choosing database.

close it due to the cluser mode isn't support select db. refer to ERR SELECT is not allowed in cluster mode

@yimiaoxiehou  not support it due to cluster mode not support it


subdirs and dirs outside the main

Okay, I know I'm making a lot of issues today, but I figured each thing should be it's own separate issue XD
Anyways, this issue is about the directory format I use for my jekyll blogs, and how I might be able to keep using it while also using your package...
See, I have what I call a grandmaster github set up, basically, I have the grandmaster folder, and under that folder are two folders, source and pages, source is where I write my posts and holds the jekyll source stuff, pages is where my jekyll compiles and outputs my jekyll site, this makes it easier when dealing with github pages.
So, the issue here is the way your package handles the directory structure, it requres that the main folder be your jekyll source, I'm not sure how it handles compiling outside the main directory though, I haven't tried that yet.
So I'm hoping there's a way to keep this all easy and useable XD

This should be fixed by the work for #47 where jekyll-atom respects source/destination config.


[WIP] aligned-nums: returns an array of aligned nums

@Mc-Zen, here's a first cut at an extra function that takes an array of strings and returns an array of aligned content.
It still needs all the normal stuff like doc additions and tests. I'd like your review and suggestions before I tackle those. There are a couple of examples in the num.typ file. Here's the output of one of them:

Hi @tshort ,
Actually I had already implemented something along the lines in the branch https://github.com/Mc-Zen/zero/tree/align-columns a few days ago.
Sorry that I didn't notify you, I had to work on a talk that I gave at the Typst meetup yesterday.
The reason was that I'm not quite convinced with the design yet. For now, this totally works but eventually num will be a type where show-num will be just a default show rule. Therefore, we have to regard the return value of it as some opaque content (although technically content will be removed by then but that's another story). For this reason we we can't just return an array for the components (at least not anymore once num is a type) - at least I believe so.

Ha. Great! Yours is more concise, too. Closing...


System http server

Add a system controller which runs a HTTP server as a user interface to interact with nydus-snapshotter.
With the system controller, we can fetch all managed nydusds's working state and control nydusd workflows.
Nydus-snapshotter might manage dozens of running nydus daemons, each daemon may have multiple
file system instances attached. For easy maintenance, the system controller can interact with
all the daemons in a consistent and automatic way.

Codecov Report
Base: 30.36% // Head: 29.36% // Decreases project coverage by -1.00% :warning:

Coverage data is based on head (05b7777) compared to base (ca8e67e).
Patch coverage: 10.00% of modified lines in pull request are covered.

:exclamation: Current head 05b7777 differs from pull request most recent head c2ef5a5. Consider uploading reports for the commit c2ef5a5 to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #201      +/-   ##
==========================================
- Coverage   30.36%   29.36%   -1.01%
==========================================
  Files          22       23       +1
  Lines        2045     2115      +70
==========================================
  Hits          621      621
- Misses       1336     1406      +70
  Partials       88       88

Impacted Files
Coverage Δ

config/config.go
0.00% <0.00%> (ø)

pkg/process/system.go
0.00% <0.00%> (ø)

pkg/process/manager.go
21.12% <50.00%> (+0.19%)
:arrow_up:

cmd/containerd-nydus-grpc/pkg/command/flags.go
100.00% <100.00%> (ø)

pkg/auth/kubesecret.go
23.71% <0.00%> (-10.31%)
:arrow_down:

pkg/filesystem/fs/blob_manager.go
55.55% <0.00%> (+11.11%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

Why not reuse the metrics server?

Why not reuse the metrics server?

Looks like we can merge the two HTTP servers.

Prometheus metrics server and system contorller api server are merged


Feature/cd

Codecov Report

Merging #33 into master will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##            master       #33   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           11        11
  Lines          340       340
  Branches        12        12
=========================================
  Hits           340       340

Flag
Coverage Δ

#backend
100.00% <ø> (ø)


android-sdk incorrectly lists the Tag/ABIs as 'no ABIs’ for Google APIs preventing the creation of AVD’s for Google APIs

[ *] Ran brew update and retried your prior step?
[ *] Ran brew doctor, fixed as many issues as possible and retried your prior step?

Bug reports:
Installing the System Images for Google APIs and related packages no longer displays the ABIs against the Google API Targets.
Steps to reproduce

brew install android-sdk
Download the following packages using 'android update sdk' command:

tools
platform-tools
build-tools-22.0.1
android-22
addon-google_apis-google-22
sys-img-x86-google_apis-22
build-tools-23.0.3
android-23
addon-google_apis-google-23
sys-img-x86-google_apis-23

Expected to happen
android list targets
Available Android targets:
id: 1 or "android-22"
Name: Android 5.1.1
Type: Platform
API level: 22
Revision: 2
Skins: HVGA, QVGA, WQVGA400, WQVGA432, WSVGA, WVGA800 (default), WVGA854, WXGA720, WXGA800, WXGA800-7in
Tag/ABIs : no ABIs.
id: 2 or "android-23"
Name: Android 6.0
Type: Platform
API level: 23
Revision: 3
Skins: HVGA, QVGA, WQVGA400, WQVGA432, WSVGA, WVGA800 (default), WVGA854, WXGA720, WXGA800, WXGA800-7in
Tag/ABIs : no ABIs.
id: 3 or "Google Inc.:Google APIs:22"
Name: Google APIs
Type: Add-On
Vendor: Google Inc.
Revision: 1
Description: Android + Google APIs
Based on Android 5.1.1 (API level 22)
Libraries:
* com.android.future.usb.accessory (usb.jar)
API for USB Accessories
* com.google.android.media.effects (effects.jar)
Collection of video effects
* com.google.android.maps (maps.jar)
API for Google Maps
Skins: HVGA, QVGA, WQVGA400, WQVGA432, WSVGA, WVGA800 (default), WVGA854, WXGA720, WXGA800, WXGA800-7in
Tag/ABIs : .google_apis/x86
id: 4 or "Google Inc.:Google APIs:23"
Name: Google APIs
Type: Add-On
Vendor: Google Inc.
Revision: 1
Description: Android + Google APIs
Based on Android 6.0 (API level 23)
Libraries:
* com.android.future.usb.accessory (usb.jar)
API for USB Accessories
* com.google.android.media.effects (effects.jar)
Collection of video effects
* com.google.android.maps (maps.jar)
API for Google Maps
Skins: HVGA, QVGA, WQVGA400, WQVGA432, WSVGA, WVGA800 (default), WVGA854, WXGA720, WXGA800, WXGA800-7in
Tag/ABIs : google_apis/x86
Instead observed
android list targets
Available Android targets:
id: 1 or "android-22"
Name: Android 5.1.1
Type: Platform
API level: 22
Revision: 2
Skins: HVGA, QVGA, WQVGA400, WQVGA432, WSVGA, WVGA800 (default), WVGA854, WXGA720, WXGA800, WXGA800-7in
Tag/ABIs : google_apis/x86
id: 2 or "android-23"
Name: Android 6.0
Type: Platform
API level: 23
Revision: 3
Skins: HVGA, QVGA, WQVGA400, WQVGA432, WSVGA, WVGA800 (default), WVGA854, WXGA720, WXGA800, WXGA800-7in
Tag/ABIs : google_apis/x86
id: 3 or "Google Inc.:Google APIs:22"
Name: Google APIs
Type: Add-On
Vendor: Google Inc.
Revision: 1
Description: Android + Google APIs
Based on Android 5.1.1 (API level 22)
Libraries:
* com.android.future.usb.accessory (usb.jar)
API for USB Accessories
* com.google.android.media.effects (effects.jar)
Collection of video effects
* com.google.android.maps (maps.jar)
API for Google Maps
Skins: HVGA, QVGA, WQVGA400, WQVGA432, WSVGA, WVGA800 (default), WVGA854, WXGA720, WXGA800, WXGA800-7in
Tag/ABIs : no ABIs.
id: 4 or "Google Inc.:Google APIs:23"
Name: Google APIs
Type: Add-On
Vendor: Google Inc.
Revision: 1
Description: Android + Google APIs
Based on Android 6.0 (API level 23)
Libraries:
* com.android.future.usb.accessory (usb.jar)
API for USB Accessories
* com.google.android.media.effects (effects.jar)
Collection of video effects
* com.google.android.maps (maps.jar)
API for Google Maps
Skins: HVGA, QVGA, WQVGA400, WQVGA432, WSVGA, WVGA800 (default), WVGA854, WXGA720, WXGA800, WXGA800-7in
Tag/ABIs : no ABIs

brew config
HOMEBREW_VERSION: 0.9.9
ORIGIN: https://github.com/Homebrew/brew
HEAD: 11d47e8325f50ab7993f3fca0432876da0ea1c11
Last commit: 2 days ago
Core tap ORIGIN: https://github.com/Homebrew/homebrew-core
Core tap HEAD: fe4534448796e38cfb5283c03b19e93450d4d264
Core tap last commit: 47 minutes ago
HOMEBREW_PREFIX: /usr/local
HOMEBREW_REPOSITORY: /usr/local
HOMEBREW_CELLAR: /usr/local/Cellar
HOMEBREW_BOTTLE_DOMAIN: https://homebrew.bintray.com
CPU: quad-core 64-bit haswell
Clang: 7.3 build 703
Perl: /usr/bin/perl
Python: /usr/bin/python
Ruby: /usr/bin/ruby => /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/bin/ruby
Java: 1.8.0_92
System Ruby: 2.0.0-p648
OS X: 10.11.4-x86_64
Xcode: 7.3.1 => /Applications/Xcode7.3.1.app/Contents/Developer
CLT: <IP_ADDRESS>.1.1461711523
X11: N/A
brew doctor
Please note that these warnings are just used to help the Homebrew maintainers
with debugging if you file an issue. If everything you use Homebrew for is
working fine: please don't worry and just ignore them. Thanks!
Warning: Unbrewed dylibs were found in /usr/local/lib.
If you didn't put them there on purpose they could cause problems when
building Homebrew formulae, and may need to be deleted.
Unexpected dylibs:
/usr/local/lib/libusb-1.0.0.dylib

Are you sure this is a Homebrew issue and not an issue with this installed manually outside Homebrew too?

Just downloaded android-sdk_r24.4.1-macosx.zip, same outcome, sorry about that will close this.
I've raised it here as well:
https://code.google.com/p/android/issues/detail?id=210223&q=fabio&colspec=ID Status Priority Owner Summary Stars Reporter Opened


DG check

[x] Chuan Hao
[x] Guguz
[x] Jerome
[x] Nicole
[x] Yunpeng

Our Acknowledgement section is empty.
I have some reuse code so I think I can add something here.

We could delete the Setting up, getting started part
#Design puml tip is probably not meant to be there.
links are all incorrect. for example, Line 39 Main has two classes called Main and MainApp. links to the se-edu Main and MainApp etc.
Font size of some PUML files, e.g. delete, edit sequence diagrams, are too small. can look into editing the css to make the side margins thinner?
Line 110 PUML references AddressBookParser
line 119 diagram is now too small due to us having too many attributes. May have to increase width in inline <img> tag.
line 131 width too low
line 140 image references JsonAdaptedTag, should be JsonAdaptedSkill
line 187 activity diagram too small
Line 194, image filename not updated, should be images/EditAllSequenceDiagram.png.
Line 206, need an extra newline, GFMD is joining the lines
Line 221, should be of all fields
{More to be added} near the end can probably be removed
Private contact detail in glossary never used
line 563 more test cases
line 581  edit references delete
line 618-620 not updated

[ ] shows fine on web but its shown on the md file from guthub

[ ] links to all such webs are not working

[ ] Therefore, with the above consideration and the fact that different applicants sharing same name is relatively rare case. We decided to proceed with alternative 1. change to Therefore, with the above consideration and the fact that different applicants sharing same name is relatively rare case, we decided to proceed with alternative 1.

[ ] a new line to start from As internship ...

[ ] edit all features recommended to split into multiple graphs

[ ] graph for edit all features to be enlarged

[ ] sequence diagram for edit all feature is broken

[ ] a new line to start for the second aspect

[ ] delete all feature:  to be split into different paragraphs

[ ]
change to
The filter mechanism is facilitated by FilterCommandParser. FilterCommandParser produces a FilterApplicantDescriptor, which in turn helps to create a FilterCommand.

[ ]

capitalise the S in set

[ ] user stories to add in filter/redo/undo/editall/delete all

[ ] use cases to add in filter

[ ] non functional requirements have the line "more to be added" to be deleted before final submission

Line 119: References address book

Line 138: References address book


⚠ AGEG website (prod) has degraded performance

In 2b0faa7, AGEG website (prod) (https://www.ageg.ca/) experienced degraded performance:

HTTP code: 200
Response time: 2151 ms

Resolved: AGEG website (prod) performance has improved in c648901.


⚠ Bofrost.de has degraded performance

In 08b0214, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1244 ms

Resolved: Bofrost.de performance has improved in 77fbd1c after 1 hour, 3 minutes.


Some errors occured in training

I followed the Tutorial of aishell, errors occured in  bash run.sh --stage 4 --stop-stage 5 step
run.sh: init method is file:///home/dapeng/PycharmProjects/wenet/examples/aishell/s0/exp/sp_spec_aug/ddp_init
  File "wenet/bin/train.py", line 81
    collate_func = CollateFunc(**configs['collate_conf'],
                                                        ^
SyntaxError: invalid syntax
do model average and final checkpoint is exp/sp_spec_aug/avg_10.pt
Traceback (most recent call last):
  File "wenet/bin/average_model.py", line 7, in <module>
    import yaml
ImportError: No module named yaml
  File "wenet/bin/recognize.py", line 87
    test_collate_func = CollateFunc(**test_collate_conf, cmvn=args.cmvn)
                                                       ^
SyntaxError: invalid syntax
  File "wenet/bin/recognize.py", line 87
    test_collate_func = CollateFunc(**test_collate_conf, cmvn=args.cmvn)
                                                       ^
SyntaxError: invalid syntax
  File "  File "wenet/bin/recognize.pywenet/bin/recognize.py", line ", line 8787

        test_collate_func = CollateFunc(**test_collate_conf, cmvn=args.cmvn)
test_collate_func = CollateFunc(**test_collate_conf, cmvn=args.cmvn)
                                                                                ^
^
SyntaxErrorSyntaxError: : invalid syntaxinvalid syntax

Traceback (most recent call last):
  File "tools/compute-wer.py", line 365, in <module>
    with codecs.open(hyp_file, 'r', 'utf-8') as fh:
  File "/usr/lib/python2.7/codecs.py", line 898, in open
    file = __builtin__.open(filename, mode, buffering)
IOError: [Errno 2] No such file or directory: 'exp/sp_spec_aug/test_ctc_prefix_beam_search/text'
Traceback (most recent call last):
  File "tools/compute-wer.py", line 365, in <module>
    with codecs.open(hyp_file, 'r', 'utf-8') as fh:
  File "/usr/lib/python2.7/codecs.py", line 898, in open
    file = __builtin__.open(filename, mode, buffering)
IOError: [Errno 2] No such file or directory: 'exp/sp_spec_aug/test_attention_rescoring/text'
Traceback (most recent call last):
  File "tools/compute-wer.py", line 365, in <module>
Traceback (most recent call last):
    with codecs.open(hyp_file, 'r', 'utf-8') as fh:
  File "tools/compute-wer.py", line 365, in <module>
  File "/usr/lib/python2.7/codecs.py", line 898, in open
    with codecs.open(hyp_file, 'r', 'utf-8') as fh:
  File "/usr/lib/python2.7/codecs.py", line 898, in open
    file = __builtin__.open(filename, mode, buffering)
IOError: [Errno 2] No such file or directory: 'exp/sp_spec_aug/test_ctc_greedy_search/text'
    file = __builtin__.open(filename, mode, buffering)
IOError: [Errno 2] No such file or directory: 'exp/sp_spec_aug/test_attention/text'

I created a python3 environment named wenet, and I change source $ANACONDA_ROOT/bin/activate py3 in path.sh to source $ANACONDA_ROOT/bin/activate wenet.
I have installed pyyaml in my environment, but it still occurred ImportError: No module named yaml and I found py2.7 in the error message. It seems that my environment had not sourced correctly.

the first issue is a bug that we have fixed, and you can pull main branch code again.
the second one, may be you can check whether path $ANACONDA_ROOT/bin has "activate".If you use a python3 environment named wenet, maybe you can try "conda activate wenet"  to run your environment.

the first issue is a bug that we have fixed, and you can pull main branch code again.
the second one, may be you can check whether path $ANACONDA_ROOT/bin has "activate".If you use a python3 environment named wenet, maybe you can try "conda activate wenet" to run your environment.

I have noticed #33 and pull the latest main branch code, but the error still appears：
run.sh: init method is file:///home/dapeng/PycharmProjects/wenet/examples/aishell/s0/exp/sp_spec_aug/ddp_init
  File "wenet/bin/train.py", line 81
    collate_func = CollateFunc(**configs['collate_conf'],
                                                                                ^
SyntaxError: invalid syntax

This bug is different from #33 , which is:
 KeyError: 'spec_aug_conf'

perhaps it was caused by your environments. You can make sure your running python version, we use python3, while your error maybe caused by wrong python version 2

if you use kaldi  ,you should comment the following line   in  file    kaldi/tools/env.sh ,which change your python to python2.7
#export PATH=/root/data/tools/kaldi/tools/python:${PATH}
export PATH=$PATH:/root/data/tools/kaldi/tools/kaldi_lm
export IRSTLM=/root/data/tools/kaldi/tools/irstlm
export PATH=${PATH}:${IRSTLM}/bin
#export PATH=/root/data/tools/kaldi/tools/python:${PATH}
export LIBLBFGS=/root/data/tools/kaldi/tools/liblbfgs-1.10
export LD_LIBRARY_PATH=${LD_LIBRARY_PATH:-}:${LIBLBFGS}/lib/.libs

if you use kaldi ,you should comment the following line in file kaldi/tools/env.sh ,which change your python to python2.7
#export PATH=/root/data/tools/kaldi/tools/python:${PATH}
export PATH=$PATH:/root/data/tools/kaldi/tools/kaldi_lm
export IRSTLM=/root/data/tools/kaldi/tools/irstlm
export PATH=${PATH}:${IRSTLM}/bin
#export PATH=/root/data/tools/kaldi/tools/python:${PATH}
export LIBLBFGS=/root/data/tools/kaldi/tools/liblbfgs-1.10
export LD_LIBRARY_PATH=${LD_LIBRARY_PATH:-}:${LIBLBFGS}/lib/.libs

Thank you for your reply! It works.

Thank you!!!!!!!!!!!!!!!!!!!


chore: drop net7.0 from Playwright.CLI

We don't plant to release a new version anymore but this produced the following warning:
    /usr/local/share/dotnet/sdk/9.0.100/Sdks/Microsoft.NET.Sdk/targets/Microsoft.NET.EolTargetFrameworks.targets(32,5): warning NETSDK1138: The target framework 'net7.0' is out of support and will not receive security updates in the future. Please refer to https://aka.ms/dotnet-core-support for more information about the support policy.

We don't plant to release a new version anymore but this produced the following warning:

Why touch it if it does not matter? 😄

net6.0 is also out of support now https://devblogs.microsoft.com/dotnet/dotnet-6-end-of-support/


Implement some of module.parent

Summary
See #4567. This leaves out id and exports, but it implements require (which I need, and is my motivation for doing this) and filename which should be enough for require-dir to work.

Test plan
New tests added

I did not know module.require was a thing. I don't like that it exists :(

id is the same as filename so added that as well.
Not sure if exports is worth it unless we can just attach the actual parent module to localModule.parent?

I tried to set localModule.parent now to something from the module cache. Doesn't work properly though.
The first test provides module.parent to modules fails, which I think is correct. Entrypoints don't have a parent so the test is faulty.
The second one makes me kinda sad though. It seems to be one layer to high in the hierarchy. Any ideas?

Hmm, yeah I don't think I really want to support exposing a runtime for the parent module in Jest. If we wanna add this, could we make it a lazy getter, so that it is only executed when somebody actually accesses module.require?

Wait, my analysis is off. Since I do module.parent.require the failure actually correct, and my initial implementation was wrong.

If we wanna add this, could we make it a lazy getter, so that it is only executed when somebody actually accesses module.require?

It's already exposed:
https://github.com/facebook/jest/blob/c44d2c65ea799e4e91b6c22a4beb6028d14149e5/packages/jest-runtime/src/index.js#L523

Yeah, but you are re-creating the runtime for the parent module in your diff, and I was proposing either not to do that and re-use the existing one, or creating it lazily.

Codecov Report

Merging #4614 into master will decrease coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #4614      +/-   ##
==========================================
- Coverage   56.17%   56.16%   -0.01%
==========================================
  Files         194      194
  Lines        6544     6543       -1
  Branches        3        3
==========================================
- Hits         3676     3675       -1
  Misses       2867     2867
  Partials        1        1

Impacted Files
Coverage Δ

packages/jest-runtime/src/index.js
85.03% <100%> (-0.06%)
:arrow_down:

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 c44d2c6...32ba23c. Read the comment docs.

Yes

I've confirmed using node that the current behavior is correct.
$ cd packages/jest-runtime/src/__tests__/test_root
$ node -p "require('./inner_parent_module').outputString"
This should happen
$ node -p "require('./inner_parent_module').parentFileName"
/Users/simen/Development/jest/packages/jest-runtime/src/__tests__/test_root/inner_parent_module.js

Actually one thing is wrong, module.parent should be null not undefined for entrypoints.
test-file.js:
console.log(module.parent);

$ node test-file.js
null
$ node -p "require('./test-file')"
Module {
  id: '[eval]',
  exports: {},
  parent: undefined,
  filename: '/Users/simen/Development/jest/[eval]',
  loaded: false,
  children:
   [ Module {
       id: '/Users/simen/Development/jest/test-file.js',
       exports: {},
       parent: [Circular],
       filename: '/Users/simen/Development/jest/test-file.js',
       loaded: false,
       children: [],
       paths: [Array] } ],
  paths:
   [ '/Users/simen/Development/jest/node_modules',
     '/Users/simen/Development/node_modules',
     '/Users/simen/node_modules',
     '/Users/node_modules',
     '/node_modules' ] }
{}

Nice work @SimenB.


Add custom_logger for script/delayed_job

When script/delayed_job run, assigns custom_logger to Delayed::Worker.logger.
I add cattributes :custom_logger in Delayed::Worker
custom_logger settings is following:
# config/initializers/delayed_job_config.rb
Delayed::Worker.custom_logger = Syslogger.new("app_name", Syslog::LOG_PID, Syslog::LOG_LOCAL2)

Yes, you're right, and my pull request is wrong... I also think your idea is great.
Can I change pull request with your idea?

Sure. We should have this capability.

Thanks a lot. I try it.

I squashed commit, ok?
Should I leave history?

Merged. Welcome to the contributor list.

Thanks a lot @betamatt . I will write wiki about logger setting.


terraform-bridge required list becomes Optional in lyra

Describe the bug
The terraform-bridge seems to convert a Required List to an Optional[Object], rather than an Object.
The case in question is Mysql_server.sku ("azurerm_mysql_server")
Which generates as
    Mysql_server => {
      annotations => {
....
        }
      },
      attributes => {
.....
        'resource_group_name' => String,
        'sku' => Optional[Object[{
            attributes => {
              'capacity' => Integer,
              'family' => String,
              'name' => String,
              'tier' => String
            }
          }]],
....
      }
    },

(note Optional[Object)
So we end up with a runtime error instead of a validation error, even though terraform marks the type as mandatory.
To Reproduce
Run make generate and observe build/types/AzureRM.pp (to see the type definition)
Run a workflow with this action:
https://github.com/ahpook/lyra-local/blob/90b646b723b33d7eee514478e729acbb17fa295b/workflows/azure_wordpress.yaml#L23-L30
Expected behavior
Validation that sku is mandatory, rather than attempt to apply the workflow.
Logs

Runtime error
2019-05-15T10:50:16.723+0200 [ERROR] lyra: apply failed: Error="error while executing resource 'azure_wordpress::mysql_server' (file: workflows/azure_wordpress.yaml)
 at /Users/dimitri.tischenko/go/pkg/mod/github.com/lyraproj/wfe@v0.0.0-20190514150706-fc1fa286c815/wfe/workflowengine.go:492 (github.com/lyraproj/wfe/wfe.(*workflowEngine).runStepCatch.func1)
 at /usr/local/Cellar/go/1.11.4/libexec/src/runtime/asm_amd64.s:522 (runtime.call32)
 at /usr/local/Cellar/go/1.11.4/libexec/src/runtime/panic.go:513 (runtime.gopanic)
 at /Users/dimitri.tischenko/go/pkg/mod/github.com/lyraproj/servicesdk@v0.0.0-20190514145959-5467213bbd8f/grpc/client.go:59 (github.com/lyraproj/servicesdk/grpc.(*Client).Invoke)
 at /Users/dimitri.tischenko/go/pkg/mod/github.com/lyraproj/wfe@v0.0.0-20190514150706-fc1fa286c815/service/crud.go:133 (github.com/lyraproj/wfe/service.ApplyState)
 at /Users/dimitri.tischenko/go/pkg/mod/github.com/lyraproj/wfe@v0.0.0-20190514150706-fc1fa286c815/wfe/resource.go:67 (github.com/lyraproj/wfe/wfe.(*resource).Run)
 at /Users/dimitri.tischenko/go/pkg/mod/github.com/lyraproj/wfe@v0.0.0-20190514150706-fc1fa286c815/wfe/workflowengine.go:527 (github.com/lyraproj/wfe/wfe.(*workflowEngine).runStepCatch)
 at /Users/dimitri.tischenko/go/pkg/mod/github.com/lyraproj/wfe@v0.0.0-20190514150706-fc1fa286c815/wfe/workflowengine.go:431 (github.com/lyraproj/wfe/wfe.(*workflowEngine).runStep)
 at /Users/dimitri.tischenko/go/pkg/mod/github.com/lyraproj/wfe@v0.0.0-20190514150706-fc1fa286c815/wfe/workflowengine.go:407 (github.com/lyraproj/wfe/wfe.(*workflowEngine).stepWorker)
 at /Users/dimitri.tischenko/go/pkg/mod/github.com/lyraproj/wfe@v0.0.0-20190514150706-fc1fa286c815/wfe/workflowengine.go:321 (github.com/lyraproj/wfe/wfe.(*workflowEngine).Run.func2)
 at /Users/dimitri.tischenko/go/pkg/mod/github.com/lyraproj/pcore@v0.0.0-20190514082225-61649d71c936/px/context.go:175 (github.com/lyraproj/pcore/px.Fork.func1)
Caused by: rpc error: code = Unknown desc = runtime error: index out of range (file: workflows/azure_wordpress.yaml)"

See https://gist.github.com/timidri/3cc99447ac588b3b2c9db4869034f6e6 for full log
Environment (please complete the following information):

Latest

Additional context

The full Mysql_server type
    Mysql_server => {
      annotations => {
        Lyra::Resource => {
          'providedAttributes' => ['mysql_server_id', 'fqdn', 'tags'],
          'immutableAttributes' => ['administrator_login', 'location', 'name', 'resource_group_name', 'version']
        }
      },
      attributes => {
        'mysql_server_id' => Optional[String],
        'administrator_login' => String,
        'administrator_login_password' => String,
        'fqdn' => Optional[String],
        'location' => String,
        'name' => String,
        'resource_group_name' => String,
        'sku' => Optional[Object[{
            attributes => {
              'capacity' => Integer,
              'family' => String,
              'name' => String,
              'tier' => String
            }
          }]],
        'ssl_enforcement' => String,
        'storage_profile' => Optional[Object[{
            attributes => {
              'backup_retention_days' => Optional[Integer],
              'geo_redundant_backup' => Optional[String],
              'storage_mb' => Integer
            }
          }]],
        'tags' => Optional[Hash[String, String]],
        'version' => String
      }
    },

The terraform-bridge concludes that while the intermediate list is indeed required, it doesn't declare MinItems: 1  which means that it is permissible to provide a list with zero or one entry in it. The generation is therefore in accordance with the schema.

Terraform does apply validation for this case.
➜  tfplanfun ls ../tfplanfun
mysql_azure.tf
➜  tfplanfun terraform apply

Error: azurerm_mysql_server.test: "sku": required field is not set

➜  tfplanfun

mysql_azure.tf
```
resource "azurerm_resource_group" "test" {
  name     = "api-rg-pro"
  location = "West Europe"
}
resource "azurerm_mysql_server" "test" {
name                = "mysql-server-1"
location            = "${azurerm_resource_group.test.location}"
resource_group_name = "${azurerm_resource_group.test.name}"
sku {
name     = "B_Gen5_2"
capacity = 2
tier     = "Basic"
family = "Gen5"
capacity = "2"
}
storage_profile {
storage_mb            = 5120
backup_retention_days = 7
geo_redundant_backup  = "Disabled"
}
administrator_login          = "mysqladminun"
administrator_login_password = "H@Sh1CoR3!"
version                      = "5.7"
ssl_enforcement              = "Enabled"
}

[source](https://www.terraform.io/docs/providers/azurerm/r/mysql_server.html)
<details>

I don't doubt that it's required in practice. I'm just stating that it isn't required in the schema, hence the generated optional. I'd consider this a schema bug (I bet there are many more similar inconsistencies).
One option is that we try to rectify such mistakes in our code, but I don't know how to find a good list or how to maintain it over time.

I wonder if it as general issue such as Terraform assumes a Required List to mean a List of at least one item.

There are entries with both Required: true and MinItems: 1 in the aws schema and there are them that lacks this definition. Examples: aws/appmesh_route and azurerm/sku. We can of course treat them equal but it would be nice to get a confirmation that such a rule should be applied. The normal assumption would be that if you don't specify a constraint (like MinItems here), then it shouldn't apply.

This is a great example of why I think it's better to integrate with the terraform runtime instead of the providers; we should be able to execute tf directly with an existing plan. IMO it's not worth spending the time to fix or avoid this problem.


Ghost and Colour difference

HI
Thank you for your opened code.  I used your code for stitching image, and Imet the problem of ghost and color difference.
How i should do ?
thanks

Currently there is no mechanism in the code to handle ghost caused by moving object or different gain between images (if that's what you mean by color difference).
If the ghost is not on moving object, then it's a stitching quality problem and would need to be diagnosed case-by-case.

yes,i have run the job on my windows vs2015,but it have ghost heavily!
you can have a look at your result demo ,also have some ghost.
thanks

When you're taking photos at close object (within several meters), try to make sure the camera lens doesn't move at all, as best as you can.
Moving the camera lens would break the geometry assumption of the algorithm. But since you cannot perfectly fix it so ghost is inevitable. It's just for distant objects the ghost won't be as serious.


Bad exit value for the command

The command always end with a 0 exit code, even if the tests failed.
Is it possible to have it return an error code if necessary, as using atoum directly I would guess?

@maxailloud https://github.com/atoum/AtoumBundle/releases/tag/1.4.1

I'll need packagist to get the new tag but thank for the quick respond.

Sorry @maxailloud, packagist did not auto-update. I triggered the update manually, the tag is no available there ;)


Change Mustache context key of recipient email address

It was profile.emailAddress, it is now recipient.emailAddress.
This requires a change to the template footer on S3. Will do that now.
Also bump comms-kafka-messages

This PR was successfully deployed to production by CircleCI build 85 at 2016-12-12 13:42 GMT.


[PostgreSQL integration] CreateNote needs to generate and persist unique ID

Expected Behavior
On CreateNote(), a unique ID is generated and persisted for each Note.
Actual Behavior
The ID field is null.
Steps to Reproduce the Problem
Bring up Grafeas with PostgreSQL described in grafeas-pgsql, and try to insert an occurrence. See instructions on how to create them.
Additional info
From local PostgreSQL logs:
Postdb_1      | 2019-06-24 20:34:59.765 UTC [72] ERROR:  null value in column "note_id" violates not-null constraint
db_1      | 2019-06-24 20:34:59.765 UTC [72] DETAIL:  Failing row contains (1, occurrence_example, test, name: "projects/occurrence_example/occurrences/test"
db_1      | 	resource: <..., null).
db_1      | 2019-06-24 20:34:59.765 UTC [72] STATEMENT:  INSERT INTO occurrences(project_name, occurrence_name, note_id, data)
db_1      | 	                      VALUES ($1, $2, (SELECT id FROM notes WHERE project_name = $3 AND note_name = $4), $5)
server_1  | 2019/06/24 20:34:59 Failed to insert Occurrence in database pq: null value in column "note_id" violates not-null constraint
server_1  | 2019/06/24 20:54:03 Failed to insert Occurrence in database pq: null value in column "note_id" violates not-null constraint
db_1      | 2019-06-24 20:54:03.541 UTC [71] ERROR:  null value in column "note_id" violates not-null constraint

CreateNote should not generate IDs, the create note request from the API def requires the user specify an ID for the note. Occurrences on the other hand, have their IDs generated.

This is about an internal ID column that's generated and used for indexing in PG.

I would like to work on it

@VishalVinayRam ok great! Please send the PR to the maintainers team when ready.


[berkeley] Fix crash on double-bootstrap

This PR is https://github.com/MinaProtocol/mina/pull/14990 against berkeley

!ci-build-me

!approved-for-mainnet


Add suport for .sv extension

Needed for https://github.com/phanrahan/magma/issues/880
Allows the user to choose .sv as an output.  In the future, we should
consider forcing the disable-ndarray option when .v is used (i.e.
choosing .sv enables this feature since it should be compatible with
tools that support .sv).   However, for backwards compatability, I
think we should leave the behavior as is (or else various downstream
users will have different code generated by default since everyone is
using .v right now but some are expected the ndarray feature enabled
for .v).

When we update magma to choose .sv versus .v depending on whether ndarray is enabled, I think we can make the change here to disable ndarray for .v

Looks like there is some call that is missing the outExt parameter causing the failing CI. Alternatively you could have a default value.


Re-PR add stm32h755II chip

@acassis
@davids5
we made PR again.
・Add new CONFIG_STM32H7_PWR_LDO_SUPPLY macro to "Kconfig".
・Delete "stm32h7x5xx_rcc.c" and add ONFIG_STM32H7_PWR_LDO_SUPPLY macro to "stm32h7x3xx_rcc.c".

@jfbblue0922 Please see https://github.com/nuttx-to-asf/incubator-nuttx/commit/c6cedbaa23161950b18caed94af54b549ef8a4b1
It is the approach I had suggested originally. It adds the LDO mode with a chip the has SMPS. Please cherry-pick it to your branch and test it does what you needed. If it is fine then please squash it and force push.

@davids5
I agree with your method.
I've confirmed that this method works correctly.
Thank you for your help.

@davids5
I agree with your method. I've confirmed that this method works correctly. Thank you for your help.

Great! You are very welcome. Now we just have to get CI to be happy.
Please rebase on current NuttX master and force push.

@jfbblue0922 - hmm Look Like CI is still not happy. @xiaoxiang781216 Any ideas what it broken?

ci break is fixed one week ago, @jfbblue0922  please rebase your patch to the latest master.

@davids5
@xiaoxiang781216
I rebased and pushed but nothing changed.
What should we do?

@jerpelea
I changed it from HAS_PWR_DIRECT_SMPS_SUPPLY to STM32H7_HAVE_PWR_DIRECT_SMPS_SUPPLY
and I rebased onto the current NuttX master and force pushed.

@jerpelea
I changed it from HAS_PWR_DIRECT_SMPS_SUPPLY to STM32H7_HAVE_PWR_DIRECT_SMPS_SUPPLY and I rebased onto the current NuttX master and force pushed.

if you check the patch there is no commit message
you can reuse the same message as the one it PR
git commit --amend
type the message and save
git push -f
this will update the current patch without the need to abort it
Best regards
Alin


Add .gyb extension to test filename

Adds a filename extension with no other changes.

Could you please submit this change to master branch instead of tensorflow branch?
master is the source of truth for almost all AutoDiff code now, including test/AutoDiff/stdlib/differential_operators.swift. Changes to master will naturally be merged to tensorflow every week.
If you need this patch urgently on tensorflow branch, you can submit PRs to both master and tensorflow branch.


Change the data type of data inserted into the db from uint64 to int64

What this PR does / why we need it:
This PR changes uint64 to int64 among the data types of data inserted into the db.
https://pkg.go.dev/go.mongodb.org/mongo-driver/bson#hdr-Native_Go_Types
According to the above document, uint64 is marshaled to int64, when marshalling a D or M to BSON.
Therefore, there is no problem in the case of a number smaller than math.MaxInt64 even now, however changing this can make the data types more consistent.
Which issue(s) this PR fixes:

Fixes #373
Special notes for your reviewer:
Changes two data's data type, ServerSeq and Lamport, which are uint64 data inserted into the db.
There are other uint64 data, but they don't seem to be inserted into the db, so I haven't modified them.
Does this PR introduce a user-facing change?:

NONE

Additional documentation:

Checklist:

[x] Added relevant tests or not required
[x] Didn't break anything

Continue on #381.


Add counting members to join/leave messages

Can you add counting members to join/leave messages? For example I want to write Welcome user! You are 7-th member on server or User has left the server. We now have 3135 users.

[[ .Guild/Server.MemberCount }} already does that.


I want to add Java Program to demonstrate the use of If else-if ladder using grading System

Languages

[x] Java

@kn0wabhi Where is the whole issue template??


Standardise errors

Standardise errors and error handling based on this proposal.

/assign

Closing as a duplicate of https://github.com/dapr/dapr/issues/6068


[Bug] International characters garbled in some messages

Example:

In some other messages on the same account (so I guess it is dependent on the sender and the client they use, not on the main.conf file), characters with accents are correctly displayed:

Yes, it looked OK for me when viewed in another client, but nmail had issues with it. Since I forwarded the messages to you using another client, maybe the issue did not show up if that client somehow re-encoded it.
I sent you another example from nmail this time. Can you confirm you received it? The draft was deleted after sending but I got a "Move message failed" error, and no message in sent mails.

Thanks, I can confirm I received it. However I'm afraid I will need the original email/encoding to efficiently determine what is going wrong. I'll look at adding the save/export message functionality.

Good to know still. The email also appeared in the sent folder, eventually. I'll wait for the export functionality. It would be an interesting feature anyway, not just for debugging, but also to have header details and information about smtp servers and so on.

I've implemented support for exporting raw email message in #30 - just press E when viewing an email.
Please help to export the email message which viewed incorrectly for you and send the file to me (via email or attach here), it will make it more straight-forward for me to reproduce and debug. Thanks!

Hi @Kabouik - I know you're busy and also facing more serious bugs using nmail, but I just wanted to send a reminder to help export an email and share with me, whenever you find time. Thanks :)

I'm sorry for opening issues and then being a bit light on troubleshooting. I postponed this for too long.
I'm sending you a couple exported emails (those in the screenshots above). Also, more recently, I realized some emails show international characters correctly as plain text, but garble them again when viewed as html in browser or in nmail using lynx (sending that too).

Hi @Kabouik - Thanks a lot for sharing the email examples.
I have analyzed a couple of them, more specifically 5_22121.eml sent to me on 2020-04-01 and 20944.eml sent to me on 2020-03-30.
These two emails both only have html-parts (no plain text part).
The html part for 5_22121.eml indicates charset=Windows-1252 in its html-header meta-tag. However interpreting it as Windows-1252 gives several "weird" characters (both using lynx and also when opening the file in a proper web-browser Google Chrome). If I however change the header to say utf-8 the file can be correctly converted to text by lynx (and viewed in Google Chrome).
The html part for 20944.eml indicates charset=iso-8859-1 in its html-header meta-tag. However interpreting it as iso-8859-1 gives several "weird" characters (both in lynx and Google Chrome). However if I manually modify the html header to say utf-8 it can be correctly viewed in Chrome, and correctly converted using lynx.
Based on the above investigation I believe these emails are wrongly encoded (alt. has wrong header), and thus I don't think there is anything that can be fixed.
But if you know of any email client that is able to display these emails the way you expect, please let me know. But my feeling is that the best a client can do is to abide to the encoding info provided in the file header.

Hi @d99kris, thanks for looking into that this thoroughly.
I am pretty sure those emails show correct characters when viewed directly in the Outlook web app (but meh, right). I just checked in Mailspring, they also display correctly. In both cases, however, the default view is HTML. In Mailspring, there is a hidden button that allows showing the raw email (similar to the .eml from nmail). I checked the raw message in Mailspring for the email that corresponds to 5.22121.eml, and I can confirm the international characters are correctly displayed. Here is the header:
Received: from [redacted] with Microsoft SMTP Server (TLS)
 id 15.0.1395.4 via Mailbox Transport; Wed, 1 Apr 2020 15:14:59 +0200
Received: from [redacted] with Microsoft SMTP Server (TLS)
 id 15.0.1395.4; Wed, 1 Apr 2020 15:14:59 +0200
Received: from [redacted] with Microsoft SMTP Server (TLS) id 15.0.1395.4; Wed, 1 Apr
 2020 15:14:59 +0200
Subject: =?UTF-8?Q?Fwd=3a_Baisse_de_biodiversit=c3=a9_et_coronavirus_=28inte?=
 =?UTF-8?Q?rvention_de_ [redacted]
References: [redacted]
To: [redacted]
From: [redacted]
X-Forwarded-Message-Id: [redacted]
Message-ID: [redacted]
Date: Wed, 1 Apr 2020 15:14:56 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101
 Thunderbird/68.6.0
In-Reply-To: [redacted]
Content-Type: multipart/mixed;
	boundary="------------27BF9F6938AB8F6A2A4F795E"
Content-Language: fr
Return-Path: [redacted]
X-MS-Exchange-Organization-AuthSource: [redacted]
X-MS-Exchange-Organization-AuthAs: Internal
X-MS-Exchange-Organization-AuthMechanism: 00
X-Originating-IP: [<IP_ADDRESS>]
X-ClientProxiedBy: [redacted]
X-MS-Exchange-Organization-Network-Message-Id: 0e923246-6f93-4314-a724-08d7d63eadfc
X-MS-Exchange-Organization-AVStamp-Enterprise: 1.0
MIME-Version: 1.0

--------------27BF9F6938AB8F6A2A4F795E
Content-Type: multipart/alternative;
	boundary="------------019299122F2C78E1692E6228"

--------------019299122F2C78E1692E6228
Content-Type: text/plain; charset="windows-1252"; format=flowed
Content-Transfer-Encoding: 8bit

I redacted a lot of information containing names or email addresses, sorry about that (please let me know if I forgot something), but it does show `charset="windows-1252" as you mentioned, yet the content is right. The subject, however, is wrong, as you can see above. The subject is OK in the non-raw message:

This is just a guess, but I expect the characters to appear correctly in Thunderbird and Outlook too, since the colleagues involved in this email discussion use either of these clients.

Thanks for the quick reply! Okay, I'll check out Mailspring and maybe Thunderbird on my side.

The colleagues in the discussion might have been using OWA too.

I received other emails with charset="iso-8859-1" since then (probably charset="Windows-1252" too) and I can confirm they display correctly in Mailspring and OWA; I have not tested Thunderbird but I suspect it would work too or I would have heard colleagues complaining about it. This seems to happen mostly (only?) with emails that contain only html parts.
I tried exporting one email with iso-8859-1 and reimporting it after replacing the charset with utf-8. It replaced all weird characters by � in nmail and external html viewer. Interestingly, the same � characters now show up in OWA as well for the imported email, while the original email with iso-8859-1 show correct characters.

This seems to happen mostly (only?) with emails that contain only html parts.

No it does not happen only with emails that contain only html parts. I received another email just now with both plain text and html parts, encoded as iso-8859-1, and it shows wrong characters when viewed with lynx, but correct characters when viewed in plain text.

I tried sending an email to myself using the Outlook web app (OWA), and accents do not display correctly in nmail (they do in the webmail). Surprisingly, nmail displayed the object correctly though, including the accents.

Hi @Kabouik - thanks for reporting the bug and sharing the email examples with me.
I've finally figured out what the issues were, and I believe the should be addressed now.
Please let me know if you still encounter garbled characters in any emails. Thanks!

Awesome, that's well worth a git pull!
I think I can confirm you did solve the issue. I am not 100% sure the emails I checked were all causing the issue with the previous version, but I'll come back here if I ever see it occur again. Thanks a lot, that's a big leap forward for me.

This is a note for myself that I need to send you some other examples, I have come across a situation with a recipient in Ukraine not seeing my messages properly when sent with nmail, but visible when sent using the Disroot webmail. Hew was talking to me in English, so I suspect the issue was with the Cyrillic characters in his name forcing a change in the encoding format. I'll send you the messages but just need to take a few minutes to review them and redact the personal information before sharing.

Sure! Feel free to perhaps log a new issue if it's for sent/outgoing messages, as opposed to received messages. Thanks!
On 2020-09-30 23:11 Kabouik<EMAIL_ADDRESS>wrote:

This is a note for myself that I need to send you some other examples,
I have come across a situation with a recipient in Ukraine not seeing
my messages properly when sent with nmail, but visible when sent using
the Disroot webmail. Hew was talking to me in English, so I suspect the
issue was with the Cyrillic characters in his name forcing a change in
the encoding format. I'll send you the messages but just need to take a
few minutes to review them and redact the personal information before
sharing.
--
You are receiving this because you modified the open/close state.
Reply to this email directly or view it on GitHub:
https://github.com/d99kris/nmail/issues/25#issuecomment-701454509


highlight: 3.52 -> 3.53

Motivation for this change
New release
Things done

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

[x] NixOS (x86_64-linux & aarch64-linux)
[ ] macOS
[ ] other Linux distributions

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

Built and tested locally :+1:


Default behaviour star restart

Whenever the voice user enters * it should return to the main menu

@imsickofmaps Please review.

:+1:


feature-wip add auth&catalog check

Proposed changes
Issue Number: close #xxx
Problem Summary:
Describe the overview of changes.
Checklist(Required)

Does it affect the original behavior: (Yes/No/I Don't know)
Has unit tests been added: (Yes/No/No Need)
Has document been added or modified: (Yes/No/No Need)
Does it need to update dependencies: (Yes/No)
Are there any changes that cannot be rolled back: (Yes/No)

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

hi @AshinGau , please add some details in your PR comment, for example:

What is changed?
How does it effect origin behavior.


Dont show trend data in history period longer than 2d for colected items

Describe the bug
In the case of choosing a collection of multiple data from multiple items, NoData will be displayed. A longer time is set to more than 2d, e.g. 30d. In the case of choosing only one item and a long period of 30 days, the graph will be displayed without any problem.
Expected behavior
The expected behavior is the display of graphs from multiple items in one view for a selected long period of 30 days or more.
Screenshots
Error:

Expected behavior

Software versions

Grafana
Zabbix
Grafana-Zabbix Plugin

11.0.0
6.4.15
4.4.9

same problem, but in my case it still shows 15d when I put it in "relative time" is there anything new to solve this?


Fix textarea

This makes the textarea work with the vercel ai replacement.

Introduces a new class ChatCompletionStream for simple, text only responses in the form of ReadableStream<string>
Rename the low level http parsing class to ChatCompletionTransport for clarity
useMakeStandardAutosuggestionFunction and useMakeStandardInsertionOrEditingFunction have been adapted to make use of this

@ataibarkai please test, for me the textarea demo was working, but I am not sure how to test  useMakeStandardInsertionOrEditingFunction

hey @mme , i addressed the concerns above in this PR:
https://github.com/CopilotKit/CopilotKit/pull/159
Looks good to merge?
Also, for future reference, in the textarea you bring up the insertion/edit box with command+k


MediaInfo incorrectly re-grouping certain MP3 tags

MediaInfo is incorrectly re-packaging some MP3 user tags, and this can cause not only duplicate tags in, for example, JSON or XML output, but it is losing some tag values.
Here's one of the identically named Biography groupings, for example:
               "Biography" : {
                  "URL" : "https://www.allmusic.com/artist/mn0000788138/biography",
                  "short" : "A highly successful record label boss, he signed some huge names from the late 60s through to the 90s."
               },

But the actual tags are, as output by exiftool:
  | UserDefinedText = (AMG Artist Biography) With their heavily orchestrated, sweet bal[snip]
  | UserDefinedText = (AMG Artist Biography (short)) Mellow Australian soft rock group [snip]
  | UserDefinedText = (AMG Artist Biography URL) https://www.allmusic.com/artist/mn0000[snip]
  | UserDefinedText = (AMG Composer Biography) A Harvard Law School graduate, Clive Dav[snip]
  | UserDefinedText = (AMG Composer Biography (short)) A highly successful record label[snip]
  | UserDefinedText = (AMG Composer Biography URL) https://www.allmusic.com/artist/mn00[snip]

Note that the value of "AMG Composer Biography" is lost - only the URL and short values are output.  E.g. AMG Composer Biography (short) and AMG Composer Biography URL.
Second, duplicate "Biography" JSON / XML groupings are created.
It seems MediaInfo is latching onto only the "Biography" portion of the full tag "AMG Artist Biography" or "AMG Composer Biography", creating two identically-named Biography containers and placing the "URL" and "short" values within.   This is entirely wrong, and breaks parsing the JSON or XML due to duplicate tags (e.g. "Biography").
This is occurring with several tags, seemingly because their names share a common root prefix.  In the case of the two Biography variants, MediaInfo seems to think the Artist Biography and Composer Biography are identical.  This is incorrect.

Wow, huge count of tags, thank you.
We'll handle that when we have free time (don't expect soon, this part of the code is messy and with lot of stuff for trying to aggregate correctly different sources).

Yes, indeed.
No hurry.  I discovered it accidentally while testing some of my own code that calls the MediaInfo CLI, used primary for video files.


Updated versions of dependencies

Switched to Android v10.0 and Xamarin.Forms 5.0

@stankonikolic Ready for Android 10 with XF 5.0 😁.

@miki-bgd, tell me that this solves System.Numerics warnings, please!

I would really want to...

For reference:

This build warning will go away when Xamarin transitions to One .NET, which is currently scheduled for .NET 6.

https://developercommunity.visualstudio.com/t/xamarin-found-conflicts-between-different-versions/788505


chore: upgrade Play to v3.0.1

What is the purpose of this change?
This upgrades Play to v3. SBT has also been upgraded to latest.
What is the value of this change and how do we measure success?
Play 3 uses Pekko, so upgrading removes our reliance on Akka.

Looks good!
I think this comment no longer applies as Play 2 was probably the blocker!

Good spot - I've removed both the comment and the workaround which seems to be redundant anyway.


client.bin issue

im using the new version of it and im on win 10
when i want to build  client builder then it says: clud not locate client.bin client.bin should be in the same location as quasar

The file has been deleted by your AV. Please add an exception for the directory. It's a false positive if you downloaded it from here: https://github.com/quasar/Quasar/releases


Ensure sdx-transform-cs meets standards

Changes

Add exceptions for failure to lookup survey schemas from disk
Add exceptions for transformation failure when performing IO operations (ZIP/PDF/Buffer creation).
Add failure and error logging for splunk/docker

How to test

Send a message with invalid survey id within to any of the transformation endpoints. Check appropriate error is logged.
Send invalid data to any of the transform endpoints. Check appropriate error is logged.
Send a valid message payload and check that a success message is logged.

Testing io exceptions is more difficult. Prevent write access to the /tmp directory and run a transform.
Who can test
Anyone but @iwootten

I can't see any tests for the new exception handling. Also, could we add the application name to the logging format in settings.py rather than every log line? This would also help to ensure it is consistently used on every log line.

The error messages are double quoted in the response JSON, e.g.
{
  "message": "'PCK:Unsupported survey/instrument id'",
  "status": 400,
  "uri": "http://localhost:5000/pck"
}

This was down to getting a representation of the exception passed into the default 400, 500 handlers. The case you highlighted was just a string passed in to that method. I've updated these calls to default to using ValueErrors.

It seems a bit unnecessary to have to wrap every error in an exception, only so the message can be pulled out with repr. What about:
@app.errorhandler(400)
def errorhandler_400(e):
    known_error(repr(e))

def known_error(error=None):
    app.logger.error("FAILURE:%s", error)
    message = {
        'status': 400,
        'message':error,
        'uri': request.url,
    }
    resp = jsonify(message)
    resp.status_code = 400

    return resp

And the same for the 500 errors.
Also, I think known_error should be client_error and unknown_error should be server_error.

Sure, I've updated this. It's unnecessary to break the server error in this way as we don't call it with strings and will only be used against flask exceptions.

👍


Add assertions on escrow balance and error codes in transfer relay_test.go for send packet

Summary
see comment. We should add assertions to TestSendTransfer in modules/apps/transfer/keeper/relay_test.go, which asserts that the tokens sent were deducted from the sender account balance and added to the escrow account. If an error is expected, if possible, we should assert the expected error code. If the error code comes from outside of ibc-go, I think it makes sense to simply assert that an error was returned (so as not to be dependent on outside error codes which might change)

For Admin Use

[ ] Not duplicate issue
[ ] Appropriate labels applied
[ ] Appropriate contributors tagged/assigned

@colin-axner Isn't this the same as this?

yes it is!


The up arrow for the Parent Folder doesn't work in workspace

The up arrow for the Parent Folder doesn't work in my workspace. It's highlighted when pointing to it. But it doesn't to anything when clicking on it.

Please give more detail. Which browser. Which folder, is it one you
created? Is it one that existed by default?
Thanks,
Andrew
On Mon, Mar 16, 2015 at 1:52 PM, maovt<EMAIL_ADDRESS>wrote:

The up arrow for the Parent Folder doesn't work in my workspace. It's
highlighted when pointing to it. But it doesn't to anything when clicking
on it.
—
Reply to this email directly or view it on GitHub
https://github.com/PATRIC3/patric3_website/issues/29.

Just found out that it works when double clicking it (not for single clicks)
From: "Andrew Warren"<EMAIL_ADDRESS>To: "PATRIC3/patric3_website"<EMAIL_ADDRESS>Cc: "Chunhong Mao"<EMAIL_ADDRESS>Sent: Monday, March 16, 2015 2:05:06 PM
Subject: Re: [patric3_website] The up arrow for the Parent Folder doesn't work in workspace (#29)
Please give more detail. Which browser. Which folder, is it one you
created? Is it one that existed by default?
Thanks,
Andrew
On Mon, Mar 16, 2015 at 1:52 PM, maovt<EMAIL_ADDRESS>wrote:

The up arrow for the Parent Folder doesn't work in my workspace. It's
highlighted when pointing to it. But it doesn't to anything when clicking
on it.
—
Reply to this email directly or view it on GitHub
https://github.com/PATRIC3/patric3_website/issues/29.

—
Reply to this email directly or view it on GitHub .
--
Chunhong Mao, Ph. D.
Senior Project Associate
Virginia Bioinformatics Institute
Virginia Tech (0477)
1015 Life Science Circle
Blacksburg, VA 24061
Tel:<PHONE_NUMBER>
Fax:<PHONE_NUMBER>


mongodb doc loader init

Description: A Document Loader for MongoDB
Issue: n/a
Dependencies: Motor, the async driver for MongoDB
Tag maintainer: n/a
Twitter handle: pigpenblue

Note that an initial mongodb document loader was created 4 months ago, but the PR was never pulled in.  @leo-gan had commented on that PR, but given it is extremely far behind the master branch and a ton has changed in Langchain since then (including repo name and structure), I rewrote the branch and issued a new PR with the expectation that the old one can be closed.
Please reference that old PR for comments/context, but it can be closed in favor of this one.  Thanks!

@eyurtsev would it be possible for you to take a look at this?  I'm installing 'motor' (the async engine for mongodb) as an optional install, then installing locally with 'poetry install -E all' since it's optional, yet the GitHub Actions don't seem to install dependencies in this way so the checks are failing.  I've tried to copy how other new packages are installed, and I read the CONTRIBUTING.MD and followed those instructions, yet still getting these issues.  thanks!

@saginawj comandeering to resolve merge conflicts


#19 Update for Senzing Python SDK package

Pull request questions
Which issue does this address
Issue number: #19

#18