DEV Community: Amazing

3.0 Alpha #2: Core feature for mobile app

Amazing — Sat, 09 Apr 2022 21:37:13 +0000

Finally, thank you @dukemanh for helping me out to pull this feature off for 3.0 alpha.

Fetching posts

This is my first time, I have a wonderful practice fetching data from an api or a services. I guess the only reason I want to take lead on our mobile app to also learn how to do thing from the ground up as well. Working on our web has been a different thing where you will learn and integrate things into an already existed system. Whereas with our mobile app I got a chance to learn thing from scratch. Lucky for me I did not have to do researching by myself. For this issue, I spend a lot of time around @dukemanh and be able to witness how he implement things and he did give me a really good suggestion on my working flow and how I can tackle the problem and things I can improve on base on his knowledge. We take a look at our Post.tsx and Timeline.tsx where ppls who had worked on this in previous semesters have well implemented displaing posts for our web. I learn how to use swr and SWRInfinite for pagination as well as config the fetcher at the top level to show how would swr behave with the data.

Using FlatList instead of ScrollView

While we was working on displaying the posts. We having a hard time for our ScollView to scroll properly even though we were doing what the react native doc suggest and changing many styles using flex and flexGrow to indentify the height of the screen for the ScrollView to scroll. When I read the doc, they also mention about FlatList which have lazy loading which help to improve performance of the app. It will only load the component when you scroll down more and delete the items above for efficient use of memory space and the usage is just simple.Our fetched object from the post service return a nested object which ask us to use map method twice on it. With Flatlist we only need to map it once

<FlatList
        data={pages}
        renderItem={renderPost}
        keyExtractor={(item, index) => index.toString()}
      />

Styling the component

Then we having a hard time after the post display. They just look ugly and plain. Since react native don't have normal html element so we can not do what our telescope-post-content.css did. Luckily Duke spot our that the react-native-render-html have let us pass a prop to styles these element using tagsStyles. Right now I still working on changing the css to work perfectly for the mobile version but I'm glad that we pull it off and be able to learn how he work on the issues have been a good learning opportunity for me.

Duke has mentioned what we should have did differently and what our prof did try to tell us from the beggining that it would be perfect for us to move our workflow from working up from the easiest thing to working from the core functionality of the app first so everything we work from there will be centralize around the core functionality. Like what I experience is that our Banner make it hard for us to do the scrolling and also to run the application where we should have implement loading the posts before implement the Banner

My PR

3.0 Alpha #1: Transforming to Supabase

Amazing — Sat, 09 Apr 2022 20:01:45 +0000

Here is my update on my way working to finish the alpha version of the Telescope mobile app.

Looking at the doc

Supabase is amazing in doc. I have developed a good habit of taking a look at the doc before searching for any tutorial. And the doc provide details how we can start using Supabase with different framework and some of them are very popular such as: React, Angular, etc.... The doc show you how to use supabase for authentication which is a classic, popular use case when it come to mind when talking about integrate a server into your project. Mine use case this time is much more simpler which is to contain all the quotes from student-quotes.js so as we can share and avoid duplicate information between our wep app and our mobile app.

Start working on the project

Since my use case is much more simpler I might not need to have to use all of the configuration option when creating the Supabase client. This is when blogging become amazing. During 60% of the meeting our prof always try to press how important writing blog and be able to reach out with other developers. When working on the issue, I come a across a wonderful article where he tackle all the basic incompatible between react-native and supabase.

"Blog about it"

After reading such an amazing article. This sentence from my prof keep running through in my mind. Your struggle might become a treasure for whoever come after and be able to read about it. So here are some highlighted issues that I have been able to tackle

Working with .env for the very first time

Yes, this is my first time ever working with the .env file and it also a best practice I learn from the telescope web team. Before I did read some guides on how to run Telescope but did not bother dig into it and see what is actually in those files untill I have to do it myself. Like I said, after creating a habit of reading docs, I feel more pleasant to spend time with it than a feel short stackoverflow answer which not gonna last in my mind more than a day after the problem has been solved. After reading the expo doc on how to work with environment variables with expo. I have no hard time implemented it but then it coming to another problem where I would not be able to connect to the client.

Trouble connecting the supabase client in local development

For this matter, I have been able to reach out the Kelvin through Linkedin to see if he have experienced the same thing but it seem he not be able to spot it out. Then after talking with peoples of the supasbase upstream to see if they have some idea on how I would be able to solve the problem but there is no luck. Then it come to my final option to search for stackoverflow and Duke had sent me a link as he know I was having problem with connecting to supabase. The answer pointing out localhost mean is not pointing to the real machine when interpreted through mobile device so in local development we will change localhost to 10.0.2.2 and finally I had be able to connect to the supabase client.

My PR

My work for 2.8

Amazing — Wed, 16 Mar 2022 01:43:59 +0000

In our 2.8 release, I would be able to contribute 3 quick fix for our project

About page and adding more documentation for react native app

I have been overthinking on how I would fit our currently About page into our mobile app. Then I regconize I should keep the ball rolling by having draft and put in some work so peoples can have more inputs into it. I then reading the doc on how to implement an ScrollView in react-native and learn how to insert line break. Working on using flex for responsive design. I try to implement a back ground image for our ScrollView so it look fancy enough but yet I will still need to look more into this ever since more UX principles need to be follow.

You can check out my current work here:About page

I also having a small PR to add 2 usefull Expo CLI commands which is expo doctor and expo update into our react native doc for the later generation of Telescope when developing our
mobile app.Most of the time when I start working on our mobile app. There has always been dependency related problems. So for react native to trasnlate mobile app writting in react to native, they host the app on a virtual machine which acting like a bridge, then that bridge distribute our app and translate into native language. The virtual machine require up to date or I can say compatible dependency to be able to run smoothly. So running expo doctor will help indentify incompatible dependency and since our renovate-bot did not allow in the mobile subfolder, expo update will get the job done easily.

My doc PR

Fixing Linkyfier

When I use LinkifyHTML to make every hyperlink clickable. We aaccidentally linkify all of the img tag which is not what we want it to behave. When I was wondering on how to fix it our prof have point out the ignore tag in the doc and here is my qucik fix:

article.content = linkifyHtml(article.content, { ignoreTags: ['img'] });

I would have to be more flexible on suing the doc to figure out how to solve many more problems. Got a lot to learn !

This is your Sheriff speaking

Amazing — Wed, 16 Mar 2022 00:45:09 +0000

This week, I'm proud to write about my pleasure experience taking over the Sheriff position for our Telescope project in week 7.

How did I prepare for this

First thing first, being a Sheriff require you to be available most of the time so I decided not to work during the week just to make sure I don't miss out on any important decision, involve in decision making, be available,resourceful and finally giving direction for the team moving forward if any

I'm on duty right after the break week which give me a plenty of time for me to learn and study the state of the project. During break week, I already reach out to people who having big issues or track their progress on Slack. People like Kevan, Francesco or Tim will introduce newly material for the project in this release or Amasia, Diana, Tuee who have taking a lead and got many issues taken by them. I try to track or talk to them to see how thing is going to make sure I got a vision about how our project moving forward.

In the beginning of the week, I jump into our 2.8 milestones and read every single issue closely untill I visualize what need to be done and also keeping the communication bridge going back and forth smootly. Night before the meeting, I staying up and check every single issue again to know which one should be drag out because they might need a little push or inputs to be merged into the project. The morning of the meeting, I do a rehearsal for myself on how I would direct the issue to my colleagues at 5am which is 3 hours away from the meeting. The meeting then went well and I take pride of doing such a decent job to manage the meeting for the first time.

Potential career opening up

After Sheriff week, I'm feeling like I might be fit working as a comunity manager for the project. One week off, giving me more vision on what I want to do with my life. As aninternational student I'm always obssesed with stablize my income and ever since graduate from Fleming and got no luck on finding an intership opportunity right after, I showed 0 motivation when starting to study at Seneca college. During the Sheriff week, for the first time I have a chance to organize and set out my goal and what
would fit better for me coming out from college. I'm now setting my goal to earn a job working as a comunity manager or a react native job.

Messing up like usual, 2 weeks are all it take

I messed up twice during the early of the week, the first one would be after I rebase Cindy work but somehow it stale all the approvals of her PR. I regconized that the change have no conflict with master so instead to wait for the approvals and decide there was no point to waste more time for reviewing the PR so I miss out the rebase proccess and accidentally merge the PR straight into master and polute our project git history. The second time would be when I merge the work from Francesco, I did indeed read Dave comment which ask the maintainers not to rebase the work since we want to keep the git history from Satallite. I got exciting to see a big things that I have been keeping track ever since the break week ready to be merged. I then follow my usual habbit and rebase it which I was ask not to do -_-. Luckily, Duke was there to help revert and merged Francesco PR again into Telescope

This blog post got written week after the release so we did also break production on the release day as well :). I guess our prof start regretting since his breaking production culture made him to work overtime on a Friday night to make it work :). After a while, Duke and Roxane be able to point out that we did not have the same git history base so Github would not be able to figure it out. Then the whole team decide to jump on another call and work untill 10pm (what a day eh ?).

How mature am I with the project moving forward ? I'm now got no lost or fear feeling when jumping into new material or subjects. I accept of the fact being lost and working on how I can solve the problem more. After attending meetings, and reviewing code I regconize that all of us get lost in the beginning and all have to work our way up. Instead of spending time overthinking and getting lost, I move to the second stage faster and doing my research. Maybe untill I pump into another big issue, but now I feel no pressure working on new materials which I have never work on before. Also I regconized how my coleagues master new materials in the 2 weeks time span for example Kevan who has been working on our Portainer set up during the break week and being able to pull it off for 2.8. Diana be able to work on some animation for our About page using all material and some researching, many more great work that I could not list it all here during my time being 2.8 Sheriff.

I would try to work on our React native app and hopefully we will be able to hang around and using Telescope on our mobile when we finish this course !

2.7 : Getting better

Amazing — Thu, 17 Feb 2022 18:41:50 +0000

Stop build header and the build log stutter

When I was working on the dashboard of the project, I regconize that our dashboard sending too many request in such a short time and when using it and it make the UI stutterbut at that time I did not practice the habbit to filling issue yet so when I was fixing the loading animation in the build header I just kind to ignored it. When our proffessor bring up the issue, I was happy to tackle the issue. At first what I did was to check the interval and see how frequently our build information got requested and rendered. It is 5 seconds beetween each time we send the request to the autodeployment server. I regconize our build on master usually took average from 3-5 minutes to finish. So I went and made a dummy change which is to extend the interval beetween each call to 1 minute. It work but after revise the issue description it is not that optimal yet. My next move would be finding a way to extract the text from the xterm terminal and compare with the upcoming data that about to be written in the terminal. I kinda form a routine where I force myself to look at the docs first instead of straight up searching things on stackoverflow. I spent 2 days on Xterm docs trying most of the available methods and properties provided from Xterm. The doc was not that good since it did not give any usage. After trying onData, onRender, terminal.selectAll(), etc,... . I then search for stackoverflow and regconize that did not provide a way to retrieve the content of the terminal with the public API, I also would think compare such a long string of text will be time consuming and not that efficient. I have to change my way on how I think about it. I decide to tackle the build which contain sha which is unique to each build. But I have to use the global scope variable which is not a good practice. I decided to pushed and make a PR to update with the team and also learn how they would solve it different than what I did.

In general I agree with you: fewer variables, reduce their scope. But this is hard to avoid completely.

I will say we try to avoid it as much a possible but it not that bad to use after all if we can not avoid it.

Indicate better build information in build-header

For me this PR is not that bad and not exploring much since I already got some experience working on the dashboard so I just need to search for bootstrap docs and read about truncate text using eslipsis. You can checkout my PR

Review and practice a habbit to file issue

So far, I being less active on filling issue on the project which I should since it is a good things cause shipping software is an endless job. Next version of the software will hopefully be better than the previous version and we always try to make the software more complete for the users. So I file 2 issues on the Telescope about bugs and enhancement needed it in the dashboard where the dashboard not showing up build in production which lead to another disscussion where we should use supabase to keep our dashboard being more consistent. Finally, I start to create more "trouble" for the whole team to tackle :)).

I also got 3 pr that needed to coming up but Jerry was one step ahead. So I help Andre to review the PR. I just want to talk a bit more a bout how I tackle this since I'm feeling like I'm getting more comfortable working and tackle new issue. Andrew suggest us to look at the utils\toast.js and after take a look at it I'm using search to find it usage accross the project and found enough information for myself to tackle the problem.

For 2.8, I have been reading and learning a bit about docker and superbase and hope to jump on any 5 min fix issues to learn more about it by doing

Week 4: Starting with React Native

Amazing — Mon, 07 Feb 2022 18:26:15 +0000

PR got merged !

My PR merged to master. Yay !. Look back on the changed that I made,I'm adding 4 lines of code but learning ton of things.First I kind of getting used to using pnpm when I have toinstall and remove packages for testing. I also learn why and how we gonna pin our dependency so as we have a stable deployment of the app everytime, follow my understanding and researching if the package or the project unless they have a security hole that need to be fixed otherwise we want to pin them to have a stable version everytime we deploy our application. Also since I kept installing dependencies and removing and rebasing with the upstream/master. My pnpm-lock.yml file ask me to resolve some of the conflict and after reading and searching in the docs I come through this link as the solution where I just need to delete the pnpm-lock.yaml and reinstall all the dependencies again.

Like I said in week 3 post, I was ask to write a test which I did not feel comfortable since I have less than 3 times writting test ever since. But it quite enjoytable to be honest. I already got the basic concept of jest and have to work on it before so I did not have a hard time refreshing how to implement the test

Get the react native ball rolling

We have some basci UI and the splash screen running for the react native app. For my next goal will be having all the post loaded on the app. I have been doing bit of research and wonder if we gonna use the parser service which is in construction or the react-native-rss-parser

Here is my work for this week
PR-1
PR-2

Week 3 : Testing procedure

Amazing — Tue, 01 Feb 2022 04:44:01 +0000

Yes ! Not only understand the code itself but testing it is a hard challenge as well. As you recalled from my week 2 I thought that 2 of my PR would be easy picker to start contributing to Telescope but no the testing and prove it working is a pain !!!! (By the way no pain no gain !)

Rendering build header animation

This PR the changes to it is quite simple but testing locally is a bit tough.

Firstly we did not know why even though when the build is successfull it still return us code:1 as indicate an error happened during the build process. I did connect with Josue as he get access to the server and he been the one I talked to eveyrtime I need him to trigger a build manually to test out my PR. Ater and 2 hours session we regconize the error related to the -f command which might create a warning and return back the error code in docker. After that Josue just went ahead and create a temporary solution to the problem which send code:0 equal to success build status.

Secondly it really bugging me when I work on the code at different time with Josue and can not always ask him to do it. I did try to make some research base on old PR and asking Andrew who been leading the creation of dashboard during fall semester and found this gem among the closed issue. The code have been changed quite a bit in like 2 weeks span and I did make my update on how to test my PR locally. Before that I have try to point the autodeploymentUrl to our dev api but no luck for me since it telling me that I'm breaking a olicy which is new to me. But after reading the closed issue above I was able to find a hack for it. But yes, that was the first time I know that we would be able to create policy for our project as such.

Fixing wrong build status url

PR.When working on the above issue I regconized there was a mistake on our production where the we requesting wrong Url on production which only need to add a regex like such

`//${window.location.hostname.replace(/(api\.|\.api)/, '')}/deploy${path}`;

Even though it is a quick fix (than the other PR) but I still learn thing such as this is my first time using or logic with regex

Third PR and it still going on

The challenging part of this PR would be where to put the code and how to test it.

At first I was trying out easiest way which choosing the react library to wrap the description section of the Youtube posts. But then I get some advice to make that change ideally in the backend which make me wondering about the difference of it. I then read and standing from the point of view of a post being procceded and changes that affect data should be happened in the back which help to avoid work for the frontend

If you see the picture above when I made a search to look for the post and as this time I could say I got 0 knowledge about the Telescope structure yet so i got consfused on where to put my changes. I remmeber talking with Abdul on Slack on why we having the api and backend at the same time and they seem to be duplicated with each orther. I did reach out to him again and what he gave me was adding my code in api would be a move to make. I then jump in the Posts service and make a dummy change on wrapping the html using linkyfyhtml in the Post object constructor which it work but then I receive a comment on how to change it which we should wrapping the html before we create the post I then make some change in to default function of the api\posts service and got no luck making it to work

I found out that Josue did also work on these files and matain the project for a long time so I did talk to him and now I know that the parser service is still under construction and post service only fetch the data from redis which I need to put my changes in the backend. For some reason my changes did not work at all and I stop at that point where it is just not working. I keep deleting the data and re run the project which is time consuming. Cause you know what ? I'm afraid of debugging but after calming my tilted reaction I regret not debugging it sooner. I put the break point on where it return the type of the post to be a video. I then recognized that all of the video post return article.content as an array and we expect linkyfyHtml to work on a string not an array of object. I then make a change to joint the content since only the first index of the returned array object needed to be process. After applying changes, my code work and I litterally dance on my chair of having the issue move away from my mind. But you know they say never be too excited about shipping software. I come across a gif which kind of related and I want to share it here and might delete it later. I feel so related with this gif.This is totally me after I received some feebacks which I need to make another changes, adding test for my changes before it got approved.

I will keep you guys posted and at the same time I could not stop laughing on the gif :)

What I learned this week

Firstly, if I bring up the 3rd PR up in the public Slack chat for Telescope. The third PR could have move way faster since I took most of the time figuring it myself instead of asking in the chanel where people who have knowledge can bring up disscussion. When talking to people, since they all contribute on different aspect of the project sometime their understanding about the project can be equal or less that what I already know about it. i guess the reason why I not feeling like doing it is because English was not my first language and I feeling like I did not do a good job of explaining things. But to be fair I try to go for this course to break those barrier. And why not doing that since I got a chance to learn with buch of great people who making fun of commits that breaking production.

Secondly, the roller coaster feeling and pressure shipping software is what I'm in this course for. I know that sooner or later this is what I have to face if I made it to the workforce. I said this in the beginning of this course that this course get as hard as you want it to be so I would love to jump on that roller coaster over and over untill I get use to it !

Let's talk next week ^-^

Week 2 : A lot of opportunity ahead

Amazing — Sat, 22 Jan 2022 04:46:09 +0000

We are heading by the end of week 2 with a lot of opportunity to expanding our lovely Telescope project

Things I work on during the week

I have been working on 2 PR during the week PR-2665 where I pick up @yodawgz0 work on idicate the status of the build. My first attempt was to figure it out how the code work after I follow the long conversation between Andrew and @yodacanada on what could have been work on. After I spent time working on refactoring the code we all come to agree that the logic have been implementing in another PR (dev life :)) and we only need to automate loading status using icon from material-icon and delete datetime-calculator.js since I find no usage for it. For this PR we still need to automate a webhook build from Github which I filed an issue-2701, I might need to investigate more since the build data seem not showing up properly on my end even though I had pinged one of the maintainers to trigger a buid manually but we did not see any information related to the build showing up.

The second PR which is quite easy where I only need to wrap the embedded Youtube video preview in an <a> tag

This week I have to say Gitpod really got me. It is way too convenience to work on it even though I was not master it yet. It automate rebuilding container images for me and get everything set up and ready to go. The only things I would need to figure it out on how I can rebuild all the images. What I did was to turn off the workspace and try to access it again which is not optimize at all.

Moving on to 2.6 release

Yesterday on Slack people was having fun of someone breaking production because of their search PR.
So that what people think and act which is possitive for the work. People don't just freak out but instead slowly looking for trouble and fix it. Just like what our prof say in the first meeting. He hope all of us get good at getting lost !

Coming into the next release I hope to contribute on the beggining of the React Native part of our project. People on the group also show many good idea on how to improve it. I would love to help out and also maybe implement a copy to clipboard button for code area in students blog post ! Looking forward to crash production !

OSD700: Maintaining Telescope

Amazing — Sun, 16 Jan 2022 07:01:21 +0000

Thi semester I got a privileged to be one of the maintainer of the Telescope

I'm back

This course in my point of view is like a cool job. "Cool job" in my term paid you for what you love to do and this class marked your work base on what you willing to do and learn. This course get as hard as you willing to push yourself.

My goal for the project

Make the entire app easier for new people to setup, debug, and develop. There's too much secret knowledge and too many manual steps right now.

I would love to work on this part where I want to shred more light and hope to make Telescope easier to navigate

I try to learn React eveyrday as my 2020 goal. Because of that I want to contribute more in the front end of the project. I also have a long story with being a mobile developer. I used to work for a tiny startup and create their app myself using java. I know it is not the same but I'm exciting to start it as we go.

But I want to learn as much as I can, either about cloud, backend as I want to have a decent knowledge to make it to the workforce :)

Release 0.4: Unfinish work

Amazing — Mon, 13 Dec 2021 19:14:07 +0000

Implement ttl to check the expired invalid key

The implementation is quite simple than I thought. First I come to the src/api/posts/src/storage.js and adding a simple change, so when we set an invalid

setInvalidFeed: (id, reason) => {
    const key = createInvalidFeedKey(id);
    const expireAfter = 60 * 60 * 24 * 7; // Expire after 7 days
    return redis.set(key, reason, 'EX', expireAfter);
  },

