| Commit message (Collapse) | Author | Age | Lines |
| |
|
|
|
|
| |
The actual replay might still be bugged, but fixed-point review works.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
e69-2 is looking good.
Now with a separate age-entity. Not really used for anything fancy right
now, but could be.
|
|
|
|
|
|
|
|
|
| |
Again.
It's using the prototype, and the objects are configurable. I assume this
will need some work.
Also: I touched ping up to make it work without linknets.
|
|
|
|
| |
Finally found something that lacks correctness in postgres.
|
|
|
|
|
|
|
|
|
|
|
|
| |
The use case is primarily about supporting generic ?offset=5m independently
from now=2015-04-02T15:00:30. Two reasons for this:
1. It allows easy generic client-side code to get two slightly offset time
series.
2. It makes it possible to get the most recent data + an offset without
having to refer to set now=(clock) to real time.
Also: Untested, so its probably broken.
|
|
|
|
|
| |
The biggest thing here is the addition of a generic poller and a generic
"hash" from the backend so equality can easily be checked.
|
| |
|
|
|
|
| |
Better to have proper isolation than this crud.
|
| |
|
|
|
|
|
|
| |
Needs lots of work.
And also, I removed CGI.pm because it sucks.
|
| |
|
|
|
|
|
|
|
| |
Moving SNMP into a separate module reduces startup time for all the stuff
that doesn't need it.
Currently comments are broken because the js hasn't been updated.
|
|
|