403unlocker / 403unlocker/403unlocker-cli

Truncated Output Table on Dropped Requests

Open
#38 0 comments 0 reactions 1 assignee Claimed by @ArmanTaheriGhaleTaki View on GitHub
bug
Dominant language
Go
Stars
75
Forks
13
PR merge metrics
No merged PRs in 30d

Description

**Describe the bug**
When running 403unlocker check spotify.com, the tool fails to display the complete results table if some DNS server requests are dropped or time out. The table renders partially (often just headers) instead of showing all resolved entries with appropriate error labels (e.g., Timeout or Dropped).
**To Reproduce**

1. Command:

```
403unlocker check spotify.com
```

2. Observed Behavior:

- Output stalls after a few rows (example below).

- No timeout warning or visual feedback for dropped requests.

**Expected behavior**
A clear and concise description of what you expected to happen.

**Screenshots**

![Image](https://github.com/user-attachments/assets/a70705f9-0bd1-4485-948e-bf763b9cc994)

**Desktop (please complete the following information):**
- OS: ubuntu 22.04
- Version: 403unlocker v1.2.3

Contributor guide

No contributing guide indexed for this repository

Research direction

Look at the code that prints the results table, likely in a command like 'check'. Find where DNS server responses are collected and formatted. The bug is about handling dropped/timeout responses in the output rendering. Run the tool with a target that causes timeouts to see the partial output. Check the table rendering logic for early exits or missing error case handling.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, shell
Domain
cli, networking
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.