# 9.6.1 developer: org.sonar.ce.task.projectanalysis.component.VisitException

**URL:** <https://community.sonarsource.com/t/9-6-1-developer-org-sonar-ce-task-projectanalysis-component-visitexception/73275>\
**Category:** SonarQube Server / Community Build\
**Created:** [September 20, 2022, 5:23pm UTC](https://community.sonarsource.com/t/9-6-1-developer-org-sonar-ce-task-projectanalysis-component-visitexception/73275 "2022-09-20T17:23:18Z")\
**Posts on this page:** 1\
**Showing post:** 17

<div class="post-metadata">

**Author:** ![dmeneses](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/dmeneses/32/2933_2.png) [@dmeneses](https://community.sonarsource.com/u/dmeneses)\
**Post date:** [November 17, 2022, 10:35am UTC](https://community.sonarsource.com/t/9-6-1-developer-org-sonar-ce-task-projectanalysis-component-visitexception/73275/17 "2022-11-17T10:35:58Z")

</div>

That’s part of the problem. The scanner should be able to collect blame for all lines.  
Is it possible that there are uncommitted changes to those files when the scanner runs?

---

_[View the full topic](https://community.sonarsource.com/t/9-6-1-developer-org-sonar-ce-task-projectanalysis-component-visitexception/73275)._