-
Notifications
You must be signed in to change notification settings - Fork 183
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
[cocom][colic] empty enriched indexes #598
Comments
Hi @FixItNowPlease Do you have any log related to the enrichment process (not the studies one)? Before
Is there any error between these logs related to |
Yes, a lot of
For several repos (3 from 57 test asset) i have this errors:
but for other repos - no errors at all. |
Any way to get it filled? :). Really no idea what's going wrong :(. |
This is only thing keeping me from rollout GL over the all my 1000+ repos :). If anybody could help - will be very appreciated! |
I hope I can have a look a it next week. |
Will be appreciated for any idea - where the reason of empty indexes could be. |
any ideas? :) |
Sorry for the late reply, I can create the
I'm using this version: |
is this only that i need to add to use
|
I think what we need it's the full list described in here: https://github.com/chaoss/grimoirelab-graal/#how-to-install-and-create-the-executables |
So... I have on my
Im using |
if there is an doc about gitlab setup for grimoirelab, any specific features - will be very appreciated to pointed on. |
Hi @GrayStranger, Is that gitlab repository public to your intranet? Does it require user and password to access the repo? Do the git indices contain any data? PD: Sorry for our late response. Most of us are on vacation, so it's hard to be active here. |
Thanks for the answer!
Below the data for one repository with same backend format and creds for git/cocom/colic sections of projects.json
|
That's weird. The difficult part is to get the raw indices. There must be some kind of error of exception we aren't seeing. Would you mind to set the platform to the debug mode and paste here the logs you get? To do it, you have to set the
Also, to reduce the noise and make the process faster, you should activate
|
here it is:
|
Could you run this query in
|
this request response with only git url:
this request response with git url with creds inside returns with full of data, too much sensitive info inside so - sorry i can't put it here :). I think the key of problem:
full format with creds inside origin stored in index, and default request to raw index with no creds within repo url - returns nothing. Am i right? |
bug or feature? :) |
Yes, that means |
but if i remove creds - it is unable to get raw data to
so for now it is only works for public repos? Because in case of |
If you remove the creds in For now, it only works for public repos |
the way to fix - modify one request within enrichment logic (to use backend format of repo entities) ? or it is more complex issue? |
The way to fix this is to anonymize the fields with credentials in the raw index so no credentials will be stored in the indexes, like https://github.com/chaoss/grimoirelab-elk/blob/master/grimoire_elk/raw/git.py#L75 Cocom and colic use https://github.com/chaoss/grimoirelab-elk/blob/master/grimoire_elk/raw/graal.py |
im using docker-compose to run grimoirelab and could fix it in mordred container, but would this fix be included in nearest release? |
If your code works, could you please create a PR with the fix? |
Yes, its works. I'll create PR tomorrow. Thanks for help! |
update: this solution only works if @sduenas could you please review connected PR to let the fix in. Thanks! |
Fixed at chaoss/grimoirelab-elk#1114 |
Hello, All
I can't get
cocom
andcolic
indexes filled.... no idea which way digging, but for now result is:and the same for
colic
I had already tried delete indexes to let sirmordred re-create it - the same result.
cloc
andfossology
builded inside the container with mordred and there are no related errors in log.versions of all apps - from the last GrimoireLab 0.10.0 release.
HelpPlease :).
The text was updated successfully, but these errors were encountered: