From a958df50bd28b91a94da9f80df17095b61121fa0 Mon Sep 17 00:00:00 2001
From: Artur Trzop <arturtrzop@gmail.com>
Date: Mon, 20 Jan 2025 22:23:37 +0100
Subject: [PATCH 1/2] update(RSpec docs): update the backtrace debugging
 example for hanging CI node

---
 docusaurus/docs/ruby/troubleshooting.mdx | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)

diff --git a/docusaurus/docs/ruby/troubleshooting.mdx b/docusaurus/docs/ruby/troubleshooting.mdx
index 5ead558e..47dca1be 100644
--- a/docusaurus/docs/ruby/troubleshooting.mdx
+++ b/docusaurus/docs/ruby/troubleshooting.mdx
@@ -105,6 +105,21 @@ Start logging 2 detected threads.
 Use the following backtrace(s) to find the line of code that got stuck if the CI node hung and terminated your tests.
 How to read the backtrace: https://knapsackpro.com/perma/ruby/backtrace-debugging
 
+Hanging specs in the main thread:
+# highlight-start
+knapsack_pro-ruby/spec_integration/b_spec.rb:7:in `kill'
+# highlight-end
+knapsack_pro-ruby/spec_integration/b_spec.rb:7:in `block (3 levels) in <top (required)>'
+
+
+Non-main thread inspect: #<Thread:0x000000011e18f6e0 spec_integration/a_spec.rb:5 sleep>
+Hanging specs in non-main thread:
+# highlight-start
+knapsack_pro-ruby/spec_integration/a_spec.rb:6:in `sleep'
+# highlight-end
+knapsack_pro-ruby/spec_integration/a_spec.rb:6:in `block (3 levels) in <top (required)>'
+
+
 Main thread backtrace:
 knapsack_pro-ruby/lib/knapsack_pro/runners/queue/base_runner.rb:83:in `backtrace'
 knapsack_pro-ruby/lib/knapsack_pro/runners/queue/base_runner.rb:83:in `block in log_threads'
@@ -118,6 +133,7 @@ knapsack_pro-ruby/spec_integration/b_spec.rb:7:in `block (3 levels) in <top (req
 .rvm/gems/ruby-3.3.4/gems/rspec-core-3.13.0/lib/rspec/core/example.rb:263:in `instance_exec'
 ...
 
+
 Non-main thread inspect: #<Thread:0x000000011e18f6e0 spec_integration/a_spec.rb:5 sleep>
 Non-main thread backtrace:
 # highlight-start

From 12a1c9f420f2566f5ba5552dab0e7c66906abf83 Mon Sep 17 00:00:00 2001
From: Artur Trzop <arturtrzop@gmail.com>
Date: Thu, 23 Jan 2025 14:51:10 +0100
Subject: [PATCH 2/2] Update troubleshooting.mdx

---
 docusaurus/docs/ruby/troubleshooting.mdx | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docusaurus/docs/ruby/troubleshooting.mdx b/docusaurus/docs/ruby/troubleshooting.mdx
index 47dca1be..2ae219c6 100644
--- a/docusaurus/docs/ruby/troubleshooting.mdx
+++ b/docusaurus/docs/ruby/troubleshooting.mdx
@@ -105,7 +105,7 @@ Start logging 2 detected threads.
 Use the following backtrace(s) to find the line of code that got stuck if the CI node hung and terminated your tests.
 How to read the backtrace: https://knapsackpro.com/perma/ruby/backtrace-debugging
 
-Hanging specs in the main thread:
+Running specs in the main thread:
 # highlight-start
 knapsack_pro-ruby/spec_integration/b_spec.rb:7:in `kill'
 # highlight-end
@@ -113,7 +113,7 @@ knapsack_pro-ruby/spec_integration/b_spec.rb:7:in `block (3 levels) in <top (req
 
 
 Non-main thread inspect: #<Thread:0x000000011e18f6e0 spec_integration/a_spec.rb:5 sleep>
-Hanging specs in non-main thread:
+Running specs in non-main thread:
 # highlight-start
 knapsack_pro-ruby/spec_integration/a_spec.rb:6:in `sleep'
 # highlight-end