libera/#commonlisp - IRC Chatlog

21:15:55 skin With regard to https://edicl.github.io/hunchentoot/#conditions ?

21:19:36 Kingsy skin: I have looked over this a few times, but it still doesnt really answer my question. for example. I want to return JSON objects not templates. I also want to be able to specify the object that is returned based on the condition that is raised. I don't see how that is done with the items listed here.

21:22:15 Kingsy the docs are vague. I can see there is a hunchentoot-error class but there is absoutely no information on how it works. What can be overriden and how? etc etc.

21:43:48 Bubblegumdrop Kingsy if you want to return json you may need to set the content type or something, caveman has this

21:44:08 Bubblegumdrop https://github.com/fukamachi/caveman/blob/master/v2/skeleton/src/view.lisp#L33

21:44:24 Bubblegumdrop hunchentoot-error is the base class and you can make your own conditions like so"

21:44:30 Bubblegumdrop (define-condition my-condition (hunchentoot-condition) ...)

21:44:32 Bubblegumdrop I believe.

21:44:59 Bubblegumdrop (hunchentoot:define-easy-handler (say-yo :uri "/yo") (name) (setf (hunchentoot:content-type*) "text/plain") (format nil "Hey~@[ ~A~]!" name))

21:45:02 Bubblegumdrop This is in the docs.

21:45:11 Bubblegumdrop (setf (hunchentoot:content-type*) "application/json")

21:45:15 Bubblegumdrop Should get you what you want.

21:46:44 Bubblegumdrop Kingsy I struggled with the condition system at first too, it's not specific to hunchentoot although hunchentoot may hook into it specifically

21:46:48 Kingsy no I understand that. but its more core than that.

21:46:54 Bubblegumdrop https://lispcookbook.github.io/cl-cookbook/error_handling.html

21:47:09 Bubblegumdrop Yeah you were trying to do something like "catch the error and return json if so"

21:47:18 Kingsy if something goes wrong, in general, it returns an error template for the 500.. I want to change that. so it never returns HTML. ever

21:47:23 Bubblegumdrop If you're able to explain what you want/are trying to acheive in english it's helpful as well

21:47:30 Bubblegumdrop Yes that can be done

21:47:48 Bubblegumdrop I will get back to you if I figure out.

21:48:14 Bubblegumdrop (I did this using caveman

21:48:15 Bubblegumdrop )

21:48:21 Kingsy so lets start with the simple example. I want to. catch ANY error that is thrown during the execution of a route, and return a custom json object, set the content type as you showed. but also log the stack trace to the repl

21:48:23 Bubblegumdrop well, caveman just uses hunchentoot underneath

21:48:26 Bubblegumdrop or woo

21:48:28 Bubblegumdrop or whatever honestly

21:48:45 Kingsy yeah this is just a learning exercise. I know there are things out there that would make this a lot easier

21:48:47 Bubblegumdrop mm yeah so you'll have to wrap all that in a progn if you're using your lambda thingy with ,@body

21:48:56 Bubblegumdrop if you want to evaluate more than one form you should use progn

21:49:06 Bubblegumdrop clhs progn

21:49:07 specbot http://www.lispworks.com/reference/HyperSpec/Body/s_progn.htm

21:49:35 Bubblegumdrop You should be able to just add (log-whatever ..) in the progn and it should just work

21:49:46 Bubblegumdrop However there may be things like the default stream isn't *standard-output*

21:49:50 Bubblegumdrop I will have to look and see.

21:51:01 Bubblegumdrop give me a moment, I'm preparing dinner. chicken and eggplant parm :)

21:51:11 Kingsy Bubblegumdrop: no I got that working. but it meant it stopped logging to REPL, which didnt help. it meant I didnt know what was going on

21:51:39 Kingsy it also got me thinking about what happens when it is deployed. we probably want different error handling based on production and not. so I was just looking for general advice.

21:51:57 Kingsy oh of course, take your time

21:53:05 Bubblegumdrop Kingsy I actually ended up using Shinmera's VERBOSE library because it's so amazing and versatile. This is what I followed to integrate it into my multithreaded web app: https://www.darkchestnut.com/2021/set-up-verbose-multi-threaded-standalone-applications/

21:54:04 Bubblegumdrop https://git.lain.church/Bubblegumdrop/cl-deck-builder2/src/branch/master/src/main.lisp#L90

