Warning: gap of negative duration
See original GitHub issueNot sure what this means, but it floods the logs when running aw-server:
2018-09-23 23:37:59 [WARNING]: Gap was of negative duration (-6.016s). This error will only show once per batch. (aw_transform.flood:28)
2018-09-23 23:38:25 [WARNING]: Gap was of negative duration (-6.016s). This error will only show once per batch. (aw_transform.flood:28)
2018-09-23 23:38:54 [WARNING]: Gap was of negative duration (-6.016s). This error will only show once per batch. (aw_transform.flood:28)
Issue Analytics
- State:
- Created 5 years ago
- Reactions:2
- Comments:13 (5 by maintainers)
Top Results From Across the Web
Negative Gap Definition
A zero duration gap is when there is no positive gap or negative gap and a firm is protected against interest rate movements....
Read more >Negative MIP gap | Decision Optimization
When solving a certain optimization problem the gap becomes negative. How can this be possible? I thought that the MIP gap quantifies the ......
Read more >Solved When the duration gap is negative, it means that the
When the duration gap is negative, it means that the duration of assets < duration of liabilities, so liabilities are more sensitive than...
Read more >The hunt for duration: not waving but drowning?
Declining long-term interest rates tend to widen the negative duration gap between the assets and liabilities of insurers and pension funds, ...
Read more >What is negative sequence current and how does it affect ...
Short time heating is of interest during system fault conditions and it is usual in determining the generator negative sequence withstand ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

@johan-bjareholt This occurs when events overlap. We would have to investigate which watcher is causing it.
I have the same issue. However, I think I know exactly what caused it in my case (probably very different from the others):
I had to test the behavior of some app when the system date changes, so I was manually changing my system’s date and time going back and forth into the future and the past.
AW was running all the time while I was doing that. I can confirm that the effected time range in AW that causes this issue is exactly the time I was playing with the system date.
Not sure if this is helpful to you or not though 😅 .