-
Notifications
You must be signed in to change notification settings - Fork 2.4k
fix: issue when parsing recipe parameters #3031
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
| } | ||
|
|
||
| fn extract_parameters_from_content(content: &str) -> Result<Option<Vec<RecipeParameter>>> { | ||
| let lines = content.lines(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@DOsinga Is this block of logic is intentional? Just to confirm as I have deleted.
| } | ||
|
|
||
| // If we didn't find a parameter block it might be because it is defined in json style or some such: | ||
| if serde_yaml::from_str::<serde_yaml::Value>(content).is_err() { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@DOsinga do we still need below as the next block also parse the content to recipe?
serde_yaml::from_str::<serde_yaml::Value>(content).is_err()
also shall we parse both json and yaml file here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
any json file is also yaml, so no need to parse that twice
…text-addition * upstream/main: fix temporal build for windows (block#3045) fix cron parsing for windows (block#3044) feat: list Databricks-supported models and enable fuzzy search during model configuration (block#3039) fix: update index when tool selection strategy changes (block#2991) docs: Add "Add Recipe button" To Recipe Cookbook (block#3038) fix: issue when parsing recipe parameters (block#3031) fix: Improves reliability of flaky log tests (block#3029)
* main: fix temporal build for windows (#3045) fix cron parsing for windows (#3044) feat: list Databricks-supported models and enable fuzzy search during model configuration (#3039) fix: update index when tool selection strategy changes (#2991) docs: Add "Add Recipe button" To Recipe Cookbook (#3038) fix: issue when parsing recipe parameters (#3031)
# By Alice Hau (6) and others # Via Alice Hau * ahau/tool-strategy: (27 commits) fix merge merged updated computercontroller and developer descriptions add additional strats to test fmt update to get vector db path from env var feat: list Databricks-supported models and enable fuzzy search during model configuration (#3039) fix: update index when tool selection strategy changes (#2991) docs: Add "Add Recipe button" To Recipe Cookbook (#3038) fix: issue when parsing recipe parameters (#3031) fix: Improves reliability of flaky log tests (#3029) Add xAI Test Coverage (#3020) Reorganizing tutorials (#3028) feat(providers): update Google Gemini models to latest available models (#2989) fix(docker): install protoc to fix lance-encoding build (#2995) fix: updated openrouter known models (#3021) Mnovich/temporal foreground tasks (#2895) add 'install in goose' asset (#3016) Added useDarkMode hook for detecting dark mode setting dynamically (#3019) docs: add sagemaker provider (#2980) ... # Conflicts: # .gitignore # crates/goose/src/agents/router_tools.rs
Signed-off-by: Soroosh <[email protected]>
Why
When running a recipe with parameters, it shows error mssage:
Missing definitions for parameters in the recipe file: dateWhat
Removed code to parsing parameter block line by line. The logic seems like: when the "parameters" line is reached, and then return empty parameters.
Modified the test cases with correct
blocksection as example so that parameters can be parsed properlyAsked a couple questions as inline comments to be confirmed