2
0
mirror of https://github.com/boostorg/redis.git synced 2026-01-20 05:02:12 +00:00

Compare commits

...

4 Commits

Author SHA1 Message Date
Marcelo Zimbres
4c91dafb84 Remove unused coverage report script. 2024-11-02 12:38:25 +01:00
Marcelo Zimbres
924b4d3496 Change log level to debug. 2024-11-02 12:38:25 +01:00
Marcelo Zimbres
937a02995b Fix error assignment. 2024-11-02 12:38:25 +01:00
Marcelo Zimbres
b15b8ceae6 Update release notes. 2024-11-02 12:38:25 +01:00
5 changed files with 21 additions and 64 deletions

View File

@@ -1,51 +0,0 @@
name: Coverage
on:
push:
branches:
- develop
jobs:
posix:
defaults:
run:
shell: bash
runs-on: ubuntu-22.04
env:
CXX: g++-11
CXXFLAGS: -g -O0 -std=c++20 --coverage -fkeep-inline-functions -fkeep-static-functions
LDFLAGS: --coverage
CMAKE_BUILD_PARALLEL_LEVEL: 4
steps:
- name: Checkout
uses: actions/checkout@v3
- name: Install dependencies
run: sudo apt-get --no-install-recommends -y install cmake lcov g++-11 redis-server python3 libgd-perl
- name: Setup Boost
run: ./tools/ci.py setup-boost --source-dir=$(pwd)
- name: Build Boost
run: ./tools/ci.py build-b2-distro --toolset=gcc-11
# Having our library there confuses the coverage reports
- name: Remove Boost.Redis from the b2 distro
run: rm -rf ~/boost-b2-distro/include/boost/redis
- name: Run CMake
run: cmake -DCMAKE_PREFIX_PATH=$HOME/boost-b2-distro --preset coverage .
- name: Build
run: cmake --build --preset coverage
- name: Test
run: ctest --preset coverage
- name: Make the coverage file
run: cmake --build --preset coverage --target coverage
- name: Upload to codecov
run: |
bash <(curl -s https://codecov.io/bash) -f ./build/coverage/coverage.info

View File

@@ -678,25 +678,32 @@ https://lists.boost.org/Archives/boost/2023/01/253944.php.
### Boost 1.87
* ([Issue 205](https://github.com/boostorg/redis/issues/205))
* (Issue [205](https://github.com/boostorg/redis/issues/205))
Improves reaction time to disconnection by using `wait_for_one_error`
instead of `wait_for_all`. The function `connection::async_run` was
also changed to return EOF to the user when that error is received
from the server. That is a breaking change.
* ([Issue 210](https://github.com/boostorg/redis/issues/210))
* (Issue [210](https://github.com/boostorg/redis/issues/210))
Fixes the adapter of empty nested reposponses.
* (Issues [211](https://github.com/boostorg/redis/issues/211) and [212](https://github.com/boostorg/redis/issues/212))
Fixes the reconnect loop that would hang under certain conditions,
see the linked issues for more details.
* (Issue [219](https://github.com/boostorg/redis/issues/219))
Changes the default log level from `disabled` to `debug`.
### Boost 1.85
* ([Issue 170](https://github.com/boostorg/redis/issues/170))
* (Issue [170](https://github.com/boostorg/redis/issues/170))
Under load and on low-latency networks it is possible to start
receiving responses before the write operation completed and while
the request is still marked as staged and not written. This messes
up with the heuristics that classifies responses as unsolicied or
not.
* ([Issue 168](https://github.com/boostorg/redis/issues/168)).
* (Issue [168](https://github.com/boostorg/redis/issues/168)).
Provides a way of passing a custom SSL context to the connection.
The design here differs from that of Boost.Beast and Boost.MySql
since in Boost.Redis the connection owns the context instead of only
@@ -704,16 +711,16 @@ https://lists.boost.org/Archives/boost/2023/01/253944.php.
apps need only one connection for their entire application, which
makes the overhead of one ssl-context per connection negligible.
* ([Issue 181](https://github.com/boostorg/redis/issues/181)).
* (Issue [181](https://github.com/boostorg/redis/issues/181)).
See a detailed description of this bug in
[this](https://github.com/boostorg/redis/issues/181#issuecomment-1913346983)
comment.
* ([Issue 182](https://github.com/boostorg/redis/issues/182)).
* (Issue [182](https://github.com/boostorg/redis/issues/182)).
Sets `"default"` as the default value of `config::username`. This
makes it simpler to use the `requirepass` configuration in Redis.
* ([Issue 189](https://github.com/boostorg/redis/issues/189)).
* (Issue [189](https://github.com/boostorg/redis/issues/189)).
Fixes narrowing convertion by using `std::size_t` instead of
`std::uint64_t` for the sizes of bulks and aggregates. The code
relies now on `std::from_chars` returning an error if a value

View File

@@ -42,10 +42,10 @@ struct connect_op {
ctor_->endpoint_ = ep;
if (ec == asio::error::operation_aborted) {
ec == error::connect_timeout;
self.complete(redis::error::connect_timeout);
} else {
self.complete(ec);
}
self.complete(ec);
}
}
};

View File

@@ -41,9 +41,10 @@ struct resolve_op {
resv_->results_ = res;
if (ec == asio::error::operation_aborted) {
ec == error::resolve_timeout;
self.complete(error::resolve_timeout);
} else {
self.complete(ec);
}
self.complete(ec);
}
}
};

View File

@@ -64,7 +64,7 @@ public:
*
* @param l Log level.
*/
logger(level l = level::disabled)
logger(level l = level::debug)
: level_{l}
{}