Skip to content

DB interface 2: raw files read API, three alerts, status page - #300

Open
mschwoer wants to merge 2 commits into
refactor_db_IIfrom
refactor_db_III
Open

mschwoer wants to merge 2 commits into
refactor_db_IIfrom
refactor_db_III

Conversation

@mschwoer

Copy link
Copy Markdown
Contributor

Stacked on #299.

  • Raw files read API with a Mongo backend
  • Three alerts and the status page use it
  • as_utc is None-safe, status filter field, order syntax documented

🤖 Generated with Claude Code

mschwoer and others added 2 commits November 6, 2026 18:30
…status page

---
# Conversation that produced these changes
---

## User prompt

"next slice please"

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
…ntax

---
# Conversation that produced these changes
---

## User prompt

"@monitoring/alerts/instrument_stall_alert.py this is just the default?  as_utc could be None-safe, could remove as_utc_or_none then. @shared/db/raw_files.py isn't this a mongodb implementation detail? RawFileFilter has "backup_status" but only "statuses" .. add
  "status: str" ?"

## Clarifying round 1

Q: In shared/db/raw_files.py, which part do you see as a MongoDB implementation detail? My reading is the `"-created_at"` order syntax (mongoengine's, also Django's).
  - The order syntax: keep it  <-- chosen
  - The order syntax: replace it
  - Something else

## User prompt

"ad order syntax: add a comment"

## User prompt

"well, it is a provider detail, right? just happens to be a widely accepted one"

## User prompt

"I changed the comment once more"

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant