rgcouto commented on issue #7091:
URL:
https://github.com/apache/incubator-devlake/issues/7091#issuecomment-2983759042
> Hey everyone!
>
> I'm experiencing a similar issue with the SonarCloud integration. I've
successfully added the SonarCloud connection, but I'm encountering errors when
trying to retrieve data from some specific repositories.
>
> My setup:
>
> * Using SonarCloud (not self-hosted SonarQube)
> * Multiple repositories configured in SonarCloud
> * DevLake version: v0.21.0-beta6 (same as reported in the issue)
>
> Symptoms:
>
> * The connection test passes successfully
> * When collecting data, I get consistent 404 errors for specific
repositories
>
> Here's an excerpt of the error log I'm seeing:
>
> > subtask CollectAdditionalFilemetrics ended unexpectedly Wraps: (2) Error
waiting
> > for async Collector execution Wraps: (3) | combined messages: | { | Retry
> > exceeded 3 times calling measures/component_tree. The last error was:
Http
> > DoAsync error calling [method:GET path:measures/component_tree query:map[
> > component:[myorg_web-api] metricKeys:[duplicated_lines_
> > density,duplicated_blocks,duplicated_lines, duplicated_files, complexity,
> > cognitive_complexity, effort_to_reach_maintainability_rating_a, lines]
p:[10] ps
> > :[100] qualifiers:[FIL]]]. Response: {"errors":[{"msg":"Project
doesn\u0027t
> > exist"}]} (404)
>
> The key issue appears to be that DevLake is trying to access a project
with component ID `myorg_web-api` (I've anonymized the ID), but SonarCloud is
responding with "Project doesn't exist" (404).
>
> This project exists in my SonarCloud organization, and I can access it
through the SonarCloud UI. However, DevLake consistently fails with the same
error when trying to collect metrics for this repository. I've tried to call
the `measures/component_tree` endpoint manually and I've noticed this is only
happening in two repositories so far on my organization.
>
> Has anyone else encountered similar problems with certain repositories in
SonarCloud? Any suggestions for troubleshooting would be greatly appreciated.
>
> Thanks for your help!
I've eventually found out that the problem was related to the lack of
"Browser Project" permissions on the Sonar user rather than a problem with the
DevLake integration.
Nothing to see here, then 😄
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...@devlake.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
