RagLeap
Contributor
@Nitjsefnie · active 2026-10-24 to 2026-10-25 · took part in 11 issues/PRs

Peter Z

Public record of Peter Z's work on RagLeap (ragleap-core), with a link to every item. GitHub profile.

Summary

5 pull requests (5 merged), 5 issues opened, 12 comments, 1 review, 1 inline review comment, 5 commits.

Pull requests (5)

Issues opened (5)

Comments on issues and pull requests (12)

  • 2026-10-25 · on #950 Voice channel sends headerless mu-law audio to STT providers labeled as WAV — comment: “Fixed by 951, now merged: each buffered Twilio mu-law utterance is converted to mono 16-bit 8 kHz WAV before it reaches either STT provider (OpenAI or Deepgram), with regression tests. The TTS directi…”
  • 2026-10-25 · on #952 feat: Google Calendar event scheduling as an outbound autonomy action — comment: “Synced with latest main — the CRM sender and the calendar sender now sit side by side behind the same approval gate, the logging fix and all its tests are preserved, and CI is green on the new head c4…”
  • 2026-10-25 · on #953 feat: HubSpot CRM record updates as an outbound autonomy action — comment: “Heads-up: this branch lives in an organization-owned fork, and GitHub doesn't let maintainers push to those. If anything needs changing, just say so here and I'll make the change on this branch right…”
  • 2026-10-24 · on #258 Autonomy Loop: contribute new autonomous action types — comment: “I'd like to claim the CRM record updates action type: a HubSpot action that updates allowlisted properties of an existing record and runs through executeorrequest (modes, both allowlists, semi-mode ap…”
  • 2026-10-24 · on #952 feat: Google Calendar event scheduling as an outbound autonomy action — comment: “Heads-up: this branch lives in an organization-owned fork, and GitHub doesn't let maintainers push to those. If anything needs changing, just say so here and I'll make the change on this branch right…”
  • 2026-10-24 · on #258 Autonomy Loop: contribute new autonomous action types — comment: “I'd like to claim the calendar scheduling action type: a Google Calendar event action that runs through executeorrequest (modes, both allowlists, semi-mode approval and the sensitive-role guardrail),…”
  • 2026-10-24 · on #951 Add Deepgram (STT) and ElevenLabs (TTS) as alternative Voice providers — comment: “Heads-up: this branch lives in an organization-owned fork, and GitHub doesn't let maintainers push to those. If anything needs changing, just say so here and I'll make the change on this branch right…”
  • 2026-10-24 · on #944 [BUG] Telegram webhook secret check raises TypeError (HTTP 500) on a non-ASCII secret-token header instead of 403 — comment: “Opened 947 with the fix: both sides of the webhook-secret comparison are now encoded as UTF-8 bytes with surrogatepass (the same comparison SecretStr.eq already uses), so a non-ASCII header or configu…”
  • 2026-10-24 · on #947 fix: compare Telegram webhook secret as UTF-8 bytes so non-ASCII tokens 403 instead of 500 — comment: “Heads-up: this branch lives in an organization-owned fork, and GitHub doesn't let maintainers push to those. If anything needs changing, just say so here and I'll make the change on this branch right…”
  • 2026-10-24 · on #932 feat: Meta WhatsApp Cloud API provider (WHATSAPP_PROVIDER=meta) — comment: “Done: the Meta and Twilio webhook credential comparisons now compare bytes instead of raw strings, so a non-ASCII signature header or verify token is rejected with the existing 403 instead of raising…”
  • 2026-10-24 · on #932 feat: Meta WhatsApp Cloud API provider (WHATSAPP_PROVIDER=meta) — comment: “The scan's findings were genuine: five fixture strings in tests/testwhatsappmeta.py weren't placeholder-prefixed, so the scanner flagged them as hardcoded secrets. They're renamed to example- values a…”
  • 2026-10-24 · on #932 feat: Meta WhatsApp Cloud API provider (WHATSAPP_PROVIDER=meta) — comment: “Heads-up: this branch lives in an organization-owned fork, and GitHub doesn't let maintainers push to those. If anything needs changing, just say so here and I'll make the change on this branch right…”

Pull request reviews (1)

  • 2026-10-24 · commented on #932 feat: Meta WhatsApp Cloud API provider (WHATSAPP_PROVIDER=meta) — review

Inline review comments (1)

  • 2026-10-24 · inline comment on #932, channels/whatsapp/router.py — view: “The failure log now records only the status code and reason — the Graph response body no longer reaches it (fd8e65a). Operators do lose Meta's error text in that log; if you'd rather keep the body and…”

Commits (5)

How to verify this record

Everything above comes from the public GitHub API for ragleap/ragleap-core. Check it yourself: pull requests · issues opened · issues and PRs commented on · reviews · commits. GitHub is the source of truth.

Compiled from the GitHub API on 2026-10-25. To correct or remove this page, open an issue.

All contributors