microsoft / microsoft/TypeScript-Sublime-Plugin

Type signature popup stops working

Aperta
#430 2 commenti 0 reazioni 1 assegnatario Vedi su GitHub

@zhengbli ci sta già lavorando.

Dal 13/2/2016.

Bug
Lingua principale
JavaScript
Stelle
1.7k
Fork
236
Merge medio
21g 13h
PR unite (30g)
1

Descrizione

I'm running Ubuntu 15.10 and Sublime Text 3 build 3083. The signature popup works fine immediately after starting sublime and writing some code, but after it pops up a few times it stops working (see my third comment for a gif showing what this looks like).

I can reproduce this behavior by simply messing around for a bit inside () blocks (i.e. writing first argument, quicking writing the second one, moving the cursor with my arrow keys etc) but often times the popup will stop working right after the first use and takes no effort to break it.

I've enabled debug level logging and the plugin gets stuck in some kind of infinite loop. This is what it prints out:

2016-01-25 15:23:45,962: 139954225895232: DEBUG: In on_scheduled for work scheduler
2016-01-25 15:23:45,962: 139954225895232: DEBUG: Timer elapsed while prior job running.  Deferring
2016-01-25 15:23:46,014: 139954225895232: DEBUG: In on_scheduled for work scheduler
2016-01-25 15:23:46,014: 139954225895232: DEBUG: Timer elapsed while prior job running.  Deferring
2016-01-25 15:23:46,065: 139954225895232: DEBUG: In on_scheduled for work scheduler

This shows up ad infinitum in my console after the popup stops working.

The regular autocompletition and everything else works fine but the signature tooltip never shows up again. I have to restart sublime to get everything back to normal.

I should also add that I was not able to reproduce this on a windows 10 machine despite trying very hard for a few minutes to mess up the popup. I was however able to reproduce it on another machine running Linux Mint 17.2 but it wasn't as easy as it was on my ubuntu machine.

Guida per i contributori

Nessuna guida per i contributori indicizzata per questo repository

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.

Valutazione

Questa issue non è ancora stata valutata.

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.