anytype 0.3.0

An ergonomic Anytype API client in rust
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49

# Known issues & Troubleshooting

## I keep getting prompted to authenticate

- Every time the anyr binary (or other program using anytype-api) is recompiled, macos prompts the user to allow the app to access the keychain. If you click "Always Allow", you should get prompted at most twice, and after that, the OS should remember the setting and allow the app to read the keychain.
- Note that each "example" is a separate "program", so if you run lots of examples, you'll get prompted many times.
- To avoid getting inundated with permission prompts while doing builds, or running tests or examples, use a file-based keystore, instead of the default OS keyring-based keystore. You can do this by setting ANYTYPE_KEYSTORE=file (for default location) or ANYTYPE_KEYSTORE=file:path=/path/to/keystore.db

## Tracking issues in `anytype-heart`

Issues in the `anytype` library should be filed in this repo.

The following issues were found during testing `anytype` and are filed in the `anytype-heart` repo.

**Issues**

- [2879](https://github.com/anyproto/anytype-heart/issues/2879) bool and number filters in list queries.
- [2887](https://github.com/anyproto/anytype-heart/issues/2887) sorting search results by `due_date`
- [2883](https://github.com/anyproto/anytype-heart/issues/2883) Crash: nil account-key from DeriveKeysFromMasterNode

**PRs**

- [2880](https://github.com/anyproto/anytype-heart/pull/2880) using "type" ids in list filters
- [2881](https://github.com/anyproto/anytype-heart/pull/2881) bool and number filters in list queries
- [2882](https://github.com/anyproto/anytype-heart/pull/2882) select tags in filters PR
- [2884](https://github.com/anyproto/anytype-heart/pull/2884) crash: nil account-key from DeriveKeysFromMasterNode

## Debug logging

To enable debug logging, set `RUST_LOG=debug`

To log http requests and responses, set `RUST_LOG=anytype::http_json=trace`

To enable logging in examples, set RUST_LOG in the environment, and initialize tracing in main().

```rust
    use tracing_subscriber::EnvFilter;
    let _ = tracing_subscriber::fmt()
        .with_env_filter(EnvFilter::from_default_env())
        .try_init();
```

## OS Keyring may require signed executables

The OS keyring feature for key storage may not work if the app is unsigned (symptom: either you get a hard error, or you get prompted authenticate with the OS too often). File-based key storage is available as a fallback.

## Spurious 500 errors

While running unit tests on `anytype`, which can hammer the server pretty hard and run into rate limits, I sometimes encounter spurious 500 errors from the anytype server when creating objects. In nearly all cases, retrying the request, with the exact same bytes, succeeds. To shield the library caller from this, the http_client middleware automatically retries requests up to 3 times if it encounters a connection timeout, server timeout, or 500 error.