Brandon Castellano would like Owners Override to review this change.
[version_history] Retire API level 26
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Code-Review | +2 |
_ => panic!("unhandled log format"),I think I prefer to undo and leave the previous exhaustive match:
```
// TODO(https://fxbug.dev/401548725): Remove this from the FIDL definition.
Format::Text => Err(AccessorError::UnsupportedFormat),
Format::Cbor => unreachable!("CBOR is not supported for logs"),
```
They aren't perfect error messages by any means, but I prefer that we get compiler errors if we adjust this enum.
persist: Some(true),I think `persist` could now be false on this path, right? So we should do `persist: Some(persist),`
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
I think I prefer to undo and leave the previous exhaustive match:
```
// TODO(https://fxbug.dev/401548725): Remove this from the FIDL definition.
Format::Text => Err(AccessorError::UnsupportedFormat),
Format::Cbor => unreachable!("CBOR is not supported for logs"),
```They aren't perfect error messages by any means, but I prefer that we get compiler errors if we adjust this enum.
Restored.
I think `persist` could now be false on this path, right? So we should do `persist: Some(persist),`
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Looks like there are a bunch of files with non-mechanical changes that haven't been reviewed, which means it seems too early for owners-override.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
The main thing
Looks like there are a bunch of files with non-mechanical changes that haven't been reviewed, which means it seems too early for owners-override.
I think I can speak to the RTC changes, they look good to me. The power changes could maybe use another set of eyes. @mbru...@google.com, can you take a look? After that I can provide OO+1.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Hunter FreyerLooks like there are a bunch of files with non-mechanical changes that haven't been reviewed, which means it seems too early for owners-override.
I think I can speak to the RTC changes, they look good to me. The power changes could maybe use another set of eyes. @mbru...@google.com, can you take a look? After that I can provide OO+1.
fxbug.dev/385742868 is still open. Looks like a number of changes have been landed but it still remains open. Maybe @martin...@google.com or @frou...@google.com know the state of things there?
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Hunter FreyerLooks like there are a bunch of files with non-mechanical changes that haven't been reviewed, which means it seems too early for owners-override.
Michael BrunsonI think I can speak to the RTC changes, they look good to me. The power changes could maybe use another set of eyes. @mbru...@google.com, can you take a look? After that I can provide OO+1.
fxbug.dev/385742868 is still open. Looks like a number of changes have been landed but it still remains open. Maybe @martin...@google.com or @frou...@google.com know the state of things there?
I guess I would have expected the CL to also remove the definitions in the //sdk/fidl/fuchsia.hardware.power.statecontrol/*.fidl files. That's what that cleanup issue is tracking, deleting the server implementation and the FIDL definitions.
| Code-Review | +1 |
Hunter FreyerLooks like there are a bunch of files with non-mechanical changes that haven't been reviewed, which means it seems too early for owners-override.
Michael BrunsonI think I can speak to the RTC changes, they look good to me. The power changes could maybe use another set of eyes. @mbru...@google.com, can you take a look? After that I can provide OO+1.
Francois Rousseaufxbug.dev/385742868 is still open. Looks like a number of changes have been landed but it still remains open. Maybe @martin...@google.com or @frou...@google.com know the state of things there?
I guess I would have expected the CL to also remove the definitions in the //sdk/fidl/fuchsia.hardware.power.statecontrol/*.fidl files. That's what that cleanup issue is tracking, deleting the server implementation and the FIDL definitions.
I've been holding on to fxbug.dev/385742868 waiting for F26 to be retired so that we could delete the logic backing the old FIDL definitions. So from that perspective, the deletions in `src/power/shutdown-shim` LGTM. But +1 to what Francois said, I'm a little confused that the FIDL definitions aren't being deleted as part of this CL.
Change-Id: Iffe85780eb923a31e4c0fc1f0d4f89c24e719310nit: would you mind adding `Bug: 385742868` to this CL description? You're performing a lot of the cleanup in scope of that bug (thanks by the way!)
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Hunter FreyerLooks like there are a bunch of files with non-mechanical changes that haven't been reviewed, which means it seems too early for owners-override.
Michael BrunsonI think I can speak to the RTC changes, they look good to me. The power changes could maybe use another set of eyes. @mbru...@google.com, can you take a look? After that I can provide OO+1.
Francois Rousseaufxbug.dev/385742868 is still open. Looks like a number of changes have been landed but it still remains open. Maybe @martin...@google.com or @frou...@google.com know the state of things there?
Jeff MartinI guess I would have expected the CL to also remove the definitions in the //sdk/fidl/fuchsia.hardware.power.statecontrol/*.fidl files. That's what that cleanup issue is tracking, deleting the server implementation and the FIDL definitions.
I've been holding on to fxbug.dev/385742868 waiting for F26 to be retired so that we could delete the logic backing the old FIDL definitions. So from that perspective, the deletions in `src/power/shutdown-shim` LGTM. But +1 to what Francois said, I'm a little confused that the FIDL definitions aren't being deleted as part of this CL.
I don't think we usually remove FIDL definitions in the same CL that we retire a given API level. Could this be done in a follow-up?
nit: would you mind adding `Bug: 385742868` to this CL description? You're performing a lot of the cleanup in scope of that bug (thanks by the way!)
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
The main thing
What an insightful comment this was.
Hunter FreyerLooks like there are a bunch of files with non-mechanical changes that haven't been reviewed, which means it seems too early for owners-override.
Michael BrunsonI think I can speak to the RTC changes, they look good to me. The power changes could maybe use another set of eyes. @mbru...@google.com, can you take a look? After that I can provide OO+1.
Francois Rousseaufxbug.dev/385742868 is still open. Looks like a number of changes have been landed but it still remains open. Maybe @martin...@google.com or @frou...@google.com know the state of things there?
Jeff MartinI guess I would have expected the CL to also remove the definitions in the //sdk/fidl/fuchsia.hardware.power.statecontrol/*.fidl files. That's what that cleanup issue is tracking, deleting the server implementation and the FIDL definitions.
Brandon CastellanoI've been holding on to fxbug.dev/385742868 waiting for F26 to be retired so that we could delete the logic backing the old FIDL definitions. So from that perspective, the deletions in `src/power/shutdown-shim` LGTM. But +1 to what Francois said, I'm a little confused that the FIDL definitions aren't being deleted as part of this CL.
I don't think we usually remove FIDL definitions in the same CL that we retire a given API level. Could this be done in a follow-up?
In general, we leave removed definitions in the FIDL files to act as historical documentation. We've bikeshedded on this several times before - I should probably just write a tiny RFC to make it official policy.
Still waiting on a +2 from @mbru...@google.com (or another owner on the `shutdown-shim` code), and then I think we're good to go.
| API-Review | +1 |
| Code-Review | +2 |
| Owners-Override | +1 |
Hunter FreyerLooks like there are a bunch of files with non-mechanical changes that haven't been reviewed, which means it seems too early for owners-override.
Michael BrunsonI think I can speak to the RTC changes, they look good to me. The power changes could maybe use another set of eyes. @mbru...@google.com, can you take a look? After that I can provide OO+1.
Francois Rousseaufxbug.dev/385742868 is still open. Looks like a number of changes have been landed but it still remains open. Maybe @martin...@google.com or @frou...@google.com know the state of things there?
Jeff MartinI guess I would have expected the CL to also remove the definitions in the //sdk/fidl/fuchsia.hardware.power.statecontrol/*.fidl files. That's what that cleanup issue is tracking, deleting the server implementation and the FIDL definitions.
Brandon CastellanoI've been holding on to fxbug.dev/385742868 waiting for F26 to be retired so that we could delete the logic backing the old FIDL definitions. So from that perspective, the deletions in `src/power/shutdown-shim` LGTM. But +1 to what Francois said, I'm a little confused that the FIDL definitions aren't being deleted as part of this CL.
Hunter FreyerI don't think we usually remove FIDL definitions in the same CL that we retire a given API level. Could this be done in a follow-up?
In general, we leave removed definitions in the FIDL files to act as historical documentation. We've bikeshedded on this several times before - I should probably just write a tiny RFC to make it official policy.
Still waiting on a +2 from @mbru...@google.com (or another owner on the `shutdown-shim` code), and then I think we're good to go.
Boom. Let's do this!
Thanks so much Brandon! Incredible dedication as always 😊
[version_history] Retire API level 26
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Change has been successfully rolled: https://turquoise-internal-review.googlesource.com/1120703
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |