racket / racket/typed-racket

Reentrant promise error during check-syntax

Open
#810 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Racket
Stars
575
Forks
106
Avg merge
2h 1m
Merged PRs (30d)
2

Description

I sometimes get this error when working in DrRacket:

internal error: force: reentrant promise `init-current-type-names'
  context...:
   /usr/share/racket/collects/racket/private/promise.rkt:53:8
   /usr/share/racket/collects/racket/private/more-scheme.rkt:265:2: call-with-exception-handler
   f1698
   /usr/share/racket/pkgs/typed-racket-lib/typed-racket/types/printer.rkt:120:0: pretty-format-rep12
   /usr/share/racket/pkgs/drracket-tool-lib/drracket/private/syncheck/annotate.rkt:42:0: add-mouse-over/loc
   /usr/share/racket/pkgs/drracket-tool-lib/drracket/private/syncheck/traversals.rkt:621:2: loop
   /usr/share/racket/pkgs/drracket-tool-lib/drracket/private/syncheck/traversals.rkt:233:18: collect-general-info
   /usr/share/racket/pkgs/drracket-tool-lib/drracket/private/syncheck/traversals.rkt:184:6: level+tail+mod-loop
   /usr/share/racket/pkgs/drracket/drracket/private/syncheck/online-comp.rkt:43:0: build-trace
   .../more-scheme.rkt:261:28
   /usr/share/racket/pkgs/drracket/drracket/private/syncheck/online-comp.rkt:91:5: loop

It seems to be harmless, usually it just stays at the top for a few seconds and then goes away.

I'm not yet sure how to reproduce this reliably, I'll update this issue once I get it.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the stack-trace entry points in drracket-tool-lib/drracket/private/syncheck/annotate.rkt, syncheck/traversals.rkt, and drracket/private/syncheck/online-comp.rkt, then inspect typed-racket-lib/typed-racket/types/printer.rkt. First establish a reliable check-syntax reproduction; done means identifying and preventing the reentrant promise error without breaking the reported annotation flow.

Written by the indexing model from the issue text.

Assessment

Domain
devtools
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.