Skip to content

Update quote in README.md#19

Merged
senamakel merged 1 commit intomainfrom
senamakel-patch-1
Mar 26, 2026
Merged

Update quote in README.md#19
senamakel merged 1 commit intomainfrom
senamakel-patch-1

Conversation

@senamakel
Copy link
Copy Markdown
Member

Removed the phrase 'No Soul. No Humanity.' from the quote by Morgan Freeman.

Removed the phrase 'No Soul. No Humanity.' from the quote by Morgan Freeman.
@senamakel senamakel merged commit 3e4b8db into main Mar 26, 2026
3 of 8 checks passed
@github-actions
Copy link
Copy Markdown
Contributor

PR Protection Rule Violation

This PR targets the main branch, which is protected.

Only automated PRs from the create-develop-to-main-pr.yml workflow are allowed to target main.

Failed validation checks:

  • ❌ Author must be github-actions[bot] (found: senamakel)
  • ❌ Head branch must be develop (found: senamakel-patch-1)
  • ❌ Title must match pattern: chore: merge develop into main or chore: merge develop into main (vX.Y.Z) (found: Update quote in README.md)
  • ❌ Body must contain: "This PR automatically merges changes from develop into main"
  • ❌ PR title must follow conventional commit format: <type>: <description>
    Allowed types: feat, fix, chore, refactor, docs, test, style, perf, revert
    Example: feat: add new authentication endpoint

To merge changes into main:

  1. Create your PR targeting the develop branch instead
  2. Once merged to develop, the automated workflow will create a PR from develop to main

Please update this PR to target develop instead, or close it and create a new PR targeting develop.

@senamakel senamakel deleted the senamakel-patch-1 branch March 26, 2026 21:28
sanil-23 added a commit to sanil-23/openhuman that referenced this pull request Apr 28, 2026
…ems)

tinyhumansai#4  gmail unknown bucket — orphan:{id} fallback instead of collapsing
    all no-address messages into one "unknown" source tree; messages with
    neither address nor id are dropped with a warn (skip sentinel).

tinyhumansai#5  PII in gmail/ingest.rs — participants, source_id, and owner wrapped
    with redact() before logging; no email addresses in log output.

tinyhumansai#7  PII in chunker.rs — source_id in debug logs replaced with
    redact(source_id) hash.

tinyhumansai#8  Parent dir fsync after rename in atomic.rs — on Unix, open the parent
    directory and call sync_all() after a successful rename so the dirent
    is durable across a crash; best-effort warn on failure, non-fatal.

tinyhumansai#9  Body verify on re-stage in atomic.rs — when the path already exists,
    read and hash the on-disk body; if sha differs from the new body,
    remove the stale file and re-write atomically so SQLite content_sha256
    always matches the on-disk bytes. New unit test covers the re-write path.

tinyhumansai#10 PII in paths.rs — malformed source_id fallback log now emits
    redact(source_id) instead of the raw string.

tinyhumansai#11 PII in read.rs — sha256 mismatch warn logs now emit
    redact(abs_path) instead of abs_path.display().

tinyhumansai#13 Same-tx enqueue in handle_extract — append_buffer and topic_route
    jobs are built before the transaction opens and enqueued via
    enqueue_tx() inside the same tx that commits the lifecycle update,
    eliminating the crash window where lifecycle commits but jobs are lost.

tinyhumansai#16 PII in score/extract/mod.rs — LLM extractor info! log demoted to
    debug! and endpoint wrapped with redact_endpoint() to strip
    path/query/credentials from the URL.

tinyhumansai#17 Non-email scope slug in bucket_seal.rs — only the gmail: prefix is
    stripped before slugify; all other source kinds (slack:, discord:,
    document:, …) slugify the full scope string so slack:#eng and
    discord:#eng no longer produce the same "eng" slug and collide in
    summaries/source/.

tinyhumansai#18 Don't commit summary on stage_summary failure — bucket_seal.rs,
    global_tree/digest.rs, and global_tree/seal.rs now propagate
    stage_summary errors via .context()?  instead of falling back to a
    NULL content_path row; the seal is retried via the normal job-retry
    path. insert_summary_tx callers in those three paths now always pass
    Some(&staged) instead of Option.

tinyhumansai#20 PII in topic_tree/backfill.rs — all entity_id occurrences in log
    lines (info/debug/warn) replaced with redact(entity_id).

New shared helper: src/openhuman/memory/tree/util/redact.rs
  - redact(s)          → stable 8-hex-char SHA-256 prefix for PII fields
  - redact_endpoint(u) → host:port only (strips scheme, creds, path, query)
  - Full unit-test coverage for both helpers

Items tinyhumansai#14 (lease tokens) and tinyhumansai#19 (preview-vs-disk reader audit)
intentionally deferred to follow-up commits — both have larger blast
radius and need separate review.

Items tinyhumansai#1, tinyhumansai#12, tinyhumansai#15 pushed back on PR thread (verified false positive or
covered by upstream contract).

Items #2, tinyhumansai#3 deferred (pre-existing in slack_backfill.rs, not introduced
by this PR).

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
sanil-23 added a commit to sanil-23/openhuman that referenced this pull request Apr 28, 2026
… in path util, last-@ for endpoint redact

Three small correctness fixes from the CodeRabbit re-review of the
preview-vs-disk reader audit (tinyhumansai#19) and surrounding work:

- read_chunk_body / read_summary_body now compare the on-disk body's
  sha256 to the value stored in SQLite at write time. Mismatch returns
  Err rather than silently serving corrupt bytes into the LLM
  pipeline. The previous code computed the sha but discarded it.

- summary_rel_path no longer panics when date_for_global is None for
  the Global tree kind. A path utility shouldn't take the process
  down; falls back to an `unknown-date` sentinel segment with a warn
  log surfacing the caller bug. Test flipped from #[should_panic] to
  asserting the sentinel.

- redact_endpoint splits the authority on the LAST `@` (rsplit_once)
  instead of the first, so URLs with `@` in user-info segments
  (e.g. `https://user:p@ass@host.com`) extract the host correctly.
  Also tightened the order-of-operations: take the authority first
  (cut at /?#), then split userinfo within it, so a `@` in path or
  query string can't be misread as a userinfo separator.

Addresses CodeRabbit comments 3157361914, 3157361930, 3157361952.

Co-Authored-By: Claude Opus 4.7 (1M context) <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