# Problem bei der Wiederherstellung von Gladys

**URL:** <https://community.gladysassistant.com/t/probleme-restauration-gladys/9133>\
**Category:** Configuration\
**Created:** [22. Oktober 2024 um 07:33 UTC](https://community.gladysassistant.com/t/probleme-restauration-gladys/9133 "2024-10-22T07:33:34Z")\
**Posts on this page:** 3\
**Page:** 3

<div class="post-metadata">

**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\
**Post date:** [28. Oktober 2024 um 12:57 UTC](https://community.gladysassistant.com/t/probleme-restauration-gladys/9133/41 "2024-10-28T12:57:02Z")

</div>

Ich nutze die Gelegenheit, um euch über die Antwort von DuckDB zu informieren. Sie können den Fehler nicht reproduzieren (ich übrigens auch nicht, ich habe den Fehler nie reproduzieren können ^^)

Sie haben mir geraten, ein Stück Code hinzuzufügen, um die „heißen“ Backups direkt vor der Wiederherstellung zu korrigieren.

Ich habe also einen Pull Request erstellt:

> <https://github.com/GladysAssistant/Gladys/pull/2147>
>
> \### 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

Das wird in der nächsten Version von Gladys enthalten sein!

---

<div class="post-metadata">

**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\
**Post date:** [1. November 2024 um 11:03 UTC](https://community.gladysassistant.com/t/probleme-restauration-gladys/9133/42 "2024-11-01T11:03:41Z")

</div>

Dieses Update ist in Gladys Assistant 4.48 enthalten:

> [@Gladys Assistant 4.48: Die Proaktive KI kommt in Gladys Assistant!](https://community.gladysassistant.com/t/gladys-assistant-4-48-lia-proactive-debarque-dans-gladys-assistant/9153):
>
> Salut à tous ! C’est une mise à jour qui va vous plaire !! smiley Je vous en dis plus sur le blog : N’hésitez pas si vous avez des retours sur ces nouvelles fonctionnalités, je suis vraiment preneur de vos retours. Le CHANGELOG est disponible [ici](https://github.com/GladysAssistant/Gladys/releases/tag/v4.48.0). Si vous avez des questions, n’hésitez pas slight_smile

Ich schließe dieses Thema.

---

<div class="post-metadata">

**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\
**Post date:** [1. November 2024 um 11:03 UTC](https://community.gladysassistant.com/t/probleme-restauration-gladys/9133/43 "2024-11-01T11:03:44Z")

</div>



[Vorherige Seite](https://community.gladysassistant.com/t/probleme-restauration-gladys/9133.md?page=2)