Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Pull request list empty

See original GitHub issue

Issue Type: Bug

Seems like there is an issue that no pullrequests are received from github?

{
	"activationTimes": {
		"startup": true,
		"codeLoadingTime": 70,
		"activateCallTime": 2,
		"activateResolvedTime": 41,
		"activationEvent": "*"
	}
}

CPU-20181011T075358.129Z.cpuprofile.txt

Extension version: 0.2.0 VS Code version: Code - Insiders 1.29.0-insider (f151c46b1783cf4f9a4ca934a85f78846f08688e, 2018-10-11T05:11:48.238Z) OS version: Darwin x64 17.7.0

System Info

Item	Value
CPUs	Intel® Core™ i7-4980HQ CPU @ 2.80GHz (8 x 2800)
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)	2, 2, 2
Memory (System)	16.00GB (0.28GB free)
Process Argv	-psn_0_1315137
Screen Reader	no
VM	0%

Issue Analytics

State:
Created 5 years ago
Comments:12 (5 by maintainers)

Top GitHub Comments

4reactions

PoisonousJohncommented, Apr 5, 2019

I have a bit different case

[Info] Looking for git repository
[Info] Git repository found, initializing review manager and pr tree view.
[Info] No GitHub remotes found
[Info] Review> no matching pull request metadata found for current branch master
[Info] Found GitHub remote
[Info] https://api.github.com: GraphQL support detected
[Info] Review> no matching pull request metadata found for current branch master

I have multiple source control providers, can it be because of that?

3reactions

RMacfarlanecommented, Feb 22, 2019

@einord From a recent change, the extension now looks for remotes named origin and upstream by convention and displays PRs from those - you can configure this with the githubPullRequests.remotes setting