Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[hololens] Handle servo panic #23983

Merged
merged 1 commit into from Aug 21, 2019
Merged

Conversation

paulrouget
Copy link
Contributor

@paulrouget paulrouget commented Aug 16, 2019

Depends on #23981

Fix #23937

I've used a different approach than checking the return code of every single functions.
Basically calling a C function on panic.

That means the errors are not recoverable. I think it's fine for now.

I'm open to any other better approach.

@jdm what do you think?


This change is Reviewable

@highfive highfive added the S-awaiting-review There is new code that needs to be reviewed. label Aug 16, 2019
@highfive
Copy link

warning Warning warning

  • These commits modify unsafe code. Please review it carefully!

@ferjm
Copy link
Contributor

ferjm commented Aug 19, 2019

r? @jdm

@highfive highfive assigned jdm and unassigned ferjm Aug 19, 2019
This was referenced Aug 19, 2019
@jdm
Copy link
Member

jdm commented Aug 19, 2019

This seems like a useful path forward.

@jdm jdm added S-blocked-on-external Something, somewhere else, needs to happen before this PR can be merged. and removed S-awaiting-review There is new code that needs to be reviewed. labels Aug 19, 2019
@highfive highfive added the S-awaiting-review There is new code that needs to be reviewed. label Aug 20, 2019
@jdm
Copy link
Member

jdm commented Aug 20, 2019

This needs a mach fmt.

@jdm jdm added S-fails-tidy `./mach test-tidy` reported errors. and removed S-awaiting-review There is new code that needs to be reviewed. labels Aug 20, 2019
@highfive highfive added the S-awaiting-review There is new code that needs to be reviewed. label Aug 21, 2019
@jdm
Copy link
Member

jdm commented Aug 21, 2019

@bors-servo r+

@bors-servo
Copy link
Contributor

📌 Commit 3933b43 has been approved by jdm

@highfive highfive added S-awaiting-merge The PR is in the process of compiling and running tests on the automated CI. and removed S-awaiting-review There is new code that needs to be reviewed. labels Aug 21, 2019
@bors-servo
Copy link
Contributor

⌛ Testing commit 3933b43 with merge 5f89dc8...

bors-servo pushed a commit that referenced this pull request Aug 21, 2019
[hololens] Handle servo panic

Depends on #23981

Fix #23937

I've used a different approach than checking the return code of every single functions.
Basically calling a C function on panic.

That means the errors are not recoverable. I think it's fine for now.

I'm open to any other better approach.

@jdm what do you think?

<!-- Reviewable:start -->
---
This change is [<img src="https://reviewable.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/servo/23983)
<!-- Reviewable:end -->
@bors-servo
Copy link
Contributor

☀️ Test successful - linux-rel-css, linux-rel-wpt, status-taskcluster
Approved by: jdm
Pushing 5f89dc8 to master...

bors-servo pushed a commit that referenced this pull request Aug 21, 2019
Do not leak the CAPI strings

Depends on #23983

I haven't remove the mem::forget here: https://github.com/servo/servo/blob/6528c0d9b7b36fbdffc29bab99e0066b83a7f970/ports/libsimpleservo/capi/src/lib.rs#L228

What would be the right approach in that specific case?

<!-- Reviewable:start -->
---
This change is [<img src="https://reviewable.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/servo/23998)
<!-- Reviewable:end -->
@bors-servo bors-servo merged commit 3933b43 into servo:master Aug 21, 2019
@highfive highfive removed the S-awaiting-merge The PR is in the process of compiling and running tests on the automated CI. label Aug 21, 2019
This was referenced Aug 21, 2019
bors-servo pushed a commit that referenced this pull request Aug 22, 2019
Do not leak the CAPI strings

Depends on #23983

I haven't remove the mem::forget here: https://github.com/servo/servo/blob/6528c0d9b7b36fbdffc29bab99e0066b83a7f970/ports/libsimpleservo/capi/src/lib.rs#L228

What would be the right approach in that specific case?

<!-- Reviewable:start -->
---
This change is [<img src="https://reviewable.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/servo/23998)
<!-- Reviewable:end -->
bors-servo pushed a commit that referenced this pull request Aug 22, 2019
Missing C methods

Depends on #23983

Fix #23969

<!-- Reviewable:start -->
---
This change is [<img src="https://reviewable.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/servo/23999)
<!-- Reviewable:end -->
bors-servo pushed a commit that referenced this pull request Aug 23, 2019
Missing C methods

Depends on #23983

Fix #23969

<!-- Reviewable:start -->
---
This change is [<img src="https://reviewable.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/servo/23999)
<!-- Reviewable:end -->
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
S-blocked-on-external Something, somewhere else, needs to happen before this PR can be merged. S-fails-tidy `./mach test-tidy` reported errors.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Make UWP embedding handle embedding API failures
5 participants