fix: connect status-line segments to feed cache + real CalendarProducer #62
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| @@ -0,0 +1,133 @@ | ||||||||||||||||
| # Retrospective: Status-Line Pipeline Disconnection (Bug #50+) | ||||||||||||||||
|
|
||||||||||||||||
| **Date:** 2026-03-08 | ||||||||||||||||
| **Severity:** Medium (user-visible but non-blocking) | ||||||||||||||||
| **Root Cause Category:** Integration gap — components work in isolation but fail end-to-end | ||||||||||||||||
|
|
||||||||||||||||
| ## What Happened | ||||||||||||||||
|
|
||||||||||||||||
| The status line showed `session: -- | cost: -- | project: -- | calendar: --` — all placeholder | ||||||||||||||||
| values despite data being available. Weather (the only live producer) was missing entirely. | ||||||||||||||||
|
|
||||||||||||||||
| ## Five Bugs, One Root Cause Pattern | ||||||||||||||||
|
|
||||||||||||||||
| | Bug | Symptom | Root Cause | Layer | | ||||||||||||||||
| |-----|---------|------------|-------| | ||||||||||||||||
| | **B1: session: --** | No session count displayed | `dispatch` never called `analytics.StartSession()` — the analytics API was built but never wired to the dispatch pipeline | Integration | | ||||||||||||||||
| | **B2: cost: --** | No cost displayed | Same as B1 — $0.00 because no sessions recorded | Integration | | ||||||||||||||||
| | **B3: weather missing** | Weather segment not shown | `hookwise.yaml` segments list omitted `weather` despite weather feed being enabled and producing real data | Config | | ||||||||||||||||
| | **B4: project/calendar: --** | Always shows `--` | Producers return `source: "placeholder"` — correctly filtered but ships as "done" | Design debt | | ||||||||||||||||
| | **B5: timezone mismatch** | Same-connection queries return 0 | `StartSession` stores UTC timestamps but `DailySummary` was queried with local date — fails in negative UTC offsets (PST evening → UTC next day) | Data | | ||||||||||||||||
|
|
||||||||||||||||
| ## First-Principle Analysis | ||||||||||||||||
|
|
||||||||||||||||
| ### Why does each component work in isolation but fail end-to-end? | ||||||||||||||||
|
|
||||||||||||||||
| The hookwise architecture has 4 independent data pipelines: | ||||||||||||||||
|
|
||||||||||||||||
| ```text | ||||||||||||||||
| Pipeline 1: Daemon → Feed JSON → bridge.CollectFeedCache → renderSegment | ||||||||||||||||
| Pipeline 2: Dispatch → [MISSING] → Dolt → DailySummary → renderBuiltinSegment | ||||||||||||||||
| Pipeline 3: Config YAML → LoadConfig → StatusLine.Segments → segment loop | ||||||||||||||||
| Pipeline 4: StartSession(UTC) → Dolt → DailySummary(local date) → mismatch | ||||||||||||||||
| ``` | ||||||||||||||||
|
|
||||||||||||||||
| Each pipeline was tested within its own boundary: | ||||||||||||||||
| - Feed producers have unit tests proving they write correct JSON | ||||||||||||||||
| - Analytics API has tests proving StartSession/DailySummary work (with UTC-safe fixed dates) | ||||||||||||||||
| - Config loading has tests proving YAML parsing works | ||||||||||||||||
| - Segment rendering has tests proving each segment renders correctly | ||||||||||||||||
|
|
||||||||||||||||
| But **no test ever validated the full pipeline from dispatch → Dolt → status-line → screen**. | ||||||||||||||||
|
|
||||||||||||||||
| ### The "Mock Confidence Trap" (Pattern #2) | ||||||||||||||||
|
|
||||||||||||||||
| This is the exact same pattern as Bug #29 (weather feed): | ||||||||||||||||
|
|
||||||||||||||||
| > Mock-based tests pass on both sides of a boundary while the real system fails. | ||||||||||||||||
|
|
||||||||||||||||
| **Bug #29:** Go producer writes `unit` → Python TUI reads `temperatureUnit` → both sides' tests pass. | ||||||||||||||||
| **Bug #50:** Go dispatch has analytics infrastructure → Go status-line reads from Dolt → both sides' tests pass but dispatch never writes. | ||||||||||||||||
|
|
||||||||||||||||
| The mock confidence trap has three variants: | ||||||||||||||||
|
|
||||||||||||||||
| 1. **Field mismatch** (Bug #29): Both sides mock the field name they expect | ||||||||||||||||
| 2. **Integration gap** (Bug #50 B1/B2): Both sides work independently but the bridge between them was never built | ||||||||||||||||
| 3. **Format mismatch** (Bug #50 B5): Both sides work with their own format (UTC vs local) but never tested together | ||||||||||||||||
|
|
||||||||||||||||
| ### Why didn't tests catch this? | ||||||||||||||||
|
|
||||||||||||||||
| | Testing Layer | What It Validates | What It Misses | | ||||||||||||||||
| |---------------|-------------------|----------------| | ||||||||||||||||
| | Unit tests | `StartSession` writes rows; `DailySummary` queries rows | Whether dispatch calls StartSession at all | | ||||||||||||||||
| | Contract tests | JSON stdout format matches spec | Whether analytics writes happen | | ||||||||||||||||
| | Integration tests | Dispatch returns correct exit codes | Whether side effects (analytics) fire | | ||||||||||||||||
| | Architecture tests | Package dependency rules | Whether wiring between packages exists | | ||||||||||||||||
| | Property-based tests | Invariants within a single domain | Cross-domain data flow | | ||||||||||||||||
|
|
||||||||||||||||
| **The gap:** No test validates the **existence of a connection** between two components, only the correctness of each component in isolation. | ||||||||||||||||
|
|
||||||||||||||||
| ### Why did placeholder producers ship? | ||||||||||||||||
|
|
||||||||||||||||
| The project/calendar/pulse/news producers were implemented as placeholders (`source: "placeholder"`) and marked as "done" in the task tracker. The renderer correctly filters placeholders, so the status line shows `--`. But: | ||||||||||||||||
|
|
||||||||||||||||
| 1. The spec didn't distinguish "producer skeleton exists" from "producer returns real data" | ||||||||||||||||
| 2. The `feedData()` filter for `source: "placeholder"` was added as a safety net, not as a signal that the feature is incomplete | ||||||||||||||||
| 3. No acceptance test validates that a segment shows **non-placeholder** data | ||||||||||||||||
|
|
||||||||||||||||
| ## Fixes Applied | ||||||||||||||||
|
|
||||||||||||||||
| 1. **B1/B2:** Added `recordAnalytics()` function in dispatch — writes SessionStart/PostToolUse/SessionEnd to Dolt with commit | ||||||||||||||||
| 2. **B3:** Added `weather` to `hookwise.yaml` segments list and global config | ||||||||||||||||
| 3. **B5:** Changed all `time.Now().Format("2006-01-02")` to `time.Now().UTC().Format("2006-01-02")` in status-line and stats commands to match analytics' UTC storage | ||||||||||||||||
| 4. **B4:** No code fix — producers need real implementations (tracked separately) | ||||||||||||||||
|
There was a problem hiding this comment. Update B4 fix status to reflect calendar producer implementation. The PR objectives state that a real Google Calendar integration was implemented in this PR with OAuth support, event handling, caching, and 10 unit tests. Stating "No code fix — producers need real implementations" contradicts the actual scope of this PR. 📝 Suggested update-4. **B4:** No code fix — producers need real implementations (tracked separately)
+4. **B4:** Implemented real CalendarProducer with Google Calendar OAuth integration (project producer tracked separately)🤖 Prompt for AI Agents |
||||||||||||||||
|
|
||||||||||||||||
| ## New Tests Added | ||||||||||||||||
|
|
||||||||||||||||
| 1. `TestPersistAcrossConnections` — validates Dolt data survives close+reopen (analytics package) | ||||||||||||||||
| 2. `TestRecordAnalytics_SessionStart` — validates dispatch→Dolt→DailySummary pipeline | ||||||||||||||||
| 3. `TestRecordAnalytics_PostToolUse` — validates event recording pipeline | ||||||||||||||||
| 4. All use UTC dates to match production behavior | ||||||||||||||||
|
Comment on lines
+85
to
+90
There was a problem hiding this comment. Include calendar producer tests in "New Tests Added" section. The PR objectives mention "10 unit tests for calendar producer, 3 CLI rendering tests for status-line calendar rendering," but this section only lists analytics-related tests. A retrospective's test inventory should be comprehensive. 📝 Suggested addition ## New Tests Added
1. `TestPersistAcrossConnections` — validates Dolt data survives close+reopen (analytics package)
2. `TestRecordAnalytics_SessionStart` — validates dispatch→Dolt→DailySummary pipeline
3. `TestRecordAnalytics_PostToolUse` — validates event recording pipeline
-4. All use UTC dates to match production behavior
+4. 10 unit tests for `CalendarProducer` — validates OAuth flow, event parsing, caching, fail-open behavior
+5. 3 CLI rendering tests for status-line calendar segment
+6. All analytics tests use UTC dates to match production behavior🤖 Prompt for AI Agents |
||||||||||||||||
|
|
||||||||||||||||
| ## Lessons Learned | ||||||||||||||||
|
|
||||||||||||||||
| ### L1: "Infrastructure-ready" ≠ "Wired" | ||||||||||||||||
|
|
||||||||||||||||
| The dispatch command had goroutine infrastructure, 50ms grace period, and side-effect handler patterns — everything EXCEPT the actual analytics call. The comment `// Brief grace period for side-effect goroutines (analytics, coaching)` promised work that didn't exist. **Lesson:** Comments describing intended behavior are not substitutes for code. | ||||||||||||||||
|
|
||||||||||||||||
| ### L2: Timezone bugs hide in happy-path tests | ||||||||||||||||
|
|
||||||||||||||||
| All existing analytics tests used `time.Date(2025, 3, 6, 9, 0, 0, 0, time.UTC)` — a UTC timestamp where local and UTC dates are the same. The bug only manifests in negative UTC offsets during evening hours. **Lesson:** Test with edge-case timestamps (midnight, day boundaries, DST transitions). | ||||||||||||||||
|
|
||||||||||||||||
| ### L3: Config completeness is untestable without a "full pipeline" smoke test | ||||||||||||||||
|
|
||||||||||||||||
| Weather was enabled in feeds config but absent from segments config. No test validates that enabled feeds appear in the status line. **Lesson:** A single e2e test that runs `hookwise status-line` with a known config and validates all expected segments appear would catch this instantly. | ||||||||||||||||
|
|
||||||||||||||||
| ### L4: The Mock Confidence Trap is a recurring pattern | ||||||||||||||||
|
|
||||||||||||||||
| This is the third time (after Bug #29 and the original status-line stub bug) that both sides of a boundary pass all tests while the real system fails. **Lesson:** After shipping any feature that crosses a producer→consumer boundary, add an integration test that validates the full pipeline with real (not mocked) data. | ||||||||||||||||
|
|
||||||||||||||||
|
coderabbitai[bot] marked this conversation as resolved.
|
||||||||||||||||
| ## Proposed E2E Test | ||||||||||||||||
|
|
||||||||||||||||
| > **Note:** This is pseudocode illustrating the test structure, not a runnable test. | ||||||||||||||||
|
|
||||||||||||||||
| ```go | ||||||||||||||||
| // TestStatusLine_EndToEnd_DispatchThenRender validates the full pipeline: | ||||||||||||||||
| // dispatch SessionStart → Dolt write → status-line reads → session count appears | ||||||||||||||||
| func TestStatusLine_EndToEnd_DispatchThenRender(t *testing.T) { | ||||||||||||||||
| tmpDir := t.TempDir() | ||||||||||||||||
| // 1. Write config with known segments | ||||||||||||||||
| // 2. Call recordAnalytics(SessionStart) with tmpDir | ||||||||||||||||
| // 3. Write weather.json with real data to cacheDir | ||||||||||||||||
| // 4. Run status-line command | ||||||||||||||||
| // 5. Assert: session count > 0, weather shows temperature, weather not "--" | ||||||||||||||||
| } | ||||||||||||||||
| ``` | ||||||||||||||||
|
coderabbitai[bot] marked this conversation as resolved.
|
||||||||||||||||
|
|
||||||||||||||||
| ## Action Items | ||||||||||||||||
|
|
||||||||||||||||
| - [ ] Implement real project producer (git repo detection) | ||||||||||||||||
| - [ ] Implement real calendar producer (Google Calendar MCP) | ||||||||||||||||
|
Comment on lines
+129
to
+130
There was a problem hiding this comment. Mark calendar producer action item as completed or remove it. The action item "Implement real calendar producer (Google Calendar MCP)" appears to have been completed in this PR according to the PR objectives. Retrospectives should clearly distinguish between work completed in the current PR and future work. 📝 Suggested update ## Action Items
-- [ ] Implement real project producer (git repo detection)
-- [ ] Implement real calendar producer (Google Calendar MCP)
+- [x] Implement real calendar producer (Google Calendar OAuth integration) — completed in this PR
+- [ ] Implement real project producer (git repo detection)
- [ ] Add e2e smoke test for status-line pipeline
- [ ] Add UTC-edge-case timestamp to analytics test suite
- [ ] Consider adding a CI job that runs `hookwise status-line` with a test config and validates non-empty output📝 Committable suggestion
Suggested change
🤖 Prompt for AI Agents |
||||||||||||||||
| - [ ] Add e2e smoke test for status-line pipeline | ||||||||||||||||
| - [ ] Add UTC-edge-case timestamp to analytics test suite | ||||||||||||||||
| - [ ] Consider adding a CI job that runs `hookwise status-line` with a test config and validates non-empty output | ||||||||||||||||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -3,38 +3,56 @@ module github.com/vishnujayvel/hookwise | |
| go 1.25.5 | ||
|
|
||
| require ( | ||
| dagger.io/dagger v0.20.1 | ||
| github.com/Khan/genqlient v0.8.1 | ||
| github.com/cenkalti/backoff/v4 v4.3.0 | ||
| github.com/charmbracelet/lipgloss v1.1.0 | ||
| github.com/dagger/otel-go v1.41.0 | ||
| github.com/dolthub/driver v0.2.0 | ||
| github.com/gobwas/glob v0.2.3 | ||
| github.com/spf13/cobra v1.10.2 | ||
| github.com/stretchr/testify v1.11.1 | ||
| github.com/vektah/gqlparser/v2 v2.5.32 | ||
| go.opentelemetry.io/otel v1.42.0 | ||
| go.opentelemetry.io/otel/sdk v1.41.0 | ||
| go.opentelemetry.io/otel/trace v1.42.0 | ||
| golang.org/x/oauth2 v0.36.0 | ||
| golang.org/x/tools v0.41.0 | ||
| google.golang.org/api v0.269.0 | ||
| gopkg.in/yaml.v3 v3.0.1 | ||
| modernc.org/sqlite v1.46.1 | ||
| pgregory.net/rapid v1.2.0 | ||
| ) | ||
|
|
||
| require ( | ||
| cel.dev/expr v0.25.1 // indirect | ||
| cloud.google.com/go v0.121.6 // indirect | ||
| cloud.google.com/go/auth v0.18.2 // indirect | ||
| cloud.google.com/go/auth/oauth2adapt v0.2.8 // indirect | ||
| cloud.google.com/go/compute/metadata v0.9.0 // indirect | ||
| cloud.google.com/go/iam v1.5.3 // indirect | ||
| cloud.google.com/go/monitoring v1.24.3 // indirect | ||
| cloud.google.com/go/storage v1.56.0 // indirect | ||
| filippo.io/edwards25519 v1.1.0 // indirect | ||
|
There was a problem hiding this comment. 🧩 Analysis chain🏁 Script executed: #!/bin/bash
# Check for newer versions of flagged dependencies
echo "Checking filippo.io/edwards25519..."
go list -m -versions filippo.io/edwards25519 2>/dev/null | head -1
echo "Checking github.com/aws/aws-sdk-go..."
go list -m -versions github.com/aws/aws-sdk-go 2>/dev/null | head -1Repository: vishnujayvel/hookwise Length of output: 16581 🏁 Script executed: # Check if edwards25519 and aws-sdk-go are direct or indirect dependencies
cd /tmp && cat go.mod | head -50Repository: vishnujayvel/hookwise Length of output: 103 🌐 Web query:
💡 Result: GO-2026-4503 is the Go vulnerability record for CVE-2026-26958 affecting What’s the issue
Impact / exposureThis is considered low severity and applies primarily to code that directly uses the advanced API FixUpgrade to References: Go vuln entry and upstream advisory. [1][2] Sources 🌐 Web query:
💡 Result: GO-2022-0635 is a Go vulnerability report for CVE-2020-8912 / GHSA-7f33-f4f5-xwgw affecting Fix / mitigation: use S3 Encryption Client / S3 Crypto SDK v2 (which authenticates the algorithm, e.g., via KMS+context key wrapping for new files) and re-encrypt old objects that were encrypted with the vulnerable scheme (notably GCM with the older Sources
🏁 Script executed: cat /workspace/*/go.mod | head -60Repository: vishnujayvel/hookwise Length of output: 118 🏁 Script executed: # Find and display go.mod from root
find . -name "go.mod" -type f | head -1 | xargs cat | head -60Repository: vishnujayvel/hookwise Length of output: 2821 🏁 Script executed: # Check if aws-sdk-go is directly used in the codebase
rg "aws-sdk-go|aws-sdk|s3crypto" --type go -i | head -20Repository: vishnujayvel/hookwise Length of output: 47 🏁 Script executed: # Check what package brings in aws-sdk-go as transitive dependency
rg "aws" go.modRepository: vishnujayvel/hookwise Length of output: 112 🌐 Web query:
💡 Result: GO-2022-0646 is the Go vulnerability ID for CVE-2020-8911 / GHSA-f5pg-7wfw-84q9, a CBC padding-oracle issue in the Amazon S3 “Crypto/Encryption Client” code shipped in Impact / scope
Fix / remediation
References
Sources: [1] https://pkg.go.dev/vuln/GO-2022-0646 [2] GHSA-f5pg-7wfw-84q9 [3] https://aws.amazon.com/blogs/developer/updates-to-the-amazon-s3-encryption-client/ [4] aws/aws-sdk-go#3403 Correct severity classification of transitive security advisories. Both dependencies are confirmed transitive (indirect):
While hookwise may not directly use S3 Crypto functionality, the aws-sdk-go advisories should not be classified as low-severity. Strongly prioritize migrating away from the affected v1 package or evaluate if S3 Crypto usage can be eliminated. 🧰 Tools🪛 OSV Scanner (2.3.3)[LOW] 36-36: filippo.io/edwards25519 1.1.0: Invalid result or undefined behavior in filippo.io/edwards25519 (GO-2026-4503) [LOW] 36-36: filippo.io/edwards25519 1.1.0: filippo.io/edwards25519 MultiScalarMult produces invalid results or undefined behavior if receiver is not the identity 🤖 Prompt for AI Agents
Owner
Author
There was a problem hiding this comment. Both are transitive/indirect dependencies pulled in by Dolt's embedded driver:
Will track the edwards25519 bump as a low-priority dep update. The aws-sdk-go issue is upstream and out of our control. There was a problem hiding this comment. Rate Limit Exceeded
|
||
| github.com/99designs/gqlgen v0.17.81 // indirect | ||
| github.com/GoogleCloudPlatform/opentelemetry-operations-go/detectors/gcp v1.30.0 // indirect | ||
| github.com/GoogleCloudPlatform/opentelemetry-operations-go/exporter/metric v0.53.0 // indirect | ||
| github.com/GoogleCloudPlatform/opentelemetry-operations-go/internal/resourcemapping v0.53.0 // indirect | ||
| github.com/HdrHistogram/hdrhistogram-go v1.1.2 // indirect | ||
| github.com/aliyun/aliyun-oss-go-sdk v3.0.2+incompatible // indirect | ||
| github.com/apache/arrow/go/arrow v0.0.0-20211112161151-bc219186db40 // indirect | ||
| github.com/apache/thrift v0.19.0 // indirect | ||
| github.com/aws/aws-sdk-go v1.50.16 // indirect | ||
| github.com/aymanbagabas/go-osc52/v2 v2.0.1 // indirect | ||
| github.com/bcicen/jstream v1.0.1 // indirect | ||
| github.com/cenkalti/backoff/v5 v5.0.3 // indirect | ||
| github.com/cespare/xxhash/v2 v2.3.0 // indirect | ||
| github.com/charmbracelet/colorprofile v0.2.3-0.20250311203215-f60798e515dc // indirect | ||
| github.com/charmbracelet/x/ansi v0.8.0 // indirect | ||
| github.com/charmbracelet/x/cellbuf v0.0.13-0.20250311204145-2c3ea96c31dd // indirect | ||
| github.com/charmbracelet/x/term v0.2.1 // indirect | ||
| github.com/cncf/xds/go v0.0.0-20251210132809-ee656c7534f5 // indirect | ||
| github.com/davecgh/go-spew v1.1.2-0.20180830191138-d8f796af33cc // indirect | ||
| github.com/denisbrodbeck/machineid v1.0.1 // indirect | ||
| github.com/dolthub/dolt/go v0.40.5-0.20240702155756-bcf4dd5f5cc1 // indirect | ||
| github.com/dolthub/dolt/go/gen/proto/dolt/services/eventsapi v0.0.0-20240212175631-02e9f99a3a9b // indirect | ||
|
|
@@ -48,22 +66,24 @@ require ( | |
| github.com/dolthub/swiss v0.2.1 // indirect | ||
| github.com/dolthub/vitess v0.0.0-20240709194214-7926ea9d425d // indirect | ||
| github.com/dustin/go-humanize v1.0.1 // indirect | ||
| github.com/envoyproxy/go-control-plane/envoy v1.36.0 // indirect | ||
| github.com/envoyproxy/protoc-gen-validate v1.3.0 // indirect | ||
| github.com/fatih/color v1.16.0 // indirect | ||
| github.com/felixge/httpsnoop v1.0.4 // indirect | ||
| github.com/go-jose/go-jose/v4 v4.1.3 // indirect | ||
| github.com/go-kit/kit v0.13.0 // indirect | ||
| github.com/go-logr/logr v1.4.3 // indirect | ||
| github.com/go-logr/stdr v1.2.2 // indirect | ||
| github.com/go-sql-driver/mysql v1.7.2-0.20231213112541-0004702b931d // indirect | ||
| github.com/goccy/go-json v0.10.2 // indirect | ||
| github.com/gofrs/flock v0.8.1 // indirect | ||
| github.com/golang/snappy v0.0.4 // indirect | ||
| github.com/google/btree v1.1.2 // indirect | ||
| github.com/google/s2a-go v0.1.9 // indirect | ||
| github.com/google/uuid v1.6.0 // indirect | ||
| github.com/googleapis/enterprise-certificate-proxy v0.3.12 // indirect | ||
| github.com/googleapis/gax-go/v2 v2.17.0 // indirect | ||
| github.com/grpc-ecosystem/grpc-gateway/v2 v2.28.0 // indirect | ||
| github.com/hashicorp/golang-lru v1.0.2 // indirect | ||
| github.com/hashicorp/golang-lru/v2 v2.0.7 // indirect | ||
| github.com/inconshreveable/mousetrap v1.1.0 // indirect | ||
|
|
@@ -76,7 +96,7 @@ require ( | |
| github.com/kylelemons/godebug v1.1.0 // indirect | ||
| github.com/lestrrat-go/strftime v1.0.6 // indirect | ||
| github.com/lucasb-eyer/go-colorful v1.2.0 // indirect | ||
| github.com/mattn/go-colorable v0.1.14 // indirect | ||
| github.com/mattn/go-isatty v0.0.20 // indirect | ||
| github.com/mattn/go-runewidth v0.0.16 // indirect | ||
| github.com/mohae/uvarint v0.0.0-20160208145430-c3f9e62bf2b0 // indirect | ||
|
|
@@ -85,48 +105,58 @@ require ( | |
| github.com/oracle/oci-go-sdk/v65 v65.55.0 // indirect | ||
| github.com/pierrec/lz4/v4 v4.1.21 // indirect | ||
| github.com/pkg/errors v0.9.1 // indirect | ||
| github.com/planetscale/vtprotobuf v0.6.1-0.20240319094008-0393e58bdf10 // indirect | ||
| github.com/pmezard/go-difflib v1.0.1-0.20181226105442-5d4384ee4fb2 // indirect | ||
| github.com/remyoudompheng/bigfft v0.0.0-20230129092748-24d4a6f8daec // indirect | ||
| github.com/rivo/uniseg v0.4.7 // indirect | ||
| github.com/sergi/go-diff v1.3.1 // indirect | ||
| github.com/shopspring/decimal v1.3.1 // indirect | ||
| github.com/silvasur/buzhash v0.0.0-20160816060738-9bdec3dec7c6 // indirect | ||
| github.com/sirupsen/logrus v1.9.3 // indirect | ||
| github.com/sony/gobreaker v0.5.0 // indirect | ||
| github.com/sosodev/duration v1.3.1 // indirect | ||
| github.com/spf13/pflag v1.0.9 // indirect | ||
| github.com/spiffe/go-spiffe/v2 v2.6.0 // indirect | ||
| github.com/tetratelabs/wazero v1.6.0 // indirect | ||
| github.com/vbauerster/mpb/v8 v8.7.2 // indirect | ||
| github.com/xitongsys/parquet-go v1.6.2 // indirect | ||
| github.com/xitongsys/parquet-go-source v0.0.0-20240122235623-d6294584ab18 // indirect | ||
| github.com/xo/terminfo v0.0.0-20220910002029-abceb7e1c41e // indirect | ||
| github.com/zeebo/xxh3 v1.0.2 // indirect | ||
| go.opentelemetry.io/auto/sdk v1.2.1 // indirect | ||
| go.opentelemetry.io/contrib/detectors/gcp v1.39.0 // indirect | ||
| go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc v0.61.0 // indirect | ||
| go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp v0.61.0 // indirect | ||
| go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploggrpc v0.17.0 // indirect | ||
| go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploghttp v0.17.0 // indirect | ||
| go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetricgrpc v1.41.0 // indirect | ||
| go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetrichttp v1.41.0 // indirect | ||
| go.opentelemetry.io/otel/exporters/otlp/otlptrace v1.41.0 // indirect | ||
| go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc v1.41.0 // indirect | ||
| go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp v1.41.0 // indirect | ||
| go.opentelemetry.io/otel/log v0.17.0 // indirect | ||
| go.opentelemetry.io/otel/metric v1.42.0 // indirect | ||
| go.opentelemetry.io/otel/sdk/log v0.17.0 // indirect | ||
| go.opentelemetry.io/otel/sdk/metric v1.41.0 // indirect | ||
| go.opentelemetry.io/proto/otlp v1.9.0 // indirect | ||
| go.uber.org/multierr v1.11.0 // indirect | ||
| go.uber.org/zap v1.26.0 // indirect | ||
| golang.org/x/crypto v0.48.0 // indirect | ||
| golang.org/x/exp v0.0.0-20251023183803-a4bb9ffd2546 // indirect | ||
| golang.org/x/mod v0.32.0 // indirect | ||
| golang.org/x/net v0.51.0 // indirect | ||
| golang.org/x/sync v0.19.0 // indirect | ||
| golang.org/x/sys v0.41.0 // indirect | ||
| golang.org/x/telemetry v0.0.0-20260109210033-bd525da824e2 // indirect | ||
| golang.org/x/term v0.40.0 // indirect | ||
| golang.org/x/text v0.34.0 // indirect | ||
| golang.org/x/time v0.14.0 // indirect | ||
| golang.org/x/xerrors v0.0.0-20231012003039-104605ab7028 // indirect | ||
| google.golang.org/genproto v0.0.0-20260128011058-8636f8732409 // indirect | ||
| google.golang.org/genproto/googleapis/api v0.0.0-20260226221140-a57be14db171 // indirect | ||
| google.golang.org/genproto/googleapis/rpc v0.0.0-20260226221140-a57be14db171 // indirect | ||
| google.golang.org/grpc v1.79.1 // indirect | ||
| google.golang.org/protobuf v1.36.11 // indirect | ||
| gopkg.in/errgo.v2 v2.1.0 // indirect | ||
| gopkg.in/square/go-jose.v2 v2.6.0 // indirect | ||
| gopkg.in/src-d/go-errors.v1 v1.0.0 // indirect | ||
|
|
||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Clarify B4 status — calendar producer was implemented in this PR.
Line 19 states project/calendar producers return placeholders, but the PR objectives indicate that this PR actually implemented a real Google Calendar integration with OAuth support, event handling, and 10 unit tests. The retrospective should distinguish between what was broken before vs. what this PR fixed.
📝 Suggested clarification
📝 Committable suggestion
🤖 Prompt for AI Agents