Avatar for the BoundaryML user
BoundaryML
baml
BlogDocsChangelog

Performance History

Latest Results

Drop error modal from optimizer error handling (#3248) <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit ## Release Notes * **Bug Fixes** * Enhanced error diagnostics by building comprehensive error messages that include the full error chain and recent log information for better troubleshooting * Improved terminal user interface error handling to exit gracefully and display errors directly in the console instead of an overlay modal, providing clearer visibility <!-- end of auto-generated comment: release notes by coderabbit.ai -->
canary
2 hours ago
Special account slack linking (#3245) <!-- CURSOR_AGENT_PR_BODY_BEGIN --> # Pull Request Template Thanks for taking the time to fill out this pull request! ## Issue Reference Please link to any related issues - [ ] This PR fixes/closes #[issue number] ## Changes Please describe the changes proposed in this pull request This PR implements a feature to identify internal team members logging in via GitHub and link their accounts to their Slack profiles for enhanced notifications. Specifically, it: - Modifies the GitHub login flow to detect users with a `@boundaryml.com` email. - Updates the user schema to store `isSpecialAccount`, `boundaryEmail`, and `slackUserId`. - Automatically looks up and links the user's Slack ID when a special account logs in. - Updates Slack notifications for comments, BEP creations, and BEP version updates to mention the relevant user's Slack account (e.g., `<@USER_ID>`) if a `slackUserId` is available. ## Testing Please describe how you tested these changes - [ ] Unit tests added/updated - [ ] Manual testing performed (Suggested: Log in with a GitHub account linked to a `@boundaryml.com` email, then create a comment or BEP to verify Slack mentions.) - [ ] Tested in [environment] ## Screenshots If applicable, add screenshots to help explain your changes [Add screenshots here...] ## PR Checklist Please ensure you've completed these items - [ ] I have read and followed the contributing guidelines - [ ] My code follows the style guidelines of this project - [ ] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [ ] My changes generate no new warnings ## Additional Notes Add any other context about the PR here This implementation is "best effort." If a Slack user cannot be found for a given `boundaryml.com` email, notifications will fall back to using the user's display name without a Slack mention. [Slack Thread](https://gloo-global.slack.com/archives/C09F3QMJE9G/p1773447396472689?thread_ts=1773447396.472689&cid=C09F3QMJE9G) <div><a href="https://cursor.com/agents/bc-f13f5d28-9a38-5fa2-91be-7fc7b3a84dc9"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/assets/images/open-in-web-dark.png"><source media="(prefers-color-scheme: light)" srcset="https://cursor.com/assets/images/open-in-web-light.png"><img alt="Open in Web" width="114" height="28" src="https://cursor.com/assets/images/open-in-web-dark.png"></picture></a>&nbsp;<a href="https://cursor.com/background-agent?bcId=bc-f13f5d28-9a38-5fa2-91be-7fc7b3a84dc9"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/assets/images/open-in-cursor-dark.png"><source media="(prefers-color-scheme: light)" srcset="https://cursor.com/assets/images/open-in-cursor-light.png"><img alt="Open in Cursor" width="131" height="28" src="https://cursor.com/assets/images/open-in-cursor-dark.png"></picture></a>&nbsp;</div> <!-- CURSOR_AGENT_PR_BODY_END --> --------- Co-authored-by: Cursor Agent <cursoragent@cursor.com> Co-authored-by: hellovai <hellovai@users.noreply.github.com>
canary
2 days ago
SAP: appease the linter
kai/jsonish
2 days ago
SAP: parse_as tests
kai/jsonish
2 days ago
Bep activity Slack thread (#3241) <!-- CURSOR_AGENT_PR_BODY_BEGIN --> # Pull Request Template Thanks for taking the time to fill out this pull request! ## Issue Reference Please link to any related issues - [ ] This PR fixes/closes # ## Changes Please describe the changes proposed in this pull request This PR implements Slack notifications for BEP (Boundary Enhancement Proposal) activity, ensuring all updates and comments for a given BEP are posted within a single, dedicated thread in the `#beps` channel. - **New `slack.ts` module:** Handles posting messages to Slack, creating new threads, and replying to existing threads. - **Schema update:** Added `slackThreadTs` to the `beps` table to store the Slack thread timestamp, ensuring all related notifications for a BEP go into the same thread. - **Integration with BEP lifecycle:** - `beps.create`: Notifies when a new BEP is created, starting a new Slack thread. - `beps.update` (for new versions), `beps.importVersion`: Notifies when a new BEP version is published. - `beps.updateStatus`: Notifies when a BEP's status changes. - `comments.add`: Notifies when a new comment is added to a BEP. All notifications for a specific BEP are posted as replies within its dedicated Slack thread. ## Testing Please describe how you tested these changes - [ ] Unit tests added/updated - [ ] Manual testing performed (Requires `SLACK_BOUNDARY_BOT_TOKEN` to be configured) - [x] Tested in local development environment (Compilation and type checks passed) ## Screenshots If applicable, add screenshots to help explain your changes [Add screenshots here...] ## PR Checklist Please ensure you've completed these items - [ ] I have read and followed the contributing guidelines - [ ] My code follows the style guidelines of this project - [ ] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [ ] My changes generate no new warnings ## Additional Notes Add any other context about the PR here To enable Slack notifications, the `SLACK_BOUNDARY_BOT_TOKEN` environment variable must be configured in Convex. Notifications will gracefully fail if the token is not set. [Slack Thread](https://gloo-global.slack.com/archives/C09F3QMJE9G/p1773359991171989?thread_ts=1773359991.171989&cid=C09F3QMJE9G) <div><a href="https://cursor.com/agents/bc-518410a1-9ddc-51ef-9103-2f32d0c4c363"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/assets/images/open-in-web-dark.png"><source media="(prefers-color-scheme: light)" srcset="https://cursor.com/assets/images/open-in-web-light.png"><img alt="Open in Web" width="114" height="28" src="https://cursor.com/assets/images/open-in-web-dark.png"></picture></a>&nbsp;<a href="https://cursor.com/background-agent?bcId=bc-518410a1-9ddc-51ef-9103-2f32d0c4c363"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/assets/images/open-in-cursor-dark.png"><source media="(prefers-color-scheme: light)" srcset="https://cursor.com/assets/images/open-in-cursor-light.png"><img alt="Open in Cursor" width="131" height="28" src="https://cursor.com/assets/images/open-in-cursor-dark.png"></picture></a>&nbsp;</div> <!-- CURSOR_AGENT_PR_BODY_END --> --------- Co-authored-by: Cursor Agent <cursoragent@cursor.com> Co-authored-by: hellovai <hellovai@users.noreply.github.com>
canary
2 days ago
claude research for env and fs
avery/bedrock
3 days ago

Active Branches

SAP port to baml_language
last run
2 days ago
#3229
CodSpeed Performance Gauge
-1%
#3242
CodSpeed Performance Gauge
+13%
last run
3 days ago
#3239
CodSpeed Performance Gauge
-14%
Ā© 2026 CodSpeed Technology
Home Terms Privacy Docs