Samir Halilčević
Samir Halilčević
Analyzing the pipeline from the past 4 months, we noticed the following tests failing occasionally in Jenkins: - [ ] `caf-robot-http-client` ([90](https://jenkins.inet.haw-hamburg.de/blue/organizations/jenkins/CAF%2Factor-framework/detail/main/90/pipeline/66), [84](https://jenkins.inet.haw-hamburg.de/blue/organizations/jenkins/CAF%2Factor-framework/detail/main/84/pipeline/62), [78](https://jenkins.inet.haw-hamburg.de/blue/organizations/jenkins/CAF%2Factor-framework/detail/main/78/pipeline/63)) - Timeout - [ ] `caf.actor_pool`...
While working on #1937 we've noticed that we have two functions that handle unescaping: `do_unescape` and `print_unescaped`, together with `print_escaped_to`. These are related to reading and printing of `json` string...
This PR prepares the switch from `caf::expected` to `std::expected`. It introduces an `caf::unexpected` class. Deprecates construction and comparison with `caf::error` in favor of `unexpected`. Also, `transform_or` becomes `transform_error`, and `or_else`...
Currently, we use CAF_CACHE_LINE_SIZE with the value of 64 bytes to prevent false sharing in the `actor_control_block` and `default_mailbox`. Intel and AMD use 64, but Apple Silicone switched to 128...
Implemented the blocking stuff. There was a small issue I've had with `do_receive`, since it receives a single message. It behaved weirdly with `timespan`s, so I switched to using `time_point`s....
## Overview This issue aims to enhance the failure proofing of CAF by leveraging [fil-c](https://fil-c.org/), a C/C++ runtime memory and safety checker. The goal is to identify common unsafe memory...
Currently, the deterministic test fixture does not handle detached actors, which can easily lead to confusing test failures or unexpected behavior. To avoid this pitfall, CAF should either immediately fail...