fixing tags warnings

.github/workflows/gh-pages.yml

@@ -30,9 +30,6 @@ jobs:
       - run: npm install
       - run: bundle install
       - run: bundle exec jekyll build
-      - run: bundle exec jekyll algolia
-        env:
-          ALGOLIA_API_KEY: ${{ secrets.ALGOLIA_API_KEY }}
       - uses: actions/upload-pages-artifact@v3
   deploy:
     environment:

Gemfile

@@ -6,7 +6,6 @@ gem 'jekyll-postcss'
 gem 'jekyll-paginate-v2'
 gem 'jekyll-timeago'
 gem 'jekyll-sitemap'
-gem 'jekyll-algolia'
 gem 'jekyll-seo-tag'
 gem 'jekyll-tagging'
 

Gemfile.lock

@@ -3,54 +3,42 @@ GEM
   specs:
     addressable (2.8.7)
       public_suffix (>= 2.0.2, < 7.0)
-    algolia_html_extractor (2.6.4)
-      json (~> 2.0)
-      nokogiri (~> 1.10)
-    algoliasearch (1.27.5)
-      httpclient (~> 2.8, >= 2.8.3)
-      json (>= 1.5.1)
     colorator (1.1.0)
     concurrent-ruby (1.3.3)
     em-websocket (0.5.3)
       eventmachine (>= 0.12.9)
       http_parser.rb (~> 0)
     eventmachine (1.2.7)
     ffi (1.17.0)
-    filesize (0.2.0)
     forwardable-extended (2.6.0)
+    google-protobuf (3.23.4-x86_64-darwin)
+    google-protobuf (3.23.4-x86_64-linux)
     http_parser.rb (0.8.0)
-    httpclient (2.8.3)
     i18n (1.14.5)
       concurrent-ruby (~> 1.0)
-    jekyll (3.9.5)
+    jekyll (4.3.3)
       addressable (~> 2.4)
       colorator (~> 1.0)
       em-websocket (~> 0.5)
-      i18n (>= 0.7, < 2)
-      jekyll-sass-converter (~> 1.0)
+      i18n (~> 1.0)
+      jekyll-sass-converter (>= 2.0, < 4.0)
       jekyll-watch (~> 2.0)
-      kramdown (>= 1.17, < 3)
+      kramdown (~> 2.3, >= 2.3.1)
+      kramdown-parser-gfm (~> 1.0)
       liquid (~> 4.0)
-      mercenary (~> 0.3.3)
+      mercenary (>= 0.3.6, < 0.5)
       pathutil (~> 0.9)
-      rouge (>= 1.7, < 4)
+      rouge (>= 3.0, < 5.0)
       safe_yaml (~> 1.0)
-    jekyll-algolia (1.7.1)
-      algolia_html_extractor (~> 2.6)
-      algoliasearch (~> 1.26)
-      filesize (~> 0.1)
-      jekyll (>= 3.6, < 5.0)
-      json (~> 2.0)
-      nokogiri (~> 1.6)
-      progressbar (~> 1.9)
-      verbal_expressions (~> 0.1.5)
+      terminal-table (>= 1.8, < 4.0)
+      webrick (~> 1.7)
     jekyll-feed (0.17.0)
       jekyll (>= 3.7, < 5.0)
     jekyll-paginate-v2 (3.0.0)
       jekyll (>= 3.0, < 5.0)
     jekyll-postcss (0.5.0)
-    jekyll-sass-converter (1.5.2)
-      sass (~> 3.4)
+    jekyll-sass-converter (3.0.0)
+      sass-embedded (~> 1.54)
     jekyll-seo-tag (2.8.0)
       jekyll (>= 3.8, < 5.0)
     jekyll-sitemap (1.4.0)
@@ -61,7 +49,6 @@ GEM
       mini_i18n (>= 0.8.0)
     jekyll-watch (2.2.1)
       listen (~> 3.0)
-    json (2.7.2)
     kramdown (2.4.0)
       rexml
     kramdown-parser-gfm (1.1.0)
@@ -70,40 +57,35 @@ GEM
     listen (3.9.0)
       rb-fsevent (~> 0.10, >= 0.10.3)
       rb-inotify (~> 0.9, >= 0.9.10)
