|
List Info
Thread: Traceback
|
|
| Traceback |
|
2006-05-17 00:35:14 |
|
While testing the most recent docudo (rev 90) I got the following traceback when clicking on the "Title Index"; link:
Page handler: <bound method Root.default of <docudo.controllers.Root
object at 0x012ADA10>>
Traceback (most recent call last):
File "d:\python24\lib\site-packages\CherryPy-2.2.1-py2.4.egg\cherrypy\_cphttptools.py", line 105, in _run
self.main()
File "d:\python24\lib\site-packages\CherryPy-
2.2.1-py2.4.egg\cherrypy\_cphttptools.py", line 254, in main
body = page_handler(*virtual_path, **self.params)
File "<string>", line 3, in default
File "d:\python24\lib\site-packages\TurboGears-
0.9a5-py2.4.egg\turbogears\controllers.py", line 210, in expose
output = database.run_with_transaction(func._expose,func, accept, allow_json, allow_json_from_config,*args, **kw)
File "d:\python24\lib\site-packages\TurboGears-
0.9a5-py2.4.egg\turbogears\database.py", line 216, in run_with_transaction
retval = func(*args, **kw)
File "<string>", line 5, in _expose
File "d:\python24\lib\site-packages\TurboGears-
0.9a5-py2.4.egg\turbogears\controllers.py", line 230, in <lambda>
func._expose.when(rule)(lambda _func, accept, allow_json, allow_json_from_config,*args,**kw: _execute_func(
File "d:\python24\lib\site-packages\TurboGears-
0.9a5-py2.4.egg\turbogears\controllers.py", line 251, in _execute_func
output = errorhandling.try_call(func, *args, **kw)
File "d:\python24\lib\site-packages\TurboGears-0.9a5-py2.4.egg\turbogears\errorhandling.py
", line 71, in try_call
return func(self, *args, **kw)
File "E:\data\code\Docudo\trunk\Docudo\docudo\controllers.py";, line 131, in default
return self.pages(version,method,path)
File "<string>", line 3, in pages
File "d:\python24\lib\site-packages\TurboGears-0.9a5-py2.4.egg\turbogears\controllers.py", line 207, in expose
output = func._expose(func, accept, allow_json, allow_json_from_config, *args, **kw)
File "<string>", line 5, in _expose
File "d:\python24\lib\site-packages\TurboGears-0.9a5-py2.4.egg\turbogears\controllers.py", line 230, in <lambda>
func._expose.when(rule)(lambda _func, accept, allow_json, allow_json_from_config,*args,**kw: _execute_func(
File "d:\python24\lib\site-packages\TurboGears-0.9a5-py2.4.egg\turbogears\controllers.py", line 251, in _execute_func
output = errorhandling.try_call(func, *args, **kw)
File "d:\python24\lib\site-packages\TurboGears-
0.9a5-py2.4.egg\turbogears\errorhandling.py", line 71, in try_call
return func(self, *args, **kw)
File "E:\data\code\Docudo\trunk\Docudo\docudo\controllers.py";, line 191, in pages
media_list =
svnutils.media(version)
File "E:\data\code\Docudo\trunk\Docudo\docudo\svnutils.py", line 165, in media
return [os.path.basename(media['name']) for media in media_list(version)]
File "E:\data\code\Docudo\trunk\Docudo\docudo\svnutils.py", line 156, in media_list
for media in svn.ls(os.path.join(get_version_dir(version),'docudo.media')):
ClientError: 'docudo.collections/0.9/docudo.media' has no URL
This has to do with the fact that I'm using the same test repository from before Ronald added his media-handling code (so
docudo.media did not exist...it's fixed now), but I thought I'd put it on the list, since this type of error should probably be trapped and a more friendly msg printed.
Should we create an exception type for cases where the repository does not match what Docudo is expecting?
Kevin H.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Docudo" group.
To post to this group, send email to docudo googlegroups.com
To unsubscribe from this group, send email to docudo-unsubscribegooglegroups.com
For more options, visit this group at http://groups.google.com/group/docudo
-~----------~----~----~----~------~----~------~--~---
|
| Traceback |
|
2006-05-17 01:19:36 |
On 5/16/06, Kevin Horn <kevin.horngmail.com> wrote:
> ClientError: 'docudo.collections/0.9/docudo.media'
has no URL
>
>
> This has to do with the fact that I'm using the same
test repository from
> before Ronald added his media-handling code (so
docudo.media did not
> exist...it's fixed now), but I thought I'd put it on
the list, since this
> type of error should probably be trapped and a more
friendly msg printed.
>
> Should we create an exception type for cases where the
repository does not
> match what Docudo is expecting?
The error it gave seems reasonable sane to me. "has no
URL' may not be
the clearest wording, but it does specifically list the path
it's
trying to look up.
Kevin
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Docudo" group.
To post to this group, send email to docudogooglegroups.com
To unsubscribe from this group, send email to
docudo-unsubscribegooglegroups.com
For more options, visit this group at http://groups.g
oogle.com/group/docudo
-~----------~----~----~----~------~----~------~--~---
|
|
| Traceback |
|
2006-05-17 15:23:17 |
|
Maybe so, but it threw me for a loop initially, as I had no idea what "docudo.media" was supposed to be. It wasn't until I read back through the SVN log that it occurred to me that Ronald had added something to the collection "schema". In other words, I was at first quite confused about _why_ it was looking for that URL.
It just seems that this kind of thing is likely to come up in the future betweens versions, and it might be a good idea to plan for it in some way. I leave it to wiser heads (and people with more time!) to either figure out what the best plan would be, or tell me to shut up  .
Kevin H.
On 5/16/06, Kevin Dangoor <gmail.com">dangoorgmail.com> wrote:
On 5/16/06, Kevin Horn <gmail.com">kevin.horngmail.com> wrote:
>; ClientError: 'docudo.collections/0.9/docudo.media' has no URL
>
>
> This has to do with the fact that I'm using the same test repository from
> before Ronald added his media-handling code (so docudo.media did not
> exist...it's fixed now), but I thought I'd put it on the list, since this
> type of error should probably be trapped and a more friendly msg printed.
>
> Should we create an exception type for cases where the repository does not
> match what Docudo is expecting?
The error it gave seems reasonable sane to me. "has no URL' may not be
the clearest wording, but it does specifically list the path it's
trying to look up.
Kevin
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Docudo" group.
To post to this group, send email to docudogooglegroups.com
To unsubscribe from this group, send email to docudo-unsubscribegooglegroups.com
For more options, visit this group at http://groups.google.com/group/docudo
-~----------~----~----~----~------~----~------~--~---
|
| Traceback |
|
2006-05-17 18:53:13 |
On 5/17/06, Kevin Horn <kevin.horngmail.com> wrote:
> Maybe so, but it threw me for a loop initially, as I
had no idea what
> "docudo.media" was supposed to be. It
wasn't until I read back through the
> SVN log that it occurred to me that Ronald had added
something to the
> collection "schema". In other words, I was
at first quite confused about
> _why_ it was looking for that URL.
>
> It just seems that this kind of thing is likely to come
up in the future
> betweens versions, and it might be a good idea to plan
for it in some way.
> I leave it to wiser heads (and people with more time!)
to either figure out
> what the best plan would be, or tell me to shut up .
While I won't claim to be a wiser head (or even to have
more time),
the likely answer is migration scripts or at least upgrade
docs (which
is what we have for TurboGears). The advantage to being in a
pre-release state is that we don't have that responsibility
for
Docudo.
Kevin
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Docudo" group.
To post to this group, send email to docudogooglegroups.com
To unsubscribe from this group, send email to
docudo-unsubscribegooglegroups.com
For more options, visit this group at http://groups.g
oogle.com/group/docudo
-~----------~----~----~----~------~----~------~--~---
|
|
[1-4]
|
|