Key dates from Bluesky - #105
Conversation
|
Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Team Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe event data now includes sourced registration, DJS, hotel, and volunteer key dates across four events. ChangesEvent metadata
Estimated code review effort: 1 (Trivial) | ~3 minutes Merge Risk: 🔵 Low · up to The change adds Bluesky-sourced key dates to four event records. Two entries use observation times rather than the source posts' exact creation times, so their provenance metadata may be inaccurate; the change remains localized and mergeable with explicit owner follow-up. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Full details: Docstring CoverageExplanation No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.) ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
e18ed31 to
4b285c8
Compare
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Team
Run ID: 85391ddc-ad64-4892-ba93-87cf6b6dc3da
📒 Files selected for processing (1)
new-anthrodam.json
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.
| "closes": { | ||
| "date": "2026-10-04", | ||
| "source": "https://bsky.app/profile/did:plc:7creot4gvsnj3vdiyudqvo6p/post/3muiuqhcqys2z", | ||
| "asOf": "2026-09-02T02:20:12.501Z", |
There was a problem hiding this comment.
🗄️ Data Integrity & Integration | 🟡 Minor | ⚡ Quick win
Use the source post's createdAt for asOf.
The documented contract defines asOf as the source post's creation timestamp. The linked post reports 2026-09-02T02:20:14.498Z, but this entry stores 2026-09-02T02:20:12.501Z. Update the value to preserve provenance. (bsky.app)
Proposed fix
- "asOf": "2026-09-02T02:20:12.501Z",
+ "asOf": "2026-09-02T02:20:14.498Z",📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| "asOf": "2026-09-02T02:20:12.501Z", | |
| "asOf": "2026-09-02T02:20:14.498Z", |
Source: MCP tools
4188e33 to
4819bd1
Compare
There was a problem hiding this comment.
Actionable comments posted: 1
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Team
Run ID: fb07c630-13a6-4f36-b8c2-957862cd99f7
📒 Files selected for processing (1)
new-years-furry-ball.json
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.
| "opens": { | ||
| "date": "2026-08-02", | ||
| "source": "https://bsky.app/profile/did:plc:ha7l7zxbpoqmo7iifjyizdg4/post/3ms4jr7nmuc2u", | ||
| "asOf": "2026-08-02T17:41:26.750Z", |
There was a problem hiding this comment.
🗄️ Data Integrity & Integration | 🟡 Minor | ⚡ Quick win
Use the exact source createdAt for asOf.
The documented contract defines asOf as the source post's creation timestamp. The hotel post was created at 2026-08-02T17:41:23.171Z, but the entry stores 2026-08-02T17:41:26.750Z. The volunteer post was created at 2026-09-01T15:21:14.909Z, but the entry stores 2026-09-01T15:21:25.222Z. (bsky.app)
Update both values to preserve accurate provenance.
Proposed correction
- "asOf": "2026-08-02T17:41:26.750Z",
+ "asOf": "2026-08-02T17:41:23.171Z",
...
- "asOf": "2026-09-01T15:21:25.222Z",
+ "asOf": "2026-09-01T15:21:14.909Z",Also applies to: 90-90
Source: MCP tools
de81c5a to
1b021cf
Compare
1b021cf to
12cb526
Compare
1 participant
Key dates from Bluesky
Extract:
openai/gpt-oss-20b· Verify (unanimous):openai/gpt-oss-120b+openai/gpt-oss-20b· 2026-09-02Applied (unanimously verified —
/reject <event> <category>.<kind>to drop a bad entry for good)wild-furloween-west.json —
wild-furloween-west-2026djs.opens → 2026-08-08 (add, conf 1.0)confuzzled.json —
confuzzled-2027registration.opens → 2026-09-07 (add, conf 1)new-anthrodam.json —
new-anthrodam-2026djs.closes → 2026-10-04 (add, conf 1.0)new-years-furry-ball.json —
new-years-furry-ball-2027hotel.opens → 2026-08-02 (add, conf 0.95)new-years-furry-ball.json —
new-years-furry-ball-2027volunteers.opens → 2026-09-01 (add, conf 0.9)Refuted by verification (not applied)
wild-furloween-west-2026registration.closes 2026-08-01 — The post only mentions a discount for registering before August 1 and that higher prices apply after that date; it does not state that registration itself endsSummary by CodeRabbit