Why Taipy is blocking config update in development version

[FlorianJacta]

Description

I am in development version. I don't want to keep my .taipy and files generated by user_data.

I change from a Taipy version to another but receive this message:

[2025-01-22 11:11:00.209][Taipy][ERROR] The version 4.1.0.dev0 of Taipy's entities does not match version of the Taipy Version management 4.0.2. Please update the core entities to be compatible with Taipy Core 4.0.2 using the `taipy migrate ...` command. For more information, please run `taipy help migrate`

Why Taipy is blocking config update in development version?

Acceptance Criteria

• Any new code is covered by a unit tested.
• Check code coverage is at least 90%.

Code of Conduct

• I have checked the existing issues.
• I am willing to work on this issue (optional)

[trgiangdo]

@jrobinAV @FlorianJacta This is happening because of the ConfigCoreVersionMismatched exception is raised here because of the _check_compatibility() method.

Should we skip the _check_compatibility() method when in development mode?

[trgiangdo]

The ConfigCoreVersionMismatched exception is raised before the clean_all_entity_by_version() method, which is trying to load the old _Version entity and the old Config.

Proposal:
Update the _version_manager.py lines 138 - 149 to:

        try:
            if version_number == cls._get_development_version():
                if cls._exists(version_number):
                    return version_number
            else:
                if cls._get(version_number):
                    return version_number
        except InconsistentEnvVariableError:  # The version exist but the Config is alternated
            return version_number
        except ConfigCoreVersionMismatched as e:
            cls._logger.error(e.message)
            raise SystemExit() from e

The main difference is only calling the _get when it's not development mode, otherwise call the _exists method

[trgiangdo]

To test the problem:

1. Install taipy 4.0.0
2. Run an application that create some entities in taipy 4.0.0 in both development mode and experiment mode (so we have entities for both dev and experiment versions)
3. Install taipy 4.1.0.dev1
4. Rerun the application in development mode. For the current code, it will log an error.
   • Expected behavior: The application should run
5. Rerun the application in experiment mode. For the current code, the exception is raised with the whole backlog
   • Expected behavior: The error should be logged properly.