graphite-web error in fetch
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 15/100
Research direction
Start by reproducing the /graphite/render/ failure for the target local.random.diceroll, then read graphite/render/views.py, evaluator.py, datalib.py, and storage.py at the traceback locations. The issue provides no configuration, reproduction steps beyond the traceback, or acceptance criterion, so completion would require identifying the failed fetch and defining a verified fix.
Written by the indexing model from the issue text.
Description
I'm trying to configure graphite-web to read data but I got an exception
Internal Server Error: /graphite/render/
Traceback (most recent call last):
File "/usr/local/lib/python2.7/dist-packages/django/core/handlers/exception.py", line 41, in inner
response = get_response(request)
File "/usr/local/lib/python2.7/dist-packages/django/core/handlers/base.py", line 187, in _get_response
response = self.process_exception_by_middleware(e, request)
File "/usr/local/lib/python2.7/dist-packages/django/core/handlers/base.py", line 185, in _get_response
response = wrapped_callback(request, *callback_args, **callback_kwargs)
File "/opt/graphite/webapp/graphite/render/views.py", line 121, in renderView
data.extend(evaluateTarget(requestContext, targets))
File "/opt/graphite/webapp/graphite/render/evaluator.py", line 14, in evaluateTarget
prefetchData(requestContext, pathExpressions)
File "/opt/graphite/webapp/graphite/render/datalib.py", line 255, in prefetchData
for result in STORE.fetch(pathExpressions, startTime, endTime, now, requestContext):
File "/opt/graphite/webapp/graphite/storage.py", line 100, in fetch
raise Exception('All fetches failed for %s' % (str(patterns)))
Exception: All fetches failed for [u'local.random.diceroll']
- Dominant language
- Java
- Stars
- 260
- Forks
- 55
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from ClickHouse/graphouse
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
ClickHouse/graphouse#150 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
ClickHouse/graphouse#140 · 1 comment ·
-
support for pickleOpen
Difficulty 5/5 Over a week Newbie friendliness 30/100
ClickHouse/graphouse#114 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
ClickHouse/graphouse#98 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
ClickHouse/graphouse#77 · 3 comments ·
All issues in ClickHouse/graphouse
Similar issues
-
5.0.x backport enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
spring-cloud/spring-cloud-function#1507 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
open-learning-exchange/myplanet#18484 ·
Maintainers usually reply within 1 day
-
ai-driven-fuzzing bug claude Minor
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
linagora/twake-calendar-side-service#1417 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
line/armeria#7109 · 3 reactions ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
open-feature/java-sdk-contrib#1966 ·
Maintainers usually reply within 1 day