Frappe Error 8.0.55 in Develop mode

Hi,
I have updated my Dev and the below error is given when i do bench start

00:47:11 redis_cache.1 | [4240] 22 May 00:47:11.676 * The server is now ready to accept connections on port 13000
00:47:18 socketio.1 | listening on *: 9000
00:47:21 worker_short.1 | 00:47:21 RQ worker u’rq:worker:ubuntu.4239.short’ started, version 0.6.0
00:47:21 worker_default.1 | 00:47:21 RQ worker u’rq:worker:ubuntu.4220.default’ started, version 0.6.0
00:47:21 worker_short.1 | 00:47:21 Cleaning registries for queue: short
00:47:21 worker_default.1 | 00:47:21 Cleaning registries for queue: default
00:47:21 worker_short.1 | 00:47:21
00:47:21 worker_long.1 | 00:47:21 RQ worker u’rq:worker:ubuntu.4212.long’ started, version 0.6.0
00:47:21 worker_default.1 | 00:47:21
00:47:21 worker_short.1 | 00:47:21 *** Listening on short…
00:47:21 worker_default.1 | 00:47:21 *** Listening on default…
00:47:21 worker_long.1 | 00:47:21 Cleaning registries for queue: long
00:47:21 worker_long.1 | 00:47:21
00:47:21 worker_long.1 | 00:47:21 *** Listening on long…
00:47:21 web.1 | * Running on http://0.0.0.0:8000/ (Press CTRL+C to quit)
00:47:21 watch.1 | /home/helio/frappe-bench/apps/frappe/frappe/build.js:47
00:47:21 watch.1 | let socket_connection = false;
00:47:21 watch.1 | ^^^
00:47:21 watch.1 |
00:47:21 watch.1 | SyntaxError: Block-scoped declarations (let, const, function, class) not yet supported outside strict mode
00:47:21 watch.1 | at exports.runInThisContext (vm.js:53:16)
00:47:21 watch.1 | at Module._compile (module.js:387:25)
00:47:21 watch.1 | at Object.Module._extensions…js (module.js:422:10)
00:47:21 watch.1 | at Module.load (module.js:357:32)
00:47:21 watch.1 | at Function.Module._load (module.js:314:12)
00:47:21 watch.1 | at Function.Module.runMain (module.js:447:10)
00:47:21 watch.1 | at startup (node.js:148:18)
00:47:21 watch.1 | at node.js:405:3
00:47:21 web.1 | * Restarting with inotify reloader
00:47:21 system | watch.1 stopped (rc=0)
00:47:21 system | sending SIGTERM to redis_socketio.1 (pid 4206)
00:47:21 system | sending SIGTERM to worker_long.1 (pid 4205)
00:47:21 system | sending SIGTERM to redis_queue.1 (pid 4210)
00:47:21 system | sending SIGTERM to web.1 (pid 4207)
00:47:21 system | sending SIGTERM to schedule.1 (pid 4208)
00:47:21 system | sending SIGTERM to worker_default.1 (pid 4213)
00:47:21 system | sending SIGTERM to socketio.1 (pid 4209)
00:47:21 system | sending SIGTERM to redis_cache.1 (pid 4238)
00:47:21 system | sending SIGTERM to worker_short.1 (pid 4222)
00:47:21 redis_socketio.1 | [4214 | signal handler] (1495410441) Received SIGTERM, scheduling shutdown…
00:47:21 worker_long.1 | 00:47:21 Warm shut down requested
00:47:21 redis_queue.1 | [4223 | signal handler] (1495410441) Received SIGTERM, scheduling shutdown…
00:47:21 worker_default.1 | 00:47:21 Warm shut down requested
00:47:21 system | socketio.1 stopped (rc=-15)
00:47:21 system | schedule.1 stopped (rc=-15)
00:47:21 redis_cache.1 | [4240 | signal handler] (1495410441) Received SIGTERM, scheduling shutdown…
00:47:21 worker_short.1 | 00:47:21 Warm shut down requested
00:47:21 redis_cache.1 | [4240] 22 May 00:47:21.599 # User requested shutdown…
00:47:21 redis_cache.1 | [4240] 22 May 00:47:21.599 # Redis is now ready to exit, bye bye…
00:47:21 system | redis_cache.1 stopped (rc=-15)
00:47:21 redis_queue.1 | [4223] 22 May 00:47:21.600 # User requested shutdown…
00:47:21 redis_queue.1 | [4223] 22 May 00:47:21.600 # Redis is now ready to exit, bye bye…
00:47:21 system | redis_queue.1 stopped (rc=-15)
00:47:21 redis_socketio.1 | [4214] 22 May 00:47:21.601 # User requested shutdown…
00:47:21 redis_socketio.1 | [4214] 22 May 00:47:21.601 # Redis is now ready to exit, bye bye…
00:47:21 system | redis_socketio.1 stopped (rc=-15)
00:47:21 system | worker_long.1 stopped (rc=-15)
00:47:21 system | worker_default.1 stopped (rc=-15)
00:47:21 system | worker_short.1 stopped (rc=-15)
00:47:21 system | web.1 stopped (rc=-15)

1 Like

This has been fixed. https://github.com/frappe/frappe/pull/3359
You will have to wait till it gets merged.

Hi, I am facing this issue as well.

@netchampfaris i hope this does not affect the Production server?