sniffer | A poor man MOSS

I have a Drupal 8 installation where I want to use the squizlabs/php_codesniffer with PhpStorm.

I installed phpcs with Composer by following this documentation from Drupal itself https://www.drupal.org/docs/contributed-modules/code-review-module/installing-coder-sniffer#s-composer-installer-plugin. I installed it with this command composer global require drupal/coder dealerdirect/phpcodesniffer-composer-installer which also installs squizlabs/php_codesniffer. At this point everything is working and phpcs is installed in my users .composer folder.

When I execute phpcs --config-show I get this output: (version 3.6.1)

I would be grateful if someone could help me with setting up bitbucket-pipeline for my php env. What I'm trying to succeed is:

1. Build image in the first step
2. In the second step run some QA stuff like unit test, code sniffer etc.
3. Deploy to preprod envirement

Currently I'm stuck with re-using image from the first step. This is how my bitbucket-pipelines.yml looks like:

In my application config i have defined the following properties:

I am trying to call an OWL API java program through terminal and it crashes, while the exact same code is running ok when I run it in IntelliJ.

The exception that rises in my main code is this:

After installing Composer in windows 10, the result of phpc -i command is:

"The installed coding standards are MySource, PEAR, PSR1, PSR12, PSR2, Squiz and Zend."

After lots of searches I was unable to find any documentation about MySource coding standard, nor for Squiz coding standard.

So what are these two standards? Are there any link to their documentation to see what sniffs they do?

In fact I need to know are there any extra sniffs which these two standard do in comparison with PSR12? (currently I've set only PSR1,PSR12 in my vscode code sniffer extension settings.)

I understand the XSS vulnerability of using web storage and the CSRF vulnerability of using cookies. So I store the access token in memory and for persistence I have a refresh token in a cookie which I use to silently refresh my access token when we lose it. I feel somewhat better about XSS and CSRF threats... BUT how do we secure the token from a packet sniffer? A packet sniffer would find the token in the request. I see a lot of discussion on XSS and CSRF but how do we keep safe from packet sniffers, and are there even more threats we do not commonly think about?

I would like to exclude everything except some directories from PHP Code Sniffer inspection in my project. Something similar like git repo exclusions with .gitignore

I had the idea that regex with negative lookahead could be used with >. I tried:

I’m attempting to deploy an SFTP server using python / paramiko into AKS.

This deployed successfully into a bare metal dev server, however I am having issues deploying this into AKS.

The problem starts when creating the LoadBalancer service, this triggers a deluge of TCP traffic on the target port which renders the SFTP server useless.

Is this expected? I’m at the limit of how the AKS internals work so I don’t want to assume this is an error, but I would like to know where I might be going wrong.

The code below reproduces the issue in a newly provisioned AKS environment using the nast network sniffer. Run the first command to launch nast and then create the load balancer service using in a separate console:

In a python3/mininet script I have a tested, valid dictionary of host machines and their IP addresses. For each of the keys - by iterating dictOfAllHostsAndIPs.keys() - I execute a script on each emulated host's terminal