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.
89 lignes
2,8 Kio
Markdown
89 lignes
2,8 Kio
Markdown
# bitset
|
|
|
|
*Go language library to map between non-negative integers and boolean values*
|
|
|
|
[](https://travis-ci.org/willf/bitset?branch=master)
|
|
[](https://coveralls.io/github/willf/bitset?branch=master)
|
|
[](https://goreportcard.com/report/github.com/willf/bitset)
|
|
[](http://godoc.org/github.com/willf/bitset)
|
|
|
|
|
|
## Description
|
|
|
|
Package bitset implements bitsets, a mapping between non-negative integers and boolean values.
|
|
It should be more efficient than map[uint] bool.
|
|
|
|
It provides methods for setting, clearing, flipping, and testing individual integers.
|
|
|
|
But it also provides set intersection, union, difference, complement, and symmetric operations, as well as tests to check whether any, all, or no bits are set, and querying a bitset's current length and number of positive bits.
|
|
|
|
BitSets are expanded to the size of the largest set bit; the memory allocation is approximately Max bits, where Max is the largest set bit. BitSets are never shrunk. On creation, a hint can be given for the number of bits that will be used.
|
|
|
|
Many of the methods, including Set, Clear, and Flip, return a BitSet pointer, which allows for chaining.
|
|
|
|
### Example use:
|
|
|
|
```go
|
|
package main
|
|
|
|
import (
|
|
"fmt"
|
|
"math/rand"
|
|
|
|
"github.com/willf/bitset"
|
|
)
|
|
|
|
func main() {
|
|
fmt.Printf("Hello from BitSet!\n")
|
|
var b bitset.BitSet
|
|
// play some Go Fish
|
|
for i := 0; i < 100; i++ {
|
|
card1 := uint(rand.Intn(52))
|
|
card2 := uint(rand.Intn(52))
|
|
b.Set(card1)
|
|
if b.Test(card2) {
|
|
fmt.Println("Go Fish!")
|
|
}
|
|
b.Clear(card1)
|
|
}
|
|
|
|
// Chaining
|
|
b.Set(10).Set(11)
|
|
|
|
for i, e := b.NextSet(0); e; i, e = b.NextSet(i + 1) {
|
|
fmt.Println("The following bit is set:", i)
|
|
}
|
|
if b.Intersection(bitset.New(100).Set(10)).Count() == 1 {
|
|
fmt.Println("Intersection works.")
|
|
} else {
|
|
fmt.Println("Intersection doesn't work???")
|
|
}
|
|
}
|
|
```
|
|
|
|
As an alternative to BitSets, one should check out the 'big' package, which provides a (less set-theoretical) view of bitsets.
|
|
|
|
Godoc documentation is at: https://godoc.org/github.com/willf/bitset
|
|
|
|
## Installation
|
|
|
|
```bash
|
|
go get github.com/willf/bitset
|
|
```
|
|
|
|
## Contributing
|
|
|
|
If you wish to contribute to this project, please branch and issue a pull request against master ("[GitHub Flow](https://guides.github.com/introduction/flow/)")
|
|
|
|
This project include a Makefile that allows you to test and build the project with simple commands.
|
|
To see all available options:
|
|
```bash
|
|
make help
|
|
```
|
|
|
|
## Running all tests
|
|
|
|
Before committing the code, please check if it passes all tests using (note: this will install some dependencies):
|
|
```bash
|
|
make qa
|
|
```
|