Fix/post testing requests #818
Open
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
This was
linked to
issues
Dec 10, 2024
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.
This branch features a lot of tiny issues, that have been uncovered following the testing of 4.0.
In rough order of commits:
#789: Apparently the observation table still included fields from v1 observations and we never noticed. It now includes the new fields.
#809: The Stepper bubbles were untranslated ... My first hunch was to replace gettext with gettext_lazy and this works. Don't ask me why ...
#811: Increase the max length of trajectory names from 15 to 30.
#814: Include linebreaks in review comments for the Secretary to read comfortably.
No issue: Remove more remnant of the old AvailableURL system ...
#813: Untranslated text.
#817: A server errors caused by some shoddy validation and logic regarding embargo and embargo_end_date.
#777: Remove the embargo question from the submit form for PreAss proposals, ensure that PreAss proposals are never placed in the archive and remove the ChangeArchiveStatus review action if a proposal is PreAss.
Its a lot of issues ... But the fixes are mostly one or two lines, so it should be manageable I hope :)