connorshea

Joined 12 years ago

Karma

657

Submissions

155

Member since

Aug 30

Software Engineer primary working with Ruby

View on Hacker News

Recent submissions

Comment · 5 years ago

I've been using Sorbet on a personal project (https://github.com/connorshea/vglist) for almost two years now, and it's been great (although I've had to build myself a lot of tooling for it over time).

I don't think I'll use the compiler (for now, at least), but I'm very interested in seeing how it grows over time :)

Comment · 8 years ago

This makes me so happy, thank you! :D

Comment · 8 years ago

As a user of the iOS app it used to have some admittedly frustrating problems, but pretty much every complaint I had previously has since been fixed, huge kudos on the progress you've made!

The only thing left that really bugs me is the fact that you can't paste images from the clipboard into the message field. It's made me change my entire workflow, from copying images to saving them.

Sorry to use this as a soapbox for my pet issue, but I saw the opportunity :P

Comment · 8 years ago

The issue in question for anyone curious: https://gitlab.com/gitlab-org/gitlab-ce/issues/28996

I'm looking forward to it as well :)

Comment · 8 years ago

Not OP but anything that makes the process smoother is good IMO :)

Comment · 8 years ago

Libre/Starter/Premium/Ultimate are the names of plans for our distributions. CE and EE are distributions of GitLab. CE has _only_ FOSS code in it for users (e.g. self-hosting open source projects) who don’t want to run any proprietary code whatsoever. Libre features are any features that are in the CE distribution by default.

The Free/Bronze/Silver/Gold plans are for GitLab.com specifically (all open source projects get Gold features by default).

Comment · 8 years ago

We also have an issue for running jobs only when modifications are made to a given file or files in a directory, it's tentatively scheduled for 10.7 (April's release).

https://gitlab.com/gitlab-org/gitlab-ce/issues/19232

Comment · 8 years ago

Not Sid, but thanks for being a fan ;)

Comment · 8 years ago

Mirroring is an Enterprise Edition feature but there are probably ways to hack around that.

Comment · 8 years ago

We actively try to make improvements so GitLab uses fewer resources, but with the scope of the application it's definitely not easy to make it super "lightweight".

You can see the hardware requirements here: https://docs.gitlab.com/ce/install/requirements.html#hardwar...

Comment · 8 years ago

There are no plans to migrate all of GitLab to Go. The main Rails app is going to stay a Rails app for the foreseeable future. There are a few reasons for this. For one it'd be such a huge project, but also Rails is working well for us, it's great for our pace of feature development.

We are working on moving the git layer to Gitaly[0] which is written in Go (and is what this blog post is about). It was one of our major bottlenecks and we've seen a lot of benefit from having made the switch. It's not done yet, but a lot of the calls to git that the application makes are now done through Gitaly.

[0]: https://gitlab.com/gitlab-org/gitaly

Comment · 8 years ago

Hey, sorry about that. I just replied.

Comment · 8 years ago

See our Stewardship page[0] for how we determine what goes in EE vs. CE, for now Burndown Charts will stay in EE. As for EBS, feel free to open an issue for it[1] since I couldn't find one :)

[0]: https://about.gitlab.com/stewardship/ [1]: https://gitlab.com/gitlab-org/gitlab-ee/issues

Comment · 8 years ago

Thanks for the feedback, I looked into it and it looks like neither of these problems have been fixed as of yet. I've asked the CI and UX teams if we can work on the Environments page.

Here's the issue for the table size: https://gitlab.com/gitlab-org/gitlab-ce/issues/41594

Comment · 8 years ago

For what it's worth, in the last year (since January 23, 2017) we've merged ~440 merge requests labeled "performance"[0]. It's not perfect right now and there's still plenty of work to do, but compared to when I started at GitLab almost two years ago it's night-and-day.

We've also got an entire team dedicated to porting our Git layer to Go with Gitaly[1], which has been a major bottleneck that we've started resolving over the last year or so.

[0]: https://gitlab.com/groups/gitlab-org/-/merge_requests?label_... [1]: https://gitlab.com/gitlab-org/gitaly