Fix: Fixed the UI and use the ViewModel in Costomization properties page

Description
I've done this before in https://github.com/files-community/Files/pull/11421 and I reverted to avoid adding off-topic changes(although it was accepted change). But here you are again.
Motivation and Context

Fix UI that was created for out-dated window style
Improve readability and maintainability of those codes

Details of change

Update UI to maximize GridView.
Update divider to use Border instead of MenuFlyoutSeparator
Update divider to use DividerStrokeDefaultBrush, which is expected, instead.
Add Commands to the ViewModel.
Remove events in the View.
Remove event handling codes in View's code-behind.

Tasks

[x] Were these changes approved in an issue or discussion with the project maintainers? In order to prevent extra work, feature requests and changes to the codebase must be approved before the pull request will be reviewed. This prevents extra work for the contributors and maintainers.
[x] Did you build the app and test your changes?
[x] Did you check for accessibility? You can use Accessibility Insights for this.
[ ] Did you remove any strings from the en-us resource file?

[ ] Did you search the solution to see if the string is still being used?

[x] Did you implement any design changes to an existing feature?

[x] Was this change approved?

Screenshots
Light

Dark

I've just found a little UI-issue related with properties (it is caused by localization and happens in preview as well). You may inlcude it in this PR.

This was fixed by #11672.

@yaira2 Ready for review.


PATCH: Migrate to poetry

Codecov Report

Merging #41 (e2534f5) into main (16dbd00) will decrease coverage by 0.00%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main      #41      +/-   ##
==========================================
- Coverage   97.89%   97.88%   -0.01%
==========================================
  Files           8        7       -1
  Lines         427      425       -2
==========================================
- Hits          418      416       -2
  Misses          9        9

Impacted Files
Coverage Δ

pynction/__init__.py
100.00% <100.00%> (ø)

pynction/monads/try_monad.py
87.50% <100.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


How to ignore error when compile ?

I cant find such build option that can ignore build error and go on compiling.

Internal Jira reference: https://jira.arm.com/browse/MBOCUSTRIA-167

@zeecy-zhao There is no such option.

@theotherjimmy Perhaps the fundamental question is whether there should be one. What do you think?

What would be the goal of ignoring build errors? If you continued to try and compile the project, what would happen when it got to the end? Linking the project not be possible.
@zeecy-zhao would you mind detailing your use case a bit more? If there was such an option, what would you expect the behavior to be?

@bridadan
just like  "make -k"

   -k, --keep-going

        Continue as much as possible after an error.  While the target that failed, and those that depend on it, cannot be remade, the other dependencies of these targets can be processed all the same.

I guess the use case is to plough on compiling as much as you can to keep the CPU occupied, while you fix the error you saw scrolling past, reducing the development cycle time as there's less remaining to compile after making the fix.
Would be annoying unless errors and progress indications were piped to different streams, or progress updates were reduced to just a bar or something. Or might work well with something like an Eclipse CDT error parser?

@kjbracey-arm
Even working with eclipse cdt, the parser result could be different with command.

Ah thanks for clarifying @zeecy-zhao. Would require some modifications to the toolchain logic in Mbed OS, but might not be too bad. Any thoughts @theotherjimmy?

We could make it happen. I'm not planning on doing it, but I can help provide guidance to anyone that wants to contribute it.

Thank you for raising this issue. Please note we have updated our policies and
now only defects should be raised directly in GitHub. Going forward questions and
enhancements will be considered in our forums, https://forums.mbed.com/ . If this
issue is still relevant please re-raise it there.
This GitHub issue will now be closed.


Add command option to transactions pulled from a specific Wallet ID

Add command option to transactions pulled from a specific Wallet ID. Default will be 1. This should be the STANDARD_WALLET creating when installing the Chia application.

Added in v0.3.0


Add Marmoset Toolbag SDK

SteamDB app page links to a few games using this
https://steamdb.info/app/836860/
https://steamdb.info/app/836870/
https://steamdb.info/app/837100/
https://steamdb.info/app/837110/
Brief explanation of the change
Find Marmoset Toolbag by it's ".mview" file type.

After running changed rules in this pull request (this bot only tests rules.ini changes):
Changed technologies: SDK.Marmoset_Toolbag
These apps now match: (4)<PHONE_NUMBER>70<PHONE_NUMBER>10
Please confirm that all these changed apps are correct.

not used by enough apps


popovers: Show hotkey reminder for sender info popovers only.

Hotkey reminders in user popovers( i.e. @ and R) should be present
only for sender info popovers, hence for user-mention and user-presence
popovers it will show no such reminders.
Fixes: #8313.

Testing Plan:
MANUAL TESTING
GIFs or Screenshots:

Should I also change "Reply to mentioning user" in another commit, as

For user-mentions, it should be "Reply mentioned user".
For user-presence, I find no use for it.

Posted a small comment on the existing changes; otherwise they look great.
For reply-mentioning user, in user-presence, it does do something potentially useful if you have an already open compose box (adding a copy of that user's mention to the compose box).  I've probably used it only once ever, though, so certainly not high-value.  I'm not sure what the right thing to do for the clicking-on-a-mention use case.  Probably something to discuss, but sorta a lower priority issue.  Copying @rishig for his thoughts, but I imagine this will become its own PR, so we should just finish and merge the immediate issue here :)

For clicking a user mention, I think we can just remove the hotkey hints. Unless I'm misunderstanding the question?

The hotkey hints will be removed regardless; the question is whether we keep the item at all.

I chatted with @rishig, and we determined we're happy to keep those items with their text.
So rebased, made the change I suggested, and merged as b17d4e193c983975e0adaf50bb974e5ed3da19e7, thanks @shubhamdhama!


Kyler branch

Here is my fix for the Drift problem, a little tweaking of the UI to work with buttons instead of sliders.,
and added an optional directional arrow.

Please merge this!

Heya, sorry for the REALLY long wait time on this!
I know its helluva ask after all this time, but do you think you can create a squashed commit of just your changes from the last master commit?
Its a bit a pain to try and browse through what's changed when its 400+ files

Hey Benotter,
I don't know exactly how to squash this branch and pull request when I've already pushed it to Github, so I just make a new branch, that has all the same changes, but squashed down into a single commit.
I've made a new pull request, so I think you can just work off of that one, and close this one.


Cannot paste from clipboard in Firefox

Do you want to request a feature or report a bug?
Report a bug.
What is the current behavior?

Copy an image to the clipboard (for example by taking a screenshot).
Go to http://facebook.github.io/draft-js/ in Firefox.
Focus the editor and paste the clipboard contents in the editor.
Result: the console shows an error: "TypeError: appendToHead is undefined". The callback function handlePastedFiles is not called.

What is the expected behavior?
I expected there to be no errors and that I would be able to access the clipboard contents in the handlePastedFiles callback function.
Which versions of Draft.js, and which browser / OS are affected by this issue? Did this work in previous versions of Draft.js?
v0.8.1, Firefox 48.

Fix just landed, and will be out in the next release. Thanks for reporting this issue!


[EMM-1893] Unable to install apps from unknown sources in android work profile

        Tried to push an enterprise android app onto the user device but it prompts "Your administrator doesn't allow installation of apps obtained from unknown sources." even though the device has allowed app installation from unknown sources. The device policy in the android configuration in the emm console has also been set to allow installation from unknown sources.
Reference: https://wso2.org/jira/browse/EMM-1893

Hi,
By default, Unknown sources are automatically blocked in the Work Profile due to security purpose by Android itself. In addition to that EMMs are also encouraged not to surface policy controls to change such default states as well. Therefore in order to adhere with the EMM requirements [1] given by Android for EMM vendors, we have to stick with it.
[1] https://developers.google.com/android/work/requirements/work-profile
(Please refer 2.7 Default security policies.)
Thanks.

Resolving based on the comment.


Make command filtering in zsh completion more robust.

Filter out any lines that don't resemble a command in the help text.

Fixes #1525.

Perfect; thank you! :sparkles:


Align casing on template

One should align casing on categories. Right now we got both database and Database, thus giving us two different categories that probably should be unified.

@danibjor This is now fixed. But I cannot close this issue.


[BugFix] fix bug when exiting process

PR types

Bug fixes
PR changes

Others
Description

fix bug when exiting process

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


jolla-configuration-DEVCOD

Trying to update to 4.2 using OTA:
[defaultuser@XperiaXZ3 ~]$ devel-su zypper in jolla-configuration-h8416
Password:
Loading repository data...
Reading installed packages...
'jolla-configuration-h8416' not found in package names. Trying capabilities.
No provider of 'jolla-configuration-h8416' found.
Resolving package dependencies...

Nothing to do.

Thanks for quick report! Indeed, we switched to official "patterns-" package naming and have to use patterns-sailfish-device-configuration-DEVCODE
README updated.


[Request] Beaker plugin for Lynx browser

A plugin to enable Lynx (CLI web browser) to access Dat sites

@rangermauve made a neat little demo of this idea https://github.com/RangerMauve/dlynx
I'm going to close because I dont think this is something Beaker should do, but if you look at dlynx you can see how to implement something like this


Error installing build dependencies

Hello,
please share the error message what you receive.
/Gabor

I'm getting this error although I've downloaded Microsoft Visual C++ from this link
https://www.scivision.dev/python-windows-visual-c-14-required/
error: Microsoft Visual C++ 14.0 is required. Get it with "Microsoft Visual C++ Build Tools": https://visualstudio.microsoft.com/downloads/

Solved!


best upgrading procedure for brackets on windows 10

Hi
I am running Brackets 1.8 on my Windows 10 machine, a HP z620 workstation and I was prompted by Brackets to upgrade.
My question is simple: Do I uninstall this 1.8 version before installing 1.9 or will 1.9 overwrite the 1.8 install by default and will I run into issues performing the upgrade this way?

Hi @TheMongooseBytes,
you can just run the 1.9. installer: it will overwrite the Brackets files, but you will keep your settings, extensions, history and other related, user specific things. There shouldn't be any issues performing the upgrade whatsoever.

Closing as answered


error in Fuseki environment

here's another error:
[2018-05-16 20:48:23] ParserARQUpdate ERROR Unexpected throwable:
java.lang.NullPointerException: input AttributeSource must not be null
	at java.util.Objects.requireNonNull(Objects.java:228)
	at org.apache.lucene.util.AttributeSource.<init>(AttributeSource.java:84)
	at org.apache.lucene.analysis.TokenStream.<init>(TokenStream.java:105)
	at org.apache.lucene.analysis.TokenFilter.<init>(TokenFilter.java:33)
	at io.bdrc.lucene.zh.PinyinNumberedToMarkedFilter.<init>(PinyinNumberedToMarkedFilter.java:64)
	at io.bdrc.lucene.zh.ChineseAnalyzer.createComponents(ChineseAnalyzer.java:285)

I'm not sure what triggers it...

I think it would be clearer if the exceptions in
https://github.com/BuddhistDigitalResourceCenter/lucene-zh/blob/master/src/main/java/io/bdrc/lucene/zh/ChineseAnalyzer.java
were killing the thing instead of trying to make it a non working zombie

are you refering to the try / catch blocks such as this one?
I guess it is not the errors I throw because the profile doesn't exist…

I'm referring to these indeed. In that case there should be a return null; I think after the e.printStackTrace();, otherwise errors should pile up until it's unclear where the first error was

looks good now


⚠ PrivateHD has degraded performance

In b2bd19b, PrivateHD ($PHD) experienced degraded performance:

HTTP code: 200
Response time: 1548 ms

Resolved: PrivateHD performance has improved in 7bc3f52.


Env.Variables during Build for process.env

** Please describe which feature you have a question about? **
I'm trying to deploy a Gatsby site with auth0.
That requires three variables to be accessible during build in process.env:
domain: process.env.AUTH0_DOMAIN,
clientID: process.env.AUTH0_CLIENTID,
redirectUri: process.env.AUTH0_CALLBACK,
Whichever way I try to pass the variables, I get the same error (if the build succeeds) on pageload:
"Uncaught Error: domain option is required" --> which suggests that the variables weren't present.
** Provide additional details**

tried this syntax "key: value" from here
https://docs.aws.amazon.com/amplify/latest/userguide/build-settings.html
--> didn't work...

added the Env.vars under App Settings and tried this syntax "npm run build:$BUILD_ENV" from here https://docs.aws.amazon.com/amplify/latest/userguide/environment-variables.html
--> Build failed with info that such a command doesn't exist...

tried hardcoding in the Build Settings file (added the "" to offset markdown) --> didn't work...
env:
variables:
"- AUTH0_DOMAIN=$AUTH0_DOMAIN"
"- AUTH0_CLIENTID=$AUTH0_CLIENTID"
"- AUTH0_CALLBACK=$AUTH0_CALLBACK"

linked Env.vars like this in the build settings...
"- $AUTH0_DOMAIN"
"- $AUTH0_CLIENTID"
"- $AUTH0_CALLBACK"
triggered this during build:
2020-06-28T07:40:46.487Z [INFO]: # Retrieving environment cache...
2020-06-28T07:40:46.530Z [INFO]: # Retrieved environment cache
2020-06-28T07:41:10.806Z [INFO]: ## Processing Environment Variables
# Set Environment Variable: 0
2020-06-28T07:41:10.808Z [INFO]: # Set Environment Variable: 1
# Set Environment Variable: 2
--> and resulted in a subsequent warning that '0=WhateverTheVariableValue' is "not a valid identifier"...

After going through about twenty builds, I'd really appreciate a quick hint as to where I'm making a mistake??

Hi @NicolasMegow,
Thanks for reporting. I will take a look and get back to you. Can you give the appId and region ?

Hi @abhi7cr ,
sure: us-east-2 and d293hfauc7dro7.
Thanks!

Hi @NicolasMegow,
The env variables should be added in process.env. I just tested adding some variables in the env section as follows:
version: 1
env:
  variables:
      TEST_A: componentA
      TEST_B: componentB
      TEST_C: componentC

I am not sure if you are using webpack, but for my project, I am using it. I had to use the EnviromentPlugin to define these env variables in order for webpack to string-substitute these values during build time.
webpack.config.js
 plugins: [
      new webpack.EnvironmentPlugin({
       TEST_A: null,
       TEST_B: null,
       TEST_C: null
      })
  ]

To test this, I console logged the above variables during runtime:
    console.log('A', process.env.TEST_A)
    console.log('B', process.env.TEST_B)
    console.log('C', process.env.TEST_C)

output from the inspect window:
tes.js:7 A componentA
test.js:8 B componentB
test.js:9 C componentC

Dear @abhi7cr,
thanks a lot for looking into this!
Gatsby is using webpack (https://www.gatsbyjs.org/docs/add-custom-webpack-config/).
I've found away to work around env.vars in this case - but I'll definitely come to back to this as I expect to soon need it again :)
The EnvironmentPlugin and console.log would make good additions to the docs.
Really appreciate your quick and thorough help! Thanks!
Nicolas


Swarm mode scaling to 1 replica doesn't route traffic correctly.

Description
I am trying to use Docker Swarm Mode (all nodes running 17.03-ce, Ubuntu 14.04). I have 2 nodes: 1 Manager, 1 worker. I ran ufw disable on both nodes, so firewall shouldn't be an issue.
When creating services via the docker service create command, the nodes balance traffic correctly when I set the replica to something more than 1. However, when I scale the service back down to 1, the nodes that do not have containers running do not route traffic to the node running the 1 container properly.
According to the docs, swarm mode should be using an ingress network that will automatically route traffic even if a node is not running any containers.
I have included the output on both nodes of various commands. In the output below the traffic is able to reach the worker node, but not the manager node. I find this weird because it looks like the manager node is listening on port 80, but its not being redirected.
Steps to reproduce the issue:

docker network create --driver=overlay sample
docker service create --name hello --network sample --publish 80:80 --replicas 2 dockercloud/hello-world
Traffic works fine on 2 nodes.
docker service scale hello=1
Traffic is only able to receive from the node running the container on the specified port.

Describe the results you received:
Traffic does not route properly after service has been scaled to 1.
Describe the results you expected:
Traffic to be routed properly after being scaled to 1.

   23 minutes ago      Up 23 minutes       80/tcp              hello.1.ycy2c4637ed0cuxqsh75wda17

Thanks @xylomo for the report.
Can you please attach the daemon logs, if you still have them. Thanks

Sorry, my organization won't allow me to post the logs because of the IPs and hostnames that are located in there.
Is there something in particular that you are looking for? I can see it setting up the network on the worker:
time="2017-03-13T13:03:16.205007345-04:00" level=debug msg="Creating service for vip <IP_ADDRESS> fwMark 256 ingressPorts []*libnetwork.PortConfig{&libnetwork.PortConfig{Name: \"\",\nProtocol: 0,\nTargetPort: 0x50,\nPublishedPort: 0x50,\n}} in sbox ingress (ingress)"
INFO[0000] Firewalld running: false
time="2017-03-13T13:03:16.277853915-04:00" level=debug msg="Programming external connectivity on endpoint gateway_ingress-sbox (fccd07e9264a79d7a4cb1542b755512235a0f0d62a7f6b40b4fda40beab7ce7b)"

Do you see any obvious error/warnings in the daemon logs when scaling down the service?
You can replace any sensible info from the logs, before posting it.

Okay, I am tailing the log file when I make a request to the node that does not have any running containers. This is the output:
time="2017-03-13T13:19:26.130764916-04:00" level=debug msg="Miss notification, l2 mac 02:42:0a:ff:00:03"
time="2017-03-13T13:19:26.767732055-04:00" level=debug msg="memberlist: Initiating push/pull sync with: <manager-ip>:7946"
time="2017-03-13T13:19:31.137987392-04:00" level=debug msg="Miss notification, l2 mac 02:42:0a:ff:00:05"
time="2017-03-13T13:19:45.165270082-04:00" level=debug msg="<worker>-cf41a0ccc591: Initiating bulk sync with nodes [<manager>-2220d2691ba1]"
time="2017-03-13T13:19:45.165360269-04:00" level=debug msg="<worker>-cf41a0ccc591: Initiating unsolicited bulk sync for networks [omgayyn9454kewjjc2twxs0aq] with node <manager>-2220d2691ba1"
time="2017-03-13T13:19:45.167381628-04:00" level=debug msg="memberlist: TCP connection from=<manager-ip>:36060"
time="2017-03-13T13:19:45.167803585-04:00" level=debug msg="<worker>-cf41a0ccc591: Bulk sync to node <manager>-2220d2691ba1 took 1.412808ms"
time="2017-03-13T13:19:46.262955572-04:00" level=debug msg="memberlist: TCP connection from=<manager-ip>:36062"

Thanks.
If you can find them, I would like to see the logs printed as a result of the docker service scale <name>=1

Sure, here you go:
time="2017-03-13T13:28:38.950894543-04:00" level=debug msg="Calling GET /_ping"
time="2017-03-13T13:28:38.951615983-04:00" level=debug msg="Calling GET /v1.26/services/hello"
time="2017-03-13T13:28:38.954599508-04:00" level=debug msg="Calling POST /v1.26/services/wc9jggth8ryx6usn7jls4k5oe/update?version=447"
time="2017-03-13T13:28:38.954791649-04:00" level=debug msg="form data: {\"EndpointSpec\":{\"Mode\":\"vip\",\"Ports\":[{\"Protocol\":\"tcp\",\"PublishMode\":\"ingress\",\"PublishedPort\":80,\"TargetPort\":80}]},\"Mode\":{\"Replicated\":{\"Replicas\":1}},\"Name\":\"hello\",\"Networks\":[{\"Target\":\"hello\"}],\"TaskTemplate\":{\"ContainerSpec\":{\"DNSConfig\":{},\"Image\":\"dockercloud/hello-world:latest@sha256:629d6815beea1ec5172ce4b56ffa0e2c3fbe288a2e5abda3076aed08ee154e72\"},\"ForceUpdate\":0,\"Networks\":[{\"Target\":\"5y80givk6kjpirdpn40bgfgzg\"}],\"Placement\":{},\"Resources\":{\"Limits\":{},\"Reservations\":{}},\"RestartPolicy\":{\"Condition\":\"any\",\"MaxAttempts\":0}},\"UpdateConfig\":{\"FailureAction\":\"pause\",\"MaxFailureRatio\":0,\"Parallelism\":1}}"
time="2017-03-13T13:28:38.955588789-04:00" level=debug msg="updating service using supplied digest reference dockercloud/hello-world:latest@sha256:629d6815beea1ec5172ce4b56ffa0e2c3fbe288a2e5abda3076aed08ee154e72"
time="2017-03-13T13:28:38.958969591-04:00" level=debug msg="Service wc9jggth8ryx6usn7jls4k5oe was scaled down from 2 to 1 instances"
time="2017-03-13T13:28:38.961783348-04:00" level=debug msg="ReleaseAddress(GlobalDefault/<IP_ADDRESS>/16, <IP_ADDRESS>)"
time="2017-03-13T13:28:38.961983763-04:00" level=debug msg="ReleaseAddress(GlobalDefault/<IP_ADDRESS>/24, <IP_ADDRESS>)"
time="2017-03-13T13:28:39.066244632-04:00" level=warning msg="cannot find target task in store" method="(*Dispatcher).UpdateTaskStatus" node.id=wo61ouqdawc7eti9kvitedk8t node.session=075c75xc4eky0laedpacwdss4 task.id=sa76vcfh27v6a3n5fttu9avgs
time="2017-03-13T13:28:39.104673874-04:00" level=error msg="task unavailable" method="(*Dispatcher).processUpdates" module=dispatcher task.id=sa76vcfh27v6a3n5fttu9avgs
time="2017-03-13T13:28:39.366032947-04:00" level=debug msg="miss notification for dest IP, <IP_ADDRESS>"
time="2017-03-13T13:28:39.366036766-04:00" level=debug msg="checkEncryption(5y80giv, <worker-ip>, 0, false)"
time="2017-03-13T13:28:39.566390352-04:00" level=debug msg="miss notification for dest IP, <IP_ADDRESS>"
time="2017-03-13T13:28:39.566395594-04:00" level=debug msg="checkEncryption(omgayyn, <worker-ip>, 0, false)"
time="2017-03-13T13:28:45.165860349-04:00" level=debug msg="memberlist: TCP connection from=<worker-ip>:19592"
time="2017-03-13T13:28:45.166195090-04:00" level=debug msg="<manager>-2220d2691ba1: Initiating  bulk sync for networks [omgayyn9454kewjjc2twxs0aq] with node <worker>-cf41a0ccc591"
time="2017-03-13T13:28:46.297719990-04:00" level=debug msg="memberlist: Initiating push/pull sync with: <worker-ip>:7946"
time="2017-03-13T13:28:52.998287861-04:00" level=debug msg="<manager>-2220d2691ba1: Initiating bulk sync with nodes [<worker>-cf41a0ccc591]"
time="2017-03-13T13:28:52.998360869-04:00" level=debug msg="<manager>-2220d2691ba1: Initiating unsolicited bulk sync for networks [omgayyn9454kewjjc2twxs0aq] with node <worker>-cf41a0ccc591"

I cannot see anything wrong from the logs, neither I can reproduce.
We need to do more debugging, check if the tx or rx path is broken.
Can you see if the request that fails reaches the container on the other node ?
You can capture on each host with, when you run the request you know will fail:
 sudo tcpdump -n -v -i any 'port 4789 or port 80'

then please replace the host IP in the capture with worker-IP and manager-IP for example, and attach it here.
Thanks.

Worker:
tcpdump: listening on any, link-type LINUX_SLL (Linux cooked), capture size 65535 bytes
14:18:38.076279 IP (tos 0x20, ttl 122, id 7687, offset 0, flags [DF], proto TCP (6), length 52)
    <client-IP>.65371 > <manager-IP>.80: Flags [S], cksum 0x370f (correct), seq<PHONE_NUMBER>, win 8192, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
14:18:38.076312 IP (tos 0x20, ttl 121, id 7687, offset 0, flags [DF], proto TCP (6), length 52)
    <client-IP>.65371 > <IP_ADDRESS>.80: Flags [S], cksum 0xdb41 (correct), seq<PHONE_NUMBER>, win 8192, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
14:18:38.076316 IP (tos 0x20, ttl 121, id 7687, offset 0, flags [DF], proto TCP (6), length 52)
    <client-IP>.65371 > <IP_ADDRESS>.80: Flags [S], cksum 0xdb41 (correct), seq<PHONE_NUMBER>, win 8192, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
14:18:38.076362 IP (tos 0x0, ttl 64, id 31241, offset 0, flags [none], proto UDP (17), length 102)
    <manager-IP>.57844 > <manager-IP>.4789: VXLAN, flags [I] (0x08), vni 4096
IP (tos 0x20, ttl 121, id 7687, offset 0, flags [DF], proto TCP (6), length 52)
    <IP_ADDRESS>.65371 > <IP_ADDRESS>.80: Flags [S], cksum 0x9174 (correct), seq<PHONE_NUMBER>, win 8192, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
14:18:38.329479 IP (tos 0x20, ttl 122, id 7688, offset 0, flags [DF], proto TCP (6), length 52)
    <client-IP>.65372 > <manager-IP>.80: Flags [S], cksum 0x2536 (correct), seq<PHONE_NUMBER>, win 8192, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
14:18:38.329518 IP (tos 0x20, ttl 121, id 7688, offset 0, flags [DF], proto TCP (6), length 52)
    <client-IP>.65372 > <IP_ADDRESS>.80: Flags [S], cksum 0xc968 (correct), seq<PHONE_NUMBER>, win 8192, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
14:18:38.329523 IP (tos 0x20, ttl 121, id 7688, offset 0, flags [DF], proto TCP (6), length 52)
    <client-IP>.65372 > <IP_ADDRESS>.80: Flags [S], cksum 0xc968 (correct), seq<PHONE_NUMBER>, win 8192, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
14:18:38.329573 IP (tos 0x0, ttl 64, id 31292, offset 0, flags [none], proto UDP (17), length 102)
    <manager-IP>.57296 > <manager-IP>.4789: VXLAN, flags [I] (0x08), vni 4096
IP (tos 0x20, ttl 121, id 7688, offset 0, flags [DF], proto TCP (6), length 52)
    <IP_ADDRESS>.65372 > <IP_ADDRESS>.80: Flags [S], cksum 0x7f9b (correct), seq<PHONE_NUMBER>, win 8192, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
14:18:44.078142 IP (tos 0x20, ttl 122, id 7690, offset 0, flags [DF], proto TCP (6), length 48)
    <client-IP>.65371 > <manager-IP>.80: Flags [S], cksum 0x4b1e (correct), seq<PHONE_NUMBER>, win 8192, options [mss 1460,nop,nop,sackOK], length 0
14:18:44.078189 IP (tos 0x20, ttl 121, id 7690, offset 0, flags [DF], proto TCP (6), length 48)
    <client-IP>.65371 > <IP_ADDRESS>.80: Flags [S], cksum 0xef50 (correct), seq<PHONE_NUMBER>, win 8192, options [mss 1460,nop,nop,sackOK], length 0
14:18:44.078196 IP (tos 0x20, ttl 121, id 7690, offset 0, flags [DF], proto TCP (6), length 48)
    <client-IP>.65371 > <IP_ADDRESS>.80: Flags [S], cksum 0xef50 (correct), seq<PHONE_NUMBER>, win 8192, options [mss 1460,nop,nop,sackOK], length 0
14:18:44.078265 IP (tos 0x0, ttl 64, id 32123, offset 0, flags [none], proto UDP (17), length 98)
    <manager-IP>.57844 > <manager-IP>.4789: VXLAN, flags [I] (0x08), vni 4096
IP (tos 0x20, ttl 121, id 7690, offset 0, flags [DF], proto TCP (6), length 48)
    <IP_ADDRESS>.65371 > <IP_ADDRESS>.80: Flags [S], cksum 0xa583 (correct), seq<PHONE_NUMBER>, win 8192, options [mss 1460,nop,nop,sackOK], length 0
14:18:44.330562 IP (tos 0x20, ttl 122, id 7691, offset 0, flags [DF], proto TCP (6), length 48)
    <client-IP>.65372 > <manager-IP>.80: Flags [S], cksum 0x3945 (correct), seq<PHONE_NUMBER>, win 8192, options [mss 1460,nop,nop,sackOK], length 0
14:18:44.330602 IP (tos 0x20, ttl 121, id 7691, offset 0, flags [DF], proto TCP (6), length 48)
    <client-IP>.65372 > <IP_ADDRESS>.80: Flags [S], cksum 0xdd77 (correct), seq<PHONE_NUMBER>, win 8192, options [mss 1460,nop,nop,sackOK], length 0
14:18:44.330607 IP (tos 0x20, ttl 121, id 7691, offset 0, flags [DF], proto TCP (6), length 48)
    <client-IP>.65372 > <IP_ADDRESS>.80: Flags [S], cksum 0xdd77 (correct), seq<PHONE_NUMBER>, win 8192, options [mss 1460,nop,nop,sackOK], length 0
14:18:44.330658 IP (tos 0x0, ttl 64, id 32145, offset 0, flags [none], proto UDP (17), length 98)
    <manager-IP>.57296 > <manager-IP>.4789: VXLAN, flags [I] (0x08), vni 4096
IP (tos 0x20, ttl 121, id 7691, offset 0, flags [DF], proto TCP (6), length 48)
    <IP_ADDRESS>.65372 > <IP_ADDRESS>.80: Flags [S], cksum 0x93aa (correct), seq<PHONE_NUMBER>, win 8192, options [mss 1460,nop,nop,sackOK], length 0
14:18:56.528436 IP (tos 0x20, ttl 122, id 7693, offset 0, flags [DF], proto TCP (6), length 52)
    <client-IP>.65373 > <manager-IP>.80: Flags [S], cksum 0x9d76 (correct), seq<PHONE_NUMBER>, win 8192, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
14:18:56.528482 IP (tos 0x20, ttl 121, id 7693, offset 0, flags [DF], proto TCP (6), length 52)
    <client-IP>.65373 > <IP_ADDRESS>.80: Flags [S], cksum 0x41a9 (correct), seq<PHONE_NUMBER>, win 8192, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
14:18:56.528487 IP (tos 0x20, ttl 121, id 7693, offset 0, flags [DF], proto TCP (6), length 52)
    <client-IP>.65373 > <IP_ADDRESS>.80: Flags [S], cksum 0x41a9 (correct), seq<PHONE_NUMBER>, win 8192, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
14:18:56.528546 IP (tos 0x0, ttl 64, id 33878, offset 0, flags [none], proto UDP (17), length 102)
    <manager-IP>.47764 > <manager-IP>.4789: VXLAN, flags [I] (0x08), vni 4096
IP (tos 0x20, ttl 121, id 7693, offset 0, flags [DF], proto TCP (6), length 52)
    <IP_ADDRESS>.65373 > <IP_ADDRESS>.80: Flags [S], cksum 0xf7db (correct), seq<PHONE_NUMBER>, win 8192, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
14:18:56.779793 IP (tos 0x20, ttl 122, id 7694, offset 0, flags [DF], proto TCP (6), length 52)
    <client-IP>.65374 > <manager-IP>.80: Flags [S], cksum 0x778b (correct), seq<PHONE_NUMBER>, win 8192, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
14:18:56.779840 IP (tos 0x20, ttl 121, id 7694, offset 0, flags [DF], proto TCP (6), length 52)
    <client-IP>.65374 > <IP_ADDRESS>.80: Flags [S], cksum 0x1bbe (correct), seq<PHONE_NUMBER>, win 8192, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
14:18:56.779845 IP (tos 0x20, ttl 121, id 7694, offset 0, flags [DF], proto TCP (6), length 52)
    <client-IP>.65374 > <IP_ADDRESS>.80: Flags [S], cksum 0x1bbe (correct), seq<PHONE_NUMBER>, win 8192, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
14:18:56.779926 IP (tos 0x0, ttl 64, id 33934, offset 0, flags [none], proto UDP (17), length 102)
    <manager-IP>.34748 > <manager-IP>.4789: VXLAN, flags [I] (0x08), vni 4096
IP (tos 0x20, ttl 121, id 7694, offset 0, flags [DF], proto TCP (6), length 52)
    <IP_ADDRESS>.65374 > <IP_ADDRESS>.80: Flags [S], cksum 0xd1f0 (correct), seq<PHONE_NUMBER>, win 8192, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
14:18:59.543987 IP (tos 0x20, ttl 122, id 7696, offset 0, flags [DF], proto TCP (6), length 52)
    <client-IP>.65373 > <manager-IP>.80: Flags [S], cksum 0x9d76 (correct), seq<PHONE_NUMBER>, win 8192, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
14:18:59.544021 IP (tos 0x20, ttl 121, id 7696, offset 0, flags [DF], proto TCP (6), length 52)
    <client-IP>.65373 > <IP_ADDRESS>.80: Flags [S], cksum 0x41a9 (correct), seq<PHONE_NUMBER>, win 8192, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
14:18:59.544025 IP (tos 0x20, ttl 121, id 7696, offset 0, flags [DF], proto TCP (6), length 52)
    <client-IP>.65373 > <IP_ADDRESS>.80: Flags [S], cksum 0x41a9 (correct), seq<PHONE_NUMBER>, win 8192, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
14:18:59.544070 IP (tos 0x0, ttl 64, id 34297, offset 0, flags [none], proto UDP (17), length 102)
    <manager-IP>.47764 > <manager-IP>.4789: VXLAN, flags [I] (0x08), vni 4096
IP (tos 0x20, ttl 121, id 7696, offset 0, flags [DF], proto TCP (6), length 52)
    <IP_ADDRESS>.65373 > <IP_ADDRESS>.80: Flags [S], cksum 0xf7db (correct), seq<PHONE_NUMBER>, win 8192, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
14:18:59.792995 IP (tos 0x20, ttl 122, id 7697, offset 0, flags [DF], proto TCP (6), length 52)
    <client-IP>.65374 > <manager-IP>.80: Flags [S], cksum 0x778b (correct), seq<PHONE_NUMBER>, win 8192, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
14:18:59.793034 IP (tos 0x20, ttl 121, id 7697, offset 0, flags [DF], proto TCP (6), length 52)
    <client-IP>.65374 > <IP_ADDRESS>.80: Flags [S], cksum 0x1bbe (correct), seq<PHONE_NUMBER>, win 8192, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
14:18:59.793039 IP (tos 0x20, ttl 121, id 7697, offset 0, flags [DF], proto TCP (6), length 52)
    <client-IP>.65374 > <IP_ADDRESS>.80: Flags [S], cksum 0x1bbe (correct), seq<PHONE_NUMBER>, win 8192, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
14:18:59.793100 IP (tos 0x0, ttl 64, id 34329, offset 0, flags [none], proto UDP (17), length 102)
    <manager-IP>.34748 > <manager-IP>.4789: VXLAN, flags [I] (0x08), vni 4096
IP (tos 0x20, ttl 121, id 7697, offset 0, flags [DF], proto TCP (6), length 52)
    <IP_ADDRESS>.65374 > <IP_ADDRESS>.80: Flags [S], cksum 0xd1f0 (correct), seq<PHONE_NUMBER>, win 8192, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
14:19:05.561264 IP (tos 0x20, ttl 122, id 7699, offset 0, flags [DF], proto TCP (6), length 48)
    <client-IP>.65373 > <manager-IP>.80: Flags [S], cksum 0xb185 (correct), seq<PHONE_NUMBER>, win 8192, options [mss 1460,nop,nop,sackOK], length 0
14:19:05.561311 IP (tos 0x20, ttl 121, id 7699, offset 0, flags [DF], proto TCP (6), length 48)
    <client-IP>.65373 > <IP_ADDRESS>.80: Flags [S], cksum 0x55b8 (correct), seq<PHONE_NUMBER>, win 8192, options [mss 1460,nop,nop,sackOK], length 0
14:19:05.561318 IP (tos 0x20, ttl 121, id 7699, offset 0, flags [DF], proto TCP (6), length 48)
    <client-IP>.65373 > <IP_ADDRESS>.80: Flags [S], cksum 0x55b8 (correct), seq<PHONE_NUMBER>, win 8192, options [mss 1460,nop,nop,sackOK], length 0
14:19:05.561391 IP (tos 0x0, ttl 64, id 35051, offset 0, flags [none], proto UDP (17), length 98)
    <manager-IP>.47764 > <manager-IP>.4789: VXLAN, flags [I] (0x08), vni 4096
IP (tos 0x20, ttl 121, id 7699, offset 0, flags [DF], proto TCP (6), length 48)
    <IP_ADDRESS>.65373 > <IP_ADDRESS>.80: Flags [S], cksum 0x0beb (correct), seq<PHONE_NUMBER>, win 8192, options [mss 1460,nop,nop,sackOK], length 0
14:19:05.793511 IP (tos 0x20, ttl 122, id 7700, offset 0, flags [DF], proto TCP (6), length 48)
    <client-IP>.65374 > <manager-IP>.80: Flags [S], cksum 0x8b9a (correct), seq<PHONE_NUMBER>, win 8192, options [mss 1460,nop,nop,sackOK], length 0
14:19:05.793547 IP (tos 0x20, ttl 121, id 7700, offset 0, flags [DF], proto TCP (6), length 48)
    <client-IP>.65374 > <IP_ADDRESS>.80: Flags [S], cksum 0x2fcd (correct), seq<PHONE_NUMBER>, win 8192, options [mss 1460,nop,nop,sackOK], length 0
14:19:05.793552 IP (tos 0x20, ttl 121, id 7700, offset 0, flags [DF], proto TCP (6), length 48)
    <client-IP>.65374 > <IP_ADDRESS>.80: Flags [S], cksum 0x2fcd (correct), seq<PHONE_NUMBER>, win 8192, options [mss 1460,nop,nop,sackOK], length 0
14:19:05.793602 IP (tos 0x0, ttl 64, id 35083, offset 0, flags [none], proto UDP (17), length 98)
    <manager-IP>.34748 > <manager-IP>.4789: VXLAN, flags [I] (0x08), vni 4096
IP (tos 0x20, ttl 121, id 7700, offset 0, flags [DF], proto TCP (6), length 48)
    <IP_ADDRESS>.65374 > <IP_ADDRESS>.80: Flags [S], cksum 0xe5ff (correct), seq<PHONE_NUMBER>, win 8192, options [mss 1460,nop,nop,sackOK], length 0
^C
40 packets captured
48 packets received by filter
0 packets dropped by kernel

Manager didn't capture anything:
tcpdump: listening on any, link-type LINUX_SLL (Linux cooked), capture size 65535 bytes
^C
0 packets captured
0 packets received by filter
0 packets dropped by kernel

Can you please double check your string substitutions ?
On the Worker reported capture I see:
<manager-IP>.57844 > <manager-IP>.4789: VXLAN, flags [I] (0x08), vni 4096

Whoops, sorry:
tcpdump: listening on any, link-type LINUX_SLL (Linux cooked), capture size 65535 bytes
14:18:38.076279 IP (tos 0x20, ttl 122, id 7687, offset 0, flags [DF], proto TCP (6), length 52)
    <client-IP>.65371 > <worker-IP>.80: Flags [S], cksum 0x370f (correct), seq<PHONE_NUMBER>, win 8192, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
14:18:38.076312 IP (tos 0x20, ttl 121, id 7687, offset 0, flags [DF], proto TCP (6), length 52)
    <client-IP>.65371 > <IP_ADDRESS>.80: Flags [S], cksum 0xdb41 (correct), seq<PHONE_NUMBER>, win 8192, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
14:18:38.076316 IP (tos 0x20, ttl 121, id 7687, offset 0, flags [DF], proto TCP (6), length 52)
    <client-IP>.65371 > <IP_ADDRESS>.80: Flags [S], cksum 0xdb41 (correct), seq<PHONE_NUMBER>, win 8192, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
14:18:38.076362 IP (tos 0x0, ttl 64, id 31241, offset 0, flags [none], proto UDP (17), length 102)
    <worker-IP>.57844 > <manager-IP>.4789: VXLAN, flags [I] (0x08), vni 4096
IP (tos 0x20, ttl 121, id 7687, offset 0, flags [DF], proto TCP (6), length 52)
    <IP_ADDRESS>.65371 > <IP_ADDRESS>.80: Flags [S], cksum 0x9174 (correct), seq<PHONE_NUMBER>, win 8192, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
14:18:38.329479 IP (tos 0x20, ttl 122, id 7688, offset 0, flags [DF], proto TCP (6), length 52)
    <client-IP>.65372 > <worker-IP>.80: Flags [S], cksum 0x2536 (correct), seq<PHONE_NUMBER>, win 8192, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
14:18:38.329518 IP (tos 0x20, ttl 121, id 7688, offset 0, flags [DF], proto TCP (6), length 52)
    <client-IP>.65372 > <IP_ADDRESS>.80: Flags [S], cksum 0xc968 (correct), seq<PHONE_NUMBER>, win 8192, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
14:18:38.329523 IP (tos 0x20, ttl 121, id 7688, offset 0, flags [DF], proto TCP (6), length 52)
    <client-IP>.65372 > <IP_ADDRESS>.80: Flags [S], cksum 0xc968 (correct), seq<PHONE_NUMBER>, win 8192, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
14:18:38.329573 IP (tos 0x0, ttl 64, id 31292, offset 0, flags [none], proto UDP (17), length 102)
    <worker-IP>.57296 > <manager-IP>.4789: VXLAN, flags [I] (0x08), vni 4096
IP (tos 0x20, ttl 121, id 7688, offset 0, flags [DF], proto TCP (6), length 52)
    <IP_ADDRESS>.65372 > <IP_ADDRESS>.80: Flags [S], cksum 0x7f9b (correct), seq<PHONE_NUMBER>, win 8192, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
14:18:44.078142 IP (tos 0x20, ttl 122, id 7690, offset 0, flags [DF], proto TCP (6), length 48)
    <client-IP>.65371 > <worker-IP>.80: Flags [S], cksum 0x4b1e (correct), seq<PHONE_NUMBER>, win 8192, options [mss 1460,nop,nop,sackOK], length 0
14:18:44.078189 IP (tos 0x20, ttl 121, id 7690, offset 0, flags [DF], proto TCP (6), length 48)
    <client-IP>.65371 > <IP_ADDRESS>.80: Flags [S], cksum 0xef50 (correct), seq<PHONE_NUMBER>, win 8192, options [mss 1460,nop,nop,sackOK], length 0
14:18:44.078196 IP (tos 0x20, ttl 121, id 7690, offset 0, flags [DF], proto TCP (6), length 48)
    <client-IP>.65371 > <IP_ADDRESS>.80: Flags [S], cksum 0xef50 (correct), seq<PHONE_NUMBER>, win 8192, options [mss 1460,nop,nop,sackOK], length 0
14:18:44.078265 IP (tos 0x0, ttl 64, id 32123, offset 0, flags [none], proto UDP (17), length 98)
    <worker-IP>.57844 > <manager-IP>.4789: VXLAN, flags [I] (0x08), vni 4096
IP (tos 0x20, ttl 121, id 7690, offset 0, flags [DF], proto TCP (6), length 48)
    <IP_ADDRESS>.65371 > <IP_ADDRESS>.80: Flags [S], cksum 0xa583 (correct), seq<PHONE_NUMBER>, win 8192, options [mss 1460,nop,nop,sackOK], length 0
14:18:44.330562 IP (tos 0x20, ttl 122, id 7691, offset 0, flags [DF], proto TCP (6), length 48)
    <client-IP>.65372 > <worker-IP>.80: Flags [S], cksum 0x3945 (correct), seq<PHONE_NUMBER>, win 8192, options [mss 1460,nop,nop,sackOK], length 0
14:18:44.330602 IP (tos 0x20, ttl 121, id 7691, offset 0, flags [DF], proto TCP (6), length 48)
    <client-IP>.65372 > <IP_ADDRESS>.80: Flags [S], cksum 0xdd77 (correct), seq<PHONE_NUMBER>, win 8192, options [mss 1460,nop,nop,sackOK], length 0
14:18:44.330607 IP (tos 0x20, ttl 121, id 7691, offset 0, flags [DF], proto TCP (6), length 48)
    <client-IP>.65372 > <IP_ADDRESS>.80: Flags [S], cksum 0xdd77 (correct), seq<PHONE_NUMBER>, win 8192, options [mss 1460,nop,nop,sackOK], length 0
14:18:44.330658 IP (tos 0x0, ttl 64, id 32145, offset 0, flags [none], proto UDP (17), length 98)
    <worker-IP>.57296 > <manager-IP>.4789: VXLAN, flags [I] (0x08), vni 4096
IP (tos 0x20, ttl 121, id 7691, offset 0, flags [DF], proto TCP (6), length 48)
    <IP_ADDRESS>.65372 > <IP_ADDRESS>.80: Flags [S], cksum 0x93aa (correct), seq<PHONE_NUMBER>, win 8192, options [mss 1460,nop,nop,sackOK], length 0
14:18:56.528436 IP (tos 0x20, ttl 122, id 7693, offset 0, flags [DF], proto TCP (6), length 52)
    <client-IP>.65373 > <worker-IP>.80: Flags [S], cksum 0x9d76 (correct), seq<PHONE_NUMBER>, win 8192, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
14:18:56.528482 IP (tos 0x20, ttl 121, id 7693, offset 0, flags [DF], proto TCP (6), length 52)
    <client-IP>.65373 > <IP_ADDRESS>.80: Flags [S], cksum 0x41a9 (correct), seq<PHONE_NUMBER>, win 8192, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
14:18:56.528487 IP (tos 0x20, ttl 121, id 7693, offset 0, flags [DF], proto TCP (6), length 52)
    <client-IP>.65373 > <IP_ADDRESS>.80: Flags [S], cksum 0x41a9 (correct), seq<PHONE_NUMBER>, win 8192, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
14:18:56.528546 IP (tos 0x0, ttl 64, id 33878, offset 0, flags [none], proto UDP (17), length 102)
    <worker-IP>.47764 > <manager-IP>.4789: VXLAN, flags [I] (0x08), vni 4096
IP (tos 0x20, ttl 121, id 7693, offset 0, flags [DF], proto TCP (6), length 52)
    <IP_ADDRESS>.65373 > <IP_ADDRESS>.80: Flags [S], cksum 0xf7db (correct), seq<PHONE_NUMBER>, win 8192, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
14:18:56.779793 IP (tos 0x20, ttl 122, id 7694, offset 0, flags [DF], proto TCP (6), length 52)
    <client-IP>.65374 > <worker-IP>.80: Flags [S], cksum 0x778b (correct), seq<PHONE_NUMBER>, win 8192, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
14:18:56.779840 IP (tos 0x20, ttl 121, id 7694, offset 0, flags [DF], proto TCP (6), length 52)
    <client-IP>.65374 > <IP_ADDRESS>.80: Flags [S], cksum 0x1bbe (correct), seq<PHONE_NUMBER>, win 8192, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
14:18:56.779845 IP (tos 0x20, ttl 121, id 7694, offset 0, flags [DF], proto TCP (6), length 52)
    <client-IP>.65374 > <IP_ADDRESS>.80: Flags [S], cksum 0x1bbe (correct), seq<PHONE_NUMBER>, win 8192, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
14:18:56.779926 IP (tos 0x0, ttl 64, id 33934, offset 0, flags [none], proto UDP (17), length 102)
    <worker-IP>.34748 > <manager-IP>.4789: VXLAN, flags [I] (0x08), vni 4096
IP (tos 0x20, ttl 121, id 7694, offset 0, flags [DF], proto TCP (6), length 52)
    <IP_ADDRESS>.65374 > <IP_ADDRESS>.80: Flags [S], cksum 0xd1f0 (correct), seq<PHONE_NUMBER>, win 8192, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
14:18:59.543987 IP (tos 0x20, ttl 122, id 7696, offset 0, flags [DF], proto TCP (6), length 52)
    <client-IP>.65373 > <worker-IP>.80: Flags [S], cksum 0x9d76 (correct), seq<PHONE_NUMBER>, win 8192, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
14:18:59.544021 IP (tos 0x20, ttl 121, id 7696, offset 0, flags [DF], proto TCP (6), length 52)
    <client-IP>.65373 > <IP_ADDRESS>.80: Flags [S], cksum 0x41a9 (correct), seq<PHONE_NUMBER>, win 8192, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
14:18:59.544025 IP (tos 0x20, ttl 121, id 7696, offset 0, flags [DF], proto TCP (6), length 52)
    <client-IP>.65373 > <IP_ADDRESS>.80: Flags [S], cksum 0x41a9 (correct), seq<PHONE_NUMBER>, win 8192, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
14:18:59.544070 IP (tos 0x0, ttl 64, id 34297, offset 0, flags [none], proto UDP (17), length 102)
    <worker-IP>.47764 > <manager-IP>.4789: VXLAN, flags [I] (0x08), vni 4096
IP (tos 0x20, ttl 121, id 7696, offset 0, flags [DF], proto TCP (6), length 52)
    <IP_ADDRESS>.65373 > <IP_ADDRESS>.80: Flags [S], cksum 0xf7db (correct), seq<PHONE_NUMBER>, win 8192, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
14:18:59.792995 IP (tos 0x20, ttl 122, id 7697, offset 0, flags [DF], proto TCP (6), length 52)
    <client-IP>.65374 > <worker-IP>.80: Flags [S], cksum 0x778b (correct), seq<PHONE_NUMBER>, win 8192, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
14:18:59.793034 IP (tos 0x20, ttl 121, id 7697, offset 0, flags [DF], proto TCP (6), length 52)
    <client-IP>.65374 > <IP_ADDRESS>.80: Flags [S], cksum 0x1bbe (correct), seq<PHONE_NUMBER>, win 8192, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
14:18:59.793039 IP (tos 0x20, ttl 121, id 7697, offset 0, flags [DF], proto TCP (6), length 52)
    <client-IP>.65374 > <IP_ADDRESS>.80: Flags [S], cksum 0x1bbe (correct), seq<PHONE_NUMBER>, win 8192, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
14:18:59.793100 IP (tos 0x0, ttl 64, id 34329, offset 0, flags [none], proto UDP (17), length 102)
    <worker-IP>.34748 > <manager-IP>.4789: VXLAN, flags [I] (0x08), vni 4096
IP (tos 0x20, ttl 121, id 7697, offset 0, flags [DF], proto TCP (6), length 52)
    <IP_ADDRESS>.65374 > <IP_ADDRESS>.80: Flags [S], cksum 0xd1f0 (correct), seq<PHONE_NUMBER>, win 8192, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
14:19:05.561264 IP (tos 0x20, ttl 122, id 7699, offset 0, flags [DF], proto TCP (6), length 48)
    <client-IP>.65373 > <worker-IP>.80: Flags [S], cksum 0xb185 (correct), seq<PHONE_NUMBER>, win 8192, options [mss 1460,nop,nop,sackOK], length 0
14:19:05.561311 IP (tos 0x20, ttl 121, id 7699, offset 0, flags [DF], proto TCP (6), length 48)
    <client-IP>.65373 > <IP_ADDRESS>.80: Flags [S], cksum 0x55b8 (correct), seq<PHONE_NUMBER>, win 8192, options [mss 1460,nop,nop,sackOK], length 0
14:19:05.561318 IP (tos 0x20, ttl 121, id 7699, offset 0, flags [DF], proto TCP (6), length 48)
    <client-IP>.65373 > <IP_ADDRESS>.80: Flags [S], cksum 0x55b8 (correct), seq<PHONE_NUMBER>, win 8192, options [mss 1460,nop,nop,sackOK], length 0
14:19:05.561391 IP (tos 0x0, ttl 64, id 35051, offset 0, flags [none], proto UDP (17), length 98)
    <worker-IP>.47764 > <manager-IP>.4789: VXLAN, flags [I] (0x08), vni 4096
IP (tos 0x20, ttl 121, id 7699, offset 0, flags [DF], proto TCP (6), length 48)
    <IP_ADDRESS>.65373 > <IP_ADDRESS>.80: Flags [S], cksum 0x0beb (correct), seq<PHONE_NUMBER>, win 8192, options [mss 1460,nop,nop,sackOK], length 0
14:19:05.793511 IP (tos 0x20, ttl 122, id 7700, offset 0, flags [DF], proto TCP (6), length 48)
    <client-IP>.65374 > <worker-IP>.80: Flags [S], cksum 0x8b9a (correct), seq<PHONE_NUMBER>, win 8192, options [mss 1460,nop,nop,sackOK], length 0
14:19:05.793547 IP (tos 0x20, ttl 121, id 7700, offset 0, flags [DF], proto TCP (6), length 48)
    <client-IP>.65374 > <IP_ADDRESS>.80: Flags [S], cksum 0x2fcd (correct), seq<PHONE_NUMBER>, win 8192, options [mss 1460,nop,nop,sackOK], length 0
14:19:05.793552 IP (tos 0x20, ttl 121, id 7700, offset 0, flags [DF], proto TCP (6), length 48)
    <client-IP>.65374 > <IP_ADDRESS>.80: Flags [S], cksum 0x2fcd (correct), seq<PHONE_NUMBER>, win 8192, options [mss 1460,nop,nop,sackOK], length 0
14:19:05.793602 IP (tos 0x0, ttl 64, id 35083, offset 0, flags [none], proto UDP (17), length 98)
    <worker-IP>.34748 > <manager-IP>.4789: VXLAN, flags [I] (0x08), vni 4096
IP (tos 0x20, ttl 121, id 7700, offset 0, flags [DF], proto TCP (6), length 48)
    <IP_ADDRESS>.65374 > <IP_ADDRESS>.80: Flags [S], cksum 0xe5ff (correct), seq<PHONE_NUMBER>, win 8192, options [mss 1460,nop,nop,sackOK], length 0
^C
40 packets captured
48 packets received by filter
0 packets dropped by kernel

Ok, can you confirm <IP_ADDRESS> is IP address of the only service task, running on the manager ?

Correct:
# docker ps
CONTAINER ID        IMAGE                                                                                COMMAND                  CREATED             STATUS              PORTS               NAMES
559bd134f7cf        dockercloud/hello-world@sha256:629d6815beea1ec5172ce4b56ffa0e2c3fbe288a2e5abda3076aed08ee154e72   "/bin/sh -c 'php-f..."   39 minutes ago      Up 39 minutes       80/tcp              hello.1.7bmfr05wcbymisnygwf99tkhz

# docker inspect 55
...
           "Networks": {
                "hello": {
                    "IPAMConfig": {
                        "IPv4Address": "<IP_ADDRESS>"
                    },
                    "Links": null,
                    "Aliases": [
                        "559bd134f7cf"
                    ],
                    "NetworkID": "5y80givk6kjpirdpn40bgfgzg",
                    "EndpointID": "94350346508b7a470c855467d1a4f298282599e613ffaabe8c08daf4fa12b5d1",
                    "Gateway": "",
                    "IPAddress": "<IP_ADDRESS>",
                    "IPPrefixLen": 24,
                    "IPv6Gateway": "",
                    "GlobalIPv6Address": "",
                    "GlobalIPv6PrefixLen": 0,
                    "MacAddress": "02:42:0a:00:00:03"
                },
                "ingress": {
                    "IPAMConfig": {
                        "IPv4Address": "<IP_ADDRESS>"
                    },
                    "Links": null,
                    "Aliases": [
                        "559bd134f7cf"
                    ],
                    "NetworkID": "omgayyn9454kewjjc2twxs0aq",
                    "EndpointID": "2c7b9a89bb049bf821d81d421e90e07f32f38dac886e37b21eb9d5f5036528b3",
                    "Gateway": "",
                    "IPAddress": "<IP_ADDRESS>",
                    "IPPrefixLen": 16,
                    "IPv6Gateway": "",
                    "GlobalIPv6Address": "",
                    "GlobalIPv6PrefixLen": 0,
                    "MacAddress": "02:42:0a:ff:00:05"
                }
            }
...

hmm, I am surprised the vxlan packet leaving worker toward manager is not being captured in the manager.
Can you double check that is true ?

Correct, just did another capture on the manager, and there was nothing in the log. It's weird.. as soon as I scale it to where both nodes have running containers, traffic is able to be served.
But, I think that's just because instead of redirecting traffic to other nodes... the Docker swarm knows that its running containers on that node that needs to handle traffic, correct?

But, I think that's just because instead of redirecting traffic to other nodes... the Docker swarm knows that its running containers on that node that needs to handle traffic, correct?

Not really. Even with a replica on each node, when you create a service publishing ports in vip mode (the default, what you are doing), the requests toward a docker node:<published port> will always be load balanced across all the service's tasks, regardless of where they are running.
From your capture, things are working, at least initially, as they should:

the request toward worker:80 is being redirected toward the ingress sandbox (<IP_ADDRESS>.80) and from there (<IP_ADDRESS>) load balanced toward one of the service's tasks (<IP_ADDRESS>) on the routing mesh (ingress network)

The sync, encapsulated in the vlxan packet directed to the manager, is being redirected from worker node:
14:18:38.076362 IP (tos 0x0, ttl 64, id 31241, offset 0, flags [none], proto UDP (17), length 102)
    <worker-IP>.57844 > <manager-IP>.4789: VXLAN, flags [I] (0x08), vni 4096
IP (tos 0x20, ttl 121, id 7687, offset 0, flags [DF], proto TCP (6), length 52)
    <IP_ADDRESS>.65371 > <IP_ADDRESS>.80: Flags [S], cksum 0x9174 (correct), seq<PHONE_NUMBER>, win 8192, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0

Try to find where that packet gets dropped.

It's interesting that you had made that comment. These VMs are located are in different zones. I'm going to test having them in the same zone and then see if that would fix dropping the VXLAN packets.

After creating VMs in the same zone, that seemed to do the trick and it works now.
So qq, during testing I noticed that the overlay network that is associated with the service created with the swarm was on all the nodes when I initially created a scale of 5, but then when I changed it to 1, the network no longer appeared on the nodes that didn't have containers running on them.
Is all of the traffic supposed to be flowing through the ingress network if there are no running containers? Or is the hello network I created on the swarm supposed to be on the worker?

Gad to hear it works now.

the network no longer appeared on the nodes that didn't have containers running on them.

That is by designed. Swarm networks are dynamically created where the tasks are deployed.
And removed when the last task on that node is shutdown.
ingress network (the one providing the routing-mesh) dispatches all the traffic incoming to the docker host on the services' published ports.
A user created network, like your hello, is for east-west traffic between tasks, possibly belonging to different services, present on that network.

I think the version 17.06 still has this issue.

It seems that I hit the same issue in #35249, any update on this issue?

+1
when I scale my-nginx=1, the routing mesh is not working at all, but scale my-nginx at least 2 instances, it works great.
centos 7
docker 17.12.0-ce
swarm cluster with 3 nodes

any update ? I have Docker version 18.03.0-ce, build 0520e24, and the issue still happens

I have the same issue even being in the same zone.
The manager is not getting the packets
IP <IP_ADDRESS>.35963 > <IP_ADDRESS>.4789: VXLAN, flags [I] (0x08), vni 4097
IP <IP_ADDRESS>.52844 > <IP_ADDRESS>.8080: Flags [S], seq<PHONE_NUMBER>, win 28200, options [mss 1410,sackOK,TS val 713390616 ecr 0,nop,wscale 7], length 0```
Any ideas on how to track where the packets are being lost?


Got code running, but no output file

Following the comments on Stack Overflow (thanks for changing the code), my colleague and I have made a few more corrections to the syntax and the new files are available here  and here.
However, while the code now runs, there is no JSON file given as an output. Unfortunately I cannot share my IXF files and I cannot find any samples online.
Any ideas?

You can use my version. ixf2json


No safe solution for partial JS applications

We provide a plugin JS application to our clients and some of them would like Microsoft Account login capabilities to be enabled. We neither control the page (or page state), meaning redirecting is unlikely to return the page in the same condition, and in our corporate clients popups may well be blocked completely by group policy.
So right now we seemingly have no solution? With the direction applications and corporate security are going this would seem to be a massive limitation.
I appreciate this is 'by design' but I could just bypass all this and provide a server side relay solution. So it seems to be security by 'annoyance' only. Likely only to keep out honest vendors who would feel uncomfortable doing this. Illicit actors are unlikely to be deterred.
Can we get a third option of an inline login or at least one that runs in an iframe? The alternative is a bypass, and I'd really rather not.

@CodeMonkeyAlpha  thanks for sharing your use case. There are a couple things we are working on here, and a couple security constraints we cant bend on.
Any credential entry in an iframe is strictly banned, because of the threat of clickjacking.
We are working to relax the constraint on iframe constrained apps from requesting tokens, but are doing so with the requirement that the top frame app is using msal and that it can delegate request on behalf of the child app (this is still in design and implementation may not look the same as I just described).
In terms of the parent apps state, if popups are blocked, and interaction is required from the user, there is no way to prevent a refresh of the app.
The end goal is to enable the iframe scenario, while preserving security for the user.
Does this provide clarity on our position / plans?
If not please let me know what I can clarify, if so I will close this ticket and you can expect a release in the next 1-2 months with this enhanced iframe functionality.

Hi,
Good to hear something is coming. I guess my point was also that the security is pretty ineffective, so it seems a little pointless. I have a reasonable bypass rigged now and I could use it to set up click jacking if I was so inclined (obviously I wouldn't). I don't think this is stopping any illicit behavior, but I guess it does make it a little more work. I've only been at it for 5 hours, and while I still have a couple of niggles, it does seem pretty easy to work around.
How likely is that delivery date? Not going to hold you to anything but I'd like to manage expectations in the business realistically if I can. As much as this bypass with a little polish would work its a bit brittle to changes and so I'd rather not.
Thanks for getting back.

@CodeMonkeyAlpha  the release is planned, but I would say that the unexpected can always happen and we should treat it as a date that we can find out if it meets your needs instead of a date that we have a battle hardened solution.  Would you be willing to do a call with us to talk through your use case, workaround, and what a great solution would look like?
@negoe  cc

Hmm sure I could do that I guess, I haven't really thought about how I would want it to be. You know how these things go you tend to focus more on what you can make of whats available. You can probably find me on Skype by my user name if you want...

Makes sense, I will close this issue for now and @negoe  can you reach out and give @CodeMonkeyAlpha  and contact he can share any feedback he has when he has it?


Now that we have a third opinion, I'll change the interface :)


java.lang.ClassNotFoundException: Didn't find class "com.github.kittinunf.fuel.core.FuelManager" on path: DexPathList

Bug Report
Description
Hi, I'm trying to implement Fuel in an android app I'm working on.
When I start my application I get error java.lang.ClassNotFoundException Didn't find class "com.github.kittinunf.fuel.core.FuelManager" on path: DexPathList
Screenshots

OS: Windows 10
IDE: Android Studio
Fuel version: 2.3.1
Kotlin version: 2.3.1

Smartphone or Emulator
Complete the following information if applicable

Device: Samsung A51
OS: Android 11

DO you have a minimal reproducible example?


minimum size of an rbd image

When I created a small test PVC with 1Mi as size, that was rounded down to size 0:
I1010 09:49:43.820983       1 rbd_util.go:124] rbd: create pvc-c46136c5-cc71-11e8-b494-deadbeef0100 size 0G format 2 (features: layering) using mon <IP_ADDRESS>:6789,<IP_ADDRESS>:6789,<IP_ADDRESS>:6789,<IP_ADDRESS>:6789, pool rbd id admin key AQAe07xbq/TsOhAAkLrH6vaRDo/xxVZg/Y6qJg==

# rbd info pvc-c46136c5-cc71-11e8-b494-deadbeef0100
rbd image 'pvc-c46136c5-cc71-11e8-b494-deadbeef0100':
	size 0 B in 0 objects
	order 22 (4 MiB objects)
	id: 5e36643c9869
	block_name_prefix: rbd_data.5e36643c9869
	format: 2
	features: layering
	op_features:
	flags:
	create_timestamp: Wed Oct 10 09:49:43 2018

Obviously the resulting /dev/rbd0 then was unusable ;-}
Is there a minimum size?

this is a bug here https://github.com/ceph/ceph-csi/blob/master/pkg/rbd/controllerserver.go#L100
PR welcome!

fixed in #213

This is fixed as  stated in #213


Duplicate/edit with IPv6 port forwarding results in Invalid Port Specification

Before you start please confirm the following.

[X] Yes, I've searched similar issues on GitHub.
[X] Yes, I've checked whether this issue is covered in the Portainer documentation or knowledge base.

Problem Description
When creating a container with an IPv6 port forwarding on all interfaces, you specify it like [::]::80
However, when editing this container, the port forward will show up as :::80 and an attempt to redeploy will result in an 'Invalid port specification' error.
Expected Behavior
The edit screen should format the port forwarding correctly, like [::]:80
Actual Behavior
See description
Steps to Reproduce
Deploy container with IPv6 port binding, edit and attempt to redeploy.
Portainer logs or screenshots
No response
Portainer version
2.19.1
Portainer Edition
Community Edition (CE)
Platform and Version
Docker version 24.0.6, build ed223bc
OS and Architecture
Debian 11, amd64
Browser
No response
What command did you use to deploy Portainer?
No response
Additional Information
No response

Thanks for the bug report - I've been able to reproduce this behavior here. I've opened an internal issue around getting this fixed.


placed blocks stats

place_block i think, why even that doesn't added?
And please as i requested for mine_block add option for all blocks there

Even though Minecraft doesn't keep track of place_block as its own category, it is being tracked - it's part of use_item, so you can look it up that way.
If you do "use_item stone", for example, that will tell you the amount of stone you placed.


[ruby] Correctly Handle . versus :: Syntax

Context

When a receiver is explicitly specified in a method invocation, it may be separated from the method name using either a period (.) or two colons (::). The only difference between these two forms occurs if the method name starts with an uppercase letter. In this case, Ruby will assume that a receiver::Thing method call is actually an attempt to access a constant called Thing in the receiver unless the method invocation has a parameter list between parentheses.

https://stackoverflow.com/questions/2276905/what-does-double-colon-mean-in-ruby

Example:
irb(main):021:0> module A
irb(main):022:1>   CONST = 0
irb(main):023:1>   def foo
irb(main):024:2>     puts "hhelo"
irb(main):025:2>   end
irb(main):026:1> end
=> :foo
irb(main):027:0> A::CONST
=> 0
irb(main):028:0>
irb(main):029:0> A::foo
Traceback (most recent call last):
        4: from /usr/bin/irb:23:in `<main>'
        3: from /usr/bin/irb:23:in `load'
        2: from /Library/Ruby/Gems/2.6.0/gems/irb-1.0.0/exe/irb:11:in `<top (required)>'
        1: from (irb):29
NoMethodError (undefined method `foo' for A:Module)

However
irb(main):030:0> module B
irb(main):031:1>   foo = 0
irb(main):032:1> end
=> 0
irb(main):033:0> B::foo
Traceback (most recent call last):
        4: from /usr/bin/irb:23:in `<main>'
        3: from /usr/bin/irb:23:in `load'
        2: from /Library/Ruby/Gems/2.6.0/gems/irb-1.0.0/exe/irb:11:in `<top (required)>'
        1: from (irb):33
NoMethodError (undefined method `foo' for B:Module)

But
irb(main):064:0> module B
irb(main):065:1>   def self.foo
irb(main):066:2>     puts "helo"
irb(main):067:2>   end
irb(main):068:1> end
=> :foo
irb(main):069:0> B::foo
helo
=> nil

Right now we approximate all of the above as calls, which is largely fine, except in the case of the constant access.
Problem
We are not testing include as an inheritance operation, nor are we making use of the heuristic that the capitalization of the member has any significance and can instead be a simple field access.

This doesn't make much sense as an issue on its own. With the separation of singleton and instance classes a lot of this confusion has been resolved


Path subclasses InetSocketAddress - v3

Path objects should be a subclass of InetSocketAddressinorder to be returnable from DatagramChannel.receive().
This approach (version 3) moves Path, RequestPath and RepsonsePath to new package-private classes PathImpl, RequestPathImpl and RepsonsePathImpl to new classes. For the public API we get three new interfaces Path, RequestPath and RepsonsePath. PathImpl now extends InetSocketAddress.
This allows paths to be returned by DatagramChannel.receive(). At the same time, a normal Path does not expose any InetSocketAddress methods to avoid confusion. In particular, as far as the user is concerned an InetSocketAddress is never a SCION address (it does not have ISD/AS), and a SCION resolved address is always a Path.
The fact that a Path is internally implemented as InetSocketAddresss is hidden from the user.

Closed. Refactoring was implemented in #94 & #95


Unify BAM and VCF Indexed Readers

One infers the index and one takes it explicitly

closed by #29


Issue with a particular day

With the grid set up with months and days the 27th October is taking 2 days of the grid and pushing a day all the events afterwards.
https://imgur.com/a/lcie3r6
Thanks

Hi there,
I could not reproduce the same trouble as you. Would you tell me the option values of the plugin that had set when you encountered the trouble?
Also, please let me know the timezone of your execution environment. Does summer-time exist in your locale? Unfortunately, the current plugin does not support daylight savings time, which may be the cause.
Thank you,

Hi,
Thanks for the quick response. I posted below the script I'm using, I'm not specifying any timezone in particular, I'm in London timezone. Do I need it? Thanks you.

Hi,
Thank you for providing information, I could reproduce the trouble you reported.
I'm looking like in all probability the cause of the trouble is the difference in time due to the end of summertime on 10/27.
The current plugin doesn't support summertime (Daylight Savings Time) or timezone offsets, so I'm going to do that.
Sorry, I hope to wait until my corresponding is over.

Oh and,
as a temporary response method at the present time, by including the summertime start date in the timeline display range, the summertime difference can be offset so that normal display can be performed.
Thank you,

This issue has already been resolved.


Add CT-CODE support for the "In Order" and "Random" VS settings

Some of the routines that update the currentCourse variable are left unpatched in CT-CODE.  Two of them are related to the "In Order" and "Random" VS course selection settings, and are encountered when "Next Course" is selected (at the end of a race), or when "Random" VS chooses its first course at random (skipping the course screen altogether).  Not patching those would result in repeating the last played course over and over, since they touch the original currentCourse variable instead of CTGP's.
Additionally, both "In Order" and "Random" VS generate a pool of up to 32 course IDs prior to starting, which could be enhanced by allowing custom tracks to be pooled.  Since the "Random" pool is basically an "In Order" pool followed with random permutations, and since it'd make sense for "Random" VS to only pick custom tracks, the last CT cup should wrap back to the first CT cup instead of the Mushroom cup.  For completion's sake, the Lightning Cup (8.4: rBC64) should wrap back to the Mushroom Cup (1.1: Luigi Circuit) in case the pool has started off with a Nintendo course.  This effectively means making the whole pool exclusive to one category, CTs or Nintendo courses, depending on what the first picked course is.
This pull request addresses all of the above notes.  I started off by making patches for PAL (debugged on Dolphin and tested on my Wii U), and proceeded to auto-port the offsets to other regions using the "Mario Kart Wii Code Generator" program, and common sense to ensure the mods are region-agnosic.  When testing other regions, make sure that "In Order" wraps correctly, and that nothing crashes.
Note that two CTs that are more than 32 slots away from each other (with wrapping taken into consideration) will never be played together in a Random VS pool due to its limited capacity (up to 32), unless the algorithm were changed to something better.
For memory-debugging purposes, look around at [menuData + 0x98] + 0x78 for the course pool's array.

Hello DimitriPilot3,
some other questions to you (as you seem to be one of the few who is able to read / understand / write own assembler code besides Chadderz & MrBean) about bugs in 1.02:
(I haven't tested your modifications yet so sorry if this already solves some of the things I write here):

This also makes online "random" work (also select custom track)?
-- If yes: When is the pool reset? At the beginning of a GP? Or for each race?
-- If not: Can you make it work, or at least make it not vote random for a whole GP (with the current random function)?
Are you able to fix the online course selection so it actually focuses the last voted Cup and track and not the last played Cup?
Are you able to modify the blue shell drag patch so the dragging only works offline, in regions, and in friend rooms but not in global races?

It would be great if you'd answer my questions.
Leseratte10

Hello @DimitriPilot3,
First of all, thanks a lot for the patch, I'm amazed anyone took the time to understand the source and actually fix something :wink:
I'll give it a test on my Wii, and test the port when I get chance and then merge this request.
@Leseratte10:

@mrbean35000vr fixed that random friend room bug in v1.03 last week, so I'll try to backport that fix at the same time as I merge this.
Never looked into that, I'd be more than happy to accept a fix for that if anyone can be bothered to write one.
Currently the blue shell's item behaviour in an item behaviour table is modified directly by this mod. Instead, the value would have to be swapped in with the correct value as modes were changed. Not impossible, but a non-trivial change, as we don't already have code which executes at the right time.

Chadderz

Aren't the assembler codes basically the same for both 1.02 and 1.03 so you could just copy the module? Or is CTGP messing with the RAM and actually moving memory parts around so the offsets aren't identical to vanilla mkw?

They are basically the same, but v1.03 is still (for some reason) compiled by hand; it doesn't use this build system. I effectively disassemble the v1.03 code to work out what to put here. This build system is also parametrised, whereas v1.03 makes fixed choices, so I have to check the parameters don't interfere. It's not too difficult, but it's not just copy/paste.

@DimitriPilot3
@Chadderz121
Today I tested this patch for all 3 regions. I played offline 3 races in-order and 3 random at each region. And it worked like DimitriPilot3 told. In the next days I'll test, if it have online side effects.

Can't find any side effects if playing online. We tested it with PAL and USA versions. I don't see any reason against the merge.

Thanks for the patch, I've now merged it into the main tree. Sorry it took so long!


Configure exclusive roles

Can a configuration option be added to make certain roles mutually exclusive from each other?

I think this is something you could manage on your own?

I could, but I feel like this is a natural fit for this package.

Not sure how to make this extensible though. I think there could be probably many different more complicated conditions you might have which roles can co-exist?

A 3rd party extension could provide that.


Traceflow with liveTraffic and droppedOnly didn't capture results from source node

Describe the bug
When traceflow is done with liveTraffic and droppedOnly for packets across nodes, the status on source nodes lacks.
Here is the manifest for the traceflow. It has the result only from the destination node.
# kubectl get tf tf-pod1-to-pod3-icmp-live-traffic -o yaml
apiVersion: crd.antrea.io/v1alpha1
kind: Traceflow
metadata:
  annotations:
    kubectl.kubernetes.io/last-applied-configuration: |
      {"apiVersion":"crd.antrea.io/v1alpha1","kind":"Traceflow","metadata":{"annotations":{},"name":"tf-pod1-to-pod3-icmp-live-traffic"},"spec":{"destination":{"namespace":"default","pod":"pod3"},"droppedOnly":true,"liveTraffic":true,"packet":{"ipHeader":{"protocol":1}},"source":{"namespace":"default","pod":"pod1"}}}
  creationTimestamp: "2021-04-16T07:28:59Z"
  generation: 1
  name: tf-pod1-to-pod3-icmp-live-traffic
  resourceVersion: "2770685"
  uid: 1e7feafa-0bd6-4aa7-acd5-2a073d1de0f8
spec:
  destination:
    namespace: default
    pod: pod3
  droppedOnly: true
  liveTraffic: true
  packet:
    ipHeader:
      protocol: 1
  source:
    namespace: default
    pod: pod1
status:
  capturedPacket:
    dstIP: <IP_ADDRESS>
    ipHeader:
      flags: 2
      protocol: 1
      ttl: 62
    length: 84
    srcIP: <IP_ADDRESS>
    transportHeader: {}
  phase: Succeeded
  results:
  - node: k8s2-md-0-647454fc57-qpqbg
    observations:
    - action: Received
      component: Forwarding
      componentInfo: Classification
    - action: Dropped
      component: NetworkPolicy
      componentInfo: IngressDefaultRule
    timestamp:<PHONE_NUMBER>

The souce node is k8s2-md-0-647454fc57-9sf7n and the destination node is k8s2-md-0-647454fc57-qpqbg.
# kubectl get pod -o wide
NAME    READY   STATUS    RESTARTS   AGE     IP            NODE                         NOMINATED NODE   READINESS GATES
debug   1/1     Running   0          3d1h    <IP_ADDRESS>   k8s2-md-0-647454fc57-9sf7n   <none>           <none>
pod1    1/1     Running   0          6d17h   <IP_ADDRESS>   k8s2-md-0-647454fc57-9sf7n   <none>           <none>
pod2    1/1     Running   0          6d17h   <IP_ADDRESS>   k8s2-md-0-647454fc57-9sf7n   <none>           <none>
pod3    1/1     Running   0          6d17h   <IP_ADDRESS>    k8s2-md-0-647454fc57-qpqbg   <none>           <none>

To Reproduce
Not sure if all the procedure is required.
The procedure including setups.

Deploy 3 pods using the manifest
Apply  kubernetes networkpoclies using this manifest
Apply the following traceflow manifest

apiVersion: crd.antrea.io/v1alpha1
kind: Traceflow
metadata:
  name: tf-pod1-to-pod3-icmp-live-traffic
spec:
  liveTraffic: true
  droppedOnly: true
  source:
    pod: pod1
    namespace: default
  destination:
    pod: pod3
    namespace: default
  packet:
    ipHeader:
      protocol: 1

Expected
The traceflow should have results from source and destination nodes.
Actual behavior
The traceflow got the result only from the destination node.
Versions:
Please provide the following information:

Antrea version (Docker image tag).
v1.0.0

Kubernetes version (use kubectl version). If your Kubernetes components have different versions, please provide the version for all of them.

# kubectl version
Client Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.0", GitCommit:"cb303e613a121a29364f75cc67d3d580833a7479", GitTreeState:"clean", BuildDate:"2021-04-08T21:15:16Z", GoVersion:"go1.16.3", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"20", GitVersion:"v1.20.1", GitCommit:"c4d752765b3bbac2237bf87cf0b1c2e307844666", GitTreeState:"clean", BuildDate:"2020-12-18T12:00:47Z", GoVersion:"go1.15.5", Compiler:"gc", Platform:"linux/amd64"}

Container runtime: which runtime are you using (e.g. containerd, cri-o, docker) and which version are you using?

containerd github.com/containerd/containerd v1.4.3 269548fa27e0089a8b8278fc4fc781d7f65a939b

Linux kernel version on the Kubernetes Nodes (uname -r).

4.19.164-1.ph3

If you chose to compile the Open vSwitch kernel module manually instead of using the kernel module built into the Linux kernel, which version of the OVS kernel module are you using? Include the output of modinfo openvswitch for the Kubernetes Nodes.

Additional context
Add any other context about the problem here, such as Antrea logs, kubelet logs, etc.
(Please consider pasting long output into a GitHub gist or any other pastebin.)

@yktsubo : thanks for trying out the new feature and providing feedback! The behavior you described is actually by design. The reason is that the source Nodes does not know if a packet will be dropped on the destination Node or not, and so cannot capture and report every matched packet it sees. Hope it makes sense to you.
BTW, I am working on a new change #2068 which will allows to capture a packet from any source or a particular IP on the destination Node, and in this case again we wont be able to capture the packet on the source Node. Also like to learn your thoughts on this one.

@jianjuns Thank you for the explanation. I thought it was a bug as octant plugin didn't show anything. But that makes sense now.
I got the impression that this live-capture traffic is more of a 'tcpdump by kubectl'.
Therefore the situation where we want to use it for troubleshooting is like to understand why packets get dropped.
In my opinion, the following function might be useful.

Captures for some period, like mentioned in the #2068
Captures packets that were dropped by a specific table. (Like default egress policy table)

Thank you.

Thanks @yktsubo . Let me add "Captures packets that were dropped by a specific table" to the todo list.
The Traceflow implementation is actually different from tcpdump. It uses OVS flows to send matched packets to agent. But I also thought about to add some tcpdump like functions, which can stream the captured packets to a collector.

@jianjuns  Thank you for considering that.
I'll close this issue as the behavior is expected. Thanks.


[Accessibility][Usable-Settings] : On Enabling 'Show Keys' button within Settings page, page gets automatically refreshed without providing any proper information.

User Experience
Users who rely on AT will face difficulty if  page gets automatically refreshed without providing any proper information.
Test Environment
Environment: Chromium Edge (Anaheim) + Narrator
Build Version: 2004 (OS Build 19564.1005)
Microsoft Edge Version: 82.0.425.0 (Official build) canary (64-bit)
Test URL: http://localhost:3000/home
Repro Steps:

Open URL: http://localhost:3000/home
"Bot Framework Composer" homepage will gets opened.
Select any of the previously created bot from "Recent Bots" or create one from the available Bots under 'Examples' and activate it.
Select 'Settings' from left navigation.
Enable 'Show Keys' button and press tab key and observe the issue.

Actual:
On Enabling 'Show Keys' button within Settings page, page gets automatically refreshed without providing any proper information. Error pop-up will come and other page gets opened but screen reader does not provide any information.
Expected:
On Enabling 'Show Keys' button within Settings page, page should not get automatically refreshed and  it should provide the proper information related to error.
Attachment:
Usable_Settings_Start keys.zip

@ShellySoni could you try this again with the updated master branch code? I cannot reproduce that error from my side.

As checked and verified on below environment, the issue is fixed now. So, we are closing the issue.
Test Environment
Browser: Microsoft Edge Dev {Version 83.0.467.0 (Official build) dev (64-bit)}
OS build: 2004 (19588.1000)
Screen Reader: Narrator
URL: Bot Framework Composer
Prerequisite Here


Added Request Feedback button to the share plan page

issue #727

added new plans.feedback_requested flag to DB
added 'Request Feedback' button to share plan page
added confirmation email for owner and co-owners
added notification email for org admins
minor modifications to tooltips and email defaults (moved email constants to user_mailer)

failing tests for this one are addressed in the other PR, #793, that removed the DB default from plans.visibility

Switched logic to user the new 'Reviewer' role. This role does not appear in the Plan's normal collaborator section and is excluded from the list of plans in My Dashboard. They will be made accessible in the new Admin -> Plans page that will be developed as a part of #434
Requires rake db:migrate

tests failing because the updated schema.rb file contains a change to the default visibility which is in separate PR. will rebase this one once that PR has been merged to resolve the conflict in this file.

Schema.rb updated to add default back to plan.visibility. This could create conflict, so merge the plan visibility PR first

made most of the requested changes. Lets create a ticket to handle our server errors better (see above comments). Ping me on Slack if you get a chance to review this one @jollopre. I'll deploy once its merged so things are ready for testing on Monday


[Enhancement] - Support For GQL Interfaces, Unions and Fragments

It would be great to have this generator / library support Fragments alongside Unions and Interfaces.
Some GraphQL API's (such as the one that I am using this project for), make heavy use of these modifiers - as these aren't supported, this leads to a lot of errors when performing queries and I've had no choice but to comment out the problematic parts in my project now.
Happy to help out where I can for adding feature support for these

Hi,
Thanks for opening a new issue, I have a couple of open points:
a) I revisited my documentation (and GraphQL one), fragments in GraphQL have been created for reusability, which is the fundament of py-graphql-mapper: if you need to reuse a particular data structure, instead of creating a hard-coded fragment, you can just create your own type as python class using the mapper module (example here).
Unless you need to manage hard-coded queries coming from an external source (that would imply a different code generation) or to have a better visibility of query logs.
Can you explain me in more detail how you intend to use fragments?
b) I explored the query containing the field you showed me in issue #25 insightsChartData: Optional[DEFTF_InsightsChartDataOutput_Field] and tried to call the API involving this information here.
Unfortunately I don't have any valid ID for the argument genFarmId. Is it possible to have one in order to analyze it?
Of course I can use some examples with the already present APIs creating dummy input, but it would be better to have a complete test to work with.
Thanks again


Fix typo in Thrift provisioning script

I haven't tested this fix, but it seems pretty obviously correct. (Right now we're downloading one version of a .deb file, then trying to install a different version.)
1.14.1-3 is the version number we want according to the Thrift installation docs for Debian.

Ping -- @hegemonic care to fix the two lines -- I think we don't care about this any more, however.

Updated to use automake 1.14.1-4.
AFAIK, we still need this example for folks who aren't using Java or Go.

Cory doesn't consider it as important at this point.


[semver] Add new port

Describe the pull request

What does your PR fix?

Added support for semver header only library https://github.com/z4kn4fein/cpp-semver

Which triplets are supported/not supported? Have you updated the CI baseline?
All. No

Does your PR follow the maintainer guide?

Yes

If you are still working on the PR, open it as a Draft: https://github.blog/2019-02-14-introducing-draft-pull-requests/

Tested the semver:x64-windows usage successfully

We appreciate your contributions to the catalog. However, we have an issue with the port's name. "semver" is way too generic. We recommend prefixing with your username. Note that "cpp-semver" will not work because there are other repositories with the same name, and this repository is still new.

Hi @JavierMatosD,
I can't see "cpp-semver" in the ports just "neargye-semver". I tried "neargye-semver" lib but unfortunately, it seems it's not working correctly. Opened an issue about the error but we still don't have any response :(
That's why we created a new lib.
if you think "semver" is way too generic I think "cpp-semver" can work.

Hi @JavierMatosD,
I can see just "neargye-semver" in the ports. Would "semver-cpp" work for you?

I think this library should be kept in a private port overlay until there are more users.

What does "private port overlay" mean?
Or just should I use the repo owner? "z4kn4fein-semver"?

Hi @JavierMatosD,
I've just renamed "semver" to "z4kn4fein-semver". I'd like to use vcpkg for dependency handling in another library and I'd like to use this semver lib there. That's why I created this port here. I hope it can be merged into the master.


[Torii] gRPC to support Events subscription

Continuation of this issue https://github.com/dojoengine/dojo/issues/1420 but for grpc event subscription

:hand:


Use ENVAR for service account impersonation

Is your feature request related to a problem? Please describe.
Simpler, environment wide way to impersonate a service account across multiple client libraries during development when my the local machines ADC is set to a user google account (or a service account) with permissions to act as the specified service account.
Google's best practices also recommend service account impersonation.
Describe the solution you'd like
To use an envar to specify a service account email to be used for client library authentication.
Describe alternatives you've considered

Giving the ADC service account needed permissions - OK until you want to check you've given the deployed code service account the correct permissions (when run in Cloud Run etc.).
Setup the ADC to be an impersonated service account (via gcloud auth application-default login --impersonate-service-account=<>) - pain to have to run that each time you need to target a certain service account (and I think it still needs targetScopes to be specified).
Using user google account with needed permissions - same issues as above, but also some APIs (e.g Identity Toolkit) don't allow authorized_user credentials without a quota project needing it to be specified (which is added boilerplate).
Passing in an GoogleAuth (which has been created with an Impersonated authClient option) using the authClient when creating each client library - just extra boilerplate to do for each client.
Using a downloaded service account key file and setting GOOGLE_APPLICATION_CREDENTIALS envar to the file local before starting - I don't want to have service account key files downloaded.

Additional context
I've already raised this in @google-cloud/common, but thought I'd re-raise here as this library seems to be a bit more active.
I was thinking as something as simple as checking for an envar when loading up the ADC and creating an Impersonated auth client here
https://github.com/googleapis/google-auth-library-nodejs/blob/151513131f6256d381480b49bdfadf692a336d3d/src/auth/googleauth.ts#L352-L370
  async _tryGetApplicationCredentialsFromEnvironmentVariable(
    options?: RefreshOptions
  ): Promise<JSONClient | null> {
    const credentialsPath =
      process.env['GOOGLE_APPLICATION_CREDENTIALS'] ||
      process.env['google_application_credentials'];
    if (!credentialsPath || credentialsPath.length === 0) {
      // Check if we're trying to impersonate a service account with envar
      if (process.env.CLOUDSDK_AUTH_IMPERSONATE_SERVICE_ACCOUNT) {
        return new Impersonated({
          ...options,
          targetPrincipal: process.env.CLOUDSDK_AUTH_IMPERSONATE_SERVICE_ACCOUNT,
          targetScopes: ['https://www.googleapis.com/auth/cloud-platform'],
        })
      }
      return null;
    }
    try {
      return this._getApplicationCredentialsFromFilePath(
        credentialsPath,
        options
      );
    } catch (e) {
      e.message = `Unable to read the credential file specified by the GOOGLE_APPLICATION_CREDENTIALS environment variable: ${e.message}`;
      throw e;
    }
  }

I've used the gcloud envar for service account impersonation just for an example.
Also I've noticed gcloud logs out warnings when using the --impersonated-service-account option - that could be added here too, to warn the user what's happening?
Note - I'm still not sure if this should be raised here or in @google-cloud/common as previously mentioned, but I feel it would probably be more useful if it could be done at the google-auth-library level as then if you created a GoogleAuth it would automatically be impersonated auth client across the board.

We have a similar scenario where we want to use impersonated service accounts to run tests in a containerised environment.
We've tried a few things to get it working, but it seems currently the only way to do it is by adding additional code in for impersonating (which we avoid at all costs).
Any update on whether this is likely to be implemented?


US-85: Implement AI Firing Of Weapons In AICommandable

US-85
As a player I want the enemies in the game to fire at me to make the game more engaging
Implementing methods in AICommandable to allow enemies to fire correctly towards the player.
Tasks

[ ] Implement method for enemies to fire at player
[ ] Implement logic so that only enemies within range fire at the player
[ ] Implement logic so that enemies fire in the correct direction of the player
[ ] Integrate use of method in application

Acceptance Criteria

[ ] Enemies within firing range of player fire at the player
[ ] Enemies fire in the correct direction facing the player

This looks a lot like US-73, this one or 73 should be closed.

US-85 already exists aswell so it needs to be renamed


Add test file for utils/head action

@houshengbo nodejs test is added. please review.

You don't need to close/reopen a pr to force a travis rebuild button - click the details link and then in the right corner you will see a circle with an arrow head which if you click will start a new build.


Appstudio update test-component-pac-ftrs

Pipelines as Code configuration proposal

Pipelines as Code CI/test-component-pac-ftrs-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
6 seconds
init

✅ Succeeded
15 seconds
clone-repository

✅ Succeeded
37 seconds
build-container

✅ Succeeded
22 seconds
sanity-inspect-image

✅ Succeeded
21 seconds
deprecated-base-image-check

✅ Succeeded
3 minutes
clair-scan

✅ Succeeded
48 seconds
clamav-scan

✅ Succeeded
15 seconds
sbom-json-check

✅ Succeeded
8 seconds
sanity-optional-label-check

✅ Succeeded
8 seconds
sanity-label-check

✅ Succeeded
8 seconds
show-summary

Pipelines as Code CI/test-component-pac-ftrs-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
5 seconds
init

✅ Succeeded
14 seconds
clone-repository

✅ Succeeded
30 seconds
build-container

✅ Succeeded
17 seconds
deprecated-base-image-check

✅ Succeeded
17 seconds
sanity-inspect-image

✅ Succeeded
32 seconds
clamav-scan

✅ Succeeded
8 seconds
clair-scan

✅ Succeeded
9 seconds
sbom-json-check

✅ Succeeded
13 seconds
sanity-optional-label-check

✅ Succeeded
12 seconds
sanity-label-check

✅ Succeeded
6 seconds
show-summary


RangeError when decrypting chacha20poly1305: start offset of Uint32Array should be a multiple of 4

I was trying to decrypt 2246 bytes (Uint8Array) with 12 bytes IV and got the error
chacha20poly1305(key, iv).decrypt(bytes)

RangeError: start offset of Uint32Array should be a multiple of 4

It also happens if I force .slice() to copy to a new buffer
chacha20poly1305(key, iv).decrypt(bytes.slice())

Using Stablelib it works fine
new ChaCha20Poly1305(key).open(iv, cipher)

for now either key or iv need to be their own array and now a subarray: chacha20poly1305(key.slice(), iv.slice()) should be a workaround

Thanks, it works

Fixed


associate timers with widget ids

currently we route timers to all widgets that have ever requested a timer; we can now store the id of the requesting widget along with the timer, and route things that way.
If someone is interested in taking this, it shouldn't be too tricky, and it will be a nice excuse to explore some of druid's internals.

I would like to take this up if it's ok.

@sjoshid definitely!

@cmyr
The timer event is received by all widgets but is acted upon only by the widget that requested it.
Is the task here to bypass all the traversing so the root widget can directly send the event to the target widget?

sort of! we don't send things "directly"; we still need to traverse the tree, but skip looking at parts of the tree that don't contain the relevant widget. You should be able to get a sense for this by looking at how the 'focus changed' lifecycle event works.

I traced focus changed event and how it traverses. It is same as timer event.

Breadth first search.
Traverse children only if target can be reached. (Bloom filters here?). Otherwise move on to next sibling.

Am I missing something obvious?

sounds about right. All the logic should be in WidgetPod::event.


Creating SBD dataset from polygon information

Hi,
I was able to successfully train and test on PASCAL VOC dataset from scratch and score accuracy of Mean<EMAIL_ADDRESS>= 65.5%.  Next, I want to conduct FCIS training on my own dataset, however the object boundaries ground truth information I have is in polygon points + class format like this: {class: "pen", "polygon": [(x1,y1), (x2,y2),(x3,y3),(x4,y4)]}.  I'd appreciate if anyone is aware of an existing code or an easy way to convert this into SBD format.  Note that closest thing I found was converting SpaceNet getJson labels to Pascal VOC labels (however, this requires converting what I have to getJson labels, which is still not as straightforward).
Any help/tips on a way to easily convert polygons/class to SBD would be appreciate.

Just convert to COCO json format, that is much easier and FCIS also works with COCO. Conversion to VOC format is a lot more difficult and there is no library etc for it afaik.

@chrieke Thanks for your great work！i want to convert COCO json format, too. But  i follow COCO_2014 dataset which the annotation file need instances_valminusminval2014.json and instances_minval2014.json, i cannot find any way to get my own .json file I mentioned. If you have a good way to share it with me? or your own dataset file structure, grateful!

@liangzhicong456 Hi, I finally uploaded my preprocessing script for the image cutting and cocojson conversion. Currently adding the rest of the project code and will convert the preprocessing code to a nicer notebook with more annotations etc. Hope this helps you out in the meantime.


EnergyConsumer objects missing from SwitchArea

EnergyConsumer objects are currently only being reported in Secondary Area. They need to be listed at the Feeder Area and Switch Area as well

resolved in pr #18


Saya/dat767 pagination in Items page

JIRA: DAT-767
Comments: Oracle.py was not returning required prametre to show Prev/Next links in the Items page. The changes in this feature branch fixed the issue.

Closing this PR to accommodate with business requirements to be clear with commit history as advised by Wangchen.


/etc/services not mapping custom port

I set my main port to 777, completed the install, rebooted the server, and was unable to connect. Upon further searching through IPTables, I noticed the only entry was tcp/udp openvpn, so I headed over to /etc/services and noticed:
openvpn         1194/tcp
openvpn         1194/udp
Looks like the custom port was not translated over to the services file. Good work though, I'm loving it so far!

I don't think the script nor any user software should change /etc/services services at all, correct me if I'm wrong.
I suppose your firewall is using this list as a reference and you did something like --add-service=openvpn?
Anyway this should be fixed in the next commit which I'm publishing very soon and will take care of both FirewallD (CentOS) and iptables properly among many other cool things :)

The problem is that I didn't run any commands to change anything.
Netstat says OpenVPN is listening on 777. IPTables says you opened 1194.
Wheres our issue?

Are you using a firewall?
You should be able to connect right after install at whatever port you selected, except if you are using a firewall.

I ran 'ufw allow 777' and that fixed my issue with not being able to connect, however it is just a workaround.

So yes, you are using a firewall.
As far as I know, ufw is not enabled by default in Ubuntu, so if the user wants to use a custom firewall that's fine, but he needs to add the rules.
My reasoning is: I support firewalls as long as they are enabled by default after a clean OS install. That's why I'm adding FirewallD and iptables support for CentOS. I can't support custom configurations by my users and I assume they know how to configure their firewalls anyway :)


Add parser for CycloneDX

@Maffooch I'm missing some CyclonDX reports here. I want to have more tests, so if you have some feel free to share.

@Maffooch I think I have a good one now


Russian translite and move registration form separate url

Added russian language translite

@diversantvlz Awesome contribution. Thank you very much!
Great idea with separating the login and registration. I divided nav link into two: login, registration
http://awesomescreenshot.com/0456ajkd2a
https://github.com/WellCommerce/WellCommerce/blob/master/web/themes/wellcommerce-default-theme/templates/WellCommerceAppBundle/Front/Common/nav.html.twig#L9-L10
Could you please check whether the RU translation fits?

Could you please check whether the RU translation fits?

No, client.link.register = Регистрация

@diversantvlz Changed :)
https://github.com/WellCommerce/WellCommerce/commit/6f55112b839914f152a6899ac4cb5db78ebf42f2


Implementation table header color with variable & Fix for inset shadow of form control on focus

Please open separate pull requests since the form change and the tables change are unrelated to each other.

We don't specifically set the <thead>'s background-color, so I don't really see a need for a variable for it.