pingdotgg / pingdotgg/t3code

[Bug]: Snoozed threads dissapeared (auto-settled?)

Open
#11,788 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug via-triage
Dominant language
TypeScript
Stars
23k
Forks
5.9k
Avg merge
11h 14m
Merged PRs (30d)
357

Description

Before submitting
  • I searched existing issues and did not find a duplicate.
  • I included enough detail to reproduce or investigate the problem.
Area

apps/desktop

Steps to reproduce

Running the nightly (although woudl have been 4ish days old)

Couple of days ago I had 8+ snoozed threads, today I had none. My suspicion is that they woke up (believe they were due to wake yesterday) and were auto settled within a minute due to inactivity.

I thought I had the auto settle on activity setting turned off, however when i checked settings it was on. unsure if I was mistaken or somethign enabled it again.

Given the number of threads I do in a day it's hard to search through the settled ones to verify if they're there.

Expected behavior
  • Auto-settle setting shouldn't turn back on if I have it off
  • Threads that wake need a decent grace period before they're auto-settled (maybe reset their timer?)
Actual behavior
  • snoozed threads missing when I look for them
Impact

Major degradation or frequent failure

Version or commit

No response

Environment

Windows

Logs or stack traces

Screenshots, recordings, or supporting files

No response

Workaround

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in apps/desktop by reproducing the report with snoozed threads that are due to wake, then inspect the auto-settle setting and the transition from snoozed to active. Verify whether the threads are being settled immediately and whether the setting changes unexpectedly. Done means the setting remains stable and waking threads are not immediately auto-settled.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.