Fix local pipeline database registration and empty village-ID handling#1122
Merged
Conversation
…pted by save_layer_info_to_db, update_layer_sync_status functions
amit-spatial
marked this pull request as ready for review
July 20, 2026 12:01
amit-spatial
force-pushed
the
fix/error_checks
branch
from
July 21, 2026 08:53
e317ab2 to
7aa32d9
Compare
pawangramvaani
approved these changes
Jul 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
save_layer_info_to_dbandupdate_layer_sync_statusfunctions after successful GeoServer publication.not applicable: local compute GeoServer layerforasset_id, which is stored ingee_asset_path.{"is_generated_locally": true}inmisc.register_layerabstraction and its package export so these first three consumers exercise the production database functions directly.village_codeKeyError.Root cause
The shared wrapper introduced a second layer-registration implementation instead of using the established production functions directly.
Separately, an empty sidecar lookup returned a DataFrame without its configured key columns. For tehsils where every village ID was missing, downstream code then accessed a nonexistent
village_codecolumn.Database behavior
Each successfully published layer now calls:
Registration and sync failures are raised explicitly rather than being silently reported as successful pipeline runs.
Validation
use_pregenerated=falseand live GeoServer publication.gee_asset_path,is_public_gee_asset=false,is_sync_to_geoserver=true, andmisc.is_generated_locally=true.village_codeschema.py_compile, focused Ruff fatal-error checks, andgit diff --check.Scope
This PR contains four commits and changes only:
computing/misc/facilities/pipeline.pycomputing/misc/antyodaya/pipeline.pycomputing/misc/livestocks/pipeline.pyutilities/pipelines/__init__.pyutilities/pipelines/publish.pyutilities/pipelines/tabular.pyNo changes are made to
computing/utils.py, authentication, API permissions, or migrations. The CS admin-standard resource work remains isolated in PR #1084.