Add Magnet dialog retains download directory from previous server
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- react, typescript
- Domain
- frontend
Research direction
Locate the Add Magnet dialog and the server-tab change handling, then reproduce the issue by adding magnets on Server 1 before switching to Server 2. Verify the download directory and saved-directory list refresh for the selected server and that paths from the previous server are not reused.
Written by the indexing model from the issue text.
Description
Version: 512b63c
Steps to reproduce
- Select the Server 1 tab.
- Open the Add Magnet dialog.
- Paste multiple magnet links, one per line (This is how I reproduced it; it is unclear whether multiple links are required or merely make the issue easier to trigger.)
- Click Add.
- Immediately switch to the Server 2 tab.
- Open the Add Magnet dialog.
Actual behavior
The download directory field and its saved-directory list may still contain Server 1 paths.
If the torrent is added without noticing this, Server 2 can receive a path that does not exist on that server. This can cause an immediate path error or a failure when Transmission tries to move the completed download from its incomplete directory.
Expected behavior
The download directory should always be refreshed for the currently selected server. Paths from one server must never be reused for another server.
Reproducibility
It happened both times when I added the same set of magnets to two different servers.
It may require actually starting a multi-link addition before switching servers. I do not remember encountering it before multi-line magnet support was introduced.
- Dominant language
- TypeScript
- Stars
- 819
- Forks
- 109
- Avg merge
- 8d 57m
- Merged PRs (30d)
- 2
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 openscopeproject/TrguiNG
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
openscopeproject/TrguiNG#338 ·
-
Difficulty 4/5 1-2 days Newbie friendliness 35/100
openscopeproject/TrguiNG#345 · 1 comment ·
-
fix-committed
Difficulty 4/5 3-5 days Newbie friendliness 42/100
openscopeproject/TrguiNG#336 · 17 comments ·
-
fix-committed
Difficulty 3/5 1-2 days Newbie friendliness 76/100
openscopeproject/TrguiNG#335 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 67/100
openscopeproject/TrguiNG#333 · 5 comments ·
All issues in openscopeproject/TrguiNG
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
bug needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
DSpace/dspace-angular#6511 ·
Maintainers usually reply within 1 day
-
area: frontend area:byok bug severity:low
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
Phone app shows Unknown for a remote machine whose key changedPossibly taken @janicduplessis claimed this today. Openarea: mobile priority: P3 type: bug
Difficulty 1/5 Under an hour Newbie friendliness 78/100
appandflow/stim#5006 · 1 comment ·
Maintainers usually reply within 1 day
-
Area - Local to Cloud Bug
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
microsoft/vscode-mssql#23209 ·
Maintainers usually reply within 1 day