feat(behavior_velocity): support new traffic signal interface

Description
In this Pull Request, we are introducing support for the new traffic signal messages within the planning modules.
For more detailed information about the new messages, please refer to the associated issue linked below.

https://github.com/autowarefoundation/autoware.universe/issues/2567

Related links

https://github.com/autowarefoundation/autoware.universe/issues/2567
https://github.com/autowarefoundation/autoware_msgs/pull/48

Tests performed
Tested on a simple planning simulator.
Traffic Light Module
https://github.com/autowarefoundation/autoware.universe/assets/11865769/7781de68-23d4-48ff-a77d-a90c67b2cbbf
Crosswalk Module
https://github.com/autowarefoundation/autoware.universe/assets/11865769/e599c125-8907-4596-9db1-b1267e1b59cd
Notes for reviewers
For the traffic light module, I have removed the old messages and variables previously used to manage inputs from either Perception or External sources, given that the External input is no longer used.
Moreover, since the input Traffic Signal message, processed by traffic_signal_arbiter, already contains the selected data (either the signal with the highest confidence or the input from the V2X source), I have also removed the process to find the signal with the highest confidence.
For all other modules, I simply replaced the old traffic signal messages with the new ones.
Interface changes
As mentioned above, Planning modules will support only new interface.
The interface change for perception modules was done in this PR.

https://github.com/autowarefoundation/autoware.universe/pull/4084

Effects on system behavior

Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[x] The PR follows the pull request guidelines.
[x] The PR has been properly tested.
[x] The PR has been reviewed by the code owners.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.
[ ] The PR is ready for merge.

After all checkboxes are checked, anyone who has write access can merge the PR.

Could you review the code that you are responsible for? :pray:
traffic light: @satoshi-ota  (@tkimura4 )
crosswalk: @satoshi-ota
intersection: @soblin

Since the TrafficLightElement is replaced with TrafficSignalElement in this PR, I should be adjusted in this PR as well.

CI result: TIER IV INTERNAL LINK
NOTE:
As the scenario simulator doesn't yet support the new traffic signal interface, some scenarios related to the traffic signal fail. However, for all other scenarios, we have confirmed that there is no degradation.

Modified the code to continue instead of return false in cases where multiple regulatory elements exist in a crosswalk.
https://github.com/autowarefoundation/autoware.universe/pull/4133/commits/a6c86419c1dba542ac62de9696cb5577d5c9ebab

I will merge this PR after scenario simulator supports the new traffic signal interface.
It is scheduled to be done by next week.


⚠ Mobitopup has degraded performance

In 36ce6aa, Mobitopup (https://napcard.voz.tech) experienced degraded performance:

HTTP code: 200
Response time: 7020 ms

Resolved: Mobitopup performance has improved in 2d138a9.


Added allowTextInput property

Q
A

Bug fix?
[ ]

New feature?
[ x ]

New sample?
[ ]

Related issues?
fixes #1094

What's in this Pull Request?
Exposed the allowTextInput property. Developer can now choose whether the user can add dates as text value rather than picking one from the date picker.

@milanholemans many thanks for the PR. I just noticed that the previous default value was true and now is false so wondering if this could cause issues to people who upgrade and don't notice the change. Could this be set to true by default, or did you experience any issues?

@milanholemans many thanks for the PR. I just noticed that the previous default value was true and now is false so wondering if this could cause issues to people who upgrade and don't notice the change. Could this be set to true by default, or did you experience any issues?

The thing is, I noticed that the DatePicker component of office-fabric-ui uses false as default value. That's why I made it false here by default as well. I can change it to true if needed.

@AJIXuMuK what are your thoughts regarding changing this default value? Should we avoid it or go ahead and ensure that it's documented/announced?

It has been changed from false to true last year, check this PR #971.

@joelfmrodrigues I would not change the defaults without a necessity.
@milanholemans - thank you for providing this info.
This is our mistake. We should have implemented this as property right away.
But for now - let's leave the default as is.

@AJIXuMuK @joelfmrodrigues I changed the default value to true.

@milanholemans many thanks, it has now been merged


Added ability to cancel commands with CTRL + C

CTRL + C will cancel a running command (if any running) by calling the cancel function registered and the cancel function on the promise if it exists
#45

Looks like the test is failing on older versions of node because we can't use const widely yet without Babel or other compilers.

Didn't realize i was using const.
Thanks for catching it

This looks great! Thanks.

@jackyjieliu See comments in the commit.

As discussed, the Vorpal action should be able to use this.cancel() internally to cancel itself. This should also emit the event.

Added ability to cancel commands with CTRL + C #45


Implement Polish translation

Prelude
I'm aware that this is already touched on in an earlier pull request (#2623), however that PR has been abandoned since late January of this year(!), and I don't believe it is going to be picked back up at this point. There is demand for an up-to-date localisation, as Bluesky's international userbase is rapidly growing and the app has evolved a lot since then.
Description
This pull request adds Polish language support to the app. Please note that some strings may certainly be rough around the edges, as the immense amount of strings in the Bluesky app was a lot for me to do by myself, this is my first time tackling a translation project of this scale. With that in mind, proofreading and suggestions are both highly welcome.

In the latest code, we've also implemented localization for dates, which required some additional changes to dates.ts.
I've created a pull request to include Polish as part of this.

@auroursa
Merged, thank you.

It's great to see a Polish localisation!
The devs usually ask for localisation PRs to be reviewed by at least one other native speaker, is there someone you could ask to do that?

I am native polish speaker. How can I contribute?

Hi, I'm native in polish and I'm currently reviewing the code though it might take a while :)

I am native polish speaker. How can I contribute?

@isulim Read through the messages.po file and leave feedback on translations that you think could be improved. You can suggest an alternate translation using the button with ± :)

Yes thank you everybody! To get this initial one merged, if another native speaker could just give it an initial review. We don't have to get really detailed, but we want to make sure it's close enough!

Yes thank you everybody! To get this initial one merged, if another native speaker could just give it an initial review. We don't have to get really detailed, but we want to make sure it's close enough!

Right now I have reviewed about half of this, I should finish it tomorrow as it's pretty long. As of right now I made less than 100 suggestions.

Hi, thanks to everyone who's taken interest in reviewing this translation!
I'm currently waiting for reviews before touching this PR at all. Heads up that if something major gets merged in the meantime, I may do a second pass before merge for coverage's sake.

Implemented most of the new suggestions. Two notes:

I'm gonna keep "interagować" in more casual contexts or shorter strings, simply because it's easier to read at a glance and has less risk of causing text overflow. Open to additional opinions on this
I've had a sentimental connection to the rhyme since it was first pointed out ;D

Implemented most of the new suggestions. Two notes:

I'm gonna keep "interagować" in more casual contexts or shorter strings, simply because it's easier to read at a glance and has less risk of causing text overflow. Open to additional opinions on this
I've had a sentimental connection to the rhyme since it was first pointed out ;D

Alright, let's keep it and see how live users interact (hyhyhy) with this version :D

Alright, this seems fully reviewed now. If nothing big happens soon, consider this ready for merge.

All done

All done

@surfdude29 @pfrazee

I suggest go back to the previous symbols. "tys." is too long.

Looks ok on my device.
Probably not the translation issue.

You also have this problem, but not as big as mine. Look closer at the like symbol in your screenshot.


MARK       all  --  anywhere             anywhere             socket --transparent /* cilium: any->pod redirect proxied traffic to host proxy / MARK set 0x200
TPROXY     tcp  --  anywhere             anywhere             mark match 0x482e0200 / cilium: TPROXY to host default/cilium-gateway-my-gateway/listener proxy / TPROXY redirect <IP_ADDRESS>:11848 mark 0x200/0xffffffff
TPROXY     udp  --  anywhere             anywhere             mark match 0x482e0200 / cilium: TPROXY to host default/cilium-gateway-my-gateway/listener proxy / TPROXY redirect <IP_ADDRESS>:11848 mark 0x200/0xffffffff
TPROXY     tcp  --  anywhere             anywhere             mark match 0xdb860200 / cilium: TPROXY to host cilium-dns-egress proxy / TPROXY redirect <IP_ADDRESS>:34523 mark 0x200/0xffffffff
TPROXY     udp  --  anywhere             anywhere             mark match 0xdb860200 / cilium: TPROXY to host cilium-dns-egress proxy */ TPROXY redirect <IP_ADDRESS>:34523 mark 0x200/0xffffffff
But still no joy:
curl <IP_ADDRESS> -v

Trying <IP_ADDRESS>:80...
Connected to <IP_ADDRESS> (<IP_ADDRESS>) port 80 (#0)

GET / HTTP/1.1
Host: <IP_ADDRESS>
User-Agent: curl/8.1.2
Accept: /

< HTTP/1.1 503 Service Unavailable
< content-length: 91
< content-type: text/plain
< date: Mon, 14 Aug 2023 15:07:46 GMT
< server: envoy
<

Connection #0 to host <IP_ADDRESS> left intact
upstream connect error or disconnect/reset before headers. reset reason: connection failure

Yep, that would explain the issue. Most likely you've got one of two things:

You don't have CONFIG_NETFILTER_XT_MATCH_SOCKET enabled in your kernel config
(like me) you're running on WSL2 which doesn't support modprobe so m.haveSocketMatch is never set to true in this piece of code

I found the issue with the module not being loaded.
My host is running Alpine linux and xt_socket module is listed in modules.alias not modules.builtin.
cat /lib/modules/6.1.44-0-lts/modules.alias | grep xt_socket
alias ip6t_socket xt_socket
alias ipt_socket xt_socket
The #23863 had a similar issue. The solution #23953 needs to search in modules.alias too.

@virtualm2000 you can have a look at your cilium agent logs to see if it complains about any other IPT-related modules not being loaded

@virtualm2000 you can have a look at your cilium agent logs to see if it complains about any other IPT-related modules not being loaded

No other errors or warnings.
I get a clean:
level=info msg="Iptables rules installed" subsys=iptables
level=info msg="Iptables proxy rules installed" subsys=iptables

I wasn't aware of such issue. I am on vacation now.
".alias" is a file containing aliases and alternative names for module. To fix this issue, it should be checked if a requested module has an alias and use the base module name in a ".builtin" check, otherwise the module should be loaded dynamically or fail if cannot be loaded (non-existing module or other already implemented cases).
I can take a look in the weekend ;)

I wasn't aware of such issue. I am on vacation now.
".alias" is a file containing aliases and alternative names for module. It does not means it has been already loaded.
To fix this issue, it should be checked if a requested module has an alias and use the base module name in a ".builtin" check, otherwise the module should be loaded dynamically or fail if cannot be loaded (non-existing module or other already implemented cases).
Aliases can be defined also in other places, should that be handled as well? (modprobe.conf files)
I can take a look in the weekend ;)
I am thinking if the ".bin" formats should be added too.

My error was that the modules could not be loaded however the function listModules will check only for builtin and /proc/modules. In my distribution (Alpine 3.18) xt_socket is compiled as separate module which if loaded with modprobe will then be detected  in /proc/modules.
Probably a new function is need it in listModules to check if the module is present, something like find /lib/modules/$(uname -r) -type f -name '*.ko*', and then load the module for listLoadedModules.

I wasn't aware of such issue. I am on vacation now.

".alias" is a file containing aliases and alternative names for module. It does not means it has been already loaded.

To fix this issue, it should be checked if a requested module has an alias and use the base module name in a ".builtin" check, otherwise the module should be loaded dynamically or fail if cannot be loaded (non-existing module or other already implemented cases).

Aliases can be defined also in other places, should that be handled as well? (modprobe.conf files)

I can take a look in the weekend ;)

I am thinking if the ".bin" formats should be added too.

My error was that the modules could not be loaded however the function listModules will check only for builtin and /proc/modules. In my distribution (Alpine 3.18) xt_socket is compiled as separate module which if loaded with modprobe will then be detected  in /proc/modules.
Probably a new function is need it in listModules to check if the module is present, something like find /lib/modules/$(uname -r) -type f -name '*.ko*', and then load the module for listLoadedModules.

Yes, but there is no such module as "xt_socket". When loading "xt_socket", "ipt_socket" and "ip6t_socket" is being loaded.
Simply searching for a file name in the directory will not work.

I am working on fix, if you have cases where modprobe misbehaves, let me know.

No problems with manually loading the module on the host:
~$ lsmod | grep xt_socket
~$ modprobe xt_socket -v
insmod /lib/modules/6.1.46-0-lts/kernel/net/ipv6/netfilter/nf_socket_ipv6.ko.gz
insmod /lib/modules/6.1.46-0-lts/kernel/net/ipv4/netfilter/nf_socket_ipv4.ko.gz
insmod /lib/modules/6.1.46-0-lts/kernel/net/netfilter/xt_socket.ko.gz
~$ lsmod | grep xt_socket
xt_socket              16384  0
nf_socket_ipv4         16384  1 xt_socket
nf_socket_ipv6         20480  1 xt_socket
nf_defrag_ipv6         24576  3 nf_conntrack,xt_socket,xt_TPROXY
nf_defrag_ipv4         16384  3 nf_conntrack,xt_socket,xt_TPROXY
x_tables               61440  15 ip6table_filter,xt_conntrack,iptable_filter,ip6table_nat,xt_socket,xt_comment,ip6_tables,xt_TPROXY,xt_CT,iptable_raw,ip_tables,iptable_nat,ip6table_mangle,iptable_mangle,xt_mark
But even with manually loaded module clearing the errors with iptables and having the correct iptables rules set it still fails with the gateway api. For me it's the looping of the SYN Ack packet between _host and _net interface.

I believe I'm also having this issue, I'll add my details here as well in case it sheds additional light on the issue or if someone can hint in case it is different.
I'm using Gateway API, BGP, etc. with config-map details as follows:
  agent-not-ready-taint-key: node.cilium.io/agent-not-ready
  arping-refresh-period: 30s
  auto-direct-node-routes: "false"
  bpf-lb-algorithm: maglev
  bpf-lb-external-clusterip: "false"
  bpf-lb-map-max: "65536"
  bpf-lb-mode: dsr
  bpf-lb-sock: "false"
  bpf-map-dynamic-size-ratio: "0.0025"
  bpf-policy-map-max: "16384"
  bpf-root: /sys/fs/bpf
  cgroup-root: /sys/fs/cgroup
  cilium-endpoint-gc-interval: 5m0s
  cluster-id: "0"
  cluster-name: default
  cni-exclusive: "true"
  cni-log-file: /var/run/cilium/cilium-cni.log
  cnp-node-status-gc-interval: 0s
  custom-cni-conf: "false"
  debug: "true"
  debug-verbose: flow
  disable-cnp-status-updates: "true"
  egress-gateway-reconciliation-trigger-interval: 1s
  enable-auto-protect-node-port-range: "true"
  enable-bgp-control-plane: "true"
  enable-bpf-clock-probe: "false"
  enable-bpf-masquerade: "true"
  enable-endpoint-health-checking: "true"
  enable-envoy-config: "true"
  enable-gateway-api: "true"
  enable-gateway-api-secrets-sync: "true"
  enable-health-check-nodeport: "true"
  enable-health-checking: "true"
  enable-hubble: "true"
  enable-ingress-controller: "true"
  enable-ingress-secrets-sync: "true"
  enable-ipv4: "true"
  enable-ipv4-big-tcp: "false"
  enable-ipv4-masquerade: "true"
  enable-ipv6: "true"
  enable-ipv6-big-tcp: "false"
  enable-ipv6-masquerade: "true"
  enable-k8s-networkpolicy: "true"
  enable-k8s-terminating-endpoint: "true"
  enable-l2-neigh-discovery: "true"
  enable-l7-proxy: "true"
  enable-local-redirect-policy: "false"
  enable-policy: default
  enable-remote-node-identity: "true"
  enable-sctp: "false"
  enable-svc-source-range-check: "true"
  enable-vtep: "false"
  enable-well-known-identities: "false"
  enable-xt-socket-fallback: "true"
  enforce-ingress-https: "true"
  external-envoy-proxy: "false"
  gateway-api-secrets-namespace: cilium-secrets
  hubble-disable-tls: "false"
  hubble-listen-address: :4244
  hubble-socket-path: /var/run/cilium/hubble.sock
  hubble-tls-cert-file: /var/lib/cilium/tls/hubble/server.crt
  hubble-tls-client-ca-files: /var/lib/cilium/tls/hubble/client-ca.crt
  hubble-tls-key-file: /var/lib/cilium/tls/hubble/server.key
  identity-allocation-mode: crd
  identity-gc-interval: 15m0s
  identity-heartbeat-timeout: 30m0s
  ingress-default-lb-mode: shared
  ingress-lb-annotation-prefixes: service.beta.kubernetes.io service.kubernetes.io
    cloud.google.com
  ingress-secrets-namespace: cilium-secrets
  ingress-shared-lb-service-name: cilium-ingress
  install-no-conntrack-iptables-rules: "false"
  ipam: kubernetes
  ipam-cilium-node-update-rate: 15s
  ipv4-native-routing-cidr: <IP_ADDRESS>/0
  ipv6-native-routing-cidr: fd00::/16
  k8s-client-burst: "10"
  k8s-client-qps: "5"
  kube-proxy-replacement: strict
  kube-proxy-replacement-healthz-bind-address: ""
  mesh-auth-enabled: "true"
  mesh-auth-gc-interval: 5m0s
  mesh-auth-queue-size: "1024"
  mesh-auth-rotated-identities-queue-size: "1024"
  monitor-aggregation: medium
  monitor-aggregation-flags: all
  monitor-aggregation-interval: 5s
  node-port-bind-protection: "true"
  nodes-gc-interval: 5m0s
  operator-api-serve-addr: <IP_ADDRESS>:9234
  preallocate-bpf-maps: "false"
  procfs: /host/proc
  proxy-connect-timeout: "2"
  proxy-max-connection-duration-seconds: "0"
  proxy-max-requests-per-connection: "0"
  proxy-prometheus-port: "9964"
  remove-cilium-node-taints: "true"
  routing-mode: native
  set-cilium-is-up-condition: "true"
  set-cilium-node-taints: "true"
  sidecar-istio-proxy-image: cilium/istio_proxy
  skip-cnp-status-startup-clean: "false"
  synchronize-k8s-nodes: "true"
  tofqdns-dns-reject-response-code: refused
  tofqdns-enable-dns-compression: "true"
  tofqdns-endpoint-max-ip-per-hostname: "50"
  tofqdns-idle-connection-grace-period: 0s
  tofqdns-max-deferred-connection-deletes: "10000"
  tofqdns-proxy-response-max-delay: 100ms
  unmanaged-pod-watcher-interval: "15"
  vtep-cidr: ""
  vtep-endpoint: ""
  vtep-mac: ""
  vtep-mask: ""
  write-cni-conf-when-ready: /host/etc/cni/net.d/05-cilium.conflist

The Gateway and HTTPRoute seem to have valid status:
$ kubectl get gateway
NAME         CLASS    ADDRESS       PROGRAMMED   AGE
my-gateway   cilium   <IP_ADDRESS>   True         4h33m

On Talos linux 1.5, all of the iptables machinery seems to be working:
Chain CILIUM_PRE_mangle (1 references)
 pkts bytes target     prot opt in     out     source               destination
   46  3058 MARK       all  --  *      *       <IP_ADDRESS>/0            <IP_ADDRESS>/0            socket --transparent /* cilium: any->pod redirect proxied traffic to host proxy */ MARK set 0x200
   11   660 TPROXY     tcp  --  *      *       <IP_ADDRESS>/0            <IP_ADDRESS>/0            mark match 0x42460200 /* cilium: TPROXY to host home-assistant/cilium-gateway-my-gateway/listener proxy */ TPROXY redirect <IP_ADDRESS>:17986 mark 0x200/0xf
fffffff
    0     0 TPROXY     udp  --  *      *       <IP_ADDRESS>/0            <IP_ADDRESS>/0            mark match 0x42460200 /* cilium: TPROXY to host home-assistant/cilium-gateway-my-gateway/listener proxy */ TPROXY redirect <IP_ADDRESS>:17986 mark 0x200/0xf
fffffff
    0     0 TPROXY     tcp  --  *      *       <IP_ADDRESS>/0            <IP_ADDRESS>/0            mark match 0x15b10200 /* cilium: TPROXY to host cilium-dns-egress proxy */ TPROXY redirect <IP_ADDRESS>:45333 mark 0x200/0xffffffff
    0     0 TPROXY     udp  --  *      *       <IP_ADDRESS>/0            <IP_ADDRESS>/0            mark match 0x15b10200 /* cilium: TPROXY to host cilium-dns-egress proxy */ TPROXY redirect <IP_ADDRESS>:45333 mark 0x200/0xffffffff
    0     0 TPROXY     tcp  --  *      *       <IP_ADDRESS>/0            <IP_ADDRESS>/0            mark match 0x7a440200 /* cilium: TPROXY to host kube-system/cilium-ingress/listener proxy */ TPROXY redirect <IP_ADDRESS>:17530 mark 0x200/0xffffffff
    0     0 TPROXY     udp  --  *      *       <IP_ADDRESS>/0            <IP_ADDRESS>/0            mark match 0x7a440200 /* cilium: TPROXY to host kube-system/cilium-ingress/listener proxy */ TPROXY redirect <IP_ADDRESS>:17530 mark 0x200/0xffffffff

