Configuration file may not be reparsed when successive save operations are called on a low resolution filesystem
|Reported by:||Ryan J Ollos||Owned by:||Ryan J Ollos|
On platforms with a low resolution timestamp, each save operation will modify the file timestamp so that the file is sure to be reparsed.
Description (last modified by )
As discussed in comment:17:ticket:11069 and comment:13:ticket:11176, the configuration file might not be reparsed when successive save operations are invoked in a time interval less that is less than the resolution of the filesystem.
In #11069 we discussed how to fix the issue for the functional test environment. Changes will be proposed here that intend to fix the issue for a Trac instance running on a low resolution filesystem.