We just ran an update to our implementation of Discourse and now the system bot is removing full quotes from user comments. This is breaking the context in replies that respond to multiple comments. I’ll add some screen shots to hopefully help,
Here is a screen shot of the Notification of the system bot’s actions editing the posts.
I’m also from the same Forum Nick is a part of, this migration ended up queueing every single historical post into Sidekiq. This proves to be a giant performance hit on the Discourse instance and is triggering hundreds of thousands of database calls, notifications, etc.
That’s a new feature to reduce duplicate content. It should only remove full quotes of the preceding post (and only if it’s the only quote in the post).
This screenshot is likely a bug. @nbianca can you have a look?
I’m fine with the feature of not having whole posts quoted, but I guess my questions revolve around the process behind the update.
Why would system notify each and every individual user that their post has been updated?
Is the intention to lean on Sidekiq for this task? If so is it acceptable to delay every other sidekiq powered feature (emails / notifications) because of an upgrade “migration”?
Our Discourse seems to be processing 5k posts per hour, so I guess we have 22 hours of upgrade pain to wade through?
Something’s wrong with your instance as this feature is not retroactive and only applies to new posts. The CrawlTopicLink jobs are coming from something else…
I hope you can add an on/off option as full quotes are not a bother on our forum, sometimes they add to the effect, sometimes are far enough down the thread it saves time wondering and wandering back through to find out what the reply means.
I do not believe this should be a mandatory setting.