| Age | Commit message (Collapse) | Author |
|---|
|
Document way to do notice compatibility routes with Nginx reverse-proxy, fixes #2900
Closes #2900
See merge request pleroma/pleroma!3701
|
|
CI: Remove cache on cycles
See merge request pleroma/pleroma!3704
|
|
cycles uses a different system than the rest of the testing_cache, creating errors like libcrypto.so.1 being missing
|
|
There were async calls happening, so they weren't always finished when assert happened.
|
|
application does not depend on :logger"
During compilation, we had the following warning which is now fixed
```
==> restarter
Compiling 1 file (.ex)
warning: Logger.__do_log__/4 defined in application :logger is used by the current application but the current application does not depend on :logger. To fix this, you must do one of:
1. If :logger is part of Erlang/Elixir, you must include it under :extra_applications inside "def application" in your mix.exs
2. If :logger is a dependency, make sure it is listed under "def deps" in your mix.exs
3. In case you don't want to add a requirement to :logger, you may optionally skip this warning by adding [xref: [exclude: [Logger]]] to your "def project" in mix.exs
Invalid call found at 2 locations:
lib/pleroma.ex:65: Restarter.Pleroma.handle_cast/2
lib/pleroma.ex:78: Restarter.Pleroma.handle_cast/2
warning: Logger.__should_log__/2 defined in application :logger is used by the current application but the current application does not depend on :logger. To fix this, you must do one of:
1. If :logger is part of Erlang/Elixir, you must include it under :extra_applications inside "def application" in your mix.exs
2. If :logger is a dependency, make sure it is listed under "def deps" in your mix.exs
3. In case you don't want to add a requirement to :logger, you may optionally skip this warning by adding [xref: [exclude: [Logger]]] to your "def project" in mix.exs
Invalid call found at 2 locations:
lib/pleroma.ex:65: Restarter.Pleroma.handle_cast/2
lib/pleroma.ex:78: Restarter.Pleroma.handle_cast/2
warning: Logger.debug/1 defined in application :logger is used by the current application but the current application does not depend on :logger. To fix this, you must do one of:
1. If :logger is part of Erlang/Elixir, you must include it under :extra_applications inside "def application" in your mix.exs
2. If :logger is a dependency, make sure it is listed under "def deps" in your mix.exs
3. In case you don't want to add a requirement to :logger, you may optionally skip this warning by adding [xref: [exclude: [Logger]]] to your "def project" in mix.exs
Invalid call found at 2 locations:
lib/pleroma.ex:65: Restarter.Pleroma.handle_cast/2
lib/pleroma.ex:78: Restarter.Pleroma.handle_cast/2
```
|
|
|
|
|
|
Signed-off-by: marcin mikołajczak <git@mkljczk.pl>
|
|
Shrink CI
See merge request pleroma/pleroma!3691
|
|
Translatable config descriptions
Closes pleroma-meta#65
See merge request pleroma/pleroma!3695
|
|
|
|
MastoAPI: Use `types` for filtering notifications
See merge request pleroma/pleroma!3648
|
|
DOCS: Add some small piece about setting up a Gitlab-runner
See merge request pleroma/pleroma!3694
|
|
Signed-off-by: marcin mikołajczak <git@mkljczk.pl>
|
|
|
|
|
|
|
|
This was done by floatingghost as part of a bigger commit in Akkoma.
See <https://akkoma.dev/AkkomaGang/akkoma/src/commit/37ae047e1652c4089934434ec79f393c4c839122/lib/pleroma/application.ex#L83>.
As explained in <https://ihatebeinga.live/objects/860d23e1-dc64-4b07-8b4d-020b9c56cff6>
> there are so many caches that clearing them all can nuke the supervisor, which by default will become an hero if it gets more than 3 restarts in <5 seconds
And further down the thread
> essentially we've got like 11 caches (https://akkoma.dev/AkkomaGang/akkoma/src/commit/37ae047e1652c4089934434ec79f393c4c839122/lib/pleroma/application.ex#L165)
> then in test we fetch them all (https://akkoma.dev/AkkomaGang/akkoma/src/branch/develop/test/support/data_case.ex#L50) and call clear on them
> so if this clear fails on any 3 of them, the pleroma supervisor itself will die
How it fails?
> idk maybe cachex dies, maybe :ets does a weird thing
> it doesn't log anything, it just consistently dies during cache clearing so i figured it had to be that
> honestly my best bet is locksmith and queuing
> https://github.com/whitfin/cachex/blob/master/lib/cachex/actions/clear.ex#L26
> clear is thrown into a locksmith transaction
> locksmith says
> >If the process is already in a transactional context, the provided function will be executed immediately. Otherwise the required keys will be locked until the provided function has finished executing.
> so if we get 2 clears too close together, maybe it locks, then doesn't like the next clear?
|
|
Translate static_pages.po (Simplified Chinese)
See merge request pleroma/pleroma!3655
|
|
|
|
|
|
|
|
|
|
|
|
This is based on me setting one up, but I kept it general with mostly linking to other documentation.
The idea is that to just provide some Pleroma-specific info, maybe give some pointers, and point to the right (external) docs.
|
|
Add short_description instance field
Closes #2865
See merge request pleroma/pleroma!3651
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
into 'develop'
Make checking blacklisted domains and restricted nicknames case-insensitive
Closes #2894 and #2888
See merge request pleroma/pleroma!3687
|
|
|
|
Pass remote follow avatar into media proxy
Closes #2830
See merge request pleroma/pleroma!3690
|
|
|
|
|
|
It used a timer to sleep.
But time also goes on when doing other things, so depending on hardware, the timings could be off.
I slightly changed the tests so we still test what we functionally want.
Instead of waiting until the cache expires I now have a function to expire the test and use that.
That means we're not testing any more if the cache really expires after a certain amount of time,
but that's the responsability of the dependency imo, so shouldn't be a problem.
I also changed `Pleroma.Web.Endpoint, :http, :ip` to `127.0.0.1` because that's the setting people typically have,
and I see no reason to do it differently.
Especially since it's an exernal ip, which may come over as weird or suspicious to people.
|
|
Signed-off-by: marcin mikołajczak <git@mkljczk.pl>
|
|
do restricted nickname validation in LDAP account registration
|
|
|
|
Fix long report notes giving errors on creation
See merge request pleroma/pleroma!3679
|
|
These changes make the encoding for the fully-qualified heart emoji very visible in editors.
|
|
mix: update eblurhash to 1.2.2
See merge request pleroma/pleroma!3686
|
|
Add index hotspots
See merge request pleroma/pleroma!3664
|
|
Use EXIF data of image for image description
See merge request pleroma/pleroma!3535
|
|
Bugfix: Validate mediaType only by it's format
See merge request pleroma/pleroma!3597
|
|
Server announcements (1st pass)
See merge request pleroma/pleroma!3643
|
|
Previous eblurhash versions bundled precompiled binaries which caused
issues on non-Darwin operating systems.
|
