ironArray / Caterva2

REST and on-demand access to local/remote Blosc2 data repositories
https://ironarray.io/caterva2
Other
5 stars 0 forks source link

Data viewer has stopped to work #74

Closed FrancescAlted closed 1 week ago

FrancescAlted commented 2 weeks ago

Somehow, the data viewer does not work properly anymore. In main, when starting the services normally, i.e.:

francesc@Francescs-MacBook-Air ~/b/Caterva2 (main)> cat2bro &                                                               (caterva2)
francesc@Francescs-MacBook-Air ~/b/Caterva2 (main)> roots={'example': Root(name='example', http='localhost:8001', subscribed=None), 'b2tests': Root(name='b2tests', http='localhost:8001', subscribed=None), 'foo': Root(name='foo', http='localhost:8001', subscribed=None)}
INFO:     Started server process [54024]
INFO:     Waiting for application startup.
INFO:     Application startup complete.
INFO:     Uvicorn running on http://localhost:8000 (Press CTRL+C to quit)
francesc@Francescs-MacBook-Air ~/b/Caterva2 (main)> cat2pub example root-example &                                          (caterva2)
francesc@Francescs-MacBook-Air ~/b/Caterva2 (main)> INFO:     ::1:58481 - "POST /api/roots HTTP/1.1" 200 OK                 (caterva2)
INFO:     Started server process [54039]
INFO:     Waiting for application startup.
INFO:     ('::1', 58482) - "WebSocket /pubsub" [accepted]
INFO:     connection open
INFO:     Application startup complete.
INFO:     Uvicorn running on http://localhost:8001 (Press CTRL+C to quit)

francesc@Francescs-MacBook-Air ~/b/Caterva2 (main)> cat2sub &                                                               (caterva2)
francesc@Francescs-MacBook-Air ~/b/Caterva2 (main)> INFO:     Started server process [54053]                                (caterva2)
INFO:     Waiting for application startup.
INFO:     Application startup complete.
INFO:     Uvicorn running on http://localhost:8002 (Press CTRL+C to quit)

I get this:

image

As you can see, neither the indices and values are updated anymore.

martaiborra commented 1 week ago

It seems that the commit which caused the problem was 64349b218233428f31ab79f3cf91256667d8cb24.