me0wster / javamelody

Automatically exported from code.google.com/p/javamelody
0 stars 0 forks source link

Can't show report for customized period #270

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Go to http://demo.javamelody.cloudbees.net/monitoring
2. Click Personnalisée to change to reporting period.
3. Enter 1-12-12 and 12-12-12 for start and end of the period.
4. Click OK

Expected output: graphs and tables show data for 1-12-12 to 12-12-12.

Actual output: graphs and tables show data for 17-12-172 to 17-12-12.

Versions: 
- JavaMelody SNAPSHOT-2012-12-17 on demo.javamelody.cloudbees.net
- JavaMelody 1.36.0 on CentOS 5.8 and Java version "1.6.0_30"
Java(TM) SE Runtime Environment (build 1.6.0_30-b12)
Java HotSpot(TM) 64-Bit Server VM (build 20.5-b03, mixed mode).

Original issue reported on code.google.com by fniess...@gmail.com on 17 Dec 2012 at 3:57

GoogleCodeExporter commented 9 years ago
Because you said "Personnalisée" and not "Customized", it seems that your 
browser is configured to use French and not English. Otherwise, what is the 
language including the country which is the first in your browser?

For example in Firefox, this is configured in "Tools, Options, Content, 
Language ... Choose".

And if you use French, you should probably write dates like "jj/mm/aa" 
(day/month/year) as suggested in the page before submitting the custom period.
In my case (I am French in France), the custom period from 1/12/12 to 12/12/12 
works for me, and in fact the graphs and tables are all empty because the 
server was reset today.

Is it ok for you? Or is your language fr-ca perhaps?

Original comment by evernat@free.fr on 17 Dec 2012 at 5:08

GoogleCodeExporter commented 9 years ago
I tested the demo site again with the following configurations:
- Chrome 23.0.1271.101 with languages English and Dutch on Mac OS X 
- Firefox 17.0.1 with languages English and Dutch on Mac OS X
- Safari 6.0.2. with English and Dutch as preferred languages on Mac OS X
- Firefox 17.0.1 with English and Dutch on Windows 7

The demo site always is in French for me.

I tried entering specific periods using both 1/1/12 and 1-1-12 format. The 
result is always the same: the tables and graphs are for the current date only 
(maybe the content is correct, but the captions say the data is for the current 
date only).

Original comment by fniess...@gmail.com on 18 Dec 2012 at 9:09

GoogleCodeExporter commented 9 years ago
I have not understood yet why it is displayed for you the same language and the 
same date format (yy-mm-dd) than the French Canadian people (fr-ca), whatever 
the language in your browser.

But, I have made a change to fix the choice of a customized period for the 
French Canadian people and it will certainly fix the same choice for you.
It is committed in trunk (revision 3196) and ready for the next release (1.43).
I have made a new build from the trunk and it is available at:
http://javamelody.googlecode.com/files/javamelody-20121218.jar

It is also deployed in the demo where you can test it:
http://demo.javamelody.cloudbees.net/monitoring
(use yy-mm-dd for dates of the customized period)

Does it work now?

Original comment by evernat@free.fr on 18 Dec 2012 at 1:40

GoogleCodeExporter commented 9 years ago
The demo is down? I get a completely blank page at 
http://demo.javamelody.cloudbees.net/monitoring

Original comment by fniess...@gmail.com on 18 Dec 2012 at 2:18

GoogleCodeExporter commented 9 years ago
No the demo is not down. But your period cookie need to be reset.

Open the following URL and then you will be able to choose a customized period:
http://demo.javamelody.cloudbees.net/monitoring?period=jour

Original comment by evernat@free.fr on 18 Dec 2012 at 2:25

GoogleCodeExporter commented 9 years ago
It works much better now. The user interface still is in French and I have to 
enter the dates with '-' instead of '/', but then the custom period works. 
Thanks!

Original comment by fniess...@gmail.com on 19 Dec 2012 at 8:46

GoogleCodeExporter commented 9 years ago
And so it is fixed for "French Canadians".

Original comment by evernat@free.fr on 19 Dec 2012 at 11:21