mirrors/arti.git/crates/arti-rpc-client-core/cbindgen.warnings, branch arti-v1.2.8mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.2.82024-09-09T14:52:56ZRe-run cbindben for new warnings and status codes2024-09-09T14:52:56ZNick Mathewsonnickm@torproject.org2024-09-04T18:41:57Zurn:sha1:a2fadf80c640bc6f9b7b42405a773c56dad04c52rpclib: FFI for opening data streams.2024-09-09T14:52:56ZNick Mathewsonnickm@torproject.org2024-08-26T15:31:18Zurn:sha1:8fd335e5ae7ad761efe3030e33b7004ec70fc2ff
There's a blocking TODO here about exposing socks error codes that
I still need to solve.
cbindgen: Correctly hide "Utf8CString".2024-08-14T17:27:51ZNick Mathewsonnickm@torproject.org2024-08-14T17:27:51Zurn:sha1:10a73c3367e526ddedcf5c81a7eddd019d95fcc5ffi: Add support for request handles2024-08-12T18:35:09ZNick Mathewsonnickm@torproject.org2024-08-06T15:57:54Zurn:sha1:2364c6dc6d2fd16f08641a1fed2cbc970005dc66
This API allows the caller to launch a request and then watch for
updates on it.
Re-run cbindgen to fix CI2024-08-08T11:52:37ZNick Mathewsonnickm@torproject.org2024-08-08T11:51:27Zurn:sha1:aa387176830457fa79506027423106609dc7eb18
For some reason, we wound up - not with anything missing in the
header - but with extra warnings in our expected warnings file.
I'm tentatively blaming the git merge algorithm, or perhaps
the phase of the moon.
Re-run cbindgen to update our generated header.2024-08-07T13:29:45ZNick Mathewsonnickm@torproject.org2024-08-07T13:27:59Zurn:sha1:383787c72a4b56a746af9702deb003907daf75e1
(This is kind of thing that the CI script should remind us to do.)
ffi: Re-run cbindgen.2024-07-31T17:57:03ZNick Mathewsonnickm@torproject.org2024-07-31T17:57:03Zurn:sha1:4497317f07df7a0f13bddc4e7a7727dbe12532b9rpclib: Grand error refactoring: outparam, not thread-local2024-07-31T17:54:16ZNick Mathewsonnickm@torproject.org2024-07-25T13:52:56Zurn:sha1:6b1f266a8405d7c07b10e5cf2b153c575e6f2288
Per discussion, we'd rather have an optional output parameter for error
objects rather than mess with thread-local variables.
This is possibly less convenient for direct usage from C,
but likely more convenient for wrapper functions in other languages.
rpclib: _Sketch_ of string API.2024-07-31T17:54:16ZNick Mathewsonnickm@torproject.org2024-07-24T19:13:40Zurn:sha1:5265d6c1aa3c14ef09d908c9695eb1f003253d33
In this API, borrowed strings are `const char *`, and owned strings
are `ArtiRpcStr *`. You can get the former from the latter with
`arti_rpc_str_get()`, which returns a `const char *` in hopes that
you will neither modify nor free() that `const char *`
(Note that there are no places where string ownership needs to be
passed into this library; and at present, there is only one case
where it is passed out. I do not anticipate that we will need to do
intake of owned strings. We will probably need to return these in a
few more cases as we add more API surface.)
rpc ffi: Try a more reference-driven approach to pointer handling.2024-07-31T17:54:16ZNick Mathewsonnickm@torproject.org2024-07-17T18:49:55Zurn:sha1:7e48f725dd665c5ff6eb07f16bd4957274767f6c