Outreachy Internship Week #11 #12

So this week ended well, I was stuck with some minor bugs for quite some time. After discussion and pair programming with my mentor those were very tiny mistakes that caused huge problems. However after finishing resolving that and me thinking “Oh great now I can move on” the next day I got some odd error!

I am proud to say that my project involved a lot of code but a lot more debugging! Getting stuck is very common and I learnt that is one of the aspect of programming. Before I thought it was all about, getting a project to do. Flawlessly coding it and it works! Not hours of debugging. Eventually, when you try to add a new feature into a huge code base and the major tool you are using is new to you. This stuck – unstuck cycle gets pretty common.

If you followed my previous posts, I have to tell you that the code  I showed back then is totally changed. The same with how it all looks like.

On Saturday I decided to do some work. There are few weeks left! Actually less than 2 weeks so it is time to accelerate.

I fixed all the pyflake errors but I now seem to get a “cucumber” error. I didn’t install cucumber testing tool, but I did do rebase and fetched the current changes from airmozilla master. Which leads me to think that, that is what cause the issue.

Now I am doing a type article + code session, to resolve the problem live.

>> ImportError: No module named celery

My solution was to install Celery: pip install celery

THAT happened to NOT be the solution because as soon as I installed that, I got…

>>ImportError djcelery: No module named djcelery

My solution to that was to install django-celery: pip install django-celery

Now my tests run but come out failed. Did I say it was working the day before Saturday?

The most interesting thing of all is, things were working well a day before then I turned off the laptop and the test were not running the next day.

Isn’t that odd?

Well, it’s time to get off and try to resolve this so I can move on with writing tests.


Brief Progress Overview – Week #9 #10

This week i’ll give another brief overview. It is getting more and more busy which makes long blog posts pretty challenging,

at least till the internship starts getting towards a successful end. I really hope things go as well as I want them to, in the next weeks.


What have you accomplished this week (list specific items accomplished)?


– Went back to basics. Stopped working on what I was working and instead tried to make it work in plain python.

– Things seem to be functioning well in the plain python file.

What issues or roadblocks have you encountered this week?
– I have been having some errors while trying to run my simple unit test

–  Trying to get the most relevant posts appear higher.

Have they been resolved, and if so, how?

– The unit test errors which was there last week is on its way to being resolved.  In the next week or so.

– The most relevant post issue seems to be fixed, but needs further testing. It was resolved by implementing  a negative boost in elastic search more like this query.

Do any of the issues or roadblocks still exist and what steps have been
taken to resolve them?

– Yes I need to fix some bugs that lead to wrong related results i.e. use analyzer

I have discuss it with my mentor and  so far we decided I first get the unit test working, then

I work on fixing the bulk indexing and lastly we work on the analyzers before we move on

to anything additional that might come up.
How does your progress compare to your project schedule?

A bit behind of where I want to be I think. It is time to speed up kind of.