all files changed to linux line endings (#379)

SECURITY.md

@@ -38,4 +38,4 @@ We prefer all communications to be in English.
 
 Microsoft follows the principle of [Coordinated Vulnerability Disclosure](https://www.microsoft.com/en-us/msrc/cvd).
 
-<!-- END MICROSOFT SECURITY.MD BLOCK -->
+<!-- END MICROSOFT SECURITY.MD BLOCK -->

dash-pipeline/.dockerignore

@@ -2,4 +2,4 @@
 *.log
 *.pcap
 __pycache__/
-.pytest_cache/
+.pytest_cache/

dash-pipeline/README-common-errors.md

@@ -20,4 +20,4 @@ You will need to logout and log back in to obtain the group membership. To check
 ```
 $ id
 uid=1001(dash) gid=1001(dash) groups=1001(dash),27(sudo),998(docker)
-```
+```

dash-pipeline/README-dash-as-submodule.md

@@ -143,4 +143,4 @@ If test ports other than `veth0/1` and `veth2/3` are used, some modifications of
 ## Custom Tests
 You can use the tests under DASH by calling the appropriate DASH make targets from the parent project. You can also have private tests in your own project repository which you invoke from your Makefiles. We recommend if you write new tests which are generally applicable that you consider upstreaming to the Community repository.
 ## Third-Party CI Pipeline Automation (Git Actions)
-You should be able to adapt the CI automation files from the dash project as located under [.github/workflows](../.github/workflows). You will need to modify them to suit your project by changing the trigger conditions (e.g. file system paths) and steps.
+You should be able to adapt the CI automation files from the dash project as located under [.github/workflows](../.github/workflows). You will need to modify them to suit your project by changing the trigger conditions (e.g. file system paths) and steps.

dash-pipeline/README-dash-ci.md

@@ -50,4 +50,4 @@ Let's drill down into the Build P4 step which failed. We see a a bad statement.
 
 The main README for this repository shows the CI failing badge:
 
-![CI-fail-README-badge](../assets/CI-fail-README-badge.png)
+![CI-fail-README-badge](../assets/CI-fail-README-badge.png)

dash-pipeline/README-pytests.md

@@ -130,4 +130,4 @@ listening on lo, link-type EN10MB (Ethernet), capture size 262144 bytes
 
 * Launch Wireshark
 * Enter the following filter: `tcp.dstport==9092`
-* You can see RPC calls being made in the packet data view, the ASCII string names of methods are displayed
+* You can see RPC calls being made in the packet data view, the ASCII string names of methods are displayed

dash-pipeline/README-saithrift.md

@@ -427,4 +427,4 @@ Continuing.
 Starting SAI RPC server on port 9092
 [New Thread 0x7f2b4b7fe700 (LWP 18)]
 [New Thread 0x7f2b4affd700 (LWP 19)]
-```
+```

dash-pipeline/SAI/README.md

@@ -37,4 +37,4 @@ In this example, the input is a dash_pipeline.json, which is a result of a P4 co
 # requirements.txt
 This is used for installing python modules, in particular for [snappi](https://github.com/open-traffic-generator/snappi) and [pytest](https://docs.pytest.org/en/7.1.x/index.html).
 
->**NOTE:** This file is a **hardlink** pointing to a single source of truth for test infrastructure. Take care accordingly. Modifying its contents will impact other collections of test scripts. It's a hardlink for convenience in order to pass the Docker context when building the `saithrift-client` images. We can't use a symlink because Docker cannot dereference symlinks in the context passed to it, see https://stackoverflow.com/questions/31881904/docker-follow-symlink-outside-context and https://medium.com/@307/hard-links-and-symbolic-links-a-comparison-7f2b56864cdd.
+>**NOTE:** This file is a **hardlink** pointing to a single source of truth for test infrastructure. Take care accordingly. Modifying its contents will impact other collections of test scripts. It's a hardlink for convenience in order to pass the Docker context when building the `saithrift-client` images. We can't use a symlink because Docker cannot dereference symlinks in the context passed to it, see https://stackoverflow.com/questions/31881904/docker-follow-symlink-outside-context and https://medium.com/@307/hard-links-and-symbolic-links-a-comparison-7f2b56864cdd.

dash-pipeline/dockerfiles/.dockerignore

@@ -2,4 +2,4 @@
 *.log
 *.pcap
 __pycache__/
-.pytest_cache/
+.pytest_cache/

dash-pipeline/dockerfiles/README.md

@@ -1,2 +1,2 @@
 # dockerfiles directory
-Dockerfiles are placed here in part to avoid exporting the entire environment of the dash-pipeline directory to the docker builder, `.dockerignore` files notwithstanding.
+Dockerfiles are placed here in part to avoid exporting the entire environment of the dash-pipeline directory to the docker builder, `.dockerignore` files notwithstanding.

dash-pipeline/tests/libsai/README.md

@@ -1,2 +1,2 @@
 # libsai tests directory
-These tests are written in c++ and are intended to test and demonstrate writing DASH API configuration and management code which links to the `libsai` library for DASH. In particular, these programs use the SAI-to-P4Runtime adaptor layer. As such they require many libraries including gRPC, protobuf, P4 PI layer etc. in addition to `libsai` itself.
+These tests are written in c++ and are intended to test and demonstrate writing DASH API configuration and management code which links to the `libsai` library for DASH. In particular, these programs use the SAI-to-P4Runtime adaptor layer. As such they require many libraries including gRPC, protobuf, P4 PI layer etc. in addition to `libsai` itself.

dash-pipeline/tests/saithrift/README.md

@@ -5,4 +5,4 @@ This directory contains tests for DASH pipeline using python `saithrift` client
 
 The tests use the same thrift and saithrift client libraries and in general the configuration and setup of the DASH data plane will use the same APIs and command sequences. The frameworks differ primarily in how test suites are designed and orchestrated. Each framework has advantages and disadvantages, hence both are supported as first-class citizens.
 
-In particular the PTF test framework has a significant body of helper libraries which simplify setup. The corollary is that the PTF libraries make a lot of embedded assumptions about the test target, the environment and the data plane SW packet generator (scapy).
+In particular the PTF test framework has a significant body of helper libraries which simplify setup. The corollary is that the PTF libraries make a lot of embedded assumptions about the test target, the environment and the data plane SW packet generator (scapy).

dash-pipeline/tests/saithrift/ptf/README.md

@@ -3,4 +3,4 @@
 
 This directory can contain PTF tests for DASH bmv2. These would supplement standard tests under [SAI/ptf](../../SAI/ptf)
 
-CI-ready DASH tests are moved to [`test/test-cases/functional/ptf`](../../../../test/test-cases/functional/ptf/)
+CI-ready DASH tests are moved to [`test/test-cases/functional/ptf`](../../../../test/test-cases/functional/ptf/)

doc-github-rules.md

@@ -204,4 +204,4 @@ See also [A collection of .gitignore templates](https://github.com/github/gitign
 - [Visual studio code](https://code.visualstudio.com/)
   - [Gitlens](https://marketplace.visualstudio.com/items?itemName=eamodio.gitlens). Supercharge the Git capabilities. 
   - [Markdown All in One](https://marketplace.visualstudio.com/items?itemName=yzhang.markdown-all-in-one). Create the ToC for an article.
-- [Drawing tool: diagrams.net](https://www.diagrams.net/)
+- [Drawing tool: diagrams.net](https://www.diagrams.net/)

documentation/dataplane/README.md

@@ -14,4 +14,4 @@ This folder contains DASH data plane design and requirements documents.
 ## Requirements
 
 | Document                                               | Description                                |
-| ------------------------------------------------------ | ------------------------------------------ |
+| ------------------------------------------------------ | ------------------------------------------ |

documentation/dataplane/dash-config-schema-json.md

@@ -734,4 +734,4 @@ last update: 04/12/2022
 }
 
 
-```
+```

documentation/encrypt-gw-service/README.md

@@ -11,4 +11,4 @@ This folder contains DASH Encryption Gateway Service design and requirements doc
 ## Requirements
 
 | Document                                               | Description                                |
-| ------------------------------------------------------ | ------------------------------------------ |
+| ------------------------------------------------------ | ------------------------------------------ |

documentation/express-route-service/README.md

@@ -11,4 +11,4 @@ This folder contains DASH Express Route Gateway Service design and requirements
 ## Requirements
 
 | Document                                               | Description                                |
-| ------------------------------------------------------ | ------------------------------------------ |
+| ------------------------------------------------------ | ------------------------------------------ |

documentation/general/README.md

@@ -20,4 +20,4 @@ This folder contains DASH general design and requirements documents.
 | Document                                               | Description                                |
 | ---------------------------------------------------------------------------------- | ------------------------------------------ |
 | [dash-general-compliance-requirements.md](dash-general-compliance-requirements.md) | DASH General Compliance Requirements    |
-| [program-scale-testing-requirements-draft.md](program-scale-testing-requirements-draft.md) | DASH scale and performance requirements   |
+| [program-scale-testing-requirements-draft.md](program-scale-testing-requirements-draft.md) | DASH scale and performance requirements   |