Skip to content

Resolve "The model cache sometimes result into an UnpicklingError"

Bram Wiepjes requested to merge 833-the-model-cache-sometimes-result-into-an-unpicklingerror into develop

This merge request changes the incorrect locking we did before when caching the table model. The locking now uses a non conflicting lock name and acquires the lock before the field_attrs are fetched from the cache. If another worker has already acquired the lock, it waits until that's finished.

How to test

Check the issue description on how to test this. The same manual test must succeed this time.

Merge Request Checklist

  • changelog.md has been updated if required
  • New/updated Premium features are separated correctly in the premium folder
  • The latest Chrome and Firefox have been used to test any new frontend features
  • Documentation has been updated
  • Quality Standards are met
  • Performance: tables are still fast with 100k+ rows, 100+ field tables
  • The redoc API pages have been updated for any REST API changes
  • Our custom API docs are updated for changes to endpoints accessed via api tokens
  • The UI/UX has been updated following UI Style Guide

Closes #833 (closed)

Edited by Bram Wiepjes

Merge request reports