Crushing when collaborating with multiplayers

[KonVas]

It seems that there are lots of crushes when trying to run with two computers. It works for a little bit when restarting concurrently but then again it crushes on one of the machines or on both of them making impossible to edit or run new lines.

[Qirky]

Hi there, I'll need a bit more information in order to try and help. What operating system were you using (Linux, Windows, Mac) and what live coding language you were using (FoxDot, Tidal, something else)? Do you get any error message in your command line program? Is there anything that you are doing when the program crashes or does it happen randomly? Thanks

[KonVas]

Hello, sorry I missed some crucial information I was during trying get my head around it at the same time. We both trying to run TidalCycles (no-stack) but also tested Stack with same problems. The issue seems to be caused by random factors thus I can't really point anything specifically. However I noticed that it will mostly hung once there is a typo, but still this is arbitrary it will also happen in normal execution from time to time, right now we are using it on Mojave vs. Sierra MacOS shifting between them the server and client assignments. I also tried to use a separate Mac computer to host the server only but same problems. Also, there is no error message to point on during the crashes. hope that makes some sense cause we really like the system and we got some very interesting results as long as it worked thus we looking forward to have it run properly for a gig.

[Qirky]

Unfortunately I have no access to any Mac OS so I'm unable to test, but if it's ok with you I'm going to ask you to do a few things. Are you running the executable file or the python file i.e. python run-client.py? Can you try using FoxDot with Troop and see if the crash also happens? What is the "typo" that also seems to affect it? Are you using any special/international characters? If you could screenshot it next time it happens and post it here that would be really helpful, thanks

[KonVas]

Okay I am about to do so. One thing, I am using a WiFi connection hope this is not a problem. Trying this python3 run-client.py the other is not working for me.

[KonVas]

So I think I found the reason of the problem. I was running the files.py with python3 command instead hunting a little bit in other issues in this repo turns out that it needs to be run with python (2.7.3) at max. Now seems okay, I wonder if there is any syntax highliting capabilities in Troop and if the other atrributes of the interface are working okay in MacOS for example, how to log the performance.

[Qirky]

Hmm that's still very strange, it should work for both Python 2 and 3, but I'm glad it is working. Not sure if I will implement syntax highlighting as it is quite complicated when using different colours for different users. Let me know if anything else happens!

[KonVas]

I am currently running Troop on Python 2.7.15 :: Anaconda, Inc. shall I try to make it work with 3 then? Is that the preferable version?

[Qirky]

If you can find the issue that would be really useful. Ideally it should be compatible with Python 2 and 3 - especially with Python 2 becoming unsupported soon

[KonVas]

Okay, for now running on Python 2.7.3 I can see this <interactive>:20:11: error: Variable not in scope: streamAll :: Stream -> t tidal> tidal> but it seems it can be safely ignored.

[KonVas]

Moment of distraction: screenshot of crush at this link: https://www.dropbox.com/s/rahbf9x5tv5pwx4/Screenshot%202019-03-13%2018.43.30.png?dl=0

You can actually rerproduce it, I executed twice after restarting the client two identical lines of code at the same time (see screenshot first and second lines).

• MacOS Mojave
• Python 3.7
• SC 3.10.0
• TidalCycles latest (1.0?)

[Qirky]

I am unable to replicate on Windows which makes me think it is specific to Mac OS. I run these two lines of code:

d1 $ jux' [id, rev, fast 2] $ sound "bd cp sn:2 mt*2" # pan saw
d1 $ jux' [id, rev, fast 2] $ sound "bd cp sn:2 mt*2" # pan saw

which gives me this error:

<interactive>:105:31: error:
    * Couldn't match expected type `Pattern ControlMap
                                    -> Pattern ControlMap'
                  with actual type `Pattern ControlMap'
    * The first argument of ($) takes one argument,
      but its type `Pattern ControlMap' has none
      In the second argument of `($)', namely
        `sound "bd cp sn:2 mt*2" # pan saw d1
           $ jux' [id, rev, fast 2] $ sound "bd cp sn:2 mt*2" # pan saw'
      In the second argument of `($)', namely
        `jux' [id, rev, fast 2]
           $ sound "bd cp sn:2 mt*2" # pan saw d1
               $ jux' [id, rev, fast 2] $ sound "bd cp sn:2 mt*2" # pan saw'

<interactive>:105:57: error:
    * Couldn't match expected type `(ControlPattern -> IO ())
                                    -> Pattern ControlMap'
                  with actual type `Pattern ControlMap'
    * The function `pan' is applied to two arguments,
      but its type `Pattern Double -> Pattern ControlMap' has only one
      In the second argument of `(#)', namely `pan saw d1'
      In the expression: sound "bd cp sn:2 mt*2" # pan saw d1

But I can run the lines individually when separated by a blank line. Are you clicking on the console when the error comes up? If so, have you tried clicking back in the main text box?

[KonVas]

Are you clicking on the console when the error comes up? If so, have you tried clicking back in the main text box?

It literally freezes, allowing no interaction, clicking, editing and whatnot. So I don't know how much more information I can give from it since it doesn't do anything after hanging. Terminal seems to be pretty agnostic of it providing no feedback at all.

[Qirky]

Hmm, ok. So just to confirm the order of things:

• You press Cmd+Enter and the code (two identical lines) runs a first time and prints output to the console at the bottom of the interface.
• You press Cmd+Enter again: does the line flash? Do you get the the expected response (or any) in the console at the bottom of the interface?

Does it only happen after you get an error in Tidal? Could you try causing a syntax error then running another line of code? I have a suspicion it might be to do with how Mac OS handles the stderr output of processes but unfortunately I'm unable to test this