DB_CONNECTION_MUTATOR ignored in 4.1.0

[michalc]

Hi,

We've recently upgraded to 4.1.0 from 4.0.2, and hitting an odd problem: our DB_CONNECTION_MUTATOR seems to be being ignored. Putting in a print statement at its beginning and looking in logs, it never seems to get called.

I've tried to replicate the issue locally, in order to get a minimum reproducible example, and I can't - it always seems to work fine, even with (almost) identical config.

Any help or ideas about what could be preventing DB_CONNECTION_MUTATOR from getting called?

[dosubot[bot]]

Hi @michalc,

I'm here to help you with any bugs, questions, or becoming a contributor. Let's squash those bugs together!

Dosu

The DB_CONNECTION_MUTATOR is supposed to be called only if it is defined in the configuration. Additionally, the source is determined based on the referrer in the request, which can affect whether the mutator is called. Ensure that the DB_CONNECTION_MUTATOR is correctly defined in your configuration and that the conditions for its invocation are met, such as having the appropriate referrer in the request ^[1].

If the mutator works locally but not in your production environment, consider checking for differences in the configuration files or the environment variables between the two setups. Also, verify that there are no conditional logic or feature flags in version 4.1.0 that might disable or bypass the DB_CONNECTION_MUTATOR, as this could be a potential cause of the issue.

To continue talking to Dosu, mention @dosu.

[michalc]

Hi @dosu,

verify that there are no conditional logic or feature flags in version 4.1.0 that might disable or bypass the DB_CONNECTION_MUTATOR, as this could be a potential cause of the issue.

How can I do this?

[dosubot[bot]]

To verify if there are any conditional logic or feature flags in version 4.1.0 that might disable or bypass the DB_CONNECTION_MUTATOR, you can follow these steps:

1. Review the Configuration: Check your configuration files to ensure that the DB_CONNECTION_MUTATOR is correctly defined. Make sure there are no conditions or flags that might prevent it from being set.

2. Check for Feature Flags: Although I couldn't find specific feature flags introduced in version 4.1.0 that affect the DB_CONNECTION_MUTATOR, it's a good idea to review the release notes or documentation for any new feature flags that might impact its functionality.

3. Examine the Codebase: Look into the codebase, especially around the parts where the DB_CONNECTION_MUTATOR is invoked, to see if there are any conditional statements that might prevent its execution. The mutator is called only if it is defined and the source is determined based on the request referrer ^[1].

4. Environment Differences: Since the mutator works locally but not in production, compare the environment variables and configurations between your local and production setups. Differences here might lead to the mutator not being called.

By following these steps, you should be able to identify any conditions or flags that might be affecting the DB_CONNECTION_MUTATOR.

To continue talking to Dosu, mention @dosu.

[michalc]

So... I think for some reason print statements weren't becoming visible from inside the mutator. If I raised an exception in the mutator, that became visible.