microsoft / microsoft/TypeScript-Sublime-Plugin

Type signature popup stops working

Ouverte
#430 2 commentaires 0 réactions 1 personne assignée Voir sur GitHub

@zhengbli y travaille déjà.

Depuis le 13/2/2016.

Bug
Langage dominant
JavaScript
Étoiles
1.7k
Forks
236
Merge moyen
21 j 13 h
PR mergées (30 j)
1

Description

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.

Guide de contribution

Aucun guide de contribution indexé pour ce dépôt

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Évaluation

Cette issue n'a pas encore été évaluée.

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.