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
Update: This PR changed a lot over the course of being open. Please refer to the documentation or code in master / 5-1-stable to use system tests I'm really excited to open this initial PR for bringing system/acceptance test support to Rails through Capybara. The goal of this PR is for Rails to take on all the setup that is needed in applications to allow Capybara and make system testing default i
Reproduction steps: https://gist.github.com/chancancode/f909d105ba70ab7f4779 This bug actually is present in 4.1 as well (but it only affected the first find test case), and what is shown here is just an example of a bigger issue. The problem is that on 4.1 we switched to use parameterized queries with the find call, and in 4.2 more of those calls followed (I noticed it in find_by, but there might
from /prod_path/shared/bundle/ruby/2.1.0/gems/tiny_tds-1.0.2/lib/tiny_tds/client.rb:43:in `connect' from /prod_path/shared/bundle/ruby/2.1.0/gems/tiny_tds-1.0.2/lib/tiny_tds/client.rb:43:in `initialize' from /prod_path/shared/bundle/ruby/2.1.0/gems/activerecord-sqlserver-adapter-4.2.11/lib/active_record/connection_adapters/sqlserver_adapter.rb:311:in `new' from /prod_path/shared/bundle/ruby/2.1.0/
Resque (pronounced like "rescue") is a Redis-backed library for creating background jobs, placing those jobs on multiple queues, and processing them later. For the backstory, philosophy, and history of Resque's beginnings, please see the blog post (2009). Background jobs can be any Ruby class or module that responds to perform. Your existing classes can easily be converted to background jobs or yo
Steps to reproduce In WSL in Win 10, after everything basic was setup, I installed rvm and through that I installed ruby-2.3.1 successfully. I created a gemset, and installed rails-5.0 in that gemset. After that I created a demo by rails new rails5_demo , and bundle install successfully. In rails5_demo dir, I run rails s. Expected behavior In the above condition, Rack server should been up and run
% debride lib These methods MIGHT not be called: MyClass good_method lib/some/file.rb:16 bad_method lib/some/file.rb:20 ... But you know that good_method is called (perhaps because it is public API), then you can whitelist it: % echo good_method > whitelist.txt % debride --whitelist whitelist.txt lib These methods MIGHT not be called: MyClass bad_method lib/some/file.rb:20 ... Usage example for a
Static analysis of code. Can be easily hooked up to a CI. As with all static analysis tools of dynamic languages, can’t be 100%. Whitelisting known good methods by name or regexp. Use –rails for Rails-specific domain knowledge. Use debride_rm to brazenly remove all unused methods. BE CAREFUL. Use ‘debride_rails_whitelist` to generate an emperical whitelist from logs. Uses path_expander, so you can
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く