If I put a summer time date into the cache then it comes out without the summer time applied.
e.g. 14:00+1 (15:00) comes back out of the cache as 14:00.
In non-summer time, there's no problem.
I've raised an issue on GitHub, which has been unanswered in a week.
Any ideas?
I fixed this with...
BlobCache.Secure.ForcedDateTimeKind = DateTimeKind.Local;
https://github.com/reactiveui/Akavache/issues/492
Related
EDIT: I really don't know what just happened right now but I was still looking over the dashboard for some other infos and the statistics just reseted! I'm sorry for posting! For anyone wondering, I think the quotas reset at 10 AM (EET)
I'm working on a work certificate in informatics and I decided to give Firebase a try with this project. I love it :)
Two days ago, when I started, everything was good. Yesterday at 8 PM I think I reached the quota for bandwidth (1GB) so I said, "ok no problem, I'll work on it tomorrow". Now today when I opened Firebase Console I still get this error in Storage: "You have exceeded your quota for this project. Please upgrade your plan."
I will leave here a few screenshots with my statistics. Can anyone help me figure out why my limits did not reset? PS. The error first showed up at maybe 8 PM yesterday and now it's 10 AM. It's another day but 24 hours didn't pass. Is this the real reason? I read on another StackOverflow question that it resets daily so I thought that at 12 AM it resets.
Thanks in advance!
You can see in this picture that on 15 December (yesterday) I have 1GB hit but on 16 December (today) is 0.
However, if I set the calendar to show me "Today" instead of "Current billing period" it shows me that the bandwidth was used today
So my question is, the quota is working on a 24 hours base or daily base?
read the fine print ...it reads 1 GB per day for Storage.
it does not tell when it resets - and might eventually depend on the zone & region.
try to use smaller files for testing purposes.
I Need to get the current Eastern time zone.
I am using asp classic. I tried alot but I did not got the solution.
Any one can help me.
I am using
Now()
to get the current value in vb classic but i need current time in Eastern time zone.
I disagree that converting to UTC time is the way to go, precisely because then you get to deal with the headaches of daylight savings time. Instead, figure out what time zone the server is set to, figure out what the offset is from that to Eastern time, and then instead of just Now, use DateAdd('h',3,Now). (Naturally, replace 3 with the correct number if the server is not on the west coast.)
Alex K has the right answer, which he put in the form of a comment. Here it is in the form of an answer:
Get UTC time -> stackoverflow.com/a/11441116/246342 Add the offset (remembering some places will use daylight savings in the summer)
For my apps I try to store all times as UTC to avoid this problem. For some date/time calcs I can get by with the local time zone of the server, such as when I just need to know elapsed time. So then I'm just careful to make sure the server time zone is what I expect in case I ever need to display it. For example, our marketing dept doesn't think having our special offers expire at "midnight UTC" is very user-friendly, so we just say "midnight Central Time" and let people convert in their heads to their local time. Internally I can compare Now to the expiration date of the offer and it works fine.
I'm using fullcalendar 1.6.4 in conjunction with a Drupal 7 site; all is well except that I'm getting the wrong number of weeks for some months with weekMode set to "variable" or "liquid". For September 2013, I get four rows of weeks, which means that I lose the last two days of the month. Most other months appear correctly, although December 2012 is shown with 5 weeks (losing the 30th and 31st), and January, February, and October 2013 are all shown with 6 weeks (one more than is needed).
I've been doing some quick hacking around with the render() code where the starting and ending dates seem to be worked out, but haven't come up with anything clearly better. So: are other people seeing this / is it a known issue / have I screwed up something with my installation? Thanks!
I think there's a bug here: in fullcalendar.js's MonthView.render(), it looks like the AddDays computation of visEnd (l. 1984) is getting messed up by firstDay getting string-concatenated into the value instead of added. visStart may be getting similarly affected, since it does pretty much the same thing. In any case, I stuck the line firstDay = parseInt(firstDay, 0) after the var FirstDay... statement, and things are working properly for me. This may not be the preferred way of handling the matter, but I think something like this is going on. Opinions from other eyes?
This is not a Full Calendar bug, but instead a bug in the Drupal implementation of Full Calendar. Drupal allows users to override the "start of the week" option (values of 0 to 6). Drupal is incorrectly storing this value as a string instead of a number.
See Drupal issue I opened.
In recent 2 days, my website's average visits duration fell from about 1:30 to 50sec in Audience>Overview window and fell from 2:00 to 1:30 in Content>Overview window. The visits duration parameters has a steady value for a long time.
The website (www.rapidtables.com) seems to function well.
Hosting server activity history graph seems normal.
All other analytics parameters (visits and pages/visit) seem normal.
Why visit duration is different in Audience>Overview and Content>Overview windows?
What could have caused the sudden drop in the duration parameter? (analytics bug / old urchin.js usage ...)?
Do you have historical data to compare to? If so, is this the first year it has happened, or do you see a dip about this time every year? If you have absolutely verified that nothing went wrong with your tracking code or your website in general, then it boils down to speculation. You just have to research the industry your site caters to and look for reasons that might have caused it. Maybe some new competitor opened shop? Maybe whatever product or service you offer is "seasonal"?
We have a really strange problem in xpages regarding dates, the Notesdocument we have contain a date field and the value is only a date, there is no time portion.
In the xpage I have specified to display the date as a date/time value. the date display correctly on the webpage but we are now getting reports from users who login at night (around midnight) and see the date as adjusted by one day. if the same people login at daytime the date is correct so this only seem to happend around midnight
I have tried to change my clock on my client to around midnight but that does not reproduce it so I assume this is a server issue.
The domino server have correct date/time and we are using the latest version of Domino
any ideas?
we encountered the same problem recently and, I believe, found a very nice solution.
system treats the pure date as a date in UTC time zone. Date value is automatically converted into server's time zone. So the question is how to prevent conversion?
this code prevents conversion:
<xp:this.converter>
<xp:convertDateTime
type="date"
ignoreUserTimeZone="true"
dateStyle="long"
timeZone="UTC">
</xp:convertDateTime>
</xp:this.converter>
pay attention at "timeZone" attribute.
The issue is related to not having the TimeZone specified in the date / time field. We ran into this just yesterday. If you don't have the TZ specified, it seems to assume UTC and will adjust accordingly. Include the time zone and your field will stop adjusting erroneously.
Perhaps it has to do with this ?
http://www-304.ibm.com/support/docview.wss?uid=swg21508734
I've seen some reports about XPages Dates and TimeZone Issues
I suspect your Domino version was 8.5.3, because there were 2 APAR, LO72278 and LO67745, on similar problems against 8.5.3. Fixpack 3 addresses them.
The root cause is that Lotus Notes allows you to save a "Date" with no time or zone and the Notes server has a default Time Zone setting to interpret these incomplete things called dates. XPages doesn't play by the same rules, and its master Java wants to know what zone you're using, and looks to the system for some clue, and generally will use midnight within some TZ to refer to a "Date". There is a whole region on Stack Overflow on the "how to store/represent a date" topic - [datetime] - since languages and DBMS each have their own approach.
Nice legacy Notes focused article about it.
http://www-10.lotus.com/ldd/ddwiki.nsf/dx/05022009100728PMAGU5MB.htm
XPages article about it
http://www-10.lotus.com/ldd/ddwiki.nsf/dx/XPagesTimeZones.htm
Too bad they are not totally on the same page, I assume each release gets closer.