 All right, let's work through the client linting error. So client linting is a way to reduce errors, improve the quality of our code base and enforce some common rules. Our rules that we use in Galaxy are defined by ESLinter and on GitHub, that command that runs is ESLint. This is what starts a process for linting code on the client side. There's a note here that we do have a Python linter as well, which you may run into problems with in the future when you contribute to Galaxy but we're not going to run through any exercises using that today. Just know that the way to diagnose and treat these is very similar to the way that you do it for the front end. So first thing, this one is going to be a little bit different than the other few because one of the failing test workflows on GitHub would be this get code and test and then you would see that it's the JS lint. But because of the way that we have the branch set up because of the multiple bugs, some of the test failures overlap and the get code and test workflow has been skipped in the last commit. So in order to see what that looks like, we're just going to be using this commit. So let's pretend everything. I'm going to just open that in a new tab. So now we clicked on the little X, the little commit message and here we are. So we see here this JS lint and that's what we're going to click on. We're going to look at that. And when we scroll down, we said, this is the command that ran. They seeded into the client and ran yarn run ES lint. At the bottom here, we see that there's one error. So we can scroll back up through all these warnings and find the error. Okay, it says view is defined but never used and it's located in a view component called rule component. So now let's go back to the tutorial. We know where the problem is. We want to verify that locally. So in order to do that, we're going to go to the terminal. I'm just going to verify that I'm on the train bridge, good. And then I'm going to activate my virtual environment. So if we go look at the tutorial again, we can just grab that. You can put copy here and it'll automatically load it. And paste it. And you'll see at the front here, it now says that I'm in my virtual environment. So we know that that is true. Then according to the tutorial, we've got some options. You can either run the exact same command that CircleCI uses, which is to seed into the client and run yarn run ES lint. Or you can run make client lint, which does the same first two things and then also runs prettier check. Something else that we use is prettier and that's a formatting thing. And so sometimes you'll run into like, oh, there's an extra space here or an extra line. And this will tell you that problem too. So I like to run make client lint. And that's what I'm going to do, but you can feel free to do whatever you want there. So you'll see that we seed into the client and now we're doing some yarn stuff. And now we're running yarn run ES lint. And you'll see it's gonna output all that same errors, all those warnings that we saw in client CI. And to that, we've got 175 problems and one of them is an error. We can scroll up and we can see off. View is defined but never used in the rule component. So next I'm going to open up VS code. I'm gonna check control P and we're going to go to this rulecomponent.view. Most recent open one. We know that this is where the problem is and we know that the problem was it's an import and it's this import. And in fact, even just looking at the screen from here, you can see that the colors of this import are muted which means that it's not being used. Ta-da! You can run yarn ES lint hyphen hyphen fix or yarn run prettier to do that. But what I'm going to do is just delete that line, save it. And now back in my command line, I'm going to rerun the linter and hopefully that error will be gone now. Ta-da! And like I said, this is also going to be running prettier. So if you would have removed the import line but left an extra space there, you'd see a prettier would tell you that the formatting was off but I removed both lines. I removed the empty line that the import statement was on. So it's not going to have any problem but it's checking all different files just to make sure that they look pretty. So yay, we did it, you fixed it. We're going to write a useful commit message if you're not sure what to write you can check out our contributors guide here and then our error is fixed. So we're going to say get status, get app, get commit dash M, removed an unused import in rule component. And there we go. Congratulations on fixing a client linter.