apple/foundationdb

Remove the double logging for open trace file failure from the TraceEvent cache based implementation

Open

#2,739 opened on Feb 25, 2020

View on GitHubContributor guide
 (4 comments) (0 reactions) (0 assignees)C++ (1,266 forks)batch import
good first issue

Repository metrics

Stars
 (13,912 stars)
PR merge metrics
 (PR metrics pending)

Description

With the new issue reporting mechanism in place (PR #2605), the old TraceEvent cache based implementation specifically for trace file open failure can be removed.

Contributor guide

Research direction
Locate the double logging of trace file open failure in the TraceEvent cache based implementation and remove it, ensuring the logging is handled by the new issue reporting mechanism from PR #2605. Verify that tests pass.
Tech stack
cpp
Domain
databasedistributed systems
Issue type
Refactor
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.
1-3 hours
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.
Clear
Prerequisites
C++FoundationDB
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60