http://raw.githubusercontent.com issues SOLVED
Set ?forcerefresh=true in the URL.
Loading an entire workspace from http://raw.githubusercontent.com is currently causing severe lack of functionality in Chilipeppr.
Now, the problem appears to stem from Github, as using services like rawgit or hosting the “auto-generated-workspace.html” file locally fix the problem with their obvious security and efficiency drawbacks. Here’s the links that will be of interest:
Chilipeppr boot script: https://gist.github.com/PyroAVR/94c950ff62ec4ace1905
@jlauer I haven’t been able to crack this one. I can confirm that his boot code is entirely from the readme.MD, and using rawgit to host the raw github url does load the workspace without issue. He also substituted the rawgit url “preview” url into the boot script and everything loaded in CP.
John - Andy’s workspace was originally forked from github workspace-tinyg which is what chilipeppr/tinygStaging uses. So in a sense he’s already what you suggested.
Remember, CP caches everything and only refreshes if you force it to. This is so you can have 100% uptime regardless of all backing hosting sites like github.
There were enough issues in the past where any downtime was unacceptable, so I had to put that cache in place. It works brilliantly, but the downside is you have to know about it if you do development. Maybe we should add a comment in that auto-generated boot script.
I saw a 3-dimensional touch plate on someone’s machine that was using Mach3. The idea was that it works like a carpenter’s square, it lines up with the corner of the workpiece, and then the machine touches off in x, y, and z to set its zero there, therefore making zeroes repeatable in all axes automatically. I’m nearly finished with it aside from the formatting, but I can’t seem to force the run function to wait until it receives a response from SPJS before sending the next command. I have some restructuring to do on that one.
I assume you can’t just send a bunch of the probe commands in a row and then read the responses asynchronously? Do you need to run one axis, then read results, then send probe for next axis? If so you’ll have to just do callbacks. Watch the onRecv and then call the appropriate callback when you see the result you are waiting for.