From 2ddf0aeb204d754636ded6ff2be4e2dcfc3ee421 Mon Sep 17 00:00:00 2001 From: Piotr Parczewski Date: Tue, 28 Mar 2023 14:08:42 +0200 Subject: [PATCH] Replace invisible unicode chars They're believed to have no special meaning and were put by accident. TrivialFix Change-Id: I66ea5711810ed0060cf89192a780bfcc92e79770 --- docker/base/Dockerfile.j2 | 4 ++-- specs/logging-with-heka.rst | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docker/base/Dockerfile.j2 b/docker/base/Dockerfile.j2 index 6e50378f10..bb62bc4ea9 100644 --- a/docker/base/Dockerfile.j2 +++ b/docker/base/Dockerfile.j2 @@ -118,9 +118,9 @@ RUN rm -f /etc/rpm/macros.image-language-conf \ {%- if not loop.last %} \{% endif %} {% endfor -%} -{% for cmd in rpm_setup %} +{% for cmd in rpm_setup %} {{ cmd }} -{% endfor %} +{% endfor %} {% block base_centos_repo_overrides_post_rpm %}{% endblock %} diff --git a/specs/logging-with-heka.rst b/specs/logging-with-heka.rst index 8087a6a41a..7b863db173 100644 --- a/specs/logging-with-heka.rst +++ b/specs/logging-with-heka.rst @@ -256,7 +256,7 @@ An alternative to this proposal involves using Logstash in a centralized way as done in [1]. Another alternative would be to execute Logstash on each cluster node, as this -spec proposes with Heka. But this would mean running a JVM on each cluster +spec proposes with Heka. But this would mean running a JVM on each cluster node, and using Redis as a centralized queue. Also, as described above, we initially considered relying on services writing