Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

First run of serve is not respecting --no-default-folder #9501

Closed
Fryuni opened this issue Apr 7, 2024 · 4 comments
Closed

First run of serve is not respecting --no-default-folder #9501

Fryuni opened this issue Apr 7, 2024 · 4 comments
Labels
bug A problem with current functionality, as opposed to missing functionality (enhancement) needs-triage New issues needed to be validated

Comments

@Fryuni
Copy link

Fryuni commented Apr 7, 2024

What happened?

When running syncthing serve --no-default-folder on a machine where Syncthing was never executed before it still generates the default "Sync" folder.

By the --no-default-folder flag docs, that shouldn't happen.

Syncthing version

v1.27.5 "Gold Grasshopper" (go1.22.1 darwin-amd64) brew@Sonoma 2024-03-25 03:45:14 UTC [noupgrade]

Platform & operating system

MacOS amd64

Browser version

No response

Relevant log output

[start] 2024/04/07 10:32:57 INFO: syncthing v1.27.5 "Gold Grasshopper" (go1.22.1 darwin-amd64) brew@Sonoma 2024-03-25 03:45:14 UTC [noupgrade]
[QCDML] 2024/04/07 10:32:57 INFO: My ID: <DEVICE ID>
[QCDML] 2024/04/07 10:32:58 INFO: Single thread SHA256 performance is 1174 MB/s using minio/sha256-simd (1162 MB/s using crypto/sha256).
[QCDML] 2024/04/07 10:32:59 INFO: Hashing performance is 752.17 MB/s
[QCDML] 2024/04/07 10:32:59 INFO: Detected upgrade from v1.27.1 to v1.27.5
[QCDML] 2024/04/07 10:32:59 INFO: Overall send rate is unlimited, receive rate is unlimited
[QCDML] 2024/04/07 10:32:59 INFO: Stored folder metadata for "default" is 2086h0m0s old; recalculating
[QCDML] 2024/04/07 10:32:59 INFO: Using discovery mechanism: global discovery server https://discovery.syncthing.net/v2/?noannounce&id=<ID 2>
[QCDML] 2024/04/07 10:32:59 INFO: Using discovery mechanism: global discovery server https://discovery-v4.syncthing.net/v2/?nolookup&id=<ID 2>
[QCDML] 2024/04/07 10:32:59 INFO: Using discovery mechanism: global discovery server https://discovery-v6.syncthing.net/v2/?nolookup&id=<ID 2>
[QCDML] 2024/04/07 10:32:59 INFO: Using discovery mechanism: IPv4 local broadcast discovery on port 21027
[QCDML] 2024/04/07 10:32:59 INFO: Using discovery mechanism: IPv6 local multicast discovery on address [ff12::8384]:21027
[QCDML] 2024/04/07 10:32:59 INFO: Ready to synchronize "Default Folder" (default) (sendreceive)
[QCDML] 2024/04/07 10:32:59 INFO: Relay listener (dynamic+https://relays.syncthing.net/endpoint) starting
[QCDML] 2024/04/07 10:32:59 INFO: GUI and API listening on 127.0.0.1:8384
[QCDML] 2024/04/07 10:32:59 INFO: Access the GUI via the following URL: http://127.0.0.1:8384/
[QCDML] 2024/04/07 10:32:59 INFO: QUIC listener ([::]:22000) starting
[QCDML] 2024/04/07 10:32:59 INFO: My name is "Lotus Mac"
[QCDML] 2024/04/07 10:32:59 INFO: Cleaned away old file config.xml.v0
[QCDML] 2024/04/07 10:32:59 INFO: Completed initial scan of sendreceive folder "Default Folder" (default)
[QCDML] 2024/04/07 10:32:59 INFO: TCP listener ([::]:22000) starting
[QCDML] 2024/04/07 10:33:06 INFO: Sent usage report (version 3)
[QCDML] 2024/04/07 10:33:09 INFO: quic://0.0.0.0:22000 detected NAT type: Symmetric NAT
[QCDML] 2024/04/07 10:33:30 INFO: New external port opened: external TCP address(es) [<MY IP>] to local address [::]:22000.
[QCDML] 2024/04/07 10:33:30 INFO: Detected 1 NAT service
[QCDML] 2024/04/07 10:35:03 INFO: Joined relay relay://129.148.29.67:22067
@Fryuni Fryuni added bug A problem with current functionality, as opposed to missing functionality (enhancement) needs-triage New issues needed to be validated labels Apr 7, 2024
@er-pa
Copy link
Member

er-pa commented Apr 7, 2024

Perhaps the brew package (seems to be the source?) changes/overwrites defaults and prevents you from supplying arguments. What you show isn't really the typical behaviour for absolutely no previous config present using the default Syncthing binary. I also cannot reproduce it using the default binary.

@calmh
Copy link
Member

calmh commented Apr 7, 2024

Yeah... log output is clearly not the first time it's run for that account, and I also cannot reproduce.

@calmh calmh closed this as not planned Won't fix, can't repro, duplicate, stale Apr 7, 2024
@Fryuni
Copy link
Author

Fryuni commented Apr 7, 2024

Yeah... log output is clearly not the first time it's run for that account, and I also cannot reproduce.

It was though...
Syncthing was never even installed on this machine. I freshly formatted it.

But ok... nothing really that annoying.

@calmh
Copy link
Member

calmh commented Apr 7, 2024

I mean, it even shows which version it was upgraded from and how long ago metadata was last updated...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug A problem with current functionality, as opposed to missing functionality (enhancement) needs-triage New issues needed to be validated
Projects
None yet
Development

No branches or pull requests

3 participants