Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CNES Report stuck on Loading Screen #411

Open
cliobrando opened this issue Aug 17, 2024 · 4 comments
Open

CNES Report stuck on Loading Screen #411

cliobrando opened this issue Aug 17, 2024 · 4 comments
Labels
bug Something isn't working

Comments

@cliobrando
Copy link

After analyzing some projects, the CNES window stops responding and the message "Loading..." appears.

If I restart the instance, the problem continues, it has happened to me before and I was able to solve it by restoring a previous database backup.
I can use the tool from the command line without problems.

In the browser's dev tools I see these messages:
net::ERR_BLOCKED_BY_RESPONSE.NotSameOriginAfterDefaultedToSameOriginByCoep 200 (OK)
/api/user_tokens/generate 400 (Bad Request)

The last message that appeared in the cnesreport-0.log was this one:

INFO: Character decoding failed. Parameter [branch] with value [%] has been ignored. Note that the name and value quoted here may be corrupted due to the failed decoding. Use debug level logging to see the original, non-corrupted values.
Note: further occurrences of Parameter errors will be logged at DEBUG level.

OS: Ubuntu 22.04
Sonarqube: 10.6
CNES Report: 5.0.0

Captures:
image

@cliobrando cliobrando added the bug Something isn't working label Aug 17, 2024
@Topin2001
Copy link
Contributor

Hello,
In order to look into your issue, can you provide me the network output of the 'f12' page when you're loading the report page please ?

@cliobrando
Copy link
Author

I restored the database to get it working again, so it's working now, I'll try to replicate the error.

@mike8161990
Copy link

mike8161990 commented Sep 24, 2024

I'm seeing this behavior too, but I've only ever noticed it from requests made during the evening hours. I suspect this has something to do with my SonarQube server running in UTC and my browser client running in Pacific Time.

It looks like a POST is being sent to /api/user_tokens/generate with form data that looks like: name=cnes-report&expirationDate=2024-09-24

Then the API responds with: msg: "The minimum value for parameter expirationDate is 2024-09-25."

Edit: I confirmed that updating my SonarQube docker container to run with environment variable TZ=America/Los_Angeles resolved this issue for me.

@cliobrando
Copy link
Author

cliobrando commented Nov 16, 2024

It's happening again:
(I can use the cmd line app just fine)
image
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants