yugabyte/yugabyte-db

[DocDB] Stack traces shown on check failures are unreadable

Open

#17,814 opened on Jun 16, 2023

View on GitHub
 (0 comments) (0 reactions) (1 assignee)C (1,003 forks)batch import
area/docdbgood first issuekind/enhancementpriority/medium

Repository metrics

Stars
 (8,229 stars)
PR merge metrics
 (Avg merge 17d 21h) (92 merged PRs in 30d)

Description

Jira Link: DB-6904

Description

Need better formatting: https://gist.githubusercontent.com/mbautin/4346817e5d7c2e0685403a9fa9d2c0cf/raw

Warning: Please confirm that this issue does not contain any sensitive information

  • I confirm this issue does not contain any sensitive information.

Contributor guide

Research direction
Review the linked gist to understand the current stack trace formatting and identify improvements for readability, such as adding line breaks, indentation, or color coding.
Tech stack
c
Domain
backenddatabase
Issue type
Documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Needs investigation
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60