Manage log locks on the Log object to prepare for multiple writers
ClosedPublic
Actions

Authored by epriestley on Feb 23 2018, 1:39 PM.

Details

Reviewers: None
Maniphest Tasks: T13088: Plans: Harbormaster UI usability and interconnectedness
Commits: rPd152bd583608: Manage log locks on the Log object to prepare for multiple writers

Summary

Depends on D19134. Ref T13088. Future changes will support API writers, so push the log lock into the Log object.

Allow open/close ("this process is writing to this log") to be separate from live/final ("this log is still generating more data").

Test Plan

Wrote logs with bin/harbormater write-log and updated logs with bin/harbormaster rebuild-log.

Diff Detail

Repository

rP Phabricator

Lint

Lint Not Applicable

Unit

Tests Not Applicable

Event Timeline

epriestley created this revision.Feb 23 2018, 1:39 PM

Owners added a subscriber: Restricted Owners Package.Feb 23 2018, 1:39 PM

Harbormaster completed remote builds in B19650: Diff 45841.Feb 23 2018, 1:41 PM

epriestley requested review of this revision.Feb 23 2018, 1:41 PM

epriestley added a child revision: D19136: In Harbormaster, record byte length on the build logs.Feb 23 2018, 1:52 PM

This revision was not accepted when it landed; it landed in state Needs Review.Feb 27 2018, 1:54 AM

Closed by commit rPd152bd583608: Manage log locks on the Log object to prepare for multiple writers (authored by epriestley). · Explain Why

This revision was automatically updated to reflect the committed changes.

Revision Contents
Changeset List

Path

Size

src/

applications/

harbormaster/

storage/

build/

HarbormasterBuildLog.php

261 lines

worker/

HarbormasterLogWorker.php

26 lines

Diff 45856

View Options

src/applications/harbormaster/storage/build/HarbormasterBuildLog.php