ccf1f695af
Prevent negative numbers in dbinfo output.
...
This might occur if things change while we're calculating the sizes.
2013-08-05 12:25:36 -04:00
06f7390c9e
Fix disk usage block size
2013-08-05 12:25:10 -04:00
6de77a08f1
Report actual disk size, not apparent size
2013-08-05 12:16:56 -04:00
04f815a24b
Reorder nilmtool commands
2013-08-04 19:51:13 -04:00
6868f5f126
fsck: limit max retries so we don't get stuck in a loop forever
2013-08-03 22:34:30 -04:00
ca0943ec19
fsck: add --no-data option to do a quicker fsck
...
This makes it fast enough to run at startup with -f, if it's expected
that a system will frequently need to be fixed.
2013-08-03 22:31:45 -04:00
68addb4e4a
Clarify output when fsck database is locked
2013-08-03 21:58:24 -04:00
68c33b1f14
fsck: add comma separator on big numbers
2013-08-03 21:50:33 -04:00
8dd8741100
Tweak options, dependencies, documentation
2013-08-03 21:42:49 -04:00
8e6341ae5d
Verify that data timestamps are monotonic
2013-08-03 21:32:05 -04:00
422b1e2df2
More fsck improvements. Fixed two problems on sharon so far.
2013-08-03 17:50:46 -04:00
0f745b3047
More fsck tools, including fixes
2013-08-03 16:43:20 -04:00
71cd7ed9b7
Add nilmdb-fsck tool to check database consistency
2013-08-03 14:23:14 -04:00
8e8ec59e30
Support "nilmtool cmd --version"
2013-08-01 15:14:34 -04:00
b89b945a0f
Better responses to invalid HTTP times
2013-07-31 13:37:04 -04:00
bd7bdb2eb8
Add --optimize option to nilmtool intervals
2013-07-30 15:31:51 -04:00
bbd59c8b50
Add nilmdb.utils.interval.intersection by generalizing set_difference
2013-07-30 14:48:19 -04:00
405c110fd7
Doc updates
2013-07-29 15:36:43 -04:00
274adcd856
Documentation updates
2013-07-27 19:51:09 -04:00
a1850c9c2c
Misc documentation
2013-07-25 16:08:35 -04:00
6cd28b67b1
Support iterator protocol in Serializer
2013-07-24 14:52:26 -04:00
d6d215d53d
Improve boolean HTTP parameter handling
2013-07-15 14:38:28 -04:00
90633413bb
Add nilmdb.utils.interval.human_string function
2013-07-09 19:01:53 -04:00
c7c3aff0fb
Add nilmdb.utils.interval.optimize function
2013-07-09 17:50:21 -04:00
e2347c954e
Split more CherrpyPy stuff into serverutil
2013-07-02 11:44:08 -04:00
222a5c6c53
Move server decorators and other utilities to a separate file
...
This will help with implementing nilmrun.
2013-07-02 11:32:19 -04:00
1ca2c143e5
Fix typo
2013-06-29 12:39:00 -04:00
2768a5ad15
Show FQDN rather than hostname.
2013-05-09 13:33:05 -04:00
a105543c38
Show a more helpful message at the root nilmdb path
2013-05-09 13:30:10 -04:00
9a27b6ef6a
Make rocket code suitable for 32-bit architectures
2013-05-08 16:35:32 -04:00
99532cf9e0
Fix coverage
2013-05-07 23:00:44 -04:00
dfdd0e5c74
Fix line parsing in http client
2013-05-07 22:56:00 -04:00
9a2699adfc
Attempt at fixing up more Unicode issues with metadata.
2013-05-07 13:44:03 -04:00
9bbb95b18b
Add unicode decode/encode helpers
2013-05-07 12:56:59 -04:00
6bbed322c5
Fix unicode in completion
2013-05-07 12:49:12 -04:00
2317894355
Tweak cache sizes to account for large numbers of decimated tables
2013-05-06 11:54:57 -04:00
539c92226c
Add more disk space info
2013-05-06 11:36:28 -04:00
77c766d85d
Bump MAX_LAYOUT_COUNT to 1024
2013-05-02 15:27:31 -04:00
49d04db1d6
Allow start==end in stream_insert_context, if no data was provided.
2013-04-11 13:25:37 -04:00
ea838d05ae
Warn against reused context managers, and fix broken tests
2013-04-11 13:25:00 -04:00
f2a48bdb2a
Test binary extract; fix bugs
2013-04-11 13:24:11 -04:00
6d14e0b8aa
Allow binary extract
2013-04-11 11:30:41 -04:00
b98ff1331a
Fix bug where too much data was getting written to each file.
...
We were still calculating the maximum number of rows correctly,
so the extra data was really extra and would get re-written to the
beginning of the subsequent file.
The only case in which this would lead to database issues is if the
very last file was lengthened incorrectly, and the "nrows" calculation
would therefore be wrong when the database was reopened. Still, even
in that case, it should just leave a small gap in the data, not cause
any errors.
2013-04-10 23:22:03 -04:00
00e6ba1124
Avoid ENOENT in nilmdb.utils.diskusage.du
...
ENOENT might show up if we're actively deleting files in the nilmdb
thread while trying to read available space from e.g. the server
thread.
2013-04-10 22:25:22 -04:00
01029230c9
Tweaks to sorting
2013-04-10 19:59:38 -04:00
23f31c472b
Split sort_streams_nicely into separate file
2013-04-10 19:07:58 -04:00
a1e2746360
Fix bug in nilmdb.stream_remove with max_removals
2013-04-10 18:37:21 -04:00
1c40d59a52
server: use a generator in /stream/remove
...
Instead of returning a single number at the end of N nilmdb calls, we
now use a generator that returns one line of text every time there's a
new count of rows removed. This ensures that the connection will stay
alive for very long removals.
2013-04-10 18:11:58 -04:00
bfb09a189f
Fix coverage
2013-04-10 16:33:08 -04:00
416a499866
Support wildcards for destroy
2013-04-10 16:23:07 -04:00
