André Luis Leal Cardoso Jr

About the corrupt output, I believe #2158 fixes it.

@Ikariusrb I don't think so, it's on my list to properly review this. And to also configure Windows tests to Github Actions to ensure it keeps working. @kyrylo any thoughts...

Can you update pry-doc to 1.2.0 ? Or at least [v0.12.0](https://github.com/pry/pry-doc/blob/master/CHANGELOG.md#v0120-january-21-2018) which includes docs for Ruby 2.5. That should fix the warning.

Tested on macOS and the same issues happens. I'll investigate

I think I got it right on http://github.com/andrehjr/less/commit/79d681d610b9ced1c1f9e6ae0e1782b70cd68fea Please take a look ;)

That's really odd 🤔 I've tried the same using the gem versions. Can you run the following cmds and let me know the result: ``` self.method(:attribute_was).source MethodSource.source_helper(self.method(:attribute_was).source_location) Pry.last_internal_error.backtrace Pry.last_internal_error.class Pry::CodeObject.lookup("self.attribute_was",...

Thanks for the additional details. I've tried this on Rails 5.1.7 app too and still trying to reproduce and understand what's happening here. It does look like a problem with...

Calling: ```pry -e ';' -e ''``` still messes up with the terminal. (on MacOS) @saiqulhaq not all windows versions are excluded though. We enabled tests for Windows OS recently and...

Split calculates the ZScore based on the participant count and conversion rate. Only displays it when confidence is >= 90% So I think the confidence level is still too low(

Hi there, yeah, it's probably related to that. BetaDistribution requires > 0. As the participation_count should not be less than the completed count. At first, the solution was to ensure...