* origin/develop: (213 commits)
Apply 1 suggestion(s) to 1 file(s)
ReverseProxy tesla client: remove handling of old_conn
ReverseProxy: Fix a gun connection leak when there is an error with no body
OpenAPI: remove accidentally pasted buffer data
OpenAPI: Replace actor_id by account_id to follow ChatMessage schema
Update types in Pleroma.Formatter group
added migrate old settings to new
Ensure Oban is available during mix tasks. Fixes: mix pleroma.user rm username
Fix mix tasks that make HTTP calls by starting the Gun connection pool
remove duplicate module
Support blocking via query parameters as well and document the change.
[#2791] AccountView: renamed `:force` option to `:skip_visibility_check`.
added warning to use old keys
Update linkify migration tests to use config from ConfigDB
Migration to fix malformed Pleroma.Formatter config
Refactor require_migration/1 into a test helper function
Add AutolinkerToLinkify migration test
Fix linkify ConfigDB migration
[#1973] Fixed accounts rendering in GET /api/v1/pleroma/chats with truish :restrict_unauthenticated. Made `Pleroma.Web.MastodonAPI.AccountView.render("show.json", _)` demand :for or :force option in order to prevent incorrect rendering of empty map instead of expected user representation with truish :restrict_unauthenticated setting.
Add related_policy field
...
The new pooling code just removes the connection when it's down,
there is no need to reconnect a connection that is just sitting idle,
better just open a new one next time it's needed
This patch refactors gun pooling to use Elixir process registry and
simplifies adapter option insertion.
Having the pool use process registry instead of a GenServer has a number of advantages:
- Simpler code: the initial implementation adds about half the lines of code it deletes
- Concurrency: unlike a GenServer, ETS-based registry can handle multiple checkout/checkin
requests at the same time
- Precise and easy idle connection clousure: current proposal for closing idle connections in
the GenServer-based pool needs to filter through all connections once a minute and compare their
last active time with closing time. With Elixir process registry this can be done
by just using `Process.send_after`/`Process.cancel_timer` in the worker process.
- Lower memory footprint: In my tests `gun-memory-leak` branch uses about 290mb on peak load (250 connections)
and 235mb on idle (5-10 connections). Registry-based pool uses 210mb on idle and 240mb on peak load
* origin/develop: (53 commits)
Add warning against parsing/reusing MastoFE settings blob
Update NotificationOperation spec
Add `is_muted` to notifications
Translated using Weblate (Italian)
Added translation using Weblate (Italian)
Add include for the "Further reading" section
HellthreadPolicy: Restrict to Notes and Articles.
Apply suggestion to lib/pleroma/web/api_spec/operations/pleroma_emoji_pack_operation.ex
proper error codes for error in adminFE
Apply suggestion to lib/pleroma/web/api_spec/operations/pleroma_emoji_pack_operation.ex
cheatsheet.md: no_attachment_links → attachment_links
fix for packs pagination
Stop filling conversation field on incoming objects (legacy, unused)
Only accounts with Service actor_type are considered as bots
Add support for bot field in update_credentials
README: Add some troubleshooting info for compilation issues.
[#1873] Fixes missing :offset pagination param support. Added pagination support for hashtags search.
default page size for files
changelog entry
adding overall count for packs and files
...
* origin/develop: (276 commits)
Remove `poll` from `notification_type` OpenAPI spec
credo fix
CHANGELOG.md: mention minimal elixir version update
Update OTP releases to official images of 1.10.3
Chunk the notification type backfill migration
moving custom ecto types in context folders
Upgrade to Elixir 1.9
naming
fix attemps to merge map
fix for updated hackney
Mogrify args as custom tuples
Fix tests
Changelog: Add info about conversation view changes.
Conversations: Return last dm for conversation, not last message.
Mastodon API: ensure the notification endpoint doesn't return less than the requested amount of records unless it's the last page
ControllerHelper: Always return id field.
Apply suggestion to lib/pleroma/web/controller_helper.ex
Remove use of atoms in MRF.UserAllowListPolicy
Fix atom leak in Rich Media Parser
Return an empty map from Pleroma.Web.RichMedia.Parsers.OGP.parse/2
...