-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
feat(assistant): cdp #3305
Merged
Merged
feat(assistant): cdp #3305
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
… rendering Refactor the chapter_body method in the PDFGenerator class to improve the rendering of content in the generated PDF. The changes include: - Adding line breaks before headers (lines starting with '#', '##', '###') for better readability. - Setting different font sizes for different header levels to create a visual hierarchy. - Handling each line of content individually to ensure proper rendering and formatting. This commit message follows the established convention of using a prefix to indicate the type of change (`chore` for chore) and provides a clear and concise description of the purpose of the changes.
…utils.py Refactor the organization and formatting of comparison sections in the `utils.py` file. This change includes the following modifications: - Use double asterisks (`**`) instead of single asterisks (`*`) to denote section names and text labels for better visual distinction. - Add line breaks before each section name for improved readability. - Replace occurrences of `<text 1>` and `<text 2>` with `{text_1}` and `{text_2}` respectively in the report template. This commit message follows the established convention of using a prefix to indicate the type of change (`chore` for chore) and provides a clear and concise description of the purpose of the changes.
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
dosubot
bot
added
size:L
This PR changes 100-499 lines, ignoring generated files.
area: backend
Related to backend functionality or under the /backend directory
labels
Oct 3, 2024
This was referenced Oct 3, 2024
Suspect IssuesThis pull request was deployed and Sentry observed the following issues:
Did you find this useful? React with a 👍 or 👎 |
StanGirard
added a commit
that referenced
this pull request
Oct 7, 2024
🤖 I have created a release *beep* *boop* --- ## 0.0.320 (2024-10-07) ## What's Changed * Enable Porter Application cdp by @porter-deployment-app in #3306 * Enable Porter Application cdp-front by @porter-deployment-app in #3307 * feat(assistant): cdp by @StanGirard in #3305 * feat: Add debug logging for OCR results by @StanGirard in #3309 * feat: Update OCR image scale for better accuracy by @StanGirard in #3310 * feat: Update PDFGenerator to include logo in header by @StanGirard in #3311 * feat: structlog parseable by @AmineDiro in #3312 * Revert "feat: structlog parseable" by @StanGirard in #3313 * feat: structlog parseable by @AmineDiro in #3314 * Revert "feat: structlog parseable" by @StanGirard in #3315 * feat: Update PDFGenerator to include logo in header by @StanGirard in #3318 * feat: structlog parseable by @AmineDiro in #3319 * feat: Update knowledge status and send notification on task success by @StanGirard in #3320 * feat: Update text retranscription instructions by @StanGirard in #3321 * feat: update sentry by @StanGirard in #3326 * chore: Remove unnecessary assertion in create_modification_report function by @StanGirard in #3329 * chore: Add NEXT_PUBLIC_INTERCOM_APP_ID to Dockerfile by @StanGirard in #3330 * feat: Update Content Security Policy for PostHog by @StanGirard in #3331 * fix(cdp): order naming cdc_etiquette by @StanGirard in #3333 * fix(notifications): added a debouncing mechanism by @StanGirard in #3327 **Full Changelog**: v0.0.319...v0.0.320 --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
StanGirard
added a commit
that referenced
this pull request
Oct 16, 2024
🤖 I have created a release *beep* *boop* --- ## [0.0.17](core-0.0.16...core-0.0.17) (2024-10-16) ### Features * **assistant:** cdp ([#3305](#3305)) ([b767f19](b767f19)) * **assistants:** mock api ([#3195](#3195)) ([282fa0e](282fa0e)) * introducing configurable retrieval workflows ([#3227](#3227)) ([ef90e8e](ef90e8e)) ### Bug Fixes * fixing pdf parsing ([#3349](#3349)) ([367242a](367242a)) ### Documentation * **core:** init ([#3365](#3365)) ([bb572a2](bb572a2)) * **fix:** fixed warnings from griffe ([#3381](#3381)) ([1a38798](1a38798)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area: backend
Related to backend functionality or under the /backend directory
size:L
This PR changes 100-499 lines, ignoring generated files.
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.
Description
Please include a summary of the changes and the related issue. Please also include relevant motivation and context.
Checklist before requesting a review
Please delete options that are not relevant.
Screenshots (if appropriate):