Closed Bug 1944395 Opened 9 months ago Closed 8 months ago

Add separate default actions for when Content Analysis times out versus hits an error

Categories

(Firefox :: Data Loss Prevention, task)

task

Tracking

()

RESOLVED FIXED
137 Branch
Tracking Status
firefox137 --- fixed

People

(Reporter: gstoll, Assigned: gstoll)

References

(Blocks 2 open bugs)

Details

Attachments

(3 files)

(also requires enterprise policies)

See Also: → 1926348
See Also: 1926348
Summary: Add separate default values for when Content Analysis times out versus hits an error → Add separate default actions for when Content Analysis times out versus hits an error
Assignee: nobody → gstoll
Status: NEW → ASSIGNED

Also add a gtest for the default result pref, which I don't think we
had anywhere.

When I added some gtests in part 1 this caused a gtest to fail. The
problem was that GetDiagnosticInfo() was looking at the last result
to determine whether we are connected to a client. The
CallClientWithRetry() logic now handles this more accurately, so if
we succeed there just set mConnectedToAgent to true.

Pushed by gstoll@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/978a727e750b part 1 - add Content Analysis pref for result to return if the agent times out r=dlp-reviewers,handyman https://hg.mozilla.org/integration/autoland/rev/0303076bb6d8 part 2 - drive-by cleanup of GetDiagnosticInfo() logic r=dlp-reviewers,handyman https://hg.mozilla.org/integration/autoland/rev/42e5e0d2a332 part 3 - add Enterprise Policy for timeout result pref r=dlp-reviewers,handyman
Regressions: 1949622
Status: ASSIGNED → RESOLVED
Closed: 8 months ago
Resolution: --- → FIXED
Target Milestone: --- → 137 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: