I’m just taking the opportunity to keep you informed about DuckDB’s response — they can’t reproduce the bug (by the way, I never managed to reproduce the bug either ^^)
They advised me to add a bit of code to fix the affected backups « on the fly » just before the restore.
So I made a PR :
master ← clean-duckdb-schema-on-restore
ouvert 12:28PM - 28 Oct 24 UTC
### Pull Request check-list
To ensure your Pull Request can be accepted as fa… st as possible, make sure to review and check all of these items:
- [x] If your changes affects code, did your write the tests?
- [x] Are tests passing? (`npm test` on both front/server)
- [x] Is the linter passing? (`npm run eslint` on both front/server)
- [x] Did you run prettier? (`npm run prettier` on both front/server)
- [x] If you are adding a new features/services, did you run integration comparator? (`npm run compare-translations` on front)
- [x] Did you test this pull request in real life? With real devices? If this development is a big feature or a new service, we recommend that you provide a Docker image to the community ([french forum](https://community.gladysassistant.com/)/[english forum](https://en-community.gladysassistant.com/)) for testing before merging.
### Description of change
Fix restore bug on some versions of DuckDB
It will be included in the next Gladys release!
3 Likes
This fix was released in Gladys Assistant 4.48:
Salut à tous !
C’est une mise à jour qui va vous plaire !! ici .
Si vous avez des questions, n’hésitez pas
I’m closing this thread.
2 Likes