21:55:46 Kingsy no this is fune, but it doesnt answer the hunchentoot question. I don't know how to properly catch and return different custom objects based on conditions whilst controlling the REPL. the way I am doing it right now feels wrong

21:56:24 Bubblegumdrop there is a section on logging http://edicl.github.io/hunchentoot/#logging

21:58:32 Bubblegumdrop it looks like by default things go to *standard-error*

21:58:53 Bubblegumdrop I've never used *standard-error* lol

21:59:05 Kingsy I'll just try and play with it. thanks for the info!

21:59:15 Bubblegumdrop Derived acceptor classes can implement methods for the ACCEPTOR-LOG-MESSAGE and ACCEPTOR-LOG-ACCESS generic functions

21:59:36 Bubblegumdrop So I think what you'll want to do is have your own acceptor class that subclasses ACCEPETOR: (defclass my-acceptor (hunchentoot:acceptor) ...)

21:59:45 Bubblegumdrop Then pass that to the thingy instead of the default acceptor or whatever you're using now.

22:00:09 Bubblegumdrop You'll want to specialize on ACCEPTOR-LOG-MESSAGE and etc for that class like so: (defmethod acceptor-log-message :after ((obj my-acceptor) ..) ..)

22:00:17 Bubblegumdrop I think.

22:01:47 Bubblegumdrop You can do things like open a log file and save it with defparameter or defvar, (defparameter *my-log-file* (open ...))

22:01:59 Bubblegumdrop I think you should be able to output to the repl like this as well

22:02:23 Bubblegumdrop I'm not sure if hunchentoot uses threads, but threads make this a whole lot more fun.

22:03:58 Bubblegumdrop and by that I mean, *standard-output* of your REPL is *not* *standard-output* of the thread hunchentoot is executing on

22:07:52 Bubblegumdrop verbose handles all of that transparently

22:15:32 Kingsy well I wrote a simple logger and just outputs with format. so I am going to try and use that. will see how it goes.

22:15:53 Kingsy interesting thoughts around threads. I don't know if thats needed yet

22:16:11 Bubblegumdrop GL!

22:16:24 Bubblegumdrop perhaps look for other applications making use of hunchentoot

22:16:31 Bubblegumdrop I don't know any off the top of my head,

22:16:40 Bubblegumdrop https://gitlab.com/myopenbookstore/openbookstore/ I learned a lot from this repository

22:16:54 Kingsy oh ool

22:16:56 Kingsy cool

22:17:06 Bubblegumdrop https://gitlab.com/myopenbookstore/openbookstore/-/blob/master/run.lisp?ref_type=heads

22:17:37 Bubblegumdrop https://gitlab.com/myopenbookstore/openbookstore/-/blob/master/src/web/web.lisp?ref_type=heads#L29

22:18:28 Bubblegumdrop If you find any other programs using hunchentoot I'm interested in knowing more as well. I primarily use woo.

22:18:47 Bubblegumdrop I'm actually not sure what the differences between clack/lack/hunchentoot/woo/etc are

22:19:03 Bubblegumdrop like superficially I understand they're different projects with different goals

0:25:06 paulapatience Shinmera: It is perfectly harmless, but I assume the asterisk is de trop here: https://github.com/Shirakumo/trial/blob/b5e95f859e82faac2db4eb6eba5be26dd1ec80c9/asset.lisp#L48

2:24:26 Bubblegumdrop paulapatience I'm not certain but I think that's an idiom, like LIST and LIST*

2:24:29 Bubblegumdrop clhs list*

2:24:29 specbot http://www.lispworks.com/reference/HyperSpec/Body/f_list_.htm

2:25:02 Bubblegumdrop In this case it does appear to be a typo, though

2:25:09 Bubblegumdrop https://github.com/Shirakumo/trial/blob/b5e95f859e82faac2db4eb6eba5be26dd1ec80c9/asset.lisp#L128

2:25:14 Bubblegumdrop Further down

2:25:42 paulapatience Indeed, I checked that

2:44:37 holycow interesting: https://www.youtube.com/watch?v=fytGL8vzGeQ

2:45:35 holycow that video points to a direction in which lisp programmers might look to find full time positions

2:46:03 holycow it could get interesting, nano tech is coming soon and it will merge with the the LLM stuff happening now

2:53:48 Bubblegumdrop It's Cando? https://github.com/cando-developers/cando

2:54:19 Bubblegumdrop It seems to be associated with Clasp as well

2:54:44 Bubblegumdrop interesting, clasp uses llvm to interop with C++ code

2:55:26 Bubblegumdrop thanks for the linkn holycow

2:55:32 holycow no probs at all

2:55:38 holycow just ran into it my self

2:55:55 holycow this is obviously the next big thing for the next 20 years imho

2:56:09 holycow <-- not associated with this in any way, just adding my opinion here

3:06:53 Bubblegumdrop Clasp appears to be its own implementation of lisp?

3:07:04 Bubblegumdrop Clasp is an implementation of Common Lisp primarily designed for compatibility with C++-language programs and libraries.

3:07:08 Bubblegumdrop interesting.

3:07:32 Bubblegumdrop Oh, theyre in #clasp

3:07:45 Bubblegumdrop oh, drmeister_ appears to be here.

3:07:47 Bubblegumdrop very cool.

3:07:53 holycow oh!

3:07:56 holycow is that who it is?

3:07:58 Bubblegumdrop indeed.

3:08:00 holycow haha!

3:08:22 Bubblegumdrop This is probably the coolest chat I've ever been on. Y'all are brilliant.

3:08:33 drmeister_ Hello

3:08:52 holycow hi!

3:09:03 holycow drmeister_: enjoying watching that video on many levels

3:09:21 holycow especially watching you desribe the beginning of a new industry

3:09:25 drmeister_ Thank you.

3:11:44 drmeister_ I don't have much to say at the moment. I'm working on a proposal.

3:12:28 holycow no probs. if you are open for questions i may have some over the next few weeks

3:15:53 Bubblegumdrop Hah, watching this video is a kick. You went from Smalltalk to lisp. I'm doing the opposite! This is so cool. Thanks for all your hard work drmeister_.

3:16:52 drmeister_ Sure.

3:17:02 drmeister_ We have a new website going live in a week or so.

3:17:45 holycow schafmesitergroup.com?

3:20:48 drmeister_ No, my company.

3:21:02 holycow link?

3:21:23 Bubblegumdrop oh, #ecl is on here too, sweet

3:21:27 drmeister_ Not yet. It's password protected for the time being.

3:21:53 holycow no probs. i don't know what the rules are here but maybe announce it here and on reddit?

3:23:43 bjorkintosh ... and the orange site. Tradition.

3:23:54 drmeister_ It will be here... https://thirdlawtx.com/

3:24:09 drmeister_ "orange site"?

3:24:12 holycow lol @ ornage site. i started to see people call it that recently

3:24:15 holycow hacker news

3:24:52 holycow aha! bookmarked the url drmeister_ thx.

3:25:16 drmeister_ These aren't quite the best audience for our tech.

3:25:36 hayley drmeister_: Did you outgrow thirdlaw.tech?

3:25:39 bjorkintosh they'll find it highly entertaining though :-)

3:27:38 hayley Bubblegumdrop: To misquote Steele, I am now trying to take Lisp programmers halfway to Newspeak.

3:28:00 Bubblegumdrop Lisptalk?

3:28:09 Bubblegumdrop My parents sent me to speech therapy because I talked with a lisp :P

3:28:51 bjorkintosh why didn't they give you ()s instead?

3:29:26 Bubblegumdrop they were BASIC.

3:29:49 bjorkintosh Parens! they mean well.

3:29:51 hayley Bubblegumdrop: Gilad Bracha in turn took Smalltalk programmers halfway to BETA and E.

3:30:10 Bubblegumdrop hm, where do I know that name from

3:30:29 Bubblegumdrop oh, literally.

3:30:52 Bubblegumdrop Totally off topic for this channel. I've been studying Smalltalk. Currently looking at GT and Pharo.

3:31:10 hayley Smalltalk comes up frequently enough in #lispcafe, much to the dismay of gilberth.

4:14:22 beach Why is that a problem for him?

4:18:14 hayley He doesn't like Smalltalk very much.

4:26:55 beach I see.

4:53:10 aeth you'd think that smalltalk would make sense in a café

4:55:52 bjorkintosh aeth, it does: https://www.helloamsterdam.nl/guide/extra/small-talk/

6:50:20 flip214 ** NICK flip768