-
Notifications
You must be signed in to change notification settings - Fork 2
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
New Search and Profile Frontend #62
Conversation
implement streaming response
- name: AUTH_SECRET | ||
value: 05mk7ukF/GSG1dHLYVp04Mxa49slQb2W3N9v1aMcRTM= |
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.
@AsmiKloud these kinds of secrets should probably be retrieved from our secret manager, right? :)
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.
I see some other ones here as well btw, like the posthog key.
} | ||
|
||
const text = decoder.decode(value, { stream: true }) | ||
const lines = text.split('\n').filter(Boolean) |
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.
True. There is also TextDecoderStream, so that we could decode during streaming and get strings directly.
…-fix Update deployment.yaml
Update service.yaml
Ignore all the changes that are not from the frontend folder. Those changes are from eng-179. Which is already merged.