Fix/url parse error #644
Merged
Fix/url parse error #644
Conversation
This file contains 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
…nalysis - Introduced a new module for filtering static resources and CDN links from URLs, including functions for analyzing URLs with LLM and programmatic checks. - Implemented a schema for batch analysis of URLs using Zod for validation. - Updated the `crawlExtractedUrls` function to optionally skip CDN filtering, enhancing flexibility in URL processing. - Ensured compliance with code style rules, including the use of single quotes for string literals.
…oken limit - Introduced MAX_URL_SOURCES_TOKENS constant to define the maximum token limit for URL sources, calculated as double the MAX_OUTPUT_TOKENS_LEVEL3. - Updated semanticSearch utility functions to utilize MAX_URL_SOURCES_TOKENS when processing page content from URL sources, ensuring efficient token management. - Ensured compliance with code style rules, including the use of single quotes for string literals.
- Wrapped context preparation logic in try-catch blocks to handle unexpected errors gracefully, logging errors and returning empty results when necessary. - Ensured proper logging of relevant context tokens and remaining tokens throughout the process for better traceability. - Updated semantic search functions to include error handling, returning fallback values in case of failures. - Ensured compliance with code style rules, including the use of single quotes for string literals.
- Integrated resetFailedState function to manage failed result IDs, preventing auto-restarting of polling for failed actions. - Updated SkillResponseNode and SkillResponseNodePreviewComponent to utilize resetFailedState before retrying actions, improving error handling. - Ensured compliance with code style rules, including the use of single quotes for string literals and proper dependency management in useEffect hooks.
…omponent - Implemented a null check for the artifact title to prevent rendering issues when the title is undefined. - Ensured compliance with code style rules, including the use of single quotes for string literals and proper handling of optional chaining.
mrcfps
approved these changes
Mar 24, 2025
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
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Tip
Close issue syntax:
Fixes #<issue number>orResolves #<issue number>, see documentation for more details.Impact Areas
Please check the areas this PR affects:
Screenshots/Videos
Checklist
Important
Please review the checklist below before submitting your pull request.
dev/reformat(backend) andcd web && npx lint-staged(frontend) to appease the lint gods