Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / datatogether/sentry issues and pull requests
#54 - fix README installation instructs based on issue #51
Pull Request -
State: closed - Opened by wesleyParriott about 6 years ago
#53 - Add repo to Codecov
Issue -
State: open - Opened by dcwalk over 6 years ago
Labels: testing
#52 - Fix link to sample schema file in Usage section of README
Pull Request -
State: closed - Opened by machawk1 over 6 years ago
#51 - Missing dependency
Issue -
State: closed - Opened by machawk1 almost 7 years ago
- 4 comments
Labels: bug, first-timers-only, documentation, ready
#50 - Add crawler_test.go and some static examples.
Pull Request -
State: closed - Opened by chinchila almost 7 years ago
- 3 comments
#49 - Docker usage
Issue -
State: closed - Opened by machawk1 almost 7 years ago
- 3 comments
Labels: bug
#48 - add usage to README
Pull Request -
State: closed - Opened by titaniumbones about 7 years ago
- 1 comment
#47 - Improve README for new developers
Issue -
State: open - Opened by titaniumbones about 7 years ago
Labels: documentation
#46 - write tests for transports.go
Issue -
State: open - Opened by titaniumbones about 7 years ago
Labels: testing
#45 - write tests for server.go
Issue -
State: open - Opened by titaniumbones about 7 years ago
Labels: testing
#44 - write tests for seed_crawler.go
Issue -
State: open - Opened by titaniumbones about 7 years ago
Labels: testing
#43 - write tests for page.go
Issue -
State: open - Opened by titaniumbones about 7 years ago
Labels: testing
#42 - write tests for middleware.go
Issue -
State: open - Opened by titaniumbones about 7 years ago
Labels: testing
#41 - write tests for handlers.go
Issue -
State: open - Opened by titaniumbones about 7 years ago
Labels: testing
#40 - write tests for doc.go
Issue -
State: open - Opened by titaniumbones about 7 years ago
Labels: testing
#39 - write tests for cron.go
Issue -
State: open - Opened by titaniumbones about 7 years ago
Labels: testing
#38 - write tests for crawler.go
Issue -
State: closed - Opened by titaniumbones about 7 years ago
- 11 comments
Labels: testing
#37 - write tests for content_crawler.go
Issue -
State: open - Opened by titaniumbones about 7 years ago
Labels: testing
#36 - write tests for config.go
Issue -
State: open - Opened by titaniumbones about 7 years ago
Labels: testing
#35 - write tests for config.go
Issue -
State: open - Opened by titaniumbones about 7 years ago
Labels: testing
#34 - 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.
Issue -
State: closed - Opened by titaniumbones about 7 years ago
#33 - 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.
Issue -
State: closed - Opened by titaniumbones about 7 years ago
#32 - 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.
Issue -
State: closed - Opened by titaniumbones about 7 years ago
#31 - 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.
Issue -
State: closed - Opened by titaniumbones about 7 years ago
#30 - 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.
Issue -
State: closed - Opened by titaniumbones about 7 years ago
#29 - 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.
Issue -
State: closed - Opened by titaniumbones about 7 years ago
#28 - 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.
Issue -
State: closed - Opened by titaniumbones about 7 years ago
#27 - 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.
Issue -
State: closed - Opened by titaniumbones about 7 years ago
#26 - 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.
Issue -
State: closed - Opened by titaniumbones about 7 years ago
#25 - 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.
Issue -
State: closed - Opened by titaniumbones about 7 years ago
#24 - 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.
Issue -
State: closed - Opened by titaniumbones about 7 years ago
#23 - 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.
Issue -
State: closed - Opened by titaniumbones about 7 years ago
#22 - 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.
Issue -
State: closed - Opened by titaniumbones about 7 years ago
#21 - 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.
Issue -
State: closed - Opened by titaniumbones about 7 years ago
#20 - 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.
Issue -
State: closed - Opened by titaniumbones about 7 years ago
#19 - Add tests for all go files
Issue -
State: open - Opened by titaniumbones about 7 years ago
Labels: testing
#18 - Feature 7/installation readme
Pull Request -
State: closed - Opened by KrzysztofMadejski about 7 years ago
- 1 comment
#17 - Added link to CircleCI badge.
Pull Request -
State: closed - Opened by patcon about 7 years ago
- 1 comment
Labels: doc-sprint
#16 - server_test.go needs to be updated so that actual outputs match desired outputs
Issue -
State: open - Opened by osterbit about 7 years ago
Labels: testing
#15 - Add README and Templates
Issue -
State: closed - Opened by titaniumbones about 7 years ago
- 2 comments
Labels: doc-sprint
#14 - Sprint prep
Pull Request -
State: closed - Opened by b5 about 7 years ago
- 2 comments
#13 - Should WARC records on the distributed web default to a flat list of hashes, or should we crawl to directories
Issue -
State: open - Opened by b5 about 7 years ago
- 4 comments
Labels: question
#12 - Import & Use WARC & CDXJ packages!
Issue -
State: open - Opened by b5 about 7 years ago
Labels: enhancement
#11 - Heritrix parity
Issue -
State: open - Opened by b5 about 7 years ago
- 1 comment
#10 - Add html test data & example test server
Issue -
State: open - Opened by b5 about 7 years ago
#9 - Error loading config
Issue -
State: open - Opened by KrzysztofMadejski over 7 years ago
- 2 comments
Labels: bug
#8 - Dependency management
Issue -
State: open - Opened by KrzysztofMadejski over 7 years ago
#7 - Good README needed
Issue -
State: open - Opened by KrzysztofMadejski over 7 years ago
- 7 comments
Labels: documentation, ready
#6 - Added link to README for archiving tool comparison research.
Pull Request -
State: closed - Opened by patcon over 7 years ago
#5 - begin querying for & handling data.json requests
Issue -
State: open - Opened by b5 over 7 years ago
Labels: enhancement
#4 - Automatic Collection Generation
Issue -
State: open - Opened by b5 over 7 years ago
Labels: enhancement
#3 - Redis-Backed que
Issue -
State: open - Opened by b5 over 7 years ago
Labels: enhancement
#2 - Sentry isn't discovering content fast enough
Issue -
State: closed - Opened by b5 over 7 years ago
- 1 comment
Labels: bug
#1 - Second Crawler for suspected content
Issue -
State: closed - Opened by b5 over 7 years ago