GitHub org import through the gh CLI has no request deadline
Maintainers usually reply within 1 day
A pull request for this has already been merged.
- #1403 by @Smilewithoutfalling — merged
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 78/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- github, node.js, typescript
Research direction
Start with src/providers/github/gh-org.ts:26 and src/providers/github/gh-cli.ts:50 to trace how ghApiPage calls ghExec and how timeoutMs is handled. Compare the REST listing deadline and its error path. Add the matching deadline so a stalled gh call fails before whitelist generation and is not swallowed by the page 1 fallback; verify with the stand-in gh api described in the issue.
Written by the indexing model from the issue text.
Description
What happens
teamai import --from-org against GitHub can still wait forever when the gh CLI is installed, which is the usual setup. #1381 gave the REST listing a 30-second deadline per page, but the gh path lists pages through ghApiPage (src/providers/github/gh-org.ts:26), which calls ghExec without timeoutMs. A gh api call that never returns keeps the import from reaching whitelist generation or its error handler.
Found while reviewing #1381: with a stand-in gh api that never returns, the import was still running after 65 s. Read from the code on main (157516d4) and run with that stand-in, not against a stalled GitHub.
Possible fix
ghExec already accepts timeoutMs (src/providers/github/gh-cli.ts:50). Passing the same 30-second deadline from ghApiPage would match the REST path. The timeout has to fail the import before any whitelist is written, as the REST path does, and should not be swallowed by the /orgs to /users fallback on page 1.
- Dominant language
- TypeScript
- Stars
- 5.6k
- Forks
- 471
- Avg merge
- 22h 54m
- Merged PRs (30d)
- 347
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from Tencent/teamai-cli
-
enhancement question
Difficulty 5/5 Over a week Newbie friendliness 45/100
Tencent/teamai-cli#1429 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 45/100
Tencent/teamai-cli#1426 · 1 comment ·
Maintainers usually reply within 1 day
-
[bug] Codebase import: --skip-enrich drops AI enrichment, same-name --dir checkouts collide, and deep enrich follows symlinksPossibly taken A pull request linked to this issue is open or already merged. Openbug help wanted
Difficulty 4/5 3-5 days Newbie friendliness 54/100
Tencent/teamai-cli#1422 · 3 comments ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
Tencent/teamai-cli#1419 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
Tencent/teamai-cli#1418 ·
Maintainers usually reply within 1 day
All issues in Tencent/teamai-cli
Similar issues
-
verified
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Maintainers usually reply within 5 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
anomalyco/opencode#59589 · 1 comment ·
Maintainers usually reply within 1 day
-
Bug: During run init command, finish the git initialize process without question to user('Initialize a new git repository?')Possibly taken @nishu-murmu claimed this today. Openpending-triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
wxt-dev/wxt#2697 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
knaw-huc/textannoviz#739 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day