Telescope 3.0 : Alpha and Release

-
First, sorry for the lack of updates. I know I'm missing a lot of details from the previous Telescope post. But to sum it up, lots of new features and fixes were shipped throughout 2.8 and 2.9 but since 3.0 alpha which was released 2 weeks ago, we've had to shift our priorities towards the mainline features that were to be shipped in the 3.0 major release which we're shipping this week.

Supabase Progress

So we've finally got our own Supabase client running on staging, and we're planning to deploy it to production for 3.0 So that's really exciting. 

Jerry has been lending a hand by coming up with more tables we can use for more info (i.e. github_data) Not only that but he's written a script to backup our Supabase/Postgres data in the events of a failure, that's really neat! This process involves starting a temporary container for the purpose of running the backup script.

We've been migrating things like accounts and feeds to the Supabase tables. But when we want to alter these tables, like say add row level security, there's a few ways you could do it. First, you could just go to the supabase studio and insert it manually with the GUI they've built. Or we could use Prisma, an ORM tool for nodeJS that Duc had suggested. This way, we generate an sql file with the prisma script, (which includes a name and date record to keep a history of the migrations) edit in all your sql statements (ALTER, INSERT, etc.), then push it to upstream for it to be ran in prod/staging.

So it's exciting to see Supabase really coming to its own in Telescope, there's still lots of potential for it to grow so I can't wait to see where it goes from here.

Status Service

So for alpha 2 weeks ago, I worked on a few issues regarding the status service. They were pretty minor, but I wanted to do what I can in contributing to the alpha and major release so I fixed an issue that's been hanging around in our status service for a while. We have a contributor card that shows a github name and avatar for the last Telescope commit. The avatar image is running into some sort of CORS error and doesn't load.

After some time debugging, I found out all it took was to add the "crossorigin=anonymous" attribute in the img tag. And just like that the contributor card shows the avatar! Another bug down for 3.0 :) Right now, I think we just need to worry about the rate limit for the API, since that will affect the contributor and commit cards for all its info.

Major Release 3.0

It's already the end of the semester and we're going to release 3.0. It's been a great experience working with telescope and I'll sum it up in a different blog post. But that's the progress so far and we've just got one more release to deploy.

Thanks for reading :)

Comments

Post a Comment

Popular posts from this blog

HacktoberFest Entry No.2

-
Image
So around last week I found a great github repo of a chrome extension that previews contents of a webpage when you hover over a link. I stumbled upon it after a suggestion from my professor about taking a look at chrome extensions for a possible repo to contribute to. I'm glad I did because this was a chrome extension that was interesting, seemed practical and had a maintainer who was keen on receiving contributions to better his program. The extension is called Survol First I had to install it and test it out first, can't just contribute to a repo meaninglessly just to force a pr. I tested the extension and liked the functionality, it was useful and is well designed. Makes it all the more exciting for me to try and contribute to it. So I read the docs and learned how the extension worked. It uses a javascript file to inject html elements through the dom and uses mousemove event to detect anchor links to request information of a page, and positions and fills the div with conten...
Read more

Lab 1 : Our First Open Source Contributions

-
So for Lab 1 our tasks were fairly simple. Find a partner to review a repo on and make contributions, no matter the scale, to their code. Be it a suggestion for their code, reporting an issue, or even fixing up small details in their readme. So through slack I partnered up with one of my coursemates  Niaz Much like me, he wrote his code in nodejs, so it was perfect since I can go through his code easier through my understanding of node. His code, though written in the same language, differed from mine a lot. For one, he didn't use yargs so he had to process the arguments manually, and secondly he didn't use fetch and opted for a module called linkinator. No problem, in fact it's an opportunity for me to understand the logic and components that he used. I forked a copy of the repo, cloned it and tested it out for myself. The code worked perfectly as intended and processed urls well. Functionally, I couldn't find find anything in the code I could identify as a flaw or imp...
Read more

Hack.... vemberfest.. PR No. 3

-
Image
OK so this is pretty long overdue (sorry Prof!) And I still have one more pull request to go and that's on me yes. BUT, this week I spent working (or should I say learning) on our course's aggregated blog website which coincidentally, our prof is making us work on this week for the lab, so I guess I got a good head start going on.  So I took on an issue that seemed pretty straight forward in the repo. It was to change the functionality of the search bar when filtered by author. Seemed pretty straightforward enough, so I went ahead, forked the repo and cloned it on my computer. Now the reading begins, the lengthy process of coding. And the fact that this was a whole website coupled with different technologies that I'm not familiar with only made it waaayyy longer, which maybe is a sign that I should have started working on this much much earlier. But that's what happens when your time management skills is hot garbage. Anyways, I spent the next few days learning about eac...
Read more