Pigamer37/buta-no-subs-stremio-addon

Crash

Open

#21 opened on Jun 14, 2026

View on GitHub
 (0 comments) (0 reactions) (0 assignees)JavaScript (3 forks)auto 404
bughelp wanted

Repository metrics

Stars
 (10 stars)
PR merge metrics
 (PR metrics pending)

Description

This happens:

Entered HandleSubRequest with /subtitles/series/tmdb:0.json
Got a series with TMDB ID: 0
Extra parameters: undefined
Didn't get AniList entry from TMDB ID because: Error: Empty response!
    at /home/kbs-lucas/Documents/GitHub/buta-no-subs-stremio-addon/routes/anilist.js:102:36
    at process.processTicksAndRejections (node:internal/process/task_queues:103:5)
Failed on anime metadata gathering: Error: HTTP error! Status: 404
/home/kbs-lucas/Documents/GitHub/buta-no-subs-stremio-addon/routes/metadata_copy.js:108
        if ((!resp.ok) || resp.status !== 200) reject(new Error(`HTTP error! Status: ${resp.status}`))
                                                      ^

Error: HTTP error! Status: 404
    at /home/kbs-lucas/Documents/GitHub/buta-no-subs-stremio-addon/routes/metadata_copy.js:108:55
    at process.processTicksAndRejections (node:internal/process/task_queues:103:5)

Node.js v24.13.1

But it should be handled with the catch on line 204. You can even see the console.log it produces in the logs!!! I don't know why this is happening.

Contributor guide

Research direction
Examine the catch block on line 204 of metadata copy.js to understand why the HTTP error (404) is not being caught. Check if the catch is in the correct scope (e.g., inside a promise chain) and if the error is being thrown before the catch can handle it.
Tech stack
javascriptnodejsexpress
Domain
backendapi
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitJavaScript
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70