Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Suggestion trigger characters not inserted #64257

Closed
mjbvz opened this issue Dec 3, 2018 · 6 comments
Closed

Suggestion trigger characters not inserted #64257

mjbvz opened this issue Dec 3, 2018 · 6 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug suggest IntelliSense, Auto Complete
Milestone

Comments

@mjbvz
Copy link
Collaborator

mjbvz commented Dec 3, 2018

Issue Type: Bug

Repo

  1. In a js file
  2. Type consol
  3. Press . to accept console suggestion

Bug
Only console inserted. The . is dropped

VS Code version: code-oss-dev 1.30.0 (Commit unknown, Date unknown)
OS version: Darwin x64 18.2.0

System Info
Item Value
CPUs Intel(R) Core(TM) i7-4770HQ CPU @ 2.20GHz (8 x 2200)
GPU Status 2d_canvas: enabled
checker_imaging: disabled_off
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
native_gpu_memory_buffers: enabled
rasterization: enabled
video_decode: enabled
video_encode: enabled
webgl: enabled
webgl2: enabled
Load (avg) 3, 3, 2
Memory (System) 16.00GB (0.34GB free)
Process Argv .
Screen Reader no
VM 25%
@mjbvz mjbvz added the suggest IntelliSense, Auto Complete label Dec 3, 2018
@mjbvz
Copy link
Collaborator Author

mjbvz commented Dec 3, 2018

Result of of c2c2e48 I think. Looks like a race:

  • If I get rid of the await in _onDidSelectItem, it works.
  • Not related to the resolve itself. If I change the await to await new Promise(resolve => setTimeout(resolve, 0));, it also doesn't work

@mjbvz mjbvz added this to the November 2018 milestone Dec 3, 2018
@mjbvz
Copy link
Collaborator Author

mjbvz commented Dec 3, 2018

@jrieken I'm reverting c2c2e48 so that it does not hit insiders. Still looking into fix

@mjbvz
Copy link
Collaborator Author

mjbvz commented Dec 4, 2018

Sorry @jrieken, I took a look but am not sure how about this one. c2c2e48 would be nice to have but is not a regression so it's not essential for November

@jrieken
Copy link
Member

jrieken commented Dec 4, 2018

Fair enough - making the insert-call async was a bold move ;-). Moving this to December for a proper fix

@jrieken jrieken added the bug Issue identified by VS Code Team member as probable bug label Dec 4, 2018
@jrieken jrieken modified the milestones: November 2018, December 2018 Dec 4, 2018
@mjbvz
Copy link
Collaborator Author

mjbvz commented Jan 21, 2019

Potential related: #42544 Support suppressing commit character from being inserted during completion

@mjbvz mjbvz modified the milestones: December/January 2019, Backlog Jan 21, 2019
@jrieken
Copy link
Member

jrieken commented May 19, 2019

Closing this in favour of #73311 and/or #63013. Both have the same root cause which is us not always resolving completions before inserting...

@jrieken jrieken closed this as completed May 19, 2019
@vscodebot vscodebot bot locked and limited conversation to collaborators Jul 3, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug suggest IntelliSense, Auto Complete
Projects
None yet
Development

No branches or pull requests

2 participants