Upgrade examine to 3.7.1#19186
Conversation
|
Hi there @dawoe, thank you for this contribution! 👍 While we wait for one of the Core Collaborators team to have a look at your work, we wanted to let you know about that we have a checklist for some of the things we will consider during review:
Don't worry if you got something wrong. We like to think of a pull request as the start of a conversation, we're happy to provide guidance on improving your contribution. If you realize that you might want to make some changes then you can do that by adding new commits to the branch you created for this work and pushing new commits. They should then automatically show up as updates to this pull request. Thanks, from your friendly Umbraco GitHub bot 🤖 🙂 |
AndyButland
left a comment
There was a problem hiding this comment.
Thanks @dawoe - yes, we'll include this in the next releases.
|
Merging, as failing E2E tests are not related. |
|
This pull request has been mentioned on Umbraco community forum. There might be relevant details there: https://forum.umbraco.com/t/running-umbraco-on-azure-web-apps-nucache-issues/5083/3 |
|
This pull request has been mentioned on Umbraco community forum. There might be relevant details there: https://forum.umbraco.com/t/examine-files-keep-locking/6989/3 |
Prerequisites
Description
We have a Umbraco 13.8.0 website running on Azure WebApps and configured as recommended in the documentation.
On a regular basis Examine indexes are corrupted. The only option is to manually delete them and restart the application to fix the problem.
See the following issues for more details :
Shazwazza/Examine#402
#16163
Last week we updated to Examine 3.7.1 and we have not seen the issue anymore.
This PR updates Examine for V13. Hopefully this can be taken into the next minor release.