Nebula console crashes on date()

Users Issues & Bugs
1

Here is what i did:

(root@nebula) [(none)]> return date() as d
2021/04/12 14:33:46 [INFO] Successfully reconnect to host: 127.0.0.1, port: 29669
2021/04/12 14:33:46 Loop error, read tcp 127.0.0.1:56124->127.0.0.1:29669: read: connection reset by peer

Bye root!
Mon, 12 Apr 2021 14:33:46 CEST

2021/04/12 14:33:46 [WARNING] Sign out failed, write tcp 127.0.0.1:56124->127.0.0.1:29669: write: broken pipe
panic: Loop error, read tcp 127.0.0.1:56124->127.0.0.1:29669: read: connection reset by peer

goroutine 1 [running]:
log.Panicf(0x7906b8, 0xe, 0xc0001a1e78, 0x1, 0x1)
        /opt/hostedtoolcache/go/1.14.15/x64/src/log/log.go:358 +0xc0
main.main()
        /home/runner/work/nebula-console/nebula-console/main.go:386 +0x4e1

But now() works fine:

(root@nebula) [(none)]> return now() as d
+------------+
| d          |
+------------+
| 1618230920 |
+------------+
Got 1 rows (time spent 374/928 us)

Mon, 12 Apr 2021 14:35:20 CEST

I’m using the latest v2-nightly from docker hub.

2

What’s your NebulaGraph’s version and Console’s version, I’m not sure whose version is v2-nightly.

3

Thanks for the feedback, this is a bug, we will pushed a pr to fix it.
When the pr is merged, you can repull the repository and make it.

$ git clone https://github.com/vesoft-inc/nebula-console
$ cd nebula-console
$ make
4

Thanks for your feedback, I will track it.

5

This problem has been fixed in this pr ：fix date() crash by jievince · Pull Request #943 · vesoft-inc/nebula-graph · GitHub