Read all session logs in ai/ to get up to speed, then proceed with Linux integration testing against a real SDP environment with a running p4d instance.
See session_log_2026-06-25-3.md for the full testing checklist.
# Sync workspace (set up a //p4lf/dev client on the Linux machine first)
p4 sync
# Build (requires Go 1.20+; install via https://go.dev/dl/ if needed)
make build
bin/p4lf -version # expect: p4lf 0.1.0 (CL ..., //p4lf/dev#N, ...)
# Configure
cp p4lf.cfg.example /p4/common/site/log_feeder/p4lf.cfg
vi /p4/common/site/log_feeder/p4lf.cfg # set P4LogFile at minimum
# Run in foreground for initial testing
bin/p4lf -config /p4/common/site/log_feeder/p4lf.cfgmake check on macOSinstall.sh ready for production use (needs binaries in main/release stream first)Consult the file P4WorkflowNotes.md for info about version control worklfows and interactions.
The 'ai/' directory under the workspace root is where this AGENTS.md file is, which is symlink'd to from the root of the workspace as copilot-instructions.md.
The ai/ folder is used to store the AGENTS.md file (updated for each AI session), AI session logs -- not part of the software itself. However, the ai/ folder contents are versioned.
For each session, write a session log that captures highlights of what was done, including prompts. Paraphrasing prompts is OK; not all prompts need to be captured, only those useful in helping understand result of the session. Capture any important decisions that were made (and why). The primary audience if the session logs is a future agent to continue the work, though they may also have training and audit value.
# Task for Today Read all session logs in ai/ to get up to speed, then proceed with **Linux integration testing** against a real SDP environment with a running p4d instance. See session_log_2026-06-25-3.md for the full testing checklist. ## Quick Start on Linux ```bash # Sync workspace (set up a //p4lf/dev client on the Linux machine first) p4 sync # Build (requires Go 1.20+; install via https://go.dev/dl/ if needed) make build bin/p4lf -version # expect: p4lf 0.1.0 (CL ..., //p4lf/dev#N, ...) # Configure cp p4lf.cfg.example /p4/common/site/log_feeder/p4lf.cfg vi /p4/common/site/log_feeder/p4lf.cfg # set P4LogFile at minimum # Run in foreground for initial testing bin/p4lf -config /p4/common/site/log_feeder/p4lf.cfg ``` ## Current Project State (as of CL 32835) - All source code in //p4lf/dev, passing `make check` on macOS - Binary builds: Linux amd64/arm64, macOS arm64/amd64 all build cleanly - `install.sh` ready for production use (needs binaries in main/release stream first) - Open job: P4LF-2 — perforce user service management (deferred, not blocking) - **Not yet done:** Linux integration testing, README update, tailer/logger unit tests ## Key Files for Context - ai/P4WorkflowNotes.md — P4 workflow, stream structure, how to create jobs - session_log_2026-06-25-3.md — integration testing checklist - session_log_2026-06-26.md — deployment/install.sh design decisions # Version Control Interaction Consult the file P4WorkflowNotes.md for info about version control worklfows and interactions. # The 'ai/' folder The 'ai/' directory under the workspace root is where this AGENTS.md file is, which is symlink'd to from the root of the workspace as copilot-instructions.md. The ai/ folder is used to store the AGENTS.md file (updated for each AI session), AI session logs -- not part of the software itself. However, the ai/ folder contents are versioned. For each session, write a session log that captures highlights of what was done, including prompts. Paraphrasing prompts is OK; not all prompts need to be captured, only those useful in helping understand result of the session. Capture any important decisions that were made (and why). The primary audience if the session logs is a future agent to continue the work, though they may also have training and audit value.
| # | Change | User | Description | Committed | |
|---|---|---|---|---|---|
| #4 | 32836 | C. Thomas Tyler | Update AGENTS.md with current project state for next session. | ||
| #3 | 32825 | C. Thomas Tyler | Session 4 log + AGENTS.md update: module path rename, ready for Linux testing. | ||
| #2 | 32824 | C. Thomas Tyler |
Rename Go module path from github.com/rcowham/p4lf to workshop.perforce.com/p4lf. The rcowham prefix was a carryover from early research into go-libtail (which is hosted at github.com/rcowham/go-libtail). p4lf is hosted on the Perforce Public Depot / Workshop, not GitHub, so workshop.perforce.com is the correct canonical module path. Updated: go.mod, all *.go files with internal imports, Makefile (MODULE and LDFLAGS). Session logs retain the old path as accurate historical record. |
||
| #1 | 32815 | C. Thomas Tyler | Added AGENTS.md. |