axe-crawler selenium webdriver chrome error - node.js

I am running axe-crawler from the command line using node and getting the following error
*ERROR: Thu Jul 23 2020 11:14:32 GMT+0100 (British Summer Time)
Error encountered in using Selenium Webdriver:
ERROR: Thu Jul 23 2020 11:14:32 GMT+0100 (British Summer Time)
[object Object]*
Not really very descriptive. Can anyone point me in the right direction to either be able to get the proper error or even point out where I might be going wrong?

As there did not seem to be a way of accessing the errors, I ended up using a C#/node hybrid, more from a sensible debugging need. I scraped the site with dotnet HtmlAgilityPack and then ran axe-core through node/javascript to produce the json response.

Related

AWS Linux Date vs node js Date

I have an AWS Instance running node v10.15.1
From linux:-
$ date
Thu 14 May 16:12:40 BST 2020
BUT node shows...
$ node
> new Date()
2020-05-14T15:13:37.941Z
Now the actual time is 16:12, So Node is showing GMT, but the System knows it really is BST.
My /etc/sysconfig/clock contains:-
ZONE="Europe/London"
UTC=true
It's possible that a re-start might sort this, but I'm trying to find an alternative, less intrusive solution. - any advice appreciated.
Date() in node always returns GMT time regardless of system time zone, you can convert to locale time :
[ec2-user ~]$ date
Thu May 14 17:38:13 BST 2020
[ec2-user ~]$ node
Welcome to Node.js v14.2.0.
Type ".help" for more information.
> d = new Date()
2020-05-14T16:38:54.746Z
> d.toLocaleTimeString()
'5:38:54 PM'

mod_pagespeed many "Unrecognized Script" messages in the console

