You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The crash was happening inside geodiff due to the fact that mergin
client was creating geodiff instances, setting logger callbacks
to temporary python functions, making it possible that geodiff
calls could crash when trying to log using invalid logger callback.
Related geodiff enhancements:
MerginMaps/geodiff#135MerginMaps/geodiff#136
Currently, geodiff registers its logger in GEODIFF_init() as the global log callback:
sqlite3_config( SQLITE_CONFIG_LOG, _errorLogCallback );
This may cause issues:
It should be possible to catch errors on per-connection level without registering global error callback: http://www.sqlite.org/c3ref/errcode.html
The text was updated successfully, but these errors were encountered: