#7494 closed defect (fixed)
StartupPage shows wrong version
| Reported by: | Cobra | Owned by: | Cobra |
|---|---|---|---|
| Priority: | normal | Component: | Core |
| Version: | Keywords: | ||
| Cc: | AM909 |
Description
See attached screenshot.
Attachments (1)
Change History (19)
Changed 15 months ago by Cobra
comment:1 Changed 15 months ago by skyper
comment:2 follow-up: ↓ 3 Changed 15 months ago by simon04
Could be due to caching of the MOTD …
comment:3 in reply to: ↑ 2 Changed 15 months ago by simon04
Strange … MOTD should be reloaded automatically if the version changes. What are the values of cache.motd.html.version and josm.version in the advanced settings?
comment:4 Changed 14 months ago by stoecker
- Owner changed from team to Cobra
- Status changed from new to needinfo
comment:5 Changed 14 months ago by Cobra
AM909 in #osm just reported this:
< AM909> Running 5159, my start page says "Active version '4279' should be updated! The current stable snapshot is 5047 and 5159 is the unstable development version." Anyone else see this?
< AM909> Help confirms I am running 5159
< AM909> cache... is 5159
< AM909> as is josm.version
comment:6 Changed 14 months ago by stoecker
Code looks good. It should be possible that no MOTD is there, but old files should not be possible. There should have been Stacktraces in commandline in previous calls of JOSM. We would need these.
I assume you are using windows and there is again a file-lock-issue involved, though also in this case the code looks clean to me.
Please change "cache.motd.html.version" to old revision by hand and have a look if there are error messages and if the issue reappears. If there is a stream conversion error or a write error for MOTD file we have at least an indication what may be wrong.
comment:7 Changed 14 months ago by skyper
- Cc AMA909 added
comment:8 Changed 14 months ago by stoecker
- Cc AM909 added; AMA909 removed
comment:9 Changed 13 months ago by simon04
Could someone reproduce this effect?
comment:10 Changed 13 months ago by AM909
I'm up at r5181 now, and the start page no longer mentions what version I'm running, nor what the current tested or latest are. It's been that way for the last several versions. It starts:
JOSM – Java OpenStreetMap Editor 2012-04-14 (5181) The entry page of josm.openstreetmap.de has been simplified and re-organized... 2012-02-07 (4905) Shortcuts for the Relation Editor have been added:... 2012-02-02 (4897 ...) Conflicting shortcuts in JOSM and plugins get fixed... More news ... Help translating JOSM into your language! Getting Started...
comment:11 Changed 13 months ago by stoecker
Ooops. Copied the test back to StartupPage. It got moved to old news VersionHistory page by accident :-)
comment:12 Changed 10 months ago by Cobra
I've got a running instance of josm-latest r5361 (current version) showing "You should update!" on the startup page. Will investigate and keep it running.
comment:13 Changed 10 months ago by Cobra
josm-latest r5361
cache.motd.html.version = 5361 josm.version = 5361 $ls -l ~/.josm/cache/motd.html ... 2012-07-26 08:30 .../.josm/cache/motd.html
comment:14 Changed 10 months ago by stoecker
Server log says:
82.212.39.199 - - [26/Jul/2012:08:30:35 +0200] "GET /wiki/StartupPage HTTP/1.1" 200 12342 16s "-" "JOSM/1.5 (5361 en) Java/1.6.0_33"
Trac log says:
2012-07-26 08:30:36,211 Trac[JOSM] WARNING: PAGE: StartupPage AGENT: JOSM/1.5 (5361 en) Java/1.6.0_33
So you accessed the page with correct revision and also should have got a valid page in return. Is the motd.html correct and the display wrong or are both wrong?
comment:15 Changed 10 months ago by Cobra
motd.html has this line:
<h2><b>You should <a href="http://josm.openstreetmap.de/">update</a>!</b></h2>
full motd.html: http://pastebin.com/UTiFZ8P3
comment:16 Changed 10 months ago by stoecker
When you delete the file and retry, what happens?
comment:17 Changed 10 months ago by stoecker
- Resolution set to fixed
- Status changed from needinfo to closed
It took 16 seconds to deliver your page. Probably it is some inconsistency in server.
I optimized the code, so it no longer uses a probably insecure method to pass the version to the wiki page. This should fix this issue
comment:18 Changed 10 months ago by Cobra
I deleted the cached file and restarted josm - looks okay now.



Can not reproduce with empty preference dir: