New release

.github/workflows/ci.yml

@@ -61,9 +61,9 @@ jobs:
       - name: Wait
         run: |
           export CID=`cat ${LANGUAGE}/${FRAMEWORK}/cid-${ENGINE}.txt`
-          until [ "`docker inspect -f {{.State.Health.Status}} ${CID}`" = "healthy" ]; do 
+          until [ "`docker inspect -f {{.State.Health.Status}} ${CID}`" = "healthy" ]; do
             echo "Wait for container to be healthy"
-            sleep 1 
+            sleep 1
           done
         timeout-minutes: 2
         env:

.tasks/collect.rake

@@ -32,8 +32,8 @@ task :collect do
   hostname = ENV.fetch('HOSTNAME')
   engine = ENV.fetch('ENGINE')
 
-  `wrk -H 'Connection: keep-alive' -d 5s -c 8 --timeout 8 -t #{threads} http://#{hostname}:3000`
-  `wrk -H 'Connection: keep-alive' -d #{duration}s -c 256 --timeout 8 -t #{threads} http://#{hostname}:3000`
+  `wrk -H 'Connection: close' -d 5s -c 8 --timeout 8 -t #{threads} http://#{hostname}:3000`
+  `wrk -H 'Connection: close' -d #{duration}s -c 256 --timeout 8 -t #{threads} http://#{hostname}:3000`
 
   db = PG.connect(database)
 
@@ -65,7 +65,7 @@ task :collect do
       concurrency_level_id = res.first['id']
 
       command = format(
-        "wrk -H 'Connection: keep-alive' --connections %<concurrency>s --threads %<threads>s --duration %<duration>s --timeout 1 --script %<pipeline>s http://%<hostname>s:3000#{uri}", concurrency:, threads:, duration:, pipeline: PIPELINE[method.to_sym], hostname:
+        "wrk -H 'Connection: close' --connections %<concurrency>s --threads %<threads>s --duration %<duration>s --timeout 1 --script %<pipeline>s http://%<hostname>s:3000#{uri}", concurrency:, threads:, duration:, pipeline: PIPELINE[method.to_sym], hostname:
       )
 
       Open3.popen3(command) do |_, stdout, stderr|

CODE_OF_CONDUCT.md

@@ -2,45 +2,73 @@
 
 ## Our pledge
 
-In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, gender identity and expression, level of
+experience, nationality, personal appearance, race, religion, or sexual identity
+and orientation.
 
 ## Our standards
 
-Examples of behavior that contributes to creating a positive environment include:
+Examples of behavior that contributes to creating a positive environment
+include:
 
-* Using welcoming and inclusive language
-* Being respectful of differing viewpoints and experiences
-* Gracefully accepting constructive criticism
-* Focusing on what is best for the community
-* Showing empathy towards other community members
+- Using welcoming and inclusive language
+- Being respectful of differing viewpoints and experiences
+- Gracefully accepting constructive criticism
+- Focusing on what is best for the community
+- Showing empathy towards other community members
 
 Examples of unacceptable behavior by participants include:
 
-* The use of sexualized language or imagery and unwelcome sexual attention or advances
-* Trolling, insulting/derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or electronic address, without explicit permission
-* Other conduct which could reasonably be considered inappropriate in a professional setting
+- The use of sexualized language or imagery and unwelcome sexual attention or
+  advances
+- Trolling, insulting/derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+- Other conduct which could reasonably be considered inappropriate in a
+  professional setting
 
 ## Our responsibilities
 
-Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
 
-Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
+Project maintainers have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, or to ban temporarily or permanently any
+contributor for other behaviors that they deem inappropriate, threatening,
+offensive, or harmful.
 
 ## Scope
 
-This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
 
 ## Enforcement
 
-Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team members. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team members. The project team will review
+and investigate all complaints, and will respond in a way that it deems
+appropriate to the circumstances. The project team is obligated to maintain
+confidentiality with regard to the reporter of an incident. Further details of
+specific enforcement policies may be posted separately.
 
-Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
 
 ## Attribution
 
-This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
 
 <p align="center" style="margin:25px 0 10px">
   :zap:

CONTRIBUTING.md

@@ -2,24 +2,25 @@
 
 Contributions of any kind a :heart: accepted
 
-+ Adding new frameworks
-+ Fix some frameworks
-+ Update dependencies
-+ Discuss best practices
+- Adding new frameworks
+- Fix some frameworks
+- Update dependencies
+- Discuss best practices
 
 ## Adding a framework
 
-+ All frameworks **SHOULD** follow this rules :
+- All frameworks **SHOULD** follow this rules :
 
 | HTTP   | Route       | Status code | Response body         |
 | ------ | ----------- | ----------- | --------------------- |
 | `GET`  | `/`         | `200`       | **Empty**             |
 | `GET`  | `/user/:id` | `200`       | **id** given as param |
-| `POST` | `/user`     | `200`       | **Empty**
+| `POST` | `/user`     | `200`       | **Empty**             |
 
-+ All framework **SHOULD** contain a `Dockerfile`
+- All framework **SHOULD** contain a `Dockerfile`
 
-+ All framework **SHOULD** be referenced in :
-   + `Makefile`, a target group for the language, and a target for the framework
-   + `neph.yaml`, a target group for the language, and a target for the framework
-   + `benchmarker.cr`, a hash for language containing all frameworks an repository information
+- All framework **SHOULD** be referenced in :
+  - `Makefile`, a target group for the language, and a target for the framework
+  - `neph.yaml`, a target group for the language, and a target for the framework
+  - `benchmarker.cr`, a hash for language containing all frameworks an
+    repository information

README.md

@@ -1,31 +1,38 @@
-+ `ruby`, all tools are made in `ruby`
+- `ruby`, all tools are made in `ruby`
+
 ```sh
 sudo dnf install ruby
 ```
-+ `wrk`, results are collected using `wrk`
+
+- `wrk`, results are collected using `wrk`
+
 ```sh
- cd `mktemp -d` && git clone https://github.com/wg/wrk -b 4.2.0 . && make && sudo mv cp /usr/bin
+cd `mktemp -d` && git clone https://github.com/wg/wrk -b 4.2.0 . && make && sudo mv cp /usr/bin
 ```
-+ `postgresql`, results are stored in `postgresql`
+
+- `postgresql`, results are stored in `postgresql`
+
 ```sh
 sudo dn install postgresql{,-server}
 ```
-+ `docker`, each implementation is implemented in an isolated **container**
-+ `jq`, processing `docker` metadata
-+ `docker-machine` if you are on `macos`
+
+- `docker`, each implementation is implemented in an isolated **container**
+- `jq`, processing `docker` metadata
+- `docker-machine` if you are on `macos`
 
 ## Usage
 
-+ Setup
+- Setup
 
 ```
 bundle install
 bundle exec rake config
 ```
 
-+ Build
+- Build
 
-:warning: On `macos`, you need to use `docker-machine` to allow `docker` usage for each framework :warning:
+:warning: On `macos`, you need to use `docker-machine` to allow `docker` usage
+for each framework :warning:
 
 ```
 docker-machine rm default --force
@@ -36,10 +43,10 @@ eval $(docker-machine env default)
 ```
 export FRAMEWORK=php/lumen
 cd ${FRAMEWORK} 
-make -f .Makefile build 
+make -f .Makefile build
 ```
 
-+ Run
+- Run
 
 ```
 make -f ${FRAMEWORK}/.Makefile collect

clojure/luminus/resources/docs/docs.md

@@ -4,9 +4,9 @@ This page will help guide you through the first steps of building your site.
 
 <p class="title is-5">Why are you seeing this page?</p>
 
-The `home-routes` handler in the `luminus.routes.home` namespace
-defines the route that invokes the `home-page` function whenever an HTTP
-request is made to the `/` URI using the `GET` method.
+The `home-routes` handler in the `luminus.routes.home` namespace defines the
+route that invokes the `home-page` function whenever an HTTP request is made to
+the `/` URI using the `GET` method.
 
 ```
 (defroutes home-routes
@@ -23,25 +23,27 @@ to render the HTML content:
     "home.html" {:docs (-> "docs/docs.md" io/resource slurp)}))
 ```
 
