mastodon

Commit Graph

Author	SHA1	Message	Date
Shlee	34d7c9edae	Rails 7+: primary_abstract_class recommendation (#32909 )	1 month ago
Claire	95e9de5777	Prevent accidental serialization of `Account` and `User` records (#30079 )	8 months ago
Claire	39da3d86f8	Fix ActiveRecord using two connection pools when no replica is defined (#27061 )	1 year ago
Claire	2c204d904b	Change `DB_REPLICA_` environment variables to `REPLICA_DB_` (#26386 )	1 year ago
Claire	3105fef21a	Rename “read” database to “replica” for consistency (#26326 )	1 year ago
Claire	5cbc402687	Fix replica being used even if not explicitly defined (#26074 )	1 year ago
Eugen Rochko	26e522ac55	Fix not actually connecting to the configured replica (#25977 )	1 year ago
Eugen Rochko	5c42f47617	Fix records not being indexed sometimes (#12024 ) It's possible that after commit callbacks were not firing when exceptions occurred in the process. Also, the default Sidekiq strategy does not push indexing jobs immediately, which is not necessary and could be part of the issue too.	5 years ago
Eugen Rochko	115dab78f1	Change admin UI for hashtags and add back whitelisted trends (#11490 ) Fix #271 Add back the `GET /api/v1/trends` API with the caveat that it does not return tags that have not been allowed to trend by the staff. When a hashtag begins to trend (internally) and that hashtag has not been previously reviewed by the staff, the staff is notified. The new admin UI for hashtags allows filtering hashtags by where they are used (e.g. in the profile directory), whether they have been reviewed or are pending reviewal, they show by how many people the hashtag is used in the directory, how many people used it today, how many statuses with it have been created today, and it allows fixing the name of the hashtag to make it more readable. The disallowed hashtags feature has been reworked. It is now controlled from the admin UI for hashtags instead of from the file `config/settings.yml`	5 years ago
Akihiko Odaki	40e5d2303b	Validate HTTP response length while receiving (#6891 ) to_s method of HTTP::Response keeps blocking while it receives the whole content, no matter how it is big. This means it may waste time to receive unacceptably large files. It may also consume memory and disk in the process. This solves the inefficency by checking response length while receiving.	7 years ago
Eugen Rochko	fdc17bea58	Fix rubocop issues, introduce usage of frozen literal to improve performance	8 years ago
Eugen Rochko	10ba09f546	Upgrade to Rails 5.0.0.1	8 years ago

12 Commits (65cea8f89f7c6453e6709f834a39b4552a330743)