Testing changes in playground doesn't work
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 32/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- azure, typescript
Research direction
Start with packages/mergebot/src/compute-pr-actions.ts and .github/workflows/deploy.yml, then inspect the linked playground-dt-review plugin and its Playground-Info request. Determine whether the deployed API can be accessed or whether the broken Playground message should be removed; done means the selected behavior works without the current failing request.
Written by the indexing model from the issue text.
Description
When a PR to DefinitelyTyped is opened, the mergebot posts a comment You can test the changes of this PR in the Playground. When the link to playground is opened and user agrees to install the playground-dt-review plugin, the plugin makes a request to https://dtmergebot.azurewebsites.net/api/Playground-Info?number=${prNum}&code=<something>. This request fails, because dtmergebot.azurewebsites.net does not exist. There is a PR (https://github.com/orta/playground-dt-review/pull/6) to change the URL to dtmergebot2, but it also doesn't exist.
According to the configuration, up-to-date domain is dtmergebot3.azurewebsites.net, but if I modify the plugin code and change the domain, server responds with 403 Ip Forbidden.
Could you either fix the API access (and somehow get @orta to update the plugin)? The alternative is removing entirely this broken functionality and the message from mergebot:
- Dominant language
- TypeScript
- Stars
- 422
- Forks
- 238
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 8
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 microsoft/DefinitelyTyped-tools
-
Difficulty 3/5 1-2 days Newbie friendliness 66/100
microsoft/DefinitelyTyped-tools#1324 · 8 comments ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
microsoft/DefinitelyTyped-tools#1229 ·
Maintainers usually reply within 1 day
-
mergebot staleness comments do not respect tooManyOwnersPossibly taken @copilot-swe-agent claimed this 326 days ago. Open
microsoft/DefinitelyTyped-tools#1218 · 1 reaction · 1 assignee ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
microsoft/DefinitelyTyped-tools#1211 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
microsoft/DefinitelyTyped-tools#1203 · 4 comments · 1 reaction ·
Maintainers usually reply within 1 day
All issues in microsoft/DefinitelyTyped-tools
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
supadata-ai/mcp#27 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
capricorn86/happy-dom#2485 ·
Maintainers usually reply within 2 days
-
优化导入 OCR 模型选择文件的按钮样式Open
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
siyuan-note/siyuan#20430 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Albert-Weasker/niubigeo#194 ·
Maintainers usually reply within 1 day