wacktrace 1.0.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: 2d1e62ed685b7a24cbd9d1853bacead2896733ad67dd4f30128fb63e8aa0e4b2
+  data.tar.gz: fb79e2c8469e8d775a5836cfd9f1bc14a4a2810f571675fa8e26480df52e6281
+SHA512:
+  metadata.gz: 1ccc53b317b2df1b84f13e0f5a49bd5da43c9a81d68871ba9665954618696585b225648a3f0c42a728ba761ca9722cdfa7b2432ae398960a5d8a30693364061c
+  data.tar.gz: 1a1da86ca8e75f8754b79fe1d12f0025610fd46bd3040c329736b4aea70c0c894a24122959c1c4d1b6b01abe465374c4a1a1d476a45bbb30224d3a7cd12f09ca

data/.rspec

@@ -0,0 +1,3 @@
+--format documentation
+--color
+--require spec_helper

data/CHANGELOG.md

@@ -0,0 +1,5 @@
+## [Unreleased]
+
+## [0.1.0] - 2021-08-30
+
+- Initial release

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,84 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
+
+Community leaders 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, and will communicate reasons for moderation decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at kevin@kevinkuchta.com. All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior,  harassment of an individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.0,
+available at https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see the FAQ at
+https://www.contributor-covenant.org/faq. Translations are available at https://www.contributor-covenant.org/translations.

data/Gemfile

@@ -0,0 +1,11 @@
+# frozen_string_literal: true
+
+source "https://rubygems.org"
+ruby '3.0'
+
+# Specify your gem's dependencies in wacktrace.gemspec
+gemspec
+
+# gem "rake", "~> 13.0"
+
+# gem "rspec", "~> 3.0"

data/Gemfile.lock

@@ -0,0 +1,48 @@
+PATH
+  remote: .
+  specs:
+    wacktrace (1.0.0)
+
+GEM
+  remote: https://rubygems.org/
+  specs:
+    byebug (11.1.3)
+    coderay (1.1.3)
+    diff-lcs (1.4.4)
+    method_source (1.0.0)
+    pry (0.13.1)
+      coderay (~> 1.1)
+      method_source (~> 1.0)
+    pry-byebug (3.9.0)
+      byebug (~> 11.0)
+      pry (~> 0.13.0)
+    rake (13.0.6)
+    rspec (3.10.0)
+      rspec-core (~> 3.10.0)
+      rspec-expectations (~> 3.10.0)
+      rspec-mocks (~> 3.10.0)
+    rspec-core (3.10.1)
+      rspec-support (~> 3.10.0)
+    rspec-expectations (3.10.1)
+      diff-lcs (>= 1.2.0, < 2.0)
+      rspec-support (~> 3.10.0)
+    rspec-mocks (3.10.2)
+      diff-lcs (>= 1.2.0, < 2.0)
+      rspec-support (~> 3.10.0)
+    rspec-support (3.10.2)
+
+PLATFORMS
+  x86_64-darwin-19
+  x86_64-linux
+
+DEPENDENCIES
+  pry-byebug (~> 3.9)
+  rake (~> 13.0)
+  rspec (~> 3.2)
+  wacktrace!
+
+RUBY VERSION
+   ruby 3.0.0p0
+
+BUNDLED WITH
+   2.2.26

data/LICENSE.txt

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) 2021 Kevin Kuchta
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.

data/README.md

@@ -0,0 +1,167 @@
+# Wacktrace
+
+Make your stacktraces wack! Insert arbitrary content into the call stack if that is, for some reason, something you want to do. Who am I to judge?
+
+```
+# in example.rb:
+Wacktrace.add_to_stack([
+  ['Fire in the disco!', 1, '🔥🕺 '],
+  ['Fire in the Taco Bell!', 2, '🔥🌮 '],
+  ['Fire in the disco!', 3, '🔥🕺 '],
+  ['Fire in the gates of hell!', 4, '🔥😈 '],
+]) do
+  raise "High Voltage!"
+end
+```
+
+```
+$ ruby example.rb
+example.rb:25:in `block in <main>': High Voltage! (RuntimeError)
+	from /Users/kevin/.rvm/gems/ruby-3.0.0/gems/wacktrace-0.1.0/lib/wacktrace.rb:49:in `block in add_to_stack'
+	from 🔥🕺 :1:in ` Fire in the disco︕ '
+	from 🔥🌮 :2:in ` Fire in the Taco Bell︕'
+	from 🔥🕺 :3:in ` Fire in the disco︕'
+	from 🔥😈 :4:in ` Fire in the gates of hell︕'
+	from /Users/kevin/.rvm/gems/ruby-3.0.0/gems/wacktrace-0.1.0/lib/wacktrace.rb:50:in `add_to_stack'
+	from example.rb:19:in `<main>'
+```
+
+Amaze your friends! Annoy your coworkers! Ok, it's mostly that second one! But maybe someone has a good use for this, like inserting warnings into stack traces:
+
+```
+Traceback (most recent call last):
+	14: from example.rb:47:in `<main>'
+	13: from example.rb:35:in `dangerous_method'
+	12: from /Users/kevin/.rvm/gems/ruby-2.7.2/gems/wacktrace-0.1.0/lib/wacktrace.rb:60:in `add_to_stack_from_lyrics'
+	11: from /Users/kevin/.rvm/gems/ruby-2.7.2/gems/wacktrace-0.1.0/lib/wacktrace.rb:50:in `add_to_stack'
+	10: from !:in ` '
+	 9: from !:1:in `  ––––––––––––––––– WARNING︕ ––––––––––––––––––––––'
+	 8: from !:2:in ` ｜ If you hit an error here， you ＊really＊ need ｜'
+	 7: from !:3:in ` ｜ to go over to the FooBarBaz admin panel and    ｜'
+	 6: from !:4:in ` ｜ clean up the Spleem that were erroniously      ｜'
+	 5: from !:5:in ` ｜ created․  If you don’t do that， bad things    ｜'
+	 4: from !:6:in ` ｜ will happen︕                                  ｜'
+	 3: from !:7:in `  ––––––––––––––––––––––––––––––––––––––––––––––––––'
+	 2: from /Users/kevin/.rvm/gems/ruby-2.7.2/gems/wacktrace-0.1.0/lib/wacktrace.rb:49:in `block in add_to_stack'
+	 1: from example.rb:44:in `block in dangerous_method'
+example.rb:30:in `real_dangerous_method': terrible error (RuntimeError)
+```
+
+### How's it work?
+
+Sketchily! It's a set of wack stack hacks. The basic idea is that we just set up a series of methods like:
+
+```
+def a; b; end
+def b; c; end
+def c; actual_function; end
+```
+
+But to dynamically generate methods, you'd usually reach for `define_method`. Unfortunately, methods defined with `define_method` don't actually show up in call stacks because that'd be too easy. Instead we'll use `eval("def #{method_name};#{next_method_name};end")`. And, as a bonus, `eval` lets us pass in a filename and line number for stack trace purposes!
+
+But to avoid having a hundred methods in the global namespace like `baby_shark_do_do_do_do_do_do_do`, we'll `Class.new`-up a temporary class and then `instance_eval` on that.
+
+But now we're stuck with underscore-laden method names. We're not gonna stand for that kinda limitation. We're gonna reach for the sun and slap the face of god. We'll take arbitrary text and replace all the invalid characters like `"` and `@` with unicode near-equivalents like `＂` and `＠`. Because `def Cthulhu R'lyeh wgah'nagl fhtagn` isn't a valid ruby method, but the visually-identical `def Cthulhu R’lyeh wgah’nagl fhtagn` is!
+
+Other fun tricks:
+
+- Detect which direction ruby is printing stack traces today (it's newest-first on a gibbous or waxing moon, and newest-last the rest of the month)
+- Deal with duplicate method names by padding them with non-breaking-spaces
+- Prepend all methods with non-breaking spaces so ruby doesn't get confused by methods that start with capital letters
+
+## Installation
+
+Add this line to your application's Gemfile:
+
+```ruby
+gem 'wacktrace'
+```
+
+And then execute:
+
+    $ bundle install
+
+Or install it yourself as:
+
+    $ gem install wacktrace
+
+## Usage
+
+To have full(ish) control over the stack trace contents, call `add_to_stack` and give it a block. That block will be run with the lines you provide in its call stack:
+
+```
+Wacktrace.add_to_stack([
+  ['method name 1', 123, 'file name 1'],
+  ['method name 2', 123, 'file name 2'],
+  ['method name 3', 123, 'file name 3'],
+]) do
+  puts caller_locations
+  # Prints out:
+  #  file name 1:123:in ` method name 1'
+  #  file name 2:456:in ` method name 2'
+  #  file name 3:789:in ` method name 3'
+end
+```
+
+If you want a quicker way to shove a bunch of text (like a warning, comment, or classic poem on the fleeting nature of mankind's greatest achievements), you can use `add_to_stack_from_lyrics` with a single newline-delimited string:
+
+```
+lyrics = "I met a traveller from an antique land,
+Who said—“Two vast and trunkless legs of stone
+Stand in the desert... Near them, on the sand,
+Half sunk a shattered visage lies, whose frown,
+And wrinkled lip, and sneer of cold command,
+Tell that its sculptor well those passions read
+Which yet survive, stamped on these lifeless things,
+The hand that mocked them, and the heart that fed;
+And on the pedestal!, these words appear:
+My name is Ozymandias, King of Kings;
+Look on my Works, ye Mighty, and despair!
+Nothing beside remains. Round the decay
+Of that colossal Wreck, boundless and bare
+The lone and level sands stretch far away.”"
+Wacktrace.add_to_stack_from_lyrics(lyrics, 'Percy Bysshe Shelley') { raise "Suck it, Horace Smith." }
+```
+
+...which will result in...
+
+```
+ruby example.rb
+example.rb:17:in `block in <main>': Suck it, Horace Smith. (RuntimeError)
+	from /Users/kevin/.rvm/gems/ruby-3.0.0/gems/wacktrace-0.1.0/lib/wacktrace.rb:56:in `block in add_to_stack'
+	from Percy Bysshe Shelley:in ` I met a traveller from an antique land，'
+	from Percy Bysshe Shelley:1:in ` Who said—“Two vast and trunkless legs of stone'
+	from Percy Bysshe Shelley:2:in ` Stand in the desert․․․ Near them， on the sand，'
+	from Percy Bysshe Shelley:3:in ` Half sunk a shattered visage lies， whose frown，'
+	from Percy Bysshe Shelley:4:in ` And wrinkled lip， and sneer of cold command，'
+	from Percy Bysshe Shelley:5:in ` Tell that its sculptor well those passions read'
+	from Percy Bysshe Shelley:6:in ` Which yet survive， stamped on these lifeless things，'
+	from Percy Bysshe Shelley:7:in ` The hand that mocked them， and the heart that fed;'
+	from Percy Bysshe Shelley:8:in ` And on the pedestal︕， these words appear：'
+	from Percy Bysshe Shelley:9:in ` My name is Ozymandias， King of Kings;'
+	from Percy Bysshe Shelley:10:in ` Look on my Works， ye Mighty， and despair︕'
+	from Percy Bysshe Shelley:11:in ` Nothing beside remains․ Round the decay'
+	from Percy Bysshe Shelley:12:in ` Of that colossal Wreck， boundless and bare'
+	from Percy Bysshe Shelley:13:in ` The lone and level sands stretch far away․”'
+	from /Users/kevin/.rvm/gems/ruby-3.0.0/gems/wacktrace-0.1.0/lib/wacktrace.rb:57:in `add_to_stack'
+	from /Users/kevin/.rvm/gems/ruby-3.0.0/gems/wacktrace-0.1.0/lib/wacktrace.rb:67:in `add_to_stack_from_lyrics'
+	from example.rb:17:in `<main>'
+```
+
+## Development
+
+After checking out the repo, run `bin/setup` to install dependencies. Then, run `rake spec` to run the tests. You can also run `bin/console` for an interactive prompt that will allow you to experiment.
+
+To install this gem onto your local machine, run `bundle exec rake install`. To release a new version, update the version number in `version.rb`, and then run `bundle exec rake release`, which will create a git tag for the version, push git commits and the created tag, and push the `.gem` file to [rubygems.org](https://rubygems.org).
+
+## Contributing
+
+Bug reports and pull requests are welcome on GitHub at https://github.com/[USERNAME]/wacktrace. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [code of conduct](https://github.com/[USERNAME]/wacktrace/blob/main/CODE_OF_CONDUCT.md).
+
+## License
+
+The gem is available as open source under the terms of the [MIT License](https://opensource.org/licenses/MIT).
+
+## Code of Conduct
+
+Everyone interacting in the Wacktrace project's codebases, issue trackers, chat rooms and mailing lists is expected to follow the [code of conduct](https://github.com/[USERNAME]/wacktrace/blob/main/CODE_OF_CONDUCT.md).

data/Rakefile

@@ -0,0 +1,8 @@
+# frozen_string_literal: true
+
+require "bundler/gem_tasks"
+require "rspec/core/rake_task"
+
+RSpec::Core::RakeTask.new(:spec)
+
+task default: :spec

data/bin/console

@@ -0,0 +1,15 @@
+#!/usr/bin/env ruby
+# frozen_string_literal: true
+
+require "bundler/setup"
+require "wacktrace"
+
+# You can add fixtures and/or initialization code here to make experimenting
+# with your gem easier. You can also use a different console, if you like.
+
+# (If you use this, don't forget to add pry to your Gemfile!)
+# require "pry"
+# Pry.start
+
+require "irb"
+IRB.start(__FILE__)

data/bin/setup

@@ -0,0 +1,8 @@
+#!/usr/bin/env bash
+set -euo pipefail
+IFS=$'\n\t'
+set -vx
+
+bundle install
+
+# Do any other automated setup that you need to do here

data/lib/wacktrace/version.rb

@@ -0,0 +1,5 @@
+# frozen_string_literal: true
+
+module Wacktrace
+  VERSION = "1.0.0"
+end

data/lib/wacktrace.rb

@@ -0,0 +1,190 @@
+# frozen_string_literal: true
+
+require_relative "wacktrace/version"
+
+module Wacktrace
+  class Error < StandardError; end
+  class << self
+    # Runs the given block with the given lines inserted into the call stack
+    # above it.  Lines should be an array like:
+    #
+    # [
+    #   ["somemethod1", 111, "somefile1"],
+    #   ["somemethod2", 222, "somefile2"],
+    #   ["somemethod3", 333, "somefile3"],
+    # ]
+    #
+    # That will result in a strack trace like:
+    #
+    #  "somefile3:333:in ` somemethod3'",
+    #  "somefile2:222:in ` somemethod2'",
+    #  "somefile1:111:in ` somemethod1'",
+    #
+    def add_to_stack(lines, &real)
+      if lines.length <= 0
+        return real.call
+      end
+
+      # If stack traces are being printed newest-to-oldest, we need to reverse
+      # the input lines in order to have them print out readably.
+      if detect_order == :recent_first
+        lines.reverse!
+      end
+
+      lines = fix_duplicate_methods(lines)
+
+      # Create a namespace for all these methods so we don't polute the global
+      # namespace.
+      container_class = Class.new
+    
+      raise "add to stack missing block" unless block_given?
+    
+      lines = lines.map { |line| [clean_method_name(line[0]), line[1], line[2]] }
+    
+      # Define each method in series: a calls b, b calls c, and so on.  The last
+      # line does not get a method defined here.
+      lines.each_cons(2) do |line_1, line_2|
+        # puts "defining '#{line_1[0]}'"
+        success = true
+        define_stack_level(container_class, line_1, line_2[0])
+      end
+    
+      last = lines.last
+      define_stack_level(container_class, last, 'ending')
+      container_class.define_singleton_method("ending") { real.call }
+      return container_class.send(lines.first[0])
+    end
+
+    # This is a convenience method to construct a stack trace from a single
+    # string with a bunch of newlines (eg the lyrics to a song or words to a
+    # poem).  It'll use the same filename for each line.
+    def add_to_stack_from_lyrics(lyrics, filename, &block)
+      lines = lyrics.split("\n").map.with_index do |line, i|
+        [line, i, filename]
+      end
+      add_to_stack(lines, &block)
+    end
+
+    private
+
+    # Because we can't have two methods with the same name in the same
+    # namespace, we'll need to modify any lines with the same method name
+    # (line[0]).  To do this, we'll just pad each duplicate line with
+    # non-breaking spaces.  So if you have several lines with the method name
+    # "foo", they'll become "foo", "foo ", "foo  ", etc.
+    def fix_duplicate_methods(lines)
+      counts = {}
+      lines.map { |line|
+        method_name = line[0]
+        if counts[method_name]
+          original_method_name = method_name
+          method_name = method_name + (' ' * counts[method_name])
+          counts[original_method_name] += 1
+        else
+          counts[method_name] = 1
+        end
+        [method_name, line[1], line[2]]
+      }
+    end
+
+    def clean_method_name(string)
+      # Always start the method name with a non-breaking space so ruby doesn't
+      # interpret it as a constant if you started the string with a capital.
+      ' ' + string
+        .gsub(' ', ' ')
+        .gsub(',', '，')
+        .gsub('.', '․')
+        .gsub(':', '：')
+        .gsub("'", '’')
+        .gsub("@", '＠')
+        .gsub("`", '`')
+        .gsub("~", '～')
+        .gsub("#", '＃')
+        .gsub("$", '＄')
+        .gsub("%", '％')
+        .gsub("^", '＾')
+        .gsub("&", '&')
+        .gsub("*", '＊')
+        .gsub("(", '（')
+        .gsub(")", '）')
+        .gsub("-", '–')
+        .gsub("+", '＋')
+        .gsub("[", '［')
+        .gsub("]", '］')
+        .gsub("|", '｜')
+        .gsub("/", '／')
+        .gsub('\\', '＼')
+        .gsub(";", ';')
+        .gsub("{", '｛')
+        .gsub("}", '｝')
+        .gsub("\"", '＂')
+        .gsub("'", '＇')
+        .gsub("<", '＜')
+        .gsub(">", '＞')
+        # These are technically allowed at the end of a method, but I'm too lazy to
+        # write logic to allow that.
+        .gsub('!', '︕')
+        .gsub('?', '︖')
+        .gsub('=', '＝')
+    end
+
+    # Calls the given block with the given "lines" inserted into the call stack.
+    # Each line should look like:
+    #
+    #  [ "somemethodname", 123, "somefilename"]
+    #
+    # which will result in a traceback line that looks like:
+    #
+    #  3: from somemethodname:123:in `somefilename'
+    #
+    def define_stack_level(container_class, line, body)
+      success = true
+
+      # For some reason line numbers come out as one higher than whatever we put in here.
+      line_number = line[1].to_i - 1
+      method_name = line[0]
+      file_name = line[2]
+
+      method_string = "def #{method_name}\n#{body}\nend"
+
+      begin
+        container_class.instance_eval(method_string, file_name, line_number)
+      rescue SyntaxError => e
+        success = false
+      end
+
+      if !success || !container_class.methods.include?(method_name.to_sym)
+        warn("
+          Unable to create a method named:
+          #{method_name}
+          with body
+          #{method_string}
+          One of them probably contains some special character that's not yet handled."
+        )
+      end
+    end
+
+    def add_lines_to_stack(lines, &real)
+      add_to_stack(lyrics_to_stack_lines(lines), &real)
+    end
+
+    # The backtrace order varies by situation (version, tty vs file, among
+    # others). Rather than hardcoding the rules, let's just detect it.
+    def detect_order
+      begin
+        detect_order_raise
+      rescue Exception => e
+        if e.backtrace.first.include?("detect_order_raise")
+          return :recent_first
+        elsif e.backtrace.last.include?("detect_order_raise")
+          return :recent_last
+        else
+          return :undetectable
+        end
+      end
+    end
+    def detect_order_raise
+      raise 'error'
+    end
+  end
+end

data/wacktrace.gemspec

@@ -0,0 +1,39 @@
+# frozen_string_literal: true
+
+require_relative "lib/wacktrace/version"
+
+Gem::Specification.new do |spec|
+  spec.name          = "wacktrace"
+  spec.version       = Wacktrace::VERSION
+  spec.authors       = ["Kevin Kuchta"]
+  spec.email         = ["kevin@kevinkuchta.com"]
+
+  spec.summary       = "Insert arbitrary text into the call stack."
+  spec.homepage      = "https://github.com/kkuchta/wacktrace"
+  spec.license       = "MIT"
+  spec.required_ruby_version = ">= 2.4.0"
+
+  spec.metadata["homepage_uri"] = spec.homepage
+  spec.metadata["source_code_uri"] = "https://github.com/kkuchta/wacktrace"
+  spec.metadata["changelog_uri"] = "https://github.com/kkuchta/wacktrace/blob/main/CHANGELOG.md"
+
+  # Specify which files should be added to the gem when it is released.
+  # The `git ls-files -z` loads the files in the RubyGem that have been added into git.
+  spec.files = Dir.chdir(File.expand_path(__dir__)) do
+    `git ls-files -z`.split("\x0").reject do |f|
+      (f == __FILE__) || f.match(%r{\A(?:(?:test|spec|features)/|\.(?:git|travis|circleci)|appveyor)})
+    end
+  end
+  spec.bindir        = "exe"
+  spec.executables   = spec.files.grep(%r{\Aexe/}) { |f| File.basename(f) }
+  spec.require_paths = ["lib"]
+
+  # Uncomment to register a new dependency of your gem
+  # spec.add_dependency "example-gem", "~> 1.0"
+  spec.add_development_dependency "rspec", "~> 3.2"
+  spec.add_development_dependency "rake", "~> 13.0"
+  spec.add_development_dependency "pry-byebug", "~> 3.9"
+
+  # For more information and examples about making a new gem, checkout our
+  # guide at: https://bundler.io/guides/creating_gem.html
+end

metadata

@@ -0,0 +1,101 @@
+--- !ruby/object:Gem::Specification
+name: wacktrace
+version: !ruby/object:Gem::Version
+  version: 1.0.0
+platform: ruby
+authors:
+- Kevin Kuchta
+autorequire:
+bindir: exe
+cert_chain: []
+date: 2021-08-31 00:00:00.000000000 Z
+dependencies:
+- !ruby/object:Gem::Dependency
+  name: rspec
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '3.2'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '3.2'
+- !ruby/object:Gem::Dependency
+  name: rake
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '13.0'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '13.0'
+- !ruby/object:Gem::Dependency
+  name: pry-byebug
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '3.9'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '3.9'
+description:
+email:
+- kevin@kevinkuchta.com
+executables: []
+extensions: []
+extra_rdoc_files: []
+files:
+- ".rspec"
+- CHANGELOG.md
+- CODE_OF_CONDUCT.md
+- Gemfile
+- Gemfile.lock
+- LICENSE.txt
+- README.md
+- Rakefile
+- bin/console
+- bin/setup
+- lib/wacktrace.rb
+- lib/wacktrace/version.rb
+- wacktrace.gemspec
+homepage: https://github.com/kkuchta/wacktrace
+licenses:
+- MIT
+metadata:
+  homepage_uri: https://github.com/kkuchta/wacktrace
+  source_code_uri: https://github.com/kkuchta/wacktrace
+  changelog_uri: https://github.com/kkuchta/wacktrace/blob/main/CHANGELOG.md
+post_install_message:
+rdoc_options: []
+require_paths:
+- lib
+required_ruby_version: !ruby/object:Gem::Requirement
+  requirements:
+  - - ">="
+    - !ruby/object:Gem::Version
+      version: 2.4.0
+required_rubygems_version: !ruby/object:Gem::Requirement
+  requirements:
+  - - ">="
+    - !ruby/object:Gem::Version
+      version: '0'
+requirements: []
+rubygems_version: 3.2.3
+signing_key:
+specification_version: 4
+summary: Insert arbitrary text into the call stack.
+test_files: []