Skip to content
This repository has been archived by the owner on Aug 25, 2024. It is now read-only.

Wrong output on unkown channel #63

Open
ai opened this issue Apr 5, 2019 · 3 comments
Open

Wrong output on unkown channel #63

ai opened this issue Apr 5, 2019 · 3 comments

Comments

@ai
Copy link
Member

ai commented Apr 5, 2019

If Logux sends { type: 'logux/susbcribe', channel: 'unknown' }, Rails will answer:

Write to Logux response: ["unknownChannel","1554484116313 380:R7BNGAP5:Pjoz3bdE 0"]
Write to Logux response: ]

But Logux wait for [["unknownChannel", …]], array in array.

/cc @dsalahutdinov

@dsalahutdinov
Copy link
Collaborator

Hi @ai
Seems it works as expected, here are the test describing the case
Let's check together at the evening :)

@ai
Copy link
Member Author

ai commented Apr 11, 2019

What is have_chunk? I can’t google docs

@ai
Copy link
Member Author

ai commented Apr 11, 2019

Here is a way to reproduce:

  1. Remove prices channel policy in Amplifr.
  2. Reload page.
  3. Look at Amplifr Logux log. You will see unknown response error. In Rails log a found just ["unknownChannel", …] instead of [["unknownChannel", …]].

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants