mirror of
https://github.com/hanzoai/insights.git
synced 2026-11-03 00:52:32 +00:00
zeekay
1b367e2b62
The tree was a debranded snapshot of upstream taken around 2026-02-20, and upstream has moved about five months since. This replaces it with upstream master, mechanically re-derived: bin/debrand does the rename, and the pipeline and squashed migrations are restored from the shipped tree. Not a merge. The previous import replaced the tree wholesale in a single commit, so there is no shared content history to merge against. Reproducing the rename on the new tree is what actually converges. What survives: .hanzo/workflows, the Dockerfiles and bin/docker* entrypoints, compose files, LLM.md, and insights/migrations. The squashed initial migration is load-bearing — the live database records it by name, so upstream's ~918 individual migrations cannot come back. Nine products are dropped as unreferenced. Twenty-one more that we do not run are kept anyway because the core app still imports them; unpicking those is a refactor and does not belong in a rebase. This base does not build yet, and the reasons are not in the rename: upstream now wants Python 3.13.13 against our 3.12.12 and Django 5.2 against our 4.2, and the dependency manifests still name upstream packages that we republish under our own names. Those are decisions, not renames.
59 lines
2.1 KiB
YAML
59 lines
2.1 KiB
YAML
# Flags datetime.now() and similar time-dependent calls in test methods that lack
|
|
# @freeze_time protection. These cause flaky failures when CI runs near midnight UTC
|
|
# because events land in a different day bucket than the assertion expects.
|
|
#
|
|
# See: https://github.com/Insights/insights/pull/48675 for context
|
|
rules:
|
|
- id: test-datetime-now-without-freeze
|
|
patterns:
|
|
- pattern-either:
|
|
- pattern: datetime.now(...)
|
|
- pattern: datetime.utcnow(...)
|
|
- pattern: datetime.today(...)
|
|
- pattern: dt.datetime.now(...)
|
|
- pattern: dt.datetime.utcnow(...)
|
|
- pattern: dt.datetime.today(...)
|
|
- pattern: date.today()
|
|
- pattern: dt.date.today()
|
|
- pattern: timezone.now(...)
|
|
- pattern: django_timezone.now(...)
|
|
- pattern-inside: |
|
|
def $FUNC(...):
|
|
...
|
|
- metavariable-regex:
|
|
metavariable: $FUNC
|
|
regex: ^test_
|
|
- pattern-not-inside: |
|
|
@freeze_time(...)
|
|
def $F(...):
|
|
...
|
|
- pattern-not-inside: |
|
|
@freeze_time(...)
|
|
class $C(...):
|
|
...
|
|
- pattern-not-inside: |
|
|
@freeze_time(...)
|
|
class $C:
|
|
...
|
|
- pattern-not-inside: |
|
|
with freeze_time(...):
|
|
...
|
|
- pattern-not-inside: |
|
|
with freeze_time(...) as $FT:
|
|
...
|
|
message: |
|
|
`datetime.now()` (or similar) in a test without `@freeze_time` causes
|
|
flaky failures when CI runs near midnight UTC. Wrap the test method or
|
|
class with `@freeze_time("...")` or use `with freeze_time("..."):`.
|
|
languages: [python]
|
|
severity: WARNING
|
|
metadata:
|
|
category: correctness
|
|
subcategory: audit
|
|
confidence: HIGH
|
|
paths:
|
|
include:
|
|
- '**/test_*.py'
|
|
- '**/test/**/*.py'
|
|
- '**/tests/**/*.py'
|