However, in my case, rather than looping on cilium_host/net as others here have described, the SA packets are going out on the host interface (bond0.95):
# tcpdump -n -i any tcp port 6052
tcpdump: data link type LINUX_SLL2
tcpdump: verbose output suppressed, use -v[v]... for full protocol decode
listening on any, link-type LINUX_SLL2 (Linux cooked v2), snapshot length 262144 bytes
21:04:43.271845 lxcefa890528704 Out IP <IP_ADDRESS>.38139 > <IP_ADDRESS>.6052: Flags [S], seq<PHONE_NUMBER>, win 64240, options [mss 1460,sackOK,TS val<PHONE_NUMBER> ecr 0,nop,wscale 7], length 0
21:04:43.271886 lxcefa890528704 In  IP <IP_ADDRESS>.6052 > <IP_ADDRESS>.38139: Flags [S.], seq<PHONE_NUMBER>, ack<PHONE_NUMBER>, win 65160, options [mss 1460,sackOK,TS val<PHONE_NUMBER> ecr<PHONE_NUMBER>,nop,wscale 7], length 0
21:04:43.271907 bond0.95 Out IP <IP_ADDRESS>.6052 > <IP_ADDRESS>.38139: Flags [S.], seq<PHONE_NUMBER>, ack<PHONE_NUMBER>, win 65160, options [mss 1460,sackOK,TS val<PHONE_NUMBER> ecr<PHONE_NUMBER>,nop,wscale 7], length 0
21:04:43.271911 bond0 Out IP7 (invalid)
21:04:43.271915 eno1  Out IP7 (invalid)
21:04:44.302476 lxcefa890528704 Out IP <IP_ADDRESS>.38139 > <IP_ADDRESS>.6052: Flags [S], seq<PHONE_NUMBER>, win 64240, options [mss 1460,sackOK,TS val<PHONE_NUMBER> ecr 0,nop,wscale 7], length 0
21:04:44.302540 lxcefa890528704 In  IP <IP_ADDRESS>.6052 > <IP_ADDRESS>.38139: Flags [S.], seq<PHONE_NUMBER>, ack<PHONE_NUMBER>, win 65160, options [mss 1460,sackOK,TS val<PHONE_NUMBER> ecr<PHONE_NUMBER>,nop,wscale 7], length 0
21:04:44.302565 bond0.95 Out IP <IP_ADDRESS>.6052 > <IP_ADDRESS>.38139: Flags [S.], seq<PHONE_NUMBER>, ack<PHONE_NUMBER>, win 65160, options [mss 1460,sackOK,TS val<PHONE_NUMBER> ecr<PHONE_NUMBER>,nop,wscale 7], length 0
21:04:44.302570 bond0 Out IP7 (invalid)
21:04:44.302575 eno1  Out IP7 (invalid)
21:04:44.302589 lxcefa890528704 In  IP <IP_ADDRESS>.6052 > <IP_ADDRESS>.38139: Flags [S.], seq<PHONE_NUMBER>, ack<PHONE_NUMBER>, win 65160, options [mss 1460,sackOK,TS val<PHONE_NUMBER> ecr<PHONE_NUMBER>,nop,wscale 7], length 0
21:04:44.302596 bond0.95 Out IP <IP_ADDRESS>.6052 > <IP_ADDRESS>.38139: Flags [S.], seq<PHONE_NUMBER>, ack<PHONE_NUMBER>, win 65160, options [mss 1460,sackOK,TS val<PHONE_NUMBER> ecr<PHONE_NUMBER>,nop,wscale 7], length 0
21:04:44.302599 bond0 Out IP7 (invalid)
21:04:44.302601 eno1  Out IP7 (invalid)

I can't provide a fix in a acceptable timeline right now, sorry.

I can't provide a fix in a acceptable timeline right now, sorry.

For the module issue it's easier to set your favorite linux flavour to load the missing module at boot. Maybe specified in documentation.  For example in alpine 3.18 I use:
cat << 'EOF' > /etc/modules-load.d/cilium.conf
xt_socket
iptable_raw
EOF

Just fyi: I have updated to cilium 1.14.2 and now my gateway works as expected... maybe my issue was not related to the reportes issue here...

Issue was resolved after loading the iptable_raw module into my nodes.  @TheAifam5 have you had a chance to work on your fix more?

Writing out an observation that I just had with some of the prerelease versions of 1.15.0-rc.0  when setting up a fresh cluster.  Cilium Ingress Controller would return upstream connect error or disconnect/reset before headers. reset reason: connection failure
Reverting to known working 1.15.0-pre.1 setup and then converting back to 1.15-rc0 appeared to fix the issue.  Note that I followed the deprecation tunnel: disabled -> routingMode: native as mentioned in release notes.  https://github.com/cilium/cilium/pull/29053
Hardware:
Pine64 SoQuartz
OS:
Plebian (Debian 12)
Kernel:
uname -a
Linux soquartz3 6.1.0-10-arm64 #1 SMP Debian 6.1.37-1 (2023-07-03) aarch64 GNU/Linux

Kubernetes Version
v1.28.4+k3s2
Cilium Version
chart: cilium
repoURL: https://helm.cilium.io/
targetRevision: 1.15.0-rc.0
Will open a dedicated ticket if I rebuild my cluster and reproduce the issue.


Less Memory Usage / More Comments in NeedlemanWunschAligner

For these dynamic programming problems, when traversing through the
matrix one must store the entire traceback matrix,
but the scores are only needed for the current row and the row above it.
In the current implementation, we only use two rows for the "top
scoring" (and match) matrix, but fill out entire matrices for the
deletion and insert (or vertical and horizontal) matrices.  This is
inefficient, as we then need 2 x M x N memory rather than 2 x 2 x N
memory.  I switched this to only use the smaller amount.  Additionally:

Changed the minimum score on the edges from an arbitray low number to

a constant near Int32.MinValue for clarity.

Added more comments throughout.

Rather than have three arrays, I used 1 array of a struct which may

help memory locality for very large global alignments.

Added more unit tests that directly compare against EMBOSS Needle

alignment program, found and reported a bug in NEEDLE while doing

that...

Change all the vague category "Priority2" labels in NW tests to a

newer version.

I ran into some problems with the NW aligner using the affine aligner, and this pull request is really just about adding more tests to continue to verify the expected behavior, and while I was doing that I rewrote the algorithm to make it simpler to read and restructure a bit.
The only functional change should be not using as much memory.  I changed it so that rather than have two full matrices, it only kept around the 2 rows it needed for the Gap matrices.  This should mean that for an alignment of a 5669 x 5068 sequence, we will use 2506842 bytes, instead of<PHONE_NUMBER> bytes, for a savings of about ~229 MB.
Profiling this shows that we do save about this much memory and in single threaded land it is only about 7% faster, but does use less memory, which should help if a system is stressed.

Memory
Time
Version

360.5
20.214
Master

256.7
20.123
Master

433.6
20.25
Master

471.3
20.69
Master

451.2
20.229
Master

241.1
18.972
New

160.5
18.82
New

195.8
18.6
New

223.9
18.8
New

Further memory reduction could be had by storing the traceback matrices for the gaps as bytes instead of ints, but all of this only matters for long global alignments, which probably shouldn't be too frequent anyway.


Problem while trying to install @vue-use-form/yup yup

Hello, I was looking for a form package for Vue and I loved vue-use-form!
I want to use yup validation but I'm having some problems.
Scenario:
Windows 11 Home
Wsl with Ubuntu
Docker container Node
Nuxt 3 Aplication
Npm version: 10.2.4
Node version: v21.6.2
I tryied to install the package many times and always get the same error:
npm ERR! code EUNSUPPORTEDPROTOCOL
npm ERR! Unsupported URL Type "workspace:": workspace:*

Complete log:

Sorry for bad english [🇧🇷]

feel free for your English.
for this project, i don't have much time to mantain it, so this problem may can't be solved.
but it's welcome for you if you want to maintain this project, i will give you permissions about this project.
I'm looking forward to your reply

Hi @SnowingFox , how can i contribute / maintain this project? I didn't see any document about planning, convention when we joined to contributing this project.
Please let me know about this, i'm using react-hook-form for react and i wanna to maintain this project for vue.js

Hi @SnowingFox , how can i contribute / maintain this project? I didn't see any document about planning, convention when we joined to contributing this project.
Please let me know about this, i'm using react-hook-form for react and i wanna maintain this project for vue.js

yes, you can, you can contact me with x https://x.com/FoxSnowing


Update region exclusion list (Norway regions)

Updating the region rotation scheduler to exclude the new Norway-based regions until we can get them added to the test subscription.

The associated pipeline, plus another one, ran through the changes without an error. Merging...


results mismatch？

DrugCLIP results in Table 1 and Table 3 should equal DrugCLIP-S results in Figure 5 ?
However, it clear to see the big diff

DrugCLIP-S is the one without HomoAug. You can find the results in Table 5


Ebiten skips drawing SubImages of 1 pixel width if the Y Scale is < 0.25

I'm trying to use Ebiten to create a raycaster game and found that my distant textures aren't being rendered until I get closer to them. In my stackoverflow question I asked since I wasn't sure if it was a bug in the raycasting method or not, I ultimately found the exact reproducible problem:
First take someImage and take a SubImage of it with a pixel width of 1, but a normal height, e.g.:
thisRect := image.Rect(15, 5, 16, 250)
myImage := someImage.SubImage(thisRect).(*ebiten.Image)

Next, scale just the Y to make it smaller and draw it:
op.GeoM.Scale(1.0, 0.25)
screen.DrawImage(myImage, op)

In that case you should see a small vertical 1 pixel width strip of the image. But, now reduce the Y scale below 0.25.
op.GeoM.Scale(1.0, 0.24)
screen.DrawImage(myImage, op)

The strip doesn't draw at all!
But it will draw at a Y scale less than 0.25 if the pixel width is 2 or more:
thisRect := image.Rect(15, 5, 17, 250)

So the question is whether the Ebiten scale rendering code can be adjusted to allow a pixel width of 1 to scale smaller than 0.25.

Hi, thank you for using Ebiten!
Unfortunately, such edge cases like rendering images with less-than-1-pixel scale depend on graphics drivers, so there is no guarantee about deterministic behavior. Thus, I'm afraid I probably cannot say the cause.

What about rendering with linear filter?

Oops sorry this is my misunderstanding, width is 1px but only Y is scaled?
Let me try, but could you give me a minimum code to reproduce this issue if possible? Thanks!

Here's a gist where I started with your highDPI example and made modifications, just tweak the values I mentioned in the issue description to see what I'm seeing.
https://gist.github.com/harbdog/075c527eb43df72fb2bd2657199185f1

OK so the cause was the mipmap selection: if the determinant of the geometry matrix is small, mipmap is used, but in your case, the mipmap level is so high that the image width becomes 0.
I think this was fixed in the latest Ebiten.

Here's a gist where I started with your highDPI example and made modifications, just tweak the values I mentioned in the issue description to see what I'm seeing.

Thanks! I could reproduce this without the fix (3cb9d18), and confirmed this doesn't happen with the fix.

Confirmed! Updated with go get -u github.com/hajimehoshi/ebiten/... and now have good rendering!
https://github.com/harbdog/raycaster-go

I'm glad to hear that. Thank you for reporting! Your game screenshot looks great!


Fixed error on save when inlines have extra > 0

The current js updates the ordering field also for blank extra rows, this is causing error on save if the inlined model has required fields.
This patch just updates the ordering field for inlines that have .has_original class.

Makes sense, thank you!

Ah hmm. Right after merging I notice that this breaks the case where you add new inlines on purpose -- those will now appear at the beginning instead of at the end, and that's bad. Dynamically created inlines' ordering fields should be updated. Or do you have a different view on this?

(I backed out the merge for now, but reopening the pull request for the moment does not work. :-(

This's an hard case... Dynamically created inlines should not be updated automatically if not populated, because if we don't populate them they should not be saved, but if the ordering field is populated django tries to save them and throws the error.

Maybe we haven't encountered the problem yet because we always use extra = 0 on inlines. This means that the problem of incomplete inlines only shows up when actively adding inlines (using the "add" button) and then not completing them.

Exactly, that's the reason.

Also in your scenario you can reproduce the error following these steps:

Add one or more inlines manually without populating them
Change order of existing inlines
Save

The second step isn't even necessary because we update the ordering values already when the formset:added event fires.

So; I added a note to the README and a default of extra=0 to the OrderableAdmin so that hopefully we may avoid this problem.
I think it is acceptable that validation fails when users manually add inlines (especially since those unsaved inlines can be removed again without losing any other edits)


Selecting multiple methods for scenarios

I thought there was a way to select multiple methods at once for interventions -- something like method='all'. This doesn't work though, and I couldn't find this in the documentation either. (This came up on a call with APHR when trying to model an education campaign intervention.)

Still an issue, but not sure how high priority it is.


Reference documentation for kube components

@tengqm quick question (more for my own understanding): assuming https://github.com/kubernetes/website/pull/13117 gets in, i guess we can replace all the html code in the markdown file with the new shortcode, is that correct?

/hold
Thanks @tengqm for the fast work! I would like to test the instructions and validate from an outside perspective before merging this so you don't need to do this again in 3 months :)
ref: #13396

@DanyC97 Code for generating the table can be found here. We were generating HTML tables directly because:

We want better control over the rendering of the table, see line 243-255 in the above file. This is not doable using plain markdown syntax.
We prefer scrollable tables over verbatim dumps of help message because the latter is very difficult o read.
Fortunately, we can embed HTML tables in markdown docs thanks to the markdown engine!

#13117 is solving a different problem regarding the syntax needed for markdown tables.

/lgtm
/approve

/hold cancel

@tengqm many thanks for the info!


Implement calling Rutabaga::event_poll(), to fix virglrenderer hang up

This PR fixes the timeout (5s) waiting for renderer poll() to finish virgl hang up properly this time.
This is acomplished by calling Rutabaga::event_poll() when we are notified using the eventfd
obtained from Rutabaga::poll_descriptor().
This refactors VhostUserGPUBackend to implement the VhostUserBackend trait instead of VhostUserBackendMut we were implementing before.
Registering a custom epoll handler required the refactoring - we cannot use the VhostUserBackendMut and put every method call behind a Mutex or RwLock like we were implicitly doing before. This is because we need to call VringEpollHandler::register_listener from within handle_event(), but VringEpollHandler::register_listener calls VhostUserBackend::num_queues, which would deadlock using the default blanket implemantion impl<T: VhostUserBackendMut> VhostUserBackend for RwLock<T> inside vhost-user-backend crate we were using before.
This refactor also has an advantage that we don't need to lock a mutex for simple calls like num_queues() method.

PR LGTM except for the few comments


fix: Add default values to validation

As explained by @mxstbr in https://github.com/gatsbyjs/gatsby/pull/27541#discussion_r510702038, it's a best practice to add default values in the validation schema

Codecov Report

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

@@           Coverage Diff           @@
##           master      #20   +/-   ##
=======================================
  Coverage   60.00%   60.00%
=======================================
  Files           1        1
  Lines          10       10
  Branches        3        3
=======================================
  Hits            6        6
  Misses          2        2
  Partials        2        2

Impacted Files
Coverage Δ

src/gatsby-node.js
60.00% <ø> (ø)

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 9c328fc...d1bd0d4. Read the comment docs.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


I have a question about testing!

Hi, i have a question about testing.  Why the test images use center crop instead of scaling  to 448x448 directly?

hi, i think the term_width is  the width of terminal, you can try to use command line to train the model or fix the term_width number.

hi, i think the term_width is the width of terminal, you can try to use command line to train the model or fix the term_width number.

Hi, I fix the term_width=50, then run util.py successfully. And I try to train the model by command line.  The error stills there. such as RuntimeError: Expected object of type torch.cuda.LongTensor but found type torch.cuda.IntTensor for argument #3 'index'. Do you meet the same problem?

@doublemanyu Hey, please show more error details for this ERROR, but I guess you need to change at here , just have a try.

@Xiaoccer I do not want to change the data distribution of training images and testing images. So I use the cropping strategy.

@yangze0930 So actually the accuracy on cropped test set can not be used as final performance?


Add a license

There's useful work here that could be used by others - would you be willing to add a license so it's clear that others can? Ideally MIT / Apache, but it's up to you. Thanks.

Thanks for the tip, @ion232. I added texts of licenses, both Apache and MIT.


Add spelling bee support

Add spelling bee support

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 100.00%. Comparing base (2baf56b) to head (bff0c4e).
Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff            @@
##              main       #12   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            4         4
  Lines           88       104   +16
  Branches        12        14    +2
=========================================
+ Hits            88       104   +16

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Implicit dependency on httpclient

If you try to use this gem, out of the box, you get:
NameError: uninitialized constant Zipmark::Adapters::HTTPClientAdapter::HTTPClient
It seems you are using the httpclient gem under the hood. It should be added to the gemspec so that users get the dependency correctly.

Is this because you offer a choice between httpclient and httparty? At the very least this should be part of the README?

@skwp yes there is a choice, as well as a simple adapter pattern to use any client library which can support the necessary features.  See the code in: https://github.com/zipmark/zipmark-ruby/tree/master/lib/zipmark/adapters
At the time of authorship httparty did not do digest auth correctly, but that may have changed.

@skwp also there arent great docs around this feature, but the client takes an optional adapter, if you are using a custom adapater, see the inline documentation here:
https://github.com/zipmark/zipmark-ruby/blob/master/lib/zipmark/client.rb#L19-L33

Thanks for the info


39149 default capabilites

- What I did
I extended the capabilities work started in:
https://github.com/moby/moby/commit/80d7bfd54d19cc25f4855b4f2e9e4ad2e47f86c0
To allow default capabilities configuration for the docker daemon.
- How I did it
I added a configuration option to set the default capabilities. I reused the code introduced in:
https://github.com/moby/moby/commit/80d7bfd54d19cc25f4855b4f2e9e4ad2e47f86c0
To handle the logic to add the caps as needed. I added some logic in the deamon configuration to copy the capabilities settings if they are set in the daemon but not the container's host config.
- How to verify it
If you start the daemon with the capabilities flag and run:
capsh --print
In the container. You should just see the capabilities you configured.
(I also updated the unit tests to use the code.)
- Description for the changelog

Added default capabilities configuration
- A picture of a cute animal (not mandatory but encouraged)

I see some extra deltas that are likely from how I did the fork. I am going to get re-base to get those cleaned up and sign the commit on the machine with my code and GPG key.


Remove --image from run command

Describe the proposal
Remove --image from run command
Make sure it is not being used and remove it.
Relates to #526
Release Note

RELEASE NOTE:

Need to remove this, was never supported.

+1


Lift Mustache/Stubble template engine from https://github.com/SteeltoeOSS/initializr

The legacy implementation using the Stubble Mustache library should be a good starting point for the API's template engine.

Duplicate of #2


KYLO-322 Add FindBugs static code analysis tool to the build configuration

FindBugs is a very powerful static code analysis tool, which examines Java bytecode and detects a wide range of issues.
This change adds FindBugs to Kylo build configuration so that FindBugs analysis is performed and a HTML report is generated.

Could you submit KYLO-322 as a separate pull request? Thanks!

Hi, sorry, a bit of Git confusion on my end. It's been corrected so that the pull request now contains the intended commit only.

I've been thinking about this and I think a good first use case is for pull requests. I think we should stick with SonarQube though since that's what we're using for development. Peter, do want to look into integrating the SonarSource GitHub plugin into our Travis CI build? An example is at the bottom of the linked page and we can use the public sonarqube.com for analysis.

@freastro, once I have some time, I'm happy to look into that. :) I think SonarSource is a great tool ...
...BUT: I still do think it is worth having this FindBugs configuration in place. Your build actually failing in front of your eyes after your latest changes in the workspace (hopefully on your local development machine, before committing/pushing it to the repo) is a much more powerful incentive to fix the code, than any tool generating reports somewhere maybe hours later might be.
Failing the build from FindBugs means poor quality code does NOT even REACH the repository.
Please note this change would only be the first step by generating reports one can review, but would NOT fail the build. (So it would not be a painful, long process to fix current issues first) and
I am more than happy to assist you ironing out any issues FindBugs detects by submitting small, targeted Git pull requests to address them.

@freastro I submitted a pull request to integrate SonarQube in Travis builds #16

OK, that's brilliant, it should help catching issues early. :)


[feature request] Also watch config files, like pyproject.toml in --watch mode.

It would be very nice if the watch mode would also watch for changes to configuration files.
Such a feature would make iterating on enabling new rulesets a lot easier.

Hi! Would it be okay if I take a look on this.
Proposal: detect changes in pyproject.toml and ruff.toml config files.

@mikeleppane - Definitely. I haven't thought too hard about what's required, but feel free to ask questions here as they come up. My guess is that, in the match rx.recv() loop in crates/ruff_cli/src/lib.rs, we can check if the file ends in .toml, then re-run the code to generate the pyproject_strategy and other variables that make it into the commands::run::run call.

Oh, we added this! From @mikeleppane in https://github.com/charliermarsh/ruff/pull/4169.


feat(pkg/catalog):  gateway CDS for SSL passthrough

Add cluster SNI passthrough for the multicluster gateway
Signed-off-by: Sean Teeling<EMAIL_ADDRESS>Please mark with X for applicable areas.
-->
Affected area:

Functional Area

New Functionality
[ ]

Documentation
[ ]

Install
[ ]

CLI Tool
[ ]

Certificate Management
[ ]

Control Plane
[ x]

Ingress
[ ]

Egress
[ ]

Networking
[ ]

Observability
[ ]

SMI Policy
[ ]

Sidecar Injection
[ ]

Security
[ ]

Upgrade
[ ]

Tests
[ ]

CI System
[ ]

Demo
[ ]

Performance
[ ]

Other
[ ]

Please answer the following questions with yes/no.

Does this change contain code from or inspired by another project?

Did you notify the maintainers and provide attribution?
No

Is this a breaking change?
No

Codecov Report

Merging #3599 (d63186a) into main (cd0bf12) will increase coverage by 0.00%.
The diff coverage is 82.85%.

@@           Coverage Diff           @@
##             main    #3599   +/-   ##
=======================================
  Coverage   67.22%   67.22%
=======================================
  Files         175      175
  Lines        8497     8507   +10
=======================================
+ Hits         5712     5719    +7
- Misses       2754     2757    +3
  Partials       31       31

Flag
Coverage Δ

unittests
67.22% <82.85%> (+<0.01%)
:arrow_up:

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

Impacted Files
Coverage Δ

pkg/envoy/cds/response.go
83.33% <76.19%> (-1.78%)
:arrow_down:

pkg/envoy/cds/cluster.go
94.73% <92.85%> (+0.10%)
:arrow_up:

pkg/kubernetes/announcement_handlers.go
71.42% <0.00%> (-5.72%)
:arrow_down:

pkg/endpoint/providers/kube/client.go
79.00% <0.00%> (+1.00%)
:arrow_up:

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 cd0bf12...d63186a. Read the comment docs.


Deployment getting stuck at finalizing the build phase

Fixed
Long deployments (over 20 minutes) no longer get stuck in the final stage.
This is done by switching to Server-Sent Events, sending heartbeat messages to keep alive the connection during long requests.
Plus, couple of improvements in FastAPI ASGI app to clean up the request properly (and show logs) if a client disconnects.

Looks good. Is the root cause confirmed to be fixed by the heartbeat thing?
Even if not, this looks useful and ready to merge.

Yes, I've checked it on the test cluster and it worked


vkquake: 1.13.0 -> 1.20.3

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/Novum/vkQuake/releases.
meta.description for vkquake is: "Vulkan Quake port based on QuakeSpasm"
meta.homepage for vkquake is: "https://github.com/Novum/vkQuake"
meta.changelog for vkquake is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.20.3 with grep in /nix/store/aqxw393w3p4dvzky668n30572sdmrwjp-vkquake-1.20.3
found 1.20.3 in filename of file in /nix/store/aqxw393w3p4dvzky668n30572sdmrwjp-vkquake-1.20.3

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
vkquake

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/aqxw393w3p4dvzky668n30572sdmrwjp-vkquake-1.20.3 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/aqxw393w3p4dvzky668n30572sdmrwjp-vkquake-1.20.3
ls -la /nix/store/aqxw393w3p4dvzky668n30572sdmrwjp-vkquake-1.20.3/bin

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

1 package built:

vkquake

Maintainer pings

Result of nixpkgs-review pr 184123 run on x86_64-linux 1

1 package built:

vkquake


Added WordPress plugin test cases file #32

Hi , I have added the WordPress plugin test cases in the Cases-Collection folder. The test cases are uploaded in csv format with Type of Test Case (Positive/Negative). Please merge the PR if you find the changes appropriate.

Thanks @nilesh-sengupta  for your contribution. Your PR has been accepted for the Hacktoberfest. Please fill this form to get the awesome LoginRadius swags. :)

Thanks for accepting my contribution in #hacktoberfest . I have filled the form.


dropdown is taking the complete screen sometimes even when maxHeight is set to a small number.

Everything works fine but sometimes dropdown container just take complete screen's height from top.

steps to reproducte:

open your app on web.
navigation to a screen where you are using dropdown.
Minimize the screen such that dropdown doesn't have enought space below it and now refresh.
After refreshing maximize the screen and the dropdown will take complete screen's height.

hi @abhinav0031 ,
How do i reproduce this problem on mobile device.

No this issue doesn't exist in mobile devices, will try to explain. What's happening is that for example when we switch to landscape mode on mobile device and dropdown doesn't have enough space, so it takes complete height of the screen and starts from the top, but when we switch back to portrait mode it behaves fine and doesn't take full screen. But in web it keeps taking full screen from top even when we maximize the screen or it have space.

hi @abhinav0031 ,
I have never tried this pack on the website before.

hi @abhinav0031 ,
Please try again with version 1.8.5.

no, didn't work still same issue.

hi @abhinav0031 ,
This issue is resolved in later version.


v 0.1.3 Update

Removed complex array properties vars.xxh from prob.vars
Memory Usage is Reduced for the computation
Restricted the FourierFlows support version to the v 0.10.1
New Timestepper LSRK54 support from https://github.com/FourierFlows/FourierFlows.jl/issues/334
New Feature: Dynamical Dashboard
Removed unused function

@JuliaRegistrator register()

Error while trying to register: Register Failed
@doraemonho, it looks like you are not a publicly listed member/owner in the parent organization (MHDFlows).
If you are a member/owner, you will need to change your membership to public. See GitHub Help

@JuliaRegistrator register()

Comments on pull requests will not trigger Registrator, as it is disabled. Please try commenting on a commit or issue.


Refs #4580 -- Drop support for Django 1.6, 1.7 and Python 2.6.

@yakky this is ready for review.

@timgraham awesome, I really like the addition / deletion ratio :)
Just waiting for develop to be opened for 3.3 submission

great work @timgraham I hope to get a decision today so we can move forward with develop being 3.3!

@timgraham thanks, this is great. Inaugurating the 3.3 development path with this PR!

Coverage decreased (-0.3%) to 89.083% when pulling c76aaa45e1ff537a06105c5c40252ced87f17f3f on timgraham:code-cleanup into f9d62da607e95864b78a6125aae17aa0c04d4dae on divio:develop.

Coverage decreased (-0.007%) to 89.326% when pulling 664426f7e25504cbfbb17e242d96b7f86c34703d on timgraham:code-cleanup into f9d62da607e95864b78a6125aae17aa0c04d4dae on divio:develop.


fix: fix data types for lane ids

Description
Lanelet2 uses int64 as data type to store ids.
However, there are inconsistency in control/planning modules to store the data.
I have searched the code in Autoware with keyword "lane_id" and "lanelet_id" and tried to fix as much as possible to use int64_t or lanelet::Id for data type declaration.

Tests performed

Not applicable.
Effects on system behavior

Not applicable.
Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[ ] I've confirmed the contribution guidelines.
[ ] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

Thanks for people who approved the PR.
I still need the review from the following package maintainers:

lane_departure_checker @kyoichi-sugahara
behavior_velocity_planner_common @tkimura4, @shmpwk, @isamu-takagi
planning_test_utils @kyoichi-sugahara , @TakaHoribe


The "" code in the icon-link examples do not work

Prerequisites

[X] I have searched for duplicate or closed issues
[X] I have validated any HTML to avoid common problems
[X] I have read the contributing guidelines

Describe the issue
Some StackBlitz examples on the https://getbootstrap.com/docs/5.3/helpers/icon-link/ page do not work.
Reduced test cases

Go to the given Bootstrap page (see above)
Click on any of the StackBlitz links that display an associated icon along with the text link
On the StackBlitz page, the icon does NOT appear

This perhaps is related to https://github.com/twbs/bootstrap/issues/36146,
which refers to https://developer.mozilla.org/en-US/docs/Web/SVG/Attribute/xlink:href, which says that xlink:href is deprecated.
This page suggests replacing xlink:href with href, but that change does not show the icon either.
What operating system(s) are you seeing the problem on?
Windows
What browser(s) are you seeing the problem on?
Chrome, Firefox, Microsoft Edge
What version of Bootstrap are you using?
5.3.2

Here's the image I forgot to post in the original:

I've noticed that this happens due to the absence of the <svg/> element on StackBlitz. If you'll open the documentation page, inspect it, found this <svg/> element, copy and paste it to StackBlitz, everything will work.

As said by @WOLFRIEND, this is because the <svg> containing the images is not transferred to StackBlitz. We'll look at how to do it without complexifying the system that does everything around this feature. Thanks for reporting it @rob-stoecklein.

Thank you so much!


answer build

RUN answer build --with github.com/apache/incubator-answer-plugins/connector-basic --with github.com/apache/incubator-answer-plugins/user-center-wecom  --with github.com/apache/incubator-answer-plugins/embed-basic --with github.com/apache/incubator-answer-plugins/editor-chart --with github.com/apache/incubator-answer-plugins/search-meilisearch --with github.com/apache/incubator-answer-plugins/cache-redis --output /tmp/new_answer
FROM alpine
go: answer imports
github.com/apache/incubator-answer-plugins/editor_formula: module github.com/apache/incubator-answer-plugins@latest found (v1.2.1), but does not contain package github.com/apache/incubator-answer-plugins/editor_formula

@314767251 Here's a strange one. I see that you don't have the editor-formula plugin in the command line, so why does the error report contain this information about the plugin. Can you give more information to help troubleshoot?

Does this module need editor_formula for incubator-answer-plugins？

@314767251 Here's a strange one. I see that you don't have the editor-formula plugin in the command line, so why does the error report contain this information about the plugin. Can you give more information to help troubleshoot?

docker logs -f  ；no more logs，so this is incubator-answer-plugins must editor-formula？

@314767251 Here's a strange one. I see that you don't have the editor-formula plugin in the command line, so why does the error report contain this information about the plugin. Can you give more information to help troubleshoot?

docker logs -f ；no more logs，so this is incubator-answer-plugins must editor-formula？

I can give the following suggestions:

editor-formula not required.
make sure the Apache Answer version is up to date.
It is recommended to add the specified version to the build command line or use the latest flag.

answer build github.com/apache/incubator-answer-plugins/connector-basic@latest

3Q


Disable message interpolation in ConstraintViolations by default

Disable message interpolation in ConstraintViolations by default but allow enabling it explicitly with SelfValidating#escapeExpressions().
Additionally, ConstraintViolations now provides a set of methods which take a map of message parameters for interpolation. These message parameters are be escaped by default.
Thanks to @pwntester and @gsmet for their invaluable input!
Refs #3153
Refs #3157

LGTM, thanks!


Make PYTHONSTARTUP script respect PYTHON_HISTORY on Python <3.13

This allows the user to set PYTHON_HISTORY as the single source of truth on python versions prior to 3.13. As an extra bit of redundancy, the script now checks the python version too, making it a no-op on Python 3.13 and later.

Thank you!


Forgot Your Password button is not working

Describe the bug
A clear and concise description of what the bug is.
"Forgot your Password" button not working on signup page
To Reproduce
Steps to reproduce the behavior:
1.
2.
3.
4.
Expected behavior
A clear and concise description of what you expected to happen.
It should be working and redirect us to a different page where we can ask the user for a registered email and send him the link to reset the password.
Logs
If applicable, add logs to help explain your problem (e.g. the error message and/or exception traceback).
Environment (please complete the following information):

OS:
Browser:

Additional context
Add any other context about the problem here.

Hi @Vishal-raj-1, Please assign it to me. I would like to work on this.

I would love to help to resolve this bug

I would love to resolve this issue under LGMSOC'21

Hey Is this issue open to work! I wish to contribute to the same.


Can't accept PyPi Project invite

I can't accept an invite to a project I got on PyPi. The project invite link fails with "no token provided" and if I try to accept the invite from the "my projects page" using the accept button, I get an internal server error page:

Happens on all major web browsers

PyPi username: erikwrede

@erikwrede, is there any chance you're using PyPI in a language/locale other than English?

Yup, German

I can confirm that changing my browser language settings to english fixed the issue. I did not specifcally setup any language in the PyPi settings though.

We recently added support for autodetecting the locale based on browser settings (https://github.com/pypi/warehouse/issues/6864) so that's why.

(Sorry, the following comment didn't get posted:)
Thanks. This is due to a broken translation string in our German translation. In the short term, this should work if you switch your locale to English (or any other language but German I think). Long term fix for this is to fall back to English for broken translations strings.

Thanks for the help! Feel free to close this if this issue is already tracked in another context! 🙂

Closing this in favor of https://github.com/pypi/warehouse/issues/12552, but thanks for the report!


Add SpatialElementBoundaryLocation options to Room.Boundaries

Make four nodes for these options and alter Room.Boundaries accordingly

Room.Boundaries now takes the SpatialElementBoundaryLocation set in the Are/Volume Calculation Settings of the project - so there's no need for additional nodes.


Having a EnabledComponent interferes with Entitas internal logic

Hello,
i just came across this interesting problem: some of my reactive system stopped triggering. (or so it seemed still not to sure where exactly this all goes wrong)
So after some testing and reverting code-changes i found the reason to be my newly added EnabledComponent, which is a simple component without any members.
For such a component the code generator produces an isEnabled property, but this property now "hides" the isEnabled property of the IEntity interface and the Entity Class, and thus destroys some internal logic.
Now i could think of an other name for that component or use the [UniquePrefix] attribute to circumvent that problem, but to prevent others from stumbling over this i suggest renaming the property in the IEntity interface and the Entity class.
Cheers
Draugor

Hi. If renamed, the issue still exist. I suggest renaming EnableComponent because isEnabled is already taken. Maybe activated?


Bot context wrapper

Changed bots to use a BotContextWrapper instead of the plain botcontext bean, and moved all methods from eventbotactionutils as well as defined list names to the respective botcontextwrappers -> these are now also configurable over spring config xml and not only via constants in the sources

i will change the botcontextwrapper config and implementation so one only has to define a botname and not every individual list name, as well as an updated bot/readme.md, i will close this pull request for now


Usage of num_nics attribute

Today I tried deploying a cisco csr router with 10 data plane interfaces.  Everything went well, except for the 10th interface (GigabitEthernet11) which wasn't present in the virtual device after it finished booting.
After some digging, I discovered that this piece of code decided that eth10 was not relevant because it was over self.num_nics.
https://github.com/hellt/vrnetlab/blob/7f99b39edbf811ca498378fee4b4c9393f779458/common/vrnetlab.py#L353-L354
For cisco csr, num nics is always 9, it is the default value of the --nics option, which containerlab doesn't seem to be using (and most router kinds don't seem to have in their cli options) so it only ever gets its default value.
https://github.com/hellt/vrnetlab/blob/7f99b39edbf811ca498378fee4b4c9393f779458/csr/docker/launch.py#L256
I tried changing this default value to 10, to see if the device would accept this additional interface, and to my surprise, it did! This is great.  But it got me wondering: What is the purpose of the num_nics attribute?

Is it supposed to represent a vendor limitation, about the maximum number of interfaces? Why is it a cli option for some device kinds then? And why is its current value under-evaluated for cisco csr?
Or is it supposed to be a dynamic value, provided by containerlab (maybe something in sync with CLAB_INTFS?)?
Or is it some legacy logic with doesn't need to be used anymore?

It looks like there is something to fix, I am willing to create a PR, but I am not sure what the fix should be, as I don't know the intention behind this attribute.  Can I get some help here?

I found a very nasty workaround to be able to use the --nics option with containerlab:
diff --git a/files/cisco-csr-2R.clab.yml b/files/cisco-csr-2R.clab.yml
index e5d9769..abbce6d 100644
--- a/files/cisco-csr-2R.clab.yml
+++ b/files/cisco-csr-2R.clab.yml
@@ -13,6 +13,9 @@ topology:
         - "22830:830"
       mgmt-ipv4: <IP_ADDRESS>
       startup-config: ./cisco-csr-evc-2R/east.cfg
+      env:
+        # Workaround https://github.com/hellt/vrnetlab/issues/273
+        USERNAME: admin --nics 32
     router-west:
       kind: vr-csr
       image: code.inmanta.com:4567/solutions/containers/vr-csr:17.03.04
@@ -22,6 +25,9 @@ topology:
         - "24830:830"
       mgmt-ipv4: <IP_ADDRESS>
       startup-config: ./cisco-csr-evc-2R/west.cfg
+      env:
+        # Workaround https://github.com/hellt/vrnetlab/issues/273
+        USERNAME: admin --nics 32

I inject the --nics option inside the username which will then we converted into the command:
https://github.com/srl-labs/containerlab/blob/5e9647beee1134c318f69b5dd24f376ff3604d06/nodes/vr_csr/vr-csr.go#L75-L76
$ docker inspect -f json  clab-cisco-csr-2R-router-east | jq ".[0].Config.Cmd"
[
  "--username",
  "admin",
  "--nics",
  "32",
  "--password",
  "admin",
  "--hostname",
  "router-east",
  "--connection-mode",
  "tc",
  "--trace"
]

But a proper fix is definitely preferable ^^

Hi. The num nics indeed is supposed to be set to a limit that the virtual product supports.
The reason it was set to 10 is likely because it was like this for older versions or it was a copy paste issue
As Cisco people don't quite govern their systems here, we rely on the community hive mind to maintain the proper settings
If anyone knows the current limits we can bump the default value

I saw that the configuration seem to accept interface number going from 1 to 32.
router-east#show interfaces GigabitEthernet ?
  <1-32>  GigabitEthernet interface number

I then tried to configure that many interfaces, but it looks like the device will only setup the first 26 ones:
router-east#show interfaces summary

 *: interface is up
 IHQ: pkts in input hold queue     IQD: pkts dropped from input queue
 OHQ: pkts in output hold queue    OQD: pkts dropped from output queue
 RXBS: rx rate (bits/sec)          RXPS: rx rate (pkts/sec)
 TXBS: tx rate (bits/sec)          TXPS: tx rate (pkts/sec)
 TRTL: throttle count

  Interface                   IHQ       IQD       OHQ       OQD      RXBS      RXPS      TXBS      TXPS      TRTL
-----------------------------------------------------------------------------------------------------------------
* GigabitEthernet1              0         0         0         0      3000         3      3000         3         0
* GigabitEthernet2              0         0         0         0         0         0         0         0         0
* GigabitEthernet3              0         0         0         0         0         0         0         0         0
* GigabitEthernet4              0         0         0         0         0         0         0         0         0
  GigabitEthernet5              0         0         0         0         0         0         0         0         0
  GigabitEthernet6              0         0         0         0         0         0         0         0         0
  GigabitEthernet7              0         0         0         0         0         0         0         0         0
  GigabitEthernet8              0         0         0         0         0         0         0         0         0
  GigabitEthernet9              0         0         0         0         0         0         0         0         0
  GigabitEthernet10             0         0         0         0         0         0         0         0         0
* GigabitEthernet11             0         0         0         0         0         0         0         0         0
  GigabitEthernet12             0         0         0         0         0         0         0         0         0
  GigabitEthernet13             0         0         0         0         0         0         0         0         0
  GigabitEthernet14             0         0         0         0         0         0         0         0         0
  GigabitEthernet15             0         0         0         0         0         0         0         0         0
  GigabitEthernet16             0         0         0         0         0         0         0         0         0
  GigabitEthernet17             0         0         0         0         0         0         0         0         0
  GigabitEthernet18             0         0         0         0         0         0         0         0         0
  GigabitEthernet19             0         0         0         0         0         0         0         0         0
  GigabitEthernet20             0         0         0         0         0         0         0         0         0
  GigabitEthernet21             0         0         0         0         0         0         0         0         0
  GigabitEthernet22             0         0         0         0         0         0         0         0         0
  GigabitEthernet23             0         0         0         0         0         0         0         0         0
  GigabitEthernet24             0         0         0         0         0         0         0         0         0
  GigabitEthernet25             0         0         0         0         0         0         0         0         0
  GigabitEthernet26             0         0         0         0         0         0         0         0         0
* Loopback0                     0         0         0         0         0         0         0         0         0

So I guess that the default nics count can be set to 26 (or 25 as the first interface is used by eth0 here)?
At the same time, the router seem to be able to start, no matter how many interfaces we ask it to setup, it just drops the ones it can't handle.  So does it make sense to use this hard-coded limit in vrnetlab? Maybe a later version of the router (I am currently using csr1000v-universalk<IP_ADDRESS>a, I have no idea what else may be out there) will be able to support more, it would be nice to not need to update vrnetlab again then.  Wdyt?

I'm good with raising it to 32 as well. Let's do it


Source Code for Longest Palindromic Subsequence in C++

Related Issue
Closes: #1031
Describe the changes you've made
Adding Source Code for Longest Palindromic Subsequence in C++
Describe if there is any unusual behaviour of your code(Write NA if there isn't)
NA
Language used for coding
C++
Checklist:

[x] My code follows the style guidelines of this project.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] I have documented the code.
[x] New and existing unit tests pass locally with my changes.

Please review the code ;-)


Quick question regarding passing custom fields

Hey @snazy2000
I have a dumb, but hopefully easy question. I''m struggling using New-Asset with custom fields.
Let's say I have a custom fieldset with 1 custom field, called MAC_Address. I want to create a new-asset with this custom field.That fieldset is already associated with the value I have in $modeldatabaseID. I have a standard MAC address value formatted like this: xx:xx:xx:xx:xx:xx stored in $EthernetMAC. Based on the documentation I should be able to include custom fields using the -customfields parameter with a hash table. I'm doing so in this manner:
New-Asset -Name "Name" -Model_id $modeldatabaseid -Status_id 5 -customfields @{"serial" = "1234"; "MAC_Address" = "$EthernetMAC"}

The asset is created, and everything is correct, including the serial, but the MAC_Address field is empty.
Thoughts on what might be occurring?

I think I may have figured this out using Postman. Looks like I need to reference the custom field slightly differently using the db_column_name, going to try that.

Closing this issue out, fixed it on my own 👍


how can i unbind widget listener?

At first Thanks JakeWharton support this project for us.
my problem is :
button bind OnClickListener can using like this :  btn_agree.setOnClickListener(this);
cancel bind this listener can using like this: btn_agree.setOnClickListener(null);
ok,then how can i unbind some widget listener using ButterKnife?
thanks author and everyone.

Calling bind() returns an Unbinder which you should hold on to and then call its unbind() method to clear any listeners.
See http://jakewharton.github.io/butterknife/#reset

Thank u my god, i found method apply can help you reach my dest.Thank u.


[PORT] Rename updateHandlers to deleteHandlers

Port this change from botbuilder-dotnet/master branch:
https://github.com/microsoft/botbuilder-dotnet/pull/3782

Fix typo in TurnContext.DeleteActivityInternalAsync
Changed projects

Microsoft.Bot.Builder

Not applicable to JS.


Support multiple Webauthn devices at once

Would be useful in case you eg. lost one of your hardware tokens but still had a backup

+1. Allowing only a single WebAuthn device is an antipattern - having one key can actually be worse than no keys for some threat models (specifically, the "I want to use only WebAuthn for auth, but also want to not get locked out" case).


collapse-wiki-sections should not run on Wiki edit pages

Visit https://github.com/webpack/webpack/wiki/_new

Paste:
# hello

world

Click "Preview" tab

Click "hello"

This should be done in github-url-detection first I think?


Explained variance of eLORETA

Hi, I've seen that the Explained variance reported in the logger when using eLORETA is very strange:

Applying inverse operator to "stim"...
Picked 62 channels from the data
Computing inverse...
Eigenleads need to be weighted ...
Computing residual...
Explained -916356207643396166123520.0% variance
Combining the current components...

When using dSPM the value makes more sense (1.9%)
I've seen that here:
https://github.com/mne-tools/mne-python/blob/3fafe437413f29b91f36ca2726a4cceb87dfbab7/mne/minimum_norm/inverse.py#L906

data_est_w.max()
Out[15]:<PHONE_NUMBER>274.191
data_w.max()
Out[16]: 21.2237224470818

Maybe it is related to https://github.com/mne-tools/mne-python/pull/6050?
I wish a could try a solution but it goes beyond my current knowledge about computing inverse solutions.
Cheers,

Yes it's currently wrong. It would help if we just printed "unknown" rather than something nonsensical. Would you be up for making a PR to do that when the method is eLORETA?

Sure, I'll do it. Thanks for the clarification.


Cleaned up LKE Cluster Create endpoint

The CLI didn't like how the spec was formatted initially, and I'm pretty
sure it was wrong.  This works with the linked CLI PR, but please verify
it looks good in the docs - I'm happy to work with someone to get this
into a mergable state.

Thanks for this update, Will. node_pools is certainly a list of objects. That was an error on my part.
I originally had node_pools as a property directly in the POST /lke/clusters request body, and not in the LKEClusterRequestBody. Ifnode_pools is in the LKEClusterRequestBody then node_pools is also displayed in the response for other endpoints:

POST /lke/clusters
GET /lke/clusters
GET /lke/clusters/{clusterId}
PUT /lke/clusters/{clusterId}

If you think it is more correct to have all properties in a component schema object, I can create a third schema object for all LKE cluster's common properties and convert LKECluster to LKEClusterResponse OR
Move node_pools back to POST /lke/clusters request body, but of course keep your update to its datatype.
OR is there a third thing I'm completely not considering?

Let me move it back to where it was originally and see if the CLI will still use it - that's probably the right place for it.

@leslitagordita fixed the placement of node_pools - cli still likes it.


Updating CUPS in OS X El Capitan

Hi,
I'm using the last version of OS X El Capitan (10.11.4) and I'm trying to update CUPS from 2.1.0 to the last version of CUPS.
I received "Operation not permitted" in the last step: make install.
I tried with "sudo make install" and I receive the same error.
Log:
Making all in cups... Installing data files in cups... Installing data files in test... Installing sample ipptool files in /usr/share/cups/ipptool... /Users/Mendes/Downloads/Zebra/cups-release-2.1.3/install-sh: line 66: /usr/share/cups/ipptool/#inst.10701#: Operation not permitted /Users/Mendes/Downloads/Zebra/cups-release-2.1.3/install-sh: line 66: /usr/share/cups/ipptool/#inst.10708#: Operation not permitted /Users/Mendes/Downloads/Zebra/cups-release-2.1.3/install-sh: line 66: /usr/share/cups/ipptool/#inst.10715#: Operation not permitted /Users/Mendes/Downloads/Zebra/cups-release-2.1.3/install-sh: line 66: /usr/share/cups/ipptool/#inst.10722#: Operation not permitted /Users/Mendes/Downloads/Zebra/cups-release-2.1.3/install-sh: line 66: /usr/share/cups/ipptool/#inst.10729#: Operation not permitted /Users/Mendes/Downloads/Zebra/cups-release-2.1.3/install-sh: line 66: /usr/share/cups/ipptool/#inst.10736#: Operation not permitted /Users/Mendes/Downloads/Zebra/cups-release-2.1.3/install-sh: line 66: /usr/share/cups/ipptool/#inst.10743#: Operation not permitted /Users/Mendes/Downloads/Zebra/cups-release-2.1.3/install-sh: line 66: /usr/share/cups/ipptool/#inst.10750#: Operation not permitted /Users/Mendes/Downloads/Zebra/cups-release-2.1.3/install-sh: line 66: /usr/share/cups/ipptool/#inst.10757#: Operation not permitted /Users/Mendes/Downloads/Zebra/cups-release-2.1.3/install-sh: line 66: /usr/share/cups/ipptool/#inst.10764#: Operation not permitted /Users/Mendes/Downloads/Zebra/cups-release-2.1.3/install-sh: line 66: /usr/share/cups/ipptool/#inst.10771#: Operation not permitted /Users/Mendes/Downloads/Zebra/cups-release-2.1.3/install-sh: line 66: /usr/share/cups/ipptool/#inst.10778#: Operation not permitted /Users/Mendes/Downloads/Zebra/cups-release-2.1.3/install-sh: line 66: /usr/share/cups/ipptool/#inst.10785#: Operation not permitted /Users/Mendes/Downloads/Zebra/cups-release-2.1.3/install-sh: line 66: /usr/share/cups/ipptool/#inst.10792#: Operation not permitted /Users/Mendes/Downloads/Zebra/cups-release-2.1.3/install-sh: line 66: /usr/share/cups/ipptool/#inst.10799#: Operation not permitted make[1]: *** [install-data] Error 1 make: *** [install-data] Error 1
Thank you

Short answer: you need to disable SIP (system integrity protection aka rootless) to do this, which I do not recommend.
Long answer: system files are protected in El Capitan and cannot normally be replaced. Also, installing your own CUPS on OSX is completely unsupported and /will/ cause problems since some applications require signed libraries to function. You can, of course, sign the cups files yourself but that isn't something the makefiles can do for you... Finally, software updates including cups will likely yield a system that won't boot due to the mix of CUPS versions...
Why do you want to install a newer version of CUPS? All security and serious bug fixes are already there.


How to Scroll down in a fragment page.

From<EMAIL_ADDRESS>on July 05, 2012 02:45:31
What steps will reproduce the problem? I have an activity with tabs in vertical on half page and if we select an tab then items for the corresponding tabs are shown in fragment.
I want to know how to scroll down the items in fragments page. the fragment consists of radio button, checkboxes and text views and it is not a list. What version of the product are you using? On what operating system? Robotium 3.3
Original issue: http://code.google.com/p/robotium/issues/detail?id=293

From<EMAIL_ADDRESS>on July 09, 2012 09:08:07
Robotium can only scroll gridviews, listviews and scrollviews.
Status: Invalid


Optimize commands

This PR removes redundant variable declarations for most commands to improve space complexity.
A general rule is to remove variables that only have 1 usage, but this is flexible and depends on the context.

Unfortunatley I made the mistake of making changes to the original branch while the changes were taking place. Merge conflicts are occuring. As such the PR is closed and I will directly apply a commit to the main branch instead or a new PR.


Remove double decoding of event payload

All events emitted from a subscription are processed based on a configurable "payload type" (bytes, string, JSON). However, for events coming out of the block decoder, they are always coerced to JSON upfront before even being passed to the event decoder. This makes the behavior inconsistent for subscriptions based on a particular chaincode vs. channel-wide subscriptions based on the block decoder.
It seems cleaner to leave the payload as bytes in the block decoder, and to only decode it into string or JSON in the event processor.

Codecov Report

Merging #107 (4083cbd) into main (fc749c3) will decrease coverage by 0.14%.
The diff coverage is 100.00%.

:exclamation: Current head 4083cbd differs from pull request most recent head 646d4a6. Consider uploading reports for the commit 646d4a6 to get more accurate results

@@            Coverage Diff             @@
##             main     #107      +/-   ##
==========================================
- Coverage   68.33%   68.20%   -0.14%
==========================================
  Files          47       47
  Lines        4523     4523
==========================================
- Hits         3091     3085       -6
- Misses       1238     1240       +2
- Partials      194      198       +4

Impacted Files
Coverage Δ

internal/events/evtprocessor.go
93.02% <ø> (ø)

internal/fabric/utils/blockdecoder.go
71.68% <100.00%> (ø)

internal/utils/payload_decoder.go
57.14% <0.00%> (-42.86%)
:arrow_down:

internal/events/eventstream.go
91.96% <0.00%> (-0.90%)
:arrow_down:

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


Improve logging content with more metrics and better readability

We aim to improve logging content with more metrics and better readability:

the systematic metrics are missing. We need to add more metrics to reflect system performance, such as communication and computational efficiency.

we may add metric to reflect the convergence, e.g., the number of rounds to converge

We can discuss specific metric requirements and logging timing here @rayrayraykk

Resolved in #90. If necessary, we can re-open this issue again.


Implement abstraction for visual selection

This implements a class abstraction to represent a selection between two positions in the buffer. Most notably this can be used to represent a selection in visual block mode. In addition to the representation, said class allows for manipulation of the represented selection.
Furthermore, a property visual_selection was added to Buffer to allow easy access to a selection made in visual (block) mode and manipulation thereof e.g. via nvim.current.buffer.visual_selection.

This is needed because Range doesn't support partial lines, right?
Instead of Selection, how about Region:
class Selection(object):
    def __init__(self, buffer, startpos, endpos):

then it can take any pair of (line, column) positions, instead of just '< and '>. Probably Range could be deprecated then, too.

This is needed because Range doesn't support partial lines, right?

Aye, exactly this.
@justinmk
So simply rename Selection to Region you mean? Would make sense to further abstract from the originally motivating visual selection.
Regarding the deprecation of Range/merge of Range into Selection/Region: Should this be done immediately in this PR or as a follow-up one?
A reason against having those two objects merged would be that Range would implement writing through onto the buffer while not caring about partials and Selection/Region takes care of the partial-lines-implementation, separating those logics. But otherwise, merging both into one object would probably reduce the overall footprint.
Furthermore, in case we go for direct merge, I think I might have found a Bug in Range that I'd like to investigate and possibly fix before we would merge the two classes, therefore I would stall this PR for the moment then to keep Bugfixes separate from Feature implementations in that case if that's ok.

Probably Range could be deprecated then, too.

Actually, another reason to not deprecate Range would be that it would make perfect sense for a Range of three lines to replace that by e.g. five lines, the Range in the original buffer would just expand a little.
This however is not well defined for a Selection/Region: inserting more lines than the Region would duplicate some part of the lines that are not part of the selection, that's why I implemented the explicit assert(…) in between because I noticed that behavior in my tests, duplicating certain lines completely.
r = Range[1:3]
r[1:3] = ['foo'] * 10  # this would be fine

s = Selection((1, 5), (3, 8))
s[1:3] = ['bar'] * 10 # this would not make sense or would duplicate parts of the buffer that are not part of the selection

Capturing this in one object would lead to rather nested code and the separation into a  range-object adn a region-object that is based on a range-object would be a much cleaner solution and range would be able to keep its larger set of functionality.

"deprecate Range" doesn't need to be discussed right now, it was only a minor future suggestion.

I think I might have found a Bug in Range that I'd like to investigate

Bugfix is welcome.

Ok, Code ready for merge now. There are some complaints of flake8 left causing the CI to fail, but they do not affect those parts of the code that this PR touches, so that shouldn't be an obstacle for the merge of this PR.
Re: Bugfix in Range: not a blocker for this PR, so this one can be merged, I'll track down the Bug I suspect to be in Range in the next couple of days and open a separate PR for that if I actually can substantiate my suspicion.

@bfredl
You might also want to take a look as we briefly discussed this in IRC.

Later on we might want abstractions directly in the API for regions on the character-level, especially with extmarks that care about adjusting character position. At first API functions that gets or sets the text between two mark objects (an abstraction that either is a named mark or concrete position, extmarks PR #5031 does steps towards this), also nvim_put #6819 could take a mark object and not just put at cursor position.

@bfredl @justinmk
Do we do something about the failing flake8-check in this PR?

Maybe just add it to the ignore list in setup.cfg

ok, then I'd say this one is ready to be merged.

Thinking about this, I think I'll introduce a BlockRegion in addition to a normal Region, distinguishing e.g. standard visual selection from visual block selection.
As this would be two types of regions that behave significantly different in what area is affected by them, I think two separate Objects for those would be the most clean approach.
If possible I try to let both inherit from a GeneralRegion object to minimize code duplication, but testing will tell if that is reasonable.

BlockRegion in addition to a normal Region, distinguishing e.g. standard visual selection from visual block selection.
As this would be two types of regions that behave significantly different in what area is affected by them, I think two separate Objects for those would be the most clean approach.

Let's not go crazy with OOP :) They aren't very different. The interface is the same:

They both return text.
They both are defined by a pair of (row,col) tuples.
A "region type" flag (charwise, linewise, block) can switch the behavior.

They both are defined by a pair of (row,col) tuples.

Actually not: standard visual mode has full lines between the first and the last lines and partial lines in the first and last row. That makes handling of such a selection actually quite different for my taste as both differ in a number of nasty details, requiring very different flavors of __setitem__ and __getitem__.
Merging both into one Class and having a switch would be an option, though. I'm not yet sure if that's a nice solution, because __getitem__ and __setitem__ work very differently and also len() can be well defined for a normal selection (as the number of characters) whereas this is very much less obvious for a block-region.
This then make up more or less the entirety of that class (as __init__ is also different (at least how I implement it) for both due to the slightly different requirements outlined above), therefore it might be advisable to have to classes for that to not also make the code harder to read by such an inline-switch-case.
(I dropped the "let's inherit from a general object"-idea, though, as that does indeed make very little sense in this context.)
At least this is my reasoning to this point as far as I have thought the thing out so far. I'm happy to be convinced otherwise, @justinmk :) Wouldn't be the first time that I don't see a more beautiful solution right away a.^^
(and don't mind the failing CI, btw., I just pushed the current state for brief review, I will fix and test ASAP. However, feel free to comment on the current code right now (at least on a conceptual level), if you want, that's why I already pushed even if it's not yet finished).

They both are defined by a pair of (row,col) tuples.
Actually not: standard visual mode has full lines between

It's still a pair of (row,col).
The behavior is different, but the interface is the same. It isn't a different "class", it's just a region.

Merging both into one Class and having a switch would be an option, though. I'm not yet sure if that's a nice solution, because getitem and setitem work very differently and also len() can be well defined for a normal selection (as the number of characters) whereas this is very much less obvious for a block-region.

Could be functions like get_text_linewise() and get_text_charwise(), whatever. The point is users shouldn't need to fumble around with different object types just to work with the same region in different ways.

Good point indeed. I'll reconsider the implementation and see how to merge both objects.

Based on the suggestions of @justinmk I redesigned the API for the Region object and it is indeed much more general now.
I still like to rebase onto master, but feel free to already review the code and give your opinion and suggestions!

See https://github.com/neovim/neovim/pull/13896#issuecomment-1621702052 and https://github.com/neovim/neovim/pull/21115#issuecomment-1622294029 .
The Lua vim.region() should be used for this. Anything missing from vim.region() should be fixed/enhanced in vim.region() rather than adding client-specific features.


[Bug Report / C#] Suspected bug list of MjBindings.cs

At first, thanks to the MjBindings.cs file, it is easy to use in C#.
In the meantime, I think there seem to be some bugs in the MjBindings.cs file.
The suspected bugs found are as follows (please check it)
[DllImport("mujoco", CallingConvention = CallingConvention.Cdecl)]
[return: MarshalAs(UnmanagedType.LPStr)]
public static unsafe extern string mj_id2name(mjModel_* m, int type, int id);
=> I failed to use "mj_id2name" method, so I modified it as follows:
[DllImport("mujoco", CallingConvention = CallingConvention.Cdecl)]
public static unsafe extern IntPtr mj_id2name(mjModel_* m, int type, int id);
If string return is still OK, please let me know a sample code if possible. :)
//------------------------------------------------------------------------------------
[DllImport("mujoco", CallingConvention = CallingConvention.Cdecl)]
public static unsafe extern mjuiThemeSpacing_* mjui_themeSpacing(int ind);
[DllImport("mujoco", CallingConvention = CallingConvention.Cdecl)]
public static unsafe extern mjuiThemeColor_* mjui_themeColor(int ind);
Looking at the original C code, the return types are not a pointer. Thus, these codes were modified as follows.
[DllImport("mujoco", CallingConvention = CallingConvention.Cdecl)]
public static unsafe extern mjuiThemeSpacing_ mjui_themeSpacing(int ind);
[DllImport("mujoco", CallingConvention = CallingConvention.Cdecl)]
public static unsafe extern mjuiThemeColor_ mjui_themeColor(int ind);
I think it's a bug caused by a typo.

cc @Balint-H

I remember using id2name at some point in the past, but that it was quite finnicky, I'll have a look into it.

I remember using id2name at some point in the past, but that it was quite finnicky, I'll have a look into it.

Below is the method I'm using (By googling)
var ptr = mj_id2name(m_, (int)mjtObj.mjOBJ_BODY, selbody);
string variable = Marshal.PtrToStringAnsi(ptr);
It would be best if we could use the return type of id2name as a C# string (if possible). :)


Allow EOS token for finetuning

This is needed to allow the finetuning dataset to be constructed correctly.

Where do you see this needed? I'm pretty sure finetuning just uses the eos from the tokenizer.

Where do you see this needed? I'm pretty sure finetuning just uses the eos from the tokenizer.

It looks like it's one of the things **ed into the superclass, I think there are some cases where omitting this causes an error. eg.
[rank2]: ValueError: sequence_id is a required argument when MPT is configured with attn_uses_sequence_id=True and the model is in train mode.

@milocress that should only be for pretraining style. finetuning style handles packing and sequence id on its own. e.g. https://github.com/mosaicml/llm-foundry/blob/fb9a2259e880b0baa3d3523ff42def9ea6c29ce3/llmfoundry/data/packing.py#L155


MS-200D+ parallel effects

According to this write up the MS-200D+ allows you to put effects in parallel.

How is this signaled in the patch file, perhaps in the PPRMv2 block? Perhaps this feature will also work on the other MS-plus pedals....

There is FW update available...
https://zoomcorp.com/en/ca/multi-effects/multistomp-pedals/ms-200d-plus/ms-200d-support/

Manual says this is accessed through the 'menu' encoder....


latest release is old

Is it just me or is the latest release/tag in this repo a long way behind what's currently available in the master branch?
Latest release/tag is 1.4 on Oct 2018.
PR #13 and #14 have been merged since that time.
Ping @echuvyrov

Lets get master moved to a new release.

I don't think anyone is home. Let's poke a few of the contributors.
@logachev
@stuartleeks
@microsoftopensource
@echuvyrov
@msftgits
@dcaro

So, is this module abandonware? Strange, since it has the blue "Validated" checkmark in the Terraform Public Registry. :( Cheers.

Ive noticed that most of the verified Azure modules seem to be mostly abandoned. Ill bounce it up the Hashicorp and MS food chain via our SEs and see what happens.

any update on this? or is this project abandoned since it's no longer usable with terraform latest (v0.12.24)

I'm really sorry for this, seems like notifications from this repo just drowned in my inbox due to other projects notifications.
I will take a look this week.
I'll also follow up internally to figure out an owner for this moving forward.

How did this happen?
I really hope that this isn't because postgres is a competitor to MSSQL.  MS has a really bad history to escape when it comes to bitter database rivalry.
The fact is, MSSQL is just not well supported enough in every ecosystem to warrant having it get better attention than postgres.
Can we get an updated provider published right away that matches the documentation?  We are creating deployment scripts for real Azure services and this is 100% blocking us.

Any updates @logachev?

Hi @ausfestivus Thanks for opening this issue. Sorry for the delayed reply. Currently, we have release 2.0.0 to fit in Terraform 0.12. Please try it if you would like. And sorry that I have to close this issue. If you have anything unclear, don't hesitate to reopen this issue.


Keyboard is not working correctly when put inside a dialog

React-simple-keyboard version
3.0.70
Describe the bug
Hi, I am having this issue. I set an initial value for the input. Then, backspace not working first time opening the dialog, unless clicking on other keys, and also, typing first time clears the initial value.
I put sandbox here

Check out this ticket for a solution: https://github.com/hodgef/simple-keyboard/issues/858
Regards,
Francisco Hodge

oh, I get it now. need to use onInit option. Thank you very much @hodgef


⚠ TiendaEnLinea has degraded performance

In f35ec70, TiendaEnLinea (https://www.fahorro.com/) experienced degraded performance:

HTTP code: 200
Response time: 7740 ms

Resolved: TiendaEnLinea performance has improved in f1040ad.