mirror of
https://github.com/hanzoai/insights.git
synced 2026-11-03 00:52:32 +00:00
zeekay
2e29e0db21
The fork half-carried the upstream vendor's name: env vars had been moved to DATASTORE_*, but every module path, identifier and doc string underneath still said ClickHouse. A fork that reads like someone else's product in every import is a vendored copy that never got renamed. insights/clickhouse/ -> insights/datastore/ insights/insightsql/functions/ -> .../functions/datastore/ products/live_debugger/backend/ -> .../backend/datastore/ docker/, docs/handbook/ -> datastore/ CLICKHOUSE_* identifiers -> DATASTORE_* (164 files) manage.py migrate_clickhouse -> migrate_datastore prose, comments, docstrings -> Datastore (1000+ files) The ORM moved with it: hanzoai/infi.clickhouse_orm now ships `datastore_orm`, so consumers write `from datastore_orm import ...` rather than threading the original vendor's `infi` org namespace through their imports. Repinned here to that revision. MIGRATION HISTORY. A package rename orphans the history table, because it keys on package_name: the runner then sees zero applied migrations, replays from 0001 and dies on 0026. That already happened once here, silently blocking every datastore migration until the rows were re-keyed by hand. So the rename carries its own fixup — migrate_datastore now adopts history from prior package names before migrating, idempotent and a no-op on a fresh database, with the list of former names as the single place a future rename has to touch. The history TABLE name is unchanged: it is persisted state, and renaming it is a data migration rather than a rename. Left with the vendor's name, because they are the vendor's: clickhouse-driver, clickhouse-pool and clickhouse-connect are third-party PyPI packages we do not fork, CLICKHOUSE_SKIP_USER_SETUP and CLICKHOUSE_SERVER_IMAGE configure the upstream server image, and clickhouse.com doc links point at the real engine's documentation. Verified: 4257 Python files parse with 0 syntax errors, no `insights.clickhouse` or `infi.clickhouse` references survive, and clickhouse_pool/_driver imports are untouched.
31 lines
1.6 KiB
XML
31 lines
1.6 KiB
XML
<component name="ProjectRunConfigurationManager">
|
|
<configuration default="false" name="Celery Beat" type="PythonConfigurationType" factoryName="Python">
|
|
<module name="insights" />
|
|
<option name="ENV_FILES" value="$PROJECT_DIR$/bin/celery-queues.env" />
|
|
<option name="INTERPRETER_OPTIONS" value="" />
|
|
<option name="PARENT_ENVS" value="true" />
|
|
<envs>
|
|
<env name="PYTHONUNBUFFERED" value="1" />
|
|
<env name="DATASTORE_SECURE" value="False" />
|
|
<env name="DATABASE_URL" value="postgres://insights:insights@localhost:5432/insights" />
|
|
<env name="DEBUG" value="1" />
|
|
<env name="KAFKA_HOSTS" value="localhost" />
|
|
<env name="SKIP_SERVICE_VERSION_REQUIREMENTS" value="1" />
|
|
<env name="REPLAY_EMBEDDINGS_ALLOWED_TEAM" value="1,2,3" />
|
|
</envs>
|
|
<option name="SDK_HOME" value="$PROJECT_DIR$/env/bin/python" />
|
|
<option name="WORKING_DIRECTORY" value="$PROJECT_DIR$" />
|
|
<option name="IS_MODULE_SDK" value="true" />
|
|
<option name="ADD_CONTENT_ROOTS" value="true" />
|
|
<option name="ADD_SOURCE_ROOTS" value="true" />
|
|
<EXTENSION ID="PythonCoverageRunConfigurationExtension" runner="coverage.py" />
|
|
<option name="SCRIPT_NAME" value="$PROJECT_DIR$/manage.py" />
|
|
<option name="PARAMETERS" value="run_autoreload_celery --type=beat" />
|
|
<option name="SHOW_COMMAND_LINE" value="false" />
|
|
<option name="EMULATE_TERMINAL" value="false" />
|
|
<option name="MODULE_MODE" value="false" />
|
|
<option name="REDIRECT_INPUT" value="false" />
|
|
<option name="INPUT_FILE" value="" />
|
|
<method v="2" />
|
|
</configuration>
|
|
</component> |