Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upLet EventSource fail fast on bad schemes #25695
Conversation
highfive
commented
Feb 5, 2020
|
Heads up! This PR modifies the following files:
|
| @@ -472,7 +483,7 @@ impl EventSource { | |||
| let event_source = event_source.root(); | |||
| if event_source.ready_state.get() != ReadyState::Closed { | |||
| event_source.ready_state.set(ReadyState::Closed); | |||
| event_source.upcast::<EventTarget>().fire_event(atom!("error")); | |||
| event_source.upcast::<EventTarget>().fire_event(atom!("error")); | |||
This comment has been minimized.
This comment has been minimized.
CYBAI
Feb 6, 2020
Collaborator
Heh, I'm surprised fmt didn't complain about this
This comment has been minimized.
This comment has been minimized.
pshaughn
Feb 6, 2020
Author
Member
This keeps happening to me in particular! My workflow is to just type stuff in emacs without thinking about indents, then run mach fmt afterwards.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
|
Seems ok to me, r=me if fmt is happy. @bors-servo delegate+ |
|
|
|
@bors-servo r=nox |
|
|
|
hold on, I didn't fix the indentation yet |
|
@bors-servo r- |
|
@bors-servo r=nox |
|
|
Let EventSource fail fast on bad schemes <!-- Please describe your changes on the following line: --> EventSource went into an infinite reconnect loop in some cases where tests wanted it to go into a hard error state; this addresses the cases where that happens because the url isn't even http(s) and will thus definitely never result in an event stream. web-platform-tests/wpt#4311 suggests the tests might just be too picky here; the spec does use the word "may" on relevant behavior. --- <!-- Thank you for contributing to Servo! Please replace each `[ ]` by `[X]` when the step is complete, and replace `___` with appropriate data: --> - [X] `./mach build -d` does not report any errors - [X] `./mach test-tidy` does not report any errors - [X] These changes fix #25692 <!-- Either: --> - [X] There are tests for these changes <!-- Also, please make sure that "Allow edits from maintainers" checkbox is checked, so that we can help you if you get stuck somewhere along the way.--> <!-- Pull requests that do not address these steps are welcome, but they will require additional verification as part of the review process. -->
|
|
|
@bors-servo retry |
Let EventSource fail fast on bad schemes <!-- Please describe your changes on the following line: --> EventSource went into an infinite reconnect loop in some cases where tests wanted it to go into a hard error state; this addresses the cases where that happens because the url isn't even http(s) and will thus definitely never result in an event stream. web-platform-tests/wpt#4311 suggests the tests might just be too picky here; the spec does use the word "may" on relevant behavior. --- <!-- Thank you for contributing to Servo! Please replace each `[ ]` by `[X]` when the step is complete, and replace `___` with appropriate data: --> - [X] `./mach build -d` does not report any errors - [X] `./mach test-tidy` does not report any errors - [X] These changes fix #25692 <!-- Either: --> - [X] There are tests for these changes <!-- Also, please make sure that "Allow edits from maintainers" checkbox is checked, so that we can help you if you get stuck somewhere along the way.--> <!-- Pull requests that do not address these steps are welcome, but they will require additional verification as part of the review process. -->
|
|
|
@bors-servo retry |
Let EventSource fail fast on bad schemes <!-- Please describe your changes on the following line: --> EventSource went into an infinite reconnect loop in some cases where tests wanted it to go into a hard error state; this addresses the cases where that happens because the url isn't even http(s) and will thus definitely never result in an event stream. web-platform-tests/wpt#4311 suggests the tests might just be too picky here; the spec does use the word "may" on relevant behavior. --- <!-- Thank you for contributing to Servo! Please replace each `[ ]` by `[X]` when the step is complete, and replace `___` with appropriate data: --> - [X] `./mach build -d` does not report any errors - [X] `./mach test-tidy` does not report any errors - [X] These changes fix #25692 <!-- Either: --> - [X] There are tests for these changes <!-- Also, please make sure that "Allow edits from maintainers" checkbox is checked, so that we can help you if you get stuck somewhere along the way.--> <!-- Pull requests that do not address these steps are welcome, but they will require additional verification as part of the review process. -->
|
|
pshaughn commentedFeb 5, 2020
•
edited
EventSource went into an infinite reconnect loop in some cases where tests wanted it to go into a hard error state; this addresses the cases where that happens because the url isn't even http(s) and will thus definitely never result in an event stream.
web-platform-tests/wpt#4311 suggests the tests might just be too picky here; the spec does use the word "may" on relevant behavior.
./mach build -ddoes not report any errors./mach test-tidydoes not report any errors