Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Live stream consuming can crash when inferences and specific filters are used #10201

Open
richard-julien opened this issue Mar 8, 2025 · 0 comments
Open

Live stream consuming can crash when inferences and specific filters are used #10201

richard-julien opened this issue Mar 8, 2025 · 0 comments
Assignees
@richard-julien
Labels
bug use for describing something not working as expected
Milestone
Release 6.5.6

Comments

@richard-julien
Copy link
Member

Description

Live stream consuming can crash when inferences and specific filters are used

Todo

Fix the response protection to not use req finished but res.writable.

Force types restriction in the resolution to prevent resolving direct meta relationships
@richard-julien richard-julien added bug use for describing something not working as expected needs triage use to identify issue needing triage from Filigran Product team and removed needs triage use to identify issue needing triage from Filigran Product team labels Mar 8, 2025
@richard-julien richard-julien self-assigned this Mar 8, 2025
@richard-julien richard-julien added this to the Release 6.5.6 milestone Mar 8, 2025
richard-julien added a commit that referenced this issue Mar 8, 2025
@richard-julien
[backend] Live stream consuming can crash when inferences and specifi…
2fef643 
…c filters are used (#10201)
@richard-julien richard-julien mentioned this issue Mar 8, 2025
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@richard-julien richard-julien

Labels
bug use for describing something not working as expected
Projects
None yet
Milestone
Release 6.5.6
Development

No branches or pull requests
1 participant
@richard-julien