about summary refs log tree commit diff stats
Commit message (Collapse)AuthorAgeFilesLines
* 3615Kartik K. Agaram2016-10-311-7/+7
|
* 3614Kartik K. Agaram2016-10-311-8/+8
|
* 3613Kartik K. Agaram2016-10-313-8/+23
|
* 3612Kartik K. Agaram2016-10-311-4/+3
|
* 3611Kartik K. Agaram2016-10-311-0/+1
| | | | Fix CI.
* 3610 - bugfix in type-checking 'call' instructionsKartik K. Agaram2016-10-312-2/+14
| | | | | | | Thanks Rebecca Allard for running into this. The test is in layer 13 even though the code that regressed was fixed in layer 71, because the test was working as-is in earlier layers.
* 3609Kartik K. Agaram2016-10-293-2/+10
|
* 3608 - concurrent writes to fake file systemKartik K. Agaram2016-10-293-2/+10
|
* 3607Kartik K. Agaram2016-10-281-1/+1
|
* 3606Kartik K. Agaram2016-10-281-1/+1
|
* 3605Kartik K. Agaram2016-10-281-25/+32
|
* 3604Kartik K. Agaram2016-10-2713-70/+108
|
* 3603Kartik K. Agaram2016-10-271-2/+0
|
* 3602Kartik K. Agaram2016-10-272-28/+20
| | | | | Simplify primitive interface to read from a socket: now returns just a single character.
* 3601Kartik K. Agaram2016-10-271-1/+1
| | | | | Now we can just read a single character from the socket, and it isn't much slower either (maybe 10%).
* 3600 - allow reading a single byte from a socketKartik K. Agaram2016-10-271-3/+3
| | | | | | | Required fixing an off-by-one error. (Not bothering writing a test for this since I'm hoping to simplify $read-from-socket to always return a single character..)
* 3599Kartik K. Agaram2016-10-272-4/+8
|
* 3598 - 'use before set' errors were too crypticKartik K. Agaram2016-10-272-3/+3
|
* 3597 - typo in screen checkingKartik K. Agaram2016-10-271-4/+4
| | | | Thanks Ella Couch for reporting this.
* 3596Kartik K. Agaram2016-10-251-0/+3
| | | | Fix CI.
* 3595Kartik K. Agaram2016-10-251-1/+1
| | | | | Fix for that annoying popup from the Mac OS firewall: inside tests keep any opened ports accessible only to localhost.
* 3594Kartik K. Agaram2016-10-251-2/+2
|
* 3593Kartik K. Agaram2016-10-251-1/+2
|
* 3592 - warn on *any* lookup of address 0Kartik K. Agaram2016-10-252-3/+19
| | | | Thanks Caleb Couch for running into this with $print.
* 3591Kartik K. Agaram2016-10-241-4/+4
|
* 3590Kartik K. Agaram2016-10-241-0/+17
| | | | | Patch in a new darling from my recent comment at https://lobste.rs/s/n0d3qo/what_are_you_working_on_this_week/comments/rue8pf#c_rue8pf
* 3589 - update authorship in the ReadmeKartik K. Agaram2016-10-241-25/+26
|
* 3588 - documentation for filesystem and networkKartik K. Agaram2016-10-245-10/+43
|
* 3587Kartik K. Agaram2016-10-242-8/+9
| | | | Another CI fix.
* 3586Kartik K. Agaram2016-10-242-6/+16
| | | | Make sure we clear the socket variable after closing it.
* 3585Kartik K. Agaram2016-10-242-18/+0
|
* 3584Kartik K. Agaram2016-10-241-2/+1
|
* 3583Kartik K. Agaram2016-10-241-5/+5
|
* 3582Kartik K. Agaram2016-10-241-3/+3
|
* 3581Kartik K. Agaram2016-10-242-3/+37
| | | | | | | Fix CI. 3 different memory leaks in the socket internals. The hard one was recognizing the need for `receive-from-client-socket-and-close`.
* 3580Kartik K. Agaram2016-10-241-1/+1
|
* 3579Kartik K. Agaram2016-10-241-1/+1
|
* 3578Kartik K. Agaram2016-10-239-369/+348
|
* 3577Kartik K. Agaram2016-10-231-0/+1
|
* 3576Kartik K. Agaram2016-10-233-1/+43
| | | | More helpful messages when people forget 'load-ingredients'.
* 3575Kartik K. Agaram2016-10-231-2/+2
|
* 3574Kartik K. Agaram2016-10-234-230/+193
| | | | Shorter branches above longer ones.
* 3573 - client socket testsKartik K. Agaram2016-10-232-4/+31
| | | | This is just the same as tests for a fake file-system.
* 3572 - new way to write server testsKartik K. Agaram2016-10-231-126/+43
| | | | | | | | | | | | | This time we're opening real sockets so we might run into issues on machines with firewalls. Macs for example flash up a dialog warning people about a port being opened, though it shuts down immediately if the test passes. On the flip side, the test has greater verisimilitude. You don't really need fakes except when you want to pin down the environment a test runs in. The only way this test might be flaky is on a machine that has lots of sockets open (so the random port opened by the test is in use for something else). That and the firewall concern above. Hmm.
* 3571 - make 'read-from-socket' non-blockingKartik K. Agaram2016-10-232-12/+40
| | | | Its interface now mirrors that of 'read-event'.
* 3570 - don't busy-wait in 'wait-for-event'Kartik K. Agaram2016-10-231-1/+3
|
* 3569Kartik K. Agaram2016-10-2351-4605/+4607
| | | | Update syntax highlighting to not color numeric locations like literals.
* 3568Kartik K. Agaram2016-10-2319-60/+62
| | | | Fix syntax highlighting for labels after commit 3552.
* 3567Kartik K. Agaram2016-10-238-25/+58
|
* 3566Kartik K. Agaram2016-10-231-3/+4
| | | | | | | | | | | | vim: Stop loading C++-specific syntax highlighting in non-C++ files. I also figured out why the autocommand wasn't running on the first file: my local setup for directory-specific vimrc files runs inside an autocommand, and it runs autocommands recursively inside an autocommand, and it runs only autocommands inside a 'LocalVimrc' autocommand group to ensure infinite regress (autocommands running multiple times in practice). And I'd forgotten this 'feature' of my vimrc setup by the time I set this up for Mu.
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-06-30 23:52:55 +0000