You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi!
I'm running flok (1.2) with tidal, following the instructions for running the repl.
whenever an error or message occurs i get it exactly twice (when i'm alone) and for each participant joining (even if they are not running the repl) twice again.. this makes it quite hard to debug code, especially with lots of people. am i doing something wrong?
so for example running return 1 prints out two 1's when i'm alone, and 4 1's when two people have joined.
this happens both with the flok.cc server and running locally.
I can see the message coming into the repl just once, so for some reason it's just sent out multiple times.
additionaly i'm curious if there is a way so that every participant can only see the messages produced by the code that they triggered?
best,
martin
The text was updated successfully, but these errors were encountered:
ok, so apparently when i'm alone (after a fresh instance of flok) it seems to be fine (must have tested it wrong before), but as soon as somone joins, the messages are duplicated for everyone
Hi!
I'm running flok (1.2) with tidal, following the instructions for running the repl.
whenever an error or message occurs i get it exactly twice (when i'm alone) and for each participant joining (even if they are not running the repl) twice again.. this makes it quite hard to debug code, especially with lots of people. am i doing something wrong?
so for example running
return 1
prints out two 1's when i'm alone, and 4 1's when two people have joined.this happens both with the flok.cc server and running locally.
I can see the message coming into the repl just once, so for some reason it's just sent out multiple times.
additionaly i'm curious if there is a way so that every participant can only see the messages produced by the code that they triggered?
best,
martin
The text was updated successfully, but these errors were encountered: