ga4gh / ga4gh/htsget-refserver
Reference server problem?
- Dominant language
- Go
- Stars
- 12
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
I am getting 502 errors now from the reference server at https://htsget.ga4gh.org/. This just started happening sometime on Dec 28, causing igv.js htsget unit tests to fail. Example in screenshot, but any request to https://htsget.ga4gh.org/ will return a "502 Bad Gateway" at the moment.
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no repository file or test; start by reproducing the 502 response from https://htsget.ga4gh.org/ and reviewing the reference server entry points. Check the failing igv.js htsget unit tests for the expected endpoint behavior. Done means the reference server responds successfully and those tests no longer fail.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100