I recently made several changes and additions to my connections on
hep.fettig.net and I'm having several problems now that make me think
that my configuration got corrupted somehow.
Most of my connections are missing, and the one or two that are there
keep coming back when I try to delete them. Also, I cannot re-import
an opml file that I exported from hep a few weeks ago. It looks like
the import works, but when I look at the list of connections it
appears unchanged. I have even tried to delete the "Connections"
resource entirely and I get a "not implemented" error with a very
pretty stack trace in HTML. An edit/save attempt on the "Connections"
resource simply hangs.
Any ideas how to fix? I think what may have caused the corruption in
the first place was an RSS feed that had a "#" in its title. Nothing
seemed to work very well after I added that. Feel free to purge my
account and start over if that would be easiest.
> I recently made several changes and additions to my connections on
> hep.fettig.net and I'm having several problems now that make me think
> that my configuration got corrupted somehow.
> Most of my connections are missing, and the one or two that are there
> keep coming back when I try to delete them. Also, I cannot re-import
> an opml file that I exported from hep a few weeks ago. It looks like
> the import works, but when I look at the list of connections it
> appears unchanged. I have even tried to delete the "Connections"
> resource entirely and I get a "not implemented" error with a very
> pretty stack trace in HTML. An edit/save attempt on the "Connections"
> resource simply hangs.
Your data wasn't corrupted on disk, but somehow Hep became confused about the state of your connections. I'll have to spend some time looking through the logs to try and figure out what happened. It's definitely a bug though - thanks for the report.
For now, I just restarted the server, which made it reload your connections from disk, and they seem to be back now. Take a look and see if there's anything missing.
> Any ideas how to fix? I think what may have caused the corruption in
> the first place was an RSS feed that had a "#" in its title. Nothing
> seemed to work very well after I added that. Feel free to purge my
> account and start over if that would be easiest.
On Thu, 28 Oct 2004 17:26:26 -0400, Abe Fettig <a...@fettig.net> wrote:
> For now, I just restarted the server, which made it reload your
> connections from disk, and they seem to be back now. Take a look and
> see if there's anything missing.
Looks good now. Thanks!
Oops... spoke too soon. The connections are all confused again. I
did two things which may have triggered the relapse:
(1) I tried viewing messages in #blah RSS feed via the web interface,
(which didn't work) and then
(2) I tried connecting via Mail.app (using IMAP) and I got the same
confused short list I now see via the web interface
Unfortunately, I didn't re-check the connection list before Mail.app
re-synchronized, so I don't know which action to blame. Is there any
way for me to reset this myself without forcing a restart of the
server?
> > Any ideas how to fix? I think what may have caused the corruption in
> > the first place was an RSS feed that had a "#" in its title. Nothing
> > seemed to work very well after I added that. Feel free to purge my
> > account and start over if that would be easiest.
> Do you see that feed in your connections now?
That feed was there, (as I indicated above) but it disappeared again
along with most of my other connections.
If you restart again I will try removing the #blah feed and see if the
problem goes away.
Matt Huyck wrote:
> Oops... spoke too soon. The connections are all confused again. I
> did two things which may have triggered the relapse:
> (1) I tried viewing messages in #blah RSS feed via the web interface,
> (which didn't work) and then
> (2) I tried connecting via Mail.app (using IMAP) and I got the same
> confused short list I now see via the web interface
> Unfortunately, I didn't re-check the connection list before Mail.app
> re-synchronized, so I don't know which action to blame.
OK, I definitely want to fix this ASAP. Let me see if I can come up with a permanent solution this morning. If I can't, I'll manually remove that feed and restart the server.
On Fri, 29 Oct 2004 07:38:26 -0400, Abe Fettig <a...@fettig.net> wrote:
> OK, I definitely want to fix this ASAP. Let me see if I can come up
> with a permanent solution this morning. If I can't, I'll manually
> remove that feed and restart the server.
I've verified this as a bug in Hep - adding a connection to the
#tvtorrents feed makes most of your feeds disappear until the server
is restarted. I believe this problem has to do with the '#'
character, although I haven't figured out exactly why yet.
For now, I've manually edited your connections list and taken out the
# - it seems to be working now.
I'll let you know once I have a permanent fix in place.
On Fri, 29 Oct 2004 16:12:31 -0400, Abe Fettig <abefet...@gmail.com> wrote:
> I've verified this as a bug in Hep - adding a connection to the
> #tvtorrents feed makes most of your feeds disappear until the server
> is restarted. I believe this problem has to do with the '#'
> character, although I haven't figured out exactly why yet.
> For now, I've manually edited your connections list and taken out the
> # - it seems to be working now.
> I'll let you know once I have a permanent fix in place.
OK, I believe I've fixed this problem. Hep should now gracefully
handle feeds with # in the title (as well as slashes and other
characters that aren't allowed in URL paths).
|
