403unlocker / 403unlocker/403unlocker-cli

Truncated Output Table on Dropped Requests

Abierto
#38 0 comentarios 0 reacciones 1 asignado Reclamado por @ArmanTaheriGhaleTaki Ver en GitHub
bug
Lenguaje dominante
Go
Estrellas
75
Forks
13
Métricas de merge de PR
Sin PR fusionados en 30 d

Descripción

**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

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Evaluación

Stack tecnológico
go, shell
Área
cli, networking
Tipo de issue
Error
Dificultad
3/5
Tiempo estimado
1-2 días
Estado de actividad
Estancado
Claridad
Bastante claro
Aptitud para principiantes
45/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.