-    mercenary (0.3.6)
+    mercenary (0.4.0)
     mini_i18n (0.9.0)
-    nokogiri (1.13.10-x86_64-darwin)
-      racc (~> 1.4)
-    nokogiri (1.13.10-x86_64-linux)
-      racc (~> 1.4)
     nuggets (1.6.1)
     pathutil (0.16.2)
       forwardable-extended (~> 2.6)
-    progressbar (1.13.0)
     public_suffix (5.1.1)
-    racc (1.8.0)
+    rake (13.2.1)
     rb-fsevent (0.11.2)
     rb-inotify (0.11.1)
       ffi (~> 1.0)
     rexml (3.3.1)
       strscan
     rouge (3.30.0)
     safe_yaml (1.0.5)
-    sass (3.7.4)
-      sass-listen (~> 4.0.0)
-    sass-listen (4.0.0)
-      rb-fsevent (~> 0.9, >= 0.9.4)
-      rb-inotify (~> 0.9, >= 0.9.7)
+    sass-embedded (1.58.3)
+      google-protobuf (~> 3.21)
+      rake (>= 10.0.0)
     strscan (3.1.0)
-    verbal_expressions (0.1.5)
+    terminal-table (3.0.2)
+      unicode-display_width (>= 1.1.1, < 3)
+    unicode-display_width (2.5.0)
+    webrick (1.8.1)
 
 PLATFORMS
   x86_64-darwin-23
   x86_64-linux
 
 DEPENDENCIES
   http_parser.rb (~> 0.6.0)
-  jekyll-algolia
   jekyll-feed (~> 0.12)
   jekyll-paginate-v2
   jekyll-postcss

_posts/2015-05-13-JAX-RS-client-api.md

@@ -2,7 +2,7 @@
 layout: post
 title: How to write JAX-RS Client fast
 author: lukasz.przybyla
-tags: [REST, client, JAX-RS]
+tags: [rest, client, JAX-RS]
 ---
 According to best practices, when developing a service, one should provide a client for it.
 If your service API undergoes changes quite often, constant client updates may become troublesome.

_posts/2015-07-09-testing-server-faults-with-Wiremock.md

@@ -2,7 +2,7 @@
 layout: post
 title: Testing server faults with Wiremock
 author: filip.marszelewski
-tags: [wiremock, TDD, testing, integration tests, fault injection]
+tags: [wiremock, tdd, testing, integration tests, fault injection]
 ---
 
 SOA (Service Oriented Architecture) as a modern approach to build distributed enterprise applications gives us many benefits,

_posts/2015-12-10-mini-rant-v-for-viable.md

@@ -2,7 +2,7 @@
 layout: post
 title: Mini rant: V for Viable
 author: michal.kosmulski
-tags: [MVP, Minimum Viable Product, project management, product development, agile]
+tags: [mvp, minimum viable product, project management, product development, agile]
 ---
 Building a [Minimum Viable Product (MVP)](http://en.wikipedia.org/wiki/Minimum_viable_product) is a method of developing new products
 by validating hypotheses using feedback from real users as soon as possible. This is supposed to reduce risk and to ensure a good

_posts/2016-06-20-kotlin-null-safety-part1.md

@@ -2,7 +2,7 @@
 layout: post
 title: Kotlin null safety and its performance considerations -- part 1
 author: konrad.kaminski
-tags: [java, kotlin, jvm, performance, null, x86, x64, assembler]
+tags: [java, kotlin, JVM, performance, null, x86, x64, assembler]
 ---
 
 [Kotlin](http://kotlinlang.org) may seem like a new kid on the block — itʼs been officially released only in [February](http://blog.jetbrains.com/kotlin/2016/02/kotlin-1-0-released-pragmatic-language-for-jvm-and-android/).

_posts/2016-10-24-self-contained-UI-tests-for-ios-applications.md

@@ -2,7 +2,7 @@
 layout: post
 title: Self-contained UI tests for iOS applications
 author: pawel.ustaborowicz
-tags: [iOS, testing, UI testing, test automation, WireMock, Xcode]
+tags: [ios, testing, ui testing, test automation, wiremock, xcode]
 ---
 We’re all familiar with
 [TDD](https://en.wikipedia.org/wiki/Test-driven_development), or at least write unit tests for our software,

_posts/2016-12-19-deep-learning-for-frame-detection.md

@@ -2,7 +2,7 @@
 layout: post
 title: Deep learning for frame detection in product images
 author: tomasz.bartczak
-tags: [ML, Machine Learning, Deep Learning]
+tags: [ml, machine learning, deep learning]
 ---
 At [Allegro](https://allegro.tech) we are faced with a technical challenge: how to recognize whether a given image
 (a product thumbnail) shows just a product itself. One of the things that we would like to detect is when the product

_posts/2016-12-29-MongoDB-schema.md

@@ -2,7 +2,7 @@
 layout: post
 title: Responsible work with MongoDB
 author: [tomasz.fijalkowski]
-tags: [MongoDB, NoSQL, RDBMS]
+tags: [mongodb, nosql, RDBMS]
 ---
 
 Understanding data model is sufficient to design good database schema in RDBMS (relational

_posts/2018-02-15-how-to-approach-testing-in-development-process.md

@@ -2,7 +2,7 @@
 layout: post
 title: How to approach testing in development process?
 author: wojciech.lizakowski
-tags: [manual tests, tech, iOS, testing, UI testing, test automation, release process, test]
+tags: [manual tests, tech, ios, testing, ui testing, test automation, release process, test]
 ---
 
 Application release process, or in fact software development process, as a release is the final stage of application

_posts/2018-04-24-Spring-WebMvcTest-with-Spock.md

@@ -2,7 +2,7 @@
 layout: post
 title: Spring @WebMvcTest with Spock Framework
 author: [rafal.glowinski]
-tags: [Spring Boot, Spock, WebMvcTest, java, testing]
+tags: [spring boot, spock, WebMvcTest, java, testing]
 ---
 
 Spring is one of the most popular JVM-targeted frameworks. One of the reasons why it has become so popular is writing tests.

_posts/2018-05-07-a-comedy-of-errors-debugging-java-memory-leaks.md

@@ -2,7 +2,7 @@
 layout: post
 title: A comedy of errors. Debugging Java memory leaks.
 author: [michal.kosmulski]
-tags: [jvm, java, memory, leak, resources, garbage collection, gc]
+tags: [JVM, java, memory, leak, resources, garbage-collection, gc]
 ---
 
 We all make errors, but some errors seem so ridiculous we wonder how anyone, let alone we ourselves, could have done such a thing.

_posts/2020-01-27-spring-boot-services-configuration-on-gcp.md

@@ -2,11 +2,11 @@
 layout: post
 title: How to manage Spring Boot services configuration on GCP
 author: karol.kuc
-tags: [java, cloud, gcp, spring-boot]
+tags: [java, cloud, gcp, spring boot]
 ---
 
 Configuration management is one of the key challenges you have to face when you decide to build an application as a distributed system based on microservices
-deployed to the Cloud. There are multiple ways of addressing different aspects of this problem, using several tools such as [Spring Cloud Config Server](https://cloud.spring.io/spring-cloud-config/reference/html/) 
+deployed to the Cloud. There are multiple ways of addressing different aspects of this problem, using several tools such as [Spring Cloud Config Server](https://cloud.spring.io/spring-cloud-config/reference/html/)
 or [Hashicorp Consul](https://cloud.spring.io/spring-cloud-consul/reference/html/). However, this article will focus on the tools that Google Cloud Platform offers
 out of the box. The approaches mentioned should be seen as complementary rather than mutually exclusive.
 
@@ -16,31 +16,31 @@ The [Runtime Configurator](https://cloud.google.com/deployment-manager/runtime-c
 related to application state management as well as application configuration management. In this article, I will dig into the latter. The Runtime Configurator features include:
 * configuring services dynamically,
 * communicating changes in application state between services,
-* notifying about changes to application data ([Watching variable state changes](https://cloud.google.com/deployment-manager/runtime-configurator/watching-a-variable) 
+* notifying about changes to application data ([Watching variable state changes](https://cloud.google.com/deployment-manager/runtime-configurator/watching-a-variable)
 and creating [Waiter resources](https://cloud.google.com/deployment-manager/runtime-configurator/creating-a-waiter)
 are beyond the scope of this article, please consult the corresponding documentation),
 * sharing information between multiple tiers of services.
 
 It can be used via the [gcloud console utility](https://cloud.google.com/sdk/gcloud/), the Deployment Manager or as a Standalone API and lets you centralize
-configuration and reuse it between different GCP resources such as 
+configuration and reuse it between different GCP resources such as
 Google Compute Engine, Google App Engine, Google Kubernetes Engine or Google Cloud Functions.
 
 ### State management: why should I use Runtime Configurator?
 
 The official [GCP documentation](https://cloud.google.com/deployment-manager/runtime-configurator/) provides an example as follows:
 
-"For example, imagine a scenario where you have a cluster of nodes that run 
-a startup procedure. During startup, you can configure your nodes to report their status 
+"For example, imagine a scenario where you have a cluster of nodes that run
+a startup procedure. During startup, you can configure your nodes to report their status
 to the Runtime Configurator, and then have another application query the Runtime Configurator and run specific tasks based on the status of the nodes.
- 
-The Runtime Configurator also offers a Watcher service and a Waiter service. The Watcher service watches a specific key pair 
+
+The Runtime Configurator also offers a Watcher service and a Waiter service. The Watcher service watches a specific key pair
 and returns when the value of the key pair changes, while the Waiter service waits for a specific end condition and returns a response once that end condition has been met."
 
 ### Managing configuration: basic terms
 
 The Runtime Configurator is built on top of the idea of a config resource. It is an abstraction that can be seen
-as a hierarchical list of configuration variables, which may separate the configuration variables 
-environment-wise (prod, dev, test) and/or tier-wise (frontend, backend). 
+as a hierarchical list of configuration variables, which may separate the configuration variables
+environment-wise (prod, dev, test) and/or tier-wise (frontend, backend).
 A configuration is local to a GCP project so there will be no interference between services managed by a GCP account (provided you deploy services as separate projects).
 Variables are simple key-value pairs that can be referenced in your Spring Boot service config files as environment variables.
 The variable key has the following format, and is local to a config ID (the config resource unique name), which, as mentioned, is on its own
@@ -120,7 +120,7 @@ consult [this link](https://cloud.google.com/deployment-manager/runtime-configur
 This is pretty much it from the GCP perspective, as you can see the API of the runtime-configuration tool is straightforward and intuitive.
 Let's now focus on how to set up a Spring Boot app to use the configuration we have created.
 ## Accessing GCP config from Spring Boot
-Set the active application profile in the main appengine/app.yaml file so that Spring Boot can pick up the right config for a given environment. 
+Set the active application profile in the main appengine/app.yaml file so that Spring Boot can pick up the right config for a given environment.
 Remember that the profile name must be part of the config ID you created on GCP in the following form:
 ```
   config-name_profile-name eg cart-db_dev
@@ -132,9 +132,9 @@ runtime: java
 env: flex
 runtime_config:
     dk: openjdk8
-**********************************                                 
-env_variables:                      
-    SPRING_PROFILES_ACTIVE: "dev"      
+**********************************
+env_variables:
+    SPRING_PROFILES_ACTIVE: "dev"
 **********************************
 handlers:
     - url: /.*
@@ -170,17 +170,17 @@ spring:
        name: cart-db
        profile: dev
 ```
-In the build.gradle file you will need the following plugin and dependencies: 
+In the build.gradle file you will need the following plugin and dependencies:
 ```
-buildscript { 
+buildscript {
     ext {
         ...
         springBootVersion = '2.1.2.RELEASE'
         ...
     }
     dependencies {
         ...
-        classpath group: 'com.google.cloud.tools', name: 'appengine-gradle-plugin', version: '2.0.1' 
+        classpath group: 'com.google.cloud.tools', name: 'appengine-gradle-plugin', version: '2.0.1'
     }
         ...
 }
@@ -191,12 +191,12 @@ dependencies {
     implementation group: 'org.springframework.cloud', name: 'spring-cloud-gcp-starters', version: '1.1.1.RELEASE'
     implementation group: 'org.springframework.cloud', name: 'spring-cloud-gcp-starter-config', version: '1.1.0.RC2'
 }
-dependencyManagement { 
-    imports { 
-        ... 
+dependencyManagement {
+    imports {
+        ...
         mavenBom "org.springframework.cloud:spring-cloud-dependencies:${springCloudVersion}"
         ...
-    }    
+    }
 }
 ```
 And then use the DBUSER config variable in the corresponding src/main/application-dev.yml:
@@ -209,7 +209,7 @@ spring:
       ...
 ```
 
-Now the configuration provided should be picked up upon application startup. If you update the values 
+Now the configuration provided should be picked up upon application startup. If you update the values
 while the application is running, you must either refresh the config via [Spring Boot Actuator](https://docs.spring.io/spring-boot/docs/current/reference/html/production-ready-features.html#production-ready) or restart the service.
 ## Further readings
 For further information about Spring Cloud GCP Runtime Config, consult this [article](https://spring.io/blog/2018/09/03/bootiful-gcp-runtime-configuration-with-spring-cloud-gcp-runtime-config-5-8)
@@ -219,17 +219,17 @@ which also looks into quirks and features of using Runtime Configurator with Goo
 ## Miscellaneous
 ### Limitations, quotas, access control
 For quotas and limitations please consult the [docs](https://cloud.google.com/deployment-manager/quotas#runtime_configurator). Currently, it's 4MB data per project and corresponding query per minute limits for specific API queries.
-[Runtime Configurator Access Control](https://cloud.google.com/deployment-manager/runtime-configurator/access-control) via IAM ([Identity Access Management](https://cloud.google.com/iam/docs/overview)) roles and permissions of a Service Account are not in the scope of this article. 
+[Runtime Configurator Access Control](https://cloud.google.com/deployment-manager/runtime-configurator/access-control) via IAM ([Identity Access Management](https://cloud.google.com/iam/docs/overview)) roles and permissions of a Service Account are not in the scope of this article.
 ### Important
 You must take into consideration that the beta Runtime Configuration tool is in a pre-release state and might undergo breaking API changes and/or have limited support.
 
 ### Summary
-As I have already mentioned, GCP Runtime Configurator 
-should not be seen as an alternative to tools such as Spring Cloud Config Server 
+As I have already mentioned, GCP Runtime Configurator
+should not be seen as an alternative to tools such as Spring Cloud Config Server
 or Hashicorp Consul. You can live without one or the other
-but you can also use both of them. 
-An example of such separation of concerns might be limiting the use of GCP RC to configuration shared between different GCP areas eg. 
-Cloud Functions and App Engine. You could then let an independent config server, running in an App Engine container, manage the configuration 
+but you can also use both of them.
+An example of such separation of concerns might be limiting the use of GCP RC to configuration shared between different GCP areas eg.
+Cloud Functions and App Engine. You could then let an independent config server, running in an App Engine container, manage the configuration
 which is used exclusively by services also running on App Engine. It is also relevant that any
 piece of infrastructure that you deploy on your own as part of the system, such as a config server or a discovery server, is then yours to monitor and maintain,
-which does not apply to tools offered by Google Cloud Platform out of the box. 
+which does not apply to tools offered by Google Cloud Platform out of the box.

_posts/2020-04-01-machine-learning-plus-agile-manifesto.md

@@ -2,7 +2,7 @@
 layout: post
 title: "Machine Learning + Agile Manifesto = ?"
 author: zbigniew.barczyk
-tags: [machine_learning, agile, soft_skills]
+tags: [machine learning, agile, soft skills]
 ---
 
 > This post was published on April 1st, 2020, and should not be taken too seriously.

_posts/2021-03-05-state-machines-made-easy.md

@@ -2,7 +2,7 @@
 layout: post
 title: Finite-state machines made easy
 author: [tymon.felski]
-tags: [tech, dotnet, state_machine, allegro_pay]
+tags: [tech, dotnet, state machine, allegro-pay]
 ---
 
 Coordinating complex processes, both business and technical, can be a challenging issue in a distributed system.