Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Potential file descriptor leak

Aperta
  • Qualcosa non va?
#24 10 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 4 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
25/100
Tipo di issue
Bug
Chiarezza
Da chiarire
Stato di attività
Ferma
Ambito
backend

Direzione di ricerca

Start with the call-with-input-file stack entry and the handlers in official/jsonp.rkt, then trace the request through src/site.rkt. Reproduce the package refresh and observe whether repeated requests lead to the reported “Too many open files” error. Done means the leak is identified and the refresh no longer exhausts file descriptors.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

needs-reproducing

I tried updating my packages, and after the next index refresh, raco pkg install still used ye olde version. I went on the package's page to check, and it still showed the old commit hash, and (possibly after I refreshed the page?) there was the error message:

Checksum error : The package checksum does not match the package source code.

bug

I clicked again on the "refresh my packages" and got this error:

Exception
The application raised an exception with the message:

jsonp-rpc!: Illegal response to "https://localhost:9004/jsonp/update?callback=callback1473965235923": "<html><head><title>Servlet Error</title><link rel=\"stylesheet\" href=\"/error.css\"/></head><body><div class=\"section\"><div class=\"title\">Exception</div><p>The application raised an exception with the message:<pre>open-input-file: cannot open input file\n  path: /var/lib/pkgserver/pkg-index/users.new/[email protected]\n  system error: Too many open files; errno=24</pre></p><p>Stack trace:<pre>call-with-input-file*61 at:\n  line 102, column 2, in file /home/pkgserver/racket/collects/racket/private/kw-file.rkt\n&lt;unknown procedure&gt; at:\n  line 49, column 5, in file /home/pkgserver/pkg-index/official/jsonp.rkt\n&lt;unknown procedure&gt; at:\n  line 40, column 2, in file /home/pkgserver/pkg-index/official/jsonp.rkt\n&lt;unknown procedure&gt; at:\n  line 340, column 33, in file /home/pkgserver/racket/collects/racket/contract/private/arrow-higher-order.rkt\n&lt;unknown procedure&gt; at:\n  line 340, column 33, in file /home/pkgserver/racket/collects/racket/contract/private/arrow-higher-order.rkt\n</pre></p></div></body></html>"
Stack trace:

<unknown procedure> at:
  line 129, column 35, in file /home/pkgserver/racket-pkg-website/src/site.rkt
<unknown procedure> at:
  line 340, column 33, in file /home/pkgserver/racket/collects/racket/contract/private/arrow-higher-order.rkt
<unknown procedure> at:
  line 58, column 2, in file /home/pkgserver/racket/share/pkgs/web-server-lib/web-server/dispatchers/dispatch-servlets.rkt
<unknown procedure> at:
  line 340, column 33, in file /home/pkgserver/racket/collects/racket/contract/private/arrow-higher-order.rkt
<unknown procedure> at:
  line 340, column 33, in file /home/pkgserver/racket/collects/racket/contract/private/arrow-higher-order.rkt
<unknown procedure> at:
  line 340, column 33, in file /home/pkgserver/racket/collects/racket/contract/private/arrow-higher-order.rkt
<unknown procedure> at:
  line 131, column 8, in file /home/pkgserver/racket/share/pkgs/web-server-lib/web-server/private/dispatch-server-with-connect-unit.rkt

Feel free to close this if it was just a transient problem. I just thought it would be best to report the issue.

Lingua principale
Racket
Stelle
13
Fork
18
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di racket/racket-pkg-website

Tutte le issue di racket/racket-pkg-website

Issue simili

Altre issue su Backend & API Design

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.