b2b48f61b0
* [WIP] Torrent Generation on not found error As asked in #1517, it allows on-the-fly torrent generation. Since it uses magnet links, it needs some time to connect to peers. So it can't be instant generation, we need the user to wait and try after a minute at least. * Replace Fatal by simple error * attempt at fixing travis * del * Add Anacrolyx dependency * Add back difflib * Remove .torrent suffix in the url example * Add some explanations when file missing page shown * Ignore downloads directory * Either use cache (third-party site) or own download directory * Wrong import * If there is an error then it means we aren't generating a torrent file May it be "torrent not found" or "We do not store torrent files" which are the two only existing errors for this page * hash is never empty * TorrentLink may be empty at times So we add a /download/:hash link if it is * Update README.md * Made a mistake here, need to check if false * Update en-us.all.json * Update CHANGELOG.md * Torrent file generation can be triggered by click on button if JS enabled * Update download.go * Update download.go * Use c.JSON instead of text/template * Return to default behavior if we don't generate the file * Don't do the query if returned to default behavior * Add "Could not generate torrent file" error * Fix JS condition & lower delay until button updates * Start download automatically once torrent file is generated * Fix torrentFileExists() constantly returning false if external torrent download URL * torrent-view-data is two tables instead of one This allows the removal of useless things without any problem (e.g Website link), but also a better responsibe design since the previous one separated stats after a certain res looking very wonky * CSS changes to go along * Remove useless <b></b> * Update main.css * In torrentFileExists, check if filestorage path exists instead of looking at the domain in torrent link When checking if the file is stored on another server i used to simply check if the domain name was inside the torrent link, but we can straight up check for filestorage length * Fix JS of on-demand stat fetching * ScrapeAge variable accessible through view.jet.html Contains last scraped time in hours, is at -1 is torrent has never been scraped Stats will get updated if it's either at -1 or above 1460 (2 months old) * Refresh stats if older than two months OR unknown and older than 24h Show last scraped date even if stats are unknown * Add StatsObsolete variable to torrent Indicating if: - They can be shown - They need to be updated * Update scraped data even if Unknown, prevent users from trying to fetch stats every seconds * Torrent file stored locally by default * no need to do all of that if no filestorage * fix filestorage path * Fix torrent download button stuck on "Generating torrent file" at rare times * fix some css rules that didn't work on IE * Fix panic error Seems like this error is a known bug from anacrolyx torrent https://github.com/anacrolix/torrent/issues/83 To prevent it, I'm creating a single client and modifying the socket.go to make it not raise a panic but a simple error log.
44 lignes
1,7 Kio
Go
44 lignes
1,7 Kio
Go
/*
|
|
Package bolt implements a low-level key/value store in pure Go. It supports
|
|
fully serializable transactions, ACID semantics, and lock-free MVCC with
|
|
multiple readers and a single writer. Bolt can be used for projects that
|
|
want a simple data store without the need to add large dependencies such as
|
|
Postgres or MySQL.
|
|
|
|
Bolt is a single-level, zero-copy, B+tree data store. This means that Bolt is
|
|
optimized for fast read access and does not require recovery in the event of a
|
|
system crash. Transactions which have not finished committing will simply be
|
|
rolled back in the event of a crash.
|
|
|
|
The design of Bolt is based on Howard Chu's LMDB database project.
|
|
|
|
Bolt currently works on Windows, Mac OS X, and Linux.
|
|
|
|
|
|
Basics
|
|
|
|
There are only a few types in Bolt: DB, Bucket, Tx, and Cursor. The DB is
|
|
a collection of buckets and is represented by a single file on disk. A bucket is
|
|
a collection of unique keys that are associated with values.
|
|
|
|
Transactions provide either read-only or read-write access to the database.
|
|
Read-only transactions can retrieve key/value pairs and can use Cursors to
|
|
iterate over the dataset sequentially. Read-write transactions can create and
|
|
delete buckets and can insert and remove keys. Only one read-write transaction
|
|
is allowed at a time.
|
|
|
|
|
|
Caveats
|
|
|
|
The database uses a read-only, memory-mapped data file to ensure that
|
|
applications cannot corrupt the database, however, this means that keys and
|
|
values returned from Bolt cannot be changed. Writing to a read-only byte slice
|
|
will cause Go to panic.
|
|
|
|
Keys and values retrieved from the database are only valid for the life of
|
|
the transaction. When used outside the transaction, these byte slices can
|
|
point to different data or can point to invalid memory which will cause a panic.
|
|
|
|
|
|
*/
|
|
package bolt
|