feat docs: update changelog for 2.12 release

Tests: протестировано CI
commit_hash:e43969f5d2db4e20afee259d74a0aa9f2a6c5cfc

Author: apolukhin

.mapping.json

@@ -641,6 +641,7 @@
   "core/functional_tests/cache_update/config_vars.yaml":"taxi/uservices/userver/core/functional_tests/cache_update/config_vars.yaml",
   "core/functional_tests/cache_update/service.cpp":"taxi/uservices/userver/core/functional_tests/cache_update/service.cpp",
   "core/functional_tests/cache_update/static_config.yaml":"taxi/uservices/userver/core/functional_tests/cache_update/static_config.yaml",
+  "core/functional_tests/cache_update/tests/CMakeLists.txt":"taxi/uservices/userver/core/functional_tests/cache_update/tests/CMakeLists.txt",
   "core/functional_tests/cache_update/tests/conftest.py":"taxi/uservices/userver/core/functional_tests/cache_update/tests/conftest.py",
   "core/functional_tests/cache_update/tests/test_cache_alerts.py":"taxi/uservices/userver/core/functional_tests/cache_update/tests/test_cache_alerts.py",
   "core/functional_tests/cache_update/tests/test_cache_update.py":"taxi/uservices/userver/core/functional_tests/cache_update/tests/test_cache_update.py",

clickhouse/include/userver/storages/clickhouse/cluster.hpp

@@ -53,11 +53,17 @@ class Cluster final {
 
     /// @brief Execute a statement at some host of the cluster
     /// with args as query parameters.
+    ///
+    /// It is convinient to keep SQL queries in separate files, see @ref scripts/docs/en/userver/sql_files.md
+    /// for more info.
     template <typename... Args>
     ExecutionResult Execute(const Query& query, const Args&... args) const;
 
     /// @brief Execute a statement with specified command control settings
     /// at some host of the cluster with args as query parameters.
+    ///
+    /// It is convinient to keep SQL queries in separate files, see @ref scripts/docs/en/userver/sql_files.md
+    /// for more info.
     template <typename... Args>
     ExecutionResult Execute(OptionalCommandControl, const Query& query, const Args&... args) const;
 

core/functional_tests/cache_update/CMakeLists.txt

@@ -3,4 +3,5 @@ project(userver-core-tests-cache-update CXX)
 add_executable(${PROJECT_NAME} "service.cpp")
 target_link_libraries(${PROJECT_NAME} userver::core)
 
-userver_chaos_testsuite_add()
+# Test that `userver_testsuite_add` works from sub directories.
+add_subdirectory(tests)

core/functional_tests/cache_update/tests/CMakeLists.txt

@@ -0,0 +1,7 @@
+userver_testsuite_add(
+    SERVICE_TARGET userver-core-tests-cache-update
+    PYTEST_ARGS
+    --service-config=${CMAKE_CURRENT_SOURCE_DIR}/../static_config.yaml
+    --service-binary=${CMAKE_CURRENT_BINARY_DIR}/../userver-core-tests-cache-update
+    --service-config-vars=${CMAKE_CURRENT_SOURCE_DIR}/../config_vars.yaml
+)

samples/static_service/testsuite/conftest.py

@@ -1,4 +1,3 @@
-# [Static service sample - config hook]
 import pathlib
 
 import pytest
@@ -18,4 +17,3 @@ def _patch_config(config_yaml, config_vars):
         )
 
     return _patch_config
-    # [Static service sample - config hook]

samples/static_service/testsuite/test_static.py

@@ -1,4 +1,4 @@
-# /// Functional test
+# [Functional test]
 import pytest
 
 
@@ -10,7 +10,7 @@ async def test_file(service_client, service_source_dir, path):
     assert response.headers['Expires'] == '600'
     file = service_source_dir.joinpath('public') / 'index.html'
     assert response.content.decode() == file.open().read()
-    # /// Functional test
+    # [Functional test]
 
 
 async def test_file_not_found(service_client):

scripts/docs/customdoxygen.css

@@ -232,14 +232,14 @@ span.paramname em {
 
 
 /* Scale down image to the page width */
-.image img {
+.image img, p > img {
   max-width: calc(100% - 7px - 7px - 1px - 1px);
   background-color: var(--primary-color-1);
-  /* matches .fragment */
   border: 1px solid var(--separator-color);
   /* matches .fragment */
   padding: 7px;
   /* matches .fragment */
+  border-radius: var(--border-radius-large);
 }
 
 hr {
@@ -1221,4 +1221,4 @@ pre {
 
 #nav-sync {
   display: none;
-}
+}

scripts/docs/doxygen.conf

@@ -376,7 +376,7 @@ OPTIMIZE_OUTPUT_SLICE  = NO
 #
 # Note see also the list of default file extension mappings.
 
-EXTENSION_MAPPING      = json=Javascript
+EXTENSION_MAPPING      = json=Javascript js=Javascript
 
 # If the MARKDOWN_SUPPORT tag is enabled then doxygen pre-processes all comments
 # according to the Markdown format, which allows for more readable

scripts/docs/en/userver/functional_testing.md

@@ -23,7 +23,7 @@ Supported features:
 
 ## CMake integration
 
-### CMake integration via `userver_testsuite_add()`
+### CMake integration via userver_testsuite_add()
 
 With `userver_testsuite_add()` function you can easily add testsuite support to your project.
 Its main purpose is:
@@ -37,7 +37,7 @@ Its main purpose is:
 Then create testsuite target:
 @snippet samples/testsuite-support/CMakeLists.txt testsuite - cmake
 
-### `userver_testsuite_add()` arguments
+### userver_testsuite_add() arguments
 
 * SERVICE_TARGET, required CMake name of the target service to test. Used as
   suffix for `testsuite-` and `start-` CMake target names.
@@ -66,7 +66,7 @@ Some of the most useful arguments for PYTEST_ARGS:
 | `--service-wait`                | With this argument the testsuite will wait for the service start by user. For example under gdb. Testsuite outputs a hint on starting the service |
 | `-rf`                           | Show a summary of failed tests          |
 
-### CMake integration via `userver_testsuite_add_simple()`
+### CMake integration via userver_testsuite_add_simple()
 
 `userver_testsuite_add_simple()` is a version of `userver_testsuite_add()`
 that makes some assumptions of the project structure.
@@ -500,7 +500,7 @@ def test_service(service_client):
 
 Testsuite allows to create tests that start a new service instance for the test and stop it on test finish:
 
-@snippet samples/testsuite-support/tests/test_metrics.py  uservice_oneshot sample 
+@snippet samples/testsuite-support/tests/test_metrics.py  uservice_oneshot sample
 
 Such functionality slows down the tests run, but it may be required
 * to test service state right after the service start,

scripts/docs/en/userver/gdb_debugging.md

@@ -24,7 +24,7 @@ See [GDB manual](https://www.sourceware.org/gdb/current/onlinedocs/gdb.html/Auto
 
 ### Custom pretty-printers
 
-The simplest extentions for GDB, that userver provides, are pretty-printers for certain data stuctures. Below is an
+The simplest extensions for GDB, that userver provides, are pretty-printers for certain data structures. Below is an
 example comparing the output for a `formats::json::Value` with and without pretty-printers:
 
 ```
@@ -34,11 +34,11 @@ $1 = {["a"] = {1, 2, 3, 4}, ["c"] = 123, ["d"] = false, ["e"] = "", ["f"] = {["k
 181 printers disabled
 0 of 181 printers enabled
 (gdb) print value
-$2 = {holder_ = {static kInvalidVersion = 18446744073709551615, data_ = {__ptr_ = 0x10f27fe04118, __cntrl_ = 0x10f27fe04100}}, 
-  root_ptr_for_path_ = 0x10f27fe04118, value_ptr_ = 0x10f27fe04118, depth_ = 0, lazy_detached_path_ = {parent_value_ptr_ = 0x0, 
-    parent_depth_ = 0, virtual_path_ = {static __endian_factor = 2, __rep_ = {__s = {{__is_long_ = 0 '\000', __size_ = 0 '\000'}, 
-          __padding_ = {<No data fields>}, __data_ = '\000' <repeats 22 times>}, __l = {{__is_long_ = 0, __cap_ = 0}, __size_ = 0, 
-          __data_ = 0x0}}, __padding1_933_ = {__padding_ = 0x7fffffffd7c0 ""}, 
+$2 = {holder_ = {static kInvalidVersion = 18446744073709551615, data_ = {__ptr_ = 0x10f27fe04118, __cntrl_ = 0x10f27fe04100}},
+  root_ptr_for_path_ = 0x10f27fe04118, value_ptr_ = 0x10f27fe04118, depth_ = 0, lazy_detached_path_ = {parent_value_ptr_ = 0x0,
+    parent_depth_ = 0, virtual_path_ = {static __endian_factor = 2, __rep_ = {__s = {{__is_long_ = 0 '\000', __size_ = 0 '\000'},
+          __padding_ = {<No data fields>}, __data_ = '\000' <repeats 22 times>}, __l = {{__is_long_ = 0, __cap_ = 0}, __size_ = 0,
+          __data_ = 0x0}}, __padding1_933_ = {__padding_ = 0x7fffffffd7c0 ""},
       __alloc_ = {<std::__y1::__non_trivial_if<true, std::__y1::allocator<char> >> = {<No data fields>}, <No data fields>}, __padding2_933_ = {
         __padding_ = 0x7fffffffd7c0 ""}, static npos = 18446744073709551615}}}
 ```
@@ -56,7 +56,7 @@ In addition, the output has a hierarchical structure that is displayed correctly
 
 * `utask list`: Lists all tasks with their names (corresponding span names) and statuses. Example:
 ```
-(gdb) utask list 
+(gdb) utask list
 Task           State     Span
 0x10f27fc40800 Suspended task_3
 0x10f27fc3f000 Suspended task_2
@@ -66,13 +66,13 @@ Task           State     Span
 0x10f27fc42000 Running   task_4
 ```
 
-* `utask apply <task> <cmd...>`: Executes `<cmd...>` in the context of selected `<task>`. The `<task>` may be 
+* `utask apply <task> <cmd...>`: Executes `<cmd...>` in the context of selected `<task>`. The `<task>` may be
 specified by its ID ("Task") or name ("Span") (as shown in `utask list`), or set to "all" to apply the command to all
  tasks. `<cmd...>` can be any GDB command, including Python scripts.
 
 
 #### Examples:
-    
+
 1. Print "Hello world!" for all tasks
 ```
 (gdb) utask apply all print "Hello world!"
@@ -121,9 +121,9 @@ For now `utask` commands are implemented for only linux x86 platforms, but can b
 In addition, all of the above functionality works for debugging both a live process and coredumps.
 
 
-## GDB complains: received signal ?, Unknown signal 
+## GDB complains: received signal ?, Unknown signal
 
-This is a side effect of stack usage monitor interferring with GDB. In unit tests you can set the environment variable
+This is a side effect of stack usage monitor interfering with GDB. In unit tests you can set the environment variable
 `USERVER_GTEST_ENABLE_STACK_USAGE_MONITOR=0` to disable the monitor, in other binaries you can either disable it
 via static config option `coro_pool.stack_usage_monitor_enabled` in components::ManagerControllerComponent or by
 disabling it at all at build time of the framework via `USERVER_FEATURE_STACK_USAGE_MONITOR`