BACKUP VR of VPC  Enters MASTER state and then BACKUP state when add a new VPC tier

Steps to reproduce the issue

create  a vpc vpc-001 with redundant VRs
create vpc tier vpc-001-001, create a vm
create vpc tier vpc-001-002, create a vm

check /var/log/messages, there are errors like
Oct 17 07:40:13 r-186-VM Keepalived_vrrp[1230230]: (inside_network) received an unexpected ip number count 2, expected 1!
Oct 17 07:40:14 r-186-VM Keepalived_vrrp[1230230]: (inside_network) received an unexpected ip number count 2, expected 1!
Oct 17 07:40:15 r-186-VM Keepalived_vrrp[1230230]: (inside_network) received an unexpected ip number count 2, expected 1!
Oct 17 07:40:16 r-186-VM Keepalived_vrrp[1230230]: (inside_network) received an unexpected ip number count 2, expected 1!
Oct 17 07:40:16 r-186-VM Keepalived_vrrp[1230230]: (inside_network) Entering MASTER STATE
Oct 17 07:40:22 r-186-VM Keepalived_vrrp[1230230]: (inside_network) IPSEC-AH : sequence number 377 already processed. Packet dropped. Local(377)
Oct 17 07:40:23 r-186-VM Keepalived_vrrp[1230230]: (inside_network) IPSEC-AH : sequence number 378 already processed. Packet dropped. Local(378)
Oct 17 07:40:24 r-186-VM Keepalived_vrrp[1230230]: (inside_network) IPSEC-AH : sequence number 379 already processed. Packet dropped. Local(379)
Oct 17 07:40:25 r-186-VM Keepalived_vrrp[1230230]: (inside_network) IPSEC-AH : sequence number 380 already processed. Packet dropped. Local(380)
Oct 17 07:40:26 r-186-VM Keepalived_vrrp[1230230]: (inside_network) IPSEC-AH : sequence number 381 already processed. Packet dropped. Local(381)
Oct 17 07:40:27 r-186-VM Keepalived_vrrp[1230230]: (inside_network) IPSEC-AH : sequence number 382 already processed. Packet dropped. Local(382)
Oct 17 07:40:28 r-186-VM Keepalived_vrrp[1230230]: (inside_network) IPSEC-AH : sequence number 383 already processed. Packet dropped. Local(383)
Oct 17 07:40:29 r-186-VM Keepalived_vrrp[1230230]: (inside_network) IPSEC-AH : sequence number 384 already processed. Packet dropped. Local(384)
Oct 17 07:40:42 r-186-VM Keepalived_vrrp[1230230]: (inside_network) IPSEC-AH : sequence number 385 already processed. Packet dropped. Local(385)
Oct 17 07:40:43 r-186-VM Keepalived_vrrp[1230230]: (inside_network) IPSEC-AH : sequence number 386 already processed. Packet dropped. Local(386)
Oct 17 07:40:44 r-186-VM Keepalived_vrrp[1230230]: (inside_network) IPSEC-AH : sequence number 387 already processed. Packet dropped. Local(387)
Oct 17 07:40:45 r-186-VM Keepalived_vrrp[1230230]: (inside_network) IPSEC-AH : sequence number 388 already processed. Packet dropped. Local(388)
Oct 17 07:40:46 r-186-VM Keepalived_vrrp[1230230]: (inside_network) IPSEC-AH : sequence number 389 already processed. Packet dropped. Local(389)
Oct 17 07:40:47 r-186-VM Keepalived_vrrp[1230230]: (inside_network) IPSEC-AH : sequence number 390 already processed. Packet dropped. Local(390)
Oct 17 07:40:48 r-186-VM Keepalived_vrrp[1230230]: (inside_network) IPSEC-AH : sequence number 391 already processed. Packet dropped. Local(391)
Oct 17 07:40:49 r-186-VM Keepalived_vrrp[1230230]: (inside_network) IPSEC-AH : sequence number 392 already processed. Packet dropped. Local(392)
Oct 17 07:40:50 r-186-VM Keepalived_vrrp[1230230]: (inside_network) IPSEC-AH : sequence number 393 already processed. Packet dropped. Local(393)
Oct 17 07:40:51 r-186-VM Keepalived_vrrp[1230230]: (inside_network) IPSEC-AH : sequence number 394 already processed. Packet dropped. Local(394)
Oct 17 07:40:52 r-186-VM Keepalived_vrrp[1230230]: (inside_network) IPSEC-AH : sequence number 395 already processed. Packet dropped. Local(395)
Oct 17 07:40:53 r-186-VM Keepalived_vrrp[1230230]: (inside_network) IPSEC-AH : sequence number 396 already processed. Packet dropped. Local(396)
Oct 17 07:40:54 r-186-VM Keepalived_vrrp[1230230]: (inside_network) IPSEC-AH : sequence number 397 already processed. Packet dropped. Local(397)
Oct 17 07:40:55 r-186-VM Keepalived_vrrp[1230230]: (inside_network) IPSEC-AH : sequence number 398 already processed. Packet dropped. Local(398)
Oct 17 07:40:56 r-186-VM Keepalived_vrrp[1230230]: (inside_network) IPSEC-AH : sequence number 399 already processed. Packet dropped. Local(399)
Oct 17 07:40:57 r-186-VM Keepalived_vrrp[1230230]: (inside_network) received an unexpected ip number count 2, expected 1!
Oct 17 07:40:58 r-186-VM Keepalived_vrrp[1230230]: (inside_network) received an unexpected ip number count 2, expected 1!
Oct 17 07:40:59 r-186-VM Keepalived_vrrp[1230230]: (inside_network) received an unexpected ip number count 2, expected 1!
Oct 17 07:41:00 r-186-VM Keepalived_vrrp[1230230]: (inside_network) received an unexpected ip number count 2, expected 1!
Oct 17 07:41:01 r-186-VM Keepalived_vrrp[1230230]: (inside_network) received an unexpected ip number count 2, expected 1!
Oct 17 07:41:02 r-186-VM Keepalived_vrrp[1230230]: (inside_network) received an unexpected ip number count 2, expected 1!
Oct 17 07:41:03 r-186-VM Keepalived_vrrp[1230230]: (inside_network) received an unexpected ip number count 2, expected 1!
Oct 17 07:41:04 r-186-VM Keepalived_vrrp[1230230]: (inside_network) received an unexpected ip number count 2, expected 1!
Oct 17 07:41:05 r-186-VM Keepalived_vrrp[1230230]: (inside_network) received an unexpected ip number count 2, expected 1!
Oct 17 07:41:06 r-186-VM Keepalived_vrrp[1230230]: (inside_network) received an unexpected ip number count 2, expected 1!
Oct 17 07:41:07 r-186-VM Keepalived_vrrp[1230230]: (inside_network) received an unexpected ip number count 2, expected 1!
Oct 17 07:41:08 r-186-VM Keepalived_vrrp[1230230]: (inside_network) received an unexpected ip number count 2, expected 1!
Oct 17 07:41:09 r-186-VM Keepalived_vrrp[1230230]: (inside_network) received an unexpected ip number count 2, expected 1!
Oct 17 07:41:10 r-186-VM Keepalived_vrrp[1230230]: (inside_network) received an unexpected ip number count 2, expected 1!
Oct 17 07:41:11 r-186-VM Keepalived_vrrp[1230230]: (inside_network) received an unexpected ip number count 2, expected 1!
Oct 17 07:41:12 r-186-VM Keepalived_vrrp[1230230]: (inside_network) received an unexpected ip number count 2, expected 1!
Oct 17 07:41:13 r-186-VM Keepalived_vrrp[1230230]: (inside_network) received an unexpected ip number count 2, expected 1!
Oct 17 07:41:14 r-186-VM Keepalived_vrrp[1230230]: (inside_network) received an unexpected ip number count 2, expected 1!
Oct 17 07:41:15 r-186-VM Keepalived_vrrp[1230230]: (inside_network) received an unexpected ip number count 2, expected 1!
Oct 17 07:41:16 r-186-VM Keepalived_vrrp[1230230]: (inside_network) received an unexpected ip number count 2, expected 1!
Oct 17 07:41:17 r-186-VM Keepalived_vrrp[1230230]: (inside_network) received an unexpected ip number count 2, expected 1!
Oct 17 07:41:18 r-186-VM Keepalived_vrrp[1230230]: (inside_network) received an unexpected ip number count 2, expected 1!
Oct 17 07:41:19 r-186-VM Keepalived_vrrp[1230230]: (inside_network) received an unexpected ip number count 2, expected 1!
Oct 17 07:41:20 r-186-VM Keepalived_vrrp[1230230]: (inside_network) IPSEC-AH : sequence number 423 already processed. Packet dropped. Local(423)
Oct 17 07:41:21 r-186-VM Keepalived_vrrp[1230230]: (inside_network) IPSEC-AH : sequence number 424 already processed. Packet dropped. Local(424)
Oct 17 07:41:22 r-186-VM Keepalived_vrrp[1230230]: (inside_network) IPSEC-AH : sequence number 425 already processed. Packet dropped. Local(425)
Oct 17 07:41:23 r-186-VM Keepalived_vrrp[1230230]: (inside_network) received an unexpected ip number count 2, expected 1!
Oct 17 07:41:23 r-186-VM Keepalived[1230226]: Reloading ...
Oct 17 07:41:23 r-186-VM Keepalived[1230226]: Opening file '/etc/keepalived/keepalived.conf'.
Oct 17 07:41:23 r-186-VM Keepalived_vrrp[1230230]: Reloading
Oct 17 07:41:23 r-186-VM Keepalived_vrrp[1230230]: Opening file '/etc/keepalived/keepalived.conf'.
Oct 17 07:41:23 r-186-VM Keepalived_vrrp[1230230]: VRRP_Script(heartbeat) considered successful on reload
Oct 17 07:41:23 r-186-VM Keepalived_vrrp[1230230]: SECURITY VIOLATION - scripts are being executed but script_security not enabled.
Oct 17 07:41:23 r-186-VM Keepalived_vrrp[1230230]: (inside_network) Master received advert from <IP_ADDRESS> with same priority 100 but higher IP address than ours
Oct 17 07:41:23 r-186-VM Keepalived_vrrp[1230230]: (inside_network) Entering BACKUP STATE

ISSUE TYPE

Bug Report

COMPONENT NAME

CLOUDSTACK VERSION

most recent versions

CONFIGURATION

OS / ENVIRONMENT

SUMMARY

STEPS TO REPRODUCE

EXPECTED RESULTS

ACTUAL RESULTS

@weizhouapache have you seen any disfunction because of this? I'm meaning to set a severity, that's why I ask.

Working on a fix in this PR: https://github.com/apache/cloudstack/pull/9251

fixed in #9251


Chinese display garbled characters

device manager：

Hi @xiaguangbo! I'm looking into this issue, and it'd be helpful to me if you could provide text of what the characters are that are missing as well, so that I can copy them and test with them, thanks!

@gcampbell-msft This is Chinese in device manager：
USB 串行设备 (COM5)
...
蓝牙链接上的标准串行 (COM8)
....

@xiaguangbo Thanks! I believe we may have been narrowing down where this issue is, we will let you know when we have a fix, though we don't have a timeline for when that will occur.

中文字体随机出现乱码，希望可以解决一下

Closing in favor of tracking here #47


Add M269 quick start guide

[ ] Write a simpler guide for M269 students: install algoesup and ruff in their env and share essay on VLE forums.
[ ] Test in Windows, Linux and macOS M269 environments, after #10 is fixed.

@densnow I've started a new branch m269-guide, based on the current main, for this. Could you please check that the instructions work for the m269-23j environment, where students have allowed locally via an alias,  and not via pip?
I haven't yet generated the docs, I'm using just mkdocs serve for the moment.
The way to download the template is clunky at the moment (requires right-click). I thought of linking to GH to then click on the download button but the GH UI can be intimidating. Any suggestions welcome.
Feel free to add detail to the instructions. Thanks.

@mwermelinger The aliased allowed does not seem to be picked up by %allowed. Although the shell=true arg is set it still seems to bypass the config files AFAIK.

Well, since allowed can check a whole notebook, it's not crucial to run it from within the notebook, but the documentation will have to say that.
The allowed on command checks the cell it's in, so at that point there should be a message if the linter can't be run.

When testing allowed that time and I forgot about the alias, it seemed to default to the alias when used in the shell. when allowed is installed via pip %allowed seems to grab the pip installed version. Its a bit messy, but it could be an option to install allowed with pip to.

Good idea, will check it tomorrow on macOS. If you could test on Linux and Windows would be good.

Yes, will test that to make sure.

The allowed on command checks the cell it's in, so at that point there should be a message if the linter can't be run.

When the commands that are used by the magics were not found (because the package was not installed), it was only %ruff that printed an error message and the message was obscure. %allowed and %pytype did not print anything to indicate that the command was not found.
I think all three magics could benefit from better error handling and clearer error messaging. This issue could be grouped together with #8 if we make the title and description more generic?

@densnow I've updated the m269 guide (pyproject.toml needs to be downloaded too) and tested on macOS. Over to you. If it works on Linux and Windows, please do

[ ] poetry run mkdocs build which will change all files because the nav panel has a new entry
[ ] push the docs
[ ] squash and merge this branch into main, with a commit msg Fix #11: add M269 start guide

Thanks

@mwermelinger We have a bug with the %allowed magic on Windows. It is not related to having both local and PyPi  versions of allowed, but has to do with Windows paths and the way \U from \Users is interpreted in the command line (as escape sequence) :upside_down_face: .
I will have to open a separate issue for this bug.

If it's an independent issue, best to first do the three tasks above to close this issue, and then work on #16.


[WIP] various particle improvements: velocity direction, separate curves

Implements  https://github.com/godotengine/godot-proposals/issues/6779
Partially implements https://github.com/godotengine/godot-proposals/issues/6657
Please give feedback!
This work is kindly sponsored by https://www.pahdolabs.com/

Alright - the direction from point will most likely change with some form of velocity controls.

superseded by https://github.com/godotengine/godot/pull/79527


Submit Workflow: linkding Bookmarks

Preflight

[X] The Alfred team has invited me to submit this workflow.

The submitted workflow:

[X] Was authored by me. ⓘ
[X] Uses Workflow Configuration or has no user-facing settings. ⓘ
[X] Does not have an auto-updater. ⓘ
[X] Does not contain unsigned and non-notarised binaries. ⓘ
[X] Does not download extra software. ⓘ
[X] Uses keywords with more than one character. ⓘ
[X] Has a descriptive About section. ⓘ
[X] Has an icon of at least 256x256 px. ⓘ

Homepage
https://github.com/FireFingers21/alfred-linkding-bookmarks
Alfred Forum page
https://www.alfredforum.com/topic/21912-linkding-bookmarks-search-linkding-bookmarks-in-alfred
Gallery page content
Setup
Set the Base URL and API Token of your linkding installation in the Workflow’s Configuration. You can find the API Token from your linkding Settings → Integrations → Rest API.
Usage
Search for your linkding bookmarks using the bm keyword.

Type to refine your search. Bookmarks are always filtered by title, while filtering by description, URL, and tags is configurable from the Workflow’s Configuration.

↩ Open bookmark in primary browser
⌘↩ Open bookmark in secondary browser
⌥↩ Edit bookmark in linkding
⇧⌥↩ View bookmark in linkding
⌃↩ Delete bookmark from linkding
⌘C Copy bookmark URL
⇧ Hold to show bookmark description

Append :: to the configured Keyword to access other actions, including manually reloading the bookmark cache. You can also change the default browser settings from here without using the Workflow’s Configuration.

Enable bookmark auto-updates from the Workflow’s Configuration. Bookmarks will reload upon Workflow Trigger. See a timestamp of the last successful reload from the other actions as shown in the image above.
Configure the Hotkey as a shortcut to search for your bookmarks. Use the Universal Action to bookmark URLs from Alfred’s Clipboard History or selected text.

Bookmarks with the tag Exclude-Alfred will be hidden from search. This tag is case sensitive.
Tags
bookmarks, self-hosted
Homebrew dependencies
jq
Bundled libraries
No response

Thank you. Live now at https://alfred.app/workflows/firefingers21/linkding-bookmarks/


fix(deps): Update react version in peer dependency requirement to include react>=0.14

Fix for #199
What:
Glamorous was intended to support react 14, but the package.json didn't actually allow for it to be installed alongside react 14 by mistakenly using a peer dep requirement of >=14 instead of >=0.14.
Why:
Glamorous (and packages that rely on it) might want to use react 14.
How:
Updated the package.json
Checklist:

[ ] Documentation N/A
[ ] Tests N/A
[X] Code complete
[X] Added myself to contributors table
[X] Followed the commit message format

Codecov Report

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

@@          Coverage Diff          @@
##           master   #200   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files          10     10
  Lines         142    142
  Branches       36     36
=====================================
  Hits          142    142

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 72511a2...484022b. Read the comment docs.


Skip setting VLAN ID when VLAN is 0 - breaks on VF trunk policy

What issue would you like to bring attention to?
When using trunk policy on VF level, the sriov-cni fails allocating the VF to the Pod.
root@worker:~# for VF in $(ls -l /sys/class/net/ens3f{0..1}/device/sriov/{0..7}/trunk | awk '{print $9}'); do echo add 1082 1082 > $VF; done
--- --- ---
$ kubectl create -f /home/deployment.yaml
$ kubectl -n test1 describe pod test-router-69945bd84f-5826r
Events:
  Type     Reason                  Age   From               Message
  ----     ------                  ----  ----               -------
  Normal   Scheduled               10s   default-scheduler  Successfully assigned test1/test-router-69945bd84f-5826r to worker
  Warning  NoNetworkFound          9s    multus             cannot find a network-attachment-definition (k8s-pod-network) in namespace (kube-system): network-attachment-definitions.k8s.cni.cncf.io "k8s-pod-network" not found
  Normal   AddedInterface          9s    multus             Add eth0 [<IP_ADDRESS>/32] from k8s-pod-network
  Warning  FailedCreatePodSandBox  9s    kubelet            Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "8be0ea041e5f00ec8cd4fe2756fc85b23ae5d691ceb4c1fd51afc9229ca6566a": plugin type="multus" name="multus-cni-network" failed (add): [test1/test-router-69945bd84f-5826r:sriov-mlnx-connectx5]: error adding container to network "sriov-mlnx-connectx5": SRIOV-CNI failed to configure VF "failed to set vf 5 vlan: operation not permitted"
  Warning  NoNetworkFound          8s    multus             cannot find a network-attachment-definition (k8s-pod-network) in namespace (kube-system): network-attachment-definitions.k8s.cni.cncf.io "k8s-pod-network" not found
  Normal   AddedInterface          8s    multus             Add eth0 [<IP_ADDRESS>/32] from k8s-pod-network
  Warning  FailedCreatePodSandBox  8s    kubelet            Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "99d05c54d8c428663e99c72716b8fc525c134286a90f97bd23d584bf471a4e40": plugin type="multus" name="multus-cni-network" failed (add): [test1/test-router-69945bd84f-5826r:sriov-mlnx-connectx5]: error adding container to network "sriov-mlnx-connectx5": SRIOV-CNI failed to configure VF "failed to set vf 5 vlan: operation not permitted"
  Warning  NoNetworkFound          7s    multus             cannot find a network-attachment-definition (k8s-pod-network) in namespace (kube-system): network-attachment-definitions.k8s.cni.cncf.io "k8s-pod-network" not found
  Normal   AddedInterface          7s    multus             Add eth0 [<IP_ADDRESS>/32] from k8s-pod-network
  Warning  FailedCreatePodSandBox  7s    kubelet            Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "a89824b786e6cb41f6dee80931d5394ad55dc32939e4647a9ad56d418aa934a9": plugin type="multus" name="multus-cni-network" failed (add): [test1/test-router-69945bd84f-5826r:sriov-mlnx-connectx5]: error adding container to network "sriov-mlnx-connectx5": SRIOV-CNI failed to configure VF "failed to set vf 5 vlan: operation not permitted"
...
...

What is the impact of this issue?

Cannot provision a VF interface inside Pod network namespace.
Reduced capabilities of NIC, not able to use all features.

Do you have a proposed response or remediation for the issue?
Either skip applying VLAN config when VLAN==0 in https://github.com/k8snetworkplumbingwg/sriov-cni/blob/master/pkg/sriov/sriov.go#L226
or
Add additional configurable field for sriov-cni which would skip VLAN config when e.g. VFtrunk=true
If necessary I can post a longer post explaining all details of this.

I see some work was done in: https://github.com/k8snetworkplumbingwg/sriov-cni/issues/133.
The issue contained a proposal for configuring sriov-cni. However, I do not demand or need a configuration option, simply make sriov-cni stop trying to apply VLAN to VF when VLAN ID is 0.

Hi @RefluxMeds thanks for the input yes please if you can explain about more the use-case this will be great!
is the trunk with allow vlan configure a driver specific?

Introduction
Hello @SchSeba !
We're trying to solve a specific security issue in our infrastructure - prohibiting Pod workloads and other host processes from provisioning any VLAN ID they want on assigned virtual functions. This issue stems from our network fabric setup, but I cannot get into details here as it would be too revealing. Also this feature would resolve our platform compliance with the company-wide security policy, so I am really really interested in pursuing it.
We are using Mellanox ConnectX-6 (Lx/Dx) and ConnectX-5 NIC on all our servers. These NICs provide a really cool feature we would like to use, however this is not supported with the current implementation of sriov-cni.
Issue description
To describe the issue, I will post a somewhat lengthy explainer on how we got to here. I apologize in advance if it is too long.

 However, this configuration would match what Nvidia calls VST or VLAN Switch Tagging.  This configuration would match what Nvidia calls VGT or VLAN Guest Tagging.
To configure this, we recreate the NetworkAttachmentDefinition without the VLAN ID and restart the Pod. But now we have to create a VLAN tag on the VF through the Pod in order to ping the gateway:
$ kubectl -n test1 exec -it test-router-69945bd84f-tb424 -- bash
root@test-router-69945bd84f-tb424:~# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet <IP_ADDRESS>/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
3: eth0@if3967: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether a2:f6:89:13:cf:2d brd ff:ff:ff:ff:ff:ff link-netnsid 0
    inet <IP_ADDRESS>/32 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::a0f6:89ff:fe13:cf2d/64 scope link
       valid_lft forever preferred_lft forever
27: net1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 5e:46:16:56:e3:b9 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::5c46:16ff:fe56:e3b9/64 scope link
       valid_lft forever preferred_lft forever

root@test-router-69945bd84f-tb424:~# ip link add link net1 name net1.1082 type vlan id 1082
root@test-router-69945bd84f-tb424:~# ip addr add <IP_ADDRESS>/28 brd <IP_ADDRESS> dev net1.1082
root@test-router-69945bd84f-tb424:~# ip link set dev net1.1082 up
root@test-router-69945bd84f-tb424:~# ping -I net1.1082 <IP_ADDRESS>
root@test-router-69945bd84f-tb424:~# ping -I net1.1082 <IP_ADDRESS>
PING <IP_ADDRESS> (<IP_ADDRESS>) from <IP_ADDRESS> net1.1082: 56(84) bytes of data.
64 bytes from <IP_ADDRESS>: icmp_seq=1 ttl=64 time=0.820 ms
64 bytes from <IP_ADDRESS>: icmp_seq=2 ttl=64 time=0.907 ms
64 bytes from <IP_ADDRESS>: icmp_seq=3 ttl=64 time=0.973 ms
64 bytes from <IP_ADDRESS>: icmp_seq=4 ttl=64 time=1.21 ms
^C
--- <IP_ADDRESS> ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3044ms
rtt min/avg/max/mdev = 0.820/0.979/1.219/0.153 ms

This is where VGT+ feature comes in. VGT+ is an advanced mode of virtual guest tagging, in which a VF is allowed to tag its own packets, but is still subject to an administrative VLAN trunk policy. To configure the VF trunk policy on both PFs we run a command that configures it:
root@worker:~# for VF in $(ls -l /sys/class/net/ens3f{0..1}/device/sriov/{0..7}/trunk | awk '{print $9}'); do echo add 1070 1081 > $VF; done
root@worker:~# cat /sys/class/net/ens3f{0..1}/device/sriov/{0..7}/trunk
Allowed 802.1Q VLANs: 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081
Allowed 802.1Q VLANs: 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081
Allowed 802.1Q VLANs: 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081
Allowed 802.1Q VLANs: 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081
Allowed 802.1Q VLANs: 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081
Allowed 802.1Q VLANs: 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081
Allowed 802.1Q VLANs: 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081
Allowed 802.1Q VLANs: 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081
Allowed 802.1Q VLANs: 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081
Allowed 802.1Q VLANs: 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081
Allowed 802.1Q VLANs: 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081
Allowed 802.1Q VLANs: 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081
Allowed 802.1Q VLANs: 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081
Allowed 802.1Q VLANs: 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081
Allowed 802.1Q VLANs: 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081
Allowed 802.1Q VLANs: 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081

The guest tagged traffic with VLAN ID 1082 will not be sent or received by the VF:
root@test-router-69945bd84f-tb424:~# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet <IP_ADDRESS>/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
3: eth0@if3967: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether a2:f6:89:13:cf:2d brd ff:ff:ff:ff:ff:ff link-netnsid 0
    inet <IP_ADDRESS>/32 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::a0f6:89ff:fe13:cf2d/64 scope link
       valid_lft forever preferred_lft forever
27: net1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 5e:46:16:56:e3:b9 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::5c46:16ff:fe56:e3b9/64 scope link
       valid_lft forever preferred_lft forever

root@test-router-69945bd84f-tb424:~# ip link add link net1 name net1.1082 type vlan id 1082
root@test-router-69945bd84f-tb424:~# ip addr add <IP_ADDRESS>/28 brd <IP_ADDRESS> dev net1.1082
root@test-router-69945bd84f-tb424:~# ip link set dev net1.1082 up

root@test-router-69945bd84f-tb424:~# ping -I net1.1082 <IP_ADDRESS>
PING <IP_ADDRESS> (<IP_ADDRESS>) from <IP_ADDRESS> net1.1082: 56(84) bytes of data.
^C
--- <IP_ADDRESS> ping statistics ---
16 packets transmitted, 0 received, 100% packet loss, time 15357ms
pipe 3

We will add an additional allowed VLAN on virtual function trunks and we will configure the same VF with another VLAN tag which is already allowed, to demonstrate that the policy indeed works:
root@worker:~# for VF in $(ls -l /sys/class/net/ens3f{0..1}/device/sriov/{0..7}/trunk | awk '{print $9}'); do echo add 1082 1082 > $VF; done
root@worker:~# cat /sys/class/net/ens3f{0..1}/device/sriov/{0..7}/trunk
Allowed 802.1Q VLANs: 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081 1082
Allowed 802.1Q VLANs: 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081 1082
Allowed 802.1Q VLANs: 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081 1082
Allowed 802.1Q VLANs: 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081 1082
Allowed 802.1Q VLANs: 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081 1082
Allowed 802.1Q VLANs: 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081 1082
Allowed 802.1Q VLANs: 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081 1082
Allowed 802.1Q VLANs: 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081 1082
Allowed 802.1Q VLANs: 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081 1082
Allowed 802.1Q VLANs: 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081 1082
Allowed 802.1Q VLANs: 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081 1082
Allowed 802.1Q VLANs: 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081 1082
Allowed 802.1Q VLANs: 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081 1082
Allowed 802.1Q VLANs: 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081 1082
Allowed 802.1Q VLANs: 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081 1082
Allowed 802.1Q VLANs: 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081 1082
--- --- --- --- --- --- --- --- ---
--- --- --- --- --- --- --- --- ---
root@test-router-69945bd84f-tb424:~# ip link add link net1 name net1.1082 type vlan id 1082
root@test-router-69945bd84f-tb424:~# ip addr add <IP_ADDRESS>/28 dev net1.1082
root@test-router-69945bd84f-tb424:~# ip link set dev net1.1082 up
root@test-router-69945bd84f-tb424:~# ip link add link net1 name net1.1081 type vlan id 1081
root@test-router-69945bd84f-tb424:~# ip addr add <IP_ADDRESS>/28 dev net1.1081
root@test-router-69945bd84f-tb424:~# ip link set dev net1.1081 up
root@test-router-69945bd84f-tb424:~# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet <IP_ADDRESS>/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
3: eth0@if3967: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether a2:f6:89:13:cf:2d brd ff:ff:ff:ff:ff:ff link-netnsid 0
    inet <IP_ADDRESS>/32 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::a0f6:89ff:fe13:cf2d/64 scope link
       valid_lft forever preferred_lft forever
8: net1.1082@net1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 5e:46:16:56:e3:b9 brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/28 scope global net1.1082
       valid_lft forever preferred_lft forever
    inet6 fe80::5c46:16ff:fe56:e3b9/64 scope link
       valid_lft forever preferred_lft forever
9: net1.1081@net1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 5e:46:16:56:e3:b9 brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/28 scope global net1.1081
       valid_lft forever preferred_lft forever
    inet6 fe80::5c46:16ff:fe56:e3b9/64 scope link
       valid_lft forever preferred_lft forever
27: net1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 5e:46:16:56:e3:b9 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::5c46:16ff:fe56:e3b9/64 scope link
       valid_lft forever preferred_lft forever

root@test-router-69945bd84f-tb424:~# ping -c4 -I net1.1082 <IP_ADDRESS>
PING <IP_ADDRESS> (<IP_ADDRESS>) from <IP_ADDRESS> net1.1082: 56(84) bytes of data.
64 bytes from <IP_ADDRESS>: icmp_seq=1 ttl=64 time=12.4 ms
64 bytes from <IP_ADDRESS>: icmp_seq=2 ttl=64 time=0.931 ms
64 bytes from <IP_ADDRESS>: icmp_seq=3 ttl=64 time=0.871 ms
64 bytes from <IP_ADDRESS>: icmp_seq=4 ttl=64 time=0.761 ms

--- <IP_ADDRESS> ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3054ms
rtt min/avg/max/mdev = 0.761/3.750/12.440/5.017 ms

root@test-router-69945bd84f-tb424:~# ping -c4 -I net1.1081 <IP_ADDRESS>
PING <IP_ADDRESS> (<IP_ADDRESS>) from <IP_ADDRESS> net1.1081: 56(84) bytes of data.
64 bytes from <IP_ADDRESS>: icmp_seq=1 ttl=64 time=23.7 ms
64 bytes from <IP_ADDRESS>: icmp_seq=2 ttl=64 time=0.777 ms
64 bytes from <IP_ADDRESS>: icmp_seq=3 ttl=64 time=0.822 ms
64 bytes from <IP_ADDRESS>: icmp_seq=4 ttl=64 time=31.3 ms

--- <IP_ADDRESS> ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3054ms
rtt min/avg/max/mdev = 0.777/14.177/31.378/13.648 ms

However, we have issues with this approach if the VF is already assigned to a Pod. When the 802.1Q trunk policy is changed all tagged interfaces inside the Pod have to be recreated for new trunk policy to apply. This means that we either stop all traffic on that interface and recreate it or we must set the trunk policies in advance (before application deployment).
Setting trunk policy before provisioning a VF has undesired consequences:
root@worker:~# for VF in $(ls -l /sys/class/net/ens3f{0..1}/device/sriov/{0..7}/trunk | awk '{print $9}'); do echo add 1082 1082 > $VF; done
--- --- ---
$ kubectl create -f /home/deployment.yaml
$ kubectl -n test1 describe pod test-router-69945bd84f-5826r
Events:
  Type     Reason                  Age   From               Message
  ----     ------                  ----  ----               -------
  Normal   Scheduled               10s   default-scheduler  Successfully assigned test1/test-router-69945bd84f-5826r to worker
  Warning  NoNetworkFound          9s    multus             cannot find a network-attachment-definition (k8s-pod-network) in namespace (kube-system): network-attachment-definitions.k8s.cni.cncf.io "k8s-pod-network" not found
  Normal   AddedInterface          9s    multus             Add eth0 [<IP_ADDRESS>/32] from k8s-pod-network
  Warning  FailedCreatePodSandBox  9s    kubelet            Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "8be0ea041e5f00ec8cd4fe2756fc85b23ae5d691ceb4c1fd51afc9229ca6566a": plugin type="multus" name="multus-cni-network" failed (add): [test1/test-router-69945bd84f-5826r:sriov-mlnx-connectx5]: error adding container to network "sriov-mlnx-connectx5": SRIOV-CNI failed to configure VF "failed to set vf 5 vlan: operation not permitted"
  Warning  NoNetworkFound          8s    multus             cannot find a network-attachment-definition (k8s-pod-network) in namespace (kube-system): network-attachment-definitions.k8s.cni.cncf.io "k8s-pod-network" not found
  Normal   AddedInterface          8s    multus             Add eth0 [<IP_ADDRESS>/32] from k8s-pod-network
  Warning  FailedCreatePodSandBox  8s    kubelet            Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "99d05c54d8c428663e99c72716b8fc525c134286a90f97bd23d584bf471a4e40": plugin type="multus" name="multus-cni-network" failed (add): [test1/test-router-69945bd84f-5826r:sriov-mlnx-connectx5]: error adding container to network "sriov-mlnx-connectx5": SRIOV-CNI failed to configure VF "failed to set vf 5 vlan: operation not permitted"
  Warning  NoNetworkFound          7s    multus             cannot find a network-attachment-definition (k8s-pod-network) in namespace (kube-system): network-attachment-definitions.k8s.cni.cncf.io "k8s-pod-network" not found
  Normal   AddedInterface          7s    multus             Add eth0 [<IP_ADDRESS>/32] from k8s-pod-network
  Warning  FailedCreatePodSandBox  7s    kubelet            Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "a89824b786e6cb41f6dee80931d5394ad55dc32939e4647a9ad56d418aa934a9": plugin type="multus" name="multus-cni-network" failed (add): [test1/test-router-69945bd84f-5826r:sriov-mlnx-connectx5]: error adding container to network "sriov-mlnx-connectx5": SRIOV-CNI failed to configure VF "failed to set vf 5 vlan: operation not permitted"
  Warning  NoNetworkFound          6s    multus             cannot find a network-attachment-definition (k8s-pod-network) in namespace (kube-system): network-attachment-definitions.k8s.cni.cncf.io "k8s-pod-network" not found
  Normal   AddedInterface          6s    multus             Add eth0 [<IP_ADDRESS>/32] from k8s-pod-network
  Warning  FailedCreatePodSandBox  6s    kubelet            Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "51687216f7597bc2ad82e99c417c5337e847c6d11b9a4505a93d90aacc9344c7": plugin type="multus" name="multus-cni-network" failed (add): [test1/test-router-69945bd84f-5826r:sriov-mlnx-connectx5]: error adding container to network "sriov-mlnx-connectx5": SRIOV-CNI failed to configure VF "failed to set vf 5 vlan: operation not permitted"
  Warning  NoNetworkFound          5s    multus             cannot find a network-attachment-definition (k8s-pod-network) in namespace (kube-system): network-attachment-definitions.k8s.cni.cncf.io "k8s-pod-network" not found
  Normal   AddedInterface          5s    multus             Add eth0 [<IP_ADDRESS>/32] from k8s-pod-network
  Warning  FailedCreatePodSandBox  5s    kubelet            Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "4ea6cbf7c5338d2677c45b09af896be704887eaac82f5006c77ea42916f6247c": plugin type="multus" name="multus-cni-network" failed (add): [test1/test-router-69945bd84f-5826r:sriov-mlnx-connectx5]: error adding container to network "sriov-mlnx-connectx5": SRIOV-CNI failed to configure VF "failed to set vf 5 vlan: operation not permitted"
  Warning  NoNetworkFound          4s    multus             cannot find a network-attachment-definition (k8s-pod-network) in namespace (kube-system): network-attachment-definitions.k8s.cni.cncf.io "k8s-pod-network" not found
  Normal   AddedInterface          4s    multus             Add eth0 [<IP_ADDRESS>/32] from k8s-pod-network
  Warning  FailedCreatePodSandBox  4s    kubelet            Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "0259497093460581de8061b1a5002a8ee8e6241e8365c3c87b75d7bf228327b4": plugin type="multus" name="multus-cni-network" failed (add): [test1/test-router-69945bd84f-5826r:sriov-mlnx-connectx5]: error adding container to network "sriov-mlnx-connectx5": SRIOV-CNI failed to configure VF "failed to set vf 5 vlan: operation not permitted"
  Warning  NoNetworkFound          3s    multus             cannot find a network-attachment-definition (k8s-pod-network) in namespace (kube-system): network-attachment-definitions.k8s.cni.cncf.io "k8s-pod-network" not found
  Normal   AddedInterface          3s    multus             Add eth0 [<IP_ADDRESS>/32] from k8s-pod-network
  Warning  FailedCreatePodSandBox  3s    kubelet            Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "de1c1c1592364e813842b5717853dfc708a37277aac87581fae3e30779937814": plugin type="multus" name="multus-cni-network" failed (add): [test1/test-router-69945bd84f-5826r:sriov-mlnx-connectx5]: error adding container to network "sriov-mlnx-connectx5": SRIOV-CNI failed to configure VF "failed to set vf 5 vlan: operation not permitted"
  Warning  NoNetworkFound          2s    multus             cannot find a network-attachment-definition (k8s-pod-network) in namespace (kube-system): network-attachment-definitions.k8s.cni.cncf.io "k8s-pod-network" not found
  Normal   AddedInterface          2s    multus             Add eth0 [<IP_ADDRESS>/32] from k8s-pod-network
  Warning  FailedCreatePodSandBox  2s    kubelet            Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "f56958ff6acb07533ea2f36a4e809e9198d54fe2eacc71d0ac1a92adc824bb8b": plugin type="multus" name="multus-cni-network" failed (add): [test1/test-router-69945bd84f-5826r:sriov-mlnx-connectx5]: error adding container to network "sriov-mlnx-connectx5": SRIOV-CNI failed to configure VF "failed to set vf 5 vlan: operation not permitted"
  Warning  NoNetworkFound          1s    multus             cannot find a network-attachment-definition (k8s-pod-network) in namespace (kube-system): network-attachment-definitions.k8s.cni.cncf.io "k8s-pod-network" not found
  Normal   AddedInterface          1s    multus             Add eth0 [<IP_ADDRESS>/32] from k8s-pod-network
  Warning  FailedCreatePodSandBox  0s    kubelet            Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "2e41362ccdf0416b6f684299070cd2a8565b848fe63f6d70620d89b053f4c5a5": plugin type="multus" name="multus-cni-network" failed (add): [test1/test-router-69945bd84f-5826r:sriov-mlnx-connectx5]: error adding container to network "sriov-mlnx-connectx5": SRIOV-CNI failed to configure VF "failed to set vf 5 vlan: operation not permitted"
  Warning  NoNetworkFound          0s    multus             cannot find a network-attachment-definition (k8s-pod-network) in namespace (kube-system): network-attachment-definitions.k8s.cni.cncf.io "k8s-pod-network" not found

This is true also for NETLINK commands:
root@worker:~# ip link set dev ens3f1 vf 3 vlan 0
RTNETLINK answers: Operation not permitted

Be mindful that we did not specify the VLAN ID in the NetworkAttachmentDefinition. Inside the SR-IOV configuration reference the VLAN tag is set to 0 by default (disabled). We believe that this being set to 0 does not prevent the sriov-cni from running this and this method trying to set 0 for VLAN tag and then failing, instead of skipping VLAN assignment and simply performing other operations (like changing network namespace of VF).
Why do we think that skipping VLAN assignment when it is 0 would solve the issue?
We tested this scenario manually by imposing an administrative trunk policy on all VFs, then we moved the VF interface into the Pod network namespace and provisioned a forbidden VLAN and an allowed VLAN.  This is because we will manually assign the virtual function interface into the Pod network namespace:
$ kubectl -n test1 exec -it test-router-875898ffb-k6g25 -- bash
root@test-router-875898ffb-k6g25:~# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet <IP_ADDRESS>/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
3: eth0@if5511: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 7e:33:bf:6b:41:a9 brd ff:ff:ff:ff:ff:ff link-netnsid 0
    inet <IP_ADDRESS>/32 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::7c33:bfff:fe6b:41a9/64 scope link
       valid_lft forever preferred_lft forever

Let us go back on the host and try to find this network namespace.
root@worker:~# ip netns list
cni-cdd833b3-1de0-8abd-e4d3-d4daa5cb1e62 (id: 13)
cni-f69bf47a-0950-361f-db8b-c1e485d34b6a (id: 3)
cni-4382825b-a464-fd6c-400c-1c5de6b0683b (id: 0)
cni-27f1a091-e6c7-dbe4-341d-dd9cae23770f (id: 12)
cni-4d7f0916-3e9e-e2f9-1f34-41f0a2630373 (id: 9)
cni-c68fc5b8-2f15-6b8f-8ba3-7c8421301974 (id: 11)
cni-2874a9fa-ac9a-2271-2da4-336164e88248 (id: 10)
cni-8cd024a2-6a0e-7761-8199-e64c217d8d17 (id: 8)
cni-4fc915e4-2931-a6a0-12d3-3de92c0f6377 (id: 7)
cni-8da838ce-80a8-9e82-b747-f72df1f472a2 (id: 6)
cni-cbaad5ab-0609-74fe-2288-a1d52e780f3c (id: 5)
cni-d8c780b4-35d2-c331-c2b4-ebe1392a3774 (id: 4)
cni-7e77f723-caa5-ed63-7240-26c6b141b407 (id: 2)
cni-978bb2af-d6d7-82e8-6752-e3aef9a0b021 (id: 1)

root@worker:~# ip netns exec cni-cdd833b3-1de0-8abd-e4d3-d4daa5cb1e62 ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet <IP_ADDRESS>/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
3: eth0@if5511: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 7e:33:bf:6b:41:a9 brd ff:ff:ff:ff:ff:ff link-netnsid 0
    inet <IP_ADDRESS>/32 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::7c33:bfff:fe6b:41a9/64 scope link
       valid_lft forever preferred_lft forever

We found the correct network namespace. Now we can move any VF interface into it; the VF interfaces are in format ens3f[0-1]v[0-7]. Lets take ens3f1v5 for this example:
root@worker:~# ip link set ens3f1v5 netns cni-cdd833b3-1de0-8abd-e4d3-d4daa5cb1e62
root@worker:~# ip netns exec cni-cdd833b3-1de0-8abd-e4d3-d4daa5cb1e62 ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet <IP_ADDRESS>/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
3: eth0@if5511: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 7e:33:bf:6b:41:a9 brd ff:ff:ff:ff:ff:ff link-netnsid 0
    inet <IP_ADDRESS>/32 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::7c33:bfff:fe6b:41a9/64 scope link
       valid_lft forever preferred_lft forever
25: ens3f1v5: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 3a:97:8b:03:e1:da brd ff:ff:ff:ff:ff:ff

Perfect! We snatched an VF interface. Lets configure it as in the previous examples from inside the Pod:
root@test-router-875898ffb-k6g25:~# ip link add link ens3f1v5 name ens3f1v5.1082 type vlan id 1082
root@test-router-875898ffb-k6g25:~# ip addr add <IP_ADDRESS>/28 dev ens3f1v5.1082
root@test-router-875898ffb-k6g25:~# ip link add link ens3f1v5 name ens3f1v5.1081 type vlan id 1081
root@test-router-875898ffb-k6g25:~# ip addr add <IP_ADDRESS>/28 dev ens3f1v5.1081
root@test-router-875898ffb-k6g25:~# ip link set dev ens3f1v5 up
root@test-router-875898ffb-k6g25:~# ip link set dev ens3f1v5.1082 up
root@test-router-875898ffb-k6g25:~# ip link set dev ens3f1v5.1081 up
root@test-router-875898ffb-k6g25:~# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet <IP_ADDRESS>/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
3: eth0@if5511: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 7e:33:bf:6b:41:a9 brd ff:ff:ff:ff:ff:ff link-netnsid 0
    inet <IP_ADDRESS>/32 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::7c33:bfff:fe6b:41a9/64 scope link
       valid_lft forever preferred_lft forever
4: ens3f1v5.1082@ens3f1v5: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 3a:97:8b:03:e1:da brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/28 scope global ens3f1v5.1082
       valid_lft forever preferred_lft forever
    inet6 fe80::3897:8bff:fe03:e1da/64 scope link
       valid_lft forever preferred_lft forever
5: ens3f1v5.1081@ens3f1v5: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 3a:97:8b:03:e1:da brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/28 scope global ens3f1v5.1081
       valid_lft forever preferred_lft forever
    inet6 fe80::3897:8bff:fe03:e1da/64 scope link
       valid_lft forever preferred_lft forever
25: ens3f1v5: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 3a:97:8b:03:e1:da brd ff:ff:ff:ff:ff:ff
    inet6 fe80::3897:8bff:fe03:e1da/64 scope link
       valid_lft forever preferred_lft forever

The final test is to perform a ping from these interfaces to confirm that our theory is indeed correct:
root@test-router-875898ffb-k6g25:~# ping -c4 -I ens3f1v5.1082 <IP_ADDRESS>
PING <IP_ADDRESS> (<IP_ADDRESS>) from <IP_ADDRESS> ens3f1v5.1082: 56(84) bytes of data.

--- <IP_ADDRESS> ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 3049ms
pipe 4

root@test-router-875898ffb-k6g25:~# ping -c4 -I ens3f1v5.1081 <IP_ADDRESS>
PING <IP_ADDRESS> (<IP_ADDRESS>) from <IP_ADDRESS> ens3f1v5.1081: 56(84) bytes of data.
64 bytes from <IP_ADDRESS>: icmp_seq=1 ttl=64 time=14.7 ms
64 bytes from <IP_ADDRESS>: icmp_seq=2 ttl=64 time=9.52 ms
64 bytes from <IP_ADDRESS>: icmp_seq=3 ttl=64 time=0.868 ms
64 bytes from <IP_ADDRESS>: icmp_seq=4 ttl=64 time=0.868 ms

--- <IP_ADDRESS> ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3033ms
rtt min/avg/max/mdev = 0.868/6.494/14.712/5.917 ms

To cleanup we delete the VLAN interfaces and return the VF interface into the root network namespace:
root@worker:~# ip netns exec cni-cdd833b3-1de0-8abd-e4d3-d4daa5cb1e62 ip link set ens3f1v5 netns 1
root@worker:~# ip netns exec cni-cdd833b3-1de0-8abd-e4d3-d4daa5cb1e62 ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet <IP_ADDRESS>/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
3: eth0@if5511: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 7e:33:bf:6b:41:a9 brd ff:ff:ff:ff:ff:ff link-netnsid 0
    inet <IP_ADDRESS>/32 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::7c33:bfff:fe6b:41a9/64 scope link
       valid_lft forever preferred_lft forever

Proposed remediation for the issue / solution time!

Here I am not asking for a new feature, but to simply not force LinkSetVfVlanQosProto when VLAN ID is 0.
This could be done by checking the NetConf struct if Vlan is 0 and skipping the method.

Please provide guidance on this matter!

@mlguerrero12 can you take a look on this one and let me know :)

@SchSeba, I think tt's a valid request.
We assign vlan 0 when the vlan parameter is not set. We could (and should) change this. The idea is to not set vlan 0 when the vlan parameter is not set and set vlan 0 when the config explicitly has the vlan parameter equal to 0.
For both cases, we will continue having the restriction of not allowing qos or vlan proto when vlan parameter is not set or 0.
I'll work on this.

@RefluxMeds, fix is in #296. Try to test it from your side please.

Hi @mlguerrero12 ,
I'm blocked with activities until next week. I'll dedicate some time next week to test out your changes!
Thank you so much!


Move _HOOKED_METHODS to variable in BaseCache

Variable is in wrong place, should be moved to BaseCache so it can be reused by other features

can't right now due to circular imports


e2e: added e2e workflows

This PR adds e2e test workflows for all 3 actions in the repo.

Closing as it's not ready.


removal of unused annotations

Signed-off-by: Robert Cerven<EMAIL_ADDRESS>

rn updated:
API changes

Removal of get_docker_build_logs method

Improvements

Removal of methods related to logs and rpm-packages annotations


Great Library!

This isn't an issue, so feel free to close or whatever you want to do. I didn't know where else to put it.
I just wanted to say that I really like this library. Everything worked exactly as expected and it's made publishing my lib 100 times easier.
Thanks for a great library!

Thanks! Glad it's useful.


Allow reading from StringIO as well as files or filenames

This PR supports loading files from stringIO, file objects or filenames.

@Exteris thanks for the PR! Could you please also add the test for that?


Letter alignment of diagonal text regressed in Firefox 47 on Linux

PDF file:
https://web.archive.org/web/20160328235633/http://www.bvg.de/images/content/linienverlaeufe/LinienverlaufBus101.pdf
Affected Configurations:

Firefox 48.0a1 (2016-04-01) + Linux Mint 17.3 (screenshot, right)
Firefox 47.0b6 + Android
HWA off

Not Affected:

Firefox 46.0 on Linux Mint 17.3 (screenshot, left)
Google Chrome
Firefox 46-49 + Windows

PDF.js version: 1.5.264
Is an extension: No
What went wrong?
The image shows the pdf file in the demo viewer on Firefox 46 (left) and Firefox 48 (right). On the right side, letters are not aligned.

This is related to #7277 where we first spotted this. As far as I know this has not yet been reported upsteam. Can someone take care of that who knows where the right place is to report these kinds of issues upsteam?

I noticed that it's broken in Firefox 46 on Android already, and updated the initial comment accordingly.

@fkaelberer Does this still happen? It seems fixed for my using Firefox 47.0.1 on Arch Linux and the bots also don't have this problem anymore, so I think upstream uplifted a patch for this.

Still broken with pdf.js 1.5.343 / Firefox 48.0b6.

@fkaelberer Based on your "Not Affected:" list above, it seems that this has been fixed upstream.
Would you be able to use mozregression, see http://mozilla.github.io/mozregression/, to find out when and in which commit/bug this was fixed.

@Snuffleupagus Awesome tool ;-)
Broke in https://hg.mozilla.org/integration/mozilla-inbound/rev/180f3f0494a7
Fixed in https://hg.mozilla.org/integration/mozilla-inbound/rev/2a0eda9a4bb6

Thank you for looking into that! Based on these findings I'm closing this issue as fixed, also since it's not something we can address in PDF.js as it's really a browser bug.

[...] also since it's not something we can address in PDF.js as it's really a browser bug.

What could perhaps be done is to comment in https://bugzilla.mozilla.org/show_bug.cgi?id=1274111, referring to e.g. this issue and pointing out that it's affecting the PDF viewer in Firefox on Linux, and ask if the patch could perhaps be uplifted to Firefox 48.
At this point, we're getting close to the next Firefox release, but I suppose it can't hurt to ask!

Sounds good. It might prevent issues for the next release(s).


Uncaught TypeError: Cannot read property 'params' of null @ start of touch event

The following error occurs when you use the wrapper on mobile devices or the viewports of browsers like Chrome:
Uncaught TypeError: Cannot read property 'params' of null
at HTMLDivElement.x.onTouchStart (app.js:640)
at t.invokeTask (app.js:975)
at e.runTask (app.js:975)
at HTMLDivElement.invoke (app.js:975)
The above error appears in the provided example: [https://zefoy.github.io/ngx-swiper-wrapper/].

I have only seen that in browser touch emulation state, although I haven't checked on actual mobile device. Its a bug in the Swiper library itself and I made a fix at some point for it, but then I noticed that the error was not critical and did not make a PR. I hope that the next Swiper release would fix that error if not I can make the fix again and make a PR to the Swiper project.

I see,
Thank you for the clarification. Good to know its not a critical error. If possible , I would appreciate the fix in a PR till Swiper solves the bug.

I will definitely look into this next month since I need to fix this somehow before we launch our new product since this error exists in our app as well.

I have the similar error when trying to use this library with Ionic 2. Any work around until sconix patch it?

Seeing the same issue with [config] here. This is a deal-breaker for me because I need a vertical swiper nested in horizontal, so I can't fall back to a single global config. Any status update on this?

If you can tell me how to reproduce the problem with config I can fix it. The params is a bug in Swiper and there is an issue about that and it not related to this library nor the config issue you are seeing.

I have encountered the same problem. Will test on actual device, but this fails in chrome using v3.4.2.

I'm getting the same error when using Swiper on its own when destroying and reiniting. I solved it by overriding the first parameter in destroy() method, setting it to false.
 deleteInstance - boolean - Set it to false (by default it is true) to not to delete Swiper instance
After this I manually remove DOM and successfully create a memory leak 👎
Not sure how to solve this properly.

Yes there is some bug in the Swiper destroy method. Lets hope that it would be fixed in next release.

@Dranix I have the same issue with Ionic 4. As soon as I add a config (with e.g. direction: 'horizontal') I get Uncaught TypeError: Cannot read property 'params' of null at HTMLDivElement.Swiper.s.onTouchStart (swiper.js:1544). Any news or should I also try to patch swiper.js?

There are no new news from the Swiper project. There is a really easy way to patch it, you just need to add if (this.swiper) check before the line where the error happens. But thats just a quick fix, the proper fix would be to tear down the event listener properly on destroy. I try to make a proper fix and PR to Swiper during this week or at the latest on next week.

I looked into this and could not find a bug in Swiper. There was very odd situation that the event listener was removed correctly but it did not remove. My conclusion is that something has to conflict with Swiper/browsers event handling. After that I noticed that with fresh npm install the error was removed from the example app at least. So what ever it was that caused the error has been fixed in some package afaik. So I am closing this for now and if somebody can still reproduce this with latest versions of the dependencies then I can open this again.

I ran into the same issue.. any updates on how to fix it?

This was fixed by the zone.js as said on the above comment. So at least with zone 0.8.10 the error was gone.


Feature: Add new topics to the list

Type of feature
🍕 Feature
Current behavior
Vue was requested as well as Kubernetes
https://github.com/orgs/open-sauced/discussions/11
Suggested solution
Add to the topics list

Add to the interests list

https://github.com/open-sauced/insights/blob/86824c217733f322b931f7f33d25b70600049737/components/atoms/LanguagePill/LanguagePill.tsx#L19
Additional context
Previous PR https://github.com/open-sauced/insights/pull/877
Code of Conduct

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

Contributing Docs

[ ] I agree to follow this project's Contribution Docs

@bdougie what icons should I use?

Vue 🔎
K8s 👀


Disable delete of organisation if there's any child organisation exists

Disable delete of organisation if there's any child organisation exists

Written by @xqliu
Created at 2016-06-16T09:50:29.000+0800
Link to http://betterlife.atlassian.net/browse/BE-241

Partially depends on  https://github.com/flask-admin/flask-admin/issues/1301

Written by @xqliu
Created at 2016-06-16T10:27:22.537+0800


I am having a problem when trying to launch Ubuntu On chrome os

Please paste the output of the following command here: sudo edit-chroot -all
```name: precise
encrypted: no
Entering /mnt/stateful_partition/crouton/chroots/precise...
crouton: version 1-20161129162558~master:5f2f11f9
release: precise
architecture: amd64
xmethod: xorg
targets: xfce
host: version 8872.76.0 (Official Build) stable-channel terra
kernel: Linux localhost 3.18.0-13437-g2bea612c #1 SMP PREEMPT Fri Jan 6 23:52:00 PST 2017 x86_64 x86_64 x86_64 GNU/Linux
freon: yes
Unmounting /mnt/stateful_partition/crouton/chroots/precise...
name: trusty
encrypted: yes, locked
Unmounting /mnt/stateful_partition/crouton/chroots/trusty...

#### Please describe your issue:
When trying to launch Ubuntu from the crosh shell, I get an error saying "Unable to contact settings server" and then "Unable to create failsafe session."
Here is what the command line looks like after attempting to start but then it fails:
Entering /mnt/stateful_partition/crouton/chroots/precise...
Failed to start message bus: Failed to open "/etc/selinux/targeted/contexts/dbus_contexts": No such file or directory
WARNING: starting chroot system dbus daemon failed with code 1
/usr/bin/startxfce4: Starting X server

_XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root

X.Org X Server 1.15.1
Release Date: 2014-04-13
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.42-75-generic x86_64 Ubuntu
Current Operating System: Linux localhost 3.18.0-13437-g2bea612c #1 SMP PREEMPT Fri Jan 6 23:52:00 PST 2017 x86_64
Kernel command line: cros_secure console= loglevel=7 init=/sbin/init cros_secure oops=panic panic=-1 root=/dev/dm-0 rootwait ro dm_verity.error_behavior=3 dm_verity.max_bios=-1 dm_verity.dev_wait=1 dm="1 vroot none ro 1,0 3584000 verity payload=PARTUUID=882c0e31-ae34-714f-bc18-e4c6b6ac250f/PARTNROFF=1 hashtree=PARTUUID=882c0e31-ae34-714f-bc18-e4c6b6ac250f/PARTNROFF=1 hashstart=3584000 alg=sha1 root_hexdigest=c177ea78b9beb329d4c1f09c2341ca1e455243ba salt=5bf74a9e1eaef12644878128e5610d35e242a02f6d996d3b35562d67d052e666" noinitrd vt.global_cursor_default=0 kern_guid=882c0e31-ae34-714f-bc18-e4c6b6ac250f add_efi_memmap boot=local noresume noswap i915.modeset=1 tpm_tis.force=1 tpm_tis.interrupts=0 nmi_watchdog=panic,lapic
Build Date: 12 February 2015  03:37:52PM
xorg-server 2:1.15.1-0ubuntu2~precise5 (For technical support please see http://www.ubuntu.com/support)
Current version of pixman: 0.30.2
        Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(++) Log file: "/tmp/Xorg.crouton.1.log", Time: Mon Jan 16 20:24:57 2017
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
setversion 1.4 failed: Permission denied
Initializing built-in extension Generic Event Extension
Initializing built-in extension SHAPE
Initializing built-in extension MIT-SHM
Initializing built-in extension XInputExtension
Initializing built-in extension XTEST
Initializing built-in extension BIG-REQUESTS
Initializing built-in extension SYNC
Initializing built-in extension XKEYBOARD
Initializing built-in extension XC-MISC
Initializing built-in extension SECURITY
Initializing built-in extension XINERAMA
Initializing built-in extension XFIXES
Initializing built-in extension RENDER
Initializing built-in extension RANDR
Initializing built-in extension COMPOSITE
Initializing built-in extension DAMAGE
Initializing built-in extension MIT-SCREEN-SAVER
Initializing built-in extension DOUBLE-BUFFER
Initializing built-in extension RECORD
Initializing built-in extension DPMS
Initializing built-in extension X-Resource
Initializing built-in extension XVideo
Initializing built-in extension XVideo-MotionCompensation
Initializing built-in extension XFree86-VidModeExtension
Initializing built-in extension XFree86-DGA
Initializing built-in extension XFree86-DRI
Initializing built-in extension DRI2
Loading extension GLX
xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted)
[intel_init_bufmgr:1069] Error initializing buffer manager.
setversion 1.4 failed: Permission denied
crouton: version 1-20161129162558~master:5f2f11f9
release: precise
architecture: amd64
xmethod: xorg
targets: xfce
host: version 8872.76.0 (Official Build) stable-channel terra
kernel: Linux localhost 3.18.0-13437-g2bea612c #1 SMP PREEMPT Fri Jan 6 23:52:00 PST 2017 x86_64 x86_64 x86_64 GNU/Linux
freon: yes
Failed to start message bus: Failed to open "/etc/selinux/targeted/contexts/dbus_contexts": No such file or directory
EOF in dbus-launch reading address from bus daemon
/etc/xdg/xfce4/xinitrc: 1: /etc/xdg/xfce4/xinitrc: ssh-agent: not found

** (xfce4-session:26996): CRITICAL **: Unable to contact D-Bus session bus: Unknown error

** (xfce4-session:26996): CRITICAL **: Unable to contact D-Bus session bus: //bin/dbus-launch terminated abnormally with the following error: EOF in dbus-launch reading address from bus daemon

(xfce4-session:26996): xfconf-CRITICAL **: xfconf_init() must be called before attempting to use libxfconf!

** (xfce4-session:26996): CRITICAL **: dbus_g_proxy_connect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed

** (xfce4-session:26996): CRITICAL **: dbus_g_proxy_connect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed

(xfce4-session:26996): xfconf-CRITICAL **: xfconf_init() must be called before attempting to use libxfconf!

** (xfce4-session:26996): CRITICAL **: dbus_g_proxy_call: assertion `DBUS_IS_G_PROXY (proxy)' failed

(xfce4-session:26996): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed

(xfce4-session:26996): xfconf-CRITICAL **: xfconf_init() must be called before attempting to use libxfconf!

** (xfce4-session:26996): CRITICAL **: dbus_g_proxy_call: assertion `DBUS_IS_G_PROXY (proxy)' failed

(xfce4-session:26996): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed

(xfce4-session:26996): xfconf-CRITICAL **: xfconf_init() must be called before attempting to use libxfconf!

** (xfce4-session:26996): CRITICAL **: dbus_g_proxy_connect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed

** (xfce4-session:26996): CRITICAL **: dbus_g_proxy_connect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed

(xfce4-session:26996): xfconf-CRITICAL **: xfconf_init() must be called before attempting to use libxfconf!

** (xfce4-session:26996): CRITICAL **: dbus_g_proxy_call: assertion `DBUS_IS_G_PROXY (proxy)' failed

(xfce4-session:26996): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed

(xfce4-session:26996): xfconf-CRITICAL **: xfconf_init() must be called before attempting to use libxfconf!

** (xfce4-session:26996): CRITICAL **: dbus_g_proxy_disconnect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed

** (xfce4-session:26996): CRITICAL **: dbus_g_proxy_disconnect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed

(xfce4-session:26996): xfconf-CRITICAL **: xfconf_init() must be called before attempting to use libxfconf!

** (xfce4-session:26996): CRITICAL **: dbus_g_proxy_call: assertion `DBUS_IS_G_PROXY (proxy)' failed

(xfce4-session:26996): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
_IceTransmkdir: Owner of /tmp/.ICE-unix should be set to root

(xfce4-session:26996): xfconf-CRITICAL **: xfconf_init() must be called before attempting to use libxfconf!

** (xfce4-session:26996): CRITICAL **: dbus_g_proxy_call: assertion `DBUS_IS_G_PROXY (proxy)' failed

(xfce4-session:26996): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed

(xfce4-session:26996): xfconf-CRITICAL **: xfconf_init() must be called before attempting to use libxfconf!

** (xfce4-session:26996): CRITICAL **: dbus_g_proxy_call: assertion `DBUS_IS_G_PROXY (proxy)' failed

(xfce4-session:26996): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed

(xfce4-session:26996): xfconf-CRITICAL **: xfconf_init() must be called before attempting to use libxfconf!

** (xfce4-session:26996): CRITICAL **: dbus_g_proxy_call: assertion `DBUS_IS_G_PROXY (proxy)' failed

(xfce4-session:26996): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed

(xfce4-session:26996): xfconf-CRITICAL **: xfconf_init() must be called before attempting to use libxfconf!

** (xfce4-session:26996): CRITICAL **: dbus_g_proxy_call: assertion `DBUS_IS_G_PROXY (proxy)' failed

(xfce4-session:26996): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed

(xfce4-session:26996): xfconf-CRITICAL **: xfconf_init() must be called before attempting to use libxfconf!

** (xfce4-session:26996): CRITICAL **: dbus_g_proxy_call: assertion `DBUS_IS_G_PROXY (proxy)' failed

(xfce4-session:26996): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed

(xfce4-session:26996): xfconf-CRITICAL **: xfconf_init() must be called before attempting to use libxfconf!

** (xfce4-session:26996): CRITICAL **: dbus_g_proxy_call: assertion `DBUS_IS_G_PROXY (proxy)' failed

(xfce4-session:26996): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
Failed to connect to Xfconf daemon: //bin/dbus-launch terminated abnormally with the following error: EOF in dbus-launch reading address from bus daemon

running 'ssh-agent -s -k'
/etc/xdg/xfce4/xinitrc: 1: eval: ssh-agent: not found
Running exit commands...
/usr/bin/xinit: connection to X server lost

waiting for X server to shut down Hangup
xscreensaver: 20:25:02: SIGHUP received: restarting...
xscreensaver: 20:25:02: running as dfordium/dfordium (1000/1000)

xscreensaver: 20:25:02: Can't open display: :1
xscreensaver: 20:25:02: running as dfordium/dfordium (1000/1000)

xscreensaver: 20:25:02: Errors at startup are usually authorization problems.
              But you're not logging in as root (good!) so something
              else must be wrong.  Did you read the manual and the FAQ?

              http://www.jwz.org/xscreensaver/faq.html
              http://www.jwz.org/xscreensaver/man.html

(EE) Server terminated successfully (0). Closing log file.

Unmounting /mnt/stateful_partition/crouton/chroots/precise...

#### If known, describe the steps to reproduce the issue:
This happens every time I try to run using sudo startxfce4

Your targets aren't fully
$ sh ~/Downloads/crouton -t list
...
xfce
        Installs the Xfce desktop environment. (Approx. 250MB)
        Requires: gtk-extra
...
gtk-extra
        GTK-based tools including gdebi, gksu, and a simple browser.
        Requires: x11
...
x11
        X11 via autodetected backend. Does not install any desktop environment.

I think you have to
sudo sh -e ~/Downloads/crouton -t x11,gtk-extra -n precise

After that to be sure your .xinitrc is complete. The next code should be at the end of the file exec startxfce4. Try for this
sudo enter-chroot -n precise
"exec startxfce4" > ~/.xinitrc

Lunch
sudo enter-chroot startxfce4

Dup of #2970, see https://github.com/dnschneid/crouton/issues/2970#issuecomment-270053222


Fixed import another lib syntax

For more detail please check out this link below
https://github.com/adobe/places-monitor-ios/issues/44

Hey @chawatvish -
Thanks for opening a PR!  We will be reviewing and investigating the changes you've proposed tomorrow.
If the changes are accepted, we'll need you to sign the Adobe CLA in order for us to merge your PR.
steve benedick
sr mobile sdk engineer
adobe experience platform

Thank you. I will wait for your review.

Hey @chawatvish -
Changes look good!
If you want to sign the CLA I can merge in this PR.  If you'd rather not sign the CLA, I will open a pull request with these changes.  Thanks again!
-steveb

Thanks for review. I signed Adobe CLA already.


Add encoding parameter to BluetoothModule and BluetoothDevice write methods

For my work project i need a different encoding type (not base64). So i decide make some improvements. This is my first pull request so don't be too strict :)

Thanks for the PR.
The issue here is that on the Native side, the data is being decoded from Base64.
Android
https://github.com/kenjdavidson/react-native-bluetooth-classic/blob/0f4c4eb8ef5e7f3d5eeb0bc73cf5848d60d07edf/android/src/main/java/kjd/reactnative/bluetooth/RNBluetoothClassicModule.java#L872
IOS
https://github.com/kenjdavidson/react-native-bluetooth-classic/blob/0f4c4eb8ef5e7f3d5eeb0bc73cf5848d60d07edf/ios/RNBluetoothClassic.swift#L399
I'm not entirely sure how if you're encoding this with ascii (lets say) on the Javascript side, that the native side is able to decode it properly and send the appropriate message?

Could you provide the example where this is being used? And decoded on then native side properly?

Essentially you shouldn't care how this is getting encoded, I wouldn't think using the following data flow:

Application calls device.connect()
Application calls `device.write('this is some data') using a String for the most basic case.

'this is some data' is base64 encoded
If for example you encoded this as Ascii using your change

Native side attempts to decode the value

as Bas64 it will be decoded properly
as ascii it will not be decoded properly without changes to native

The native side actually writes this new string to the device (where it uses the correct encoding).

Without your actual use case it's hard to see whats up but:
let connected = await device.connect({ charset: 'ascii' });

Will cause:

Connect with charset
Call `device.write("this is some data")
"this is some data" as base64
decode "this is some data" as base64, which should give us our string back
Write "this is some data" to device using ascii

The end product is ascii gets written to the device.  If you're having an issue with this, we should definitely fix it.  But the Base64 just for communication to the Native side through the React Native bridge, and NOT to the device.

Thanks for the PR.
The issue here is that on the Native side, the data is being decoded from Base64.
Android
https://github.com/kenjdavidson/react-native-bluetooth-classic/blob/0f4c4eb8ef5e7f3d5eeb0bc73cf5848d60d07edf/android/src/main/java/kjd/reactnative/bluetooth/RNBluetoothClassicModule.java#L872
IOS
https://github.com/kenjdavidson/react-native-bluetooth-classic/blob/0f4c4eb8ef5e7f3d5eeb0bc73cf5848d60d07edf/ios/RNBluetoothClassic.swift#L399
I'm not entirely sure how if you're encoding this with ascii (lets say) on the Javascript side, that the native side is able to decode it properly and send the appropriate message?

Could you provide the example where this is being used? And decoded on then native side properly?

Essentially you shouldn't care how this is getting encoded, I wouldn't think using the following data flow:

Application calls device.connect()
Application calls `device.write('this is some data') using a String for the most basic case.

'this is some data' is base64 encoded
If for example you encoded this as Ascii using your change

Native side attempts to decode the value

as Bas64 it will be decoded properly
as ascii it will not be decoded properly without changes to native

The native side actually writes this new string to the device (where it uses the correct encoding).

Without your actual use case it's hard to see whats up but:
let connected = await device.connect({ charset: 'ascii' });

Will cause:

Connect with charset
Call `device.write("this is some data")
"this is some data" as base64
decode "this is some data" as base64, which should give us our string back
Write "this is some data" to device using ascii

The end product is ascii gets written to the device.  If you're having an issue with this, we should definitely fix it.  But the Base64 just for communication to the Native side through the React Native bridge, and NOT to the device.

Sry, didnt see that on the Native side, the data is being decoded from Base64.
But i dont understand one thing. I write some data as Buffer:
const data = Buffer.from([1,2,3,4]); device.write(data).
and then in BluetoothModule that data will be encoded with base64. But we have condition:
if ("string" === typeof message) {   data = Buffer.from(message); } else {   data = Buffer.from(message.toString()); }
Buffer.from(message.toString()) will change data that i was send. Or i something understand again?

Sry, didnt see that on the Native side, the data is being decoded from Base64.
But i dont understand one thing. I write some data as Buffer:
const data = Buffer.from([1,2,3,4]); device.write(data).
and then in BluetoothModule that data will be encoded with base64. But we have condition:
if ("string" === typeof message) {   data = Buffer.from(message); } else {   data = Buffer.from(message.toString()); }
Buffer.from(message.toString()) will change data that i was send. Or i something understand again?

Oh ya, the data's going to get all out of wack, the problem is you're going to need to unwackify it on the native side.   The only viable type for transferring data across the react bridge is String:
https://reactnative.dev/docs/native-modules-android#argument-types
So the goal is:

Get a the data into a consistent String value
Unwrap it in your DeviceConnection

The currently available DeviceConnection only expects String.  So regardless of the changes you make, you're going to need to write your own DeviceConnection for handling that data on the Native side.
If you look at the data processing, this is what happens on the React side:
> const message = Buffer.from([1,2,3,4]);
> message.toString()
'\u0001\u0002\u0003\u0004'
> const data = Buffer.from(message.toString());
> data.toString();
'\u0001\u0002\u0003\u0004'
> const sent = data.toString("base64");
> sent
'AQIDBA=='

So the Native (Java and IOS) get the string AQIDBA==.  When this is converted back to a String (which again is all we have to work with):
            // At this point the data should be encoded correctly.  The original version did some
            // weird decoding and encoding but it didn't seem right.  At this point leaving it
            // as is and required to be set at the client level.
            byte[] data = Base64.decode(message, Base64.DEFAULT);

So you've got the byte[] that matches the original decoding: '\u0001\u0002\u0003\u0004'.  So ya, at this point the default will write that String to the device in the provided charset (ascii default, which is probably not what you want).
If you want to write the unicode, you need to tell the native side that:
let connected = await device.connect({ charset: 'utf-8' });  // Or whatever you want

So what exactly is getting written to the device?
And what exactly are you expecting to be written to the device?

Oh ya, the data's going to get all out of wack, the problem is you're going to need to unwackify it on the native side.   The only viable type for transferring data across the react bridge is String:
https://reactnative.dev/docs/native-modules-android#argument-types
So the goal is:

Get a the data into a consistent String value
Unwrap it in your DeviceConnection

The currently available DeviceConnection only expects String.  So regardless of the changes you make, you're going to need to write your own DeviceConnection for handling that data on the Native side.
If you look at the data processing, this is what happens on the React side:
> const message = Buffer.from([1,2,3,4]);
> message.toString()
'\u0001\u0002\u0003\u0004'
> const data = Buffer.from(message.toString());
> data.toString();
'\u0001\u0002\u0003\u0004'
> const sent = data.toString("base64");
> sent
'AQIDBA=='

So the Native (Java and IOS) get the string AQIDBA==.  When this is converted back to a String (which again is all we have to work with):
            // At this point the data should be encoded correctly.  The original version did some
            // weird decoding and encoding but it didn't seem right.  At this point leaving it
            // as is and required to be set at the client level.
            byte[] data = Base64.decode(message, Base64.DEFAULT);

So you've got the byte[] that matches the original decoding: '\u0001\u0002\u0003\u0004'.  So ya, at this point the default will write that String to the device in the provided charset (ascii default, which is probably not what you want).
If you want to write the unicode, you need to tell the native side that:
let connected = await device.connect({ charset: 'utf-8' });  // Or whatever you want

So what exactly is getting written to the device?
And what exactly are you expecting to be written to the device?

Hey, so I took these changes and made them manually, with one other change that wasn't included.  So you should be able to call:
device#write(data, encoding?)
or
RNBluetoothClassic.writeToDevice(address, data, encoding?)
which will now:

If data is a Buffer it will leave it as is
If data is anything else, it will encode using the provided encoding (utf8 as default, which is undefined anyhow)
Finally this is still Base64 encoded to get across the React Native bridge

At this point, within the Java / IOS modules you will have:
byte[] data = Base64.decode(message)
You'll still need to create and assign a custom DeviceConnection in order to write this data to the device, the default DelimitedStringDeviceConnectionImpl will still attempt to convert this device to a string then write it as those bytes.
I've also added ByteArrayDeviceConnectionImpl which:

Writes the byte[] as it was provided to Native side
Reads the byte[] and passes the Base64 encoding of it.

So you'll still need to handle that in javascript correctly on the React Native side.
Please let me know.

Hey, so I took these changes and made them manually, with one other change that wasn't included.  So you should be able to call:
device#write(data, encoding?)
or
RNBluetoothClassic.writeToDevice(address, data, encoding?)
which will now:

If data is a Buffer it will leave it as is
If data is anything else, it will encode using the provided encoding (utf8 as default, which is undefined anyhow)
Finally this is still Base64 encoded to get across the React Native bridge

At this point, within the Java / IOS modules you will have:
byte[] data = Base64.decode(message)
You'll still need to create and assign a custom DeviceConnection in order to write this data to the device, the default DelimitedStringDeviceConnectionImpl will still attempt to convert this device to a string then write it as those bytes.
I've also added ByteArrayDeviceConnectionImpl which:

Writes the byte[] as it was provided to Native side
Reads the byte[] and passes the Base64 encoding of it.

So you'll still need to handle that in javascript correctly on the React Native side.
Please let me know.

Hey, thanks for update. It will help to write Buffer type wridth into device. That was i need :)
Now i saw another problem with receiving data from device. DelimitedStringDeviceConnectionImpl.java that used by default when we receive data have method:
@Override
    protected void receivedData(byte[] bytes) {
        Log.d(this.getClass().getSimpleName(),
                String.format("Received %d bytes from device %s", bytes.length, getDevice().getAddress()));

        mBuffer.append(new String(bytes, mCharset));

        if (mOnDataReceived != null) {
            Log.d(this.getClass().getSimpleName(),
                    "BluetoothEvent.READ listener is registered, providing data");

            String message;
            while ((message = read()) != null) {
                mOnDataReceived.accept(getDevice(), message);
            }
        } else {
            Log.d(this.getClass().getSimpleName(),
                    "No BluetoothEvent.READ listeners are registered, skipping handling of the event");
        }
    }

But i receive "raw" data and operation mBuffer.append(new String(bytes, mCharset)); return empty string for me.
Also i see that there is was added new class ByteArrayDeviceConnectionImpl with alternative receivedData method in last commit. That will solve my problem as i think, but how can i use that class instead of DelimitedStringDeviceConnectionImpl?

Hey, thanks for update. It will help to write Buffer type wridth into device. That was i need :)
Now i saw another problem with receiving data from device. DelimitedStringDeviceConnectionImpl.java that used by default when we receive data have method:
@Override
    protected void receivedData(byte[] bytes) {
        Log.d(this.getClass().getSimpleName(),
                String.format("Received %d bytes from device %s", bytes.length, getDevice().getAddress()));

        mBuffer.append(new String(bytes, mCharset));

        if (mOnDataReceived != null) {
            Log.d(this.getClass().getSimpleName(),
                    "BluetoothEvent.READ listener is registered, providing data");

            String message;
            while ((message = read()) != null) {
                mOnDataReceived.accept(getDevice(), message);
            }
        } else {
            Log.d(this.getClass().getSimpleName(),
                    "No BluetoothEvent.READ listeners are registered, skipping handling of the event");
        }
    }

But i receive "raw" data and operation mBuffer.append(new String(bytes, mCharset)); return empty string for me.
Also i see that there is was added new class ByteArrayDeviceConnectionImpl with alternative receivedData method in last commit. That will solve my problem as i think, but how can i use that class instead of DelimitedStringDeviceConnectionImpl?

Documentation is a wonderful thing.  :P
At least I think so. Haha. You should be able to easily add it to your package in Android. IOS I haven't tried yet but it smuch more annoying.
Keep me posted man. This week is rough for me, the byte array was don't quickly and will need some love. So feel free to pr it.

Documentation is a wonderful thing.  :P
At least I think so. Haha. You should be able to easily add it to your package in Android. IOS I haven't tried yet but it smuch more annoying.
Keep me posted man. This week is rough for me, the byte array was don't quickly and will need some love. So feel free to pr it.

https://www.kenjdavidson.com/react-native-bluetooth-classic/android/rn-bluetooth-classic-package/

https://www.kenjdavidson.com/react-native-bluetooth-classic/android/rn-bluetooth-classic-package/


Move admin state from Group name to dedicated field

Closes #184

Coverage remained the same at 82.647% when pulling b7daa906ed9ade5bd213aabfa6796c02794890c9 on feature/internal-group-permission into 502e1105ecb7ff84c147c287cae02abcb500e46d on master.


High tier boss idea

Another boss idea, potentially high tiered: Demon of Deception. The fight starts out with the boss standing in the middle of the arena, with an aura that steals away stats and auto attacks. If you hit boss with any form of damage (radiance included), it will kinda manta style and spawn two illusions along. However you have to hit the real boss 4 times total in order to be able to deal damage to it, but if you hit an illusion, it will also spawn two other illusions for a total of three. The illusions still have the auto attack animation, but do no damage whatsoever. The purpose is to figure out which one is the real boss while taking as little time as possible. For every illusion hit during this phase, the boss will gain a stackable buff that grants armor and magic resist. The stat steals from the initial encounter and the protected buff persists until the challenge is over. So that the challengers should try to pass this phase as quickly as possible while not using cleave items or of the sort.
Phase 1: The demon fires out spells in a random direction, all obvious ones, but the particular spells are decided from the heroes that step into the battle. (if a pudge is fighting then there would be pudge hooks, etc). The spell chosen would not be random, (unless programmers want to code a projectile spell for every heroe's ability for the boss to use), and the number of spells would increase as the battle drags on. The catch is that as the fight goes on, the boss will start throwing out illusion spells. Illusion spells are spells that only have the particle animation, but do no damage and inflict no status effects. The idea is that the screen is filled with spells, both real and fake, and for heroes that lack the movement speed to dodge them all, they would have to risk the probability of a fake spell.
Phase 2: After a percentage of hp is removed, the boss throws out target point projectiles called Fracturing. The hero hit with this projectile will have one of its abilities muted for the rest of the battle, and spawn an illusion similar to Morphling's ult (the illusion does not die when the hero dies and the illusion has access to only the spell that was muted). Both the original hero and the clone will have half the stats of the orginal. If a hero is hit with another one of these Fracturing spells while under the effect of one, then an additional illusion is spawned and the stats of the illusions and original hero is reduced to a third of what it should be. Micro-management is the key to this stage, and the crowdiness serve to hinder dodging.
If an Fractured illusion dies during the battle, the hero loses that ability entirely until the battle is over. If the original hero dies while saving an illusion, the Hero will not be considered dead. They would respawn at the location of the Fractured illusion.
Jack Grayling - Today at 11:02 PM
Only heroes will be targetted by the Fracturing spell, Heroes hit with three Fracturing spells (split into four) will no longer be able to be hit by the spell again
As of currently, there is no phase 3, as I believe it is difficult enough. This could still be changed
tl;dr Phase 1 is whack-a-mole (Lasts 4 hits), Phase 2 is dodge the projectiles-but-it-might-be-fake, Phase 3 is Phase 2+ your abilities are now on illusions

This seems like a lot of busy work. Phase three has served as inspiration for Stop Killing Yourself.


Folders Do Not Expand

Issue Type: Bug
Since the latest update, folders do not expand.  I have the entire "D:" drive available to view, but when I try to open a folder to view the files, it just spins.  I need to close VS Code from Task Manager to get it to stop.
VS Code version: Code 1.32.1 (05f146c7a8f7f78e80261aa3b2a2e642586f9eb3, 2019-03-08T00:51:49.278Z)
OS version: Windows_NT x64 10.0.17763

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz (8 x 3408)

GPU Status
2d_canvas: enabledchecker_imaging: disabled_offflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwarerasterization: enabledsurface_synchronization: enabled_onvideo_decode: enabledwebgl: enabledwebgl2: enabled

Memory (System)
31.90GB (21.62GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions (1)

Extension
Author (truncated)
Version

mssql
ms-
1.4.0

Is this in the Explorer view? Did you open the D drive through Open Folder?

Yes, this is the Explorer view.  The "D:" drive is my default folder that I
just keep open and browse in the Explorer.
Currently no files open, and I can't close the application.
On Tue, Mar 12, 2019 at 8:56 AM Rob Lourens<EMAIL_ADDRESS>wrote:

Is this in the Explorer view? Did you open the D drive through Open Folder?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/vscode/issues/70226#issuecomment-472055619,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGwXr01e5bxxYr_5ag4pUPYtLY27ZM6Wks5vV84ngaJpZM4bo4_s
.

I can not preorduce this.
Can you reproduce using vscode insiders? https://code.visualstudio.com/insiders/
If yes, can you attach a gif showing this issue?

Sorry, but I cannot help with troubleshooting this.
Version 1.32.1 cannot be used, so I have uninstalled and re-installed
1.31.0.
I'll watch for future updates and hope things get fixed.
On Wed, Mar 13, 2019 at 2:22 AM Isidor Nikolic<EMAIL_ADDRESS>wrote:

I can not preorduce this.
Can you reproduce using vscode insiders?
https://code.visualstudio.com/insiders/
If yes, can you attach a gif showing this issue?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/vscode/issues/70226#issuecomment-472342148,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGwXr8oplDaiV1qIVQGvTXZfi8iE5Ug3ks5vWMNigaJpZM4bo4_s
.

Sure.


Default destructuring object not recognized properly.

Bug Report
🔎 Search Terms
destrucruting, object, default, empty
🕗 Version & Regression Information
Version 4.9.4
⏯ Playground Link
https://www.typescriptlang.org/play?#code/GYVwdgxgLglg9mABMAFAbwB6ILyIIwC+AXIpiWCALYBGApgE4E6kECUpAUIt4vbVCHpIMHAkA
💻 Code
function f({x = 1}: {x: number} = {}) {
    return x
}

🙁 Actual behavior
Property 'x' is missing in type '{}' but required in type '{ x: number; }'
This is wrong because calling, for example, f() will result in x being 1, even tho the = {} default definition is empty (because the destructuring object has a default).
🙂 Expected behavior
I would expect this to pass type linting.

Note that this is the best DRY way to define this in javascript. If you leave out the = {} then f() will result in an error (x not defined). If you instead define this as function f({x} = {x: 1} then calling f({}) will result in x not defined as well. The above is the shortest way to defined it so that both f() and f({}) can be called without issue.

Duplicate of #51179.

Ah I see, the correct way of writing this is:
function f({x = 1}: {x:? number} = {}) {
    return x
}

I assume this is because the type {x:? number} here is defining what argument type can be passed in rather than defining what parameter type is received. This is a rather awkward situation. It seems that typescript does recognize the fact that the parameter has a different type than the argument, and properly recognizes that the parameter is not in fact optional.

Yeah, for destructurings, the type annotation specifies what kind of values can be used to initialize it, not what types the bindings will ultimately have.  It usually happens to be that these are the exact same type, except for the case where one or more of the bindings has a default.
The way to think about it is that you’re annotating the imaginary temp variable used to destructure the object.  It’s a bit weird IMO, but that’s how they chose to design it.

Yeah, among equal desugarings to choose from, TS treats this as
function f(_obj: {x: number} = {}) { // <- type violation
    let x = _obj.x ?? 1;
    return x;
}


lc823450_usbdev: use small lock in arch/arm/src/lc823450/lc823450_usbdev.c

Summary
lc823450_usbdev: use small lock in arch/arm/src/lc823450/lc823450_usbdev.c
Impact
lc823450_usbdev
Testing
ci

[Experimental Bot, please feedback here]
No.  This PR does not meet the NuttX requirements. The provided information is far too brief.  Here's why:

Summary:  While it states what was changed (using a small lock), it fails to explain why this change was necessary, how it works (what the small lock replaces and the mechanism of the change), and lacks any reference to related issues.
Impact:  Simply repeating "lc823450_usbdev" doesn't explain the impact.  All the YES/NO questions need actual answers with descriptions where applicable.  Does this change how the driver interacts with the hardware? Does it affect performance?  These details are critical.
Testing:  "ci" is insufficient.  The requirements ask for specific host and target details, along with actual log output before and after the change to demonstrate the improvement or fix.  Just stating "ci" doesn't provide any evidence that the change works as intended.

The submitter needs to significantly expand on all sections to adequately describe the change and its effects.  Without more information, it's impossible to properly review the PR.


update0914

💻 变更类型 | Change Type

[ ] feat
[x] fix
[ ] refactor
[ ] perf
[ ] style
[ ] test
[ ] docs
[ ] ci
[ ] chore
[ ] build

🔀 变更说明 | Description of Change

📝 补充信息 | Additional Information

Summary by CodeRabbit

New Features

Updated sidebar header to display "Walker ChatGPT" with a new subtitle "Welcome to Walker ChatGPT" and a logo.

Branding Updates

Rebranded application title from "NextChat" to "Walker ChatGPT" across various configurations and metadata.
Updated application name and short name in the web manifest to "Walker ChatGPT."

11


The app is crashing on Security & Privacy.

The app crashed as soon as level 3 was completed and when I logged in again and clicked on the security and privacy tab still app is crashing.

Verified this issue on dev app v2.0.0(349)


Feature for opening urls from the Company Detail Page

@fredfalcon @just-ary27

I propose it will be a good feature for the user to be able to open the email app and the company website from the company detail page .

/assign

Nice idea, I suggest you to open it in the browser.


Replace simulator uses of sm.tracer. with sm.tracer?.

sm.tracer may not always be set

when are you thinking that the tracer might not be set in the simulator? If we want to freeze history pane?
Might be nice to always call tracer in fsm, and then let higher js decide whether to show it or not?

See my explanation here: https://github.com/StateSmith/StateSmith/pull/311#discussion_r1625219086


fix(backend-embed): force executable permissions on vendored packages

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#482  👈
#481
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @NathanFlurry and the rest of your teammates on  Graphite


[Switch] Accept children for track

Summary 💡
Switch should accept a prop/children so that additional customization can be passed to the Switch, namely adding labels/text within the Switch track.
Examples 🌈
Something like this would be nice. I don't believe this is possible currently as the switch track span does not accept any children.

Motivation 🔦
Given that we're already allowed to customize the styles of the Switch track, I think it'd be nice to give that extra bit of customization.
Benchmark

https://atlassian.design/components/toggle/examples

Hi you all! I was thinking about how to implement it, but then I thought about going to the Material UI website first to check their switches description and guidelines here
It seems that they recommend not adding texts inside the switch graphics itself, as stated here:

Avoid creating a switch that includes the text “on” and “off” within the graphic itself. The switch alone should be sufficient.

A preceding line tells the corresponding inline label should describe it the best:

The option that the switch controls, as well as the state it’s in, should be made clear from the corresponding inline label.

With that, I think it may not be a good idea to include it in the component library.
Don't get me wrong, please! I would love to help implementing it. But I am trying to contribute here with an analysis comparing to Google Material guidelines.

@renanliberato I don't think that MD discouraging it should be a reason on its own for us to not implement it. Our users are the developers/designers, not the end-users. MD puts a priority on the end-users. So if we get enough traction for this feature request, why not :+1:.

Alright, thank you for clarifying it!

Is there any update on this issue ?

@Kundan28 Would you like to work on it?

@Kundan28 Would you like to work on it?

Actually I don't know how to implement that.

More customization options that would be great to support: https://dribbble.com/shots/10070945-Toggles

@oliviertassinari I'll try implementing the customizable thumb.

@siriwatknp Has managed to pull this off with the ::after and ::before selectors: https://mui-treasury.com/styles/switch/. It's probably good enough.


Where will I get the image to display in the readme file?

The Usage instructions mention to add the following image tag in the profile's readme file:
<img src="https://github.com/<username>/<repository-name>/blob/master/images/codeStats.svg" alt="Alternative Text"/>

Where will I get the image linked in the above tag?

Looks like the author of this github action is not interested in resolving queries or issues. Closing this issue...


Add support for SIGEV_THREAD_ID and sigev_notify_thread_id

Summary
Add support for SIGEV_THREAD_ID and sigev_notify_thread_id.
Impact
SIGEV_THREAD_ID is now supported.
Testing
Functionality was tested using rt-tests/cyclictest, which employs sigev_notify_thread_id to notify a sleeping thread.

Please drop the first one

Please drop the first one