[WIP] Release 0.4.0 -- Fully adding SQL #113
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Owner
Ianleeclark
commented
Apr 24, 2016
•
Ianleeclark
commented
- Accrue technical debt
- Fixes Write to volume with docker #122 (Write to volumes w/ docker)
- Fixes While peer reaper is sleeping, do useful backend tasks. #121 (Perform operations while reaper is sleeping)
- Fixes Unit test config/config.go #117 (Unit test config.go)
- Fixes Add a CONTRIBUTORS.md #114 (Add contributors.md w/ section explaining why I do things the way I do)
- Fixes Investigate go mysql migration tools #89 (MySQL Migration tooling)
- Fixes Build redis info_hash list from MySQL database #88 (Build redis info_hash list from whitelisted torrents, depends upon Allow torrent-file whitelisting #87)
- Fixes Allow torrent-file whitelisting #87 (Allow torrent-file whitelisting)
- Fixes Allow for sql-tiering #81 (Add sql tiering)
- Fixes Add statistics tracking #64 (Add statistics tracking)
- Fixes Support /scrape convention #25 (support /scrape, depends upon Allow for sql-tiering #81)
added 2 commits
April 24, 2016 10:41
Update config.yaml
|
https://github.com/go-playground/overalls This looks like I might be able to add coverage. |
* Issue #87 ADD: - database/schemas.go:Torrent a new structure used to represent how the torrent exists in the DB. - database/database_test.go Working on adding tests for all Database abstractions CHANGE: - server/server.go:scrapeHandler() Or whatever its called. Removing for now. * Issue #87 CHANGE: - {.travis.yml, config.yaml}: Changing the database name because `test-db` isn't a valid MYSQL db name. * Update config.yaml * Issue #87 CHANGE: - config/config.go Changing how LoadConfig() returns. * Issue #87 ADD: - build/schema_create.sql a new file used to create a user for the local mysql server
|
#88 will allow us to remove the DB query from the whitelist checking because if it doesn't exist in Redis and we're whitelisting, we don't need to double check. |
Ianleeclark
changed the title
* Issue #88 ADD: - database.go:GetWhitelistedTorrents() A new way to retrieve all of the whitelisted torrents. * Issue #88: Test 2 * Issue #88 test 3 * Issue #88: teststststs * Issue #88: more tests * Update database_test.go * Update database_test.go * Update database_test.go * Update database_test.go * Update database.go * Update database_test.go * Update database_test.go * Update database_test.go * Update database_test.go * Update database_test.go * Issue #88 ADD: - main.go:init() Now loads whitelisted torrents into Redis - server/announce.go Now rejects upon invalid torrent. * Issue #88 REMOVE: server/announce.go:StartedEventHandler() Removed DB verification, as if the torrent doesn't exist in Redis, it shouldn't be whitelisted.
* Issue #64 ADD: - We now tracker tracker-wide upload/download bytes. - Any file changes are to support this or issue #81 * Issue #81 ADD: - database.go:UpdatePeerStats() Is now working and online, but it only filters by the user's IP. This should be updated in the future, but I'm not sure what else to filter by.
Resolve merge conflicts on origin/devel
ADD:
- database/database.go:UpdateTorrentStats() Now updates torrent stats to +/1
the seeders/leechers for a specific torrent.
- server/announce_response.go:formatScrapeResponse() Now formats the scrape
response into a dictionary.
CHANGE:
- database/schemas.go:Torrent.{Seeders,Leechers} Are now type `int` instead
of type `int64`
- server/server.go Updated how we write responses to two functions and
finished scrape responses
[WIP] Issue #25
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.