Branch:
master
NicoNex/master
datatypes
experimental-lfu
fix_recovery_paths
fix_runGC
github-actions-test
gofrs_flock
jsign/goversion
master
range_scan
regression_locking_after_merge
reviewdog_checks
scan_deadlock
0.0.1
0.0.10
0.0.11
0.0.12
0.0.13
0.0.14
0.0.15
0.0.16
0.0.17
0.0.18
0.0.19
0.0.2
0.0.20
0.0.21
0.0.22
0.0.23
0.0.24
0.0.25
0.0.26
0.0.3
0.0.4
0.0.5
0.0.6
0.0.7
0.0.8
0.0.9
1.0.0
1.03
v0.1.0
v0.1.1
v0.1.2
v0.1.3
v0.1.4
v0.1.5
v0.1.6
v0.1.7
v0.2.0
v0.2.1
v0.2.2
v0.3.0
v0.3.1
v0.3.10
v0.3.11
v0.3.12
v0.3.13
v0.3.14
v0.3.2
v0.3.3
v0.3.4
v0.3.5
v0.3.6
v0.3.7
v0.3.8
v0.3.9
v1.0.0
v1.0.1
v1.0.2
${ noResults }
1 Commits (master)
| Author | SHA1 | Message | Date |
|---|---|---|---|
 James Mills
|
5429693cc8 |
Add ErrBadConfig and ErrBadMetadata as errors that consumers can check and use (#241)
cc @taigrr This PR will _hopefully_ help to fix some critical isseus in the real world with several or more [Yarn.social](https://yarn.social) pods running [yarnd](https://git.mills.io/yarnsocial/yarn) where starting back up after a power failure or crash can sometimes result in an empty `config.json` or empty `meta.json` or both! I'm not actually sure how this can arise, and as yet I haven't been able to reproduce it (_I can only assume this has to be failures cases outside of our control_); but in any case the application and database is recoverable by simply `rm config.json` and/or `rm meta.json`. So this PR makes errors loading the config and metadata first-class errors and exported error types that consumers of the library can use to perform automated recovery without requiring human intervention. Basiclaly in this case it's no big deal we lost the database config of metadata, we can simply carry on. Co-authored-by: James Mills <prologic@shortcircuit.net.au> Reviewed-on: #241 Co-authored-by: James Mills <james@mills.io> Co-committed-by: James Mills <james@mills.io> |
8 months ago |