Federation: Join/Leave circle non-responsive

changed the description

mentioned in issue management/core-team#3

@jbpasquier we tested this and it works correctly when we are running localhost with test1 as the config, is there a difference with the front-end of test1?

@calummackervoy No difference

@matthieu That's the one I spoke you about, after few more tests it still works on some instances and not on others. Pretty weird.

Yes indeed. If it's used with 0.9, it's only related to the workarounds of the sib-app as there is no reactivity in the framework yet, right?

Absolutely :)

Still, it does works on some instance and not on others. I have no workaround to the workaround of the workaround.

Anyway, I give all my hope on 0.10 to solve this one.

I did some more debugging

for the leave circle case it's a race condition: the GET CirclesJoinable is executed before the server has processed the delete CircleMember signal, meaning that the resource appears to refresh the circles-joinable whilst test2 still believes the test1 user is a member

from the logs:

[Circles-Joinable] super().get_queryset() = <QuerySet [<Circle: Test 2 Circle>]>
[Circles-Joinable] excluded external ids = <QuerySet [<Circle: Test 2 Circle>]>
[Circles-Joinable] excluded user 19 circles = <QuerySet []>
[Circles-Joinable] excluded Private/Archived circles = <QuerySet []>
[Sender] Received deleted non-backlink instance Test 2 Circle - Unknown Unknown(<class 'djangoldp_circle.models.CircleMember'>)
[Sender] model has relation Test 2 Circle
[Sender] model has relation d21cea79-4f05-4ef8-a8ca-969306d821ff
[Sender] built dict of targets: {'https://api.test1.startinblox.com/users/calum-test1/': {'@type': 'foaf:user', '@id': 'https://api.test1.startinblox.com/users/calum-test1/'}}
[Sender] sending delete activity {'@context': ['https://www.w3.org/ns/activitystreams', 'https://cdn.happy-dev.fr/owl/hdcontext.jsonld'], 'summary': 'https://api.test2.startinblox.com/circle-members/22/ was deleted', 'type': 'Delete', 'actor': {'type': 'Service', 'name': 'Backlinks Service'}, 'object': {'@id': 'https://api.test2.startinblox.com/circle-members/22/', '@type': 'hd:circlemember'}}
[Sender] sent, receiver responded {}

this will be the case with the join circle as well, assuming that the GET test1/users/xxx/ request is sent before test1 has processed the backlink, which is likely

mentioned in issue framework/sib-core#617 (closed)

@jbpasquier is this something we can test / close now?

Staging, it's on live there.

changed milestone to %Federation part I

@jbpasquier on staging I did the following test:

On staging 1 I created a channel
On staging 2 I could join the channel and the page refreshed all good
However then I created a channel on stg2, and tried to join it from stg1: the button was not responsive. I clicked a few times with no result so I refreshed. From this moment on the channel disappeared from the list of available channels on stg1, while still being available on stg2:

I tried again to add a channel on stg2, I could see the new channel on stg1 but still not the previous circle:

Here is the console when I tried to join a stg2 circle on stg1:

After trying to join, if I refresh, again I lost all access to the stg2 channels, so this is reproductible:

The list on stg2 is working good though:

Reproduced with the same behavior. Hopefully a fix came this afternoon on djangoldp (not deployed right now, will do tomorrow) and the 0.10 should fix the last reactivity issues.

That was fast :) Will it fixed also this scenario:

I've created a private channel on stg2
I've invided Rachel Arnould from stg1 on it.
On stg1 however Rachel Arnould does not see the circle in the left column. And on the list of circles in admin she has a blank line which could well be that private circle:

Again, doing the reverse test: creating the private channel on stg1, adding rachel-stg2 ended with a smooth behavior on stg2.

EDIT: forget my comment on notifications. They do work. They are slower than usual to appear, that's all.

mentioned in issue #569 (closed)

closed

Federation: Join/Leave circle non-responsive

Designs

Child items ...

Activity