But the testing would be a bit tricky, as first I just restart all the images and cd into src\backend and run npm start. After talking with Emily I come to my ubuntu and type
sudo docker exec -it redis sh and using redis-cli I would be able to use commands to interact with the redis data. I would search for the invalid key using keys *invalid and I pick out a random key ttl key but the result retunred -1 which prefer to the doc

The command returns -1 if the key exists but has no associated expire

So clearly the change did not work or my prediction would be that I have to wait for the new invalid feed to come up which my change would be apply to but after a long time waiting I regconize that I might be able to delete all the data. I came into my project and rm -f redis-data and after that my project stop working and I have to ask the maitaince of the project to kindly send me the redis-data folder again.

After that, I found out that we would be able to use flushall in the redis-cli to clear all the invalid key and after run the project again. My change clearly did not work at all.

After talking with Emily she also suggest me to come to src/backend/utils/storage.js and change the same line of codes. It seem surpising to me when we have two indentical code at two different places of the project but the change did the job

After talking with some of the folks in the Slack channel which have more experience. They have kindly explain

that's because initially we had only one back-end (the one inside the backend folder) doing everything, and as we started developing microservices, we had to move the code to the microservices using that code. The easiest way was to copy the whole chunk of code from the old backend to the microservice you're working on, but sometimes you might copy parts that you don't need, like setInvalidFeed in this case

This has not make a lot of sense to me yet because of my knowledge about the project but I will note it here for feature preference

You can check out my PR

Another trick that I learn when using Git

When talking and working with Duke, we try to co-operate and using Gitpod for our work so I upload a dummy version of what I got on branch issue-2569 butn since I did not be able to pull off the second requirement of the issue and I need to submit my PR. I come into the project and use git reset --soft and discard the change from the MOCK_REDIS = and changes in the proccesor.js then push -f back into the branch.

I can say I get a bit handy with git and understand the flow of it now after 14 weeks !

Release 0.4: Progressing

Amazing — Mon, 13 Dec 2021 04:31:51 +0000

A few updates here for you folks

Fixing the first requirement

Like what I thought the first requirement is quite simple. I use JSON pretty print to help me get a better and clean look at the returned JSON when testing. But not to mention this is my first time actually running the docker and start all the images by using npm services:start and every time you made some change to the code you will have to stop and run it again npm services:stop.

I hear that Emily has been working on the invalid feeds for a long time so I thinking about checking her commit would give me an idea on where to start it. I see Emily create some change in the src/api/posts/src/storage.js where we might get the info of the invalid feed through getInvalidFeeds. I went in and make use regex to chane all the \n to whitespace

reason: reason.replace(/\n/g, ' '),

Then I restart the images and ran again the results the regex do the work

A lot of debugging for second requirement

For the second requirement, I would check all the common point of the 304 invalid and it is weird to me that some of them seem to work fine and show up in telescope where it should not

An invalid post would be a post that we would not be able to pass through the parser.

I put the break point at src/backend when the queue is failed we will call invalidateFeed

And to my prediction, the rss-parser fetcha a feed and gets 304, the 304 has no body so we considered it to be failed request and mark it invalid

I try to make change at src/backend/feed/processor.js

 if (!(response && response.status >= 400)) {
    info.shouldDownload = false;
    return info;
  }

When I restart it, for a while there was no 304 psot which make me feel so exiciting about it but for a while the 304 keep showing up more and more so the problem has not been solved

Third fix

I actually found 2 resources which might be useful to help me in setting the ttl expire period for the key: Redis-doc and issue-100 and I wil be dig in to it in couple days to figure it out

Release 0.4: Planning

Amazing — Mon, 13 Dec 2021 02:12:41 +0000

For the final submission I choose to continue contribute to telescope as I belive this would be a steepping stone for me to study OSD700. I choose to fix a bug in the project where we we try to improve handling invalid feed

My plan and my goal

My goal for when working on this issue will be to understand more how the project work because as you know my precent contribution to Telescope would be mitigrate ESlint to the newest version which require not a lot of coding and debugging so I will choose to go with this issue which seem not be quite difficult to work on.

I got 3 goal that need to be fill for this issue:

Remove \n from the reason so that we can display it as a single line. We could replace them with ' ' (space)
Figure out why 304s are showing up as invalid.
Set a ttl for these invalid keys in Redis

My plan from the start would be fixing the first 2 where the first one seem to be solve using regex and since I know a bit about response I will try to investigate it and then solving the thrid one which I got no clue where to start.