Week 7 for me is a mid-term week as well as a pre-release week, so this blog probably won't be as long.
Dealing with ES Errors for createError
My PR last week on Satellite, for refactoring our exported createError to deal with ElasticSearch errors, was merged this week. Of course, it was only after a few reviews and fix ups. I'm continuing to relearn small things like remembering to name files in lower case, because not all filesystems are case sensitive.
Update to ElasticSearch 8.0?
This week, I tried to see what would've happened if we updated to ES 8.0. I hadn't initially planned to tackle this so soon, mostly cause I had mid-terms and originally, the possible Docker-related problems made this issue less appealing. But I was lucky that Josue, one of our alumni, poked me on Slack about it. Through his help, I was able to get Telescope running in dev mode with ES 8.0. Unfortunately, even though ES 8.0 seemed like it worked fine, ElasticSearch-Mock doesn't support ES 8.0 yet. If we updated now, we'd have to rip out the tests that took us weeks to get in, and we'd be moving forward without tests for a while.
Getting Satellite Updates Semi-automatically
I've already mentioned this issue last week. This week, I managed to get a hold of Duke, our resident Renovate bot guru (just, one of the many titles that he has). He directed me to a possible solution, by changing to rangeStrategy="bump" for Satellite in the bot's configs. The PR was a quick fix, and has been merged. Hopefully, next time Satellite has an update, Renovate will be able to detect it, and we can just get the bot to create an update PR, instead of running the code ourselves.
Parser Tests
Tue had gotten his Parser service PR merged, and is now writing tests on it. I figured I'd try help out since ElasticSearch is used in this service. I've created a PR to his PR, with replacing some (actually only one) of the tests with using ES-mock. But, the Parser service is huge, with many tests involved. So, currently this is an ongoing project.
The agenda for next week
These are the open issues currently assigned to me. It might look like a lot, but I'm sure its not as daunting as it seems. Some of the issues I've already mentioned above; Some, I won't be working alone, and would have help while learning to tackle it; Some, I'm not sure if I can proceed just quite yet.
Overall, next week would be interesting, but, my priority would be getting the autocomplete in. It is an issue that has surprisingly been open for two years, so hopefully, it can get closed soon.
Conclusion
It was not exactly an OSD focused week for me, but I'm glad I got some coding in. Hopefully next week will be very fruitful.
On a final note, my HacktoberFest t-shirt (and many stickers) has finally arrived, yay! I wasn't blogging on dev.to back then, and I realized I missed the date to claim the badge on dev.to. Oh well, I'm happy the shirt arrived at least.
Top comments (0)