The value 0 is not of type sequence

[Slobodan Milnović]

Hi,

Either I'm doing something wrong, or there are some issues with latest
weblocks and sbcl. I've tried with weblocks-demo, and I'm getting the
same result as with my app.

The error is "The value 0 is not of type sequence" and it seems to be
related with the mark-dirty that runs at the initial access of the web
page. I've tried (trace weblocks:mark-dirty), but when I do that,
everything works. It seems that tracing mark-dirty "removes" the
problem. But as soon as I (untrace weblocks:mark-dirty) the issue is
back. I've come accross this situation before, where debug mode of an
compiler "does the magic" and allows an piece of code to run which
doesn't in "production" mode.

I'm using clbuild with the latest weblocks-dev and all of the
dependency libraries, and sbcl 1.0.46.13, all of them updated today.
All of the release versions after sbcl 1.0.43 report the same error,
I've downloaded them from the official site, compiled and tried with
both weblocks-demo and my app.

1.0.43 works for me, so I've managed to "mitigate" the issue for now,
but I'm not sure how to proceed. Can anyone else confirm this issue,
or is it something with my setup?

[Scott L. Burson]

2011/2/25 Slobodan Milnović <slobodan...@gmail.com>:

> Hi,
>
> Either I'm doing something wrong, or there are some issues with latest
> weblocks and sbcl. I've tried with weblocks-demo, and I'm getting the
> same result as with my app.
>
> The error is "The value 0 is not of type sequence" and it seems to be
> related with the mark-dirty that runs at the initial access of the web
> page. I've tried (trace weblocks:mark-dirty), but when I do that,
> everything works.
>

> I'm using clbuild with the latest weblocks-dev and all of the
> dependency libraries, and sbcl 1.0.46.13, all of them updated today.
> All of the release versions after sbcl 1.0.43 report the same error,
> I've downloaded them from the official site, compiled and tried with
> both weblocks-demo and my app.

That's a strange enough collection of symptoms that I think you should
give the SBCL maintainers a heads-up about an apparent bug. (An error
that goes away when you trace?? Pretty weird.) Then I suggest asking
them for read access to their repo, and seeing if you can find the
exact commit that introduces the problem. That should be a sufficient
clue to figure out what is going on.

I'm using 1.0.45 with my app, but I haven't updated weblocks in a
while. Also I'm using quicklisp rather than clbuild.

-- Scott

[Huw]

On Feb 26, 2:39 am, "Scott L. Burson" <Sc...@ergy.com> wrote:
> 2011/2/25 Slobodan Milnović <slobodan.milno...@gmail.com>:

I have the same issue with:

Hunchentoot 1.1.1 (SBCL 1.0.46)

The SBCL binary is Mach-O 64-bit executable x86_64, installed with
macports on a macbook.

weblocks installed from quicklisp:

#<SYSTEM weblocks / weblocks-20110219-hg / quicklisp 2011-02-19>
#<SYSTEM weblocks-demo / weblocks-20110219-hg / quicklisp
2011-02-19> ...

Huw

[Slobodan Milnović]

On Sat, Feb 26, 2011 at 20:20, Huw <huw.sof...@gmail.com> wrote:
> I have the same issue with:
>
> Hunchentoot 1.1.1 (SBCL 1.0.46)
>
> The SBCL binary is Mach-O 64-bit executable x86_64, installed with
> macports on a macbook.
>
> weblocks installed from quicklisp:
>
> #<SYSTEM weblocks / weblocks-20110219-hg / quicklisp 2011-02-19>
> #<SYSTEM weblocks-demo / weblocks-20110219-hg / quicklisp
> 2011-02-19> ...

It has been fixed now, the problem was in sbcl. It works in x86_64
linux, I think it should on Mac too. Get the latest sbcl from the
devel tree, current is 1.0.46.17 and try it out.

[Leslie P. Polzer]

Slobodan Milnović wrote:

> It has been fixed now, the problem was in sbcl. It works in x86_64
> linux, I think it should on Mac too. Get the latest sbcl from the
> devel tree, current is 1.0.46.17 and try it out.

Thanks for taking care of this!

Leslie