Skip to content

feat: sse-events with vanguard#508

Merged
joroshiba merged 2 commits into
mainfrom
joroshiba/sse-vanguard
Oct 2, 2025
Merged

feat: sse-events with vanguard#508
joroshiba merged 2 commits into
mainfrom
joroshiba/sse-vanguard

Conversation

@joroshiba

@joroshiba joroshiba commented Sep 30, 2025

Copy link
Copy Markdown
Contributor

Summary

Updates to some dependencies which weren't at latest, and updates vanguard-go to utilize a fork I have created enabling SSE streams.

Background

Vanguard blocks streams via REST.

Issues

closes GRE-252

@socket-security

socket-security Bot commented Sep 30, 2025

Copy link
Copy Markdown

@joroshiba joroshiba marked this pull request as ready for review September 30, 2025 22:43

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR updates dependencies to their latest versions and integrates a forked version of vanguard-go to enable Server-Sent Events (SSE) streaming support. The changes address the limitation where the standard Vanguard library blocks streams via REST.

  • Updated multiple dependencies including connect, validate, vanguard, and various other packages to their latest versions
  • Replaced the official vanguard package with a custom fork that supports SSE streaming
  • Modified server configuration to enable REST Server-Sent Events for the thread service

Reviewed Changes

Copilot reviewed 2 out of 3 changed files in this pull request and generated 1 comment.

File Description
tim-api/internal/server/server.go Updated validate interceptor initialization and enabled SSE for thread service
tim-api/go.mod Updated dependencies and replaced vanguard with custom fork supporting SSE

Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.

Comment thread tim-api/go.mod Outdated
)

replace (
connectrpc.com/vanguard => github.com/joroshiba/vanguard-go v0.0.0-20250930221328-b9a1ff0dc494

Copilot AI Sep 30, 2025

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Using a personal fork with a pseudo-version (v0.0.0-...) creates dependency maintenance risks. Consider creating a proper release tag in the fork or submitting the SSE changes upstream to the official vanguard repository for better long-term maintainability.

Suggested change
connectrpc.com/vanguard => github.com/joroshiba/vanguard-go v0.0.0-20250930221328-b9a1ff0dc494
connectrpc.com/vanguard => github.com/joroshiba/vanguard-go v0.1.0

Copilot uses AI. Check for mistakes.
@joroshiba

Copy link
Copy Markdown
Contributor Author

Note, I have opened a PR into the upstream: connectrpc/vanguard-go#176

@jbowen93 jbowen93 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit

if err != nil {
return err
}
validateInterceptor := validate.NewInterceptor()

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it fine to not check this err?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

With the latest version of vanguard, there is no error returned by the new operator

@joroshiba joroshiba force-pushed the joroshiba/sse-vanguard branch from 8d8a486 to e51019f Compare October 1, 2025 21:54
@linear

linear Bot commented Oct 2, 2025

Copy link
Copy Markdown

@joroshiba joroshiba added this pull request to the merge queue Oct 2, 2025
Merged via the queue into main with commit 4dc6caa Oct 2, 2025
41 checks passed
@joroshiba joroshiba deleted the joroshiba/sse-vanguard branch October 2, 2025 17:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants