Artifact: https://docs.google.com/document/d/10wcYWOW_CWfkkZXLmzwIkEssjSCYVnrd72HqFGdaAxU/edit#

By default in Keycloak you can change:
Email
First name
Last name
Password
2FA
and Username only if enabled on Admin portal.

The decision was made to:
Get official image
Update it using git submodule with official extensions and custom once.
We will enable extensions in CustomSettings.php which will be automatically included in LocalSettings.php during deploy.
Sensitive data will be passed to LocalSettings.php with env variables.

Hi! I have merged master into patch and solved merge conflicts. Please review.

Hi! Thanks for answer! Now I understand :)
I have fixed table name and now I think we are done.

Hi @aaron! I have tested your suggested solution. It works smoothly. All announces were sent without deadlocks and errors for client. Only one question: you are using nl_newsletters table name to lock, but in code we are inserting data into nl_issues table, so maybe we have to use nl_issues table to lock? Just to be sure I have tested both variants:

In T253926#7189453, @tstarling wrote:

@aaron, never mind.

@Art.tsymbar on line 465 pass IDatabase::ATOMIC_CANCELABLE to startAtomic. The correct way to catch a query error in an atomic section is:

		$dbw->startAtomic( __METHOD__, IDatabase::ATOMIC_CANCELABLE );
		try {
			... query that may fail...
			$dbw->endAtomic( __METHOD__ );
		} catch ( DBQueryError $e ) {
			$dbw->cancelAtomic( __METHOD__ );
		}

This is documented in IDatabase::startAtomic().

Hi @tstarling ! I have finished task and have succeeded tests. Could you make a code review, please?

Hi @tstarling ! Short update for this task. I have made button with ajax call (js file connected like module) that sends timestamp to backend, getting correct data from DB and backend logic for this. There was one case left: 1) Render new data without page reload using “action=render” and “peek” parameters. And it looks like we will need some js code for that.