/heartbeat # bin/heartbeat
I, [2021-06-11T06:40:27.272858 #122] INFO -- : Reading configuration from config/heartbeat.invalid.yml.
#<Thread:0x00007f228acff7e8 bin/heartbeat:32 run> terminated with exception (report_on_exception is true):
bin/heartbeat:37:in `block (2 levels) in <main>': undefined method `deep_symbolize_keys' for {"base_url"=>"https://robot-ws.your-server.de", "basic_auth"=>{"username"=>"username", "password"=>"password"}, "failover_ip"=>"0.0.0.0", "ping_ip"=>"0.0.0.0", "ips"=>[{"ping"=>"1.1.1.1", "target"=>"1.1.1.1"}, {"ping"=>"2.2.2.2", "target"=>"2.2.2.2"}], "interval"=>30, "timeout"=>10, "tries"=>3, "dry"=>true, "only_once"=>true}:Hash (NoMethodError)
I suggest to leave the hashr gem dependency in, that is to revert these changes (the below diff is not real or correct, but instead freestyle edited to convey the idea):
I suggest to leave the
hashr
gem dependency in, that is to revert these changes (the below diff is not real or correct, but instead freestyle edited to convey the idea):I suggest to fix that, use rebase with fixup to merge the fix into commit 7eac3a2 and then to force push the commits?
Removing
hashr
not only breaks thedeep_symbolize_keys
call, which would be trivial to remove, but it breaks subsequenthash access. These could all be fixed by using string hash lookup notation:
which of course would also be OK instead of reintroducing the
hashr
dependendy. It's your call.