mirror of
https://github.com/1Remote/1Remote.git
synced 2026-04-25 13:36:03 +03:00
[GH-ISSUE #614] 1.0.0 BETA: Custom SFP Runners not working #1457
Labels
No labels
area-configuration
area-ct-app
area-ct-rdp
area-ct-remoteapp
area-ct-ssh
area-ct-vnc
area-launcher
area-list
area-tags
area-teamwork
bug
chore
dependencies
general-build/ci
general-performance
general-refactor
general-security
general-supportive
general-ux
meta-documentation
meta-enhancement
meta-enhancement
meta-feature
meta-help-wanted
meta-unknown-error
priority-hi
priority-low
pull-request
question
resolution-duplicate
resolution-invalid
resolution-wontfix
stale
task-put-off
task-still-considering
task-working-in-progress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/1Remote#1457
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @t-ru on GitHub (Feb 19, 2024).
Original GitHub issue: https://github.com/1Remote/1Remote/issues/614
Originally assigned to: @VShawn on GitHub.
Password, Private Key and Username are not correctly passed to WinSCP runners.
Configured SFTP Runner
Delivered WinSCP Runner... unchanged.
To Reproduce
Test Connection... Error Message from WinSCP... Host "value of %1RM_USERNAME%" does not exist.
Edit Connection... Do not make any changes. Exit edit mode with cancel.
Test Connection... all is working fine.
Affected versions
All versions since switch from PRemote to 1Remote
@VShawn commented on GitHub (Feb 20, 2024):
thx for alert, I found that when the
Hostingoption is not checked, the custom runner will have issues, I did not test the caseHosting = FALSEafter development is completed, BUT..i FIXed it now.
But the error I encountered here did not prompt Host
Host "value of %1RM_USERNAME%" does not exist., but another error, so please check if the problem you encountered has been resolved.@github-actions[bot] commented on GitHub (Mar 22, 2024):
This issue is stale because it has been open for 30 days with no activity.
@github-actions[bot] commented on GitHub (Apr 5, 2024):
This issue was closed because it has been inactive for 14 days since being marked as stale.