Commit Graph

11842 Commits

Author SHA1 Message Date
Roman Chvanikov
0223dc4e02 Add migration 2019-10-26 22:38:07 +03:00
Roman Chvanikov
d12555a69e Add migration 2019-10-26 22:37:30 +03:00
Roman Chvanikov
7ac42fefe3 Add migration 2019-10-26 22:36:43 +03:00
Roman Chvanikov
c1ff8472fd Add migration 2019-10-26 22:33:18 +03:00
Roman Chvanikov
5cb03fe801 Add migration 2019-10-26 22:32:31 +03:00
Roman Chvanikov
cd0218c205 Add migration 2019-10-26 22:31:25 +03:00
Roman Chvanikov
6e7fd364a4 Add migration 2019-10-26 22:28:18 +03:00
kaniini
beee3e75a8 Merge branch 'conversation-read-status-for-blocking-user' into 'develop'
Count only visible conversations in the user's unread_conversation_count

See merge request pleroma/pleroma!1886
2019-10-26 10:37:27 +00:00
rinpatch
12ab7b3280 User info migration improvements
- Move column additions into a separate migration, so postgres doesn't
need an exclusive lock on the table for the main part
- Fill in columns by using one big update statement instead of a bunch
of small ones because it's much faster (the migration took 140s on
patch.cx database)
2019-10-26 03:45:24 +03:00
eugenijm
0580654485 Mark the conversations with the blocked user as read and update the blocking user's unread_conversation_count.
Since the conversations with the blocked user are invisible, they are excluded
from the blocking user's `unread_conversation_count`.
2019-10-26 02:29:18 +03:00
lain
a43b899e94 Merge branch 'release/1.1.3' into 'stable'
1.1.3 release

See merge request pleroma/pleroma!1884
2019-10-25 17:08:01 +00:00
rinpatch
948d0d3b0b mixfile: bump version to 1.1.3 2019-10-25 18:49:21 +03:00
rinpatch
3627ffc8b7 Changelog: Add 1.1.3 entry 2019-10-25 18:46:28 +03:00
rinpatch
ca1871fbb4 Do not include notifications from blocked users when with_muted is set
This is not what with_muted is for per documentation and it was agreed
on irc that this behavior doesn't make sense.
2019-10-25 18:44:23 +03:00
rinpatch
e91d5a23f4 pleroma_ctl: fix crashes due to different shift(1) behavior on dash 2019-10-25 18:32:09 +03:00
rinpatch
653054d301 Merge branch 'remove-unsed-info-fields-fn' into 'develop'
Remove unused Pleroma.User.info_fields/0

See merge request pleroma/pleroma!1882
2019-10-25 14:51:02 +00:00
Egor Kislitsyn
b777083f3f
Add also_known_as field to Pleroma.User 2019-10-25 19:14:18 +07:00
Egor Kislitsyn
dbee53c2df
Remove unused Pleroma.User.info_fields/0 2019-10-25 16:48:01 +07:00
kaniini
96cd66ac1b Merge branch 'fix/pleroma-ctl-fix-shift-dash' into 'develop'
pleroma_ctl: fix crashes due to different shift(1) behavior on dash

See merge request pleroma/pleroma!1880
2019-10-25 00:24:01 +00:00
kaniini
40a2a92a1f Merge branch 'object-fetch-errors' into 'develop'
Object fetch errors

See merge request pleroma/pleroma!1881
2019-10-25 00:22:50 +00:00
rinpatch
f3451e723b pleroma_ctl: fix crashes due to different shift(1) behavior on dash 2019-10-24 23:28:59 +03:00
stwf
5329b361ec fix test 2019-10-24 12:48:17 -04:00
stwf
2ab072f949 object fetcher error handling 2019-10-24 12:08:34 -04:00
Maksim Pechnikov
922e3d082c add test 2019-10-24 12:17:50 +03:00
kaniini
07a6f8b8a3 Merge branch 'fix/readme' into 'develop'
fix link on docs-develop.pleroma.social

See merge request pleroma/pleroma!1876
2019-10-24 08:34:35 +00:00
Egor Kislitsyn
4c1dd55c48 Merge remote-tracking branch 'upstream/develop' into refactor/following-relationships 2019-10-24 14:55:36 +07:00
Maksim Pechnikov
a57f0dbd42 fix link on docs-develop.pleroma.social 2019-10-24 09:58:37 +03:00
Maksim Pechnikov
99cf1ef9be Merge branch 'develop' into issue/1276 2019-10-24 09:23:59 +03:00
Maksim Pechnikov
d3fb9e02cc add tests 2019-10-23 22:48:04 +03:00
Maxim Filippov
b08b1d5d91 Store status data inside Flag activity 2019-10-23 21:27:22 +02:00
Maksim Pechnikov
aa64b3108b fix migrate 2019-10-23 22:02:59 +03:00
feld
17c237ba80 Merge branch '1304-user-info-deprecation' into 'develop'
[#1304] User.Info deprecation

Closes #1304

See merge request pleroma/pleroma!1851
2019-10-23 17:34:42 +00:00
Ivan Tashkinov
c0246309a5 [#1304] Extra bullet-proofing. 2019-10-23 19:30:02 +03:00
Ivan Tashkinov
065e9fac12 [#1304] Adjusted User.Info references from Notification. 2019-10-23 17:31:02 +03:00
Ivan Tashkinov
8cc809e44e Merge remote-tracking branch 'remotes/upstream/develop' into 1304-user-info-deprecation
# Conflicts:
#	lib/pleroma/notification.ex
2019-10-23 17:22:42 +03:00
Ivan Tashkinov
11cd994425 [#1304] Fixed null::jsonb handling in User.Info migration. 2019-10-23 17:15:48 +03:00
lain
25077812bf SideEffectsTest: Fix test. 2019-10-23 12:25:20 +02:00
lain
1adafa0966 Credo fixes. 2019-10-23 12:18:05 +02:00
lain
97d5c79aa0 Add Pipeline module, test for federation. 2019-10-23 11:52:27 +02:00
Maksim Pechnikov
9a4afbd2a0 added update unread_count for notifications 2019-10-23 11:22:48 +03:00
kaniini
54077677ea Merge branch 'bugfix/announce-with-bare-to-cc' into 'develop'
activitypub: visibility: refactor is_public?() to use JSON-LD safe accessors

Closes #1326

See merge request pleroma/pleroma!1874
2019-10-23 02:25:08 +00:00
Ariadne Conill
3f6a596922 activitypub: visibility: refactor is_public?() to use JSON-LD safe accessors 2019-10-22 20:50:46 -05:00
kaniini
894fb806e9 Merge branch 'chore/add-single-value-deserialization-tests' into 'develop'
tests: transmogrifier: add explicit regression tests for JSON-LD strings as single-element array fuckery

See merge request pleroma/pleroma!1873
2019-10-23 00:47:28 +00:00
Ariadne Conill
277aea45b9 tests: transmogrifier: add explicit regression tests for JSON-LD string to single-element array deserialization
There appears to be confusion on whether or not Pleroma can handle this particular
sin of JSON-LD.  It can, and we will add regression tests to prove that it can handle
this particular sin.  Which, by the way, this is actually not a "feature" of JSON-LD,
but whatever.
2019-10-22 19:43:31 -05:00
Mark Felder
752d0c6833 Relocate to configuration subdir 2019-10-22 15:14:04 -05:00
Mark Felder
47a551837a Remove proxy_cache_lock suggestion 2019-10-22 15:13:42 -05:00
Mark Felder
b9d164fb89 Formatting 2019-10-22 14:12:01 -05:00
Mark Felder
a1ad8dc349 Leverage nginx proxy cache to store items with a 1 year TTL with no size limit.
It does not purge items when they expire, but will only update them if the origin's
copy has changed for some reason. If origin is offline/unavailable or gone forever
it will still serve the cached copies.
2019-10-22 14:07:59 -05:00
Mark Felder
c077dc7af5 Initial doc about storing remote media 2019-10-22 11:52:21 -05:00
Maksim Pechnikov
d4270397dc Marker: added unread_count field 2019-10-22 14:51:46 +03:00