system-timer | Reliable Ruby timeouts for M.R.I. 1.8

by ph7 Ruby Version: Current License: Non-SPDX

X-Ray Key Features Code Snippets Community Discussions(3)Vulnerabilities Install Support

kandi X-RAY | system-timer Summary

system-timer is a Ruby library. system-timer has no bugs, it has no vulnerabilities and it has low support. However system-timer has a Non-SPDX License. You can download it from GitHub.

System Timer, a timer based on underlying SIGALRM system timers, is a solution to Ruby processes which hang beyond the time limit when accessing external resources. This is useful when timeout.rb, which, on M.R.I 1.8, relies on green threads, does not work consistently.

Support

Quality

Security

License

Reuse

Support

system-timer has a low active ecosystem.

It has 75 star(s) with 14 fork(s). There are 4 watchers for this library.

It had no major release in the last 6 months.

There are 9 open issues and 8 have been closed. On average issues are closed in 70 days. There are 3 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of system-timer is current.

Quality

system-timer has 0 bugs and 126 code smells.

Security

system-timer has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

system-timer code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

system-timer has a Non-SPDX License.

Non-SPDX licenses can be open source with a non SPDX compliant license, or non open source licenses, and you need to review them closely before use.

Reuse

system-timer releases are not available. You will need to build from source code and install.

Installation instructions are not available. Examples and code snippets are available.

system-timer saves you 3869 person hours of effort in developing the same functionality from scratch.

It has 8244 lines of code, 1207 functions and 183 files.

It has medium code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi has reviewed system-timer and discovered the below as its top functions. This is intended to give you an instant insight into system-timer implemented functionality, and help decide if they suit your requirements.

Returns the next deadline for the current timer
Trigger the next timer for the given timer
Logs the timeout after a timeout
register a thread
register a timer
Logs out of a registered timer .
Returns the next trigger for the trigger
Calculates the next trigger for the given interval .
Cancel a registered timer

Get all kandi verified functions for this library.

system-timer Key Features

No Key Features are available at this moment for system-timer.

system-timer Examples and Code Snippets

No Code Snippets are available at this moment for system-timer.

Community Discussions

Trending Discussions on system-timer

Which is to use Stop/Start timer vs SynchronizingObject vs lock for System.Timers.Timer?

Problems with System.Timers.Timer. Firing more than once occasionally

Need to include audit trail and error logging in my use case diagram

QUESTION

Which is to use Stop/Start timer vs SynchronizingObject vs lock for System.Timers.Timer?

Asked 2017-Nov-07 at 17:33

Top note: Per comments I could guess all are working solutions with this note Indeed in my application I am trying to combine them. By the way before downvoting you could ask me for details.

Top note 2: By the way, as SO is different from MSO downvotes or close votes encourages deleting question, I won't, otherwise all valuable comments and answer will be deleted. Here is a place to help and try to understand each other

Here is most basic of 4 different implemantations of linqpad codes. Except first all others gives desired output.

Can you explain details for them?

As I have many timers in my application I need to manage and synchronize, in complete code which is to best use and what are the pro/cons of alternative solutions

Without Neither SynchronizingObject nor timer stop/start nor lock

...

ANSWER

Answered 2017-Nov-07 at 17:19

The 4th solution (lock) is a dangerous one. Since the Elapsed event will be raised on a ThreadPool thread each time and you might potentially block many of them simultaneously, this could cause the ThreadPool to grow (with all the consequences). So that solution is a bad one.
The 3rd solution (start/stop) will process the events not at the rate set by the timer, but rather at the rate that depends on how much time does each particular action take. So it may "skip" many events. This solution is like a "frame drop" in video streaming.
The 2nd solution will enqueue all the actions and won't skip them. It's potentially dangerous when the action's processing time is (almost always) longer than the timer interval. The queue will only grow causing an OutOfMemoryException at some time. This solution is like a "frame buffer" in video streaming.
The 1st one should be deleted, there are only issues with that.

So you should choose between the 2nd and the 3rd solution depending on what is of importance for your use case: a reliable processing of all incoming events or a processing with a maximal possible throughput (rate).

Source https://stackoverflow.com/questions/47163541

QUESTION

Problems with System.Timers.Timer. Firing more than once occasionally

Asked 2017-Jul-18 at 20:26

I'm using System.Timers.Timer to backup my SQL Server Express Database once a day. It seems to work fine, most of the time. Occasionally, the ElapsedEventHandler gets called multiple times at 1 or 4 minute intervals. It should just be hit once a day. I have AutoReset as false and I call Start at the end of the ElapsedEventHandler. Also, possibly relevant is that I do recalculate the interval so that the timer always goes off as close to 1 am. as possible. The backing up of the database can take a few minutes, and if I didn't change the interval, the time might drift unacceptably. I mention this because these links suggest there might be a problem with resetting the interval:

See in particular the answers by Hans Passant

However, I don't see how I can avoid resetting the interval. Also, I looked into the code for System.Timers.Timer. It didn't seem like just resetting the interval would Start the timer again. I'm not opposed to using a different timer (System.Threading.Timer?) but I'd like to know what is going on first.

I've pasted all the code below. I would think the truly relevant part is the method: DatabaseBackupTimerOnElapsed

Finally, I'll mention that the program is sometimes stopped and restarted (if there are uncaught exceptions in other parts of the code). I would assume though that all timers are killed at the point of exiting the program even if Dispose is not called? That is Timers don't live on in the operating system?

EDIT I was requested to put down a small, complete, verifiable example. I do so here. I've kept the full example as someone might claim (quite correctly!) that I took out an important detail. I've run this code and have NOT seen the problem but then, it only happens very occasionally with the original code.

...

ANSWER

Answered 2017-Jul-18 at 19:03

I think the solution is overly complicated.

The timer interval will fire the Elapsed event independent of when the fact that a previous run had finished or not, unless you explicitly stop the timer during the event. This should not be necessary. You could simply keep track of whether you are running or not when you enter the method.
Set the interval to 59999. This is a millisecond short of a minute. Then at entry in the event handler check if the current hour and minute correspond to the time when you want to backup.

Source https://stackoverflow.com/questions/45174202

QUESTION

Need to include audit trail and error logging in my use case diagram

Asked 2017-Jan-31 at 12:38

Our app support team is suggesting to implement audit trail, extensive error logging and a new batch job to process some data internally. Before implementing this, I want to make changes in my use case diagram. I think audit trail must be an use case but not sure about the error logging. Should it be considered as an use case. This link http://www.umlchannel.com/en/uml/item/24-use-case-actor-system-timer is saying an use case sometimes may have NO actor. Can we consider error logging as an use case without an actor? Can I consider a batch job as an use case where batch scheduler as an actor?

Another clarification I need is : I know actor can be a person or another system. Can we consider an event (that interact with a solution through use case) as an actor?

...

ANSWER

Answered 2017-Jan-31 at 12:38

A use case must have an actor, since basically it just describes the added value for its actor. The author of the referenced article is simply wrong here.

P. 637 of the UML 2.5 specs:

Each UseCase specifies some behavior that a subject can perform in collaboration with one or more Actors.

...

A subject of a UseCase could be a system or any other element that may have behavior, such as a Component or Class. Each UseCase specifies a unit of useful functionality that the subject provides to its users

N.B.: Though the UML is the "true source", it's not a good read about use cases. Instead I highly recommend Bittner/Spence.

There are several ways to approach the Log error "use case". One would be to use cases with Log error. But actually, there are a couple of drawbacks with this. Log error might give additional value in the long term (system improvements and bug corrections), but it is not an a-priori added value. Also you would just clutter your use case diagrams.

A second way is to change the perspective and include the "system" itself as an actor. But this is an anti-pattern. So not recommended as well.

Finally, you could simply add a non-functional requirement to your system and just trace to the use cases which are relevant. This is what I'd recommend to do.

Your additional questions:

A batch job is no use case, but a use case can be implemented as a batch job and the scheduler can be the actor.
No, an event is an event and not an actor. An event can trigger a chain of actions being part of a use case.

Source https://stackoverflow.com/questions/41951170

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install system-timer

You can download it from GitHub.
On a UNIX-like operating system, using your system’s package manager is easiest. However, the packaged Ruby version may not be the newest one. There is also an installer for Windows. Managers help you to switch between multiple Ruby versions on your system. Installers can be used to install a specific or multiple Ruby versions. Please refer ruby-lang.org for more information.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: