freenode/#clasp - IRC Chatlog
Search
2:04:36
drmeister
I can launch a thread that updates widgets in the notebook asynchronously while the notebook continues to respond to input.
2:07:14
drmeister
It creates a widget, displays the widget and then launches a thread that has a jupyter notebook cell dynamic environment and can update widgets.
2:08:50
stassats
ok, because often when i ask "why is it written that way" it turns out to be some limitation
2:15:08
drmeister
Well, the key point is I can set up complex dashboard of jupyter widgets and have them updated asynchronously from a thread that watches a bunch of processes, directories and files to monitor their progress.
2:15:44
drmeister
I just didn't like the idea of evaluating a jupyter notebook cell and having it go off into la la land for hours and days.
2:16:52
drmeister
I'm still mulling over approaches of how to develop an "application" in a Jupyter notebook.
5:11:39
drmeister
beach: What is the cleavir instruction that you were going to add to enable debugging across threads?
5:12:14
drmeister
Bike and I were talking about it today and we couldn't recall what you were going to call it.
5:13:37
drmeister
Hmmm. I was describing to Bike my musings about an instruction that would check the status of a flag and if it was set would unwind the stack.
5:14:10
drmeister
Something that would be inserted at the bottoms of loops and at the ends of functions to check for signals and do something if a signal was received.
5:14:25
drmeister
He thought it sounded like this facility that you were thinking of adding for debugging.
5:19:05
drmeister
What I'm looking for is something that will occasionally check if a unix signal occurred.
5:20:36
drmeister
Ok. Is that something I can do at the Common Lisp level? Modifying the LOOP macro for instance?
5:22:25
beach
The definition of back arc is clear in the literature. No need to work with addresses.
5:23:46
drmeister
What about when leaving a function - stassats mentioned that as another place to put these.
5:28:48
beach
Then you also make sure that every back arc (and return, and ...) is such that your virtual machine is in a state that makes it capable to take Unix signals.
5:55:46
drmeister
I'm starting to rely on threads more - and I need to be able to shut them down reliably using unix signals.
5:56:23
drmeister
Unix signals are asynchronous and C++ exception handling is synchronous - there is no way to marry them other than to have safe points in the code.
13:42:08
drmeister
It got pushed back to April 3 - we had a huge storm here two days ago - that shut everything down the next morning.
13:43:16
attila_lendvai
drmeister: well, first take a look at least at the commit messages to see if it aligns with what you have in mind
13:44:32
attila_lendvai
as we agreed cst, and anything large, should be merged into dev, then i forward port the wscript related changes to my branch, and then it can go into dev
13:45:10
attila_lendvai
becase it's probably easier for me to forward port than to Bike and you to merge
13:46:10
attila_lendvai
ACTION hopes that there won't be large whitespace noise kinda changes in the wscripts...
13:47:32
attila_lendvai
Bike: yep, mostly just the wscripts. i don't know how much they are changed in cst. i remember seeing at least one change that will need to be addressed
13:48:15
Bike
well the long and short of it is cst won't be merged into dev for a while. it only builds with major slowdown.
13:48:33
Bike
i didn't think this would be important for your refactor, since your refactor isn't about lisp code at all- but i guess i missed a conversation