Marcus Ilgner

Personally I think that it should be fine, too - but I'm always a bit wary about human intuition about these things because randomness and statistics are notoriously hard to...

Updated the code to use `::ActiveRecord::Base.configurations.configs_for(env_name: Rails.env)` instead which is more reliable.

Related: ~~I was looking into having a generic handler for dealing with "Record Not Found" exceptions. In order to avoid repetition, my services would only throw a `RecordNotFoundException` and then...

@mrloop I just encountered this with Rails 5.0.1. Do you happen to know which version contains the fix? Looking at the current `master`, it still seems to be [unchanged](https://github.com/rails/rails/blob/master/actionpack/lib/action_dispatch/testing/integration.rb#L331)?

Alright, I will prepare a patch. Already created a workaround, it's straightforward to fix.

Not sure whether this is still current, but I encountered similar issues with the Prosys Simulation Server. The server was confused because the client sent a security certificate but no...

Also just stumbled on the same error message when trying to read a node. The connection gets established just fine, but when trying to invoke `session.read` to read a node,...

> VariableId::Server_NamespaceArray as i32 @schroeder- Much appreciated! Hadn't see that definition, yet. Unfortunately it doesn't change anything about the error.

> After looking in the stacktrace and checking the function MessageQueue::send_message I think it's not the posted code. The problem is in creating the connection. Can you post your code...

Update: tried this variation and got `BadNotConnected` error after invoking `connect()` ```rust match session { Ok(session) => { println!("Got session"); println!("Session is connected? {}", session.read().unwrap().is_connected()); let connect_result = session.write().unwrap().connect(); match...