rustfix automatic fixes fail due to using wrong import for custom derive macro

Problem
rustfix (via cargo fix) fails to apply automatic updates on one of my crates. It incorrectly changes serde's Deserialize and Serialize custom derives from:
#[derive(Deserialize, Serialize)]

to:
#[derive(crate::Deserialize, Serialize)]

when it should be:
#[derive(serde_json::Deserialize, serde_json::Serialize)]

Changing it to the latter results in the crate compiling along with rustfix's changes.
Steps

Check out ruma-events at commit 6240c25.
Run cargo fix --edition.
See output:

$ cargo fix --edition
    Checking ruma-events v0.11.0 (/ruma-events)
warning: failed to automatically apply fixes suggested by rustc to crate `ruma_events`

after fixes were automatically applied the compiler reported errors within these files:

  * src/macros.rs

This likely indicates a bug in either rustc or cargo itself,
and we would appreciate a bug report! You're likely to see
a number of compiler warnings after this message which cargo
attempted to fix but failed. If you could open an issue at
https://github.com/rust-lang/cargo/issues
quoting the full output of this command we'd be very appreciative!

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/macros.rs:81:32
   |
81 |         #[derive(Clone, Debug, Deserialize, Serialize)]
   |                                ^^^^^^^^^^^ help: use `crate`: `crate::Deserialize`
   |
note: lint level defined here
  --> src/lib.rs:101:9
   |
101| #![deny(warnings)]
   |         ^^^^^^^^
   = note: #[warn(absolute_paths_not_starting_with_crate)] implied by #[warn(warnings)]
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/macros.rs:81:32
   |
81 |         #[derive(Clone, Debug, Deserialize, Serialize)]
   |                                ^^^^^^^^^^^ help: use `crate`: `crate::Deserialize`
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
 --> src/collections/all.rs:4:5
  |
4 | use call::answer::AnswerEvent;
  |     ^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::call::answer::AnswerEvent`
  |
  = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
  = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
 --> src/collections/all.rs:5:5
  |
5 | use call::candidates::CandidatesEvent;
  |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::call::candidates::CandidatesEvent`
  |
  = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
  = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
 --> src/collections/all.rs:6:5
  |
6 | use call::hangup::HangupEvent;
  |     ^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::call::hangup::HangupEvent`
  |
  = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
  = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
 --> src/collections/all.rs:7:5
  |
7 | use call::invite::InviteEvent;
  |     ^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::call::invite::InviteEvent`
  |
  = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
  = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
 --> src/collections/all.rs:8:5
  |
8 | use direct::DirectEvent;
  |     ^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::direct::DirectEvent`
  |
  = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
  = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
 --> src/collections/all.rs:9:5
  |
9 | use presence::PresenceEvent;
  |     ^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::presence::PresenceEvent`
  |
  = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
  = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/collections/all.rs:10:5
   |
10 | use receipt::ReceiptEvent;
   |     ^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::receipt::ReceiptEvent`
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/collections/all.rs:11:5
   |
11 | use room::aliases::AliasesEvent;
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::room::aliases::AliasesEvent`
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/collections/all.rs:12:5
   |
12 | use room::avatar::AvatarEvent;
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::room::avatar::AvatarEvent`
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/collections/all.rs:13:5
   |
13 | use room::canonical_alias::CanonicalAliasEvent;
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::room::canonical_alias::CanonicalAliasEvent`
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/collections/all.rs:14:5
   |
14 | use room::create::CreateEvent;
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::room::create::CreateEvent`
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/collections/all.rs:15:5
   |
15 | use room::guest_access::GuestAccessEvent;
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::room::guest_access::GuestAccessEvent`
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/collections/all.rs:16:5
   |
16 | use room::history_visibility::HistoryVisibilityEvent;
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::room::history_visibility::HistoryVisibilityEvent`
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/collections/all.rs:17:5
   |
17 | use room::join_rules::JoinRulesEvent;
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::room::join_rules::JoinRulesEvent`
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/collections/all.rs:18:5
   |
18 | use room::member::MemberEvent;
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::room::member::MemberEvent`
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/collections/all.rs:19:5
   |
19 | use room::message::MessageEvent;
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::room::message::MessageEvent`
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/collections/all.rs:20:5
   |
20 | use room::name::NameEvent;
   |     ^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::room::name::NameEvent`
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/collections/all.rs:21:5
   |
21 | use room::pinned_events::PinnedEventsEvent;
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::room::pinned_events::PinnedEventsEvent`
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/collections/all.rs:22:5
   |
22 | use room::power_levels::PowerLevelsEvent;
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::room::power_levels::PowerLevelsEvent`
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/collections/all.rs:23:5
   |
23 | use room::redaction::RedactionEvent;
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::room::redaction::RedactionEvent`
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/collections/all.rs:24:5
   |
24 | use room::third_party_invite::ThirdPartyInviteEvent;
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::room::third_party_invite::ThirdPartyInviteEvent`
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/collections/all.rs:25:5
   |
25 | use room::topic::TopicEvent;
   |     ^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::room::topic::TopicEvent`
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/collections/all.rs:26:5
   |
26 | use tag::TagEvent;
   |     ^^^^^^^^^^^^^ help: use `crate`: `crate::tag::TagEvent`
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/collections/all.rs:27:5
   |
27 | use typing::TypingEvent;
   |     ^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::typing::TypingEvent`
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/collections/all.rs:28:5
   |
28 | use {CustomEvent, CustomRoomEvent, CustomStateEvent, EventType};
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::{CustomEvent, CustomRoomEvent, CustomStateEvent, EventType}`
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
 --> src/collections/only.rs:4:5
  |
4 | use call::answer::AnswerEvent;
  |     ^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::call::answer::AnswerEvent`
  |
  = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
  = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
 --> src/collections/only.rs:5:5
  |
5 | use call::candidates::CandidatesEvent;
  |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::call::candidates::CandidatesEvent`
  |
  = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
  = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
 --> src/collections/only.rs:6:5
  |
6 | use call::hangup::HangupEvent;
  |     ^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::call::hangup::HangupEvent`
  |
  = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
  = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
 --> src/collections/only.rs:7:5
  |
7 | use call::invite::InviteEvent;
  |     ^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::call::invite::InviteEvent`
  |
  = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
  = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
 --> src/collections/only.rs:8:5
  |
8 | use direct::DirectEvent;
  |     ^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::direct::DirectEvent`
  |
  = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
  = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
 --> src/collections/only.rs:9:5
  |
9 | use presence::PresenceEvent;
  |     ^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::presence::PresenceEvent`
  |
  = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
  = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/collections/only.rs:10:5
   |
10 | use receipt::ReceiptEvent;
   |     ^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::receipt::ReceiptEvent`
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/collections/only.rs:11:5
   |
11 | use room::message::MessageEvent;
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::room::message::MessageEvent`
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/collections/only.rs:12:5
   |
12 | use room::redaction::RedactionEvent;
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::room::redaction::RedactionEvent`
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/collections/only.rs:13:5
   |
13 | use tag::TagEvent;
   |     ^^^^^^^^^^^^^ help: use `crate`: `crate::tag::TagEvent`
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/collections/only.rs:14:5
   |
14 | use typing::TypingEvent;
   |     ^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::typing::TypingEvent`
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/collections/only.rs:15:5
   |
15 | use {CustomEvent, CustomRoomEvent, EventType};
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::{CustomEvent, CustomRoomEvent, EventType}`
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/macros.rs:36:32
   |
36 |         #[derive(Clone, Debug, Deserialize, Serialize)]
   |                                ^^^^^^^^^^^ help: use `crate`: `crate::Deserialize`
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
   --> src/macros.rs:155:32
    |
155 |         #[derive(Clone, Debug, Deserialize, Serialize)]
    |                                ^^^^^^^^^^^ help: use `crate`: `crate::Deserialize`
    |
    = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
    = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
 --> src/room/member.rs:6:5
  |
6 | use stripped::StrippedState;
  |     ^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::stripped::StrippedState`
  |
  = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
  = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
 --> src/room/power_levels.rs:7:5
  |
7 | use EventType;
  |     ^^^^^^^^^ help: use `crate`: `crate::EventType`
  |
  = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
  = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/stripped.rs:12:5
   |
12 | use room::aliases::AliasesEventContent;
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::room::aliases::AliasesEventContent`
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/stripped.rs:13:5
   |
13 | use room::avatar::AvatarEventContent;
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::room::avatar::AvatarEventContent`
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/stripped.rs:14:5
   |
14 | use room::canonical_alias::CanonicalAliasEventContent;
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::room::canonical_alias::CanonicalAliasEventContent`
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/stripped.rs:15:5
   |
15 | use room::create::CreateEventContent;
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::room::create::CreateEventContent`
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/stripped.rs:16:5
   |
16 | use room::guest_access::GuestAccessEventContent;
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::room::guest_access::GuestAccessEventContent`
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/stripped.rs:17:5
   |
17 | use room::history_visibility::HistoryVisibilityEventContent;
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::room::history_visibility::HistoryVisibilityEventContent`
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/stripped.rs:18:5
   |
18 | use room::join_rules::JoinRulesEventContent;
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::room::join_rules::JoinRulesEventContent`
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/stripped.rs:19:5
   |
19 | use room::member::MemberEventContent;
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::room::member::MemberEventContent`
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/stripped.rs:20:5
   |
20 | use room::name::NameEventContent;
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::room::name::NameEventContent`
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/stripped.rs:21:5
   |
21 | use room::power_levels::PowerLevelsEventContent;
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::room::power_levels::PowerLevelsEventContent`
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/stripped.rs:22:5
   |
22 | use room::third_party_invite::ThirdPartyInviteEventContent;
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::room::third_party_invite::ThirdPartyInviteEventContent`
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/stripped.rs:23:5
   |
23 | use room::topic::TopicEventContent;
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::room::topic::TopicEventContent`
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/stripped.rs:24:5
   |
24 | use EventType;
   |     ^^^^^^^^^ help: use `crate`: `crate::EventType`
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/macros.rs:81:32
   |
81 |         #[derive(Clone, Debug, Deserialize, Serialize)]
   |                                ^^^^^^^^^^^ help: use `crate`: `crate::Deserialize`
   |
note: lint level defined here
  --> src/lib.rs:101:9
   |
101| #![deny(warnings)]
   |         ^^^^^^^^
   = note: #[warn(absolute_paths_not_starting_with_crate)] implied by #[warn(warnings)]
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/macros.rs:81:32
   |
81 |         #[derive(Clone, Debug, Deserialize, Serialize)]
   |                                ^^^^^^^^^^^ help: use `crate`: `crate::Deserialize`
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
 --> src/collections/all.rs:4:5
  |
4 | use call::answer::AnswerEvent;
  |     ^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::call::answer::AnswerEvent`
  |
  = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
  = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
 --> src/collections/all.rs:5:5
  |
5 | use call::candidates::CandidatesEvent;
  |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::call::candidates::CandidatesEvent`
  |
  = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
  = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
 --> src/collections/all.rs:6:5
  |
6 | use call::hangup::HangupEvent;
  |     ^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::call::hangup::HangupEvent`
  |
  = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
  = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
 --> src/collections/all.rs:7:5
  |
7 | use call::invite::InviteEvent;
  |     ^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::call::invite::InviteEvent`
  |
  = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
  = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
 --> src/collections/all.rs:8:5
  |
8 | use direct::DirectEvent;
  |     ^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::direct::DirectEvent`
  |
  = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
  = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
 --> src/collections/all.rs:9:5
  |
9 | use presence::PresenceEvent;
  |     ^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::presence::PresenceEvent`
  |
  = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
  = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/collections/all.rs:10:5
   |
10 | use receipt::ReceiptEvent;
   |     ^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::receipt::ReceiptEvent`
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/collections/all.rs:11:5
   |
11 | use room::aliases::AliasesEvent;
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::room::aliases::AliasesEvent`
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/collections/all.rs:12:5
   |
12 | use room::avatar::AvatarEvent;
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::room::avatar::AvatarEvent`
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/collections/all.rs:13:5
   |
13 | use room::canonical_alias::CanonicalAliasEvent;
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::room::canonical_alias::CanonicalAliasEvent`
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/collections/all.rs:14:5
   |
14 | use room::create::CreateEvent;
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::room::create::CreateEvent`
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/collections/all.rs:15:5
   |
15 | use room::guest_access::GuestAccessEvent;
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::room::guest_access::GuestAccessEvent`
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/collections/all.rs:16:5
   |
16 | use room::history_visibility::HistoryVisibilityEvent;
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::room::history_visibility::HistoryVisibilityEvent`
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/collections/all.rs:17:5
   |
17 | use room::join_rules::JoinRulesEvent;
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::room::join_rules::JoinRulesEvent`
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/collections/all.rs:18:5
   |
18 | use room::member::MemberEvent;
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::room::member::MemberEvent`
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/collections/all.rs:19:5
   |
19 | use room::message::MessageEvent;
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::room::message::MessageEvent`
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/collections/all.rs:20:5
   |
20 | use room::name::NameEvent;
   |     ^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::room::name::NameEvent`
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/collections/all.rs:21:5
   |
21 | use room::pinned_events::PinnedEventsEvent;
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::room::pinned_events::PinnedEventsEvent`
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/collections/all.rs:22:5
   |
22 | use room::power_levels::PowerLevelsEvent;
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::room::power_levels::PowerLevelsEvent`
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/collections/all.rs:23:5
   |
23 | use room::redaction::RedactionEvent;
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::room::redaction::RedactionEvent`
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/collections/all.rs:24:5
   |
24 | use room::third_party_invite::ThirdPartyInviteEvent;
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::room::third_party_invite::ThirdPartyInviteEvent`
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/collections/all.rs:25:5
   |
25 | use room::topic::TopicEvent;
   |     ^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::room::topic::TopicEvent`
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/collections/all.rs:26:5
   |
26 | use tag::TagEvent;
   |     ^^^^^^^^^^^^^ help: use `crate`: `crate::tag::TagEvent`
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/collections/all.rs:27:5
   |
27 | use typing::TypingEvent;
   |     ^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::typing::TypingEvent`
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/collections/all.rs:28:5
   |
28 | use {CustomEvent, CustomRoomEvent, CustomStateEvent, EventType};
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::{CustomEvent, CustomRoomEvent, CustomStateEvent, EventType}`
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
 --> src/collections/only.rs:4:5
  |
4 | use call::answer::AnswerEvent;
  |     ^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::call::answer::AnswerEvent`
  |
  = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
  = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
 --> src/collections/only.rs:5:5
  |
5 | use call::candidates::CandidatesEvent;
  |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::call::candidates::CandidatesEvent`
  |
  = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
  = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
 --> src/collections/only.rs:6:5
  |
6 | use call::hangup::HangupEvent;
  |     ^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::call::hangup::HangupEvent`
  |
  = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
  = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
 --> src/collections/only.rs:7:5
  |
7 | use call::invite::InviteEvent;
  |     ^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::call::invite::InviteEvent`
  |
  = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
  = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
 --> src/collections/only.rs:8:5
  |
8 | use direct::DirectEvent;
  |     ^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::direct::DirectEvent`
  |
  = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
  = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
 --> src/collections/only.rs:9:5
  |
9 | use presence::PresenceEvent;
  |     ^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::presence::PresenceEvent`
  |
  = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
  = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/collections/only.rs:10:5
   |
10 | use receipt::ReceiptEvent;
   |     ^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::receipt::ReceiptEvent`
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/collections/only.rs:11:5
   |
11 | use room::message::MessageEvent;
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::room::message::MessageEvent`
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/collections/only.rs:12:5
   |
12 | use room::redaction::RedactionEvent;
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::room::redaction::RedactionEvent`
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/collections/only.rs:13:5
   |
13 | use tag::TagEvent;
   |     ^^^^^^^^^^^^^ help: use `crate`: `crate::tag::TagEvent`
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/collections/only.rs:14:5
   |
14 | use typing::TypingEvent;
   |     ^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::typing::TypingEvent`
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/collections/only.rs:15:5
   |
15 | use {CustomEvent, CustomRoomEvent, EventType};
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::{CustomEvent, CustomRoomEvent, EventType}`
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/macros.rs:36:32
   |
36 |         #[derive(Clone, Debug, Deserialize, Serialize)]
   |                                ^^^^^^^^^^^ help: use `crate`: `crate::Deserialize`
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/direct.rs:26:9
   |
26 |     use collections;
   |         ^^^^^^^^^^^ help: use `crate`: `crate::collections`
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/direct.rs:27:9
   |
27 |     use direct::{DirectEvent, DirectEventContent};
   |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::direct::{DirectEvent, DirectEventContent}`
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
   --> src/macros.rs:155:32
    |
155 |         #[derive(Clone, Debug, Deserialize, Serialize)]
    |                                ^^^^^^^^^^^ help: use `crate`: `crate::Deserialize`
    |
    = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
    = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
 --> src/room/member.rs:6:5
  |
6 | use stripped::StrippedState;
  |     ^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::stripped::StrippedState`
  |
  = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
  = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/room/pinned_events.rs:22:9
   |
22 |     use room::pinned_events::{PinnedEventsContent, PinnedEventsEvent};
   |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::room::pinned_events::{PinnedEventsContent, PinnedEventsEvent}`
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/room/pinned_events.rs:23:9
   |
23 |     use Event;
   |         ^^^^^ help: use `crate`: `crate::Event`
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/room/pinned_events.rs:24:9
   |
24 |     use EventType;
   |         ^^^^^^^^^ help: use `crate`: `crate::EventType`
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/room/pinned_events.rs:25:9
   |
25 |     use RoomEvent;
   |         ^^^^^^^^^ help: use `crate`: `crate::RoomEvent`
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/room/pinned_events.rs:26:9
   |
26 |     use StateEvent;
   |         ^^^^^^^^^^ help: use `crate`: `crate::StateEvent`
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
 --> src/room/power_levels.rs:7:5
  |
7 | use EventType;
  |     ^^^^^^^^^ help: use `crate`: `crate::EventType`
  |
  = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
  = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/stripped.rs:12:5
   |
12 | use room::aliases::AliasesEventContent;
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::room::aliases::AliasesEventContent`
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/stripped.rs:13:5
   |
13 | use room::avatar::AvatarEventContent;
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::room::avatar::AvatarEventContent`
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/stripped.rs:14:5
   |
14 | use room::canonical_alias::CanonicalAliasEventContent;
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::room::canonical_alias::CanonicalAliasEventContent`
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/stripped.rs:15:5
   |
15 | use room::create::CreateEventContent;
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::room::create::CreateEventContent`
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/stripped.rs:16:5
   |
16 | use room::guest_access::GuestAccessEventContent;
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::room::guest_access::GuestAccessEventContent`
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/stripped.rs:17:5
   |
17 | use room::history_visibility::HistoryVisibilityEventContent;
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::room::history_visibility::HistoryVisibilityEventContent`
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/stripped.rs:18:5
   |
18 | use room::join_rules::JoinRulesEventContent;
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::room::join_rules::JoinRulesEventContent`
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/stripped.rs:19:5
   |
19 | use room::member::MemberEventContent;
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::room::member::MemberEventContent`
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/stripped.rs:20:5
   |
20 | use room::name::NameEventContent;
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::room::name::NameEventContent`
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/stripped.rs:21:5
   |
21 | use room::power_levels::PowerLevelsEventContent;
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::room::power_levels::PowerLevelsEventContent`
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/stripped.rs:22:5
   |
22 | use room::third_party_invite::ThirdPartyInviteEventContent;
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::room::third_party_invite::ThirdPartyInviteEventContent`
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/stripped.rs:23:5
   |
23 | use room::topic::TopicEventContent;
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::room::topic::TopicEventContent`
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
  --> src/stripped.rs:24:5
   |
24 | use EventType;
   |     ^^^^^^^^^ help: use `crate`: `crate::EventType`
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
   = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
   --> src/stripped.rs:260:9
    |
260 |     use room::join_rules::JoinRule;
    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::room::join_rules::JoinRule`
    |
    = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
    = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
   --> src/stripped.rs:261:9
    |
261 |     use room::topic::TopicEventContent;
    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::room::topic::TopicEventContent`
    |
    = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
    = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
   --> src/stripped.rs:263:9
    |
263 |     use EventType;
    |         ^^^^^^^^^ help: use `crate`: `crate::EventType`
    |
    = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
    = note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>

    Finished dev [unoptimized + debuginfo] target(s) in 6.33s

Notes
Output of cargo version: cargo 1.32.0-nightly (5e85ba14a 2018-12-02)
OS: macOS 10.14.1
According to the reply to this comment by killercup this might be more appropriate in rust-lang/rust, but I'm being conservative and filing it here since this is what the cargo output suggests.

Here is the most minimal reproduction I can come up with:
#![warn(rust_2018_compatibility)]
extern crate serde;
#[macro_use]
extern crate serde_derive;

use serde::{Deserialize, Deserializer};

macro_rules! event {
    (
        pub struct $name:ident() {}
    ) => {
        #[derive(Deserialize)]
        pub struct $name {
            pub event_type: $crate::EventType,
        }
    }
}

pub enum EventType {}

event! {
    pub struct CustomEvent() {}
}

impl<'de> Deserialize<'de> for EventType {
    fn deserialize<D>(_deserializer: D) -> Result<Self, D::Error>
    where
        D: Deserializer<'de>,
    {
        unimplemented!()
    }
}

It seems that $crate in serde_derive is confusing things somehow.  cc rust-lang/rust#56622 which seems sort-of related, maybe @dtolnay has some insight?

Thanks for the report @jimmycuadra and the reduction @ehuss! I've moved this over to https://github.com/rust-lang/rust/issues/56683


Add hint for custom CA store locations

The python requests module uses the certifi CA store by default to verify all TLS requests done by it.
This can cause problems if openqa-review has to access resources protected by custom TLS certificates and results in:
openqa_review.browser.DownloadError: Request to https://openqa.example.com/group_overview/110.json was not successful after multiple retries, giving up

guess it's time to disable python-2 tests ;)

nope, not yet. This project should also work as an example how to write python2+python3 compatible code

@okurz I still don't see the reason why my adjustments to the README.md is breaking anything. Could you please help to resolve this or at least merge/review the change?

Yeah, fixed that. Problem was that sorted containers on pip was broken in recent releases but fixed just recently.


typeString (and other keyboard functions) ignore setKeyboardDelay and type slowly

Expected Behavior

typeString should type at the correct speed
Current Behavior

typeString types at a very slow, inconsistent speed
Possible Solution

Using XFlush instead of XSync at https://github.com/octalmage/robotjs/blob/master/src/keypress.c#L25
Steps to Reproduce (for bugs)

robot.setKeyboardDelay(5);
console.time("type");
robot.typeString("This is a test");
console.timeEnd("type");

type: 2.776s

Context

I was just testing it and this happened
Your Environment

RobotJS version: 0.6.0
Node.js version: v16.16.0
npm version: 8.11.0
Operating System: Kubuntu 22.04

I will test the change I recommended locally, and maybe submit a PR if it works.

Yep, it works. Forking

so glad I learned X programming literally yesterday


WebView2: Improve docs for async methods

Accidentally pushed it to master hence open a PR from master to live.

Docs Build status updates of commit 3b5dfb7:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/webview2/gettingstarted/wpf.md
:white_check_mark:Succeeded

microsoft-edge/webview2/reference/dotnet/0-9-538/microsoft-web-webview2-core-corewebview2.md
:white_check_mark:Succeeded

microsoft-edge/webview2/reference/win32/0-9-538/icorewebview2.md
:white_check_mark:Succeeded

microsoft-edge/webview2/reference/win32/0-9-538/icorewebview2devtoolsprotocoleventreceiver.md
:white_check_mark:Succeeded

microsoft-edge/webview2/reference/win32/0-9-538/icorewebview2newwindowrequestedeventargs.md
:white_check_mark:Succeeded

microsoft-edge/webview2/reference/win32/0-9-538/webview2-idl.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 9a872b0:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/devtools-guide-chromium/memory-problems/index.md
:white_check_mark:Succeeded

microsoft-edge/webview2/gettingstarted/wpf.md
:white_check_mark:Succeeded

microsoft-edge/webview2/reference/dotnet/0-9-538/microsoft-web-webview2-core-corewebview2.md
:white_check_mark:Succeeded

microsoft-edge/webview2/reference/win32/0-9-538/icorewebview2.md
:white_check_mark:Succeeded

microsoft-edge/webview2/reference/win32/0-9-538/icorewebview2devtoolsprotocoleventreceiver.md
:white_check_mark:Succeeded

microsoft-edge/webview2/reference/win32/0-9-538/icorewebview2newwindowrequestedeventargs.md
:white_check_mark:Succeeded

microsoft-edge/webview2/reference/win32/0-9-538/webview2-idl.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 6f98ec6:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/devtools-guide-chromium/memory-problems/index.md
:white_check_mark:Succeeded

microsoft-edge/web-platform/site-impacting-changes.md
:white_check_mark:Succeeded

microsoft-edge/webview2/gettingstarted/wpf.md
:white_check_mark:Succeeded

microsoft-edge/webview2/reference/dotnet/0-9-538/microsoft-web-webview2-core-corewebview2.md
:white_check_mark:Succeeded

microsoft-edge/webview2/reference/win32/0-9-538/icorewebview2.md
:white_check_mark:Succeeded

microsoft-edge/webview2/reference/win32/0-9-538/icorewebview2devtoolsprotocoleventreceiver.md
:white_check_mark:Succeeded

microsoft-edge/webview2/reference/win32/0-9-538/icorewebview2newwindowrequestedeventargs.md
:white_check_mark:Succeeded

microsoft-edge/webview2/reference/win32/0-9-538/webview2-idl.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 9a9ea07:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/devtools-guide-chromium/memory-problems/index.md
:white_check_mark:Succeeded

microsoft-edge/web-platform/site-impacting-changes.md
:white_check_mark:Succeeded

microsoft-edge/webview2/gettingstarted/wpf.md
:white_check_mark:Succeeded

microsoft-edge/webview2/reference/dotnet/0-9-538/microsoft-web-webview2-core-corewebview2.md
:white_check_mark:Succeeded

microsoft-edge/webview2/reference/win32/0-9-538/icorewebview2.md
:white_check_mark:Succeeded

microsoft-edge/webview2/reference/win32/0-9-538/icorewebview2devtoolsprotocoleventreceiver.md
:white_check_mark:Succeeded

microsoft-edge/webview2/reference/win32/0-9-538/icorewebview2newwindowrequestedeventargs.md
:white_check_mark:Succeeded

microsoft-edge/webview2/reference/win32/0-9-538/webview2-idl.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit cbd2d27:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/devtools-guide-chromium/memory-problems/index.md
:white_check_mark:Succeeded

microsoft-edge/web-platform/site-impacting-changes.md
:white_check_mark:Succeeded

microsoft-edge/webview2/gettingstarted/wpf.md
:white_check_mark:Succeeded

microsoft-edge/webview2/reference/dotnet/0-9-538/microsoft-web-webview2-core-corewebview2.md
:white_check_mark:Succeeded

microsoft-edge/webview2/reference/win32/0-9-538/icorewebview2.md
:white_check_mark:Succeeded

microsoft-edge/webview2/reference/win32/0-9-538/icorewebview2devtoolsprotocoleventreceiver.md
:white_check_mark:Succeeded

microsoft-edge/webview2/reference/win32/0-9-538/icorewebview2newwindowrequestedeventargs.md
:white_check_mark:Succeeded

microsoft-edge/webview2/reference/win32/0-9-538/webview2-idl.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 2fa526d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/devtools-guide-chromium/memory-problems/index.md
:white_check_mark:Succeeded

microsoft-edge/web-platform/site-impacting-changes.md
:white_check_mark:Succeeded

microsoft-edge/webview2/gettingstarted/wpf.md
:white_check_mark:Succeeded

microsoft-edge/webview2/reference/dotnet/0-9-538/microsoft-web-webview2-core-corewebview2.md
:white_check_mark:Succeeded

microsoft-edge/webview2/reference/win32/0-9-538/icorewebview2.md
:white_check_mark:Succeeded

microsoft-edge/webview2/reference/win32/0-9-538/icorewebview2devtoolsprotocoleventreceiver.md
:white_check_mark:Succeeded

microsoft-edge/webview2/reference/win32/0-9-538/icorewebview2newwindowrequestedeventargs.md
:white_check_mark:Succeeded

microsoft-edge/webview2/reference/win32/0-9-538/webview2-idl.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 20fddd5:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/devtools-guide-chromium/memory-problems/index.md
:white_check_mark:Succeeded

microsoft-edge/web-platform/site-impacting-changes.md
:white_check_mark:Succeeded

microsoft-edge/webview2/gettingstarted/wpf.md
:white_check_mark:Succeeded

microsoft-edge/webview2/reference/dotnet/0-9-538/microsoft-web-webview2-core-corewebview2.md
:white_check_mark:Succeeded

microsoft-edge/webview2/reference/win32/0-9-538/icorewebview2.md
:white_check_mark:Succeeded

microsoft-edge/webview2/reference/win32/0-9-538/icorewebview2devtoolsprotocoleventreceiver.md
:white_check_mark:Succeeded

microsoft-edge/webview2/reference/win32/0-9-538/icorewebview2newwindowrequestedeventargs.md
:white_check_mark:Succeeded

microsoft-edge/webview2/reference/win32/0-9-538/webview2-idl.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 2555851:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/devtools-guide-chromium/memory-problems/index.md
:white_check_mark:Succeeded

microsoft-edge/web-platform/site-impacting-changes.md
:white_check_mark:Succeeded

microsoft-edge/webview2/gettingstarted/wpf.md
:white_check_mark:Succeeded

microsoft-edge/webview2/reference/dotnet/0-9-538/microsoft-web-webview2-core-corewebview2.md
:white_check_mark:Succeeded

microsoft-edge/webview2/reference/win32/0-9-538/icorewebview2.md
:white_check_mark:Succeeded

microsoft-edge/webview2/reference/win32/0-9-538/icorewebview2devtoolsprotocoleventreceiver.md
:white_check_mark:Succeeded

microsoft-edge/webview2/reference/win32/0-9-538/icorewebview2newwindowrequestedeventargs.md
:white_check_mark:Succeeded

microsoft-edge/webview2/reference/win32/0-9-538/webview2-idl.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 5fa2adf:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/devtools-guide-chromium/memory-problems/index.md
:white_check_mark:Succeeded

microsoft-edge/web-platform/site-impacting-changes.md
:white_check_mark:Succeeded

microsoft-edge/webview2/gettingstarted/wpf.md
:white_check_mark:Succeeded

microsoft-edge/webview2/reference/dotnet/0-9-538/microsoft-web-webview2-core-corewebview2.md
:white_check_mark:Succeeded

microsoft-edge/webview2/reference/win32/0-9-538/icorewebview2.md
:white_check_mark:Succeeded

microsoft-edge/webview2/reference/win32/0-9-538/icorewebview2devtoolsprotocoleventreceiver.md
:white_check_mark:Succeeded

microsoft-edge/webview2/reference/win32/0-9-538/icorewebview2newwindowrequestedeventargs.md
:white_check_mark:Succeeded

microsoft-edge/webview2/reference/win32/0-9-538/webview2-idl.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit e2b3856:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/devtools-guide-chromium/memory-problems/index.md
:white_check_mark:Succeeded

microsoft-edge/web-platform/site-impacting-changes.md
:white_check_mark:Succeeded

microsoft-edge/webview2/gettingstarted/wpf.md
:white_check_mark:Succeeded

microsoft-edge/webview2/reference/dotnet/0-9-538/microsoft-web-webview2-core-corewebview2.md
:white_check_mark:Succeeded

microsoft-edge/webview2/reference/win32/0-9-538/icorewebview2.md
:white_check_mark:Succeeded

microsoft-edge/webview2/reference/win32/0-9-538/icorewebview2devtoolsprotocoleventreceiver.md
:white_check_mark:Succeeded

microsoft-edge/webview2/reference/win32/0-9-538/icorewebview2newwindowrequestedeventargs.md
:white_check_mark:Succeeded

microsoft-edge/webview2/reference/win32/0-9-538/webview2-idl.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit e2b3856:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/devtools-guide-chromium/memory-problems/index.md
:white_check_mark:Succeeded

microsoft-edge/web-platform/site-impacting-changes.md
:white_check_mark:Succeeded

microsoft-edge/webview2/gettingstarted/wpf.md
:white_check_mark:Succeeded

microsoft-edge/webview2/reference/dotnet/0-9-538/microsoft-web-webview2-core-corewebview2.md
:white_check_mark:Succeeded

microsoft-edge/webview2/reference/win32/0-9-538/icorewebview2.md
:white_check_mark:Succeeded

microsoft-edge/webview2/reference/win32/0-9-538/icorewebview2devtoolsprotocoleventreceiver.md
:white_check_mark:Succeeded

microsoft-edge/webview2/reference/win32/0-9-538/icorewebview2newwindowrequestedeventargs.md
:white_check_mark:Succeeded

microsoft-edge/webview2/reference/win32/0-9-538/webview2-idl.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit e12c9e9:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/devtools-guide-chromium/memory-problems/index.md
:white_check_mark:Succeeded

microsoft-edge/hosting/chakra-hosting/hosting-the-javascript-runtime.md
:white_check_mark:Succeeded

microsoft-edge/hosting/chakra-hosting/javascript-runtime-typedefs-constants-and-enumerations.md
:white_check_mark:Succeeded

microsoft-edge/hosting/chakra-hosting/jsgettypedarrayinfo-function.md
:white_check_mark:Succeeded

microsoft-edge/hosting/chakra-hosting/jsinstanceof-function.md
:white_check_mark:Succeeded

microsoft-edge/hosting/chakra-hosting/jsparseserializedscriptwithcallback-function.md
:white_check_mark:Succeeded

microsoft-edge/hosting/chakra-hosting/jsrunserializedscriptwithcallback-function.md
:white_check_mark:Succeeded

microsoft-edge/hosting/chakra-hosting/jsserializedscriptloadsourcecallback-typedef.md
:white_check_mark:Succeeded

microsoft-edge/hosting/chakra-hosting/jsserializedscriptunloadcallback-typedef.md
:white_check_mark:Succeeded

microsoft-edge/hosting/chakra-hosting/jssetcontextdata-function.md
:white_check_mark:Succeeded

microsoft-edge/hosting/chakra-hosting/reference-javascript-runtime.md
:white_check_mark:Succeeded

microsoft-edge/hosting/chakra-hosting/targeting-edge-vs-legacy-engines-in-jsrt-apis.md
:white_check_mark:Succeeded

microsoft-edge/hosting/includes/deprecation-note.md
:white_check_mark:Succeeded

microsoft-edge/hosting/javascript-runtime-hosting.md
:white_check_mark:Succeeded

microsoft-edge/hosting/webview.md
:white_check_mark:Succeeded

microsoft-edge/hosting/webview/DeferredPermissionRequest.md
:white_check_mark:Succeeded

microsoft-edge/hosting/webview/FocusNavigationEvent.md
:white_check_mark:Succeeded

microsoft-edge/hosting/webview/LongRunningScriptDetectedEvent.md
:white_check_mark:Succeeded

microsoft-edge/hosting/webview/MSWebViewAsyncOperation.md
:white_check_mark:Succeeded

microsoft-edge/hosting/webview/MSWebViewProcess.md
:white_check_mark:Succeeded

microsoft-edge/hosting/webview/MSWebViewSettings.md
:white_check_mark:Succeeded

microsoft-edge/hosting/webview/NavigationCompletedEvent.md
:white_check_mark:Succeeded

microsoft-edge/hosting/webview/NavigationEvent.md
:white_check_mark:Succeeded

microsoft-edge/hosting/webview/NavigationEventWithReferrer.md
:white_check_mark:Succeeded

microsoft-edge/hosting/webview/PermissionRequest.md
:white_check_mark:Succeeded

microsoft-edge/hosting/webview/PermissionRequestedEvent.md
:white_check_mark:Succeeded

microsoft-edge/hosting/webview/ScriptNotifyEvent.md
:white_check_mark:Succeeded

microsoft-edge/hosting/webview/UnviewableContentIdentifiedEvent.md
:white_check_mark:Succeeded

microsoft-edge/hosting/webview/WebResourceRequestedEvent.md
:white_check_mark:Succeeded

microsoft-edge/web-platform/site-impacting-changes.md
:white_check_mark:Succeeded

microsoft-edge/webview2/gettingstarted/wpf.md
:white_check_mark:Succeeded

microsoft-edge/webview2/reference/dotnet/0-9-538/microsoft-web-webview2-core-corewebview2.md
:white_check_mark:Succeeded

microsoft-edge/webview2/reference/win32/0-9-538/icorewebview2.md
:white_check_mark:Succeeded

microsoft-edge/webview2/reference/win32/0-9-538/icorewebview2devtoolsprotocoleventreceiver.md
:white_check_mark:Succeeded

microsoft-edge/webview2/reference/win32/0-9-538/icorewebview2newwindowrequestedeventargs.md
:white_check_mark:Succeeded

microsoft-edge/webview2/reference/win32/0-9-538/webview2-idl.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


[Q] How to remove all null packets from TS

Is it possible to remove all null packets from input TS? Input TS is CBR, but usefull payload may be CBR or VBR. Tried 'reduce' plugin, but have no luck.

Use tsp .. -P filter -n -p 0x1FFF ...
Please RTFM for more details.

Thank you very much! That is what I need! Forgot that null packets have pid 0x1FFF.


Get get-address command to 100% test coverage

Bounty: 100 tokens
The scope of this Issue is to add tests to the get-address tests in order to achieve 100% test coverage. It is currently at 70% test coverage. Make any changes needed to the get-address command necessary to facilitate mocks and test coverage.

The burn-tokens tests have achieved 100% test coverage. This provides a good example of the patterns that will be needed to complete this Issue.

This YouTube video covers JavaScript design and testing patterns that should be followed.

This YouTube video shows how to generate test coverage reports. These reports will help you identify the lines that are not being covered by current tests.

Acceptance Criteria

A Pull Request (PR) should be submitted that meet the above criteria. The PR should be from a branch and not a fork. In order to create a branch, you'll need commit to access to this repository.
All tests should pass when running npm test.
The command targeted by this Issue should show 100% test coverage when tests are run.
All commands should still be fully functional.
The bounty will be awarded upon successfully merging of the PR into the master branch.

This pull request resolves this Issue.
https://github.com/Permissionless-Software-Foundation/slp-cli-wallet/pull/3


Removing fleetsync controller

The fleetsync controller has been moved to https://github.com/nephio-project/porch-fleets
This means it can be removed from the porch controllers codebase

/retest

/lgtm


Add github token in dependencies install CI step

Codecov Report

Merging #65 (abcd6df) into master (deaf19c) will increase coverage by 0.09%.
The diff coverage is n/a.

:exclamation: Current head abcd6df differs from pull request most recent head 34fa5ec. Consider uploading reports for the commit 34fa5ec to get more accurate results

@@             Coverage Diff             @@
##             master     #65      +/-   ##
===========================================
+ Coverage      9.52%   9.61%   +0.09%
  Complexity       57      57
===========================================
  Files             9       9
  Lines           252     260       +8
===========================================
+ Hits             24      25       +1
- Misses          228     235       +7

Impacted Files
Coverage Δ

...emVerCheckerGit/Console/Command/SuggestCommand.php
22.93% <0.00%> (-0.37%)
:arrow_down:

...emVerCheckerGit/Console/Command/CompareCommand.php
0.00% <0.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Best way to recommend an explorable to add?

Hi!
Love the site :).
I may have failed at searching, but I couldn't find anywhere on https://explorabl.es/ or this repo for your preferred method for having additional explorabl.es suggested to be added? Do you have a preferred way for people to contact you to suggest something?
thanks!
Zan

Also... is there a particular criteria for what you're looking for? Or is it pretty open-ended?

+1 to this question. I recently discovered some great examples on https://method.ac/ and thought it would be good to have them included.

+1 to this question. I have an aspiring explorable, and I wanted to see if it would qualify.

This is an interesting point ! I think Nicky is on Hiatus, so perhaps it would be worthwhile to fork the website and create this feature that allows the community to add more Explorables !


The CT pickle structure needs to be changed

the pickle file is created in cdisc library service get_codelist_terms_map() function.  There does not appear to be any functions reliant on this pickle structure except for valid_terms which is what is used by the valid_codelist_term.
changing the structure to allow for codelist level vs term level checks would be ideal as well as using dict instead of lists for easier fetching of desired information.  NCI, extensibility would need to be returned by default still.

Ideally this structure would facilitate making the uses_valid_codelist_terms operator into something more generalizable, parameters could potentially look as follows:
level: codelist // term // both
check: [synonyms/preferred terms/submission value/NCI value]
allowing more granular control on the return for various checks.  This would also likely warrant a name change, potentially 'codelist_validation'


Step 3 is asking to tag the PKS Control VM before it's created

Following the steps at https://docs.pivotal.io/runtimes/pks/1-1/gcp-api-load-balancer.html Step 3 is asking that the PKS controller VM be tagger, but the PKS tile has not been imported yet so the VM has not yet been created.

+1
This wasn't like this in previous versions of the docs (extracted from the cookbook)
Step 3 (https://docs.pivotal.io/runtimes/pks/1-1/gcp-api-load-balancer.html#step-3:-create-a-network-tag-for-the-firewall-rule) can only happen after installing PKS.
It should be moved into Step 5 here: https://docs.pivotal.io/runtimes/pks/1-0/installing-pks.html#-step-5:-configure-external-load-balancer

Hi @asaikali @jaimegag. We updated the Configuring a GCP Load Balancer for the PKS API and Installing and Configuring PKS topics:

https://docs.pivotal.io/runtimes/pks/1-1/gcp-api-load-balancer.html#install

https://docs.pivotal.io/runtimes/pks/1-1/installing-pks.html#loadbalancer-pks-api


Dialog has no EventHandler for Left button.

Describe the bug
Dialog has EventHandler for ButtonRightClick but not for ButtonLeftClick
Additional context
As I mentioned here, their event handler code for the buttons is different, yes they are different controls, but the purpose of the buttons is the same in both controls - one for action the other for cancel.

As far as I can see, the left button is just Click. Not very obvious I agree :D
To answer your previous question, this can happen when the code is written at different times. I use the MessageBox method (i.e. switch/case)


The camera starts centered on the absolute map center upon loading a save

The expected behavior is that the camera starts centered on the capital. Unsure of how to fix this tbh, any ideas?

We could register a function with this event: Events.LoadScreenClose() that centers the camera, similar to this function in CityPanel.lua:
-- ===========================================================================
--	Recenter camera on city
-- ===========================================================================
function RecenterCameraOnCity()
local kCity:table = UI.GetHeadSelectedCity();
UI.LookAtPlot( kCity:GetX(), kCity:GetY() );
end

@RatchetJ Seems good, it can even go in CityPanel since the function already exist there

I'll get started on this. It seems like this issue also exists on a fresh game as well. In that case should the camera start on the starting settler?

Yes, good thinking on that one

Fixed in PR #86


Apply topology options also to sub-topologies

Subtopologies inherit the applied options if the keys are the same.
The labels are still determined by the topology itself.
Fixes #1221

Nice, LGTM


--inline-scripts breaks valid code

vulcanize --inline-scripts replaces for(g=d+e;g-->d;) with for(g=d+e;g--\x3ed;), which results in parse error.
Encountered while trying to use https://github.com/OpenKieler/klayjs/blob/master/klay.js - Java library compiled with GWT.

duplicate of https://github.com/Polymer/polymer-bundler/issues/304

Thanks for pointing that out @arturparkhisenko Closed as duplicate. @gelraen you may want to subscribe to #304


hack/build.sh fails latest version of shellcheck

The shellcheck output gives the problem and the fix
In ./hack/build.sh line 110:
if [[ "${NDM_AGENT_DEV}" ]]; then
    ^----------------^ SC2244: Prefer explicit -n to check non-empty string (or use =/-ne to check boolean/integer).

Did you mean:
if [[ -n "${NDM_AGENT_DEV}" ]]; then

For more information:
https://www.shellcheck.net/wiki/SC2244

SC2244 was added just a few days ago to shellcheck.
Should the "latest" version of shellcheck continue to be used, or should the latest release be chosen manually? If the latter then the relevant line in the Makefile could be changed from
wget -c 'https://goo.gl/ZzKHFv' -O - | tar -xvJ -C /tmp/
to
wget -c 'https://storage.googleapis.com/shellcheck/shellcheck-v0.6.0.linux.x86_64.tar.xz' -O - | tar -xvJ -C /tmp/

Fixed in #193

Thanks @michael-db for reporting. Issue is fixed and merged to master.


Added information about resource selection

This is a summary of our discussion from our meeting on resource selection. I do need some help in making sure I am correct in describing how nf-core operates (since I believe nf-core creates a separate config file for every pipeline defining resources, but we wanted a shared config file, am I correct?).
Please let me know if you have any other comments or suggestions.

You are correct! The basic config file it spits out has some boiler plate labels (which you can choose to alter or use), and the config file can live with the pipeline and a seperate config file can be specified at the command line to overwrite the values associated with those labels.
One thing we may need (for developers) is a way to lint our code to verify that all labels for our institution show up in the modules. One source of inspiration/information we could use is some of the "institution configs" shared on the nf-core website here: https://github.com/nf-core/configs

You are correct! The basic config file it spits out has some boiler plate labels (which you can choose to alter or use), and the config file can live with the pipeline and a seperate config file can be specified at the command line to overwrite the values associated with those labels.
One thing we may need (for developers) is a way to lint our code to verify that all labels for our institution show up in the modules. One source of inspiration/information we could use is some of the "institution configs" shared on the nf-core website here: https://github.com/nf-core/configs

Thanks. So, do you think the idea is that we could keep the base.config produced by nextflow, but we ignore that file when executing in WES and use a shared config file that we define (with base.config useful if you are executing outside of WES)?
I agree we would need a way to lint code to make sure it confirms to our standards. I'll have to check out the "institution configs".

I guess the we can use a shared config is just have everything in a wes_azure profile, or wes_local_cluster profile and have WES select those profiles depending on where the pipeline is executed.

That seems like a good idea to me, we keep the base.config and let the and replace it with the WES shared config. I also agree with your idea of having the WES local and Azure configs.
I would like to keep a base.conf with each pipeline as well, so that when a pipeline is released to the public there will be an obvious way to trun the pipeline.

Thanks so much for all of your input and the great discussion. I am merging this in.
@mattheww95 I added an issue about linting code here https://github.com/phac-nml/pipeline-standards/issues/2


Sort Julia.jl

Many packages are too old for Julia v1.5+. I would like to sort it out.

[x] Import svaksha's repo as a Git submodule. Dependabot could inform me when there is an update.
[x] ODC Open Database License (ODbL) and CODE LICENSE : AGPLv3+ (I'm only using their data, not code)
[x] Mark packages unable to run in Julia v1.5+
[x] Docsify template

It's on https://github.com/sosiristseng/JuliaResources


Make it easy to use Apollo with Redux directly

Continuing from: https://github.com/apollostack/react-apollo/issues/26

@abhiaiyer91 assigned this to you! Let me know if I can help you get set up in any way.

I think it would be prudent, if we document this interface, to make it clear that this is a more internal API, and possibly more likely to change. In the future, I think it would be great to make this stuff a separate NPM module that has internal utilities, and make the client library a nice wrapper around all of the reducers etc.

:+1: ing this, because it might be similar to connecting apollo with Vuex and Vue, so I'd like to keep track of any progress.
https://github.com/vuejs/vuex
Scott