You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the latest default code base (changeset 4530d12232c2), mserver5 fails to start properly:
.../MonetDB $ mserver5
MonetDB 5 server v11.16.0
This is an unreleased version
Serving database 'demo', using 8 threads
Compiled for x86_64-unknown-linux-gnu/64bit with 64bit OIDs dynamically linked
Found 15.629 GiB available main-memory.
Copyright (c) 1993-July 2008 CWI.
Copyright (c) August 2008-2013 MonetDB B.V., all rights reserved
Visit http://www.monetdb.org/ for further information
!SyntaxException:parseError:address JSONrenderobject;
!SyntaxException:parseError: ^
not found
!SyntaxException:parseError:address JSONrenderobject;
!SyntaxException:parseError: ^ not found
Comment 18764
Date: 2013-06-01 08:56:23 +0200
From: @mlkersten
fixed by checking in the (incomplete) implementation
The text was updated successfully, but these errors were encountered:
Date: 2013-06-01 08:32:17 +0200
From: @drstmane
To: MonetDB5 devs <>
Version: -- development
CC: @mlkersten
Last updated: 2013-07-03 08:47:59 +0200
Comment 18761
Date: 2013-06-01 08:32:17 +0200
From: @drstmane
With the latest default code base (changeset 4530d12232c2), mserver5 fails to start properly:
.../MonetDB $ mserver5
not foundMonetDB 5 server v11.16.0
This is an unreleased version
Serving database 'demo', using 8 threads
Compiled for x86_64-unknown-linux-gnu/64bit with 64bit OIDs dynamically linked
Found 15.629 GiB available main-memory.
Copyright (c) 1993-July 2008 CWI.
Copyright (c) August 2008-2013 MonetDB B.V., all rights reserved
Visit http://www.monetdb.org/ for further information
!SyntaxException:parseError:address JSONrenderobject;
!SyntaxException:parseError: ^
!SyntaxException:parseError:address JSONrenderobject;
!SyntaxException:parseError: ^ not found
Comment 18764
Date: 2013-06-01 08:56:23 +0200
From: @mlkersten
fixed by checking in the (incomplete) implementation
The text was updated successfully, but these errors were encountered: