Use a record-replay deterministic hash for Member types that contain ScriptWrappable objects

https://linear.app/replay/issue/RUN-1665/detect-and-automatically-make-all-instances-of-wtf-set-and-map
This change makes the hash functions that @klochek added the default for Member's that contain subclasses of ScriptWrappable.
Once this and #545 are merged, I can go back through the containers where a record-replay deterministic hash was set manually and validate that the default hash should now have the behavior that we want.

Not quite as clean as I thought, I ended up having to replace a couple of forward declarations with #includes. It doesn't seem like there are cyclic dependencies that were prevented by the forward declarations, so I'm not 100% sure why they were being used.


Bug report: Regex issue with negated character class before end of line

Describe the bug
There appears to be some mistake in the regex matching of the last line of some input, when using a negated character class.
To Reproduce
Input:
abc
de
def
ghi

(Note: cr on last line)
Recipe of Regular expression: User defined: Regex .[^ie]$, (that is, any character, not an i nor e, then the end of the line)
Highlight matches.
Expected behaviour
Expected it to highlight like this:
a<blue>bc<blue />
de
d<yellow>ef<yellow />
ghi

Actually got:
a<blue>bc<blue />
de                                <-- Correctly not highlighted.
d<yellow>ef<yellow />
gh<blue>i<blue />                 <--- Didn't expect this to be highlighted.

Desktop:

OS: Windows 10 Home
Browser: FF 106.0.5, also tried on Edge 107.0.1418.35 (Official build) (64-bit)
CyberChef version: 9.48.0. Also tried with 9.32.3

Other content
Perhaps there is some issue with regex that I am not aware of? Maybe a JS regex engine issue?
But I tried the same regex in Python, and it worked as expected:
import re
s = """abc
de
def
ghi
"""
for line in s.splitlines():
    if re.search(r'.[^ie]$', line):
        print(line)

Output:
abc
def

I don't think this is a bug.
At the end of input, there are characters 'g', 'h', 'i', '\n'.
Therefore, the i is highlignted because . matches 'i', [^ie] matches '\n', and $ matches at the end of input.
In your Python example, s.splitlines() doesn't include '\n' in the result, so this doesn't happen.
>>> import re
>>> s = """abc
... de
... def
... ghi
... """
>>> s
'abc\nde\ndef\nghi\n'
>>> list(s.splitlines())
['abc', 'de', 'def', 'ghi']
>>>

Ahh. Interesting. Yes, you're right about splitlines. But I was still unclear about the de\n "correctly" not being highlighted, when ghi\n is being <strikethrough>incorrectly</strikethrough> highlighted.
I've added my understanding below, to help anyone else stumbling across this issue.
I'm assuming that ticking "^ and $ match at newlines" in CC is the equivalent to Python's re.MULTILINE mode. Python's help says "$ Matches the end of the string or just before the newline at the end of the string, and in MULTILINE mode also matches before a newline" (My emphasis). (I know CC is in JS, but this behaviour appears to be the same).
I think the key word there is "also". So $ is actually hitting twice at the end - once for the end of line, and then again for end of string. Which is why de\n in my example is not being highlighted: $ matches end-of-line, and e is failing the not-i-or-e.
But for ghi\n<end-of-string>, . is matching the i, [^ie] is matching the \n, and $ is matching end-of-string.
This made it clearer for me:
>>> re.findall(r'.[^ie]$', 'abc\nde\ndef\nghi\n', re.MULTILINE)
['bc', 'ef', 'i\n']

So this is not a bug with CyberChef, and the issue can be closed. Thanks for your insights.


Make I/O cce stream to get rid of converters

This is a future placeholder PR, will fill in details shortly
Originally posted by @dpetrisko in https://github.com/black-parrot/black-parrot/pull/893#r676030290

Closing. I/O CCE uses Burst interface, which provides easy conversion to/from WH network.


fix(types): useTexture()

Correctly infer the return type based on the argument.
Note: I would personally have accepted a single string rather than [string] to build a single Texture but that would be a breaking change

@posva you're right, lets keep it like you changed for the moment. I will write it down for a potential v4 in the future.

Thanks for fixing this @posva


Walking Through Doors

According to your testing, does the issue occur with ONLY Immersive Portals mod installed?
Yes
Forge Version
40.1.84
ImmersivePortals Version
1.4.12-mc1.18.2
Latest Log
No idea where the 'logs' folder is and can't post this without filling out this field.
Crash Report (if applicable)
No response
Steps to Reproduce

Create your two portal frames
Ignite a portal (link them, whatever)
Place a door in front of one of the portals
Go to the side that portals you into the back of the door
4b) close the door if it is open
Step a few blocks away from portal
Sprint through portal

What You Expected
Faceplant into the door, or be unable to go through the portal
What Happened Instead
ran through the door as if it wasn't there

Additional Details
((I do not have fabric, so I am unsure as to whether this happens on the fabric version as well))
Please Read and Confirm The Following

[X] I have confirmed this bug can be replicated without the use of Optifine.
[X] I have confirmed the details provided in this report are concise as possible and does not contained vague information (ie. Versions are properly recorded, answers to questions are clear).
[X] I have confirmed this does not happen on the fabric version (If it does please report to here instead).
[X] I have confirmed I'm not using a hybrid server (Magma, Cauldron) or a different (non official) Forge Server release.
[X] I have confirmed this issue is unique and has not been reported already.

Can you reproduce this issue in the latest Fabric version in 1.19.2?

I came to the realization that it's not actually the door that I'm walking through - it's the blocks around the door..
Sometimes this will result in your character being fired off into a random direction. The last encounter that I had with it, prior to discontinuing my use of the mod, resulted in my being fired off so horribly that I wound up under the bedrock floor and, therefore, into the void.
As per whether it can be reproduced in the Fabric version; I answered that in the form to provide the report...

Additional Details
((I do not have fabric, so I am unsure as to whether this happens on the fabric version as well))

That said, the full response to that question is;; I have no idea, I don't use Fabric as most of the mods that I actually like are not available on Fabric.

Can you show a video about this issue? A video could explain things better.

The quality is terrible... 10MB filesize limit really isn't enough for an effective video... Anyway.. Enjoy.
https://user-images.githubusercontent.com/78976418/197364076-95656c96-f1c8-4016-9a9b-95b836bd27bb.mp4

In the latest Fabric version a similar issue can be reproduced but not exactly like the one in video.


Local Redirect Policy results in loopback when socket-LB is disabled

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
PR#13287  was added to prevent the local-redirect service from looping back packets from the service's node-local backend to itself. However, this solution works only when socket load balancing mode is fully enabled (ENABLE_SOCKET_LB_FULL) or when the node local backend uses host network (ENABLE_SOCKET_LB_HOST_ONLY). We would run into the same loopback issue when the local-redirect service uses pod network and we probably need to have a loop prevention logic added in the lxc ebpf code.
cc: @sugangli ,  @liuyuan10 , @aojea
Cilium Version
Client: 1.13.10
Daemon: 1.13.10
Kernel Version
Linux default-byac 6.1.58+ #1 SMP PREEMPT_DYNAMIC Sat Nov  4 14:14:29 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
Kubernetes Version
Client Version: v1.28.5
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.28.3-gke.1203001
Sysdump
No response
Relevant log output
No response
Anything else?
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

cc @aditighag

We would run into the same loopback issue when the local-redirect service uses pod network

Hi! Could you describe your use case: when would you want packets not to be looped back in case of LRP?

Hi @aditighag , we want to use LRP to redirect traffic to Nodelocal DNS on  pod network and be able to send DNS to other DNS service when there is cache miss.  However, we cannot enable socket LB because we want to be compatible with Istio (see this doc we shared with the OSS for more context).  Is there a better way to do it with bpf_lxc only?

we want to use LRP to redirect traffic to Nodelocal DNS on pod network and be able to send DNS to other DNS service when there is cache miss.

Did you follow the guide to set up LRP for the node-local dns use case?
Per the official k8s documentation, when there is a cache miss, the node-local dns pods would send DNS requests to the upstream (cluster) DNS pods. When do you see packets getting looped?

However, we cannot enable socket LB because we want to be compatible with Istio (see this doc we shared with the OSS for more context). Is there a better way to do it with bpf_lxc only?

The datapath code that prevents loop in the socket-lb case has some drawbacks, and we are planning to replace that logic (see issue).

cc @Weil0ng

when there is a cache miss, the node-local dns pods would send DNS requests to the upstream (cluster) DNS pods. When do you see packets getting looped?

The bpf program on the lxc interface translates the request from node-local DNS pod to cluster DNS back to itself here. We probably need a loop back check here before translation.

Here is a repro:

Followed the dev setup gide to set up a kind cluster with cilium 1.14

  cilium version
  cilium-cli: v0.15.20 compiled with go1.21.6 on linux/amd64
  cilium image (default): v1.14.5
  cilium image (stable): v1.14.6
  cilium image (running): 1.14.6

Set up node local DNS from here. The node local DNS would use cluster metadata server as the upstream DNS server (<IP_ADDRESS>  as a proxy for cluster metadata server).

Created a simple pod and updated the DNS server to forward the queries to the cluster metadata server (<IP_ADDRESS>).

cat <<EOF | kubectl apply -f -
apiVersion: v1
kind: Pod
metadata:
  name: pk-pod
spec:
  containers:
    - name: pk-pod
      image: busybox
      command: ["/bin/sh", "-c", "echo 'nameserver <IP_ADDRESS>' > /etc/resolv.conf && sleep 10000"]
EOF

Added a LRP  to steer the reqests to node-local-dns pods

  apiVersion: cilium.io/v2
  kind: CiliumLocalRedirectPolicy
  metadata:
    annotations:
    name: nodelocaldns
    namespace: kube-system
  spec:
    redirectFrontend:
      addressMatcher:
        ip: <IP_ADDRESS>
        toPorts:
        - name: dns
          port: "53"
          protocol: UDP
        - name: dns-tcp
          port: "53"
          protocol: TCP
    redirectBackend:
      localEndpointSelector:
        matchLabels:
          k8s-app: node-local-dns
      toPorts:
      - name: dns
        port: "53"
        protocol: UDP
      - name: dns-tcp
        port: "53"
        protocol: TCP

Trigger a ping command and it works as expected.

kubectl exec pk-pod -- ping -v -c 1 www.google.com
PING www.google.com (<IP_ADDRESS>): 56 data bytes
64 bytes from <IP_ADDRESS>: seq=0 ttl=112 time=1.432 ms

--- www.google.com ping statistics ---
1 packets transmitted, 1 packets received, 0% packet loss
round-trip min/avg/max = 1.432/1.432/1.432 ms

From hubble logs:
hubble observe --pod pk-pod -f
Feb  3 01:54:09.224: default/pk-pod (ID:3296) <> kube-system/nodelocaldns-local-redirect:53 (world) pre-xlate-fwd TRACED (UDP)
Feb  3 01:54:09.224: default/pk-pod (ID:3296) <> kube-system/node-local-dns-24dnm:53 (ID:32364) post-xlate-fwd TRANSLATED (UDP)
Feb  3 01:54:09.224: default/pk-pod:45520 (ID:3296) -> kube-system/node-local-dns-24dnm:53 (ID:32364) to-endpoint FORWARDED (UDP)
Feb  3 01:54:09.224: default/pk-pod:45520 (ID:3296) <> kube-system/node-local-dns-24dnm (ID:32364) pre-xlate-rev TRACED (UDP)
Feb  3 01:54:09.224: default/pk-pod:45520 (ID:3296) <> kube-system/node-local-dns-24dnm (ID:32364) pre-xlate-rev TRACED (UDP)
Feb  3 01:54:09.226: default/pk-pod:45520 (ID:3296) <- kube-system/node-local-dns-24dnm:53 (ID:32364) to-endpoint FORWARDED (UDP)
Feb  3 01:54:09.226: kube-system/node-local-dns-24dnm:53 (ID:32364) <> default/pk-pod (ID:3296) pre-xlate-rev TRACED (UDP)
Feb  3 01:54:09.226: kube-system/nodelocaldns-local-redirect:53 (world) <> default/pk-pod (ID:3296) post-xlate-rev TRANSLATED (UDP)
Feb  3 01:54:09.226: kube-system/node-local-dns-24dnm:53 (ID:32364) <> default/pk-pod (ID:3296) pre-xlate-rev TRACED (UDP)
Feb  3 01:54:09.226: kube-system/nodelocaldns-local-redirect:53 (world) <> default/pk-pod (ID:3296) post-xlate-rev TRANSLATED (UDP)
Feb  3 01:54:09.226: default/pk-pod (ID:3296) -> <IP_ADDRESS> (world) to-stack FORWARDED (ICMPv4 EchoRequest)
Feb  3 01:54:09.228: default/pk-pod (ID:3296) <- <IP_ADDRESS> (world) to-endpoint FORWARDED (ICMPv4 EchoReply)

Edit cilium-config configmap to enable socket LB in host only mode (bpf-lb-sock-hostns-only: "true") and restart the cilium-agent pods.

Trigger a ping command, but now it fails as DNS resolution fails.

kubectl exec pk-pod -- ping -v -c 1 www.google.com
ping: bad address 'www.google.com'
command terminated with exit code 1

From hubble logs:
root@kind-worker:/home/cilium# hubble observe --pod pk-pod -f
Feb  3 01:56:31.292: default/pk-pod:53548 (ID:3296) -> kube-system/node-local-dns-24dnm:53 (ID:32364) to-endpoint FORWARDED (UDP)
Feb  3 01:56:36.777: default/pk-pod:53548 (ID:3296) <- kube-system/node-local-dns-24dnm:53 (ID:32364) to-endpoint FORWARDED (UDP)
Feb  3 01:56:38.855: default/pk-pod (ID:3296) -> <IP_ADDRESS> (world) to-stack FORWARDED (ICMPv4 DestinationUnreachable(Port))

Adding some logs in the bpf_lxc.c i confirmed that the requests from node local dns were getting looped back during service lookup.

The node local DNS would use cluster metadata server as the upstream DNS server (<IP_ADDRESS> as a proxy for cluster metadata server).

I don't follow this. What's "cluster metadata server"? In a standard node-local-dns deployment there is a cluster DNS service and upstream DNS service.
Also, I just noticed that the LRP you've mentioned is incorrect for the node-local dns use case. Please follow this guide to deploy node-local dns and LRP - https://docs.cilium.io/en/latest/network/kubernetes/local-redirect-policy/#node-local-dns-cache.

I don't follow this. What's "cluster metadata server"

Sorry for not big clear with my earlier comment (edited it now).  "cluster metadata server" is a cluster external DNS server.

I just noticed that the LRP you've mentioned is incorrect for the node-local dns use case. Please follow this guide to deploy node-local dns and LRP -  - https://docs.cilium.io/en/latest/network/kubernetes/local-redirect-policy/#node-local-dns-cache

We cannot exactly use the same config because in our setup, pod DNS queries for external URLs (URLs that don't refer to cluster resources) are forwarded directly to the cluster external DNS server bypassing kube-dns.

I just noticed that the LRP you've mentioned is incorrect for the node-local dns use case. Please follow this guide to deploy node-local dns and LRP -  - https://docs.cilium.io/en/latest/network/kubernetes/local-redirect-policy/#node-local-dns-cache

We cannot exactly use the same config because in our setup, pod DNS queries for external URLs (URLs that don't refer to cluster resources) are forwarded directly to the cluster external DNS server bypassing kube-dns.

Ok, this context was missing in the original report. There are still some gaps in your last comment though.
Can you clearly describe the expected connectivity flow? Application pods connect to <IP_ADDRESS> which is a cluster external DNS server. This traffic is redirected to node-local DNS cache pods using the deployed LRP. What happens when the node-local DNS cache can't resolve a DNS request? Does it reach out to upstream kube-dns service?
The hubble flows you've added with and without socket-lb needs some more comments, and I'm not seeing "loopback" packets in the flows.

Adding some logs in the bpf_lxc.c i confirmed that the requests from node local dns were getting looped back during service lookup.

What was the IP address the node-local dns was trying to reach?

What was the IP address the node-local dns was trying to reach?

We want to bypass kube-dns and route external URLs to cluster external DNS server. This is for both normal pods and node local DNS pods.
Below is the sequence:

User pod sends a DNS request for an external URL, and the request is resolved by an cluster external DNS server.
LRP redirects the traffic directed to cluster external DNS server to node-local DNS pod
When node-local DNS pod can't resolve a DNS request, it makes a request to cluster external DNS server
LRP again redirects the traffic back to itself

The hubble flows you've added with and without socket-lb needs some more comments, and I'm not seeing "loopback" packets in the flows.

Including the hubble flow logs for the node-local DNS pod with the setup in https://github.com/cilium/cilium/issues/30558#issuecomment-1925020478. The loopback packets originate from the default address for service loopback <IP_ADDRESS>  .

kubectl exec pk-pod -- ping -c 1 www.google.com
ping: bad address 'www.google.com'
command terminated with exit code 1

hubble observe -f --pod kube-system/node-local-dns-jpxh5
Feb  9 22:44:49.847: <IP_ADDRESS>:34755 (ID:51577) -> kube-system/node-local-dns-jpxh5:53 (ID:51577) to-endpoint FORWARDED (UDP)
Feb  9 22:44:49.847: <IP_ADDRESS>:49049 (ID:51577) -> kube-system/node-local-dns-jpxh5:53 (ID:51577) to-endpoint FORWARDED (UDP)
Feb  9 22:44:49.847: <IP_ADDRESS>:32944 (ID:51577) -> kube-system/node-local-dns-jpxh5:53 (ID:51577) to-endpoint FORWARDED (UDP)
Feb  9 22:44:49.847: <IP_ADDRESS>:52390 (ID:51577) -> kube-system/node-local-dns-jpxh5:53 (ID:51577) to-endpoint FORWARDED (UDP)
Feb  9 22:44:49.847: <IP_ADDRESS>:42290 (ID:51577) -> kube-system/node-local-dns-jpxh5:53 (ID:51577) to-endpoint FORWARDED (UDP)
Feb  9 22:44:49.847: <IP_ADDRESS>:38228 (ID:51577) -> kube-system/node-local-dns-jpxh5:53 (ID:51577) to-endpoint FORWARDED (UDP)
Feb  9 22:44:49.847: <IP_ADDRESS>:35429 (ID:51577) -> kube-system/node-local-dns-jpxh5:53 (ID:51577) to-endpoint FORWARDED (UDP)
Feb  9 22:44:49.847: <IP_ADDRESS>:33449 (ID:51577) -> kube-system/node-local-dns-jpxh5:53 (ID:51577) to-endpoint FORWARDED (UDP)
Feb  9 22:44:49.847: <IP_ADDRESS>:41205 (ID:51577) -> kube-system/node-local-dns-jpxh5:53 (ID:51577) to-endpoint FORWARDED (UDP)
Feb  9 22:44:49.847: <IP_ADDRESS>:40057 (ID:51577) -> kube-system/node-local-dns-jpxh5:53 (ID:51577) to-endpoint FORWARDED (UDP)
Feb  9 22:44:49.848: <IP_ADDRESS>:58018 (ID:51577) -> kube-system/node-local-dns-jpxh5:53 (ID:51577) to-endpoint FORWARDED (UDP)
Feb  9 22:44:49.848: <IP_ADDRESS>:53857 (ID:51577) -> kube-system/node-local-dns-jpxh5:53 (ID:51577) to-endpoint FORWARDED (UDP)
Feb  9 22:44:49.848: <IP_ADDRESS>:37298 (ID:51577) -> kube-system/node-local-dns-jpxh5:53 (ID:51577) to-endpoint FORWARDED (UDP)
Feb  9 22:44:49.848: <IP_ADDRESS>:34583 (ID:51577) -> kube-system/node-local-dns-jpxh5:53 (ID:51577) to-endpoint FORWARDED (UDP)
Feb  9 22:44:49.848: <IP_ADDRESS>:57067 (ID:51577) -> kube-system/node-local-dns-jpxh5:53 (ID:51577) to-endpoint FORWARDED (UDP)
Feb  9 22:44:49.848: <IP_ADDRESS>:37750 (ID:51577) -> kube-system/node-local-dns-jpxh5:53 (ID:51577) to-endpoint FORWARDED (UDP)
Feb  9 22:44:49.848: <IP_ADDRESS>:51369 (ID:51577) -> kube-system/node-local-dns-jpxh5:53 (ID:51577) to-endpoint FORWARDED (UDP)
Feb  9 22:44:49.848: <IP_ADDRESS>:38577 (ID:51577) -> kube-system/node-local-dns-jpxh5:53 (ID:51577) to-endpoint FORWARDED (UDP)
Feb  9 22:44:49.848: <IP_ADDRESS>:42392 (ID:51577) -> kube-system/node-local-dns-jpxh5:53 (ID:51577) to-endpoint FORWARDED (UDP)
Feb  9 22:44:49.848: <IP_ADDRESS>:54031 (ID:51577) -> kube-system/node-local-dns-jpxh5:53 (ID:51577) to-endpoint FORWARDED (UDP)
Feb  9 22:44:49.848: <IP_ADDRESS>:41034 (ID:51577) -> kube-system/node-local-dns-jpxh5:53 (ID:51577) to-endpoint FORWARDED (UDP)
Feb  9 22:44:49.848: <IP_ADDRESS>:60081 (ID:51577) -> kube-system/node-local-dns-jpxh5:53 (ID:51577) to-endpoint FORWARDED (UDP)
Feb  9 22:44:49.848: <IP_ADDRESS>:49210 (ID:51577) -> kube-system/node-local-dns-jpxh5:53 (ID:51577) to-endpoint FORWARDED (UDP)
Feb  9 22:44:49.848: <IP_ADDRESS>:40176 (ID:51577) -> kube-system/node-local-dns-jpxh5:53 (ID:51577) to-endpoint FORWARDED (UDP)
Feb  9 22:44:49.848: <IP_ADDRESS>:47465 (ID:51577) -> kube-system/node-local-dns-jpxh5:53 (ID:51577) to-endpoint FORWARDED (UDP)
Feb  9 22:44:49.848: <IP_ADDRESS>:53171 (ID:51577) -> kube-system/node-local-dns-jpxh5:53 (ID:51577) to-endpoint FORWARDED (UDP)
Feb  9 22:44:49.848: <IP_ADDRESS>:51823 (ID:51577) -> kube-system/node-local-dns-jpxh5:53 (ID:51577) to-endpoint FORWARDED (UDP)
Feb  9 22:44:49.849: <IP_ADDRESS>:43854 (ID:51577) -> kube-system/node-local-dns-jpxh5:53 (ID:51577) to-endpoint FORWARDED (UDP)
Feb  9 22:44:49.849: <IP_ADDRESS>:43709 (ID:51577) -> kube-system/node-local-dns-jpxh5:53 (ID:51577) to-endpoint FORWARDED (UDP)
Feb  9 22:44:49.849: <IP_ADDRESS>:37854 (ID:51577) -> kube-system/node-local-dns-jpxh5:53 (ID:51577) to-endpoint FORWARDED (UDP)
Feb  9 22:44:49.849: <IP_ADDRESS>:55706 (ID:51577) -> kube-system/node-local-dns-jpxh5:53 (ID:51577) to-endpoint FORWARDED (UDP)
Feb  9 22:44:49.849: <IP_ADDRESS>:52043 (ID:51577) -> kube-system/node-local-dns-jpxh5:53 (ID:51577) to-endpoint FORWARDED (UDP)
Feb  9 22:44:49.849: <IP_ADDRESS>:33113 (ID:51577) -> kube-system/node-local-dns-jpxh5:53 (ID:51577) to-endpoint FORWARDED (UDP)
Feb  9 22:44:49.850: <IP_ADDRESS>:58154 (ID:51577) -> kube-system/node-local-dns-jpxh5:53 (ID:51577) to-endpoint FORWARDED (UDP)
Feb  9 22:44:49.850: <IP_ADDRESS>:48747 (ID:51577) -> kube-system/node-local-dns-jpxh5:53 (ID:51577) to-endpoint FORWARDED (UDP)
Feb  9 22:44:49.850: <IP_ADDRESS>:34080 (ID:51577) -> kube-system/node-local-dns-jpxh5:53 (ID:51577) to-endpoint FORWARDED (UDP)
Feb  9 22:44:49.850: <IP_ADDRESS>:58907 (ID:51577) -> kube-system/node-local-dns-jpxh5:53 (ID:51577) to-endpoint FORWARDED (UDP)
Feb  9 22:44:49.851: <IP_ADDRESS>:59788 (ID:51577) -> kube-system/node-local-dns-jpxh5:53 (ID:51577) to-endpoint FORWARDED (UDP)
Feb  9 22:44:49.851: <IP_ADDRESS>:32898 (ID:51577) -> kube-system/node-local-dns-jpxh5:53 (ID:51577) to-endpoint FORWARDED (UDP)
Feb  9 22:44:49.851: <IP_ADDRESS>:55613 (ID:51577) -> kube-system/node-local-dns-jpxh5:53 (ID:51577) to-endpoint FORWARDED (UDP)
Feb  9 22:44:49.851: <IP_ADDRESS>:34498 (ID:51577) -> kube-system/node-local-dns-jpxh5:53 (ID:51577) to-endpoint FORWARDED (UDP)
Feb  9 22:44:49.851: <IP_ADDRESS>:42829 (ID:51577) -> kube-system/node-local-dns-jpxh5:53 (ID:51577) to-endpoint FORWARDED (UDP)
Feb  9 22:44:49.851: <IP_ADDRESS>:41303 (ID:51577) -> kube-system/node-local-dns-jpxh5:53 (ID:51577) to-endpoint FORWARDED (UDP)
Feb  9 22:44:49.851: <IP_ADDRESS>:33720 (ID:51577) -> kube-system/node-local-dns-jpxh5:53 (ID:51577) to-endpoint FORWARDED (UDP)
Feb  9 22:44:49.851: <IP_ADDRESS>:36272 (ID:51577) -> kube-system/node-local-dns-jpxh5:53 (ID:51577) to-endpoint FORWARDED (UDP)
Feb  9 22:44:49.851: <IP_ADDRESS>:50874 (ID:51577) -> kube-system/node-local-dns-jpxh5:53 (ID:51577) to-endpoint FORWARDED (UDP)
Feb  9 22:44:49.851: <IP_ADDRESS>:51058 (ID:51577) -> kube-system/node-local-dns-jpxh5:53 (ID:51577) to-endpoint FORWARDED (UDP)
Feb  9 22:44:49.851: <IP_ADDRESS>:54992 (ID:51577) -> kube-system/node-local-dns-jpxh5:53 (ID:51577) to-endpoint FORWARDED (UDP)
Feb  9 22:44:49.851: <IP_ADDRESS>:54247 (ID:51577) -> kube-system/node-local-dns-jpxh5:53 (ID:51577) to-endpoint FORWARDED (UDP)
Feb  9 22:44:49.851: <IP_ADDRESS>:38798 (ID:51577) -> kube-system/node-local-dns-jpxh5:53 (ID:51577) to-endpoint FORWARDED (UDP)
Feb  9 22:44:49.851: <IP_ADDRESS>:60185 (ID:51577) -> kube-system/node-local-dns-jpxh5:53 (ID:51577) to-endpoint FORWARDED (UDP)
Feb  9 22:44:49.851: <IP_ADDRESS>:59962 (ID:51577) -> kube-system/node-local-dns-jpxh5:53 (ID:51577) to-endpoint FORWARDED (UDP)
Feb  9 22:44:49.851: <IP_ADDRESS>:39159 (ID:51577) -> kube-system/node-local-dns-jpxh5:53 (ID:51577) to-endpoint FORWARDED (UDP)
Feb  9 22:44:49.851: <IP_ADDRESS>:44398 (ID:51577) -> kube-system/node-local-dns-jpxh5:53 (ID:51577) to-endpoint FORWARDED (UDP)
...
...

Hi @pravk03 Thanks! Based on the additional context you provided, yes, it does look like a case of loopback traffic for LRP backends.
Note that, the loop prevention logic for LRP backends with socket-lb enabled that you've mentioned in the original report has some corner cases, so I'm planning to replace it. The loop prevention logic also needs to be exposed to the end user through the LRP spec, so that users can only enable it in certain LRPs (e.g., kiam, or the use case you have mentioned in this issue). Here is the PR - https://github.com/cilium/cilium/pull/26144. While the PR only addresses this for socket-lb, it can be extended for the per-packet LB case as well.

Thanks @aditighag. Is there a plan to merge https://github.com/cilium/cilium/pull/26144 soon ?

@pravk03 Yes... I'll be sending out a couple of dependent PRs, you can follow the PR for updates.

Since we are currently blocked and want this addressed soon, wondering if there are any potential issues with adding a backend IP address check before doing service translation in the lxc interface (commit).

@aditighag As PR #30879 shows, it seems very easy to achieve the same loopback prevention for LRP in non socket LB mode. I assume it can't be done the same way in socket LB because source address of packets are not available in that context (pls correct me if wrong). Does that PR make sense and worth merging so that we can get feature parity for LRP in both socket LB and non-socket LB mode.

@liuyuan10 We don't want to enforce this behavior for all LRPs, which is why 26144 exposes this as part of the API.

@aditighag I understand you want to control it by a flag in the API. Your PR only covers socket-lb. For per packet LB, can I ask for you opinion on the approach taken in PR #30879  though I know we need to protect it behind a config flag. If it's the right path, we can talk about how to rebase it on top of you PR #26144

For per packet LB, can I ask for you opinion on the approach taken in PR https://github.com/cilium/cilium/pull/30879 though I know we need to protect it behind a config flag. If it's the right path, we can talk about how to rebase it on top of you PR https://github.com/cilium/cilium/pull/26144

It's not just about protecting it behind a flag. We need to check in the datapath which LRP services + pods we need to skip service translation. I can give pointers for the per-packet LB changes once 26144 is ready for review, and you can rebase on top.

We need to check in the datapath which LRP services + pods we need to skip service translation

Yes. that's about how to decide if enable loop prevention following your PR #26144 . Other than that, do you think the way we detect the loop makes sense for per packet LB?

@pravk03 / @liuyuan10 Are you planning to pick the PR back up now that https://github.com/cilium/cilium/pull/26144 is merged?

Thanks. With your changes, we can set skipRedirectFromBackend to true and wouldn't need #30879 ?

Thanks. With your changes, we can set skipRedirectFromBackend to true and wouldn't need #30879 ?

#30879 revised the socket-lookup based loopback logic in the socket-LB datapath. But IIUC, you opened #30879 for per-packet LB, right?

Got it. Let me update https://github.com/cilium/cilium/pull/30879.

Hi @pravk03 I looked into the BPF source code, and yes, bpf_get_netns_cookie helper is not exposed to BPF TC programs. So we won't be able to invoke it from cilium tc programs. It'll be great, however, if we can use the same skip_lb{4,6}_maps infrastructure across per-packet LB and socket-LB.
There are a couple of options -
(1) Write per EP_NETNS_COOKIE to cilium TC hooks via ELF variable substitutions. We already write per ep fields like LXC_ID, IP, MAC, etc, you can take a look at the code here - https://github.com/cilium/cilium/blob/master/pkg/datapath/loader/template.go#L214. The per ep netns cookie then can be retrieved in the tc egress programs without having to call bpf_get_netns_cookie.
(2) Maintain a mapping of endpoint IP to netns cookie, and use that to get netns cookie.
(3) Modify skip_lb_map key to have a union of netns_cookie (socket-LB) or ep IP fields (per-packet LB).
Option (1) looks the cleanest, and I would suggest looking into it to unblock PR #30879.


When open source code！

Thanks youy great work, when open source code?

Hello, thanks for asking.
The manuscript has just got accepted recently. I am planning to tidy up and upload the code within the next month. Stay tuned.

Hello there, I have uploaded all the necessary codes!
Only the download link for the dataset is left behind, but you can generate the dataset by yourself.


Add new intent: bye

https://github.com/the-vision/jarvis-core/wiki

I want to work on this

@AishwaryaVarma I have assigned this issue to you. Let me know if you need any help!

@TeAmP0is0N @swapagarwal  if she is not working on this can I give it a try....

@hritikpapa I have assigned this issue to you. Let me know if you need any help!

@hritikpapa I have assigned this issue to you. Let me know if you need any help!

thank you @sgpritam

@sgpritam @TeAmP0is0N @swapagarwal what all function do you want me to add in this


Compute short names of items

Items in the pretty output have fully-qualitied names that are hard to read. We could compute for each item a shorter name that is guaranteed to be unique across the whole llbc output, and use that shorter name when displaying to the user.

As discussed: I believe this is a good idea. There is just one thing which is not clear to me: do you intend to compute a short name for all names, or only for a small selection of the most common ones (such as Box)?
As a side remark: of course, we will need an option to print the full names - in my case, I often write name patterns by looking at the debugging output, but those can only be derived by looking at the full names.

I intend this for all names. I also intend for the name matcher to optionally work on short names (and raise an error if there could be ambiguity).

I intend this for all names. I also intend for the name matcher to optionally work on short names (and raise an error if there could be ambiguity).

Ok, understood. A small remark for the name matcher: I think it would be good if the patterns are stable, which would not be the case if we allow matching by using short names (as adding a dependency to a crate might introduce ambiguities, making some previously succeeding patterns suddenly fail).


Display file Directory instead of full path in properties dialog

Before:

After:

@xPoppyx I'm kind of divided on this because the full path can be useful for some users.

We can technically provide a feature flag for this, I am in favor of just showing the path since the file name is already displayed but this should be left up for discussion.

What about a "show full path" button when hovering over it?

We could add a button or context menu "Copy path"

We can create an option in settings whether to show complete path or the directory of the file. That would also be useful

There is a difference with the file name and the path, mainly that the path is made up of folders while the file is a file name. In this case we should just keep them separate to create a division between the two.

Changes to resolve this issue will roll out with the next update.


One click binding provides update/delete/create queries as options which does not make sense

https://www.notion.so/One-click-binding-provides-update-delete-create-queries-as-options-which-does-not-make-sense-9a5b73e9fb63455b9ebfe9fe92d664aa

Already being worked on as part of learnability.


Add threading for Webex adapter

Add parentId to Webex message, methods for replyInThread and startConversationInThread

 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: billyzoellers sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

This looks like a good PR! Thanks for doing the inline docs and everything.
Can you put a few simple demo/test cases in the testbot/skills/webex_features.js file please?

Absolutely! I'll get those added this week.


Vagrantfile update for build dependency

(If this PR fixes a github issue, please add Fixes #<xyz>.)
Fixes #5967
Motivation
Cannot build the project successfully.
Modifications
Add install commands to install the unzip zip tools when vm sets up
Verifying this change

[x] Make sure that the change passes the CI checks.
This change is a trivial rework / code cleanup without any test coverage.

Does this pull request potentially affect one of the following parts:
If yes was chosen, please highlight the changes

Dependencies (does it add or upgrade a dependency): (no)
The public API: (no)
The schema: (don't know)
The default values of configurations: ( no)
The wire protocol: (no)
The rest endpoints: (no)
The admin cli options: ( no)
Anything that affects deployment: (no)

Documentation

Does this pull request introduce a new feature? (no)
If yes, how is the feature documented? (not documented)
If a feature is not applicable for documentation, explain why?
If a feature is not documented yet in this PR, please create a followup issue for adding the documentation

It's weird that my update affects the Jenkins Unit Tests because I just modify the Vagrantfile. Anyone could help?


Bug: colors still show after disabling them

After disabling colors from the settings menu they continue to show. Might use vars instead of macros for colors

Found the solution. Currently implementing. Pretty simple fix actually.


docs: improve wording in rook command documentation

just some rewording that occurred to me when reading the docs

@travisn, I think I addressed all your requests  and/or committed and squashed all your suggestions


Release v0.1 has bug where it doesn't actually build from its own folder but via QL...woops

FIxed


Linting cli package

Updated packages: cli/app, cli/command, cli/docker/app, cli/logger, cli/main.
Wating for #21 to be merged but that opens it to reviews already :wink:.
🐸
Signed-off-by: Vincent Demeester<EMAIL_ADDRESS>

@ibuildthecloud Updated according to your comments :wink:.

LGTM :+1:

LGTM

:tada: :wink:


[#230] block side navigation ux - without search

Description
New Block for the documentation pages side navigation. First pass (ux only desktop, without search)
Test URLs (Block):

Before: https://main--helix-website--adobe.hlx.page/drafts/redesign/blocks/side-navigation
After: https://redesign-documentation-nav--helix-website--adobe.hlx.page/drafts/redesign/blocks/side-navigation

Test URLs (Fragment):

Before: https://main--helix-website--adobe.hlx.page/drafts/redesign/documentation
After: https://redesign-documentation-nav--helix-website--adobe.hlx.page/drafts/redesign/documentation

Documentation:

Readme

Received direction from Kiel for mobile - will work on this today.

@nicolerego able to fix the styles.css conflict?

@solomon71 just resolved the merge conflict in styles.css


Make overview doc more visible in built docs

Adds a few links for clarity as per discussion at the end of today's meeting.
cc @afshin

Thx @Carreau for the typo fix! Merged now @afshin :)


complex UniRef query support regression

Hello, in the legacy UniRef search, this returns 9 results:
uniprot:((ec:<IP_ADDRESS>) (taxonomy:bacteria))

even though the advanced query builder reformats this search as
uniprot:"((ec:<IP_ADDRESS>) (taxonomy:bacteria))"

which returns no results. In the new UniProt search, this still generates results as expected
(ec:<IP_ADDRESS>) (taxonomy_name:bacteria)

But the new UniRef when using
uniprot:((ec:<IP_ADDRESS>) (taxonomy_name:bacteria))

reports that the ec search field is not supported. What does work is
<IP_ADDRESS> (taxonomy_name:bacteria)

But that searches the EC number in "all" (whatever that is) and additional restrictions such as (reviewed:true) cannot be specified with a direct UniRef query. The same happens through the REST interface. Please help.

Hello MRMHmdeleeuw,
Unfortunately, we currently do not support external collection queries in our new API. (I will raise this issue in our next team meeting).
But, you can resolve your problem, by adding one extra request to get the list of UniProt accession (format=list) and using it as an input to your UniRef query

https://rest.uniprot.org/uniprotkb/search?compressed=true&format=list&query=(ec%3A<IP_ADDRESS>) AND (taxonomy_id%3A2)&size=250
This will return
B1VTI5
A0A7K0C9D4
A0A539CUU8
A0A7R8RU82

For each id  you could query UniRef
https://rest.uniprot.org/uniref/search?format=fasta&query=uniprot_id%3AB1VTI5&size=250
Or using OR clause (as you prefer)
https://rest.uniprot.org/uniref/search?format=fasta&query=uniprot_id%3AB1VTI5 OR uniprot_id%3AA0A7K0C9D4 OR uniprot_id%3AA0A539CUU8 OR uniprot_id%3AA0A7R8RU82&size=250

In this link you can get more help about our API

https://www.uniprot.org/help/api_queries

https://www.uniprot.org/help/return_fields

Sorry for this inconvenience
Best Regards
Leonardo Gonzales

Hello Leonardo,
Many thanks for the quick follow-up. This looks like a workable solution for me now. Is there any limitation on the query length, i.e. OR-ing 200 uniprot_id's will work?
Best regards,
Marcel de Leeuw

Unfortunately we do not have a POST for it. In this case, it would need to search in batches.

Apologies for not closing this one out earlier. The Gapseq team has long since implemented a new R script to call the current REST API, which I have reviewed and tested only now.


External scalars still generate comment in SDL

Let's report it without words:
// UserEntity
  @Column({ unique: true })
  @Field(() => GraphQLEmail)
  @IsEmail()
  public email: string

  const schema = await TypeGraphQL.buildSchema({
    resolvers: Object.values(resolvers),
    pubSub,
    authChecker,
    container: Container
  })
  await TypeGraphQL.emitSchemaDefinitionFile('./service.graphqls', schema)

# -----------------------------------------------
# !!! THIS FILE WAS GENERATED BY TYPE-GRAPHQL !!!
# !!!   DO NOT MODIFY THIS FILE BY YOURSELF   !!!
# -----------------------------------------------

# UNEXPECTED EXPRESSION
"""
The javascript `Date` as string. Type represents date and time as the ISO Date string.
"""
scalar DateTime

# UNEXPECTED EXPRESSION
"""
The Email scalar type represents E-Mail addresses compliant to RFC 822.
"""
scalar Email

...

Enviorment:

Package version: 0.17.0

Let's redirect you to the graphql-js repository - I just use printSchema function and there's no option to emit non canonical type definitions omitting the descriptions:
https://github.com/graphql/graphql-js/blob/master/src/utilities/schemaPrinter.js


Add logging around timing and better formatting

Is this data in a dashboard yet?

not yet, but it is being worked on


Opensearch initialization process missing index

Describe the bug
If there is an exception during the initialization process that causes the system index creation to fail, restarting will execute the initialization step code again
Related component
Other
To Reproduce

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
How can I fix the missing index situation
Additional Details
Plugins
Please list all plugins currently enabled.
Screenshots
If applicable, add screenshots to help explain your problem.
Host/Environment (please complete the following information):

OS: [e.g. iOS]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

@smallemployees AFAIK this is the expected behavior. Could you please describe why this is a problem, and maybe provide repro steps?

[Triage - attendees 1 2 3 4 5 6 7 8]
@smallemployees Thanks for creating this issue; however, it isn't being accepted due to not having clear reproduction steps and expectations. Please feel free to open a new issue after addressing the reason.

@smallemployees What error message are you receiving on bootstrap?
If the high watermark is exceeded (disk space is full) it can fail to create indices.


Trouble getting started

Hi Sam,
Your share buttons are the most beautiful social sharing buttons I have seen on the web. Job well done!
I apologize for my lack of knowledge when it comes to HTML/CSS, but I am having trouble getting started. I followed your instructions to the best of my knowledge, but I still cannot seem to get it to work. I get things to appear without any console errors, but from this point I'm not sure where to go:

How to reproduce my issue

Here is a test URL if you want to see it on your end: http://toolshop.521hosting.net/shr/
Here is a zip file of my code too.

I guess the good thing is that once I can figure it out, I am pretty sure anyone else can figure it out :-) Once I figure it out, I would love to submit a pull request with clear documentation on how to get started for newbies.
I know this is open source work too, so no rush! Whenever you have a free moment. Thanks again!

Hey @jaydrogers ,
Cheers dude! Hope you're well. I'll take a look later tonight and see if I can fix up the default styling a bit. Sorry about that.

Thanks so much, hope you are doing well also!! No rush. Keep up the great work!

Hey mate,
Sorry it took me so long to get to this... It should be sorted in the latest version (1.1.0). I've made the default CSS a little better and it'll handy the SVG icons etc a little better. I still want to make it a bit more of a "complete" package (i.e. you just dump the JS in and away you go) but this'll do for now.
Chucked a demo up here: https://jsfiddle.net/bybtcebr/

Hey Sam,
Sorry I couldn't get back to you sooner. I was out traveling. This update helps out a ton. I am confident that if I can get started with Shr, anyone can 😀
Thanks for your beautiful contributions to the open source world. Hope you and the family are doing well!


Unified timer handling

As much as possible code is shared between both timer abstractions. We already had (slight) deviations between tim1 and tim3 code.

One more comment: Maybe it's not ideal how the definition of the used timer is done. Currently we have two situations:

STM32F0 && PWM_TIM == 1 or
STM32L0 && PWM_TIM == 3

For the new revision of the 20A MPPT I plan to use the STM32G431 and TIM1, but most probably using different pins than for the F0. Maybe the #define in the PCB configuration should also consider the used pins... but then we are almost at the point of generating a universal timer HAL.

As for the pin assignments and HAL: I think we are far from make a universal timer HAL but of course we want a half_bridge PWM to be implemented for different processors in the same way with as little fuss as possible. And there are already lots of pin-assignments in the PCB configuration anyways, but there is also no issue for us to keep this for the half_bridge in the half_bridge_tim.cpp, especially if this is per processor derivate and not per PCB.

The commit including unit-tests looks very nice. Thanks!
And also good that the unit-tests already helped to find a bug. I'm becoming more and more a fan of test-driven development, as I also found some bugs I never thought about before. So yeah, for all future additions we should probably follow the "write test first" rule and for existing code the tests can be added step by step.
I think it's fine to define the SystemCoreClock as a constant for the unit tests.
So I'll merge this to master now, afterwards rebase the dcdc-rework branch and then do some tests with the MPPT 1210 HUS today.


ERR_NETWORK_ACCESS_DENIED

When I try to log in when connected to the WG VPN I get this error in Chrome:
ERR_NETWORK_ACCESS_DENIED
As soon as I disconnect from the VPN it is working again.
What could be the problem?
System:    Kernel: 5.4.0-96-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 Desktop: Xfce 4.16.0
tk: Gtk 3.24.20 wm: xfwm4 dm: LightDM Distro: Linux Mint 20.3 Una
base: Ubuntu 20.04 focal

Hi, I'm sorry you encountered problems. Is your server running in the same network as your client? Such as your server is <IP_ADDRESS> and you are <IP_ADDRESS>

Yes, the server is 192.XXX.Y.197 and the PC is 192.XXX.Y.195

Yes, that's what i'm thinking. That is because your server is under 192.xxx.x.197 and your WireGuard interface is not under the same subnet. Did you enable net.ipv4.ip_forward=1?

 Thank you mate! :D Keep on, this page is amazing.

No problem, please let me know if i can help for any other questions! I'm glad you like this project ;)


st.io.read_h5ad still used in Tutorials

Many tutorials (e.g. CCC) use st.io.read_h5ad which does not exist any more (replaced with st.io.read_ann_h5ad). Please consider fixing this.

On the contrary, we will plan to replace read_ann_h5ad to read_h5ad, I think you are not using the latest stereopy, please upgrade.


workflows/docker: base homebrew/brew on 22.04

As per discussion on Slack, I think we can make the switch now rather than wait some arbitrary length of time.
I've also disabled fail-fast so that if a image upload fails in the future, we don't stop the other uploads halfway unnecessarily.

Review period will end on 2022-04-29 at 20:27:43 UTC.

Review period ended.


Update functions-bindings-storage-blob-trigger.md

Hello,
I see some Blob trigger functions occur errors as it cannot access a queue storage. To avoid this issue, proposing an additional
note to allow the access.

@ggailey777
Can you review the proposed changes?
IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
@MicrosoftDocs/public-repo-pr-review-team

emailed author

@yuna-s how did you get into the situation where your function app didn't have access to Queue Storage in the storage account you are using for AzureWebJobsStorage? I'm disinclined to accept your suggestion because I don't think this situation is very likely to occur.
I will go ahead and update this article to include blob trigger as something that required the queue storage.
Please let me know if I am misunderstanding your scenario.

hi @ggailey777 Thank you for your checking! Your suggestions is nice. Some customer enables Firewall on Azure Storage and it blocks requests to queue storage. Using Firewall on the Storage is not unusual sinario. I think it would be more kindly that making it clear to customers that Blob trigger also needs access to Queue storage.

Thanks @yuna-s this is very good information! I'll keep it in mind as I work on our troubleshooting documentation.


optimized query for stuck requests

 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.You have signed the CLA already but the status is still pending? Let us recheck it.


fix:jwt example yaml plugs order

What this PR does:
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

NONE

Codecov Report

Merging #365 (bb86f2f) into develop-0.5.0 (6ffe284) will not change coverage.
The diff coverage is n/a.

@@              Coverage Diff               @@
##           develop-0.5.0     #365   +/-   ##
==============================================
  Coverage          39.66%   39.66%
==============================================
  Files                 52       52
  Lines               3061     3061
==============================================
  Hits                1214     1214
  Misses              1717     1717
  Partials             130      130

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 6ffe284...bb86f2f. Read the comment docs.

添加 omitempty，除去空 config


Failed to create container with todo-nodejs-mongo-swa-func template

Describe the issue:
When using todo-nodejs-mongo-swa-func template to build container for codespace, get error as follow:

Repro Steps:

Open repo: https://github.com/Azure-Samples/todo-nodejs-mongo-swa-func
Open in a codesapce

After container build is completed, a pop-up window appears as shown below, clicking the View Creation Log button to view the error log.

Expected behavior:
Creating codespace success with func template.
@rajeshkamal5050 for notification.

@vhvb1989 can you triage and see if this is a blocker for today's release?

I reproduced the issue from main branch on the template.
However, using staging branch works.
The problem is that main branch uses FROM mcr.microsoft.com/vscode/devcontainers/base:0-bullseye} for Dockerfile.
This img might've been updated recently and introduced this issue.
After releasing azd and updating main branch, this issue will be fixed.
See main v/s staging devcontainer changes here: https://github.com/Azure-Samples/todo-nodejs-mongo-swa-func/compare/main...staging#diff-13bd9d7a30bf46656bc81f1ad5b908a627f9247be3f7d76df862b0578b534fc6R2

This should be fixed by now.  Please re-open if you still see the issue after latest release


Added new tmplate #1

@leofls Thanks for the PR. I'll review and merge it soon.

You may look into a few good first issues which are up for grabs.

:white_check_mark: Link to the repository


[PE-D][Tester C] UI details in use cases

I found that there are some UI details in use cases that could be omitted. Here are some examples:
Under Adding a person,

Under Editing a person,

Labels: type.DocumentationBug severity.Medium
original: ZweZeya/ped#27

Resolved.


Create Union Find in Cpp

Union Find Implementation in Cpp

@AlphaBAT69 You must resolve your conflicts.

@AlphaBAT69 We have already a bubble sort implementation in C++. See here


Magnify v2024

closes #81
closes #76
tasks:

[x] Update with Venture classes
[x] Other db courses
[x] Update course data fields
[x] AP tag
[x] Venture tag
[x] Rename History to Social Studies
~- [ ] Add option to search for "AP" and it will search for "Advanced Placement" too (the PoS varies names) and vice versa~
[x] maybe address #76

@Ascent817 Do you think for classes that are part of a Venture strand, but also as a normal non-Venture class, should we add the Venture tag to it in the database? For example, Earth Science is a normal class, but it can also be part of the Venture Earth Science Strand. I already added the classes that cannot be a non-Venture class and is part of a strand.

Don't merge this yet but I forgot to fix some typos with bullet points which the parser didn't do correctly


Enhance to allow additional media types to be defined

With file_type() being a class method, media_types initialization can be moved out of the file_type() method and into the constructor. This will allow additional, custom media types to be defined at runtime.

Added in 0.5.0


Adding firebase to my current iOS SwiftUI project causes black screen

Description
Hi ,
After adding my firebase-ios to project with swift package manager
the app open on simulator with black screen only
running in iPhone 11 iOS 15.5 simulator
with firebase 9.6.0
nothing special with my other packages i only use PopVIew package
Reproducing the issue
1- create new iOS project using SwiftUI
2- add latest firebase via SPM 9.6.0
3- configure your app on firebase console
4- download .plist file and add it to your project
5-run the app on simulator

Firebase SDK Version
9.6.0
Xcode Version
13.4.1
Installation Method
Swift Package Manager
Firebase Product(s)
Analytics, App Check, App Distribution, Authentication, Crashlytics, DynamicLinks, Messaging
Targeted Platforms
iOS
Relevant Log Output
2023-01-23 12:08:39.009420+0200 MostakblySwiftUI[7288:103407] 9.6.0 - [FirebaseMessaging][I-FCM001000] FIRMessaging Remote Notifications proxy enabled, will swizzle remote notification receiver handlers. If you'd prefer to manually integrate Firebase Messaging, add "FirebaseAppDelegateProxyEnabled" to your Info.plist, and set it to NO. Follow the instructions at:
https://firebase.google.com/docs/cloud-messaging/ios/client#method_swizzling_in_firebase_messaging
to ensure proper integration.
2023-01-23 12:08:39.728444+0200 MostakblySwiftUI[7288:103409] [boringssl] boringssl_metrics_log_metric_block_invoke(153) Failed to log metrics

If using Swift Package Manager, the project's Package.resolved

Expand Package.resolved snippet

Replace this line with the contents of your Package.resolved.

If using CocoaPods, the project's Podfile.lock

Expand Podfile.lock snippet

Replace this line with the contents of your Podfile.lock!

Hi @mohadel92, I'm unable to reproduce the same behavior. Could you try checking your debug logs if you're seeing any error by adding -FIRDebugEnabled flag in your scheme? Also, could you try resetting the simulator and Xcode and see if the issue persists?

thanks @rizafran  for your immediate response
i tried again and again with different simulators
i deleted the package and reinstalled it
i don't know how to add flag
but this is my logs
2023-01-24 11:47:05.615263+0200 MostakblySwiftUI[1384:14062] [ViewportSizing] maximumViewportInset cannot be larger than frame
2023-01-24 11:47:05.615481+0200 MostakblySwiftUI[1384:14062] [ViewportSizing] minimumViewportInset cannot be larger than frame
2023-01-24 11:47:07.445003+0200 MostakblySwiftUI[1384:15327] [assertion] Error acquiring assertion: <Error Domain=RBSServiceErrorDomain Code=1 "target is not running or doesn't have entitlement com.apple.runningboard.assertions.webkit" UserInfo={NSLocalizedFailureReason=target is not running or doesn't have entitlement com.apple.runningboard.assertions.webkit}>
2023-01-24 11:47:07.445478+0200 MostakblySwiftUI[1384:15327] [ProcessSuspension] 0x109004d80 - ProcessAssertion: Failed to acquire RBS assertion 'WebProcess Background Assertion' for process with PID=1439, error: Error Domain=RBSServiceErrorDomain Code=1 "target is not running or doesn't have entitlement com.apple.runningboard.assertions.webkit" UserInfo={NSLocalizedFailureReason=target is not running or doesn't have entitlement com.apple.runningboard.assertions.webkit}
2023-01-24 11:47:07.457342+0200 MostakblySwiftUI[1384:15327] [assertion] Error acquiring assertion: <Error Domain=RBSAssertionErrorDomain Code=2 "Specified target process does not exist" UserInfo={NSLocalizedFailureReason=Specified target process does not exist}>
2023-01-24 11:47:07.459709+0200 MostakblySwiftUI[1384:15327] [ProcessSuspension] 0x109004e40 - ProcessAssertion: Failed to acquire RBS assertion 'ConnectionTerminationWatchdog' for process with PID=1439, error: Error Domain=RBSAssertionErrorDomain Code=2 "Specified target process does not exist" UserInfo={NSLocalizedFailureReason=Specified target process does not exist}
2023-01-24 11:47:07.461728+0200 MostakblySwiftUI[1384:15327] [assertion] Error acquiring assertion: <Error Domain=RBSAssertionErrorDomain Code=2 "Specified target process does not exist" UserInfo={NSLocalizedFailureReason=Specified target process does not exist}>
2023-01-24 11:47:07.462004+0200 MostakblySwiftUI[1384:15327] [ProcessSuspension] 0x109004ea0 - ProcessAssertion: Failed to acquire RBS assertion 'WebProcess Suspended Assertion' for process with PID=1439, error: Error Domain=RBSAssertionErrorDomain Code=2 "Specified target process does not exist" UserInfo={NSLocalizedFailureReason=Specified target process does not exist}
2023-01-24 11:47:08.088242+0200 MostakblySwiftUI[1384:15333] [boringssl] boringssl_metrics_log_metric_block_invoke(153) Failed to log metrics
2023-01-24 11:47:08.300414+0200 MostakblySwiftUI[1384:15333] [default] Failed to open URL com.MohammedAdel.MostakblySwiftUI://google/link/?request_ip_version=IP%5FV4&match_message=No%20pre%2Dinstall%20link%20matched%20for%20this%20device%2E: Error Domain=NSOSStatusErrorDomain Code=-10814 "(null)" UserInfo={_LSLine=225, _LSFunction=-[_LSDOpenClient openURL:options:completionHandler:]}

@mohadel92, you can put the -FIRDebugEnabled flag in the scheme editor as shown here.

@rizafran
2023-01-24 15:53:21.178282+0200 MostakblySwiftUI[7507:218539] [ViewportSizing] maximumViewportInset cannot be larger than frame
2023-01-24 15:53:21.178507+0200 MostakblySwiftUI[7507:218539] [ViewportSizing] minimumViewportInset cannot be larger than frame
2023-01-24 15:53:22.635294+0200 MostakblySwiftUI[7507:218728] [assertion] Error acquiring assertion: <Error Domain=RBSServiceErrorDomain Code=1 "target is not running or doesn't have entitlement com.apple.runningboard.assertions.webkit" UserInfo={NSLocalizedFailureReason=target is not running or doesn't have entitlement com.apple.runningboard.assertions.webkit}>
2023-01-24 15:53:22.635527+0200 MostakblySwiftUI[7507:218728] [ProcessSuspension] 0x105004d20 - ProcessAssertion: Failed to acquire RBS assertion 'WebProcess Background Assertion' for process with PID=7510, error: Error Domain=RBSServiceErrorDomain Code=1 "target is not running or doesn't have entitlement com.apple.runningboard.assertions.webkit" UserInfo={NSLocalizedFailureReason=target is not running or doesn't have entitlement com.apple.runningboard.assertions.webkit}
2023-01-24 15:53:22.642996+0200 MostakblySwiftUI[7507:218728] [assertion] Error acquiring assertion: <Error Domain=RBSAssertionErrorDomain Code=2 "Specified target process does not exist" UserInfo={NSLocalizedFailureReason=Specified target process does not exist}>
2023-01-24 15:53:22.644822+0200 MostakblySwiftUI[7507:218728] [ProcessSuspension] 0x105004de0 - ProcessAssertion: Failed to acquire RBS assertion 'ConnectionTerminationWatchdog' for process with PID=7510, error: Error Domain=RBSAssertionErrorDomain Code=2 "Specified target process does not exist" UserInfo={NSLocalizedFailureReason=Specified target process does not exist}
2023-01-24 15:53:22.649461+0200 MostakblySwiftUI[7507:218728] [assertion] Error acquiring assertion: <Error Domain=RBSAssertionErrorDomain Code=2 "Specified target process does not exist" UserInfo={NSLocalizedFailureReason=Specified target process does not exist}>
2023-01-24 15:53:22.650842+0200 MostakblySwiftUI[7507:218728] [ProcessSuspension] 0x105004e40 - ProcessAssertion: Failed to acquire RBS assertion 'WebProcess Suspended Assertion' for process with PID=7510, error: Error Domain=RBSAssertionErrorDomain Code=2 "Specified target process does not exist" UserInfo={NSLocalizedFailureReason=Specified target process does not exist}
2023-01-24 15:53:22.988986+0200 MostakblySwiftUI[7507:218728] [boringssl] boringssl_metrics_log_metric_block_invoke(153) Failed to log metrics
2023-01-24 15:53:23.170204+0200 MostakblySwiftUI[7507:218722] [default] Failed to open URL com.MohammedAdel.MostakblySwiftUI://google/link/?request_ip_version=IP%5FV4&match_message=No%20pre%2Dinstall%20link%20matched%20for%20this%20device%2E: Error Domain=NSOSStatusErrorDomain Code=-10814 "(null)" UserInfo={_LSLine=225, _LSFunction=-[_LSDOpenClient openURL:options:completionHandler:]}

@rizafran
i found the part of my code that is causing the issue
after using this code
final class AppDelegate: NSObject,UIApplicationDelegate {
    func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?) -> Bool {
        // Override point for customization after application launch.

        FirebaseApp.configure()

        return true
    }
}

i inserted this code before my main code and after @main and this was the problem
@main should only be above the main entry point of my app
feel free to close this ticket thanks a lot


junod's --height flag seems to have issues now

Specifications
Juno version: v11, also 10.1.0
OS & Version: OSX
Expected behaviour
The --height flag should allow us to check details at a given block height
Actual behaviour
This error:

Error: rpc error: code = InvalidArgument desc = contract: not found: invalid request

Steps to reproduce the behaviour
Note that this works…
without --height:
(works)
junod q wasm contract-state smart juno1h8t6uhqukwgp4qn0nf6h9j93zu4z57rjlzp0x00qrnu4lmnfw9tsjas2g6 '{"get_tasks":{}}' --node https://juno-testnet-rpc.polkachu.com:443 --chain-id uni-5 -o json | jq
same command with --height:
junod q wasm contract-state smart juno1h8t6uhqukwgp4qn0nf6h9j93zu4z57rjlzp0x00qrnu4lmnfw9tsjas2g6 '{"get_tasks":{}}' --height 5484637 --node https://juno-testnet-rpc.polkachu.com:443 --chain-id uni-5 -o json | jq

Because uni testnet has been restarted, current block in uni-5 is 585940.

hey @vuong177 thanks for that. I think I have a better way to reproduce this…
Note that at the time of this writing, the latest block for Juno testnet is around 590,470
This works at height 530,000 :
junod q wasm contract-state smart juno1h8t6uhqukwgp4qn0nf6h9j93zu4z57rjlzp0x00qrnu4lmnfw9tsjas2g6 '{"get_tasks":{}}' --height 530000 --node https://juno-testnet-rpc.polkachu.com:443 --chain-id uni-5 -o json | jq
This doesn't work at height 530,600 (600 blocks "sooner", so you'd think it's not pruned):
junod q wasm contract-state smart juno1h8t6uhqukwgp4qn0nf6h9j93zu4z57rjlzp0x00qrnu4lmnfw9tsjas2g6 '{"get_tasks":{}}' --height 530600 --node https://juno-testnet-rpc.polkachu.com:443 --chain-id uni-5 -o json | jq
Second one errors with:

Error: rpc error: code = InvalidArgument desc = contract: not found: invalid request

@mikedotexe thank you for your help. I'm digging into it.

Are you expecting it to return any data? All three of those return for me, except with data: [] as the response.
Note: I used a different RPC (local one on a val box)

@mikedotexe maybe the node for https://juno-testnet-rpc.polkachu.com:443 is a pruning node, so you can't query the old height.

Note: I used a different RPC (local one on a val box)

Interesting, maybe it is polkachu's testnet RPC. Just very strange that it pruned state after a block height that returned properly. Sounds like this is an RPC issue instead of one for this repo. Feels like it's a good time to close it. Thank you both!


Firefox bullet point rendering bug (F0B7 unicode character)

Link to PDF file (or attach file here): https://cloud.box.com/s/bs6708c0hwpoxuew4br2yx16eunhg2zu
Configuration:

Web browser and its version: Firefox 53.0.3
Operating system and its version: Mac OSX El Capitan
PDF.js version: Latest on https://mozilla.github.io/pdf.js/web/viewer.html
Is an extension: No

Steps to reproduce the problem:

Download PDF from https://cloud.box.com/s/bs6708c0hwpoxuew4br2yx16eunhg2zu
Go to https://mozilla.github.io/pdf.js/web/viewer.html on Firefox
Open downloaded PDF
Go to third page, highlight a bullet point
Notice that 'F0B7' unicode character shows up over the bullet point, even though it's supposed to be transparent. This shows up as a square character in Chrome that is hidden, regardless of text selection.

What is the expected behavior? (add screenshot)
No unicode character shows up after text selection:

What went wrong? (add screenshot)
Unicode character shows up after text selection:

Link to a viewer (if hosted on a site other than mozilla.github.io/pdf.js or as Firefox/Chrome extension): N/A

Not sure if this is a text selection or rendering issue in Firefox - in the sample pdf.js viewer, the F0B7 character only shows up after a text selection, but using a custom build (we're on 1.8.323) on Firefox, the character shows up before text selection as well.
To view for yourself:

Use Firefox 53.0.3
Visit https://darth.app.box.com/on/beta
Visit https://darth.box.com/s/ujwqqtlqst73ts3a6yof3866phiqtli6
Go to page 2, notice the character is visible before any sort of text selection

Closing since this no longer happens. This might have been a bug in Firefox.


Syntax error output if a field is named 'from'

This tool generates .pyi files with syntax error when parsing a proto-file with a field named from. E.g. foo.proto:
message FooRequest {
	int64 from = 5;
}

Running mypy on a project with this kind of autogenerated files results in syntax error:
$ mypy
package/schemas/foo_pb2.pyi:356: error: invalid syntax

This is because the foo_pb2.pyi file has this in it:
class FooRequest(google___protobuf___message___Message):
    from = ... # type: int

The from = ... is invalid syntax, and so we have a problem.
Just to say I've set up my mypy to ignore these files, mypy.ini:
[mypy]

[mypy-package.schemas.*]
ignore_errors = True

But this doesn't ignore syntax errors. As per https://github.com/python/mypy/issues/6897 mypy can't ignore syntax errors. It would be favorable if this project did not generate syntax-invalid output.
I'm using versions:
$ python --version Python 3.6.7
mypy==0.701
mypy-protobuf==1.10

And here is a gist with the entire contents of the .proto file, the generated .py file (which does not have syntax errors and the problematic and unexcludable .pyi file:
https://gist.github.com/gaggle/8aef6102d314936c9eb33724194682b0

Great bugreport! Thanks.
I don't know offhand how we're supposed to type a variable with a reserved keyword name. Will look into it w/ mypy docs / folks. Thanks for reporting!

It looks like the .py file generator sidesteps the issue by not generating Python code but some meta thing. So at runtime you'd have to write getattr(thing, 'from'). (And add # noqa :-)
Since there can't be any code that writes thing.from, maybe the simplest thing would be to just not emit the field at all? Or perhaps emit it with a # in front of it?

I'd not emit them. See also https://developers.google.com/protocol-buffers/docs/reference/python-generated#keyword-conflicts


tf.enable_eager_execution must be called at program startup.

from __future__ import absolute_import, division, print_function
import os
import matplotlib.pyplot as plt

import tensorflow as tf
print(tf.VERSION)   #  => 1.7.0
import tensorflow.contrib.eager as tfe

tf.enable_eager_execution()

ValueError                                Traceback (most recent call last)
<ipython-input-59-0c62cac7517d> in <module>()
      7 import tensorflow.contrib.eager as tfe
      8
----> 9 tf.enable_eager_execution()

D:\Anaconda3\envs\tensorflow\lib\site-packages\tensorflow\python\framework\ops.py in enable_eager_execution(config, device_policy)
   5242     if graph_mode_has_been_used:
   5243       raise ValueError(
-> 5244           "tf.enable_eager_execution must be called at program startup.")
   5245   context._default_mode = context.EAGER_MODE
   5246   if context._context is None:

ValueError: tf.enable_eager_execution must be called at program startup.

tf.enable_eager_execution() is intended to be called once in a program, typically the first thing in a program. Libraries should not be calling tf.enable_eager_execution() and instead should in general work for both graph construction and eager execution (or assert tf.executing_eagerly() if they work only with eager execution).
That said, I can't reproduce the error you're seeing using the snippet provided. Is there more to reproducing the problem? Thanks.

Thank you for your quick response.
I tried the same codes in Windows terminal, it works.
But it doesn't work in Jupyter (Version 5.4.1, latest version).

Sounds like the Jupyter kernel needs to be restarted.

Cool, it works, thank you for  your time.

Thanks a lot, also fix my issue

Cool, solved my problem.

Met this problem again when I run the example of Neural Machine Translation with Attention in colab.  What should I do to make this notebook work.

For now, you can restart the colab runtime ("Runtime -> Restart Runtime...").
In future releases, I think the error will go away (thanks to e2c6ec9e86dd86e0dd56e0f11302a5bf5d9ed440)

@asimshankar  Thanks guy,  but restarting the runtime does not work for me, even I change the notebook environment to python2 without GPU.

I have the same issue with the notebook below.
Restart runtime, Reset all runtimes neither do not solve, but I could run it once before.
https://colab.research.google.com/github/tensorflow/tensorflow/blob/master/tensorflow/contrib/eager/python/examples/pix2pix/pix2pix_eager.ipynb

Same issue here:
import os
import logging.config
import tensorflow as tf
from tensor2tensor import problems
from tensor2tensor.data_generators.translate_ende import TranslateEndeWmtBpe32k

from asr.util import is_debug_mode

if __name__ == '__main__':

    logging.config.fileConfig('../logging.conf')
    logger = logging.getLogger(__name__)
    logger.setLevel(level=logging.DEBUG)

    tfe = tf.contrib.eager

    if is_debug_mode():
        logger.info('Debug mode. Enabling tensorflow eager excetion.')
        if not tf.executing_eagerly():
            # Enable tensorflow Eager execution
            tfe.enable_eager_execution()

Throws
19-09-2018:10:37:35,546 INFO     [example_transformer_ende.py:41] Debug mode. Enabling tensorflow eager excetion.
Traceback (most recent call last):
  File "/home/everest11/.pycharm_helpers/pydev/pydevd.py", line 1664, in <module>
    main()
  File "/home/everest11/.pycharm_helpers/pydev/pydevd.py", line 1658, in main
    globals = debugger.run(setup['file'], None, None, is_module)
  File "/home/everest11/.pycharm_helpers/pydev/pydevd.py", line 1068, in run
    pydev_imports.execfile(file, globals, locals)  # execute the script
  File "/home/everest11/.pycharm_helpers/pydev/_pydev_imps/_pydev_execfile.py", line 18, in execfile
    exec(compile(contents+"\n", file, 'exec'), glob, loc)
  File "/home/everest11/tmp/pycharm_project_254/asr/example_transformer_ende.py", line 44, in <module>
    tfe.enable_eager_execution()
  File "/home/everest11/miniconda3/envs/t2t-asr/lib/python3.5/site-packages/tensorflow/python/framework/ops.py", line 5187, in enable_eager_execution
    config, device_policy, execution_mode, None)
  File "/home/everest11/miniconda3/envs/t2t-asr/lib/python3.5/site-packages/tensorflow/python/framework/ops.py", line 5255, in enable_eager_execution_internal
    "tf.enable_eager_execution must be called at program startup.")
ValueError: tf.enable_eager_execution must be called at program startup.

I had the same problem. My code looks something like
import utils
import tensorflow as tf
tf.enable_eager_execution()

Turns out utils already imports tensorflow. The exception goes away if I run tf.enable_eager_execution immediately after tensorflow is imported for the very first time (i.e., in utils).

I have a similar problem with this code:
import tensorflow as tf tf.enable_eager_execution()
This is right at the top of the code. However, even tf.enable_eager_execution() is right after import tensorflow as tf and these are the first two lines of code, I still get the error.

Restart Kernel and clear output and run the code block again from start. Issue will be resolved

As a tip, at least in tensorflow version 1.13.1, you can't even check if eager execution is enabled before you try to enable eager execution.
That is the following will not work:
import tensorflow as tf
tf.executing_eagerly()
tf.enable_eager_execution()

However, with a new python kernel, the following works:
import tensorflow as tf
tf.enable_eager_execution()
tf.executing_eagerly()


Remove special characters from view names

Special characters, like "ç" can originate problems for the collection name. We should normalize them here:
https://github.com/byteroad/ogcapi-simple/blob/64626f34a2e810e01f2a24c76fc5b7135448c0bc/postgis/scripts/create-views.sql#L14

https://github.com/byteroad/ogcapi-simple/commit/bbd5ab96aade58263378d3c2c76a33c0684400d2


niconico - WARNING: unable to log in: bad username or password

Make sure you are using the latest version: run youtube-dl --version and ensure your version is 2018.05.01. If it's not, read this FAQ entry and update. Issues with outdated version will be rejected.

[x] I've verified and I assure that I'm running youtube-dl 2018.05.01

Before submitting an issue make sure you have:

[x] At least skimmed through the README, most notably the FAQ and BUGS sections
[x] Searched the bugtracker for similar issues including closed ones
[x] Checked that provided video/audio/playlist URLs (if any) are alive and playable in a browser

What is the purpose of your issue?

[x] Bug report (encountered problems with youtube-dl)
[ ] Site support request (request for adding support for a new site)
[ ] Feature request (request for a new functionality)
[ ] Question
[ ] Other

If the purpose of this issue is a bug report, site support request or you are not completely sure provide the full verbose output as follows:
Add the -v flag to your command line you run youtube-dl with (youtube-dl -v <your command line>), copy the whole output and insert it here. It should look similar to one below (replace it with your log inserted between triple ```):
~ youtube-dl -v -n http://www.nicovideo.jp/watch/sm9913701
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['-v', '-n', 'http://www.nicovideo.jp/watch/sm9913701']
[debug] Encodings: locale UTF-8, fs utf-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2018.05.01
[debug] Python version 3.6.5 (CPython) - Linux-4.16.5-1-ARCH-x86_64-with-arch
[debug] exe versions: ffmpeg 3.4.2, ffprobe 3.4.2, rtmpdump 2.4
[debug] Proxy map: {}
[niconico] Logging in
WARNING: unable to log in: bad username or password
[niconico] sm9913701: Downloading webpage
[niconico] sm9913701: Downloading JSON metadata for h264_500kbps_360p-aac_64kbps
[niconico] sm9913701: Downloading JSON metadata for h264_300kbps_360p-aac_64kbps
[debug] Default format spec: bestvideo+bestaudio/best
[debug] Invoking downloader on 'http://pb03.dmc.nico:2808/vod/ht2_nicovideo/nicovideo-sm9913701_a9c5e12be6a0d8a74b5ec45aa77edcb143fff7afbd813c17642781f36f99373c?ht2_nicovideo=6-6ITVjm3P0M_1525621368193.cx19m6_p8bczh_3oj3ikkqbmexh'
[download] Destination: 「断罪ヤマザナドゥ！」に絵を付けてみた-sm9913701.mp4
[download]  88.9% of 16.56MiB at 140.65KiB/s ETA 00:13[download] Got server HTTP error: [Errno 104] Connection reset by peer. Retrying (attempt 1 of 10)...
ERROR: unable to download video data: HTTP Error 403: Forbidden
Traceback (most recent call last):
  File "/usr/lib/python3.6/site-packages/youtube_dl/YoutubeDL.py", line 1900, in process_info
    success = dl(filename, info_dict)
  File "/usr/lib/python3.6/site-packages/youtube_dl/YoutubeDL.py", line 1839, in dl
    return fd.download(name, info)
  File "/usr/lib/python3.6/site-packages/youtube_dl/downloader/common.py", line 365, in download
    return self.real_download(filename, info_dict)
  File "/usr/lib/python3.6/site-packages/youtube_dl/downloader/http.py", line 340, in real_download
    establish_connection()
  File "/usr/lib/python3.6/site-packages/youtube_dl/downloader/http.py", line 109, in establish_connection
    ctx.data = self.ydl.urlopen(request)
  File "/usr/lib/python3.6/site-packages/youtube_dl/YoutubeDL.py", line 2203, in urlopen
    return self._opener.open(req, timeout=self._socket_timeout)
  File "/usr/lib/python3.6/urllib/request.py", line 532, in open
    response = meth(req, response)
  File "/usr/lib/python3.6/urllib/request.py", line 642, in http_response
    'http', request, response, code, msg, hdrs)
  File "/usr/lib/python3.6/urllib/request.py", line 570, in error
    return self._call_chain(*args)
  File "/usr/lib/python3.6/urllib/request.py", line 504, in _call_chain
    result = func(*args)
  File "/usr/lib/python3.6/urllib/request.py", line 650, in http_error_default
    raise HTTPError(req.full_url, code, msg, hdrs, fp)
urllib.error.HTTPError: HTTP Error 403: Forbidden

Description of your issue, suggested solution and other information
This is what happens when I download this video: it starts downloading at non capped speed, then it caps speed down to 80/160 kb/s and when it's almost compelted (88-89%) a 403 error happens and download fails. As you can see it also warns me that my username or password are wrong but I used them to login so this can't be possible. I also recently changed email and password, maybe that's the issue. Speaking of the 403 type error, it happened before I changed email and password as well but at the time I was using jdownloader for the job. My username and passwords are stored correctly in my .netrc in $HOME with the proper credentials..

I get this 403 a lot too, and it's always with larger files. youtube-dl retries a few times, but I had a few where it seemed like it wasn't getting very much for each retry. But when I waited a minute and ran it again, that worked fine. So it's maybe like there should be some kind of back-off period for nicovideo to avoid them booting the client if it retries immediately.
Also if you retry rapidly enough with nicovideo, the server will eventually give you a 503 for a while, even for videos which would have otherwise worked. I found out of my run of 200 or so videos, about 50 of them failed with 503 on the first run, then about 15 on the second run, and then on the third run everything was fine again.


Added support for plural days interval

Thanks for the PR 😃  I'm on the fence here –  would the goal of this to be able to do something like schedule.every(3).wednesdays.do(...)?
I'm worried that this will lead people down a path that's going to hurt them in the long run. This sounds like something Cron would be better suited for.
Any thoughts on that?

I'd recommend adding some examples and test cases.


165 fix more validation errors

@frehburg
validation errors were given, because the newly generated phenopackets were not moved to the folder that the validator checks. For us important to know: the synth data is valid, however illogical in terms of mutations and phenotyping.
also the mc4r_v1.7 data is now in phenopacket format and all validated.

This was fixed in #158


Terminal support in app launcher

Add implementation of https://gitlab.freedesktop.org/terminal-wg/specifications/-/merge_requests/3

As of 4e4108407ff97098eb8d578fc188119fe393b5fb terminal support is working, but I'm thinking on finishing implementation of a negative cache for fallback entries, that's why there is a reject_mtp parameter in find_entries function.


Update footer.html

Summary

Added  tag attribute to open social media accounts in a new window.
Ticket Link

Hello @AugustinJose1221,
Thanks for your pull request! A Core Committer will review your pull request soon. For code contributions, you can learn more about the review process here.
Per the Mattermost Contribution Guide, we need to add you to the list of approved contributors for the Mattermost project.
Please help complete the Mattermost contribution license agreement?
Once you have signed the CLA, please comment with /check-cla and confirm that the CLA check is green.
This is a standard procedure for many open source projects.
Please let us know if you have any questions.
We are very happy to have you join our growing community! If you're not yet a member, please consider joining our Contributors community channel to meet other contributors and discuss new opportunities with the core team.

/check-cla

/check-cla

The cla check has failed. I'm not much familiar with its workflow. So can anyone tell how to complete the cla check for this PR?

/check-cla

That did the trick :wink:

Thanks for the quick fix @AugustinJose1221 :+1:


feat: sql fast path initial

@stephaniewang526 PTAL

Codecov Report

Merging #1 into master will decrease coverage by 0.41%.
The diff coverage is 56.84%.

@@             Coverage Diff              @@
##             master       #1      +/-   ##
============================================
- Coverage     81.48%   81.06%   -0.42%
- Complexity     1225     1240      +15
============================================
  Files            77       78       +1
  Lines          6218     6302      +84
  Branches        691      706      +15
============================================
+ Hits           5067     5109      +42
- Misses          792      814      +22
- Partials        359      379      +20

Impacted Files
Coverage Δ
Complexity Δ

.../com/google/cloud/bigquery/spi/v2/BigQueryRpc.java
81.81% <ø> (ø)
0.00 <0.00> (ø)

.../google/cloud/bigquery/spi/v2/HttpBigQueryRpc.java
5.18% <0.00%> (-0.02%)
2.00 <0.00> (ø)

...va/com/google/cloud/bigquery/QueryRequestInfo.java
51.61% <51.61%> (ø)
10.00 <10.00> (?)

...n/java/com/google/cloud/bigquery/BigQueryImpl.java
83.05% <72.41%> (-0.54%)
79.00 <4.00> (+5.00)
:arrow_down:

...m/google/cloud/bigquery/QueryJobConfiguration.java
89.80% <100.00%> (-0.28%)
66.00 <0.00> (ø)

...ogle/cloud/bigquery/WriteChannelConfiguration.java
86.23% <0.00%> (-0.58%)
46.00% <0.00%> (ø%)

...om/google/cloud/bigquery/LoadJobConfiguration.java
92.77% <0.00%> (-0.44%)
56.00% <0.00%> (ø%)

...a/com/google/cloud/bigquery/InsertAllResponse.java
88.88% <0.00%> (-0.31%)
15.00% <0.00%> (ø%)

...google/cloud/bigquery/StandardTableDefinition.java
93.15% <0.00%> (-0.19%)
16.00% <0.00%> (ø%)

... and 4 more

Continue to review full report at Codecov.

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


Tolerance Documentation is Incorrect

There are two issues:

Group colors to limit the output and give a better visual representation.

While technically accurate "group" is technically accurate, but misleading. The program scans pixel by pixel. When a pixel is scanned, its color is compared to that of every other unique color on record. If the color of the pixel is deemed unique enough (something determined by the tolerance parameter), it is saved as a unique color. If not, it is ignored. There is no averaging or blending.
For example, if the program is run on the image of a rectangle for whose left half is solid red and the right half is solid blue, given a high enough tolerance, the image will group the whole image's color as pure red.

Similarly, it would be blue if blue were on the left. It depends on what pixels are scanned first, so colors that are further up and further left are the ones that are counted as unique.
I guess not technically an issue, but I feel like this should be noted in the documentation.

[Tolerance is] based on a scale from 0 to 100. Where 0 won't group any color and 100 will group all colors into one.

This is outright false.  The "tolerance" parameter is just the minimum distance in the CIELAB (Lab*) color space (as determined by the CIE76 algorithm: math.sqrt((l * l) + (a * a) + (b * b))) for two colors to be grouped together. As a result, although tolerance = 0 works as stated, tolerance = 100 does not. For example, the minimum integer value for the program to group the red and blue rectangle from before into one color is tolerance = 177. Thankfully, you can enter tolerance values greater than 100 without raising an error because of the other issue I opened: ArgumentTypeErrors aren't raised if the module isn't run using the command line.

Hi @SturgeonInc Thanks for this explanation, as I had some doubts along the same lines. As I am working on a piece where generally the variety of colors in an image ranges from 10 to 20. I have used different types of modules either it's based on some kind of clustering ( where we input the clusters generally but I would prefer it in an automated way) or some version of distance formula. Also tried automatic k finding but that takes a lot of time. Did you find any better color extraction technique ?

I don’t fully understand what your application is. What I ended up using was:
https://github.com/zygisS22/color-palette-extraction
It is in Javascript, but served my purposes. It has a nice demo app to play around with, as well as a [useful article] (https://dev.to/producthackers/creating-a-color-palette-with-javascript-44ip)  explaining how it works (median cut algorithm, in short)
If you’re looking for something much more in-depth, there’s TinEye’s multicolor engine API. I hope this helps.


Can I training your code with V100 GPU

You should be able to; based on the memory available on the V100 cards though, you may need to cut the batch size, or turn on gradient accumulation.


Feedback From Qingqing

Hello @JimmyYang917 ,
This is my initial feedback about your research project.
Your research proposal has provided the readers with a comprehensive selection of variables which relation to macro econometric analysis, you have considered the selection of variables with respect to many factors including the subject of the study itself and the external environment that can influence it, also gives me a hint to consider my variable selection.
However, there may also need some improvement towards the data cleaning part. The first is about the formatting under the ‘Data properties’, you have given a very detailed explanation and therefore take up a lot of space, giving some blank space under some subheadings I think would increase readability. The second is that we may can shorten the names of some variables, which is more common for example, treasurybills can be written as tbills. The third is I have personally taken the log transformation of some of my data to narrow the data range and get rid of the effect of outliers and a code loop may be more efficient. The fourth is for correlation plot, since we may only focus on the correlation between Y and X variables which means we can transfer the plot to the numeric value which only contains the correlation between Y and X variables and become more straightforward. The fifth is about the adf test, we may can write in a loop to show the results more efficient.
I have made some changes in the qmd file already and hope it is making sense and helpful for you.
Good luck!
Qingqing Pang

Hi  Qingqing @comeseemeintheocean:
Thanks for the pull request and hope you have a great day.
After check all requirements and pull request details, I'd like to say thank you to what you have done and uopdate following changes.

[ ]  update new correlation diagrams

[ ] update new adf test details and results

For repo designed in first stage recently, all variables transformation will be done after ADF tests results. Blank lines and shorter variable names will included in after wedsite design.
Thank you so much
Best wishes
Yuqiao

Website format update:

[ ] Rename the variables structure and discribtion
[ ] Update some Title structure

Nice cooperative work @comeseemeintheocean and @JimmyYang917  Thank you!


MessagingException on grails 3.1.0

application.yml
grails:
            mail:
                host: "smtp.gmail.com"
                port: 465
                username<EMAIL_ADDRESS>                password: "**********"
                props:
                    mail.smtp.auth: "true"
                    mail.smtp.socketFactory.port: "465"
                    mail.smtp.socketFactory.class: "javax.net.ssl.SSLSocketFactory"
                    mail.smtp.socketFactory.fallback: "false"

Action
def create = {
        println "sending mail now............."
        sendMail {
            from<EMAIL_ADDRESS>            to<EMAIL_ADDRESS>            subject "New user"
            text "A new user has been created"
        }
        println "mail sent";
    }

ERROR
ERROR org.grails.web.errors.GrailsExceptionResolver - MessagingException occurred when processing request: [GET] /ims/test/create
Could not connect to SMTP host: smtp.gmail.com, port: 465, response: -1. Stacktrace follows:
org.springframework.mail.MailSendException: Mail server connection failed; nested exception is javax.mail.MessagingException: Could not connect to SMTP host: smtp.gmail.com, port: 465, response: -1. Failed messages: javax.mail.MessagingException: Could not connect to SMTP host: smtp.gmail.com, port: 465, response: -1
	at grails.plugins.mail.MailMessageBuilder.sendMessage(MailMessageBuilder.groovy:130) ~[mail-2.0.0.RC6.jar:na]
	at grails.plugins.mail.MailService.sendMail(MailService.groovy:53) ~[mail-2.0.0.RC6.jar:na]
	at grails.plugins.mail.MailService.sendMail(MailService.groovy:57) ~[mail-2.0.0.RC6.jar:na]
	at grails.plugins.mail.SendMail$Trait$Helper.sendMail(SendMail.groovy:31) ~[mail-2.0.0.RC6.jar:na]

It says, that it fails to connect to smtp.gmail.com on port 465. This is not  a but in the mail plugin, but rather some connection issue on your localhost.

and by the way, it is not recommended to use closures as action definitions in Grails 2.x and up. You should change it to methods instead.

@sbglasius  well I  have another project  that uses mail 1.0.7 on grails 2.4.2 and it's working fine.
mail-2.0.0.RC6 on grails 3.1.0 gives me the error on the same config

You should try and convert your mail settings to application.groovy and use the old format. I'm not sure that the props: section gets passed back to the mail plugin correctly using application.yml

I even tried that one too.myconfig on application.groovy
grails {
mail {
host = "smtp.gmail.com"
port = 465
username =<EMAIL_ADDRESS>password = ""
props = ["mail.smtp.auth":"true",
"mail.smtp.socketFactory.port":"465",
"mail.smtp.socketFactory.class":"javax.net.ssl.SSLSocketFactory",
"mail.smtp.socketFactory.fallback":"false"]
}
}
And the error is same
ERROR org.grails.web.errors.GrailsExceptionResolver - MessagingException occurred when processing request: [GET] /ims/test/create
Could not connect to SMTP host: smtp.gmail.com, port: 465, response: -1. Stacktrace follows:
org.springframework.mail.MailSendException: Mail server connection failed; nested exception is javax.mail.MessagingException: Could not connect to SMTP host: smtp.gmail.com, port: 465, response: -1. Failed messages: javax.mail.MessagingException: Could not connect to SMTP host: smtp.gmail.com, port: 465, response: -1
at grails.plugins.mail.MailMessageBuilder.sendMessage(MailMessageBuilder.groovy:130) ~[mail-2.0.0.RC6.jar:na]
at grails.plugins.mail.MailService.sendMail(MailService.groovy:53) ~[mail-2.0.0.RC6.jar:na]
at grails.plugins.mail.MailService.sendMail(MailService.groovy:57) ~[mail-2.0.0.RC6.jar:na]
at ims.TestController.create(TestController.groovy:17) ~[main/:na]
at grails.plugin.springsecurity.web.UpdateRequestContextHolderExceptionTranslationFilter.doFilter(UpdateRequestContextHolderExceptionTranslationFilter.groovy:64) ~[spring-security-core-3.1.1.jar:na]
at grails.plugin.springsecurity.web.filter.GrailsAnonymousAuthenticationFilter.doFilter(GrailsAnonymousAuthenticationFilter.groovy:53) ~[spring-security-core-3.1.1.jar:na]
at grails.plugin.springsecurity.web.authentication.logout.MutableLogoutFilter.doFilter(MutableLogoutFilter.groovy:62) ~[spring-security-core-3.1.1.jar:na]
at grails.plugin.springsecurity.web.SecurityRequestHolderFilter.doFilter(SecurityRequestHolderFilter.groovy:58) ~[spring-security-core-3.1.1.jar:na]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) ~[na:1.8.0]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) ~[na:1.8.0]
at java.lang.Thread.run(Thread.java:744) [na:1.8.0]
Caused by: javax.mail.MessagingException: Could not connect to SMTP host: smtp.gmail.com, port: 465, response: -1
at com.sun.mail.smtp.SMTPTransport.openServer(SMTPTransport.java:2042) ~[javax.mail-1.5.4.jar:1.5.4]
at com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:697) ~[javax.mail-1.5.4.jar:1.5.4]
at javax.mail.Service.connect(Service.java:364) ~[javax.mail-api-1.5.4.jar:1.5.4]
... 11 common frames omitted

This example works: https://github.com/sbglasius/g3-tour-de-plugin-demo/blob/mail/grails-app/conf/application.groovy (notice, that it's on the tag mail)
The presentation is here: https://www.youtube.com/watch?v=RuK90qD6RJU
Notice, that the password in my example is set in an external file.

@sbglasius  Today i tried the plugin for grails 3.0.2  and everything is working fine. I guess there is a issue for  grails 3.1.0 . I tried installing the plugin several times but still the error is same.
Which version of grails did you use for the presentation?

I used Grails 3.2.3

Thanks . It worked on other grails version . But there is a issue for 3.1.0


Batch commits to the state and block store

Currently, state is committed to the block and state store using asynchronous calls followed by a synchronous call at the end.
We need to investigate whether explicitly batching them improves performance. In particular, consider the work done in :
https://github.com/tendermint/tendermint/pull/6067
https://github.com/tendermint/tendermint/pull/6018
and issue: https://github.com/tendermint/tendermint/issues/5888
The goal of this is two fold:

Increase atomicity guarantees
Improve performance
DoD:

[ ] Understand, from a DB perspective whether atomicity is actually increased or not
[ ] Evaluate whether there are corner cases where the batch becomes very big and understand how the DB handles this underneath (memory vs. disk)
[x] State is saved in batches with an indication on performance improvement

This task has been completed but initial go benchmarking suggests that the performance is actually downgraded. The plan is to rerun the experiments once we change the key ordering during Q4 2023. This would then help make the final decision on whether this is to be merged or rejected.

Understand, from a DB perspective whether atomicity is actually increased or not

Atomicity is increasing, as mentioned in https://github.com/tendermint/tendermint/pull/6018 because it is all or nothing in the case of the batch.

Evaluate whether there are corner cases where the batch becomes very big and understand how the DB handles this underneath (memory vs. disk)

LSMs don't handle big batches very well (1). The ideal for goleveldb is ~ 100KB (2), which is more or less equal to our block part size (64kB).
Here are the results from running the Anton's benchmark on my local PC:

Benchmark
```go
func BenchmarkBlockStore_SaveBlockWithExtendedCommit(b *testing.B) {
	dbTypes := []dbm.BackendType{
		dbm.GoLevelDBBackend,
	}
	NTXs := int64(1024)
for _, dbType := range dbTypes {
	state, bs, cleanup := makeStateAndBlockStoreSpecificBackend(dbType)
	b.Run(fmt.Sprintf("DBType:%s;NTxs:%d", dbType, NTXs),
		func(b *testing.B) {
			for i := 0; i < b.N; i++ {
				height := bs.Height() + 1
				block := state.MakeBlock(height, test.MakeNTxs(height, NTXs), new(types.Commit), nil, state.Validators.GetProposer().Address)
				validPartSet, err := block.MakePartSet(types.BlockPartSizeBytes)
				if err != nil {
					b.Error(err)
				}
				seenCommit := makeTestExtCommit(block.Header.Height, cmttime.Now())

				bs.SaveBlockWithExtendedCommit(block, validPartSet, seenCommit)
			}
		})

	cleanup()
}

}
type cleanupFunc func()
func makeStateAndBlockStoreSpecificBackend(backendType dbm.BackendType) (sm.State, *BlockStore, cleanupFunc) {
config := test.ResetTestRoot("blockchain_reactor_test")
blockDB, err := dbm.NewDB("block", backendType, config.DBDir())
if err != nil {
panic(fmt.Errorf("error creating %s: %w", backendType, err))
}
stateDB, err := dbm.NewDB("state", backendType, config.DBDir())
if err != nil {
panic(fmt.Errorf("error creating %s: %w", backendType, err))
}
stateStore := sm.NewStore(stateDB, sm.StoreOptions{
DiscardABCIResponses: false,
})
state, err := stateStore.LoadFromDBOrGenesisFile(config.GenesisFile())
if err != nil {
panic(fmt.Errorf("error constructing state from genesis file: %w", err))
}
return state, NewBlockStore(blockDB), func() { os.RemoveAll(config.RootDir) }
}
</details>

batching / 1 MB block / goleveldb
155921071 ns/op
NO batching / 1 MB block / goleveldb
134169606 ns/op
batching / 10 MB block / goleveldb
1135896143 ns/op
NO batching / 10 MB block / goleveldb
1096632817 ns/op

My recommendation is NOT to save the block in a single batch.


Still Maintained?

Is this rep still maintained?

Barely, but yeah. It's not the project I have the most motivation for so I try to keep my effort relatively low. If there are any major problems I'll fix them though.

ok thanks


catch all item's found nodes (via class) with a List

major change to this.get = function(item, valueNames) (~line 530):
-values[valueNames[i]] = []; use a List to catch all item's found nodes via class, not just the first. VERY useful in filter calls.
-if (!founds) continue; less vulnerable to nullpointer error if class not found.
-all tabs changed to spaces

also, sometimes matching is populated but not used..

Thanks fo the pull request! I will look deeper in to your improvements as soon as possible!

Sure! This is a major change, as the values map is a string to a list(of strings), not a string to a string. Eg:
var elms = h.getByClass(v, item.elm);
for (var e in elms) {
elms[e].innerHTML = values[v][e];
}
Note: I haven't tested this with explicit adding/removing list items, just on parsing existing lists. (http://steveandbetsy.com/resorts/)


Docs sidebar cache issues?

Something I’ve observed many times is that we add a page, like #2615, and it doesn’t show up in the sidebar until you enter the URL directly into your browser once. It’s as if the sidebar content is being aggressively cached in the browser. No amount of refreshes will fix it, but clearing website data or using a private window will. @orta any idea what’s going on here or where to begin looking?

Off hand, no, I'm not sure I've seen that behavior during dev.
There's no additional caching WRT the sidebar, it gets rendered directly into the HTML (e.g. is visible on CURL)  which should always be grabbed by a browser for the main route

My best guess is either:

Gatsby PWA shenanigans (we're two major semvers away, so I was thinking of trying top update over the winter break) - I tried to not let any PWA stuff happen on the site (I dont see a service worker when I open it now, so this is very unlikely

Deployment shenanigans? Perhaps we need some sort of caching headers on the HTML files when says when the file's content has changed?  The app service side of the site is all the defaults


How to use GetX (or Obx) with Column instead of ListView

I want to update a Column with its children when I'm changing the .obs List, but it's only allowed to use with a ListView like so:
Obx(
  () => ListView.builder(
    itemBuilder: (context, index) => Text('Person ${model.persons.elementAt(index)}'),
    itemCount: model.persons.length,
    shrinkWrap: true,
  ),
),

and I'm trying to update the Column like so:
Obx(
  () => Column(
    children: [
      for (final person in model.persons) ...[
        Text('Person: $person'),
      ],
    ],
  ),
),

Here is full source code to reproduce problem https://gist.github.com/Andreigr0/38954aeb098984366f8aad5359431e50
How could I solve the problem?

 for (final person in model.persons.value) (value is required only for this situation)

I couldn't guess the solution would be that simple
Thanks