dev bit of Gemfile
group :development, :test do
gem "rspec-rails"
gem 'capybara'
gem 'factory_girl_rails'
gem 'forgery'
gem "database_cleaner"
gem "mongoid-rspec"
dev bit of Gemfile
group :development, :test do
gem "rspec-rails"
gem 'capybara'
gem 'factory_girl_rails'
gem 'forgery'
gem "database_cleaner"
gem "mongoid-rspec"
If you're encountering ping github.com
failing inside WSL with a Temporary failure in name resolution
, you're not alone — this has been a long-standing issue, especially when using VPNs or corporate networks.
This issue is now fixed robustly with DNS tunneling, which preserves dynamic DNS behavior and avoids limitations like WSL’s former hard cap of 3 DNS servers in /etc/resolv.conf
.
DNS tunneling is enabled by default in WSL version 2.2.1 and later, meaning that if you're still seeing DNS resolution issues, the first and most effective fix is simply to upgrade WSL. Upgrading WSL updates the WSL platform itself, but does not affect your installed Linux distributions, apps, or files.
To upgrade WSL, follow these steps,
-- show running queries (9.2) | |
SELECT pid, age(clock_timestamp(), query_start), usename, query | |
FROM pg_stat_activity | |
WHERE query != '<IDLE>' AND query NOT ILIKE '%pg_stat_activity%' | |
ORDER BY query_start desc; | |
-- show long-running queries (greater than 5 minutes) | |
SELECT | |
pid, | |
now() - pg_stat_activity.query_start AS duration, |