Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

dxfeed websockets API Not Respecting FEED_SETUP Message #6

Closed
avil-jc01 opened this issue Apr 24, 2024 · 5 comments
Closed

dxfeed websockets API Not Respecting FEED_SETUP Message #6

avil-jc01 opened this issue Apr 24, 2024 · 5 comments
Labels
question Further information is requested

Comments

@avil-jc01
Copy link

Hello,

I am debugging my dxfeed client, and keep running into this stubborn issue. I am unable to reproduce exactly; running the same code multiple times results in either a successful FEED_SETUP or an unsuccessful one depending on the day/hour.

I am trying to send the following FEED_SETUP message:

{'type': 'FEED_SETUP', 'channel': 1, 'acceptAggregationPeriod': 0.0, 'acceptDataFormat': 'FULL', 'acceptEventFields': {'Quote': ['eventType', 'eventSymbol', 'eventTime', 'sequence', 'timeNanoPart', 'bidTime', 'bidExchangeCode', 'bidPrice', 'bidSize', 'askTime', 'askExchangeCode', 'askPrice', 'askSize']}}

However, I keep getting back

{"type":"FEED_CONFIG","channel":1,"dataFormat":"COMPACT","aggregationPeriod":0.0}

, where acceptDataFormat is not respected. My parser is based only on the FULL dataset; COMPACT won't work for me. Why does the API not respect my FEED_SETUP message?

@avil-jc01
Copy link
Author

I can post the full exchange if necessary - this is the version string I'm using:

"version":"1.0-1.0.0-20240320-140337"

@voros1
Copy link

voros1 commented Apr 27, 2024

I'm also getting this issue, and have no solution. Worse, I sometimes get FULL. I've been using dxlink since middle of last summer, and this issue seems new within the past couple of weeks.

@Fyzu
Copy link
Member

Fyzu commented May 15, 2024

Please share which endpoint do you use?

@Fyzu Fyzu added the question Further information is requested label May 15, 2024
@avil-jc01
Copy link
Author

Hi @Fyzu - happy to continue the discussion in the other issue. I have the same as the other commenter - same endpoint and everything.

@avil-jc01
Copy link
Author

closing as dupe

@avil-jc01 avil-jc01 closed this as not planned Won't fix, can't repro, duplicate, stale May 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants