additional_mounts accumulate in self.mounted across multiple run() calls
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 30/100
Research direction
Start by locating the run() entry point and the handling of additional_mounts and self.mounted. Reproduce multiple run() calls, then add or update a focused test showing that mounts do not accumulate unexpectedly; done means repeated calls leave self.mounted in the intended state.
Written by the indexing model from the issue text.
Description
This issue has no description.
- Dominant language
- Python
- Stars
- 38
- Forks
- 21
- Avg merge
- 4d 3h
- Merged PRs (30d)
- 2
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.
More from microsoft/microbots
-
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 20/100
-
enhancement
-
enhancement
All issues in microsoft/microbots
Similar issues
-
agent-ready documentation needs-triage
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 91/100
-
workflow-status page template still says reusable workflows are "triggered only by workflow_call:" Open
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
instance instance add
Difficulty 1/5 Under an hour Newbie friendliness 72/100
searxng/searx-instances#939 · 1 comment ·
-
area-deployment area-integrations triage:bot-seen
Difficulty 2/5 Half a day Newbie friendliness 86/100