Your message dated Wed, 5 Jan 2011 13:48:42 -0300
with message-id <[email protected]>
and subject line Re: Bug#608809: twidge: it works again
has caused the Debian Bug report #608809,
regarding please provide more useful error messages in case of service failure
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
608809: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=608809
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: twidge
Version: 1.0.6
Severity: normal
Hi,
I have been using twidge for some time already, and it always worked ok with
identi.ca. Today, however, both lsrecent and lsreplies fail like this:
$ twidge -c .twidge-identica lsrecent
twidge: user error (Bad response: 0)
The contents of .twidge-identica, except my private oauthdata, is as follows:
------------------8<------------------------8<-------------------
$ grep -v oauthdata .twidge-identica
[DEFAULT]
oauthaccesstoken: %(serverbase)s/oauth/access_token
oauthauthorize: %(serverbase)s/oauth/authorize
oauthrequesttoken: %(serverbase)s/oauth/request_token
sendmail: /usr/sbin/sendmail
serverbase: https://identi.ca/api
shortenurls: yes
urlbase: %(serverbase)s
[lsrecent]
lastid: 61351772
[lsreplies]
lastid: 61308072
------------------8<------------------------8<-------------------
I tried to setup a fresh config file, and that also failed:
------------------8<------------------------8<-------------------
$ twidge -c twidge-identica setup
Welcome to twidge. We will now configure twidge for your
use with Twitter (or a similar service). This will be quick and easy!
Please wait a moment while I query the server...
twidge: user error (Error from oauthRequest: "")
terce...@morere:/tmp$ cat twidge-identica
[DEFAULT]
oauthaccesstoken: %(serverbase)s/oauth/access_token
oauthauthorize: %(serverbase)s/oauth/authorize
oauthrequesttoken: %(serverbase)s/oauth/request_token
sendmail: /usr/sbin/sendmail
serverbase: https://identi.ca
shortenurls: yes
urlbase: %(serverbase)s/api
------------------8<------------------------8<-------------------
Please let me know if there is any extra information I can provide to help
fixing this.
-- System Information:
Debian Release: 6.0
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core)
Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages twidge depends on:
ii curl 7.21.2-4 Get a file from an HTTP, HTTPS or
ii libc6 2.11.2-7 Embedded GNU C Library: Shared lib
ii libcurl3-gnutls 7.21.2-4 Multi-protocol file transfer libra
ii libffi5 3.0.9-3 Foreign Function Interface library
ii libgmp3c2 2:4.3.2+dfsg-1 Multiprecision arithmetic library
twidge recommends no packages.
twidge suggests no packages.
-- no debconf information
--
Antonio Terceiro <[email protected]>
http://softwarelivre.org/terceiro
signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
John Goerzen escreveu isso aí:
> On 01/05/2011 07:45 AM, Antonio Terceiro wrote:
> >retitle 608809 please provide more useful error messages in case of service
> >failure
> >severity 608809 wishlist
> >thanks
> >
> >Now it works again. So probably it was caused by a problem in identi.ca
> >and not in twidge.
> >
> >Nevertheless, maybe twidge could provide more useful error messages, so
> >that when things like this happens users can report/complain directly to
> >the service providers.
> >
>
> Hi Antonio,
>
> Thank you for the reports, both of them. These services, in my
> experience, don't provide error messages in a consistent way; for
> instance, sometimes they may be in the HTTP headers, sometimes in
> the response document. That is why there is the --debug option,
> which dumps the traffic between you and the remote and stands a good
> chance of showing you the error.
>
> Is that sufficient for your needs?
I think you are right. And I guess "Provide more useful error messages"
is not a very much precise request ... nevermind. If such problem
happens again I will try using --debug and filing a more useful bug
request. :)
Thank you,
--
Antonio Terceiro <[email protected]>
http://softwarelivre.org/terceiro
signature.asc
Description: Digital signature
--- End Message ---
