bazel - a fast, scalable, multi-language and extensible build system

	Commit message (Collapse)	Author	Age
...
*	Block when another command is running on the server and not on the client ↵	Lukacs Berki	2016-04-20
\| \| \| \| \| \| \|	when in gRPC mode. -- MOS_MIGRATED_REVID=120233121
*	Bind the gRPC command server port only to localhost.	Lukacs Berki	2016-04-19
\| \| \| \| \| \| \|	Work towards #930. -- MOS_MIGRATED_REVID=120205147
*	Make it possible to interrupt commands when communicating over gRPC.	Lukacs Berki	2016-04-19
\| \| \| \| \| \| \| \| \| \| \|	Drive-by fix: eliminate the GRPC messages from the console by passing a null logging function. This also prepares us for the time when multiple commands will be running, because then we'll need to tell which command exactly we want to interrupt. Work towards #930. -- MOS_MIGRATED_REVID=120203008
*	Do not start the AF_UNIX server when in gRPC mode.	Lukacs Berki	2016-04-19
\| \| \| \| \| \| \|	Work towards #930. With this, it's conceivable that server mode works on Windows to some degree (I haven't tried, though, because there are many issues that need to be fixed) -- MOS_MIGRATED_REVID=120202037
*	Rename field names in command_server.proto so that they don't conflict with ↵	Lukacs Berki	2016-04-18
\| \| \| \| \| \| \| \| \|	C symbols. Fixed #1155. -- MOS_MIGRATED_REVID=120107746
*	Initial version of client-server communication over gRPC.	Lukacs Berki	2016-04-15
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	This still has a number of issues, including, but not limited to: - When switching between gRPC and AF_UNIX mode, you need to do a manual shutdown - The console is spammed with "connection refused" messages on server startup - When in gRPC mode, server also starts up an AF_UNIX server even though it's not necessary and concurrent requests probably make Bazel crash and burn - I have no idea how concurrent gRPC requests are handled and now many threads gRPC creates - Not tested except under Linux - The request/response cookies are written in an odd format (negative bytes are not handled correctly). This is only a cosmetic issue, since the data content of the string is the same either way. Can be tested with the --grpc_port=0 (or a valid port number) startup option. -- MOS_MIGRATED_REVID=119948959
*	Add the --grpc_port startup option and start a Java server if it's passed in.	Lukacs Berki	2016-04-14
	Note that the presence of server/grpc_port does not guarantee that the server actually listens to it and we can't guarantee it, either, because it can always be kill -9'd. I haven't decided yet how the transition between AF_UNIX and gRPC will work. For now, I'm happy that we can start up a Java server. The way to get the kernel-chosen port is truly awful, but it is apparently impossible to do so in a different way: https://github.com/grpc/grpc-java/issues/72 -- MOS_MIGRATED_REVID=119828354