microsoft / microsoft/vscode-github-issue-notebooks
Notebook grabs ad-hoc REPOS even when REPOS specified
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 237
- Forks
- 37
- PR merge metrics
- No merged PRs in 30d
Description
Type: Bug
- Clone the microsoft/vscode repository.
- Run the endgame.github-issues notebook.
- The notebooks take forever to run and I get rate-limited. I also see results from Azure/azure-cli and sourcegraph/sourcegraph show up even though those aren't specified repos under $REPOS.
Extension version: 0.0.130
VS Code version: Code - Insiders 1.88.0-insider (246d700c4604eb5ebdbb561a1a86562bf9217a62, 2024-03-27T05:50:10.528Z)
OS version: Windows_NT x64 10.0.22631
Modes:
System Info
| Item | Value |
|---|---|
| CPUs | Intel(R) Core(TM) i7-1065G7 CPU @ 1.30GHz (8 x 1498) |
| GPU Status | 2d_canvas: enabled canvas_oop_rasterization: enabled_on direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled multiple_raster_threads: enabled_on opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok skia_graphite: disabled_off video_decode: enabled video_encode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled webgpu: enabled |
| Load (avg) | undefined |
| Memory (System) | 31.60GB (16.61GB free) |
| Process Argv | --crash-reporter-id 4c04ed84-a786-470f-a717-2c55c63c7b0c |
| Screen Reader | no |
| VM | 0% |
A/B Experiments
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805:30301674
vsaa593:30376534
py29gd2263:30784851
c4g48928:30535728
962ge761:30841072
pythongtdpath:30726887
welcomedialog:30812478
pythonidxpt:30768918
pythonnoceb:30776497
asynctok:30898717
dsvsc013:30777762
dsvsc014:30777825
dsvsc015:30821418
pythontestfixt:30866404
pythonregdiag2:30926734
pyreplss1:30879911
pythonmypyd1:30859725
pythoncet0:30859736
h48ei257:31000450
pythontbext0:30879054
accentitlementst:30870582
dsvsc016:30879898
dsvsc017:30880771
dsvsc018:30880772
bf62j303:30968145
cppperfnew:30980852
d34g3935:30961436
fegfb526:30952798
bg6jg535:30979844
ccp1r6:30958151
pythonait:30973460
7ghi1836:30988844
gd77d436:30999572
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by running the endgame.github-issues notebook with REPOS set to a specific repository and compare its results with the reported Azure/azure-cli and sourcegraph/sourcegraph entries. Trace how REPOS is read and how repositories are selected; done means only specified repositories are queried and the run no longer performs unnecessary work that causes rate limiting.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- jupyter-notebook, typescript
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100