https://dagster.io/ logo
#ask-ai
Title
# ask-ai
s

Slackbot

02/20/2024, 9:31 PM
This message was deleted.
s

Scout

02/20/2024, 9:31 PM
The error message you're encountering indicates that there is an unexpected configuration entry for the
store_precog_results
op within the job
write_precog_results_to_db
. Specifically, the error is saying that it received a config entry where it wasn't expecting one. To debug this error, let's go through a few steps: 1. Check the Op Configuration: Ensure that the
store_precog_results
op is defined with the correct configuration schema. If
LMEvalResultsConfig
is a custom configuration class, make sure that it is defined correctly and that it matches the configuration you are passing to the job. 2. Job Configuration: When you execute the job, you need to provide the correct configuration for the ops within the job. According to the documentation, Dagster validates any provided run config against the corresponding Pydantic model and will abort execution with a
DagsterInvalidConfigError
if validation fails. 3. Passing Configuration: If you are passing configuration to the job when you execute it, ensure that it is structured correctly. For example, if you are using a YAML file for configuration, it should look something like this:
Copy code
yaml ops:   store_precog_results:     config:       # ... configuration for LMEvalResultsConfig
And you would execute the job with the following command:
Copy code
shell dagster job execute --config my_config.yaml
4. Configuration Schema: If the
store_precog_results
op requires a configuration, ensure that the
config_schema
parameter is set correctly in the
@op
decorator to accept the configuration. If
LMEvalResultsConfig
is a Pydantic model, you would typically use it directly as the
config_schema
. 5. Execution: When executing the job, make sure you are providing the configuration in the manner expected by Dagster. If you are using the CLI, you should pass the configuration file using the
--config
option. If you've checked all of the above and the error persists, please provide more details about how you are executing the job and passing the configuration. This will help in pinpointing the exact issue. If the configuration is sensitive, make sure to redact any sensitive information before sharing.