freenode/#clasp - IRC Chatlog
Search
16:41:42
attila_lendvai
drmeister: I pushed a half-assed solution that sets LANG for the scraper, but it should be done globally for all external commands. but for now I couldn't figure out how...
16:52:53
attila_lendvai
Bike: I've seen something like that while transitioning from git submodules to the new setup
16:55:19
attila_lendvai
it will still happen when you switch to a branch/state where submodules existed... maybe you're on master?
17:31:08
drmeister
frgo: Hi - I had it build twice last night - once just the 'dev' branch of clasp and again within cando.
17:31:33
drmeister
If it's failing with a compile error on that 'set4' method - then something is different with your environment and mine.
17:32:26
drmeister
It turned out to be a change in one of the .pmp files - to have it use the 7th argument as a list of all arguments rather than a 7th argument.
17:33:48
shiho
drmeister: Build failed again. Should I pull the most recent clasp?? Now my clasp is behind by 4 commits.
17:33:54
frgo
Ok - will take a moment here to get to the point where I can see if it's me or something other ...
18:36:52
attila_lendvai
sorry, still busy. can you reset --hard it out locally, or just delete the error from scrape.lisp? I'll get to it soon
18:49:35
Bike
attila_lendvai: so what exactly happened with this? apparently the scraper fails on non-ascii sources now
18:56:04
drmeister
attila_lendvai: I disabled the LANG check in the scraper. Then I ran the scraper and it failed everytime it hit a source file with unicode. I then converted the unicode characters to regular characters (6 files or so) until the scraper ran on everything.
18:57:10
attila_lendvai
the problem was that LANG was whatever was on the host, and sbcl (scraper) runs with that
18:57:39
drmeister
Changes to the build system always lead to unintended and unpredictable consequences. This is why it makes me very, very anxious when changes are made.
18:58:12
drmeister
We need to improve the build system - I'm in total agreement. But it makes me anxious.
18:58:14
attila_lendvai
in my branch I've already added this to the wscript file: os.environ['LANG'] = "en_US.utf8"
18:59:06
attila_lendvai
stassats: it's done by the wscript file -- except it wasn't on their machines for some reason
18:59:49
Bike
it was done. you saw the error, $LANG was en_US.utf8 but sbcl's default external format was :us-ascii
19:03:11
attila_lendvai
stassats: someone adds a new with-open-file to the scraper, or whatever else is exec'd from the build for that matter, and forgets the keyword arg
19:03:56
drmeister
Warning: Setting locale failed. Check the following variables for correct values: LANG=en_US.utf8
19:05:36
attila_lendvai
the problem is I assumed that you can just set LANG, but apparently you need to jump more hoops on linux (need to compile the locale by hand, but we shouldn't go there)
19:32:56
attila_lendvai
drmeister: so, do you want to keep the source code non-utf-8 in the long run? shall I go on with that assumption? (I would go with utf-8, but I don't have a dog in that fight)
19:45:31
attila_lendvai
...and sorry for breaking the build and then being away, I dislike that myself.
20:14:17
shiho
drmeister: I got the error. Build aborted. Received condition of type: LAMBDA-LIST-KEYWORD-NOT-ALLOWED
20:57:03
attila_lendvai
ACTION wonders if there was a reason to switch mps to the clasp-developers repo from its upstream
21:03:38
shiho
drmeister: I got another error. In switch_add_argument_mode ../../src/core/lambdaListHandler.cc line 798
21:16:01
attila_lendvai
git reset --mixed doesn't do what we want... :/ I've fixed it in the build-cleanup branch
21:36:38
drmeister
Yeah - I think we just hit a problem with git. The sicl repo was kind of messed up.
21:43:02
attila_lendvai
Bike: it was, but that erased some local changes for drmeister. I recorded a change for --merge, that seems to do what we want, but I'm still testing.
21:44:25
attila_lendvai
drmeister: let me know if I should push that into dev. it's only moderately tested. alternatively, you can test it locally by editing fetch-git-repos.sh to use git reset --merge
21:45:36
drmeister
Let's hold off for now - I have a demo to give on Tuesday and we need to stabilize things.
21:56:50
drmeister
Kevslinger: Re: cytoscape-jupyter - after we installed webpack on your system. Did you try 'make'?
21:58:04
Kevslinger
Yes, I got a permission denied error from some part of python. So I tried ‘sudo make’ and got a few operation denied or operation failed errors
22:12:52
drmeister
Kevslinger: Have you been able to get the cytoscape-jupyter thing to display anything?
22:14:22
Kevslinger
I’m on mobile and not at my computer at the moment. Once I get back, I’ll check the error I got.
22:18:05
shiho
drmeister: I got the error.... Too many heap sections: Increase MAXHINCR or MAX_HEAP_SECTS
0:06:28
Kevslinger
As soon as this gets figured out and we can get the python to work to see what JSON messages the graph is sending, this should be easy..
1:23:49
drmeister
cytoscape-jupyter was put online about a year ago - since then there have been three (3!) major revisions of 'webpack'. Cytoscape-jupyter needs webpack version 1.12.14. Once I evaluated the commands I just pasted in the bash shell I was able to run 'make' in cytoscape-jupyter and it got a lot further.
1:38:07
drmeister
After installing webpack@1.12.14 (and maybe uninstalling the other webpack first) I ran 'make' again in jupyter-cytoscape and then the demo started up.
1:39:52
drmeister
The 'make' starts up jupyterlab on my machine and the widget doesn't work. But when I backup to the jupyter file browser...
1:41:09
drmeister
and start the smallNetwork.ipynb and then shift-click through the entire notebook - then the demo works.
1:45:12
Kevslinger
This is splendid. Once we figure out how the Python packages the JSON, all we need to do is mimic it
1:51:01
stassats
clasp itself has multiple compilers, interpreters, garbage collectors, and requires another lisp implementation to build