-
-
Notifications
You must be signed in to change notification settings - Fork 4.6k
WIP: Clean up after full attachments rollout #104092
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
base: master
Are you sure you want to change the base?
Conversation
❌ 6 Tests Failed:
View the top 3 failed test(s) by shortest run time
To view more test analytics, go to the Test Analytics Dashboard |
3eb26a1 to
373fa6c
Compare
373fa6c to
0167520
Compare
This cleans up the codebase after attachmens on objectstore has been fully rolled out. It assumes that attachments are now fully stored from within relay, and assumes that no attachment chunks will ever be emitted. Thus, there is no more need for the attachments cache, or the chunk message handlers. All feature flags related to objectstore rollout are removed and hardcoded.
0167520 to
58fd0d4
Compare
|
This issue has gone three weeks without activity. In another week, I will close it. But! If you comment or otherwise update it, I will reset the clock, and if you remove the label "A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀 |
|
This issue has gone three weeks without activity. In another week, I will close it. But! If you comment or otherwise update it, I will reset the clock, and if you remove the label "A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀 |
This cleans up the codebase after attachmens on objectstore has been fully rolled out. It assumes that attachments are now fully stored from within relay, and assumes that no attachment chunks will ever be emitted.
Thus, there is no more need for the attachments cache, or the chunk message handlers. All feature flags related to objectstore rollout are removed and hardcoded.