Comunidad Guías…

Ayuda y problemas de piper-morgan-product

Pregunta a la comunidad o invita a KiBot con contexto del repositorio.

Publicar un problema

No publiques contraseñas, tokens ni claves privadas. HostingByte aplica una redacción básica de secretos evidentes antes de guardar el texto.

Problemas en HostingByte

Todavía no hay problemas publicados.

Issues abiertas upstream

#2350 Hosts drop every info log line (root WARNING from the CLI quiet mode); evidence events need a named logger kept at INFO · 2 comentarios #2333 Slack spatial positions use salted hash(): a room's position changes on every process start · 4 comentarios #2348 /health should report Redis, as it does the database and the credential store · 4 comentarios #2189 Integrations 'Last checked' lives only in process memory, so every deploy resets it; plus a sweep for other user-facing state that does the same · 16 comentarios #2345 GitHub and Calendar connect keep their sign-in state in the process, not Redis · 2 comentarios #2335 RedisFactory logs the full REDIS_URL at startup; an Upstash URL carries the password · 4 comentarios #2344 Buttondown confirmations: read the sending-domain setup and check SPF/DKIM/DMARC (split from 2292) · 3 comentarios #2349 EPIC: Piper self-knowledge: codebase, ethos, documentation, lore and best practices (design exploration first; Arch owns) · 3 comentarios #2347 Remove two dead Redis paths: the conversation manager's turn cache and FeedbackCapture · 1 comentarios #1186 PIPER-SELF-KNOWLEDGE: support info + help-doc pointers + RAG over own docs (so Piper can answer 'how do you work?') · 1 comentarios #1423 Silent-death pattern: broad try/except on the core path converts broken features into invisible defaults — inventory + un-swallow · 7 comentarios #2343 One command for the GitHub App cutover sitting: set the App's values and run the cutover, secret never in argv (issue 2342's step 3 and 4) · 4 comentarios #2342 Build ADR-081 D3: GitHub connect through one published GitHub App, with user tokens that expire and refresh · 16 comentarios #2261 GitHub connect requests the classic `repo` scope (full read/write on every repo the login reaches); narrow it per ADR-081 D3, or to the narrowest classic scope on the OAuth-App fallback · 5 comentarios #2341 One command with hidden prompts for procedures where xian holds the secrets (first: ADR-081 D3's refresh check) · 3 comentarios #2163 GitHub identity: one app/token model and whose token serves a read (ADR plus carrying it into the six issues) · 6 comentarios #2174 ADR-081 D3 check: do github-mcp-server and our REST reads accept a GitHub App user access token? · 2 comentarios #2339 Local fault run: the failed-preferences line on the Slack, Calendar and Notion settings pages (the unserved rest of 2154) · 0 comentarios #2231 Tracking: eleven close:pins-only closes whose failure path was never served on alpha (xian's beta test: 'fully tracking anything we know isn't working yet') · 10 comentarios #2330 "make take care of mean mark it done" changes "clear" when clear is stored: the classifier names the clear alias for the take-care-of verb · 3 comentarios