Some bug. I think it may be in routes

24 views
Skip to first unread message

Александр Бокарев

unread,
Jan 18, 2014, 10:21:38 PM1/18/14
to res...@googlegroups.com
I really do not know, is it fixed?
I've added many routes like:

(restas:define-route name1 ("/name1:(id)")
  (:requirement #'admin-user-p) ;where admin-user-p is to (compute-user-login-name) and check rights in DB
  (functions here))

(restas:define-route name2 ("/name2:(id)")
  (:requirement #'admin-user-p) ;where admin-user-p is to (compute-user-login-name) and check rights in DB
  (functions here))

(restas:define-route name3 ("/name3:(id)")
  (:requirement #'admin-user-p) ;where admin-user-p is to (compute-user-login-name) and check rights in DB
  (functions here))

All was fine untill:

(restas:define-route name9000 ("/name9000:(id)") ; Where 9000 is some last number in this list of routes
  (:requirement #'admin-user-p)
  (functions here))

Compiling name9000 give me error, that:
The value #<ROUTES:OR-TEMPLATE #{VALUE}> is not of type LIST.

#{VALUE} is something about name8998 and name8999. I mean LAST route with error -1 and LAST -2

recompiling any other route give this error for name8998 and name8999

OK. Stopping SBCL (ubuntu 12.04). Erasing name9000 from source.

Start SBCL, (ql:quickload "my-system") - all is fine again.

Then again.


(restas:define-route name9000 ("/name9000:(id)") ; Where 9000 is some last number in this list of routes
  (:requirement #'admin-user-p)
  (functions here))

Compiling name9000 give me error, that:
The value #<ROUTES:OR-TEMPLATE #{VALUE}> is not of type LIST.

Stopping again, reboot ubuntu, and defining like this:

(restas:define-route name9000 ("/test/name9000:(id)")
  (:requirement #'admin-user-p)
  (functions here))

gives NO error :)

Orivej Desh

unread,
Jan 19, 2014, 5:04:29 AM1/19/14
to res...@googlegroups.com
Would you post a call trace with the error?
  1. Delete route 9000 from source.
  2. (ql:quickload "my-system")
  3. (trace "ROUTES" "RESTAS")
  4. Eval define-route name9000 alone to trigger the error.
Reply all
Reply to author
Forward
0 new messages