zgsrc / ibjs Goto Github PK

this.fields = []in Quote constructor conflict with fields getter on his parent class RealTime class

Hi. I got this error when i run the first example on README.md
I'm using version "^0.4.9".

TypeError: ib.exit is not a function
    at Environment.sdk.environment (/Users/grantchiu/dev/algo.strategies/algo.sdk/index.js:44:6)
    at Environment.g (events.js:291:16)
    at emitTwo (events.js:106:13)
    at Environment.emit (events.js:191:7)
    at Accounts.loadHandler (/Users/grantchiu/dev/algo.strategies/algo.sdk/node_modules/ib-sdk/model/environment.js:55:22)
    at Accounts.g (events.js:291:16)
    at emitNone (events.js:86:13)
    at Accounts.emit (events.js:185:7)
    at Request.service.accountSummary.on.on.cancel (/Users/grantchiu/dev/algo.strategies/algo.sdk/node_modules/ib-sdk/model/accounts.js:122:18)
    at emitOne (events.js:101:20)

Have a coding request related to this.. Do u freelance, How to contact u by email..??

On the client code here: https://github.com/triploc/ib-sdk/blob/master/doc/remoting.md

var io = require('socket.io-client')('http://localhost:8080'),
    session = sdk.proxy(io);
    
session.service.relay(socket);

what is "socket" in session.service.relay(socket)? thanks!

Hi,

do you have an example of how the structure of symbols in the startup file has to look like that it could be accessed?

How do I add a security "SPY" or even a respective order?

Thank you!

failed to get data as following example.

AAPL.charts.minutes.five.stream().on("update", data => {
    console.log(data);
});

Thanks for a great library, It's my first stab at node so please bear with me if I misunderstood something.

When creating a contract object the dates in .schedule are all Invalid dates for me. It might be because I am trying to run this on the Swedish stock exchange in the CET timezone.

I have tracked this error down to the lines in contract.js that looks like this:

Date.create(date.format("{Month} {dd}, {yyyy}") + " " + time[0] + ":00 " + timeZoneId, { future: true })

In my case the string to be parsed look like this

Date.create("January 12, 2018 09:00:00 MET", { future: true })

That returns an invalid date. A reproducible example below

require("sugar").extend();
console.log("startdate " + Date.create("January 12, 2018 09:00:00 MET", { future: true })); // IB format
console.log("startdate " + Date.create("January 12, 2018 09:00:00 CET", { future: true })); // MET and CET is the same TZ
console.log("startdate " + Date.create("January 12, 2018 09:00:00 UTC", { future: true })); // Returns a CET date. not UTC
console.log("startdate " + Date.create("January 12, 2018 09:00:00", { future: true }));

returns

startdate Invalid Date
startdate Invalid Date
startdate Fri Jan 12 2018 10:00:00 GMT+0100 (CET)
startdate Fri Jan 12 2018 09:00:00 GMT+0100 (CET)

On the Sugar npm page they say that sugar can't handle timezones directly but you can use another library for that.

Sugar does not deal with timezone abbreviations (i.e. "PST", etc). Timezone offsets will be correctly parsed if they are in ISO-8601 format (+09:00, +0900, or Z for UTC), however if an abbreviation exists it will be ignored. Sugar however plays nicely with other libraries that offer full timezone support such as timezone.js.

Any ideas on how to solve this?

Does this project support trading of options? Especially ODAX based on the DAX index? I've had no luck using the the node-ib package.

Thanks!

when i initial sdk env. with sdk.environment("./config/default.json", (err, ib) => {}).
It doesnt work and got Cannot read property 'timeout' of undefined

After investigate you code
I found that you should use sync call when reading config file.

Can't find you :)
https://www.npmjs.com/search?q=interactive+brokers

TypeError: config.hooks.traceError is not a function
at fs.appendFile.err (C:\Users\J\node_modules\ibjs\index.js:197:140)
at fs.js:1279:7
at FSReqWrap.oncomplete (fs.js:135:15)