Skip to contentSkip to conversation

nvmetcli creates tilde directories

DISCUSSION Richard Weinberger 3 participants 10 messages Apr 9, 2025 – Apr 14, 2025 NVMe

lore
Share & tools
lore
#0 lore raw

Hi!

After playing with nvmetcli, I noticed that my home directory was sprinkled with directories named "~".
It seems like configshell used by nvmetcli does not resolve "~" to my home directory.

From the source:
shell = configshell.shell.ConfigShell('~/.nvmetcli')

Is this a known issue, or is it a misconfiguration on my side? FWIW, I'm on openSUSE Tumbleweed.

Thanks,
//richard

#1 lore raw
Quoted 5 lines · Richard Weinberger

Hi!

After playing with nvmetcli, I noticed that my home directory was sprinkled with directories named "~".
It seems like configshell used by nvmetcli does not resolve "~" to my home directory.

Is this a regression? Which version of configshell is Tumbleweed running?

There were some large changes to configshell upstream recently so I am wondering if something has been broken.

Maurizio

#2 lore raw

Maurizio,

----- Ursprüngliche Mail -----

Quoted 2 lines

Is this a regression? Which version of configshell is Tumbleweed running?

Dunno. It was the very first time I used nvmetcli. Tumbleweed shipps configshell-fb 2.0.0.

Quoted 2 lines

There were some large changes to configshell upstream recently so I am wondering if something has been broken.

This would make sense.

Thanks,
//richard

#3 lore raw
Quoted 9 lines · Richard Weinberger

Maurizio,

----- Ursprüngliche Mail -----

Quoted 2 lines

Is this a regression? Which version of configshell is Tumbleweed running?

Dunno. It was the very first time I used nvmetcli. Tumbleweed shipps configshell-fb 2.0.0.

Ok, 2.0.0 switched to Pathlib library and
I see where the bug is now.

A patch is gonna be pushed soon.

Thanks,
Maurizio

#4 lore raw

----- Ursprüngliche Mail -----

Quoted 2 lines

Von: "Maurizio Lombardi" <[email protected]> A patch is gonna be pushed soon.

Where is your git tree located?
I'm a but puzzled where to look for the most recent nvmetcli sources.

Thanks,
//richard

#5 lore raw
Quoted 6 lines · Richard Weinberger

----- Ursprüngliche Mail -----

Quoted 2 lines

Von: "Maurizio Lombardi" <[email protected]> A patch is gonna be pushed soon.

Where is your git tree located?
I'm a but puzzled where to look for the most recent nvmetcli sources.

The official nvmetcli repository should be the following one:
http://git.infradead.org/users/hch/nvmetcli.git

But the patch I am talking about will have to be pushed to configshell (it's on Github):

https://github.com/open-iscsi/configshell-fb

Maurizio

#7 lore raw
In reply to Maurizio Lombardi
Quoted 7 lines · Maurizio Lombardi
Quoted 5 lines · Richard Weinberger

Hi!

After playing with nvmetcli, I noticed that my home directory was sprinkled with directories named "~".
It seems like configshell used by nvmetcli does not resolve "~" to my home directory.

Quoted 5 lines

Is this a regression? Which version of configshell is Tumbleweed running?

There were some large changes to configshell upstream recently so I am wondering if something has been broken.

FYI, I recently had a ~ directory show up in my home directory as well, but didn't manage to track it down. I've not used nvmetcli on that system, but did use targetcli so configshell would be involved as well. This is on a debian unstable system using configshell-fb 1:2.0.0-1.

#8 lore raw
In reply to Richard Weinberger
Quoted 6 lines · Richard Weinberger

Hi!

After playing with nvmetcli, I noticed that my home directory was sprinkled with directories named "~".
It seems like configshell used by nvmetcli does not resolve "~" to my home directory.

I released configshell version v2.0.2, it should fix this bug.

Thanks,
Maurizio

#9 lore raw

----- Ursprüngliche Mail -----

Quoted 8 lines

Von: "Maurizio Lombardi" <[email protected]>

Quoted 5 lines

After playing with nvmetcli, I noticed that my home directory was sprinkled with directories named "~".
It seems like configshell used by nvmetcli does not resolve "~" to my home directory.

I released configshell version v2.0.2, it should fix this bug.

Nice, thx!
Let's hope distros will pickup the fix soon.

Thanks,
//richard