Harden the vikunja client and sync against malformed responses #12
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Deferred review findings from the vikunja-project-sync implementation (all approved-with-notes, none blocking):
common/vikunja.pyprojects()trusts the parsed body to be a list; a malformed 2xx (proxy quirk, API drift) silently corrupts the accumulated result instead of raisingRestAdapterError.per_pageitems loops forever. A generous page cap turning the hang into a clear error is enough.project/sync.py_ensure_parentresolves viaby_parent_title.get(...) or client.create_project(...)while_resolve_childuses an explicitis not Nonecheck; align on the latter so a falsy-but-present dict can never trigger a spurious create.RestAdapter.puthas no error-path test, unlikeget/post(coverage holds via the shared_request, symmetry only).