Using Puppeteer 0.13.0, I'm wondering which timezone it configures its Chromium instances for?
It appears to me, from my testing, that Chromium will use UTC for timezone, but I can't find any confirmation of this anywhere.
For example, if I log the current time, via console.log(new Date()) in the Puppeteer Chromium instance, I get UTC time: Wed Jan 10 2018 08:10:21 GMT+0000 (UTC). If I do the same in my normal Chrome browser however, I get local time: Wed Jan 10 2018 09:09:36 GMT+0100 (CET).
It looks to me as if this problem is solved as of Puppeteer 1.0, so I guess it was a bug.
Related
I am new to Electron and want to make (at first) a sample javascript change in the Slack Electron app. I am here on a Mac OSX:
/Applications/Slack.app/Contents/Resources
and run the following:
asar extract app.asar ~/Desktop/src
And then without even making a change run:
asar pack ~/Desktop/src app.asar
The "re-packed" file is significantly larger:
-rw-r--r-- 1 oliverwilliams staff 28336486 Apr 21 03:25 app.asar
-rw-r--r-- 1 oliverwilliams staff 8175963 Mar 21 13:26 app.asar.original
and Slack will not start. Reverting back to the original file, Slack runs again.
Obviously I need to crawl before I can walk. What needs to be done here?
I am finishing off a blog tutorial and am trying to do my final push to GitHub and Heroku. I just added the popper gem to the Gemfile and then tried to push to GitHub as usual using git push origin master.
Normally it then asks for my username and password, but instead I got the following error and have no idea what it means or why I got it. I haven't changed anything else as far as I remember.
fatal: unable to access 'https://github.com/<username>/FrogBlog.git/': error:1407742E:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert protocol version
I am unsure how to proceed, as this message means nothing to me. I can post more files from my project if required, please advise.
GitHub recently deprecated some old and insecure cryptographic standards, including TLSv1, which is referenced in your error message:
On February 8, 2018 we’ll start disabling the following:
TLSv1/TLSv1.1: This applies to all HTTPS connections, including web, API, and git connections to https://github.com and https://api.github.com.
diffie-hellman-group1-sha1: This applies to all SSH connections to github.com
diffie-hellman-group14-sha1: This applies to all SSH connections to github.com
We’ll disable the algorithms in two stages:
February 8, 2018 19:00 UTC (11:00 am PST): Disable deprecated algorithms for one hour
February 22, 2018 19:00 UTC (11:00 am PST): Permanently disable deprecated algorithms
Most Git clients should continue to work, but there are some known incompatibilities.
If you update your Git client (it looks like you're using the standard CLI client?) pushing to GitHub will probably start working again.
I just installed log4c and log4c-devel on CentOS 6.x by yum. All works fine except the log time, it's slow for 8 hours
Following is the output of my machine:
[rafael#localhost ~]$ date
Tue Jan 14 15:17:34 CST 2014
Following is the log produced by log4c:
20140114 07:17:34.453 DEBUG GFXLog- CTimerManager::killTimer: time id-0x0000000198c4e0.
you see, slow for 8 hours. I have setup my machine with correct time and timezone, and also keep ntpd running. I think maybe i should setup log4c timezone, but I don't know how? log4crc or code? cannot find any document about that by google.
I had exactly the same problem, but in Ubuntu 14.04 dated_local is not available because log4c is an older version. I wrote an update based on the latest log4c code which does not require modifying the supplied shared library.
See https://bugs.launchpad.net/ubuntu/+source/log4c/+bug/1314576
When saving a CMS block in Magento 1.4.1, I am getting an error, connection reinitalized by my web browser. I only get this this error, when adding the tags <script></script>. Any other changes I can save and I can add new blocks as long as I don't use <script></script>
The only error I'm seeing is in /var/www/website/var/log/exception is this and only if I hit F5 after getting the connection reinitalized error. Apache and other system logs are not reporting any additional errors.
2012-07-06T08:47:22+00:00 DEBUG (7): HEADERS ALREADY SENT: <pre>[0]
/var/www/vhosts/site/app/code/core/Mage/Core/Controller/Response/Http.php:44
[1] /var/www/vhosts/site/lib/Zend/Controller/Response/Abstract.php:727
[2] /var/www/vhosts/site/app/code/core/Mage/Core/Controller/Response/Http.php:75
[3] /var/www/vhosts/site/app/code/core/Mage/Core/Controller/Varien/Front.php:188
[4] /var/www/vhosts/site/app/code/core/Mage/Core/Model/App.php:304
[5] /var/www/vhosts/site/app/Mage.php:596
[6] /var/www/vhosts/site/index.php:78
This website was working fine on a Centos 5.4 with PHP 5.2.13. All the same Apache and PHP modules were installed on the new Debian server. Any help would be sincerely appreciated.
Version Information
Magento 1.4.1
Debian 6.0 i386
PHP 5.3.3-7+squeeze13 with Suhosin-Patch (cli) (built: Jun 10 2012 09:35:18)
Copyright (c) 1997-2009 The PHP Group
Zend Engine v2.3.0, Copyright (c) 1998-2010 Zend Technologies
with the ionCube PHP Loader v4.0.7, Copyright (c) 2002-2011, by ionCube Ltd.
Server version: Apache/2.2.16 (Debian)
Server built: Apr 1 2012 06:40:08
A rule in our Netasq firewall was blocking the <SCRIPT> tag. Once we disabled the rule, the client was able to use the tag again. We did warn him, however, that netasq probably put that rule their for a very good reason.
I disabled some plugins to upgrade Jira. The upgrade was not carried out as new version of Jira needs 64 bit hardware. Upon stopping and restarting the instance to resume with original application, I get this message:
The following plugins are required by JIRA, but have not been started:
FishEye Plugin (com.atlassian.jirafisheyeplugin)
catalina.out:
***********************************************************************************************************************
The following plugins are required by JIRA, but have not been started: FishEye Plugin (com.atlassian.jirafisheyeplugin)
***********************************************************************************************************************
2011-08-04 16:08:51,896 main FATAL [atlassian.jira.upgrade.UpgradeLauncher] Skipping, JIRA is locked.
2011-08-04 16:08:51,896 main INFO [atlassian.jira.scheduler.JiraSchedulerLauncher] JIRA Scheduler not started: JIR startup checklist failed.
2011-08-04 16:08:52,219 main FATAL [jira.web.dispatcher.JiraWebworkActionDispatcher]
******************************************
JIRA startup failed, JIRA has been locked.
******************************************
Aug 4, 2011 4:08:52 PM org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on http-8080
Aug 4, 2011 4:08:52 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 62989 ms
Does anyone have a clue as to how to re-enable fisheye plugin manually?
Any help greatly appreciated, thanks to all SO`ers.
This also happens when the update is succesfull and you've deactivates FishEye before. Sad.
There's an article in Atlassian's documentation at http://confluence.atlassian.com/display/JIRA/How+to+Enable+the+FishEye+Plugin+from+the+Plugin+Administration+Screen, but this doesn't work for me (note that the plugin name is written wrong there, too).
Any other hints?