Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RSSReader breaks down on shortener's error #3

Open
mrshu opened this issue Jul 1, 2017 · 4 comments
Open

RSSReader breaks down on shortener's error #3

mrshu opened this issue Jul 1, 2017 · 4 comments

Comments

@mrshu
Copy link
Contributor

mrshu commented Jul 1, 2017

An important feature of RSSReader is sending the links in shortened form. This happens right before the link is sent https://github.com/errbotters/err-rssreader/blob/master/rssreader.py#L185

Sometimes, however, the shortener raises an exception. This is a pretty serious problem, as the cache never gets cleaned and the result is repeated sending of the same items over and over again.

Since we currently make use of just the is.gd shortener, fixing this should be as easy as handling the ShorteningErrorException correctly (just by returning from the function right away).

@mrshu
Copy link
Contributor Author

mrshu commented Jul 1, 2017

@Adman since you added the shortening in the first place (if I am not mistaken), does the plan outlined in the previous comment make sense to you? I'd like to know your perspective.

@Adman
Copy link
Member

Adman commented Jul 1, 2017

@mrshu I think you programmed whole plugin including shortening, didn't you? I just suggested adding some url shortener.

I strongly agree with fixing this bug the way you mentioned in first comment.
But what if this problem persists for a longer time and the bot will not be able to send any rss feed?

@mrshu
Copy link
Contributor Author

mrshu commented Jul 1, 2017

But what if this problem persists for a longer time and the bot will not be able to send any rss feed?

If my reading of the code currently in master is correct, the fix would only made sure that the execution gets past this line and thus the other messages should get delivered and the cache cleared. Should the issue with the shortener fix itself, the link should be sendable next time.

Does that make sense?

@Adman
Copy link
Member

Adman commented Jul 1, 2017

Makes sense.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants