[LNA] Remove URLRequest.target_ip_address_space [chromium/src : main]

0 views
Skip to first unread message

Hubert Chao (Gerrit)

unread,
Nov 5, 2025, 2:15:39 PM (18 hours ago) Nov 5
to Chris Thompson, Chromium LUCI CQ, Chromium Metrics Reviews, chromium...@chromium.org, Nate Chapin, asvitkine...@chromium.org, blink-...@chromium.org, blink-work...@chromium.org, gavinp...@chromium.org, ipc-securi...@chromium.org, kinuko...@chromium.org, loading...@chromium.org, network-ser...@chromium.org
Attention needed from Chris Thompson and mmenke

Hubert Chao voted and added 1 comment

Votes added by Hubert Chao

Commit-Queue+1

1 comment

Patchset-level comments
File-level comment, Patchset 6 (Latest):
Hubert Chao . resolved

cthomp@ for initial review, mmenke@ for services/network/OWNERS

Open in Gerrit

Related details

Attention is currently required from:
  • Chris Thompson
  • mmenke
Submit Requirements:
  • requirement satisfiedCode-Coverage
  • requirement is not satisfiedCode-Owners
  • requirement is not satisfiedCode-Review
  • requirement is not satisfiedReview-Enforcement
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. DiffyGerrit
Gerrit-MessageType: comment
Gerrit-Project: chromium/src
Gerrit-Branch: main
Gerrit-Change-Id: Ie23801750309eff519c6373974365e238ef501b0
Gerrit-Change-Number: 7116538
Gerrit-PatchSet: 6
Gerrit-Owner: Hubert Chao <hc...@chromium.org>
Gerrit-Reviewer: Chris Thompson <cth...@chromium.org>
Gerrit-Reviewer: Hubert Chao <hc...@chromium.org>
Gerrit-Reviewer: mmenke <mme...@chromium.org>
Gerrit-CC: Chromium Metrics Reviews <chromium-met...@google.com>
Gerrit-CC: Nate Chapin <jap...@chromium.org>
Gerrit-Attention: mmenke <mme...@chromium.org>
Gerrit-Attention: Chris Thompson <cth...@chromium.org>
Gerrit-Comment-Date: Wed, 05 Nov 2025 19:15:33 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: Yes
satisfied_requirement
unsatisfied_requirement
open
diffy

mmenke (Gerrit)

unread,
Nov 5, 2025, 2:37:50 PM (18 hours ago) Nov 5
to Hubert Chao, Chris Thompson, Chromium LUCI CQ, Chromium Metrics Reviews, chromium...@chromium.org, Nate Chapin, asvitkine...@chromium.org, blink-...@chromium.org, blink-work...@chromium.org, gavinp...@chromium.org, ipc-securi...@chromium.org, kinuko...@chromium.org, loading...@chromium.org, network-ser...@chromium.org
Attention needed from Chris Thompson and Hubert Chao

mmenke added 5 comments

Patchset-level comments
File-level comment, Patchset 6:
mmenke . resolved

I'll defer to Chris in terms of changed behavior.

File services/network/public/mojom/cors.mojom
Line 134, Patchset 6: // This is set if:
mmenke . unresolved

"This is set if" implies this is an optional, but it is not. Should it be an optional?

Line 135, Patchset 6: // * The request had a required_address_space set but the
mmenke . unresolved

nit: Here, and on the next two lines, use backticks around field names (`)

Line 136, Patchset 6: // resource_address_space did not match. In this case, this will be set ot
mmenke . unresolved

to

Line 145, Patchset 6:
mmenke . unresolved

Remove extra blank line.

Open in Gerrit

Related details

Attention is currently required from:
  • Chris Thompson
  • Hubert Chao
Submit Requirements:
    • requirement satisfiedCode-Coverage
    • requirement is not satisfiedCode-Owners
    • requirement is not satisfiedCode-Review
    • requirement is not satisfiedNo-Unresolved-Comments
    • requirement is not satisfiedReview-Enforcement
    Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. DiffyGerrit
    Gerrit-MessageType: comment
    Gerrit-Project: chromium/src
    Gerrit-Branch: main
    Gerrit-Change-Id: Ie23801750309eff519c6373974365e238ef501b0
    Gerrit-Change-Number: 7116538
    Gerrit-PatchSet: 6
    Gerrit-Owner: Hubert Chao <hc...@chromium.org>
    Gerrit-Reviewer: Chris Thompson <cth...@chromium.org>
    Gerrit-Reviewer: Hubert Chao <hc...@chromium.org>
    Gerrit-Reviewer: mmenke <mme...@chromium.org>
    Gerrit-CC: Chromium Metrics Reviews <chromium-met...@google.com>
    Gerrit-CC: Nate Chapin <jap...@chromium.org>
    Gerrit-Attention: Chris Thompson <cth...@chromium.org>
    Gerrit-Attention: Hubert Chao <hc...@chromium.org>
    Gerrit-Comment-Date: Wed, 05 Nov 2025 19:37:45 +0000
    Gerrit-HasComments: Yes
    Gerrit-Has-Labels: No
    satisfied_requirement
    unsatisfied_requirement
    open
    diffy

    Chris Thompson (Gerrit)

    unread,
    Nov 5, 2025, 5:48:40 PM (15 hours ago) Nov 5
    to Hubert Chao, Chromium LUCI CQ, Chromium Metrics Reviews, chromium...@chromium.org, Nate Chapin, asvitkine...@chromium.org, blink-...@chromium.org, blink-work...@chromium.org, gavinp...@chromium.org, ipc-securi...@chromium.org, kinuko...@chromium.org, loading...@chromium.org, network-ser...@chromium.org
    Attention needed from Hubert Chao

    Chris Thompson added 3 comments

    Patchset-level comments
    File-level comment, Patchset 7 (Latest):
    Chris Thompson . resolved

    Overall LGTM, but let's consider the "default to kUnknown" vs. optional question below.

    File services/network/private_network_access_url_loader_interceptor.cc
    Line 79, Patchset 7 (Latest): // Error here is that we initially saw the email in the
    Chris Thompson . unresolved
    ```suggestion
    // Error here is that we initially saw the response in the
    ```
    File services/network/public/mojom/cors.mojom
    Line 134, Patchset 6: // This is set if:
    mmenke . unresolved

    "This is set if" implies this is an optional, but it is not. Should it be an optional?

    Chris Thompson

    Having this default to `unknown` is consistent with the other PNA/LNA address space fields. I don't have a strong preference on having this be an optional vs. adjusting the comments to be "defaults to kUnknown unless XYZ", although optional is maybe a bit more explicit

    Open in Gerrit

    Related details

    Attention is currently required from:
    • Hubert Chao
    Submit Requirements:
    • requirement satisfiedCode-Coverage
    • requirement is not satisfiedCode-Owners
    • requirement is not satisfiedCode-Review
    • requirement is not satisfiedNo-Unresolved-Comments
    • requirement is not satisfiedReview-Enforcement
    Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. DiffyGerrit
    Gerrit-MessageType: comment
    Gerrit-Project: chromium/src
    Gerrit-Branch: main
    Gerrit-Change-Id: Ie23801750309eff519c6373974365e238ef501b0
    Gerrit-Change-Number: 7116538
    Gerrit-PatchSet: 7
    Gerrit-Owner: Hubert Chao <hc...@chromium.org>
    Gerrit-Reviewer: Chris Thompson <cth...@chromium.org>
    Gerrit-Reviewer: Hubert Chao <hc...@chromium.org>
    Gerrit-Reviewer: mmenke <mme...@chromium.org>
    Gerrit-CC: Chromium Metrics Reviews <chromium-met...@google.com>
    Gerrit-CC: Nate Chapin <jap...@chromium.org>
    Gerrit-Attention: Hubert Chao <hc...@chromium.org>
    Gerrit-Comment-Date: Wed, 05 Nov 2025 22:48:31 +0000
    Gerrit-HasComments: Yes
    Gerrit-Has-Labels: No
    Comment-In-Reply-To: mmenke <mme...@chromium.org>
    satisfied_requirement
    unsatisfied_requirement
    open
    diffy

    mmenke (Gerrit)

    unread,
    Nov 5, 2025, 6:07:45 PM (15 hours ago) Nov 5
    to Hubert Chao, Chris Thompson, Chromium LUCI CQ, Chromium Metrics Reviews, chromium...@chromium.org, Nate Chapin, asvitkine...@chromium.org, blink-...@chromium.org, blink-work...@chromium.org, gavinp...@chromium.org, ipc-securi...@chromium.org, kinuko...@chromium.org, loading...@chromium.org, network-ser...@chromium.org
    Attention needed from Hubert Chao

    mmenke added 1 comment

    File services/network/public/mojom/cors.mojom
    Line 134, Patchset 6: // This is set if:
    mmenke . unresolved

    "This is set if" implies this is an optional, but it is not. Should it be an optional?

    Chris Thompson

    Having this default to `unknown` is consistent with the other PNA/LNA address space fields. I don't have a strong preference on having this be an optional vs. adjusting the comments to be "defaults to kUnknown unless XYZ", although optional is maybe a bit more explicit

    mmenke

    I'm happy to defer to you two here, the name and value really confused me, at least, until I realized it was to have additional metadata in the case of specific errors (Admittedly, that may partly be because my context was full of the input param target_address_space, and I was trying to model `inconsistent_address_space` as an input param)

    Gerrit-Comment-Date: Wed, 05 Nov 2025 23:07:40 +0000
    Gerrit-HasComments: Yes
    Gerrit-Has-Labels: No
    Comment-In-Reply-To: mmenke <mme...@chromium.org>
    Comment-In-Reply-To: Chris Thompson <cth...@chromium.org>
    satisfied_requirement
    unsatisfied_requirement
    open
    diffy
    Reply all
    Reply to author
    Forward
    0 new messages