starred/1Remote

Fork 0

mirror of https://github.com/1Remote/1Remote.git synced 2026-04-25 13:36:03 +03:00

[GH-ISSUE #1013] Pinned tags not show after program restart #804

New issue

Closed

opened 2026-02-26 11:59:52 +03:00 by kerem · 5 comments

kerem commented

2026-02-26 11:59:52 +03:00

Owner

Originally created by @reginfo on GitHub (Oct 21, 2025).
Original GitHub issue: https://github.com/1Remote/1Remote/issues/1013

Originally assigned to: @VShawn on GitHub.

Describe the bug
Pinned tags not appear on the top bar after program restart

To Reproduce
Steps to reproduce the behavior:

Go to Tags
Right Click on tag
Select Pin

Expected behavior
Tag is pinned also after program shutdown but it lost, only one remains.

Desktop (please complete the following information):

OS: Windows 11 24H2 Enterprise
1Remote 1.2.1 Portable

Originally created by @reginfo on GitHub (Oct 21, 2025). Original GitHub issue: https://github.com/1Remote/1Remote/issues/1013 Originally assigned to: @VShawn on GitHub. **Describe the bug** Pinned tags not appear on the top bar after program restart **To Reproduce** Steps to reproduce the behavior: 1. Go to Tags 2. Right Click on tag 3. Select Pin **Expected behavior** Tag is pinned also after program shutdown but it lost, only one remains. **Desktop (please complete the following information):** - OS: Windows 11 24H2 Enterprise - 1Remote 1.2.1 Portable

kerem

2026-02-26 11:59:52 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-26 11:59:53 +03:00

Author

Owner

@itagagaki commented on GitHub (Oct 25, 2025):

On my end, the behavior I've observed differs slightly from what's been reported, but the pin/unpin behavior does indeed seem a bit off.

P.S.
1.2.1 works fine for me.
The latest main branch is does not work with pining the tags. I suspect the issue is caused by the refactoring that made three months ago, but I'm not sure.

@itagagaki commented on GitHub (Oct 25, 2025): On my end, the behavior I've observed differs slightly from what's been reported, but the pin/unpin behavior does indeed seem a bit off. P.S. 1.2.1 works fine for me. The latest main branch is does not work with pining the tags. I suspect the issue is caused by the refactoring that made three months ago, but I'm not sure.

kerem commented

2026-02-26 11:59:53 +03:00

Author

Owner

@VShawn commented on GitHub (Nov 13, 2025):

@reginfo sorry for delay, plz check file .locality/.tags.json after you pin something. if it correctly saved the IsPinned should be true.

1.2.1 shouldn't have this problem, I suspect that 1Remote doesn't have permission to write to .tags.json

The latest main branch does have issues.

@VShawn commented on GitHub (Nov 13, 2025): @reginfo sorry for delay, plz check file `.locality/.tags.json` after you pin something. if it correctly saved the IsPinned should be true. 1.2.1 shouldn't have this problem, I suspect that 1Remote doesn't have permission to write to .tags.json The latest main branch does have issues.

kerem commented

2026-02-26 11:59:53 +03:00

Author

Owner

@reginfo commented on GitHub (Nov 14, 2025):

Hi,

So when I make changes nothing new appears in .tags.json. There is only one tag. But is I modify this file manually - tags appears.
I don`t think it is permission issue, as DB is updating on my changes and the on one folder. Maybe it related to portable version?
I also testes Nightly version - the same behavior.

@reginfo commented on GitHub (Nov 14, 2025): Hi, So when I make changes nothing new appears in .tags.json. There is only one tag. But is I modify this file manually - tags appears. I don`t think it is permission issue, as DB is updating on my changes and the on one folder. Maybe it related to portable version? I also testes Nightly version - the same behavior.

kerem commented

2026-02-26 11:59:53 +03:00

Author

Owner

@VShawn commented on GitHub (Nov 15, 2025):

@reginfo That doesn't make sense, at least not for the nightly version. Just yesterday I checked the nightly build while troubleshooting this issue, and the .tags.json file was being modified correctly (i.e., when pinning a tag, the corresponding IsPinned would change to true).

Could you please double-check the nightly version and verify if the .tags.json file is actually being updated when you pin/unpin tags? There might be something specific about your setup that's causing this behavior.

Additionally, I found that the tag issue in the nightly version appears to be related to incorrect data binding objects after the refactoring.

@VShawn commented on GitHub (Nov 15, 2025): @reginfo That doesn't make sense, at least not for the nightly version. Just yesterday I checked the nightly build while troubleshooting this issue, and the .tags.json file was being modified correctly (i.e., when pinning a tag, the corresponding IsPinned would change to true). <img width="630" height="155" alt="Image" src="https://github.com/user-attachments/assets/a394eebe-83cc-4b93-aff0-d16a88a3f9ac" /> Could you please double-check the nightly version and verify if the .tags.json file is actually being updated when you pin/unpin tags? There might be something specific about your setup that's causing this behavior. Additionally, I found that the tag issue in the nightly version appears to be related to incorrect data binding objects after the refactoring.

kerem commented

2026-02-26 11:59:53 +03:00

Author

Owner

@reginfo commented on GitHub (Nov 19, 2025):

Hi,

I have renamed folder and get a new one with nightly version.
I have copy my DB file. And now everything is OK.
Thanks.

@reginfo commented on GitHub (Nov 19, 2025): Hi, I have renamed folder and get a new one with nightly version. I have copy my DB file. And now everything is OK. Thanks.

kerem referenced this issue

2026-02-28 12:05:35 +03:00

[GH-ISSUE #804] Resolve environment variables present in connection options #1612

kerem referenced this issue

2026-03-01 17:21:36 +03:00

[GH-ISSUE #804] Resolve environment variables present in connection options #2572

kerem referenced this issue

2026-03-13 12:03:10 +03:00

[GH-ISSUE #804] Resolve environment variables present in connection options #3570