Need to handle error better on Analytics plugin errors
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
Research direction
Start by comparing the missing report table and unreadable UI error in the screenshots with the corresponding error in the logs. Trace how Analytics plugin report errors reach the UI; done means the UI presents a readable, appropriate error when the report table is missing.
Written by the indexing model from the issue text.
Description
Kaui : 3.0.24-6144625
analytics-plugin-8.1.4-SNAPSHOT
Please refer to the below screenshots. The table for the report is missing and it is rightly caught by the logs. But the UI shows unreadable error. Appropriate error should be shown.
- Dominant language
- Java
- Stars
- 13
- Forks
- 33
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
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 killbill/killbill-analytics-plugin
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Automation analysisOpen
Difficulty 5/5 Over a week Newbie friendliness 20/100
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
killbill/killbill-analytics-plugin#163 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
killbill/killbill-analytics-plugin#152 · 3 comments ·
All issues in killbill/killbill-analytics-plugin
Similar issues
-
component/data-layer
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
-
RegistryExceptionHandler uses self-referencing basePackageClasses instead of a controller classOpenbug finsim-registry good-first-issue
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
? - Needs Triage bug
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
NVIDIA/cudf-spark#17063 ·
Maintainers usually reply within 2 days
-
status:pending type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100