EYLogger#post_process fails if called in the top-level namespace
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 35/100
Research direction
Start by reviewing EYLogger#post_process and the linked commit 878708bec3ccb0c7779da8e96fc5fd882d51924c. Reproduce the failure when it is called from the top-level namespace, then compare the behavior with the linked fix. Done means the top-level call no longer fails and the existing relevant checks still pass.
Written by the indexing model from the issue text.
Description
- Dominant language
- Ruby
- Stars
- 115
- Forks
- 55
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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 engineyard/eycap
-
test abc Open
Difficulty 5/5 Over a week Newbie friendliness 1/100
engineyard/eycap#48 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
engineyard/eycap#8 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
engineyard/eycap#5 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
engineyard/eycap#2 · 3 comments ·
All issues in engineyard/eycap
Similar issues
-
user-reported
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Kong/developer.konghq.com#7316 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
TheOdinProject/curriculum#31408 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
bensheldon/good_job#1816 · 5 comments ·