id,summary,reporter,owner,description,type,status,priority,milestone,component,version,severity,resolution,keywords,cc,branch,changelog,apichanges,internalchanges 11329,Configuration file may not be reparsed when successive save operations are called on a low resolution filesystem,Ryan J Ollos,Ryan J Ollos,"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.",defect,assigned,normal,1.0.2,general,,normal,,,,,"On platforms with a low resolution timestamp, each save operation will modify the file timestamp so that the file is sure to be reparsed.",The function `wait_for_file_mtime_change` can be placed before a `save` operation to ensure that the timestamp will be changed by the call to `save`.,