“...I've been working since 2008 with Ruby / Ruby on Rails, love a bit of Elixir / Phoenix and learning Rust.
I also poke through other people's code and make PRs for OpenSource Ruby projects that sometimes make it. Currently working for InPay who are based in Denmark...”
It’s just silently falling over and restarting when trying to start with brew services start postgresql
New-MacBook-Pro:local cex$ sudo -s tail -f /var/log/system.log
Password:
Feb 19 09:52:41 New-MacBook-Pro com.apple.xpc.launchd[1] (homebrew.mxcl.postgresql[27587]): Service exited with abnormal code: 1
Feb 19 09:52:41 New-MacBook-Pro com.apple.xpc.launchd[1] (homebrew.mxcl.postgresql): Service only ran for 0 seconds. Pushing respawn out by 10 seconds.
Feb 19 09:52:51 New-MacBook-Pro com.apple.xpc.launchd[1] (homebrew.mxcl.postgresql[27616]): Service exited with abnormal code: 1
Starting manually and checking the server.log
New-MacBook-Pro:local cex$ pg_ctl -D /usr/local/var/postgres -l /usr/local/var/postgres/server.log start
waiting for server to start.... stopped waiting
pg_ctl: could not start server
Examine the log output.
New-MacBook-Pro:local cex$ cat /usr/local/var/
cache/ db/ homebrew/ lib/ log/ mongodb/ mysql/ postgres/ run/
New-MacBook-Pro:local cex$ cat /usr/local/var/postgres/server.log
2019-02-19 10:00:29.473 GMT [30912] FATAL: database files are incompatible with server
2019-02-19 10:00:29.473 GMT [30912] DETAIL: The data directory was initialized by PostgreSQL version 10, which is not compatible with this version 11.1.
New-MacBook-Pro:local cex$ brew postgresql-upgrade-database
==> brew install postgresql@10
==> Downloading https://homebrew.bintray.com/bottles/postgresql@10-10.6_1.mojave.bottle.1.tar.gz
######################################################################## 100.0%
==> Pouring postgresql@10-10.6_1.mojave.bottle.1.tar.gz
==> /usr/local/Cellar/postgresql@10/10.6_1/bin/initdb /usr/local/var/postgresql@10
==> Caveats
To migrate existing data from a previous major version of PostgreSQL run:
brew postgresql-upgrade-database
postgresql@10 is keg-only, which means it was not symlinked into /usr/local,
because this is an alternate version of another formula.
If you need to have postgresql@10 first in your PATH run:
echo 'export PATH="/usr/local/opt/postgresql@10/bin:$PATH"' >> ~/.bash_profile
For compilers to find postgresql@10 you may need to set:
export LDFLAGS="-L/usr/local/opt/postgresql@10/lib"
export CPPFLAGS="-I/usr/local/opt/postgresql@10/include"
For pkg-config to find postgresql@10 you may need to set:
export PKG_CONFIG_PATH="/usr/local/opt/postgresql@10/lib/pkgconfig"
To have launchd start postgresql@10 now and restart at login:
brew services start postgresql@10
Or, if you don't want/need a background service you can just run:
pg_ctl -D /usr/local/var/postgresql@10 start
==> Summary
/usr/local/Cellar/postgresql@10/10.6_1: 1,706 files, 20.8MB
==> Upgrading postgresql data from 10 to 11...
Stopping `postgresql`... (might take a while)
==> Successfully stopped `postgresql` (label: homebrew.mxcl.postgresql)
waiting for server to start....2019-02-19 10:05:34.199 GMT [32604] LOG: listening on IPv6 address "::1", port 5432
2019-02-19 10:05:34.199 GMT [32604] LOG: listening on IPv4 address "127.0.0.1", port 5432
2019-02-19 10:05:34.200 GMT [32604] LOG: listening on Unix socket "/tmp/.s.PGSQL.5432"
2019-02-19 10:05:34.219 GMT [32605] LOG: database system was shut down at 2019-02-07 21:30:24 GMT
2019-02-19 10:05:34.223 GMT [32604] LOG: database system is ready to accept connections
done
server started
waiting for server to shut down....2019-02-19 10:05:34.362 GMT [32604] LOG: received fast shutdown request
2019-02-19 10:05:34.362 GMT [32604] LOG: aborting any active transactions
2019-02-19 10:05:34.363 GMT [32604] LOG: worker process: logical replication launcher (PID 32611) exited with exit code 1
2019-02-19 10:05:34.363 GMT [32606] LOG: shutting down
2019-02-19 10:05:34.369 GMT [32604] LOG: database system is shut down
done
server stopped
==> Moving postgresql data from /usr/local/var/postgres to /usr/local/var/postgres.old...
The files belonging to this database system will be owned by user "cex".
This user must also own the server process.
The database cluster will be initialized with locale "en_US.UTF-8".
The default database encoding has accordingly been set to "UTF8".
The default text search configuration will be set to "english".
Data page checksums are disabled.
fixing permissions on existing directory /usr/local/var/postgres ... ok
creating subdirectories ... ok
selecting default max_connections ... 100
selecting default shared_buffers ... 128MB
selecting dynamic shared memory implementation ... posix
creating configuration files ... ok
running bootstrap script ... ok
performing post-bootstrap initialization ... ok
syncing data to disk ... ok
WARNING: enabling "trust" authentication for local connections
You can change this by editing pg_hba.conf or using the option -A, or
--auth-local and --auth-host, the next time you run initdb.
Success. You can now start the database server using:
/usr/local/opt/postgresql/bin/pg_ctl -D /usr/local/var/postgres -l logfile start
Performing Consistency Checks
-----------------------------
Checking cluster versions ok
Checking database user is the install user ok
Checking database connection settings ok
Checking for prepared transactions ok
Checking for reg* data types in user tables ok
Checking for contrib/isn with bigint-passing mismatch ok
Creating dump of global objects ok
Creating dump of database schemas
ok
Checking for presence of required libraries ok
Checking database user is the install user ok
Checking for prepared transactions ok
If pg_upgrade fails after this point, you must re-initdb the
new cluster before continuing.
Performing Upgrade
------------------
Analyzing all rows in the new cluster ok
Freezing all rows in the new cluster ok
Deleting files from new pg_xact ok
Copying old pg_xact to new server ok
Setting next transaction ID and epoch for new cluster ok
Deleting files from new pg_multixact/offsets ok
Copying old pg_multixact/offsets to new server ok
Deleting files from new pg_multixact/members ok
Copying old pg_multixact/members to new server ok
Setting next multixact ID and offset for new cluster ok
Resetting WAL archives ok
Setting frozenxid and minmxid counters in new cluster ok
Restoring global objects in the new cluster ok
Restoring database schemas in the new cluster
ok
Copying user relation files
ok
Setting next OID for new cluster ok
Sync data directory to disk ok
Creating script to analyze new cluster ok
Creating script to delete old cluster ok
Upgrade Complete
----------------
Optimizer statistics are not transferred by pg_upgrade so,
once you start the new server, consider running:
./analyze_new_cluster.sh
Running this script will delete the old cluster's data files:
./delete_old_cluster.sh
==> Upgraded postgresql data from 10 to 11!
==> Your postgresql 10 data remains at /usr/local/var/postgres.old
==> Successfully started `postgresql` (label: homebrew.mxcl.postgresql)
I thought initially it would be incredibly easy to add a wrapper method alongside existing let, let!, subject memoized helper methods in RSpec.
def current_user(&block)
u = yield
allow(User).to receive(:current_user).and_return(u)
end
describe 'stuff' do
let(:artist) { Fabricate(:artist) }
current_user { artist.user }
end
But I kept getting. `artist` is not available on an example group when the current user block was yielded. I had to dig into RSpec::Core to find how let is defined and came up with and ensure that artist and current_user were in the same scope when calling one another.
module CurrentUserHelpers
extend ActiveSupport::Concern
module ClassMethods
def current_user(&block)
raise "#current_usercalled without a block" if block.nil?
RSpec::Core::MemoizedHelpers.module_for(self).__send__(:define_method, :current_user, &block)
# Apply the memoization. The method has been defined in an ancestor
# module so we can use `super` here to get the value.
define_method(:current_user) do
u = __memoized.fetch_or_store(:current_user) do
block.arity == 1 ? super(RSpec.current_example, &nil) : super(&nil)
end
allow(User).to receive(:current_user).and_return(u)
u
end
end
def current_user!(&block)
current_user(&block)
before { current_user }
end
end
end
Your CI environment probably doesn’t mirror your development setup 100% of the time. So when stuff spectactularly fails testing elsewhere and not locally you might be tempted to throw your laptop in the bin.
Basic Backbone scaffold, but….where the hell has this indentation error come from?
Showing /Users/cex/repos/robl/app/views/layouts/application.html.haml where line #7 raised:
SyntaxError: [stdin]:4:9: unexpected indentation
Rails.root: /Users/cex/repos/robl
Application Trace | Framework Trace | Full Trace
(execjs):7539:8
(execjs):7545:14
(execjs):1:102
app/views/layouts/application.html.haml:7:in `_app_views_layouts_application_html_haml__3268572193542758911_70297544684220'
config/initializers/cookies.rb:10:in `call'
Precompiling Javascript and CSS in magic, but then then Javascript bugs like this appear after running a scaffold generator which spits out 20 files then this is frustrating. A stray object which should have had some nested attributes, was just left hanging.
blah:
// should have been
blah: {}
If only it could have pointed me to the right file, rather than just a line/char in some file. Next up. How does the default Backbone scaffold cope with MongoDB → JSON objects that don’t have a standard ‘id’.
Today I got almost 300 spec errors when flipping our core app to use Rails 5.1. Why? Well, it’s just syntax in controller, request specs but the syntax makes things much clearer and is probably a welcome change if not a time consuming fix.
Robs-iMac:hello roblacey$ mix ecto.create
warning: found quoted keyword "test" but the quotes are not required. Note that keywords are always atoms, even when quoted, and quotes should only be used to introduce keywords with foreign characters in them
mix.exs:52
Compiling 12 files (.ex)
Generated hello app
The database for Hello.Repo has already been created
So apparently Phoenix is super fast, scary fast. Well let’s see with ab 10 concurrent requests (longest request is 144ms)
Robs-iMac:hello roblacey$ ab -n 10 -c 10 http://phoenix.dv/
This is ApacheBench, Version 2.3 <$Revision: 1826891 $>
Copyright 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/
Licensed to The Apache Software Foundation, http://www.apache.org/
Benchmarking phoenix.dv (be patient).....done
Server Software: Cowboy
Server Hostname: phoenix.dv
Server Port: 80
Document Path: /
Document Length: 1931 bytes
Concurrency Level: 10
Time taken for tests: 0.059 seconds
Complete requests: 10
Failed requests: 0
Total transferred: 22600 bytes
HTML transferred: 19310 bytes
Requests per second: 169.19 [#/sec] (mean)
Time per request: 59.105 [ms] (mean)
Time per request: 5.910 [ms] (mean, across all concurrent requests)
Transfer rate: 373.41 [Kbytes/sec] received
Connection Times (ms)
min mean[+/-sd] median max
Connect: 0 0 0.1 0 0
Processing: 8 16 10.7 13 46
Waiting: 7 16 10.6 13 45
Total: 8 16 10.6 13 46
Percentage of the requests served within a certain time (ms)
50% 13
66% 13
75% 13
80% 14
90% 46
95% 46
98% 46
99% 46
100% 46 (longest request)
1000 concurrent requests, 144ms
Robs-iMac:hello roblacey$ ab -n 1000 -c 1000 http://localhost:4000/
This is ApacheBench, Version 2.3 <$Revision: 1826891 $>
Copyright 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/
Licensed to The Apache Software Foundation, http://www.apache.org/
Benchmarking localhost (be patient)
Completed 100 requests
Completed 200 requests
Completed 300 requests
Completed 400 requests
Completed 500 requests
Completed 600 requests
Completed 700 requests
Completed 800 requests
Completed 900 requests
Completed 1000 requests
Finished 1000 requests
Server Software: Cowboy
Server Hostname: localhost
Server Port: 4000
Document Path: /
Document Length: 1931 bytes
Concurrency Level: 1000
Time taken for tests: 0.152 seconds
Complete requests: 1000
Failed requests: 0
Total transferred: 2260000 bytes
HTML transferred: 1931000 bytes
Requests per second: 6569.65 [#/sec] (mean)
Time per request: 152.215 [ms] (mean)
Time per request: 0.152 [ms] (mean, across all concurrent requests)
Transfer rate: 14499.43 [Kbytes/sec] received
Connection Times (ms)
min mean[+/-sd] median max
Connect: 0 36 11.8 35 55
Processing: 25 64 16.7 69 90
Waiting: 6 64 16.8 69 90
Total: 46 100 24.2 103 144
Percentage of the requests served within a certain time (ms)
50% 103
66% 115
75% 121
80% 124
90% 131
95% 136
98% 140
99% 142
100% 144 (longest request)
10,000 requests, Ok so I get a socket error. Too many open files (24) That’s ok, I’m not at that stage yet anyway.
Robs-iMac:hello roblacey$ ab -n 10000 -c 10000 http://localhost:4000/
This is ApacheBench, Version 2.3 <$Revision: 1826891 $>
Copyright 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/
Licensed to The Apache Software Foundation, http://www.apache.org/
Benchmarking localhost (be patient)
socket: Too many open files (24)
So that’s pretty fast, but that’s just a static page. This would be better tested with a page that does a little more, or an API request that reads from the database.
Lastly just adding a new route, controller and view and template for a /hello
diff --git a/web/controllers/hello_controller.ex b/web/controllers/hello_controller.ex
new file mode 100644
index 0000000..f3e97b4
--- /dev/null
+++ b/web/controllers/hello_controller.ex
@@ -0,0 +1,7 @@
+defmodule Hello.HelloController do
+ use Hello.Web, :controller
+
+ def index(conn, params) do
+ render(conn, "world.html")
+ end
+end
diff --git a/web/router.ex b/web/router.ex
index e7a505b..6df752f 100644
--- a/web/router.ex
+++ b/web/router.ex
@@ -15,7 +15,7 @@ defmodule Hello.Router do
scope "/", Hello do
pipe_through :browser # Use the default browser stack
-
+ get "/hello", HelloController, :index
get "/", PageController, :index
end
diff --git a/web/templates/hello/world.html.eex b/web/templates/hello/world.html.eex
new file mode 100644
index 0000000..e69de29
diff --git a/web/views/hello_view.ex b/web/views/hello_view.ex
new file mode 100644
index 0000000..00f1881
--- /dev/null
+++ b/web/views/hello_view.ex
@@ -0,0 +1,3 @@
+defmodule Hello.HelloView do
+ use Hello.Web, :view
+end
No, not something that eats bunnies. I wanted to know if I could easily run a RabbitMQ consumer that just sat there listening. It seems incorrect to have a loop sat there just doing nothing all the time but I guess it the connection is open then it should just sit there, if not it can stop and have forty winks.
require 'rubygems'
# ENV['BUNDLE_GEMFILE'] ||= File.expand_path('Gemfile', __dir__)
require 'bundler/setup'
Bundler.require(:default)
conn = Bunny.new
conn.start
# open a channel
ch = conn.create_channel
# declare a queue
q = ch.queue('test1')
q.subscribe do |_, _, payload|
Thread.new do
puts "payload #{payload}"
sleep(5)
puts "finished sleeping"
end
end
while conn.status == :open do
# nothing is happening here
end
As expected, when an event occurs the subscribe block is called and the payload is send to STDOUT. Wait five seconds and finish. Had I not added Thread.new consumer would have waited 5 seconds and order is not quaranteed.
Interesting to note that when using manual_ack. Events are not automatically re-read from the queue until a new connection is made if the job is not ack’ed.
q.subscribe(manual_ack: true) do |delivery_info, _, payload|
Thread.new do
puts "payload #{payload} - Redelivered #{delivery_info.redelivered?}\n"
sleep(5)
puts "finished sleeping #{payload}\n"
puts payload.class
ch.acknowledge(delivery_info.delivery_tag, false) unless payload == '1' && !delivery_info.redelivered?
end
end
while conn.status == :open do
# nothing is happening here
end
Some warnings and errors appears today, or at least I only just noticed them.
Firstly I forget to load guard without bundle exec and this makes me a bad person.
Apparently I might have more than one version of rspec-expectations and rb-notify installed and I should probably clean them up.
So this might be the case, oh actually. I see the problem. I have a project that has two branches, master and upgrade/rails51. I’m using RVM but each branch has a different .ruby-gemset because of course Rails 5.1 is an upgrade and will have multiple dependencies that are all upgraded too. I must remember to switch RVM environments when flipping branches.
Robs-iMac:core roblacey$ guard
Warning: you have a Gemfile, but you're not using bundler or RUBYGEMS_GEMDEPS
09:36:26 - INFO - Guard here! It looks like your project has a Gemfile, yet you are running
> [#] `guard` outside of Bundler. If this is your intent, feel free to ignore this
> [#] message. Otherwise, consider using `bundle exec guard` to ensure your
> [#] dependencies are loaded correctly.
> [#] (You can run `guard` with --no-bundler-warning to get rid of this message.)
WARN: Unresolved specs during Gem::Specification.reset:
rb-inotify (~> 0.9, >= 0.9.7)
rspec-expectations (~> 3.8.0)
WARN: Clearing out unresolved specs.
