After a recent quicklisp update, suddenly update-dao throws syntax errors. Simplest example: (update-dao (get-dao 'topic 182)) throws the following error: Database error 42601: syntax error at or near "Border" QUERY: UPDATE topics SET name = Cross Border Transactions, comments = NULL, usergroup_id = 1, permission_id = 1, parenttopic_id = 0 WHERE (id = 182) [Condition of type CL-POSTGRES-ERROR:SYNTAX-ERROR-OR-ACCESS-VIOLATION] I haven't updated anything and having a hard time trying to figure out what is triggering the problem. Anyone else seeing this or just me? Any pointers would be appreciated. Sabra
is update-dao in postmodern broken? the strings are not being quoted Database error 42703: column "croatia" does not exist QUERY: (SELECT * FROM country WHERE (name = Croatia)) From the html quickstart (let ((croatia (get-dao 'country "Croatia"))) (setf (country-inhabitants croatia) 4500000) (update-dao croatia)) On Jan 22, 2014, at 4:33 PM, Sabra Crolleton <sabra.crolleton@gmail.com> wrote:
After a recent quicklisp update, suddenly update-dao throws syntax errors. Simplest example:
(update-dao (get-dao 'topic 182))
throws the following error:
Database error 42601: syntax error at or near "Border" QUERY: UPDATE topics SET name = Cross Border Transactions, comments = NULL, usergroup_id = 1, permission_id = 1, parenttopic_id = 0 WHERE (id = 182) [Condition of type CL-POSTGRES-ERROR:SYNTAX-ERROR-OR-ACCESS-VIOLATION]
I haven't updated anything and having a hard time trying to figure out what is triggering the problem. Anyone else seeing this or just me?
Any pointers would be appreciated.
Sabra
Yes, recently someone submitted a patch that broke a bunch of things. It has already been reverted in the git repository, but I guess quicklisp picked up the broken version (since it seems to assume that repositories are never broken). Update from git, I guess. On Thu, Jan 23, 2014 at 9:07 AM, Colin Carr <colinpcarr@gmail.com> wrote:
is update-dao in postmodern broken? the strings are not being quoted Database error 42703: column "croatia" does not exist QUERY: (SELECT * FROM country WHERE (name = Croatia)) From the html quickstart (let ((croatia (get-dao 'country "Croatia"))) (setf (country-inhabitants croatia) 4500000) (update-dao croatia))
On Jan 22, 2014, at 4:33 PM, Sabra Crolleton <sabra.crolleton@gmail.com> wrote:
After a recent quicklisp update, suddenly update-dao throws syntax errors. Simplest example:
(update-dao (get-dao 'topic 182))
throws the following error:
Database error 42601: syntax error at or near "Border" QUERY: UPDATE topics SET name = Cross Border Transactions, comments = NULL, usergroup_id = 1, permission_id = 1, parenttopic_id = 0 WHERE (id = 182) [Condition of type CL-POSTGRES-ERROR:SYNTAX-ERROR-OR-ACCESS-VIOLATION]
I haven't updated anything and having a hard time trying to figure out what is triggering the problem. Anyone else seeing this or just me?
Any pointers would be appreciated.
Sabra
Marijn Haverbeke <marijnh@gmail.com> writes:
Yes, recently someone submitted a patch that broke a bunch of things. It has already been reverted in the git repository, but I guess quicklisp picked up the broken version (since it seems to assume that repositories are never broken). Update from git, I guess.
I don't assume that repositories are never broken. I don't have a good system in place to do pre-release testing beyond "Does it build?" I'd like to do more thorough testing, but setting up the infrastructure for it takes time. The easiest short-term fix is something like: cd ~/quicklisp/local-projects git clone https://github.com/marijnh/Postmodern.git Another option is to go back to the previous dist via the instructions in http://blog.quicklisp.org/2011/08/going-back-in-dist-time.html. Sorry for the inconvenience. The fixed dist will be available in early February. Zach
On Thu, Jan 23, 2014 at 10:05:55AM -0500, Zach Beane wrote:
Marijn Haverbeke <marijnh@gmail.com> writes:
Yes, recently someone submitted a patch that broke a bunch of things. It has already been reverted in the git repository, but I guess quicklisp picked up the broken version (since it seems to assume that repositories are never broken). Update from git, I guess.
Urghs, I just created some (Debian) package building scripts that rely on Quicklisp (i.e. that install a temporsry quicklisp to build standalone binaries). The idea that quicklisp might deploy some arbitrary checkout makes me frown.
I don't assume that repositories are never broken. I don't have a good system in place to do pre-release testing beyond "Does it build?" I'd like to do more thorough testing, but setting up the infrastructure for it takes time.
It might be a good idea to offer the upstream programmers a way to provide a branch/tag to mark quicklisp ready versions of the code (I personally use git-flow and that has a branch named 'release'). Cheers, Ralf Mattes
Ralf Mattes <rm@seid-online.de> writes:
On Thu, Jan 23, 2014 at 10:05:55AM -0500, Zach Beane wrote:
Marijn Haverbeke <marijnh@gmail.com> writes:
Yes, recently someone submitted a patch that broke a bunch of things. It has already been reverted in the git repository, but I guess quicklisp picked up the broken version (since it seems to assume that repositories are never broken). Update from git, I guess.
Urghs, I just created some (Debian) package building scripts that rely on Quicklisp (i.e. that install a temporsry quicklisp to build standalone binaries). The idea that quicklisp might deploy some arbitrary checkout makes me frown.
It does use arbitrary checkouts for many projects. There are many useful projects for which that is the only way the software is made available. Most of the time it works ok, but sometimes it doesn't. I'd like to improve the situation, but it takes time.
I don't assume that repositories are never broken. I don't have a good system in place to do pre-release testing beyond "Does it build?" I'd like to do more thorough testing, but setting up the infrastructure for it takes time.
It might be a good idea to offer the upstream programmers a way to provide a branch/tag to mark quicklisp ready versions of the code (I personally use git-flow and that has a branch named 'release').
Not a lot of Quicklisp-provided projects follow this convention, but when they do, I try to use it. Zach
On Thu, Jan 23, 2014 at 11:22:53AM -0500, Zach Beane wrote:
It does use arbitrary checkouts for many projects. There are many useful projects for which that is the only way the software is made available.
Most of the time it works ok, but sometimes it doesn't. I'd like to improve the situation, but it takes time.
I see. So, is there a way to install a specific quicklisp dist? My buildscript currently uses the following: sbcl --non-interactive --no-userinit --load quicklisp.lisp --eval "(quicklisp-quickstart:install :path (merge-pathnames \"quicklisp/\" (directory-namestring (truename *default-pathname-defaults*))))" But this seems to fetch the current quicklisp dist. And, related: how long do you provide older versions of the dist? Thanks for all that work - by using quicklisp I was able to drop thew need to create Debian wrappers for 12 lisp packages. Cheers, RalfD
Ralf Mattes <rm@seid-online.de> writes:
On Thu, Jan 23, 2014 at 11:22:53AM -0500, Zach Beane wrote:
It does use arbitrary checkouts for many projects. There are many useful projects for which that is the only way the software is made available.
Most of the time it works ok, but sometimes it doesn't. I'd like to improve the situation, but it takes time.
I see. So, is there a way to install a specific quicklisp dist?
http://blog.quicklisp.org/2011/08/going-back-in-dist-time.html describes the current process. It can only be done after the initial install. As it happens, in the next day or two I am going to update the initial install process to make it easy to install a specific dist by URL during installation rather than afterwards. This will extend to the Quicklisp software itself (i.e. asdf and the code that fetches and loads library code). The goal is to make it easy to have a stable, reproducible Quicklisp configuration.
My buildscript currently uses the following:
sbcl --non-interactive --no-userinit --load quicklisp.lisp --eval "(quicklisp-quickstart:install :path (merge-pathnames \"quicklisp/\" (directory-namestring (truename *default-pathname-defaults*))))"
But this seems to fetch the current quicklisp dist. And, related: how long do you provide older versions of the dist?
I hope to provide them indefinitely. The cost for Amazon storage for Quicklisp is very low, currently around $5/month.
Thanks for all that work - by using quicklisp I was able to drop thew need to create Debian wrappers for 12 lisp packages.
Glad to hear it. (Further discussion should probably go to quicklisp@googlegroups.com instead.) Zach
Thank you sir! - C (Eos:run! :postmodern) .............................. Did 65 checks. Pass: 65 (100%) Skip: 0 ( 0%) Fail: 0 ( 0%) On Jan 23, 2014, at 10:05 AM, Zach Beane <xach@xach.com> wrote:
Marijn Haverbeke <marijnh@gmail.com> writes:
Yes, recently someone submitted a patch that broke a bunch of things. It has already been reverted in the git repository, but I guess quicklisp picked up the broken version (since it seems to assume that repositories are never broken). Update from git, I guess.
I don't assume that repositories are never broken. I don't have a good system in place to do pre-release testing beyond "Does it build?" I'd like to do more thorough testing, but setting up the infrastructure for it takes time.
The easiest short-term fix is something like:
cd ~/quicklisp/local-projects git clone https://github.com/marijnh/Postmodern.git
Another option is to go back to the previous dist via the instructions in http://blog.quicklisp.org/2011/08/going-back-in-dist-time.html.
Sorry for the inconvenience. The fixed dist will be available in early February.
Zach
Thank you for the confirmation. I thought I was losing my mind. Sabra On Thu, Jan 23, 2014 at 2:56 AM, Marijn Haverbeke <marijnh@gmail.com> wrote:
Yes, recently someone submitted a patch that broke a bunch of things. It has already been reverted in the git repository, but I guess quicklisp picked up the broken version (since it seems to assume that repositories are never broken). Update from git, I guess.
is update-dao in postmodern broken? the strings are not being quoted Database error 42703: column "croatia" does not exist QUERY: (SELECT * FROM country WHERE (name = Croatia)) From the html quickstart (let ((croatia (get-dao 'country "Croatia"))) (setf (country-inhabitants croatia) 4500000) (update-dao croatia))
On Jan 22, 2014, at 4:33 PM, Sabra Crolleton <sabra.crolleton@gmail.com> wrote:
After a recent quicklisp update, suddenly update-dao throws syntax errors. Simplest example:
(update-dao (get-dao 'topic 182))
throws the following error:
Database error 42601: syntax error at or near "Border" QUERY: UPDATE topics SET name = Cross Border Transactions, comments = NULL, usergroup_id = 1, permission_id = 1, parenttopic_id = 0 WHERE (id =
On Thu, Jan 23, 2014 at 9:07 AM, Colin Carr <colinpcarr@gmail.com> wrote: 182)
[Condition of type CL-POSTGRES-ERROR:SYNTAX-ERROR-OR-ACCESS-VIOLATION]
I haven't updated anything and having a hard time trying to figure out what is triggering the problem. Anyone else seeing this or just me?
Any pointers would be appreciated.
Sabra
participants (5)
-
Colin Carr -
Marijn Haverbeke -
Ralf Mattes -
Sabra Crolleton -
Zach Beane