You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Suddenly pry has started opening whenever this code is run, which is all the time:
From: /Users/rct/.rbenv/versions/2.1.5/lib/ruby/gems/2.1.0/gems/temple-0.6.10/lib/temple/utils.rb @ line 19 Temple::Utils#escape_html_safe:
18: def escape_html_safe(html, safe = true)
=> 19: safe && html.html_safe? ? html : escape_html(html)
20: end
[1] pry(Temple::Utils)> breakpoints
No breakpoints defined.
[1] pry(Temple::Utils)> break --disable-all
No breakpoints defined.
As you can see from the console printout, there is no binding.pry in that file, nor does Pry-debugger think there are any breakpoints defined. (Not sure if this is an issue with Pry or Pry-debugger, but I'm trying here first.) Just updated all gems and rebooted server, to no effect. How do I clear this phantom breakpoint?
The text was updated successfully, but these errors were encountered:
Resolved, kind of -- the binding.pry was in a ruby-slim template, which calls the gem in question:
.title
= binding.pry
- if on_path? survey_path(survey)
= survey.title
Normally putting binding.pry in a slim template opens pry at the correct line inside the template, as expected; it would be nice to know why this is not happening here.
hi @aeonaut I will guess this is the same problem as your last issue. Please try to remove pry-byebug from Gemfile, and reopen if it's still an issue. Thanks.
Suddenly pry has started opening whenever this code is run, which is all the time:
As you can see from the console printout, there is no
binding.pry
in that file, nor does Pry-debugger think there are any breakpoints defined. (Not sure if this is an issue with Pry or Pry-debugger, but I'm trying here first.) Just updated all gems and rebooted server, to no effect. How do I clear this phantom breakpoint?The text was updated successfully, but these errors were encountered: