Flipper Redis Adapter ignoring configuration block sometimes about flipper HOT 5 OPEN

@micahtessler I'm not sure how to reproduce this. It sounds like Flipper is getting used during the boot process prior to your custom config possibly? @bkeepers does it sound like that to you or do you have any different ideas?

One option to figure out where this is happening is to bundle open flipper and add something like caller inside the flipper configure block there to see the backtrace of where it's getting invoked from. Once you have that, it should be easier to determine why this is happening.

Can you give that a try and let me know if it helps?

from flipper.

@micahtessler I'm not sure how to reproduce this. It sounds like Flipper is getting used during the boot process prior to your custom config possibly? @bkeepers does it sound like that to you or do you have any different ideas?

I agree, that's what it sounds like.

I edited my local copies of the gems to dump the stack to trace the problem (so some line numbers don't 100% line up).

If youc an paste the whole stack trace, we should be able to tell if it's happening during app boot and where.

from flipper.

Not sure what you reference as the boot process. The first initialization happens correctly as you can see above, it calls into my initializer config.
The second and third intializations happen incorrectly and occur afterwards.

so it there was a boot problem, I would expect the opposite, the first initialization would not get the config as it hadn't been set.
The 2nd and third would pick up the correct config as it's set in a rails initilaizer.

from flipper.

What from the stack trace do you need to see specifically?

from flipper.

What from the stack trace do you need to see specifically?

From inside of the default redis configure block. If you bundle open flipper-redis you can add the require and pp caller in the screenshot. Restart your process and copy the backtrace that gets printed.

from flipper.