aports/community/ruby-eventmachine/remove-debug-puts-from-connection.patch
Jakub Jirutka 6ba486fbe4 community/ruby-eventmachine: vendor patches linked from GitHub
I don't know how it's possible, but checksum of
fixes-for-process-status-in-ruby-3.patch doesn't match. It seems that
commit patches on GitHub are really somehow unstable. :(

Please note that I added the Patch-Source header to all downloaded
patches, that's why they *all* have a different checksum.
2022-07-29 16:37:20 +02:00

34 lines
1.5 KiB
Diff

Patch-Source: https://github.com/eventmachine/eventmachine/commit/681bc4e995a3c860d08a22c48723eef2b7719ae4.patch
--
From 681bc4e995a3c860d08a22c48723eef2b7719ae4 Mon Sep 17 00:00:00 2001
From: Aaron Stone <aaron@serendipity.cx>
Date: Sun, 1 Mar 2020 11:17:00 -0800
Subject: [PATCH] Remove debug puts from base class of EM::Connection (#911)
---
lib/em/connection.rb | 4 ----
1 file changed, 4 deletions(-)
diff --git a/lib/em/connection.rb b/lib/em/connection.rb
index b5f8b0ad7..f2362cecd 100644
--- a/lib/em/connection.rb
+++ b/lib/em/connection.rb
@@ -100,9 +100,6 @@ def post_init
# in your redefined implementation of receive_data. For a better understanding
# of this, read through the examples of specific protocol handlers in EventMachine::Protocols
#
- # The base-class implementation (which will be invoked only if you didn't override it in your protocol handler)
- # simply prints incoming data packet size to stdout.
- #
# @param [String] data Opaque incoming data.
# @note Depending on the protocol, buffer sizes and OS networking stack configuration, incoming data may or may not be "a complete message".
# It is up to this handler to detect content boundaries to determine whether all the content (for example, full HTTP request)
@@ -114,7 +111,6 @@ def post_init
# @see #send_data
# @see file:docs/GettingStarted.md EventMachine tutorial
def receive_data data
- puts "............>>>#{data.length}"
end
# Called by EventMachine when the SSL/TLS handshake has