summaryrefslogtreecommitdiff
path: root/Gemfile.lock
diff options
context:
space:
mode:
authorStan Hu <stanhu@gmail.com>2018-12-05 16:51:48 -0800
committerStan Hu <stanhu@gmail.com>2018-12-05 16:51:48 -0800
commitd47cd9be8f38c09ccebe750a123fce0c27a3a88e (patch)
tree697affa1587321593504a812e4e3aeb55fb0095b /Gemfile.lock
parentec2c268b5ea51a11ded3dc87b034cca81b5090c4 (diff)
downloadgitlab-ce-d47cd9be8f38c09ccebe750a123fce0c27a3a88e.tar.gz
Upgrade rspec-parameterized to 0.4.1
rspec-parameterized 0.4.0 fails spectacularly with Ruby 2.5.3 with the following error: ``` RuntimeError: No such frame, gone beyond end of stack! ``` This happens because of a Ruby bug in https://bugs.ruby-lang.org/issues/15105. The binding_of_caller gem induces this failure. This upgrade switches to the binding_of_ninja gem, which does not have the same problem.
Diffstat (limited to 'Gemfile.lock')
-rw-r--r--Gemfile.lock7
1 files changed, 4 insertions, 3 deletions
diff --git a/Gemfile.lock b/Gemfile.lock
index 699d77615aa..f51eaef9357 100644
--- a/Gemfile.lock
+++ b/Gemfile.lock
@@ -82,6 +82,7 @@ GEM
erubi (>= 1.0.0)
rack (>= 0.9.0)
bindata (2.4.3)
+ binding_ninja (0.2.2)
binding_of_caller (0.8.0)
debug_inspector (>= 0.0.1)
bootsnap (1.3.2)
@@ -724,8 +725,8 @@ GEM
rspec-mocks (3.7.0)
diff-lcs (>= 1.2.0, < 2.0)
rspec-support (~> 3.7.0)
- rspec-parameterized (0.4.0)
- binding_of_caller
+ rspec-parameterized (0.4.1)
+ binding_ninja (>= 0.2.1)
parser
proc_to_ast
rspec (>= 2.13, < 4)
@@ -895,7 +896,7 @@ GEM
get_process_mem (~> 0)
unicorn (>= 4, < 6)
uniform_notifier (1.10.0)
- unparser (0.2.7)
+ unparser (0.4.2)
abstract_type (~> 0.0.7)
adamantium (~> 0.2.0)
concord (~> 0.1.5)