Skip to content

Ytp2022 - #1

Open
OmeletWithoutEgg wants to merge 24 commits into
masterfrom
ytp2022
Open

Ytp2022#1
OmeletWithoutEgg wants to merge 24 commits into
masterfrom
ytp2022

Conversation

@OmeletWithoutEgg

Copy link
Copy Markdown
Collaborator

Add bb/v1.4 features.

andreyv and others added 24 commits November 4, 2018 22:32
Due to active Jinja whitespace handling, whitespace was removed between
consecutive {% trans %} blocks, resulting in translated sentences being
glued together. Fix this by disabling the lstrip_blocks behaviour in
relevant places.
Also add missing style for the empty print job table case. Perhaps the
table may benefit from more extensive styling, like with the submission
and the user test tables, but this change fixes the immediate visual
problem.
If alchemy returns a weird order for the tasks, an integrity error on
task.num could happen.

Thanks to Romeo Rizzi for pointing this out and fixing it in master.
curses produces bytes, that should be decoded in a string before printing.
Although scary since editing an admin made it look like being logged
in as that admin, that was only a rendering issue - further request
would be evaluated against the real logged in admin.

Thanks to @andreyv and @PPakalns for the bugreport and the investigation.
In previous psutil versions the "used" field of memory stats included
also buffers and cache. However, this is no longer the case starting
from psutil 4.4. Now the output matches the free(1) utility, which
reports used memory without buffers and cache.

Reference: giampaolo/psutil@ec7957c
With this approach, JS always sees rounded scores, whereas Python has
to round.
I first reverted the `{%` -> `{%+` change as that doesn't appear to be
compatible with Babel's extracter, then ran `./setup.pt
extract_messages`.
The strings are already in .pot, so no .pot update is needed.
The only drawback is that if admins change a user's password from
plaintext to hashed or vice versa that user will have to log in again.
Attackers knowing hashed passwords shouldn't be a problem as the server
only accepts it if it's signed (together with a recent timestamp) with
its secret key.

Fixes #1076.
fix: sort subtasks using index
Revert "fix: sort subtasks using index"
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants