34148f9f44
Previously, we would reject this with a 400 error. Considering the request body is expected to contain "array of requests" and that arrays may be empty, we really should not be rejecting the requests. Prior to 156ca21472, sending the empty array would have been convenient for channel creation. Empty arrays getting rejected forced clients to inject a faux poke (commonly hi-ing oneself). With that recent change, the most common case for wanting to PUT the empty list of requests is largely obsolete, but one can still imagine it being useful for clients that want to keep their channel alive without necessarily being connected to it. This also implements sloppier clients from running into 400 responses when they submit an empty "command queue" for whatever. Regardless, there seems to be no clear reason why the empty request list _shouldn't_ be accepted and processed as normal. We add a small test to ensure eyre accepts this. |
||
|---|---|---|
| .github | ||
| bin | ||
| doc/spec | ||
| extras | ||
| nix | ||
| pkg | ||
| sh | ||
| tests | ||
| .gitattributes | ||
| .gitignore | ||
| .ignore | ||
| .mailmap | ||
| .stylish-haskell.yaml | ||
| CONTRIBUTING.md | ||
| default.nix | ||
| flake.lock | ||
| flake.nix | ||
| LICENSE.txt | ||
| MAINTAINERS.md | ||
| Makefile | ||
| README.md | ||
| shell.nix | ||
| test-desk.bill | ||
| vere-version | ||
Urbit
Urbit is a personal server stack built from scratch. It has an identity layer (Azimuth), virtual machine (Vere), and operating system (Arvo).
A running Urbit "ship" is designed to operate with other ships peer-to-peer. Urbit is a general-purpose, peer-to-peer computer and network.
This repository contains the Arvo Kernel
For the Runtime, see Vere. For more on the identity layer, see Azimuth. To manage your Urbit identity, use Bridge.
Install
To install and run Urbit, please follow the instructions at urbit.org/getting-started. You'll be on the live network in a few minutes.
Contributing
Contributions of any form are more than welcome! Please take a look at our contributing guidelines for details on our git practices, coding styles, and how we manage issues.
You might also be interested in joining the urbit-dev mailing list.
Release
For details about our release process, see the maintainers guidelines