darthShadow
Joined 7 years ago
Karma
2,025
Submissions
61
Member since
Mar 14
https://github.com/darthShadow
View on Hacker NewsRecent submissions
Comment · 5 months ago
Comment · 9 months ago
> doesn't honor dropbox's retry-after header
That hasn't been true for more than 8 years now.
Source: https://github.com/rclone/rclone/blob/9abf9d38c0b80094302281...
And the PR adding it: https://github.com/rclone/rclone/pull/2622
Comment · 1 year ago
Just curious, was something like https://github.com/containerd/stargz-snapshotter considered/evaluated before designing your own lazily-loaded container FS and if so, any pros/cons for the same?
Comment · 1 year ago
Visa/MasterCard/Amex already support such a facility in India due to RBI requirements. Doesn't seem too difficult to adapt similar functionality for other countries too, if the regulations are updated to require it.
* https://www.visa.co.in/about-visa/newsroom/press-releases/vi... * https://pgi.billdesk.com/web/sihub
Comment · 1 year ago
Comment · 1 year ago
These may be useful reading:
https://github.com/TryGhost/node-sqlite3/issues/408#issue-57...
https://github.com/WiseLibs/better-sqlite3/issues/32#issueco...
Copying a quote from the second:
> The sqlite3 C API serializes all operations (even reads) within a single process. You can parallelize reads to the database but only by having multiple processes, in which case one process being blocked doesn't affect the other processes anyways. In other words, because sqlite3 serializes everything, doing things asynchronously won't speed up database access within a process. It would only free up time for your app to do other things (like HTTP requests to other servers). Unfortunately, the overhead imposed on sqlite3 to serialize asynchronous operations is quite high, making it disadvantageous 95% of the time.
Comment · 1 year ago
From the project README:
> Thruster also wraps the Puma process so that you can use it without managing multiple processes yourself. This is particularly useful when running in a containerized environment, where you typically won't have a process manager available to coordinate the processes. Instead you can use Thruster as your CMD, and it will manage Puma for you.
Comment · 1 year ago
You have Lidarr[1] as an equivalent to Sonarr/Radarr etc. and there is a pending PR[2] for adding Lidarr support to Overseerr which also has a custom docker image to try.
[1] https://github.com/Lidarr/Lidarr [2] https://github.com/sct/overseerr/pull/3800
Comment · 1 year ago
FWIW, auto_vacuum set to INCREMENTAL doesn't do any vacuuming automatically; it just stores the information needed to vacuum the DB.
From https://www.sqlite.org/pragma.html#pragma_auto_vacuum:
> When the value of auto-vacuum is 2 or "incremental" then the additional information needed to do auto-vacuuming is stored in the database file but auto-vacuuming does not occur automatically at each commit as it does with auto_vacuum=full. In incremental mode, the separate incremental_vacuum pragma must be invoked to cause the auto-vacuum to occur.
Comment · 2 years ago
Comment · 2 years ago
Hardcover may be worth a try: