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
The websocket functionality is behind a default feature so that it can be disabled. However, disabling the feature results in the crate failing to compile with the following error:
failed to resolve: maybe a missing crate `ws`?
--> src/reject.rs:253:37
|
253 | MissingConnectionUpgrade(crate::ws::MissingConnectionUpgrade),
| ^^ maybe a missing crate `ws`?
error: aborting due to previous error
The problematic code is behind a macro, so I don't immediately see a way to fix it. The macro was introduced in #311, but the issue appeared to still exist in the commit beforehand, albeit erroring on a different line:
error[E0433]: failed to resolve: maybe a missing crate `ws`?
--> src/reject.rs:400:35
|
400 | e.is::<crate::ws::MissingConnectionUpgrade> () {
| ^^ maybe a missing crate `ws`?
error: aborting due to previous error
The text was updated successfully, but these errors were encountered:
jxs
added a commit
to jxs/warp
that referenced
this issue
Dec 28, 2019
The websocket functionality is behind a default feature so that it can be disabled. However, disabling the feature results in the crate failing to compile with the following error:
The problematic code is behind a macro, so I don't immediately see a way to fix it. The macro was introduced in #311, but the issue appeared to still exist in the commit beforehand, albeit erroring on a different line:
The text was updated successfully, but these errors were encountered: