Add section about clearing the sessions store during OMERO.web upgrade #2312
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Motivated by some of the changes introduced in OMERO.web 5.18.0. It is expected the same issues will arise when switching to Django 4.2 and this could happen anytime if the session serialization format is modified. A new paragraph about common issues when OMERO.server fails to start is also added to the troubleshooting section and this PR should create a link that can be reference from UPGRADING.md in the source code repo.
will-moore
reviewed
May 4, 2023
will-moore
reviewed
May 4, 2023
will-moore
reviewed
May 4, 2023
jburel
reviewed
May 4, 2023
jburel
reviewed
May 4, 2023
jburel
reviewed
May 4, 2023
Co-authored-by: jean-marie burel <j.burel@dundee.ac.uk>
will-moore
reviewed
May 9, 2023
sbesson
commented
May 9, 2023
|
The failure is not related to the change. It started to happen on other repositories. I fixed the issue in ome/omero-guide-python#58 |
|
@sbesson you will have to rebase the PR in order to fix the error |
|
This should ready for review and integration in the next documentation release. With the upcoming move to Django 4.2, I expect the session clearing step will be mandatory (unless people have switched to the JSON serializer) |
jburel
reviewed
Jul 3, 2023
Clarify the two main supported session backends and their configuration Provide the example for the default configuration in both case Add final sentence about additional backend configuration
jburel
reviewed
Jul 4, 2023
jburel
reviewed
Jul 4, 2023
jburel
approved these changes
Jul 4, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See ome/omero-web#435, ome/omero-web#459 and ome/omero-web#383 for more context about the requirement for this new optional section
See also https://docs.djangoproject.com/en/3.2/topics/http/sessions/ for some reference documentation about the different types of Django session store backends.
Motivated by some of the changes introduced in OMERO.web 5.18.0. It is expected the same issues will arise when switching to Django 4.2 and this could happen anytime if the session serialization format is modified.
A new paragraph about common issues when OMERO.server fails to start is also added to the troubleshooting section and this PR should create a link that can be reference from UPGRADING.md in the source code repo.