-The `render` function will render the `home.html` template found in the `resources/templates`
-folder using a parameter map containing the `:docs` key. This key points to the
-contents of the `resources/docs/docs.md` file containing these instructions.
+The `render` function will render the `home.html` template found in the
+`resources/templates` folder using a parameter map containing the `:docs` key.
+This key points to the contents of the `resources/docs/docs.md` file containing
+these instructions.
 
-The HTML templates are written using [Selmer](https://github.com/yogthos/Selmer) templating engine.
+The HTML templates are written using [Selmer](https://github.com/yogthos/Selmer)
+templating engine.
 
 ```
 <div class="content">
   {{docs|markdown}}
 </div>
 ```
 
-<a class="level-item button" href="http://www.luminusweb.net/docs/html_templating.md">learn more about HTML templating »</a>
-
-
+<a class="level-item button" href="http://www.luminusweb.net/docs/html_templating.md">learn
+more about HTML templating »</a>
 
 <p class="title is-5">Organizing the routes</p>
 
-The routes are aggregated and wrapped with middleware in the `luminus.handler` namespace:
+The routes are aggregated and wrapped with middleware in the `luminus.handler`
+namespace:
 
 ```
 (defstate app
@@ -57,30 +59,35 @@ The routes are aggregated and wrapped with middleware in the `luminus.handler` n
                        :title "page not found"}))))))
 ```
 
-The `app` definition groups all the routes in the application into a single handler.
-A default route group is added to handle the `404` case.
+The `app` definition groups all the routes in the application into a single
+handler. A default route group is added to handle the `404` case.
 
-<a class="level-item button" href="http://www.luminusweb.net/docs/routes.md">learn more about routing »</a>
+<a class="level-item button" href="http://www.luminusweb.net/docs/routes.md">learn
+more about routing »</a>
 
-The `home-routes` are wrapped with two middleware functions. The first enables CSRF protection.
-The second takes care of serializing and deserializing various encoding formats, such as JSON.
+The `home-routes` are wrapped with two middleware functions. The first enables
+CSRF protection. The second takes care of serializing and deserializing various
+encoding formats, such as JSON.
 
 <p class="title is-5">Managing your middleware</p>
 
-Request middleware functions are located under the `luminus.middleware` namespace.
-
-This namespace is reserved for any custom middleware for the application. Some default middleware is
-already defined here. The middleware is assembled in the `wrap-base` function.
-
-Middleware used for development is placed in the `luminus.dev-middleware` namespace found in
-the `env/dev/clj/` source path.
-
-<a class="level-item button" href="http://www.luminusweb.net/docs/middleware.md">learn more about middleware »</a>
+Request middleware functions are located under the `luminus.middleware`
+namespace.
 
+This namespace is reserved for any custom middleware for the application. Some
+default middleware is already defined here. The middleware is assembled in the
+`wrap-base` function.
 
+Middleware used for development is placed in the `luminus.dev-middleware`
+namespace found in the `env/dev/clj/` source path.
 
+<a class="level-item button" href="http://www.luminusweb.net/docs/middleware.md">learn
+more about middleware »</a>
 
 <p class="title is-5">Need some help?</p>
 
 Visit the [official documentation](http://www.luminusweb.net/docs) for examples
-on how to accomplish common tasks with Luminus. The `#luminus` channel on the [Clojurians Slack](http://clojurians.net/) and [Google Group](https://groups.google.com/forum/#!forum/luminusweb) are both great places to seek help and discuss projects with other users.
+on how to accomplish common tasks with Luminus. The `#luminus` channel on the
+[Clojurians Slack](http://clojurians.net/) and
+[Google Group](https://groups.google.com/forum/#!forum/luminusweb) are both
+great places to seek help and discuss projects with other users.

clojure/luminus/resources/html/about.html

@@ -1,4 +1,2 @@
-{% extends "base.html" %}
-{% block content %}
-  <img src="/img/warning_clojure.png"></img>
-{% endblock %}
+{% extends "base.html" %} {% block content %}
+<img src="/img/warning_clojure.png"></img> {% endblock %}