I can get tarantool client version using this command:
$ tarantool --version
Tarantool 2.5.2-50-g0cb9a4bba
but how can I get the tarantool server version inside the terminal?
tarantoolctl connect 3301
connected to localhost:3301
localhost:3301>
---
- error: '[string "return version()"]:1: attempt to call global ''version'' (a nil
value)'
...
There are several ways to obtain the version:
tarantool> _TARANTOOL
---
- 2.7.0-74-g71377c28e
...
tarantool> require('tarantool').version
---
- 2.7.0-74-g71377c28e
...
tarantool> box.info.version -- only after box.cfg{<...>}
---
- 2.7.0-74-g71377c28e
...
Nevermind, found it
box.info.version
---
- 2.6.0-0-g47aa4e01e
Related
When I run the command apollo client:codegen the following error comes up :
Error: Cannot find module 'graphql/validation/rules/KnownArgumentNamesRule'
Require stack:
- C:\Users\Minseo\AppData\Roaming\npm\node_modules\apollo\node_modules\#apo
llo\federation\dist\composition\validate\preNormalization\tagDirective.js
- C:\Users\Minseo\AppData\Roaming\npm\node_modules\apollo\node_modules\#apo
llo\federation\dist\composition\validate\preNormalization\index.js
- C:\Users\Minseo\AppData\Roaming\npm\node_modules\apollo\node_modules\#apo
llo\federation\dist\composition\validate\index.js
- C:\Users\Minseo\AppData\Roaming\npm\node_modules\apollo\node_modules\#apo
llo\federation\dist\composition\composeAndValidate.js
- C:\Users\Minseo\AppData\Roaming\npm\node_modules\apollo\node_modules\#apo
llo\federation\dist\composition\index.js
- C:\Users\Minseo\AppData\Roaming\npm\node_modules\apollo\node_modules\#apo
llo\federation\dist\index.js
- C:\Users\Minseo\AppData\Roaming\npm\node_modules\apollo\node_modules\apol
lo-language-server\lib\providers\schema\file.js
- C:\Users\Minseo\AppData\Roaming\npm\node_modules\apollo\node_modules\apol
lo-language-server\lib\providers\schema\index.js
- C:\Users\Minseo\AppData\Roaming\npm\node_modules\apollo\node_modules\apol
lo-language-server\lib\project\base.js
- C:\Users\Minseo\AppData\Roaming\npm\node_modules\apollo\node_modules\apol
lo-language-server\lib\index.js
- C:\Users\Minseo\AppData\Roaming\npm\node_modules\apollo\lib\commands\clie
nt\codegen.js
- C:\Users\Minseo\AppData\Roaming\npm\node_modules\apollo\node_modules\#ocl
if\config\lib\plugin.js
- C:\Users\Minseo\AppData\Roaming\npm\node_modules\apollo\node_modules\#ocl
if\config\lib\config.js
- C:\Users\Minseo\AppData\Roaming\npm\node_modules\apollo\node_modules\#ocl
if\config\lib\index.js
- C:\Users\Minseo\AppData\Roaming\npm\node_modules\apollo\node_modules\#ocl
if\command\lib\command.js
- C:\Users\Minseo\AppData\Roaming\npm\node_modules\apollo\node_modules\#ocl
if\command\lib\index.js
- C:\Users\Minseo\AppData\Roaming\npm\node_modules\apollo\bin\run
Code: MODULE_NOT_FOUND
Downgrading does not help. But installing graphql globally seem to solve the issue.
npm install -g graphql
This is a known issue with apollo. I followed the suggestion to downgrade to node v14.17.5, and everything worked.
You only have to install apollo(yarn add apollo) and fix the problem
Very annoying issue, I installed graphql and apollo globally using node v 14. At the end this worked for me: https://github.com/apollographql/apollo-tooling/issues/2415#issuecomment-930173053
Now it works with node v 16 and w/o post install. 🤷♂️
Just install appolo into your dev dependencies, e.g yarn add -D apollo and use it like ./node_modules/.bin/apollo client:codegen
I've tried on a windows PC instead of mac with following versions
apollo/2.34.0 win32-x64 node-v10.15.3
That worked for me
I am getting Mongo::OperationFailure - Database command 'update' failed: BSON field 'update.multi' is an unknown field. error on MongoMapper set method.
eg:
Metadata.set({:cid => 123}, :brand => "b1")
REF: http://mongomapper.com/documentation/plugins/modifiers.html
I am using following environment:
- Ruby 2.2.0
- Rails 3.2.22
- Gem MongoMapper 0.14.0
- MongoDB 3.6.0
[EDIT]
I am also getting it on insert with error Mongo::OperationFailure: Database command 'insert' failed: BSON field 'insert.w' is an unknown field.
MongoMapper Query
Had the same exact error, was fighting for a while.
solved by using mongo 3.2 - inside of docker container, because wasn't able to start it localy...
something like this eventually worked for me
docker run -it -p 27017:27017 mongo:3.2 bash
I had the same problem, in my case the problem was on the connection:
logger = Logger.new(STDOUT)
mongo_connection = Mongo::Connection.new '127.0.0.1', 27017, logger: logger
The 'logger:' option was missing.
I am trying to use Zeppelin (v 0.7.0 java 1.8 on Windows 10; same with docker v .0.7.1) JDBC interpreter to query Oracle Database.
So far I've found papers like example. I try to use jdbc interpreter with:
common.max_count=100
default.driver=oracle.jdbc.pool.OracleDataSource
default.password:$password
default.user=$my_user_name
default.url=jdbc:oracle:thin:#$host:1521/$service_name>
zeppelin.jdbc.concurrent.max_connection=10
zeppelin.jdbc.concurrent.use=true
Connection looks to be established successfully*, but even simplest query (like sql% select 1 from dual) runs for ever.
Does anyone knows/have a clue on what is to be added?
what I see in terminal - repeating lines
sKey: shared_process for InterpreterSetting Id: 2CMBZV4T1, Name: jdbc
DEBUG [2017-06-15 16:03:28,203] ({Thread-90} InterpreterSetting.java[getInterpreterProcessKey]:143) - getInterpreterProcessKey: shared_process for InterpreterSetting Id: 2CMBZV4T1, Name: jdbc
DEBUG [2017-06-15 16:03:28,204] ({Thread-90} InterpreterSetting.java[getInterpreterProcessKey]:143) - getInterpreterProcessKey: shared_process for InterpreterSetting Id: 2CMBZV4T1, Name: jdbc
DEBUG [2017-06-15 16:03:28,204] ({Thread-90} InterpreterFactory.java[getInterpreterSessionKey]:1244) - Interpreter session key: shared_session, for note: 2CMEC9SS4, user: anonymous, InterpreterSetting Name: jdbc
DEBUG [2017-06-15 16:03:28,205] ({Thread-90} InterpreterSetting.java[getInterpreterProcessKey]:143) - getInterpreterProcessKey: shared_process for InterpreterSetting Id: 2CMBZV4T1, Name: jdbc
DEBUG [2017-06-15 16:03:28,205] ({Thread-90} InterpreterSetting.java[getInterpreterProcessKey]:143) - getInterpreterProcessKey: shared_process for InterpreterSetting Id: 2CMBZV4T1, Name: jdbc
In the same time I don't have an issue using spark interpretor with scala over jdbc same driver.
at least when I provide wrong password it prints meaningful response
Are you sure a query is running?
selec 1 from dual
is not valid SQL.
Check on Oracle side in gv$session for your query. If it is running, it will be there.
I am working with PHPStorm and XAMPP on Win7. Both works fine, but at some point I start getting "500 Internal Server Error PhpStorm 9.0.2" as soon as I add more code e.g. a new <div></div>. When I delete it again, it works again. The same code works on webhosting but not on localhost.
What could be the issue?
That just makes no sense, why would adding a new div cause an server error?
There are no logs about this issue in the error.log or php_error_log.
Found out that there is a IDE-error log, it says:
2015-11-08 17:49:28,975 [6667034] ERROR - ains.io.fastCgi.FastCgiService - readerIndex(5) + length(1) exceeds writerIndex(5): CompositeByteBuf(ridx: 5, widx: 5, cap: 8189, components=2)
java.lang.IndexOutOfBoundsException: readerIndex(5) + length(1) exceeds writerIndex(5): CompositeByteBuf(ridx: 5, widx: 5, cap: 8189, components=2)
at io.netty.buffer.AbstractByteBuf.checkReadableBytes(AbstractByteBuf.java:1138)
at io.netty.buffer.AbstractByteBuf.readByte(AbstractByteBuf.java:542)
at org.jetbrains.io.fastCgi.FastCgiService.a(FastCgiService.java:197)
at org.jetbrains.io.fastCgi.FastCgiService.responseReceived(FastCgiService.java:170)
at org.jetbrains.io.fastCgi.FastCgiDecoder.contentReceived(FastCgiDecoder.java:128)
at org.jetbrains.io.fastCgi.FastCgiDecoder.contentReceived(FastCgiDecoder.java:15)
at org.jetbrains.io.Decoder.readContent(Decoder.java:68)
at org.jetbrains.io.fastCgi.FastCgiDecoder.messageReceived(FastCgiDecoder.java:75)
at org.jetbrains.io.Decoder.channelRead(Decoder.java:38)
at io.netty.channel.ChannelHandlerInvokerUtil.invokeChannelReadNow(ChannelHandlerInvokerUtil.java:84)
at io.netty.channel.DefaultChannelHandlerInvoker.invokeChannelRead(DefaultChannelHandlerInvoker.java:153)
at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:187)
at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:947)
at io.netty.channel.oio.AbstractOioByteChannel.doRead(AbstractOioByteChannel.java:147)
at io.netty.channel.oio.AbstractOioChannel$1.run(AbstractOioChannel.java:44)
at io.netty.channel.ThreadPerChannelEventLoop.run(ThreadPerChannelEventLoop.java:52)
at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:834)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
at org.jetbrains.ide.PooledThreadExecutor$1$1.run(PooledThreadExecutor.java:56)
2015-11-08 17:49:28,975 [6667034] ERROR - ains.io.fastCgi.FastCgiService - PhpStorm 9.0.2 Build #PS-141.2462
2015-11-08 17:49:28,975 [6667034] ERROR - ains.io.fastCgi.FastCgiService - JDK: 1.8.0_51
2015-11-08 17:49:28,976 [6667035] ERROR - ains.io.fastCgi.FastCgiService - VM: Java HotSpot(TM) Server VM
2015-11-08 17:49:28,976 [6667035] ERROR - ains.io.fastCgi.FastCgiService - Vendor: Oracle Corporation
2015-11-08 17:49:28,976 [6667035] ERROR - ains.io.fastCgi.FastCgiService - OS: Windows 7
2015-11-08 17:49:28,976 [6667035] ERROR - ains.io.fastCgi.FastCgiService - Last Action: ShowLog
You are using PhpStorm's own simple built-in web server. For some reason it shows those errors. If you have XAMPP .. then just XAMPP.
For that you need to create an Deployment entry where you will specify your base URL which PhpStorm will use to open files in browser. For that:
Settings | Build, Execution, Deployment | Deployment
Create and configure new deployment entry ("In Place" should be fine)
Do not forget to mark it as Default for this project
Now IDE will use URL specified there instead of built-in web server.
As for actual error:
Please try latest & recently released PhpStorm v10
Try changing your PHP version (in case if you have upgraded it recently)
Submit bug report ticket to JetBrains' Issue Tracker if you wish keep using built-in web server for devs to look into.
As recommended, I updated honeybadger gem to version 2.0.
I follow all the instructions while upgrading as mention here.
Next when I started my server after upgrading i.e shotgun -p3000, and load page, request gets timeout and throw:
ERROR: Got response code: 500
And Log look like this:
I, [2015-06-02T10:43:01.447813 #11587] INFO -- : Starting Honeybadger version 2.0.12 level=1 pid=11587
I, [2015-06-02T10:43:01.448585 #11586] INFO -- : Starting Honeybadger version 2.0.12 level=1 pid=11586
W, [2015-06-02T10:43:01.454212 #11587] WARN -- : Initializing development backend: data will not be reported. level=2 pid=11587
W, [2015-06-02T10:43:01.454692 #11586] WARN -- : Initializing development backend: data will not be reported. level=2 pid=11586
I, [2015-06-02T10:43:01.462911 #11588] INFO -- : Starting Honeybadger version 2.0.12 level=1 pid=11588
W, [2015-06-02T10:43:01.472935 #11588] WARN -- : Initializing development backend: data will not be reported. level=2 pid=11588
I, [2015-06-02T10:43:04.496411 #11601] INFO -- : Starting Honeybadger version 2.0.12 level=1 pid=11601
W, [2015-06-02T10:43:04.500226 #11601] WARN -- : Initializing development backend: data will not be reported. level=2 pid=11601
I, [2015-06-02T10:43:07.004766 #11614] INFO -- : Starting Honeybadger version 2.0.12 level=1 pid=11614
W, [2015-06-02T10:43:07.008677 #11614] WARN -- : Initializing development backend: data will not be reported. level=2 pid=1161
I am using following tools:
Ruby 2.1.2
Sinatra 1.4.6
Grape 0.11.0
HoneyBadger 2.0.12
Please help me to resolve this issue.
In previous honeybadger version i.e ~> 1.9, we had to specify Honeybadger::Rack::ErrorNotifier in config.ru file. But after upgrading, we have to remove Honeybadger::Rack::ErrorNotifier from config.ru file(upgrading document does not consist this info).
After removing Honeybadger::Rack::ErrorNotifier from config.ru, it works as expected.
Next, If you find your server slow and spawns more pids after upgrading then update your honeybadger gem
gem 'honeybadger', '2.1.0.beta.1'.