News for hackers. Stuff that matters.
Re:FoundationDB community highlights, two weeks in by ihnorton on Friday May 04, 2018 @11:27AM (#16995287)
I’m curious how they plan to do continuous integration. The Apple hardware-only clause of the macOS SDK license agreement really crimps the options for CI, especially for open source projects with limited budget. Travis is a godsend, but there are startup latency and capacity issues there even in the paid tier. Apple has made major contributions to open source, as evidenced by FoundationDB here, LLVM, WebKit, and other projects. But they no longer make servers, and the fallback — Mac mini — is on life support, which puts projects and service providers who need to treat macOS as a first-class target in a real bind. Even something limited like the IE Edge and Visual Studio images Microsoft provides would be a huge boost.
Re:FoundationDB community highlights, two weeks in by wwilson on Friday May 04, 2018 @02:11PM (#16996804)
The only license you need to accept to use this software is Apache 2, so I’m not sure where you’re getting the idea that there’s an Apple hardware restriction.
Re:FoundationDB community highlights, two weeks in by ihnorton on Friday May 04, 2018 @02:30PM (#16997025)
The question is not about where FoundationDB can run in general. Sorry if that was unclear.

The question is about (public?) continuous integration testing for changes to FDB against macOS specifically, eg for pull-requests (for example, to allow contributors to make changes targeting other platforms without needing to own a mac for local tests).

Re:FoundationDB community highlights, two weeks in by wwilson on Friday May 04, 2018 @03:41PM (#16997583)
Ah, sorry, that’s a good question.

The good news is that FDB has a fairly opaque platform abstraction, and deterministic simulation tests for everything above it, so the vast majority of continuous testing in terms of CPU cycles can be run on Linux.

The only thing that really needs to run on a Mac are tests for changes to the build or packaging system, or to the MacOS implementation of the platform layer. My sense is those changes are pretty rare.

I don’t know whether the FDB team has an official recommendation for MacOS CI. I’d recommend posting a question on the forums: http://forums.foundationdb.org

Re:FoundationDB community highlights, two weeks in by bluejekyll on Friday May 04, 2018 @05:04PM (#16998323)
what's wrong with Travis? https://travis-ci.org/bluejekyll/foundationdb-rs/jobs/375032...

I already set that up, it installs the binary for FoundationDB then runs the tests for our Rust client on mac. No reason why they couldn't do the same for FoundationDB, but I bet they have something in house.

Re:FoundationDB community highlights, two weeks in by fnord123 on Friday May 04, 2018 @11:46AM (#16995463)
>I’m curious how they plan to do continuous integration. The Apple hardware-only clause of the macOS SDK license agreement really crimps the options for CI, especially for open source projects with limited budget.

FoundationDB is a distributed key value store. These almost always run on servers. macOS is not a server OS. Is there any reason to build this on macOS, over, say, FreeBSD.

Re:FoundationDB community highlights, two weeks in by jen20 on Friday May 04, 2018 @03:23PM (#16997445)
Many developers want to install it for local development - presumably this is a particular popular sentiment _at Apple_. There is a FreeBSD port already, however [1].

[1]: https://www.freshports.org/databases/foundationdb/

Re:FoundationDB community highlights, two weeks in by Mister_Snuggles on Friday May 04, 2018 @04:32PM (#16998046)
Sadly, as I discovered today, the FreeBSD port is incomplete.

First up, it doesn't create the fdb.cluster file. I reverse engineered that logic out of the Mac OS packaging script, which wasn't a big deal. Once I created the file I was able to start it up and connect to it with fdbcli.

Second, the Python bindings do not work on FreeBSD. Trying to set the API version (the first step in calling the API) gives an error specifically saying they're not supported on FreeBSD.

Still though, for something that was released two weeks ago to be already ported to FreeBSD is pretty impressive!

Re:FoundationDB community highlights, two weeks in by jen20 on Tuesday May 08, 2018 @04:00PM (#17024356)
There has been a more complete pull request [1],[2] back to the main project repository which solves some of these problems, and should ultimately result in the (FreeBSD) port being fairly straightforward.

[1]: https://github.com/apple/foundationdb/pull/309

[2]: https://forums.foundationdb.org/t/freebsd-support-for-founda...

Re:FoundationDB community highlights, two weeks in by fnord123 on Saturday May 05, 2018 @04:30AM (#17000936)
>Many developers want to install it for local development

Why? Just use the in tree Dockerfile (which didn't work due to linking errors with libstdc++.a missing definitions for basic_istream::ignore last I checked).

Re:FoundationDB community highlights, two weeks in by hiroshi3110 on Saturday May 05, 2018 @07:34AM (#17001373)
Re:FoundationDB community highlights, two weeks in by maccam94 on Friday May 04, 2018 @02:08PM (#16996781)
> they no longer make servers, and the fallback -- Mac Mini -- is on life support

Well, there's also the Mac Pro (companies even make rack mounts that fit 2 machines in a 4U). But I wholeheartedly agree about the CI issues (having been hampered by them in a previous project). That doesn't really seem to be an issue for FoundationDB though?

Re:FoundationDB community highlights, two weeks in by saagarjha on Friday May 04, 2018 @07:43PM (#16999327)
The Swift project uses an array of Mac Pros: https://ci.swift.org/computer/
Re:FoundationDB community highlights, two weeks in by soperj on Friday May 04, 2018 @11:48AM (#16995478)
lol to webkit. It was a fork of khtml.
Re:FoundationDB community highlights, two weeks in by solarkraft on Friday May 04, 2018 @01:05PM (#16996166)
It is, but they improved and maintain it.
Re:FoundationDB community highlights, two weeks in by hb3b on Friday May 04, 2018 @11:49AM (#16995485)
Is there a precedent for Apple enforcing this clause on providers in the CI space? I vaguely remember some cease-and-disist letters to Hackintosh vendors but I'd imagine that has to do with brand protection.