chore: don't log non-error message at error level#3091
Conversation
Up to standards ✅🟢 Issues
|
| Metric | Results |
|---|---|
| Duplication | 0 |
🟢 Coverage 0.00% diff coverage
Metric Results Coverage variation Report missing for 48e40a31 Diff coverage ✅ 0.00% diff coverage Coverage variation details
Coverable lines Covered lines Coverage Common ancestor commit (48e40a3) Report Missing Report Missing Report Missing Head commit (1ffea70) 82477 19111 23.17% Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch:
<coverage of head commit> - <coverage of common ancestor commit>Diff coverage details
Coverable lines Covered lines Diff coverage Pull request (#3091) 6 0 0.00% Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified:
<covered lines added or modified>/<coverable lines added or modified> * 100%1 Codacy didn't receive coverage data for the commit, or there was an error processing the received data. Check your integration for errors and validate that your coverage setup is correct.
NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.
@fschade Not without changes to the What is your concern? Are you thinking about wrapper errors here? Then I guess we could leverage |
Yes, exactly, I just didn't want us to overlook it. |
When walking the tree for creating the search index, ignore "not found" errors. Search indexing happens asynchronously so the underlying space, file or folder might just not exist anymore when the indexing starts.
53ed23d to
1ffea70
Compare
|
@fschade PTAL |
3 participants
When walking the tree for creating the search index, ignore "not found" errors. Search indexing happens asynchronously so the underlying space, file or folder might just not exist anymore when the indexing starts.