Closed Tjzabel closed 5 years ago
Running teleirc from HEAD
works perfectly fine on Fedora 29.
I am wondering if this is indeed an old package versioning issue on the CentOS 7 machine.
The version of the CentOS 7 machine is just CentOS 7.0.
@jwflory I am actually still unable to reach the CentOS machine I've provisioned for RITlug teleirc. Did you ever get to running the Ansible update to allow me to ssh in? I can't even ping the machine.
After debugging with @jwflory, it seems this is an issue with CentOS and EPEL, not teleirc.
CentOS's node
version is v6.14.3
, which does not support asnyc calls. This makes teleirc fail.
Since we already specify a node version of ~8
, this issue may be able to be closed. I'm leaving this open until our teleirc hack session sunday morning.
It was a deployment issue. This was resolved after upgrading to Node v10.x LTS. The development bot is working and online again. Thanks for the debugging help @Tjzabel. :+1:
Closing. :clapper:
Issue
Currently, when running teleirc from CentOS 7, teleirc does not start, citing an unexpected identifier.
In my experience, this usually occurs when
async
is not supported in nodejs. However,node
is on version8.x.x
, which should support the async functionality added in the7.x.x
versions.We need to figure out why the master branch is failing, and also whether or not this is an isolated case with a CentOS 7 server. Further testing needs to be done with our Dockerfiles to figure out if this is an isolated issue or not.
Stacktrace