You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm considering upgrading http to v1 on atrium-xrpc along with this, but isahc, which can be used with atrium-xrpc-client, still depends on 0.2, and it seems it will be a few more months before isahc upgrades to v1.0, as discussed in this issue sagebind/isahc#432
Maintain the current configuration unchanged until isahc supports http v1.0.
Temporarily remove the feature that depends on the isahc client until an updated isahc version becomes available.
Consider alternative approaches.
This note serves as a reminder of the current situation and the decisions that need consideration.
The text was updated successfully, but these errors were encountered:
The
http
crate version was upgraded to v1 in the recentreqwest
v0.12.0 release.https://github.com/seanmonstar/reqwest/blob/master/CHANGELOG.md#v0120
I'm considering upgrading
http
to v1 onatrium-xrpc
along with this, butisahc
, which can be used withatrium-xrpc-client
, still depends on 0.2, and it seems it will be a few more months beforeisahc
upgrades to v1.0, as discussed in this issuesagebind/isahc#432
isahc
supportshttp
v1.0.isahc
client until an updated isahc version becomes available.This note serves as a reminder of the current situation and the decisions that need consideration.
The text was updated successfully, but these errors were encountered: