Resolve "Add periodic task for syncing rooms" #58
No reviewers
Labels
No labels
Security
TeX
auto-update
board
done
board
ready
board
todo
check
delete-eslint-rc-js
check
update-builddeps-package-json
check
update-eslint-rc-js
check
update-gitignore
check
update-merge-request-template
check
update-prettier-ignore
check
update-pyproject-toml
check
update-renovate-json
check
update-tox-ini
part
backend
part
ci
part
docs
part
frontend
part
i18n
part
non-technical
part
packaging
prio
1
prio
2
prio
3
release-mr-5.x
size
large
size
medium
size
small
source
customer
source
customer::fsmw
source
customer::fss
source
customer::teckids
source
downstream
type
breaking
type
bug
type
feature
type
refactoring
workflow
blocked
workflow
confirmed
workflow
current-todo
workflow
discussing
workflow
new-app
workflow
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
aleksis/AlekSIS-App-Matrix!58
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "18-add-periodic-task-for-syncing-rooms"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Closes #18
added 1 commit
6e6218e6- Add tasks for syncing rooms periodically or after changesCompare with previous version
assigned to @nik
marked this merge request as ready
added 15m of time spent
Why do you want to skip sync on creation?
MatrixRoom objects are usually created in the provisioning process which also includes a full sync. Therefore, this would mean doing two complete syncs.
added 1m of time spent
We also need to react to:
Group.membersGroup.ownersMatrixRoom.groupMatrixProfile.personMatrixProfileadded 1 commit
0f47c6a7- Register more signals to detect changes that need a Matrix room syncCompare with previous version
added 1h 12m of time spent
This should probably use sub-tasks](https://docs.celeryq.dev/en/2.4-archived/userguide/tasksets.html) or a taskset, so that we don't get one long-running task and failures in syncing one room don't prevent others from getting synced.
This should also use a task set.
This is a little bit antique. And I am not able to find current information on tasksets.
see above
@nik Any update?
"usually" depends on the use case. For Teckids, all Matrix rooms already exist and are linked by an existing room ID, outside the automatic provisioning process. And this is also true for (at least) all schools who already use solutions like Logineo Messenger and add AlekSIS to the stack now.
https://docs.celeryq.dev/en/stable/userguide/tasks.html#avoid-launching-synchronous-subtasks
see above ;)
Ne war Quatsch
changed this line in version 3 of the diff
changed this line in version 3 of the diff
added 1 commit
92224d6d- Sync rooms in separate tasksCompare with previous version
resolved all threads
added 10 commits
masterb6730fc4- Merge branch 'master' into 18-add-periodic-task-for-syncing-roomsCompare with previous version
added 1 commit
a85d41c5- Fix lint and testsCompare with previous version
mentioned in commit
41d34239dd