[BUG] Error: this.stream.clearLine is not a function

Question

[BUG] Error: this.stream.clearLine is not a function

brodyFlannigan opened this issue 4 years ago · comments

Hi! I seem to have encountered an error with the latest release of GTFS-to-HTML (1.4.5)

Issue

When running GTFS-to-HTML, feed will import correctly and GTFS-to-HTML will export 1 timetable, then this error message appears:

Error: this.stream.clearLine is not a function
[  TypeError: this.stream.clearLine is not a function

  - node-progress.js:210 ProgressBar.interrupt
    [npm]/[gtfs-to-html]/[progress]/lib/node-progress.js:210:15

  - gtfs-to-html.js:81 module.exports
    [npm]/[gtfs-to-html]/lib/gtfs-to-html.js:81:11

  - gtfs-to-html.js:39 async setupImport
    [npm]/[gtfs-to-html]/bin/gtfs-to-html.js:39:3

]

Expected behaviour

GTFS-to-HTML would not produce an error message, and all timetables would export

Reproduction steps

Install GTFS-to-HTML
Open the config-sample.json file and remove the sqlitePath variable from the file, then set showMap to false.
Run GTFS-to-HTML using the sample config file
Watch GTFS-to-HTML come to a grinding halt.

Thanks!

Brendan Nee · Answer 1 · Fri Dec 11 2020 13:51:37 GMT+0800 (China Standard Time)

Thanks for the detailed report.

Can you tell me what OS you are on and what version of node.js you are using so I I can try to reproduce?

Does this issue only occur when showMap is set to false?

Brody Flannigan · Answer 2 · Sun Dec 13 2020 00:55:05 GMT+0800 (China Standard Time)

Sorry for the delay OS is Win7 Pro (I know, it's brutal but I need it to run specialized software) Node version is 12.18.3 This is also an issue with showMap set to true (and when a valid MapBox key is entered)

…

On Fri, Dec 11, 2020 at 12:51 AM Brendan Nee ***@***.***> wrote: Thanks for the detailed report. Can you tell me what OS you are on and what version of node.js you are using so I I can try to reproduce? Does this issue only occur when showMap is set to false? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#101 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALDT5VZM4VTOTKNBONWUHVLSUGXPNANCNFSM4UVQSWDQ> .

Brendan Nee · Answer 3 · Sun Dec 13 2020 17:19:26 GMT+0800 (China Standard Time)

It seems like a windows issue with the way logging to the console is happening inside of the node progress module.

I pushed an update that may solve this - GTFS-to-HTML 1.4.6

If updating to version 1.4.6 doesn't work, here are a few suggestions:

Try setting verbose to false in your config.json for GTFS-to-HTML - this should hide all logs to the terminal

Try running gtfs-to-html in an external terminal application on your machine and not inside of VScode or webstorm. See this comment for details https://stackoverflow.com/a/58063715/363155

Brody Flannigan · Answer 4 · Wed Dec 16 2020 06:59:57 GMT+0800 (China Standard Time)

Sorry about the delay in response. I'm really busy. I should have time to try out you possible fix tomorrow.

Brody Flannigan · Answer 5 · Fri Dec 18 2020 04:42:08 GMT+0800 (China Standard Time)

Setting verbose to false was the fix, although it isn't ideal, I can live with it.
Thanks for the help. Closing issue