hackclub / hackclub/lapse

Timelapses show Hackatime tracking but no time is recorded

Open
#276 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
25
Forks
27
PR merge metrics
No merged PRs in 30d

Description

## Summary

Two Lapse timelapses show **“tracked on Hackatime as `Observatory`”**, but their time is not recorded in Hackatime.

## Reproduction

1. Use the Lapse account [@johann_eugen](https://lapse.hackclub.com/user/@johann_eugen).
2. Publish a timelapse and select the Hackatime project `Observatory`.
3. Wait for processing to finish.
4. Check the [Hackatime Observatory project](https://hackatime.hackclub.com/my/projects/Observatory).

Affected timelapses:

- **Heat Set inserts** — 26 minutes — shown as `UNLISTED`
- **breadboard** — 33 minutes — shown as `UNLISTED`

## Expected behavior

Each processed timelapse snapshot should be synced to Hackatime under the selected project, and the recorded time should appear in the project.

## Actual behavior

Lapse displays **“tracked on Hackatime as `Observatory`”**, but Hackatime has no corresponding recent time or timelapse heartbeats for these recordings. A check of the Aug 26–27 time window showed **0 seconds** for `Observatory`.

The existing historical `Observatory` time is present, so the account and project mapping itself works.

## Request

Please requeue/replay the Hackatime snapshot sync for these two timelapses. Also consider exposing sync success/failure and allowing a retry when the background sync fails.

Related: #232

Contributor guide

Open the contributing guide

Research direction

Start with the Hackatime snapshot-sync background job and compare processing for the two affected timelapses against the working historical Observatory time; related issue #232 may provide context. Requeue the two snapshots, verify their heartbeats appear in Hackatime, and confirm that sync failures are visible and retryable if that part is included.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
api, backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.