I don't know why, but the values of Settings on the webpage opened by the fossil ui / are inconsistent with those on the webpage opened by the fossil ui.

i'm unable to reproduce this. Can you walk us through exactly how you're changing the setting?

In my case:

• fossil ui /
• Select the top-most repository in the list
• Browse to its setup_settings page
• Change the preferred-diff setting from 0 to 2
• Apply changes - the new value is there
• Visit a different page in that repo
• Browse back to the setup_settings page
• The new value is still there

I have recorded a video.

@Anonymous i rejected your last response because we don't want those video links stored forever in the forum and emailed to all subscribers.

i cannot explain the value not being stored properly there. My two suspicions are currently:

• A browser-caching issue (this seems unlikely, though, as the cache should not be used for POST requests). The only mostly-reliable way i know to verify and avoid this is to open the browser's dev tools and use the "disable cache" option in the network tab while updating the settings.

• It may be a bug related to handling of Chinese characters in the URL. The easiest way to verify that is to try the same test on a repository which uses only ASCII names. If this is the case then it should be easy to track down and fix.

The easiest way to verify that is to try the same test on a repository which uses only ASCII names.

我换用其他不带中文字符的仓库试了一下，照常运行了。 看来你是对的，就是因为非阿斯码表字符的原因。

I tried another repository without Chinese characters and it worked. So you were right; it was because of the non-ASCII characters.

If this is the case then it should be easy to track down and fix.

这个缺陷还会修复吗？

will fix?

will fix?

We're aware of the problem now, and will eventually fix it if doing so does not cause other problems, but it is a rare corner case with easy workarounds so is not a high priority.

The current workarounds for changing settings are:

1. Use "fossil ui the-repo.fossil" instead of "fossil ui /"

2. Use the "fossil settings" CLI command

I tried, but was unable to recreate the problem. I created a repository named "你好.fossil" and set the preferred-diff-type to 1, and when I access that repository using "fossil ui /" it does show the preferred-diff-type as 1. Am I misunderstanding your bug report?

Can you please provide a precise sequence of steps needed to cause an issue, and provide a more detailed description of what the problem is?

Can you please provide a precise sequence of steps needed to cause an issue, and provide a more detailed description of what the problem is?

He posted a video link demonstrating it but i rejected that post. i'll post it to you off-list.

He posted a video link demonstrating it but i rejected that post.

Here's the part of that post which wasn't a video link:

• fossil ui /
• Select the top-most repository in the list
• Browse to its setup_settings page
• Change the preferred-diff setting from 0 to 1
• Apply changes - the new value is not there

It is when I do it!

i'm able to repro it on both Windows 11 and (to my surprise) Linux but only on a repo with non-ascii characters and only via "ui /". My repro:

$ f new äöü.fossil
$ mkdir de
$ cd de
$ f open ../äöü.fossil # to register the repo with "fossil all"
$ cd ..
$ f ui /

Browse to äöü.fossil → Admin → Settings. Change preferred-diff, tap apply, and the old value is still there. It does not repro if "f ui" is run from the opened checkout or run as "f ui äöü.fossil".

Please rebuild using the latest Fossil check-in (dated 202503171246Z or later) and let us know if that clears your problem.

Please rebuild

# fossil clone https://fossil-scm.org/ myclone.fossil -v --xverbose --httptrace
                Bytes      Cards  Artifacts     Deltas
URL: https://fossil-scm.org/
Sending 163 byte header and 97 byte payload
Read: [HTTP/1.0 200 OK]
Read: [Cache-control: no-cache]
Read: [X-Frame-Options: SAMEORIGIN]
Read: [Content-Type: application/x-fossil-uncompressed]
Read: [Content-length: 5000327]
Reply received: 5000327 of 5000327 bytes
Sent:              97          1          0          0
Received:     5000327      16501       2013       6256

一直卡在这……

Stuck in this situation all the time...

Reply received: 5000327 of 5000327 bytes

5 million sounds like it might be a limit set in a proxy somewhere between you and fossil. We have had reports in the past of nginx, or similar, limiting traffic to similar amounts.

我明白了。用fossil clone https://www3.fossil-scm.org/site.cgi fossil.fossil可以正确clone。

测试了一下修改过的功能，bug已解决。

I understand. Using fossil clone https://www3.fossil-scm.org/site.cgi fossil.fossil can clone correctly.

I tested the modified features and the bug has been resolved.