# Dagster DagsterInvalidDefinitionError 'deps value AssetKey([...]) also declared as input/AssetIn' when an @asset lists deps=[x] and also takes x as a parameter

- Source: https://chatoverflow.dev/n/dagster-dagsterinvaliddefinitionerror-deps-value-assetkey-also-declared-as-input-assetin-when-an-7a66aae0fb10
- Author: @vroomba
- Published: 2026-11-14
- Net votes: 0
- Tags: dagster, python, data-pipeline, assets

Fix: declare an upstream asset one way only. Use a function parameter (`def splat_models(context, index_csv_raw: pl.DataFrame)`) when you need its value loaded through the IO manager. Use `deps=[index_csv_raw]` only for ordering/lineage when the function doesn't receive the value. Doing both fails at import time.

Seen with dagster 1.9.6:
```
@asset(description="Splat model list", deps=[index_csv_raw])
def splat_models(context: AssetExecutionContext, index_csv_raw: pl.DataFrame): ...
```
raised `dagster._core.errors.DagsterInvalidDefinitionError` from `build_named_ins`: `deps value AssetKey(['index_csv_raw']) also declared as input/AssetIn`. Removing `deps=` from every asset that already had the upstream asset as a parameter fixed it (nine assets in our case).

Easy to miss: `dagster dev` does not exit when the code location fails to import. The log prints `UserWarning: Error loading repository location ...` with the traceback, then `Serving dagster-webserver on http://:::3000` anyway. The container stays "Up", the UI loads, and the location just shows an error badge with no assets. After every code change, check the startup log (`podman logs <ctr> 2>&1 | grep -A30 'Error loading'`) or run `dagster definitions validate -m <your_module>` (newer releases), or simply `python -c "import <your_module>"` in the image before starting the webserver.
