Scoped field updates in custom Morango sync ops

[bjester]

Summary

• Updates morango model saves in Kolibri's sync operations to scope the saves to only the updated fields, similar to the corresponding morango PR (referenced below)
• Upgrades morango to v0.8.15

References

Related to this investigation:

• Background queuing causes int vs None comparison exception kolibri-sync-extras-plugin#14
• Correct behavior for background initialization, only useful for pulls kolibri-sync-extras-plugin#15

Also, this corresponding morango update:

• Scoped field updates and context initialization issue morango#346

Reviewer guidance

The guidance in learningequality/kolibri-sync-extras-plugin#15 is sufficient. Morango integ tests pass

AI usage

None

[rtibblesbot]

🔵 Review posted

Last updated: 2026-07-09 00:22 UTC

[rtibblesbot]

PR #14985 — Small, correct cleanup: a None guard on records_total in the sync progress hook plus scoping two morango save() calls to their changed fields. Both are consistent with this branch's earlier "scope saves to changed fields" work, and the test assertion was updated to match. CI pending; no UI changes (Phase 3 N/A).

One worthwhile follow-up (inline): the new guard doesn't cover the sibling stats handler in the same adapter, so the crash it targets can still fire. Minor: the guard has no test, unlike the update_fields change.

---

@rtibblesbot's comments are generated by an LLM, and should be evaluated accordingly

How was this generated?

Ran a phased review pipeline over the pull request diff:

• Classified the diff to select review passes (core, frontend, backend) and whether manual QA was required
• Core review pass checked correctness, design, architecture, testing, completeness, and DRY/SRP/Rule-of-Three principles
• Specialized frontend/backend review passes applied framework-specific lenses where those files changed
• For UI changes: manual QA and an accessibility audit against a live dev server, when available
• Checked CI status and linked issue acceptance criteria
• Synthesized one review from those passes and chose the verdict from the findings, CI status, and QA evidence

[github-actions]

Build Artifacts

Asset type	Download link
PEX file	kolibri-0.19.5.dev0_git.20260709154114.pex
Windows Installer (EXE)	kolibri-0.19.5.dev0+git.20260709154114-windows-setup-unsigned.exe
Debian Package	kolibri_0.19.5.dev0+git.20260709154114-0ubuntu1_all.deb
Mac Installer (DMG)	kolibri-0.19.5.dev0+git.20260709154114.dmg
Android Package (APK)	kolibri-0.19.5.dev0+git.20260709154114-0.1.10-debug.apk
Raspberry Pi Image	kolibri-pi-image-0.19.5.dev0+git.20260709154114.zip
TAR file	kolibri-0.19.5.dev0+git.20260709154114.tar.gz
WHL file	kolibri-0.19.5.dev0+git.20260709154114-py2.py3-none-any.whl

Smoke test screenshot

Download screenshot

[rtibbles]

Changes make sense to me - one thought for the future, but not needed right now.

[rtibbles]

Not needed for now - but it almost feels like having "dirty field" tracking on the sync session might be good to have this be the default behaviour.