Hi all,

I am now finished with my test installation - successfully. I did provide what 
I adapted in two pull requests for kibble-1 (pull/131) and kibble-scanners 
(pull/10).

Actually what I found is, that the git scanner is working quite well. I may ask 
therefore the comdev people again, why gitbox repos are not scanned yet, there 
might be a reason behind...

Though, I might do further testing by checking git repos with git modules 
inside..

At this point, I think kibble-1 is still in "good enough" shape to get an 
update and work on with a newer python version 3.13.0 and updated libraries as 
well.

In kibble-scanners there a lot more dependencies in the background for git 
scanner (clock, perl in particular and some more), but I could install all of 
them..

If you have any questions regarding the pull requests, please do not hesitate 
to ask. Apparently I just started with kibble two weeks ago ..

I am not a day-to-day elasticsearch user, but I think the basic configuration 
needed for EL8 is correctly done. Further fine tuning might be necessary though 
..

Have fun and best regards, 

Georg

On 2024/11/06 15:55:36 "Kallidis, Georg" wrote:
> Hi all,
> 
> ok, sorry for any disturbance. I think I found the error for not setting the 
> cookie 
> 
> In handle.py
> 
> session.headers.append(bucket)
> 
> and later
> 
> start_response("200 Okay", (session.headers) )
> 
> and bucket is not a valid response header (key=value) format, which causes 
> that session.headers in the PUT request is not set at all .
> 
> After this the cookie setting was successful.
> 
> Best regards, Georg
> 
> -----Ursprüngliche Nachricht-----
> Von: Georg Kallidis <g...@apache.org> 
> Gesendet: Mittwoch, 6. November 2024 15:57
> An: dev@kibble.apache.org
> Betreff: Re: [DISCUSSION]: What is the future for Kibble?
> 
> Hi all,
> 
> I did not know about this project about a couple of days, when I first 
> created this issue INFRA-26246. 
> 
> I still do not know much more, but started to check and test install the 
> kibble-1 project (I checked first kibble, but this seems to be just a future 
> project or a wrapper -?).
> 
> Up to now I got to the point that I could generate the initial indexes with 
> setup,  create an account and could start the server(s) (elasticsearch, httpd 
> with kibble-1/ui and waitress proxy). 
> 
> Logging in using http://localhost a session is created, but the set-cookie is 
> not successfull - may be due to localhost and samesite issues? I might try it 
> later with an https scenario...
> 
> My final target would be to scan a gitbox repo and get commits from there ..
> 
> As this is still work in progress I might later share my changes either as a 
> PR or just put it into a branch as I use python 3.13.0 and el 8.15.3.
> 
> That is, I may find more time in an irregular way to get this done, 
> finalizing test installation ..
> 
> Thanks so far for any help!
> 
> Best regards, 
> 
> Georg
> 
> -------
> Georg Kallidis / ASF Projects Turbine, Db
> 
> On 2024/09/04 01:54:25 Sharan F wrote:
> > Hi All
> > 
> > Over the last year or two we’ve been trying to kick off some community 
> > activity to develop the project. Unfortunately so far we haven’t been 
> > able to do that successfully.
> > 
> > Recently my own personal circumstances have changed meaning that I no 
> > longer have the time to spend on the project - so I have a question to 
> > whole community - Are there people in the community that would like to 
> > take a more active role in the project?
> > 
> > If so then please speak up as I think this is becoming a critical time 
> > for the project. My thoughts are that without any active 
> > contributions, project vision or general progress then we need to consider 
> > retiring the project.
> > It’s a sad thought since Kibble provides some great insights for all 
> > the ASF projects that could be developed even further.
> > 
> > Happy to get any feedback, comments, thoughts (though hopefully some 
> > responses from potential active contributors :-) would be great!
> > 
> > Thanks
> > Sharan
> > 
> 

Reply via email to