Skip to content

Add tests to verify that rebase is working correctly #100

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Jul 6, 2021
Merged

Conversation

wonder-sk
Copy link
Contributor

@wonder-sk wonder-sk commented Jun 24, 2021

New tests:

  • when rebase is successful
  • when rebase fails because local gpkg got schema changed
  • when rebase fails because remote gpkg got schema changed

The tests are parametrized to check also the case when there is a pending
sqlite connection to gpkg (e.g. layer open in QGIS), to make sure things work
correctly in that case too (no sync failures / data corruption or loss).

Ensures that #96 and MerginMaps/qgis-plugin#246 are fixed now (thanks to fix for #30)

- when rebase is successful
- when rebase fails because local gpkg got schema changed
- when rebase fails because remote gpkg got schema changed

The tests are parametrized to check also the case when there is a pending
sqlite connection to gpkg (e.g. layer open in QGIS), to make sure things work
correctly in that case too (no sync failures / data corruption or loss).
Now we make a temporary copy of the geopackage if we upload its full
content instead of just a diff, to make sure that we do not miss any
data (checkpoint may fail if there's a pending reader/writer).
This is because currently pygeodiff bundles its own sqlite3 library
different from python's sqlite3 library, and that's causing clashes.
@wonder-sk wonder-sk requested a review from erpas June 29, 2021 21:52
@erpas
Copy link
Contributor

erpas commented Jul 6, 2021

All seems good.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants