BadHttpRequestException in PluginBundleEndpoints.SpoolUploadAsync

Abierto
  • ¿Algo no está bien?
#8,026 4 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
25/100
Tipo de issue
Error
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
csharp
Área
backend-api-design

Línea de trabajo

Start by locating PluginBundleEndpoints.SpoolUploadAsync and inspect its upload handling alongside the Kestrel BadHttpRequestException details in the incident node at Admin/_LogIncident/1013b7b1c23016aa. The payload gives no request details or reproduction steps, so first identify which request condition triggers the exception. Done means the cause is fixed and the upload behavior is covered by a relevant test.

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

Descripción

bug sev:M

The triage write-up stays on the incident node: the agent reads the raw log lines, so its text is not published (LogWatch:PublishTriageDraft=false).

Evidence
Fingerprint 1013b7b1c23016aa
Category Microsoft.AspNetCore.Diagnostics.ExceptionHandlerMiddleware
Severity Error
Exception Microsoft.AspNetCore.Server.Kestrel.Core.BadHttpRequestException
Top frame Memex.Portal.Shared.Api.PluginBundleEndpoints.SpoolUploadAsync
Namespace memex-cloud 2 occurrence(s), 2026-11-08 20:33:23Z → 2026-11-08 20:33:24Z; pods memex-portal-deployment-785fbdb87d-9jxqj
Occurrences 2
First seen 2026-11-08 20:33:23Z
Last seen 2026-11-08 20:33:24Z
Routing not determined — no configured route matches the category Microsoft.AspNetCore.Diagnostics.ExceptionHandlerMiddleware. This repository is the configured fallback, not a finding about who owns the fault; the category names the LOGGER, which may not be the subject.
Recent sightings
Logged at Pod
2026-11-08 20:33:23Z memex-portal-deployment-785fbdb87d-9jxqj
2026-11-08 20:33:24Z memex-portal-deployment-785fbdb87d-9jxqj

The log lines themselves are not published: formatted log text can carry the values a call site logged. They stay on Admin/_LogIncident/1013b7b1c23016aa on the instance that recorded them.

Opened automatically from Admin/_LogIncident/1013b7b1c23016aa. Recurrences are folded into this issue rather than opening new ones.
It also stands for the whole log site dc0ee3b1d34e8ab0: other fingerprints of this site fold in here as comments rather than opening tickets of their own.

Lenguaje dominante
C#
Estrellas
12
Forks
5
Merge medio
5 h 14 min
PR fusionados (30 d)
957

Preparar el entorno

  • Sin Dockerfile ni archivo de Docker Compose
  • Tiene una plantilla de pull request
  • Sin guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de Systemorph/MeshWeaver

Todos los issues de Systemorph/MeshWeaver

Issues similares

Más issues de C#

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.