http://codereview.stackexchange.com/questions/84697/timeout-watchdog-using-a-standby-thread

he simple but generic timeout class to be used watching for network connections, user input, filesystem events, and is intended to have a very simple interface specific to only our use cases (i.e. no satisfy-all attitude).

Intended steps to use:

  1. Construct
  2. Activate
  3. Potentially react to a timeout, deactivates itself
  4. Re-activate
  5. Destruct cleanly

After triggering the alarm the guard is expected to be inactive until explicitly activated. The code expected to be reasonably tested (that is one of the issues).

This posted code as a testable Visual Studio 2013 project lives on the GitHub.

Besides a general feedback on the code quality - or if, please, please, please, you see a bug, I would love to hear about these areas:

  1. Destruction. Although I did my best to tell the guard thread to end, I am still concerned about having to join() in the destructor. Generally I love my destructors short and sweet for emergency landings - is it possible here? Is there an STL way to brutally kill that thread?

  2. Tests. Existing ones test for intended simple scenarios. I am not sure this is enough to claim that the code works as intended. Is it? I did not find a better way to test timing edge cases. Also, as tests are time-dependant, they occasionally spuriously fail when run on slow VMs. Or are they? Is it sufficient for code like this to know that if tests run somewhere consistently? If I increase timeouts the spurious fails go away, but that lengthens the overall project test run.

Below are the current header, implementation, and tests files to save the GitHub trip.

Header:

#pragma once

namespace utility
{
/**
The `clock` alias is for easy switching to `steady_clock` once Microsoft fixes it
*/
typedef std::chrono::system_clock clock; /**
The `TimeoutGuard` class triggers the `alarm` callback from the `guard_thread`
if `touch` was not called for at least the `timeout` duration. Because of the way the `guard_thread` sleeps, the actual detection may happen
as late as after `timeout` + `naptime` duration. Hence it is possible that the alarm
will not be called if the `TimeoutGuard` instance is touched within the
'timeout` and `timeout` + `naptime` timeframe. If not provided, by default the `naptime` is same as `timeout`. The `TimeoutGuard` is not active after construction, whicn means, that the
`guard_thread` will block until it is activated by calling the `watch` method. The `TimeoutGuard` class is not copyable and not moveable.
*/
class TimeoutGuard
{
public:
TimeoutGuard(
clock::duration timeout,
std::function<void( void )> alarm,
clock::duration naptime
); TimeoutGuard(
clock::duration timeout,
std::function<void( void )> alarm
); ~TimeoutGuard(); TimeoutGuard( const TimeoutGuard & ) = delete;
TimeoutGuard & operator=(const TimeoutGuard & ) = delete; TimeoutGuard( TimeoutGuard && ) = delete;
TimeoutGuard & operator=( TimeoutGuard && ) = delete; void watch();
void touch(); private: void guard(); clock::duration timeout;
clock::duration naptime;
std::function<void( void )> alarm; std::atomic_bool idle;
std::atomic_bool live; std::atomic<clock::time_point> touched; std::thread guard_thread;
std::mutex guard_mutex;
std::condition_variable wakeup;
};
}

Here is the implementation:

#include "stdafx.h"
#include "TimeoutGuard.h" namespace utility
{
TimeoutGuard::TimeoutGuard(
clock::duration timeout,
std::function<void( void )> alarm,
clock::duration naptime
)
: timeout( timeout )
, alarm( alarm )
, naptime( naptime )
{
idle.store( true );
live.store( true ); guard_thread = std::thread( std::bind( &TimeoutGuard::guard, this ) );
} TimeoutGuard::TimeoutGuard(
clock::duration timeout,
std::function<void( void )> alarm
)
: TimeoutGuard( timeout, alarm, timeout )
{}; TimeoutGuard::~TimeoutGuard()
{
live.store( false );
wakeup.notify_all();
guard_thread.join();
} void TimeoutGuard::guard()
{
while ( live.load() )
{
if ( idle.load() )
{
// Sleep indefinitely until either told to become active or destruct
std::unique_lock<std::mutex> live_lock( guard_mutex );
wakeup.wait( live_lock, [this]() { return ! this->idle.load() || ! this->live.load(); } );
}; // quit the loop if destructing
if ( ! live.load() ) break; // the actual timeout checking
auto now = clock::now(); if ( ( now - touched.load() ) > timeout )
{
idle.store( true );
alarm();
continue; // skip waiting for next timeout
} {
// sleep until next timeout check or destruction
std::unique_lock<std::mutex> live_lock( guard_mutex );
wakeup.wait_for( live_lock, naptime, [this](){ return ! this->live.load(); } );
}
};
} void TimeoutGuard::watch()
{
touch();
idle.store( false );
wakeup.notify_all();
} void TimeoutGuard::touch()
{
touched.store( clock::now() );
}
}

And, finally, existing tests:

#include "stdafx.h"
#include "CppUnitTest.h" #include "TimeoutGuard.h" using namespace Microsoft::VisualStudio::CppUnitTestFramework; namespace utility
{
TEST_CLASS( TimeoutGuardTest )
{
public: bool triggered = false; void shoud_trigger()
{
triggered = true;
} TEST_METHOD( TimeoutGuardExpiration )
{
TimeoutGuard tg{
std::chrono::milliseconds{ 5 },
std::bind( &TimeoutGuardTest::shoud_trigger, this )
}; triggered = false;
tg.watch();
std::this_thread::sleep_for( std::chrono::milliseconds{ 10 } );
Assert::IsTrue( triggered, L"Failed to call the timeout alarm on the first run", LINE_INFO() ); triggered = false;
tg.watch();
std::this_thread::sleep_for( std::chrono::milliseconds{ 10 } );
Assert::IsTrue( triggered, L"Failed to call the timeout alarm on the second run", LINE_INFO() );
} TEST_METHOD( TimeoutGuardNoAlarm )
{
TimeoutGuard tg{
std::chrono::milliseconds{ 5 },
std::bind( &TimeoutGuardTest::shoud_trigger, this )
}; triggered = false;
tg.watch();
std::this_thread::sleep_for( std::chrono::milliseconds{ 1 } );
Assert::IsFalse( triggered, L"Wrongly called the timeout alarm on the first run", LINE_INFO() ); triggered = false;
tg.watch();
for (auto i = 0; i < 10; ++i)
{
std::this_thread::sleep_for( std::chrono::milliseconds{ 1 } );
tg.touch();
}
Assert::IsFalse( triggered, L"Wrongly called the timeout alarm on the second run", LINE_INFO() );
}
};
}

Timeout watchdog using a standby thread的更多相关文章

  1. Concurrent.Thread.js

    (function(){ if ( !this.Data || (typeof this.Data != 'object' && typeof this.Data != 'functi ...

  2. 多线程爬坑之路-Thread和Runable源码解析

    多线程:(百度百科借一波定义) 多线程(英语:multithreading),是指从软件或者硬件上实现多个线程并发执行的技术.具有多线程能力的计算机因有硬件支持而能够在同一时间执行多于一个线程,进而提 ...

  3. java中多线程中Runnable接口和Thread类介绍

    java中的线程时通过调用操作系统底层的线程来实现线程的功能的. 先看如下代码,并写出输出结果. // 请问输出结果是什么? public static void main(String[] args ...

  4. Thread的run()与start()的区别

    Java的线程是通过java.lang.Thread类来实现的.VM启动时会有一个由主方法所定义的线程.可以通过创建Thread的实例来创建新的线程.每个线程都是通过某个特定Thread对象所对应的方 ...

  5. Thread类源码剖析

    目录 1.引子 2.JVM线程状态 3.Thread常用方法 4.拓展点 一.引子 说来也有些汗颜,搞了几年java,忽然发现竟然没拜读过java.lang.Thread类源码,这次特地拿出来晒一晒. ...

  6. 从源码解读线程(Thread)和线程池(ThreadPoolExecutor)的状态

    线程是比进程更加轻量级的调度执行单位,理解线程是理解并发编程的不可或缺的一部分:而生产过程中不可能永远使用裸线程,需要线程池技术,线程池是管理和调度线程的资源池.因为前不久遇到了一个关于线程状态的问题 ...

  7. HttpClient throws TaskCanceledException on timeout

    error msg: HttpClient throws TaskCanceledException on timeout HttpClient is throwing a TaskCanceledE ...

  8. java Thread 类的源码阅读(oracle jdk1.8)

    java线程类的源码分析阅读技巧: 首先阅读thread类重点关注一下几个问题: 1.start() ,启动一个线程是如何实现的? 2.java线程状态机的变化过程以及如何实现的? 3. 1.star ...

  9. [Java多线程]-Thread和Runable源码解析

    多线程:(百度百科借一波定义) 多线程(英语:multithreading),是指从软件或者硬件上实现多个线程并发执行的技术.具有多线程能力的计算机因有硬件支持而能够在同一时间执行多于一个线程,进而提 ...

随机推荐

  1. WINDOWS批量替换不同文件夹下的相同文件

    今天帮媳妇解决的问题,记录一下,也许以后有用 例子: N个文件夹下有同一个文件(common.php),但是,现在对common.php文件进行了大量修改. 现在想用最新的common.php替换掉所 ...

  2. 快速获取Android应用包名和Activity名

    一.获取包名 方法1: 先说明一下这里讲的方法是通用的,而网上其他方法获取PackageName不通用(因为他是建立在root的基础上的,我不敢保证你的设备已经root). ①在android设备上点 ...

  3. python week09 Mysql 数据库基础知识

    第一篇:初识数据库 注:<基础概念,不再赘述,点开链接查看> 第二篇:库相关操作 一 系统数据库 information_schema: 虚拟库,不占用磁盘空间,存储的是数据库启动后的一些 ...

  4. 精通CSS高级Web标准解决方案(7、布局)

    7.1 让设计居中 7.1.1 使用自动空白边让设计居中 <body> <div id="wrapper"> </div> </body& ...

  5. Leetcode 557.反转字符串中的单词III

    反转字符串中的单词III 给定一个字符串,你需要反转字符串中每个单词的字符顺序,同时仍保留空格和单词的初始顺序. 示例 1: 输入: "Let's take LeetCode contest ...

  6. sqlserver 操作access数据库

    exec sp_configure 'show advanced options',1  reconfigure  exec sp_configure 'Ad Hoc Distributed Quer ...

  7. CentOS6.5 安装中文输入法

    直接转载他人文章:http://hi.baidu.com/dxqt58592/item/a85b96e72c423cc0baf37d3c centos 6.5使用yum安装中文输入法 1.需要root ...

  8. [oldboy-django][2深入django]学生管理(Form)-- 编辑(设置input标签属性,设置input标签默认显示值,设置input的类型)

    1 django 后台实现设置input标签属性,设置input标签默认显示值,设置input输入框类型 # Form生成html标签 a. 通过Form生成Input输入框,Form标签,以及sub ...

  9. Zookeeper ZooDefs.Ids

    OPEN_ACL_UNSAFE  : 完全开放的ACL,任何连接的客户端都可以操作该属性znode CREATOR_ALL_ACL : 只有创建者才有ACL权限 READ_ACL_UNSAFE:只能读 ...

  10. 纸上得来终觉浅,绝知此事要躬行——Spring boot任务调度

    前言:之前今日开讲项目的时候,用到了Quartz进行任务调度.后来做一个电商项目的时候,还用到了Quartz任务调度. 觉得挺简单的,a peace of cake.  忽略了总结,当时闭着眼睛都能捉 ...