Termix-SSH / Termix-SSH/Support

[BUG] Importing an export with custom settings do not apply them correctly

Open
#1,287 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug platform-docker platform-web ssh
Dominant language
No language data
Stars
28
Forks
4
PR merge metrics
No merged PRs in 30d

Description

Title

Importing an export with custom settings do not apply them correctly

Platform

Website - Chrome

Server Installation Method

Docker

Version

2.7.1

CLI Installation Method

No response

CLI Version

No response

Troubleshooting
  • I have examined logs and tried to find the issue
  • I have reviewed opened and closed issues
  • I have tried restarting the application
  • I have checked open issues and ensured this is not a duplicate
The Problem

Importing a previously exported json can behave in unexpected ways.
Also overwriting/setting state is not correct

How to Reproduce

Precondition:
Have 3 entries available:

  • 1 thats just used as a jumphost "Jump"
  • 1 is just to compare lets call it "Original"
  • The other one "ToBeModified"

For "Original" and "ToBeModified" we need to make sure to have following settings:

  • Jumphost set to "Jump"
  • SSH > Terminal > Option Key Sends Meta = True
  • SSH > Terminal > Command History = True
  • SSH > Terminal > Enable Terminal Toolbar = True

Have an export file that Includes 2 different hosts and ToBeModified

  • Host 1 = ExportJump
  • Host 2 = UseJump
  • ToBeModified (with all 3 settings set to false and exported afterwards (see attachment)

Steps:

  1. Import BaseStart.json
  2. Check all values have the correct state
  3. Import Test.json (overwrite values)
  4. Verify all changeg value

BaseStart.json
Test.json

Result:
"UseJump" has no valid jumphost added, as the previoulsy stored id is not the id of the newly imported host "ExportJump"
"ToBeModified" still shows "Option Key Sends Meta" as active but the overwrite should have been disabling it.
For all Hosts, Command History and Enable Terminal Toolbar are untouched or enabled by default (even if they were disabled by the user)

On larger sets of data this is a nightmare to maintain right now espacially when moveing between different termix environments.

Additional Context

No response

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by importing BaseStart.json and then Test.json in the website, following the reproduction steps and comparing the listed host and terminal settings. Done means the imported jumphost reference resolves to ExportJump and the imported false values overwrite existing settings for Option Key Sends Meta, Command History, and Enable Terminal Toolbar.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker
Domain
backend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
67/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.