can't override ConfigCatClient via webmock (bypassing via cache?) about ruby-sdk HOT 8 CLOSED

A bit of extra info, when the tests run in a fresh docker image (with webmock enabled), I get the following

WARN -- : Evaluating get_value('my_feature') failed. Cache is empty. Returning default_value in your get_value call: [false].

So in addition to being bypassed, the webmock stub fails to provide the configuration in the test-suite when there is no cache already present.

from ruby-sdk.

Hi @graial,

Thanks for reaching out.
I couldn't reproduce the issue.

Could you please tell me which ConfigCat SDK version you are using?
Could you please provide a full example (e.g. on github)? That would be a big help to repro the issue.

from ruby-sdk.

I've produced a minimal example here but the behaviour isn't seen:
https://github.com/graial/configcat_stubbed_spec_example

I assume it is v5 (based on the filename from the stub).
in Gemfile.lock, it says configcat (5.0.2)

So it appears to be a bug in my initial implementation. I'll poke around a little more and circle back

from ruby-sdk.

Hi @graial,

Thanks for reaching out. I couldn't reproduce the issue.

Could you please tell me which ConfigCat SDK version you are using? Could you please provide a full example (e.g. on github)? That would be a big help to repro the issue.

Are you able to point me to where the update call is made within the SDK?

I am still unable to locate the issue in my main app and Webmock is failing to block the update call to the api no matter where I place WebMock.disable_net_connect! within the spec or rails_helper.rb folder.

I also tried a fresh clone of the repo on a different computer so it's not a local caching issue

from ruby-sdk.

Hi @graial,

We download the config.json in the ConfigFetcher class :
https://github.com/configcat/ruby-sdk/blob/master/lib/configcat/configfetcher.rb#L172

The caching/fechtime checking in the ConfigService class:
https://github.com/configcat/ruby-sdk/blob/master/lib/configcat/configservice.rb

We have just releases a new SDK version 6.0.0.
In this version we restructured the config fetching. I think it worth to check the issue with this release.

from ruby-sdk.

I also checked your minimal example project. I didn't get the issue either.

from ruby-sdk.

This issue is marked stale because it has no activity in the last 3 weeks. The issue will be closed in one week. Please remove the stale flag to keep it open.

from ruby-sdk.

This issue was closed due to no activity.

from ruby-sdk.