 Welcome to today's functional group update for the platform backend team. My name is Auman and I'm the engineering manager and today as it says there and as I hope you are aware it is the first of May 2018. The last update was actually only three weeks ago. Usually we do five but because of some moving around of updates it has only been three weeks. Not all that much has happened since but we did release get that 10.7 on April 22nd. Of course platform team contributed a lot of things to this release and the blog posts that are linked to covers that in great detail. But there were a couple things that I don't think deserved quite the attention they or didn't quite get to the attention they deserved. So I wanted to correct that with this slide. Couple things I think are very much worth mentioning. On the one hand we have the create commit API that now respects LFS tracking rules which means that if you use the API to create a file upload file with a certain extension and we know that that file should be tracked by LFS. Instead of just putting the file in the repository anyway we actually on the back end go through the trouble of uploading it to LFS and the file that ends up in the repo is just the LFS pointer. Thanks James and for Jones for working on this. We also have better LDAP connection feel your hand. The other three couple times and when it still doesn't work after a couple retires if we still cannot connect to LDAP we interpret that as the user no longer existing in LDAP which in the past would result in user being blocked or being removed from a group those kinds of things. Now we are a little bit better about realizing that it's just a connection failure and that we will have another chance at underline. Of course if there's a certain time period where you haven't been able to verify if the user should still have access to certain resources we do block them but not just because there is a momentary connection error. The future of the project is also pretty much the you can see this in the actual thank you Tiago. The archive projects which in the past only had a read only repository are now completely really their issues their merge requests you cannot comment you cannot change you cannot create anything in there which makes them a lot more archived than they previously were and it's just something that Bob worked on. Then in the next five weeks hopefully the next update will be in five weeks so this should cover everything that happened until then. The first thing we're going to do on May 7th is finalize the development of GitLab 10.8 and a couple of the things that are going to be in that piece are listed here. I'm not going to go into too much detail because of the links and read up all about them there. The one I wanted to call out which might sound all too interesting is important mirroring relays without project stable. Projects in GitLab that are mirrors of an external project posted on some other repository of course updates frequently they update on some schedule. Apparently I'm having some connection issues let me just retry sharing the sites and otherwise I hope that everyone will just be able to read the sites for themselves and go from there. Give me one second I'll try to restart this and we're going to give it another try. Okay I think you should see my screen again if not then please let me know. I'm also going to open up the chat window again so I can know if someone says something's broken. All right Bob says for back I guess that's good news. So yeah now I was talking about important mirroring related columns moved out of the project stable. On GitLab.com we have a lot of projects that are mirrors of externally hosted projects and periodically GitLab will sync up and get any latest changes from those remote resources, those remote locations and we have a lot of those projects doing that and every time they do that they go through a couple state transitions they go from scheduled to be updated currently updating finished or updating filled and at some point they go back through that cycle again and we're pretty much constantly doing that for at this point around 15 different 15 mirrors per second to get updated and this of course means that there's a lot of actual updates to the status field happening in the database. Right now these status fields are stored right on the project stable which is a quite large table which stores a lot of project related data mostly settings and some cash stuff but it's still quite a wide table with a lots of columns that means that every time that we just switch the state from one value to another we actually write a whole new row into Postgres and mark the other one as as old as still which means that we are actually accumulating a lot of old still data because we're doing this in this pretty big table so one thing we're going to do is to move these fields to a separate table which will be much smaller which will only store mirroring and import related data which means that if we update it as frequently as we do we will not be building this huge amount of still rows so this will be you will be able to see this not directly in the application but hopefully you'll be able to experience performance benefits and just you know everything on get the outcome will be a little bit faster hopefully you won't notice which means that everything is going right and there's a couple more issues there that you might want to check out if you're interested in specific people for doing for 10.8 then on May 8 we will be kicking off development of GitLab 11.0 what's going to go in there is not quite clear yet but it will be announced on the public kickoff on May the 8th and this is available to everyone everyone can join if you check out that link you will be able to see the details of where you can follow along and then another happy event that's going to take place in the next couple weeks is that Imre Farkas will be joining the team as a senior developer on May 9th and I would like to specifically thanks Jan who I think worked with him previously and who referred to GitLab and as Sean mentioned to me a couple times when Jan referred Imre he told Sean he's a pretty good developer and Sean immediately said like oh yeah if Jan thinks he's pretty good we have to get him and it turns out that he is absolutely great and I'm very much looking forward to having him join the team that's everything that I had to share for now like I mentioned it's only been three weeks since the last update so not too much has happened hopefully the next third will be a little bit more interesting if anyone has any questions though I'd be more than happy to answer them and if not I'm going to give everyone about 10 seconds and then I will give you about 23 minutes every day left back