datatogether sentry issues

datatogether / sentry

Parallelized web crawler written in Golang

GNU Affero General Public License v3.0

14 stars 6 forks source link

issues

Newest

Newest Most commented Recently updated Oldest Least commented Least recently updated

fix README installation instructs based on issue #51

#54 wesleyParriott closed 6 years ago
0
Add repo to Codecov

#53 dcwalk opened 6 years ago
0
Fix link to sample schema file in Usage section of README

#52 machawk1 closed 6 years ago
0
Missing dependency

#51 machawk1 closed 6 years ago
4
Add crawler_test.go and some static examples.

#50 chinchila closed 6 years ago
3
Docker usage

#49 machawk1 closed 7 years ago
3
add usage to README

#48 titaniumbones closed 6 years ago
1
Improve README for new developers

#47 titaniumbones opened 7 years ago
0
write tests for transports.go

#46 titaniumbones opened 7 years ago
0
write tests for server.go

#45 titaniumbones opened 7 years ago
0
write tests for seed_crawler.go

#44 titaniumbones opened 7 years ago
0
write tests for page.go

#43 titaniumbones opened 7 years ago
0
write tests for middleware.go

#42 titaniumbones opened 7 years ago
0
write tests for handlers.go

#41 titaniumbones opened 7 years ago
0
write tests for doc.go

#40 titaniumbones opened 7 years ago
0
write tests for cron.go

#39 titaniumbones opened 7 years ago
0
write tests for crawler.go

#38 titaniumbones closed 6 years ago
11
write tests for content_crawler.go

#37 titaniumbones opened 7 years ago
0
write tests for config.go

#36 titaniumbones opened 7 years ago
0
write tests for config.go

#35 titaniumbones opened 7 years ago
0
write tests for $i\n\ntests should cover all functions with CapitalizedNames and demonstrate an understanding of what the function is supposed to accomplish[the Golang Book](https://www.golang-book.com/books/intro/12) for more information about testing in go.\n\nThis issue is part of #19, the testing coverage metaissue.

#34 titaniumbones closed 7 years ago
0
write tests for $i\n\ntests should cover all functions with CapitalizedNames and demonstrate an understanding of what the function is supposed to accomplish[the Golang Book](https://www.golang-book.com/books/intro/12) for more information about testing in go.\n\nThis issue is part of #19, the testing coverage metaissue.

#33 titaniumbones closed 7 years ago
0
write tests for $i\n\ntests should cover all functions with CapitalizedNames and demonstrate an understanding of what the function is supposed to accomplish[the Golang Book](https://www.golang-book.com/books/intro/12) for more information about testing in go.\n\nThis issue is part of #19, the testing coverage metaissue.

#32 titaniumbones closed 7 years ago
0
write tests for $i\n\ntests should cover all functions with CapitalizedNames and demonstrate an understanding of what the function is supposed to accomplish[the Golang Book](https://www.golang-book.com/books/intro/12) for more information about testing in go.\n\nThis issue is part of #19, the testing coverage metaissue.

#31 titaniumbones closed 7 years ago
0
write tests for $i\n\ntests should cover all functions with CapitalizedNames and demonstrate an understanding of what the function is supposed to accomplish[the Golang Book](https://www.golang-book.com/books/intro/12) for more information about testing in go.\n\nThis issue is part of #19, the testing coverage metaissue.

#30 titaniumbones closed 7 years ago
0
write tests for $i\n\ntests should cover all functions with CapitalizedNames and demonstrate an understanding of what the function is supposed to accomplish[the Golang Book](https://www.golang-book.com/books/intro/12) for more information about testing in go.\n\nThis issue is part of #19, the testing coverage metaissue.

#29 titaniumbones closed 7 years ago
0
write tests for $i\n\ntests should cover all functions with CapitalizedNames and demonstrate an understanding of what the function is supposed to accomplish[the Golang Book](https://www.golang-book.com/books/intro/12) for more information about testing in go.\n\nThis issue is part of #19, the testing coverage metaissue.

#28 titaniumbones closed 7 years ago
0
write tests for $i\n\ntests should cover all functions with CapitalizedNames and demonstrate an understanding of what the function is supposed to accomplish[the Golang Book](https://www.golang-book.com/books/intro/12) for more information about testing in go.\n\nThis issue is part of #19, the testing coverage metaissue.

#27 titaniumbones closed 7 years ago
0
write tests for $i\n\ntests should cover all functions with CapitalizedNames and demonstrate an understanding of what the function is supposed to accomplish[the Golang Book](https://www.golang-book.com/books/intro/12) for more information about testing in go.\n\nThis issue is part of #19, the testing coverage metaissue.

#26 titaniumbones closed 7 years ago
0
write tests for $i\n\ntests should cover all functions with CapitalizedNames and demonstrate an understanding of what the function is supposed to accomplish[the Golang Book](https://www.golang-book.com/books/intro/12) for more information about testing in go.\n\nThis issue is part of #19, the testing coverage metaissue.

#25 titaniumbones closed 7 years ago
0
write tests for $i\n\ntests should cover all functions with CapitalizedNames and demonstrate an understanding of what the function is supposed to accomplish[the Golang Book](https://www.golang-book.com/books/intro/12) for more information about testing in go.\n\nThis issue is part of #19, the testing coverage metaissue.

#24 titaniumbones closed 7 years ago
0
write tests for $i\n\ntests should cover all functions with CapitalizedNames and demonstrate an understanding of what the function is supposed to accomplish[the Golang Book](https://www.golang-book.com/books/intro/12) for more information about testing in go.\n\nThis issue is part of #19, the testing coverage metaissue.

#23 titaniumbones closed 7 years ago
0
write tests for $i\n\ntests should cover all functions with CapitalizedNames and demonstrate an understanding of what the function is supposed to accomplish[the Golang Book](https://www.golang-book.com/books/intro/12) for more information about testing in go.\n\nThis issue is part of #19, the testing coverage metaissue.

#22 titaniumbones closed 7 years ago
0
write tests for $i\n\ntests should cover all functions with CapitalizedNames and demonstrate an understanding of what the function is supposed to accomplish[the Golang Book](https://www.golang-book.com/books/intro/12) for more information about testing in go.\n\nThis issue is part of #19, the testing coverage metaissue.

#21 titaniumbones closed 7 years ago
0
write tests for $i\n\ntests should cover all functions with CapitalizedNames and demonstrate an understanding of what the function is supposed to accomplish[the Golang Book](https://www.golang-book.com/books/intro/12) for more information about testing in go.\n\nThis issue is part of #19, the testing coverage metaissue.

#20 titaniumbones closed 7 years ago
0
Add tests for all go files

#19 titaniumbones opened 7 years ago
0
Feature 7/installation readme

#18 KrzysztofMadejski closed 7 years ago
1
Added link to CircleCI badge.

#17 patcon closed 7 years ago
1
server_test.go needs to be updated so that actual outputs match desired outputs

#16 osterbit opened 7 years ago
0
Add README and Templates

#15 titaniumbones closed 7 years ago
2
Sprint prep

#14 b5 closed 7 years ago
2
Should WARC records on the distributed web default to a flat list of hashes, or should we crawl to directories

#13 b5 opened 7 years ago
4
Import & Use WARC & CDXJ packages!

#12 b5 opened 7 years ago
0
Heritrix parity

#11 b5 opened 7 years ago
1
Add html test data & example test server

#10 b5 opened 7 years ago
0
Error loading config

#9 KrzysztofMadejski opened 7 years ago
2
Dependency management

#8 KrzysztofMadejski opened 7 years ago
0
Good README needed

#7 KrzysztofMadejski opened 7 years ago
7
Added link to README for archiving tool comparison research.

#6 patcon closed 7 years ago
0
begin querying for & handling data.json requests

#5 b5 opened 7 years ago
0