INI method fails about epics HOT 3 CLOSED

Hmm, I checked installing it from a fresh Gemfile without having a version defined and it went to the latest release.

As you figured it out, I'd consider the issue resolved for now

from epics.

HI @sebgrebe

so that means it stopped working at commit 211677a?
Or did you just go back to where the unit tests seemed to pass on the CI?

I just tested against latest master with ruby 2.6.3 and the EBICS test server provided by subsembly that I still have access to. Everything worked for that test case.
If you can tell me a bit more about your environment, I can run the init steps which would be closer to your environment.
E.g. which nokogiri version do you have in use, which ruby version, which exact commit did you experience the issue on

Generally, based on the line you pointed to, it seems a bit odd - as bugs usually do.

The INI call is executed here:

from epics.

@tobischo, I found the cause of the issue:

• When I call client.INI, it fails on this line because env["body"] is nil.
• This is an older commit though, even behind the current release. Instead, it should look like this.
• Checking my Gemfile.lock, I could see that when simply adding epics to my Gemfile and running bundle install, the epics version is resolved to 1.7.2, which is this commit, at which point we still get the offending line
• If I run bundle update epics, it resolves to the latest version 1.8.1, at which point I don't get that issue anymore

So the cause of the issue was that by default it resolves to 1.7.2. Not sure whether that is a general issue or down to my Gemfile.

from epics.