posit-dev / posit-dev/positron
Output from later/promises doesn't get matched to correct console input
Open
Nobody has claimed this yet.
area: console
lang: r
- Dominant language
- TypeScript
- Stars
- 4.3k
- Forks
- 184
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 195
Description
I haven't investigated yet, but it's pretty weird:
async_method <- coro::async(function() {
for (i in await_each(1:3)) {
print(i)
}
})
async_method()
https://github.com/user-attachments/assets/ccb36a92-c218-427d-b978-abd6d272e9ba
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
No file, test, or entry point is named. Reproduce the provided R async_method example in the Positron console and use the attached recording to compare each output with its originating input; the issue is done when later/promises output is matched to the correct console input.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- developer-experience
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100