error: proc-macro derive panicked
  --> src/lib.rs:14:10
   |
14 | #[derive(GraphQLQuery)]
   |          ^^^^^^^^^^^^
   |
   = help: message: Extracting query path.
           The graphql attribute is missing

error: proc-macro derive panicked
  --> src/lib.rs:14:10
   |
14 | #[derive(GraphQLQuery)]
   |          ^^^^^^^^^^^^
   |
   = help: message: Extracting schem

$cargo run

Finished dev [unoptimized + debuginfo] target(s) in 0.13s
Running /home/folaht/testbot/devlohpmaq/target/debug/testbot
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Io(Os { code: 2, kind: NotFound, message: "No such file or directory" })', src/main.rs:10:15
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

`$strace

Run cargo doc --document-private-items and we get the following warnings:

warning: unresolved link to `transaction`
  --> src/transaction/snapshot.rs:11:27
   |
11 | /// See the [Transaction](transaction) docs for more information on the methods.
   |                           ^^^^^^^^^^^ no item named `transaction` in scope
   |
   = note: `#[warn(broken_intra_doc_links)]` on by d

clear-all can be implemented with empty byte-array as begin and 255 as the end parameter. This can be helpful where we want to wipe all the keys similar to FLUSHALL in Redis. Similar thing can be done to implement get-all using get-range to return all the keys in the database.

Reference: https://forums.foundationdb.org/t/how-to-clear-all-keys-in-foun

This is a notice I'm filling in repo of every HTTP Client I can find.
Feel free to close it if this project already works fine with go-ipfs 0.5

POST-only HTTP API

go-ipfs 0.5 will block GET commands on the API port (ipfs/go-ipfs#7097), requiring every command (RPC) to be sent as HTTP POST request.
See API reference docs: https://docs.ipfs.io/referen

Sorunome has inline custom emoji things for matrix (there is also somewhere a Spec proposal for this). Basically we need to convert mxc links to real urls in text.

Implement more methods of the ArangoDB's REST API marked for milestone 2 (M.2).

The rincon_client crate does not implement all methods of ArangoDB's REST API. The current status is documented in docs/arangodb_rest_api_methods.md. Methods that are planned to be implemented are marked with a milestone.