I am running mod_pagespeed (Apache) on my server and it is functioning great, apart from many "info level" messages in the admin console log. The site is currently scoring 94/89 on GTMetrix and I'm at the point of trying to squeeze that last bit of juice from this wonderful module.
These messages refer to unrecognised scripts that mod_pagespeed was attempting to process. In most cases they contain json or text/html, i.e.:
[Wed, 29 Jan 2020 13:17:10 GMT] [Info] [16645] [https://www.example.com/comment/:271] Unrecognized script:'<script type='application/ld+json'></script> 271...295'
[Wed, 29 Jan 2020 13:17:10 GMT] [Info] [16645] [https://www.example.com/comment/:88] Unrecognized script:'<script type='application/ld+json' class='yoast-schema-graph yoast-schema-graph--main'></script> 88...88'
[Wed, 29 Jan 2020 13:13:01 GMT] [Info] [14352] [https://www.example.com/comment/:47] Unrecognized script:'<script type="text/html" id="wpb-modifications"></script> 47...47'
[Wed, 29 Jan 2020 13:13:01 GMT] [Info] [14352] [https://www.example.com/comment/:11] Unrecognized script:'<script type='application/ld+json'></script> 11...33'
[Wed, 29 Jan 2020 13:13:01 GMT] [Info] [14352] [https://www.example.com//:11] Unrecognized script:'<script type='application/ld+json' class='yoast-schema-graph yoast-schema-graph--main'></script> 11...11'
Does anyone here know of any way to configure Pagespeed to be able to recognise this format?
I've already fixed some issues with unrecognised image links within some tags:
ModPagespeedUrlValuedAttribute img data-lazy-src image
ModPagespeedUrlValuedAttribute a data-tolb-src image
And those assets are now being rewritten/compressed.
My main problem is that I don't know how to get Pagespeed to recognise these script tags.
Is there a way? (Is it even necessary for these type of script tags?)
Many thanks in advance.

Servers with same timezone but different time

I have 3 servers, 2 on AWS and one on Digital Ocean, and the timezone for all is set to CDT. But when I check the current time on all 3 by using the date command via command line, none of them matches.
Server1: Wed Jun 12 23:36:01 CDT 2019
Server2: Wed Jun 12 23:45:51 CDT 2019
Server3: Wed Jun 12 23:38:39 CDT 2019
Could anyone please suggest what needs to be done here? Thanks.
Since you have not explicitly said that you have ntp running on them, you'll need to install that. Once that is installed and set up properly, you should show the same exact time on all of them.

Kurento Media Server 6.4 segmentation fault in libnice

I am using latest Kurento Media Server (6.4) and node.js app for one-2-one calls. However, Kurento process crashes from time to time inside libnice: (multiple crashes point to the same lib entries)
Segmentation fault (thread 139888166897408, pid 1093)
Stack trace:
[nice_output_stream_new]
/usr/lib/x86_64-linux-gnu/libnice.so.10:0x28C74
[nice_output_stream_new]
/usr/lib/x86_64-linux-gnu/libnice.so.10:0x2B00A
[nice_output_stream_new]
/usr/lib/x86_64-linux-gnu/libnice.so.10:0x2BD09
[nice_agent_gather_candidates]
/usr/lib/x86_64-linux-gnu/libnice.so.10:0x13E8B
[nice_agent_gather_candidates]
/usr/lib/x86_64-linux-gnu/libnice.so.10:0x1431E
[g_simple_permission_new]
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0:0x75B21
[g_main_context_dispatch]
/lib/x86_64-linux-gnu/libglib-2.0.so.0:0x49EAA
[g_main_context_dispatch]
/lib/x86_64-linux-gnu/libglib-2.0.so.0:0x4A250
[g_main_loop_run]
/lib/x86_64-linux-gnu/libglib-2.0.so.0:0x4A572
[gst_nice_src_get_type]
/usr/lib/x86_64-linux-gnu/gstreamer-1.5/libgstnice15.so:0x2F99
[g_test_get_filename]
/lib/x86_64-linux-gnu/libglib-2.0.so.0:0x70965
[start_thread]
/lib/x86_64-linux-gnu/libpthread.so.0:0x8182
[clone]
/lib/x86_64-linux-gnu/libc.so.6:0xFA47D
At the same time, the most recent debug events recorded to log files are ice candidates pairings:
2016-03-17 08:43:12,095520 1093 [0x00007f3a407f0700] debug KurentoWebRtcEndpointImpl WebRtcEndpointImpl.cpp:214 newSelectedPairFull() <kmswebrtcendpoint43> New pair selected stream_id: 1, component_id: 1, local candidate: candidate:4 1 UDP 2013266431 222.250.42.158 55844 typ host, remot
e candidate: candidate:candidate:2003496507 1 UDP 25042687 222.250.42.151 51817 typ relay raddr 83.21.212.134 rport 51817
Application log shows that error happens at the moment after both SDP answers were generated, and just before startCommunication command is going to be fired:
AppServer-0 Thu, 17 Mar 2016 08:43:11 GMT kms:CallMediaPipeline generateSdpOffer 16
AppServer-0 Thu, 17 Mar 2016 08:43:11 GMT kms:server pipeline:sdpAnswer:caller sdpReady
AppServer-0 Thu, 17 Mar 2016 08:43:11 GMT kms:CallMediaPipeline generateSdpOffer 15
AppServer-0 Thu, 17 Mar 2016 08:43:11 GMT kms:server pipeline:sdpAnswer:callee sdpReady
AppServer-0 reconnect to server 0 100 ff19ebc8-b114-495e-bf31-31f188f6ea8e
Full stack trace and log in can be seen in this gist
$ kurento-media-server -v
Version: 6.4.1~1.g3ffe480
Found modules:
Module: 'core' version '6.4.1~2.g4ed0cfc'
Module: 'elements' version '6.4.1~3.g8e842ad'
Module: 'filters' version '6.4.1~3.g06e2b4f'
# dpkg -l |grep -i libnice
ii libnice10:amd64 0.1.13.1~20160224182402.77.g7bbb87a.trusty amd64 ICE library (shared library)
I can reproduce this by using two Chrome browsers (Mac + Win) and by making around 10-15 calls (call out - hang - call out - hang ..)
If anyone could give any hints, suggestions or directions, I would really appreciate that.
Thanks!
UPD: Problem solved after switching TURN server from reciprocate-turn-server 1.9.7 to coturn 4.4.2.1

Hubot-hipchat works 1-1 chat but not on a room

Whenever I throw a command at hubot in a room i.e #hubot help I get nothing, but typing help in 1-1 chat works fine, am I missing something? has anyone else had this problem??
i have followed the setup instructions to the tee, and it still wont work
Did you end up specifying a host? I was having a similar problem, and removing the hostname fixed it. See the GH issue here:
https://github.com/github/hubot/issues/651
In my case, I could see in the logs that Hubot was receiving the commands, and even replying with the correct response, but the response was never showing up in the channel:
In the chat room (no visible in-room response):
#hubot ping
[Mon Feb 24 2014 02:04:21 GMT+0000 (UTC)] DEBUG Message '[object Object]' matched regex //^[#]?hubot[:,]?\s*(?:PING$)/i/
[Mon Feb 24 2014 02:04:21 GMT+0000 (UTC)] DEBUG OUT >
<message to="XXXXXX_hubot_test#conf.hipchat.com" type="chat" from="XXXXXX_XXXXXX#chat.hipchat.com/hubot-hipchat">
<inactive xmlns="http://jabber/protocol/chatstates"/>
<body>PONG</body>
</message>
In 1:1 messages:
[Mon Feb 24 2014 02:06:01 GMT+0000 (UTC)] DEBUG Message '[object Object]' matched regex //^[#]?hubot[:,]?\s*(?:PING$)/i/
[Mon Feb 24 2014 02:06:01 GMT+0000 (UTC)] DEBUG OUT >
<message to="XXXXX_188883#chat.hipchat.com" type="chat" from="XXXXXXXX#chat.hipchat.com/hubot-hipchat">
<inactive xmlns="http://jabber/protocol/chatstates"/>
<body>PONG</body>
</message>
I think the issue is that it uses chat.hipchat.com for 1:1 chat, and conf.hipchat.com for rooms. If you specified a specific hostname, you'll get one or the other, but not both.
If you set the environmental variables via CLI, to unset it, do
unset HUBOT_HIPCHAT_HOST.
Have you only tried: #hubot help? You can set up your prefix via: Here It does say that the
For example, the HipChat Adapter converts #hubot into hubot: before passing it to Hubot.
But I'd go ahead and try the following. Also attempt to try it locally via bin/hubot running it via the shell.
Hubot help
hubot help
Not to mention check heroku logs to make sure that hubot is showing up in your hipchat channel correctly.
Hope this helps.

Resources